WO2008151563A1

WO2008151563A1 - Method and apparatus for realizing private network services in pnm

Info

Publication number: WO2008151563A1
Application number: PCT/CN2008/071239
Authority: WO
Inventors: Dongming Zhu; Xiaoyan He; Shuang Liang; Li Wen
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-06-13
Filing date: 2008-06-06
Publication date: 2008-12-18
Also published as: CN101325508B; CN101325508A

Abstract

A method and apparatus for realizing private network services in PNM are provided to obtain hierarchical accessing for privacy services. The method comprises the following steps: a PNM server matches the information contained in the received service request message with private network service configuration information of the callee UE; the PNM server looks up service logic strategy with the matching result,and then performs the service logic according to the finding out. Another method and apparatus for realizing private network services in PNM are also provided to obtain different experience for the callee UE when connecting different types of messages. The another method comprises the following steps: a PNM server receives the service request message from the caller UE and verifies that the caller is not in the access list; the PNM server matches the information contained in the received service request message with service logic strategy; the PNM server performs the service logic according to the matching result.

Description

Method and device for realizing private network management private network service

The present invention relates to the field of communications, and in particular, to a method and apparatus for implementing a personal network management private network service. Background technique

A new service, the Personal Network Management PNM service, was introduced in the R7 version of 3GPP. This service is aimed at a scenario in which a subscriber in a future network may have multiple terminal devices. These terminal devices constitute a personal network of subscribers, called PN (Personal Network), and centralized management for Ϊ>Ν is PNM.

The current PNM architecture of the IMS domain and the CS domain are shown in Figure 〖 and Figure 2, respectively.

See 罔 1. In the IMS domain, the HSS and the PNM AS have a Sh interface, which can directly interact with each other to obtain corresponding user configuration and control information. The PNM AS has an ISC interface with the S-CSCF, which can directly interact with each other; obtain relevant information of 1^, and redirect the service request to the PNM AS. The UE has a Ut interface with the PNM AS, which can directly interact with some notification and configuration information.

As shown in Figure 2, in the CS domain, the HSS has an interface with the gsmSCF and the GMSC, and can directly interact through the MAP. The VMSC has an interface with the GMSC, and can directly interact through the LSAP interface. The gsmSCF. interacts with the UE through its network element. , . . . may pass the USSD information carrier information, if the gsmSCF and PNM AS are combined, the Ut interface can also be interacted.

The so-called private network is to control the access of the UE to the UE outside the PN by setting the access rights of some UEs in the PN to Private or Public. For UEs whose access rights are set to Public, they can be accessed by any UE. For a UE whose access right is set to Private, it means that the UE can be accessed by UEs in the PN, and access to the UE outside the PN is restricted. At present, only the specific implementation of the PN external UE access restriction is given (the JE sets the guest UE list mode, that is, the PN outside the UE in the guest UE list can access the U E.

1

Replacement page (Article 26) During the process of the invention, the inventor found that when the UE access access authority outside the PN is set to Private UE in the private network service, the definition of access restriction is relatively simple, and no specific access level is given. At the same time, when the existing method determines whether the user is neither the PN UE nor the Guest UE to connect to the called user, the different experiences of the called user for connecting different types of messages are not considered. Users want different experiences for different businesses. Send content

The embodiment of the invention provides a method and a device for implementing a personal network to manage a private network service, so that the private network service has a rich access level.

The embodiment of the present invention further provides another method and device for implementing a personal network management private network service, so that the called user experiences different experiences in the process of connecting different types of messages.

The method for managing the private network service of the current network in the embodiment of the present invention includes: 个人¹ ] the personal network management PNM server matches the information carried in the received service request message with the private network service configuration information of the called UE. And the PNM server performs the business logic with the matching result against the business logic policy and the business logic policy obtained by the comparison.

A PNM server according to an embodiment of the present invention includes: a first saving unit, configured to save private network service configuration information of the UE; and a receiving and extracting unit, configured to extract information from the received service request message; ^ "Receives the information of the 3⁄4 single first ^ The first saves the private network service configuration information of the called UE saved by the car ψ, and outputs the matching result; the execution unit is used to match the output of the matching unit The business logic is executed against the business logic strategy and the business logic strategy derived from the comparison.

Another method for implementing a personal network management private network service according to an embodiment of the present invention includes the following steps: The personal network management PNM server receives a service request message sent by a calling user, and determines that the calling user is not in the called UE. In the access list; the PNM server matches the information carried in the received service request message with the business logic policy; and the PNM server performs the matching service

2

Replacement page (Article 26) Series.

Another PNM server of the embodiment of the present invention includes a receiving unit, configured to receive a service request message sent by a calling user, and a determining unit, configured to determine whether the calling user is in an access list of the called UE, and When the calling user is not in the access list of the called UE, the triggering signal is sent; the matching unit is configured to: when receiving the trigger signal sent by the determining unit, the information and the service carried in the service request message received by the receiving unit The logic strategy performs matching, and outputs the matching business logic; the execution unit is configured to execute the matching business logic of the matching unit output.

In a solution of the embodiment of the present invention, the PNM server is extended to determine whether the calling user accesses the restricted element (ie, the private network service configuration information). When the PNM. server receives the service request message, it matches the information carried in the received service request message with the private network service configuration information of the called UE; and performs the corresponding service logic according to the matching result and the business logic policy. This allows for more flexible control of the caller's access.

In another solution in the embodiment of the present invention, after the PNM server receives the service request message sent by the calling user and determines that the calling user is not in the access list of the called UE, the PN server will receive The information carried in the service request message is matched with the business logic policy, and the corresponding operation is performed according to the matching result, so the called user experiences different experiences in the process of connecting different types of messages. DRAWINGS

Figure 1. Schematic diagram of the PNM architecture of the existing IMS domain;

2 is a schematic diagram of a PNM architecture of an existing CS domain;

3 is a flowchart of a method for implementing a PNM private network service according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of a PNM server according to an embodiment of the present invention;

FIG. 5 is a flowchart of another method for implementing a PNM private network service according to an embodiment of the present invention; FIG. 6 is a schematic structural diagram of another PNM server according to an embodiment of the present invention;

Figure 7 is a flowchart of Embodiment 1 of the present invention;

3

Replacement page (Article 26) Figure 8 is a flowchart of Embodiment 2 of the present invention;

Figure 9 is a flowchart of Embodiment 3 of the present invention;

Figure 10 is a flowchart of Embodiment 4 of the present invention;

1 is a flowchart of Embodiment 5 of the present invention;

FIG. 12 is a flowchart of Embodiment 6 of the present invention; FIG.

Figure 13 is a flowchart of Embodiment 7 of the present invention;

Figure 14 is a flow chart of Embodiment 8 of the present invention. detailed description

In order to make the private network business have a rich level of access.

The embodiment of the present invention provides a method for implementing a PNM private network service. Referring to FIG. 3, the following main steps are included:

- : The server will match the information carried in the received service request message with the called ό private network service configuration information.

The premise of this step is that the private network service configuration information of the called UE is pre-stored in the server. The specific save process is as follows: The server receives the private network service configuration request sent by the UE; Configure the parameters related to the private network service. Save the parameters as the private network service configuration information of the UE.

The private network service configuration information includes at least the following elements: ^ a service code, a media type, and a message type. For example, the private network service configuration information includes a service code (including one element); for example, the private network service configuration information includes two media types (including two elements); for example: private network service configuration information Includes a service code, two media types, and a message type (that is, four elements). Further, each element included in the private network service configuration information is identified by an allowed symbol or a forbidden symbol (also in a default manner, for example, if there is no symbol, it is considered as an allowed symbol).

Since the embodiment of the present invention gives more elements, it is necessary to provide a rich access layer.

4

Replacement page (Article 26) Set the foundation.

This step contains three matching strategies:

Matching policy 1. The calling party that initiates the service does not consider whether the information carried in the service request message matches the private network service configuration information of the called UE in the access list (the guest list) of the called party. According to the definition of Private and Public, this policy is valid for the access rights of the called UE, Private or Public.

Matching policy 2: Before the PNM server matches the information carried in the service request message with the private network service configuration information of the called UE, the following conditions are met: The PNM server determines to initiate - the called user of the service is in the called UE. In the access list. That is, according to the definitions of Private and Public, when the calling user is in the access list of the called UE, the matching of the private network service configuration information needs to be further performed, thereby providing more access restrictions, so correspondingly increasing the level of access "matching strategy 3, PNM server fans the service configuration information into the private network service request message carries the information of the called UE ^{^:} Chicago horses before V 'need to satisfy the following condition: the PNM server

The calling user of the service is not in the access list of the called UE. That is, according to the definition of Private and Public, when the calling user is in the access list of the called UE, the calling user can normally access the called UE; when the calling user is not in the access list of the called UE, The access is directly denied, but the matching of the configuration information of the private network service is performed. If the matching is successful, the calling user can access the called L) E according to a specific service access mode (for example, a specific media type). This will satisfy some users who want to

The P external UE accesses unrestricted requirements in a specific service access manner.

The S12 PNM server compares the results against the business logic policy and performs the business logic with the comparison of the business logic policies.

The PNM server performs the business logic according to the business logic policy, including but not limited to the following cases, or any combination of the following:

The information carried in the service request message includes at least one of the following elements: a service code, a media type, and a message type; and the matching result is any element in the information carried by the service request message. The element identified as prohibited in the private network service configuration information of the called UE

5

Replacement page (Article 26) If the element is the same, or the element carried in the service request message is different from the element identified in the private network service configuration information of the called UE, the PNM server directly returns the service logic policy obtained by the comparison. The service establishment failed response.

The information carried in the service request message includes: a media type; the matching result is that the media type in the information carried in the service request message and the private network service configuration information of the called UE are prohibited. A media type is the same, or the media type in the information carried in the service request message and any media type identified as allowed in the private network service configuration information of the called UE. Both are, and then PJMM J3⁄43⁄4i"i recorded The outgoing business logic policy replaces the called UE. The media is re-negotiated with the calling party that initiated the service. This can effectively complete the access access, and the user can call the user^ for a better experience.

Case 3, the service request message carries information including at least one of the following elements: a service code, a medium type, a message type; the matching result of the service request ^message; ⁵ it ': the information Any element in the private network service configuration information of the called UE is the same as the element identified as forbidden, or any element in the information carried in the service request message and the private network service configuration information of the called UE are identified as If the allowed elements are different, the PNM server replaces the calling user that initiated the service with the service logic policy obtained by the comparison, and dynamically requests the access authority to the default UE set in the PN. This can effectively complete access access and bring a better experience to the calling user.

Case 4: The information carried in the service request message includes at least one of the following elements: a • service code, 'media message ^: class 3⁄41', and any element in the information carried by the service and the called party If the element identified in the private network service configuration information of the UE is the same as the forbidden element, or any element in the information carried in the service request message is different from the element identified in the private network service configuration information of the called UE, The PNM server adds the "identity information" of the called UE to the service request message in a comparison with the derived service logic policy, and continues to route the message. Specifically, if the service request message is a SIP message, the Reject-Contact header field may be added to the service request message, and the unique identifier information of the called UE is filled in the header field. Make a decision to reject or accept, so as to better solve the same problem of IMS domain

6

Replacement page (Article 26) In the case of a different UE Share IMPU of the user, the UE that does not have the private network service cannot be accessed.

The present embodiment also proposes a UI server, as shown in FIG. 4, which includes: a first saving unit, a receiving extracting unit, a matching unit, and an executing unit.

And a first saving unit, configured to save private network service configuration information of the UE; and the following elements: at least one code, at least one media type, and/or at least one message type.

a receiving and extracting unit, configured to extract information from the received service request message;

Matching element designed manually extracting the received information and the second single extraction matchmaker - a saving unit to save _cattle: Spear network service called UE configuration information match, and outputs a matching result;.

The execution smuggling is used to compare the business logic strategy according to the matching result output by the matching unit, and execute the business logic with the comparison business logic strategy.

Further, the PNM server may further include: a second saving unit and a triggering unit.

The ^ memory element is used to save the user's visit: ;.

a triggering unit, configured to determine, when the calling user of the initiating service is in the access list of the called UE, trigger a matching unit (corresponding to the matching policy 2, that is, according to the definitions of Private and Public, the policy is when the calling user is called When the UE accesses the list, it is necessary to further perform the private network service configuration information or determine that the calling user of the originating service is not in the called access list, and trigger the matching unit (corresponding to the matching policy 3, that is, according to Private and Definition of Public, this policy When the calling user is in the access list of the called U, the calling user can normally access the called UE; 'When the calling party is not in the access list of the called UE, it does not directly reject The access, but the matching of the private network service configuration message, if the matching is successful, the calling user can access the called UE according to a specific service access mode (such as: a specific media type).

Another embodiment of the present invention also proposes a spear method for implementing a private network management private network service, as shown in FIG.

The S2K PNM server receives the service request message sent by the calling user, and determines that the calling user is not in the access list of the called UE. Replacement page (Article 26) 522. The PNM server compares the information carried in the received service request message with the business logic policy,

The information carried in the service request message includes: the message type is further in the SIP message of the IMS domain, and the message types used to establish the service include: INVFTE, MESSAGE. OPTION, REFER, etc., wherein the message type is MESSAGE and OPTION, No user involvement is required in the process of establishing a business.

The result of the matching is that the called user needs to participate in the process of successfully establishing the service by the message type; or the called user does not need to participate in the process of successfully establishing the service by the message type-type.

523. The PNM server performs matching matching business logic.

The matching results and operations performed by the PNM server, including but not limited to:

The matching result is that the called user needs to participate in the process of successfully establishing the service by the message type, and the operation performed by the PNM server according to the matching result is: direct return-back service establishment failure response; or the calling user of the PNM service service, to the PN The internal Κυέ Κυέ dynamically requests access rights; or adds the unique identification information of the called UE to the service request message, and continues to route the message.

If the matching result is that the called user does not need to participate in the process of successfully establishing the service by the message type, the server performs a normal service establishment process.

Another embodiment of the present invention is also provided. Referring to FIG. 6, the method includes: a receiving unit, a determining unit, a matching unit, and an executing unit.

a receiving unit, configured to receive a service request message sent by the calling user;

a determining unit, configured to determine whether the calling user is in an access list of the called UE, and issue a trigger signal when determining that the calling user is not in the access list of the called UE;

The matching vehicle element is configured to: when receiving the trigger signal sent by the determining unit, match the information carried in the service request message received by the receiving unit with the service logic policy, and output the matching business logic;

Execution unit, the business logic used to perform the matching of the output of the matching unit

8

Replacement page (Article 26) Embodiment 1 The IMS domain terminal configures a private network service process. As shown in Figure 7, the following steps are included:

1. The PNM UE1 sends a private network service configuration request, which includes: an IMPU (one or more) of the PNM UE1, access rights information (Public or Private) of the PNM UE 1, and one or more service codes, one or Multiple media type information, and/or one or more SIP message types. Further, if the access right information is private, the request may further carry one or more guest UE lists composed of 1MPUs.

The NAF requests the PNM for the sending disk. The authentication of the UEL is authenticated by ^--request. $Plus:, the IMPI of the requesting UE (ie, the IMPI of the PNM UE1) is sent, and the request is forwarded to the PNM. AS. . .

2. The PNM AS checks the status of the PNM UE 1 according to the IMP1 and/or IMPU of the PNM UE1 in the request, that is, determines whether the PNM UE1 has used its IMPI and/or MPU to join the PN, for example, if the PNM UE1 does not join the PN, If the configuration fails, the configuration fails. Otherwise, go to the next step.

Note: If the user registration is considered to mean that the user has joined the PN, then it is necessary to check whether the PNM UE1 has signed the PN service.

3. The PNM AS saves the access rights of the user in the private network service configuration request, and extracts parameters related to the private network service configuration (one or more service codes, one or more media type information, from the network service configuration request, And / or one or more siP message types), and this parameter is recommended as a service and information. In the case where the guest UE list is carried, the guest UE list is stored in association with the PNM UE1 (the guest UE list is not included in the private network service configuration information of the PNM UE1).

4. If the access right of the PNM UE 1 in the request is Private and the request carries the Guest UE list, the PNM AS separately sends a notification to each Guest UE in the list (for example, U E2 in FIG. 7) to notify these The UE is set as the Guest UE of the PNM UE1

Note: In step 4, the PNM AS notifies the Guest UE in many ways, not limited to the following: 1. The PNM AS uses the SIP MESSAGE message to inform the Guest UE; 2. The PNM AS makes

9

Replacement page (Article 26) The Guest UE is informed by the Push method in the 〇MA; 3. Other similar message notification modes.

Note: Step 4 is an optional step. If some predetermined policies decide not to notify the Guest UE, it will not affect the subsequent process.

5. The P M AS returns a response to the requesting PNM UE1, which contains the result of the operation.

Note: After that, the PNM UE1's modification to the private network service configuration, such as: service code, message type, media type, etc., is similar to the above process. The difference is that the parameters passed will change accordingly, and will not be described here.

Embodiment 2, CS domain terminal configuration. Private network. Business process See FIG. 8 , including the following - column steps: .

1~3. PNM UE1 sends a private network service configuration request, which includes: MS1SDN number of PNM UE1 and 1M.S1, access rights information (Public or Private) of PNM UE1, to one or more service codes. Further, if the access permission information is Private, the request may also carry a list of Guest UEs composed of multiple MSISDN numbers.

Here, the USSD method is used to send a request to the gsmSCF responsible for the PNM service through the MSC VLR and HSS of the PNM UE1.

4. The gsmSCF saves the access rights of the user in the private network service configuration request, and extracts parameters (one or more service codes) related to the configuration of the private network service from the private network service configuration request, and uses the parameter as the PNM UE1. The private network service configuration information is saved. Further, if the private network service configuration request further includes a guest UE list, the Ouest UE list is saved in association with the PNM UE1 (the guest UE list is not included in the private network service configuration information of the PNM UE1).

5. If the access permission of the PNM UE1 in the request is Private, and the request carries the Guest UE list, each Guest UE in the list (for example, UE2 in FIG. 8) respectively sends a notification to notify these UEs that Set to the Guest UE of PNM UE1

Note: In step 5, there are many ways for the gsmSCF to notify the Guest UE. It is recommended to notify the Guest UE by means of USSD. However, it is not limited to this method, and other similar messages can be used.

10

Replacement page (Article 26) Note: Step 5 is an optional step. If the predetermined policy decides not to notify the Guest UE, it will not affect the subsequent process.

6~8. The gsmSCF returns a response to the PNM UE1 that initiated the request by the HSS, MSC/VLR hop by hop, including the operation result.

Note: After that, the PNM UE1's modification of the private network service configuration (modification of the service code) is similar to the above process. The difference is that the parameters passed will change accordingly, and will not be described here.

If there are both IMS users and CS domain users in a network, allowing one IMS user to set other CS domain users as Guest UEs, and vice versa, the Guest UE list can also be a combination of an IMPU and an MSISDN number. List, setting and notification mode The above two embodiments have been included and will not be described again.

Embodiment 3: The private UE that is called the CS domain performs the calling identity verification directly according to the private network service configuration information of the UE in the CS domain. Here is the case where gsmSCF (responsible for PNM service) directly returns the failure response. The car is shown in Figure 9, including the following steps.

1. The called GMSC receives the ίΑΜ request sent by the calling side, and the request carries the service code 1;

2. The GMSC sends a route query request message to the called HSS;

3. The HSS returns a route query response, which includes the called side smart subscription information T_CS, wherein the called user subscribes to the PNM service, and includes the address information of the gsmSCF responsible for the PNM service;

4. The called GMSC triggers the gsmSCF to implement the PNM service according to the T-CSI;

5. The gsmCSF verifies the calling identity according to the calling PNM service logic, and finds that the service code 1 is in the forbidden service code list configured by the called UE, and directly determines that the called party does not allow the calling party to access; 6-7. gsmSCF hop by hop Return the Release message to the calling side to release the call.

Embodiment 4: The called UE is a Private UE in the IMS domain, and when the calling party is authenticated, the calling party is determined to be the guest UE of the IMS domain UE, and further determined according to the private network service configuration information of the UE in the IMS domain. Eventually the PNM AS returns a failure response. See Figure 10, package

11

Replacement page (Article 26) Including the following steps: 3⁄4:

1. The called S-CSCF receives the INVITE service setup request, which carries the service code, media type, and message type.

2. The S-CSCF detects a match to the PNM iFC trigger rule.

3. The S-CSCF forwards the request to the PNM AS based on the iFC.

4. The PNM AS finds that the access rights information of the called party is Private. The PNM AS first determines that the calling party is in the called Guest UE list; further the PNM AS will carry the service code, the media type and the message type carried in the request, the prohibited service code set by the called party, the prohibited media type, and the forbidden message type. If there is any match, it is considered that the calling user does not have the right to establish the session (other matching rules may be used, not limited to this), and the subsequent steps are performed. Otherwise the session is allowed to continue to be established.

5~6. The PNM AS sets the default UE to the called user PN to dynamically request access rights for the calling user.

7. The called 妁 Default UE' (the default UE set in ^) determines the allowable to call service establishment request.

8~9. The Default UE returns a query response to the PNM AS according to the original path.

10. The PNM AS allows the business to continue to be established based on the information carried in the response.

11-13. Perform a normal service establishment process to establish a service between the called UE1 and the calling user.

Embodiment 5: The Feature Tag method is an extension of the SIP mechanism. Some features of the IJE are described by adding some expressiveness in the Contact header field in the SIP message or a parameter set described for the UE's own characteristics, such as receiving video capabilities, supporting mobility, and the like. When registering, the UE reports these parameters to the network and stores them by the S-CSCF that provides services. In the process of service establishment, the caller adds a new header field Accept-Contact, Reject through the SIP message. -Contact, the parameters carried in the Request-Disposition, to express the called terminal that wishes or rejects the connection, or express the way the desired network entity processes the message. For example, if you want the session establishment request to be forking, etc. 3GPP in the IMS architecture Registration and meeting

12

Replacement page (Article 26) The foregoing extension mode is introduced in the session establishment process to implement the capability reporting of the UE and express the calling preference, thereby achieving the purpose of selecting the most suitable UE connection according to the needs of the user.

In this embodiment, the called UE1 is a Private UE in the IMS domain. When performing the identity verification of the calling party, it is first determined that the calling party is not the Guest UE of the IMS domain UE, but the access UE is not denied. Further, according to the private network of the IMS domain UE The service configuration information is judged again, and finally the PNM AS adds the Reject-Contact header ^^ mode control. See Figure 11, which includes the following steps:

1. The called S-CSCF receives the INVITE service establishment request, which carries the service code media type and message type.

4. The PNM AS finds that the called access rights information is Private PNM AS first determines that the calling party is not in the called Guest UE list; further, the PNM AS will carry the service code, media type or cancellation type and called number carried in the request. The set 'Allow Service Code ¥ 'Allows the media type and the allowed message class. Type to match ^", if they are different, the PNM AS adds a Reject-Contact header field that expresses the preference in the service request message (other matches can also be used) The rule, not limited to this, fills in the Feature tag carried in the Contact header field when the called UE1 registers.

In this step, after the called UE1 is registered, the called user is provided with a service. The S-CSCF registers with the PNM AS by using a publicly-known third-party registration mechanism, and then the PNM AS obtains the Feature tag of the UE1 by registering the event packet. The feature tag 3⁄4 can be the instance id of UE1, or other information that can be uniquely determined to UE1.

5. The PNM AS sends the modified service setup request message to the S-CSCF, and the S-CSCF determines that it does not wish to connect to the UE1 according to the Re"ect-Contact header field carried in the request. If there are other connectable UEs in the IMPU corresponding to the UEI, and it is assumed to be UE2, the subsequent steps are performed. Otherwise, the called S-CSCF returns 403 Forbidden response hop by hop to the calling side.

6. S-CSCF finds that there is a splicable shared shared (so-shared one 1MPU is multiple

UE sharing, associated with multiple IMPIs) UE2 of the iMPU, then contiguous UE2,. Replacement page (Rule 26) 7~8. Perform a normal business establishment process.

Embodiment 6: The called UE1 is a Private UE of the IMS domain, and the PNM AS is controlled by the B2BUA method. As shown in FIG. 2, the following steps are included:

3. The S-CSCF forwards the request to the PNM AS based on the iFC.

4...PNM AS finds that the access permission value of the called party is -Private. The PN AS first judges that the calling party is not in the called UE list of the called party; further the PNM AS matches the media type carried in the request with the prohibited media type set by the called party, when the media carried in the request If the type is one of the forbidden media types, the subsequent steps are performed, otherwise the service establishment process is performed normally. '

5. PNM. AS adopts the B2BUA method in SIP messages instead of the called user and the calling side to conduct media chats.

6. After the media renegotiation process is completed, the PNM AS sends a service setup request to the called S-CSCF.

7. The S-CSCF routes the request to the called UE1.

8. Perform the normal SIP service establishment process.

Embodiment 7: The PNM AS is deployed only in the IMS domain, and the called party is a Private UE in the CS domain.

Since the CS domain is the old network, when the new network is deployed, it is possible to consider only the PNM AS in the IMS domain, and consider the compatibility with the CS domain terminal. Therefore, the implementation of deploying the PNM AS only in the IMS domain is introduced. The PNM AS is only deployed in the IMS domain. It means that a PNM AS is set up in the IMS domain, and both the CS domain and the [MS domain terminal service. In this mode, the process of configuring the private network service between the MS terminal and the CS domain terminal is similar to the process of deploying the PNM AS in the two domains respectively. Under the conditions described in Embodiment 3, only the route routed to the PNM AS is slightly different. See Figure 13, which includes the following steps:

1. The calling side sends a session establishment request Invite to the called MGCF. Which carries the service code replacement page (Article 26) Lo

2. The MGCF converts the SIP message into an ISUP message and sends it to the called GMSC.

3. The GMSC sends a Route Query Request message SRI to the called HSS.

The HSS returns a route query response SRI to the GMSC, which includes the called side smart subscription information T-CSI, which indicates that the called user has subscribed to deploy the service only in the IMS domain.

5. The GMSC sends a request message imtialDP to the SDS of the CS domain according to the T_CSI.

6. The SDS of the CS domain sends a service request message to the GSMC to route the request to the IMS.

7. The GMSC sends a Service Request message IAM to the MGCF requesting routing to the IMS domain SDS.

8~10. MGCF is established by the called tCSCF and S"CSCF ^i tongue please go to PNMAS ₀

11. The PNM AS finds that the access authority information of the called UE is Private according to the PNM service logic, and the gsmSCF further verifies the calling identity, and finds that the service code 1 is in the forbidden service code list of the called UE. Then directly determine that the called party does not allow the calling party to access, and perform the subsequent steps, otherwise the session is established normally.

12-15. The PNM AS returns to the calling side 403 Forbidden response hop by hop according to the original path.

If the Connect message in Step 6 is given the public service identity PSI address information of the IMS domain SDS, the session establishment request is routed to the IMS domain, and the SDS needs to be first routed to the IMS domain, and the SDS of the CS domain from the IMS domain SDS. The original called number is restored, and then routed to the called S-CSCF for routing to the PNM AS.

Embodiment 8: The PNM server receives the service request message sent by the calling user, and determines that the calling user is not in the access list of the called UE.

After that, the PNM server matches the message type of the received service request with the business logic policy, and performs the corresponding process according to the matching result. Referring to FIG. 14, the following steps are included: 1. The called S- The CSCF receives the INVITE service setup request.

2. The S-CSCF detects a match to the PNM iFC trigger rule.

3. The S-CSCF forwards the request to the PNM AS based on the iFC.

15

Replacement page (Article 26) 4. The PNM AS 4 determines whether the service needs to be called by the called user according to the message type of the service establishment request, and allows the service establishment request to continue to be established if not required, otherwise directly returns a service establishment failure response.

In the SIP message of the IMS domain, the message types used to establish the service include: INV] TE, MESSAGE, OPTION, REFER, etc., wherein the user does not need to participate in the message type, including but not limited to MESSAGE and OPTION, and the types of messages that the user needs to participate include. But not limited to INVITE, REFERo

5-7. Execute the _ regular J service establishment process. _ς

In summary, the embodiment of the present invention extends the ΡΝΜ server to determine whether the queried user accesses a restricted number of elements (ie, private network service configuration information). When the server receives the service request message, it matches the information carried in the received service request message with the private network service configuration information of the called UE; and performs the corresponding service logic according to the matching result and the business logic policy. This allows for a more controlled control of the caller's access.

Further, the matching policy 1 in the embodiment of the present invention can meet the requirement that some users want to access all UEs in a specific service access manner.

The matching policy 2 in the embodiment of the present invention, when the calling user is in the access list of the called UE, further needs to perform matching of the private network service configuration information, thereby providing a stricter than the prior art. restriction of visit.

The present invention implements the strategy of 3, which satisfies certain needs, and hopes to access all UEs in a specific service access manner.

Further, if the information carried in the service request message includes: a media type, the matching result is that the media type in the information carried in the service request message and the private network service configuration information of the called UE are prohibited. If the media type is the same, or the media type in the information carried in the service request message is different from any media type identified as allowed in the private network service configuration information of the called UE, the called UE may be replaced by the ΡΝΜ server. Media renegotiation with the calling user who initiated the service. This can effectively complete access access and bring a better experience to the calling user.

16

Replacement page (Article 26) If the information carried in the service request message includes the following elements: at least one service code, at least one media type, and/or at least one message type; the matching result is any one of the information carried by the service request message. The element is the same as the element that is identified as being forbidden in the private network service configuration information of the called UE, or any element in the information carried in the service request message and the element identified as allowed in the private network service configuration information of the called UE. If the PNM server is not the same, the PNM server can dynamically apply for access rights to the default UE set in the PN instead of the calling user that initiates the service. This can effectively complete access access and bring a better experience to the calling user.

If the information carried in the service request message includes the following elements: „ at least one service code, at least one media type, − and/or. at least one message type; the matching result is in the information carried by the service request message. Any element of the private network service configuration information of the called UE is the same as the forbidden element, or any element of the information carried by the service request message and the private network service configuration information of the called UE are identified as allowed. The elements are all different, and the unique identification information of the called UE is stunned and continues to route the message. This can make a rejection or acceptance decision on the preference mechanism provided by the ί3⁄43⁄4⁄4, thereby better solving the IMS domain. In the case of a different UE Share IMPU of the same user, there is no problem that the UE that configures the private network service cannot be accessed. Therefore, the embodiments of the present invention provide different implementation schemes based on different policies, and different accesses are given for different types of access. The processing method enables the private network service to have rich access levels and enrich the characteristics of the private network service, and enhances the User experience.

In another solution of the embodiment of the present invention, when the PNM server receives the service request message sent by the calling user and determines that the calling user is not in the access list of the called UE, the PNM server will receive The information carried in the service request message is matched with the business logic policy, and the corresponding operation is performed according to the matching result, so the called user experiences different experiences in the process of connecting different types of messages.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

17

Replacement page (Article 26)

Claims

Rights request

A method for implementing a personal network management private network service, characterized in that the method comprises the following steps:

The personal network management PNM server matches the information carried in the received service request message with the private network service configuration information of the called UE;

The PNM server compares the business logic policy with the matching result, and executes the business logic with the business logic policy obtained by the comparison.

2. The method according to claim 1, characterized in that, before the PNM server matches the information carried in the service request message with the ''private network configuration letter' of the called UE, the PNM server needs to satisfy The following: The PNM server determines that the calling party that initiated the service is in the access list of the called UE.

The method according to claim 1, wherein before the PNM server matches the information carried in the service request message with the private network service configuration information of the called UE, the following conditions are met: PNM server determines The calling user that initiated the service is not in the access list of the called UE.

The method according to any one of claims 1 to 3, characterized in that the private network service configuration information includes at least one of the following elements: a service code, a media type, and a message type. .

The method according to claim 4, wherein the information carried in the service request message includes at least one of the following elements: a service code, a media type, and a message type;

The matching result is that any one of the information carried in the service request message is the same as the element identified as prohibited in the private network service configuration information of the called UE, or any element in the information carried by the service request message. If the elements identified in the private network service configuration information of the called UE are different, the PNM server directly returns to the industry with the business logic strategy obtained by the comparison.

18

Replacement page (Article 26) Establish a failure response.

The method of claim 4, wherein the information carried in the service request message includes: a media type;

The matching result is that the media type in the information carried in the service request message is the same as any media type identified as prohibited in the private network service configuration information of the called UE, or the media in the information carried in the service request message. If the type of the private network service configuration information of the called UE is different from any of the allowed media types, the server replaces the called UE with the service logic policy obtained by the comparison, and performs the calling user that initiates the service. Media weight - negotiation „

7. The method of claim 4, wherein the information carried in the service request message includes at least one of the following elements: a service code, a media type, and a message type;

The matching result is any element and called information in the information carried by the service request message.

' ΌΕ ^ 酒酒^; Confidence: the identifier in the message is the same as the forbidden premise, : any element in the information carried in the service request message and the element identified in the private network service configuration information of the called UE are not allowed. In the same way, the server replaces the calling user that initiated the service with the service logic policy obtained by the comparison, and dynamically requests the access authority to the default UE set in the network.

The matching criterion is any element and called information in the information carried by the service request message.

If the element identified in the private network service configuration information of the UE is the same as the forbidden element, or any element in the information carried in the service request message is different from the element identified in the private network service configuration information of the called UE, The server adds the unique identification information of the called UE to the service request message by using the compared business logic policy, and continues to route the message.

The method according to claim 8, wherein the service request message is an S1P message, and the unique identification information of the called UE is added to the service request message, which is

19

Replacement page (Article 26) A Reject-Contact header field is added to the service request message, and the unique identifier information of the called UE is filled in the header domain.

The method according to claim 1, wherein the private network service configuration information of the called UE is pre-stored in the PNM server, and the saving process includes the following steps: the PNM server receives the UE. Private network service configuration request;

The PN server extracts parameters related to the configuration of the private network service in the request;

The PNM server saves the parameter as the private network service configuration information of the UE.

1 1. A PNM server, comprising:

a first saving unit, configured to save private network service configuration information of the UE;

a matching unit, configured to match the information extracted by the receiving and extracting unit with the private network service configuration information of the called UE saved in the first saving unit, and output a matching result;

Execution Wish: According to the matching result output by the matching unit, the business logic is executed against the business logic strategy.

The server according to claim 11, further comprising:

a second saving unit, configured to save a user's access list;

The triggering unit is configured to: when the calling user that initiates the service is in the access list of the called UE, trigger the matching unit.

13. The server of claim 11H, further comprising:

a second saving unit, configured to save a user's access list;

The triggering unit is configured to trigger the matching unit when the calling user that initiates the service is not in the access list of the called UE.

The server according to any one of claims 11 to 13, wherein the private network service configuration information of the UE saved by the first saving unit includes at least one of the following elements: a service code, a media type, A message type.

15. A method for implementing a personal network management private network service, characterized in that it comprises the following

20

Replacement page (Article 26) step:

The personal network management PNM server receives the service request message sent by the calling user, and determines that the calling user is not in the access list of the called UE;

The PNM server compares the information carried in the received service request message with the business logic policy;

The PNM server performs matching matching business logic.

The method of claim 15, wherein the information carried in the service request message comprises: a message type;

The matching result is that the called user needs to participate in the process of successfully starting the business with the message type, and the PNM server directly returns the service establishment failure response; or the PNM server replaces the calling user that initiated the service, and the setting to the PN is The default UE dynamically requests access rights; or adds the unique identification information of the called UE to the service request message, and continues to route the message:

The method according to claim 16, wherein the matching result is that the PNM server performs a normal service establishment process in the process of successfully establishing a service by using the message type without the called user participating.

18. A PNM server, characterized in that

a determining unit; 3⁄4 in determining whether the calling user is ^called UE: in the question list, and when the determining that the calling user is not in the access list of the called UE, issuing a trigger signal;

a matching unit, configured to: when receiving the trigger signal sent by the determining unit, match the information carried in the service request message received by the receiving unit with the service logic policy, and output the matching service logic;

An execution unit, configured to perform matching of the business logic of the matching unit output.

twenty one

Replacement page (Article 26)