Service management and orchestration method for base station and service management and orchestration apparatus for base station

Abstract

A service management and orchestration method for a base station, according to embodiments, may comprise the steps of: transmitting a message to a message control unit of a service management and orchestration (SMO), by a non-real-time RAN intelligent controller application (non-RT RIC application, rAPP), on the basis of an interface (R1 interface) between a non-RT RIC framework and rAPPs which produce and use R1 services, wherein the R1 service includes one or more of service registration and service discovery, service authentication and authorization, artificial intelligence / machine learning (AI / ML) services, or radio access network operation administration maintenance (RAN OAM)-related services; determining whether the message complies with an interface (O1 interface) for O-RAN; activating an interface capable of controlling a legacy O-RAN and operating the legacy O-RAN if the message does not comply with the O1 interface; and operating the O-RAN on the basis of the O1 interface if the message complies with the O1 interface.

Description

Service management and orchestration method of a base station and service management and orchestration device of a base station

[0001] The embodiments relate to a service management and orchestration method of a base station and a service management and orchestration device of a base station.

[0002] RAN SMO (Service Management & Orchestration) is a system that operates and manages O-DU / O-CU / O-RU (hereinafter referred to as O-RAN base station) defined in the O-RAN standard specifications.

[0003] The system's Non-RT RIC (Non-real-time RAN Intelligent Controller) is a platform that enables the provision of various services, such as base station operation automation and external exposure of base station data, as apps. Apps that run on the Non-RT RIC platform are called rApps and interface with the Non-RT RIC platform using the O-RAN standard interface, R1.

[0004] The O-RAN standard defines the interface between rApp and Non-RT RIC (R1 interface) and the interface between OAM management component (Network Function Management, hereinafter referred to as NFM) and O-RAN base station (O1 interface), so that not only existing OAM management (NFM) developers but also 3rd party developers can develop rApp.

[0005] However, SMO has the problem and limitation that it can only connect with O-RAN base stations developed based on O-RAN standards and cannot connect with legacy base stations developed according to the base station vendor's own standards.

[0006] In other words, since it is not possible to control legacy base stations through Non-RT RIC and rApp within the current O-RAN standard specifications, it is necessary to build an automation platform developed by each vendor.

[0007] The embodiments provide a service management and orchestration method of a base station and a service management and orchestration of a base station that can efficiently control a legacy base station through a Non-RT RIC and rApp in an SMO structure.

[0008] However, the scope of the embodiments is not limited to the technical tasks described above, and the scope of the embodiments may be expanded to other technical tasks that can be inferred by a person skilled in the art based on the entire described content.

[0009] A service management and orchestration method of a base station according to embodiments may include a step of transmitting a message to a message control unit of an SMO (Service Management and Orchestration) based on an interface (R1 interface) between a Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application) and a Non-RT RIC framework in which an R1 service is provided and processed by the rApp, wherein the R1 service includes at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance)-related service; a step of determining whether the message conforms to an interface for an O-RAN (O1 interface); a step of activating an interface capable of controlling a legacy O-RAN and operating the legacy O-RAN when the message does not conform to the O1 interface; and a step of operating the O-RAN based on the O1 interface when the message conforms to the O1 interface.

[0010] The service management and orchestration method of a base station and the service management and orchestration device of the base station according to the embodiments can provide various services such as operation automation by using a common platform independent from a base station vendor such as SMO (Non-RT RIC).

[0011] The base station service management and orchestration method and the base station service management and orchestration device according to the embodiments can effectively reduce investment and management costs for an operation automation platform that must be built by each existing vendor.

[0012] The drawings are included to further understand the embodiments, and the drawings illustrate the embodiments together with the description related to the embodiments. For a better understanding of the various embodiments described below, reference should be made to the following description of the embodiments in conjunction with the following drawings, in which like reference numerals correspond to corresponding parts throughout the drawings.

[0013] Figure 1 shows Legacy RAN interconnection through Legacy Termination according to embodiments, and O1 Termination shows O-RAN interconnection according to the standards of the O-RAN Alliance.

[0014] Figure 2 illustrates O-RAN and Legacy RAN control procedures for determining whether rApp is O-RAN compliant according to embodiments.

[0015] Figure 3 illustrates the registration, bootstrap, and legacy RAN control procedures of rApp according to embodiments.

[0016] Figure 4 illustrates a procedure for changing Legacy RAN settings after Legacy RAN registration according to embodiments.

[0017] Preferred embodiments of the embodiments are described in detail, examples of which are illustrated in the accompanying drawings. The following detailed description, with reference to the accompanying drawings, is intended to illustrate preferred embodiments of the embodiments, rather than merely show embodiments that can be implemented according to the embodiments. The following detailed description includes details to provide a thorough understanding of the embodiments. However, it will be apparent to those skilled in the art that the embodiments may be practiced without these details.

[0018] While most of the terms used in the examples are commonly used in the field, some terms were arbitrarily selected by the applicant, and their meanings are described in detail in the following descriptions as needed. Therefore, the examples should be understood based on the intended meaning of the terms, not simply their names or meanings.

[0019] The definitions of terms according to the embodiments are as follows.

[0020] Non-RT RIC (O-RAN Non-Real-Time RAN Intelligent Controller): A unit within the SMO that enables non-real-time control and optimization of AI / ML workflows, including RAN elements and resources, model training and updates, and policy-based guidance for applications / functions of the Near-RT RIC.

[0021] The definition of the R1 application protocol according to the embodiments can be interpreted based on the 3GPP service framework for network functions defined in 3GPP TS 29.501.

[0022] The R1 interface is an open logical interface within the O-RAN architecture between rApps and the non-RT RIC framework. The R1 interface supports the exchange of control signaling information and the collection and transmission of data between endpoints. The R1 interface enables R1 services to be used and provided by rApps from multiple manufacturers and is independent of the specific implementation of the SMO and non-RT RIC framework. The R1 interface is defined in an extensible manner, allowing the addition of new services and data types without requiring changes to protocols or procedures.

[0023] The R1 interface is defined between the rApp and the Non-RT RIC framework with reference to O-RAN TS R1GAP.

[0024] According to the Non-RT RIC architecture standard, the service management and exposure services provided by the SMO / Non-RT RIC framework enable: rApp registration, service registration, service discovery, authentication and authorization, communication support, bootstrap (optional), and heartbeat (optional).

[0025] Additionally, if a bootstrap service is provided by the SMO / Non-RT RIC framework, the rApp can use it to discover endpoints for service management and exposed services.

[0026] The protocol stack for the R1 interface can consist of a physical layer, a data link layer, a network layer (IP), a transport layer (TCP), a security layer (TLS), an application layer (HTTP), and a data interchange layer (JSON).

[0027] Figure 1 illustrates Legacy RAN interconnection through Legacy Termination and O-RAN interconnection through O1 Termination according to embodiments.

[0028] Figure 1 is a diagram illustrating a service management and orchestration method of a base station according to embodiments and a RAN SMO (Service Management & Orchestration) configuration corresponding to the service management and orchestration of the base station. It is a system for operating / managing O-DU / O-CU / O-RU (hereinafter referred to as O-RAN base station) defined in the O-RAN standard and is largely composed of components such as OAM management and Non-RT RIC.

[0029] Each component constituting the service management and orchestration device of Figure 1 may correspond to hardware, software, a processor, and / or a combination thereof.

[0030] OAM management performs roles such as configuration (CM), performance (PM), and fault (FM) management. In the SMO structure, it performs RAN OAM-related functions and O1 termination.

[0031] Non-RT RIC performs various service provision roles, such as base station automation operation and external data linkage.

[0032] Referring to Figure 1, the rAPP of the SMO (Service Management and Orchestration) / Non-RT RIC of the base station according to the embodiments can be used to jointly accommodate Legacy RAN and O-RAN. The current O-RAN standard does not provide a Legacy RAN interworking method.

[0033] Accordingly, the O-RAN Alliance according to embodiments provides an R1 interface for rAPP in the Non-RT RIC framework, and an O1 interface for O-RAN in the SMO framework.

[0034] The SMO framework includes a Non-RT RIC framework. A Non-RT RIC framework can include at least one rApp (application).

[0035] An rApp (application) is a Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application) that provides and uses R1 services. When multiple rApps exist, each rApp can control the RAN. An rApp that controls the Legacy RAN and an rApp that controls the O-RAN can be distinguished, and a single rApp can control both the Legacy RAN and the O-RAN. An rApp is connected to the R1 Termination based on the R1 interface.

[0036] Legacy RAN refers to a different type of RAN from O-RAN, and is interpreted as a term referring to RAN currently operating in commercial networks.

[0037] R1 Termination is the unit that controls message exchange between the non-RT RIC framework and rApps. Messages are exchanged to access R1 services based on the R1 interface.

[0038] The SMO / Non-RT RIC framework includes an internal message infrastructure (hereinafter referred to as the SMO / Non-RT RIC message control unit). The SMO / Non-RT RIC message control unit controls message exchange operations on the SMO / Non-RT RIC framework and determines whether Legacy Termination and / or O1 Termination operations are performed.

[0039] In order to jointly operate Legacy RAN and O-RAN on a common SMO / Non-RT RIC framework, the method / device according to the embodiments includes a Legacy Termination unit and / or an O1 Termination unit.

[0040] Conventional frameworks that only allow connection with O-RAN base stations have limitations and problems that prevent them from connecting with various types of base stations. Therefore, the methods / devices according to the embodiments effectively address the aforementioned technical issues through a framework structure like that shown in Figure 1.

[0041] As shown in Figure 1, Legacy Termination can be established to simultaneously operate both existing O-RAN and Legacy RAN via rAPP. Depending on the base station operation method in a non-RT RIC, the following methods are used:

[0042] Method 1: An O-RAN base station developed based on the O-RAN standard uses and controls the O-RAN O1 / R1 interface defined in the O-RAN standard.

[0043] Method 2: Legacy RAN base stations that do not follow the O-RAN standard establish a Legacy termination and use and control the Legacy / R1 interface.

[0044] The specific operations of Method 1 and Method 2 are described later in Fig. 2.

[0045] These methods eliminate the need to install separate systems or equipment for each legacy RAN manufacturer through rAPP operation, and provide various services such as operation automation using a common platform independent from the base station vendor, thereby reducing the investment and management costs for operation automation platforms that must be built by each existing vendor.

[0046] Hereinafter, with reference to each drawing, a service management and orchestration method of a base station according to embodiments and a method in which a Legacy Termination of a service management and orchestration device of the base station operates a Legacy RAN based on a Legacy interface and a method in which an O1 Termination operates an O-RAN based on an O1 interface are described.

[0047] Figure 2 illustrates a procedure for determining whether an rApp is O-RAN compliant according to embodiments.

[0048] The present invention illustrates a method for service management and orchestration of a base station according to embodiments of FIG. 1 and a procedure for determining whether a service management and orchestration device of a base station is O-RAN compliant with rAPP.

[0049] All rApp messages are processed by the internal message infrastructure (hereinafter, the message control unit of SMO (Service Management and Orchestration) / Non-RT RIC) through the R1 interface (R1 Termination). The rApp and SMO / Non-RT RIC message control unit determines whether the RAN and related interfaces currently being operated are O-RAN compliant through message transmission and reception.

[0050] At this time, the message exchange used between the rApp and the SMO / Non-RT RIC message control unit is performed by the REST API (HTTPS / REST) ​​used in the O-RAN standard. As shown in Fig. 2, if the RAN and interface are compliant with O-RAN, the legacy O-RAN is controlled by O1 Termination. If the RAN and interface are not compliant with O-RAN, the legacy RAN is controlled by Legacy Termination.

[0051] According to the flowchart in Figure 2, rApp performs each operation, and SMO performs the functions required for each operation. For example, rApp sends a message to SMO / Non-RT RIC based on the R1 interface. SMO / Non-RT RIC receives a message from rApp. As described above, the message exchange between rApp and SMO / Non-RT RIC is controlled by the R1 interface and / or SMO / Non-RT RIC message control unit on the SMO / Non-RT RIC framework.

[0052] The SMO / Non-RT RIC message control unit receives messages from the rApp and determines whether the base station information corresponding to the received message information conforms to the specifications of the O1 interface. In other words, it determines whether the base station is an O-RAN base station or an additional base station of various types, and performs base station operation according to each base station type.

[0053] If O1 compliant, O-RAN is controlled based on O1Termination.

[0054] If not O1 compliant, Legacy RAN is controlled based on Legacy Termination.

[0055] That is, both O-RAN and / or Legacy RAN can be jointly accommodated and controlled.

[0056] Referring to FIGS. 1 and 2, a service management and orchestration method of a base station according to embodiments may include a step of transmitting a message to a message control unit of an SMO (Service Management and Orchestration) / Non-RT RIC based on an interface (R1 interface) between an rApp and a Non-RT RIC framework in which an R1 service is produced and used by a Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application); a step of determining whether the message conforms to an interface for an O-RAN (O1 interface); a step of activating an interface capable of controlling a legacy RAN and operating the legacy RAN when the message does not conform to the O1 interface; and a step of operating the O-RAN based on the O1 interface when the message conforms to the O1 interface.

[0057] Here, the R1 service may include at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance) related service.

[0058] Likewise, the service management and orchestration device of the base station includes a Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application) unit that transmits a message to a message control unit of Service Management and Orchestration (SMO) based on an interface (R1 interface) between the rApp and the Non-RT RIC framework through which the R1 service is provided and used, the R1 service including at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance)-related service; and a control unit that determines whether the message conforms to an interface for O-RAN (O1 interface); and when the message does not conform to the O1 interface, an interface capable of controlling a Legacy O-RAN is activated, and when the Legacy O-RAN is operated and the message conforms to the O1 interface, the O-RAN can be operated based on the O1 interface.

[0059] Likewise, the service management and orchestration system includes at least one application that produces and processes a service; an R1 Termination that controls the exchange of messages based on a first interface (R1 interface) between at least one application and a Non-RT RIC (O-RAN Non-real-time RAN intelligent Controller) framework; an intra-message structure that transmits and receives messages; a Legacy Termination that controls a Legacy RAN; and an O1 Termination that controls the O-RAN; wherein at least one application determines whether a message conforms to a second interface (O1 interface) for the O-RAN, and if the message does not conform to the second interface, activates an interface capable of controlling the Legacy RAN and operates the Legacy RAN; and if the message conforms to the O1 interface, operates the O-RAN based on the second interface.

[0060] Likewise, in a computer-readable recording medium for executing a service management and orchestration method of a base station, the service management and orchestration method comprises: a step of transmitting a message to a message control unit of a Service Management and Orchestration (SMO) / Non-RT RIC based on an interface (R1 interface) between an rApp and a Non-RT RIC framework in which an R1 service is produced and used by a Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application), wherein the R1 service includes at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance)-related service; a step of determining whether the message conforms to an interface for O-RAN (O1 interface); a step of activating an interface capable of controlling a legacy O-RAN and operating the legacy O-RAN when the message does not conform to the O1 interface; And if the message matches the O1 interface, a step of operating O-RAN based on the O1 interface can be executed.

[0061] Figure 3 illustrates the registration and bootstrap or legacy RAN control procedures of rApp according to embodiments.

[0062] FIG. 3 illustrates a procedure in which rApp registers and bootstraps the Legacy RAN and performs settings for the Legacy RAN in the operation of operating the Legacy RAN in FIG. 2.

[0063] Through the R1 interface of the existing O-RAN, rAPP performs registration and bootstrapping for service provision. Subsequently, rApps can control existing registered O-RANs by performing service registration and service discovery (Register service & Discover service for rApp). For legacy RANs that did not previously exist, legacy RAN registration can be used to control the legacy RAN.

[0064] To register, an rApp may provide security credentials, including the rApp name, vendor, software version, and certificate, as well as the role (service provider and / or service user) for which the rApp is registering. The response to an rApp registration request may include the registration status, i.e., success or failure.

[0065] For successful rApp registration, the response may also include the rAppId. If rApp registration fails, the response may also include an error code along with relevant information. The rApp can obtain information about the Service Management and Exposure (SME) service endpoint from the bootstrap service producer.

[0066] To discover a service, an rApp can provide an rAppId and optional selection criteria, such as the service name, service type, and functionality. The SME function responds with information about the service, including endpoint information and a service identifier.

[0067] The rApp may transmit a registration request for a Legacy RAN to the SMO / Non-RT RIC message control unit, and may transmit type information and identifier information for Legacy RAN registration. For example, the type information may indicate Legacy, and the identifier may have a unique value for Legacy RAN, such as 111.

[0068] The SMO message control unit registers the Legacy RAN and sends a response message to the rApp in response to the request. Similarly, it returns type information and identifier information for the Legacy registration to the rApp.

[0069] After the rApp registration and bootstrap and Legacy RAN registration request procedures, a registration procedure is performed between the Legacy RAN and the rApp. Heartbeat messages are sent and received between the Legacy RAN and the rApp. The message transmission and reception interval can be 3 minutes. For example, heartbeats can be sent and received at 3-minute intervals, and the default value of the transmission and reception interval can be 3 minutes, but the value of 3 minutes can be set differently depending on the embodiment. The Legacy RAN and the rApp can check each other's existence and settings through the heartbeat message.

[0070] Through this, the rApp collects Legacy RAN information from the Legacy RAN. The collected information may include CM (Configuration Management), PM (Statistics), FM (Alarm) information, etc. Since the link to the Legacy RAN may not be constantly active, the period during which the link is active to collect Legacy RAN information may be set according to embodiments. For example, the collection period may be 5 minutes to 7 days. The value of the collection period of 5 minutes to 7 days may be set differently according to embodiments. CM (Configuration Management) information is configuration information, PM (Performance Management) information is statistical information, and FM (Fault Management) information is alarm information.

[0071] According to the configuration information, the configuration task is performed between the Legacy RAN and the rApp. The Legacy RAN receives the request to collect CM / PM / FM information from the rApp and collects CM (common information). Based on the information collected, the Legacy RAN sends an information collection response to the rApp. The rApp sends a request to update the collected common information to the SMO / Non-RT RIC message control unit. The SMO / Non-RT RIC message control unit updates common information such as CM, PM, and FM for the Legacy RAN. The SMO / Non-RT RIC message control unit sends confirmation information of the common information collection to the rApp.

[0072] Referring to FIG. 3, in the service management and orchestration method of the base station, the rApp transmits registration completion information to the Legacy RAN, transmits a request to the Legacy RAN to collect configuration information including at least one of CM (Configuration Management) information, PM (Performance Management) information, and FM (Fault Management) information, and in response to the request, receives configuration information from the Legacy RAN, and the SMO updates the configuration information.

[0073] As shown in Figure 3, Legacy RAN can be registered through the rApp, R1 interface, and controlled according to the registration procedure. In other words, by providing a common platform, the burden of providing additional services / devices by vendor can be effectively eliminated.

[0074] Figure 4 illustrates a procedure for changing Legacy RAN settings after Legacy RAN registration according to embodiments.

[0075] Figure 4 illustrates a flowchart for changing the settings of a legacy RAN after registering the legacy RAN as in Figure 2-3.

[0076] After Legacy RAN registration, information acquisition can be performed from both the existing O-RAN and the Legacy RAN, and the Legacy RAN configuration change operation is performed as shown in Fig. 4. The O1 Termination section operates identically to Legacy Termination and is therefore omitted from Fig. 4, but the operation is identical.

[0077] Through operation 2-3, after the setup between the rApp, the SMO / Non-RT RIC message control unit, and the Legacy RAN is completed, the rApp transmits a change request for the Legacy RAN to the SMO / Non-RT RIC message control unit. The request information may include a message for parameter change, type information indicating the Legacy type, and identifier information identifying the request.

[0078] The SMO / Non-RT RIC message control unit determines whether the RAN and interface for the request conform to the O1 interface. Depending on the conformance determination result, Legacy Termination can be performed if the RAN is Legacy, or O1 Termination can be performed if the RAN is O-RAN.

[0079] In the case of non-O1 compliance, the SMO / Non-RT RIC message control unit sends a change request for the Legacy RAN to the Legacy RAN. The change request includes a message for changing parameters.

[0080] The Legacy RAN changes the parameters. It sends a confirmation message for the parameter change to the SMO / Non-RT RIC message control unit. The SMO / Non-RT RIC message control unit sends a change request confirmation containing the parameter change message to the rApp. The rApp sends a request to update the change request information to the SMO message control unit. The SMO / Non-RT RIC message control unit updates the change information for the Legacy RAN. The SMO / Non-RT RIC message control unit sends an update confirmation to the rApp.

[0081] Referring to FIG. 4, the service management and orchestration method of the base station may further include the steps of: rApp transmitting a change request for Legacy RAN to a message control unit; and, if the change request does not conform to the O1 interface, the service management and orchestration method may further include the steps of: transmitting the change request to the Legacy RAN; receiving information indicating a parameter change from the Legacy RAN; transmitting information indicating a parameter change to the rApp; receiving an update request for the parameter change from the rApp; and updating the change information for the Legacy RAN.

[0082] Additionally, if the change request conforms to the O1 interface, the service management and orchestration method may further include a step of operating the O-RAN based on the O1 interface.

[0083] The service management and orchestration method / device according to the embodiments can register and control both O-RAN and Legacy RAN as described above. Furthermore, when the settings of O-RAN or Legacy RAN change and require updating, the settings can be changed through a procedure as shown in FIG. 4, and based on the updated information, the O-RAN and Legacy RAN can be efficiently controlled.

[0084] Additionally, the service management and orchestration method of the base station can be performed by a service management and orchestration device of the base station.

[0085] Due to the embodiments, the service management and orchestration method of the base station and the service management and orchestration device of the base station can provide various services such as operation automation by using a common platform independent from the base station vendor, such as SMO (Non-RT RIC).

[0086] The base station service management and orchestration method and the base station service management and orchestration device according to the embodiments can effectively reduce investment and management costs for an operation automation platform that must be built by each existing vendor.

[0087] The embodiments may be interpreted with reference to the definitions and descriptions of O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00 Technical Specification, O-RAN.WG2.R1AP-R003-v02.00 Technical Specification, O-RAN.WG2.R1GAP-R003-v05.00 Technical Specification, O-RAN.WG2.R1TP-R003-v03.00 Technical Specification, O-RAN.WG2.R1UCR-R003-v04.00 Technical Specification, O-RAN.WG2.Use-Case-Requirements-R003-v07.00 Technical Specification.

[0088] The embodiments have been described in terms of methods and / or devices, and the descriptions of methods and devices may be applied complementarily.

[0089] For the convenience of explanation, each drawing has been described separately, but it is also possible to design a new embodiment by combining the embodiments described in each drawing. In addition, designing a computer-readable recording medium having a program recorded thereon for executing the previously described embodiments, as needed by a person skilled in the art, also falls within the scope of the embodiments. The devices and methods according to the embodiments are not limited to the configurations and methods of the embodiments described above, but the embodiments may be configured by selectively combining all or part of the embodiments so that various modifications can be made. Although preferred embodiments of the embodiments have been illustrated and described, the embodiments are not limited to the specific embodiments described above, and various modifications can be made by a person skilled in the art to which the present invention pertains without departing from the gist of the embodiments claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the embodiments.

[0090] The various components of the devices of the embodiments may be implemented by hardware, software, firmware, or a combination thereof. The various components of the embodiments may be implemented by a single chip, for example, a single hardware circuit. According to embodiments, the components according to the embodiments may be implemented by separate chips. According to embodiments, at least one of the components of the devices of the embodiments may be configured with one or more processors capable of executing one or more programs, and the one or more programs may perform, or include instructions for performing, one or more of the operations / methods according to the embodiments. The executable instructions for performing the methods / operations of the devices of the embodiments may be stored in non-transitory CRMs or other computer program products configured to be executed by one or more processors, or may be stored in temporary CRMs or other computer program products configured to be executed by one or more processors. In addition, the memory according to the embodiments may be used as a concept including not only volatile memory (e.g., RAM, etc.), but also non-volatile memory, flash memory, PROM, etc. Additionally, it may be implemented in the form of a carrier wave, such as transmission via the Internet. Furthermore, the processor-readable recording medium may be distributed across network-connected computer systems, allowing the processor-readable code to be stored and executed in a distributed manner.

[0091] In this document, “ / ” and “,” are interpreted as “and / or”. For example, “A / B” is interpreted as “A and / or B”, and “A, B” is interpreted as “A and / or B”. Additionally, “A / B / C” means “at least one of A, B, and / or C”. Also, “A, B, C” means “at least one of A, B, and / or C”. Additionally, “or” in this document is interpreted as “and / or”. For example, “A or B” can mean 1) “A” only, 2) “B” only, or 3) “A and B”. In other words, “or” in this document can mean “additionally or alternatively”.

[0092] Terms such as "first" and "second" may be used to describe various components of the embodiments. However, the various components according to the embodiments should not be interpreted as limited by these terms. These terms are merely used to distinguish one component from another. For example, a first user input signal may be referred to as a "second user input signal." Similarly, a second user input signal may be referred to as a "first user input signal." The use of these terms should be interpreted as not departing from the scope of the various embodiments. Although "first user input signal" and "second user input signal" are both user input signals, they do not mean the same user input signals unless the context clearly indicates otherwise.

[0093] The terminology used to describe the embodiments is for the purpose of describing particular embodiments and is not intended to be limiting of the embodiments. As used in the description of the embodiments and in the claims, the singular is intended to include the plural unless the context clearly dictates otherwise. The expressions “and / or” are used to mean all possible combinations of terms. The expression “includes” describes the presence of features, numbers, steps, elements, and / or components, but does not mean that additional features, numbers, steps, elements, and / or components are not included. Conditional expressions such as “if” or “when” used to describe the embodiments are not intended to be limited to only optional cases. When a specific condition is satisfied, a related action is performed in response to a specific condition, or a related definition is intended to be interpreted.

[0094] Additionally, the operations according to the embodiments described in this document may be performed by a transceiver device including a memory and / or a processor according to the embodiments. The memory may store programs for processing / controlling the operations according to the embodiments, and the processor may control various operations described in this document. The processor may be referred to as a controller, etc. The operations according to the embodiments may be performed by firmware, software, and / or a combination thereof, and the firmware, software, and / or a combination thereof may be stored in the processor or in the memory.

[0095] Meanwhile, the operations according to the embodiments described above may be performed by a transmitting device and / or a receiving device according to the embodiments. The transmitting / receiving device may include a transmitting / receiving unit for transmitting and receiving media data, a memory for storing instructions (program code, algorithm, flowchart, and / or data) for a process according to the embodiments, and a processor for controlling the operations of the transmitting / receiving device.

[0096] As described above, the relevant contents have been described in the best form for carrying out the embodiments.

[0097] As described above, the embodiments may be applied in whole or in part to a service management and orchestration method of a base station and a service management and orchestration device of a base station.

[0098] Those skilled in the art may make various changes or modifications to the embodiments within the scope of the embodiments.

[0099] Embodiments may include modifications / changes, which do not depart from the scope of the claims and their equivalents.

Claims

1. A step for receiving a message for SMO (Service Management and Orchestration) based on an interface (R1 interface) between the rApp and the Non-RT RIC framework where R1 services are produced and used from the Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application). The above R1 service includes at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance) related service; A step for determining whether the above message conforms to the interface for O-RAN (O1 interface); If the above message does not conform to the O1 interface, a step of activating an interface capable of controlling the Legacy O-RAN and operating the Legacy O-RAN; and If the above message conforms to the O1 interface, a step of operating O-RAN based on the O1 interface is included; Method for service management and orchestration at a base station.

2. In paragraph 1, Based on the above R1 interface, service registration and service discovery are performed, and the O-RAN registered in the above SMO is controlled. A registration request for the Legacy RAN is received from the above rApp, A response to the registration request is sent to the above rApp, The above registration request and the above response each include type information and identification information indicating the Legacy RAN. Method for service management and orchestration at a base station.

3. In paragraph 2, Registration completion information is transmitted to the Legacy RAN, a request is transmitted to the Legacy RAN to collect configuration information including at least one of CM (Configuration Management) information, PM (Performance Management) information, and FM (Fault Management) information, and in response to the request, the configuration information is received from the Legacy RAN. The above setting information is updated based on the above SMO. Method for service management and orchestration at a base station.

4. In paragraph 2, A change request for the above Legacy RAN is received, If the above change request does not conform to the O1 interface, the method comprises the steps of transmitting a change request to the Legacy RAN; A step of receiving information indicating a parameter change from the Legacy RAN; a step of transmitting information indicating a change in said parameter to said rApp; A step of receiving an update request for parameter change from the above rApp, Further comprising a step of updating change information for the Legacy RAN, Method for service management and orchestration at a base station.

5. In paragraph 4, If the change request conforms to the O1 interface, the method further includes a step of operating O-RAN based on the O1 interface. Method for service management and orchestration at a base station.

6. In paragraph 4, The change request for the above Legacy RAN includes a message indicating a parameter change, type information indicating Legacy, and an identifier identifying the change request. The change request transmitted to the above Legacy RAN includes a message indicating a parameter change. Method for service management and orchestration at a base station.

7. Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application) that sends messages to the message control section of SMO (Service Management and Orchestration) based on the interface (R1 interface) between rApp and Non-RT RIC framework where R1 service is produced and used. The above R1 service includes at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance) related service; and A control unit for determining whether the above message conforms to an interface for O-RAN (O1 interface); If the above message does not conform to the O1 interface, activate the interface that can control the Legacy O-RAN, and the Legacy O-RAN is operated. If the above message conforms to the O1 interface, O-RAN is operated based on the O1 interface. Service management and orchestration device of the base station.

8. In paragraph 7, The above rApp controls the O-RAN registered in the SMO by performing service registration and service discovery based on the R1 interface. The above rApp transmits a registration request for the Legacy RAN to the message control unit, The above message control unit transmits a response to the registration request to the above rApp, The above registration request and the above response each include type information and identification information indicating the Legacy RAN. Service management and orchestration device of the base station.

9. In paragraph 8, The above rApp transmits registration completion information to the Legacy RAN, transmits a request to the Legacy RAN to collect configuration information including at least one of CM (Configuration Management) information, PM (Performance Management) information, and FM (Fault Management) information, and in response to the request, receives the configuration information from the Legacy RAN, The above SMO updates the above setting information, Service management and orchestration device of the base station.

10. In paragraph 8, The above rApp transmits a change request for the Legacy RAN to the message control unit, If the above change request does not conform to the above O1 interface, the message control unit of the SMO: Send a change request to the above Legacy RAN, Receive information indicating parameter changes from the above Legacy RAN, Transmit information indicating a change in the above parameters to the above rApp, Receive an update request for parameter change from the above rApp, Updating change information for the above Legacy RAN Service management and orchestration device of the base station.

11. In paragraph 10, If the above change request conforms to the above O1 interface, the message control unit of the SMO: Operating O-RAN based on the above O1 interface, Service management and orchestration device of the base station.

12. In paragraph 10, The change request for the above Legacy RAN includes a message indicating a parameter change, type information indicating Legacy, and an identifier identifying the change request. The change request transmitted to the above Legacy RAN includes a message indicating a parameter change. Service management and orchestration device of the base station.

13. A computer-readable recording medium for executing a method for service management and orchestration of a base station, The above service management and orchestration method, A step for receiving a message for SMO (Service Management and Orchestration) based on an interface (R1 interface) between an rApp and a Non-RT RIC framework where an R1 service is produced and used from a Non-RT RIC application (rApp, Non-real-time RAN intelligent Controller application). The above R1 service includes at least one of service registration and service discovery, service authentication and authorization, AI / ML (Artificial Intelligence / Machine Learning) service, or RAN OAM (Radio Access Network Operation Administration Maintenance) related service; A step for determining whether the above message conforms to the interface for O-RAN (O1 interface); If the above message does not conform to the O1 interface, a step of activating an interface capable of controlling the Legacy O-RAN and operating the Legacy O-RAN; and A computer-readable recording medium, which executes a step of operating O-RAN based on the O1 interface when the above message conforms to the O1 interface.

14. In paragraph 13, Based on the above R1 interface, service registration and service discovery are performed, and the O-RAN registered in the above SMO is controlled. A registration request for the Legacy RAN is received from the above rApp, A response to the registration request is sent to the above rApp, The above registration request and the above response each include type information and identification information indicating the Legacy RAN. Computer readable recording medium.

15. In paragraph 14, Registration completion information is transmitted to the Legacy RAN, a request is transmitted to the Legacy RAN to collect configuration information including at least one of CM (Configuration Management) information, PM (Performance Management) information, and FM (Fault Management) information, and in response to the request, the configuration information is received from the Legacy RAN. The above setting information is updated based on the above SMO. Computer readable recording medium.

16. In paragraph 14, A change request for the above Legacy RAN is received, If the above change request does not conform to the O1 interface, the method comprises the steps of transmitting a change request to the Legacy RAN; A step of receiving information indicating a parameter change from the Legacy RAN; a step of transmitting information indicating a change in said parameter to said rApp; A step of receiving an update request for parameter change from the above rApp, Further comprising a step of updating change information for the Legacy RAN, Computer readable recording medium.

17. In paragraph 16, If the change request conforms to the O1 interface, the method further includes a step of operating O-RAN based on the O1 interface. Computer readable recording medium.

18. In paragraph 16, The change request for the above Legacy RAN includes a message indicating a parameter change, type information indicating Legacy, and an identifier identifying the change request. The change request transmitted to the above Legacy RAN includes a message indicating a parameter change. Computer readable recording medium.

19. At least one application that produces and processes services; An R1 Termination unit controlling the exchange of messages based on a first interface between at least one application and a Non-RT RIC (O-RAN Non-real-time RAN intelligent Controller) framework; Intra message structure for sending and receiving the above messages; Legacy Termination that controls Legacy RAN; and O1 Termination controlling O-RAN; Including; At least one of the above applications, Determine whether the above message conforms to the second interface for O-RAN, If the above message does not conform to the second interface, activate the interface capable of controlling the Legacy O-RAN and operate the Legacy O-RAN; and If the above message conforms to the O1 interface, the O-RAN is operated based on the second interface. Service management and orchestration system.

20. In paragraph 19, The above rApp controls the O-RAN registered in the SMO by performing service registration and service discovery based on the R1 interface. The above rApp transmits a registration request for the Legacy RAN to the message control unit, The above message control unit transmits a response to the registration request to the above rApp, The above registration request and the above response each include type information and identification information indicating the Legacy RAN. Service management and orchestration system.

Images