Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/26—Network addressing or numbering for mobility support
• • 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

Definitions

• the present invention relates to a communication system, and in particular to a communication system wherein a subscription is allowed to have multiple registrations to control means of the system.
• a communication system can be seen as a facility that enables communication between two or more entities such as user equipment and/or other nodes associated with the system.
• the communication may comprise, for example, communication of voice, data, multimedia and so on.
• 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.
• the standard or specification may define if the user, or more precisely, user equipment or terminal is provided with a circuit switched service and/or a packet switched service.
• Communication protocols and/or parameters which shall be used for the connection may also be defined.
• a specific set of "rules" on which the communication can be based on needs to be defined to enable communication by means of the system.
• Communication systems proving wireless communication for user equipment or other types of terminating nodes are known.
• An example of the wireless systems is a cellular network.
• a base transceiver station (BTS) or similar access entity serves user equipment (UE) via a wireless interface between these entities.
• the mobile user equipment is typically referenced by the term mobile station (MS).
• Communications in the system 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 another cellular system or to a public switched telephone network (PSTN) and/or other communication networks such as an IP (Internet Protocol) and/or other packet switched networks.
• PSTN public switched telephone network
• IP Internet Protocol
• the communication between the user equipment and the entities of the communication network can be based on an appropriate communication protocol.
• An example of the protocols is the session initiation protocol (SIP).
• the communication systems have developed in the direction wherein various service provision functions of the network are handled by network entities known as servers.
• servers For example, in the current third generation (3G) wireless multimedia network architectures it is assumed that several different servers are used for handling different functions. These include functions such as the call state control functions (CSCFs).
• the call state control functions may be divided into various categories such as a proxy call state control function (P-CSCF), interrogating call state control function (l-CSCF), and serving call state control function (S-CSCF). It shall be appreciated that sometimes the CSCFs may be referenced to as the call session control functions.
• P-CSCF proxy call state control function
• l-CSCF interrogating call state control function
• S-CSCF serving call state control function
• the serving call state control function forms the entity the subscriber needs to be registered at in order to be able to request for a service from the communication system.
• the user may need to be associated with proxy and interrogating control entities.
• a user may have more than one registration at the same time. At least one registration is required for the user to be able to communicate via the communication system. During registration proceedings various authentication queries or messages and authentication parameters such as those based on authentication quintets and/or keys may need to be transferred between the entities involved in the process.
• a registration means that a user registers an identity at the serving call state control function.
• an identity such as a public identity (ID) is provided for the controller entity.
• the public ID is an identity that associates with the subscription to the communication system.
• the public identity may function as a telephone number of the known telephone systems.
• a conventional telephone such as a 2 nd generation (2G) mobile phone can only have one number, e.g. a 3G phone may have more than one identity (e.g. a telephone number, one or more email-like addresses, for example session initiation protocol (SIP) universal resource locators (URL), an address or addresses for alternative communications means, and so on).
• SIP session initiation protocol
• URL universal resource locators
• a subscription may also have at least one associated private identity.
• the private identity may refer to a particular user of a subscription. That is, a subscription may have more than one user.
• the user may be seen as logically equalling an identity entity such as any appropriate subscriber identity module (SIM).
• SIM subscriber identity module
• a subscription may associate with various identities and users. For example, it is possible that a family or organisation (such as a an office) has a common public identity. In addition to that, all members of the group may have further public identities and private identities.
• a user who wants to initiate a call or receive a call the user must register his/hers public ID. If a user has two public IDs (e.g. ID1 and ID2) and only ID1 is registered, all calls initiated to/from ID2 will be unsuccessful since ID2 has not been registered with the network.
• ID1 and ID2 two public IDs
• the current registration procedures such as those specified by the 3 rd generation partnership project (3GPP) register public IDs for a user separately and independently, save those public IDs that belong to the same service profile. It has been proposed that all user identities of a particular subscriber shall be registered in a call controller entity. For example, release 5 (Rel5) version of a 3GPP standard document proposes that all those identities are registered in the same serving call state control function (S-CSCF) entity.
• S-CSCF serving call state control function
• the S-CSCF entity is aware of the registration status only in the level of individual public IDs, and therefore it cannot know if a user has more than one registration and if the user is registered in more that one control entity.
• IMS IP multimedia subsystem
• all public identities that belong to the same IP multimedia subsystem (IMS) subscriber have to be registered to the same controller entity.
• IMS IP multimedia subsystem
• any registration, re-registration and de-registration proceeding are done on a one-by-one basis. Since the registration of individual public IDs is handled independently, it may happen that a user is registered to at least two S-CSCFs. This may not be allowed in all applications. For example, if the public ID such as public user identities (IMPUs) are registered to different S-CSCFs then it may be impossible to execute some services (e.g. forking).
• IMPUs public user identities
• the S-CSCF selection is typically done in the I- CSCF during registration.
• the l-CSCF cannot know if the user is registered in any other S-CSCFs.
• the independent registrations of the same subscription are forwarded to different S-CSCFs based on the server capability information received by the l-CSCF from the home subscriber server (HSS).
• HSS home subscriber server
• WO 02/091785 does not address the problem of having different types of identities and/or multiple private identities.
• a subscription may have a plurality of private user identities (IMPI) and a plurality of public identities.
• IMPI private user identities
• public identities a plurality of public identities.
• IP internet protocol
• 3G third generation
• SIP session initiation protocol
• Embodiments of the present invention aim to address one or several of the above problems.
• a subscription is associated with a plurality of public and private identities
• the method comprising: storing in a user information storage information of relations between the plurality of public and private identities and of a control entity in which at least one of the identities is registered; and allocating the control entity to a further registration based on the information stored in the user information storage.
• a communication system comprising a plurality of control entities and a user information storage configured for storing information of relations between public and private identities associated with users of the communication system and of a control entity in which at least one of the public and private identities is registered, and means for allocating a call control entity to a further registration associated with a user based on the information stored in the user information storage.
• a user information storage entity for a communication system, the user information storage entity comprising means for storing information of relations between public and private identities associated with users of the communication system and of a control entity in which at least one of the public and private identities is registered, and means for allocating the call control entity to a further registration associated with a user based on the information stored in the user information storage.
• a further control entity queries for the registration status of the user from the user information storage, the query being responded by returning information enabling routing of a registration request to the control entity.
• the control entity may comprise a servicing call state control function and the further entity may comprise an interrogating call state control function.
• the user information storage may comprise a home subscriber server.
• the information enabling routing to the control entity may comprise the name or the address of the control entity.
• the user information storage may be configured to select the control entity to be allocated for the further registration.
• the embodiments may provide various advantages. All identities associated with a subscription may be registered to a single call state control function. The services may work in a normal manner and independently of the identity used by the subscription. In some embodiments it can be ensured that the private and public identities associated with a subscription are registered to the same servicing call control function. Some embodiments may enable provision of the same service for different identities in a similar manner.
• Figure 1 shows information flows in an prior art arrangement
• Figure 2 shows a part of a communication system wherein the present invention can be embodied
• Figure 3 shows information flows in accordance with an embodiment of the present invention
• Figure 4 shows possible user identity relationships for a user. Description of Preferred Embodiments of the Invention
• the mobile communication system is arranged to serve a plurality of mobile user equipment 1 via a wireless interface.
• the basic operational principles of mobile user equipment, that may also be referenced to as mobile stations, are known by the skilled person, and will thus not be explained in any more detail here.
• a mobile communication system can typically be divided between a radio access network (RAN) and a core network (CN).
• RAN radio access network
• CN core network
• a plurality of user equipment 1 of mobile users is served by a 3G radio access network (RAN) over a wireless interface.
• the user equipment is enabled to move relative to the access entity, and may thus be referred to by the term mobile station.
• the 3G radio access network (RAN) is connected to appropriate core network entity or entities, such as to a serving general packet radio service support node (SGSN).
• SGSN serving general packet radio service support node
• FIG 2 shows also a plurality of call state control function entities (CSCFs) 22 to 24, 30 and 31.
• the call state control function entity 22 is the so called serving call state control function (S-CSCF) with which the user equipment 1 has at least one registration. That is, the user has registered at least one identity with the control entity 22.
• S-CSCF serving call state control function
• Call state control function entities 23 and 24 could also provide similar functionality, should an identity of the user be registered with either of them.
• the functions the proxy CSCF 30 and the interrogating CSCF 31 will described below with reference also to the signalling flowchart of Figure 3.
• a user information storage 26 is also shown.
• the user information storage is shown to be provided by means of a home subscriber server (HSS).
• HSS home subscriber server
• the HSS is configured to store information of identities of the user and of a call control entity in which the user is registered. Information of possible relations between identities of different users may also be stored at the home subscriber server (HSS) 26.
• the home subscriber server (HSS) 26 may also store information such as the status of the registration identities (ID) (currently-registered-with a S-CSCF or currently-not- registered) and further similar information associated with the use of the communication system.
• ID the registration identities
• S-CSCF currently-not- registered
• Control entity and status information may be saved in the storage means 35 of the user information storage 26 during registration.
• the stored information can be updated during re-registration and/or de-registration.
• the home subscriber server can be queried by the control entities, e.g. during registration and session set-up procedures.
• session refers to any communication a user may have such as to a call, data (e.g. web browsing) or multimedia communication and so on.
• individual identity (ID) registrations for a subscription are synchronised in a 3GPP IMS (IP Multimedia Subsystem) domain by means of the HSS.
• the HSS keeps a record of the relations between various identities associated with the subscription.
• the HSS also maintains information regarding identities that are registered to the S-CSCFs.
• the same S-CSCF can be allocated for this registration by providing appropriate routing information such as the name and/or address of the S-CSCF.
• the HSS may detect e.g. in the case of an initial registration of, for example, a public user identity (IMPU) whether any identities of the same user or subscription has already been registered.
• IMPU public user identity
• the HSS shall return the S-CSCF name in the response given for the user registration status query, instead of returning the server capabilities as is done in the prior art.
• such a response may be given for a user registration status query (UAR) that has been initiated by an l-CSCF.
• UAR user registration status query
• the l-CSCF may then forward the register message to the S-CSCF which name or address received in the response (UAA).
• a subscription may a plurality of public and private identities.
• The are shown as IMPUs and IMPIs, respectively, in Figure 4 which is an example of such Subscription-IMPI-IMPU-SP relations.
• the private identities IMPI1 and IMPI2 may be provided by two separate subscriber identity modules (SIM) or similar user identity modules associated with the user equipment. For example, in the 3GPP these identity modules are referenced as USIMs.
• the HSS may not be able to forward registration from these user equipment to the same S-CSCF.
• the HSS can be provided with information regarding a common feature that refers to common services.
• the HSS may track the relation between the IMPIs e.g. based on either at least one common public identity (IMPU) or common service profile (SP) or common subscription behind the private identities. Based on the relations the HSS can recognise that the same services should be provided.
• IMPU common public identity
• SP common service profile
• the HSS 26 would return the service capabilities to the l-CSCF 31.
• the l-CSCF 31 may then make the allocation based on the service capabilities data received from the HSS 26 as shown in Figure 1.
• the HSS 26 checks if the subscription already has a registered public identity. It is possible that the private identity (e.g. a user associated with the subscription) associated with the public identity to be registered does not have any registered public identities while the subscription already has at least one such associated registration. In this case the HSS 26 may send the S-
• the HSS 26 makes the allocation instead of the l-CSCF 31 based on the detection that the identity has a related identity, the relation being through the subscription.
• the HSS 26 is able to recognize that different private identities (IMPIs) having common public identities (IMPUs) belong to a single subscriber. Information regarding the relations between the identities and the service profiles (SPs) may also be analysed. Private identities may be used, for example, for bundling several public identities of a given subscription or a number of user equipment together.
• the two public identities IMPU1 and IMPU3 are totally independent from each other.
• the two public identities are having a relation via two private identities IMPI1 and IMPI2.
• the two private identities are also each having a relationship with a third public identity IMPU2.
• the registration of the two independent public identities in the same S-CSCF can be made due to the common IMPU2.
• the build-up of the relationship chain may be done regardless the registration status of the common private identity.
• the HSS allocates the same S-CSCF to both IMPU and IMPI2 in instance where there are two users or one user with two terminals. Nevertheless, both of these users would like to access a common service.
• the HSS stores information regarding the relations between the identities and is thus able to determine the relation between the two separate IMPIs.
• the HSS may only need to send to the l-CSCF the name or other information enabling routing to the already used S-CSCF instead of sending information regarding server capabilities.
• the new identities will be registered at the same S-CSCF than where the existing registrations are.
• a user equipment may have requested for registration e.g. by sending a SIP REGISTER message to a proxy server entity 30.
• the registration request is forwarded from the proxy 30 to an interrogating server entity 31.
• An appropriate query procedure may then be accomplished between the interrogating server entity 31 and the subscriber information database 35 of the home subscriber server 26.
• the HSS 26 may recognise based on the information stored thereof that the identity relates to some other already registered public and/or private identities associated with a subscription.
• the stored information may describe the relationships between the various identities.
• An example of various relations two private identities may have is shown in Figure 4.
• the HSS may e.g. recognise that at least one other public identity is registered with the control entity 22 (S-CSCF1).
• S-CSCF1 control entity 22
• the interrogating server 31 may then request for registration from the controller entity 22 based on the returned routing information .
• This mechanism may be used to ensure that registrations of all public and/or private IDs utilising the same services take place at the same controller entity.
• the proposed mechanism may ensure that all IDs belonging to the same subscription or same service profile are registered to the same S-CSCF.
• Registration at the same servicing control entity enables provision of the same services for a subscriber or a number of subscribers. This can be realised by the storing information about the relationships between the identities in a user information storage and by responding control entity queries by the name or address of the servicing control entity instead of server capabilities information. It should be appreciated that whilst embodiments of the present invention have been described in relation to user equipment such as mobile stations, embodiments of the present invention are applicable to any other suitable type of users.
• the embodiment of the present invention has been described in the context of the Universal Mobile Telecommunication System (UMTS) 3G system and session initiation protocol (SIP). This invention is also applicable to any other communication systems and protocols. Examples of other systems, without limiting to these, include the General Packet Radio Service (GPRS), the Enhanced Data rate for GSM Evolution (EDGE) mobile data network, other third generation (3G) telecommunication systems such as the i-phone or IMT-2000 (International Mobile Telecommunications) and the Terrestrial Trunked Radio (TETRA) system.
• GPRS General Packet Radio Service
• EDGE Enhanced Data rate for GSM Evolution
• 3G third generation
• IMT-2000 International Mobile Telecommunications
• TETRA Terrestrial Trunked Radio

Landscapes

• Engineering & Computer Science (AREA)
• Databases & Information Systems (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)
• Radio Relay Systems (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (1)

Family

ID=9956216

Family Applications (1)

Country Status (11)

Cited By (6)

Families Citing this family (28)

Citations (3)

Family Cites Families (3)

• 2003
  • 2003-04-04 GB GBGB0307853.2A patent/GB0307853D0/en not_active Ceased
  • 2003-08-01 US US10/632,088 patent/US20040196796A1/en not_active Abandoned
• 2004
  • 2004-03-25 AT AT04723275T patent/ATE361648T1/de not_active IP Right Cessation
  • 2004-03-25 KR KR1020057018918A patent/KR100755984B1/ko not_active Expired - Fee Related
  • 2004-03-25 DE DE602004006246T patent/DE602004006246T2/de not_active Expired - Lifetime
  • 2004-03-25 EP EP04723275A patent/EP1611764B1/en not_active Expired - Lifetime
  • 2004-03-25 CN CNB2004800116869A patent/CN100542321C/zh not_active Expired - Fee Related
  • 2004-03-25 RU RU2005134227/09A patent/RU2005134227A/ru not_active Application Discontinuation
  • 2004-03-25 CA CA002521311A patent/CA2521311A1/en not_active Abandoned
  • 2004-03-25 WO PCT/IB2004/001043 patent/WO2004089022A1/en not_active Ceased
  • 2004-03-25 JP JP2006500342A patent/JP2006522501A/ja active Pending

Patent Citations (3)

Also Published As

Similar Documents

Legal Events