User plane processing and data forwarding

Abstract

Extensions of user plane (UP) processing and data forwarding functionality, including support for additional traffic, are provided. Not only communication, the configuration of the UP functionality may include support of traffic, including computing traffic, smart traffic, storage traffic, or security traffic.

Description

TECHNICAL FIELD

[0001] The present application relates generally to wireless communications. More specifically, User Plane (UP) handling and data forwarding functions include support for additional services. BACKGROUND

[0002] Wireless communication technology is pushing the world towards an increasingly interconnected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes, including but not limited to Radio Access Network (RAN) nodes and wireless base stations. New generation networks are 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 more and more complex, and the amount of data transmitted continues to increase. With the development of more advanced radar and sensing systems, communication with the UE can be modernized. SUMMARY

[0003] The present application relates to methods, systems and devices for extending User Plane (UP) handling and data forwarding functions, including support for additional services. Not only End to End (E2E) communication services, the configuration of UP functions can include support for services, including communication services, computing services, intelligent services, storage services or security services, etc.

[0004] In an embodiment, a method of wireless communication is provided that includes configuring a network entity for a user plane (UP) function; and receiving the configuration. The UP function includes identifying traffic types, UP handling, and UP data forwarding. The UP function supports traffic other than communication traffic, including at least computing, intelligence, storage, and / or security traffic. The network entity includes a user plane (UP) entity. The configuration is by a control plane (CP) entity of the UP entity, where the configuration is received at the UP entity from the CP entity. The configuration is by internal signaling or interface-based signaling. The configuration includes configuration of one or more user plane (UP) entities. The configuration includes configuration of traffic types, UP handling modes, or UP forwarding modes. The traffic types, UP handling modes, or UP forwarding modes include pre-defined index identification or explicit indication. The configuration is configured to allow data transfer traffic to be terminated at an intermediate node instead of an end node. The intermediate node is configured to forward user data of different traffic types to any other network node. The configuration includes configuration of handling modes, where the handling modes include at least: pass-through of incoming packets; compression of incoming packets; concatenation of incoming packets; segmentation of incoming packets; or local backup of packets. The configuration includes configuration of forwarding modes, where the forwarding modes include at least: protocol data unit (PDU) session types; data radio bearer (DRB) types; control plane (CP) signaling types; transmission control protocol (TCP) types; or quick user datagram protocol internet connections (QUIC types.

[0005] In another embodiment, there is also provided a method for wireless configuration, comprising: establishing a user plane (UP) configuration for a network entity supporting different types of services; performing a UP processing based on a reception of the UP configuration. The supported services include a communication service, a computing service, an intelligence service, a storage service, or a security service. The network entity includes a user plane (UP) entity for performing an action according to the UP configuration, wherein the establishing and configuring are performed by a control plane (CP) entity. The UP configuration includes a configuration of one or more user plane (UP) entities. The establishing is performed by internal signaling or interface-based signaling. The UP configuration is for a service type, a UP processing mode, or a UP forwarding mode. The service type, the UP processing mode, or the UP forwarding mode includes a predefined index identification or an explicit indication. The UP configuration allows a data transfer service to be terminated at an intermediate node instead of an end node. The intermediate node is configured to forward user data of different service types to any other network node. The UP configuration is for a processing mode, wherein the processing mode includes at least: a pass-through incoming packet; a compression incoming packet; a concatenation incoming packet; a segmentation incoming packet; or a local backup packet. The UP configuration is for a forwarding mode, wherein the forwarding mode includes at least: a PDU session type; a DRB type; a control plane (CP) signaling type; a TCP type; or a QUIC type.

[0006] In another embodiment, there is also provided a wireless communication apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement any of the methods described in this embodiment.

[0007] In another embodiment, there is also provided a computer program product comprising a computer-readable program medium having code stored thereon, the code, when executed by a processor, causing the processor to implement any of the methods described in this embodiment.

[0008] In some embodiments, there is a wireless communication apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement any of the methods described in any of the embodiments. In some embodiments, a computer program product comprises a computer-readable program medium having code stored thereon, the code, when executed by a processor, causing the processor to implement any of the methods described in any of the embodiments. The above and other aspects and implementations thereof are more fully described in the following detailed description together with the appended claims and drawings. BRIEF DESCRIPTION OF DRAWINGS

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

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

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

[0012] Figure 4 A single connectivity wireless communication system is shown with split cases.

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

[0014] Figure 6 User Plane (UP) handling and data forwarding is shown.

[0015] Figure 7 A single base station system diagram with extended User Plane (UP) handling and data forwarding is shown.

[0016] Figure 8 A dual base station system diagram with extended User Plane (UP) handling and data forwarding is shown.

[0017] Figure 9 Protocol stacks for different User Plane (UP) handling forwarding modes are shown. DETAILED DESCRIPTION

[0018] The present disclosure will now be described in detail below with reference to the attached drawings, which form a part of this disclosure, and which illustrate specific exemplary embodiments. However, the present disclosure can be embodied in various different forms, and should not be construed or interpreted as limited to the embodiments set forth herein. Rather, these embodiments are provided as examples of the disclosure, and there are many other ways to implement the subject matter of the present disclosure.

[0019] Throughout the specification and claims, unless the context dictates otherwise, the term "may" is intended to be synonymous with the term "may" and the term "may" is intended to be synonymous with the term "may". The term "in one embodiment" or "in some embodiments" as used herein does not necessarily refer to the same embodiment, and the term "in another embodiment" or "in other embodiments" as used herein does not necessarily refer to a different embodiment. The term "in one implementation" or "in some implementations" as used herein does not necessarily refer to the same implementation, and the term "in another implementation" or "in other implementations" as used herein does not necessarily refer to a different implementation. For example, the claimed subject matter is intended to include a combination of example embodiments or implementations, in whole or in part.

[0020] Generally, terminology can be understood at least in part from the context in which it is used. For example, the terms used in the present embodiments, such as “and”, “or”, “and / or”, can include a variety of meanings that can depend at least in part upon the context in which they are used. Typically, “or” if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” or “at least one” as used in the present embodiments, at least depending on the context, can be used to describe any feature, structure, or characteristic in the singular or can be used to describe combinations of features, structures or characteristics. Similarly, terms such as “a”, “an” or “the” again can be understood to convey a singular usage or to convey a plural usage, at least depending on the context in which it is used. Also, the term “based on” or “determined by” can be understood as not necessarily intended to convey an exclusive set of factors, but rather can allow for existence of additional factors not explicitly described, again at least depending on the context.

[0021] Radio Resource Control (RRC) is a protocol layer between a UE and a base station on top of IP layer (wireless network layer). There can be various Radio Resource Control (RRC) states, such as RRC Connected (RRC_CONNECTED), RRC Inactive (RRC_INACTIVE), and RRC Idle (RRC_IDLE) states. RRC messages are transported via Packet Data Convergence Protocol (PDCP). A UE can transmit infrequent (periodic and / or aperiodic) data in RRC_INACTIVE state without moving to RRC_CONECTED state. This can save UE power consumption and signaling overhead. This can be implemented by a Random Access Channel (RACH) protocol scheme or a Configured Grant (CG) scheme. The wireless communications described in the present embodiments can be over a wireless access. Figure 1 and Figure 2 Example radio access network (RAN) nodes (e.g., base stations) and user equipment and message environments are shown that can be applicable to the user plane (UP) functions and communications described below.

[0022] With the recent developments of wireless communication systems (e.g., 5G-NR and 6G wireless systems) and various distributed computing, intelligence, storage, and security systems, integration can be a challenge. The integration among each other can 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 can attempt to integrate various new functions and traffic with legacy systems, including but not limited to computing traffic, intelligence traffic, storage traffic, and / or security systems. As a result, core network (CN) and RAN nodes can provide not only wireless communication traffic, but also computing traffic, intelligence traffic, storage traffic, and / or security traffic, etc.

[0023] User plane (UP) processing and data forwarding functions can be used to process and transfer user data associated with mobile traffic (e.g., mobile applications and network traffic) for different users. As a result, the UP processing and data forwarding functions in a network node can not be concerned with the data type / content or characteristics of the user data. Instead, the processing and forwarding can be based on internal UP processing units from input ports to output ports. As described below, based on the extension of UP processing and data forwarding functions, data of additional traffic types can be processed and transferred. The extension can cover different traffic types. A wireless network node can differentiate between different types of traffic data, take different UP processing and forwarding strategies for different types of traffic data, and thus achieve the purpose of efficient network interface resource.

[0024] Figure 1 An example (RAN) node or base station 102 is shown. The RAN node can also be referred to as a wireless network node. The RAN node 102 can further be identified as a Node B (NB) in a mobile telecommunication environment (e.g., eNB or gNB). An example RAN node can include wireless Tx / Rx circuitry 113 to receive and transmit with user equipment (UE) 104. The RAN node can also include network interface circuitry 116 to couple the RAN node to a core network 110, e.g., optical or wired interconnections, Ethernet, and / or other data transfer media / protocols.

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

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

[0027] The mobile device 200 includes a communication interface 212, system logic 214, and a user interface 218. The system logic 214 can include any combination of hardware, software, firmware, or other logic. The system logic 214 can be implemented, for example, with one or more Systems on a Chip (SoCs), Application Specific Integrated Circuits (ASICs), discrete analog and digital circuits, and other circuits. The system logic 214 is part of the implementation of any desired functionality in the UE 104. In this regard, the system logic 214 can include logic to facilitate, for example, decoding and playing music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular telephone calls or data connections, such as for Internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 218. The user interface 218 and input 228 can include a graphical user interface, a touch-sensitive display, tactile feedback or other haptic output, voice or facial recognition input, buttons, switches, a speaker, and other user interface elements. Additional examples of input 228 can include a microphone, a video and still image camera, a temperature sensor, a vibration sensor, a rotation and orientation sensor, earphone and microphone input / output jacks, a Universal Serial Bus (USB) connector, a memory card slot, a radiation sensor (e.g., an IR sensor), and other types of input.

[0028] System logic 214 can include one or more processors 216 and memory 220. Memory 220 stores, for example, control instructions 222 that the processors 216 execute to implement the desired functionality of the UE 104. Control parameters 224 provide and specify configuration and operational options for the control instructions 222. Memory 220 can also store any BT, WiFi, 3G, 4G, 5G, or other data 226 that the UE 104 will transmit or has received through the communication interface 212. In various implementations, system power can be provided by a power storage device (e.g., battery 282).

[0029] In the communication interface 212, radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 230 handles transmission and reception of signals through one or more antennas 232. The communication interface 212 can include one or more transceivers. The transceivers can be wireless transceivers that include modulation / demodulation circuitry, digital to analog converters (DACs), shaping tables, analog to digital converters (ADCs), filters, wave shapers, pre-amplifiers, power amplifiers, and / or other logic for transmission and reception through one or more antennas or, for some devices, through physical (e.g., wired) media.

[0030] The signals transmitted and received can adhere to any of a different array of formats, protocols, modulations (e.g., QPSK (Quadrature Phase Shift Keying), 16-QAM (16-Level Quadrature Amplitude Modulation), 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific example, the communication interface 212 can include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. However, the technology described below is applicable to other wireless communication technologies, whether derived from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0031] Figure 3 A single connectivity wireless communication system is shown. Single connectivity (SC) can include a UE with only a master radio link (M-RL) and no radio link at the secondary RAN node side. In contrast, dual connectivity (DC) includes a UE with a secondary communication radio link (S-RL) at the secondary RAN node side. In the case of Figure 3 In an IMT wireless communication system (e.g., 4G-LTE and 5G-NR) as shown, a radio access network (RAN) node can transmit downlink (DL) pilot reference signals, e.g., SSB, CSI-RS, etc. A UE receives, measures, and processes these signals so that the UE can learn the quality of the radio link (RL) connection over the air. This can be a communication between a traffic RAN node and a UE in order to maintain communication traffic continuity. This is an example of single connectivity (SC).

[0032] Figure 4 A single connectivity wireless communication system is shown in the split case. Figure 3 A non-split case is shown, while Figure 4 A split of a CU-CP node and a CU-UP node is shown. In an IMT wireless communication system (e.g., 5G-NR as specified by 3GPP) as shown, Figure 3 and Figure 4 In an IMT wireless communication system (e.g., 5G-NR as specified by 3GPP) as shown, a core network (CN) can include various types of control plane (CP) nodes or entities (e.g., 5G AMF / SMF) and user plane (UP) nodes or entities (e.g., 5G UPF). In the case of Figure 3 In a RAN non-split case in, a RAN node (e.g., 5G aggregated base station) includes a CP part and a UP part, which are then terminated on a UE via an over-the-air radio link (RL). In the case of Figure 4 In a RAN split case in, a RAN node (e.g., 5G disaggregated base station) includes a CU-CP node, a CU-UP node, and a DU node or entity, which are then terminated on a UE via an over-the-air RL. The CP part or node can be responsible for generating, processing, and transmitting control signaling (e.g., for (re)configuration and monitoring of other nodes). The UP part or node is responsible for processing and transmitting user data (e.g., associated with mobile APPs and web traffic, etc.). There can be separate interfaces and protocol stacks for the CP and UP planes, and typically span from the CN domain to the RAN network, and then to the UE. The UP functionality is further described below, and can be in Figure 1 and Figure 2 In the system as shown or described belowFigure 5 implemented in the system of FIG. 1.

[0033] Figure 5 An embodiment of a wireless network system architecture is shown. This architecture is merely one example, and more or fewer components can be utilized to implement the embodiments described in this embodiment. The interconnection or communication between components is identified as N1, N2, N4, N6, N7, N8, N10, and N11, which can be referenced in the specification or through other drawings. Figure 2 An example user equipment (UE) 104 is shown. The UE 502 is a device that accesses a wireless network (e.g., 5GS) and obtains traffic via an NG-RAN node or base station 504. The UE 502 interacts with an Access and Mobility Control Function (AMF) 506 of the core network via NAS signaling. Figure 1 An example base station or NG-RAN 102 is shown. The NG-RAN node 504 is responsible for scheduling of air interface resources and management of air interface connections for the network that the UE accesses. 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 anchor and relays

[0034] The SMF 508 includes the following functionalities: session management (e.g., session establishment, modification, and release), UE IP address allocation and management (including optional authorization), selection and control of the uplink function, downlink data notification, etc. The User Plane Function (UPF) 510 includes the following functionalities: anchor point for intra- / inter-RAT mobility, packet routing and forwarding, traffic usage reporting, quality of service (QoS) handling for user plane, downlink packet buffering and downlink data notification triggering, etc. The Unified Data Management (UDM) 512 manages the subscription profile for UEs. The subscription includes data for mobility management (e.g., restricted area) and session management (e.g., QoS profile). The subscription data also includes slice selection parameters for the AMF 506 to select a suitable SMF 508. The AMF 506 and the SMF 508 obtain the subscription from the UDM 512. The subscription data can be stored in a unified data repository with the UDM 512, which uses such data upon receiving a request from the AMF 506 or the SMF 508. The Policy Control Function (PCF) 514 includes the following functionalities: support for a unified policy framework to govern the network behavior, provide policy rules to control plane functions to enforce, and implement a front end to access subscription information relevant for policy decisions in a user data repository. The Network Exposure Function (NEF) 516 is optionally deployed for exchanging information with external third parties. In one implementation, the Application Function (AF) 516 can store application information in the unified data repository via the NEF. The UPF 510 communicates with the data network 518.

[0035] In New Radio (NR) or 5GC, Access Mobility Function (AMF) and Session Management Function (SMF) are control plane entities, and User Plane Function (UPF) is a user plane entity. The signaling connection between AMF / SMF and MN can be Next Generation-Control Plane (NG-C) / MN interface. The signaling connection between MN (Master Node) and SN (Secondary Node or Secondary Node) can be Xn-Control Plane (Xn-C) interface. The signaling connection between MN and UE can be Uu-Control Plane (Uu-C) RRC interface. As described below, there can be additional components or entities for UP handling and data forwarding functions.

[0036] Figure 6 User Plane (UP) handling and data forwarding in one example is shown. For the UP part integrated in a network node or UP node as a standalone network node, it can be (re)configured by the CP part or CP node with UP handling policies and various protocol parameters. Once the UP part or UP node gets input user data (i.e., DL / UL packet flow), it is handled accordingly based on the CP configuration and then output / forwarded in turn to the next UP part or UP node. In legacy wireless communication systems (e.g., 4G-LTE and 5G-NR), user data can always be terminated on a specific UE in the DL direction or on a data network server in the UL direction without additional functions, so always for end-to-end (E2E) communication service with only transport of user data. The mechanism for UP handling and data forwarding is shown in Figure 6 In the following implementations, there are additional functions / services for UP handling and data forwarding.

[0037] In some implementations, UP functions (e.g., UP and data forwarding) are used for various services, not just the default E2E communication service. Likewise, the service is not just the transport of user data of the end node UE (i.e., associated UE). Instead, the transport of user data can now be terminated on any intermediate network node in addition to the UE or data network / DN server.

[0038] In some embodiments, the intermediate network node or entity (e.g., 5G UPF, CU-UP and DU-UP parts) can trigger and initiate UP functions by itself. This can happen without the need for input user data from upstream or downstream nodes. For data generated by the intermediate network node, its transmission can be based on the current UP function or tunnel.

[0039] In some embodiments, the intermediate network node can dynamically process user data and then forward it to an upstream or downstream target node. The target can not be static based on the association with the served UE. The intermediate network node can forward user data to any other network node, even those not associated with the served UE. This can be referred to as a “UP transmission path” and can be dynamic or adjustable, rather than static / fixed.

[0040] In some embodiments, for any UP entity, the UP processing mode, forwarding mode, and its related interface protocol stack can be used for different traffic, rather than just needing to forward any user data of any UE, regardless of different traffic characteristics.

[0041] Traffic As mentioned above, in addition to E2E communication, the extended / expanded traffic can include computing traffic, intelligent traffic, storage traffic, and / or security traffic, etc. The capabilities of these traffic can be integrated into the wireless communication system. Various data of different traffic types can be processed and forwarded during their distributed traffic operations. The traffic characteristics of these traffic can be different from the traditional E2E communication traffic. Example differences include data generator and packet size / frequency / periodicity, etc. As described in the embodiments of the present embodiment, the UP mechanism can be changed to incorporate additional traffic / functionality. This can be referred to as extended or expanded UP processing and data forwarding functionality.

[0042] Figure 7 A single base station system diagram with extended user plane (UP) processing and data forwarding is shown. The diagram is a centralized model of the use of extended UP processing and data forwarding functionality. In one embodiment, a single base station has a single CP entity. While the CP entity and UP entity are shown separately, they can be together physically. There can be several blocks in the UP entity, including forwarding mode and processing mode. The traditional UP entity (for communication only) does not have as many modes as the present embodiment. The CP entity can configure the appropriate UP processing mode and / or UP forwarding mode. The functionality extension of the UP entity includes providing additional traffic (in addition to communication).

[0043] The following are related terms that extend other UP functionality: • "CP entity": refers to the control plane (CP) part integrated in a certain network node or a dedicated CP node as a standalone network node.

[0044] • "UP entity": refers to the user plane (UP) part integrated in a certain network node or a dedicated UP node as a standalone network node.

[0045] • "UP function": refers to user plane (UP) packet processing, data forwarding, and related UP interface protocol stack.

[0046] • "Communication service data": user data generated by a data network service or UE, related to a certain E2E communication service.

[0047] • "Computing service data": intermediate data generated by any network node, associated with a certain computing service.

[0048] • "Intelligent service data": intermediate data generated by any network node, associated with a certain intelligent service.

[0049] • "Storage service data": intermediate data generated by any network node, associated with a certain storage service.

[0050] • "Security service data": intermediate data generated by any network node, associated with a certain security service.

[0051] • "Multi-service node": a network node capable of providing multiple types of services in addition to a single traditional E2E communication service.

[0052] • "Service type": at least refers to additional services, including but not limited to: network-supported communication, computing, intelligent, storage, and security services.

[0053] • "UP processing mode": the mode in which the "UP entity" processes input data of a certain service type.

[0054] • "UP forwarding mode": the mode in which the "UP entity" forwards output data of a certain service type.

[0055] • "UP configuration": the settings and configurations of "service type", "UP processing mode", "UP forwarding mode", and other UP function-related parameters.

[0056] Figure 8 A dual base station system diagram with extended user plane (UP) processing and data forwarding is shown. Compared to the conventional dual base station system Figure 7Likewise, this figure is a decentralized model for the use of extended UP processing and data forwarding functions. As shown, there can be two independent base stations, each with a CP entity. In this example, there can be Xn signaling between CP entities. For split base stations, CP entities and UP entities can be physically separated.

[0057] Reference Figure 7 Or Figure 8 The following are the features of UP function extension. A CP entity can configure one or more UP entities with parameters such as "traffic type", "UP processing mode" and "UP forwarding mode" via internal signaling or interface-based signaling. The content of the parameters: "traffic type", "UP processing mode" and "UP forwarding mode" can take the form of index identification or explicit indication. The meaning of each index id or indication can be pre-defined by standard specifications. The "UP configuration" configured by the CP entity can be applicable to different types of traffic, for example, the communication, computing, intelligence, storage and / or security traffic described in the embodiments. In order to decouple from the traditional existing parameters similar to "traffic type", "UP processing mode" and "UP forwarding mode", there can be new parameters, including but not limited to: "new traffic type", "new UP processing mode" and "new UP forwarding mode" which can be additionally defined and used instead.

[0058] Two adjacent CP entities can synchronize the content of "traffic type", "UP processing mode" and "UP forwarding mode" and the like via interface-based signaling, so that the UP processing in adjacent UP entities can be synchronized with each other or adapted to each other.

[0059] "Multi-traffic node" can support multiple types of traffic, for example, the communication, computing, intelligence, storage and / or security traffic described in the embodiments, and can support one or more "UP processing mode" and "UP forwarding mode" and multiple related interface protocol stacks described below with reference to Figure 9 .

[0060] "UP processing mode" can include at least: "transmitting incoming packets", "compressing incoming packets", "connecting incoming packets", "splitting incoming packets" and / or "locally backing up packets" and the like. "UP forwarding mode" can include at least: "PDU session type", "DRB type", "CP signaling type", "TCP type", "QUIC type" and the like. In addition, its related interface protocol stack is shown in Figure 9 .

[0061] Figure 9Protocol stacks are shown for different user plane (UP) forwarding modes. Examples of different “UP forwarding modes” and corresponding protocol stacks are shown. These protocols are merely examples that can be used for various traffic. NG uses PDU sessions. QUIC can be a combination of TCP and PDU. New UP functions can support at least these protocol stacks, but additional protocol stacks can be supported in the future. As described above, the supported protocol stacks can be configured as part of the UP function extension. This configuration allows various protocol stacks to be supported.

[0062] After being configured by the control CP entity, the UP entities in the plurality of traffic nodes perform corresponding UP processing and UP data forwarding activities according to the configuration. Two adjacent UP entities can exchange different types of traffic data via different types of UP forwarding modes or related UP interface protocol stacks based on different types of data transport tunnels configured by the CP entity.

[0063] As described and shown in Figure 7 and Figure 8 , the configuration can include traffic type, UP processing mode, and / or UP forwarding mode. Due to the provided configurability, any of these types / modes can change. In addition, the tunnel type between the CU-UP and the signaling procedure with the CP (and between the CPs of Figure 8 can also change. When multiple traffics are configured simultaneously, different types of tunnels can be established and coexist between the same related CU-UPs. And any combination of these configurable parameters is possible. The following are example implementations describing specific combinations of those configurable parameters. These are merely examples, and many other combinations are possible in other examples.

[0064] In a first implementation as shown in Figure 7 , the CU entity communicates via the E1AP signaling procedure. The tunnel type is PDU session. For this example, the traffic type is compute traffic, Deep Packet Inspecting (DPI) operation, the UP processing mode is compressing incoming packets, and the UP forwarding mode is PDU session type. This is merely one example of the parameters that can be configured.

[0065] The UP entity is capable of performing some type of compute task, e.g., performing a specific DPI algorithm on incoming packets. Due to a local lack of compute capability resources, or to obtain better DPI analysis results, the CP entity can have the upstream UP entity and the downstream UP entity jointly perform the compute task, e.g., in one example, the upstream UP entity performs the DPI operation on some “odd” QoS flow packets, and the downstream UP entity performs the DPI operation on some “even” QoS flow packets. The compute traffic data is transported from the upstream UP entity to the downstream UP entity via a forwarding tunnel.

[0066] As a control node, the CP entity configures the upstream UP entity and the downstream UP entity respectively via E1AP signaling procedures, which include the following parameters: “Service Type”: Compute Service, DPI Operation; “UP Processing Mode”: Compress Inbound Packets; and “UP Forwarding Mode”: PDU Session Type.

[0067] After being configured by the CP entity, the upstream UP entity performs the compute task (e.g., DPI operation) as instructed and compresses the input QoS flow packets as instructed. In addition, some “compute service data” (e.g., user data packets) can be transmitted to the adjacent downstream UP entity to offload the compute task. Likewise, the downstream UP entity knows to perform a compute task (e.g., DPI operation) as instructed and can compress the input QoS flow packets as instructed and receive some “compute service data” from the adjacent upstream UP entity. After being configured by the CP entity, the upstream UP entity can establish a “PDU Session Type Tunnel” with the adjacent downstream UP entity. Thereafter, the upstream UP entity and the downstream UP entity each perform the compute task (e.g., DPI operation) as instructed and the “compute service data” is transmitted via the established “PDU Session Type Tunnel” and further processed by the downstream UP entity.

[0068] In a second embodiment, there can be multiple CU entities, as shown in Figure 8 This is different from the first embodiment because there are multiple CU entities and because the tunnel type and forwarding mode are DRBs. The CU entities communicate via the Xn interface. For this example, the service type is compute service, deep packet inspection (DPI) operation, the UP processing mode is compress inbound packets, and the UP forwarding mode is DRB type. This is just one example of parameters that can be configured.

[0069] One CP entity is connected with an upstream UP entity and another CP entity is connected with a downstream UP entity via the standardized E1 interface. Both the adjacent upstream UP entity and the downstream UP entity are capable of performing a certain compute task (e.g., executing a particular DPI algorithm) on the inbound packets. Due to the local lack of compute capability resources, or to obtain better DPI analysis results, one CP entity decides to have the upstream UP entity and the downstream UP entity connected to another CP entity jointly perform the compute task. In one example, the upstream UP entity performs the DPI operation on some “odd” QoS flow packets, while the downstream UP entity performs the DPI operation on some “even” QoS flow packets. The “compute service data” can be transmitted from the upstream UP entity to the downstream UP entity via a forwarding tunnel of appropriate type.

[0070] As a control node, the first CP entity configures the upstream UP entity via E1AP signaling procedures, including the following parameters in this example: “Traffic Type”: Compute traffic, DPI operation; “UP Processing Mode”: Compress incoming packets; “UP Forwarding Mode”: DRB type.

[0071] The first CP entity transmits configuration parameters to another CP entity via Xn signaling procedures, and then the second / other CP entity configures the downstream UP entity via E1AP signaling procedures, including the following parameters in this example: “Traffic Type”: Compute traffic, DPI operation; “UP Processing Mode”: Compress incoming packets; “UP Forwarding Mode”: DRB type.

[0072] After being configured by the first CP entity, the upstream UP entity determines whether to perform the compute task (e.g., DPI operation) as instructed and can compress the input QoS flow packets. Some “compute traffic data” can be transmitted to the adjacent downstream UP entity to offload the compute task. Likewise, the downstream UP entity determines whether to perform the compute task (e.g., DPI operation) as instructed. The input QoS flow packets can be compressed as instructed and some “compute traffic data” is received from the adjacent upstream UP entity. After being configured by the first CP entity, the upstream UP entity can establish a “DRB type tunnel” with the adjacent downstream UP entity as shown. Thereafter, the upstream UP entity and the downstream UP entity each perform the compute task (e.g., DPI operation) as instructed and the “compute traffic data” is transmitted via the established “DRB type tunnel” and further processed by the downstream UP entity.

[0073] In a third implementation as shown in Figure 7 , the CU entity communicates via E1AP signaling procedures. The tunnel type is DRB. For this example, the traffic type is intelligent traffic. The UP processing mode is locally backed up packets and the UP forwarding mode is DRB. This is just one example of parameters that can be configured. The intelligent traffic used in this example can be associated with machine learning and / or artificial intelligence, including training features. Multiple UPs can offload tasks from each other. This is just one example of parameters that can be configured.

[0074] The CP entity is connected with two neighboring base station UPs via the El interface. Both the upstream UP entity and the downstream UP entity are capable of performing intelligent traffic and backup tasks (e.g., performing specific AI training operations on incoming packets). Due to the accuracy and reliability requirements of AI training, the CP entity can have the upstream UP entity and the downstream UP entity jointly perform tasks. For example, the upstream UP entity performs compression operations on incoming packets to collect statistics on the delay and jitter of the packets, and then transmits the packets to the downstream UP entity. The downstream UP entity performs local backup operations to save sample data for future AI training. The "intelligent traffic data" needs to be transmitted from the upstream UP entity to the downstream UP entity via a proper type of forwarding tunnel.

[0075] As a control node, the CP entity configures the upstream UP entity and the downstream UP entity respectively via El AP signaling procedures. In one example, the following parameters are configured for the upstream UP entity: "Traffic type": intelligent traffic with AI training; "UP processing mode": compress incoming packets; "UP forwarding mode": DRB type.

[0076] In one example, the following parameters are configured for the downstream UP entity: "Traffic type": intelligent traffic with AI training; "UP processing mode": locally backup incoming packets; "UP forwarding mode": DRB type.

[0077] After being configured by the CP entity, the upstream UP entity determines whether to perform intelligent tasks (e.g., AI training for vertical industry applications) as instructed. The incoming packets can be compressed as instructed, and some sample data is transmitted to the neighboring downstream UP entity for "intelligent traffic data". Likewise, the downstream UP entity determines whether to perform backup tasks (e.g., AI training for vertical industry applications) as instructed, and should backup the incoming packets as instructed. Some "intelligent traffic data" can be received from the neighboring upstream UP entity. After being configured by the CP entity, the upstream UP entity will establish a "DRB type tunnel" with the neighboring downstream UP entity as instructed. Thereafter, the upstream UP entity and the downstream UP entity each perform intelligent AI training and backup tasks (e.g., for vertical industry applications) as instructed, and the "intelligent traffic data" is transmitted via the established "DRB type tunnel" and further processed by the downstream UP entity.

[0078] In the fourth implementation, there can be multiple CU entities, such as Figure 8The tunnel type and forwarding mode is DRB. The CU entities communicate via the Xn interface. For this example, the traffic type is intelligent traffic. For both UP entities, the UP handling mode is different, with the downstream UP entity locally backing up packets and the upstream UP entity compressing into packets. This is just one example of parameters that can be configured.

[0079] As shown in Figure 8 The two CP entities are connected to each other via the standardized Xn interface. The first CP entity is connected to the upstream UP entity, and the second CP entity is connected to the downstream UP entity via the standardized El interface. Both the upstream UP entity and the downstream UP entity are capable of performing intelligent traffic or AI training and backup tasks (e.g., performing AI training on incoming packets). Due to the accuracy and reliability requirements of AI training, the CP entities determine whether to let the upstream UP entity and the downstream UP entity jointly perform the tasks. In this example, the upstream UP entity performs a compression operation on incoming packets to collect statistics on the delay and jitter of the packets, then transmits the packets to the downstream UP entity and performs a local backup operation to save sample data for future training. The “intelligent traffic data” can be transmitted from the upstream UP entity to the downstream UP entity via an appropriate type of forwarding tunnel.

[0080] As the control node, the first CP entity can configure the upstream UP entity via the El AP signaling procedure. In one example, this can include the following parameters: “Traffic Type”: Intelligent traffic, AI training for vertical industry applications, “UP Handling Mode”: Compress into packets; “UP Forwarding Mode”: DRB type.

[0081] The first CP entity transmits the configuration parameters to the second CP entity via the Xn signaling procedure, and then the second CP entity configures the downstream UP entity via the El AP signaling procedure, including the following parameters in one example: “Traffic Type”: Intelligent traffic, AI training for vertical industry applications; “UP Handling Mode”: Local backup into packets; “UP Forwarding Mode”: DRB type.

[0082] After being configured by the first CP entity, the upstream UP entity knows to perform the intelligent AI training task (e.g., AI training for vertical industry applications) as instructed, can compress the incoming packets as instructed, and transmit some sample data to the adjacent downstream UP entity for “smart traffic data”. Likewise, the downstream UP entity determines whether to perform the backup task (e.g., AI training for vertical industry applications) as instructed, and can backup the incoming packets as instructed. Some “smart traffic data” can be received from the adjacent upstream UP entity. After being configured by the first CP entity, the upstream UP entity will establish a “DRB type tunnel” with the adjacent downstream UP entity as instructed. Thereafter, the upstream UP entity and the downstream UP entity each perform the intelligent AI training and backup tasks (e.g., AI training for vertical industry applications) as instructed, and the “smart traffic data” is transmitted via the established “DRB type tunnel” and further processed by the downstream UP entity.

[0083] In a fifth embodiment as shown in Figure 7 the CU entity communicates via an E1AP signaling procedure. The UP forwarding mode and tunnel type is TCP, and the traffic type is smart traffic. In this example, the UP processing mode is split incoming packets. Splitting incoming packets can allow for different training. The smart traffic used in this example can be associated with machine learning and / or artificial intelligence, including training features. This is just one example of parameters that can be configured.

[0084] The CP entity is connected with two adjacent UP entities via an E1 interface. Both the upstream UP entity and the downstream UP entity are capable of performing an intelligent traffic or AI training task (e.g., performing a specific splitting operation on incoming packets for XR traffic). Due to computational capability limitations and user experience requirements, the CP entity determines whether to let the upstream UP entity and the downstream UP entity jointly perform the intelligent AI training task (e.g., the upstream UP entity can split video and voice related data and perform a splitting operation on video related packets for AI codec training). The downstream UP entity performs a splitting operation on voice related packets for AI codec training. “Smart traffic data” can be transmitted from the upstream UP entity to the downstream UP entity via an appropriate type of forwarding tunnel.

[0085] As a control node, the CP entity configures the upstream UP entity and the downstream UP entity via an E1AP signaling procedure, including the following parameters in one example: “Traffic type”: smart traffic, AI codec training for XR applications; “UP processing mode”: split incoming packets; “UP forwarding mode”: TCP type.

[0086] After being configured by the CP entity, the upstream UP entity determines whether to perform the smart AI training task (e.g., AI codec training for XR application) as instructed. The incoming packets can be split as instructed and some “smart traffic data” is transmitted to the neighboring downstream UP entity to offload the AI training task. Likewise, the downstream UP entity determines whether to perform the smart AI training task (e.g., AI codec training for XR application) as instructed. The incoming packets can be split as instructed and some “smart traffic data” is received from the neighboring upstream UP entity. According to the configuration of the CP entity, the upstream UP entity will establish a “TCP type tunnel” with the neighboring downstream UP entity. After that, the upstream UP entity and the downstream UP entity perform the smart AI training task (e.g., AI codec training for XR application) as instructed respectively, and the “smart traffic data” is transmitted via the established “TCP type tunnel” and further processed by the downstream UP entity.

[0087] In the sixth implementation, there can be multiple CU entities, as shown. Figure 8 The tunnel type and forwarding mode are TCP. The CU entities communicate via Xn interface. For this example, the traffic type is smart traffic. The UP processing mode is split-incoming packet. This is just one example of the parameters that can be configured.

[0088] The first CP entity is connected with the upstream UP entity, and the second CP entity is connected with the downstream UP entity via the standardized E1 interface. Both the upstream UP entity and the downstream UP entity are capable of performing the smart AI training task (e.g., AI codec training for XR traffic). Due to the computation capability limitation and user experience requirement, the CP entity determines whether to let the upstream UP entity and the downstream UP entity jointly perform the smart AI training task. For example, the upstream UP entity will split the video and voice related data and perform split operation on the video related packets for AI codec training, while the downstream UP entity performs split operation on the voice related packets for AI codec training. The “smart traffic data” needs to be transmitted from the upstream UP entity to the downstream UP entity via an appropriate type of forwarding tunnel.

[0089] As the control node, the first CP entity configures the upstream UP entity via the E1AP signaling procedure, including the following parameters in one example: “Traffic type”: smart traffic, smart AI training for XR application; “UP processing mode”: split-incoming packet; “UP forwarding mode”: TCP type.

[0090] The first CP entity transmits configuration parameters to the second CP entity via an Xn signaling procedure. The second CP entity configures the downstream UP entity via an ElAP signaling procedure, including the following parameters in one example: “Service Type”: Intelligent service, intelligent AI training for XR applications; “UP Processing Mode”: Split-in grouping; “UP Forwarding Mode”: TCP type.

[0091] After being configured by the first CP entity, the upstream UP entity determines whether to perform intelligent service or AI training tasks (e.g., AI training for XR applications) as instructed, can split-in group as instructed, and transmits some “intelligent service data” to the adjacent downstream UP entity to offload the intelligent AI training tasks. Likewise, the downstream UP entity determines whether to perform intelligent AI training tasks (e.g., AI training for XR applications) as instructed, will split-in group, and receive some “intelligent service data” from the adjacent upstream UP entity. After being configured by the first CP entity, the upstream UP entity establishes a “TCP type tunnel” with the adjacent downstream UP entity. Thereafter, the upstream UP entity and the downstream UP entity respectively perform the intelligent AI training tasks (e.g., AI training for XR applications), “intelligent service data” is transmitted via the established “TCP type tunnel”, and further processed by the downstream UP entity.

[0092] In a seventh embodiment as shown in Figure 7 , the CU entity communicates via an ElAP signaling procedure. In this example, the UP forwarding mode and tunnel type are QUICP. The service type is intelligent service, but with federated learning execution. The UP processing mode is connect-in grouping. The intelligent service used in this example can be associated with machine learning and / or artificial intelligence, including training features. This is just one example of parameters that can be configured.

[0093] Both the upstream UP entity and the downstream UP entity are capable of performing intelligent service or AI training tasks, e.g., performing federated learning. Due to sample data privacy requirements, the CP entity determines whether to let the upstream UP entity and the downstream UP entity jointly perform the intelligent AI training tasks. The upstream UP entity and the downstream UP entity can not transmit sample data to each other for data privacy protection considerations, so they use their own local sample data to obtain gradient information, which are then combined together by one node. Therefore, “intelligent service data” needs to be bidirectional for transmission between the upstream UP entity and the downstream UP entity via an appropriate type of forwarding tunnel.

[0094] As a control node, the CP entity configures the upstream UP entity and the downstream UP entity, respectively, via E1AP signaling procedures, including the following parameters in one example: “Service Type”: Intelligent service, joint learning application; “UP processing mode”: Connection entering packet; “UP forwarding mode”: QUIC type.

[0095] After being configured by the CP entity, the upstream UP entity determines whether to perform an intelligent service or an AI training task. In this example, the service / task includes a joint learning application. Connection entering packet can be connected, and gradient information as “intelligent service data” is transmitted / received to or from the adjacent downstream UP entity. Likewise, the downstream UP entity determines whether to perform an intelligent AI training task (e.g., joint learning application). Connection entering packet can be connected, and gradient information as “intelligent service data” is transmitted / received to or from the adjacent upstream UP entity. After being configured by the CP entity, the upstream UP entity establishes a “QUIC type tunnel” with the adjacent downstream UP entity. Thereafter, the upstream UP entity and the downstream UP entity perform an intelligent AI training task (e.g., joint learning application), respectively, and gradient information as “intelligent service data” is transmitted via the established “QUIC type tunnel” and further processed by the upstream UP entity or the downstream UP entity.

[0096] The following is a list of abbreviations:

[0097] Table 1 – Abbreviations.

[0098] The above systems and processes can be encoded in a signal-bearing medium, computer readable medium (e.g., memory), programmed in a device such as one or more integrated circuits, one or more processors, or the like, or handled by a controller or computer. The data can be analyzed in a computer system and used to generate a spectrum. If the method is performed by software, the software can reside in a memory resident on or connected to a storage device, a synchronizer, a communication interface, or in a non-volatile or volatile memory in communication with a transmitter. Circuitry or electronics are designed to send data to another location. The memory can include an ordered listing of executable instructions for implementing logical functions. The described logical functions or any system elements can be implemented by optical circuitry, digital circuitry, source code, analog circuitry, analog sources (e.g., analog electrical, audio, or video signals), or combinations thereof. The software can be contained in any computer-readable or signal-bearing medium for use by or in connection with an instruction-executable system, apparatus, or device. Such a system can include a computer-based system, a system containing a processor, or another system that can selectively fetch instructions from an instruction-executable system, apparatus, or device that can also execute instructions.

[0099] "Computer-readable medium," "machine-readable medium," "propagated-signal medium" and / or "signal bearing medium" can include any device, apparatus, or means including a storage device, communication device, or other device that is configured to store or transport software in the form of instructions or data structures. Machine-readable media can selectively be, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a propagating signal. A non-exhaustive list of examples of machine- readable media can include: electrical connection "electronic" having one or more wires, portable magnetic or optical disk, volatile memory, non-volatile memory, or fiber optics. Machine-readable media can also include tangible media upon which software is printed, as the software can be electronically stored, then compiled, and / or interpreted or otherwise processed in the form of an image or other format, for example, by an optical scanner or other form of electronic reader. The processed media can then be stored in a computer and / or machine memory.

[0100] The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of various embodiments. The illustrations are not intended to serve as a complete description of all the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments can be apparent to those of ordinary skill in the art upon reading this disclosure. Other embodiments can be derived from the practice of the embodiments described herein by a variety of means, including use of other structures and methods in addition to or in place of the structures and methods described herein. What has been described herein is merely illustrative of the application of the principles of the present disclosure. Other embodiments can be apparent to those of ordinary skill in the art upon reading this disclosure, and it will be understood that the scope of the disclosure is not limited to the described embodiments but extends to any other embodiments with in the scope and spirit of the claims.

[0101] One or more embodiments of the application can be referred to herein, individually and / or collectively, by the term "application" merely for convenience and without intending to voluntarily limit the scope of this application to any particular application or applications. Additionally, although specific embodiments have been shown and described herein, it is understood that a myriad of other arrangements of the application are possible that are not shown and described herein. The present disclosure is intended to cover any and all subsequent adaptations and modifications of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of ordinary skill in the art upon reading this disclosure. The scope of the application is limited only by the claims.

[0102] The phrase "coupled" is defined as directly connected to or indirectly connected through one or more intermediate components. Such intermediate components can include both hardware- and software-based components. Variations can be made in the arrangement and types of components without departing from the spirit or scope of the claims as set forth in this disclosure. Additionally, different or fewer components can be provided.

[0103] The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other implementations falling within the true spirit and scope of the application. Therefore, to the extent that there is inadvertent departure from the object and scope of the application, then such should not be precluded from the scope of the present application as set forth in the appended claims and their equivalents. While various embodiments of the present application have been described above, it should be understood that they have been presented by way of example only, and not limitation. Numerous changes to the disclosed embodiments can be made in accordance with the disclosure herein without departing from the spirit or scope of the application. Accordingly, the scope of the application is defined only by the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

1. A method of wireless communication, the method comprising: Comprise: configuring a network entity for user plane UP functionality; receiving the UP configuration.

2. The method of claim 1, wherein, The UP functionality comprises identifying traffic types, UP handling, and UP data forwarding.

3. The method of claim 2, wherein, The UP functionality supports traffic other than communication traffic, including at least computing, intelligence, storage, and / or security traffic.

4. The method of claim 1, wherein, The network entity comprises a user plane UP entity.

5. The method of claim 4, wherein, The configuration is by a control plane CP entity of the UP entity, wherein the UP configuration is received at the UP entity from the CP entity.

6. The method of claim 5, wherein, The configuration is by internal signaling or interface-based signaling.

7. The method of claim 1, wherein, The configuration comprises UP configuration of one or more user plane UP entities.

8. The method of claim 1, wherein, The configuration comprises configuration of traffic types, UP handling modes, or UP forwarding modes.

9. The method of claim 8, wherein, The traffic types, UP handling modes, or UP forwarding modes comprise predefined index identification or explicit indication.

10. The method of claim 1, wherein, The UP configuration is configured to allow data transfer traffic to terminate at an intermediate node rather than an end node.

11. The method of claim 10, wherein, The intermediate node is configured to forward user data of different traffic types to any other network node.

12. The method of claim 1, wherein, The configuration comprises configuration of handling modes, including at least: pass-through incoming packets; compressed incoming packets; connected incoming packets; split incoming packets; or locally backed-up packets.

13. The method of claim 1, wherein, The configuration comprises UP configuration of forwarding modes, including at least: protocol data unit PDU session types; data radio bearer DRB types; control plane CP signaling types; transmission control protocol TCP types; or quick user datagram protocol network connection QUIC types.

14. A wireless configuration method, comprising: The method comprises: establishing one or more user plane UP configurations for a network entity supporting different types of traffic; performing UP handling based on the received UP configuration.

15. The method of claim 14, wherein, The supported traffic includes communication traffic, computing traffic, intelligence traffic, storage traffic, or security traffic.

16. The method of claim 14, wherein, The network entity comprises a user plane UP entity for performing behavior according to UP configuration, wherein the establishing and configuring are by a control plane CP entity.

17. The method of claim 16, wherein, The UP configuration comprises configuration of one or more user plane UP entities.

18. The method of claim 14, wherein, The establishing is by internal signaling or interface-based signaling.

19. The method of claim 14, wherein, The UP configuration is for traffic types, UP handling modes, or UP forwarding modes.

20. The method of claim 19, wherein, The traffic types, UP handling modes, or UP forwarding modes comprise predefined index identification or explicit indication.

21. The method of claim 14, wherein, The UP configuration allows data transfer traffic to terminate at an intermediate node rather than an end node.

22. The method of claim 21, wherein, The intermediate node is configured to forward user data of different traffic types to any other network node.

23. The method of claim 14, wherein, The UP configuration is for handling modes, including at least: pass-through incoming packets; compressed incoming packets; connected incoming packets; split incoming packets; or locally backed-up packets.

24. The method of claim 14, wherein, The UP configuration is for forwarding modes, including at least: protocol data unit PDU session types; data radio bearer DRB types; control plane CP signaling types; transmission control protocol TCP types; or quick user datagram protocol network connection QUIC types.

25. The method of claim 14, wherein, When multiple services are configured simultaneously, the multiple sets of different UP configurations are applied simultaneously.

26. A wireless communication device, comprising: A computer program product comprising a computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 25.

27. A computer program product, characterised in that, A computer program product comprising a computer readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 25.

Images