WO2019223638A1 - 一种api信息传输方法及装置 - Google Patents

一种api信息传输方法及装置 Download PDF

Info

Publication number
WO2019223638A1
WO2019223638A1 PCT/CN2019/087567 CN2019087567W WO2019223638A1 WO 2019223638 A1 WO2019223638 A1 WO 2019223638A1 CN 2019087567 W CN2019087567 W CN 2019087567W WO 2019223638 A1 WO2019223638 A1 WO 2019223638A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
terminal
request
network
information
Prior art date
Application number
PCT/CN2019/087567
Other languages
English (en)
French (fr)
Inventor
朱强华
阎亚丽
朱奋勤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019223638A1 publication Critical patent/WO2019223638A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and a device for transmitting API information.
  • SCEF service capability open function network elements
  • APIs application programming interfaces
  • SCEF Service capability open function network elements
  • Figure 1 shows an example of a SCEF architecture.
  • Third-party applications can obtain the terminal's related information by calling the API in SCEF.
  • the network open function network element can also open 5G network functions to third-party applications through APIs, that is, third-party applications. You can obtain the related information of the terminal by calling the API in NEF.
  • the terminal may switch between 4G and 5G, resulting in third party applications being unable to provide business services to the terminal, resulting in poor user experience .
  • the present application provides an API information transmission method and device, so as to avoid a situation in which a terminal cannot access an API that is not compatible with a network type, and a business service cannot be provided for a third-party application.
  • this application provides an API information transmission method, which includes:
  • the first network device receives a first request sent by a second network device, where the first request includes an identifier of a terminal or an identifier of a terminal group, and the first request is used to request API information of a third network device.
  • the first network device sends first instruction information to the second network device, the first instruction information includes API information, the API information is determined according to a network type accessed by the terminal, or is determined according to a network type accessed by the terminal group .
  • the second network device can obtain the API information determined according to the network type that the terminal or terminal group accesses, which helps to prevent the second network device from calling the terminal when it provides business services to the terminal.
  • APIs with inconsistent network types may lead to situations in which terminal-related information may not be obtained, and business services may not be provided for the terminal. Therefore, the foregoing embodiment is beneficial to improving the user experience.
  • the foregoing method further includes: the first network device acquires a network type currently accessed by the terminal or terminal group, and then the first network device determines API information according to the acquired network type.
  • the first network device when the first network device acquires the type of the network currently accessed by the terminal or terminal group, it may be obtained by receiving second instruction information sent by the third network device, where the second instruction information includes the terminal Or the type of network the terminal group is currently connected to.
  • the third network device may query the network type currently accessed by the terminal or terminal group, and the third network device sends the queried network type to the first network device, so that the first network device determines the API information according to the network type.
  • the first network device may send a second request to the third network device, where the second request includes an identifier of a terminal or an identifier of a terminal group.
  • the second request may be used to request to obtain a network type that the terminal or terminal group accesses, or may also be used to request a third network device to report to the first when the network type that the terminal or terminal group accesses changes.
  • the network device sends the type of network to which the terminal or terminal group is currently connected.
  • the first network device may query the network type currently accessed by the terminal or terminal group or the network type currently accessed by the long-term subscription terminal or terminal group according to actual needs, so as to determine the corresponding API information conveniently.
  • the foregoing method further includes: receiving, by the first network device, third indication information sent by a third network device, where the third indication information includes the API information.
  • the first network device can receive the API information sent by the third network device, and it is no longer necessary for the first network device to determine the API information according to the network type accessed by the terminal or terminal group, reducing the first network device. Load.
  • the method before the first network device receives third instruction information sent by a third network device, the method further includes: the first network device sends a third network device to the third network device. Three requests; the third request is used to request to obtain API information determined according to the network type accessed by the terminal or the terminal group; or the third request is used to request that when the API information changes, Sending the API information to the first network device.
  • the first network device can request to obtain the current API information, and also request the third network device to send the API information when the API information transmission changes, which can flexibly meet the needs of different scenarios.
  • the first request is used to request to obtain the API information, and the first indication information is carried in a response message to the first request; or, the first request is used to When the request changes, the API information is sent to the second network device.
  • the second network device may query the current API information or the long-term subscription API information according to actual needs, so as to facilitate the API call.
  • an embodiment of the present application provides a first network device, which includes a processor, a memory, and a communication interface.
  • the memory is used to store a program.
  • the processor calls a program stored in the memory and executes the program through the communication interface. The process performed by the first network device in the method according to any one aspect.
  • an embodiment of the present application provides a third network device, including a processor, a memory, and a communication interface.
  • the memory is used to store a program.
  • the processor calls a program stored in the memory and executes the program through the communication interface. The process performed by the third network device in one aspect.
  • an embodiment of the present application provides a communication system including the first network device described in the second aspect and the third network device described in the third aspect, or may include the first network device described in the second aspect The network device and the third network device according to the fourth aspect.
  • an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and when the instructions are run on a computer, the computer is caused to execute any one of the first aspects Item.
  • an embodiment of the present application provides a chip system, including: a processor, configured to support a communication device to implement the method according to any one of the foregoing first aspects.
  • FIG. 1 is a schematic diagram of an SCEF architecture according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a 5G network architecture according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a 4G and 5G network architecture provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of SCEF + NEF functions provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a network architecture including a CAPIF network element according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of an API information transmission method according to an embodiment of the present application.
  • FIG. 7 is a second schematic flowchart of an API information transmission method according to an embodiment of the present application.
  • FIG. 8 is a third schematic flowchart of an API information transmission method according to an embodiment of the present application.
  • FIG. 9 is a fourth schematic flowchart of an API information transmission method according to an embodiment of the present application.
  • FIG. 10 is a fifth schematic flowchart of an API information transmission method according to an embodiment of the present application.
  • FIG. 11 is a sixth schematic flowchart of an API information transmission method according to an embodiment of the present application.
  • FIG. 12 is one of a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 13 is a second schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 14 is a third schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 3 exemplarily shows a schematic diagram of a network system architecture.
  • EPC evolved packet core network
  • SCEF services capability server
  • AS application server
  • third-party applications can obtain information about the terminal from the EPC through SCEF.
  • 5GC 5th generation communication core network
  • AF application functions
  • third-party applications can obtain information about the terminal from the 5GC through NEF .
  • SCEF + NEF network elements with open capabilities
  • SCEF + NEF network equipment with SCEF function modules and NEF function modules
  • SCEF + NEF can provide two types of APIs for third-party applications. Way to achieve, as shown in Figure 4.
  • SCEF and NEF can provide their own APIs, that is, 4G network APIs and 5G network APIs, respectively.
  • an enhanced API can be provided on SCEF, and the request is forwarded to NEF when a 5G network API call request is received; or an enhanced API can be provided on NEF, and a 4G network API is received Forward the request to SCEF when invoking the request; or, for SCEF + NEF, you can also set in SCEF + NEF a module that can only serve 4G networks, a module that can only serve 5G networks, and a module that can serve 4G and The 5G network provides a service module. After receiving a 4G or 5G network API call request, it transmits the request to the corresponding module for processing.
  • the third-party application is not clear about the network changes of the terminal access.
  • the terminal switches from 5G to 4G, if the AF still requests to call the API in NEF, it may not be able to obtain the terminal information, or when the terminal switches from 4G After switching to 5G, if you still request to call the API in SCEF, you may not be able to obtain terminal information.
  • an embodiment of the present application provides a network architecture including a CAPIF network element, as shown in FIG. 5, where the CAPIF network element can communicate with an open capability network element and a third-party application.
  • the CAPIF network element can communicate with an open capability network element and a third-party application.
  • third-party applications can request CAPIF to provide API information to prevent third-party applications from calling unavailable APIs when they request API calls.
  • FIG. 6 is a schematic flowchart of an API information transmission method according to an embodiment of the present application. As shown in the figure, the method may include the following steps:
  • Step 601 The first network device receives a first request sent by a second network device.
  • the first request is used to request to obtain API information of the third network device.
  • the first request may include a terminal identifier, that is, the first request is used to request acquisition of terminal-level API information, or the first request may include a terminal group identifier, that is, the first request is used to request acquisition of a terminal. Group-level API information.
  • Step 602 The first network device sends first instruction information to the second network device, where the first instruction information includes API information.
  • the API information may be an identifier of an available API, so as to indicate that the second network device may call an API corresponding to the API identifier.
  • the API information may also be an unavailable API identifier, to indicate that the second network device is unavailable to call an API corresponding to these API identifiers.
  • the API information may further include an API identifier and status information of the API.
  • the status information of the API may be used to indicate availability or unavailability.
  • the status information of the API can be used to indicate suspended or resumed, where suspended indicates that it is temporarily unavailable. For example, when a terminal falls from a 4G network to a 2G network due to a call, the terminal's 4G network session and The related bearer will be suspended.
  • the status information of the API can also be used to indicate service level information.
  • API_1 can serve terminals that access EPC, the corresponding level is 1, API_2 can serve terminals that access 5GC, the corresponding level is 2, and API_3 can serve The terminal accessing the 5GC or EPC has a corresponding level of 3; so that the second network device can determine the available API according to the service level of the API.
  • the API information included in the first indication information is determined according to the type of network to which the terminal corresponding to the terminal identifier is connected; when the first request includes a terminal group identifier, then The API information included in the first instruction information is determined according to the type of network to which the terminals included in the terminal group are connected.
  • the second network device may obtain API information related to each terminal separately when there are a small number of terminal service requirements, that is, each first request includes the identity of one or more terminals; for example, the second network The device may also request API information about one or more terminal groups when there is a large number of terminal business requirements, that is, each first request may include the identity of one or more terminal groups.
  • the type of network accessed by the terminal can be the type of core network (CN) that the terminal accesses, such as 5GC, EPC, EPC, and 5GC, non-5GC (Non-5GC), 5G, 4G, 3G, and non-5G ( Non-5G) and other 3GPP core network types or combinations thereof.
  • the type of core network that a terminal accesses can be 5GC or EPC, or, for a terminal that can register on both a 4G network and a 5G network, the type of core network that it accesses can also be 5GC and EPC.
  • the type of network accessed by the terminal can also be one or a combination of the following: universal terrestrial radio access network (UTRAN), code division multiple access (CDMA) 2000, global mobile communication system wireless Access network (GSM / EDGE radio access network, GERAN), long term evolution (LTE), 5G new air interface (NR), evolved UTRAN, next generation radio access network (next generation radio access network) , NG-RAN) and other 3GPP radio access technology (radio access technology, RAT) types.
  • UTRAN universal terrestrial radio access network
  • CDMA code division multiple access
  • GSM / EDGE radio access network GSM / EDGE radio access network
  • GERAN global mobile communication system wireless Access network
  • LTE long term evolution
  • NR 5G new air interface
  • evolved UTRAN next generation radio access network
  • next generation radio access network next generation radio access network
  • NG-RAN next generation radio access network
  • RAT radio access technology
  • a terminal group includes multiple terminals, and the types of core networks accessed by the multiple terminals may be the same or different. Therefore, in the API information determined according to the network type accessed by the terminal group, when all terminals in the terminal group access the same network type, the access network type of this terminal group is the access network type of the terminal; when When the network types of the terminals in the terminal group are not the same, the access type of this terminal group is a combination of the access network types of all terminals; for example, if all the terminals in the terminal group are connected to the EPC, the terminal group is connected.
  • the type of the incoming network is EPC. If some terminals access the EPC and some terminals access the 5GC, the network type that the terminal group accesses is EPC + 5GC.
  • the first network device may be a 3GPP common API framework (common API framework for 3GPP northbound APIs, CAPIF) core function network element.
  • the second network device may be a network element such as a service capability server (SCS) or an application server (AS) in a 4G network, or may be an application function (AF) in a 5G network And other network elements, or network element equipment that can be used to support third-party applications in other communication networks in the future.
  • the third network device may be SCEF or NEF, or may also be a network device (hereinafter referred to as SCEF + NEF) in which SCEF and NEF are co-located.
  • the third-party application may need to obtain relevant information about the terminal from the core network (EPC, 5GC, etc.) accessed by the terminal when providing business services to the terminal. If the terminal has already switched to the network, the third-party application still has If you call the API in the network before the switch to obtain the terminal information, you may not be able to obtain the required information, and thus may not be able to serve the terminal through business services.
  • the second network device can obtain the API information determined according to the network type accessed by the terminal or terminal group, which helps to prevent the second network device from calling the terminal when providing business services to the terminal. APIs of different network types may lead to situations in which terminal-related information may not be obtained, and thus may not be able to provide business services to the terminal. Therefore, the foregoing embodiment is beneficial to improving the user experience.
  • the first request in step 601 may be used to request API information.
  • the second network device may receive a service request, or when a preset timer expires, or receive
  • a first request is sent to the first network device, such as a service discovery request (service discovery request), to obtain the current API information.
  • the first network device obtains the current API information and sends it to the second network device.
  • the first network device may also change the API information after the API information changes according to the protocol or different business requirements. , Sending the changed API information to the second network device.
  • the first request may also be used to request that the API information be sent to the second network device when the API information sending changes.
  • the second network device may send an event subscription request (event subscribe request) to the first network device.
  • the request may include event indication information, and a terminal identifier or terminal group identifier.
  • the event indication information indicates the event for which the subscription is requested. Events for API information changes.
  • the first network device executes the foregoing step 602 again.
  • the API information can be related to the type of network accessed by the terminal or terminal group.
  • the status information of the API may change.
  • the terminal access The API available at EPC may be different from the API available at 5GC.
  • a change in the network type of one or more terminals included in the terminal group may cause changes in the API information corresponding to the terminal group.
  • the information of the API can also be related to other factors, such as the service type of the terminal. When the service type of the terminal changes, the status information of the API may change. As a result, some APIs are unavailable, or new APIs are added.
  • the first network device may request to subscribe to the information change event related to the API information, and determine whether the API information has changed after receiving the subscription event report.
  • the first network device may also periodically query the information related to the API information, and determine whether the API information has changed.
  • the API information included in the first indication information is determined by the first network device according to the type of network to which the terminal or terminal group currently accesses. For example, if the first network device obtains that the network currently accessed by terminal A is an EPC, the first network device may determine that the API in SCEF is an available API, that is, a third-party application may call the API in SCEF to obtain related information of terminal A In addition, if there are APIs common to SCEF and NEF, the first network device may also determine that these common APIs are available APIs.
  • the first network device may determine that the API in NEF is an available API, that is, a third-party application may call the API in NEF to obtain the relevant information of terminal B.
  • the first network device may also determine these common APIs as APIs that can be used.
  • the first network device may obtain the network type currently accessed by the terminal or terminal group in the following four ways:
  • Manner 1 The first network device sends a request to the third network device, requesting to obtain the network type currently accessed by the terminal or terminal group. After receiving the above request, the third network device sends the network type currently accessed by the terminal or terminal group to the first network device. Optionally, after the above step 601, the first network device may send a request to the third network device to obtain a network type.
  • the first network device may send a core network type query request (CN type query request) to the third network device.
  • the request may include the identity of the terminal, that is, the request Obtain the type of core network accessed by the terminal; the request may also include the identity of the terminal group, that is, the type of core network accessed by the terminal included in the terminal group is requested.
  • the third network device After acquiring the core network type accessed by the terminal or terminal group, the third network device sends a core network type query response (CN type query response) to the first network device, and the response includes the obtained core network type.
  • CN type query response core network type query response
  • the third network device may obtain the network type that the terminal or terminal group accesses from other network elements in the core network.
  • the third network device may interact with the access and mobility management function (AMF), policy control function (PCF), or unified data management (UDM) in the 5GC.
  • AMF access and mobility management function
  • PCF policy control function
  • UDM unified data management
  • Network elements communicate to obtain the type of core network that the terminal or terminal group accesses; or the third network device can also communicate with the mobility management entity (MME) and serving GPRS support node in the EPC (SGSN), home subscriber server (HSS), or policy and charging rules function (PCRF), etc., to communicate with each other to obtain the core network type that the terminal or terminal group accesses; in addition
  • MME mobility management entity
  • HSS home subscriber server
  • PCRF policy and charging rules function
  • Method 2 The first network device sends a request to the third network device, requesting that the third network device send the first network device the type of the network currently accessed by the terminal or terminal group when the type of the network accessed by the terminal or terminal group changes. That is, the first network device requests to subscribe to a network type change event that the terminal or terminal group accesses. After the third network device receives the above request, when it is found that the type of the network accessed by the terminal or the terminal group is changed, it sends instruction information to the first network device to indicate that the terminal or the terminal group is currently connected. Network type.
  • the first network device may send an event subscription request (event subscribe request) to the third network device, and the request may include event indication information, and a terminal identifier or a terminal group identifier; wherein the event indication information indicates the event for which the subscription is requested Network type change event for a terminal or terminal group access.
  • the third network device sends the subscription event report to the first network device after obtaining the information that the terminal or the terminal group accesses the changed network type.
  • the report may include the terminal identifier or terminal group identifier, and the currently accessed network. Types of.
  • the first network device may send a request to the third network device, so that the third network device generates the current network type to the third network device when the type of the network accessed by the terminal or terminal group changes.
  • First network equipment For example, the first network device may send an event subscription request (for requesting a network) to a third network device after receiving an event subscription request (for requesting changed API information when the API information changes) sent by the second network device. Send the current network type when the type changes).
  • the first network device may also actively send a request to the third network device, so that the third network device sends the current network type to the first network device when the network type accessed by the terminal or terminal group changes.
  • the first network device may also send the above-mentioned request for subscribing to a network type change event to the third network device when providing other business services and needs to obtain a network type accessed by the terminal or terminal group.
  • the method for the third network device to obtain the network type that the terminal or terminal group accesses is similar to that in the first method, and is not repeated here.
  • the third network device After determining that the type of the network accessed by the terminal or terminal group has changed, the third network device sends the identifier of the terminal or terminal group with the changed network type and the current network type to the first network device.
  • the first network device may store the identifier of the terminal or terminal group corresponding to the network type, so that when a request for acquiring API information sent by the second network device is received thereafter, the API information may be determined according to the network type of the stored terminal or terminal group, No need to query the third network device.
  • the first network device may send a request to obtain the network type that the terminal or terminal group accesses, and the third network device may according to the protocol or different service requirements, after the network type that the terminal or terminal group accesses changes And sending the changed network type to the first network device.
  • the method for the third network device to obtain the network type accessed by the terminal or terminal group is similar to that in the second method.
  • the first network device may store the received identifier of the terminal or terminal group in correspondence with the network type.
  • the third network device may actively send the changed network type to the first network device when the network type accessed by the terminal or terminal group changes.
  • the method for the third network device to obtain the network type accessed by the terminal or terminal group is similar to that in the first method.
  • the first network device may store the received identifier of the terminal or terminal group in correspondence with the network type.
  • the API information included in the first indication information may also be obtained by the first network device from a third network device.
  • the first network device may also obtain API information in three ways:
  • Method 1 The first network device sends a request to the third network device, requesting to obtain API information determined according to the type of network to which the terminal or terminal group is currently connected. After receiving the request, the third network device obtains the current network type of the terminal or terminal group, determines the current API information according to the obtained network type, and then sends the determined API information to the first network device.
  • the method for the third network device to obtain the network type accessed by the terminal or terminal group is similar to the foregoing embodiment.
  • Manner 2 The first network device sends a request to the third network device, requesting to send the current API information to the first network device when the API information changes.
  • changes in the API information may be caused by changes in the type of network accessed by the terminal or terminal group, or they may be caused by factors such as terminal service types or network function adjustments.
  • the third network device may subscribe to an information change event related to the API information, and determine whether the API information has changed after receiving the subscription event report, or may also periodically query the information related to the API information, and Determine if API information has changed.
  • the third network device may subscribe to an information change event related to the network type that the terminal or terminal group accesses, and after receiving the subscription event report, obtain the current network type that the terminal or terminal group is connected to, and determine whether the API information is Changes occur, or you can periodically query information related to the type of network that the terminal or terminal group accesses, obtain the type of network that the terminal or terminal group currently accesses, and determine whether the API information has changed.
  • the third network device sends the terminal or terminal group identifier and the changed API information to the first network device.
  • the first network device may store the received terminal or terminal group identifier corresponding to the API information, so that when a request for acquiring API information sent by the second network device is received thereafter, the corresponding API information may be read from the memory and sent to the The second network device without having to query the third network device.
  • the first network device may send a request to obtain the API information determined according to the type of network the terminal or terminal group is currently connected to.
  • the third network device may, according to the protocol or different business requirements, after the API information changes, Send the changed API information to the first network device.
  • the manner in which the third network device determines whether the API information is changed is similar to that in manner two.
  • the first network device may store the received terminal or terminal group identifier in correspondence with the API information.
  • the third network device may also actively send the changed API information to the first network device when determining that the API information transmission changes.
  • the third network device may subscribe to information change events related to the network type that the terminal or terminal group accesses, and after receiving the subscription event report, obtain the current network type that the terminal or terminal group is connected to, and determine whether API information occurs
  • the API information transmission method provided in the embodiment of the present application may include the steps shown in FIG. 7:
  • Step 701 In the initialization phase, the capability open network element (NEF, SCEF, or SCEF + NEF) sends a service publication request (service publication request) to the CAPIF, and the request may include a service name (service name).
  • NEF capability open network element
  • the above request may also include the core network type (CN type) corresponding to the service name, for example, service item 1 is provided by EPC, service item 2 is provided by 5GC; when the capacity open network element is In NEF or SCEF, the CN request type may not be carried in the above request.
  • CAPIF can determine the CN type based on the NEF or SCEF identifier carried in the request. For example, the CN type corresponding to the NEF identifier is 5GC and the CN type corresponding to SCEF is EPC.
  • Step 702 The CAPIF saves registration information, such as the terminal or terminal group identifier, the service name, and the core network type.
  • Step 703 The third-party application (AF, SCS, or AS) sends an event subscription request to the CAPIF.
  • the request may include service API capability information (service availability APIs) and the terminal or terminal group identifier.
  • the service API The capability information is used to indicate the subscription service API information change event, that is, to request the CAPIF to send the current API information to the third-party application when the API information changes.
  • Step 704 The CAPIF sends an event subscription request or a monitoring request to the capability-open network element.
  • the request includes core network type change information (CN type change) and a terminal or terminal group identifier.
  • the core network type change information is used In the event of indicating a change in the type of core network subscription, that is, the requesting open network element sends the current core network type to the CAPIF when the core network type accessed by the terminal or terminal group changes.
  • Step 705 The capability open network element monitors a core network type change event. Specifically, the capability open network element can monitor whether the core network type accessed by the terminal or terminal group is changed from AMF, MME, SGSN, PCF, PCRF, PCF + PCRF, HSS, UDM, or HSS + UDM.
  • Step 706 After detecting that the core network type changes, the capability open network element sends a subscription event report or monitoring response (monitoring response) or other indication information to the CAPIF, and identifies the terminal or terminal group identification, core network type change indication information, and / Or notify the CAPIF of the changed core network type.
  • a subscription event report or monitoring response (monitoring response) or other indication information to the CAPIF, and identifies the terminal or terminal group identification, core network type change indication information, and / Or notify the CAPIF of the changed core network type.
  • Step 707 The CAPIF determines the core network type currently accessed by the terminal or terminal group according to the information sent by the capability open network element, and determines the API information according to the core network type.
  • the API information determined by CAPIF may be API status information.
  • the API status information may indicate that the API is available or unavailable, or indicates that the API is suspended or resumed, or indicates service level information.
  • Step 708 The CAPIF sends an event notification (event notification) report to the third-party application.
  • the report may include a terminal or terminal group identifier, and API information.
  • the API information included in the report may include an available API identifier, or an unavailable API identifier, or may include an API list, which includes the API identifier and corresponding status information.
  • Step 709 According to the obtained API information, the third-party application calls an available API to provide a terminal or terminal group with a business service.
  • the API information transmission method provided in the embodiment of the present application may also include the steps shown in FIG. 8:
  • Steps 801-802 are similar to the foregoing steps 701-702, and are not repeated here.
  • Step 803 The third-party application (AF, SCS, or AS) sends a service discovery request (service discovery request) to the CAPIF.
  • the request may include a terminal or terminal group identifier, so that the CAPIF feedback is based on API information about the terminal or terminal group.
  • Step 804 The CAPIF sends a core network type query request (CN type query) to the capability open network element.
  • the request may include a terminal or terminal group identifier, so that the capability open network element feedbacks the core network currently accessed by the terminal or terminal group. Types of.
  • Step 805 The capability open network element queries the core network type currently accessed by the terminal or terminal group. Specifically, the capability open network element can query the core network type accessed by the terminal or terminal group from AMF, MME, SGSN, PCF, PCRF, PCF + PCRF, HSS, UDM, or HSS + UDM.
  • Step 806 The capability open network element sends a core network type query response (CN type query response) to the CAPIF, where the response includes the core network type currently accessed by the terminal or terminal group.
  • CN type query response CN type query response
  • Step 807 The CAPIF determines the API information according to the obtained core network type.
  • the API information determined by CAPIF may be API status information.
  • the API status information may indicate that the API is available or unavailable, or indicates that the API is suspended or resumed, or indicates service level information.
  • Step 808 The CAPIF sends a service discovery response (service discovery response) to the third-party application.
  • the response may include an available API identifier, or an unavailable API identifier, or may include an API list.
  • the list includes the API identifier. And corresponding status information.
  • Step 809 According to the obtained API information, the third-party application calls available APIs to provide business services to the terminal or terminal group.
  • the API information transmission method provided in the embodiment of the present application may also include the steps shown in FIG. 9:
  • Steps 901 to 902 are similar to the foregoing steps 701 to 702, and are not repeated here.
  • step 903 the CAPIF sends user information (user information) to the capability open network element, the information includes a terminal or terminal group identifier, and is used to subscribe to the capability open network element about the above-mentioned terminal or terminal group API Information change event.
  • Step 904 If the above step 903 exists, the capability open network element monitors the terminal or terminal group access to the core network type change event; if the above step 903 does not exist, the capability open network element monitors each terminal or terminal group access to the core network type Change event.
  • Step 905 After detecting that the core network type accessed by a certain terminal or terminal group changes, the capability open network element determines API information about the terminal or terminal group according to the changed core network type.
  • Step 906 The capability open network element sends a service release request or an update request to the CAPIF.
  • the request may include an API identifier, a terminal or terminal group identifier, and API information.
  • the API information includes status information of the API.
  • the CAPIF stores the received service name, terminal or terminal group identification, and API information.
  • the CAPIF may store an API identifier and a list of terminals or terminal groups corresponding to the API identifier, the list including available or unavailable terminal / terminal group identifiers.
  • Step 907 The CAPIF receives an event subscription request or a service discovery request sent by a third-party application (AF, SCS, or AS).
  • the event subscription request may include service API capability information and a terminal or terminal group identifier.
  • the service API capability information is used to indicate a subscription service API information change event, that is, to request CAPIF to send current API information to a third-party application when the API information changes;
  • the service discovery request may include a terminal or terminal group identification, so that the CAPIF feedback is based on API information about the terminal or terminal group.
  • Step 908 The CAPIF obtains API information corresponding to the terminal or terminal group indicated in step 907 from the stored API information.
  • Step 909 The CAPIF sends an event notification report or a service discovery response to the third-party application, and the report or response includes the API information obtained in step 908.
  • Step 910 According to the obtained API information, the third-party application calls available APIs to provide business services to the terminal or terminal group.
  • the API information transmission method provided in the embodiment of the present application may also include the steps shown in FIG. 10:
  • Steps 1001-1003 are similar to the foregoing steps 701-703, and are not repeated here.
  • Step 1004 The CAPIF sends an API support capability information subscription request, an event subscription request, or a monitoring request to the capability open network element.
  • an API support capability information subscription request is sent, the request includes the identity of the terminal or terminal group to be queried; if a time subscription request or monitoring request is sent, the request includes API support capability change information (API support capability change) and the terminal or terminal Group identification, API support capability change information is used to indicate subscription to API information change events, that is, when the capability open network element is requested to change the API information, it sends the changed API information to the CAPIF.
  • Step 1005 The capability open network element monitors the type change event of the terminal or terminal group accessing the core network.
  • Step 1006 After detecting that the core network type accessed by the terminal or terminal group changes, the capability open network element determines API information about the terminal or terminal group according to the changed core network type.
  • Step 1007 The capability open network element sends the identification of the terminal or terminal group and the determined API information to the CAPIF by carrying the API support capability status notification, event subscription report, or monitoring response message.
  • Steps 1008 to 1009 are similar to the foregoing steps 708 to 709 and will not be described again.
  • the API information transmission method provided in the embodiment of the present application may further include the steps shown in FIG. 11:
  • Steps 1101-1102 are similar to the foregoing steps 701-702, and are not repeated here.
  • Step 1103 The third-party application (AF, SCS, or AS) sends a service discovery request (service discovery request) to the CAPIF.
  • the request may include a terminal or terminal group identifier, so that the CAPIF feedback is based on API information about the terminal or terminal group.
  • Step 1104 The CAPIF sends an API support capability query request to the capability open network element, and the request includes the identifier of the terminal or the terminal group, so that the capability open network element sends API information about the terminal or the terminal group to the CAPIF.
  • Step 1105 The capability open network element queries the core network type currently accessed by the terminal or terminal group.
  • Step 1106 The capability open network element determines API information about the terminal or terminal group according to the queried core network type.
  • Step 1107 The capability open network element sends an API support capability query response to the CAPIF, and the response includes the API information determined in step 1106.
  • Step 1108 The CAPIF sends a service discovery response to the third-party application.
  • the response includes the API information received by the CAPIF.
  • the API information may specifically include an available API identifier, or an unavailable API identifier, or may include an API list.
  • the list includes API identifiers and corresponding status information.
  • Step 1109 According to the obtained API information, the third-party application calls available APIs to provide business services to the terminal or terminal group.
  • the embodiment of the present application further provides a network device, which is used to implement the function performed by the first network device in the foregoing method embodiment.
  • the structure of the network device may be as shown in FIG. 12, including a receiving unit 1201, a sending unit 1202, and further including a processing unit 1203.
  • the receiving unit 1201 is configured to receive a first request sent by a second network device, where the first request includes an identifier of a terminal or an identifier of a terminal group, and the first request is used to request an API of a third network device. information.
  • the sending unit 1202 is configured to send the first indication information to the second network device, where the first indication information includes the API information, and the API information is determined according to a network type accessed by the terminal, or according to The type of the network accessed by the terminal group is determined.
  • the foregoing network device further includes a processing unit 1203, configured to obtain a network type currently accessed by the terminal or the terminal group; and determine the API information according to the network type.
  • the receiving unit 1201 is further configured to receive second indication information sent by the third network device, where the second indication information includes a type of a network currently accessed by the terminal, or the The type of network the terminal group is currently connected to.
  • the sending unit 1202 is further configured to: before the receiving unit 1201 receives the second instruction information sent by the third network device, send a second request to the third network device, including the terminal Or the identity of the terminal group; wherein the second request is used to request to obtain the type of network that the terminal or the terminal group currently accesses; or the second request is used to request the terminal Or when the network type accessed by the terminal group changes, sending to the first network device the network type currently accessed by the terminal or the terminal group;
  • the receiving unit 1201 is further configured to receive third instruction information sent by a third network device, where the third instruction information includes the API information.
  • the sending unit 1202 is further configured to: before the receiving unit 1201 receives the third instruction information sent by the third network device, send a third request to the third network device; the third request Configured to request to obtain API information currently determined according to the network type accessed by the terminal or the terminal group; or the third request is used to request the first network device to change when the API information changes Sending the API information.
  • the first request is used to request to obtain the API information, and the first indication information is carried in a response message to the first request; or, the first request is used to When the request changes, the API information is sent to the second network device.
  • the embodiment of the present application further provides a network device, which is used to implement the function performed by the third network device in the foregoing method embodiment.
  • the structure of the network device may be as shown in FIG. 13, including a processing unit 1301 and a sending unit 1302, and further, a receiving unit 1303 may be further included.
  • the processing unit 1301 is configured to obtain a network type accessed by a terminal or a terminal group.
  • the sending unit 1302 is configured to send first instruction information to a first network device, where the first instruction information includes a network type that the terminal or the terminal group accesses.
  • the foregoing third network device may further include a receiving unit 1303, configured to receive a first A request, the first request includes an identifier of the terminal or an identifier of the terminal group; the first request is for requesting to obtain a network type accessed by the terminal or the terminal group, and the first indication information is carried in In the response message to the first request, or the first indication information is sent when a type of a network accessed by the terminal or the terminal group changes, or the first request is used to request When the network type accessed by the terminal or the terminal group changes, the network type accessed by the terminal or the terminal group is sent to the first network device.
  • a receiving unit 1303 configured to receive a first A request, the first request includes an identifier of the terminal or an identifier of the terminal group; the first request is for requesting to obtain a network type accessed by the terminal or the terminal group, and the first indication information is carried in In the response message to the first request, or the first indication information is sent when a type of a network accessed by the terminal or
  • the embodiment of the present application further provides a network device, which is used to implement the function performed by the third network device in the foregoing method embodiment.
  • the structure of the network device is similar to that shown in FIG. 13, and may also include a processing unit and a sending unit. Further, it may further include a receiving unit.
  • the processing unit is configured to obtain a network type accessed by a terminal or a terminal group;
  • a sending unit configured to send first indication information to the first network device, where the first indication information includes information of an API of the third network device, and the API information is the third network device according to the The network type is determined.
  • the third network device further includes a receiving unit, configured to receive a first request sent by the first network device before the sending unit sends the second instruction information to the first network device.
  • the first request includes an identifier of the terminal or an identifier of the terminal group; the first request is used to request to obtain API information determined according to a network type to which the terminal or the terminal group accesses, and
  • the first indication information is carried in a response message to the first request, or the first indication information is sent when a type of a network accessed by the terminal or the terminal group changes; or The request is used to request that the API information is sent to the first network device when the API information changes.
  • each unit of the above network equipment is only a division of logical functions. In actual implementation, it may be fully or partially integrated into a physical entity, or it may be physically separated. And these units can all be implemented in the form of software calling through processing elements; they can also be all implemented in hardware; some units can also be implemented through software calling through processing elements, and some units can be implemented through hardware.
  • the sending unit may be a separately established processing element, or it may be integrated and implemented in a certain chip of the network device. In addition, it may also be stored in the form of a program in the memory of the network device and called by a processing element of the network device And perform the function of the sending unit. The implementation of other units is similar.
  • each step of the above method or each unit above may be completed by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.
  • the above sending unit may be a sending control unit, and may receive information through a sending device of a network device, such as an antenna and a radio frequency device.
  • the above units may be one or more integrated circuits configured to implement the above method, for example: one or more application specific integrated circuits (ASICs), or one or more microprocessors (digital integrated processors) , DSP), or one or more field programmable gate array (FPGA).
  • ASICs application specific integrated circuits
  • DSP digital integrated processors
  • FPGA field programmable gate array
  • the processing element may be a general-purpose processor, such as a central processing unit (CPU) or another processor that can call a program.
  • CPU central processing unit
  • SOC system-on-a-chip
  • the embodiment of the present application provides a network device 1400, which is used to implement the function performed by the first network device in the foregoing method embodiment.
  • the hardware structure of the network device 1400 includes at least one processor 1401, a communication bus 1402, a memory 1403, and at least one communication interface 1404.
  • the processor 1401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program of the application scheme integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus 1402 may include a path for transmitting information between the aforementioned components.
  • the communication interface 1404 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 1403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM), or other types that can store information and instructions
  • Dynamic storage device can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory (EEPROM)), read-only compact disc (compact disc-read-only memory (CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.
  • the memory 1403 is configured to store application program code for executing the solution of the present application, and the processor 1401 controls execution.
  • the processor 1401 is configured to execute application program code stored in the memory 1403, so as to implement the API information transmission method provided by the foregoing embodiment of the present application.
  • the processor 1401 may also execute related functions in the API information transmission method provided by the foregoing embodiments of the present application.
  • the communication interface 1404 is responsible for communicating with other devices or communication networks. Examples do not specifically limit this.
  • the processor 1401 may include one or more CPUs.
  • the network device may include multiple processors.
  • processors can be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • an embodiment of the present application provides a network device for implementing a function performed by the third network device in the foregoing method embodiment.
  • the hardware structure of the network device may be similar to the structure shown in FIG. 14 and includes at least one processor, a communication bus, a memory, and at least one communication interface.
  • the processor may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the solution of the present application.
  • the communication bus may include a path for transmitting information between the aforementioned components.
  • the communication interface uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, RAN, WLAN, etc.
  • the memory can be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, and can also be EEPROM, CD-ROM or other optical disk storage, optical disk storage, A magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, is not limited thereto.
  • the memory may exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.
  • the memory is used to store application program code that executes the solution of the present application, and is controlled and executed by the processor.
  • the processor is configured to execute application program code stored in the memory, so as to implement the API information transmission method provided by the foregoing embodiment of the present application.
  • the processor may also perform related functions in the API information transmission method provided by the foregoing embodiments of the present application, and the communication interface is responsible for communicating with other devices or communication networks. This is not specifically limited.
  • the processor may include one or more CPUs.
  • the network device may include multiple processors.
  • processors can be a single-core processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • an embodiment of the present application further provides a communication system, including the foregoing first network device and any third network device.
  • an embodiment of the present application further provides a chip system, which includes a processor, and is configured to support a communication device to implement the foregoing API information transmission method.
  • the chip system further includes a memory. This memory is used to store program instructions and data necessary for communication equipment.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices, which are not specifically limited in the embodiments of the present application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be from a website site, a computer, a server, or a data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or includes one or more data storage devices such as servers, data centers, and the like that can be integrated with the medium.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种API信息传输方法及装置。该方法中，第一网络设备接收第二网络设备发送的第一请求，该第一请求中包括终端的标识或终端组的标识，该第一请求用于请求获取第三网络设备的API信息；第一网络设备向第二网络设备发送第一指示信息，该第一指示信息包括API信息，该API信息是根据终端标识对应的终端所接入的网络类型确定的，或者是根据终端组标识对应的终端组所接入的网络类型确定的。通过上述方法，使得第二网络设备能够获取到根据终端或终端组的接入网络类型确定的API信息，有助于避免第二网络设备调用了与终端接入网络类型不符的API而无法为终端提供业务服务的情况，有利于提高用户体验。

Description

一种API信息传输方法及装置
本申请要求于2018年5月21日提交中国国家知识产权局、申请号为201810491022.0、发明名称为“一种API信息传输方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种API信息传输方法及装置。
背景技术
在传统网络中，如演进分组系统(evolved packet system，EPS)中，服务能力开放功能网元(service capability exposure function，SCEF)可以通过应用程序编程接口(application programming interface，API)的形式向第三方应用开放4G网络功能。图1实例性的给出了一种SCEF的架构，第三方应用程序可以通过调用SCEF中的API获取终端的相关信息。
在新的移动通信系统中，例如图2所示的5G网络中，网络开放功能网元(network exposure function，NEF)也可以通过API的形式向第三方应用开放5G网络功能，即，第三方应用可以通过调用NEF中的API获取终端的相关信息。
对于支持4G、5G接入的终端，由于终端的移动、网络覆盖范围等因素，可能使得终端在4G和5G之间进行切换，导致第三方应用无法为终端提供业务服务，造成较差的用户体验。
发明内容
本申请提供一种API信息传输方法及装置，用以避免调用终端接入网络类型不符的API而导致无法为第三方应用提供业务服务的情况。
第一方面，本申请提供了一种API信息传输方法，该方法包括：
第一网络设备接收第二网络设备发送的第一请求，该第一请求中包括终端的标识或终端组的标识，该第一请求用于请求获取第三网络设备的API信息。第一网络设备向第二网络设备发送第一指示信息，该第一指示信息包括API信息，该API信息是根据终端接入的网络类型确定的，或者是根据终端组接入的网络类型确定的。
在本申请上述实施例中，第二网络设备能够获取到根据终端或终端组接入的网络类型确定出的API信息，有助于避免第二网络设备在为终端提供业务服务时调用与终端的网络类型不相符的API，导致可能无法获取到终端相关信息，进而无法为终端提供业务服务的情况，因而上述实施例有利于提高用户体验。
在一种可能的实现方式中，上述方法还包括：第一网络设备获取终端或终端组当前接入的网络类型，然后第一网络设备根据获取到的网络类型确定API信息。
在一种可能的实现方式中，第一网络设备在获取终端或终端组当前接入的网络类型时，可以通过接收第三网络设备发送的第二指示信息获取，该第二指示信息中包括终端或终端组 当前接入的网络类型。第三网络设备可以查询到终端或终端组当前接入的网络类型，第三网络设备将查询到的网络类型发送给第一网络设备，以便第一网络设备根据网络类型确定出API信息。
在一种可能的实现方式中，第一网络设备在接收第二指示信息之前，可以向第三网络设备发送第二请求，该第二请求中包括终端的标识或终端组的标识。具体地，该第二请求可以用于请求获取终端或终端组接入的网络类型，或者，也可以用于请求第三网络设备在终端或终端组接入的网络类型发生变化时，向第一网络设备发送终端或终端组当前接入的网络类型。在上述实施例中，第一网络设备可以根据实际需求，查询终端或终端组当前接入的网络类型或者长期订阅终端或终端组当前接入的网络类型，以方便确定相应的API信息。
在一种可能的实现方式中，上述方法还包括：所述第一网络设备接收第三网络设备发送的第三指示信息，所述第三指示信息包括所述API信息。在此种实现方式中，第一网络设备可以接收第三网络设备发送的API信息，可以不再需要第一网络设备根据终端或终端组接入的网络类型确定API信息，减少了第一网络设备的负荷。
在一种可能的实现方式中，在所述第一网络设备接收第三网络设备发送的第三指示信息之前，所述方法还包括：所述第一网络设备向所述第三网络设备发送第三请求；所述第三请求用于请求获取根据所述终端或所述终端组接入的网络类型确定的API信息；或者，所述第三请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。在此种实现方式中，第一网络设备可以请求获取当前的API信息，也请求第三网络设备在API信息发送变化时发送API信息，能够灵活满足不同场景的需求。
在一种可能的实现方式中，所述第一请求用于请求获取所述API信息，所述第一指示信息携带在对所述第一请求的响应消息中；或者，所述第一请求用于请求在所述API信息发生变化时，向所述第二网络设备发送API信息。在上述实施例中，第二网络设备可以根据实际需求，查询当前的API信息或者长期订阅API信息，以方便调用API。
第二方面，本申请实施例提供了一种第一网络设备，包括处理器、存储器和通信接口，所述存储器用于存储程序，所述处理器调用存储器存储的程序，通过通信接口执行如第一方面任一项所述方法中第一网络设备执行的流程。
第三方面，本申请实施例提供了一种第三网络设备，包括处理器、存储器和通信接口，所述存储器用于存储程序，所述处理器调用存储器存储的程序，通过通信接口执行如第一方面中第三网络设备执行的流程。
第四方面，本申请实施例提供了一种通信系统，包括第二方面所述的第一网络设备和第三方面所述的第三网络设备，或者，可以包括第二方面所述的第一网络设备和第四方面所述的第三网络设备。
第五方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机指令，当所述指令在计算机上运行时，使得计算机执行如第一方面中任一项所述的方法。
第六方面，本申请实施例提供一种芯片系统，包括：处理器，用于支持通信设备实现上述第一方面任一项所述的方法。
附图说明
图1为本申请实施例提供的SCEF架构示意图；
图2为本申请实施例提供的5G网络架构示意图；
图3为本申请实施例提供的4G和5G网络架构示意图；
图4为本申请实施例提供的SCEF+NEF功能示意图；
图5为本申请实施例提供的包括CAPIF网元的网络架构示意图；
图6为本申请实施例提供的API信息传输方法流程示意图之一；
图7为本申请实施例提供的API信息传输方法流程示意图之二；
图8为本申请实施例提供的API信息传输方法流程示意图之三；
图9为本申请实施例提供的API信息传输方法流程示意图之四；
图10为本申请实施例提供的API信息传输方法流程示意图之五；
图11为本申请实施例提供的API信息传输方法流程示意图之六；
图12为本申请实施例提供的一种网络设备结构示意图之一；
图13为本申请实施例提供的一种网络设备结构示意图之二；
图14为本申请实施例提供的一种网络设备结构示意图之三。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
图3示例性的给出了一种网络系统架构示意图，如图所示，终端接入演进分组核心网(evolved packet core，EPC)时，第三方应用可以通过业务能力服务器(services capability server，SCS)或者应用服务器(application server，AS)等实现；第三方应用可以通过SCEF从EPC中获取有关终端的信息。当终端接入第五代移动通信系统核心网(5th generation core，5GC)时，第三方应用可以通过应用功能(application function，AF)实现；第三方应用可以通过NEF从5GC中获取有关终端的信息。
为了兼容EPC和5GC，能力开放网元，如SCEF、NEF，或者设置有SCEF功能模块和NEF功能模块的网络设备(以下简称SCEF+NEF)，在为第三方应用提供API时，可通过两种方式实现，如图4所示。在方式一中，SCEF和NEF可以分别提供各自的API，即分别提供4G网络API和5G网络API。在方式二中，可以在SCEF上提供一套增强的API，在接收到5G网络API调用请求时将请求转发给NEF；或者也可以在NEF上提供一套增强的API，在接收到4G网络API调用请求时将请求转发给SCEF；或者，对于SCEF+NEF来说，还可以在SCEF+NEF中设置仅能够为4G网络提供服务的模块、仅能够为5G网络提供服务的模块以及能够为4G和5G网络提供服务的模块，在接收到4G或5G网络API调用请求后，将请求传输给相应的模块处理。
然而，第三方应用并不清楚终端接入的网络变化情况，当终端从5G切换至4G后，若AF仍请求调用NEF中的API，则可能无法获取到终端的信息，或者，当终端从4G切换至5G后，若仍请求调用SCEF中的API，也可能无法获取到终端信息。
为了解决上述技术问题，本申请实施例提供了一种包括CAPIF网元的网络架构，如图5所示，其中，CAPIF网元能够与能力开放网元、第三方应用进行通信。基于支持CAPIF的网络架构，第三方应用可以请求CAPIF提供API信息，以避免第三方应用在请求调用API时调用不可用的API。
具体地，图6为本申请实施例提供的一种API信息传输方法的流程示意图，如图所示，该方法可以包括以下步骤：
步骤601、第一网络设备接收第二网络设备发送的第一请求。其中，第一请求中用于请求获取第三网络设备的API信息。
其中，该第一请求中可以包括终端标识，即该第一请求用于请求获取终端级别的API信息，或者，该第一请求中可以包括终端组标识，即该第一请求用于请求获取终端组级别的API信息。
步骤602、第一网络设备向第二网络设备发送第一指示信息，该第一指示信息中包括API信息。
其中，API信息，可以是可用的API的标识，以指示第二网络设备可以调用这些API标识所对应的API。或者，API信息也可以是不可用的API标识，以指示第二网络设备不可用调用这些API标识对应的API。又或者，API信息还可以包括API标识以及API的状态信息。具体的，API的状态信息可以用于指示可用或不可用。或者，API的状态信息可以用于指示挂起(suspended)或者恢复(resumed)，其中挂起表示暂时不可用，例如，当终端由于通话从4G网络回落到2G网络时，终端的4G网络会话及相关承载将被挂起，当终端通话结束，4G网络会话及相关承载将被恢复。或者，API的状态信息还可以用于指示服务级别信息，例如，API_1可服务接入EPC的终端，对应的级别为1，API_2可服务接入5GC的终端，对应的级别为2，API_3可服务接入5GC或者EPC的终端，对应的级别为3；使得第二网络设备能够根据API的服务级别确定可用的API。
当第一请求中包括终端标识时，那么第一指示信息中包含的API信息，是根据终端标识对应的终端所接入的网络类型确定出的；当第一请求中包括终端组标识时，那么第一指示信息中包含的API信息，是根据终端组包含的终端所接入的网络类型确定出的。例如，第二网络设备可以在有少量终端的业务需求时，分别获取与每个终端相关的API信息，即，每个第一请求中包括一个或多个终端的标识；又例如，第二网络设备还可以在有大量终端的业务需求时，请求获取关于一个或多个终端组的API信息，即，每个第一请求中可以包括一个或多个终端组的标识。
具体的，终端接入的网络类型，可以为终端接入的核心网类型(CN type)，如5GC、EPC、EPC和5GC、非5GC(Non-5GC)、5G、4G、3G、非5G(Non-5G)等3GPP核心网的类型或者其组合。其中，一个终端所接入的核心网类型，可以为5GC或EPC，或者，对于能够同时在4G网络和5G网络注册的终端，其接入的核心网类型也可以为5GC和EPC。终端接入的网络类型还可以是以下之一或组合：通用陆地无线接入网(universal terrestrial radio access network，UTRAN)、码分多址(code division multiple access，CDMA)2000、全球移动通信系统无线接入网络(GSM/EDGE radio access network，GERAN)、长期演进(long term evolution，LTE)、5G新空口(new radio，NR)、演进的UTRAN、下一代无线接入网(next  generation radio access network，NG-RAN)等3GPP无线接入技术(radio access technology，RAT)类型等。
一个终端组中包括多个终端，该多个终端所接入的核心网类型可能相同，也可能不同。因此，根据终端组接入的网络类型确定出的API信息中，当终端组中所有的终端接入的网络类型相同时，则此终端组的接入网络类型为终端的接入网络类型；当终端组中的终端接入的网络类型不完全相同时，则此终端组的接入类型为所有终端的接入网络类型的组合；例如，终端组中所有终端都接入EPC，则终端组接入的网络类型为EPC；如果部分终端接入EPC，部分终端接入5GC，则终端组接入的网络类型为EPC+5GC。
在上述方法中，第一网络设备可以为3GPP公共API架构(common API framework for 3GPP northbound APIs，CAPIF)核心功能网元。第二网络设备可以为4G网络中的业务能力服务器(services capability server，SCS)或应用服务器(application server，AS)等网元，或者，也可以为5G网络中的应用功能(application function，AF)等网元，或者，还可以是未来其他通信网络中可用于支持第三方应用的网元设备。第三网络设备可以为SCEF，或者NEF，或者还可以是SCEF与NEF合设的网络设备(以下简称SCEF+NEF)。
第三方应用(第二网络设备)为终端提供业务服务时可能需要从终端接入的核心网(EPC、5GC等)中获取终端的相关信息，若终端已进行了网络切换，而第三方应用仍调用切换前的网络中的API获取终端信息，则可能无法获取所需信息，从而无法为终端通过业务服务。而在本申请上述实施例中，第二网络设备能够获取到根据终端或终端组接入的网络类型确定出的API信息，有助于避免第二网络设备在为终端提供业务服务时调用与终端的网络类型不相符的API，导致可能无法获取到终端相关信息，进而无法为终端提供业务服务的情况，因而上述实施例有利于提高用户体验。
在一些实施例中，上述步骤601中的第一请求，可以是用于请求获取API信息，例如，第二网络设备可以在有业务需求时，或者在当预设定时器超时时，或者接收到用于指示API支持能力发生改变的指示信息时，向第一网络设备发送第一请求，如服务发现请求(service discover request)，获取当前的API信息即可。第一网络设备在接收到上述第一请求后，获取当前的API信息并发送给第二网络设备；进一步地，第一网络设备也可以根据协议规定或不同的业务需求，在API信息发生变化后，将变化后的API信息发送给第二网络设备。
在另外一些实施例中，第一请求也可以用于请求在API信息发送变化时，向第二网络设备发送API信息。例如，第二网络设备可以向第一网络设备发送事件订阅请求(event subscribe request)，该请求中可以包括事件指示信息，以及终端标识或终端组标识；其中，该事件指示信息表示请求订阅的事件为API信息变化事件。相应的，第一网络设备在API信息发生变化时，再执行上述步骤602。
其中，API的信息可以与终端或终端组接入的网络类型相关，当终端或终端组接入的网络类型发生变化时，则可能导致API的状态信息发生变化，如前所述，终端接入EPC时可用的API与接入5GC时可用的API可能不同。而终端组中包含的一个或多个终端接入的网络类型发生变化，则可能导致终端组对应的API信息发生变化。API的信息还可以与其他因素相关，例如与终端的业务类型相关，那么当终端的业务类型发生变化时，则可能导致API的状态信息发生变化；又例如，由于网络功能的调整，可能也会导致某些API不可用，或增加新 的API等。
可选地，第一网络设备可以请求订阅上述与API信息相关的信息变化事件，并在接收到订阅事件报告后，确定API信息是否发生变化。或者，第一网络设备也可以周期性地查询与API信息相关的信息，并确定API信息是否发生变化。
在一种可能的实现方式中，上述第一指示信息中包含的API信息，是第一网络设备根据获取到的终端或终端组当前接入的网络类型确定出的。例如，若第一网络设备获取到终端A当前接入的网络为EPC，则第一网络设备可以确定SCEF中的API为可用API，即第三方应用可以调用SCEF中的API获取终端A的相关信息；此外，若还存在SCEF与NEF共用的API，第一网络设备也可以确定这些共用的API为可用API。又例如，若第一网络设备获取到终端B当前接入的网络为5GC，则第一网络设备可以确定NEF中的API为可用API，即第三方应用可以调用NEF中的API获取终端B的相关信息；此外，若还存在SCEF和NEF共用的API，第一网络设备也可以将这些共用的API确定为可以API。
具体地，第一网络设备可以通过以下四种方式获取终端或终端组当前接入的网络类型：
方式一、第一网络设备向第三网络设备发送请求，请求获取终端或终端组当前接入的网络类型。第三网络设备在接收到上述请求后，将终端或终端组当前接入的网络类型发送给第一网络设备。可选地，第一网络设备可以在上述步骤601之后，向第三网络设备发送请求，以获取网络类型。
例如，第一网络设备在接收到第二网络设备发送的第一请求后，可以向第三网络设备发送核心网类型查询请求(CN type query request)，该请求中可以包括终端的标识，即请求获取该终端接入的核心网类型；该请求中也可以包括终端组的标识，即请求获取该终端组中包含的终端所接入的核心网类型。第三网络设备在获取到终端或终端组接入的核心网类型后，向第一网络设备发送核心网类型查询响应(CN type query response)，该响应中包含获取到的核心网类型。
可选地，第三网络设备在接收到第一网络设备发送的上述请求后，可以从核心网中的其它网元获取终端或终端组接入的网络类型。例如，第三网络设备可以与5GC中的接入和移动性管理功能(access and mobility management function，AMF)、策略控制功能(policy control function，PCF)或统一数据管理(unified data management，UDM)等网元进行通信，从而获取终端或终端组接入的核心网类型；或者，第三网络设备也可以与EPC中的移动性管理实体(mobility management entity MME)、服务GPRS支持节点(serving GPRS supporting node，SGSN)、归属用户服务器(home subscribe user，HSS)或策略和计费规则功能(policy and charging rules function，PCRF)等网元进行通信，从而获取终端或终端组接入的核心网类型；此外，第三网络设备还可以从HSS+UDM或PCF+PCRF处获取终端或终端组接入的核心网类型。
方式二、第一网络设备向第三网络设备发送请求，请求第三网络设备在终端或终端组接入的网络类型发生变化时，向第一网络设备发送终端或终端组当前接入的网络类型，即，第一网络设备请求订阅终端或终端组接入的网络类型变化事件。第三网络设备在接收到上述请求后，当发现终端或终端组中包含的终端所接入的网络类型发生变化时，则向第一网络设备发送指示信息，以指示终端或终端组当前接入的网络类型。
例如，第一网络设备可以向第三网络设备发送事件订阅请求(event subscribe request)，该请求中可以包括事件指示信息，以及终端标识或终端组标识；其中，该事件指示信息表示请求订阅的事件为终端或终端组接入的网络类型变化事件。第三网络设备在获取到终端或终端组接入的网络类型发生变化的信息后，向第一网络设备发送订阅事件报告，该报告中可以包括终端标识或终端组标识，以及当前接入的网络类型。
可选地，第一网络设备可以在上述步骤601之后，向第三网络设备发送请求，以使第三网络设备在终端或终端组接入的网络类型发生变化时，将当前的网络类型发生给第一网络设备。例如，第一网络设备可以在接收到第二网络设备发送的事件订阅请求(用于请求API信息变化时发送变化后的API信息)后，向第三网络设备发送事件订阅请求(用于请求网络类型发生变化时发送当前的网络类型)。或者，第一网络设备也可以主动向第三网络设备发送请求，以使第三网络设备在终端或终端组接入的网络类型发生变化时，将当前的网络类型发生给第一网络设备。又或者，第一网络设备还可以在提供其他业务服务需要获取终端或终端组接入的网络类型时，向第三网络设备发送上述订阅网络类型变化事件的请求。
第三网络设备获取终端或终端组接入的网络类型的方法，与方式一中类似，此处不再赘述。第三网络设备在确定终端或终端组接入的网络类型发生变化后，将网络类型发生变化的终端或终端组的标识、当前的网络类型发生给第一网络设备。第一网络设备可以将终端或终端组的标识与网络类型对应存储，以便此后接收到第二网络设备发送的获取API信息的请求时，可以根据存储的终端或终端组的网络类型确定API信息，而无需再向第三网络设备查询。
方式三、第一网络设备可以发送请求，请求获取终端或终端组接入的网络类型，第三网络设备可以根据协议规定或不同的业务需求，在终端或终端组接入的网络类型发生变化后，将变化后的网络类型发送给第一网络设备。第三网络设备获取终端或终端组接入的网络类型的方法，与方式二中类似。第一网络设备可以将接收到的终端或终端组的标识与网络类型对应存储。
方式四、第三网络设备可以在终端或终端组接入的网络类型发生变化时，主动将变化后的网络类型发送给第一网络设备。第三网络设备获取终端或终端组接入的网络类型的方法，与方式一中类似。第一网络设备可以将接收到的终端或终端组的标识与网络类型对应存储。
在另一种可能的实现方式中，上述第一指示信息中包含的API信息，也可以是第一网络设备从第三网络设备处获取的。具体地，第一网络设备也可以通过三种方式获取API信息：
方式一、第一网络设备向第三网络设备发送请求，请求获取根据终端或终端组当前接入的网络类型确定的API信息。第三网络设备在接收到该请求后，获取终端或终端组当前接入的网络类型，并根据获取到的网络类型确定当前的API信息，然后将确定出的API信息发送给第一网络设备。其中，第三网络设备获取终端或终端组接入的网络类型的方法，与前述实施例类似。
方式二、第一网络设备向第三网络设备发送请求，请求在API信息发生变化时，向第一网络设备发送当前API信息。
如前所述，API信息的变化，可能是由于终端或终端组接入的网络类型发生变化而导致的，也可能是由于终端业务类型或网络功能调整等因素导致的。具体地，第三网络设备可以订阅与API信息相关的信息变化事件，并在接收到订阅事件报告后，确定API信息是否发生 变化，或者，也可以周期性地查询与API信息相关的信息，并确定API信息是否发生变化。具体地，第三网络设备可以订阅与终端或终端组接入的网络类型相关的信息变化事件，并在接收到订阅事件报告后，获取终端或终端组当前接入的网络类型，确定API信息是否发生变化，或者，也可以周期性地查询与终端或终端组接入的网络类型相关的信息，获取终端或终端组当前接入的网络类型，并确定API信息是否发生变化。第三网络设备在确定API信息发生变化时，将终端或终端组标识，以及变化后的API信息发送给第一网络设备。
第一网络设备可以将接收到的终端或终端组标识与API信息对应存储，以便此后接收到第二网络设备发送的获取API信息的请求时，可以从存储器中读取相应的API信息并发送给第二网络设备，而无需再向第三网络设备查询。
方式三、第一网络设备可以发送请求，请求获取根据终端或终端组当前接入的网络类型确定的API信息，第三网络设备可以根据协议规定或不同的业务需求，在API信息发生变化后，将变化后的是API信息发送给第一网络设备。第三网络设备确定API信息是否变化的方式，与方式二中类似。第一网络设备可以将接收到的终端或终端组标识与API信息对应存储。
方式四、第三网络设备也可以在确定API信息发送变化时，主动将变化后的API信息发送给第一网络设备。例如，第三网络设备可以订阅与终端或终端组接入的网络类型相关的信息变化事件，并在接收到订阅事件报告后，获取终端或终端组当前接入的网络类型，确定API信息是否发生变化，或者，也可以周期性地查询与终端或终端组接入的网络类型相关的信息，获取终端或终端组当前接入的网络类型，并确定API信息是否发生变化。
为了更清楚理解本申请上述实施例，下面结合附图7至附图11进行举例说明。
参见图7，本申请实施例提供的API信息传输方法可以包括如图7所示的步骤：
步骤701、初始化阶段，能力开放网元(NEF、SCEF或SCEF+NEF)向CAPIF发送服务发布请求(service publish request)，该请求中可以包括服务名称(service name)。
当能力开放网元为SCEF+NEF时，上述请求中还可以包括服务名称对应的核心网类型(CN type)，例如服务项目1由EPC提供，服务项目2由5GC提供；当能力开放网元为NEF或SCEF时，上述请求中可以不携带CN type，CAPIF可以根据请求中携带的NEF或SCEF的标识判断出CN type，例如，NEF标识对应的CN type为5GC，SCEF对应的CN type为EPC。
步骤702、CAPIF保存注册信息，例如上述终端或终端组标识、服务名称以及核心网类型。
步骤703、第三方应用(AF、SCS或AS)向CAPIF发送事件订阅请求(event subscription request)，该请求中可以包括服务API能力信息(availability of service APIs)以及终端或终端组标识，其中服务API能力信息用于表示订阅服务API信息变化事件，即请求CAPIF在API信息发生变化时向第三方应用发送当前API信息。
步骤704、CAPIF向能力开放网元发送事件订阅请求或监听请求(monitoring request)，该请求中包括核心网类型变化信息(CN type change)以及终端或终端组标识，其中，核心网类型变化信息用于表示订阅核心网类型变化事件，即请求能力开放网元在终端或终端组接入的核心网类型发生变化时，向CAPIF发送当前核心网类型。
步骤705、能力开放网元监听核心网类型变化事件。具体的，能力开放网元可以从AMF、MME、SGSN、PCF、PCRF、PCF+PCRF、HSS、UDM或HSS+UDM处监听终端或终端组接入的核心网 类型是否发生变化。
步骤706、能力开放网元在监听到核心网类型发生变化后，向CAPIF发送订阅事件报告或监听响应(monitoring response)或其他指示信息，将终端或终端组标识、核心网类型变化指示信息和/或变化后的核心网类型通知给CAPIF。
步骤707、CAPIF根据能力开放网元发送的信息，确定终端或终端组当前接入的核心网类型，并根据核心网类型确定API信息。
具体的，CAPIF确定出的API信息可以API状态信息。其中，API状态信息可表示API可用或不可用，或者表示挂起(suspended)或恢复(resumed)，或者表示服务级别信息。
步骤708、CAPIF向第三方应用发送事件通知(event notification)报告，该报告中可以包括终端或终端组标识，以及API信息。具体的，该报告中包含的API信息可以包括可用的API标识，或者包括不可用的API标识，或者，也可以包括API列表，该列表中包括API标识以及对应的状态信息。
步骤709、第三方应用根据获取到的API信息，调用可用的API为终端或终端组提供业务服务。
参见图8，本申请实施例提供的API信息传输方法也可以包括如图8所示的步骤：
步骤801-802，与前述步骤701-702类似，不再赘述。
步骤803、第三方应用(AF、SCS或AS)向CAPIF发送服务发现请求(service discover request)，该请求中可以包括终端或终端组标识，以使CAPIF反馈根据关于终端或终端组的API信息。
步骤804、CAPIF向能力开放网元发送核心网类型查询请求(CN type query request)，该请求中可以包括终端或终端组标识，以使能力开放网元反馈终端或终端组当前接入的核心网类型。
步骤805、能力开放网元查询终端或终端组当前接入的核心网类型。具体的，能力开放网元可以从AMF、MME、SGSN、PCF、PCRF、PCF+PCRF、HSS、UDM或HSS+UDM处查询终端或终端组接入的核心网类型。
步骤806、能力开放网元向CAPIF发送核心网类型查询响应(CN type query response)，该响应中包括终端或终端组当前接入的核心网类型。
步骤807、CAPIF根据获取到的核心网类型，确定API信息。
具体的，CAPIF确定出的API信息可以API状态信息。其中，API状态信息可表示API可用或不可用，或者表示挂起(suspended)或恢复(resumed)，或者表示服务级别信息。
步骤808、CAPIF向第三方应用发送服务发现响应(service discover response)，该响应中可以包括可用的API标识，或者包括不可用的API标识，或者，也可以包括API列表，该列表中包括API标识以及对应的状态信息。
步骤809、第三方应用根据获取到的API信息，调用可用的API为终端或终端组提供业务服务。
参见图9，本申请实施例提供的API信息传输方法也可以包括如图9所示的步骤：
步骤901-902，与前述步骤701-702类似，不再赘述。
步骤903(该步骤为可选项)、CAPIF向能力开放网元发送用户信息(user information)，该信息中包括终端或终端组标识，用于向能力开放网元订阅关于上述终端或终端组的API信息变化事件。
步骤904、若存在上述步骤903，能力开放网元监听上述终端或终端组接入核心网类型变化事件；若不存在上述步骤903，能力开放网元监听每个终端或终端组接入核心网类型变化事件。
步骤905、能力开放网元在监听到某个终端或终端组接入的核心网类型发生变化后，根据变化后的核心网类型，确定关于该终端或终端组的API信息。
步骤906、能力开放网元向CAPIF发送服务发布请求或更新请求(update request)，上述请求中可以包括API标识、终端或终端组标识以及API信息。其中，API信息包括API的状态信息。
CAPIF对接收到的服务名称、终端或终端组标识以及API信息进行存储。例如，CAPIF可以存储API标识以及与API标识对应的终端或终端组列表，该列表包括可用或不可用的终端/终端组标识。
步骤907、CAPIF接收到第三方应用(AF、SCS或AS)发送的事件订阅请求或服务发现请求。其中，事件订阅请求可以包括服务API能力信息以及终端或终端组标识，服务API能力信息用于表示订阅服务API信息变化事件，即请求CAPIF在API信息发生变化时向第三方应用发送当前API信息；服务发现请求中可以包括终端或终端组标识，以使CAPIF反馈根据关于终端或终端组的API信息。
步骤908、CAPIF从已存储的API信息中获取与步骤907中指示的终端或终端组对应的API信息。
步骤909、CAPIF向第三方应用发送事件通知报告或服务发现响应，该报告或响应中包括步骤908中获取到的API信息。
步骤910、第三方应用根据获取到的API信息，调用可用的API为终端或终端组提供业务服务。
参见图10，本申请实施例提供的API信息传输方法也可以包括如图10所示的步骤：
步骤1001-1003，与前述步骤701-703类似，不再赘述。
步骤1004、CAPIF向能力开放网元发送API支持能力信息订阅请求、事件订阅请求或监听请求。其中，若发送API支持能力信息订阅请求，该请求包括待查询的终端或终端组标识；若发送时间订阅请求或监听请求，请求中包括API支持能力变化信息(API support capability change)以及终端或终端组标识，API支持能力变化信息用于表示订阅API信息变化事件，即请求能力开放网元在API信息发生变化时，向CAPIF发送变化后的API信息。
步骤1005、能力开放网元监听上述终端或终端组接入核心网类型变化事件。
步骤1006、能力开放网元在监听到终端或终端组接入的核心网类型发生变化后，根据变化后的核心网类型，确定关于该终端或终端组的API信息。
步骤1007、能力开放网元将终端或终端组标识以及确定出的API信息，携带在API支持 能力状态通知、事件订阅报告或监听响应等消息中发送给CAPIF。
步骤1008-1009，与前述步骤708-709类似，不再赘述。
参见图11，本申请实施例提供的API信息传输方法还可以包括如图11所示的步骤：
步骤1101-1102，与前述步骤701-702类似，不再赘述。
步骤1103、第三方应用(AF、SCS或AS)向CAPIF发送服务发现请求(service discover request)，该请求中可以包括终端或终端组标识，以使CAPIF反馈根据关于终端或终端组的API信息。
步骤1104、CAPIF向能力开放网元发送API支持能力查询请求，该请求包括上述终端或终端组标识，以使能力开放网元将关于上述终端或终端组的API信息发送给CAPIF。
步骤1105、能力开放网元查询终端或终端组当前接入的核心网类型。
步骤1106、能力开放网元根据查询到的核心网类型，确定关于上述终端或终端组的API信息。
步骤1107、能力开放网元向CAPIF发送API支持能力查询响应，该响应中包括步骤1106中确定出的API信息。
步骤1108、CAPIF向第三方应用发送服务发现响应，该响应中包括CAPIF接收到的API信息，API信息具体可以包括可用的API标识，或者包括不可用的API标识，或者，也可以包括API列表，该列表中包括API标识以及对应的状态信息。
步骤1109、第三方应用根据获取到的API信息，调用可用的API为终端或终端组提供业务服务。
基于相同的技术构思，本申请实施例还提供了一种网络设备，用于实现上述方法实施例中第一网络设备所执行的功能。具体地，该网络设备的结构可以如图12所示，包括接收单元1201，发送单元1202，进一步可以包括处理单元1203。
其中，接收单元1201用于接收第二网络设备发送的第一请求，所述第一请求中包括终端的标识或终端组的标识，所述第一请求用于请求获取第三网络设备的API的信息。
发送单元1202用于向所述第二网络设备发送第一指示信息，所述第一指示信息包括所述API信息，所述API信息是根据所述终端接入的网络类型确定的，或者是根据所述终端组接入的网络类型确定的。
在一种可能的实现方式中，上述网络设备还包括处理单元1203，用于获取所述终端或所述终端组当前接入的网络类型；根据所述网络类型，确定所述API信息。
在一种可能的实现方式中，接收单元1201还用于：接收所述第三网络设备发送的第二指示信息，所述第二指示信息包括所述终端当前接入的网络类型，或所述终端组当前接入的网络类型。
在一种可能的实现方式中，发送单元1202，还用于：在接收单元1201接收所述第三网络设备发送的第二指示信息之前，向第三网络设备发送第二请求，包括所述终端的标识或所述终端组的标识；其中，所述第二请求用于请求获取所述终端或所述终端组当前接入的网络类型；或者，所述第二请求用于请求在所述终端或所述终端组接入的网络类型发生变化时， 向所述第一网络设备发送所述终端或所述终端组当前接入的网络类型；
在一种可能的实现方式中，接收单元1201还用于：接收第三网络设备发送的第三指示信息，所述第三指示信息包括所述API信息。
在一种可能的实现方式中，发送单元1202还用于：在接收单元1201接收第三网络设备发送的第三指示信息之前，向所述第三网络设备发送第三请求；所述第三请求用于请求获取当前根据所述终端或所述终端组接入的网络类型确定的API信息；或者，所述第三请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。
在一种可能的实现方式中，所述第一请求用于请求获取所述API信息，所述第一指示信息携带在对所述第一请求的响应消息中；或者，所述第一请求用于请求在所述API信息发生变化时，向所述第二网络设备发送API信息。
基于相同的技术构思，本申请实施例还提供了一种网络设备，用于实现上述方法实施例中第三网络设备所执行的功能。具体地，该网络设备的结构可以如图13所示，包括处理单元1301和发送单元1302，进一步的，还可以包括接收单元1303。
其中，处理单元1301，用于获取终端或终端组接入的网络类型。
发送单元1302，用于向第一网络设备发送第一指示信息，所述第一指示信息包括所述终端或所述终端组接入的网络类型。
在一种可能的实现方式中，上述第三网络设备还可以包括接收单元1303，用于在发送单元1302向第一网络设备发送第一指示信息之前，接收所述第一网络设备发送的第一请求，所述第一请求包括所述终端的标识或所述终端组的标识；所述第一请求用于请求获取所述终端或所述终端组接入的网络类型，第一指示信息携带在对第一请求的响应消息中，或者，所述第一指示信息是在所述终端或所述终端组接入的网络类型发生变化时发送的；或者，所述第一请求用于请求在所述终端或所述终端组接入的网络类型发生变化时，向所述第一网络设备发送所述终端或所述终端组接入的网络类型。
基于相同的技术构思，本申请实施例还提供了一种网络设备，用于实现上述方法实施例中第三网络设备所执行的功能。该网络设备的结构与图13所示的结构类似，也可以包括处理单元和发送单元，进一步的，还可以包括接收单元。
其中，处理单元，用于获取终端或终端组接入的网络类型；
发送单元，用于向所述第一网络设备发送第一指示信息，所述第一指示信息包括所述第三网络设备的API的信息，所述API信息是所述第三网络设备根据所述网络类型确定的。
在一种可能的实现方式中，上述第三网络设备还包括接收单元，用于在发送单元向所述第一网络设备发送第二指示信息之前，接收所述第一网络设备发送的第一请求，所述第一请求包括所述终端的标识或所述终端组的标识；所述第一请求用于请求获取根据所述终端或所述终端组接入的网络类型确定的API信息，所述第一指示信息携带在对第一请求的响应消息中，或者，所述第一指示信息是在所述终端或所述终端组接入的网络类型发生变化时发送的；或者，所述第一请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。
需要说明的是，应理解以上网络设备的各个单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元通过软件通过处理元件调用的形式实现，部分单元通过硬件的形式实现。例如，发送单元可以为单独设立的处理元件，也可以集成在网络设备的某一个芯片中实现，此外，也可以以程序的形式存储于网络设备的存储器中，由网络设备的某一个处理元件调用并执行该发送单元的功能。其它单元的实现与之类似。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。此外，以上发送单元可以是一种控制发送的单元，可以通过网络设备的发送装置，例如天线和射频装置接收信息。
以上这些单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)等。再如，当以上某个单元通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(central processing unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
基于相同的技术构思，本申请实施例提供了一种网络设备1400，用于实现上述方法实施例中第一网络设备所执行的功能。具体地，该网络设备1400的硬件结构可以如图14所示，包括至少一个处理器1401，通信总线1402，存储器1403以及至少一个通信接口1404。
处理器1401可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线1402可包括一通路，在上述组件之间传送信息。
通信接口1404，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器1403可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1403用于存储执行本申请方案的应用程序代码，并由处理器1401来控制执行。处理器1401用于执行存储器1403中存储的应用程序代码，从而实现本申请上述实施例提供的API信息传输方法。
或者，可选的，本申请实施例中，也可以是处理器1401执行本申请上述实施例提供的API信息传输方法中的相关功能，通信接口1404负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1401可以包括一个或多个CPU。
在具体实现中，作为一种实施例，该网络设备可以包括多个处理器。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
基于相同的技术构思，本申请实施例提供了一种网络设备，用于实现上述方法实施例中第三网络设备所执行的功能。具体地，该网络设备的硬件结构可以与图14所示结构类似，包括至少一个处理器，通信总线，存储器以及至少一个通信接口。
处理器可以是一个CPU，微处理器，ASIC，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线可包括一通路，在上述组件之间传送信息。
通信接口，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，RAN，WLAN等。
存储器可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器用于存储执行本申请方案的应用程序代码，并由处理器来控制执行。处理器用于执行存储器中存储的应用程序代码，从而实现本申请上述实施例提供的API信息传输方法。
或者，可选的，本申请实施例中，也可以是处理器执行本申请上述实施例提供的API信息传输方法中的相关功能，通信接口负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器可以包括一个或多个CPU。
在具体实现中，作为一种实施例，该网络设备可以包括多个处理器。这些处理器中的每一个可以是一个单核处理器，也可以是一个多核处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
基于相同的技术构思，本申请实施例还提供一种通信系统，包括上述第一网络设备和任一种第三网络设备。
基于相同的技术构思，本申请实施例还提供一种芯片系统，该芯片系统包括处理器，用于支持通信设备实现上述的API信息传输方法。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存通信设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。

Claims (22)

  1. 一种应用编程接口API信息传输方法，其特征在于，包括：
    第一网络设备接收第二网络设备发送的第一请求，所述第一请求中包括终端的标识或终端组的标识，所述第一请求用于请求获取第三网络设备的API的信息；
    所述第一网络设备向所述第二网络设备发送第一指示信息，所述第一指示信息包括所述API信息，所述API信息是根据所述终端接入的网络类型确定的，或者是根据所述终端组接入的网络类型确定的。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述第一网络设备获取所述终端或所述终端组当前接入的网络类型；
    所述第一网络设备根据所述网络类型，确定所述API信息。
  3. 如权利要求2所述的方法，其特征在于，所述第一网络设备获取所述终端或所述终端组当前接入的网络类型，包括：
    所述第一网络设备接收所述第三网络设备发送的第二指示信息，所述第二指示信息包括所述终端当前接入的网络类型，或所述终端组当前接入的网络类型。
  4. 如权利要求3所述的方法，其特征在于，在所述第一网络设备接收所述第三网络设备发送的第二指示信息之前，还包括：
    所述第一网络设备向第三网络设备发送第二请求，包括所述终端的标识或所述终端组的标识；
    所述第二请求用于请求获取所述终端或所述终端组接入的网络类型；或者，
    所述第二请求用于请求在所述终端或所述终端组接入的网络类型发生变化时，向所述第一网络设备发送所述终端或所述终端组当前接入的网络类型。
  5. 如权利要求1所述的方法，其特征在于，还包括：
    所述第一网络设备接收第三网络设备发送的第三指示信息，所述第三指示信息包括所述API信息。
  6. 如权利要求5所述的方法，其特征在于，在所述第一网络设备接收第三网络设备发送的第三指示信息之前，所述方法还包括：
    所述第一网络设备向所述第三网络设备发送第三请求；
    所述第三请求用于请求获取根据所述终端或所述终端组接入的网络类型确定的API信息；或者，
    所述第三请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。
  7. 如权利要求1-6中任一项所述的方法，其特征在于，所述第一请求用于请求获取所述API信息，所述第一指示信息携带在对所述第一请求的响应消息中；或者
    所述第一请求用于请求在所述API信息发生变化时，向所述第二网络设备发送API信息。
  8. 一种应用编程接口API信息传输方法，其特征在于，包括：
    第三网络设备获取终端或终端组接入的网络类型；
    所述第三网络设备向所述第一网络设备发送第一指示信息，所述第一指示信息包括所 述终端或所述终端组接入的网络类型。
  9. 如权利要求8所述的方法，其特征在于，在所述第三网络设备向所述第一网络设备发送第一指示信息之前，所述方法还包括：
    所述第三网络设备接收所述第一网络设备发送的第一请求，所述第一请求包括所述终端的标识或所述终端组的标识，；
    所述第一请求用于请求获取所述终端或所述终端组接入的网络类型，第一指示信息携带在对第一请求的响应消息中，或者，所述第一指示信息是在所述终端或所述终端组接入的网络类型发生变化时发送的；或者，
    所述第一请求用于请求在所述终端或所述终端组接入的网络类型发生变化时，向所述第一网络设备发送所述终端或所述终端组接入的网络类型。
  10. 一种应用编程接口API信息传输方法，其特征在于，包括：
    第三网络设备获取终端或终端组接入的网络类型；
    所述第三网络设备向所述第一网络设备发送第一指示信息，所述第一指示信息包括所述第三网络设备的API的信息，所述API信息是所述第三网络设备根据所述网络类型确定的。
  11. 如权利要求10所述的方法，其特征在于，在所述第三网络设备向所述第一网络设备发送第二指示信息之前，所述方法还包括：
    所述第三网络设备接收所述第一网络设备发送的第一请求，所述第一请求包括所述终端的标识或所述终端组的标识；
    所述第一请求用于请求获取根据所述终端或所述终端组接入的网络类型确定的API信息，所述第一指示信息携带在对第一请求的响应消息中，或者，所述第一指示信息是在所述终端或所述终端组接入的网络类型发生变化时发送的；或者
    所述第一请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。
  12. 一种网络设备，其特征在于，所述网络设备作为第一网络设备，包括：处理器，以及与所述处理器连接的存储器和通信接口；
    所述处理器，用于读取所述存储器中存储的计算机程序执行：
    通过所述通信接口接收第二网络设备发送的第一请求，所述第一请求中包括终端的标识或终端组的标识，所述第一请求用于请求获取第三网络设备的API的信息；
    通过所述通信接口向所述第二网络设备发送第一指示信息，所述第一指示信息包括所述API信息，所述API信息是根据所述终端接入的网络类型确定的，或者是根据所述终端组接入的网络类型确定的。
  13. 如权利要求12所述的网络设备，其特征在于，所述处理器还用于：
    获取所述终端或所述终端组当前接入的网络类型；
    根据所述网络类型，确定所述API信息。
  14. 如权利要求13所述的网络设备，其特征在于，所述处理器在获取所述终端或所述终端组当前接入的网络类型时，具体用于：
    通过所述通信接口接收所述第三网络设备发送的第二指示信息，所述第二指示信息包 括所述终端当前接入的网络类型，或所述终端组当前接入的网络类型。
  15. 如权利要求14所述的网络设备，其特征在于，所述处理器还用于：
    在通过所述通信接口接收所述第三网络设备发送的第二指示信息之前，通过所述通信接口向第三网络设备发送第二请求，包括所述终端的标识或所述终端组的标识；
    所述第二请求用于请求获取所述终端或所述终端组接入的网络类型；或者，
    所述第二请求用于请求在所述终端或所述终端组接入的网络类型发生变化时，向所述第一网络设备发送所述终端或所述终端组当前接入的网络类型。
  16. 如权利要求12所述的网络设备，其特征在于，所述处理器还用于：
    通过所述通信接口接收第三网络设备发送的第三指示信息，所述第三指示信息包括所述API信息。
  17. 如权利要求16所述的网络设备，其特征在于，所述处理器，还用于：
    在通过所述通信接口接收第三网络设备发送的第三指示信息之前，通过所述通信接口向所述第三网络设备发送第三请求；
    所述第三请求用于请求获取根据所述终端或所述终端组接入的网络类型确定的API信息；或者，
    所述第三请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。
  18. 如权利要求12-17中任一项所述的网络设备，其特征在于，所述第一请求用于请求获取所述API信息，所述第一指示信息携带在对所述第一请求的响应消息中；或者
    所述第一请求用于请求在所述API信息发生变化时，向所述第二网络设备发送API信息。
  19. 一种网络设备，其特征在于，所述网络设备作为第三网络设备与第一网络设备进行通信，所述第三网络设备包括：处理器，以及与所述处理器连接的存储器和通信接口；
    所述处理器，用于读取所述存储器中存储的计算机程序执行：
    获取终端或终端组接入的网络类型；
    通过所述通信接口向所述第一网络设备发送第一指示信息，所述第一指示信息包括所述终端或所述终端组接入的网络类型。
  20. 如权利要求19所述的网络设备，其特征在于，所述处理器，还用于：
    在通过所述通信接口向所述第一网络设备发送第一指示信息之前，通过所述通信接口接收所述第一网络设备发送的第一请求，所述第一请求包括所述终端的标识或所述终端组的标识；
    所述第一请求用于请求获取所述终端或所述终端组接入的网络类型，第一指示信息携带在对第一请求的响应消息中，或者，所述第一指示信息是在所述终端或所述终端组接入的网络类型发生变化时发送的；或者，
    所述第一请求用于请求在所述终端或所述终端组接入的网络类型发生变化时，向所述第一网络设备发送所述终端或所述终端组接入的网络类型。
  21. 一种网络设备，其特征在于，所述网络设备作为第三网络设备与第一网络设备进行通信，所述第三网络设备包括：包括：处理器，以及与所述处理器连接的存储器和通信 接口；
    所述处理器，用于读取所述存储器中存储的计算机程序执行：
    获取终端或终端组接入的网络类型；
    通过所述通信接口向所述第一网络设备发送第一指示信息，所述第一指示信息包括所述第三网络设备的API的信息，所述API信息是所述第三网络设备根据所述网络类型确定的。
  22. 如权利要求21所述的网络设备，其特征在于，所述处理器，还用于：
    在通过所述通信接口向所述第一网络设备发送第二指示信息之前，通过所述通信接口接收所述第一网络设备发送的第一请求，所述第一请求包括所述终端的标识或所述终端组的标识；
    所述第一请求用于请求获取根据所述终端或所述终端组接入的网络类型确定的API信息，所述第一指示信息携带在对第一请求的响应消息中，或者，所述第一指示信息是在所述终端或所述终端组接入的网络类型发生变化时发送的；或者
    所述第一请求用于请求在所述API信息发生变化时，向所述第一网络设备发送所述API信息。
PCT/CN2019/087567 2018-05-21 2019-05-20 一种api信息传输方法及装置 WO2019223638A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810491022.0 2018-05-21
CN201810491022.0A CN110519749B (zh) 2018-05-21 2018-05-21 一种api信息传输方法及装置

Publications (1)

Publication Number Publication Date
WO2019223638A1 true WO2019223638A1 (zh) 2019-11-28

Family

ID=68615550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/087567 WO2019223638A1 (zh) 2018-05-21 2019-05-20 一种api信息传输方法及装置

Country Status (2)

Country Link
CN (1) CN110519749B (zh)
WO (1) WO2019223638A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022245667A1 (en) * 2021-05-18 2022-11-24 T-Mobile Innovations Llc User equipment (ue) service over a network exposure function (nef) in a wireless communication network

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116709292A (zh) * 2022-02-28 2023-09-05 华为技术有限公司 一种接口调用方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107438996A (zh) * 2015-03-31 2017-12-05 日本电气株式会社 用于接收通信参数集的通信系统
CN108029007A (zh) * 2015-07-31 2018-05-11 康维达无线有限责任公司 用于小小区网络中的服务层和应用的通知和触发

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170164288A1 (en) * 2014-07-14 2017-06-08 Nec Corporation Method and apparatus for communication management
CN106648557B (zh) * 2015-10-28 2020-04-03 华为技术有限公司 一种应用程序编程接口api的分享方法和装置
CN117082641A (zh) * 2016-08-22 2023-11-17 三星电子株式会社 用于无线通信网络中的区域数据网络配置的方法和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107438996A (zh) * 2015-03-31 2017-12-05 日本电气株式会社 用于接收通信参数集的通信系统
CN108029007A (zh) * 2015-07-31 2018-05-11 康维达无线有限责任公司 用于小小区网络中的服务层和应用的通知和触发

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2(Release 15", 3GPP TS 23. 222, vol. SA WG6, no. V0.1.0, 19 October 2017 (2017-10-19) - 31 October 2017 (2017-10-31), pages 1 - 44, XP051337631 *
HUAWEI ET AL.: "Solution to EN on requirement for discovery policy information", 3GPP TSG-SA WG6 MEETINE S6-171694, vol. SA WG6, 1 December 2017 (2017-12-01) - 3 December 2017 (2017-12-03), XP051381676 *
SAMSUNG: "Pseudo-CR on TS 23.222 CAPIF discover service APIs", 3GPP TSG-SA WG6 MEETING #19 S 6-171359, vol. SA WG6, 9 October 2017 (2017-10-09) - 13 October 2017 (2017-10-13), XP051362553 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022245667A1 (en) * 2021-05-18 2022-11-24 T-Mobile Innovations Llc User equipment (ue) service over a network exposure function (nef) in a wireless communication network
US11956702B2 (en) 2021-05-18 2024-04-09 T-Mobile Innovations Llc User equipment (UE) service over a network exposure function (NEF) in a wireless communication network

Also Published As

Publication number Publication date
CN110519749A (zh) 2019-11-29
CN110519749B (zh) 2021-07-20

Similar Documents

Publication Publication Date Title
US11425634B2 (en) Slice information update method and apparatus
US11758504B2 (en) Selection method, selection device, management function entity, access network node, GMLC and NRF
WO2021017689A1 (zh) 一种用户面数据的获取方法、装置及存储介质
US11457334B2 (en) Context management method and apparatus
US11533666B2 (en) Communication method, communications apparatus, and communications system
US20220264428A1 (en) Method for controlling use of network slice, apparatus, and system
CN114270789B (zh) 一种获取信息的方法及装置
KR102596924B1 (ko) 이벤트 통지 방법, 장치 및 저장매체
WO2019075623A1 (zh) 一种移动性管理的方法、装置及系统
US11877188B2 (en) Implementing a fault-tolerant multi-NRF network topology
US20220377653A1 (en) Slice information update method and apparatus
US20200280892A1 (en) Session context handling method, network element, and terminal device
EP4124094A1 (en) Policy determination method and device, and system
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2021170033A1 (zh) 一种网络配置方法及装置
WO2020200122A1 (zh) 一种通信方法及装置
WO2019223638A1 (zh) 一种api信息传输方法及装置
EP4024940A1 (en) Communication method and apparatus
CN110730487A (zh) 一种选择会话管理功能网元的方法、装置及系统
WO2021134175A1 (zh) 一种漫游的方法、装置及系统
US20230037402A1 (en) Communication method, apparatus, and system
WO2022151967A1 (en) Methods, network nodes, and computer readable media for dynamically discovering serving network node in core network
WO2019061400A1 (en) IMPROVED SERVICE DISCOVERY FOR THE NETWORK FUNCTION ASSOCIATION
CN116321110B (zh) 服务订阅方法、装置、服务提供网元及存储介质
WO2023220998A1 (zh) 无线通信的方法、用户设备及网络设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19807919

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19807919

Country of ref document: EP

Kind code of ref document: A1