WO2009046674A1

WO2009046674A1 - Universal service open interface system and universal service open method

Info

Publication number: WO2009046674A1
Application number: PCT/CN2008/072573
Authority: WO
Inventors: Chenghui Peng; Jianjun Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-30
Filing date: 2008-09-27
Publication date: 2009-04-16
Also published as: CN101400109B; CN101400109A

Abstract

A USI system is disclosed. Said system comprises the service function interface and the policy control engine. Said service function interface receives the interface registration request of the service entity in CSN and stores the open interface information in said registration request. Said policy control engine receives the interface calling request and inquires whether service function interface stores the open interface information corresponding to the interface calling request; after the open interface information is obtained by inquiring, said policy control engine sends the interface calling request to the corresponding service entity in CSN. By employing said system, the open capability of WiMAX network is greatly improved and the function requirement for USI system is reduced.

Description

General business open interface system and general business open method

The present invention relates to the field of communication technologies, and in particular to business open technologies.

Background technique

WiMAX (Wor ldwide Interoperabi l ty for Microwave Acces s ), the Chinese name for global access to microwave interoperability, is a wireless metropolitan area network technology based on the IEEE 802.16 standard. The WiMAX network is mainly composed of three parts: client (MSS/SS), access service network (ASN) and connection service network (CSN). Among them, the connection service network includes various service entities, such as a prepaid server (PPS), an authentication, authorization and accounting server (AAA Server), a location server, and the like.

Along with the requirement of open network services, the WiMAX network also opens some of the services to the external network. The external entity can send various information query requests to the service entities inside the WiMAX network to obtain information in the internal business entities of the WiMAX network.

As shown in Figure 1, the WiMAX network provides a service interface to the application service provider/Internet application service provider (ASP/iASP) through the Common Service Open Interface (USI) system. The USI system is an interface for a WiMAX network to open service capabilities to third-party applications within or outside the network.

In this technology, the WiMAX network defines a new service interface through the USI system, and provides service interface capabilities, including user information, location information, and device information, through the new service interface, and has high requirements for the US I system. Its technology is difficult to implement.

In another technique, the US I service capability interface defined by the WiMAX network is only an open application programming interface standard X (OSA/Par lay X) interface to the 3GPP network open service framework/fixed or mobile telephone network. Mapping, opening the service capabilities of the WiMAX network through the open service capabilities of the 3GPP network, as shown in Figure 2. The ASP may be in the 3GPP network or outside the 3GPP network, calling the 0SA application programming interface (API) or the communication network open application programming interface standard (Parlay) API or Parlay X to use the open service capability of the WiMAX network. .

In this technology, the USI service capability interface is only the 3GPP network OSA/Par lay X interface. Mapping, can not support the direct call of other systems, WiMAX's service capability open interface is bound to the 3GPP network service capability open interface system, WiMAX network must be deployed simultaneously with the 3GPP network to open the service capability, thus limiting the WiMAX network service The ability to open interfaces to third-party applications.

Summary of the invention

The embodiment of the invention provides a WiMAX network universal service open interface system and a WiMAX network general service open method, which can improve the open capability of the WiMAX network.

The WiMA network general service open interface system (US I) provided by the embodiment of the present invention includes a service function interface and a policy control engine; wherein:

Receiving, by the service function interface, an interface registration request sent by the service entity in the connection service network CSN, and storing the open interface information included in the registration request;

The policy control engine receives an interface call request, and queries whether the open interface information corresponding to the interface call request is stored in the service function interface, and if the open interface information is queried, the interface call request is sent to the queried The open interface information corresponds to the business entity in the CSN.

The method for opening a general service of a WiMAX network provided by the embodiment of the present invention includes:

Receiving an interface registration request sent by the service entity in the WiMAX network CSN, and storing the open interface information included in the interface registration request;

Receiving an interface call request, querying whether the open interface information corresponding to the interface call request is stored, and if the open interface information corresponding to the interface call request is queried, sending the interface call request to the queried open The business entity corresponding to the interface information.

In the embodiment of the present invention, the interface registration request sent by the service entity in the WiMAX is received by the USI system, and the open interface information included in the interface registration request is stored, so that the service entity and the 0MA service in the ASP/iASP and the 3GPP are enabled. Components or other third-party applications can use the US I system to call the open service capability interface of the WiMAX network according to the open interface information registered in the USI system, which greatly improves the open capability of the WiMAX network.

Moreover, in the embodiment of the present invention, since the USI system does not need to separately define a service open interface, only Accepting the registration of the business entity reduces the functional requirements of the US I system and reduces the cost and difficulty of implementing the USI system.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

Figure 1 is a schematic diagram of the composition of the first prior art;

2 is a schematic diagram of the composition of a second prior art;

3 is a schematic structural diagram of a first embodiment of a USI system according to the present invention;

4 is a schematic diagram of the composition of a second embodiment of the USI system of the present invention;

Figure 5 is a schematic diagram showing the composition of a third embodiment of the USI system of the present invention;

6 is a flowchart of a first embodiment of a method for opening a general service of a WiMAX network according to the present invention; FIG. 7 is a flowchart of a second embodiment of a method for opening a general service of a WiMAX network according to the present invention; FIG. 9 is a flowchart of an exemplary embodiment of a method for opening a general service of a WiMAX network according to the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

First, a specific embodiment of the USI system provided by the present invention will be described.

The composition of the first embodiment of the USI system is as shown in FIG. 3. As can be seen from FIG. 3, in the solution of the embodiment of the USI system, the USI system 10 is set in the CSN11 of the WiMAX network, and the group of the USI system 10 The business function interface 101 and the policy control engine 102 are included.

The service function interface 101 is connected to the service entity 111 in the CSN 11, receives the interface registration request of the service entity 111 registered open interface in the CSN 11, and stores the open interface information included in the registration request. By receiving the above interface registration request and storing the open interface information in the interface registration request, the business entity 111 for the transmission interface registration request in the US I system 10 is registered to open the interface.

Specifically, the service function interface 101 may include an interface registration receiving module 1011 and an interface registration information storage module 1012. The interface registration receiving module 1011 is configured to receive an interface registration request that includes the open interface information sent by the service entity 111 in the CSN. The interface registration information storage module 1012 is configured to obtain the open interface information in the interface registration request, and store the open interface information.

The policy control engine 102 receives an interface call request for invoking the above-mentioned registered open interface, and interacts with the interface registration information storage module 1012 in the service function interface through the connection with the service function interface 101, and queries whether the service function interface stores the The received interface invokes the corresponding open interface information of the request. If yes, the request is sent to the corresponding service entity 111 in the CSN 11, that is, the service entity 111 of the queried open interface is registered with the USI system. Here, if the corresponding open interface information is not queried, the policy control engine 102 can further return a response to the failed call to the initiator of the interface call request.

Specifically, the policy control engine 102 may include an interface call receiving module 1021 and an interface query module 1022. The interface call receiving module 1021 is configured to receive an interface call request. The interface query module 1022 is configured to obtain an interface call request sent by the interface call receiving module, and query whether the interface registration information storage module 1012 stores the open corresponding to the interface call request through the connection with the interface registration information storage module 1012. The interface information, if the open interface information is queried, sends the interface call request to the service entity in the CSN corresponding to the queried open interface information.

In this embodiment, the service entity that initiates registration with the service function interface 101 may have one or more, and in the case that multiple service entities initiate registration with the service function interface 101, the service The function interface 101 can store multiple sets of open interface information, and the stored open interface information corresponds to the service entity. Open interface information can be described in a common XML language, which can include: interface type, interface method name, calling parameters, and policy called by the interface.

In this embodiment, the interface call request is a request from a service entity external to the WiMAX network or from a service entity within the WiMAX network to invoke the WD AX network interface. The interface call request includes the interface information related to the interface to be called. When the policy control engine 102 queries the service function interface 101 for the open interface information according to the interface call request, it determines whether the service function interface 101 exists and the call request. The open interface information that matches the interface information, if yes, the interface call request is legal, and the interface call request may be forwarded to the service entity corresponding to the open interface information that matches the interface information in the interface call request. When the forwarding interface invokes the request to the corresponding service entity, the interface call request may be forwarded to the corresponding service entity according to the policy invoked by the interface in the open interface information that matches the interface information in the interface call request.

The service entity in the CSN mentioned in this embodiment may be, for example, an AAA server or a location information server; and the interface control request received by the policy control engine may be, for example, an ASP/iASP, a service entity in the 3GPP network. , a business entity within the WiMAX network, a 0MA service enablement component, or other third-party application.

In this embodiment, only the USI system is set in the CSN as an example. In the specific implementation, the USI system may not be set in the CSN, or even in the WiMAX network, as long as it has the above two modules. . Similarly, in the following embodiments, the service function interface 101 and the policy control engine 102 in the USI system may not be disposed in the CSN or even in the WiMAX network.

In the second embodiment of the USI system, the USI system can further authenticate the interface registration request from the service entity to ensure the security of the interface registration. In addition, in this embodiment, the network operator can filter and open according to requirements. The service interface, and ensure that each open service interface complies with its established policies, such as billing policies, and can be integrated with the interfaces of third-party business entities. At the same time, the USI system can further authenticate the received interface call request to improve the WiMAX network. Security, to prevent system performance problems caused by a large number of illegal calls, and to prevent billing fraud. In this embodiment, the composition of the USI system is as shown in FIG. As shown in FIG. 4, in the embodiment, the service function interface 101 specifically includes an interface registration receiving module 101 1 , an interface registration information storage module 1012 , and an interface authentication module 101 3 . among them:

The interface registration receiving module 1011 is configured to receive an interface registration request sent by the service entity 111 in the CSN, where the registration request includes the authentication information of the registered entity and the information of the open interface requesting registration.

The interface authentication module 101 is connected to the interface registration receiving module 1011, and configured to receive an interface registration request sent by the interface registration receiving module 1011, and authenticate the registration entity and the open interface according to the authentication information of the registered entity, and determine the registration. Whether the entity and the open interface are licensed by the WiMAX network service provider, and if so, the authentication is passed; otherwise the authentication fails. If the authentication is passed, the interface authentication module 101 3 transmits the open interface information in the interface registration request to the interface registration information storage module 1012.

The interface registration information storage module 1012 is connected to the interface authentication module 1 013 for acquiring the open interface information from the interface authentication module 1013 and storing the open interface information.

In this embodiment, the policy control engine 102 specifically includes an interface call receiving module 1021 and an interface query module 1022 and an external authentication module 1023. among them:

The interface call receiving module 1021 is configured to receive an interface call request.

The external authentication module 1023 is configured to receive an interface call request from the interface call receiving module 1 021, and authenticate the initiator of the interface call request according to the content in the interface call request, and if the authentication passes, the interface call request Transfer to interface query module 1 022. The certification here can use common authentication methods, such as certification using a certificate. The present invention is not limited to a specific authentication method.

The interface query module 1022 is configured to obtain an interface call request from the external authentication module 1023, and query whether the interface registration information storage module 1012 stores the interface with the interface registration information storage module 1012 according to the interface call request. Invoking the open interface information corresponding to the request, if the open interface information is queried, sending the interface call request to the queried open The service entity 111 in the CSN corresponding to the interface information.

Here, in the interface call request, the interface information to be called is included, and the query whether to store the open interface information corresponding to the interface call request specifically includes: querying the interface registration information storage module

Whether the open interface information matching the interface information in the above interface call request is included in 1012.

In the third embodiment of the USI system, a USI gateway module is further provided in the USI system, and the module may be set in the CSN of the WiMAX network or in the 3GPP network connected to the WiMAX network. Through the setting of the USI network management module, the advantages of the USI system in the present invention are realized, and the solution with the least cost to the existing system is provided.

The structure of the USI system and the connection between the USI system and the WiMAX network and the 3GPP network in this embodiment are as shown in FIG. In the structure of the USI system, the functions of the other modules except the USI gateway module are the same as those of the third embodiment. The USI gateway module is used to complete the service open interface of the target network, that is, the protocol conversion between the 3GPP network service open interface and the USI system in this embodiment.

The above is a description of the US I system embodiment, and the following is further explained by several specific embodiments for the WiMAX network general service opening method.

The process of the first embodiment of the WiMAX network common service opening method is as shown in FIG. 6, and includes the following steps:

Step 601: Receive an interface registration request sent by the service entity in the WiMAX network CSN, and store the open interface information that is requested to be registered in the interface registration request.

Here, one or more service entities in the CSN may perform interface registration. In this step, the stored open interface information may correspondingly include one or more groups. The stored open interface information includes an interface type and an interface parameter, or may further include a policy and an interface method name invoked by the interface.

Step 602: Receive an interface call request, and query whether the open interface information corresponding to the interface call request is stored. If the open interface information corresponding to the interface call request is stored, the interface call request is sent to the corresponding service. entity.

In this step, the interface call request may include an interface type and an interface parameter that are requested to be called. If the interface information is used to query whether the open interface information corresponding to the interface call request is stored, whether the open interface information stored in the query matches whether the set of open interface information matches the interface information in the interface call request, such as determining the interface. Whether the type, interface name, and other parameters match, and if so, the interface call request is sent to the business entity that registered the open interface of the group.

The interface invokes the interface information in the request, and the originator of the request may sign a service level agreement with the WiMAX service provider in advance or the WiMAX service provider informs the initiator in other manners, so that the initiator can know The interface information is set in the interface call request. Other ways here can be to provide paper, fax, or publicly released industry standards, corporate standards, and more.

The technical solution of this embodiment can be implemented by the above US I system. In addition, the service entity in the CSN in this embodiment and the following embodiments may be an AAA server or a location information server, and the interface call request may be a service entity from an ASP/iASP or a 3GPP network. , a business entity within the WiMAX network, a 0MA service enablement component, or other third-party application.

In a second embodiment of the WiMAX network general service open method, the interface registration request from the service entity can be authenticated to ensure the security of the interface registration. The process of this embodiment is shown in FIG. 7, and specifically includes the following steps:

Step 701: Receive an interface registration request sent by a service entity in a WiMAX network CSN, and perform authentication on the interface registration request. If the authentication is passed, perform step 702; otherwise, directly terminate the process, or return a response failure of the interface registration to the service entity. , end this process.

In this step, the interface registration request may include the authentication information of the registered entity and the open interface information that is requested to be registered. The authentication of the received interface registration request includes: according to the authentication information of the registered entity in the interface registration request, Determine whether the registered entity and the open interface are licensed by the WiMAX network service provider. If yes, the authentication passes; otherwise, the authentication fails.

Step 702: Store open interface information included in the interface registration request. In this step, the response of the successful registration of the interface may be further returned to the business entity.

Step 703: Receive an interface call request from a non-WiMAX network, and query that the request has been stored. After the corresponding open interface information is sent, the interface call request is sent to the service entity corresponding to the queried open interface information.

After step 703, an interface call response returned by the service entity according to the interface call request may also be received, and the response is sent to the initiator of the interface call request.

In the third embodiment of the WiMAX network general service open method, the interface call request may also be authenticated to improve the network security of the WiMAX. The process of this embodiment is as shown in FIG. 8, and specifically includes the following steps:

Step 801: Receive an interface registration request sent by a service entity in a WiMAX network CSN, and perform authentication on the interface registration request. If the authentication is passed, perform step 802; otherwise, directly terminate the process, or return a response failure of the interface registration to the service entity. , end this process.

Step 802: Store open interface information included in the interface registration request. In this step, the response of the successful registration of the interface may be further returned to the business entity.

Step 803: Receive an interface call request, perform authentication on the interface call request, and if the authentication is passed, perform step 804; otherwise, directly end the process, or directly return the process after the interface call failure response is returned to the initiator of the interface call request. .

Step 804: Query whether the corresponding open interface information is stored according to the interface information in the received interface call request. If yes, execute step 805, and send the interface call request to the service entity corresponding to the queried open interface information. Then, the process ends; otherwise, step 806 is executed to return an interface call failure response to the initiator of the interface call request, and then the process ends.

After step 805, before ending the process, the service entity may also receive an interface call response returned by the service entity according to the interface call request, and send the response to the initiator of the interface call request.

In this embodiment and the foregoing method embodiments, the stored open interface information may include an interface type, an interface method name, and a call parameter. In addition, the open interface information may further include a policy invoked by the interface, and in the foregoing step 805, when the interface call request is sent to the service entity in the CSN, the policy of the interface call in the found open interface information is executed. Send an interface call request to the corresponding business entity. In addition, in this embodiment and the foregoing embodiments, after receiving the interface call request, the service entity in the CSN may perform the interface call request for authentication, and if the authentication passes, perform corresponding service processing, for example, for the query request. , get the information to be queried, and return the processing result by calling the response through the interface. Here, in the case that the service processing involves the user's private data, the business entity in the CSN can also interact with the user, and after the user's permission is obtained, the processing is continued, and after the processing is completed, the response is returned through the interface call response. The certification here can use a common authentication method, such as certificate authentication. The invention does not limit the specific authentication method.

The following is a detailed description of an embodiment of the WiMAX network general service open method by way of a specific example.

As shown in FIG. 9, the entities involved in this embodiment include: a mobile terminal (MS), an ASN, an AAA server, a location information server (LS), a USI system, and an ASP/iASP. The specific steps of these entities are as follows: :

Step 901: The LS sends an interface registration request (reques t WS b ind ing ) to the USI system. The interface registration request includes the authentication information of the LS and the interface information for requesting registration. The interface information requesting registration may include the interface type, the policy invoked by the interface, the interface name, and the interface parameters.

In step 902, the USI system authenticates the LS and the open interface according to the authentication information of the LS in the interface registration request. After the authentication is passed, the open interface information in the interface registration request is stored, and the interface registration success response is returned to the LS (b inding succes s).

Similarly, in step 903, the AAA server sends an interface registration request (reques t WS/Par layX bind ing) to the US I system, where the request includes the authentication information of the AAA server and the open interface information requesting registration.

In step 904, the USI system authenticates the AAA server and the open interface according to the authentication information of the AAA server in the interface registration request. After the authentication is passed, the open interface information in the interface registration request is stored, and the interface registration success response is returned to the AAA server. (b inding succes s).

After the registration is completed, a third-party application such as ASPAASP can initiate an interface call to the above two servers through the USI system, such as: In step 905, the ASP/iASP first sends an interface call request (Reql) for querying the user information to the USI system, where the request includes interface information such as the interface type and interface parameters requested to be called. For example, the information may include: ASP/iASP authentication information, the name of the interface to be invoked, such as reque st locat ion, and interface parameters such as user identifier.

In step 906, after receiving the Req1, the USI system performs access policy control, including authenticating the request and querying whether the corresponding open interface information is stored. If the authentication passes and queries the corresponding open interface information, step 907 is performed.

Step 907: Execute the policy invoked by the interface in the queried open interface information, and forward the Reql to the AAA server.

Step 908: The AAA server performs access authentication on Req1. If the authentication is passed, step 909 is performed to perform user information update with the ANS, MS, LS, etc., and then, in step 910, the requested user information is carried in the user information query response. (respl) is returned to the ASP/1 ASP that initiated the request through the USI system.

In step 911, ASP/iASP sends an interface call request (req2) for querying the user location information to the USI system, and includes interface information such as the interface type and interface parameters requested to be called in req2. For example, the specifics may include: The interface type is Par lay X, and the interface parameter may be a parameter defined by the Par lay X protocol.

In step 912, after receiving the Red2, the USI system performs access policy control, including authenticating the request and querying whether the corresponding open interface information is stored. If the authentication is passed, and the corresponding open interface information is queried, step 913 is performed.

Step 913: Execute the policy invoked by the interface in the open interface information that is queried, and forward the Req2 to the LS.

Step 914: The LS performs access authentication on Req2. If the authentication is passed, step 915 is performed to acquire user location information by interacting with ANS, MS, etc. Finally, in step 916, the requested user location information is carried in the user information query response (resp2). Returned to the ASP/iASP that initiated the request through the USI system.

In the above embodiments, the internal processing of the WiMAX network, such as the AAA server and the MS, is involved. For information about how to obtain user information and how to obtain user location information through interaction between the LS and the MS, refer to the related technical specifications of the WiMAX AAA server or LS that have been disclosed, or the specific implementation schemes of different devices and software vendors. Said.

In the foregoing embodiment of the present invention, the interface registration request sent by the service entity in the WiMAX is received by the USI system, and the open interface information included in the interface registration request is stored, so that the ASP/i ASP and the service entity and the 0MA service in the 3GPP are The enabling component or other third-party application can use the USI system to call the open service capability interface of the WiMAX network according to the open interface information registered in the USI system, which greatly improves the open capability of the WiMAX network.

Moreover, in the embodiment of the present invention, since the USI system does not need to separately define the service open interface, it only needs to accept the registration of the service entity, which reduces the functional requirements of the US I system, and also reduces the cost and implementation difficulty of the USI system.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above is a description of specific embodiments of the present invention, and the method of the present invention may be appropriately modified in a specific implementation process to suit the specific needs of a specific situation. Therefore, it is to be understood that the specific embodiments of the present invention are not intended to limit the scope of the invention.

Claims

Claim

A global microwave access interoperability WiMAX network general service open interface system USI, wherein the USI system comprises: a service function interface (101) and a policy control engine (102); wherein the service function interface (101) receiving an interface registration request sent by the service entity (111) in the connection service network CSN (11), and storing the open interface information included in the registration request;

The policy control engine (102) receives an interface call request, and queries whether the open interface information corresponding to the interface call request is stored in the service function interface (101), and if the query has been stored, the corresponding interface call request is stored. After the interface information is opened, the interface call request is sent to the service entity (111) in the CSN (11) corresponding to the queried open interface information.

The USI system according to claim 1, wherein the service function interface includes: an interface registration receiving module (1011) and an interface registration information storage module (1012);

The interface registration receiving module (1011) is configured to receive an interface registration request that includes the open interface information sent by the service entity (111) in the CSN (1 l);

The interface registration information storage module (1012) is configured to obtain the open interface information in the interface registration request, and store the open interface information.

The USI system according to claim 2, wherein the service function interface (101) further comprises:

The interface authentication module (1013) is configured to obtain the interface registration request from the interface registration receiving module, and perform authentication on the interface registration request. If the authentication is passed, the open interface information in the interface registration request is transmitted to the interface registration. Information storage module.

The USI system according to claim 1, wherein the policy control engine (102) comprises: an interface call receiving module (1021) and an interface query module (1022), wherein

The interface calls a receiving module (1021) for receiving an interface call request;

The interface query module (1022) is configured to obtain the interface call request, and query whether the open interface information corresponding to the interface call request is stored in the service function interface (101), and if the open interface information is queried, Sending the interface call request to the queried open interface information corresponding to Business entity (111) in CSN (11).

The USI system according to claim 4, wherein the policy control engine (102) further comprises:

An external authentication module (1023), configured to receive the interface call request from the interface call receiving module (1021), perform authentication on the request, and if the authentication passes, transmit the interface call request to the interface query module (1022).

The US I system according to claim 1, wherein the system further comprises: a USI gateway module, configured to connect a service open interface of the non-WiMAX network with the policy control engine, and complete service opening of the non-WiMAX network Protocol conversion between the interface and the USI system.

A method for opening a general service of a WiMAX network, the method comprising: receiving an interface registration request sent by a service entity in a WiMAX network CSN, and storing the open interface information included in the registration request of the interface;

The method according to claim 7, wherein, after receiving the interface registration request, the method further comprises: performing authentication on the received interface registration request, and if the authentication is passed, executing the storing the interface registration request The steps to include open interface information.

The method according to claim 8, wherein the interface registration request includes: authentication information of the registration entity and open interface information for requesting registration;

The authenticating the received interface registration request includes:

And determining, according to the authentication information of the registered entity in the interface registration request, whether the registered entity and the open interface are permitted by the WiMAX network service provider, and if yes, the authentication is passed.

The method according to claim 7, wherein, after receiving the interface call request, the method further includes: performing authentication on the initiator of the request, and if the authentication is passed, executing the open interface information corresponding to the query step.

The method according to claim 7, wherein the querying whether the interface information corresponding to the interface call request has been stored includes:

Query whether the stored open interface information includes open interface information that matches the interface information in the interface call request.

The method according to claim 11, wherein the stored open interface information includes: a policy invoked by an interface;

The sending the interface call request to the corresponding service entity includes:

And sending, according to the policy invoked by the interface in the matched open interface information, the interface call request to the corresponding service entity.

The method according to claim 7, wherein, after the sending the interface call request to the service entity in the CSN corresponding to the queried open interface information, the method further includes: receiving the service entity in the CSN The response returned by the interface call request is returned and returned to the originator of the interface call request.

The method according to claim 7, wherein the service entity further includes: after receiving the interface call request:

The service entity authenticates the interface call request, and if the authentication passes, performs corresponding service processing, and returns a request processing result through an interface call response.

The method according to claim 14, wherein when the interface call request involves user data, the performing corresponding service processing includes:

Interact with the user, confirm whether the requested information can be returned, and if the user confirms that it can return, the interface call response returns the information requested by the interface call request.

The method according to claim 7, wherein the interface call request comprises: an interface call request for querying user information or an interface call request for querying user location information.

The method according to any one of claims 7, 10 or 13, wherein the initiator of the interface call request comprises: ASP/i ASP, a service entity in a 3GPP network, an 0MA service enabling component, A business entity or other third-party application within the WiMAX network.