CN1303793C - Method for realizing application server communication - Google Patents

Abstract

The invention discloses a method for realizing application server communication. The method includes: a first AS establishes a route to a second AS through an IMS functional entity, information exchange is performed between the first AS and the second AS, and the second AS AS can be one or more AS. According to the method proposed by the present invention, by using the routing function of IMS, the information exchange between ASs is realized, and then the information sharing and cooperation between multiple ASs are realized, the network structure of the service layer is simplified, and the service provision of OSE is enhanced. ability. The present invention can make the information interaction between ASs efficient and concise, reduce the complexity of information interaction between ASs, avoid complex search and judgment processes, save network resources, and help operators deploy networks more flexibly. It also enhances the network capability of the IMS.

Description

A method for realizing application server communication

technical field

The invention relates to information transmission technology, in particular to a method for realizing application server communication.

Background technique

With the development of broadband network, mobile communication will not only be limited to traditional voice communication, but also multimedia services combining audio, video, picture and text and other media types will be gradually developed, through the communication with presence, short message The combination of business, webpage (WEB) browsing service, positioning service, push service (PUSH), file sharing service and other data services can meet various needs of users.

Driven by a variety of applications, the 3rd Generation Partnership Project (3GPP) standard organization has launched an Internet Protocol (IP)-based multimedia subsystem (IMS, IP Multimedia Subsystem) architecture, the purpose of which is to provide standardized open communication networks. structure to support a variety of multimedia applications; and the Open Mobile Alliance (OMA, Open Mobile Alliance) standard organization launched the OMA Service Environment (OSE, OMA Service Environment), as a service implementation layer on top of the IMS architecture, to provide users with more More choices and richer feelings.

Figure 1 shows a schematic diagram of the IMS architecture. As shown in Figure 1, the IMS is superimposed on the packet switching network, and consists of a call session management function (CSCF, Call Session Control Function), a media gateway control function (MGCF, Media Gateway Control Function) , Media Resource Function (MRF, Multimedia Resource Function) and Home Subscriber Server (HSS, HomeSubscriber Server) and other functional entities. According to the different functions realized by CSCF, it can be divided into three logical entities: Serving CSCF (S-CSCF), Proxy CSCF (P-CSCF) and Inquiring CSCF (I-CSCF). S-CSCF is the business switching center of IMS and can Complete session control, maintain session state, manage user information, generate billing information, etc.; P-CSCF is the access point for user equipment (UE) to access IMS, and can complete user registration, quality of service (QoS) control and Security management, etc.; I-CSCF implements routing lookup, such as intercommunication within and between IMS domains, manages S-CSCF allocation, hides network topology and configuration from external networks and other IMS domains, and generates calculations fee information, etc. The MGCF implements the function of the control gateway and realizes the intercommunication between the IMS network and other networks; the MRF provides media resources, such as audio playback, encoding and decoding of information transmitted between terminals, and multimedia conference bridge, etc., including media resource function control ( MRFC, Multimedia Resource Function Controller) and media resource function processing (MRFP, Multimedia Resource Function Processor). The subscription data and configuration information of users in the IMS network are stored in the HSS. The Session Initiation Protocol (SIP, Session Initiation Protocol) is used in the IMS as the session control protocol.

Figure 2 shows a schematic diagram of information interaction between the OSE and the IMS. As shown in Figure 2, the OSE is mainly composed of multiple ASs. Currently, the AS defined in OMA includes a push-to-talk voice service server based on a cellular system ( PoC Server), Presence Server that provides user status, Group List Management Server (GLMS, Group List Management Server) that enables users to store and obtain group information, and Device Management Server (DMServer, Device Management Server) ), etc., these ASs and related support systems, such as billing entities, network management entities, etc., constitute the OSE. The main functions of IMS include business capabilities, support capabilities, and general capabilities. Among them, business capabilities include session management, user data storage and reading, event subscription and notification, messages, conferences, etc.; support capabilities include billing, etc.; general capabilities include Secure connection, authentication, authorization, routing, etc. As the upper layer of IMS, OSE will utilize these capabilities provided by IMS. OMA is responsible for defining OSE, and proposes requirements for IMS according to the requirements of OSE for IMS. 3GPP is responsible for defining IMS and the interface between IMS and OSE. The interface between OSE and IMS includes ISC interface, Sh interface, Dh interface, Ut interface, Ro interface, Rf interface, Gm interface, Mb interface, etc. Among them, the ISC interface is the interface between the AS and the IMS, which realizes functions such as call control of the AS by the IMS, SIP event subscription and notification, and SIP messages; Read, modify, and change the subscribed user subscription data; the Dh interface is the interface between the AS and the Service Locator Function (SLF, ServiceLocator Function), which realizes the query of the HSS address by the ASS; the Ut interface is the interface between the OSE client and the AS The interface between AS and the user can realize the operation ability of configuring AS user data through the OSE client; the Ro interface is the interface between the AS and the online charging entity, which realizes real-time charging; the Rf interface is between the AS and the offline charging entity The interface realizes offline billing; the Gm interface is the interface between the OSE client and the IMS, which realizes functions such as session function, event subscription notification, and message; the Mb interface is the service flow interface between the AS and the OSE client through the IMS , to transmit media stream information.

In practical applications, for the services used by users, multiple ASs can be combined as needed. For example, several game servers can be combined through a conference processing server to provide users with online games. In this way, it is necessary to exchange information between ASs. interact. At present, IMS defines the routing mechanism between users and users, users to AS, and AS to users in detail; for routing between ASs, IMS requires AS to have Service Capability Interaction Manager (SCIM, Service Capability Interaction Manager), that is, IMS assumes that the OSE layer provides Routing mechanism between ASs.

Figure 3 shows a schematic diagram of information exchange between ASs defined by 3GPP. As shown in Figure 3, when information exchanges between ASs, the service-providing device AS performs information exchanges with other ASs through SCIM. SCIM is an implementation AS defined by 3GPP. The entities that exchange information between them. The dotted line shown in the figure is the interface between ASs through SCIM. The solid line arrow shown in the figure is the interface between OSE and IMS, such as ISC interface, Sh interface, and Dh interface. etc. 3GPP classifies SCIM into the scope of AS, and does not define the specific implementation process between SCIM and AS.

It can be seen from the above description that SCIM must be set in OSE to realize information exchange between ASs, which makes the network structure of AS and business layer more complex, and it is necessary to provide routing-related servers in the business layer, resulting in network construction costs and network Maintenance costs are greatly increased.

Contents of the invention

In view of this, the purpose of the present invention is to provide a method for realizing communication between application servers, so as to realize information exchange between application servers.

In order to achieve the above object, the present invention provides a method for implementing application server communication, the method includes step A: the first AS sends a request to establish a route with the second AS to the first S-CSCF to which it belongs;

B. The first S-CSCF provides the second AS identity to the I-CSCF;

C. The I-CSCF returns to the first S-CSCF the address information of the second S-CSCF to which the second AS belongs obtained through DNS or the HSS signed by the second AS;

D. The first AS establishes a route with the second AS according to the address information of the second S-CSCF.

Before the step A, it further includes: the first AS establishes a session with the first S-CSCF, and the second AS establishes a session with the second S-CSCF.

The establishment of a session between the first AS and the first S-CSCF is as follows: the first AS sends a registration request to the I-CSCF, and the I-CSCF obtains the address information of the first S-CSCF through the HSS signed by the first AS, and then reports to the The first S-CSCF forwards the registration request, and the first S-CSCF responds to the registration request to establish a session with the first AS;

The establishment of a session between the second AS and the second S-CSCF is as follows: the second AS sends a registration request to the I-CSCF, and the I-CSCF obtains the address information of the second S-CSCF through the HSS signed by the second AS, and then sends the The second S-CSCF forwards the registration request, and the second S-CSCF establishes a session with the second AS in response to the registration request.

The I-CSCF acquires the address information of the first S-CSCF through the HSS signed by the first AS: the I-CSCF acquires the address information of the HSS signed by the first AS through the SLF, and then the I-CSCF acquires the first S-CSCF address information through the HSS. S-CSCF address information;

The I-CSCF obtains the address information of the second S-CSCF through the HSS signed by the second AS: the I-CSCF obtains the address information of the HSS subscribed to the second AS through the SLF, and then the I-CSCF obtains the second S-CSCF address information through the HSS. S-CSCF address information.

The first S-CSCF responds to the registration request to establish a session with the first AS: the first S-CSCF obtains the subscription data of the first AS through the HSS signed by the first AS, and then returns a registration response to the first AS, Establish a session with the first AS;

The second S-CSCF responds to the registration request to establish a session with the second AS: the second S-CSCF obtains the subscription data of the second AS through the HSS subscribed to by the second AS, and then returns a registration response to the second AS, A session is established with the second AS.

Before the step A, it further includes: configuring the address information of the first S-CSCF in the first AS, and configuring the address information of the second S-CSCF in the second AS.

The step D includes: the first AS sends a session establishment request carrying the second AS identifier to the first S-CSCF, and the first S-CSCF forwards the session establishment request carrying the second AS identifier to the second S-CSCF, After the second S-CSCF receives the session establishment request, it sends the session establishment request to the second AS according to the second AS identifier, and after the second AS receives the session establishment request, it sends the session establishment request to the second AS through the first S-CSCF and the second S-CSCF. An AS returns a session establishment response to establish a session with the first AS.

The first AS establishes a session with the first S-CSCF, and further includes: performing a security detection mechanism between the first AS and the first S-CSCF, and if the security detection mechanism passes, the first AS and the first S-CSCF Establish a session; otherwise, end the current process;

The second AS establishes a session with the second S-CSCF, and further includes: performing a security detection mechanism between the second AS and the second S-CSCF, and if the security detection mechanism passes, the second AS and the second S-CSCF Establish a session; otherwise, end the current process.

The step D further includes: the first AS negotiates a service quality policy with the second AS through the first S-CSCF and the second S-CSCF, and determines service quality parameters.

After the step D, it further includes: the second AS returns a response to the first AS through the second S-CSCF and the first S-CSCF.

The second AS is more than one AS.

The method further includes: the first S-CSCF triggers to the third-party AS according to the related service trigger condition.

The trigger condition is configured in the first S-CSCF; or configured in the HSS subscribed to by the first AS, and the first S-CSCF acquires the trigger condition through interaction with the HSS.

According to the method proposed by the present invention, by using the routing function of IMS, the ASs can establish information exchange channels through the functional entities in the IMS, so as to realize the information exchange between ASs, and then realize the information sharing and cooperation among multiple ASs , simplifies the network structure of the service layer, and enhances the service provision capability of the OSE. The present invention can make the information interaction between ASs efficient and concise, reduce the complexity of information interaction between ASs, avoid complex search and judgment processes, save network resources, and help operators deploy networks more flexibly. It also enhances the network capability of the IMS.

Description of drawings

Figure 1 shows a schematic diagram of the IMS architecture;

Figure 2 shows a schematic diagram of information exchange between OSE and IMS;

FIG. 3 shows a schematic diagram of information exchange between ASs defined by 3GPP;

FIG. 4 shows a schematic diagram of information exchange between ASs in the present invention;

FIG. 5 shows a flow chart of information interaction between the AS and the IMS functional entity in the present invention;

Fig. 6 shows the flowchart of establishing a session between AS and S-CSCF in the present invention;

Fig. 7 shows the flowchart of establishing a session between AS1 and AS2 in the present invention;

FIG. 8 shows a schematic diagram of Embodiment 1 of information exchange between ASs based on non-session in the present invention;

FIG. 9 shows a schematic diagram of Embodiment 2 of information exchange between ASs based on non-session in the present invention;

FIG. 10 shows a schematic diagram of Embodiment 3 of information exchange between ASs based on non-session in the present invention;

FIG. 11 shows a flow chart of direct information exchange between ASs in the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings.

In the present invention, by using the routing function of the IMS, the information exchange channel is established between the ASs through the functional entities in the IMS, and then the information sharing and collaboration between multiple ASs are realized, the network structure of the service layer is simplified, and the OSE is enhanced. Business provision capability.

Fig. 4 shows a schematic diagram of information exchange between ASs in the present invention. As shown in Fig. 4, since ASs are not only used by users, but also used by other servers, it is necessary to provide reasonable information exchange solutions for ASs to ensure that ASs The dotted line shown in the figure is the logical interface between the ASs. First, the information exchange channel between the ASs needs to be established through the SIP signaling of the IP Multimedia Service Routing (ISR, IPMultimedia Service Routing) indicated by the two-way arrow in the figure. Then, information exchange between ASs can be carried out through the channel established, which can be a transmission network between ASs, such as IP network, Asynchronous Transfer Mode (ATM) network, etc.; this channel can also be a link between AS and IMS functional entity Transmission channel, that is, information exchange between ASs through IMS functional entities, such as SIP Message, etc.

Fig. 5 shows the flow chart of AS performing information interaction through IMS functional entities in the present invention. As shown in Fig. 5, the implementation process of AS performing information interaction through IMS functional entities includes the following steps:

Step 501-Step 502: To ensure communication security, a security detection mechanism can be added between AS and IMS functional entity, such as mutual authentication between AS1 and IMS functional entity, mutual authentication between AS2 and IMS functional entity, If both parties pass the authentication of the other party, the subsequent information exchange will continue.

Steps 503 to 504: AS1 sends information carrying the ID of AS2 to the IMS functional entity, and the IMS functional entity forwards the received information to AS2 according to the received ID of AS2.

Steps 505 to 506: After receiving the information, AS2 sends a response carrying the ID of AS1 to the IMS functional entity, and the IMS functional entity forwards the received response to AS1 according to the received ID of AS1, and notifies AS1 that the information sent by AS2 has been completed. take over.

Due to the complex structure of the IMS with numerous network elements and interfaces, depending on the location of the AS, the ASs can exchange information through each network element in the IMS, such as CSCF, SLF, MGCF, BGCF, and MRF. The manners of information exchange between network elements are basically the same, and the specific implementation manner of the present invention will be described in detail below by taking the AS as an example through the CSCF.

There are generally two ways of information exchange between ASs, one is a session-based information exchange mode, and the other is a non-session-based information exchange mode.

The session-based information exchange mode refers to information exchange between ASs through established sessions. Before establishing a session between ASs and implementing information exchange between ASs through the routing capability of the IMS, the AS first needs to access the IMS and establish a session with the IMS functional entity. The AS can establish a session with the IMS functional entity by registering with the IMS functional entity.

Fig. 6 shows the flow chart of establishing a session between AS and S-CSCF in the present invention. As shown in Fig. 6, the realization process of establishing session between AS and S-CSCF includes the following steps:

Step 601 to Step 603: AS sends a registration request carrying its own identity to the I-CSCF. After receiving the registration request, the I-CSCF sends an HSS query request carrying the AS identifier to the SLF, and queries the HSS corresponding to the data of the corresponding AS, that is, the HSS signed by the AS. After receiving the query request, the SLF searches for the HSS that stores the corresponding subscription data of the AS according to the AS identifier, and then returns the HSS query response carrying the HSS address information to the I-CSCF.

Steps 604 to 605: After receiving the HSS query response, the I-CSCF sends an S-CSCF query request carrying the AS identifier to the corresponding HSS according to the HSS address information. HSS receives the S-CSCF query request, obtains the capability information of the S-CSCF required by the AS according to the subscription data of the corresponding AS, then determines the S-CSCF that can meet the capability information, and returns the S-CSCF carrying the S-CSCF to the I-CSCF. - S-CSCF query response for CSCF address information.

Steps 606 to 608: After receiving the query response from the S-CSCF, the I-CSCF sends a registration request carrying the AS identifier to the corresponding S-CSCF according to the address information of the S-CSCF. After receiving the registration request, the S-CSCF sends a subscription data request carrying the AS identifier to the HSS according to the AS identifier. After receiving the subscription data request, the HSS searches for the subscription data of the AS according to the AS identifier, and then returns a subscription data response carrying the AS identifier and subscription data to the S-CSCF. If the HSS does not allow the AS to establish a session with the S-CSCF, it will directly return a subscription data response carrying the corresponding identifier to the S-CSCF, and the S-CSCF refuses to establish a session with the AS, that is, rejects the registration of the AS.

Step 609: The S-CSCF returns a registration response to the corresponding AS according to the AS identity, notifying the AS whether the registration is allowed.

In addition, the address information of the S-CSCF can also be pre-configured in the AS, so that the AS can directly establish a session with the configured S-CSCF, and the registration process for establishing the session described above can be omitted.

Fig. 7 shows the flowchart of establishing a session between AS1 and AS2 in the present invention. As shown in Fig. 7, AS1 has established a session with S-CSCF1, and AS2 has established a session with S-CSCF2. Under the situation based on the SIP protocol, AS1 and AS2 The implementation process of establishing a session includes the following steps:

Step 701 to Step 703: AS1 sends an Invite message carrying the ID of AS2 to S-CSCF1. After receiving the Invite message, S-CSCF1 sends the Invite message carrying the AS2 identifier to S-CSCF2. After receiving the Invite message, S-CSCF2 sends the Invite message to AS2 according to the AS2 identifier.

S-CSCF1 can obtain address information of S-CSCF2 through I-CSCF, that is, S-CSCF1 provides AS2 identification to I-CSCF to request I-CSCF to provide address information of S-CSCF2, and I-CSCF requests HSS or domain name server ( DNS) queries the S-CSCF2 corresponding to AS2, and the HSS or DNS returns the address information of the S-CSCF2, thereby obtaining the address information of the S-CSCF2.

Steps 704 to 706: After receiving the Invite message, AS2 returns to S-CSCF2 a 200 OK response carrying the AS1 identifier; after receiving the 200 OK response, S-CSCF2 returns a 200 OK response carrying the AS1 identifier to S-CSCF1 according to the AS1 identifier. 200 OK response; after receiving the 200 OK response, S-CSCF1 returns a 200 OK response to AS1 according to the identity of AS1.

Steps 707 to 709: After receiving the 200 OK response, AS1 returns to S-CSCF1 the Ack response carrying the AS2 identity; after receiving the Ack response, S-CSCF1 returns to S-CSCF2 the Ack carrying the AS2 identity according to the AS2 identity response. After receiving the Ack response, S-CSCF2 returns an Ack response to AS2 according to the AS2 identifier.

Step 710: Through the above process, a session has been established between AS1 and AS2. In this way, media flow information is transmitted between AS1 and AS2. For example, AS1 sends media flow information carrying the AS2 identifier to S-CSCF1; S-CSCF1 receives After receiving the media stream information, it forwards the media stream information carrying the AS2 identifier to S-CSCF2; after receiving the media stream information, S-CSCF2 sends the media stream information to AS2 according to the AS2 identifier.

In the above process, AS1 and AS2 can transmit QoS parameters through S-CSCF1 and S-CSCF2, and negotiate QoS policies. After agreeing on QoS parameters, the transmission quality of media stream information transmitted between AS1 and AS2 will not be low. Based on the agreed QoS parameters.

In the session-based information interaction method described above, ASs exchange information through IMS functional entities, making full use of the routing function of IMS; and can negotiate the transmission quality between ASs, and establish QoS according to the needs of information interaction. The corresponding session connection of the quality of service; when the QoS policy is not negotiated, the session connection of simple fixed quality of service can be realized.

The non-session-based information exchange mode means that the information exchange between ASs is not performed through an established session, but is directly forwarded by the IMS functional entity. In the non-session-based information exchange mode, the information exchanged between ASs is mainly general information, such as message information. If it is media stream information, QoS parameters need to be manually configured.

In order to ensure communication security, AS can implement a security detection mechanism with the IMS functional entity, such as mutual authentication between AS1 and IMS functional entity, and mutual authentication between AS2 and IMS functional entity. If the right is not granted, the subsequent information exchange will continue.

FIG. 8 shows a schematic diagram of Embodiment 1 of non-session-based information interaction between ASs in the present invention. As shown in FIG. 8 , the implementation process of non-session-based information interaction between ASs in this embodiment includes the following steps:

Steps 801 to 803: AS1 sends information carrying the identity of AS2 to the I-CSCF. After receiving the information, the I-CSCF sends an HSS query request carrying the AS2 identifier to the HSS according to the AS2 identifier. After receiving the HSS query request, the HSS searches for the address information and related subscription data of AS2 according to the AS2 identifier, and then returns the HSS query response to the I-CSCF.

Steps 804 to 806: After receiving the HSS query response, the I-CSCF sends information to AS2 according to the address information of AS2. After receiving the information, AS2 returns a response carrying AS1 to the I-CSCF. After receiving the response, the I-CSCF returns a response to AS1 according to the identity of AS1, notifying AS1 that the information it sent has been received by AS2.

FIG. 9 shows a schematic diagram of Embodiment 2 of information interaction between ASs based on non-session in the present invention. As shown in FIG. 9 , the realization process of information interaction between ASs based on non-session in this embodiment includes the following steps:

Steps 901 to 903: AS1 sends information carrying the identity of AS2 to the I-CSCF. After receiving the information, the I-CSCF sends a DNS query request carrying the AS2 identifier to the DNS according to the AS2 identifier. After receiving the DNS query request, the DNS searches for the address information and related subscription data of AS2 according to the AS2 identifier, and then returns a DNS query response to the I-CSCF.

Steps 904 to 906: After receiving the DNS query response, the I-CSCF sends information to AS2 according to the address information of AS2. After receiving the information, AS2 returns a response carrying AS1 to the I-CSCF. After receiving the response, the I-CSCF returns a response to AS1 according to the identity of AS1, notifying AS1 that the information it sent has been received by AS2.

FIG. 10 shows a schematic diagram of Embodiment 3 of information interaction between ASs based on non-session in the present invention. As shown in FIG. 10 , the implementation process of information interaction between ASs based on non-session in this embodiment includes the following steps:

Steps A1 to A4: AS1 sends information carrying the AS2 ID to S-CSCF1. After receiving the information, the S-CSCF1 sends the information carrying the AS2 identifier to the I-CSCF. After receiving the information, the I-CSCF sends the information carrying the AS2 identifier to the S-CSCF2. After receiving the information, S-CSCF2 sends information to AS2 according to the AS2 identifier.

The I-CSCF may request the HSS or the DNS to query the S-CSCF2 corresponding to AS2, and the HSS or the DNS returns the address information of the S-CSCF2, thereby obtaining the address information of the S-CSCF2.

Steps A5 to A8: After receiving the information, AS2 returns a response carrying the AS1 identifier to S-CSCF2. After receiving the response, S-CSCF2 returns a response carrying the AS1 identifier to the I-CSCF. After receiving the response, the I-CSCF returns a response carrying the AS1 identifier to the S-CSCF1 according to the AS1 identifier. After receiving the response, S-CSCF1 returns a response to AS1 according to the identity of AS1, notifying AS1 that the information it sent has been received by AS2.

The address information of the IMS functional entity involved in the above description of information exchange between ASs based on non-session can be pre-configured in the corresponding AS, so that when the AS needs to exchange information with other ASs, the exchanged information can be directly sent to the configured corresponding IMS functional entity, and then the corresponding IMS functional entity sends the information to other ASs.

In addition, the IMS functional entity can be used as the trigger point of the corresponding service. For example, when the IMS functional entity receives a trigger message, it sends information to the corresponding AS according to the configured trigger conditions, and the AS returns an operation instruction to the IMS functional entity, such as generating a fee information, etc. That is to say, when ASs exchange information through the IMS functional entity, the IMS functional entity can trigger to the third-party AS according to the trigger condition. For example, when the IMS functional entity receives a message carrying the trigger condition identifier, it triggers the AS. The trigger condition can be configured in the IMS functional entity; it can also be configured in the HSS, and the corresponding IMS functional entity can obtain the trigger condition through interaction with the HSS.

According to the configuration of the operator, the IMS can generate charging information for the information exchange process of the AS through it.

In addition, after a session is established between ASs, information exchange can be performed directly through the transmission network between ASs without passing through the IMS functional entity, as shown in Figure 11:

Step B1 to Step B2: AS1 sends information to AS2 through the transmission network; after receiving the information, AS2 returns a response to AS1, notifying AS1 that it has received the information it sent.

Step B3 to Step B4: AS2 sends information to AS1 through the transmission network; after receiving the information, AS1 returns a response to AS2, notifying AS2 that it has received the information it sent.

There is no obvious order of execution between steps B1 to B2 and steps B3 to B4.

Before information exchange between AS1 and AS2, QoS parameters can be directly transmitted, and QoS policies can be negotiated. After agreeing on QoS parameters, the transmission quality of media stream information transmitted between AS1 and AS2 will not be lower than the agreed QoS parameters.

The above only describes the situation of information exchange between two ASs. In fact, information exchange can also be performed between multiple ASs, that is, information exchange can be performed between multiple ASs through IMS functional entities. The specific implementation process It is basically the same as the above description, so it is not repeated here.

In a word, the above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (13)

1. A method for realizing application server AS communication, characterized in that the method comprises: A. The first AS sends a request to establish a route with the second AS to the first serving call session control function entity S-CSCF to which it belongs; B. The first S-CSCF provides the second AS identifier to the inquiring call session control function entity I-CSCF; C. The I-CSCF returns to the first S-CSCF the address information of the second S-CSCF to which the second AS belongs obtained through the domain name server DNS or the home subscriber register HSS signed by the second AS; D. The first AS establishes a route with the second AS according to the address information of the second S-CSCF. 2. The method according to claim 1, further comprising: before the step A, the first AS establishes a session with the first S-CSCF, and the second AS establishes a session with the second S-CSCF. 3. The method according to claim 2, wherein the establishment of the session between the first AS and the first S-CSCF is as follows: the first AS sends a registration request to the I-CSCF, and the I-CSCF subscribes through the first AS The HSS obtains the address information of the first S-CSCF, and then forwards the registration request to the first S-CSCF, and the first S-CSCF establishes a session with the first AS in response to the registration request; The establishment of a session between the second AS and the second S-CSCF is as follows: the second AS sends a registration request to the I-CSCF, and the I-CSCF obtains the address information of the second S-CSCF through the HSS signed by the second AS, and then sends the The second S-CSCF forwards the registration request, and the second S-CSCF responds to the registration request to establish a session with the second AS. 4. The method according to claim 3, wherein the I-CSCF obtains the first S-CSCF address information through the HSS signed by the first AS: the I-CSCF obtains the first S-CSCF address information through the service location function SLF The address information of the HSS signed by the AS, and then the I-CSCF obtains the address information of the first S-CSCF through the HSS; The I-CSCF obtains the address information of the second S-CSCF through the HSS signed by the second AS: the I-CSCF obtains the address information of the HSS subscribed to the second AS through the SLF, and then the I-CSCF obtains the second S-CSCF address information through the HSS. S-CSCF address information. 5. The method according to claim 3, wherein the first S-CSCF responds to the registration request to establish a session with the first AS: the first S-CSCF obtains the first AS through the HSS signed by the first AS. AS subscription data, and then return a registration response to the first AS, and establish a session with the first AS; The second S-CSCF responds to the registration request to establish a session with the second AS: the second S-CSCF obtains the subscription data of the second AS through the HSS subscribed to by the second AS, and then returns a registration response to the second AS, A session is established with the second AS. 6. The method according to claim 1, further comprising: configuring the address information of the first S-CSCF in the first AS before step A, and configuring the address information of the second S-CSCF in the second AS Address information. 7. The method according to claim 1 or 2, wherein the step D comprises: the first AS sends a session establishment request carrying the second AS identifier to the first S-CSCF, and the first S-CSCF sends a session establishment request to the first S-CSCF. The second S-CSCF forwards the session establishment request carrying the second AS identifier. After receiving the session establishment request, the second S-CSCF sends the session establishment request to the second AS according to the second AS identifier, and the second AS receives the session establishment request. After the request, the first S-CSCF and the second S-CSCF return a session establishment response to the first AS to establish a session with the first AS. 8. The method according to claim 2, wherein before establishing a session between the first AS and the first S-CSCF, further comprising: performing a security detection mechanism between the first AS and the first S-CSCF, if If the security detection mechanism is passed, the first AS establishes a session with the first S-CSCF; otherwise, the current process ends; The second AS establishes a session with the second S-CSCF, and further includes: performing a security detection mechanism between the second AS and the second S-CSCF, and if the security detection mechanism passes, the second AS and the second S-CSCF Establish a session; otherwise, end the current process. 9. The method according to claim 1, wherein the step D further comprises: the first AS negotiates the service quality policy with the second AS through the first S-CSCF and the second S-CSCF, and determines the service quality parameters . 10. The method according to claim 1, further comprising: after step D, the second AS returns a response to the first AS through the second S-CSCF and the first S-CSCF. 11. The method according to claim 1, wherein the second AS is more than one AS. 12. The method according to claim 1, further comprising: the first S-CSCF triggers to the third-party AS according to the relevant service trigger conditions. 13. The method according to claim 12, wherein the trigger condition is configured in the first S-CSCF; or configured in the HSS signed by the first AS, and the first S-CSCF communicates with the HSS Interact to get the trigger condition.

Images