WO2008095402A1

WO2008095402A1 - A method and a device for activating and registering a personal network management circuit domain terminal

Info

Publication number: WO2008095402A1
Application number: PCT/CN2008/000169
Authority: WO
Inventors: Xiaoyan He; Shuang Liang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-02-02
Filing date: 2008-01-23
Publication date: 2008-08-14
Also published as: CN101237678B; CN101237678A

Abstract

A method and a device for activating a personal network management circuit domain terminal is used to complete the activation of a user equipment UE which has registered with a personal network PN in the PNM service. a method and a device for activating and registering a personal network management circuit domain terminal is used to enable the PNM server to interact the PNM service related data with the HSS. The method for activating a personal network management circuit domain terminal comprises the following steps: the personal network management PNM server receives an activation request containing an activation configuration sent by the circuit domain terminal; the PNM server authenticates the activation right of the circuit domain terminal and authenticates the activation configuration; the PNM server stores the activation configuration for completing the activation operation when both the authentication are passed.

Description

Method and device for activating and registering personal network management circuit domain terminal

The present invention relates to the field of communications, and in particular, to a method, system and apparatus for activating and registering a terminal of a personal network management circuit domain. Background technique

A new PNM (Personal Network Management) service has been introduced. This service is aimed at a scenario where a user in a future network may have multiple terminal devices. The network composed of these terminal devices is called a PN (Personal Network), and the centralized management of the user is PNM. The PNM service mainly provides two services for users: re-targeting services and private network services. Users can set the order of ending specific services and the access rights of terminals according to the capabilities of different terminals in the PN and personal preferences, so as to obtain a better service experience.

At present, the architecture of the service in the CS domain has been adopted, and the architecture of CAMEL (Customized Applications for Mobile Network Enhanced Logic) has been adopted. In this architecture, the PNM service is regarded as a smart (CAMEL) service, and the execution of the PNM service is completed in the gsmSCF (GSM Service Control Function), that is, the gsmSCF acts as a PNM server.

HSS (Home Subscriber Server) is the most important database for each user. It stores user-related and subscription-related data, and is used to support other entities in the network to handle calls or sessions, and other various services. Including: user's identity, numbering and addressing information; user's security information, including authorization and authentication; user's location information; user's configuration information. For the HLR (Home Location Register) before R5, the HSS is a superset of it, containing all the data that the HLR can provide.

The gsmSCF is a functional entity that includes CAMEL service logic in the CS (Circuit Switched) domain to implement operator-specific services. In the CAMEL implementation architecture of PNM, the relevant data of the PNM service needs to be exchanged between the gsmSCF and the HSS.

In the prior art, the MAP (Mobile Application Part) interface is used for information interaction between the gsmSCF and the HSS, and the interactive content includes: CF (Call Forward) and CB (Call Barring) for the CS domain. Blocking, ODB (Object DataBase) data, CSI (CAMEL Subscription Information, CAMEL subscription information) data query, modification and subscription. The specific content includes the following aspects: Use Any Time Modification Request (ack) to modify and subscribe to related data of CF, CB, ODB and CSI services. When these data changes, the gsmSCF that has subscribed is obtained through Notify Subscriber Data Change. Port; Use Any Time Subscription Interrogation Request for CF, CB, ODB, CSI, and user-subscribed basic business lists.

The redirection service is an important part of the PNM service. How to activate a valid redirection record (ie, activate a user equipment UE that has been registered to the PN of the personal network) is very important for the implementation of the redirection service, because it is effective. Activation can guarantee the correct execution of the redirected service. However, the prior art cannot implement activation of a user equipment UE that has registered to the personal network PN.

As a new CAMEL service, the PNM service currently has few data related to the PNM service. It only supports the indication of whether to sign the PNM service, and cannot meet the requirements of the PNM service for the user's subscription data. The logic and execution of the PNM service are performed on the gsmSCF. The HSS should update the PNM service subscription data of the user according to the logic and execution result of the gsmSCF. However, the data related to the PNM service cannot be exchanged between the gsmSCF and the HSS.

When the basic service or attachment status of the user subscription changes, the HSS should notify the gsmSCF to perform the corresponding processing, but currently the gsmSCF and the HSS cannot exchange data related to the PNM service.

The inventors found in the course of the invention that the prior art cannot activate a user equipment UE that has registered to the personal network PN.

As in the prior art, data related to the PNM service cannot be exchanged between the PNM server and the HSS. SUMMARY OF THE INVENTION A user equipment UE that has registered to a personal network PN is activated. So, so that the PNM server and the HSS can exchange data related to the PNM service.

A method for activating a personal network management circuit domain terminal according to an embodiment of the present invention includes the following steps: a personal network management PNM server receives an activation request sent by a circuit domain terminal and carries an activation configuration; and a PNM server activates the circuit domain terminal The authority is authenticated, and the activation configuration is authenticated; the PNM server saves the activation configuration when the two authentications pass, to complete the activation operation.

A PNM server according to an embodiment of the present invention includes: an activation request receiving unit, configured to receive an activation request sent by a circuit domain terminal; and an authentication unit, configured to receive, by the activation request receiving unit, an activation request sent by the circuit domain terminal After that, the activation authority of the circuit domain terminal is authenticated, and the activation configuration carried in the activation request is authenticated. The activation unit is configured to save the activation configuration when the authentication unit confirms that both authentications are passed. , to complete the activation operation.

A home subscription register of the embodiment of the present invention includes: a PN identifier holding unit, configured to save a PN identifier inserted by the PNM server, and an association relationship between the PN identifier and its corresponding PN.

A method for registering a personal network management circuit domain terminal according to an embodiment of the present invention includes the following steps: the PNM server receives a request sent by a circuit domain terminal to join a registration request of a PN; and the PNM server inserts a request with the circuit domain terminal to the HSS The PN identifier corresponding to the added PN indicates that the circuit domain terminal is registered to the PN, and indicates that the circuit domain terminal cannot register to other PNs before the PN removal registration.

Another PNM server of the embodiment of the present invention includes: a registration request receiving unit, configured to receive a registration request sent by a circuit domain terminal to join a PN; and an insertion unit, configured to receive the circuit domain terminal at the registration request receiving unit After the registration request is sent, the PN identifier corresponding to the PN that the circuit domain terminal requests to join is inserted into the HSS to indicate that the circuit domain terminal is registered to the PN, and the table It is clear that the circuit domain terminal cannot register to other PNs before the PN removal registration.

The activation scheme of the personal network management circuit domain terminal of the embodiment of the present invention discloses a process of activating a user equipment UE registered to the personal network PN in the PNM service.

And the registration scheme of the personal network management circuit domain terminal of the embodiment of the present invention discloses a process of interacting with the PNM service related data between the PNM server and the HSS.

This further satisfies the needs of PNM services and users. DRAWINGS

1 is a flowchart of a method for activating a personal network management circuit domain terminal according to an embodiment of the present invention; FIG. 2 is a schematic structural diagram of an activation system for a personal network management circuit domain terminal according to an embodiment of the present invention; FIG. 3 is a PNM according to an embodiment of the present invention; Schematic diagram of the server;

4 is a schematic structural diagram of Embodiment 1 of a PNM server according to the present invention;

5 is a schematic structural diagram of Embodiment 2 of a PNM server according to the present invention;

6 is a schematic structural diagram of a home subscription register according to an embodiment of the present invention;

FIG. 7 is a flowchart of a method for registering a terminal of a personal network management circuit domain according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of a registration system for a terminal of a personal network management circuit domain according to an embodiment of the present invention; Signaling flow chart;

10 is a signaling flowchart of Embodiment 2 of a method according to the present invention;

11 is a signaling flowchart of Embodiment 3 of a method according to the present invention;

12 is a signaling flowchart of Embodiment 4 of a method according to the present invention;

13 is a signaling flowchart of Embodiment 5 of a method according to the present invention;

14 is a flowchart of a signaling method according to Embodiment 6 of the present invention;

FIG. 15 is a signaling flowchart of Embodiment 7 of a method according to the present invention. detailed description

In order to complete the PNM service, a user equipment UE that has registered to the personal network PN is activated. An embodiment of the present invention provides a method for activating a terminal of a personal network management circuit domain, as shown in FIG. 1 As shown, the following main steps are included:

S11. The circuit domain terminal sends an activation request to the PNM server.

The circuit domain terminal sends an activation request carrying the activation configuration to the PNM server. There are two cases:

One of the sending activation request conditions, the circuit domain terminal initiates an active activation, that is, sends an activation request to the PNM server, and the activation request carries an activation configuration.

In the second case of sending the activation request, the circuit domain terminal initiates an invitation activation request to the third-party circuit domain terminal, and the PNM server determines whether the circuit domain terminal has the activation authority by whether the circuit domain terminal that initiates the invitation activation request has been registered in the PN. . When it is determined that there is an activation right, the PNM server forwards the invitation activation request to the invited circuit domain terminal and starts a timer. After receiving the request, the invited circuit domain terminal decides whether to initiate active activation to the PNM server according to the user's will. When the circuit domain terminal invited in the preset time does not initiate active activation, it is determined that the invitation activation fails, and the PNM server sends an invitation activation failure response to the circuit domain terminal that initiates the invitation activation request; when the circuit is invited within the preset time The domain terminal initiates active activation (that is, sends an activation request to the PNM server, the activation request carries an activation configuration), and after completing the activation, determines that the invitation activation is successful, and the PNM server sends the invitation activation to the circuit domain terminal that initiates the invitation activation request. response.

In the activation configuration, the activation type needs to be explicitly indicated, or the activation configuration carries parameters to implicitly indicate the activation type. The activation type includes global activation, specific service activation, media type activation, and global activation allows the user to not specify any The service code and the media component, the specific service activation requires the user to specify the service code, and the media type activation requires the user to specify the service code and the media type. If the activation type is implicitly specified, the MSISDN (Mobile Station International ISDN Number) number of the circuit domain terminal is carried in the activation configuration, and the service code that needs to be redirected to the MSISDN number may be further carried. And/or the media type identifier, if it does not contain any service code, it is considered to be global activation, if it only contains the service code, it is considered to be a specific service activation, and if the service code and the media component are included, it is considered to be the media component activation. If the activation type is explicitly indicated, the MSISDN number and the activation type of the circuit domain terminal are carried in the activation configuration. The step may also carry a service code and/or media type identifier that needs to be redirected to the MSISDN number. S12. The PNM server authenticates the activation permission of the circuit domain terminal, and authenticates the activation configuration. If both the above authentications are passed, the process proceeds to step S13; otherwise, the activation process is ended.

The PNM server authenticates the activation rights of the circuit domain terminals and authenticates the activation configuration in no particular order.

The PNM server authenticates the activation rights of the circuit domain terminal, including the following contents:

The PNM server may determine, according to a preset policy, whether the circuit domain terminal has an activation right, for example: the PNM server determines whether the circuit domain terminal has an activation right by whether the circuit domain terminal is registered in the PN, that is, the circuit domain terminal is registered to Within the PN, it is determined that there is an activation authority, otherwise, it is determined that there is no activation authority.

There are two cases in the above process of registering to the PN:

One of the registration conditions, the circuit domain terminal initiates registration.

The circuit domain terminal sends a registration request to the PNM server requesting to join a PN. After receiving the registration request, the PNM server carries the PNM data by expanding the MAP message (in a specific implementation, the PNM data may be added in the MAP Any Time Modification Request) to transmit the PN identifier through the MAP interface, thereby inserting the PN identifier into the HSS. A PN identifier corresponding to the PN that the circuit domain terminal requests to join to indicate that the circuit domain terminal is registered to the PN, and indicates that the circuit domain terminal cannot register to other PNs before the PN removal registration.

In the second registration case, the circuit domain terminal initiates third party registration.

When the PNM server receives the invitation registration request, the PNM server determines whether the circuit domain terminal has the invitation authority by whether the circuit domain terminal that initiated the invitation registration request has been registered in the PN. When it is determined that there is an invitation authority, the PNM server forwards the invitation registration request to the invited circuit domain terminal, and starts a timer. After receiving the request, the invited circuit domain terminal decides whether to initiate a registration request to the PNM server according to the user's will. When the circuit domain terminal invited in the preset time does not actively initiate the registration request, it is determined that the invitation registration fails, and the PNM server returns an invitation registration failure response to the circuit domain terminal that initiated the invitation registration request; when invited within a preset time The circuit domain terminal initiates a registration request (ie, continues one of the above registration conditions), and after completing the registration, determines the invitation to board If the record is successful, the PNM server returns an invitation registration success response to the circuit domain terminal that initiated the invitation registration request.

The PNM server authenticates the activation configuration carried in the activation request sent by the circuit domain terminal, including the following contents:

The PNM server queries the HSS for the subscription service corresponding to the MSISDN number carried in the activation request, and the PNM server determines that the queried subscription service includes the service code in the activation configuration, and the activation configuration matches the subscription service of the circuit domain terminal; the PNM server determines the circuit domain. The terminal capability of the terminal can satisfy the capability required by the service or media included in the activation configuration, and the activation configuration matches the terminal capability of the circuit domain terminal. There is a special case in which, when the service code and the media component are both empty in the active configuration, the PNM server uses the subscription service code corresponding to the MSISDN carried in the activation request as the service code in the activation configuration, and determines the activation configuration matching circuit. The subscription service of the domain terminal; and the PNM server determines that the terminal capability of the circuit domain terminal can satisfy the capability required by the subscription service or the media corresponding to the MSISDN, and the activation configuration matches the terminal capability of the circuit domain terminal.

When the activation configuration matches the subscription service of the circuit domain terminal and the terminal capability of the circuit domain terminal, the PNM server determines that the activation configuration authentication passes.

S13. The PNM server saves the activation configuration to complete the activation operation.

When the activation request initiated by the circuit domain terminal is active activation (including direct active activation and active activation initiated by a third party invitation), the PNM server saves the activation configuration carried in the activation request. There is a special case in which, when the service code and the media component are both empty in the active configuration, the PNM server uses the subscription service code corresponding to the MSISDN carried in the activation request as the service code in the activation configuration, and after the activation configuration authentication is passed, The PNM server saves the activation configuration.

Thereafter, the activation response returned to the circuit domain terminal includes the MSISDN number of the circuit domain terminal, the service code redirected to the MSISDN number, and/or the media type identification.

After the step S13, the subscription operation may also be performed: the MAP message is used to carry the related information of the subscription identifier, and the related information of the subscription identifier is transmitted through the MAP interface (in a specific implementation, the MAP Any Time Modification Request message may be added. Types of parameters that can be subscribed, such as: subscription subscription service changes, attachment status changes, etc., so that the PNM server can send subscriptions to the HSS After receiving the subscription request sent by the PNM server, the HSS sets a subscription identifier for the subscription service list and/or the attachment status of the MSISDN number carried in the activation request according to the indication therein.

After the subscription operation is completed, when the attachment status of the circuit domain terminal changes, the HSS notifies the PNM server (specifically, the attachment status is added to the MAP message and is transmitted through the MAP interface); the PNM service determines that the received notification indicates the circuit domain terminal. When the attached state is changed to the separated state, the activation configuration associated with the activation of the circuit domain terminal is initiated to perform a deactivation operation. When the subscription service list of the circuit domain terminal changes, the HSS notifies the PNM server; when the PNM server determines that the received notification indicates that the subscription service in the circuit domain terminal subscription service list changes from the subscription status to the unsigned status, the subscription service The associated activation configuration performs a deactivation operation.

If the HLR is a subset of the HSS embedded, the HLR unconditionally notifies the HSS of the event through the internal interface when the user circuit field information changes through the information exchange with the VLR. If the HSS and the HLR are located in different physical entities, the HLR detects that the user circuit domain information changes through the interaction with the VLR, and the HSS changes the information of the user circuit domain from the HLR through the external interface.

The subscription and notification mechanism can further satisfy the management and correspondence of the PNM service subscription data by passing the subscription identifier for the attachment status information and/or the user subscription list in the MAP message.

Before the step S11, the query operation may also be performed: the circuit domain terminal initiates an activation query request to the PNM server, where the MSISDN number of the circuit domain terminal is carried; the PNM server obtains the MSISDN number carried in the activation query request, and saves it locally. The activation record records the activation configuration information corresponding to the MSISDN number; and the PNM server returns the queried activation configuration information to the circuit domain terminal. Through the above query mechanism, the circuit domain terminal can be targeted to initiate an activation request.

In the above content, the deregistration process after completion of registration is similar to the active registration process. The gsmSCF (ie, PNM server) responsible for the PNM service in the deregistration process deletes the PN identity that has been added to the PN to the HSS to ensure the circuit domain after the process. The terminal can rejoin other PNs. The operation of deleting the PN identifier can be achieved by setting the PN flag to null. Other steps in the process and the main The registration is similar, and will not be repeated here.

The deactivation process is similar to the active activation process. Deactivation messages also require parameters similar to the activation request to indicate which level of deactivation is active. The gsmSCF (ie, the PNM server) responsible for the PNM service needs to determine whether to perform the deactivation operation by whether there is an activation record matching the request, and if so, delete the corresponding activation record, and remove the subscription service list and/or attachment status to the HSS. Subscription. The other steps in the process are similar to active activation and will not be described here.

The embodiment of the present invention further provides an activation system for a personal network management circuit domain terminal. As shown in FIG. 2, the circuit domain terminal and the PNM server are included.

The circuit domain terminal is configured to send an activation request carrying an activation configuration to the PNM server. The PNM server is configured to receive an activation request sent by the circuit domain terminal, authenticate the activation authority of the circuit domain terminal, and authenticate the activation configuration; when the two authentications are passed, save the activation configuration. , to complete the activation operation.

Further, the circuit domain terminal is further configured to send a registration request to the PNM server to join the PN; the PNM server is further configured to receive the registration request sent by the circuit domain terminal, and carry the PNM data by extending the MAP message to pass The MAP interface between the PNM server and the HSS transmits the PN identifier, thereby inserting a PN identifier corresponding to the PN that the circuit domain terminal requests to join to the HSS, to indicate that the circuit domain terminal is registered to the PN, and indicating that the circuit domain terminal is The PN may not be registered to other PNs before registration; and the system further includes an HSS for holding the PN identifier inserted by the PNM server and the association relationship between the PN identifier and its corresponding PN.

Further, when the activation request initiated by the circuit domain terminal is active activation, the PNM server is further configured to carry the MSISDN number of the circuit domain terminal in the activation response returned to the circuit domain terminal, and is redirected to the service code of the MSISDN number. And/or media type identification.

Further, after the PNM server saves the activation configuration and completes the activation operation on the circuit domain terminal, the PNM server is further configured to carry the information about the subscription identifier by using the extended MAP message to deliver the subscription through the MAP interface between the PNM server and the HSS. Identifying related information to send a subscription request to the HSS; and the HSS is further configured to receive a subscription request sent by the PNM server, and according to the indication, a subscription service list and/or attached to the MSISDN number carried in the activation request The status sets the subscription ID.

Further, before the circuit domain terminal initiates the activation request, the circuit domain terminal is further configured to initiate an activation query request to the PNM server, where the MSISDN number of the circuit domain terminal is carried; and the PNM server is further configured to receive the activation sent by the circuit domain terminal. Querying the request and obtaining the MSISDN number carried in the activation query request, and querying the activation configuration information corresponding to the MSISDN number from the locally saved activation record, and returning the queried activation configuration information to the circuit domain terminal.

The embodiment of the present invention further provides a PNM server, which is shown in FIG. 3, which includes an activation request receiving unit, an authentication unit, and an activation unit that are sequentially connected; the further authentication unit includes an activation authority authentication subunit and an activation configuration. Authentication subunit.

The activation request receiving unit is configured to receive an activation request sent by the circuit domain terminal.

The authentication unit is configured to: after the activation request receiving unit receives the activation request sent by the circuit domain terminal, authenticate the activation authority of the circuit domain terminal, and authenticate the activation configuration carried in the activation request.

The activation authority authentication subunit is configured to determine that the circuit domain terminal has an activation right when the terminal of the confirmation circuit domain has been registered in the personal network PN.

The activation configuration authentication subunit is configured to determine that the activation configuration authentication passes when the activation configuration is confirmed to match the subscription service of the circuit domain terminal and the terminal capability of the circuit domain terminal.

The activation unit is configured to: when the authentication unit confirms that the two authentications are passed, save the activation configuration to complete the activation operation.

Referring to Fig. 4, a registration request receiving unit and an insertion unit respectively connected to the activation authority authentication subunit and the registration request receiving unit are further included.

The registration request receiving unit is configured to receive a registration request sent by the circuit domain terminal to join a PN.

The inserting unit is configured to insert, after the registration request receiving unit receives the registration request sent by the circuit domain terminal, a PN identifier corresponding to the PN that the circuit domain terminal requests to join, to indicate that the circuit domain terminal is registered to the PN, and indicating that the circuit domain terminal cannot register to other PNs before the PN removal registration; and notifying the PN of the circuit domain terminal to activate the rights authentication subunit, or When the authorization authentication subunit is activated for authentication, the participant is queried to the insertion unit whether the circuit domain terminal has joined the PN.

Referring to FIG. 5, further comprising an activated query request receiving unit and a query unit connected to each other, the query unit is further connected to the activation unit.

The activation query request receiving unit is configured to receive an activation query request sent by the circuit domain terminal. The query unit is configured to obtain an MSISDN number carried in the activation query request, and query activation configuration information corresponding to the MSISDN number from an activation configuration saved by the activation unit, and return the queried activation configuration to the circuit domain terminal. information.

The embodiment of the present invention further provides a home subscription register, which includes a PN identifier holding unit, configured to save the PN identifier inserted by the PNM server, and the association relationship between the PN identifier and its corresponding PN.

Referring to FIG. 6, the method further includes: an interconnection request receiving unit and a setting unit.

The subscription request receiving unit is configured to receive a subscription request sent by the PNM server.

The setting unit is configured to: after the subscription request receiving unit receives the subscription request sent by the PNM server, set the subscription identifier to the subscription service list and/or the attachment status of the MSISDN number carried in the activation request according to the indication therein .

The embodiment of the present invention further provides a registration method for a personal network management circuit domain terminal, as shown in FIG. 7, which includes the following main steps:

S21. The circuit domain terminal sends a registration request to the PNM server to join a PN. There are two cases in which a circuit domain terminal sends a registration request to a PNM server:

In one of the cases, the circuit domain terminal initiates registration.

In one case, the circuit domain terminal initiates a third party registration.

When the PNM server receives the invitation registration request, the PNM server determines whether the circuit domain terminal has the invitation authority by whether the circuit domain terminal that initiated the invitation registration request has been registered in the PN. When it is determined that there is an invitation authority, the PNM server forwards the invitation registration request to the invited circuit domain terminal, and starts a timer. After the invited circuit domain terminal receives the request, it determines whether it is based on the user's will. A registration request is initiated to the PNM server. When the circuit domain terminal invited in the preset time does not actively initiate the registration request, it is determined that the invitation registration fails, and the PNM server returns an invitation registration failure response to the circuit domain terminal that initiated the invitation registration request; when invited within a preset time The circuit domain terminal actively initiates the registration request (ie, continues one of the above situations), and after completing the registration, determines that the invitation registration is successful, and the PNM server returns an invitation registration success response to the circuit domain terminal that initiated the invitation registration request.

S22. After receiving the registration request, the PNM server inserts, into the HSS, a PN identifier corresponding to the PN that the circuit domain terminal requests to join.

After receiving the registration request, the PNM server carries the PNM data by expanding the MAP message (in a specific implementation, the PNM data may be added in the MAP Any Time Modification Request) to transmit the PN identifier through the MAP interface, thereby transmitting the PN identifier to the HSS. A PN identifier corresponding to the PN that the circuit domain terminal requests to join is inserted to indicate that the circuit domain terminal is registered to the PN, and that the circuit domain terminal cannot register to other PNs before the PN removal registration.

In the above content, the deregistration process after completion of registration is similar to the active registration process. The gsmSCF (ie, PNM server) responsible for the PNM service in the deregistration process deletes the PN identity that has been added to the PN to the HSS to ensure the circuit domain after the process. The terminal can rejoin other PNs. The operation of deleting the PN identifier can be achieved by setting the PN flag to null. The other steps in the process are similar to the active registration and are not described here.

The embodiment of the present invention further provides a registration system for a personal network management circuit domain terminal, as shown in FIG. 8, comprising: a circuit domain terminal, a PNM server, and an HSS.

The circuit domain terminal is configured to send a registration request to the PNM server to join a PN. The PNM server is configured to receive a registration request sent by the circuit domain terminal, and carry the PNM data by extending the MAP message to pass the MAP interface between the PNM server and the HSS. Transmitting the PN identifier, thereby inserting a PN identifier corresponding to the PN that the circuit domain terminal requests to join to the HSS to indicate that the circuit domain terminal is registered to the PN, and indicating that the circuit domain terminal cannot register to other before the PN removal registration PN.

The HSS is configured to save a PN identifier inserted by the PNM server, and an association relationship between the PN identifier and its corresponding PN.

Another embodiment of the present invention further provides a PNM server including a registration request receiving unit and an inserting unit that are connected to each other.

An insertion unit, configured to: after the registration request receiving unit receives the registration request sent by the circuit domain terminal, insert a PN identifier corresponding to the PN that the circuit domain terminal requests to join to the HSS, to indicate that the circuit domain terminal is registered to the PN, And it is indicated that the circuit domain terminal cannot register to other PNs before the PN removal registration.

The following is specifically described by the seven embodiments.

Method Embodiment 1: Active registration process of a CS domain terminal. Before the PNM UE initiates the registration request, it has already signed the PNM service. The gsmSCF and the HSS responsible for the PNM service store the IMSI (International Mobile Subscriber Identifier) of the UE (User Equipment, User Equipment) that subscribes to the PNM service. And MSISDN, while the gsmSCF allocates a unique PN-ID for UEs belonging to the same PN. See Figure 9, which includes the following steps:

1. The circuit i or the terminal sends a registration request through US SD (Unstructured Supplementary Service Data), which includes: IMSI, MSISDN, registration type, AccessLevel. The last item is an optional parameter.

2. The request is routed to the MSC (Mobile Switching Center) / VLR (Visit Location Register). The MSC/VLR passes the parameters in the USSD and passes it through to the HSS.

3. The HSS routes the service code in the USSD to the gsmSCF that is responsible for the PNM service. 4. The gsmSCF sends a request to the HSS to insert a unique identifier PN-ID that can identify the UE to join the PN in the HSS, and the identifier is used to identify that the UE has joined a PN.

5. HSS checks if the IMSI or MSISDN already has a PN-ID record. If there is no record or the record value is empty, the insert ID is returned with a successful response. Otherwise return the insert ID failure response.

6. If the failure response is returned here, you do not need to perform step 7. Jump directly to steps 8~10 to return the registration failure response, otherwise execute sequentially.

7. The gsmSCF locally stores a registration record of the UE according to the successful response returned by the HSS, including: IMSI, MSISDN, PN-ID, AccessLeveL

8-10. The gsmSCF returns a registration response to the UE through the HSS and the MSC/VLR.

Method Embodiment 2: The third party registration process of the CS domain terminal (the essence of the third party registration is the process in which the UE in the PN invites the PN outside the UE to join the PN). See Figure 10, which includes the following steps:

1~3. UE1 sends a registration invitation request through USSD, which includes: IMSI of UE1, MSISDN of UE1, registration type (third party registration), and MSISDN of UE2. The request is routed to the gsmSCF through the MSC/VLR and HSS.

4. The gsmSCF receives the request according to the locally saved record, determines whether UE1 has registered to a certain PN, and invites UE2 to join the same PN. If not, return the invitation failure response directly, otherwise perform the next steps in sequence.

5-7. The gsmSCF sends a registration invitation through the USSD, which includes: MSISDN of UE2, MSISDN of UEl. The request is routed to UE2 through the HSS, MSC/VLR. At the same time, gsmSCF starts a timing, which is used to request UE2 to initiate the registration process within the specified time.

8-10. After receiving the notification, UE2 returns a response message according to the original path.

11. UE2 initiates an active registration process. If the timer does not time out at this time, the active registration step is performed sequentially. Otherwise, the gsmSCF sends a cancel invitation notification message to the UE2, and directly performs steps 12~14 to return an invitation registration failure response to the UE1.

12-14. The gsmSCF sends a registration invitation response via USSD, which contains the results of the registration invitation. The request is routed to UE1 through the HSS, MSC/VLR.

Method Embodiment 3: The active activation process of the CS domain terminal. See Figure 11, including the following steps Step:

1-2. CS domain PNM UE1 sends a USSD request to the HSS through the VMSC (Visit MSC) to access the current configuration information. The request carries the MSISDN to be queried.

3. The HSS routes the service code to the gsmSCF responsible for the PNM service based on the mapping between the service code in the USSD and the locally stored gsmSCF address.

4-6. The gsmSCF judges the authority of the UE according to the locally saved activation configuration, and returns the query result if the UE has the permission query. The query response is returned to the UE by the HSS and the MSC/VLR.

7~8. CS domain PNM UE1 sends the USSD request to the HSS through the VMSC/VLR. The request contains the IMSI, MSISDN, activation type, and optionally includes the service code and priority parameter that you want to activate.

9. The HSS routes the service code to the gsmSCF responsible for the PNM service based on the mapping between the service code in the USSD and the locally stored gsmSCF address.

10. The gsmSCF determines whether the UE has registered to a PN based on the locally stored registration record. If it is not added, skip steps 11~17 and go directly to steps 18~20 to return the activation failure response. Otherwise, the subsequent steps are performed in sequence.

11. The gsmSCF queries the HSS through the MAP interface for the basic service code list signed by the MSISDN.

12. The HSS returns all the subscription services and current status of UE1. If the service code is included in the request, it is necessary to match the service code carrying the service code and the subscription in the request. If there is no match at all, skip steps 13~17 and go directly to steps 18-20 to return the activation failure response. Otherwise, follow the steps in sequence.

13-14. The gsmSCF acquires the capability information of the activated UE from the entity that stores the UE capability information. Note: There is no strict order relationship between steps 11 and 12, 13 and 14. If the contract information or the terminal capability information has been obtained before, these steps can be omitted here.

15. The gsmSCF compares the capability information of the activated UE with the capabilities required to activate the service. If the capability of the UE can meet the service requirement in the activation request, the UE is considered to be successfully activated for the service, and the gsmSCF needs to record the service activation setting information (service code, priority). And the subsequent steps are performed sequentially. When all the services are not satisfied, skip steps 16~17 and return the activation failure response.

16-17. The gsmSCF sets a subscription identifier to the HSS for gsmSCF to be notified when the UE subscribes to the service or the registration status of the UE changes.

18-20. The gsmSCF returns an activation response to the UE through the HSS and the MSC/VLR.

The above steps 1~6 are user query activation configuration operations, which is an optional operation before the activation request. The user can perform the query configuration at any time, not limited to the activation request.

Method Embodiment 4: The third-party activation process of the CS domain terminal (the essence of the third-party activation is the process in which the UE in the PN invites other UEs in the PN to actively activate) „ Referring to FIG. 12, the following steps are included:

1~3. UE1 sends an activation request through USSD, which includes: IMSI of UE1, MSISDN of UE1, activation type (third party invitation activation), MSISDN of UE2, activation type, optionally recommended activation configuration, including hope Activated service code, priority parameter. The request is routed through the MSC/VLR, and the HSS is routed to the gsmSCF.

Note: Third-party activation only serves as a notification. UE2 expects that activation to be determined by UE2 itself. Therefore, UE1 gives the activation type (service code, media component) when the invitation is initiated, and UE2 may not. Follow this advice.

4. The gsmSCF receives the request to determine whether UE1 and UE2 have joined the same PN according to the locally saved record.

Note: Here, it is possible to check only whether UE1 has already registered to a PN, and then check the authority of UE2 in the process of UE2 performing active activation.

5~7. The gsmSCF sends an activation invitation through the USSD, which includes: MSISDN of UE2, MSISDN of UE1, optionally the recommended activation configuration, including the service code and priority parameter that you want to activate. The request is routed to UE2 through the HSS, MSC/VLR. At the same time, gsmSCF starts a timer, which is used to request UE2 to initiate an active activation process within a specified time.

11. UE2 initiates an active activation process. If the timer does not time out at this time, the active execution is performed sequentially. Activation step. Otherwise, the gsmSCF sends a cancel invitation notification message to the UE2, and directly performs steps 12-14 to return an invitation activation failure response to the UE1.

12-14. The gsmSCF sends an invitation activation response via USSD with the results of the invitation activation. The request is routed to UE1 through the HSS, MSC/VLR.

Method Embodiment 5: A network initiated deactivation process. See Figure 13, which includes the following steps:

1-2. When the attached status, and / or user subscription information changes, the HSS notifies the gsmSCF through the MAP interface. After receiving the notification, gsmSCF returns a response message to the HSS.

3. The gsmSCF determines whether to perform the deactivation operation based on the received notification. If the attachment state changes and changes from the attached state to the detached state, all activation failures associated with it will result in network-initiated deactivation. If the basic service list subscribed by the user changes, and a certain subscription service is cancelled, and the service has an activation setting, the activation related to the changed service is invalid, that is, the network-initiated deactivation is caused. If the decision does not result in a deactivation operation, then no further steps are required. Otherwise, gsmSCF deletes the activation record that meets the condition locally and performs the subsequent steps in sequence.

4-5. If all UE-related activation records have been deleted, the gsmSCF needs to unsubscribe from the HSS. Otherwise skip these two steps and follow the next steps in sequence.

6-8. The gsmSCF sends a deactivation notification to the UE through the HSS and the MSC/VLR.

9-11. After receiving the notification, the UE returns a response message according to the original path.

Method Embodiment 6: The CS domain terminal actively goes to the registration process. See Figure 14 for the following steps:

1. The circuit domain terminal sends a registration request through the USSD, which includes: IMSI, MSISDN, registration type, AccessLevel. The last item is an optional parameter.

2. The request is routed to the MSC/VLR. The MSC/VLR transparently transmits the parameters to the HSS by determining the parameters in the USSD.

4. The gsmSCF determines whether the UE has joined the PN according to the locally saved record. If it has already joined, the subsequent steps are performed in sequence, otherwise the registration failure response is returned. 5. The gsmSCF sends a request to the HSS, requesting to delete the unique identifier PN-ID identifying the UE to join the PN in the HSS, which can be implemented by setting the value of the PN-ID to Null.

6. The HSS checks whether the IMSI or MSISDN already has a PN-ID record. If it is set to Null, it indicates that the UE has registered from the PN.

7. The HSS returns a delete identity response to the gsmSCF.

8. The gsmSCF deletes all UE records locally, including registration records and activation records.

Note: Going to registration will result in deactivation.

9. The gsmSCF cancels the subscription identifier to the HSS, and indicates that the gsmSCF does not need to be notified when the UE subscription service or the attachment status of the UE changes.

10. The HSS returns an unsubscribe identity response to the gsmSCF.

11-13. The gsmSCF returns the registration response to the UE hop by hop through the HSS and the MSC/VLR.

Method Embodiment 7: The CS domain terminal actively deactivates the process. See Figure 15 for the following steps:

1~2. CS domain PNM UE1 sends a USSD request to the HSS through the VMSC/VLR to query the current configuration information. The request carries the MSISDN to be queried.

7. The circuit domain terminal sends a deactivation request through the USSD. The request includes IMSI, MSISDN, deactivation type, and optionally includes the service code and priority parameter that you want to deactivate.

8. The request is routed to the MSC/VLR. The MSC/VLR transparently transmits the parameters to the HSS by judging the parameters in the USSD.

10. The gsmSCF determines whether there is an activation record that matches the parameter carried in the deactivation request according to the locally saved activation record, and if so, performs the subsequent steps in sequence, otherwise directly returns the deactivation loss. Responsive.

11. The gsmSCF unsubscribes from the HSS to indicate that the UE subscription service or the attached status of the UE changes, and the gsmSCF does not need to be notified.

12. The HSS returns an unsubscribe identity response to the gsmSCF.

Note: Steps 11 and 12 are optional steps. Steps 11 and 12 are performed when all activation records indicated by the UE, that is, the MSISDN number are deleted. Otherwise, the subsequent steps are skipped.

13-15. The gsmSCF returns the activation response to the UE hop by hop through the HSS and the MSC/VLR.

The above steps 1~6 are user query activation configuration operations, which is an optional operation before initiating the deactivation request. The user can perform the query configuration at any time, not limited to deactivating the request.

The activation scheme of the personal network management circuit domain terminal in the embodiment of the present invention discloses a process of activating a user equipment UE registered to the personal network PN in the PNM service. And the registration scheme of the personal network management circuit domain terminal of the embodiment of the present invention discloses a process of interacting with the PNM service related data between the PNM server and the HSS. This meets the needs of PNM services and users.

Further, after the activation operation is completed, the PNM server transmits the subscription identifier for the attachment status information and/or the user subscription list by extending the MAP message, so that the subscription and notification mechanism can further satisfy the management and correspondence of the PNM service subscription data. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A method for activating a personal network management circuit domain terminal, comprising the steps of: personal network management: the PNM server receives an activation request sent by the circuit domain terminal and carrying an activation configuration;

The PNM server authenticates the activation authority of the circuit domain terminal, and authenticates the activation configuration;

The PNM server saves the activation configuration when both authentications are passed to complete the activation operation.

2. The method according to claim 1, wherein the activation configuration carried in the activation request received by the PNM server explicitly indicates an activation type; or: carrying the parameter in the activation configuration to implicitly Indicates the type of activation.

3. The method of claim 1, wherein the PNM server determines that the circuit domain terminal registered in the personal network PN has activation authority.

4. The method according to claim 1, wherein before the PNM server receives the activation request sent by the circuit domain terminal, the method includes the following steps:

The circuit domain terminal sends a registration request to the PNM server requesting to join a PN; and after receiving the registration request, the PNM server inserts a request with the circuit domain terminal to join the HSS terminal.

The PN flag corresponding to the PN indicates that the circuit domain terminal is registered to the PN, and indicates that the circuit domain terminal cannot register to other PNs before the PN removal registration.

5. The method according to claim 4, wherein, when the PNM server receives the invitation registration request before the circuit domain terminal initiates the activation request, the PNM server registers with the circuit domain terminal that initiated the invitation registration request to the PN. Internally determining whether the circuit domain terminal has an invitation authority; when it is determined that the invitation authority is available, the PNM server forwards the invitation registration request to the invited circuit domain terminal;

After receiving the request, the invited circuit domain terminal actively initiates a registration request to the PNM server according to the user's wishes.

6. The method of claim 5, wherein the PNM server sends the invited electricity After the domain terminal forwards the invitation registration request, the timer is started. When the circuit domain terminal invited in the preset time does not actively initiate the registration request, it is determined that the invitation registration fails.

The method according to claim 1, wherein the activation configuration carried by the activation request received by the PNM server simultaneously matches the subscription service of the circuit domain terminal and the terminal capability of the circuit domain terminal, and the PNM server It is determined that the activation configuration authentication is passed.

8. The method of claim 7, wherein after determining that the activation authority has been activated, the PNM server authenticates the activation configuration, comprising the steps of:

The PNM server queries the HSS for the subscription service corresponding to the MSISDN number carried in the activation request, and the PNM server determines that the queried subscription service includes the service code in the activation configuration, and the activation configuration matches the subscription service of the circuit domain terminal;

The PNM server determines that the terminal capabilities of the circuit domain terminal are capable of satisfying the capabilities required by the service or medium included in the activation configuration, and the activation configuration matches the terminal capabilities of the circuit domain terminal.

The method according to claim 8, wherein the service code in the activation configuration carried by the activation request received by the PNM server is empty,

The PNM server uses the subscription service code corresponding to the MSISDN carried in the activation request as the service code in the activation configuration, and determines that the activation configuration matches the subscription service of the circuit domain terminal;

The PNM server determines that the terminal capability of the circuit domain terminal can meet the capability required by the subscription service or the media corresponding to the MSISDN, and the activation configuration matches the terminal capability of the circuit domain terminal.

10. The method according to claim 1, wherein the PNM server receives an invitation activation request directed to the third-party circuit domain terminal before the circuit domain terminal initiates the activation request, and the PNM server initiates the invitation activation request circuit domain terminal. Whether it has been registered in the PN to determine whether the circuit domain terminal has activation authority;

When it is determined that the activation authority is available, the PNM server forwards the invitation activation request to the invited circuit domain terminal;

After receiving the request, the invited circuit domain terminal initiates a master to the PNM server according to the user's wishes. Activated.

The method according to claim 10, wherein after the PNM server forwards the invitation activation request to the invited circuit domain terminal, the timer is started, and the circuit domain terminal invited in the preset time does not initiate active activation. At the time, it is determined that the invitation activation failed.

The method according to any one of claims 1 to 11, wherein the PNM server saves the activation record to complete the activation operation of the circuit domain terminal, comprising the following steps:

The PNM server sends a subscription request to the HSS;

After receiving the subscription request sent by the PNM server, the HSS sets a subscription identifier for the subscription service list and/or the attachment status of the MSISDN number carried in the activation request according to the indication.

13. The method according to claim 12, wherein when the attachment state of the circuit domain terminal changes, the HSS notifies the PNM server:

The PNM service determines that the received notification indicates that the circuit domain terminal is changed from the attached state to the separated state, and initiates a deactivation operation for the activation configuration associated with the circuit domain terminal.

14. The method according to claim 12, wherein, when the subscription service list of the circuit domain terminal changes, the HSS notifies the PNM server;

The PNM server determines that the received notification indicates that the subscription service in the circuit domain terminal subscription service list changes from the subscription status to the unsigned status, and performs a deactivation operation on the activation configuration related to the subscription service.

The method according to any one of claims 1 to 11, wherein before the PNM server receives the activation request sent by the circuit domain terminal, the method includes the following steps:

The circuit domain terminal initiates an activation query request to the PNM server, where the MSISDN number of the circuit domain terminal is carried;

The PNM server obtains the MSISDN number carried in the activation query request, and queries the activation record corresponding to the MSISDN number from the locally saved activation record;

The PNM server returns the queried activation configuration information to the circuit domain terminal.

16. A PNM server, comprising:

An activation request receiving unit, configured to receive an activation request sent by the circuit domain terminal; An authentication unit, configured to: after the activation request receiving unit receives the activation request sent by the circuit domain terminal, authenticate the activation authority of the circuit domain terminal, and authenticate the activation configuration carried in the activation request;

And an activation unit, configured to: when the authentication unit confirms that the two authentications are all passed, save the activation configuration to complete the activation operation.

The PNM server according to claim 16, wherein the authentication unit includes the following subunits:

An activation authority sub-unit is configured to determine that the circuit domain terminal has an activation right when confirming that the circuit domain terminal has been registered in the personal network PN;

The activation configuration sub-unit is configured to determine that the activation configuration authentication is passed when the activation configuration is confirmed to match the subscription service of the circuit domain terminal and the terminal capability of the circuit domain terminal.

The PNM server according to claim 16, further comprising: a registration request receiving unit, configured to receive a registration request sent by the circuit domain terminal to join a PN;

The PNM server according to claim 16, further comprising: an activation query request receiving unit, configured to receive an activation query request sent by the circuit domain terminal; and a query unit, configured to acquire the activation query request The MSISDN number, and the activation configuration information corresponding to the MSISDN number is queried from the activation configuration saved by the activation unit, and the queried activation configuration information is returned to the circuit domain terminal.

20. A home subscription register, comprising: a PN identifier holding unit, configured to store a PN identifier inserted by the PNM server, and an association relationship between the PN identifier and a corresponding PN.

21. The home subscription register of claim 20, further comprising: a subscription request receiving unit, configured to receive a subscription request sent by the PNM server, and a setting unit, configured to: after the subscription request receiving unit receives the subscription request sent by the PNM server, according to the indication, carry the subscription request The subscription service list and/or the attachment status of the MSISDN number set the subscription identifier.

22. A method for registering a terminal of a personal network management circuit domain, comprising: the following steps:

The PNM server receives a request from the circuit domain terminal to join a PN registration request; and the PNM server inserts a PN identifier corresponding to the PN that the circuit domain terminal requests to join to the HSS to indicate that the circuit domain terminal registers with the PN, and indicates The circuit domain terminal cannot register to other PNs before the PN removal registration.

The method according to claim 22, wherein, when the PNM server receives the invitation registration request, the PNM server determines whether the circuit domain terminal is determined by whether the circuit domain terminal that initiated the invitation registration request has been registered in the PN. Have invitation rights;

When the PNM server determines that there is an invitation authority, it forwards the invitation registration request to the invited circuit domain terminal; after receiving the request, the invited circuit domain terminal actively initiates a registration request to the PNM server according to the user's intention.

The method according to claim 23, wherein after the PNM server forwards the invitation registration request to the invited circuit domain terminal, the timer is started, and the circuit domain terminal that is invited within the preset time does not take the initiative. When the registration request is initiated, it is determined that the invitation registration has failed.

25. A PNM server, comprising:

a registration request receiving unit, configured to receive a registration request sent by the circuit domain terminal to join a PN;