A METHOD FOR TRANSMITTING SPECIFIC APPLICATION DATA IN A CELLULAR NETWORK
Field of the invention
The present invention relates to machine-to-machine communication in the General Packet Radio Service (GPRS) for the Global System for Mobile communications (GSM) network and the Universal Mobile Telephone Service (UMTS) network.
Background of the invention
Machine-to-machine communication relates to the transfer of data directly between communicating data systems without the interaction of human beings. The data concerned may be sensor data, alarm data, control data for an apparatus, data from a mobile payment terminal, etc. In some instances it might be necessary or practical to transfer such data over a wireless link in the cellular network. Especially the modern packet switched mobile networks, GPRS over GSM or GPRS over UMTS are suited for such applications, due to their high data transfer rates.
The user equipment at one end of the transfer link includes a mobile terminal in connection with a cellular network trough a SGSN. The User equipment wants to exchange data with an application server in an external IP network. When the user equipment is about to send data to the external network, an activation procedure is started, whereupon the mobile terminal is authenticated and connected to the external network through a GGSN. The data is then transferred to the external IP network using IP protocols.
However, the current pricing of data transmission in the GPRS network for GSM and UMTS makes it unsuitable for machine-to-machine communication. This prevents the adoption of cellular networks for the transfer of data from mobile or otherwise inaccessible user equipment.
Brief summary of the invention
It is an object of the present invention to provide a method for transmitting specific application data from a User Equipment to an application in the external network, or vice versa, by utilizing the resources in a GSM or a UMTS network more efficiently.
This is achieved in a method as defined in the appended patent claims. In particular, according to the present invention application specific data is transmitted between a User Equipment connected to a Global System for Mobile communications (GSM) network or a Universal Mobile Telephone Service (UMTS) network and an application server in an external IP network by the General Packet Radio Service, by letting a login server authenticate and negotiate IP protocol configurations for the User Equipment, and sending application data from a Terminal or User Equipment transparent through the GSM or UMTS network to the application server in the external network, and vice versa, using Protocol Configuration Options for sending the application data as parameter values.
Brief description of the drawings
In order to make the invention more readily understandable, the discussion that follows will refer to the accompanying drawings, in which:
Fig. 1 gives an overview of the GSM and UMTS networks,
Fig. 2 is a signalling sequence diagram illustrating the PDP context activation procedure for GSM, and
Fig. 3 is the corresponding signalling sequence diagram illustrating the PDP context activation procedure for UMTS.
Detailed description of preferred embodiments
This invention make use of existing control signals to carry application specific data, by enhancing the use of certain control parameters.
In packet switched cellular communication networks, like GPRS for GSM and UMTS, User Equipment performs a Packet Data Protocol (PDP) context activation procedure to establish a communication path towards an external network in order to access the services and facilities of that external network. This procedure is described in the recommendation of the 3GPP TS 23.060.
In connection with the PDP context activation procedure, a set of parameters, i.e. the Protocol Configuration Options parameters, may be sent from the User Equipment to the GGSN for authentication and IP protocol configuration. The parameters are however
forwarded transparently in the case when the external network is responsible for authentication and IP protocol configuration.
In the external network these parameters are received, and handled according to defined rules. This invention makes use of these Protocol Configuration Options for the purpose of sending specific application information, both from the User Equipment to an application in the external network, as well as sending information from the external network to the User Equipment.
According to current standard 3 GPP TS 24.008, the Protocol Configuration Options are coded according to RFC 1700, carrying protocol configuration options for LCP, PAP, CHAP and IPCP. This invention makes use of the framework of these protocols, but utilises the parameter values for transmitting specific application data.
Figure 1 shows the logical architecture of the GPRS part of a GSM and a UMTS network. The PDN is referred to as the "external network", this is any network with an IP connection to the GGSN. The TE and MT are referred to as the User Equipment (UE), also called a user terminal.
The User Equipment UE is by default always connected to the Serving GPRS Support Node (SGSN), the procedures for this are described in the 3GPP TS 23.060. The SGSN keeps information of the current location of the UE.
When the UE is about to connect to the external network an activation procedure is started, this procedure is also described in the 3GPP TS 23.060.
When the UE shall connect to the external network, it may be authenticated, the UE must obtain an IP address and some protocol configuration options are negotiated. These tasks may be performed by the GGSN or the external network. This invention is only valid when the external network is handling the authentication or the IP address allocation or the protocol negotiation.
The signalling sequence for the procedure is shown in Figure 2 and Figure 3.
An example:
Before the UE can connect to the external network, several parameters may be set, e.g. username and password. In the case where the authentication (or IP allocation or the
protocol configuration) is done by the external network, these parameters are transparent to the SGSN and GGSN. The parameters is sent as "Protocol Configuration Options" in the message "Activate PDP context request" from the UE to the SGSN, and in the message "Create PDP context request" from SGSN to GGSN.
The interface between the GGSN and the external network is described in 3 GPP TS 29.061. Several protocols are available, e.g. RADIUS, DHCP, PPP (including IPCP, LCP; CHAP, PAP) and L2TP.
The "protocol configuration options" parameters are handled in the GGSN in the way that they are taken from the "Create PDP context request" and mapped (as is) into e.g. a "Radius Authentication Request message" or they are used inside a PPP session between the GGSN and the external network.
The "Radius Authentication Request message" or the "PPP session" is terminated in an application server in the external network, where these parameters may be handled specifically by the application.
In order to send application specific data from the external network to the UE, the
"protocol configuration options" in the messages "Create PDP context response" from GGSN to SGSN and "Activate PDP context response" from SGSN to the UE may be used. This may be done by e.g. using the IPCP parameters "IP address" and/or "IP- Compression-potocol" fields.
In the embodiment of the invention discussed in the example above, some specific protocols and parameters are used to visualize the invention, but the invention is by no means limited to these specifically mentioned protocols/parameters. The scope of the invention is as defined in the appended patent claims.
Abbreviations
CHAP - Challenge Handshake Authentication Protocol DHCP - Dynamic Host Configuration Protocol IPCP - Internet Protocol Control Protocol LCP - Link Control Protocol IP - Internet Protocol
PAP - Password Authentication Protocol PPP - Point-to-Point Protocol
RADIUS- Remote Authentication Dial In User Service
References
3GPP: Technical Specification 23.060.
3GPP: Technical Specification 23.061. 3GPP: Technical Specification 24.008.
IETF: RFC 1700