WO2025211751A1

WO2025211751A1 - Providing split operation pipeline details in a communication network system

Info

Publication number: WO2025211751A1
Application number: PCT/KR2025/004345
Authority: WO
Inventors: Sapan Pramodkumar SHAH; Arunprasath Ramamoorthy; Narendranath Durga Tangudu; Basavaraj Jayawant Pattan
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2024-04-05
Filing date: 2025-04-02
Publication date: 2025-10-09
Anticipated expiration: 2026-10-05

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein provide a method of a network apparatus for a split operation in a communication network system. The method includes: receiving, from a user equipment (UE), a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, validating whether the UE is authorized for the request, generating a subscription for the split operation in case that the UE is authorized, and transmitting, to the UE, a split operation subscribe response message that indicates the success of the subscription and includes a subscription identity.

Description

PROVIDING SPLIT OPERATION PIPELINE DETAILS IN A COMMUNICATION NETWORK SYSTEM

This application is based on and derives the benefit of Indian Provisional Application 202441028100 filed on 5^th April 2024 the contents of which are incorporated herein by reference. The present disclosure is related to the field of wireless communication. More particularly, the present disclosure is related to a method and system for providing split operation pipeline details in a communication network system.

5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GH" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

The principal object of the embodiments herein is to provide a system and method for providing split operation pipeline details in a communication network system.

Another object of the embodiments herein is to enable the AIML enablement client to send a request to subscribe for split operation pipeline related events to the AIML enablement server.

Yet another object of the embodiments herein is to allow the AIML enablement server to create the subscriptions and start monitoring split operation pipeline related events.

Yet another object of the embodiments herein is to allow the AIML enablement server to send notification to a subscriber when it detects that a new split operation profile is created or an existing pipeline is updated (for example, node is added or removed, stage order, ML models are modified, etc.) or deleted.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

Accordingly, the embodiments herein provide a method of a network apparatus for a split operation in a communication network system. The method includes: receiving, from a user equipment (UE), a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, validating whether the UE is authorized for the request, generating a subscription for the split operation in case that the UE is authorized, and transmitting, to the UE, a split operation subscribe response message that indicates the success of the subscription and includes a subscription identity.

Accordingly, the embodiments herein provide a method of a user equipment (UE) for a split operation in a communication network system. The method includes: transmitting, to a network apparatus, a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, and receiving, from the network apparatus, a split operation subscribe response message indicating a success or failure of the subscription.

Accordingly, the embodiments herein provide a network apparatus for a split operation in a communication network system. The network apparatus includes: a transceiver; and a controller coupled to the transceiver, the controller is configured to: receive, from a user equipment (UE), a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, validate whether the UE is authorized for the request, generate a subscription for the split operation in case that the UE is authorized, and transmit, to the UE, a split operation subscribe response message that indicates the success of the subscription and includes a subscription identity.

Accordingly, the embodiments herein provide a user equipment (UE) for a split operation in a communication network system. The UE includes: a transceiver; and a controller coupled to the transceiver, the controller is configured to: transmit, to a network apparatus, a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, and receive, from the network apparatus, a split operation subscribe response message indicating a success or failure of the subscription.

Aspects of the disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below.

Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

These and other features, aspects, and advantages of the present embodiments are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

Fig. 1 is a block diagram that illustrates a schematic of an AIML enablement client implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

Fig. 2 is a block diagram that illustrates a schematic of a network apparatus implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein.

Fig. 3 is a sequence diagram that illustrates a split operation pipeline subscribe-notify method according to an embodiment as disclosed herein.

Fig. 4 is a flow diagram that illustrate a method for providing split operation pipeline details in a communication network system by the AIML enablement client according to an embodiment as disclosed herein.

Fig. 5 is a flow diagram that illustrate a method for providing split operation pipeline details in a communication network system by the network apparatus according to an embodiment as disclosed herein.

Fig. 6 is a block diagram of an internal configuration of a base station, according to an embodiment.

Fig. 7 is a block diagram showing an internal structure of a terminal, according to an embodiment of the present disclosure.

In an embodiment, the split operation subscribe response message may indicate a failure of the subscription and includes a reason for the failure, in case that the subscription is not generated.

In an embodiment, the method may further include: detecting an event related to the split operation, and transmitting, to the UE, a split operation notification message indicating the event. The event may include at least one of: creation of a new split profile, an update of an existing pipeline and a deletion of an existing pipeline.

In an embodiment, the split operation notification message may include a split operation profile, and the split operation notification message may include information on at least one of: a split operation identifier, a head endpoint, a tail endpoint, or usage information of the split operation.

In an embodiment, the method may further comprises: receiving, from the network apparatus, a split operation notification message indicating the event. The event may include at least one of: creation of a new split profile, an update of an existing pipeline, or a deletion of an existing pipeline.

In an embodiment, the controller may further configured to: detect an event related to the split operation, and transmit, to the UE, a split operation notification message indicating the event. The event may include at least one of: creation of a new split profile, an update of an existing pipeline and a deletion of an existing pipeline.

In an embodiment, the controller is further configured to: receive, from the network apparatus, a split operation notification message indicating the event. The event may include at least one of: creation of a new split profile, an update of an existing pipeline, or a deletion of an existing pipeline.

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

The term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components. The terms such as “include” and/or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

The term “or” used in various embodiments of the present disclosure includes any or all of combinations of listed words. For example, the expression “A or B” may include A, may include B, or may include both A and B.

Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the present disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the present disclosure.

The accompanying drawings discussed below and various embodiments for describing the principles of the present disclosure in this patent document are only for illustration and should not be interpreted as limiting the scope of the disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with a plurality of other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

As is existing in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in a plurality of semiconductor chips, or on substrate supports such as printed circuit boards, and the like. The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., a plurality of programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method. Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

The accompanying drawings are used to help easily understand various technical features and it is understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the proposed method is construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. used herein to describe various elements, these elements are not be limited by these terms. These terms are generally used to distinguish one element from another.

Artificial Intelligence/Machine Learning (AI/ML) is being used in a range of application domains across industry sectors. In mobile communications systems, mobile devices (for example, smartphones, automotive, robots) are increasingly replacing conventional procedures (for example, speech recognition, image recognition, video processing) with the AI/ML models to enable applications. In order to offload the computation-intensive, energy-intensive parts to network endpoints, and to leave the privacy-sensitive and delay-sensitive parts at the end device, the AI/ML operation/model is split into multiple parts according to the current task, environment, and computation-intensive, energy-intensive parts are offloaded to network endpoints. The device executes the inference up to a specific layer of the machine learning model (for example, Convolutional Neural Network (CNN)) and sends the intermediate data to the network endpoints. Data can be provided at the entry point of the pipeline, and sequentially processed through each node of the pipeline.

3GPP is currently defining application enablement layer to support AI/ML operations. The AIML enablement client registers to AIML enablement server to indicate the client’s capability to perform AIML operations. The AIML enablement server supports AIML enablement client by providing AIML split operation pipeline by discovering the required nodes to perform split operation. However, some of the basic aspects to support AIML split operation are not specified in the standard, like when the split operation pipeline is created. The nodes that are added into the pipeline are not aware about the pipeline creation and also model on which they need to work. Further, the nodes that are added into the pipeline are not aware where to send the intermediate result for further processing. Also, when the AIML enablement client is removed from the pipeline or the whole pipeline is deleted, the nodes from the pipeline are not aware of the latest situation or updates made within the pipeline.

Hence, is desirable to address the above mentioned problems and disadvantages or at least provide a useful alternative.

In the prior art, the AI/ML operation is split into multiple parts and computation-intensive, energy-intensive parts are offloaded to network endpoints. The 3GPP is defining the enabler layer to support AIML operations. The AIML enablement server supports AIML enablement client by providing AIML split operation pipeline by discovering the required nodes to perform split operation. However, the nodes which are added in to the pipeline are not aware of any pipeline specific information. The proposed solution provides a method for the AIML enabler client to subscribe for AIML split operation pipeline related events.

The proposed solution discloses a system and method for providing split operation pipeline details. The method includes supporting basic AIML split operation capability to the AIML enablement layer. The AIML enablement client sends a subscription request to the AIML enablement server to receive split operation pipeline related events. Upon the AIML enablement client being added to the pipeline, the AIML enablement server sends a notification to the AIML enablement client indicating pipeline creation event along with pipeline identity, model information, list of all nodes added into the pipeline, notification target where the result of the slit operation is to be sent, and the like. Upon the AIML enablement client being removed from the pipeline or the pipeline itself being removed, the AIML enablement server sends the notification to the AIML enablement client indicating the pipeline removal event along with pipeline identity. Upon the split operation pipeline being updated (for example, new nodes are added into the pipeline), the AIML enablement server sends the notification to the AIML enablement client indicating the pipeline update event along with pipeline identity, model information, list of all nodes added into the pipeline, notification target where the result of the slit operation is to be sent, and the like.

Fig. 1 is a block diagram that illustrates a schematic of an AIML enablement client (102) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. The AIML enablement client (102) is part of a user equipment (UE). Examples of the UE can include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.).

In an embodiment, in Fig. 1, the AIML enablement client (102) includes a first processor (104), a first memory (106), a first I/O interface (108), and a split operation pipeline controller (110) coupled to the first processor (104) and the first memory (106). The components are explained in further detail below.

The first processor (104) communicates with the first memory (106), the first I/O interface (108), and the split operation pipeline controller (110). The first processor (104) is configured to execute instructions stored in the first memory (106) and to perform various processes. The first processor (104) includes one or a plurality of processors, is a general-purpose processor such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an Artificial Intelligence (AI) dedicated processor such as a neural processing unit (NPU).

The first memory (106) includes storage locations to be addressable through the first processor (104). The first memory (106) is not limited to a volatile memory and/or a non-volatile memory. Further, the first memory (106) includes a plurality of computer-readable storage media. The first memory (106) includes non-volatile storage elements. For example, non-volatile storage elements includes magnetic hard disks, optical disks, floppy disks, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

The first I/O interface (108) transmits the information between the first memory (106) and external peripheral devices. The peripheral devices are the input-output devices associated with the AIML enablement client (102). Further, the split operation pipeline controller (110) communicates with the first I/O interface (108) and the first memory (106). The split operation pipeline controller (110) is coupled to the first memory (106) and the first processor (104). The split operation pipeline controller (110) is an innovative hardware that are realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

In an embodiment, the split operation pipeline controller (110) generates a split operation event subscribe request to subscribe for split operation related events. The split operation event subscribe request message includes a requestor identity of a requestor associated with the AIML enablement client (102), security credentials of the requestor associated with the AIML enablement client (102), and a list of pipeline events. For instance, the list of pipeline events include a creation of a new pipeline, an update of the existing pipeline, and a deletion of the existing pipeline. Updating the existing pipeline includes adding of a new node to the existing pipeline, a removal of an existing node from the existing pipeline, a change in a stage order, a change in a model information, and the like. The split operation pipeline controller (110) then transmits the split operation event subscribe request to a network apparatus including an AIML enablement server.

In an embodiment, the split operation pipeline controller (110) receives a split operation event subscribe response message from the network apparatus. This indicates either a success or a failure of subscription for the split operation related events. The response message includes a subscription identifier in case of success in subscription of the split operation related events. Else, the response message includes a failure cause in case of failure in subscription of the split operation related events.

Fig. 2 is a block diagram that illustrates a schematic of the network apparatus (202) implemented to carry out the disclosed subject matter according to an embodiment as disclosed herein. As shown, the network apparatus (202) includes a second processor (204), a second memory (206), a second I/O interface (208), and a network split operation pipeline controller (210).

The network apparatus (202) includes various hardware and software components that facilitate communication between user equipment and network infrastructure. Examples of the network apparatus (202) can include, but is not limited to an AIML enablement server (212), Base Stations (such as macro cells, small cells, femtocells, picocells, etc.) for wireless communication, Antennas and RF Units (e.g., MIMO, beamforming) to enhance signal coverage and data throughput, Core Network Equipment (e.g., MMEs, S-GWs, P-GWs in 4G; AMFs, SMFs, UPFs in 5G) for data routing, mobility, and session control, Network Function Virtualization (NFV) and Software-Defined Networking (SDN) for dynamic resource allocation and scalability, Edge Computing Nodes (e.g., MEC servers) for low-latency processing, Backhaul and Transport Equipment (e.g., fiber-optic links, microwave relays, Ethernet switches) to connect base stations to the core network, Network Management Systems (NMS) and Operation Support Systems (OSS) for network configuration, fault management, and optimization, Radio Network Controllers (RNCs) in 3G, Distributed Units (DUs), and Centralized Units (CUs) in 5G, Network Slicing Components for virtualized resource allocation, Security elements (e.g., Firewalls, IDS, AAA Servers) for secure communication.

The network split operation pipeline controller (210) is coupled to the second memory (206) and the second processor (204). The network split operation pipeline controller (210) is an innovative hardware that are realized through the physical implementation of both analog and digital circuits, including logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive and active electronic components, as well as optical components.

In an embodiment, the network split operation pipeline controller (210) receives a split operation event subscribe request message from a requestor associated with the AIML enablement client (102) in the UE. The split operation event subscribe request message includes information such as an identifier of the requestor, security credentials of the requestor, a list of pipeline events (for example, created, modified, removed, etc.), a pipeline identifier, and the like. The pipeline identifier indicates the specific pipeline related events that the requestor is looking to subscribe for.

In an embodiment, the network split operation pipeline controller (210) determines whether the requestor is authorized to subscribe for split operation related events upon receiving the split operation event subscribe request message. This determination is essential to ensure that only authorized entities or persons are granted access to information regarding the split operations. The authorization can be determined by analyzing the credentials and permissions of the requestor. This involves verifying the requestor's identity, role, and any other attributes that define their access level within the communication network system.

In an embodiment, the network split operation pipeline controller (210) creates a subscription for the split operation related events upon successful authorization of the requestor. This subscription allows the network split operation pipeline controller (210) to send real-time notifications and updates about various events that occur during the split operations. These events can include the initiation of the split, progress updates, completion notifications, and any errors or issues that arise.

In an embodiment, the network split operation pipeline controller (210) generates a split operation event subscribe response message that indicates either a success or a failure of the subscription created for the split operation related events. The split operation event subscribe response message includes a subscription identifier in case of success in the subscription of the split operation related events. Further, the split operation event subscribe message includes a failure cause in case of failure in the subscription of the split operation related events. The network split operation pipeline controller (210) then transmits the split operation event subscribe response message to the AIML enablement client (102).

In an embodiment, the network split operation pipeline controller (210) detects whether at least one of a new split operation profile is created, an existing pipeline is updated, and an existing pipeline is deleted. The network split operation pipeline controller (210) then generates a split operation notification message upon detection of at least one of creation of the new split operation pipeline, an update of the existing pipeline, and a deletion of the existing pipeline. For instance, the split operation notification message includes a pipeline event, information about a planned usage of the new split operation pipeline or the existing pipeline, an identifier of the new split operation pipeline or the existing pipeline, a pipeline head endpoint of the new split operation pipeline or the existing pipeline, a pipeline tail endpoint of the new split operation pipeline or the existing pipeline, and the like.

The pipeline event indicates the nature of the event (creation, update, or deletion) and provides context for the changes being communicated. The planned usage outlines the purpose of the new or existing pipeline, helping users understand its role within the communication network system. Each split operation pipeline is assigned a unique identifier, which is included in the notification message. This identifier is important for tracking and referencing the split operation pipelines in future split operations. The pipeline head endpoint is the starting point for data flow. The pipeline head endpoint information is essential for understanding how data enters the split operation pipeline. Further, the pipeline tail endpoint refers to the endpoint where data exits the split operation pipeline.

Fig. 3 is a sequence diagram that illustrates a split operation pipeline subscribe-notify method according to an embodiment as disclosed herein. As shown in the sequence diagram, the AIML enablement client (102) is in communication with the AIML enablement server (212) part of the network apparatus (202). Each step is explained in further detail below.

At step 1, the AIML enablement client (102) sends a request message to subscribe to split operation related events to the AIML enablement server (212). The request includes requestor identifier, security credentials, events for which the requestor is subscribing, pipeline identifier. The parameters as shown in Table 1 are included in the request.

At step 2, upon receiving the request, the AIML enablement server (212) validates if the requestor is authorized to subscribe for split operation events. If the requestor is authorized, the AIML enablement server (212) creates the subscription.

At step 3, the AIML enablement server (212) sends subscription response message to the AIML enablement client (102) indicating success or failure of the request. In case of success, the response includes the subscription identifier. In case of failure, the response includes the failure cause. The parameters as shown in the Table 2 are included in the response.

At step 4, the AIML enablement server (212) detects the event, that is, the AIML enablement client (102) is either added to the pipeline or removed from the pipeline or the pipeline is modified or removed. At step 5, the AIML enablement server (212) sends a split operation notification message to the AIML enablement client (102) indicating the event. The notification includes pipeline identifier. The notification includes AIML split operation profile if the new pipeline is created or existing pipeline is modified. The parameters as shown in Table 3 are included in the notification message.

In an embodiment, the procedure can also be initiated by Application Data Analytics Enablement (ADAE) client, any Service Enabler Architecture Layer (SEAL) client, Edge Enabler Client (EEC), or any other client.

In an embodiment, the procedure can also be performed by ADAE server, any SEAL server, EES or any other server.

In an embodiment, the procedure can also be performed by SEAL group management server with list of ordered members as group property.

In an embodiment, the AIML controller performs AIML split operation capability to an AIML enablement layer.

Fig. 4 is a flow diagram that illustrate a method for providing split operation pipeline details in a communication network system by the AIML enablement client (102) according to an embodiment as disclosed herein. The method includes steps (402-406). Each step is explained in further detail below.

At step (402), the AIML enablement client (102) generates a split operation event subscribe request to subscribe for split operation related events. The split operation event subscribe request message includes a requestor identity of a requestor associated with the AIML enablement client (102), security credentials of the requestor associated with the AIML enablement client (102), and a list of pipeline events. For instance, the list of pipeline events include a creation of a new pipeline, an update of the existing pipeline, and a deletion of the existing pipeline. Updating the existing pipeline includes adding of a new node to the existing pipeline, a removal of an existing node from the existing pipeline, a change in a stage order, a change in a model information, and the like.

At step (404), the AIML enablement client (102) then transmits the split operation event subscribe request to the network apparatus (202) including the AIML enablement server (212).

At step (406), the AIML enablement client (102) receives a split operation event subscribe response message from the network apparatus (202). This indicates either a success or a failure of subscription for the split operation related events. The split operation event subscribe response message includes a subscription identifier in case of success in subscription of the split operation related events. Further, the split operation event subscribe response message includes a failure cause in case of failure in subscription of the split operation related events.

At step (408), the AIML enablement client (102) receives a split operation notification message from the network apparatus (202). The split operation notification message is received upon detection of creation of a new split operation profile, an update of an existing pipeline, and a delete of an existing pipeline.

Fig. 5 is a flow diagram that illustrate a method for providing split operation pipeline details in a communication network system by the network apparatus (202) according to an embodiment as disclosed herein. The method includes steps (502-516). Each step is explained in further detail below.

At step (502), the network apparatus (202) receives a split operation event subscribe request message from a requestor associated with the AIML enablement client (102) in the UE. The split operation event subscribe request message includes information such as an identifier of the requestor, security credentials of the requestor, a list of pipeline events (for example, created, modified, removed, etc.), a pipeline identifier, and the like. The pipeline identifier indicates the specific pipeline related events that the requestor is looking to subscribe for.

At step (504), the network apparatus (202) determines whether the requestor is authorized to subscribe for split operation related events upon receiving the split operation event subscribe request message. It is essential to establish this determination to guarantee that access to information concerning the split operations is restricted to authorized individuals or entities only. The authorization process involves evaluating the credentials and permissions of the requester. This includes confirming the requester's identity, role, and any other factors that set their access rights within the communication network system.

At step (506), the network apparatus (202) creates a subscription for the split operation related events upon successful authorization of the requestor. This subscription allows the network split operation pipeline controller (210) to send real-time notifications and updates about various events that occur during the split operations. These events can include the initiation of the split, progress updates, completion notifications, and any errors or issues that arise.

At step (508), the network apparatus (202) generates a split operation event subscribe response message that indicates either a success or a failure of the subscription created for the split operation related events. The split operation event subscribe response message includes a subscription identifier in case of success in the subscription of the split operation related events. Further, the split operation event subscribe message includes a failure cause in case of failure in the subscription of the split operation related events. At step (510), the network apparatus (202) then transmits the split operation event subscribe response message to the AIML enablement client (102).

At step (512), the network apparatus (202) detects whether at least one of a new split operation profile is created, an existing pipeline is updated, and an existing pipeline is deleted. At step (514), the network apparatus (202) then generates a split operation notification message upon detection of at least one of creation of the new split operation pipeline, an update of the existing pipeline, and a deletion of the existing pipeline. For instance, the split operation notification message includes a pipeline event, information about a planned usage of the new split operation pipeline or the existing pipeline, an identifier of the new split operation pipeline or the existing pipeline, a pipeline head endpoint of the new split operation pipeline or the existing pipeline, a pipeline tail endpoint of the new split operation pipeline or the existing pipeline, and the like.

At step (516), the network apparatus (202) transmits the split operation notification message to the AIML enablement client (102).

As shown in Fig. 6, the base station according to an embodiment may include a transceiver 610, a memory 620, and a processor (or a controller) 630. The transceiver 610, the memory 620, and the processor 630 (or the controller) of the base station may operate according to a communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 630, the transceiver 610, and the memory 620 may be implemented as a single chip. Also, the processor 630 may include at least one processor.

The transceiver 610 collectively refers to a base station receiver and a base station transmitter, and may transmit/receive a signal to/from a terminal. The signal transmitted or received to or from the terminal may include control information and data. The transceiver 610 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 610 and components of the transceiver 610 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 610 may receive and output, to the processor 630, a signal through a wireless channel, and transmit a signal output from the processor 630 through the wireless channel.

The memory 620 may store a program and data required for operations of the base station. Also, the memory 620 may store control information or data included in a signal obtained by the base station. The memory 620 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 630 may control a series of processes such that the base station operates as described above. For example, the transceiver 610 may receive a data signal and/or a control signal transmitted by the terminal, and the processor 630 may determine a result of receiving the signal transmitted by the terminal and/or the core network function.

As shown in Fig. 7, the terminal of the present disclosure may include a transceiver 710, a memory 720, and a processor (or a controller) 730. The transceiver 710, the memory 720, and the processor (or the controller) 730 of the terminal may operate according to a communication method of the terminal described above. However, the components of the terminal are not limited thereto. For example, the terminal may include more or fewer components than those described above. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented as a single chip. Also, the processor 730 may include at least one processor.

The transceiver 710 collectively refers to a terminal receiver and a terminal transmitter, and may transmit/receive a signal to/from a base station. The signal transmitted or received to or from the base station may include control information and data. In this regard, the transceiver 710 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 710 and components of the transceiver 710 are not limited to the RF transmitter and the RF receiver.

Also, the transceiver 710 may receive and output, to the processor 730, a signal through a wireless channel, and transmit a signal output from the processor 730 through the wireless channel.

The memory 720 may store a program and data required for operations of the terminal. Also, the memory 720 may store control information or data included in a signal obtained by the terminal. The memory 720 may be a storage medium, such as ROM, RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 730 may control a series of processes such that the terminal operates as described above. For example, the transceiver 710 may receive a data signal and/or a control signal, and the processor 730 may determine a result of receiving the signal transmitted by the base station and/or the other terminal.

In an aspect, the objectives are achieved by providing a method for providing split operation pipeline details in a communication network system. The method includes generating a split operation event subscribe request to subscribe for split operation related events. Further, the method includes transmitting the split operation event subscribe request to a network apparatus including an AIML enablement server. Further, the method includes receiving a split operation event subscribe response message from the network apparatus that indicates either a success or a failure of subscription for the split operation related events. The response message includes either a subscription identifier in case of success in subscription of the split operation related events or a failure cause in case of failure in subscription of the split operation related events.

In another aspect, the objectives are achieved by providing a method for providing split operation pipeline details in a communication network system. The method includes receiving a split operation event subscribe request message from a requestor associated with an AIML enablement client in a UE. Further, the method includes determining whether the requestor is authorized to subscribe for split operation related events upon receiving the split operation event subscribe request message. Further, the method includes creating a subscription for the split operation related events upon successful authorization of the requestor. Further, the method includes generating a split operation event subscribe response message that indicates either a success or a failure of the subscription created for the split operation related events. The split operation event subscribe response message includes either a subscription identifier in case of success in the subscription of the split operation related events or a failure cause in case of failure in the subscription of the split operation related events. Further, the method includes transmitting the split operation event subscribe response message to the AIML enablement client.

In another aspect, the objectives are achieved by providing an AIML enablement client for providing split operation pipeline details in a communication network system. The AIML enablement client includes a first processor, a first memory coupled to the first processor, and a split operation pipeline controller coupled to the first memory and the first processor. The split operation pipeline controller generates a split operation event subscribe request to subscribe for split operation related events. Further, the split operation pipeline controller transmits the split operation event subscribe request to a network apparatus including an AIML enablement server. Further, the split operation pipeline controller receives a split operation event subscribe response message from the network apparatus that indicates either a success or a failure of subscription for the split operation related events. The response message includes either a subscription identifier in case of success in subscription of the split operation related events or a failure cause in case of failure in subscription of the split operation related events.

In another aspect, the objectives are achieved by providing a network apparatus for providing split operation pipeline details in a communication network system. The network apparatus includes a second processor, a second memory coupled to the second processor, and a network split operation pipeline controller coupled to the second memory and the second processor. The network split operation pipeline controller receives a split operation event subscribe request message from a requestor associated with an AIML enablement client in a UE. Further, the network split operation pipeline controller determines whether the requestor is authorized to subscribe for split operation related events upon receiving the split operation event subscribe request message. Further, the network split operation pipeline controller creates a subscription for the split operation related events upon successful authorization of the requestor. Further, the network split operation pipeline controller generates a split operation event subscribe response message that indicates either a success or a failure of the subscription created for the split operation related events. The split operation event subscribe response message includes either a subscription identifier in case of success in the subscription of the split operation related events or a failure cause in case of failure in the subscription of the split operation related events. Further, the network split operation pipeline controller transmits the split operation event subscribe response message to the AIML enablement client.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications be made within the scope of the embodiments herein.

The methods according to the embodiments described in the claims or the detailed description of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

The programs (e.g., software modules or software) may be stored in random access memory (RAM), non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), a magnetic disc storage device, compact disc-ROM (CD-ROM), a digital versatile disc (DVD), another type of optical storage device, or a magnetic cassette. Alternatively, the programs may be stored in a memory system including a combination of some or all of the above-mentioned memory devices. In addition, each memory device may be included by a plural number.

The programs may also be stored in an attachable storage device which is accessible through a communication network such as the Internet, an intranet, a local area network (LAN), a wireless LAN (WLAN), or a storage area network (SAN), or a combination thereof. The storage device may be connected through an external port to an apparatus according the embodiments of the present disclosure. Another storage device on the communication network may also be connected to the apparatus performing the embodiments of the present disclosure.

Those skilled in the art will understand that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. Furthermore, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that aspects of the invention of the disclosure as generally described herein and shown in the drawings may be arranged, replaced, combined, separated and designed in various different configurations, all of which are contemplated herein.

Those skilled in the art will understand that the various illustrative logical blocks, modules, circuits, and steps described in this application may be implemented as hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in the form of their functional sets. Whether such function sets are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Technicians may implement the described functional sets in different ways for each specific application, but such design decisions should not be interpreted as causing a departure from the scope of this application.

The various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logics, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

When the electrical structures and methods are implemented in software, a computer-readable recording medium having one or more programs (software modules) recorded thereon may be provided. The one or more programs recorded on the computer-readable recording medium are configured to be executable by one or more processors in an electronic device. The one or more programs include instructions to execute the methods according to the embodiments described in the claims or the detailed description of the present disclosure.

In the afore-described embodiments of the present disclosure, elements included in the present disclosure are expressed in a singular or plural form according to the embodiments. However, the singular or plural form is appropriately selected for convenience of explanation and the present disclosure is not limited thereto. As such, an element expressed in a plural form may also be configured as a single element, and an element expressed in a singular form may also be configured as plural elements.

The above flowcharts illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

A method of a network apparatus for a split operation in a communication network system, comprising:

receiving, from a user equipment (UE), a split operation subscribe request message including information on a requestor identifier, a security credential, and an event,

validating whether the UE is authorized for the request,

generating a subscription for the split operation in case that the UE is authorized, and

transmitting, to the UE, a split operation subscribe response message that indicates the success of the subscription and includes a subscription identity.
The method of claim 1, wherein the split operation subscribe response message indicates a failure of the subscription and includes a reason for the failure, in case that the subscription is not generated.
The method of claim 1, further comprising:

detecting an event related to the split operation, and

transmitting, to the UE, a split operation notification message indicating the event,

wherein the event includes at least one of: creation of a new split profile, an update of an existing pipeline and a deletion of an existing pipeline.
The method of claim 3,

wherein the split operation notification message includes a split operation profile, and

wherein the split operation notification message includes information on at least one of: a split operation identifier, a head endpoint, a tail endpoint, or usage information of the split operation.
A method of a user equipment (UE) for a split operation in a communication network system, comprising:

transmitting, to a network apparatus, a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, and

receiving, from the network apparatus, a split operation subscribe response message indicating a success or failure of the subscription.
The method of claim 5, wherein the split operation subscribe response message indicates a failure of the subscription and includes a reason for the failure, in case that the subscription is not generated.
The method of claim 5, further comprising:

receiving, from the network apparatus, a split operation notification message indicating the event,

wherein the event includes at least one of: creation of a new split profile, an update of an existing pipeline, or a deletion of an existing pipeline.
The method of claim 7,

wherein the split operation notification message includes a split operation profile, and

wherein the split operation notification message includes information on at least one of: a split operation identifier, a head endpoint, a tail endpoint, or usage information of the split operation.
A network apparatus for a split operation in a communication network system, comprising:

a transceiver; and

a controller coupled to the transceiver, the controller is configured to:

receive, from a user equipment (UE), a split operation subscribe request message including information on a requestor identifier, a security credential, and an event,

validate whether the UE is authorized for the request,

generate a subscription for the split operation in case that the UE is authorized, and

transmit, to the UE, a split operation subscribe response message that indicates the success of the subscription and includes a subscription identity.
The network apparatus of claim 9, wherein the split operation subscribe response message indicates a failure of the subscription and includes a reason for the failure, in case that the subscription is not generated.
The network apparatus of claim 9, wherein the controller is further configured to:

detect an event related to the split operation, and

transmit, to the UE, a split operation notification message indicating the event,

wherein the event includes at least one of: creation of a new split profile, an update of an existing pipeline and a deletion of an existing pipeline.
The network apparatus of claim 11,

wherein the split operation notification message includes a split operation profile, and

wherein the split operation notification message includes information on at least one of: a split operation identifier, a head endpoint, a tail endpoint, or usage information of the split operation.
A user equipment (UE) for a split operation in a communication network system, comprising:

a transceiver; and

a controller coupled to the transceiver, the controller is configured to:

transmit, to a network apparatus, a split operation subscribe request message including information on a requestor identifier, a security credential, and an event, and

receive, from the network apparatus, a split operation subscribe response message indicating a success or failure of the subscription.
The UE of claim 13, wherein the split operation subscribe response message indicates a failure of the subscription and includes a reason for the failure, in case that the subscription is not generated.
The UE of claim 13, wherein the controller is further configured to:

receive, from the network apparatus, a split operation notification message indicating the event,

wherein the event includes at least one of: creation of a new split profile, an update of an existing pipeline, or a deletion of an existing pipeline,

wherein the split operation notification message includes a split operation profile, and

wherein the split operation notification message includes information on at least one of: a split operation identifier, a head endpoint, a tail endpoint, or usage information of the split operation.