CN100527743C

CN100527743C - Method for registering IMS user public ID and recessive registration in IP multimedia subsystem

Info

Publication number: CN100527743C
Application number: CNB2005101275394A
Authority: CN
Inventors: 李绪健
Original assignee: Huawei Technologies Co Ltd
Current assignee: Global Innovation Polymerization LLC; Gw Partnership Co ltd
Priority date: 2005-12-05
Filing date: 2005-12-05
Publication date: 2009-08-12
Anticipated expiration: 2025-12-05
Also published as: WO2007065336A1; CN1863205A

Abstract

The invention discloses a method for registering IMS user public ID in IP multimedia subsystem and the latent registering method thereof. And the method for registering IMS user public ID comprises the steps of: setting sharing attribute elements of IMS user public ID to indicate the IMS user public ID to share all or part of IMS user private IDs of subscriber; the user device of a subscriber cured with a first IMS user private ID initiates a first IMS user private ID registering request to kernel network; the kernel network related component agrees or refuses the user device to register the first IMS user private ID according to the original related IMS user private ID of the first IMS user public ID and the sharing attribute elements; the kernel network related component returns an agreeing response and the user device completes registering. And the invention meets the requirements of users for partial sharing and saves network resources and improves quality of service (QoS).

Description

Registered ims users public ID and recessive process registration in the IP Multimedia System

Technical field

The present invention relates to IP Multimedia System (IP Multimedia Subsystem, IMS) technical field, particularly the IMPU in the IP Multimedia System (IMS Public User Identity, IMS user public ID) shares and the recessive technical field of registering.

Background technology

In the IMS territory, allow an ISIM (IP Multimedia Services Identity Module, IP multimedia service identity module) related a plurality of IMPU on the card, and allow to register a plurality of IMPU once when terminal is used the IMSI card, this mechanism is called recessive login mechanism.

Simultaneously, in the IMS territory, also allow the user on the basis of using many ISIM cards, an IMPU is set to share, make and can use this IMPU except the original ISIM related with this IMPU that other ISIM also can use this IMPU, this mechanism is called shared mechanism.

In the IMS territory, a subscriber (Subscriber) is meant the entity that uses service, is equivalent to the user of indication in the CS territory, and each subscriber can apply for one or more IMPI (IMS Private UserIdentity, the privately owned ID of IMS user).Generally speaking, solidified an IMPI on the ISIM card, the user is when using the ISIM card, be to carry out authentication registration on the network by IMPI this identity, it is the defined global identity with uniqueness of home network operator, and each IMPI can related one or more IMPU, promptly on every ISIM card one or more IMPU can be arranged, IMPU is an identity used when being used to ask with other telex networks, comprise use professional.

In " 3GPP TS 23.228 V7.0.0 (2005-06) ", above-mentioned shared mechanism is described, it is the method for the shared attribute that the subscriber can be by being provided with IMPU, this IMPU is associated with the IMPI that the subscriber is had, this will make the subscriber can use same IMPU to be registered on the network, and use the pairing service of this IMPU, Fig. 1 has shown this shared relationship, wherein IMPU1 and IMPU3 do not share, IMPU2 has shared, it can be used simultaneously by IMPI1 and the IMPI2 under the subscriber, the XML of this shared mechanism (eXtensible Markup Language, extend markup language) document representation can for:

＜Identity〉sip:Public User Identity-1@homedomain.com＜/Identity〉// do not share

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

</PublicIdentity>

<Identity>sip:Public?User?Identity-2@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

＜Shared〉1＜/Shared〉// be set to share

</PublicIdentity>

＜Identity〉sip:Public User Identity-3@homedomain.com＜/Identity〉// do not share

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

</PublicIdentity>

The IMPU that share I MPU certainly will will cause be shared may be registered by a plurality of UE (UserEquipment) at one time.Carry out necessary selection in the time of so just must taking certain measure to guarantee service such as calling, can preferentially select at registration phase such as the user, or define preferential selection strategy by server, then working as the subscriber has a plurality of UE to register a shared IMPU simultaneously, when the calling that this IMPU is initiated is arranged, server can be called out some UE according to preferential selection strategy, if when this UE does not respond then can continue to attempt other UE of contact.Can certainly preferentially not select, but select concurrently, promptly side by side a plurality of UE are called out, then this moment, the user can only select some UE to answer, but the result has only one, and the user can only use a UE to reply, and is illustrated below:

Example 1: when one family has been applied for a subscriber to the operator business hall, and 3 IMPI have been applied for, each IMPI is solidificated in respectively on the ISIM card, and the while is also bought 3 IMS UE (UserEquipment, subscriber equipment) gives father, mother and son respectively, ISIM card of each UE binding.Then use a IMPU:smith@ims.example.com among its UE as son, order an online television service and this IMPU of smith@ims.example.com is set when sharing, then father and mother's UE also can use this online television to serve, obviously father, mother and son but can enjoy same service not same local time.

The above-mentioned example that uses the indifference sex service when being a kind of share I MPU, promptly father, mother and son enjoy the ordered service content of smith@ims.example.com does not have difference, in practice, may the property of there are differences.Such as, son also uses this IMPU to order the service of a game on line, and when having only son's UE just to support to play this game on line, father and mother then obviously can not use this game on line service.Use the example of variant service below again for same individual.

Example 2: when Bob has a subscriber, and two IMPI are arranged, a respectively corresponding IMS UE and a game terminal.IMS UE has an IMPU:Bob@ims.example.com, is used for communication service; Game terminal has an IMPU:Game_Bob@ims.example.com then to be used to manage a game on line.Bob is when this IMPU of Game_Bob@ims.example.com is set to share now, then he just can use this IMPU by IMS UE, different with game terminal is, Bob uses the purpose of this IMPU just in order to obtain the state of game on line on IMSUE, is not in order to manage its game on line.

Owing in " 3GPP TS 23.228 V7.0.0 (2005-06) " " sharing " made this restrictive condition of sharing of overall importance, make to be shared in flexibility and the fail safe to have many disadvantages, mainly show:

1, the user can't satisfy the protection requirement of sharing, and only shares when customer requirements and comes into force in part UE, and when not coming into force in other UE, can't realize by existing shared mechanism.In above-mentioned example 1, when if son is the minor, father may order the service of the property of growing up or other by certain IMPU and not want the service that allows son use, and father wants to allow mother share these services, then father can not be set to share by this IMPU, otherwise son just can use; In addition, the demand that also exists its communicating number of father to be set to share, then when others did not contact father, server can have been got in touch mother automatically; Problem is, also has the situation that does not contact mother, at this moment just needed the contact son, if but father does not think to bother like this son's study, just can not this IMPU is shared.

2, Fu Wu the speciality of sharing has reduced, share mean can allow a lot of people in other words UE share certain or some services, but share of overall importancely brought following two problems:

All services or part that some (one or more) people does not need to use certain share I MPU to order are served, generally speaking, an IMPU may order a plurality of services, and in the reality, all services that some people may not need this share I MPU to order, we can say that then this share I MPU obviously is insignificant concerning these people, this has obviously run counter to the purpose of sharing; Moreover, though the part service that some people also may use this share I MPU to order when in other service the business of propelling movement being arranged, there is no need these people;

Some UE does not have the ability of the service of using certain share I MPU order, because the ability of UE is always limited, each UE below subscriber also may the property of there are differences, and makes some UE can use some service, and other UE then can not use these services.Then when having these othernesses, certain IMPU is shared, and some UE can't use and can only be not intended to the free burial ground for the destitute registration, and this has obviously also reduced the speciality of sharing; In addition, when the request of server forwards incoming call waits service, may relate to the UE that some can not use this service, this will be a kind of unnecessary burden concerning server and network.

Recessive login mechanism has description in " 3GPP TS 23.228 V7.0.0 (2005-06) ", it is meant that the user can be provided with some IMPU in certain set, then the some IMPU in this set be registered/when nullifying, all IMPU in this set can be by registration/cancellation side by side, this set is called recessive registered set (Implicitly Registered Set), and this registration just is called as recessive registration.

As shown in Figure 2, such as certain subscriber an IMPI1 is arranged, related three IMPU of this IMPI1, the user can be put into these three IMPU among the recessive registered set IRS, then when the user registers some IMPU, can register other two IMPU recessively, and after succeeding in registration, if during the some IMPU of user log off, also can nullify other two IMPU recessively, the XML document representation of this recessiveness registered set IRS can for:

<Identity>sip:Public?User?Identity-1@homedomain.com</Identity>

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

＜IRSid〉1＜/IRSid〉// be set in the recessive registered set 1

</PublicIdentity>

<Identity>sip:Public?User?Identity-2@homedomain.com</Identity>

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

＜IRSid〉1＜/IRSid〉// be set in the recessive registered set 1

</PublicIdentity>

<Identity>sip:Public?User?Identity-3@homedomain.com</Identity>

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

＜IRSid〉1＜/IRSid〉// be set in the recessive registered set 1

</PublicIdentity>

When recessiveness is registered with shared the combination, will bring following restriction: when an IMPU of a recessive registered set is set to share, other IMPU of this recessiveness registered set requires to be set to share, therefore the shown situation of Fig. 3 is not allowed to, IMPU1 among Fig. 3 and IMPU2 are among the IRS, wherein IMPU1 is set to share, but IMPU2 is not set to share.

Yet there is many disadvantages in this restrictive condition in flexibility and fail safe, and these defectives mainly show:

Cause some offending user experiences, when some IMPU of a recessive registered set of user are set to share, mean that other IMPU of recessive registered set also will be set to share simultaneously; And if the user does not want other IMPU is also shared, that is again a kind of contradiction concerning the user; On the other hand, if certain IMPU was set to share when the user began, again it is placed on a recessive registered set with other several non-share I MPU and also can has same problem, if and user and unclear this problem, can cause the undesirable result of some users, may be unaffordable to the user, also mean the reduction of sharing speciality of service simultaneously.

Summary of the invention

The object of the present invention is to provide registered ims users public ID and recessive process registration in the IP Multimedia System, under the condition of the existing shared mechanism of compatibility, realize local sharing, simultaneously when combining with the recessiveness registration, when an IMPU of the recessive registered set of user was set to share, unnecessary all being set to of other IMPU of this recessiveness registered set shared.

To achieve these goals, the invention provides and carry out the local method of sharing in a kind of IP Multimedia System, comprise the steps:

The shared property element of IMS user public ID is set, is used to indicate the IMS user public ID shared or shared the privately owned ID of part IMS user to subscriber's the privately owned ID of all IMS users;

The subscriber equipment that is solidified with the privately owned ID of an IMS user under one subscriber is initiated the request of registration the one IMS user public ID to core net;

The core net associated components is agreed according to the privately owned ID of former related IMS user of a described IMS user public ID and shared property element or is refused the described IMS user public ID of described user equipment registration;

If agree, after the core net associated components returned the response of agreeing the described IMS user public ID of described user equipment registration, subscriber equipment was finished registration.

The method of registered ims users public ID in the above-mentioned IP Multimedia System, wherein, described shared property element comprises:

Share the scope daughter element, when its value was first particular value, a described IMS user public ID was shared for the privately owned ID of all IMS users under the subscriber, and when being second particular value, the privately owned ID of part IMS user that a described IMS user public ID is the subscriber shares;

The privately owned ID tabulation of share I MS user daughter element, when described shared scope daughter element is second particular value, the tabulation that is used to store the privately owned ID of described part IMS user.

The method of registered ims users public ID in the above-mentioned IP Multimedia System, wherein, the core net associated components returns the response of agreeing the described IMS user public ID of described user equipment registration in following several situations:

The privately owned ID of former related IMS user of a described IMS user public ID is the privately owned ID of a described IMS user;

The privately owned ID of former related IMS user of a described IMS user public ID is the privately owned ID of the 2nd IMS user, but the value of the shared scope daughter element of a described IMS user public ID is first particular value;

The privately owned ID of former related IMS user of a described IMS user public ID is the privately owned ID of the 2nd IMS user, but the value of the shared scope daughter element of a described IMS user public ID is second particular value, and comprises the privately owned ID of a described IMS user in the tabulation of the privately owned ID of described part IMS user.

Share the key daughter element, when described shared scope daughter element is second particular value, is used to store one and shares key.

The privately owned ID of former related IMS user of a described IMS user public ID is the privately owned ID of the 2nd IMS user, but the value of the shared scope daughter element of a described IMS user public ID is second particular value, and the key that the privately owned ID of described IMS user provides is identical with described shared key.

In order better to realize above-mentioned purpose, the present invention also provides recessive process registration in a kind of IP Multimedia System, comprises the steps:

The recessive registered set property element of IMS user public ID is set, be used to indicate the recessive registered set under the IMS user public ID, indicate described IMS user public ID to be associated or only to be associated simultaneously with the privately owned ID of former related IMS user with the shared relevant privately owned ID of all IMS users;

After user equipment registration the one IMS user public ID success, described core net associated components is agreed according to the shared property element of a described IMS user public ID and recessive registered set property element or is refused described subscriber equipment and carry out recessiveness and register.

Recessive process registration in the above-mentioned IP Multimedia System, described shared property element comprises:

The privately owned ID tabulation of share I MS user daughter element, when described shared scope daughter element is second particular value, the tabulation that is used to store the privately owned ID of described part IMS user;

Described recessive registered set property element comprises:

Recessive registered set is shared the scope daughter element, when its value is the 3rd particular value, corresponding IMS user public ID is associated with shares the relevant privately owned ID of all IMS users, and when its value was the 4th particular value, corresponding IMS user public ID only was associated with the privately owned ID of former related IMS user;

Recessive registered set ID daughter element is used to store the ID of the affiliated recessive registered set of IMS user public ID.

Share the key daughter element, when described shared scope daughter element is second particular value, is used to store one and shares key;

Described recessive registered set property element comprises:

Recessive process registration in the above-mentioned IP Multimedia System, under following several situations, described subscriber equipment carries out the recessiveness registration:

Judge a described IMS user public ID according to described shared property element and after sharing, just be associated with the privately owned ID of a described IMS user, and other IMS user public ID that existence is identical with the recessive registered set ID daughter element of a described IMS user public ID, the privately owned ID of former related IMS user of described other IMS user public ID is consistent with the privately owned ID of a described IMS user, and the value of the shared scope daughter element of the recessive registered set of described other IMS user public ID is described the 4th particular value simultaneously;

The described recessive registered set property element of a described IMS user public ID exists, and the value of the shared scope daughter element of described recessive registered set is described the 3rd particular value or the 4th particular value.

Registered ims users public ID and recessive process registration are by being provided with shared property element in the IP Multimedia System of the present invention, can be set to partly share by the IMS user public ID, simultaneously, by recessive registered set property element is set, when an IMPU among certain IRS is shared, the user both can make other IMPU among this IRS only be used by certain IMPI, promptly only be associated with an IMPI, also can make it be shared all relevant IMPI and use, promptly be associated with and share all relevant IMPI.The present invention has satisfied the demand that the user shares part, has saved Internet resources simultaneously, has improved service quality.

Description of drawings

Fig. 1 is the schematic diagram that concerns that the IMPU of prior art shares back and IMPI;

Fig. 2 be prior art IRS, IMPU, IMPI concern schematic diagram;

The schematic diagram of the situation that Fig. 3 shares for the IMPU that does not allow among the IRS of prior art to occur;

Fig. 4 is the schematic diagram that concerns that IMPU of the present invention shares back and IMPI;

Fig. 5 is the schematic diagram that concerns of IRS of the present invention, IMPU, IMPI.

Embodiment

In the IP Multimedia System of the present invention in the method for registered ims users public ID, need make the user that a certain IMPU both can be set is shared by part IMPI, promptly only be associated with part IMPI, simultaneously this IMPU can be set is also shared by its all IMPI, promptly be associated with all IMPI, when certain IMPU was set to partly shared or overall sharing, associated IMPI followed existing mechanism in the requirement of registering and use is served when using this IMPU.

Carry out in the IP Multimedia System of the present invention among first embodiment of the local method of sharing sharing property element and realizing by IMPU is set.

This IMPU shares property element and comprises that two daughter element: IMPU share scope daughter element SharedRange and share I MPI tabulation daughter element SharedIMPIList, wherein:

SharedRange show this IMPU be of overall importance shared, or locality share, when sharedRange value is 0, represent of overall importance sharing, be then to represent the shared of locality at 1 o'clock;

When the SharedRange value was 1, SharedIMPIList was used to store the IMPI tabulation that needs are shared this IMPU.

As the shared relationship that is provided among Fig. 4, wherein shared relationship is as follows: IMPU1 and IMPU5 do not share, IMPU2 and IMPU4 by the part share, IMPU3 shared by the overall situation, its XML document representation is as follows:

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

</PublicIdentity>

<Identity>sip:Public?User?Identity-2@homedomain.com</Identity>

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

<IMPI>Private?User?Identity-2@homedomain.com</IMPI>

</SharedIMPIList>

＜/Shared〉// be set to local sharing, and indicate the IMPI tabulation that needs to share this IMPU

</PublicIdentity>

<Identity>sip:Public?User?Identity-3@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

＜/Shared〉// be set to the overall situation share

</PublicIdentity>

<Identity>sip:Public?User?Identity-4@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

<IMPI>Private?User?Identity-3@homedomain.com</IMPI>

</SharedIMPIList>

</PublicIdentity>

＜Identity〉sip:Public User Identity-5@homedomain.com＜/Identity〉// do not share

<PrivateID>Private?User?Identity-3@homedomain.com</PrivateID>

</PublicIdentity>

Be that example illustrates corresponding server testing process with registration IMPU1 below, comprise the steps:

Step 501, certain UE initiates the request of registration IMPU1 to core net, and the IMPI that this UE solidifies is IMPI1;

Step 502, whether the inspection of core net associated components needs to share the registration in the association, specifically comprises the steps:

Step 5021, in the IMPU1 information that the inspection database is preserved, whether its privately owned ID of former related IMS user (PrivateID) is IMPI1, is IMPI1 if be checked through, show the original just related IMPU1 of this IMPI, then returned the response of agreeing this IMPU of registration this moment; Otherwise, show that this IMPI originally was not associated with IMPU1, then entered the inspection that step 5022 is shared related aspect;

Step 5022 checks whether IMPU1 is provided with shared property element, is provided with if be checked through, then enters step 503; Otherwise show that promptly IMPU1 is not shared, it is related obviously can to determine that IMPU1 and IMPI1 do not exist this moment, then can return the response of this IMPU of refusal registration;

This step 502 also can be:

Step 5021 ', check whether IMPU1 is provided with shared element property, is provided with if be checked through, shows that IMPU1 has been set to share, and enters step 503; Otherwise, show that IMPU1 is not shared to enter step 5022 ';

Step 5022 ', check whether the privately owned ID of former related IMS user (PrivateID) of IMPU1 is IMPI1, if then return the response of agreeing this IMPU of registration; If not and IMPU1 be not set to share, then return the response of this IMPU of refusal registration;

Step 503, the core net associated components continues the correlation attribute value of the shared element property of inspection IMPU1, if the SharedRange attribute is 0, perhaps the SharedRange attribute be 1 and SharedIMPIList in exist certain IMPI consistent with IMPI1, then return the response of agreeing to register this IMPU; Otherwise, return the response of this IMPU of refusal registration.

Carry out in the IP Multimedia System of the present invention among second embodiment of the local method of sharing, share secret key and realize by using, promptly replace share I MPI tabulation daughter element SharedIMPIList among first embodiment by increasing a shared key daughter element SharedPassword.For example, if the IMPU1 of IMPI1 will share to IMPI2, the SharedPassword property value then can be set and it is distributed to the UE or the server preservation of solidifying IMPI2, then just can just can register by mating this shared secret key when IMPI2 will register this IMPU1, other IMPI that does not obtain this shared secret key then can not register.

Therefore carry out in the IP Multimedia System of the present invention among second embodiment of the local method of sharing, IMPU shares property element and comprises two daughter elements: share scope daughter element SharedRange and shared key daughter element SharedPassword, wherein:

Sharing scope daughter element SharedRange and be used to indicate that this shares is of overall importance, or locality, represent of overall importance sharing when sharedRange value is 0, is then to represent the shared of locality at 1 o'clock;

Shared secret key when shared key daughter element SharedPassword is used to indicate the locality sharing.

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

</PublicIdentity>

<Identity>sip:Public?User?Identity-2@homedomain.com</Identity>

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

＜/Shared〉// be set to local sharing, and indicate shared secret key

</PublicIdentity>

<Identity>sip:Public?User?Identity-3@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

＜/Shared〉// be set to the overall situation share

</PublicIdentity>

＜Identity〉sip:Public User Identity-4@homedomain.com＜/Identity〉// do not share

<PrivateID>Private?User?Identity-3@homedomain.com</PrivateID>

</PublicIdentity>

Be example with registration IMPU1 below, corresponding server testing process is described, comprise the steps:

Step 601, certain UE initiates the request of registration IMPU1 to core net, and the IMPI that this UE solidifies is IMPI1;

Step 602, whether the inspection of core net associated components needs to share the registration in the association, specifically comprises the steps:

Step 6021, in the IMPU1 information that the inspection database is preserved, whether its privately owned ID of former related IMS user (PrivateID) is IMPI1, is IMPI1 if be checked through, show the original just related IMPU1 of this IMPI, then returned the response of agreeing this IMPU of registration this moment; Otherwise, show that this IMPI originally was not associated with IMPU1, then proceed to share the inspection of related aspect;

Step 6022 checks whether IMPU1 is provided with shared property element, is provided with if be checked through, then enters step 603; Otherwise show that promptly IMPU1 is not shared, it is related obviously can to determine that IMPU1 and IMPI1 do not exist this moment, then can return the response of this IMPU of refusal registration;

This step 602 also can be:

Step 6021 ', check whether IMPU1 is provided with shared element property, is provided with if be checked through, show that IMPU1 has been set to the shared step 603 that then enters; Otherwise, show that IMPU1 is not shared, and enters step 6022 ';

Step 6022 ', check whether the privately owned ID of former related IMS user (PrivateID) of IMPU1 is IMPI1, if then return the response of agreeing this IMPU of registration; If not and IMPU1 be not set to share, then return the response of this IMPU of refusal registration;

Step 603, the core net associated components continues the correlation attribute value of the Shared element of inspection IMPU1, if the SharedRange attribute is 0, or the SharedRange attribute for 1 and the SharedPassword property value consistent with the SharedPassword that IMPI1 is provided, then return the response of agreeing this IMPU of registration; Otherwise, return the response of this IMPU of refusal registration.

At this, the core net associated components can be S-CSCF (Serving-CallSession Control Function) parts in the IMS core net, but may replace S-CSCF with other functional part in practice.

When the method for carrying out sharing the part in the IP Multimedia System of the present invention combines with recessive registration, when an IMPU among certain IRS is shared, the user both can make other IMPU among this IRS only be used by certain IMPI, promptly only be associated with an IMPI, also can make it be shared all relevant IMPI and use, promptly be associated with and share all relevant IMPI, on this basis, when certain IRS was set up, associated IMPI must follow the requirement of current mechanism when using this IRS.

Carry out in the IP Multimedia System of the present invention among first embodiment of the local method of sharing sharing property element and realizing,, increase an IRS property element at this by IMPU is set.

This IRS property element comprises that two daughter element: IRS share scope daughter element IRSRange and IRS ID daughter element IRSid, wherein:

It is multi-joint property, or simply connected that IRSRange indicates this IRS, when being 0, the IRSRange value represents multi-joint property, this IMPU can be associated with and share all relevant IMPI, represents simply connected when property value is 1, promptly only is associated with the original associated IMPI of current this IMPU;

IRSid indicates id number of current I RS, and the IMPU that the IRSid value is identical belongs to same IRS.

Shared relationship shown in Figure 5 is as follows: IMPU1, IMPU9, IMPU10 do not share, IMPU2, IMPU3, IMPU4, IMPU7 and IMPU8 by the part share, IMPU5 and IMPU6 shared by the overall situation, its XML document representation is as follows:

<PrivateID>Private?User?Identity-1@homedomain.com</PrivateID>

<IRS>

</IRS>

</PublicIdentity>

<Identity>sip:Public?User?Identity-2@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

<IRS>

</IRS>

<IMPI>Private?User?Identity-2@homedomain.com</IMPI>

</SharedIMPIList>

</PublicIdentity>

<Identity>sip:Public?User?Identity-3@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

<IRS>

</IRS>

<IMPI>Private?User?Identity-1@homedomain.com</IMPI>

</SharedIMPIList>

</PublicIdentity>

<Identity>sip:Public?User?Identity-4@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</P?rivateID>

<IRS>

</IRS>

<IMPI>Private?User?Identity-1@homedomain.com</IMPI>

</SharedIMPIList>

</PublicIdentity>

<Identity>sip:Public?User?Identity-5@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

<IRS>

</IRS>

＜/Shared〉// be set to all share

</PublicIdentity>

<Identity>sip:Public?User?Identity-6@homedomain.com</Identity>

<PrivateID>Private?User?Identity-2@homedomain.com</PrivateID>

<IRS>

</IRS>

＜/Shared〉// be set to all share

</PublicIdentity>

<Identity>sip:Public?User?Identity-7@homedomain.com</Identity>

<PrivateID>Private?User?Identity-3@homedomain.com</PrivateID>

<IRS>

</IRS>

<IMPI>Private?User?Identity-2@homedomain.com</IMPI>

</SharedIMPIList>

</PublicIdentity>

<Identity>sip:Public?User?Identity-8@homedomain.com</Identity>

<PrivateID>Private?User?Identity-3@homedomain.com</PrivateID>

<IRS>

</IRS>

<IMPI>Private?UserIdentity-2@homedomain.com</IMPI>

</SharedIMPIList>

</PublicIdentity>

＜Identity〉sip:Public User Identity-9@homedomain.com＜/Identity〉// do not share

<PrivateID>Private?User?Identity-3@homedomain.com</PrivateID>

<IRS>

</IRS>

</PublicIdentity>

＜Identity〉sip:Public User Identity-10@homedomain.com＜/Identity〉// do not share

<PrivateID>Private?User?Identity-3@homedomain.com</PrivateID>

<IRS>

</IRS>

</PublicIdentity>

Carry out recessiveness with registration IMPU1 below and be registered as example, corresponding server testing process is described, it comprises the steps:

Step 701, UE (having solidified IMPI1) has finished the request of registration IMPU1 in core net, and obtains whether this IMPU1 just is associated with IMPI1 after sharing information;

Step 702, core net associated components are obtained the value of the IRS property element of IMPU1;

Step 703, the core net associated components whether just is associated with the information of IMPI1 according to IMPU1 after sharing and the IRS property element of this IMPU judges whether to carry out the recessiveness registration, specifically comprises the steps:

Step 7031, the IRS property element of IMPU1 does not exist, and shows that IMPU1 does not belong to any recessive registered set, and UE (having solidified IMPI1) does not carry out the recessiveness registration;

Step 7032, the IRS property element of IMPU1 exists, and does not exist but IRS shares scope daughter element IRSRange, and IMPU1 just is associated with IMPI1 after sharing, UE (having solidified IMPI1) does not carry out the recessiveness registration, and wherein, this is shared and comprises that the overall situation is shared and local sharing;

Step 7033, the IRS property element of IMPU1 exists, but IRS shares scope daughter element IRSRange not to be existed, and IMPU1 just is associated with IMPI1 after sharing, then search other IMPU identical with the IRSid of IMPU1, if other IMPU identical with the IRSid of IMPU1 and IMPI1 do not exist related (its privately owned ID of former related IMS user (PrivateID) and IMPI1 are inconsistent, and the IRSRange property value is not 1), UE (having solidified IMPI1) does not carry out the recessiveness registration; If the privately owned ID of former related IMS user (PrivateID) of other IMPU identical with the IRSid of IMPU1 and IMPI1 unanimity, the IRSRange property value is 1 o'clock simultaneously, and UE (having solidified IMPI1) carries out the recessiveness registration;

Step 7034, the IRS element of IMPU1 exists, and the IRSRange property value is 0 or 1 o'clock, and UE (having solidified IMPI1) can register carrying out recessiveness, promptly all IMPUs identical with the IRSid of IMPU1 is registered.

Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art work as can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection range of the appended claim of the present invention.

Claims

1. the method for registered ims users public ID in the IP Multimedia System is characterized in that, comprises the steps:

2. the method for registered ims users public ID is characterized in that in the IP Multimedia System according to claim 1, and described shared property element comprises:

3. the method for registered ims users public ID is characterized in that in the IP Multimedia System according to claim 2, and the core net associated components returns the response of agreeing the described IMS user public ID of described user equipment registration in following several situations:

4. the method for registered ims users public ID is characterized in that in the IP Multimedia System according to claim 1, and described shared property element comprises:

5. the method for registered ims users public ID is characterized in that in the IP Multimedia System according to claim 4, and the core net associated components returns the response of agreeing the described IMS user public ID of described user equipment registration in following several situations:

The privately owned ID of former related IMS user of a described IMS user public ID is the privately owned ID of the 2nd IMS user, but the value of the shared scope daughter element of a described IMS user public ID is second particular value, and the key that the privately owned ID of a described IMS user provides is identical with described shared key.

6. recessive process registration in the IP Multimedia System is characterized in that, comprises the steps:

7. recessive process registration in the IP Multimedia System according to claim 6 is characterized in that, described shared property element comprises:

Described recessive registered set property element comprises:

8. recessive process registration in the IP Multimedia System according to claim 6 is characterized in that, described shared property element comprises:

Described recessive registered set property element comprises:

9. according to recessive process registration in claim 7 or the 8 described IP Multimedia System, it is characterized in that under following several situations, described subscriber equipment carries out the recessiveness registration: