Information processing device, method, and program

Abstract

To improve processing delay associated with disclosing a network function of a predetermined network.SOLUTION: A information processing device includes a control unit configured to execute receiving a request including at least two identification information among a plurality of identification information for designating a type of information in each of first service and second service for disclosing a network function of a predetermined network, and conditions for combining at least two information obtained for each of the at least two identification information, and transmitting first information obtained by combining the at least two information according to the conditions.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device and an information processing method. [Background technology]

[0002] In the 5G core network, network functions (NF) are provided as services. The Network Exposure Function (NEF) was introduced, which is a function that exposes network information to third parties such as network service providers. The network functions that are made public include various functions such as statistical information analysis, event monitoring, provisioning of UE (User Equipment) related parameters, and QoS monitoring of UE. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.502 V17.4.0 “Procedures for the 5G System (5GS); Stage 2 (Release 17),” March 2022 [Non-patent document 2] 3GPP TS 23.288 V17.4.0 “Architecture enhancements for 5G System (5GS) to support network data analytics services(Release 17)”, March 2022 [Non-patent document 3] 3GPP TSG-WG SA2 Meeting #150E e-meeting, “TR 23.700-80: KI#7 - 5GS assistance for FL member selection using QoS monitoring”, April 6-12, 2022 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present disclosure is to provide an information processing device and method capable of reducing processing delays associated with publishing a network function of a predetermined network. [Means for solving the problem]

[0005] One aspect of the present disclosure is Receiving a request including at least two pieces of identification information among a plurality of pieces of identification information specifying types of information in each of a first service and a second service that expose a function of a predetermined network, and a condition for combining at least two pieces of information obtained for each of the at least two pieces of identification information; transmitting first information obtained by combining the at least two pieces of information in accordance with the condition; The information processing device is provided with a control unit that executes the above.

[0006] Another aspect of the present disclosure is The computer Receiving a request including at least two pieces of identification information among a plurality of pieces of identification information specifying types of information in each of a first service and a second service that expose a function of a predetermined network, and a condition for combining at least two pieces of information obtained for each of the at least two pieces of identification information; transmitting first information obtained by combining the at least two pieces of information in accordance with the condition; This is a method for doing this. [Effects of the Invention]

[0007] According to the present disclosure, it is possible to improve the processing delay involved in publishing a network function of a predetermined network. [Brief explanation of the drawings]

[0008] [Figure 1]FIG. 1 is a diagram illustrating an example of a system configuration of a network system according to the first embodiment. [Figure 2] FIG. 2 shows an example of the hardware configuration of an NEF server. [Figure 3] FIG. 3 is a diagram illustrating an example of the functional configuration of the NEF server. [Figure 4] Figure 4 is an example of the Subscribe API specification. [Figure 5] Figure 5 is an example of the Notify API specification. [Figure 6] FIG. 6 is an example of a flowchart of the Subscribe API process. [Figure 7] FIG. 7 is an example of a flowchart of the Notify API process. [Figure 8] FIG. 8 is a diagram showing an example of the sequence of the Nnef_CompositeExposure service. DETAILED DESCRIPTION OF THE INVENTION

[0009] For example, NEF exposes network functions as APIs (Application Programming Interfaces). An API is prepared for each service, and for example, By using the API, an F (Application Function) can access the NEF and use desired network functions through the NEF.

[0010] Examples of services that obtain information within the network include Nnef_EventExposure and Nnef_AnalyticsExposure. Nnef_EventExposure is a service that reports the results of event monitoring. Events include, for example, UE connectivity (UE reachability), These include loss of connectivity, location reporting, and the number of UEs present in a geographical area. Nnef_AnalyticsExposure is a service that reports network statistics, such as network performance information, QoS information, and congestion information.

[0011] For example, suppose there is information A and B that can be obtained by Nnef_EventExposure, and information X that can be obtained by Nnef_AnalyticsExposure. When it is desired to obtain information compounded by the logical sum or logical product of information A and information X, the requesting device that requests the information obtains information A and information X from NEF via the Nnef_EventExposure API and the Nnef_AnalyticsExposure API, respectively, and performs a logical sum or logical product operation on information A and information X. Also, when it is desired to obtain information compounded by the logical product of information A and information B, the requesting device obtains information A and information B from NEF via the Nnef_EventExposure API, and performs a logical product operation on information A and information B.

[0012] As described above, when a requesting device wishes to acquire information obtained by combining information provided by different services through a logical product or logical sum, or when a requesting device wishes to acquire information obtained by combining multiple types of information from the same service through a logical product, the requesting device performs processing in multiple steps. In view of this, one aspect of the present disclosure enables a requesting device to acquire information obtained by combining multiple types of information through a logical product or logical sum in one step. Note that similar issues are not limited to those occurring in 5G core networks, but may occur in any network that exposes network functions to the outside.

[0013] Specifically, one aspect of the present disclosure is an information processing device including a control unit that receives a request and transmits a notification corresponding to the request, the request including a plurality of pieces of identification information that specify types of information in a first service and a second service, respectively. The request includes at least two pieces of identification information and a condition for combining the at least two pieces of information obtained for each of the at least two pieces of identification information. The first service and the second service are services that publish network functions of a predetermined network. The notification corresponding to the request is the first information obtained by combining the at least two pieces of information in accordance with the condition.

[0014] For example, a service that exposes network functions of a predetermined network is an NEF. The information processing device is, for example, a dedicated server that operates as an NEF in a 5G core network. Note that the device that operates as an NEF is not limited to a dedicated server, and may be any device equipped with a computer. The control unit is, for example, a processor such as a CPU (Central Processing Unit) and a DSP (Digital Signal Processor). In addition, the NEF and The device that operates as the NEF may be a dedicated device, and the control unit may be a dedicated circuit configured to be able to perform the operations of the NEF.

[0015] If the service that exposes network functions of a predetermined network is NEF, the first service is, for example, an Nnef_EventExposure service. If the first service is the Nnef_EventExposure service, the plurality of identification information specifying the type of information in the first service is an Event ID. If the second service is the Nnef_AnalyticsExposure service, the plurality of identification information specifying the type of information in the second service is an Analytics ID. The condition for combining at least two pieces of information obtained for the identification information is at least one of a logical sum and a logical product. Note that the service that exposes network functions of a predetermined network is not limited to NEF. Furthermore, the first service and the second service are not limited to the Nnef_EventExposure service and the Nnef_AnalyticsExposure service, and may be any NEF service.

[0016] According to one aspect of the present disclosure, a requesting device can obtain information in which a desired type of information is combined according to desired conditions simply by transmitting a request. Therefore, the requesting device can obtain the desired information by performing a one-step process. This also reduces the processing delay until the requesting device obtains the desired information. Furthermore, communication between the information processing device and the requesting device can be limited to transmitting a request from the requesting device to the information processing device and transmitting first information from the information processing device to the requesting device. This reduces the amount of data communication between the information processing device and the requesting device, thereby reducing network bandwidth consumption.

[0017] For example, in the case of NEF, a requesting device can execute a single API to obtain multiple types of information for multiple services, or obtain information that combines multiple types of information according to specified conditions.

[0018] In one aspect of the present disclosure, the request may include action information that specifies an action to be performed on the user equipment included in the first information. In this case, the control unit may execute the action specified by the action information included in the request on the user equipment included in the first information. This allows the requesting device to execute the specified action on a specific UE simply by sending a request, thereby improving processing efficiency.

[0019] In one aspect of the present disclosure, the request may further include application identification information specifying an application. In this case, the control unit may transmit second information from the first information that matches the application identification information. This allows the requesting device to obtain the second information extracted for the desired application.

[0020] In one aspect of the present disclosure, the request may further include area identification information specifying a target area. In this case, the control unit may transmit third information from the first information that matches the area identification information. This allows the requesting device to obtain the extracted third information related to the desired area.

[0021] In another aspect, the present disclosure can be specified as a method. The method includes receiving, by a computer, a request including at least two pieces of identification information among a plurality of pieces of identification information specifying types of information in each of a first service and a second service that expose network functions of a predetermined network, and a condition for combining at least two pieces of information obtained for each of the at least two pieces of identification information, and transmitting first information obtained by combining the at least two pieces of information in accordance with the condition. In another aspect, the present disclosure can be specified as a program for causing a computer to execute processing of the information processing device described above, and a non-transitory computer-readable recording medium having the program recorded thereon.

[0022] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. The configurations of the following embodiments are examples, and the present disclosure is not limited to the configurations of the embodiments.

[0023] First Embodiment FIG. 1 is a diagram illustrating an example of a system configuration of a network system 500 according to the first embodiment. The network system 500 includes a core network 100. In the first embodiment, it is assumed that the core network 100 is a 5G network system. The core network 100 includes an NEF server 1. The NEF server 1 is a server that implements an NEF, which is one of the network functions (NF) in a 5G core network. The core network 100 also includes, as NFs, servers that implement functions such as an Access and Mobility Management Function (AMF), a Network Data Analytics Function (NWDAF), a Session Management Function (SMF), a User Data Repository (UDR), and a Unified Data Management (UDM).

[0024] The AF (Application Function) server 50 is, for example, an external device managed by a third-party service provider, etc. In the first embodiment, the description will be given assuming that the requesting device that receives the NEF service is the AF server 50. However, the requesting device that receives the NEF service is not limited to the AF server 50.

[0025] When the NEF server 1 receives a request from the AF server 50 to disclose the network functions of the core network 100, it queries the corresponding NF and performs processing according to the request. In the first embodiment, the NEF server 1 provides the Nnef_CompositeExposure service, which provides information obtained by combining multiple specified types of information that can be acquired by the Nnef_EventExposure service and the Nnef_AnalyticsExposure service under specified conditions.

[0026] In the Nnef_EventExposure service, the NEF server 1 receives an Nnef_EventExposure_Subscribe request requesting the disclosure of information from the AF server 50. The Nnef_EventExposure_Subscribe request includes an event ID that specifies the type of information to be acquired. The NEF server 1 acquires information corresponding to the event ID from the NF corresponding to the event ID in the core network 100, and notifies the AF server 50 of the information by sending an Nnef_EventExposure_Notify message. It is sent to the server 50. The Nnef_EventExposure_Subscribe request is an example of a "request."

[0027] In the Nnef_AnalyticsExposure service, the NEF server 1 also receives an Nnef_AnalyticsExposure_Subscribe request from the AF server 50 requesting the disclosure of information. The Nnef_AnalyticsExposure_Subscribe request includes an Analytics ID that specifies the type of information to be acquired. The NEF server 1 acquires information corresponding to the Analytics ID from the NF corresponding to the Analytics ID in the core network 100, and transmits it to the AF server 50 by means of an Nnef_AnalyticsExposure_Notify message. Nnef_EventExposure_Subscribe, Nnef_EventExposure_Notify, Nnef_AnalyticsExposure_Subscribe, and Nnef_AnalyticsExposure_Notify are each provided as different APIs. do.

[0028] On the other hand, in the Nnef_CompositeExposure service, the NEF server 1 receives an Nnef_CompositeExposure_Subscribe request requesting the disclosure of information from the AF server 50. The Nnef_CompositeExposure_Subscribe request includes one or more event IDs and one or more analytics IDs, multiple event IDs, or multiple analytics IDs. Furthermore, the Nnef_CompositeExposure_Subscribe request includes specified conditions for combining information corresponding to each of multiple IDs including event IDs and / or analytics IDs. The conditions for combining information are, for example, logical product (AND) and logical sum (OR).

[0029] The NEF server 1 acquires information corresponding to each of a plurality of IDs, including an event ID and / or an analytics ID, from one or more NFs corresponding to each of the IDs. The NEF server 1 combines the acquired information according to specified conditions and transmits the combined information to the AF server 50 in a Nnef_CompositeExposure_Notify message. Nnef_CompositeExposure_Subscribe and Nnef_CompositeExposure_Notify are different It is provided as an API.

[0030] In the first embodiment, the Nnef_CompositeExposure service can provide, via a single API, information that combines multiple types of information acquired through separate APIs from the Nnef_EventExposure service and the Nnef_AnalyticsExposure service under specified conditions.

[0031] FIG. 2 shows an example of the hardware configuration of the NEF server 1. The NEF server 1 is, for example, a dedicated server. However, the NEF server 1 is not limited to a dedicated server, and may be a relay device or the like equipped with a dedicated computer for executing NEF processing. The NEF server 1 may also be a Field-Programmable Gate Array (FPGA) dedicated to executing NEF processing. ) or ASIC (Application Specific Integrated Circuit) or other electrical circuits 2 shows the hardware configuration when the NEF server 1 is a server.

[0032] The NEF server 1 includes, as its hardware configuration, a processor 101, a memory 102, an auxiliary storage device 103, and a communication unit 104. The memory 102 and the auxiliary storage device 103 are computer-readable recording media. The NEF server 1 is an example of an "information processing device." The processor 101, the auxiliary storage device 103, and the communication unit 104 are electrically connected by a bus.

[0033] The auxiliary storage device 103 stores programs used to operate as the NEF and data used by the processor 101 when executing each program. The auxiliary storage device 103 is, for example, an erasable programmable read only memory (EPROM), a hard disk drive, or a solid state drive (SSD). The programs retained include, for example, the operating system (OS), the NEF control There are programs and multiple APIs for NEF.

[0034] The memory 102 is a storage device that provides the processor 101 with a storage area and a working area for loading programs stored in the auxiliary storage device 103, and is used as a buffer. The memory 102 includes, for example, semiconductor memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory).

[0035] The processor 101 executes the processing of the NEF by loading the OS and programs related to the NEF stored in the auxiliary storage device 103 into the memory 102 and executing them. The processor 101 is, for example, a CPU or a DSP (Digital Signal Processor). The number of processors 101 is not limited to one, and multiple processors 101 may be provided. The processor 101 is an example of a "control unit."

[0036] The communication unit 104 is, for example, a network interface card (NIC), an optical line interface, etc. The communication unit 104 is connected to an access network such as a local area network (LAN) or an optical line network via a wired connection, and is connected to the network N1 through the access network. The communication unit 104 may also be, for example, a wireless communication circuit that connects to a wireless network such as a wireless LAN.

[0037] The hardware configuration of the NEF server 1 is not limited to that shown in Fig. 2. The AF server 50 includes a processor, a memory, an auxiliary storage device, and a communication unit, similar to the NEF server 1. The auxiliary storage device of the AF server 50 stores, for example, an OS, programs related to applications executed by the AF server 50, and APIs for using NEF.

[0038] 3 is a diagram showing an example of the functional configuration of the NEF server 1. The NEF server 1 has, as its functional configuration, an Nnef_CompositeExposure API group 11 and a plurality of other APIs 12. The Nnef_CompositeExposure API group 11 is an API group for the Nnef_CompositeExposure service. The other APIs 12 include APIs corresponding to other services provided by NEF. The Nnef_CompositeExposure API group 11 includes a Subscribe API 111 and a Notify API 112.

[0039] FIG. 4 is an example of the specifications of the Subscribe API 111. In FIG. 4, the specifications regarding the input and output of the Nnef_CompositeExposure API 111 are shown. The input of the Subscribe API 111 is an Nnef_CompositeExposure_Subscribe request. That is, "Inputs" and "Inputs, Option" in FIG. 4 are information included in the Nnef_CompositeExposure_Subscribe request. The information input to the Subscribe API 111 is The information included in the Nnef_CompositeExposure_Subscribe request includes the list of target UEs, Event ID or / and Analytics ID, Event Reporting Information or / and Analytics Reporting Information, Analytics Filter There is information and condition.

[0040] The list of target UEs includes identification information of the target UEs. The UE identification information may be, for example, a Generic Public Subscription Identifier (GPSI), a Subscription Permanent Identifier (SUPI), an External Group Identifier, a Single-Network Slice Selection Assistance Information (S-NSSAI), an Internal Group Identifier, an IP address, a MAC address, or other information that can identify a UE. Furthermore, the UE identification information is not limited to information that uniquely identifies a UE, and may be information that identifies multiple UEs in groups, such as a network address of an IP address.

[0041] Examples of the event IDs include Location Report, UE moving in or out of Area of ​​Interest, Access Type, Location, Reachability Filter, Total number of Transactions, and Number of UEs present in a geographical area. Examples of the analytics IDs include Network Performance, UE Mobility, UE Communication, Abnormal behavior, User Data Congestion, QoS Sustainability, Dispersion Analytics, WLAN performance, Session Management Congestion Control Experience, Redundant Transmission Experience, and DN Performance. If a Nnef_CompositeExposure_Subscribe request contains only multiple event IDs, it can be used for multiple analytics. There are cases where only an ID is included, and cases where one or more event IDs and one or more analytics IDs are included. Therefore, hereafter, when referring to an event ID and analytics ID included in an Nnef_CompositeExposure_Subscribe request, it will be expressed as "event ID and / or analytics ID."

[0042] In the first embodiment, the event ID and the analytics ID are identified as a set with the service name. Therefore, the event ID is included in the set of the service name "Nnef_EventExposure" + the event ID. The analytics ID is included in the set of the service name "Nnef_AnalyticsExposure" + the analytics ID. However, this is not limited to this, and if there is no overlap between the event ID and the analytics ID, the service name may be omitted.

[0043] The Event Reporting Information and the Analytics Reporting Information are information indicating parameters related to the report of information obtained corresponding to the Event ID and the Analytics ID, respectively. The Event Reporting Information and the Analytics Reporting Information include, for example, the report mode (whether to report up to the upper limit number of times or to report periodically, etc.), the upper limit number of reports, or the report period. The Event Reporting Information and the Analytics Reporting Information may be, for example, that shown in Table 4.15.1-1 of 3GPP TS 23.502 V17.4.0.

[0044] If only multiple event IDs are included in the Nnef_CompositeExposure_Subscribe request, only Event Reporting Information is included. If only multiple Analytics IDs are included in the Nnef_CompositeExposure_Subscribe request, only Event Reporting Information is included. If the event ID is not specified, only Analytics Reporting Information is included. In a Nnef_CompositeExposure_Subscribe request, one or more Event IDs and one or more Analytics Reporting Information are included. If a ytics ID is included, Event Reporting Information and Analytics Reporting Information are included, and both may indicate the same content, or only one of them may be included.

[0045] The Analytics Filter Information is information about parameters for filtering information obtained corresponding to the Analytics ID. For example, the Analytics Filter Information specified for each Analytics ID in Section 6 of 3GPP TS 23.288 V17.4.0 can be used.

[0046] Therefore, if an event ID is included in the Nnef_CompositeExposure_Subscribe request, one or more segments of (service name “Nnef_EventExposure” + event ID) are included. Includes a set of Event Reporting Information and Analytics If an ID is included, one or more sets of (Service Name "Nnef_AnalyticsExposure" + Analytics ID + Analytics Filter Information) + Analytics Reporting Information set are included. (The set of Service Name "Nnef_EventExposure" + Event ID is hereinafter referred to as event-related information. Service Name "Nnef_AnalyticsExposure" + The set of Analytics ID + Analytics Filter Information will be referred to as analysis-related information hereinafter.

[0047] The condition includes a condition for combining the information obtained for each event ID and / or Analytics ID. The condition for combining information is a logical product (AND) or a logical sum (OR). Note that the condition can be omitted. If the condition is omitted, the event ID and / or Analytics ID are combined. The information obtained for each ID is combined by logical ANDing.

[0048] Next, the Nnef_CompositeExposure_Subscribe request may optionally include an Event Filter, an application ID, area information, a Subscription Correlation ID, an Expiry Time, and an Action. The Event Filter is information about parameters for filtering information obtained corresponding to an Event ID. For example, 3GPP TS 23.502 V17.4.0 specifies one or more different Event Filters for each Event ID. In the first embodiment, the Event Filter specified in 3GPP TS 23.502 V17.4.0 is used. For example, the Event Filter for an Event ID for which AMF is the information query destination can be the one shown in Table 5.2.2.3.1-1 of 3GPP TS 23.502 V17.4.0. When a filter setting for D is specified, an Event Filter selected from one or more Event Filters defined for the event ID is included in the Nnef_CompositeExposure_Subscribe request. When an Event Filter is included, the event-related information is the service name "Nnef_EventExposure" + event ID + Event Filter.

[0049] The application ID is included when an application for which information is to be acquired is specified. The area information is included when an area for which information is to be acquired is specified. The area information may include, for example, a TA (Tracking Area) ID, a cell ID, or a geographical area identification. Information is used.

[0050] The Subscription Correlation ID is an ID that identifies the Nnef_CompositeExposure_Subscribe service in the NEF server 1 to the AF server 50. The Subscription Correlation ID is assigned by the NEF server 1 when the Nnef_CompositeExposure_Subscribe request is received for the first time from the AF server 50. The Expiry Time is included in the Nnef_CompositeExposure_Subscribe request when the server 50 wants to change the content of the Nnef_CompositeExposure_Subscribe service. The expiration time of the Nnef_CompositeExposure_Subscribe service for , is included when the expiration date is specified by the AF server 50 side.

[0051] Action is included in the Nnef_CompositeExposure_Subscribe request when a service to be executed for a UE included in information obtained by compounding the specified event ID and / or analytics ID according to the condition is specified. Services specified by Action include Nnef_ParameterProvision, Nnef_BDTPNegotiation, Nnef_ChargeableParty, Nnef_AFsessionWithQoS, and Nnef_ApplyPolicy. The Nnef_ParameterProvision service is a service that provisions UE-related parameters. The Nnef_BDTPNegotiation service is a service that provisions BDT (Background Data Transfer)-related parameters. The Nnef_ChargeableParty service is a service that sets charging information for a data session in the UE. The Nnef_AFsessionWithQoS service is a service that sets charging information for a UE's QoS. The Nnef_ApplyPolicy service is a service that applies a BDT policy to a UE. APIs for these services are provided in the NEF server 1 as other APIs 12. Action includes, for example, a request message for these services.

[0052] The description of the part related to the information to be acquired in the Nnef_CompositeExposure_Subscribe request is, for example, as follows: However, Action is described only if it is specified. Nnef_CompositeExposure_Subscribe request = List of target UEs + (Event-related information or Analysis-related information) + (Condition + Event-related information or Analysis-related information) Information)^n+Action^k (^n and ^k indicate n or k repetitions, respectively. n and k are integers greater than or equal to 1.)

[0053] More specifically, for example, when a request is made to apply a BDT policy to a UE extracted as a result of the logical product of event IDs #1 and #2 and Analytics ID ID #3, the Nnef_CompositeExposure_Subscribe request is written as follows: Nnef_CompositeExposure_Subscribe request = List of target UEs + Event-related information for ID#1 + (AND + Event-related information for ID#2) + (AND + Analysis-related information for ID#3) + Nnef_ApplyPolicy_Create request The Nnef_ApplyPolicy_Create request is a message requesting the application of a BDT policy. It's sage.

[0054] Next, when the Nnef_CompositeExposure_Subscribe request is accepted, the output of the Subscribe API 111 is an Nnef_CompositeExposure_Subscribe response. That is, "Output" in Fig. 4 is information included in the Nnef_CompositeExposure_Subscribe response. The information output from the Subscribe API 111, that is, the information included in the Nnef_CompositeExposure_Subscribe response, includes a Subscription Correlation ID. Note that if the Nnef_CompositeExposure service for the AF server 50 is terminated based on the policy of the operator of the core network 100, the Nnef_CompositeExposure_Subscribe response includes an Expiry time. Note that the specifications of the Subscribe API 111 shown in Fig. 4 are an example, and the specifications of the Subscribe API 111 The example shown in FIG. 4 is not limiting.

[0055] Fig. 5 is an example of the specifications of the Notify API 112. Fig. 5 shows the specifications regarding the input and output of the Notify API 112. "Inputs" shown in Fig. 5 includes a list of UEs that meet the conditions specified in the Nnef_CompositeExposure_Subscribe request, an event ID, an analytics ID, event information, and analytics information. , and Notification Correlation Information.

[0056] The identification information of the UEs included in the list of UEs is stored in the Subscribe API 11 shown in FIG. The input is the same as the list of UEs in the input of 1. The event ID and / or analytics ID are the same as the IDs included in the Nnef_CompositeExposure_Subscribe request. Note that, similar to the input of the Subscribe API 111 shown in FIG. 4, The event ID and analytics ID are identified as a set with the service name.

[0057] Event Information is the event specified in the Nnef_CompositeExposure_Subscribe request. Analytic Information is information that satisfies the analysis related information (Analytics ID + Analytics Filter Information) specified in the Nnef_CompositeExposure_Subscribe request. If the application ID and / or area information is specified in the Nnef_CompositeExposure_Subscribe request, Event Information and Analytic Information are information that satisfies the analysis related information (Analytics ID + Analytics Filter Information) specified in the Nnef_CompositeExposure_Subscribe request. In addition to the information related to the event, this information also satisfies these requirements.

[0058] Event Information and Analytic Information each contain one event ID and One piece of information is acquired for one Analytics ID. Also, if only an Event ID is specified in the Nnef_CompositeExposure_Subscribe request, only Event Information is input to the Notify API 112. If only an Analytics ID is specified in the Nnef_CompositeExposure_Subscribe request, only Analytics Information is input to the Notify API 112.

[0059] The Notification Correlation Information is identification information that allows the NF, which is the information destination, to identify a request from the NEF server 1. The Notification Correlation Information is assigned depending on the information destination. The information destination may be, for example, AMF, SMF, or UDR.

[0060] The list of UEs that meet the conditions specified in the Nnef_CompositeExposure_Subscribe request is generated by compositing the Event Information and / or Analytic Information obtained corresponding to the specified Event ID and / or Analytics ID according to the Condition. Event Information and Analytic Information are acquired by The information included varies depending on the Event ID and Analytics ID, and does not necessarily include a list of UEs. The list of UEs is not included in the Event Information or Analytics ID. This is an example of information obtained by combining Analytic Information and Condition.

[0061] Event Information and Analytic Information are "First Service and Second Service" This is an example of "information obtained for a plurality of identification information specifying the type of information in each of the conditions." The information obtained by compounding according to n is an example of "first information."

[0062] Next, the output of the Notify API 112 ("Outputs" in FIG. 5) is the result of processing the Nnef_CompositeExposure_Subscribe request. Since the Notify API 112 sends an Nnef_CompositeExposure_Notify message to the AF server 50, the output of the Notify API 112 can be said to be the information included in the Nnef_CompositeExposure_Notify message. Specifically, the output of the Notify API 112 is obtained by combining Event Information and / or Analytic Information according to the Condition. Furthermore, if an action is specified in the Nnef_CompositeExposure_Subscribe request, the execution result of the specified action is also output from the Notify API 112. Note that the specifications of the Notify API 112 shown in Fig. 5 are merely an example, and the specifications of the Notify API 112 are not limited to the example shown in Fig. 5.

[0063] <Processing flow> FIG. 6 is an example of a flowchart of the processing of the Subscribe API 111. The processing is repeatedly executed at a predetermined interval while the NEF server 1 is running. In OP101, the processor 101 determines whether or not an Nnef_CompositeExposure_Subscribe request has been received. If an Nnef_CompositeExposure_Subscribe request has been received (OP101: YES), the processing proceeds to OP102. If an Nnef_CompositeExposure_Subscribe request has not been received (OP101: NO), the processing shown in FIG. 6 ends.

[0064] In OP102, the processor 101 transmits a request for information acquisition to one or more NFs according to the event ID and / or analytics ID included in the Nnef_CompositeExposure_Subscribe request. For example, if the event ID is Location Report, UE moving in or out of Area of ​​Interest, Access Type, Location, Reachability Filter, Total number of Transactions, and Number of UEs present in a geographical area, For example, the processor 101 sends a request to the AMF. For the Analytics ID, the processor 101 sends a request to the NWDAF. An API is provided for each information acquisition request to each NF. The processor 101 sends an information acquisition request using the appropriate API depending on the NF to be queried.

[0065] In OP103, the processor 101 receives a response from one or more NFs to which the request was sent in OP102. This response indicates that the request has been accepted. In OP104, the processor 101 sends an Nnef_CompositeExposure_Subscribe response to the AF server 50 that is the sender of the Nnef_CompositeExposure_Subscribe request. Thereafter, the processing shown in FIG. 6 ends.

[0066] 7 is an example of a flowchart of the processing of the Notify API 112. The processing shown in FIG. 7 is started, for example, when an Nnef_CompositeExposure_Subscribe response is received, and continues until the Expiry time has elapsed or until an Nnef_CompositeExposure_unSubscribe message indicating the termination of the Nnef_CompositeExposure_Subscribe service is received from the AF server 50. It will be executed repeatedly until you confirm.

[0067] In the OP201, the processor 101 receives event information and / or analytical information from one or more NFs that have sent information acquisition requests in the OP102. If event information or / and analytic information has been received from the one or more NFs (OP201: YES), the process proceeds to OP202. If the event information and / or analytical information has not been received from any of the one or more NFs (OP201: NO), the process shown in FIG. 7 ends. , is executed repeatedly.

[0068] In OP202, the processor 101 converts the received Event Information and / or Analytic Information into Composite Exposure Information included in the Nnef_CompositeExposure_Subscribe request. In OP203, the processor 101 determines whether or not the Nnef_CompositeExposure_Subscribe request received in OP101 includes an Action. If the Nnef_CompositeExposure_Subscribe request includes an Action (OP203: YES), the processing proceeds to OP204. If the Nnef_CompositeExposure_Subscribe request does not include an Action (OP203: NO), the processing proceeds to OP205.

[0069] In OP204, the processor 101 executes the service specified by Action. The service specified by Action is executed by the processor 101 through an API corresponding to the service specified by Action. In OP205, the processor 101 transmits the execution result by using an Nnef_CompositeExposure_Notify message. If an Action is included in the Nnef_CompositeExposure_Subscribe request, the processor 101 transmits the execution result by using the API specified by Action. The execution result of the requested service is also included. After that, the process shown in FIG.

[0070] The processing of the Subscribe API 111 shown in FIG. 6 and the processing of the Notify The API 112 is merely an example and is not limited to the processes shown in Figures 6 and 7. Processes can be added as appropriate depending on the embodiment.

[0071] Fig. 8 is a diagram showing an example of the sequence of the Nnef_CompositeExposure service. In the example shown in Fig. 8, a processing sequence is shown when an Nnef_CompositeExposure_Subscribe request including an event ID #A and an Analytics ID #X is received from the AF server 50. Event ID #A is an event ID that queries AMF. In addition, in FIG. 8, it is assumed that an Action is included in the Nnef_CompositeExposure_Subscribe request.

[0072] In S11, the NEF server 1 receives an Nnef_CompositeExposure_Subscribe request from the AF server 50 (FIG. 6, OP101: YES). S12 and S13 are processes executed for the Analytics ID#X included in the Nnef_CompositeExposure_Subscribe request. In S12, the NEF server 1 transmits an Nnwdaf_AnalyticsSubscribe_Subscribe request, which is a request for information acquisition, to the NWDAF 2 (FIG. 6, In S13, the NEF server 1 receives an Nnwdaf_AnalyticsSubscribe_Subscribe response indicating that the Nnwdaf_AnalyticsSubscribe_Subscribe request has been accepted from the NWDAF 2 (FIG. 6, OP103).

[0073] S14 and S15 are processes executed for event ID#A included in the NEF_CompositeExposure_Subscribe request. In S14, the NEF server 1 sends a Namf_EventExposure_Subscribe request, which is a request for information acquisition, to the AMF 3 (FIG. 6, OP102). In S15, the NEF server 1 receives a Namf_EventExposure_Subscribe response indicating that the Namf_EventExposure_Subscribe request has been accepted from the AMF 3 (FIG. 6, OP103).

[0074] In S16, the NEF server 1 receives responses from the NWDAF 2 and the AMF 3, and therefore transmits an Nnef_CompositeExposure_Subscribe response to the AF server 50 (FIG. 6, OP104).

[0075] In S21, the NEF server 1 receives the analytic information corresponding to the analytics ID #X from the NWDAF 2 (FIG. 7, OP201: YES). In step S22, the NEF server 1 receives the event information corresponding to the event ID #A from the AMF 3 (FIG. 7, OP201: YES). The event information is sent from the AMF 3 in the form of a Namf_EventExposure_Notify message.

[0076] In S23, the NEF server 1 receives the Analytic Information and Event Information. and are composited according to the Condition included in the Nnef_CompositeExposure_Subscribe request. Furthermore, the NEF server 1 executes the action included in the Nnef_CompositeExposure_Subscribe request for the UEs included in the information obtained by combining the Analytic Information and the Event Information (FIG. 7, OP204).

[0077] In S24, the NEF server 1 sends the execution result of the processing for the Nnef_CompositeExposure_Subscribe request to the AF server 50 in the Nnef_CompositeExposure_Notify message. As a result of executing the process for the Nnef_CompositeExposure_Subscribe request, the AF server 50 can obtain information obtained by combining information corresponding to the event ID#A and the analytics ID#X under specified conditions, and the execution result of the specified action for the UE included in the obtained information.

[0078] <Effects of the First Embodiment> In the first embodiment, the AF server 50 can acquire, through a single API, information corresponding to an event ID and information corresponding to an Analytics ID, which are originally acquired through separate APIs, by using the Nnef_CompositeExposure service. Also, the AF server 50 can acquire, through the Nnef_CompositeExposure service, at least two pieces of information, information corresponding to an event ID and / or information corresponding to an Analytics ID, under specified conditions. It is possible to obtain composite information.

[0079] The Nnef_CompositeExposure service enables the AF server 50 to obtain information in which multiple specified types of information are combined under specified conditions by simply sending a single request to the NEF server 1. This requires only one round-trip of communication between the NEF server 1 and the AF server 50, compared to the AF server 50 sending a request for each type to the NEF server 1, receiving multiple specified types of information, and combining them under specified conditions. Therefore, the Nnef_CompositeExposure service can shorten the time it takes to obtain information in which multiple specified types of information are combined under specified conditions. It can also reduce the bandwidth used for communication between the NEF server 1 and the AF server 50.

[0080] Furthermore, in the Nnef_CompositeExposure service, an Action to be executed on a UE included in information acquired by combining information corresponding to an event ID and / or an analytics ID under specified conditions can be specified in an Nnef_CompositeExposure_Subscribe request. This makes it possible to acquire information in which multiple specified types of information are combined under specified conditions through a single API, as well as to execute a specified Action on the UE, thereby reducing processing delays in the AF server 50.

[0081] <Other embodiments> The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate within the scope that does not deviate from the gist of the disclosure.

[0082] In the first embodiment, the Nnef_CompositeExposure service can acquire information acquired by the Nnef_EventExposure service and information acquired by the Nnef_AnalyticsExposure service. This is not limiting, and the Nnef_CompositeExposure service may also be capable of acquiring information acquired by other services in addition to the Nnef_EventExposure service and the Nnef_AnalyticsExposure service. For example, by including identification information equivalent to the event ID and Analytics ID of another service in an Nnef_CompositeExposure_Subscribe request, it is possible to enable the Nnef_CompositeExposure service to acquire information that can be acquired by that service.

[0083] The processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0084] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0085] The present disclosure can also be realized by providing a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors in the computer read and execute the program. Such a computer program may be provided to the computer via a non-transitory computer-readable storage medium connectable to the computer's system bus or via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (e.g., a floppy disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk), a read-only memory (ROM), a random-access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, or any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0086] 1. NEF Server 2. Edge Server 11··Nnef_CompositeExposure API 50··AF Server 100 Core Network 101 Processor 102 Memory 103...Auxiliary storage device 104··Communications Department 111··Subscribe API 112··Notify API 500 Network System

Claims

1. receiving a request including at least two pieces of identification information among a plurality of pieces of identification information specifying types of information in each of a first service and a second service that expose network functions of a predetermined network, and a condition for combining at least two pieces of information obtained for each of the at least two pieces of identification information; transmitting first information obtained by combining the at least two pieces of information in accordance with the condition; An information processing device comprising a control unit that executes the above.

2. the condition includes at least one of a logical AND or a logical OR of the at least two pieces of information; The information processing device according to claim 1 .

3. the request includes action information that specifies an action to be performed on the user terminal included in the first information; the control unit executes an action specified by the action information on the user terminal included in the first information.

3. The information processing device according to claim 1 or 2.

4. the request further includes application identification information that specifies an application; the control unit transmits second information that matches the application identification information from the first information. The information processing device according to claim 1 .

5. the request further includes area identification information specifying a target area; the control unit transmits third information that matches the area identification information among the first information. The information processing device according to claim 1 .

6. the first service is an Nnef_EventExposure service, and the plurality of pieces of identification information specifying the type of information in the first service are Event IDs; the second service is Nnef_AnalyticsExposure, and the plurality of identification information specifying the type of information in the second service is Analytics ID; The information processing device according to claim 1 .

7. The computer receiving a request including at least two pieces of identification information among a plurality of pieces of identification information specifying types of information in each of a first service and a second service that expose network functions of a predetermined network, and a condition for combining at least two pieces of information obtained for each of the at least two pieces of identification information; transmitting first information obtained by combining the at least two pieces of information in accordance with the condition; How to do it.

Images