Procedure and system for transmission of data

• US 20030140224A1
• Filed: 12/23/2002
• Published: 07/24/2003
• Est. Priority Date: 06/21/2000
• Status: Abandoned Application

• Current Assignee: Sonera Oyj
• Original Assignee: Sonera Oyj
• Inventors: Vatanen, Harri
• Application Number:
  US10/328,390
• Publication Number:
  US 20030140224A1
• Time in Patent Office: Days
• US Class Current: 713/153
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/48 Secure or trusted billing, e.g. trusted elements or encryption
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/67 Transmitting arrangements for sending billing related information
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 2215/0156 Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
• CPC Class Codes: H04M 2215/0164 Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
• CPC Class Codes: H04M 2215/2026 Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/22 Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/48 Sending information over a non-traffic network channel or another connection than the one actually used, e.g. signalling, D-channel, data and voice
• CPC Class Codes: H04M 2215/54 Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

A method and system for the handling of a transaction request sent to a server from a terminal device over a telecommunication network, where the transaction request includes identifying data of the requester, identifying data of a utilized network component, and the digital signature of the requester. In response to the transaction request, a transaction message is sent from the server to the terminal device and/or to identified utilized network component. Message-type data and subscriber data are appended to the transaction message before it is sent by the server. The appended message-type data and subscriber data are then extracted from the transaction message in the telecommunication network and are used as handling data for carrying out and otherwise in connection with the transaction.

Claims

1. A method for handling transaction data in a telecommunications network in which a transaction request is sent to a server from a terminal device of a requester, the transaction request comprising identifying data of the requester, identifying data of a utilized network component and a digital signature of the requester, and wherein a transaction message is sent from the server to one of the terminal device and the identified network component in response to the transaction request, said method comprising the steps of:

attaching to the transaction message, prior to said sending of the transaction message from the server to one of the terminal device and the network component, message-type data and subscriber data;

collecting, in the telecommunications network, the message-type data and the subscriber data from the sent transaction message; and

using the collected message-type data and subscriber data as handling data for a transaction that is the subject of the transaction request.

2. A method in accordance with claim 1, where said collecting step comprises collecting the message-type data and the subscriber data in a billing database.

3. A method in accordance with claim 1, wherein said attaching step comprises attaching the message-type data and the subscriber data to a header part of the transaction message.

4. A method in accordance with claim 1, further comprising the steps of:

forming a data link between the terminal device and the server;

registering the terminal device with the server using a user identity of the terminal device; and

declaring a physical network address of one of the terminal device and another device to which the transaction message is to be sent.

5. A method in accordance with claim 1, further comprising the step of encrypting the transaction request to be sent from the terminal device to the server with one of a service-specific encryption key and a server-specific encryption key.

6. A method in accordance with claim 1, further comprising the step of sending a confirmation message from the server to the terminal device in response to receipt of the transaction message.

7. A method in accordance with claim 1, wherein messages sent between the terminal device and the server are sent as short messages.

8. A method in accordance with claim 4, wherein the data link comprises a Bluetooth connection.

9. A method in accordance with claim 4, wherein the data link comprises an infrared connection.

10. A method in accordance with claim 5, wherein said encrypting is effected using a public-private key encryption technique.

11. A method in accordance with claim 1, further comprising the step of forming a communication connection between the terminal device and the server using WAP protocol.

12. A method in accordance with claim 1, further comprising the step of forming a communication connection between the terminal device and the server using HTML protocol.

13. A method in accordance with claim 1, wherein messaging communications between the terminal device and the server are effected using MIME-type messages.

14. A system for handling transaction data in a telecommunications network, comprising:

a server;

a terminal device of a requester for forming and sending a transaction request from the terminal device to the server, wherein the transaction request comprises identifying data of the requester, identifying data of a utilized network component and a digital signature of the requester;

means in said server for forming and sending a transaction message in response to receipt by the server of the transaction request;

an adder for appending message-type data and subscriber data to the transaction message before the transaction message is sent by the server;

a filter in the telecommunications network for extracting the message-type data and the subscriber data from the sent transaction message; and

a handling device in the telecommunications network for using the collected message-type data and subscriber data as handling data for a transaction that is the subject of the transaction request.

15. A system in accordance with claim 14, further comprising a collector for collection of the extracted message-type data and subscriber data and for storing the collected message-type data and subscriber data in a billing database.

16. A system in accordance with claim 14, wherein said adder is operative for attaching the message-type data and the subscriber data to a header part of the transaction message.

17. A system in accordance with claim 14, further comprising means for forming a data link between the terminal device and the server.

18. A system in accordance with claim 14, further comprising registration tools in said terminal device for registering the terminal device with the server using a user identity of the terminal device and for notifying the server of a physical network address of one of the terminal device and another device to which the transaction message is to be sent.