Systems and methods for cloud-native network function data streaming

Abstract

A cellular communication system includes a plurality of network functions (NF) executing on a plurality of components in the cellular communication system and configured to report collected data, such as RAN NTs and core network NF s that may function as a MnS producer. A MnS consumer implementation may transmit a session establishment request to a MnS producer from a destination of the MnS producer, the session establishment request including first subscription information. The MnS consumer implementation receives publication requests and routes, by a messaging framework, the publication request to a destination in the MnS consumer implementation according to second subscription information received from the destination in the MnS consumer implementation.

Description

Attorney Docket No. RAKU-13600WO (PI25-00138W001) Title: SYSTEMS AND METHODS FOR CLOUD-NATIVE NETWORK FUNCTION DATA STREAMINGCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to U.S Provisional Application Serial No. 63 / 778,913 filed March 27, 2025; the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to systems and methods for native network function data streaming.BACKGROUND

[0003] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] The third-generation partnership project (3 GPP) standard provides for a management system that implements back-end software for managing a cellular communication network. Managing the cellular communication network includes collecting a large amount of data that must be streamed with high-reliability to the management system.Attorney Docket No. RAKU-13600WO (PI25-00138W001) SUMMARY

[0005] In one aspect, an apparatus includes a management service (MnS) consumer implementation configured to transmit a session establishment request to a MnS producer to destination of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network. The MnS consumer implementation receives, from the MnS producer, published data based on message bus publishing protocol, the published data corresponding to the first subscription information. The MnS consumer implementation routes, by a messaging framework internal to the MnS consumer implementation, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.

[0006] In another aspect, a method includes transmitting, by a management service (MnS) consumer implementation, a session establishment request to a MnS producer to one or more destinations of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network. The method includes receiving, by the MnS consumer implementation, from the MnS producer, published data based on a message bus publishing protocol, the published data corresponding to the first subscription information. The method includes routing, by the MnS consumer implementation, by a messaging framework internal to the MnS consumer implementation, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one orAttorney Docket No. RAKU-13600WO (PI25-00138W001) more destinations, the second subscription information being different from the first subscription information.

[0007] In another aspect, a non-transitory computer-readable medium stores executable code that, when executed in a cellular communication system, causes the cellular communication system to: transmit, by a management service (MnS) consumer implementation, a session establishment request to a MnS producer to one or more destinations of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network; receive, by the MnS consumer implementation, from the MnS producer, published data based on a message bus publishing protocol, the published data corresponding to the first subscription information; and route, by the MnS consumer implementation, by a messaging framework internal to the MnS consumer, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0009] Fig. 1 is a schematic block diagram illustrating a cellular communication network in accordance with an embodiment;

[0010] Fig. 2 is a schematic block diagram illustrating the streaming of network function data in a cloud-computing environment in accordance with an embodiment;Attorney Docket No. RAKU-13600WO (PI25-00138W001)

[0011] Fig. 3 is a process flow diagram of a method for transferring data between a management service (MnS) producer and consumer in accordance with an embodiment;

[0012] Fig. 4 is a schematic block diagram illustrating an approach for streaming network function data using a message bus in accordance with an embodiment;

[0013] Fig. 5 is a process flow diagram of a method for transferring data between management functions using a message bus in accordance with an embodiment;

[0014] Fig. 6 is a schematic block diagram illustrating an approach for streaming network function data using a technology-agnostic message bus in accordance with an embodiment;

[0015] Fig. 7 is a process flow diagram of a method for streaming network function data using a technology-agnostic message bus in accordance with an embodiment;

[0016] Fig. 8 is a schematic block diagram illustrating an approach for streaming network function data using WebSocket connections in accordance with an embodiment;

[0017] Fig. 9 is a schematic block diagram illustrating an approach for streaming network function data using message brokers in accordance with an embodiment;

[0018] Fig. 10 is a schematic block diagram of an example computing device suitable for implementing methods in accordance with embodiments of the disclosureDETAILED DESCRIPTION

[0019] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustrations and descriptions but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the present disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may beAttorney Docket No. RAKU-13600WO (PI25-00138W001) incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to at least one of the embodiments in the present disclosure. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0020] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods should not limit their implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0021] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

[0022] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” (in other words, nouns not mentioned in the plural) are intended to include one or more items, and may be usedAttorney Docket No. RAKU-13600WO (PI25-00138W001) interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0023] Referring to Fig. 1, in a cellular communication system 100 user equipment (UE) 102 transmits wireless signals to one or more antennas 104 coupled to a radio unit (RU) 106 configured to manage generated signals to be transmitted over the antenna 104 and to detect signals received by the antenna 104. The RU 106 may be implemented as part of a gNodeB (gNB) in a fifth generation (5G) network, sixth generation network (6G) (e.g., a 6NB), or other type of network. The data transmitted to the UE 102 and received from the UE 102 as well as managing a logical connection with the UE 102 according to a cellular communication protocol may be managed by a distributed unit (DU) 108 of the gNB that is coupled to the RU 106. Each DU 108 may be in data communication with a central unit (CU) 112 of the gNB. The CU 112 may perform functions that require coordination among DUs 108 such as performing handoffs of connections to UE 102 between RU 106.

[0024] The cellular communication system 100 may include a core network 114 executing core network NFs 116, such as the access and mobility management function (AMF), user plane function (UPF), and session management function (SMF).

[0025] Some or all of the RU 106, DU 108, CU 112, and core network 114 may be connected to a management system 118 (e.g., a 3GPP management system). The management system 118 may gather data reported by network functions (NFs) in the cellular communication network, such as performance data. The network functions may include radio access networks (RAN) NFsAttorney Docket No. RAKU-13600WO (PI25-00138W001) executing on some or all of the RU 106, DU 108, or CU 112, such as a gNodeB central unit control plane (GNB-CU-CP), a gNodeB central unit user plane (GNB-CU-UP) and / or gNodeB distributed unit (GNB-DU). The network functions may include the core network NF s 116.

[0026] The management system 118 may further control operation of one or more of the RU 106, DU 108, CU 11 , or core network 114. The management system 118 may gather data reported by the UE 102, such as by way of the RU 106, DU 108, and / or CU 112. In the subsequent description, reference is made to the management system 118 with the understanding that other management platforms may be used in a like manner, such as the operations support system (OSS) used in the Third Generation Partnership Project (3 GPP) standard.

[0027] Referring to Fig. 2., the management system 118 may be implemented in one or more cloud computing platforms 200a, 200b. However non-cloud implementations may also be implemented. In some embodiments, an edge cloud computing platform 202 may also be used and may provide a central cloud computing platform for interacting with a plurality of other cloud computing platforms 200a, 200b. There may be any number of cloud computing platforms 200a, 200b in cellular communication system 100. Each cloud computing platform 200a, 200b, 202 may itself be implemented as an O-cloud according to the Open Radio Access Network (O-RAN) standard. The cloud computing platforms 200a, 200b, 202 may be implemented on a general-purpose cloud computing platform, e.g., AMAZON Web Services (AWS), MICROSOFT AZURE, GOOGLE CLOUD, or the like.

[0028] A messaging framework 204 may execute in the edge cloud computing platform 202 or in one of the cloud computing platforms 200a 200b. The messaging framework 204 facilitates the exchange of data between a source of data and a destination of the data. The messaging framework 204 may be implemented according to any of the approaches described below withAttorney Docket No. RAKU-13600WO (PI25-00138W001) respect to Figs. 3 to 9.

[0029] In some embodiments, the cloud computing platforms 200a, 200b may implement network functions (NFs) 206 that produce data, such as performance monitoring (PM) data, facilities management (FM) data, or other data. Each network function may implement one or more workloads, such as containerized workloads 208, that collect and transmit the data. The transmission of the data may be managed by a management function 210 of the NF 206. There may be any number of NFs 206. The cloud computing platforms 200a, 200b may execute one or more operations, administration, and management (0AM) applications 212 that consume data generated by the NFs 206. Each 0AM application 212 may include one or more containerized workloads 214 executing the functions of the application 212.

[0030] Communication between the NF s 206 and the 0AM applications 212 may be facilitated by the messaging framework 204. In the illustrated example, NFs 206 and 0AM applications 212 execute in different cloud computing platforms 200a, 200b and the messaging framework 204 executes in the edge cloud computing platform 202. In some embodiments, all of the messaging framework 204, NFs 206, and 0AM applications 212 execute in a single cloud computing platform 200a.

[0031] Referring to Fig. 3, the illustrated method 300 may be implemented by a management service (MnS) producer 302 and a MnS consumer 304. For example, the MnS producer 302 may be implemented by a management function associated with a NF 206 (e.g., “the MnS producer 302 implementation”) and the MnS consumer 304 may be implemented by a combination of the messaging framework 204 and one or more 0AM applications 212 (e g., “the MnS consumer 304 implementation”). The illustrated method 300 may be implemented by the MnS producer 302 and the MnS consumer 304 using the messaging framework 204 of the MnS consumer 304.Attorney Docket No. RAKU-13600WO (PI25-00138W001)

[0032] At step 306, the MnS consumer 304 provides management data job control to the MnS producer 302, such as to one or more destinations in the MnS producer 302, such as a NF 206 or containerized workload 208 of a NF 206. For example, the MnS consumer 304 may transmit data defining creation of a performance management (PM) job or trace job. Fhe MnS consumer 304 may transmit first subscription information defining a first subscription to a performance management metric generated by the PM or trace job. Step 306 may include transmitting endpoint information, e.g., an identifier of the MnS consumer 304, an address of the MnS consumer 304, or other information.

[0033] In response to step 306, the MnS producer 302 may perform message bus communication over the messaging framework 204 at step 308. For example, the MnS producer 302 may transmit publication requests including published data using a message bus-based communication protocol to the MnS consumer 304 corresponding to the management data job control received at step 306. The MnS producer 302 may record a first subscription of the MnS consumer 304 in the management data job control received at step 306 and send the publication requests according to transmission endpoint information provided by the MnS consumer 304 according to the first subscription. The transmission endpoint information may correspond to a message broker endpoint from which instances of one or more 0AM applications 212implementing the MnS consumer 304 can retrieve data.

[0034] Fig. 4 illustrates an example message bus that may be implemented as part of a MnF 400 in the management system along with one or more 0AM applications 212 inside the MnF 400. The MnF 400 is an example of a MnS consumer 304 implementation. In the illustrated embodiment, the messaging framework 204 is implemented by the message bus. The messaging framework 204 and 0AM applications 212 may be implemented in the MnF 400, such as a MnFAttorney Docket No. RAKU-13600WO (PI25-00138W001) 400 executing in a cloud computing platform 200a, 200b, or 202.

[0035] In the illustrated embodiment, the messaging framework 204 includes a load balancer 402 and a plurality of message brokers 404. The load balancer 402 receives publication requests from the MnF 210, e.g., publication requests generated by the containerized workloads 208 of the NF 206 and transmitted by the MnF 210 to the messaging framework 204. The publication requests may include metric identifiers or other identifiers indicating the type of data in the publication requests. For each publication request, the load balancer 402 selects a message broker 404 from the plurality of message brokers 404 according to a load balancing algorithm and transmits the publication request to that message broker 404. The message broker 404 then processes the publication requests according to second subscription information received by the message broker 404 from one or more destinations in the MnF 400 that defines a second subscription, the second subscription information being different from the first subscription information. For example, second subscription information may be received from one or more 0AM applications 212 such that the message broker 404 forwards the data to each 0AM application 212 that have subscribed for the data internally to the MnF 400 according to the second subscription information.

[0036] Fig. 5 illustrates a method 500 that may be implemented by the MnF 210 of the NF 206 and the MnF 400 including the one or more 0AM applications 212. At step 502, the MnF 400, such as an 0AM application 212 of the MnF 400, requests to establish a message bus communication session with the NF 206. The request may include first subscription information identifying one or more topics. The topics may include the identifier of a metric, an identifier of a component of the cellular communication system 100, an identifier of a class of components (e.g., in a geographic area, of a certain type, etc.), and / or other indicator of a type of PM, FM, or other data requested by the 0AM application 212. The request of step 502 may include anAttorney Docket No. RAKU-13600WO (PI25-00138W001) identifier, e.g., address, of message brokers 404 implemented in the MnF 400.

[0037] Step 502 may include the 0AM application 212 making an application programming interface (API) call to an API implemented by the MnF 210. The request of step 502 may be transmitted directly from the 0AM application 212 to the MnF 210, such as through the one or more cloud computing platforms 200a, 200b, 202 hosting the 0AM application 212 and MnF 210.

[0038] At step 504, the MnF 210 reports management data according to a message bus publishing protocol, e.g., a publication request according to a message bus protocol implemented by the load balancer 402 and the message broker 404. For example, the MnF 210, e.g., a containerized workload 208 of the NF 206, may perform a function (e.g., collect data, process data to obtain a metric, or execute some other function) and return a result of the function as the publication request according to the first subscription information. The MnF 210 may forward the management data, e.g., a publication request, to the load balancer 402. The MnF 210 may label the forwarded management data with one or more topics corresponding to the function that generated the management data.

[0039] At step 506, the load balancer 402 and message brokers 404 route the publication request including the management data to each 0AM application 212, e.g., to each containerized workload 214, having an identifier associated with the topics include with the management data, i.e., subscribed to the topics according to second subscription information received by the message brokers 404 from the 0AM application 212, the second subscription information being different from the first subscription information. For example, the load balancer 402 may select a message broker 404 from a plurality of message brokers 404 according to a load balancing and that message broker 404 may then processes the publication request by identifying subscribers that are subscribed to the topics included with the management data and forwarding the publication requestAttorney Docket No. RAKU-13600WO (PI25-00138W001) to the subscribers.

[0040] Fig. 6 illustrates an approach for streaming network function data using a technologyagnostic message bus. The messaging framework 204 and 0AM applications 212 may be implemented in a MnF 600, such as a MnF executing in a cloud computing platform 200a, 200b, or 202. The MnF 600 is an example of a MnS consumer 304 implementation.

[0041] In the approach of Fig. 6, the messaging framework 204 is technology agnostic in the sense that the messaging framework 204 may adapt itself to any of a plurality of message bus technologies that may be implemented by the MnF 210. In particular, the messaging framework 204 may configure itself with a load balancer 602, messaging server 604, and possibly an aggregation and distribution layer 606 according to a message bus technology implemented by the MnF 210 (see Figs. 8 and 9 and corresponding description). In this manner, modification of an MnF 210 is not required to implement a specific message bus technology, which facilitates the operation of heterogeneous cellular communication systems 100 including components from different providers or manufactured at different times.

[0042] Fig. 7 illustrates a method 700 that may be performed by the MnF 210 of an NF 206 and the MnF 600. At step 702 the MnF 210 transmits a request to establish a communication session. In response to the request of step 702, the MnF 210 reports a message bus type to the MnF 600 at step 704. For example, the message bus type may include a WebSocket, KAFKA, REDIS, RABBITMQ, or other message bus type. The MnF 600 receives the report from step 704 and instantiates a messaging framework 204 corresponding to the type at step 706. Step 704 may require that the MnF 210 to be able to respond to the request from step 702. However, subsequent steps of the method 700 may be performed by an otherwise unmodified MnF 210. For example, steps 702 and 704 may be performed by making calls to an API implemented by the MnF 210 thatAttorney Docket No. RAKU-13600WO (PI25-00138W001) is independent of the message bus type and by which the MnF 210 can receive requests to discover the message bus type supported by the MnF 210 at step 702 and report the message bus type at step 704.

[0043] The MnF 600 then establishes a communication session with the MnF 210 according to the type at step 708. Step 708 may include transmitting information identifying a destination for the communication session (e.g., an identifier 0AM application 212 and / or containerized workload 214) according to a protocol defined for the type. Step 708 may include transmitting management control, such as PM or trace job creation, metric subscription, or other information. Step 708 may include transmitting subscription information, e.g., topics associated with the identifier of the destination for the communication session, e.g., first subscription information as discussed above. The first subscription information may be received by the messaging framework 204.

[0044] Following establishment of a communication session according to the type at step 708, the MnF 210 reports management data to the MnF 600 according to the message bus type at step 710, e.g., within the communication session established at step 708 and according to the protocol defined for the type. For example, step 708 may include generating a publication request including the management data according to the first subscription information.

[0045] The MnF 600, e.g., the messaging framework 204 instantiated at step 706, then routes the publication request including the management data to subscribers at step 712. The routing may be performed according to the type of the message bus and according to second subscription information received as part of step 708, e.g., topics associated with the identifier of the destination for the communication session and topics included in the management data. For example, the destination for the second subscription information may be received from an 0AM applicationAttorney Docket No. RAKU-13600WO (PI25-00138W001) 212.

[0046] Figs. 8 and 9 illustrate messaging frameworks according to two example message bus types that may be instantiated at step 706.

[0047] Referring to Fig. 8, where the message bus type is WebSocket, the messaging framework 204 may include a WebSocket load balancer 802, one or more WebSocket server nodes 804a and one or more high-availability WebSocket server nodes 804b that are instantiated and deinstantiated as needed according to loading. The messaging framework 204 may include a data aggregation and distribution layer 806.

[0048] In operation, a source (e.g., the containerized workloads 208 of the NF 206) may transmit WebSocket connection requests to the WebSocket load balancer 802. The WebSocket load balancer 802 selects a WebSocket server node 804a, 804b according to a load balancing algorithm (“the selected server node”). The source establishes a persistent WebSocket connection with the selected server node and publishes data to the selected server node according to a messaging session, e.g., the PM or trace job, metric, or other information defined for the messaging session according to the method 700. The connection to the selected server node may persist throughout a messaging session and may be reestablished if interrupted.

[0049] The selected server node evaluates publication requests with respect to subscriptions received from one or more destinations (e.g., according to second subscription information discussed above received from one or more containerized workloads 214 of one or more 0AM applications 212) and transmits the publication requests to the each destination that is subscribed to receive the publication requests, e.g., to topics include in the publication requests. The data aggregation and distribution layer 806 may buffer publication requests for a destination and periodically transfer the buffered publication requests to the destination.Attorney Docket No. RAKU-13600WO (PI25-00138W001)

[0050] Referring to Fig. 9, where the message bus type is KAFKA, REDIS, RABBITMQ, or other type of message broker architecture, the messaging framework 204 may include a load balancer 902, one or more message brokers 904a, and one or more high-availability message brokers 904b that are instantiated and de-instantiated as needed according to loading.

[0051] In operation, a source (e.g., the containerized workloads 208 of the NF 206) may send publication requests to the load balancer 902 according to messaging sessions established according to the method 700. The load balancer 902 selects a message broker 904a, 904b according to a load balancing algorithm (“the selected message broker”) and forwards the publication request to the selected message broker. The selected server node evaluates the publication request, e.g., topics in the publication request, with respect to subscriptions received from one or more destinations (e.g., second subscription information as discussed above received one or more containerized workloads 214 of one or more 0 AM applications 212) and transmits the publication request to the each destination that is subscribed to receive the published data, e.g., to topics associated with the publication request. No persistent connection between the source and the selected message broker is created.

[0052] Fig. 10 illustrates an embodiment of a computing device 1000 that may be used to implement any of the components described above. As shown in Fig. 10, the device 1000 includes processor 1010, a memory 1020, a storage component 1030, an input component 1040, an output component 1050, a communication interface 1060, and a bus 1070.

[0053] The processor 1010, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 1010 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like.Attorney Docket No. RAKU-13600WO (PI25-00138W001) The processor 1010 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0054] Memory 1020 includes a non-transitory computer readable medium. Memory 1020 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 1010. The memory 1020 comprises machine-readable instructions which are executable by the processor 1010. These machine-readable instructions when executed by the processor 1010 cause the processor 1010 to perform one or more method steps of an embodiment described above.

[0055] Storage component 1030 stores information and / or software related to the operation and use of the device 1000. For example, storage component 1030 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0056] Input component 1040 is configured to receive information, such as user input. For example, the input component 1040 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 1040 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0057] Output component 1050 is configured to provide output information from the device 1000. For example, the output component 1050 may be, but not limited to, a display, a speaker, instructions to an external device, and / or one or more light-emitting diodes (LEDs).Attorney Docket No. RAKU-13600WO (PI25-00138W001)

[0058] Communication interface 1060 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 1060 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 1000 and other devices. In other words, the standard of the communication interface 1060 is not limited.

[0059] The bus 1070 acts as an interconnect between the processor 1010, the memory 1020, the storage component 1030, the input component 1040, the output component 1050, and the communication interface 1060 of the device 1000. The bus 1070 may include a wired interconnection or a wireless interconnection.

[0060] The number and arrangement of components shown in Fig. 10 are provided as an example. In practice, device 1000 may include additional components, fewer components, different components, or differently arranged components than those shown in Fig. 10. Additionally, or alternatively, a set of components (e.g., one or more components) of device 1000 may perform one or more functions described as being performed by another set of components of device 1000. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 1000 in communication with one another.

[0061] In a first example embodiment, an apparatus includes: a management service (MnS) consumer implementation configured to: transmit a session establishment request to a MnS producer to destination of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network; receive, from the MnS producer, published data based on message bus publishing protocol, the published data corresponding to the first subscriptionAttorney Docket No. RAKU-13600WO (PI25-00138W001) information; and route, by a messaging framework internal to the MnS consumer implementation, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.

[0062] In a second example embodiment according to the first example embodiment, the cellular communication network is a third-generation partnership project (3GPP) communication network.

[0063] In a third example embodiment according to the first example embodiment, the MnS consumer implementation is further configured to: (a) receive from the MnS producer a message bus type in response to the session establishment request; and in response to (a), instantiate the messaging framework, the messaging framework corresponding to the message bus type.

[0064] In a fourth example embodiment according to the third example embodiment, the message bus type includes at least one of WebSocket, KAFKA, REDIS, or RABBITMQ.

[0065] In a fifth example embodiment according to the fourth example embodiment, the message bus type is WebSocket and the messaging framework includes a load balancer, a plurality of WebSocket servers, and a data aggregation and distribution layer.

[0066] In a sixth example embodiment according to the fourth example embodiment, the message bus type is at least one of KAFKA, REDIS, or RABBITMQ and the messaging framework includes a load balancer and a plurality of message brokers.

[0067] In a seventh example embodiment according to the first example embodiment, the one or more destinations in the MnS consumer implementation are one or more operations, administration, and management (0AM) application.Attorney Docket No. RAKU-13600WO (PI25-00138W001)

[0068] In an eighth example embodiment according to the seventh example embodiment, the first subscription information includes one or more metrics.

[0069] In a ninth example embodiment according to the first example embodiment, the MnS consumer implementation and the MnS producer execute in one or more cloud computing platforms.

[0070] In a tenth example embodiment according to the first example embodiment, the network function is at least one of an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), a gNodeB central unit control plane (GNB-CU-CP), a gNodeB central unit user plane (GNB-CU-UP), or a gNodeB distributed unit (GNB-DU).

[0071] In an eleventh example embodiment, a method includes: transmitting, by a management service (MnS) consumer implementation, a session establishment request to a MnS producer to one or more destinations of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network; receiving, by the MnS consumer implementation, from the MnS producer, published data based on a message bus publishing protocol, the published data corresponding to the first subscription information; and routing, by the MnS consumer implementation, by a messaging framework internal to the MnS consumer implementation the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.Attorney Docket No. RAKU-13600WO (PI25-00138W001)

[0072] In a twelfth example embodiment according to the eleventh example embodiment, the cellular communication network is a third-generation partnership project (3GPP) communication network.

[0073] In a thirteenth example embodiment according to the eleventh example embodiment, the method includes: (a) receiving, by the MnS consumer implementation, from the MnS producer a message bus type in response to the session establishment request; and in response to (a), instantiating, by the MnS consumer implementation, the messaging framework, the messaging framework corresponding to the message bus type.

[0074] In a fourteenth example embodiment according to the thirteenth example embodiment, the message bus type includes at least one of WebSocket, KAFKA, REDIS, or RABBITMQ.

[0075] In a fifteenth example embodiment according to the fourteenth example embodiment, the message bus type is WebSocket and the messaging framework includes a load balancer, a plurality of WebSocket servers, and a data aggregation and distribution layer.

[0076] In a sixteenth example embodiment according to the fourteenth example embodiment, the message bus type is at least one of KAFKA, REDIS, or RABBITMQ and the messaging framework includes a load balancer and a plurality of message brokers.

[0077] In a seventeenth example embodiment according to the eleventh example embodiment, the one or more destinations in the MnS consumer implementation are one or more operations, administration, and management (0AM) application.

[0078] In an eighteenth example embodiment according to the eleventh example embodiment, the first subscription information includes one or more metrics.

[0079] In a nineteenth example embodiment according to the eleventh example embodiment, the network function is at least one of an access and mobility management function (AMF), a userAttorney Docket No. RAKU-13600WO (PI25-00138W001) plane function (UPF), a session management function (SMF), a gNodeB central unit control plane (GNB-CU-CP), a gNodeB central unit user plane (GNB-CU-UP), or a gNodeB distributed unit (GNB-DU).

[0080] In a twentieth example embodiment, a non-transitory computer-readable medium stores executable code that, when executed in a cellular communication system, causes the cellular communication system to: transmit, by a management service (MnS) consumer implementation, a session establishment request to a MnS producer to one or more destinations of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network; receive, by the MnS consumer implementation, from the MnS producer, published data based on a message bus publishing protocol, the published data corresponding to the first subscription information; and route, by the MnS consumer implementation, by a messaging framework internal to the MnS consumer the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.

Claims

Attorney Docket No. RAKU-13600WO (PI25-00138W001) Claims:

1. An apparatus comprising:a management service (MnS) consumer implementation configured to: transmit a session establishment request to a MnS producer to destination of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network;receive, from the MnS producer, published data based on message bus publishing protocol, the published data corresponding to the first subscription information; and route, by a messaging framework internal to the MnS consumer implementation, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.

2. The apparatus of claim 1, wherein the cellular communication network is a third-generation partnership project (3 GPP) communication network.

3. The apparatus of claim 1, wherein the MnS consumer implementation is further configured to:(a) receive from the MnS producer a message bus type in response to the session establishment request; andAttorney Docket No. RAKU-13600WO (PI25-00138W001) in response to (a), instantiate the messaging framework, the messaging framework corresponding to the message bus type.

4. The apparatus of claim 3, wherein the message bus type includes at least one of WebSocket, KAFKA, REDIS, orRABBITMQ.

5. The apparatus of claim 4, wherein the message bus type is WebSocket and the messaging framework includes a load balancer, a plurality of WebSocket servers, and a data aggregation and distribution layer.

6. The apparatus of claim 4, wherein the message bus type is at least one of KAFKA, REDIS, or RABBITMQ and the messaging framework includes a load balancer and a plurality of message brokers.

7. The apparatus of claim 1, wherein the one or more destinations in the MnS consumer implementation are one or more operations, administration, and management (OAM) application.

8. The apparatus of claim 7, wherein the first subscription information includes one or more metrics.

9. The apparatus of claim 1, wherein the MnS consumer implementation and the MnS producer execute in one or more cloud computing platforms.Attorney Docket No. RAKU-13600WO (PI25-00138W001)10. The apparatus of claim 1, wherein the network function is at least one of an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), a gNodeB central unit control plane (GNB-CU-CP), a gNodeB central unit user plane (GNB-CU-UP), or a gNodeB distributed unit (GNB-DU).

11. A method comprising:transmitting, by a management service (MnS) consumer implementation, a session establishment request to a MnS producer to one or more destinations of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network;receiving, by the MnS consumer implementation, from the MnS producer, published data based on a message bus publishing protocol, the published data corresponding to the first subscription information; androuting, by the MnS consumer implementation, by a messaging framework internal to the MnS consumer implementation, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.

12. The method of claim 11, wherein the cellular communication network is a third-generation partnership project (3 GPP) communication network.Attorney Docket No. RAKU-13600WO (PI25-00138W001) 13. The method of claim 11, further comprising:(a) receiving, by the MnS consumer implementation, from the MnS producer a message bus type in response to the session establishment request; andin response to (a), instantiating, by the MnS consumer implementation, the messaging framework, the messaging framework corresponding to the message bus type.

14. The method of claim 13, wherein the message bus type includes at least one of WebSocket, KAFKA, REDIS, orRABBITMQ.

15. The method of claim 14, wherein the message bus type is WebSocket and the messaging framework includes a load balancer, a plurality of WebSocket servers, and a data aggregation and distribution layer.

16. The method of claim 14, wherein the message bus type is at least one of KAFKA, REDIS, or RABBITMQ and the messaging framework includes a load balancer and a plurality of message brokers.

17. The method of claim 11, wherein the one or more destinations in the MnS consumer implementation are one or more operations, administration, and management (OAM) application.

18. The method of claim 11, wherein the first subscription information includes one or more metrics.Attorney Docket No. RAKU-13600WO (PI25-00138W001) 19. The method of claim 11, wherein the network function is at least one of an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), a gNodeB central unit control plane (GNB-CU-CP), a gNodeB central unit user plane (GNB-CU-UP), or a gNodeB distributed unit (GNB-DU).

20. A non-transitory computer-readable medium storing executable code that, when executed in a cellular communication system, causes the cellular communication system to: transmit, by a management service (MnS) consumer implementation, a session establishment request to a MnS producer to one or more destinations of the MnS producer, the session establishment request including first subscription information, the MnS producer being implemented by a network function (NF) of a cellular communication network;receive, by the MnS consumer implementation, from the MnS producer, published data based on a message bus publishing protocol, the published data corresponding to the first subscription information; androute, by the MnS consumer implementation, by a messaging framework internal to the MnS consumer implementation, the published data to one or more destinations in the MnS consumer implementation according to second subscription information provided by the one or more destinations, the second subscription information being different from the first subscription information.

Images