Method, computer system, and program

Abstract

According to the present invention, an application (rApp) is implemented in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) that includes a Non-RT RIC framework. The rApp transmits, to the Non-RT RIC framework, a subscription to a service for transmitting target data to the rApp when the Non-RT RIC framework has acquired the target data. The subscription is configured to be able to designate one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

Description

Method, computer system, and program

[0001] The present disclosure relates to a method, a computer system, and a program.

[0002] The Open Radio Access Network (O-RAN) Alliance is a community of mobile operators, vendors, and research and academic institutions whose mission is to restructure radio access networks (RANs) to be more intelligent, open, virtualized, and fully interoperable. The O-RAN Working Group 2 (WG2) is conducting technical studies on the Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC) and applications (rApps) implemented in the Non-RT RIC, and is providing technical specifications for these (see, for example, Non-Patent Documents 1-5).

[0003] The Non-RT RIC is located within a Service Management and Orchestration (SMO) that performs RAN monitoring, maintenance, and orchestration. The Non-RT RIC has a Non-RT RIC framework. The Non-RT RIC framework can acquire data related to performance management (PM), configuration management (CM), and fault management (FM) from an E2 node or a Near-Real-Time (Near-RT) RAN Intelligent Controller (RIC) via an O1 interface (see, for example, Non-Patent Document 6).

[0004] The Non-RT RIC framework is connected to rApp via the R1 interface. It is specified that when the Non-RT RIC framework acquires data related to a PM, the Non-RT RIC framework transmits the data related to the PM to the rApp via the R1 interface, and that the rApp can transmit a subscription to the service to the Non-RT RIC framework via the R1 interface (see, for example, Non-Patent Documents 4 and 5).

[0005] O-RAN.WG2.Non-RT-RIC-ARCH-R003-v05.00 "Non-RT RIC: Architecture", November 2023 O-RAN.WG2.R1AP-R003-v04.00 Technical Specification "R1 interface: Application Protocols for R1 Services", November 2023 O-RAN.WG2.R1GAP-R003-v07.00 Technical Specification "R1 interface: General Aspects and Principles", November 2023 O-RAN.WG2.R1UCR-R003-v06.00 Technical Specification "R1 interface: Use Cases and Requirements", November 2023 O-RAN.WG2.R1TD-R003-v01.00 Technical Specification "Type Definitions for R1 Services", November 2023 O-RAN.WG10.OAM-Architecture-R003-v11.00 Technical Specification "O-RAN Working Group 10 O-RAN Operations and Maintenance Architecture", November 2023

[0006] However, the services that the Non-RT RIC framework exposes to rApps via the R1 interface, as well as subscriptions to those services, have not yet been fully explored, meaning there is room for extending the services of the R1 interface.

[0007] An object of the present disclosure is to provide a method, a computer system, and a program that can extend the services of the R1 interface. Note that this object is only one of multiple objects that the multiple embodiments disclosed in this specification aim to achieve. Other objects or problems and novel features will become apparent from the description of this specification or the accompanying drawings.

[0008] The method disclosed herein is a method executed by a Non-RT RIC framework included in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC), and includes receiving a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to allow one or both of data related to Configuration Management (CM) and data related to Fault Management (FM) to be specified as the target data.

[0009] The method disclosed herein is a method executed by an application (rApp) implemented in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) including a Non-RT RIC framework, and includes sending a subscription to the Non-RT RIC framework to a service that sends target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

[0010] A computer system according to the present disclosure comprises at least one memory and at least one processor coupled to the at least one memory and configured to provide an application (rApp) to be executed in a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC), wherein the at least one processor transmits to the Non-RT RIC framework a subscription to a service that transmits target data to the rApp when the Non-RT RIC framework included in the Non-RT RIC acquires the target data, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

[0011] A computer system according to the present disclosure comprises at least one memory and at least one processor coupled to the at least one memory and configured to provide a Non-RT RIC framework included in a Non-RT Radio Access Network (RAN) Intelligent Controller (Non-RT RIC), wherein the at least one processor receives a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

[0012] The program disclosed herein causes an application (rApp) implemented in a Non-RT Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) including a Non-RT RIC framework to execute a process of sending to the Non-RT RIC framework a subscription to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

[0013] The program according to the present disclosure causes a Non-RT RIC framework included in a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC) to execute a process of receiving a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

[0014] The present disclosure provides a method, a computer system, and a program that can extend the services of the R1 interface.

[0015] FIG. 1 is a block diagram illustrating a basic configuration of Non-RTRIC of the present disclosure. FIG. 2 is a diagram illustrating the operation of an rApp and a Non-RTRIC framework. FIG. 3 is a diagram illustrating an example of a communication system of the present disclosure. FIG. 4 is a flowchart illustrating an example of processing operation of an rApp of the present disclosure. FIG. 5 is a sequence diagram illustrating an example of processing operation of a communication system of the present disclosure. FIG. 6 is a flowchart illustrating an example of processing operation of the Non-RTRIC framework of the present disclosure. FIG. 7 is a diagram illustrating another example of a communication system of the present disclosure. FIG. 8 is a diagram illustrating another example of a subscription for CM-related data. FIG. 9 is a diagram illustrating an example of a subscription for FM-related data. FIG. 10 is a flowchart illustrating another example of processing operation of the Non-RTRIC framework of the present disclosure. FIG. 11 is a diagram illustrating another example of a communication system of the present disclosure. FIG. 12 is a sequence diagram illustrating another example of processing operation of a communication system of the present disclosure.

[0016] Hereinafter, embodiments will be described with reference to the drawings. In this disclosure, the drawings may relate to one or more embodiments. Furthermore, each element in the drawings may apply to one or more embodiments. Furthermore, in the embodiments, identical or equivalent elements are given the same reference numerals, and redundant description will be omitted.

[0017] First, the basic configuration and operation of a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC) of the present disclosure will be described. Fig. 1 is a block diagram showing the basic configuration of the Non-RT RIC of the present disclosure. Fig. 2 is a diagram explaining the operation of the rApp and Non-RT RIC framework.

[0018] In FIG. 1, the Non-RT RIC 100 includes an rApp 101 and a Non-RT RIC framework 102 .

[0019] 2, the rApp 101 transmits to the Non-RT RIC framework a subscription to a service (public service) that transmits target data to the rApp when the Non-RT RIC framework acquires the target data (step S101). The Non-RT RIC framework then receives the subscription transmitted from the rApp 101. The subscription is configured to allow one or both of data related to configuration management (CM) and data related to fault management (FM) to be specified as the target data. This allows the public service provided by the Non-RT RIC framework 102 and the subscription to the public service to be extended to include FM-related data and CM-related data, thereby enabling the extension of the R1 interface services.

[0020] <First Embodiment> <Configuration Example of a Communication System> Figure 3 is a diagram illustrating an example of a communication system according to the present disclosure. The communication system illustrated in Figure 3 includes an SMO framework 1 and an O1 node 2 connected to the SMO framework 1 via an O1 interface. Here, each of the Near-RT RIC and the E2 node connected to the SMO framework 1 via the O1 interface, or the Near-RT RIC and the E2 node collectively, is referred to as an O1 node. That is, the O1 node is a node that terminates the O1 interface. The E2 node may also be referred to as a RAN node. The E2 node may be an O-CU-CPs, an O-CU-UP, or an O-DU for NR access. Alternatively, the E2 node may be an O-eNB for Evolved Universal Terrestrial Radio Access (E-UTRA) access.

[0021] Each element shown in Figure 3 may be implemented, for example, as an element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualization function instantiated on an application platform. Each element shown in Figure 3 may be implemented as a computer system including one or more memories and one or more processors. The computer system may be a single computer system or multiple (distributed) computer systems. The computer system may be a standalone computer or may include one or more networked computers.

[0022] The SMO framework 1 includes a Non-RT RIC 11 and O1 interface terminating nodes 12. The Non-RT RIC 11 includes an rApp 15 and a Non-RT RIC framework 16 connected to the rApp 15 via an R1 interface. The Non-RT RIC framework 16 provides platform functionality used to host the rApp 15 and support specific functions hosted by the rApp 15.

[0023] The Non-RT RIC framework 16 provides one or more services to the rApp 15 via the R1 interface. The one or more services include a service (hereinafter sometimes referred to as a "public service") that exposes data acquired by the Non-RT RIC framework 16 to the rApp 15.

[0024] To receive a public service, the rApp 15 sends a subscription to the public service to the Non-RT RIC framework 16. The subscription may be, for example, a Subscribe data request message. The subscription is configured to be able to specify data to be published (hereinafter, may be simply referred to as "target data"). The target data may be either data related to configuration management (CM) (CM-related data) or data related to fault management (FM) (FM-related data), or may be both CM-related data and FM-related data.

[0025] The Non-RT RIC framework 16 transmits the target data specified by the subscription to the rApp 15. This allows the rApp 15 to obtain the target data specified by the subscription.

[0026] The Non-RT RIC framework 16 may send target data to the rApp 15 using a pull method. In this case, the Non-RT RIC framework 16 first sends a notification to the rApp 15 indicating that the target data is available. The Non-RT RIC framework 16 then receives a transmission request for the target data sent from the rApp 15 that received the notification. The Non-RT RIC framework 16 then transmits the target data to the rApp 15 in response to the transmission request.

[0027] Alternatively, the Non-RT RIC framework 16 may use the PUSH method to send the target data to the rApp 15. In this case, the Non-RT RIC framework 16 sends the target data to the rApp 15 without sending a notification to the rApp 15 indicating that the target data is available.

[0028] <Example of operation of communication system> Fig. 4 is a flowchart showing an example of the processing operation of the rApp of the present disclosure. Fig. 5 is a sequence diagram showing an example of the processing operation of the communication system of the present disclosure. Fig. 5 particularly shows the transmission and reception of signals between the rApp 15 and the Non-RT RIC framework 16.

[0029] The rApp 15 transmits a Subscribe data request message to the Non-RT RIC framework 16 (steps S11 and S21). The Subscribe data request message is configured so that target data can be specified.

[0030] The rApp 15 receives a Subscribe data response message corresponding to the Subscribe data request message from the Non-RT RIC framework 16 (steps S12 and S22).

[0031] The rApp 15 acquires the target data from the Non-RT RIC framework 16 (step S13). As described above, the rApp 15 can acquire the target data from the Non-RT RIC framework 16 using either the PULL method or the PUSH method.

[0032] When the rApp 15 obtains target data using the PULL method, the rApp 15 receives a Notify data availability message (corresponding to the notification indicating that the target data is available) from the Non-RT RIC framework 16 (step S23). The Notify data availability message may include detailed information about the available data (pull delivery details). The rApp 15 sends a Pull data request message (corresponding to the request to send the target data) to the Non-RT RIC framework 16 (step S24). The rApp 15 receives a Pull data response message from the Non-RT RIC framework 16 (step S25). The Pull data response message includes the target data (data payload) in its payload.

[0033] When the rApp 15 acquires the target data using the PUSH method, the rApp 15 receives a Push data message from the Non-RT RIC framework 16 without receiving a Notify data availability message (step S26). The Push data message includes the target data (data payload) in its payload.

[0034] FIG. 6 is a flowchart showing an example of the processing operation of the Non-RT RIC framework of the present disclosure.

[0035] The Non-RT RIC framework 16 receives a Subscribe data request message from the rApp 15 (steps S31 and S21).

[0036] The Non-RT RIC framework 16 transmits a Subscribe data response message corresponding to the Subscribe data request message to the rApp 15 (steps S32, S22).

[0037] The Non-RT RIC framework 16 publishes (transmits) the target data to the rApp 15 (step S33). As described above, the Non-RT RIC framework 16 can publish the target data to the rApp 15 using the PULL method and the PUSH method.

[0038] When the Non-RT RIC framework 16 publishes target data to the rApp 15 using the PULL method, the Non-RT RIC framework 16 sends a Notify data availability message (corresponding to a notification indicating that the target data is available) to the rApp 15 (step S23). The Non-RT RIC framework 16 receives a Pull data request message (corresponding to a request to send the target data) from the rApp 15 (step S24). The Non-RT RIC framework 16 sends a Pull data response message to the rApp 15 (step S25).

[0039] When the Non-RT RIC framework 16 publishes target data to the rApp 15 using the PUSH method, the Non-RT RIC framework 16 sends a Push data message to the rApp 15 without sending a Notify data availability message (step S26).

[0040] As described above, according to the first embodiment, the rApp 15 is configured to transmit a subscription to a public service provided by the Non-RT RIC framework 16 to the Non-RT RIC framework 16 in order to receive the public service. The public service provided by the Non-RT RIC framework 16 is a service that transmits target data to the rApp 15 when the Non-RT RIC framework 16 acquires target data to be made public. The subscription is configured to be able to specify the target data to be made public. The target data may be either CM-related data or FM-related data, or may be both CM-related data and FM-related data.

[0041] This configuration of the rApp 15 allows the public services provided by the Non-RT RIC framework 16 and subscriptions to those public services to be extended to include FM-related data and CM-related data, thereby expanding the services of the R1 interface. Furthermore, by having the rApp 15 apply for public services for FM-related data and CM-related data by sending a subscription, the rApp 15 does not need to send a message to the Non-RT RIC framework 16 requesting the transmission of the target data each time FM-related data or CM-related data is required. This reduces the energy consumption of the computer system that provides the rApp 15. Furthermore, the Non-RT RIC framework 16, which receives messages from the rApp 15, also receives fewer messages from the rApp 15. This reduces the energy consumption of the computer system that provides the Non-RT RIC framework 16, thereby enabling power savings.

[0042] Second Embodiment Example of Configuration of Communication System Fig. 7 is a diagram illustrating another example of a communication system according to the present disclosure. The communication system illustrated in Fig. 7 includes an SMO framework 3 and an O1 node 2 connected to the SMO framework 3 via an O1 interface.

[0043] Each element shown in Figure 7 may be implemented, for example, as an element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualization function instantiated on an application platform. Each element shown in Figure 3 may be implemented as a computer system including one or more memories and one or more processors. The computer system may be a single computer system or multiple (distributed) computer systems. The computer system may be a standalone computer or may include one or more networked computers.

[0044] The SMO framework 3 includes a Non-RT RIC 31 and an O1 interface end node 12. The Non-RT RIC 31 includes an rApp 35 and a Non-RT RIC framework 36 connected to the rApp 35 via an R1 interface. The Non-RT RIC framework 36 hosts the rApp 35 and provides platform functions used to support specific functions hosted by the rApp 35.

[0045] The Non-RT RIC framework 36, like the Non-RT RIC framework 31, provides one or more services to the rApp 35 via an R1 interface. The one or more services include a "public service."

[0046] To receive a public service, the rApp 35 sends a subscription to the public service to the Non-RT RIC framework 36. The subscription may be, for example, a Subscribe data request message. The subscription is configured to be able to specify target data for publication. The target data may be either CM-related data or FM-related data, or may be both CM-related data and FM-related data.

[0047] For example, the subscription may include an information element (IE) for selecting CM-related data as target data. The information element for selecting target data may include an information element (hereinafter, sometimes referred to as a "first IE") for selecting a portion of the CM-related data received by the Non-RT RIC framework 36 as target data. The information element for selecting target data may also include an information element (hereinafter, sometimes referred to as a "second IE") for selecting a notification including data corresponding to the target data from among one or more types of CM-related notifications received by the Non-RT RIC framework 36 via the O1 interface.

[0048] 8 is a diagram showing an example of a subscription for CM-related data. The subscription shown in FIG. 8 includes the following information elements:

[0049] dataTypeId dataTypeId is an information element that defines the type of Data Management and Exposure services (DME). dataTypeId consists of, for example, namespace, name, and version.

[0050] dataCategory At least one data category is assigned to a DME type.

[0051] dataSelector > configurationParameterList >> configurationParameter dataSelector is an information element for selecting the data to be included in the data instance to be created. In other words, dataSelector is an object that sets the requested data. This dataSelector corresponds to the "first IE" above. dataSelector includes configurationParameterList and configurationParameter. configurationParameterList is a list of parameters for which the rApp requests change notification. The Non-RT RIC framework will notify the rApp only of notifications that include parameters in this list. configurationParameter defines the parameter information requested by the rApp.

[0052] targetSelector>nodeFilter>objecInstances targetSelector is an information element for selecting a target for the data to be produced. targetSelector includes nodeFilter and objecInstances.

[0053] notificationSelector > cooperaterappIdList > > rappId > notificationTypeList > > notificationType > parameterThresholdList > > configurationPrameter > > threshold > > operator notificationSelector is an information element that is set for the purpose of filtering by notification type, etc. when an rApp obtains information from the Non-RT RIC framework using the push method. The Non-RT RIC framework notifies the rApp according to the conditions set in this object. This notificationSelector corresponds to the "second IE" above. notificationSelector includes cooperaterappIdList, rappId, notificationTypeList, notificationType, parameterThresholdList, configurationPrameter, threshold, and operator. cooperaterappIdList is a list of rappIds of other collaborating rApps. The Non-RT RIC framework will notify notifications caused by change requests by rApps with rappIds in this list. The rApp allows the Non-RT RIC framework to send only notifications related to the configuration parameters controlled by the rApps set in this list, enabling information sharing about configuration parameters with other rApps. rappId is the rappId of the other rApp to collaborate. notificationTypeList is a list of notificationTypes for which the rApp requests notifications. The Non-RT RIC framework only sends notifications of the specific notificationTypes set in this list to the rApp. notificationType defines the type of notification.The parameterThresholdList is a list of thresholds for the setting values ​​of configuration parameters when the Non-RT RIC framework notifies an rApp. The configurationPrameter is an information element for setting the configuration parameter for which you want to set a threshold value. The threshold is an information element for setting the threshold when notifying a configuration parameter. The operator is an information element for indicating the operator.

[0054] Also, for example, the subscription may include an information element for selecting FM-related data as target data. The information element for selecting the target data may include an information element (hereinafter, sometimes referred to as a "third IE") for selecting a portion of the FM-related data received by the Non-RT RIC framework 36 as target data. The information element for selecting the target data may also include an information element (hereinafter, sometimes referred to as a "fourth IE") for selecting a notification including data corresponding to the target data from among one or more types of FM-related notifications received by the Non-RT RIC framework 36 via the O1 interface.

[0055] 9 is a diagram showing an example of a subscription for FM-related data. The subscription shown in FIG. 9 includes the following information elements:

[0056] dataTypeId dataTypeId is an information element that defines the type of Data Management and Exposure services (DME).

[0057] dataCategory At least one data category is assigned to a DME type.

[0058] dataSelector > alarmIdList >> alarmId > alarmTypeList >> alarmType > probableCauseList >> probableCause > perceivedSeverityList >> perceivedSeverity > securityRelatedFilter >> serviceUser >> serviceProvider >> securityAlarmDetector dataSelector is an information element for selecting the data to be included in the data instance to be created. In other words, dataSelector is an object that sets the requested data. This dataSelector corresponds to the above-mentioned "third IE." dataSelector includes alarmIdList, alarmId, alarmTypeList, alarmType, probableCauseList, probableCause, perceivedSeverityList, perceivedSeverity, securityRelatedFilter, serviceUser, serviceProvider, and securityAlarmDetector. alarmIdList is a list of alarmIds requested by the rApp. The Non-RT RIC framework will only send notifications of the specific alarmIds set in this list to the rApp. alarmTypeList is a list of alarmTypes requested by the rApp. The Non-RT RIC framework will only send notifications of the specific alarmTypes set in this list to the rApp. probableCauseList is a list of probableCauses requested by the rApp. The Non-RT RIC framework will only send notifications of the specific probableCauses set in this list to the rApp. perceivedSeverityList is a list of perceivedSeverities requested by the rApp. The Non-RT RIC framework will only send notifications of the specific perceivedSeverities set in this list to the rApp.securityRelatedFilter is a filtering condition for notifying security-related alarms. The Non-RT RIC framework will only send notifications that match the parameters set here to the rApp.

[0059] targetSelector>nodeFilter>objecInstances targetSelector is an information element for selecting a target for the data to be produced. targetSelector includes nodeFilter and objecInstances.

[0060] notificationSelector > notificationTypeList >> notificationType The notificationSelector is an information element that is set for the purpose of filtering by notification type, etc. when an rApp obtains information from the Non-RT RIC framework using the push method. The Non-RT RIC framework notifies the rApp according to the conditions set in this object. This notificationSelector corresponds to the "fourth IE" above. The notificationSelector includes a notificationTypeList and a notificationType. The notificationTypeList is a list of notificationTypes for which the rApp requests notification. The notificationType defines the type of notification.

[0061] 7, the Non-RT RIC framework 36 determines whether the target data specified by the subscription has already been acquired. If it is determined that the target data has already been acquired, the Non-RT RIC framework 36 transmits the target data specified by the subscription to the rApp 35, similar to the Non-RT RIC framework 16. This allows the rApp 35 to acquire the target data specified by the subscription.

[0062] If it is determined that the target data has not yet been acquired, the Non-RT RIC framework 36 executes an "O1-related data collection procedure based on data subscription" with the O1 node 2 via the O1 interface terminal node 12. The "O1-related data collection procedure based on data subscription" may utilize, for example, the Operation Subscribe procedure described in Clause 4.2.2.3.1 of Non-Patent Document 6. In the "O1-related data collection procedure based on data subscription," the Non-RT RIC framework 36 may send another subscription to a service to which the O1 node 2 sends data including the target data. By executing the "O1-related data collection procedure based on data subscription," for example, the O1 node 2 begins to send notifications related to changes in configuration data to the Non-RT RIC framework 36. In addition, the O1 node 2 begins to send notifications related to setting, changing, and canceling alarms to the Non-RT RIC framework 36.

[0063] Upon receiving target data from the O1 node 2, the Non-RT RIC framework 36 transmits the target data to the rApp 35. For example, the Non-RT RIC framework 36 may select a portion of the CM-related data received from the O1 node 2 as target data based on the content of the subscription from the rApp 35. The Non-RT RIC framework 36 may also select a notification including data corresponding to the target data from one or more types of CM-related notifications received from the O1 node 2 based on the content of the subscription from the rApp 35. The Non-RT RIC framework 36 may also select a portion of the FM-related data received from the O1 node 2 as target data based on the content of the subscription from the rApp 35. The Non-RT RIC framework 36 may also select a notification including data corresponding to the target data from one or more types of FM-related notifications received from the O1 node 2 based on the content of the subscription from the rApp 35.

[0064] <Example of operation of communication system> Figure 10 is a flowchart showing another example of the processing operation of the Non-RT RIC framework of the present disclosure. Figure 11 is a sequence diagram showing another example of the processing operation of the communication system of the present disclosure. Note that the processing operation of rApp 35 is not particularly different from the processing operation of rApp 15, so a description thereof will be omitted.

[0065] The Non-RT RIC framework 36 receives a Subscribe data request message from the rApp 35 (steps S41 and S51).

[0066] The Non-RT RIC framework 36 transmits a Subscribe data response message corresponding to the Subscribe data request message to the rApp 35 (steps S42 and S52).

[0067] The Non-RT RIC framework 36 determines whether the target data specified by the subscription has already been acquired (steps S43, S53).

[0068] If it is determined that the target data has already been acquired (step S43 YES), the Non-RT RIC framework 36 publishes (sends) the target data to the rApp 35 (step S44). Specifically, the Non-RT RIC framework 36 executes the processes of steps S57 to S60. The processes of steps S57 to S60 are the same as the processes of steps S23 to S26.

[0069] If it is determined that the target data has not yet been acquired (step S43 NO), the Non-RT RIC framework 36 executes an "O1-related data collection procedure based on data subscription" between the O1 node 2 via the O1 interface terminal node 12 (steps S45, S54).

[0070] The Non-RT RIC framework 36 waits to receive the target data transmitted from the O1 node 2 (step S46: NO). When the Non-RT RIC framework 36 receives the target data transmitted from the O1 node 2 (steps S46: YES, S55, S56), it publishes (transmits) the target data to the rApp 35 (step S44).

[0071] Third Embodiment The third embodiment relates to an example of the configuration of a Non-RT RIC framework.

[0072] <Configuration Example of Communication System> Fig. 12 is a diagram showing another example of a communication system according to the present disclosure. In Fig. 12, a Non-RT RIC framework 36 includes a DME (Data Management and Exposure functions) 36A and a RAN-OAM related functions 36B.

[0073] For example, the DME 36A performs a management service and a publication service of data to be disclosed to the rApp 35, among the functions of the Non-RT RIC framework 36. Also, for example, the RAN-OAM related functions 36B performs a service of collecting data from the O1 node 2 via the O1 interface and passing the collected data to the Non-RT RIC framework 36, among the functions of the Non-RT RIC framework 36.

[0074] <Example of Operation of Communication System> Fig. 13 is a sequence diagram showing another example of the processing operation of the communication system of the present disclosure. Among the processing steps shown in Fig. 13, the same processing steps as those in Fig. 11 are assigned the same reference numerals.

[0075] The DME 36A determines whether the target data specified by the subscription has already been acquired (step S53). If it is determined in step S53 that the target data has already been acquired, the DME 36A publishes (transmits) the target data to the rApp 35. Specifically, the DME 36A executes the processes of steps S57 to S60.

[0076] If it is determined that the target data has not yet been acquired, the DME 36A transmits a request to the RAN-OAM related functions 36B to execute an "O1-related data collection procedure based on a data subscription" for the new subscription (step S61). In response to this request, the RAN-OAM related functions 36B executes an "O1-related data collection procedure based on a data subscription" with the O1 node 2 via the O1 interface termination node 12 (step S54).

[0077] When the RAN-OAM related functions 36B receives the data from the O1 node 2 via the O1 interface termination node 12, it transmits the data to the DME 36A (step S62).

[0078] <Variation of Third Embodiment> In the above description, the DME 36A executes a public service for the rApp 35, but the present disclosure is not limited to this. For example, as shown in Fig. 14, the RAN-OAM related functions 36B may have a function of executing a public service for the rApp 35 in addition to a function of collecting data from the O1 node 2 via the O1 interface. Fig. 14 is a sequence diagram showing another example of the processing operation of the communication system of the present disclosure.

[0079] <Other Embodiments> Fig. 15 is a diagram showing an example of the configuration of a Non-RT RIC. In the example of Fig. 15, the Non-RT RIC 1000 is implemented as a computer system. Here, the rApp and Non-RT RIC frameworks included in the Non-RT RIC 1000 may each be implemented as one or more computer systems. The computer system includes one or more processors 1001, memory 1002, and mass storage 1003, which communicate with each other via a bus 1007. The one or more processors 1001 may include, for example, a Central Processing Unit (CPU) or a Graphics Processing Unit (GPU), or both. The computer system may also include other devices such as one or more output devices 1004, one or more input devices 1005, and one or more peripherals 1006. The one or more peripherals 1006 may include a modem, a network adapter, or any combination thereof.

[0080] One or both of the memory 1002 and the mass storage 1003 may include a computer-readable medium having stored thereon one or more sets of instructions. These instructions may be located partially or completely in memory within one or more processors 1001. These instructions, when executed on one or more processors 1001, cause the one or more processors 1001 to provide the functionality of the Non-RT RIC 11, 31, 100 described in the above embodiments.

[0081] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the invention. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0082] Each drawing is merely an example for describing one or more embodiments. Each drawing may not relate to only one particular embodiment, but may also relate to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

[0083] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Supplementary Note 1) A program causing an application (rApp) implemented in a Non-RT Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) including a Non-RT RIC framework to execute a process of sending to the Non-RT RIC framework a subscription to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, the subscription being configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data. (Supplementary Note 2) The program according to Supplementary Note 1, wherein the subscription includes an information element for selecting data related to the CM as the target data. (Supplementary Note 3) The program according to Supplementary Note 2, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data. (Supplementary Note 4) The program according to Supplementary Note 2, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 5) The program according to Supplementary Note 1, wherein the subscription includes an information element for selecting data related to the FM as the target data. (Supplementary Note 6) The program according to Supplementary Note 5, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the FM received by the Non-RT RIC framework as the target data.(Supplementary Note 7) The program according to Supplementary Note 5, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of FM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 8) The program according to any one of Supplements 1 to 7, wherein the processing includes acquiring the target data from the Non-RT RIC framework by a pull method. (Supplementary Note 9) The program according to Supplementary Note 8, wherein acquiring the target data by a pull method includes receiving a notification from the Non-RT RIC framework indicating that the target data is available, transmitting a transmission request for the target data, and receiving the target data transmitted from the Non-RT RIC framework in response to the transmission request. (Supplementary Note 10) The program according to any one of Supplements 1 to 7, wherein the processing includes acquiring the target data from the Non-RT RIC framework by a push method. (Supplementary Note 11) The program according to Supplementary Note 10, wherein acquiring the target data by the PUSH method includes receiving the target data transmitted from the Non-RT RIC framework without receiving a notification from the Non-RT RIC framework indicating that the target data is available. (Supplementary Note 12) The program according to any one of Supplements 1 to 7, wherein the subscription is a Subscribe data request message.(Supplementary Note 13) A program causing a Non-RT RIC framework included in a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC) to execute processing to receive, from an application (rApp) implemented in the Non-RT RIC, a subscription to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, wherein the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data. (Supplementary Note 14) The program according to Supplementary Note 13, wherein the subscription includes an information element for selecting data related to the CM as the target data. (Supplementary Note 15) The program according to Supplementary Note 14, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data. (Supplementary Note 16) The program according to Supplementary Note 14, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 17) The program according to Supplementary Note 13, wherein the subscription includes an information element for selecting data related to the FM as the target data. (Supplementary Note 18) The program according to Supplementary Note 17, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the FM received by the Non-RT RIC framework as the target data. (Supplementary Note 19) The program according to Supplementary Note 17, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of FM-related notifications received by the Non-RT RIC framework via an O1 interface.(Supplementary Note 20) The program according to any one of Supplements 13 to 19, wherein the processing includes sending the target data to the rApp by a pull method. (Supplementary Note 21) The program according to Supplementary Note 20, wherein sending the target data by a pull method includes sending a notification to the rApp indicating that the target data is available, receiving a request to send the target data from the rApp, and sending the target data to the rApp in response to the request. (Supplementary Note 22) The program according to any one of Supplements 13 to 19, wherein the processing includes sending the target data to the rApp by a push method. (Supplementary Note 23) The program according to Supplementary Note 22, wherein sending the target data by a push method includes sending the target data to the rApp without sending a notification to the rApp indicating that the target data is available. (Supplementary Note 24) The program according to Supplementary Note 13, wherein the processing includes, if target data corresponding to the received subscription has not yet been acquired, sending another subscription to a node to which the Non-RT RIC framework is connected via an O1 interface, to a service to which the node transmits data including the target data. (Supplementary Note 25) The program according to any one of Supplements 13 to 19, wherein the subscription is a Subscribe data request message.(Supplementary Note 26) A computer system comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to provide an application (rApp) to be executed in a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC), wherein the at least one processor transmits a subscription to a service to the Non-RT RIC framework included in the Non-RT RIC that transmits the target data to the rApp when the target data is acquired by the Non-RT RIC framework, the subscription being configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data. (Supplementary Note 27) The computer system according to Supplementary Note 26, wherein the subscription includes an information element for selecting data related to the CM as the target data. (Supplementary Note 28) The computer system according to Supplementary Note 27, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data. (Supplementary Note 29) The computer system according to Supplementary Note 27, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 30) The computer system according to Supplementary Note 26, wherein the subscription includes an information element for selecting data related to the FM as the target data. (Supplementary Note 31) The computer system according to Supplementary Note 30, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the FM received by the Non-RT RIC framework as the target data.(Supplementary Note 32) The computer system of Supplementary Note 30, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of FM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 33) The computer system of any one of Supplements 26 to 32, wherein the at least one processor acquires the target data from the Non-RT RIC framework in a pull manner. (Supplementary Note 34) The computer system of Supplementary Note 33, wherein the at least one processor receives a notification from the Non-RT RIC framework indicating that the target data is available, transmits a transmission request for the target data, and receives the target data transmitted from the Non-RT RIC framework in response to the transmission request. (Supplementary Note 35) The computer system of any one of Supplements 26 to 32, wherein the at least one processor acquires the target data from the Non-RT RIC framework in a push manner. (Supplementary Note 36) The computer system according to Supplementary Note 35, wherein the at least one processor receives the target data transmitted from the Non-RT RIC framework without receiving a notification from the Non-RT RIC framework indicating that the target data is available. (Supplementary Note 37) The computer system according to any one of Supplements 26 to 32, wherein the subscription is a Subscribe data request message.(Supplementary Note 38) A computer system comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to provide a Non-RT RIC framework included in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC), wherein the at least one processor receives a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to allow one or both of data related to configuration management (CM) and data related to fault management (FM) to be specified as the target data. (Supplementary Note 39) The computer system according to Supplementary Note 38, wherein the subscription includes an information element for selecting data related to the CM as the target data. (Supplementary Note 40) The computer system according to Supplementary Note 39, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data. (Supplementary Note 41) The computer system according to Supplementary Note 39, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 42) The computer system according to Supplementary Note 38, wherein the subscription includes an information element for selecting data related to the FM as the target data. (Supplementary Note 43) The computer system according to Supplementary Note 42, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the FM received by the Non-RT RIC framework as the target data.(Supplementary Note 44) The computer system of Supplementary Note 42, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of FM-related notifications received by the Non-RT RIC framework via the O1 interface. (Supplementary Note 45) The computer system of any one of Supplements 38 to 44, wherein the at least one processor transmits the target data to the rApp in a pull manner. (Supplementary Note 46) The computer system of Supplementary Note 45, wherein the at least one processor transmits a notification to the rApp indicating that the target data is available, receives a request to transmit the target data from the rApp, and transmits the target data to the rApp in response to the transmission request. (Supplementary Note 47) The computer system of any one of Supplements 38 to 44, wherein the at least one processor transmits the target data to the rApp in a push manner. (Supplementary Note 48) The computer system of Supplementary Note 47, wherein the at least one processor sends the target data to the rApp without sending a notification to the rApp indicating that the target data is available. (Supplementary Note 49) The computer system of Supplementary Note 38, wherein, if the target data corresponding to the received subscription has not yet been obtained, the at least one processor sends, to a node to which the Non-RT RIC framework is connected via an O1 interface, another subscription to a service to which the node sends data including the target data. (Supplementary Note 50) The computer system of any one of Supplements 38 to 44, wherein the subscription is a Subscribe data request message.(Supplementary Note 51) A method executed by an application (rApp) implemented in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) including a Non-RT RIC framework, comprising: sending, to the Non-RT RIC framework, a subscription to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, wherein the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data. (Supplementary Note 52) The method according to Supplementary Note 51, wherein the subscription includes an information element for selecting data related to the CM as the target data. (Supplementary Note 53) The method according to Supplementary Note 52, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data. (Supplementary Note 54) The method according to Supplementary Note 52, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 55) The method according to Supplementary Note 51, wherein the subscription includes an information element for selecting data related to the FM as the target data. (Supplementary Note 56) The method according to Supplementary Note 55, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the FM received by the Non-RT RIC framework as the target data. (Supplementary Note 57) The method according to Supplementary Note 55, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of FM-related notifications received by the Non-RT RIC framework via an O1 interface.(Supplementary Note 58) The method of any one of Supplements 51 to 57, comprising acquiring the target data from the Non-RT RIC framework in a pull manner. (Supplementary Note 59) The method of Supplementary Note 58, wherein acquiring the target data in a pull manner comprises receiving a notification from the Non-RT RIC framework indicating that the target data is available, transmitting a transmission request for the target data, and receiving the target data transmitted from the Non-RT RIC framework in response to the transmission request. (Supplementary Note 60) The method of any one of Supplements 51 to 57, comprising acquiring the target data from the Non-RT RIC framework in a push manner. (Supplementary Note 61) The method of Supplementary Note 60, wherein acquiring the target data in a push manner comprises receiving the target data transmitted from the Non-RT RIC framework without receiving a notification from the Non-RT RIC framework indicating that the target data is available. (Supplementary Note 62) The method of any one of Supplements 51 to 57, wherein the subscription is a Subscribe data request message. (Supplementary Note 63) A method executed by a Non-RT RIC framework included in a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC), comprising receiving a subscription to a service from an application (rApp) implemented in the Non-RT RIC that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, wherein the subscription is configured to allow one or both of data related to configuration management (CM) and data related to fault management (FM) to be specified as the target data. (Supplementary Note 64) The method of Supplementary Note 63, wherein the subscription includes an information element for selecting data related to the CM as the target data.(Supplementary Note 65) The method according to Supplementary Note 64, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data. (Supplementary Note 66) The method according to Supplementary Note 64, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface. (Supplementary Note 67) The method according to Supplementary Note 63, wherein the subscription includes an information element for selecting data related to the FM as the target data. (Supplementary Note 68) The method according to Supplementary Note 67, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the FM received by the Non-RT RIC framework as the target data. (Supplementary Note 69) The method of Supplementary Note 67, wherein the information element for selecting the target data includes an information element for selecting a notification including data corresponding to the target data from one or more types of FM-related notifications received by the Non-RT RIC framework via the O1 interface. (Supplementary Note 70) The method of any one of Supplements 63 to 69, comprising sending the target data to the rApp in a pull manner. (Supplementary Note 71) The method of Supplementary Note 70, wherein sending the target data in a pull manner includes: sending a notification to the rApp indicating that the target data is available; receiving a request to send the target data from the rApp; and sending the target data to the rApp in response to the send request. (Supplementary Note 72) The method of any one of Supplements 63 to 69, comprising sending the target data to the rApp in a push manner. (Supplementary Note 73) The method of Supplementary Note 72, wherein sending the target data in the PUSH manner includes sending the target data to the rApp without sending a notification to the rApp indicating that the target data is available.(Supplementary Note 74) The method of Supplementary Note 63, comprising: if the target data corresponding to the received subscription has not yet been obtained, the Non-RT RIC framework sending another subscription to a service to which the node connected via the O1 interface will transmit data including the target data. (Supplementary Note 75) The method of any one of Supplements 63 to 69, wherein the subscription is a Subscribe data request message.

[0084] This application claims priority based on Japanese Patent Application No. 2024-045871, filed March 22, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0085] 1 SMO framework 2 O1 node 3 SMO framework 11 Non-RT RIC 12 O1 interface termination node 15 rApp 16 Non-RT RIC framework 31 Non-RT RIC 35 rApp 36 Non-RT RIC framework 36A DME 36B RAN-OAM related functions 100 Non-RT RIC 101 rApp 102 Non-RT RIC framework

Claims

1. A method executed by a Non-RT RIC framework included in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC), comprising receiving a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, wherein the subscription is configured to allow one or both of data related to Configuration Management (CM) and data related to Fault Management (FM) to be specified as the target data.

2. The method of claim 1, wherein the subscription includes an information element for selecting data related to the CM as the target data.

3. The method of claim 2, wherein the information element for selecting the target data includes an information element for selecting a portion of the data related to the CM received by the Non-RT RIC framework as the target data.

4. The method of claim 2, wherein the information element for selecting the target data includes an information element for selecting a notification containing data corresponding to the target data from among one or more types of CM-related notifications received by the Non-RT RIC framework via an O1 interface.

5. The method of claim 1, wherein the subscription includes an information element for selecting data related to the FM as the target data.

6. The method of claim 5, wherein the information element for selecting the target data includes an information element for selecting a portion of the data associated with the FM received by the Non-RT RIC framework as the target data.

7. The method of claim 5, wherein the information element for selecting the target data includes an information element for selecting a notification containing data corresponding to the target data from among one or more types of FM-related notifications received by the Non-RT RIC framework via an O1 interface.

8. A method according to any one of claims 1 to 7, comprising sending the target data to the rApp in a pull manner.

9. The method of claim 8, wherein sending the target data in the PULL manner includes: sending a notification to the rApp indicating that the target data is available; receiving a request to send the target data from the rApp; and sending the target data to the rApp in response to the request to send.

10. The method of any one of claims 1 to 7, comprising sending the target data to the rApp in a push manner.

11. The method of claim 10, wherein sending the target data in the PUSH manner includes sending the target data to the rApp without sending a notification to the rApp indicating that the target data is available.

12. The method of claim 1, further comprising: if target data corresponding to the received subscription has not yet been obtained, the Non-RT RIC framework sending another subscription to a service to which the node connected via the O1 interface will transmit data including the target data.

13. The method of any one of claims 1 to 7, wherein the subscription is a Subscribe data request message.

14. A method executed by an application (rApp) implemented in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) including a Non-RT RIC framework, comprising: sending a subscription to the Non-RT RIC framework for a service that sends target data to the rApp when the Non-RT RIC framework acquires the target data, wherein the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

15. A computer system comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to provide an application (rApp) to be executed in a non-real-time radio access network (RAN) intelligent controller (Non-RT RIC), wherein the at least one processor transmits a subscription to a service to the Non-RT RIC framework that transmits target data to the rApp when the target data is acquired by the Non-RT RIC framework included in the Non-RT RIC, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

16. A computer system comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to provide a Non-RT Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) framework included in a Non-RT RIC, wherein the at least one processor receives a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to allow one or both of data related to configuration management (CM) and data related to fault management (FM) to be specified as the target data.

17. A program that causes an application (rApp) implemented in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) including a Non-RT RIC framework to execute a process of sending to the Non-RT RIC framework a subscription to a service that sends target data to the rApp when the Non-RT RIC framework acquires the target data, wherein the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

18. A program that causes a Non-RT RIC framework included in a Non-Real-Time Radio Access Network (RAN) Intelligent Controller (Non-RT RIC) to execute processing to receive a subscription from an application (rApp) implemented in the Non-RT RIC to a service that transmits target data to the rApp when the Non-RT RIC framework acquires the target data, and the subscription is configured to be able to specify one or both of data related to configuration management (CM) and data related to fault management (FM) as the target data.

Images