Abstract: Techniques for enabling access in a multi-assistant speech processing system are described, where a first assistant system may use components of a second assistant system as data processing components. Runtime operational data and user input data related to the first assistant may be kept separate from the processing data and input data related to the second assistant by propagating a first account ID, for user inputs directed to the first assistant, through the processing pipeline, and using a second account for user inputs directed to the second assistant. A mapping between the first account ID and the second account ID may be accessible to a select number of system components. Handoffs between the two assistants are handled in a manner where data related to one assistant is not accessible by the other assistant.

Abstract: A method for optimizing the scheduling of an O-Cloud node, the method includes: determining a NF hosted on a O-Cloud node to be migrated to another O-Cloud nodes; sending a recommendation to the SMO to migrate the determined NF; sending instructions to implement the migration of the NF via an O2 interface to an O-Cloud management service; controlling the implementation of the migration of the determined NF to the other O-Cloud nodes; upon implementation of the migration, sending a confirmation notice to the SMO via the O2 interface; wherein the determining the one or more network functions NFs to be migrated, includes: obtaining data referring to historical and/or current utilization patterns of a O-Cloud node and/or a NF hosted thereon; inputting the data to an AI/ML model; obtaining a prediction of a utilization scenario; and determining a migration recommendation for the NF.

Abstract: A method including determining, by a processor, whether a processing load on one or more network slice subnet management functions (NSSMFs) has exceeded a predetermined processing limit; and determining, by the processor, which processing load on the one or more NSSMFs has exceeded the predetermined processing limit; and implementing, by the processor, based on the processing load that exceeded the predetermined processing limit, an additional NSSMF for each NSSMF that exceeded the predetermined processing limit.

Abstract: A method includes creating, by a processor and based on a network slice design submitted by a user, a network slice; and generating, automatically by the processor, a network slice selection assistance information ID (nSSAI ID) for the network slice.

Abstract: A correlation engine and policy manager (CPE) system includes: a persistent database, a cache database, an event gate, an event enricher, an event transformer, and an event dispatcher. The event gate obtains event data from at least one event source, and forwards the event data to the event enricher. The event enricher enriches the event data with additional data in the cached business layer data of the cache database, and forwards the enriched event data to the event transformer. The event transformer applies one or more policies in a cached business layer data of the cache database to the enriched event data to obtain transformed event data, and outputs the transformed event data to be stored in the persistent database. The event dispatcher dispatches output data to cause or prompt an action responsive to the transformed event data satisfying the at least one policy.

Abstract: Provided are a method and system for cordoning an open radio access network (O-RAN) cloud (O-Cloud) node The method may include: receiving, by a Service Management and Orchestration Framework (SMO) function, a first request to cordon at least one O-Cloud node, the first request being received from a user terminal or from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC); transmitting, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to cordon the at least one O-Cloud node based on the received first request; and receiving, from the IMS/DMS, a first notification that the at least one O-Cloud node has been cordoned, wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).

Abstract: Provided are a method and system for cordoning an open radio access network (O-RAN) cloud (O-Cloud) node The method may include: receiving, by a Service Management and Orchestration Framework (SMO) function, a first request to cordon at least one O-Cloud node, the first request being received from a user terminal or from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC); transmitting, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to cordon the at least one O-Cloud node based on the received first request; and receiving, from the IMS/DMS, a first notification that the at least one O-Cloud node has been cordoned, wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).

Abstract: A system includes processing circuitry and a memory connected to the processing circuitry. The memory is configured to store executable instructions that, when executed by the processing circuitry, facilitate performance of operations. The operations include filtering, based upon business logic, business data within a cache database. Converting the filtered business data into a data model. Loading the data model to a persistent cache database. Obtaining event messages from a data source, where the event messages are generated by one or more state changes within a network operatively connected to the system. Obtaining, for an event message, event-related data from the data model, where the event-related data is topologically related to the event message. Combining the event message with the event-related data from the data model. Framing the event message with the event-related data; and route the frame according to a user-defined configuration file.

Abstract: A correlation engine and policy manager (CPE) system includes: a persistent database, a cache database, an event gate, an event enricher, an event transformer, and an event dispatcher. The event gate obtains event data from at least one event source, and forwards the event data to the event enricher. The event enricher enriches the event data with additional data in the cached business layer data of the cache database, and forwards the enriched event data to the event transformer. The event transformer applies one or more policies in a cached business layer data of the cache database to the enriched event data to obtain transformed event data, and outputs the transformed event data to be stored in the persistent database. The event dispatcher dispatches output data to cause or prompt an action responsive to the transformed event data satisfying the at least one policy.

Abstract: A system includes processing circuitry; and a memory connected to the processing circuitry, wherein the memory is configured to store executable instructions that, when executed by the processing circuitry, facilitate performance of operations, including: receive an event message frame from a data source, wherein the event message frame is generated by one or more state changes within a network operatively connected to the system; correlate one or more business policies based the event message frame; apply the one or more operations to the event message frame based on the one or more business policies to create a transformed event message frame; and route the transformed event message frame to a message queue.

Abstract: A system includes processing circuitry and a memory connected to the processing circuitry. The memory is configured to store executable instructions that, when executed by the processing circuitry, cause the processing circuitry to startup a configuration parser module and an invoke worker module. To obtain a configuration file from a database where the configuration file specifies configuration information for constructing a pluggable event gate that includes a data adaptor for an online source, a data adaptor for an offline source, a data adaptor sink. To construct one or more event gates based on the configuration file. The configuration file further specifies one or more user-defined data sources and one or more user-defined data sinks. To create, responsive to a number of the user-defined data sources and a number of user-defined data sinks, multiprocessing workers located on one or more cores of a network and share data between the multiprocessing workers.

Abstract: A system includes processing circuitry and a memory connected to the processing circuitry. The memory is configured to store executable instructions that, when executed by the processing circuitry, facilitate performance of operations. The operations include filtering, based upon business logic, business data within a cache database. Converting the filtered business data into a data model. Loading the data model to a persistent cache database. Obtaining event messages from a data source, where the event messages are generated by one or more state changes within a network operatively connected to the system. Obtaining, for an event message, event-related data from the data model, where the event-related data is topologically related to the event message. Combining the event message with the event-related data from the data model. Framing the event message with the event-related data; and route the frame according to a user-defined configuration file.

Abstract: An application programming interface (API) server for a correlation engine and policy manager (CPE) system includes a processor, and a memory coupled to the processor. The CPE system includes a plurality of components of various component types, and each component among the plurality of components is configured to perform at least one corresponding processing on event data input to the CPE system. The memory is configured to store executable instructions that, when executed by the processor, cause the processor to perform at least one of registering, removing or updating a configuration of at least one component among the plurality of components of the CPE system, or changing a number of components of a same component type among the various component types, to scale up or down the CPE system.