CA2480864C - A method of registering and deregistering a user - Google Patents
A method of registering and deregistering a user Download PDFInfo
- Publication number
- CA2480864C CA2480864C CA2480864A CA2480864A CA2480864C CA 2480864 C CA2480864 C CA 2480864C CA 2480864 A CA2480864 A CA 2480864A CA 2480864 A CA2480864 A CA 2480864A CA 2480864 C CA2480864 C CA 2480864C
- Authority
- CA
- Canada
- Prior art keywords
- request
- node
- register
- user equipment
- deregister
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/12—Mobility data transfer between location registers or mobility servers
Abstract
The invention comprises a method for registering and deregistering user equipment from a communications system and comprises the steps of sending a request to a first node to register or deregister the user equipment from or to the communications system, determining at the first node to determine if the request is a request to register or a request to deregister, and carrying out at one least predetermined operation at a second node only if the request is a request to register.
Description
A method of registering and deregistering a user Field of the Invention The present invention relates to a method of registering and deregistering a user to and from a communications network and in particular but not exclusively a method for use with a wireless communications network.
Background of the Invention A communication. system can be seen as a facility that enables communication between two or more entities such as user equipment and other nodes associated with the system. A communication system typically operates in accordance with a given standard or specification which sets out what the various elements of the system are permitted to do and how that should be achieved. For example, the standard or specification may define if the user, or more precisely the user equipment or terminal, is provided with a packet switch server and/or a circuit switch server.
Communication protocol and/or parameters which are used for the connection may also be defined. In other words, a specific set of "rules" in which the communication can be made need to be defined in order to enable communication by means of the system.
Communication systems providing wireless communication for the user terminal or other nodes are known. An example of the wireless system is a cellular network. In cellular systems, a base transceiver station (BTS) or similar access entity serves mobile stations (MS) or similar wireless user equipment (UE) via a wireless interface between these entities. The operation of the base station and the nodes required for the communication can be controlled by one or several control entities. The various control entities may be interconnected. One or more gateway nodes may also be provided for connecting the cellular network to other networks such as to a public switched telephone network (PSTN) and/or other communication networks such as an IP (internet protocol) and/or other packet switch network.
A communication system may be adapted to provide wireless data communication services. A communication system may be adapted to provide wireless data communication services such as packet switched (PS) services for a mobile station.
Examples of systems enabling wireless data communication services, without limitation to these include the general packet radio service (GPRS), the enhanced data rate for GSM evolution (EDGE) mobile data network, the so-called third generation (3G) telecommunication systems such as the universal mobile telecommunication system (UNITS), i-phone or IMT-2000 (international mobile telecommunication) and the terrestrial trunked radio (TETRA) system.
In the third generation system, it has been proposed to provide multimedia network architecture. It is intended that a multimedia architecture be able to handle different kinds of data such as voice, audio, video, data per se and indeed any other type of media. It has been proposed to have an IP (internet protocol) multimedia subsystem for such network architecture. Thus, the subsystem of the architecture is arranged to transfer the data between the various entities and packet data form, in accordance with the internet protocol.
More particularly, the IP multimedia subsystem comprises core network elements for the provision of a multimedia service. This includes the collection of signalling and bearer related network elements. The IP multimedia core network is arranged to enable PLMN operators to offer their subscribers multimedia services based on and build upon internet applications, services and protocols. It is intended that the IP
multimedia core network subsystem should enable convergence of and access to voice, video, messaging, data and web based technology for wireless users. The proposed third generation multimedia network architecture may have several different servers for handling different functions. These include functions such as the call state control functions (CSCF) . This function is sometimes called the session control function. The call state control function may comprise functions such as a proxy call state control function (P-CSCF), interrogating call state control function (I-CSCF) and serving call state control function (S-CSCF).
Control functions may also be provided by entities such as a home subscriber server (HSS) and various application services.
Reference is made to the current versions of the third generation specifications: Third Generation Partnership Project; Technical Specification Group Core Network; CX and DX
Interface Based on the Diameter Protocol; (release 5) , 3GPP
TS29.229 V1.1.0 and IP Multimedia (IM) Subsystem CX and DX
Interfaces; Signalling Flows and Message Contents; (release 5) 3GPP TS29.228 V1.1Ø In these specifications, a CX interface is defined. The CX interface is the interface between the home subscriber server and the interrogating call state control functions. The CX interface is also the interface between the home subscriber server and the serving call state control function. In the currently proposed specifications, the same message is used both to register a user and to deregister a user. At present it cannot be distinguished whether the message is to register or to deregister.
Accordingly, every time this message is received by a CSCF, the HSS needs to check if the user really exists and that the user is allowed to register to a particular visited network.
The HSS also checks to see if a CSCF has already been assigned. Accordingly, with the current proposals, the user will send a register message, if the user wants to register or deregister. Regardless of whether the user is registering or deregistering, all of the checks will be made by the HSS.
It has been appreciated by the inventor that all of these checks are not required for deregistration. Thus, the use of the same message for registration and deregistration is disadvantageous in that unnecessary processing is required.
This unnecessarily slows down the process of deregistration and also unnecessarily uses up the HSS resources.
Summary of the Invention It is therefore an aim of embodiments of the present invention to address or at least mitigate one of the problems described above.
According to a further broad aspect of the present invention there is provided a method comprising: receiving at a second node from a first node a message indicating the result of a determination at the first node as to whether a request to register or deregister user equipment to or from a communications system is a request to register or a request to deregister; and carrying out at least one predetermined operation at said second node only if said request is a request to register.
According to a still further broad aspect of the present invention there is provided a method comprising: receiving at a first node a request to register or deregister user equipment to or from a communication system; checking at the first node to determine if said request is a request to register or if said request is a request to deregister; and 5 sending to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
According to a still further broad aspect of the present invention there is provided an apparatus, which is configured to: receive from a first node at a second node a message indicating the result of a determination at said first node as to whether a request to register and deregister user equipment to or from a network is a request to register or a request to deregister; and carry out at said second node at least one predetermined check only if said request is a request to register.
According to a still further broad aspect of the present invention there is provided an apparatus, comprising: means for receiving at a first node a request to register or deregister user equipment to or from a communications system;
means for checking at said first node if said request is a request to register or a request to deregister; and means for sending from said first node to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
Brief Description of the Drawings For a better understanding of the present invention and as to how the same may be carried into effect reference will now be made by way of example to the accompanying drawings in which:
Figure 1 shows a communication system architecture in which embodiments of the present invention can be incorporated;
Figure 2 shows an information flow in accordance with the currently proposed specification for registration;
Figure 3 shows an information flow in accordance with the currently proposed specification for registration;
Figure 4 shows an information flow in accordance with an embodiment of the present invention; and Figure 5 shows a flow chart of a method embodying the present invention.
Description of Preferred Embodiments of the Present Invention Reference is made first to Figure 1 which shows a possible network system architecture in which embodiments of the present invention can be incorporated. The exemplifying network system is arranged in accordance with UTMS 3G
specifications. However, it should be appreciated that alternative embodiments of the present invention may be used with other third generation specifications or indeed with any other suitable standard. A user equipment 10 is connectable to a radio access network 12. This connection between the user equipment 10 and the radio access network 12 is via a wireless connection 11. The user equipment 10 can take any suitable form and may for example be a mobile telephone, a portable computer, a personal digital assistant (PDA) or any other suitable wireless equipment.
The wireless equipment may or may not be mobile.
The radio access network 12 consists of at least a base station and usually also a controller. The radio access network 12 is connected to a GPRS core network.
For example, the RAN 12 may be connected to an SGSN 30 (serving GPRS support node). The SGSN 30 in turn may be connected to a GGSN 32 (gateway GPRS
support node). The GGSN and SGSN constitute the GPRS network 14. The GGSN
is connected to the DHCP (dynamic host configuration protocol) 15. The DHCP 15 is used to provide user equipment 10 with a domain name of a proxy-CSCF node 16.
The P-CSCF node 16 is connected to the GGSN 32. The domain name server DNS
18 is connected to the P-CSCF 16 and to the SGSN 30. The elements marked in box 34 can be regarded as being a visited network, that is the RAN 12, the SGSN 30, the GGSN 32, the DNS 18, and P-CSCF.
The home network is marked in block 36. The home network 36 is the network with which the user is associated and from which the user is billed etc. The connection between the visited and home networks are via the P-CSCF 16 of the visited network and an I-CSCF 20 of the home network. Between the P-CSCF 16 and I-CSCF 20 is a backbone network or other form of connection. The I-CSCF of the home network 20 is connected to an S-CSCF 22. Both of these CSCFs 20 and 22 are connected to the HSS 24. The S-CSCF 22 is the serving call state control function and is a server currently serving at least one of the user equipment and is in control of the status of that user equipment. The home subscriber server entity 24 is used for storing registration identities, similar user related information and the like.
Reference will now be made to Figure 2 which shows the currently procedure for registering a user.
Background of the Invention A communication. system can be seen as a facility that enables communication between two or more entities such as user equipment and other nodes associated with the system. A communication system typically operates in accordance with a given standard or specification which sets out what the various elements of the system are permitted to do and how that should be achieved. For example, the standard or specification may define if the user, or more precisely the user equipment or terminal, is provided with a packet switch server and/or a circuit switch server.
Communication protocol and/or parameters which are used for the connection may also be defined. In other words, a specific set of "rules" in which the communication can be made need to be defined in order to enable communication by means of the system.
Communication systems providing wireless communication for the user terminal or other nodes are known. An example of the wireless system is a cellular network. In cellular systems, a base transceiver station (BTS) or similar access entity serves mobile stations (MS) or similar wireless user equipment (UE) via a wireless interface between these entities. The operation of the base station and the nodes required for the communication can be controlled by one or several control entities. The various control entities may be interconnected. One or more gateway nodes may also be provided for connecting the cellular network to other networks such as to a public switched telephone network (PSTN) and/or other communication networks such as an IP (internet protocol) and/or other packet switch network.
A communication system may be adapted to provide wireless data communication services. A communication system may be adapted to provide wireless data communication services such as packet switched (PS) services for a mobile station.
Examples of systems enabling wireless data communication services, without limitation to these include the general packet radio service (GPRS), the enhanced data rate for GSM evolution (EDGE) mobile data network, the so-called third generation (3G) telecommunication systems such as the universal mobile telecommunication system (UNITS), i-phone or IMT-2000 (international mobile telecommunication) and the terrestrial trunked radio (TETRA) system.
In the third generation system, it has been proposed to provide multimedia network architecture. It is intended that a multimedia architecture be able to handle different kinds of data such as voice, audio, video, data per se and indeed any other type of media. It has been proposed to have an IP (internet protocol) multimedia subsystem for such network architecture. Thus, the subsystem of the architecture is arranged to transfer the data between the various entities and packet data form, in accordance with the internet protocol.
More particularly, the IP multimedia subsystem comprises core network elements for the provision of a multimedia service. This includes the collection of signalling and bearer related network elements. The IP multimedia core network is arranged to enable PLMN operators to offer their subscribers multimedia services based on and build upon internet applications, services and protocols. It is intended that the IP
multimedia core network subsystem should enable convergence of and access to voice, video, messaging, data and web based technology for wireless users. The proposed third generation multimedia network architecture may have several different servers for handling different functions. These include functions such as the call state control functions (CSCF) . This function is sometimes called the session control function. The call state control function may comprise functions such as a proxy call state control function (P-CSCF), interrogating call state control function (I-CSCF) and serving call state control function (S-CSCF).
Control functions may also be provided by entities such as a home subscriber server (HSS) and various application services.
Reference is made to the current versions of the third generation specifications: Third Generation Partnership Project; Technical Specification Group Core Network; CX and DX
Interface Based on the Diameter Protocol; (release 5) , 3GPP
TS29.229 V1.1.0 and IP Multimedia (IM) Subsystem CX and DX
Interfaces; Signalling Flows and Message Contents; (release 5) 3GPP TS29.228 V1.1Ø In these specifications, a CX interface is defined. The CX interface is the interface between the home subscriber server and the interrogating call state control functions. The CX interface is also the interface between the home subscriber server and the serving call state control function. In the currently proposed specifications, the same message is used both to register a user and to deregister a user. At present it cannot be distinguished whether the message is to register or to deregister.
Accordingly, every time this message is received by a CSCF, the HSS needs to check if the user really exists and that the user is allowed to register to a particular visited network.
The HSS also checks to see if a CSCF has already been assigned. Accordingly, with the current proposals, the user will send a register message, if the user wants to register or deregister. Regardless of whether the user is registering or deregistering, all of the checks will be made by the HSS.
It has been appreciated by the inventor that all of these checks are not required for deregistration. Thus, the use of the same message for registration and deregistration is disadvantageous in that unnecessary processing is required.
This unnecessarily slows down the process of deregistration and also unnecessarily uses up the HSS resources.
Summary of the Invention It is therefore an aim of embodiments of the present invention to address or at least mitigate one of the problems described above.
According to a further broad aspect of the present invention there is provided a method comprising: receiving at a second node from a first node a message indicating the result of a determination at the first node as to whether a request to register or deregister user equipment to or from a communications system is a request to register or a request to deregister; and carrying out at least one predetermined operation at said second node only if said request is a request to register.
According to a still further broad aspect of the present invention there is provided a method comprising: receiving at a first node a request to register or deregister user equipment to or from a communication system; checking at the first node to determine if said request is a request to register or if said request is a request to deregister; and 5 sending to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
According to a still further broad aspect of the present invention there is provided an apparatus, which is configured to: receive from a first node at a second node a message indicating the result of a determination at said first node as to whether a request to register and deregister user equipment to or from a network is a request to register or a request to deregister; and carry out at said second node at least one predetermined check only if said request is a request to register.
According to a still further broad aspect of the present invention there is provided an apparatus, comprising: means for receiving at a first node a request to register or deregister user equipment to or from a communications system;
means for checking at said first node if said request is a request to register or a request to deregister; and means for sending from said first node to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
Brief Description of the Drawings For a better understanding of the present invention and as to how the same may be carried into effect reference will now be made by way of example to the accompanying drawings in which:
Figure 1 shows a communication system architecture in which embodiments of the present invention can be incorporated;
Figure 2 shows an information flow in accordance with the currently proposed specification for registration;
Figure 3 shows an information flow in accordance with the currently proposed specification for registration;
Figure 4 shows an information flow in accordance with an embodiment of the present invention; and Figure 5 shows a flow chart of a method embodying the present invention.
Description of Preferred Embodiments of the Present Invention Reference is made first to Figure 1 which shows a possible network system architecture in which embodiments of the present invention can be incorporated. The exemplifying network system is arranged in accordance with UTMS 3G
specifications. However, it should be appreciated that alternative embodiments of the present invention may be used with other third generation specifications or indeed with any other suitable standard. A user equipment 10 is connectable to a radio access network 12. This connection between the user equipment 10 and the radio access network 12 is via a wireless connection 11. The user equipment 10 can take any suitable form and may for example be a mobile telephone, a portable computer, a personal digital assistant (PDA) or any other suitable wireless equipment.
The wireless equipment may or may not be mobile.
The radio access network 12 consists of at least a base station and usually also a controller. The radio access network 12 is connected to a GPRS core network.
For example, the RAN 12 may be connected to an SGSN 30 (serving GPRS support node). The SGSN 30 in turn may be connected to a GGSN 32 (gateway GPRS
support node). The GGSN and SGSN constitute the GPRS network 14. The GGSN
is connected to the DHCP (dynamic host configuration protocol) 15. The DHCP 15 is used to provide user equipment 10 with a domain name of a proxy-CSCF node 16.
The P-CSCF node 16 is connected to the GGSN 32. The domain name server DNS
18 is connected to the P-CSCF 16 and to the SGSN 30. The elements marked in box 34 can be regarded as being a visited network, that is the RAN 12, the SGSN 30, the GGSN 32, the DNS 18, and P-CSCF.
The home network is marked in block 36. The home network 36 is the network with which the user is associated and from which the user is billed etc. The connection between the visited and home networks are via the P-CSCF 16 of the visited network and an I-CSCF 20 of the home network. Between the P-CSCF 16 and I-CSCF 20 is a backbone network or other form of connection. The I-CSCF of the home network 20 is connected to an S-CSCF 22. Both of these CSCFs 20 and 22 are connected to the HSS 24. The S-CSCF 22 is the serving call state control function and is a server currently serving at least one of the user equipment and is in control of the status of that user equipment. The home subscriber server entity 24 is used for storing registration identities, similar user related information and the like.
Reference will now be made to Figure 2 which shows the currently procedure for registering a user.
In step S1, the user equipment 10 sends a register request from the user equipment to the P-CSCF 16. The purpose of this request is to register the users SIP
(session internet protocol) uniform resource identifier with a CSCF 22 in the home network.
This request is routed to the P-CSCF 16 because it is the contact point with the IP
multimedia subsystem for the user equipment. The register message may include the following information: private identity, public identity, home domain name and the requested expiration time of the registration; content length, destination domain for the request; the IP address of SIP session allocated; the IP address of the user and authorisation information.
In step S2, the P-CSCF 16 determines that the user equipment 10 is registering from a visiting domain and performs a domain name server query DNS18 to locate the (-CSCF 20 in the home network. The lookup table in the DNS 18 is based on an address specified in the URL of the request. The P-CSCF 16 sends the register request, originating from the user equipment 10 to the I-CSCF 20 identified.
In step S3, the I-CSCF 20 makes a request for information relating to the subscriber (ie the user) registration status by sending a query to the HSS in the form of a user authorisation request (UAR) command. This request is sent to the HSS in order to request the authorisation of the registration of a multimedia user. The HSS 24 validates whether identities provided for example private or public identities, belong to the same user. Additionally, the HSS 24 may check whether the user has already registered and/or whether the user is authorised to register in the network where the user is roaming.
In step S4, the HSS sends a reply to the I-CSCF in the form of a user authorisation answer (UAA) command. If the user has been authorised to register and a server is already assigned to it, the message will contain the SIP URL of the server so that the registration request can be forwarded. If the user has been authorised and the server has not yet been assigned, instead server capability information may be provided which can be used for the selection of the server that will perform the control of the services for the multimedia user.
This information is sent from the HSS 24 to the I-CSCF 20.
Based on the information received from the HSS 24, the I-CSCF 20 selects the appropriate S-CSCF 22. Where the S-CSCF 22 is not identified, the I-CSCF uses the capability information provided by the HSS to choose an appropriate S-CSCF.
Where the HSS 24 provides information identifying the S-CSCF, then the identified S-CSCF is used. In step S5, the I-CSCF 20 forwards the register message to the selected S-CSCF 22.
In step S6, a multimedia authorisation request (MAR) is sent from the S-CSCF
22 to.
the HSS 24 in order to request security information.
The HSS 24, in response to the MAR command, selects an authentication vector to be used in order to challenge the user. The S-CSCF may also indicate to the HSS
24 that it has been assigned to serve the particular user, in the step.
In step S7, the HSS sends a multimedia authentication answer MAA command to the S-CSCF which provides the requested authentication vectors.
In step S8, the S-CSCF sends an authentication challenge to the I-CSCF 20 including the provided authentication vector. In step S9, the challenge is forwarded by the I-CSCF 20 to the P-CSCF 16.
In step S10, the authentication challenge is forwarded by the P-CSCF 16 to the user equipment 10.
In step S11, the user equipment 10 generates a response to the authentication challenge and sends back response to the P-CSCF 16 in a further register message.
Steps S12 to S15 are similar to steps S2 to S5 and are carried out to forward the register message to the S-CSCF 22. The S-CSCF 22 then carries out an 5 authentication procedure based on the response from the user equipment. In step S16, the S-CSCF 22 sends a server assignment request (SAR) command. This effectively requests that the HSS 24 indicate that the S-CSCF 22 is serving a particular user. In step S17, a server assignment answer is sent from the HSS
to the S-CSCF 22 which effectively provides confirmation that the S-CSCF 22 is to provide 10 the required service to the user. In step S18, a message is sent from the S-to the I-CSCF 20 effectively confirming the user is registered. This message is forwarded by the I-CSCF to the P-CSCF in step S19 and from the P-CSCF 16 to the user equipment 10 in step S20.
Reference will now be made to Figure 3 which shows the procedure for the deregistration of an already registered user. Steps T1 to T5 are similar to steps S1 to S5 of Figure 2. However, there is no need to do the S-CSCF selection as this will have already been done. As the user is already registered, the next step after stepT5 will be steps T6 and T7 which are the same as steps S18 and S19 of Figure 2.
The register message sent by the user equipment contains information that the user equipment wishes to deregister. Nevertheless, the I-CSCF still needs to interrogate the HSS and the HSS still needs to provide the correct command. The SAR
command in step T6 will indicate to the HSS that the user is deregistering.
This is only after the HSS has been interrogated for example to check if the user is permitted to roam to the network to which it is currently attached. The HSS will be suitably updated. The SAA message in step T7 confirms to the S-CSCF that the mobile station can be deregistered. Steps T8 to T10 are the forwarding of the acknowledgement of this to the mobile station.
Reference will now be made to an embodiment of the present invention. In embodiments of the present invention, the register procedure is as outlined in relation to Figure 2. However, a different procedure is provided for the deregistration procedure. In this regard, reference is made to Figure 4.
Figure 4 shows the signal flow during a deregistration procedure. In the first step Q1, a register message is sent from the user equipment to the P-CSCF 16. This is the same as step S1 in Figure 2. In step Q2, the P-CSCF sends the register message to the I-CSCF 20. Again, this is the same as step S2 in Figure 2.
Reference is made to Figure 5 which shows the method carried out by the I-CSCF
20. In step Al, the register message is received. In step A2, the I-CSCF 20 checks the value of the expires header field which contains the requested expiry time in the SIP REGISTER message In particular in step A3, the I-CSCF checks if the value is 0. If it is, the next step is A4. The value 0 is taken to indicate that the message is a deregister message. If it is determined that the message is a deregister message then an attribute or field in a UAR message is set to indicate that the message is a deregistration message. That message is sent in step Q3 to the HSS 24. If the UAR
message received indicates that the message is a deregister message then the HSS
does not carry out the roaming analysis, that is the determination as to whether or not the user equipment is entitled to operate with the network to which it is currently attached.
If the value is determined in step A3 not to be 0, then the next step is A6.
The registration type in the UAR message is set to indicate that the message is a register message. On receipt of the UAR message, in step A7, the HSS will carry out the roaming analysis. It should be appreciated that UAR message sent in step Q3 to the HSS 24 from the I-CSCF 20 is similar to that sent in step S3 with the additional information as to whether or not the user wishes to register or deregister.
Alternatively it can be exactly the same as in step S3 as long as there has been defined different messages for registration and deregistration.
As mentioned already, the HSS will not carry out a roaming analysis if the message is a deregister message. The next step will be step Q4 which is the same as step S4 in Figure 2. The next step Q5 involves the I-CSCF sending the register message to the S-CSCF. Steps Q6 to Q10 are the same as steps T6 to T10 of Figure 3.
It should be appreciated that the UAR message embodying the present invention will have may have the following fields:
Diameter header Session identity Authorised application identity Authorised session state Origin host Origin realm Destination host Destination realm User name Public identity Visited network identity Registration type - whether or not the message is a registration or deregistration message Embodiments of the present invention have been described particularly in relation to a third generation telecommunications system. It should be appreciated that alternative embodiments of the present invention may be used in any suitable standard. Embodiments of the present invention have been described in the context of an IP multimedia subsystem. It should be appreciated that embodiments of the present invention may be used with any other system.
(session internet protocol) uniform resource identifier with a CSCF 22 in the home network.
This request is routed to the P-CSCF 16 because it is the contact point with the IP
multimedia subsystem for the user equipment. The register message may include the following information: private identity, public identity, home domain name and the requested expiration time of the registration; content length, destination domain for the request; the IP address of SIP session allocated; the IP address of the user and authorisation information.
In step S2, the P-CSCF 16 determines that the user equipment 10 is registering from a visiting domain and performs a domain name server query DNS18 to locate the (-CSCF 20 in the home network. The lookup table in the DNS 18 is based on an address specified in the URL of the request. The P-CSCF 16 sends the register request, originating from the user equipment 10 to the I-CSCF 20 identified.
In step S3, the I-CSCF 20 makes a request for information relating to the subscriber (ie the user) registration status by sending a query to the HSS in the form of a user authorisation request (UAR) command. This request is sent to the HSS in order to request the authorisation of the registration of a multimedia user. The HSS 24 validates whether identities provided for example private or public identities, belong to the same user. Additionally, the HSS 24 may check whether the user has already registered and/or whether the user is authorised to register in the network where the user is roaming.
In step S4, the HSS sends a reply to the I-CSCF in the form of a user authorisation answer (UAA) command. If the user has been authorised to register and a server is already assigned to it, the message will contain the SIP URL of the server so that the registration request can be forwarded. If the user has been authorised and the server has not yet been assigned, instead server capability information may be provided which can be used for the selection of the server that will perform the control of the services for the multimedia user.
This information is sent from the HSS 24 to the I-CSCF 20.
Based on the information received from the HSS 24, the I-CSCF 20 selects the appropriate S-CSCF 22. Where the S-CSCF 22 is not identified, the I-CSCF uses the capability information provided by the HSS to choose an appropriate S-CSCF.
Where the HSS 24 provides information identifying the S-CSCF, then the identified S-CSCF is used. In step S5, the I-CSCF 20 forwards the register message to the selected S-CSCF 22.
In step S6, a multimedia authorisation request (MAR) is sent from the S-CSCF
22 to.
the HSS 24 in order to request security information.
The HSS 24, in response to the MAR command, selects an authentication vector to be used in order to challenge the user. The S-CSCF may also indicate to the HSS
24 that it has been assigned to serve the particular user, in the step.
In step S7, the HSS sends a multimedia authentication answer MAA command to the S-CSCF which provides the requested authentication vectors.
In step S8, the S-CSCF sends an authentication challenge to the I-CSCF 20 including the provided authentication vector. In step S9, the challenge is forwarded by the I-CSCF 20 to the P-CSCF 16.
In step S10, the authentication challenge is forwarded by the P-CSCF 16 to the user equipment 10.
In step S11, the user equipment 10 generates a response to the authentication challenge and sends back response to the P-CSCF 16 in a further register message.
Steps S12 to S15 are similar to steps S2 to S5 and are carried out to forward the register message to the S-CSCF 22. The S-CSCF 22 then carries out an 5 authentication procedure based on the response from the user equipment. In step S16, the S-CSCF 22 sends a server assignment request (SAR) command. This effectively requests that the HSS 24 indicate that the S-CSCF 22 is serving a particular user. In step S17, a server assignment answer is sent from the HSS
to the S-CSCF 22 which effectively provides confirmation that the S-CSCF 22 is to provide 10 the required service to the user. In step S18, a message is sent from the S-to the I-CSCF 20 effectively confirming the user is registered. This message is forwarded by the I-CSCF to the P-CSCF in step S19 and from the P-CSCF 16 to the user equipment 10 in step S20.
Reference will now be made to Figure 3 which shows the procedure for the deregistration of an already registered user. Steps T1 to T5 are similar to steps S1 to S5 of Figure 2. However, there is no need to do the S-CSCF selection as this will have already been done. As the user is already registered, the next step after stepT5 will be steps T6 and T7 which are the same as steps S18 and S19 of Figure 2.
The register message sent by the user equipment contains information that the user equipment wishes to deregister. Nevertheless, the I-CSCF still needs to interrogate the HSS and the HSS still needs to provide the correct command. The SAR
command in step T6 will indicate to the HSS that the user is deregistering.
This is only after the HSS has been interrogated for example to check if the user is permitted to roam to the network to which it is currently attached. The HSS will be suitably updated. The SAA message in step T7 confirms to the S-CSCF that the mobile station can be deregistered. Steps T8 to T10 are the forwarding of the acknowledgement of this to the mobile station.
Reference will now be made to an embodiment of the present invention. In embodiments of the present invention, the register procedure is as outlined in relation to Figure 2. However, a different procedure is provided for the deregistration procedure. In this regard, reference is made to Figure 4.
Figure 4 shows the signal flow during a deregistration procedure. In the first step Q1, a register message is sent from the user equipment to the P-CSCF 16. This is the same as step S1 in Figure 2. In step Q2, the P-CSCF sends the register message to the I-CSCF 20. Again, this is the same as step S2 in Figure 2.
Reference is made to Figure 5 which shows the method carried out by the I-CSCF
20. In step Al, the register message is received. In step A2, the I-CSCF 20 checks the value of the expires header field which contains the requested expiry time in the SIP REGISTER message In particular in step A3, the I-CSCF checks if the value is 0. If it is, the next step is A4. The value 0 is taken to indicate that the message is a deregister message. If it is determined that the message is a deregister message then an attribute or field in a UAR message is set to indicate that the message is a deregistration message. That message is sent in step Q3 to the HSS 24. If the UAR
message received indicates that the message is a deregister message then the HSS
does not carry out the roaming analysis, that is the determination as to whether or not the user equipment is entitled to operate with the network to which it is currently attached.
If the value is determined in step A3 not to be 0, then the next step is A6.
The registration type in the UAR message is set to indicate that the message is a register message. On receipt of the UAR message, in step A7, the HSS will carry out the roaming analysis. It should be appreciated that UAR message sent in step Q3 to the HSS 24 from the I-CSCF 20 is similar to that sent in step S3 with the additional information as to whether or not the user wishes to register or deregister.
Alternatively it can be exactly the same as in step S3 as long as there has been defined different messages for registration and deregistration.
As mentioned already, the HSS will not carry out a roaming analysis if the message is a deregister message. The next step will be step Q4 which is the same as step S4 in Figure 2. The next step Q5 involves the I-CSCF sending the register message to the S-CSCF. Steps Q6 to Q10 are the same as steps T6 to T10 of Figure 3.
It should be appreciated that the UAR message embodying the present invention will have may have the following fields:
Diameter header Session identity Authorised application identity Authorised session state Origin host Origin realm Destination host Destination realm User name Public identity Visited network identity Registration type - whether or not the message is a registration or deregistration message Embodiments of the present invention have been described particularly in relation to a third generation telecommunications system. It should be appreciated that alternative embodiments of the present invention may be used in any suitable standard. Embodiments of the present invention have been described in the context of an IP multimedia subsystem. It should be appreciated that embodiments of the present invention may be used with any other system.
Claims (29)
1. A method comprising:
receiving at a second node from a first node a message indicating the result of a determination at the first node as to whether a request to register or deregister user equipment to or from a communications system is a request to register or a request to deregister; and carrying out at least one predetermined operation at said second node only if said request is a request to register.
receiving at a second node from a first node a message indicating the result of a determination at the first node as to whether a request to register or deregister user equipment to or from a communications system is a request to register or a request to deregister; and carrying out at least one predetermined operation at said second node only if said request is a request to register.
2. A method as claimed in claim 1, wherein said message includes an identifier set in dependence on if the request is a request to register or a request to deregister.
3. A method as claimed in claim 1 or claim 2 wherein said at least one predetermined operation comprises checking if the user equipment is permitted to register with a network to which the user equipment is currently attached.
4. A method comprising:
receiving at a first node a request to register or deregister user equipment to or from a communication system;
checking at the first node to determine if said request is a request to register or if said request is a request to deregister; and sending to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
receiving at a first node a request to register or deregister user equipment to or from a communication system;
checking at the first node to determine if said request is a request to register or if said request is a request to deregister; and sending to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
5. A method as claimed in claim 4, comprising setting in said message an identifier in dependence on if the request is a request to register or a request to deregister.
6. A method as claimed in claim 4 wherein said checking comprises checking information in a header field of said request.
7. A method as claimed in claim 6, wherein said header field is an expires header field.
8. A method as claimed in claim 7, wherein said expires header field has one value if the request is a request to register and a different value if the request is a request to deregister.
9. A method as claimed in any of claims 1 to 8, wherein said message requests authorization of the user equipment from the second node.
10. A method as claimed in any of claims 1 to 9, wherein said first node is a call state control function or call session control function.
11. A method as claimed in any of claims 1 to 10, wherein said first node is an interrogating call state control function node.
12. A method as claimed in any of claims 1 to 11 wherein said second node is a home subscriber server.
13. A method as claimed in any of claims 1 to 12 wherein said message is a user authorisation request message.
14. A method as claimed in any of claims 1 to 13 wherein said request from said user equipment is a SIP REGISTER
message.
message.
15. Apparatus, which is configured to:
receive from a first node at a second node a message indicating the result of a determination at said first node as to whether a request to register and deregister user equipment to or from a network is a request to register or a request to deregister; and carry out at said second node at least one predetermined check only if said request is a request to register.
receive from a first node at a second node a message indicating the result of a determination at said first node as to whether a request to register and deregister user equipment to or from a network is a request to register or a request to deregister; and carry out at said second node at least one predetermined check only if said request is a request to register.
16 Apparatus as claimed in claim 15, wherein said at least one predetermined check comprises checking if the user equipment is permitted to register with a network to which the user equipment is currently attached.
17. Apparatus as claimed in claim 15 or claim 16, wherein the message from the first node includes an identifier set in dependence on if the request is a request to register or a request to deregister.
18. Apparatus, comprising:
means for receiving at a first node a request to register or deregister user equipment to or from a communications system;
means for checking at said first node if said request is a request to register or a request to deregister; and means for sending from said first node to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
means for receiving at a first node a request to register or deregister user equipment to or from a communications system;
means for checking at said first node if said request is a request to register or a request to deregister; and means for sending from said first node to a second node a message including an indication of whether the request is a request to register or whether the request is a request to deregister.
19. A method according to claim 1, wherein said user equipment is associated with a home network, and said request is a request to register or deregister said user equipment to or from a visiting network; said request is received from said visiting network; said first node is a node of said home network; and said second node is also a node of said home network.
20. Apparatus according to claim 15, wherein said user equipment is associated with a home network; said request is a request to register or deregister said user equipment to or from a visiting network; said first node is a node of said home network; and said second node is also a node of said home network.
21. Apparatus according to claim 18, wherein said first node is a node of a home network with which said user equipment is associated; said request is a request to register or deregister said user equipment to or from a visiting network; and said second node is also a node of said home network.
22. A method according to claim 4, wherein said first node is a node of a home network with which said user equipment is associated; said request is a request to register or deregister said user equipment to or from a visiting network;
and said second node is also a node of said home network.
and said second node is also a node of said home network.
23. A method according to claim 1, wherein said at least one predetermined operation includes a roaming analysis.
24. Apparatus according to claim 15, wherein said at least one predetermined check includes a roaming analysis.
25. A method according to claim 4, wherein said second node is a home subscriber server, and said indication is readable by the home subscriber server.
26. A method according to claim 4, wherein said request is included in a message according to a first protocol; and wherein sending a message to said second node comprises sending to said second node a message according to a second protocol different to said first protocol.
27. Apparatus according to claim 18, wherein said second node is a home subscriber server, and said indication is readable by the home subscriber server.
28. Apparatus according to claim 18, wherein said request is included in a message according to a first protocol; and wherein said means for sending a message to said second node is a means for sending to said second node a message according to a second protocol different to said first protocol.
29. A system including user equipment; apparatus according to any of claims 18, 21, 27 and 28; and apparatus according to any of claims 15 to 17, 20 and 24.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/109,565 US8121597B2 (en) | 2002-03-27 | 2002-03-27 | Method of registering and deregistering a user |
| US10/109,565 | 2002-03-27 | ||
| PCT/IB2003/001410 WO2003081937A1 (en) | 2002-03-27 | 2003-03-25 | A method of registering and deregistering a user |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2480864A1 CA2480864A1 (en) | 2003-10-02 |
| CA2480864C true CA2480864C (en) | 2011-05-31 |
Family
ID=28453137
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2480864A Expired - Lifetime CA2480864C (en) | 2002-03-27 | 2003-03-25 | A method of registering and deregistering a user |
Country Status (9)
| Country | Link |
|---|---|
| US (1) | US8121597B2 (en) |
| EP (1) | EP1488656B1 (en) |
| JP (1) | JP4002895B2 (en) |
| CN (1) | CN1643967B (en) |
| AU (1) | AU2003214573A1 (en) |
| CA (1) | CA2480864C (en) |
| ES (1) | ES2433194T3 (en) |
| RU (1) | RU2316153C2 (en) |
| WO (1) | WO2003081937A1 (en) |
Families Citing this family (45)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100704036B1 (en) * | 2002-01-21 | 2007-04-05 | 노키아 코포레이션 | Method and system for changing a subscription |
| US7139566B2 (en) * | 2002-09-10 | 2006-11-21 | Samsung Electronics Co., Ltd. | Method for informing mobile communication terminal of entrance into specific service network in mobile communication system and method for changing incoming call indication mode to vibration or silent mode |
| US7487199B2 (en) * | 2002-09-24 | 2009-02-03 | Motorola, Inc. | Method and apparatus for maintaining SIP contact addresses |
| US20040234060A1 (en) * | 2003-03-31 | 2004-11-25 | Nokia Corporation | Method and system for deactivating a service account |
| CN1799270A (en) * | 2003-05-02 | 2006-07-05 | 美商内数位科技公司 | Method and architecture for accessing an internet protocol multimedia subsystem (ims) over a wireless local area network (WLAN) |
| US7069002B2 (en) * | 2003-06-30 | 2006-06-27 | Lucent Technologies Inc. | Message waiting indication operable to overcome a border condition between mobile switching centers |
| US7151923B2 (en) * | 2003-06-30 | 2006-12-19 | Lucent Technologies Inc. | Systems for providing message waiting notification updates in a cellular communication network |
| KR100741152B1 (en) * | 2004-01-07 | 2007-07-20 | 후아웨이 테크놀러지 컴퍼니 리미티드 | A method for reducing interface load of home subscriber server |
| US7715856B2 (en) | 2004-06-02 | 2010-05-11 | Interdigital Technology Corporation | Reporting terminal capabilities for supporting short message service |
| GB0417296D0 (en) | 2004-08-03 | 2004-09-08 | Nokia Corp | User registration in a communication system |
| MX2007001408A (en) * | 2004-08-04 | 2007-04-16 | Lg Electronics Inc | Broadcast/multicast service system and method providing inter-network roaming. |
| US7844745B1 (en) * | 2004-08-19 | 2010-11-30 | Nortel Networks Limited | Alternate home subscriber server (HSS) node to receive a request if a first HSS node cannot handle said request |
| CN1642083A (en) * | 2004-09-23 | 2005-07-20 | 华为技术有限公司 | Network side anthority-discrimination-mode selecting method |
| CN1761359B (en) * | 2004-10-12 | 2012-02-29 | 株式会社日立制作所 | Mobile communication control method and communication control system |
| ATE553584T1 (en) * | 2004-12-17 | 2012-04-15 | Tekelec Us | METHODS, SYSTEMS AND COMPUTER PROGRAM PRODUCTS FOR CLUSTERING AND COMMUNICATE BETWEEN INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM (IMS) ENTITIES |
| EP2317725B1 (en) * | 2005-04-01 | 2012-09-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for initiating IMS based communications |
| US8090392B2 (en) | 2005-08-05 | 2012-01-03 | Interdigital Technology Corporation | Method and system for reporting a short message capability via an IP multimedia subsystem |
| WO2007043849A1 (en) | 2005-10-14 | 2007-04-19 | Samsung Electronics Co., Ltd. | Roaming service method in a mobile broadcasting system, and system thereof |
| KR100856256B1 (en) * | 2005-10-14 | 2008-09-03 | 삼성전자주식회사 | Apparatus and method for supporting roaming service in mobile broadcasting system |
| CN100581286C (en) * | 2005-10-19 | 2010-01-13 | 华为技术有限公司 | Method and system for mobile subscriber device to register mobile Internet protocol |
| CN100527874C (en) * | 2005-10-21 | 2009-08-12 | 华为技术有限公司 | A data inspection method for private service identification |
| US8665862B1 (en) | 2005-10-24 | 2014-03-04 | Apple Inc. | Performing cross-domain deregistration |
| GB2432748A (en) | 2005-11-25 | 2007-05-30 | Ericsson Telefon Ab L M | SIP messaging in an IP Multimedia Subsystem wherein a local user identity is added to message header as a basis for application server processing |
| EP1835686B1 (en) * | 2006-03-13 | 2015-12-23 | Vodafone Group PLC | Method of providing access to an IP multimedia subsystem based on provided access network data. |
| DE102006026929B4 (en) * | 2006-06-09 | 2008-03-06 | Siemens Ag | Method for multiple registration of a multimodal communication terminal |
| US20080014961A1 (en) * | 2006-07-12 | 2008-01-17 | Tekelec | Methods, systems, and computer program products for providing geographically diverse IP multimedia subsystem (IMS) instances |
| US8149725B2 (en) * | 2006-07-31 | 2012-04-03 | Tekelec | Methods, systems, and computer program products for a hierarchical, redundant OAM&P architecture for use in an IP multimedia subsystem (IMS) network |
| US20080155658A1 (en) * | 2006-12-22 | 2008-06-26 | Nokia Corporation | Authentication type selection |
| US20080219241A1 (en) * | 2007-03-09 | 2008-09-11 | Nokia Corporation | Subscriber access authorization |
| WO2009023198A1 (en) * | 2007-08-13 | 2009-02-19 | Nortel Networks Limited | New diameter signaling for mobile ipv4 |
| JP4882966B2 (en) * | 2007-11-12 | 2012-02-22 | 沖電気工業株式会社 | Proxy server, communication program, and communication system |
| CN101577634B (en) * | 2008-05-07 | 2012-01-25 | 华为技术有限公司 | Network-quitting method, network side management device and network system of multi-host system |
| US8085810B2 (en) * | 2008-08-06 | 2011-12-27 | Movik Networks | Cross-layer pipelining optimizations for reduced roundtrips and improving quality of experience |
| US8880067B2 (en) | 2008-08-08 | 2014-11-04 | Qualcomm Incorporated | Correlating registrations originating from a device |
| US9185141B2 (en) * | 2009-05-19 | 2015-11-10 | Telefonaktiebolaget L M Ericsson (Publ) | Managing roaming agreements between IMS networks |
| CN101931934B (en) * | 2009-06-26 | 2014-06-11 | 中兴通讯股份有限公司南京分公司 | User registration method of IP multimedia subsystem (IMS) network and business realizing system |
| CN101931923B (en) * | 2009-06-26 | 2014-10-22 | 中兴通讯股份有限公司 | Method for user registration of IP multimedia subsystem network and service fulfillment system |
| US20110117914A1 (en) * | 2009-11-12 | 2011-05-19 | Electronics And Telecommunications Research Institute | Method and apparatus for deregistration of personal network element(pne) in 3gpp personal network(pn) |
| CN101867918B (en) | 2010-06-04 | 2015-06-03 | 中兴通讯股份有限公司 | Real-name system registration state acquiring method, device and terminal |
| EP2853072B1 (en) * | 2012-05-21 | 2018-02-14 | Telefonaktiebolaget LM Ericsson (publ) | Method and apparatus for handling p-cscf failure and restoring connectivity |
| FR2996096A1 (en) * | 2012-09-24 | 2014-03-28 | France Telecom | METHODS OF VERIFICATION AND CONTROL IN A CORE OF IP MULTIMEDIA NETWORK, AND SERVERS |
| US9380549B2 (en) * | 2014-03-27 | 2016-06-28 | Apple Inc. | Cellular network assisted proximity services registration procedures and event framework for proximity requests/alerts using session initiation protocol |
| WO2016209262A1 (en) * | 2015-06-26 | 2016-12-29 | Hewlett Packard Enterprise Development Lp | Authentication requests |
| CN108881118B (en) * | 2017-05-12 | 2020-07-17 | 大唐移动通信设备有限公司 | IMS (IP multimedia subsystem) cascade networking method and equipment |
| CN112929946B (en) * | 2019-12-06 | 2023-10-17 | 维沃移动通信有限公司 | Processing method of network configuration command and terminal equipment |
Family Cites Families (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE19643658C1 (en) * | 1996-10-22 | 1998-03-26 | Siemens Ag | Cordless mobile communications device calling method |
| US5848055A (en) * | 1996-11-19 | 1998-12-08 | Northern Telecom Limited | Bandwidth correlation means for paths in connection-oriented packet switching networks |
| US6535493B1 (en) * | 1998-01-15 | 2003-03-18 | Symbol Technologies, Inc. | Mobile internet communication protocol |
| US6084866A (en) | 1998-01-21 | 2000-07-04 | Motorola, Inc. | Method and apparatus in a wireless messaging system for minimizing unnecessary communications with coverage zones of differing size and differing bandwidth capacity when entered by a mobile subscriber unit |
| GB2352932B (en) | 1999-07-31 | 2003-10-08 | Ericsson Telefon Ab L M | Charging control in a mobile telecommunications system |
| US7171199B1 (en) | 1999-09-10 | 2007-01-30 | Lucent Technologies Inc. | Method and system for directing a data message in a wireless communications network including multiple wireless systems |
| US6763233B2 (en) * | 2000-01-05 | 2004-07-13 | Nortel Networks Limited | Terminal roaming operations between intergenerational wireless networks |
| US6456234B1 (en) * | 2000-06-07 | 2002-09-24 | William J. Johnson | System and method for proactive content delivery by situation location |
| US20020037723A1 (en) * | 2000-06-08 | 2002-03-28 | Adam Roach | Refreshing service profile information using third-party SIP register messages |
| DE60023359T2 (en) | 2000-08-10 | 2006-07-06 | Nokia Corp. | Method and system for roaming support in UMTS |
| US7170863B1 (en) * | 2001-02-12 | 2007-01-30 | Nortel Networks Limited | Push-to-talk wireless telecommunications system utilizing a voice-over-IP network |
| DE10116547A1 (en) * | 2001-04-03 | 2002-10-10 | Nokia Corp | Registration of a terminal in a data network |
| US6810243B2 (en) * | 2001-04-30 | 2004-10-26 | Lucent Technologies Inc. | Surrogate service attendant |
| AU2001262396B2 (en) * | 2001-05-28 | 2006-06-01 | Nokia Corporation | Charging in telecommunications network |
| US6871070B2 (en) * | 2001-07-31 | 2005-03-22 | Lucent Technologies Inc. | Communication system for providing roaming between an internet protocol multimedia system and a circuit-switched domain |
| US7028089B2 (en) * | 2001-09-21 | 2006-04-11 | International Business Machines Corporation | Method and apparatus for caching subscribed and non-subscribed content in a network data processing system |
-
2002
- 2002-03-27 US US10/109,565 patent/US8121597B2/en not_active Expired - Fee Related
-
2003
- 2003-03-25 AU AU2003214573A patent/AU2003214573A1/en not_active Abandoned
- 2003-03-25 ES ES03710153T patent/ES2433194T3/en not_active Expired - Lifetime
- 2003-03-25 EP EP03710153.2A patent/EP1488656B1/en not_active Expired - Lifetime
- 2003-03-25 WO PCT/IB2003/001410 patent/WO2003081937A1/en active Application Filing
- 2003-03-25 RU RU2004131649/09A patent/RU2316153C2/en active
- 2003-03-25 CN CN038071150A patent/CN1643967B/en not_active Expired - Lifetime
- 2003-03-25 CA CA2480864A patent/CA2480864C/en not_active Expired - Lifetime
- 2003-03-25 JP JP2003579497A patent/JP4002895B2/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| RU2004131649A (en) | 2005-11-20 |
| EP1488656B1 (en) | 2013-08-07 |
| CN1643967A (en) | 2005-07-20 |
| RU2316153C2 (en) | 2008-01-27 |
| CN1643967B (en) | 2012-07-11 |
| US8121597B2 (en) | 2012-02-21 |
| JP4002895B2 (en) | 2007-11-07 |
| CA2480864A1 (en) | 2003-10-02 |
| JP2005521349A (en) | 2005-07-14 |
| ES2433194T3 (en) | 2013-12-09 |
| WO2003081937A1 (en) | 2003-10-02 |
| AU2003214573A1 (en) | 2003-10-08 |
| EP1488656A1 (en) | 2004-12-22 |
| US20040203763A1 (en) | 2004-10-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2480864C (en) | A method of registering and deregistering a user | |
| US9860737B2 (en) | Communication system and method | |
| CA2447049C (en) | Subscriber registrations in a mobile communication system | |
| US7853697B2 (en) | Handling suspended network state of a terminal device | |
| US7583963B2 (en) | User registration in a communication system | |
| US7894593B2 (en) | Callback services in a communication system | |
| EP1835686B1 (en) | Method of providing access to an IP multimedia subsystem based on provided access network data. | |
| EP1611764B1 (en) | Multiple registration of a subscriber in a mobile communication system | |
| EP1864464B1 (en) | Providing an ip multimedia communication session to a mobile user equipment | |
| GB2375004A (en) | Collecting, storing and using information associated with user equipment | |
| US20040243711A1 (en) | Method, system and network element for controlling data transmission in a network environment | |
| KR20030055417A (en) | The Apparatus and Method for the Mobility Management of IP Multimedia Service Subscriber | |
| KR101629815B1 (en) | 3G Mobile Communication System supporting Service Centralized and Continuity and Method thereof | |
| NZ553728A (en) | Method of providing access to an IP multimedia subsystem |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20230327 |