Service instance selection methods, network architecture, devices, and storage media

Abstract

This application provides a service instance selection method, network architecture, device, and storage medium. The method includes: an nRIC service instance registering the API corresponding to its wireless capability with an API registration unit by sending an API registration request message; the API registration request message carrying the API's service area information; when a business application system initiates an API call request to the NEF using a terminal identifier, the NEF selects a target nRIC service instance using the terminal identifier and the API's service area information discovered by the NEF; and forwards the API call request to the target nRIC service instance. This technical solution improves the accuracy of service instance selection.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular to a service instance selection method, network architecture, device, and storage medium. Background Technology

[0002] Currently, the core network defines the Network Exposure Function (NEF) to realize network capability exposure. It can support applications to securely provide some user behavior and service-related information to the 3GPP network, and also support the external exposure of core network data analysis capabilities.

[0003] To enable open capabilities of the radio access network, a near-real-time RAN intelligent controller (nRIC) is provided under the Open-Radio Access Network (O-RAN) network architecture. The nRIC includes multiple xApps, which can implement multiple features such as QoS optimization and cell load balancing. It can also be responsible for implementing the same feature in different ranges.

[0004] In the process of opening up wireless capabilities based on nRIC, when business applications call the API of wireless capabilities, NEF is currently unable to determine a suitable nRIC service instance, which leads to the problem of low accuracy in service instance selection. Summary of the Invention

[0005] This application provides a service instance selection method, network architecture, device, and storage medium that can improve the accuracy of service instance selection.

[0006] The technical solution of this application is implemented as follows:

[0007] In a first aspect, embodiments of this application provide a service instance selection method, the method comprising:

[0008] The near real-time wireless intelligent controller (nRIC) service instance registers the API corresponding to the wireless capability with the API registration unit by sending an API registration request message to the API registration unit; the API registration request message carries the service area information of the API.

[0009] When a business application system initiates a call request to the API using a terminal identifier to the Network Open Function (NEF), the NEF uses the terminal identifier and the service area information of the API discovered by the NEF to select a target nRIC service instance; and forwards the API call request to the target nRIC service instance.

[0010] Secondly, embodiments of this application provide a network architecture, the architecture comprising:

[0011] An nRIC service instance is used to register the API corresponding to the wireless capability on the API registration unit by sending an API registration request message to the API registration unit; the API registration request message carries the service area information of the API.

[0012] NEF is used to select a target nRIC service instance by utilizing the terminal identifier and the service area information of the API discovered by the NEF when a business application system initiates a call request to the API using the terminal identifier. The NEF then forwards the API call request to the target nRIC service instance.

[0013] Thirdly, embodiments of this application provide a network device, characterized in that the device includes: a processor, a memory, and a communication bus; when the processor executes a running program stored in the memory, it implements the service instance selection method as described in any of the above.

[0014] Fourthly, embodiments of this application provide a storage medium storing a computer program thereon, characterized in that the computer program, when executed by a processor, implements the service instance selection method as described in any of the preceding claims.

[0015] This application provides a service instance selection method, network architecture, device, and storage medium. The method includes: an nRIC service instance registering the API corresponding to its wireless capability on the API registration unit by sending an API registration request message; the API registration request message carries the service area information of the API; when a business application system initiates a call request for the API to the NEF using a terminal identifier, the NEF selects a target nRIC service instance using the terminal identifier and the service area information of the API discovered by the NEF; and forwards the API call request to the target nRIC service instance. Using the above implementation, when the online API registration unit of the nRIC service instance sends an API registration request message, it carries the service area information of the API in the API registration request message. Then, when a business application system initiates a call request for the API to the NEF, the NEF can use the terminal identifier and the API service area information to determine the target service area where the terminal identifier is located, and then determine the nRIC service instance corresponding to the target service area as the target nRIC service instance. This can accurately find the nRIC service instance in the area where the terminal is located, thereby improving the accuracy of service instance selection. Attached Figure Description

[0016] Figure 1 A flowchart illustrating a service instance selection method provided in this application embodiment;

[0017] Figure 2 A schematic diagram of an exemplary nRIC architecture provided for embodiments of this application;

[0018] Figure 3 A schematic diagram of an exemplary network architecture for implementing wireless capability openness based on nRIC, provided for embodiments of this application;

[0019] Figure 4 An interactive diagram illustrating an exemplary service instance selection process provided in this application embodiment;

[0020] Figure 5 An interactive diagram illustrating another exemplary service instance selection process provided in this application embodiment;

[0021] Figure 6 A schematic diagram illustrating the composition of a network architecture provided in an embodiment of this application;

[0022] Figure 7 This is a schematic diagram of the composition structure of a network device provided in an embodiment of this application. Detailed Implementation

[0023] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit the scope of this application.

[0024] This application provides a service instance selection method. Figure 1 A flowchart of a method provided in an embodiment of this application is shown below. Figure 1 As shown, the method may include:

[0025] S101 and nRIC service instances register the API corresponding to their wireless capabilities on the API registration unit by sending an API registration request message; the API registration request message carries the service area information of the API.

[0026] It should be noted that the nRIC architecture, such as Figure 2 As shown, the nRIC includes an E2 interface, database, shared data layer, A1 termination, O1 termination, and API enabling section. The API enabling section includes multiple xApps, a messaging infrastructure module, a conflict mitigation module, a subscription management module, a management service module, a security module, and an Artificial Intelligence (AI) / Machine Learning (ML) support module. The E2 interface connects to the base station (…). Figure 2 The E2 node is connected, the A1 end is connected to the non-real-time wireless intelligent controller of the SMO, and the O1 end is connected to the SMO.

[0027] The service instance selection method provided in this application is applied to a network architecture for wireless capability openness based on nRIC. This network architecture can be referenced from... Figure 3 The nRIC, API registration unit, NEF / local NEF, and base stations all belong to the Public Land Mobile Network (PLMN) domain. The nRIC connects to the base station via the E2 interface to collect radio data from the base station in near real-time, analyzes and processes it using AI / ML technologies, and issues commands using the control capabilities provided by the base station (such as modifying DRB configuration and scheduling priorities) to achieve intelligent control and optimization of radio resources. This processing is generally implemented through multiple xApps within the nRIC. The nRIC registers the radio capability open APIs generated by the xApps with the API registration unit.

[0028] It should be noted that the API registration unit can be either the core functionality of the Common API Framework for 3GPP Northbound APIs (CAPIF) or NEF, and the choice should be made based on the actual situation. This application does not impose any specific limitations on this embodiment.

[0029] It should be noted that the "radio capabilities" exposed by nRIC include the following two categories: First, the xApp or nRIC platform processes and abstracts data collected from base stations (such as cell / slice / user configuration, UE measurement reports, cell / slice / UE performance measurements, signaling), and provides the generated radio dynamic information (such as available bandwidth prediction) to external service application systems to assist them in optimizing their services. Second, the xApp or nRIC platform can obtain service dynamic information (such as dynamic changes in required bandwidth) from service application systems to intelligently control base stations and adapt to dynamic changes in services. These exposed radio capabilities are defined in the form of APIs. For example, a RAN analysis information service API is used to provide a UE radio bandwidth prediction capability subscription service, with relevant input and output data including: UE ID, reporting interval, bandwidth unit, confidence level, etc.

[0030] In this embodiment, the nRIC service instance carries API service area information in the API registration request message sent to the API registration unit. This information is used to indicate the region of the API service.

[0031] Optionally, the service area information of the API includes at least one of the following: the cell identifier corresponding to the API, the base station identifier corresponding to the API, and the tracking area list corresponding to the API. The specific selection can be made according to the actual situation, and this application embodiment does not impose specific limitations.

[0032] For example, the service area information of the API can be found in Table 1.

[0033] Table 1

[0034] Service Area Information Types and Reference Information Semantic description Base station node identifier list Array (Base Station Node Identifiers) List of gNB or eNB identifiers Community Identification List Array (cell identifier) Community Identification List Tracking Area List Array (Tracking Area) Tracking Area List

[0035] In this embodiment of the application, after registering the API corresponding to the wireless capability on the API registration unit, NEF discovers multiple nRIC service instances of the registered API and multiple service area information from the multiple nRIC service instances; NEF aggregates the multiple nRIC service instances into a corresponding API and sets the endpoint address to the NEF address.

[0036] It should be noted that multiple nRIC service instances can register for the same API. NEF discovers multiple nRIC service instances that have registered the API, as well as multiple service region information from these nRIC service instances. NEF aggregates these multiple nRIC service instances into a single API and exposes it to the business application system, setting the endpoint address for calling this API to the NEF / local NEF address. The multiple service region information is hidden from the business application system.

[0037] S102. When a business application system initiates an API call request to NEF using a terminal identifier, NEF uses the terminal identifier and the service area information of the API discovered by NEF to select a target nRIC service instance; and forwards the API call request to the target nRIC service instance.

[0038] In this embodiment of the application, the business application system obtains the endpoint address and uses the terminal identifier to initiate a call request to NEF for an API.

[0039] It should be noted that the business application system obtains the endpoint address through the service registration or discovery mechanism and uses the endpoint identifier to initiate an API call request to NEF.

[0040] refer to Figure 3 The Application Function (AF) system discovers the open API for wireless capabilities through the NEF / local NEF. The AF then initiates an API call request to the NEF / local NEF. The NEF / local NEF forwards the API call request to the corresponding nRIC service instance.

[0041] In this embodiment, the NEF queries the 5G core network 5GC network function NF for the terminal location based on the terminal identifier; the NEF selects the target service area information where the terminal is located from multiple service area information; and finds the target nRIC service instance corresponding to the target service area information.

[0042] In this embodiment of the application, the 5GC NF includes a Session Management Function (SMF) / Binding Support Function (BSF) and an Authentication Management Function (AMF). Specifically, the NEF / local NEF uses the terminal identifier to query the SUPI from the SMF / BSF, and then the NEF / local NEF uses the SUPI to find the terminal location of the terminal from the AMF.

[0043] Understandably, when the online API registration unit of the nRIC service instance sends an API registration request message, it carries the API's service area information in the API registration request message. Subsequently, when the business application system initiates a call request to the NEF for this AIP, the NEF can use the terminal identifier and the API's service area information to determine the target service area where the terminal identifier is located. Then, it can identify the nRIC service instance corresponding to the target service area as the target nRIC service instance, which can accurately find the nRIC service instance in the region where the terminal is located, thereby improving the accuracy of service instance selection.

[0044] For example, based on the above embodiments, this application proposes an exemplary method for selecting service instances for wireless capability exposure, such as... Figure 4 As shown, the method may include:

[0045] 1. Multiple nRIC instances register the same open API for wireless capabilities with the API registration unit and carry a list of cell identifiers for the service area in the API configuration file.

[0046] It should be noted that the API configuration file is sent to the API registration unit along with the API registration request message.

[0047] 2. NEF discovers multiple nRIC service instances and multiple API configuration files from multiple nRIC service instances, and NEF aggregates multiple nRIC service instances into a single API.

[0048] 3. NEF exposes a single aggregated API to AF, with the endpoint address being (Local)NEF.

[0049] 4. AF sends an API call request to NEF, carrying the terminal identifier.

[0050] 5. NEF uses the terminal identifier to query SUPI from SMF / BSF.

[0051] 6. NEF uses SUPI to query the AMF for the cell identifier where the terminal is located.

[0052] It should be noted that the method for querying the cell identifier of the terminal is the "Namf_Location_ProvideLocationInfo" service operation defined in 3GPP TS 23.502.

[0053] 7. NEF searches for the target API configuration file containing the cell identifier of the terminal among multiple API configuration files, and the nRIC service instance to which it belongs is the target service instance.

[0054] It should be noted that this matching result can be used for subsequent API service requests to the same terminal.

[0055] 8. NEF target service instances forward API call requests.

[0056] It should be noted that if the API registration request message in this embodiment only carries the service instance identifier corresponding to the nRIC service instance, then between S101 and S102, the following steps are also included: the Service Management and Orchestration (SMO) discovers the service instance identifier; the SMO determines and maintains the service area information of the service instance identifier.

[0057] Correspondingly, when a business application system uses a terminal identifier to initiate an API call request to NEF, NEF uses the service area information of the terminal identifier and the service instance identifier maintained by the SMO to select the target nRIC service instance.

[0058] Specifically, NEF queries the 5GC NF for the terminal location based on the terminal identifier; NEF queries the SMO for the target service area information corresponding to the terminal location, as well as the target nRIC service instance corresponding to the target service area information.

[0059] Optionally, the service area information of the service instance identifier includes at least one of the following: the cell identifier corresponding to the service instance identifier, the base station identifier corresponding to the service instance identifier, and the tracking area list corresponding to the service instance identifier. The specific selection can be made according to the actual situation, and this application embodiment does not impose specific limitations.

[0060] It should be noted that the service area information of the service instance identifier and the service area information of the API are inclusive, that is, the service area information of the service instance identifier can contain the service area information of one or more APIs. The specific selection can be made according to the actual situation, and this application embodiment does not make specific limitations.

[0061] It should be noted that in this solution, the nRIC instance does not need to carry the service region information of the API in the API registration request information, but instead carries the service instance identifier in the API registration request information.

[0062] In this embodiment of the application, the SMO discovers the service instance identifier, determines and maintains the service area information corresponding to the service instance identifier.

[0063] In this embodiment of the application, after NEF / local NEF finds the terminal location based on the terminal identifier, NEF directly queries the SMO for the target service area information corresponding to the terminal location, as well as the target nRIC service instance corresponding to the target service area information.

[0064] Understandably, when the online API registration unit for the nRIC service instance sends an API registration request message, it carries the nRIC service instance identifier within the message. The SMO discovers the nRIC service instance identifier, determines and maintains the service area information corresponding to it. Subsequently, when a business application system initiates a call request to the NEF for this AIP, the NEF can use the terminal identifier and the service area information of the nRIC service instance identifier maintained in the SMO to determine the target service area where the terminal identifier is located. Then, the nRIC service instance corresponding to the target service area is identified as the target nRIC service instance. This allows for accurate location of the nRIC service instance in the terminal's region, thereby improving the accuracy of service instance selection.

[0065] For example, based on the above embodiments, this application proposes an exemplary method for selecting service instances for wireless capability exposure, such as... Figure 5 As shown, the method may include:

[0066] 1. Multiple nRIC instances register the same wireless capability open API with the API registration unit and carry the nRIC service instance identifier in the API configuration file.

[0067] 2. The SMO discovers the nRIC service instance identifier, determines and maintains the service area information corresponding to the nRIC service instance identifier.

[0068] 3. NEF discovers multiple nRIC service instances and multiple API configuration files from multiple nRIC service instances, and NEF aggregates multiple nRIC service instances into a single API.

[0069] 4. NEF exposes a single aggregated API to AF, with the endpoint address being (Local)NEF.

[0070] 5. AF sends an API call request to NEF, carrying the terminal identifier.

[0071] 6. NEF uses the terminal identifier to query SUPI from SMF / BSF.

[0072] 7. NEF uses SUPI to query the AMF for the cell identifier where the terminal is located.

[0073] 8. NEF queries the SMO for the nRIC service instance identifier corresponding to the cell identifier, which is the target service instance.

[0074] 9. NEF target service instance forwards API call requests.

[0075] Based on the above embodiments, in another embodiment of this application, a network architecture 1 is provided. Figure 6 A schematic diagram of the composition structure of a network architecture provided in this application is shown below. Figure 6 As shown, the network architecture 1 includes:

[0076] nRIC service instance 10 is used to register the API corresponding to the wireless capability on the API registration unit by sending an API registration request message to the API registration unit; the API registration request message carries the service area information of the API.

[0077] NEF11 is used to select a target nRIC service instance by utilizing the terminal identifier and the service area information of the API discovered by the NEF when the business application system 2 initiates a call request for the API to the NEF using the terminal identifier; and to forward the call request for the API to the target nRIC service instance.

[0078] In some embodiments of this application, the NEF11 is further configured to discover multiple nRIC service instances that register the API and multiple service area information from the multiple nRIC service instances; aggregate the multiple nRIC service instances into a single API, and set the endpoint address to the NEF address;

[0079] The business application system 2 is used to obtain the endpoint address; and use the terminal identifier to initiate a call request to an API to the NEF.

[0080] In some embodiments of this application, the NEF11 is further configured to query the 5G core network 5GC network function NF for the terminal location based on the terminal identifier; select the target service area information where the terminal location is located from the plurality of service area information; and find the target nRIC service instance corresponding to the target service area information.

[0081] In some embodiments of this application, the service area information of the API includes at least one of the following:

[0082] The API corresponds to the cell identifier, the API corresponds to the base station identifier, and the API corresponds to the tracking area list.

[0083] In some embodiments of this application, if the API registration request message carries a service instance identifier corresponding to the nRIC service instance,

[0084] SMO3 is used to discover the service instance identifier; determine and maintain the service area information of the service instance identifier;

[0085] NEF11 is also used to select a target nRIC service instance by utilizing the service area information of the terminal identifier and the service instance identifier maintained by the SMO when the business application system initiates a call request to the API to NEF using the terminal identifier.

[0086] In some embodiments of this application, the NEF11 is further configured to query the terminal location from the 5GC NF based on the terminal identifier; query the target service area information corresponding to the terminal location from the SMO, and the target nRIC service instance corresponding to the target service area information.

[0087] In some embodiments of this application, the service area information of the service instance identifier includes at least one of the following:

[0088] The service instance identifier corresponds to the cell identifier, the service instance identifier corresponds to the base station identifier, and the service instance identifier corresponds to the tracking area list.

[0089] This application provides a network architecture including: an nRIC service instance, used to register an API corresponding to a wireless capability with an API registration unit by sending an API registration request message; the API registration request message carries the service area information of the API; and a NEF, used to select a target nRIC service instance by utilizing the terminal identifier and the service area information of the API discovered by the NEF when a business application system initiates a call request to the NEF using a terminal identifier, and forwards the API call request to the target nRIC service instance. Using the above network architecture, when the online API registration unit of the nRIC service instance sends an API registration request message, it carries the API's service area information in the message. Then, when a business application system initiates a call request to the NEF for the API, the NEF can use the terminal identifier and the API's service area information to determine the target service area where the terminal identifier is located, and then identify the nRIC service instance corresponding to the target service area as the target nRIC service instance. This accurately locates the nRIC service instance in the area where the terminal is located, thereby improving the accuracy of service instance selection.

[0090] Figure 7 This is a schematic diagram of the composition structure of a network device provided in an embodiment of this application. In practical applications, based on the same disclosed concept of the above embodiments, such as... Figure 7 As shown, the network device 2 in this embodiment includes: a processor 20, a memory 21, and a communication bus 22.

[0091] In specific embodiments, the processor 20 can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), CPU, controller, microcontroller, and microprocessor. It is understood that for different devices, the electronic device used to implement the processor function can also be other types, and this embodiment does not impose specific limitations.

[0092] In this embodiment, the communication bus 22 is used to realize the connection communication between the processor 20 and the memory 21; when the processor 20 executes the running program stored in the memory 21, it implements the following service instance selection method:

[0093] A near real-time wireless intelligent controller (nRIC) service instance registers the API corresponding to its wireless capabilities with an API registration unit by sending an API registration request message. The API registration request message carries the service area information of the API. When a business application system initiates a call request to the API using a terminal identifier to the Network Open Function (NEF), the NEF uses the terminal identifier and the service area information of the API discovered by the NEF to select a target nRIC service instance and forwards the API call request to the target nRIC service instance.

[0094] In some embodiments of this application, the processor 20 is further configured to: discover multiple nRIC service instances that register the API and multiple service area information from the multiple nRIC service instances; aggregate the multiple nRIC service instances into a corresponding API and set the endpoint address to the NEF address; obtain the endpoint address and use the terminal identifier to initiate a call request to the NEF for an API.

[0095] In some embodiments of this application, the processor 20 is further configured to: query the 5G core network 5GC network function NF for the terminal location based on the terminal identifier; select the target service area information where the terminal location is located from the plurality of service area information; and search for the target nRIC service instance corresponding to the target service area information.

[0096] In some embodiments of this application, the service area information of the API includes at least one of the following:

[0097] The API corresponds to the cell identifier, the API corresponds to the base station identifier, and the API corresponds to the tracking area list.

[0098] In some embodiments of this application, if the API registration request message carries a service instance identifier corresponding to the nRIC service instance,

[0099] The processor 20 is further configured to: discover the service instance identifier using the operator network management system (SMO); determine and maintain the service area information of the service instance identifier; and, when a business application system uses a terminal identifier to initiate a call request to the API to the NEF, the NEF uses the terminal identifier and the service area information of the service instance identifier maintained by the SMO to select a target nRIC service instance.

[0100] In some embodiments of this application, the processor 20 is further configured to allow the NEF to query the terminal location from the 5GC NF based on the terminal identifier; the NEF queries the SMO for target service area information corresponding to the terminal location, and the target nRIC service instance corresponding to the target service area information.

[0101] In some embodiments of this application, the service area information of the service instance identifier includes at least one of the following:

[0102] The service instance identifier corresponds to the cell identifier, the service instance identifier corresponds to the base station identifier, and the service instance identifier corresponds to the tracking area list.

[0103] This application provides a storage medium storing a computer program thereon. The computer-readable storage medium stores one or more programs, which can be executed by one or more processors and applied in a network device. The computer program implements the service instance selection method described above.

[0104] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0105] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause an image display device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0106] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A service instance selection method, characterized in that, The method includes: The near real-time wireless intelligent controller (nRIC) service instance registers the API corresponding to the wireless capability with the API registration unit by sending an API registration request message to the API registration unit; the API registration request message carries the service area information of the API. When a business application system initiates a call request to the API using a terminal identifier to the Network Open Function (NEF), the NEF uses the terminal identifier and the service area information of the API discovered by the NEF to select a target nRIC service instance; and forwards the API call request to the target nRIC service instance.

2. The method according to claim 1, characterized in that, After registering the wireless capability API on the API registration unit, and before the NEF selects a target nRIC service instance using the terminal identifier and the service area information of the API discovered by the NEF, the method further includes: The NEF discovers multiple nRIC service instances that register the API and multiple service area information from the multiple nRIC service instances; The NEF aggregates the multiple nRIC service instances into a single API and sets the endpoint address to the NEF address. The business application system obtains the endpoint address and uses the terminal identifier to initiate a call request to an API to the NEF.

3. The method according to claim 1 or 2, characterized in that, The NEF uses the terminal identifier and the service area information of the API discovered by the NEF to select a target nRIC service instance, including: The NEF queries the 5G core network 5GC network function NF for the terminal location based on the terminal identifier; The NEF selects the target service area information where the terminal is located from multiple service area information; and finds the target nRIC service instance corresponding to the target service area information; wherein, the multiple service area information are multiple service area information from multiple nRIC service instances; the multiple nRIC service instances are multiple nRIC service instances that have registered the API.

4. The method according to claim 1, characterized in that, The service area information of the API includes at least one of the following: The API corresponds to the cell identifier, the API corresponds to the base station identifier, and the API corresponds to the tracking area list.

5. The method according to claim 1, characterized in that, If the API registration request message carries a service instance identifier corresponding to the nRIC service instance, the method further includes: The operator's network management system (SMO) discovers the service instance identifier; the SMO determines and maintains the service area information of the service instance identifier. When a business application system initiates a call request to the API from the NEF using a terminal identifier, the NEF uses the terminal identifier and the service area information of the service instance identifier maintained by the SMO to select a target nRIC service instance.

6. The method according to claim 5, characterized in that, The NEF uses the service area information of the terminal identifier and the service instance identifier maintained by the SMO to select a target nRIC service instance, including: The NEF queries the 5GC NF for the terminal location based on the terminal identifier; The NEF queries the SMO for target service area information corresponding to the terminal location, and the target nRIC service instance corresponding to the target service area information.

7. The method according to claim 5, characterized in that, The service area information identified by the service instance includes at least one of the following: The service instance identifier corresponds to the cell identifier, the service instance identifier corresponds to the base station identifier, and the service instance identifier corresponds to the tracking area list.

8. A network architecture, characterized in that, The architecture includes: A near real-time wireless intelligent controller (nRIC) service instance is used to register the API corresponding to the wireless capability on the API registration unit by sending an API registration request message to the API registration unit; the API registration request message carries the service area information of the API. The Network Open Function (NEF) is used to select a target nRIC service instance when a business application system initiates a call request to the NEF for the API using a terminal identifier. The NEF then uses the terminal identifier and the service area information of the API discovered by the NEF to forward the API call request to the target nRIC service instance.

9. A network device, characterized in that, The device includes: a processor, a memory, and a communication bus; when the processor executes the running program stored in the memory, it implements the method as described in any one of claims 1-7.

10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

Images