CN100527874C - A data inspection method for private service identification - Google Patents

Abstract

The invention discloses a data inspection method of a private service identification. Including: A. The Home Subscriber Server (HSS) receives the Configuration Server Request (SAR) sent by the Serving Call Control Session Function Module (S-CSCF) and requests to log out of the PSI of the service. The user identification part in the SAR only carries the private service identification ; B. The HSS obtains the value of the server assignment type (Server Assignment Type) cell, and performs subsequent operations according to the value. The present invention provides a data inspection method. In the PSI operation, the SAR request only carries a private service identifier without a public service identifier, checks the value of the ServerAssignment Type parameter in the request, and associates the private service identifier with the private service identifier. The check of the activation state of the public service identification solves the situation that the existing solution does not take into account.

Description

A data inspection method for private service identification

technical field

The invention relates to the communication field, in particular to a data checking method of a private service identifier.

Background technique

Starting from the 3GPP R5 stage, the UMTS core network is divided into three subsystems: Circuit Domain (CS), Packet Domain (PS) and IP Multimedia Subsystem (IMS). An IP multimedia subsystem located above the PS domain in the WCDMA) network uses the packet domain as the bearer channel for upper-layer control signaling and media transmission, and introduces the Session Initiation Protocol (SIP) as a service control protocol. Using SIP is simple and easy to expand , The characteristics of convenient media combination, through the separation of service control and bearer control, provide rich multimedia services, these rich multimedia services are usually provided by the service server (AS).

As shown in Figure 1, it is a schematic diagram of the UMTS core network structure in 3GPP R5. It can be seen from the figure that it mainly includes the following parts:

Call Session Control Function Module (CSCF):

CSCF can be divided into three types: P/S/I according to its position and function: among them:

P-CSCF (Proxy CSCF): It is the first connection point with the user in IMS, providing proxy (Proxy) function, that is, accepting service requests and forwarding them, but cannot modify the Request URI field in the INVITE message; P-CSCF also Can provide user agent (UA) function, that is, interrupt and independently generate SIP session under abnormal circumstances;

S-CSCF (Serving CSCF): S-CSCF is in the core control position in the IMS core network, responsible for UE registration authentication and session control, and performs basic session routing functions for calling and called IMS users. And according to the IMS trigger rule signed by the user, when the conditions are met, the value-added service routing trigger and service control interaction to the AS are performed;

I-CSCF (Interrogating CSCF): Similar to the gateway node of IMS, it provides the functions of local user service node allocation, route query and IMS inter-domain topology hiding;

Home Subscriber Server (HSS):

HSS is a centralized and comprehensive database that stores the subscription information of IMS users in the home network, including basic identifiers, routing information, and service subscription information. It is located at the top of the IMS core network architecture. The main information stored in the HSS includes:

IMS user identification (including public and private identification), number and address information;

IMS user security context: user network access authentication key information, roaming restriction information;

IMS user routing information: HSS supports user registration and stores user location information;

Service subscription information of IMS users: including value-added service data of other ASs;

Due to the introduction of various service servers AS in the IMS field, these service servers can provide users with a variety of rich services, such as online services, conference services, and message services. Correspondingly, each service needs to exist in the IMS network. The service identifier is used to identify the service and the data related to the service. This introduces the concept of the public service identifier (PSI). The PSI is used to identify a service in the AS or a resource of a specific service in the IMS. Treat PSI as an IMSUser to the greatest extent and maintain compatibility with existing interfaces, and introduce the concept of private service identity (PrivateService Identity) for PSI.

Private service identifiers are specified by network operators and are unique within the network. The relationship between them and PSI is a one-to-many relationship, that is, one private service identifier may be associated with one or more public service identifiers.

For PSI users, there are two ways to allocate S-CSCF, static configuration and dynamic allocation. Since PSI is not allowed to display and initiate the registration process, when dynamic allocation is used, the S-CSCF of PSI can only be obtained through the PSI When the user is called, when the PSI user is called for the first time, the home domain I-CSCF requests the user's location information from the HSS through the location information request command (LIR), and the HSS returns the server capability set required by the user According to the capability set information, select an S-CSCF that can meet the requirements, and forward the request for the PSI to the S-CSCF. After receiving the request, the S-CSCF finds that there is no user data locally and sends a configuration server request command (SAR ) to the HSS to request downloading of user data, the HSS locally saves the S-CSCF name for the user and returns the relevant user data, the S-CSCF finds the AS to which the PSI belongs according to the returned data, and performs the next hop to complete the routing of the PSI process.

In a proposal passed by the latest 3GPP standard meeting, the activation (Activation) status bit was introduced to the PSI, and its value range is activated and inactive. It stipulates that if the PSI is in the inactive (INACTIVE) state, the PSI is not allowed to accept services. Therefore, before initiating a service request to a PSI user, the HSS needs to check whether the PSI is in an active state to determine whether the operation is allowed.

The process of initiating a service request for PSI is shown in Figure 2, which mainly includes the following steps:

S01. The I-CSCF in the home domain of the PSI receives the INVITE request for the PSI forwarded by the P-CSCF;

S02. The I-CSCF queries the user location information from the HSS storing the user data;

S03. In the HSS inspection request, the PSI is in the Notregistered state, that is, there is no S-CSCF serving the PSI, and the S-CSCF capability set information that can satisfy the order relationship is returned;

S04. The I-CSCF selects an S-CSCF server that meets the requirements according to the returned capability set information;

S05. Forward the INVITE request to the selected S-CSCF;

S06. The S-CSCF sends a SAR request to the HSS, requesting to download user data, wherein the Server Assignment Type parameter value is unregistered (UNREGISTERED_USER);

S07. The HSS returns relevant data, saves the S-CSCF name, and sets the public user identification status contained in the request to unregistered (Unregistered);

S08. The S-CSCF performs service control according to the downloaded service configuration data;

S09. The S-CSCF performs subsequent service operations.

The proposal passed at the latest 3GPP standard meeting pointed out that in the command processing of the Cx interface, when the HSS receives the LIR and SAR requests, it needs to judge whether the identifier carried in the message is PSI. If it is PSI, it needs to further judge whether the PSI is PSI or not. Already activated, if the PSI has not been activated, the request is not allowed to continue and an error prompt is returned to the S-CSCF.

For some reason (such as an S-CSCF upgrade), when the administrator wants to delete all service PSIs, he needs to notify the HSS that the S-CSCF no longer serves these PSIs, and needs to reselect S-CSCFs for them. At this time, if a A private service identifier is associated with multiple public service identifiers at the same time. In order to reduce message traffic, only the private service identifier can be carried in the SAR in this case.

The existing solution only considers the existence of PSI in the request during the SAR command processing data inspection process, but does not consider the fact that there is only a private service identifier but no PSI and the private service identifier may be associated with more than one PSI Condition.

Contents of the invention

The present invention provides a data inspection method of a private service identifier, which is used to solve the problem existing in the prior art during the SAR command processing data inspection process, when there is only a private service identifier but no PSI and the private service identifier may be incompatible with In the case of more than one PSI association, the data inspection of the private service identifier cannot be performed.

The inventive method comprises:

A data inspection method for a private business identifier, characterized in that it comprises the following steps:

A. The Home Subscriber Server (HSS) receives the Configuration Server Request (SAR) sent by the Serving Call Control Session Function Module (S-CSCF), and requests to cancel the Public Service Identity (PSI) of the service, and the user in the Configuration Server Request (SAR) The identification part only carries the private business identification;

B. The HSS obtains the value of the server assignment type (Server Assignment Type) cell, and performs subsequent operations according to the value.

In the method, if in the step B, if the value of the server assignment type information element is a system reason, the home subscriber server (HSS) checks that the public service identification associated with the private service identification is activated state.

The method and the system reason include administrator reason logout (ADMINISTRATIVE_DEREGISTRATION) or too much data reason logout (DEREGISTRATION_TOO_MUCH_DATA).

The Home Subscriber Server (HSS) checks the activation status of the public service identifier associated with the private service identifier, and performs subsequent operations, including one of the following:

If all public service identifiers (PSI) are not activated, an unknown error (DIAMETER_ERROR_USER_UNKNOWN) is returned;

If all Public Service Identifiers (PSI) are activated, proceed with the logout operation;

If some public service identities (PSIs) are activated and some public service identities (PSIs) are not activated, the deregistration operation will continue, and the HSS will complete the deregistration of the activated public service identities (PSIs).

In the method, if in the step B, the value of the server-assigned type information element is the reason of the requester, the home subscriber server (HSS) returns an error to the serving call control session function module (S-CSCF) code.

In the step B, the reason of the requester includes timeout initiated logout (TIMEOUT_DEREGISTRATION) or initiative initiated logout (USER_DEREGISTRATION).

The configuration server request (SAR) is a configuration server request (SAR) initiated for a single wildcard public service identifier (PSI).

The present invention provides a data inspection method of a private service identifier. In the PSI operation, when only the private service identifier is carried in the SAR request without the public service identifier, the value of the ServerAssignment Type parameter in the request is checked, and the sum The checking of the activation state of the public service identifier associated with the private service identifier solves the problems not considered in the existing scheme, reduces message traffic, saves network resources, and optimizes network performance.

Description of drawings

Fig. 1 is the structural representation of the UMTS core network in 3GPP R5 in the prior art;

FIG. 2 is a schematic flow diagram of initiating a service request to PSI in the prior art;

Fig. 3 is a schematic flow chart of the present invention.

Detailed ways

The specific implementation manners of the present invention will be described below in conjunction with the accompanying drawings.

The present invention provides a supplementary improvement of SAR command processing on the Cx interface, including the limitation of the value range of the Server AssignmentType parameter in the request when there is only a private service identifier (Private Service Identifier) in the request, and all and the private service identifier. The process of checking the activation status of the PSI associated with the service identifier.

As shown in Figure 3, it is a schematic flow sheet of the present invention, as can be seen from Figure 3, the present invention mainly comprises the following steps:

S1. The HSS receives the SAR sent by the S-CSCF, and requests to cancel the PSI of the service. The SAR only carries the private service identifier.

When the HSS receives the SAR request, it checks the user ID in the request, and finds that there is no public service ID in the request, only a private service ID, and proceeds to step S2.

S2. The HSS obtains a value of a server assignment type information element (Server Assignment Type).

After HSS obtains the value of Server Assignment Type, it judges the value of Server Assignment Type, and judges according to the value to determine the content of subsequent processing.

S3. If in the above step S2, the value of the Server Assignment Type is the reason of the requester, such as TIMEOUT_DEREGISTRATION initiated by timeout, or USER_DEREGISTRATION initiated by the timeout, since these two values are meaningless to PSI, HSS will report to S - CSCF returns error code DIAMETER_ERROR_USER_UNKNOWN.

S4. If in the above step S2, the value of the Server Assignment Type is the system reason, if the value is the reason for the administrator to cancel ADMINISTRATIVE_DEREGISTRATION, it means that the administrator wants to delete all the public service identifiers associated with this private service identifier S-CSCF name; if the value is deregistration of DEREGISTRATION_TOO_MUCH_DATA due to too much data, it indicates that the S-CSCF has received too much data and notifies the HSS to clear the S-CSCF name. Then the HSS checks the activation state of the PSI associated with the private service identifier.

HSS checks the activation status of all public service identifiers associated with this private service identifier, and the check includes:

S5. If all PSIs are not activated, an error code DIAMETER_ERROR_USER_UNKNOWN should be returned to the S-CSCF at this time.

S6. If all PSIs are activated, allow the operation to continue.

S7. If some are activated and some are not activated, the operation is allowed to continue, and then the HSS is responsible for completing the de-registered process for these activated PSIs one by one.

In the above solution, for the SAR operation of a single wildcarded PSI (wildcardedPSI), it is necessary to clearly carry the PSI in the request. If only the private service identifier exists in the request, the above principle is also applicable to the wildcarded PSI.

Let's look at two specific examples.

Example 1:

The private business ID and public business ID stored in the HSS have a one-to-many relationship, and only the private business ID chatl@realm exists in this SAR request, and there is no public business ID;

When checking the value of Server-Assignment-Type, the value of Server-Assignment-Type is DEREGISTRATION_TOO_MUCH_DATA, indicating that the SAR request for deregistration is re-initiated because the S-CSCF has received too much data in the SAA;

If the public service identifier associated with the private service identifier on the HSS is not activated (the user deactivates the PSI during this process), the HSS returns an error code DIAMETER_ERROR_USER_UNKNOWN in the SAA.

The server assignment request and server assignment response of instance 1 and other related processes can be shown in the following code:

<Server-Assignment-Request>::=<Diameter Header: 301, REQ, PXY, 16777216>

[User-Name::＝chatl@realm]

{Server-Name::＝serverl@rims.realm.com}

{Server-Assignment-Type::＝DEREGISTRATION_TOO_MUCH_DATA}

{User-Data-Already-Available::＝USER_DATA_NOT_AVAILABLE}

<Server-Assignment-Answer>::=<Diameter Header: 301, PXY, 16777216>

[Result-Code::＝DIAMETER_ERROR_USER_UNKNOWN]

[User-Name::＝chatl@realm]

Example 2:

The private service identifier and public service identifier stored in the HSS have a one-to-many relationship, and only the private service identifier chatl@realm exists in this SAR request, and there is no public service identifier; the value of Server-Assignment-Type is ADMINISTRATIVE_DEREGISTRATION, indicating that Since the administrator of the S-CSCF wants to delete the PSI located on the S-CSCF, and notify the HSS;

The public service identifiers associated with the private service identifier on the HSS are all activated or partially activated: the HSS clears the S-CSCF names saved for these PSIs, and returns the success indication DIAMETER_SUCCESS in the SAA.

The server assignment request and server assignment response of instance 2 and other related processes can be shown in the following code:

<Server-Assignment-Request>::=<Diameter Header: 301, REQ, PXY, 16777216>

                         …

[User-Name::＝chat l@realm]

{Server-Name::＝serverl@rims.realm.com}

{Server-Assignment-Type::＝ADMINISTRATIVE_DEREGISTRATION}

{User-Data-Already-Available::＝USER_DATA_NOT_AVAILABLE}

                      ...

<Server-Assignment-Answer>::=<DiameterHeader: 301, PXY, 16777216>

                      ...

[Result-Code::＝DIAMETER_SUCCESS]

[User-Name::＝chatl@realm]

The present invention provides a data inspection method. In the PSI operation, the SAR request only carries the private service identifier without the public service identifier, checks the value of the Server Assignment Type parameter in the request, and compares the private service identifier The checking of the activation state of the associated public service identifier solves the situation that is not considered in the existing solution.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (7)

1. A data inspection method of a private business identification, characterized in that, comprising the following steps: A. The home subscriber server HSS receives the configuration server request SAR sent by the service call control session function module S-CSCF, and requests to cancel the public service identifier PSI of the service, and the user identifier part in the configuration server request SAR only carries the private service identifier; B. The HSS acquires the value of the Server Assignment Type IE, and performs subsequent operations according to the value. 2. The method according to claim 1, characterized in that if in said step B, if said server-assigned type cell value is a system reason, then the Home Subscriber Server (HSS) checks with said private service Identifies the activation status of the associated public service identifier. 3. The method according to claim 2, wherein the system reason includes administrator's reason to log out of ADMINISTRATIVE_DEREGISTRATION or reason of too much data to log out of DEREGISTRATION_TOO_MUCH_DATA. 4. The method according to claim 2 or 3, wherein the Home Subscriber Server (HSS) checks the activation status of the public service identifier associated with the private service identifier, and performs subsequent operations, including one of the following: one: If all public service identifiers PSI are not activated, an unknown error DIAMETER_ERROR_USER_UNKNOWN will be returned; If all public service identities PSI are activated, proceed with the logout operation; If some PSIs are activated and some PSIs are not activated, the deregistration operation is continued, and the HSS completes the deregistration of the activated PSIs. 5. The method according to claim 1, wherein in said step B, if the value of said server-assigned type information element is the requester reason, then the home subscriber server (HSS) calls the service call control session function Module S-CSCF returns an error code. 6. The method according to claim 5, wherein in the step B, the reason of the requester includes TIMEOUT_DEREGISTRATION initiated by timeout or USER_DEREGISTRATION initiated by the requester. 7. The method according to claim 1, wherein the configuration server request SAR is a configuration server request SAR initiated for a single wildcard public service identifier (PSI).

Images