Coordination of multiple traffic nodes

Abstract

A control plane (CP) entity manages and coordinates multiple traffic nodes for multiple types of traffic. The services include communication services, computing services, intelligent services, storage services and / or security services. The CP entity configures extended user plane (UP) functions that support multiple traffic, and initiates execution of these functions based on the configuration. The UP entity reports capabilities of a plurality of traffic within the UP entity and receives a configuration of the supported plurality of traffic. The UP function is initiated and executed based on the UP configuration received from the CP entity.

Description

Technical Field

[0001] This document generally relates to wireless communication. More specifically, a User Plane (UP) entity supports multiple configured services. Background Art

[0002] Wireless communication technologies are driving the world towards an increasingly interconnected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and radio access network nodes (including but not limited to Radio Access Network (RAN) nodes and radio base stations). The new generation of networks is expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet the needs of different industries and users. User mobile stations or User Equipment (UE) are becoming increasingly complex, and the amount of communication data is constantly increasing. With the development of more advanced radar and sensing systems, communication with UEs can be more modernized. Summary of the Invention

[0003] This document relates to methods, systems, and devices for a Control Plane (CP) entity to manage and coordinate multiple service nodes for multiple types of services. The services include at least communication services, computing services, intelligent services, storage services, and / or security services. The CP entity configures extended User Plane (UP) functions to support multiple services and initiates the execution of these functions based on this configuration. The UP entity reports the capabilities of multiple services within the UP entity and receives the configuration of the multiple supported services. The UP functions are initiated and executed based on the UP configuration received from the CP entity.

[0004] In one embodiment, a method for wireless communication includes: configuring an extended UP function that supports multiple services; and initiating the execution of the UP function to a UP entity based on the configuration. The UP function includes functions of identifying service types, UP task identifiers, and executing multiple services based on UP configurations. The multiple services include at least two of communication services, computing services, intelligent services, storage services, and / or security services. The configuration and transmission of the UP configuration are performed by a network entity including a CP entity. The UP configuration is received by the UP entity from the CP entity. The configuration is performed through internal signaling or through interface-based signaling. The configuration includes the UP configuration for multiple services for one or more UP entities. The method includes synchronizing and coordinating the multiple services among multiple UP entities. The method includes assigning task identifiers for synchronizing and coordinating the multiple services among the multiple UP entities. The multiple UP entities are configured to interact service data of different service types through different data transmission tunnels among the multiple UP entities. The UP entity reports and updates the status or result of task execution to the CP entity through internal signaling or through an interface-based signaling process.

[0005] In another embodiment, a method for wireless communication includes: reporting the capabilities of multiple services within a UP entity; and receiving a UP configuration for the multiple services supported. The UP function includes functions of identifying service types, UP task identifiers, and executing the multiple services based on the UP configuration. The multiple services include at least two of communication services, computing services, intelligent services, storage services, and / or security services. The reporting of the capabilities and the receiving of the UP configuration are performed by a network entity including one or more UP entities. The UP configuration is from a CP entity, where the UP configuration is received by the one or more UP entities from the CP entity. The UP configuration is implemented through internal signaling or through interface-based signaling. The UP configuration includes a separate UP configuration for each service to be configured for one or more UP entities. The UP configuration includes the synchronization and coordination of multiple services among one or more UP entities. The UP configuration includes task identifiers for the synchronization and coordination of multiple services among one or more UP entities. The one or more UP entities are configured to interact service data of different service types through different data transmission tunnels among the one or more UP entities. The UP entity reports and updates the status or result of task execution to the CP entity through internal signaling or through an interface-based signaling process.

[0006] In another embodiment, a wireless communication device includes a processor and a memory, where the processor is configured to read code from the memory and implement any of the methods described herein.

[0007] In another embodiment, a computer program product includes computer-readable program code stored thereon, and the computer-readable program code, when executed by a processor, causes the processor to implement any of the methods described herein.

[0008] In some embodiments, a wireless communication device includes a processor and a memory. The processor is configured to read code from the memory and implement any of the methods in any of the embodiments. In some embodiments, a computer program product includes computer-readable program medium code stored therein, and when executed by a processor, the computer-readable program medium code causes the processor to implement any of the methods in any of the embodiments. The above and other aspects and their implementations are described in more detail in the drawings, the description, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example base station is shown.

[0010] Figure 2 An example random access (RA) message interaction environment is shown.

[0011] Figure 3 A single-connection wireless communication system is shown.

[0012] Figure 4 A split single-connection wireless communication system is shown.

[0013] Figure 5 An embodiment of a wireless network system architecture is shown.

[0014] Figure 6 UP processing and data forwarding are shown.

[0015] Figure 7 A single base station system diagram with an extended UP function supporting multiple services is shown.

[0016] Figure 8 A dual base station system diagram with an extended UP function supporting multiple services is shown. DETAILED DESCRIPTION

[0017] The technical content related to the present disclosure will be described in detail below with reference to the accompanying drawings, which are a part of the present disclosure and exemplarily show some specific examples in the embodiments. Please note that the present disclosure may be embodied in multiple forms, and thus the subject matter covered or claimed is intended to be understood as not limited to any specific embodiment described below.

[0018] Throughout the specification and claims, unless the meaning is clearly stated otherwise, terms may have nuanced meanings that are implied or implicit in the context. Similarly, phrases such as "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and phrases such as "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. Phrases such as "in one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, and phrases such as "in another implementation" or "in other implementations" as used herein do not necessarily refer to different implementations. For example, it is intended to indicate that the claimed subject matter includes example embodiments or implementations, either in whole or in part, in combination.

[0019] Generally, terms can be understood at least from their use in context. For example, terms such as "and", "or", "and / or" as used herein may have various meanings that depend at least in part on the context in which these terms are used. Generally, "or" when associated with a list, such as A, B, or C, is intended to mean A, B, and C, used here in the inclusive sense, as well as A, B, or C, used here in the exclusive sense. Additionally, terms such as "one or more" or "at least one" as used herein may, at least in part, depend on the context, be used to describe any feature, structure, or characteristic in the singular sense, or may be used to describe a combination of features, structures, or characteristics in the plural sense. Similarly, terms such as "a", "an", or "the" may convey singular or plural usage depending on the context. Further, terms such as "based on" or "determined by" may be understood to not necessarily imply the conveyance of an exclusive set of factors, but may instead allow for the presence of additional factors that are not necessarily explicitly described, and how this is understood depends at least in part on the context.

[0020] Radio Resource Control (RRC) is a protocol layer at the IP level (radio network layer) between the UE and the base station. There can be various RRC states, such as RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states. RRC messages are transmitted via the Packet Data Convergence Protocol (PDCP). The UE can send infrequent (periodic and / or aperiodic) data in the RRC_INACTIVE state without switching to the RRC_CONNECTED state. This can save the power consumption and signaling overhead of the User Equipment (UE). This can be achieved through the Random Access Channel (RACH) protocol scheme or the Configured Grant (CG) scheme. The wireless communication described here may be via wireless access. Figure 1 and Figure 2 illustrates an example Radio Access Network (RAN) node (e.g., a base station) and user equipment and a message environment, which may be applicable to the UP functions and communications described below.

[0021] With the latest developments in wireless communication systems (e.g., Fifth Generation - New Radio (5G - NR) and Sixth Generation (6G) wireless systems) and the development of various distributed computing, intelligence, storage, and security systems, integration can be a challenge. The integration between each other may be in terms of architecture or capabilities, or in terms of network and air interface resource usage, etc. 5G - Advanced (5G - A) and 6G wireless systems may attempt to integrate various new functions and services with legacy systems, including but not limited to computing services, intelligence services, storage services, and / or security systems. Therefore, the Core Network (CN) and RAN nodes may not only provide wireless communication services, but also provide computing services, intelligence services, storage services, and / or security services, etc.

[0022] The user plane (UP) function in a single-service wireless communication node may be only for processing, transmitting, and / or forwarding user data related to different user mobile services, such as mobile applications and web services. Such a single service may be referred to as a communication service. The corresponding control plane (CP) entity may provide UP settings and configurations to the UP entity. The UP entity follows the rules and configurations indicated by the CP entity. The UP entity may have multiple service capabilities and be able to handle additional UP functions described below. Example services include communication services, computing services, intelligent services, storage services, and / or security services. These services may be associated with different functions and services. As described below, the CP entity can coordinate multiple service nodes for these multiple service types.

[0023] Figure 1 An example radio access network (RAN) node or base station 102 is shown. The RAN node may also be referred to as a wireless network node. In the field of mobile communication, the RAN node 102 may further be referred to as a Node B (NB, e.g., an evolved Node B (eNB) or a Next Generation Node B (gNB)). This example RAN node may include wireless transceiver (Tx / Rx) circuitry 113 for receiving and transmitting signals to and from the UE 104. The RAN node may also include network interface circuitry 116 for connecting the RAN node to the core network 110, e.g., via fiber optic or wired interconnection, Ethernet, and / or other data transmission media / protocols.

[0024] The RAN node may also include system circuitry 122. The system circuitry 122 may include one or more processors 124 and / or a memory 126. The memory 126 may contain operations 128 and control parameters 130. The operations 128 may contain instructions to be executed on one or more processors 124 to support the functions of the RAN node. For example, these operations may process random access transmission requests from multiple UEs. The control parameters 130 may contain parameters or support the execution of the operations 128. For example, the control parameters may contain network protocol settings, random access message format rules, bandwidth parameters, radio frequency mapping assignments, and other such parameters.

[0025] Figure 2An example random access message interaction environment 200 is shown. In this random access message interaction environment, the UE 104 can communicate with the RAN node 102 via the random access channel 252. In this example, the UE 104 supports one or more Subscriber Identity Modules (SIMs), such as SIM1 202. The electrical and physical interface 206 connects SIM1 202 to other parts of the user equipment hardware, e.g., via the system bus 210.

[0026] The mobile device 200 includes a communication interface 212, system logic 214, and a user interface 218. The system logic 214 may include any combination of hardware, software, firmware, or other logic. The system logic 214 can be implemented, for example, by one or more System on a Chip (SoC), Application Specific Integrated Circuit (ASIC), discrete analog and digital circuits, and other circuits. The system logic 214 is a component that implements the required functions in the UE 104. In this regard, the system logic 214 may include logic that helps to decode and play music and videos, e.g., the decoding and playing of MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; run applications; accept user input; save and retrieve application data; establish, maintain, and terminate a phone or data connection, e.g., an Internet connection; establish, maintain, and terminate a wireless network connection, a Bluetooth connection, or other connections; and display relevant information on the user interface 218. The user interface 218 and input 228 may include a graphical user interface, a touch screen, haptic feedback or other haptic output, voice or face recognition input, buttons, switches, speakers, and other user interface elements. Other examples of the input 228 include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., infrared (IR) sensors), and other types of input.

[0027] System logic 214 may include one or more processors 216 and a memory 220. The memory 220 stores, for example, control instructions 222, and the processor 216 executes these instructions to implement the functions required by the UE 104. Control parameters 224 provide and specify the configuration and operation options of the control instructions 222. The memory 220 may also store any Bluetooth, WiFi, 3G, 4G, 5G, or other data 226 that the UE 104 will send or has received via the communication interface 212. In various implementations, the system power may be provided by a power storage device, such as a battery 282.

[0028] In the communication interface 212, radio frequency (RF) transmit (Tx) and receive (Rx) circuits 230 process the transmission and reception of signals via one or more antennas 232. The communication interface 212 may include one or more transceivers. These transceivers may be wireless transceivers that include modulation / demodulation circuits, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas, or (for some devices) for transmission and reception via a physical (e.g., wired) medium.

[0029] The signals transmitted and received may follow various formats, protocols, modulation schemes (e.g., Quadrature Phase Shift Keying (QPSK), 16-State Quadrature Amplitude Modulation (16-QAM), 64-State Quadrature Amplitude Modulation (64-QAM), or 256-State Quadrature Amplitude Modulation (256-QAM)), channels, bit rates, and coding. As a specific example, the communication interface 212 may include a transceiver that supports transmission and reception under Second Generation (2G), Third Generation (3G), Bluetooth (BT), Wireless Fidelity (WiFi), Universal Mobile Telecommunications System (UMTS), High Speed Packet Access+ (HSPA+), and Fourth Generation (4G) / Long Term Evolution (LTE) standards. However, the techniques described below are applicable to other wireless communication technologies, whether from the 3rd Generation Partnership Project (3GPP), Global System for Mobile Communications Association (GSM Association), 3GPP2, Institute of Electrical and Electronics Engineers (IEEE), or other partners or standards organizations.

[0030] Figure 3A single-connectivity wireless communication system is shown. Single connectivity (SC) may include a UE that has only one Master Radio Link (M-RL), but no radio link on the secondary RAN node side. In contrast, dual connectivity (DC) includes a UE that has a Secondary communication Radio Link (S-RL) on the secondary RAN node side. In an International Mobile Telecommunications (IMT) wireless communication system (such as 4G-LTE and 5G-NR) as shown in Figure 3 RAN nodes may transmit downlink (DL) pilot reference signals such as Synchronization Signal Block (SSB), Channel State Information-Reference Signal (CSI-RS), etc. The UE receives, measures, and processes these signals so that the UE can understand the air connection quality of the Radio Link (RL). This may be communication between the serving RAN node and the UE to maintain the continuity of communication services. This is an example of single connectivity (SC).

[0031] Figure 4 A split single-connectivity wireless communication system is shown. Figure 3 A non-split single-connectivity wireless communication system is shown, while Figure 4 shows the case where the CU-CP node and the CU-UP node are separated. In an IMT wireless communication system (such as 5G-NR specified by 3GPP), as shown in Figure 3 and Figure 4 the core network (CN) may include various types of CP nodes or entities (such as 5G Access and Mobility Management Function (AMF) / Session Management Function (SMF)), and UP nodes or entities (such as 5G User Plane Function (UPF)). In the case of non-split RAN in Figure 3 the RAN node (such as a 5G aggregated base station) includes a CP part and a UP part, and then terminates on the UE through the radio link (RL) in the air. In Figure 4In the case of RAN separation, the RAN node (e.g., a 5G split base station) includes a CU-CP node, a CU-UP node, and a DU node or entity, and then the RL over the air terminates at the UE. The CP part or node may be responsible for generating, processing, and transmitting control signaling (e.g., for (re)configuring and monitoring other nodes). The UP part or node is responsible for processing and transmitting user data (e.g., data related to mobile applications and web services, etc.). For the CP plane and the UP plane, there may be separate interfaces and protocol stacks, usually extending from the CN domain to the RAN network and then to the UE. Further description of the UP function is provided below and can be implemented in Figure 1 and Figure 2 the system shown in Figure 5 or in the system described below.

[0032] Figure 5 Embodiments of the wireless network system architecture are shown. This architecture is only an example and may include more or fewer components to implement the embodiments described herein. The interconnection or communication between components is identified as N1, N2, N4, N6, N7, N8, N10, and N11, which may be referenced in the description or other figures. Figure 2 An example of a UE 104 is shown. The UE 502 is a device that accesses a wireless network (e.g., 5GS) and obtains services through a new generation of radio access network nodes or base stations 504. The UE 502 interacts with the Access and Mobility Control Function (AMF) 506 in the core network through Non-Access Stratum signaling (NAS signaling). Figure 1 An example of a base station or a Next Generation Radio Access Network (NG-RAN) 102 is shown. The NG-RAN node 504 is responsible for the scheduling of air interface resources and the management of air interface connections for the network accessed by the UE. The AMF 506 includes the following functions: registration management, connection management, reachability management, and mobility management. The AMF 506 also performs access authentication and access authorization. The AMF 506 is a NAS security endpoint and relays session management NAS between the UE 502 and the Session Management Function (SMF) 508, etc.

[0033] The SMF 508 includes the following functions: session management, such as session establishment, modification, and release, UE IP address allocation and management (including optional Authorization), selection and control of uplink functions, downlink data notification, etc. The User Plane Function (UPF) 510 includes the following functions: mobility anchor point between the same radio access technology (RAT) / RATs, packet routing and forwarding, traffic usage reporting, quality of service (QoS) handling of the user plane, downlink packet buffering, and triggering of downlink data notification, etc. The Unified Data Management (UDM) 512 manages the subscription profiles of UEs. The subscription includes data for mobility management (such as restricted areas) and session management (such as QoS profiles). The subscription data also includes slice selection parameters, which are used by the AMF 506 to select an appropriate SMF 508. The AMF 506 and the SMF 508 obtain the subscription data from the UDM 512. The subscription data may be stored in the Unified Data Repository of the UDM 512, and this unified data repository uses this data when receiving requests from the AMF 506 or the SMF 508. The Policy Control Function (PCF) 514 includes the following functions: supporting a unified policy framework to manage network behavior, providing policy rules for the Control Plane Function (CP function) to enforce policy rules, and implementing subscription information related to policy decisions in the front-end access user data repository. The Network Exposure Function (NEF) 516 is optionally deployed for exchanging information with external third parties. In one embodiment, the Application Function (AF) 516 can store application information in the unified data repository through the NEF. The UPF 510 communicates with the data network 518.

[0034] The Access and Mobility Function (AMF) and the Session Management Function (SMF) are non-access stratum entities, and the User Plane Function (UPF) is a non-access stratum entity in New Radio (NR) or 5G Core (5GC). The signaling connection between the AMF / SMF and the Master Node (MN) may be the Next Generation-Control Plane (NG-C) / MN interface. The signaling connection between the MN and the Secondary Node (SN) may be the Xn-Control Plane (Xn-C) interface. The signaling connection between the MN and the UE may be the Uu-Control Plane (Uu-C) RRC interface. As described below, there may be additional components or entities for UP processing and data forwarding functions.

[0035] Figure 6 An example of UP processing and data forwarding is shown. Whether the UP part integrated in a network node or the UP node as a separate network node, it may be (re)configured by the CP part or the CP node through UP processing policies and various protocol parameters. Once the UP part or the UP node obtains the input user data (i.e., downlink / uplink packet flows), the UP part or the UP node will process these user data accordingly according to the CP configuration, and then output / forward them in sequence to the next UP part or UP node. In the absence of additional functions, in traditional wireless communication systems (such as 4G-LTE and 5G-NR), user data may always terminate at a certain UE in the downlink direction or at a data network server in the uplink direction, so it is always an End to End (E2E) communication service, only used for transmitting user data. The mechanism of UP processing and data forwarding is shown in Figure 6 which is shown in the following embodiments, there are additional functions / services for coordinating multiple service nodes.

[0036] In some embodiments, intermediate network nodes or entities (e.g., 5G UPF, CU-UP, and DU-UP parts) are only used for end-to-end (E2E) communication services and / or for transmitting / forwarding user data of a UE in the downlink (DL) or uplink (UL) direction. Coordination of control plane (CP) entities can provide additional support for multiple services. There may be different implementation manners, including some internal and different levels of computing services, intelligent services, storage services, and / or security service processing / behaviors, including Deep Packet Inspection (DPI), packet compression, packet encryption, and artificial intelligence (training, inference, etc.). The processing or behaviors of these computing services, intelligent services, storage services, and / or security services may not be controlled by the CP entity if the configurations as described herein are not provided. The CP entity can manage, orchestrate, or control multiple service types performed or executed by one UP entity or multiple UP entities. The CP entity can effectively coordinate the separate work and processing belonging to multiple service types among several UP entities. This coordination is implemented in the CP entity to achieve resource-efficient and Quality of Experience friendly (QoE friendly) without enabling a high level of multi-service provisioning.

[0037] Multi-service coordination

[0038] As described above, the CP entity manages and coordinates multiple service nodes for multiple types of services. These services at least include communication services, computing services, intelligent services, storage services, and / or security services. The CP entity configures extended UP functions that support multiple services and initiates the execution of these functions according to the configuration. The UP entity reports the capabilities of multiple services supported internally and receives the configurations of multiple services supported. The UP functions are initiated and executed based on the UP configuration received from the CP entity.

[0039] Figure 7A single base station system diagram with an extended UP function supporting multiple services is shown. This diagram is a centralized model for coordinating multiple service nodes. In one embodiment, a single base station has a single CP entity. Although the CP entity and the UP entity are shown separately in the diagram, they may be physically together. The UP entity may contain several modules, including other functions or configurations. A traditional UP entity (for communication only) may not have the functions / services shown here. The CP entity can configure and coordinate multiple service nodes. The CP entity coordinates / controls the processing of different entities. Services can be synchronized among multiple UP entities. As described below, there is a UP task identifier assigned by the CP for controlling the synchronization between UP entities. Although service processing was previously invisible to the CP entity, the UP configuration (which may be referred to as "generalized UP configuration") may allow the CP to manage and configure multiple services.

[0040] The following are the relevant terms for coordinating multiple service nodes:

[0041] · "CP entity": Refers to the control plane (CP) part integrated in a certain network node, or a dedicated CP node as an independent network node.

[0042] · "UP entity": Refers to the user plane (UP) part integrated in a certain network node, or a dedicated UP node as an independent network node.

[0043] · "Multiple services": Refers to additional services provided by a (wireless) network system, including but not limited to communication services, computing services, intelligent services, storage services, and / or security services.

[0044] · "Communication service data": User data related to a certain E2E communication service generated by a data network server or a UE.

[0045] · "Computing service data": Intermediate data related to a certain computing service generated by any network node.

[0046] · "Intelligent service data": Intermediate data related to a certain intelligent service generated by any network node.

[0047] · "Storage service data": Intermediate data related to a certain storage service generated by any network node.

[0048] · "Security service data": Intermediate data related to a certain security service generated by any network node.

[0049] · "Multi-service node": A network node that can provide multiple service types in addition to traditional end-to-end communication services. The multi-service node supports at least two services, including communication services, computing services, intelligent services, storage services, and / or security services, etc.

[0050] · "Service type": At least refers to additional services supported by the network, including but not limited to: communication, computing, intelligent, storage, and security services.

[0051] · "General UP function": Refers to data / packet processing related to multiple services, and the multiple services at least include communication services, computing services, intelligent services, storage services, and / or security services. Traditional UP function only refers to data / packet processing related to end-to-end communication services.

[0052] · "General UP configuration": Refers to the settings and configurations for the "General UP function", at least including: "Service type" and UP settings and parameters related to various services, including:

[0053] 1. ◆ UP parameters set for communication services, such as source / destination IP / port addresses, data transmission bandwidth, latency limit requirements, etc.;

[0054] 2. ◆ UP parameters set for computing services, such as computing resource type / address, number of computing resources, latency limit requirements, etc.;

[0055] 3. ◆ UP parameters set for intelligent services, such as artificial intelligence (AI) / machine learning (ML) mode, algorithms, or models, etc.;

[0056] 4. ◆ UP parameters set for storage services, such as storage resource type / address, number of storage resources, etc.;

[0057] 5. ◆ UP parameters set for security services, such as security mode, algorithms, or models, etc.

[0058] Figure 8 The figure shows a dual-base station system diagram with an extended UP function that supports multiple services. Different from Figure 7 this, this figure is a decentralized model. As Figure 8As shown, there may be two independent base stations, each with a CP entity. In this example, there may be Xn signaling between the CP entities. For separate base stations, the CP entity and the UP entity may be physically separated. The UP entity may contain several modules, including other functions or configurations. A traditional UP entity (for communication only) may not have the functions / services shown here. Services can be synchronized between multiple UP entities. As described below, there is a UP task identifier assigned by the CP to control the synchronization between UP entities. Although the CP entity was previously invisible to service processing, the UP configuration (which may be referred to as the "general UP configuration") may allow the CP to manage and configure multiple services.

[0059] Reference Figure 7 Or Figure 8 The following are the characteristics of the coordination of multiple service nodes. The UP entity in a multi-service node can report and update the actual multiple service capabilities of this multi-service node to the connected / controlled CP entity through internal signaling or through an interface-based signaling process. In this way, the CP entity can know the actual / true capabilities of each connected multi-service node. The interface-based signaling process may include a Radio Resource Control (RRC) process, a Non-Access Stratum (NAS) process, a Next Generation Application Protocol (NGAP) process, an Xn Application Protocol (XnAP) process, an F1 Application Protocol (F1AP) process, an E1 Application Protocol (E1AP) process, or an interface process that may be newly specified. The multiple service capabilities supported by the UP entity include at least communication services, computing services, intelligent services, storage services, and / or security services. Each service may have detailed capability information.

[0060] The CP entity can allocate and configure a series of parameters (the number of UP tasks), such as UP Task identification, Service Type, and UP Configuration or generalized UP configuration, for one or more UP entities through internal signaling or through an interface-based signaling process. The content of the UP Task identification may be an index ID, which is used to indicate a specific UP task allocated by the CP entity. The UP Task identification can be used to track / link / correlate the same UP tasks that need to be executed in different UP entities. The content of the Service Type may include an index ID or a clear indication, and the meaning of each index ID or indication may be predefined by the specification.

[0061] The UP configuration is configured by the CP entity and is adapted to different types of services and related tasks, including at least communication services, computing services, intelligent services, storage services, and / or security services, as well as the UP tasks related to these services. The UP configuration (or generalized UP configuration) may include:

[0062] · UP parameters set for communication services, such as source / destination IP / port addresses, data transfer bandwidth, latency limit requirements, etc.;

[0063] · UP parameters set for computing services, such as computing resource type / address, number of computing resources, latency limit requirements, etc.;

[0064] · UP parameters set for intelligent services, such as Artificial Intelligence (AI) / Machine Learning (ML) modes, algorithms, or models, etc.;

[0065] · UP parameters set for storage services, such as storage resource type / address, number of storage resources, etc.;

[0066] · UP parameters set for security services, such as security modes, algorithms, or models, etc.

[0067] The interface-based signaling procedures may at least include RRC procedures, NAS procedures, NGAP procedures, XnAP procedures, F1AP procedures, E1AP procedures, or potentially newly specified interface procedures. Once allocated and configured by the CP entity, the UP entity in the multi-service node will perform or execute corresponding UP tasks related to different configured service types. The UP entity can perform or execute multiple corresponding UP tasks simultaneously in parallel or in the indicated order / sequence. The UP entity can report and update the execution progress / status / result of the actual UP tasks of the UP entity to the CP entity via internal signaling or via the interface-based signaling procedures. In this way, the CP entity can learn about the actual progress / status / result of each UP task executed by the UP entity. Two neighboring CP entities can coordinate parameter lists such as UP task identification, service type, and UP configuration via the interface-based signaling procedures. When needed, two neighboring UP entities can exchange data of different types of services (such as data of communication services, computing services, intelligent services, storage services, and / or security services) via the data / packet transmission tunnel between the UP entities.

[0068] As described and shown in Figure 7 and Figure 8 The configuration may include service type, UP task identification, and / or UP configuration (i.e., general UP configuration). These are just examples of potential configuration parameters, and there may be more or fewer parameters. Due to the provided configurability, any of these types / modes can vary. The following are example embodiments that describe specific combinations of these configurable parameters. These are just examples, and many other combinations are possible in other examples.

[0069] In Figure 7 the first example embodiment, the CU entity communicates with two UP entities via the E1AP signaling procedure. In this example, the UP task identification is configured with a communication service type of UP task identification 1 and a computing service type of UP task identification 2. This is just one example of the parameters that can be configured. Both UP entity 1 and UP entity 2 are capable of effectively performing UP tasks of communication and computing service types (e.g., both UP entities can transmit user data and perform specific DPI operations on the incoming data packets from the upstream node UPF). Due to the lack of local computing resources or to obtain better DPI analysis results, the CP entity can let UP entity 1 and UP entity 2 jointly perform the computing UP tasks (e.g., UP entity 1 performs DPI operations on some "odd-numbered" QoS flow data packets, while UP entity 2 performs DPI operations on some "even-numbered" QoS flow data packets). UP entity 1 and UP entity 2 jointly perform the communication UP tasks in parallel (e.g., exchange / transmit QoS flow user data packets from the UPF between UP entity 1 and UP entity 2).

[0070] As a control / coordination node, the CP entity allocates and configures the UP entity 1 and the UP entity 2 respectively through the E1AP signaling process. The configuration may include the following parameters for two UP tasks of two different service types, including:

[0071] ·{UP Task id = 1, Service Type = Communication, transmit user data, UP parameters set for communication services};

[0072] ·{UP Task id = 2, Service Type = Computing, DPI operation, UP parameters set for computing services}.

[0073] After the CP entity allocates and configures, the UP entity 1 and the UP entity 2 determine how / when to execute the communication UP task 1 and the computing UP task 2 according to the instructions of the CP entity. The UP entity 1 may establish a "data transmission tunnel 1" when needed to exchange the communication service data of the UP task 1 with the neighboring UP entity 2. The UP entity 1 may establish a "data transmission tunnel 2" when needed to exchange the computing service data of the UP task 2 with the neighboring UP entity 2. The UP entity 1 and the UP entity 2 jointly execute the communication UP task 1 according to the UP parameters set for communication services and exchange the communication service data of the UP task 1 through the "data transmission tunnel 1". The UP entity 1 and the UP entity 2 jointly execute the computing UP task 2 according to the UP parameters set for computing services and exchange the computing service data of the UP task 2 through the "data transmission tunnel 2". During the execution of the two UP tasks, the UP entity 1 and the UP entity 2 can respectively report and update the progress / status / result of the UP task 1 or the UP task 2 to the CP entity through the E1AP signaling process. The CP entity can also reconfigure the UP entity 1 and the UP entity 2 separately when necessary.

[0074] In the second exemplary embodiment, there may be multiple CU entities, such as in Figure 8As shown. This is different from Embodiment 1 because there are multiple CU entities as well as different UP task identifiers and service types. These two CU entities communicate with each other through the Xn interface. In this example, the UP task identifier is configured with a communication service type of UP task identifier 3 and a computing service type of UP task identifier 4. This is just an example of the parameters that can be configured. Both UP entity 1 and UP entity 2 are capable of performing UP tasks of communication and computing service types (e.g., both UP entities can transmit user data and perform specific DPI operations on the data packets incoming from the upstream node UPF). As shown in the figure, CP entity 1 is connected to UP entity 1, and CP entity 2 is connected to UP entity 2. Two adjacent (neighboring) CP entities, CP entity 1 and CP entity 2, are connected through the Xn interface. Both UP entity 1 and UP entity 2 are capable of performing UP tasks of communication and computing service types (e.g., both UP entities can transmit user data and perform specific DPI operations on the data packets incoming from the upstream node UPF). Due to the lack of local computing resources or to obtain better DPI analysis results, CP entity 1 may let UP entity 1 and UP entity 2 jointly perform computing UP tasks (e.g., UP entity 1 performs DPI operations on some "odd-numbered" QoS flow data packets, while UP entity 2 performs DPI operations on some "even-numbered" QoS flow data packets). UP entity 1 and UP entity 2 may jointly perform communication UP tasks in parallel (e.g., they exchange / transmit QoS flow data packets of user data from UPF).

[0075] As the main coordination / control node, CP entity 1 performs allocation and configuration for UP entity 1 through the E1AP signaling procedure. CP entity 1 further performs allocation and configuration for neighboring CP entity 2 through the XnAP signaling procedure. CP entity 2 further performs allocation and configuration for UP entity 2 through the E1AP signaling procedure. All these signaling procedures may include the parameters of the following two UP tasks of different service types:

[0076] · {UP Task id = 3, Service Type = communication, transmit user data, UP parameters set for communication service};

[0077] · {UP Task id = 4, Service Type = computing, DPI operation, UP parameters set for computing service}.

[0078] After being allocated and configured by CP entity 1 and CP entity 2 respectively, UP entity 1 and UP entity 2 determine how / when to execute communication UP task 3 and computing UP task 4. UP entity 1 may establish a data transmission tunnel 3 when needed for exchanging communication service data of UP task 3 with neighbor UP entity 2. UP entity 1 may establish a data transmission tunnel 4 when needed for exchanging computing service data of UP task 4 with neighbor UP entity 2. UP entity 1 and UP entity 2 jointly execute communication UP task 3 according to the UP parameter configuration set for the communication service and exchange the communication service data of UP task 3 through data transmission tunnel 3. UP entity 1 and UP entity 2 jointly execute computing UP task 4 according to the UP parameter configuration set for the computing service and exchange the computing service data of UP task 4 through data transmission tunnel 4. After that, during the execution of the two UP tasks, UP entity 1 and UP entity 2 can respectively report and update the progress / status / result of UP task 3 or UP task 4 to CP entity 1 and CP entity 2 through the E1AP signaling process. CP entity 1 and CP entity 2 can also reconfigure UP entity 1 and UP entity 2 individually.

[0079] In the third exemplary embodiment, as Figure 7 shown, the CU entity communicates with two UP entities in the DU through the F1 signaling process. In this example, the UP task identifiers are configured as the communication service type with UP task identifier 5 and the intelligent service type with UP task identifier 6. Additionally, the UP entities here may be DUs instead of CUs. The UP entities in the DU are all capable of executing or performing UP tasks of the communication and intelligent service types (e.g., both UP entities can transmit user data and perform specific AI model training operations on incoming data packets from either UP entity). For distributed AI model training with different sampling data sets, the CP entity may have UP entity 1 and UP entity 2 jointly execute the intelligent UP task. UP entity 1 and UP entity 2 can jointly execute the communication UP task in parallel (e.g., they exchange / transmit DRB data packets of user data from the UP entities).

[0080] As a coordination / control node, the CP entity allocates and configures UP entity 1 and UP entity 2 respectively through the F1AP signaling process. The configuration may include the parameters of the following two different service type UP tasks:

[0081] ·{UP Task id = 5, Service Type = communication, transmit user data, UP parameters set for the communication service};

[0082] ·{UP Task ID = 6, Service Type = Intelligence, AI model training, UP parameters set for intelligent services}

[0083] After the CP entity in the CU is allocated and configured, the UP entity 1 and the UP entity 2 in the DU determine when / how to execute the communication UP task 5 and the intelligent UP task 6 according to the instructions of the CP entity. The UP entity 1 may establish a data transmission tunnel 5 when needed for exchanging the communication service data of the UP task 5 with the adjacent UP entity 2. The UP entity 1 may establish a data transmission tunnel 6 for exchanging the intelligent service data of the UP task 6 with the adjacent UP entity 2. The UP entity 1 and the UP entity 2 jointly execute the communication UP task 5 according to the UP parameters configured for the communication service and exchange the communication service data of the UP task 5 through the data transmission tunnel 5. The UP entity 1 and the UP entity 2 jointly execute the intelligent UP task 6 according to the UP parameters configured for the intelligent service and exchange the intelligent service data of the UP task 6 through the data transmission tunnel 6. After that, during the execution of the two UP tasks, the UP entity 1 and the UP entity 2 can respectively report and update the progress / status / result of the UP task 5 or the UP task 6 to the CP entity through the F1AP signaling process. The CP entity can also reconfigure the UP entity 1 and the UP entity 2 separately.

[0084] In the fourth exemplary embodiment, as Figure 7 shown, the CU entity is a gNB / base station / xNB entity that communicates with two UP entities in the UE through the Uu air interface. In this example, the UP task identifiers are configured as the communication service type with the UP task identifier 7 and the security service type with the UP task identifier 8. Both the UP entity 1 and the UP entity 2 are capable of executing or performing the UP tasks of the communication and security service types (for example, both UEs can transmit user data and perform specific data security protection operations together with the incoming data packets). In this example, the CP entity may be the base station / gNB / xNB, and the UP entity may be the UE. With the UE as the UP entity, the communication may be through RRC. For distributed data security protection with different backup sets, the CP entity may let the UP entity 1 and the UP entity 2 jointly execute the security UP task. The UP entity 1 and the UP entity 2 determine when / how to jointly execute the communication UP task in parallel (for example, they exchange / transmit user data packets from the CU entity or the base station / gNB / xNB).

[0085] As a coordination / control node, the CU entity (such as the base station / gNB / xNB) allocates and configures the UP entity 1 and the UP entity 2 in the UE respectively through the RRC signaling process. The configuration includes the parameters of the following two UP tasks of different service types:

[0086] ·{UP Task id = 7, Service Type = Communication, transmitting user data, UP parameters set for communication services};

[0087] ·{UP Task id = 8, Service Type = Security, distributed data protection, UP parameters set for security services}.

[0088] After the CU entity performs allocation and configuration, the UP entity 1 and UP entity 2 in the UE determine when / how to execute the communication UP task 7 and the security UP task 8. The UP entity 1 may establish a sidelink tunnel 7 when needed to exchange communication service data of the UP task 7 with the adjacent UP entity 2. The UP entity 1 may establish a sidelink tunnel 8 to exchange security service data of the UP task 8 with the adjacent UP entity 2. The UP entity 1 and UP entity 2 jointly execute the communication UP task 7 according to the UP parameters set for communication services and exchange communication service data of the UP task 7 through the sidelink tunnel 7. The UP entity 1 and UP entity 2 jointly execute the security UP task 8 according to the UP parameters set for security services and exchange security service data of the UP task 8 through the sidelink tunnel 8. Subsequently, during the execution of the two UP tasks, the UP entity 1 and UP entity 2 can separately report and update the progress / status / result of the UP task 7 or UP task 8 to the CU entity or the base station / gNB / xNB through the RRC signaling procedure. The CU entity or the base station / gNB / xNB can also reconfigure the UP entity 1 and UP entity 2 separately.

[0089] The following is a list of abbreviations:

[0090]

[0091]

[0092] Table 1 – Abbreviations

[0093] The systems and processes described above can be encoded on a signal-bearing medium, a computer-readable medium such as a memory, programmed in a device such as one or more integrated circuits, one or more processors, or processed by a controller or computer. These data can be analyzed in a computer system and used to generate a spectrum. If these methods are performed by software, the software may reside in a memory associated with a storage device, a synchronizer, a communication interface, or a non-volatile or volatile memory that communicates with a transmitter. Circuits or electronic devices are designed to send data to another location. The memory may include an ordered list of executable instructions for implementing logical functions. Any described logical function or system element can be implemented by an optical circuit, a digital circuit, source code, an analog circuit, an analog source (such as an analog electrical, audio, or video signal), or a combination. The software can be embodied in any computer-readable or signal-bearing medium for use or connection with a system, apparatus, or device of executable instructions. Such a system may include a computer-based system, a system that includes a processor, or another system that can selectively obtain and execute instructions from a system, apparatus, or device of executable instructions.

[0094] "Computer-readable medium", "machine-readable medium", "propagated signal" medium, and / or "signal-bearing medium" may include any device that stores, communicates, propagates, or transports software for use or connection with a system, apparatus, or device of executable instructions. Machine-readable media can be selective, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, devices, or propagation media. A non-exhaustive list of examples of computer-readable media will include: "electronic" electrical connections with one or more wires, portable magnetic or optical disks, volatile memories such as random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), or optical fibers. Computer-readable media can also include tangible media on which software is printed, since the software can be electronically stored in an image or other format (e.g., by optical scanning), and then compiled and / or interpreted or otherwise processed. The processed media can then be stored in a computer and / or machine memory.

[0095] The schematic diagrams of the embodiments described herein are intended to provide a general understanding of the structures of the various embodiments. These schematic diagrams are not intended as a complete description of the elements and features of the devices and systems that utilize the structures or methods described herein. Many other embodiments may become apparent to those of ordinary skill in the art upon review of the disclosure. Other embodiments may be utilized and derived from the disclosure so as to make structural and logical substitutions and changes without departing from the scope of the disclosure. In addition, these schematic diagrams are merely representative and may not be drawn to scale. Some of the ratios in the schematic diagrams may be exaggerated while others may be minimized. Accordingly, the disclosure and the schematic diagrams are to be regarded as illustrative rather than restrictive.

[0096] One or more of the disclosed embodiments may be referred to herein individually and / or collectively as an "invention" merely for convenience and are not intended to voluntarily limit the scope of this application to any particular invention or inventive concept. Additionally, although specific embodiments have been illustrated herein, it should be understood that any subsequent arrangement designed to achieve the same or similar purpose may replace the specific embodiments shown. This disclosure is intended to cover all subsequent adaptations or variations of the various embodiments. Upon review of the description, those of ordinary skill in the art will readily recognize combinations of the above-described embodiments as well as other embodiments not specifically described herein.

[0097] The term "coupled" is defined as directly connected or indirectly connected through one or more intermediate components. These intermediate components may include both hardware- and software-based components. Variations in the arrangement and type of components may be made without departing from the spirit or scope of the claims described herein. Additional, different, or fewer components may be provided.

[0098] The subject matter disclosed above should be considered illustrative rather than restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the invention. Accordingly, the scope of the invention should be determined by the broadest interpretation of the following claims and their equivalents and should not be limited by the foregoing detailed description. Although various embodiments of the invention have been described, it will be apparent to those of ordinary skill that many more embodiments and implementations are possible within the scope of the invention. Accordingly, the invention should not be limited except as provided in the appended claims and their equivalents.

Claims

1. A method for wireless communication, comprising: Configuring an extended user plane (UP) function that supports multiple services; And Initiating the execution of the UP function to a UP entity based on the configuration.

2. The method according to claim 1, wherein The UP function includes functions of identifying service types, UP task identifiers, and executing multiple services based on UP configurations.

3. The method according to claim 1, wherein, The multiple services include at least two of communication services, computing services, intelligent services, storage services, and / or security services.

4. The method according to claim 1, wherein The configuration and transmission of the UP configuration are performed by a network entity including a control plane (CP) entity.

5. The method according to claim 4, wherein, The UP configuration is received by the UP entity from the CP entity.

6. The method according to claim 5, wherein The configuration is performed through internal signaling or through interface-based signaling.

7. The method according to claim 5, wherein The configuration includes the UP configuration for multiple services for one or more UP entities.

8. The method according to claim 7, further comprising: Synchronizing and coordinating the multiple services among multiple UP entities.

9. The method according to claim 8, further comprising: Allocating task identifiers for synchronizing and coordinating the multiple services among the multiple UP entities.

10. The method according to claim 8, wherein, The multiple UP entities are configured to interact service data of different service types through different data transmission tunnels among the multiple UP entities.

11. The method according to claim 5, wherein, The UP entity reports and updates the status or result of the executed task to the CP entity through internal signaling or through an interface-based signaling process.

12. A method for wireless communication, comprising: Reporting the capabilities of multiple services within a user plane (UP) entity; And Receiving a UP configuration for the multiple supported services.

13. The method according to claim 12, wherein, The UP function includes functions of identifying service types, UP task identifiers, and executing the multiple services based on the UP configuration.

14. The method according to claim 12, wherein, The multiple services include at least two of communication services, computing services, intelligent services, storage services, and / or security services.

15. The method according to claim 12, wherein, The reporting of the capabilities and the receiving of the UP configuration are performed by a network entity including one or more UP entities.

16. The method according to claim 15, wherein, The UP configuration comes from a control plane (CP) entity, wherein the UP configuration is received by the one or more UP entities from the CP entity.

17. The method according to claim 16, wherein, The UP configuration is implemented through internal signaling or through interface-based signaling.

18. The method according to claim 16, wherein The UP configuration includes separate UP configurations for each service to be configured for one or more UP entities.

19. The method according to claim 18, wherein, The UP configuration includes the synchronization and coordination of multiple services among one or more UP entities.

20. The method according to claim 19, wherein, The UP configuration includes task identifiers for the synchronization and coordination of multiple services among one or more UP entities.

21. The method according to claim 16, wherein, The one or more UP entities are configured to interact service data of different service types through different data transmission tunnels among the one or more UP entities.

22. The method according to claim 16, wherein, The UP entity reports and updates the status or result of the executed task to the CP entity through internal signaling or through an interface-based signaling process.

23. A wireless communication device includes a processor and a memory, wherein, The processor is configured to read the code from the memory and implement the method according to any one of claims 1 to 22.

24. A computer program product, comprising computer-readable program code stored thereon, the computer-readable program code causing the processor to implement the method according to any one of claims 1 to 22 when executed by the processor.

Images