WO2008031295A1

WO2008031295A1 - Method for acquiring initial request filter conditions by the home-call session control server.

Info

Publication number: WO2008031295A1
Application number: PCT/CN2006/003681
Authority: WO
Inventors: Baojian Zhang; Hangwei Hao
Original assignee: Zte Corporation
Priority date: 2006-09-07
Filing date: 2006-12-29
Publication date: 2008-03-20
Also published as: CN101141440A; CN101141440B

Abstract

A method for acquiring initial request filter conditions by the home-call session control server includes: configuring the IFC data on the total HSS; when initializing the S-CSCF, hss informs the S-CSCF of the corresponding ID of the ifc from the hss ifc data including the ID of every IFC; or when the subscriber initiates a request, the HSS transmits the id of the ifc to the S-CSCF, and the S-CSCF determines whether the correlated data corresponding to the IFC ID of the subscriber has been downloaded, if not, it requests the hss for the integrated IFC data of the subscriber; during the registration of the subscriber, when the S-CSCF acquiresthe IFC data from the HSS, the hss just tells the ID of the ifc to the S-CSCF. the problem that the primary scheme complicates the management of the every element of the network can be resolved because the S-CSCF doesn't configure the data of the ifc any more, and basically all advantages brought by the primary sharing IFC can be retained.

Description

FIELD OF THE INVENTION The present invention relates to the field of communications, and more particularly to the initial call origination control data (S-CSCF) in a next-generation network IMS (IP Multimedia Subsystem) network. A method of requesting filter (iFC) data. BACKGROUND With the development of communication technologies, more and more personalized services are appearing (Ring, MMS, POC, etc.). In order to meet the development of rich and colorful IP multimedia services, the telecommunications network is IP. 3GPP first proposed IMS (IP Multimedia Subsystem) in the 3^弋 mobile communication network; f. With the in-depth study of IMS, the IMS network structure gradually came out of the third generation mobile communication. The network's limitations have become a converged architecture for fixed-line next-generation networks (NGNs) and mobile NGNs.

The IMS network inherits the traditional mobile communication network model, and users can move and roam, which is achieved through the IMS user registration process.

The IMS network is mainly composed of a Call Session Control Function Server (CSCF), a Media Resource Function Server (MRF), a Home Signing Server (HSS), an interworking node (such as a Media Gateway Control Server MGCF, an Outgoing Gateway Control Server BGCF), and an Application Server (AS). )composition. The CSCF completes the user registration and session control triggering functions, and is further divided into a proxy call session control function server (P-CSCF), an interworking call session control function server (I-CSCF), and a home call session control function server (S-CSCF). The MRF controls the media plane and performs functions such as playback, user plane code conversion, and conference resource control. The HSS is the same concept as the HLR in mobile communication. It stores all the subscriber's subscription information and the user's location information. The interworking node completes the interworking between the IMS network user and other network (PSTN, 2G, ETC) users. The AS is the service processing network element in the IMS network. The S-CSCF of the IMS network triggers the session to the corresponding AS through the user-signed iFC, and the AS completes the corresponding service logic. iFC is a filtering rule condition, which is in XML format and belongs to a part of user subscription data. It is stored in HSS and realizes the separation of service and session control through iFC. The iFC defines the receipt of the SIP initial request message - according to which conditions determine that the call is to be triggered to the application server to execute the corresponding business logic, for example, iFC can define when the INVITE message is received, and the FROM field of the message contains "joe "When the call is triggered to an application server. The steps for IMS to use iFC to complete service and control separation are as follows (including obtaining iFC and using iFC). 1. User obtains iFC in subscription data by registration. Figure 1 is the initial registration process of IMS existing user: Step 101: User initiated to Initial registration of the IMS network REGISTER; Step 102: The P-CSCF forwards the REGISTER to the user's home network I-CSCF; Step 103: The I-CSCF queries the HSS according to the user ID in the REGISTER message; Step 104: The HSS returns the S assigned to the user registration -CSCF, or select the capability set of the S-CSCF; Step 105: The I-CSCF sends the user registration information to the S-CSCF according to the S-CSCF allocated by the HSS or the S-CSCF selected according to the capability set; Step 106: S-CSCF The user is authenticated; Step 107: After the authentication is passed, the S-CSCF downloads the user subscription data (including the iFC) through the CX interface and saves it, returns a response to the user 200, and completes the registration. Example of the user using the iFC to trigger the service process: Figure 2 is the IMS user caller service process triggering process Step 201: User A initiates a session to User B, User A signs the calling number display P system supplementary service, initiated INVITE The message carries the Privacy: id parameter. Step 202: The S-CSCF queries the iFC of the user A. The iFC indicates that if the INVITE request includes the Privacydd parameter, the AS is triggered to perform the service processing. Step 203: The AS processes the calling number of the user A. The display restricts the charging service and continues to call user B. Step 204: The S-CSCF routes the call request to the user B. From the above background description, we can see 1. Because iFC adopts the XML encoding format, the message size is relatively large. In the first stage, when the iFC is acquired, the step 107 of the user registration every time is downloaded through the cx interface, which may affect the network performance;

2. There is a situation where the service can use exactly the same iFC for a large number of users. In order to solve the above problem, the implementation of the shared iFC is proposed in the 3gpp protocol, that is, the S-CSCF and the HSS configure the iFC data at the same time, and configure the same ID for each iFC, and the user registration step 107 downloads the user iFC. The HSS only returns the ID of the iFC, and the S-CSCF determines the iFC corresponding to the ID according to the configuration. The protocol scheme improves network performance, enabling a large number of users to share the same iFC in the S-CSCF. However, this solution has the problem of complicating the management of network elements in the network:

1. The S-CSCF that did not use shared iFC technology does not need to configure iFC data, but now it needs to be configured, and it must be consistent with the HSS data;

2. If large-scale changes are made to the shared iFC, all S-CSCFs need to be modified, including data on the HSS, and the configuration changes are heavy. SUMMARY OF THE INVENTION The technical problem to be solved by the present invention is to provide a method for acquiring an iFC by an S-CSCF with improved iFC technology for the problems existing in the prior art. The technical solution of the present invention includes the following steps: Step 1: All initial request filtering condition (iFC) data is configured on a home subscription server (HSS); Step 2: Initializing at a home call session control server (S-CSCF) At the time, all initial request filtering conditions (iFC) data are downloaded from the home subscription server (HSS), including the ID of each initial request filtering condition (iFC), and the home subscription server (HSS) informs the home call session control server (S) - CSCF) the ID corresponding to the initial request filter condition (iFC); or when the user makes a request, the home subscription server (HSS) sends the ID of the initial request filter condition (iFC) to the home call session control server (S-CSCF) And determining, by the home call session control server (S-CSCF), whether the relevant data corresponding to the initial request filtering condition (iFC) ID of the user has been downloaded, and if not, requesting the user to complete the user to the home signing server (HSS) Initial request filter condition (iFC) data; Step 3: During the user registration process, when the home call session control server (S-CSCF) obtains initial request filtering condition (iFC) data from the home subscription server (HSS), the home subscription server (HSS) only informs the home call session control server. (S-CSCF) The ID of the initial request filter condition (iFC). In step 2, after the S-CSCF downloads and saves the IFC data, if the HSS modifies the IFC in the user subscription data, the HSS notifies the S-CSCF that the IFC has been changed, and sends the changed IFC to the S-CSCF. Related changes. In the above solution, when the home call session control server (S-CSCF) initializes, all initial request filtering conditions (iFC) data are downloaded from the home subscription server (HSS), and implemented by FTP, SCTP, and TCP. In the above solution, when the user requests to obtain the initial request filtering condition, the first user issues a registration request, and the home call session control server (S-CSCF) requests the home subscription server (HSS) to acquire the user. The subscription data, the home subscription server (HSS) returns initial request filtering condition (iFC) data, and carries the shared ID of the initial request filtering condition (iFC) data, and records that the home call session control server (S-CSCF) has acquired the original Shared initial request filter condition (iFC) data; when a subsequent user initiates a registration request, the home subscription server (HSS) returns the ID of the initial request filter condition (iFC) data, and the home call session control server (S-CSCF) according to the ID The initial request filter condition (iFC) data used by the user who initiated the registration request can be obtained; if the home call session control server (S-CSCF) cannot determine the shared initial request filter condition (iFC) data, the home call session control server (S -CSCF ) Re-initiate the subscription data request of the latter user, requesting complete transmission in the request Start request filtering conditions (the iFC) data, the home subscriber server (HSS) of the initial request returns the complete filtering conditions (the iFC) data and its ID. The S-CSCF does not configure the data of the iFC, which effectively solves the problem that the original scheme complicates the management of the network elements of the network, and basically retains all the benefits brought by the original shared IFC. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a flow chart of a user registration registration data in the prior art; FIG. 2 is a diagram showing an example of a service using an iFC to trigger an AS in the prior art; FIG. 3 is a flowchart of a scheme for acquiring an iFC through a registration process; Figure 4 is a flow chart of a scheme for the S-CSCF to actively acquire the iFC. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A plurality of specific implementations can be implemented by using the present invention to implement the shared iFC technology: Solution 1: Obtain an iFC solution when a user initiates a request, as shown in FIG. 3: Step 301: S-CSCF 4 to User A registration request; 302: The S-CSCF requests the HSS to obtain the user A subscription data. The shared iFC obtained this time is the first acquisition request of the S-CSCF, the HSS returns the iFC data, and carries the shared ID of the iFC, and records the S-CSCF acquired. The shared iFC; Step 303: S-CSCF > registration request to User B; Step 304: The S-CSCF requests the HSS to obtain the User B subscription data, because User B uses the same iFC as User A, and S- The CSCF has obtained the iFC of the user A, the HSS returns the ID of the iFC, and the S-CSCF can obtain the iFC used by the user B according to the ID; further, the shared iFC cannot be determined at the 304 S-CSCF, and the S-CSCF re-initiates the user B subscription. Data request, the request requires full transmission of iFC data, and the HSS returns iFC complete data and its ID. Solution 2: When the S-CSCF is initialized, the iFC solution is downloaded from the HSS, as shown in Figure 4: Step 401: The S-CSCF initiates a shared iFC acquisition request to the home HSS, which can be FTP, SCTP or TCP, but is not limited to In the above manner, step 402: If the HSS supports the iFC, the HSS sends the shared iFC and the ID to the S-CSCF, and if not, responds to the NOT-SUPPORTED; Step 403: User A initiates registration to the S-CSCF; Step 404: The S-CSCF obtains the subscription data of the user A from the HSS. Step 405: If the HSS supports the iFC, the HSS determines that the relevant shared iFC has been downloaded to the S-CSCF, and then returns the ID of the shared iFC, and the S-CSCF obtains the user according to the shared ID. A corresponds to the shared iFC; if the HSS does not support iFC, it returns the relevant data of the corresponding user's iFC.

Claims

Claim

A method for a home call session control server to obtain an initial request filtering condition, comprising the following steps:

Step 1: All the initial request filtering condition data is configured on the home subscription server;

Step 2: When the home call session control server initializes, download all initial request filter condition data from the home subscription server, including the ID of each initial request filter condition, and the home subscription server informs the home call session control server of the initial request filter condition. ^" should be the ID; or

When the user issues a request, the home subscription server sends the ID of the initial request filtering condition to the home call session control server, and the home call session control server determines whether the data related to the initial request filtering condition ID of the user has been downloaded, if not Downloading, requesting the user to complete the initial request filtering condition data from the home subscription server;

Step 3: During the user registration process, when the home call session control server obtains the initial request filter condition data from the home subscription server, the home subscription server only informs the home call session control server of the initial request filter condition ID.

The method for obtaining the initial request filtering condition by the home call session control server according to claim 1, wherein after the home call session control server downloads and saves the initial request filtering condition data, if the home subscription server modifies the user subscription data, In the initial request filtering condition, the home subscription server notifies the home call session control server that the initial request filtering condition has been changed, and sends the changed initial request filtering condition to the home call session control server for related modification.

3. The method for obtaining an initial request filtering condition by the home call session control server according to claim 1, wherein, when the home call session control server performs initialization, all initial request filtering condition data is downloaded from the home subscription server, and is performed by FTP. , SCTP TCP implementation.

The method for obtaining the initial request filtering condition by the home call session control server according to claim 1, wherein, when the user requests to obtain the initial request filtering condition, the first user issues a registration request, and the home call session control The server requests the home subscription server to acquire the user subscription data, and the home subscription server returns the initial request filtering condition data. And carrying the shared ID of the initial request filtering condition data, and recording that the home call session control server has acquired the initial request filtering condition data of the sharing; when the subsequent user initiates the registration request, the home subscription server returns the ID of the initial request filtering condition data. The home call session control server can obtain the initial request filter condition data used by the user who initiates the registration request according to the ID; if the home call session control server cannot determine the shared initial request filter condition data, the home call session control server re-initiates the subsequent user. The subscription data request, the request requires complete transmission of the initial request filter condition data, and the home subscription server returns the complete initial request filter condition data and its ID.