Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/1066—Session management
  • H04L65/1101—Session protocols
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/1066—Session management
  • H04L65/1101—Session protocols
  • H04L65/1104—Session initiation protocol [SIP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/14—Session management
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/14—Session management
  • H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
  • H04W60/005—Multiple registrations, e.g. multihoming

Definitions

• the present invention relates to a method, terminal device and system for registering a user in a communication network, especially in a 3GPP (third generation partnership project) Internet Protocol (IP) Multimedia subsystem (IMS).
• IP Internet Protocol
• IMS Internet Multimedia subsystem
• a user equipment (UE) accessing IM core network (CN) subsystem services requires an IP address that is part of an IP addressing domain of a visited network IM CN subsystem. This is established using an appropriate PDP (Packet Data Protocol) context. For routing efficiency this context should be connected through a GGSN (General Packet Radio Services Gateway Support Node) in the visited network.
• PDP Packet Data Protocol
• Every IM CN subsystem subscriber has a private identity assigned by the home network operator and used e.g. for registration, authorization, administration, and accounting purposes.
• This private identity is a unique global identity valid for the duration of the user's subscription with the home network and takes the form of a Network Access Identifier (NAI) as defined in the IETF (Internet Engineering Task Force) specification RFC 2486.
• NAI Network Access Identifier
• the NAI for the private identity may contain the IMSI (International Mobile Subscriber Identity).
• the private identity is securely stored in the USIM (Universal Mobile Telecommunications System Subscriber Identity Module) and cannot be modified by the UE.
• Every IM CN subsystem subscriber has one or more public identities assigned by the home network operator and used by any user for requesting communications to other users.
• these public identities may be indicated on a business card. Both telecom numbering and Internet naming schemes can be used to address users depending on the public identities allocated to the users.
• the public identities may take the form of a SIP URL (Session Initiation Protocol Uniform Resource Locator), as defined in the IETF specifications RFC 2543 and RFC 2396, or an E.164 number. At least one public identity is stored in the USIM.
• each public identity is registered separately, as indicated in Fig. 1. Therefore, the registration of other subscriber identities requires additional registration procedures if a subscriber wishes to use multiple identities.
• the subscriber may have several profiles that he would like to use separately e.g. business profile, private profile, chess club member profile etc.
• one private identity but several user profiles as shown in Fig. 2
• the public identities that belong to the same user profile are bundled together and therefore they are also administrated together.
• severe private identities as shown in Fig. 3, every user profile has its own private identity.
• the subscriber registers with one of his public identities and lists all the other public identities that he wants to be registered with at the same time.
• a subscriber When a subscriber has registered with one of his identities, he can use his other identities for outgoing calls without any further registration but he doesn't receive any calls with those identities.
• the subscriber can explicitly change an existing registration or make a new registration with whichever of his identities for incoming calls only, for outgoing calls only, or for both incoming and outgoing calls. He can make one or several registrations at a time.
• the subscriber can register with one of his public identities specially indicating that all public identities should be registered, and all his public identities will be registered. As an option the subscriber can register without the mentioned indication, and all his public identities are registered by a default setting.
• the subscriber may have several public identities. Normally, he registers with one public identity. If he wants to use another of his public identities e.g. to make a business call in the evening from home, he has to register with that identity before he can use it. It would be desirable to be able to register with all or with some of the public identities all together at the same time. After the registration, that public identity is valid also for incoming calls e.g. people may call home in business matters.
• new optional header field is used in the registration message.
• the payload of the registration message can be used.
• the terminal may perform a one-by-one registration to all items stored e.g. in a list on the SIM or the USIM and/or memory of the terminal.
• a default registration of at least one other identity of the user, stored in a subscriber database may be performed based on a default setting.
• the at least one other identity may be comprised in a default set defined by the user.
• the default set may be defined via a web page or a terminal menu.
• a new parameter, header, flag or the like can be added to the registration message to convey the direction (incoming calls / outgoing calls / both) of the registration.
• a new parameter, header, flag or the like can be added to the registration message to convey the direction (incoming calls / outgoing calls / both) of the registration.
• several fields or a separate header can be used.
• the registration message might also provide a mechanism to tell that all valid identities should be activated at the same time.
• Private identities, user profiles and public identities may all be stored in a subscriber database, e.g. HSS.
• the client identity may be used as a link that binds together the private identities of one client.
• the invention provides the advantage that only one registration is necessary in order to be able to use some or all public identities. This saves resources such as bandwidth and capacity, which is especially important on the air interface. Furthermore, only one registration is necessary in order to be able to use all identities for outgoing calls. The subscriber can explicitly administrate all his identities and decide whether he wants to allow incoming calls, outgoing calls or both. Only those identities are registered that are really needed. Identities may be given by different operators and/or organizations.
• the solution is (IETF) SIP compliant (extension to standard SIP) and backwards compatible.
• HSS Home Subscriber Server
• the invention provides a solution, which is easy to use because outgoing calls are allowed with whichever identity as default, if not denied in the master database in the HSS. Moreover, a special usage is possible with parameters.
• the terminal device or user equipment used for registering the user in the communication network comprises a memory, e.g. the USIM, SIM or any other memory, for storing the identity information of the user, which defines an identity and at least one other identity of the user. Based on this identity information, a signaling function or unit performs or initiates a one-by-one registration according to the user's instructions.
• Fig. 1 shows a diagram indicating the case of "one private identity", where all public identities are bound to a single private identity
• Fig. 2 shows a diagram indicating the case of "one private identity, but several user profiles", where public identities are bundled to profiles and therefore an additional profile layer is needed;
• Fig. 3 shows a diagram indicating the case of "several private identities", where several public identities are bundled to several private identities and therefore an additional profile layer is not needed;
• Fig. 4 shows a call flow diagram relating to an internet protocol (IP) registration, according to the preferred embodiments.
• IP internet protocol
• the architecture is based on the principle that the service control for home subscribed services for a roaming subscriber is in the home network, e.g. the Serving Call State Control Function (S-CSCF) is located in the home network.
• S-CSCF Serving Call State Control Function
• P-CSCF Proxy-CSCF
• the P- CSCF enables the session control to be passed to the home network based S- CSCF which provides the service control.
• one or more Interrogating- CSCFs l-CSCFs
• l-CSCFs Interrogating- CSCFs
• public identities are registered according to a specified user equipment indication.
• the user equipment i.e. the user's terminal, sends one of the valid public identities in a "To" header field of the SIP REGISTER message and other identities in a new header field called "Other-Identities".
• the S- CSCF registers the public identities, contained in the "To" header field and the "Other-Identities" header field and returns the list of registered public identities in the "Other-Identities" header field.
• the P-CSCF stores the registered public identities for later use.
• a user equipment UE(A) initiates a registration procedure by issuing the REGISTER message to the P-CSCF. Besides the public address in the "To" header field of the REGISTER message, it wants to register at the same time also other public identities as listed in the new "Other-Identities" header field of the REGISTER message. In the following an example for such a header is given:
• step 2 of Fig. 4 the P-CSCF forwards the registration request to the contact point of the home network, i.e. an l-CSCF.
• the header of the message looks as follows:
• the l-CSCF selects a suitable Serving-Call State Control Function (S-CSCF) for the subscriber based on the received registration request.
• S-CSCF Serving-Call State Control Function
• step 4 of. Fig. 4 the l-CSCF forwards the registration request to the selected S- CSCF.
• the header of the message looks as follows:
• step 5 of. Fig. 4 the S-CSCF registers the address in the "To" header field as well as the addresses in the "Other-Identities" header field. Additionally, the S- CSCF removes public identities that could't be registered from the "Other- Identities" header field.
• step 6 of Fig. 4 the S-CSCF sends a 200OK SIP message as a response to the registration request to the l-CSCF.
• the header of the response message looks as follows:
• step 7 of Fig. 4 the l-CSCF forwards the 200OK response message to the P- CSCF.
• the header of the response message looks as follows:
• step 8 of Fig. 4 the P-CSCF stores the names from the "To" header field and the "Other-Identities" header field. Then, in step 9 of Fig. 4, the P-CSCF forwards the response message to the user equipment UE(A).
• the header of the response message looks as follows:
• all public identities stored in subscriber database are registered if indicated in the user equipment.
• the user equipment i.e. the user's terminal sends one of the valid public identities in the "To" header field of the REGISTER message and a flag, a suitable mark, a note or the like, e.g. in the header field "Other-Identities" indicating that all public identities should be registered.
• the S-CSCF registers all public identities listed in the subscriber's profile contained in the subscriber database, i.e. the HSS.
• the S- CSCF returns the list of registered public identities in the "Other-Identities" header field to the P-CSCF.
• the P-CSCF stores the registered public identities for later use.
• all public identities stored in the subscribers database are registered by a default setting.
• the REGISTER message is send without the "Other-Identities" header field or any other indication.
• the S-CSCF registers all available public identities listed in the subscriber's profile stored in the HSS and returns the registered public identities to the P-CSCF in the "Other-Identities" header field, in the payload or in another appropriate way.
• the P-CSCF then stores the registered public identities for later use.
• the subscriber may have defined beforehand, e.g. via a web page, a certain menu displayed on his terminal or the like, the identities and/or profiles included in the "default" set.
• the subscriber might want to administrate his public identities himself to avoid being charged by the operator, to make changes quickly and smoothly and to feel to be his own master. It would be also easy to the operator to allow subscribers e.g. to change the list of public identities that are registered always by default at the registration; or to allow delete, change and create subprofiles and define their content in limits given by the operator.
• the HSS database may or may not be divided into several subdatabases. If it is divided into subdatabases, some of the subdatabases can be edited by the subscriber, and others by the operator only. Thereby, the HSS is less vulnerable. If it is not divided into subdatabases, some part(s) of the database can be edited by the subscriber, and others by the operator only. The subscriber edits a temporal copy of his entry in the database. After editing the validity and the correctness of the change or the whole entry is checked. If no errors are found, the temporal copy of the subscribers entry replaces the old entry in the database or subdatabase. According to operator specified rules a new production version may then be generated of the database or the subdatabase(s).
• the HSS is a register of the services the subscriber has ordered, it is the proper place where subscriber can make changes when ordering/cancelling/deleting/changing a service. Furthermore, generating a DNS-ENUM (Domain Name System - E.- Number) database is easier because not the whole HSS database has to be searched. In case the HSS original database is divided into subdatabases, the generation can be done based on possibly only one subdatabase.
• the subscriber's private key may be the key that is common in all subdatabases.
• the database/subdatabase may have three versions: the first is the original database, the second is the production version and the third is the temporal version where the subscriber makes changes to his own entry.
• a new optional header (e.g. "Other-Identities") is introduced in the REGISTER message to convey the information what other public identities the user wants to register. Any other name can be used for the header field "Other- identities".
• the "From” field of the REGISTER message comprises the private identity and the "To” field one of the valid public identities of the subscriber. It doesn't matter which one of the valid public identities is used in the "To” field.
• the "Other-identities" header field there are listed the other public identities that the subscriber wants to register at the same time.
• one or more of the items in the "Other-identities" optional header can be a profile instead of individual public identity. In that case, all public identities that are included in the listed profiles are registered, according to the concept "one private identity but several user profiles”. Attributes, which modify the registration of individual profile or public identity, may be attached to profiles and even public identities listed in the "Other-identities" header field. If the user wants to attach attributes to the public identity used in the "To" field, the public identity can be repeated in the "Other-identities" header with appropriate attributes.
• the terminal or user equipment may insert the "Other-identities" header to the
• the list of the valid profiles/public identities may be stored in the UMTS subscriber identity module (USIM) and/or in terminal's memory and/or it may be inserted by the user.
• USIM UMTS subscriber identity module
• the same information could be conveyed in the payload of the REGISTER message. It is assumed that the subscriber has registered with one of his identities. As a default setting, that identity can be used for incoming and outgoing calls. When the subscriber wants to use one of his other identities, he simply makes a call with it, i.e. sends an INVITE SIP message with the unregistered identity in the "From" header field. When the network element in charge of keeping track of the subscriber's identities, i.e.
• S-CSCF and/or P-CSCF receives the INVITE message from the subscriber's terminal, it stores the INVITE message and sends a REGISTER message with the unregistered identity in order to register it. If the registration succeeds, the identity is registered for outgoing calls as a default setting and the network element proceeds with retrieving the INVITE message and sending it further. If the registration fails the call is released.
• the subscriber may register or change his registration explicitly with whichever of his identities for incoming calls only, or for outgoing calls only, or for both by sending a REGISTER message with the identity in question and with an appropriate parameter(s).
• the subscriber's choice may be limited with master parameters in the HSS. Limiting factors can be e.g. the time, whether the bill is paid, and the direction (incoming/outgoing/both).
• the subscriber can do several registrations at the same time. With a certain parameter in the INVITE message, the registration may be done also for incoming calls, not only for outgoing calls (that may be a default setting). With another certain parameter in the REGISTER message all valid identities may be registered and received from HSS.
• DNS Domain Name Server
• the present invention can also be used together with user profiles.
• An operation targeted to a user profile has influence on all public identities which belong to that user profile.
• a user profile is only a bundle of public identities. For example, when a user registers a user profile, all public identities under that profile are registered.
• a user profile may be addressed e.g. with one of its public identities.
• the present invention can also be used together with several private identities.
• An operation targeted to a private identity has influence on all public identities that belong to that private identity.
• a private identity is a bundle of public identities.
• the private identities of a subscriber can be bound together with one or more client identities that are used e.g. for charging.
• the subscriber may get a warning (if desired) about calls to his non- registered public identities.
• the present invention describes a registration method wherein a user is registered in a communication network.
• a registration message is used, which comprises a header field for defining at least one other identity of the subscriber.
• a registration message is used, which comprises an identity information in its payload portion, said identity information defining at least one other identity of the subscriber.
• a one-by-one registration is performed based on an identity information stored at the terminal device, said identity information defining at least one other identity of the subscriber.

Priority Applications (5)

Applications Claiming Priority (2)

Publications (1)

Family

ID=7680187

Family Applications (1)

Country Status (5)

Cited By (10)

Families Citing this family (39)

Citations (1)

Family Cites Families (12)

• 2001
  • 2001-04-03 DE DE10116547A patent/DE10116547A1/de not_active Withdrawn
  • 2001-07-13 EP EP01955348A patent/EP1380137B1/de not_active Expired - Lifetime
  • 2001-07-13 DE DE60139718T patent/DE60139718D1/de not_active Expired - Lifetime
  • 2001-07-13 EP EP09010127A patent/EP2112852A3/de not_active Withdrawn
  • 2001-07-13 WO PCT/EP2001/008161 patent/WO2002082731A1/en active Application Filing
  • 2001-07-13 US US13/163,448 patent/USRE45161E1/en not_active Expired - Lifetime
  • 2001-07-13 AT AT01955348T patent/ATE441303T1/de not_active IP Right Cessation
  • 2001-07-13 US US10/473,795 patent/US7792974B2/en not_active Ceased

Patent Citations (1)

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events