USER PLAN PROCESSING AND DATA FORWARDING

Abstract

An extension of user plane (UP) processing and data forwarding functions include support for additional services. Rather than just communication, a configuration of UP functions may include support for services that include computing services, intelligence services, storage services, or security services.

Description

1 / 40 USER PLAN PROCESSING AND DATA FORWARDING CROSS-REFERENCE ON RELATED REQUEST

[001] This application is a continuation of International Patent Application PCT Number PCT / CN2023 / 100860, filed with the China National Intellectual Property Administration, PRC on June 16, 2023, which is incorporated herein by reference in its entirety. FIELD OF TECHNIQUE

[002] The present invention relates generally to wireless communications. More specifically, the user plane (UP) data processing and forwarding functions include support for additional services. BACKGROUND

[003] Wireless communication technologies are moving the world toward an increasingly connected and networked society. Wireless communications depend on efficient network resource management and allocation between mobile user stations and wireless access network nodes (including, but not limited to, radio access network (RAN) nodes and wireless base stations). A next-generation network is expected to provide high-speed, low-latency, and ultra-reliable communication capabilities, and meet the requirements of different industries and users. Mobile user stations or user equipment (UE) are becoming more complex, and the amount of data communicated is continuously increasing. With the development of more advanced radar and sensor systems, communications between UE can be modernized. SUMMARY

[004] This document refers to methods, systems and devices Petition 870250083397, dated 09 / 16 / 2025, pp. 64 / 112 2 / 40 vos for an extension of user plane (UP) data processing and forwarding functions, which include support for additional services. Instead of just an end-to-end (E2E) communication service, a UP functions configuration can include support for services that include communication services, computing services, intelligence services, storage services, or security services, etc.

[005] In one embodiment, a method for wireless communication includes configuring a network entity for user plane (UP) functions; and receiving the configuration. The UP functions comprise identifying the service type, UP processing, and UP data forwarding. The UP functions support services beyond a communication service, including at least computing, intelligence, storage, and / or security services. The network entity comprises a user plane (UP) entity. The configuration is made by a control plane (CP) entity to the UP entity, and the configuration is received by the UP entity from the CP entity. The configuration is via internal signaling or interface-based signaling. The configuration comprises the configuration of one or more user plane (UP) entities. The configuration comprises the configuration of a service type, UP processing mode, or UP forwarding mode.The service type, UP processing mode, or UP forwarding mode comprises an index identifier or explicit indication that is predefined. The configuration is set to allow a data transfer service to terminate 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 configuration includes the configuration of processing modes, where the modes of... Petition 870250083397, dated 09 / 16 / 2025, pages 65 / 112 3 / 40 processing at least includes: transparent delivery of received packets; compression of received packets; concatenation of received packets; segmentation of received packets; or local backup of packets. Configuration includes configuration of forwarding modes, wherein forwarding modes at least include: PDU session type; DRB type; control plane (CP) signaling type; TCP type; or QUIC type.

[006] In another embodiment, a method for wireless configuration includes establishing a user plane (UP) configuration for a network entity to support different types of services; and performing UP processing based on receiving the UP configuration. The supported services comprise communication services, computing services, intelligence services, storage services, or security services. The network entity comprises a user plane (UP) entity to perform behaviors according to the UP configuration, wherein the establishment and configuration are by a control plane (CP) entity. The UP configuration comprises a configuration of one or more user plane (UP) entities. The establishment is through internal signaling or interface-based signaling. The UP configuration is for a service type, UP processing mode, or UP forwarding mode.The service type, UP processing mode, or UP forwarding mode comprises an index identifier or explicit indication that is predefined. The UP configuration allows a data transfer service to terminate 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 processing modes, where the processing modes at least comprise: en. Petition 870250083397, dated 09 / 16 / 2025, pp. 66 / 112 4 / 40 Transparent delivery of received packets; compression of received packets; concatenation of received packets; segmentation of received packets; or local packet backup. The UP configuration is for forwarding modes, where the forwarding modes at least comprise: PDU session type; DRB type; control plane (CP) signaling type; TCP type; or QUIC type.

[007] In another embodiment, a wireless communications device includes a processor and a memory, wherein the processor is configured to read code from memory and implement any method described herein.

[008] In another embodiment, a computer program product includes a computer-readable program medium code stored therein, the code, when executed by a processor, causing the processor to implement any method described herein.

[009] In some embodiments, there is a wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from memory and implement any methods recited in any of the embodiments. In some embodiments, a computer program product comprises a computer-readable program medium code stored therein, the code, when executed by a processor, causing the processor to implement any method recited in any of the embodiments. The above and other aspects and their implementations are described in greater detail in the drawings, descriptions and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 shows an exemplary base station.

[0011] Figure 2 shows an access message environment. Petition 870250083397, dated 09 / 16 / 2025, pp. 67 / 112 5 / 40 random (RA) exemplary.

[0012] Figure 3 shows a single-connectivity wireless communication system.

[0013] Figure 4 shows a single-connectivity wireless communication system with a split case.

[0014] Figure 5 shows one embodiment of a wireless network system architecture.

[0015] Figure 6 shows user plane (UP) processing and data forwarding.

[0016] Figure 7 shows a single base station system diagram with user plane (UP) processing and extended data forwarding.

[0017] Figure 8 shows a dual base station system diagram with user plane (UP) processing and extended data forwarding.

[0018] Figure 9 shows protocol stacks for different user plane processing (UP) forwarding modes. DETAILED DESCRIPTION OF THE INVENTION

[0019] The present description will now be described in detail hereafter with reference to the accompanying drawings, which form a part of the present description and which show, by way of illustration, specific examples of embodiments. Note that the present description may, however, be incorporated in a variety of different forms and, therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any of the embodiments to be presented below.

[0020] Throughout the specification and claims, terms may have different meanings, suggested or implied in the context, in addition to an explicitly stated meaning. Similarly, the sentence in one embodiment or in some embodiments, Petition 870250083397, dated 09 / 16 / 2025, pp. 68 / 112 6 / 40 as used herein does not necessarily refer to the same embodiment, and the phrase in another embodiment or in other embodiments, as used herein, does not necessarily refer to a different embodiment. The phrase in one implementation or in some implementations, as used herein, does not necessarily refer to the same implementation, and the phrase in another implementation or in other implementations, as used herein, does not necessarily refer to a different implementation. It is intended, for example, that the claimed subject matter includes combinations of exemplary embodiments or implementations, in whole or in part.

[0021] In general, terminology can be understood, at least in part, from its use in context. For example, terms such as and, or, or and / or, as used herein, can encompass a variety of meanings that may depend, at least in part, on the context in which such terms are used. Typically, or, if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, used here in an inclusive sense, as well as A, B, or C, used here in an exclusive sense. Furthermore, the term one or more or at least one, as used herein, depending, at least in part, on the context, can be used to describe any aspect, structure, or feature in a singular sense or can be used to describe combinations of aspects, structures, or features in a plural sense.Similarly, terms such as a, an, or the, again, can be understood to convey a singular usage or to convey a plural usage, depending, at least in part, on the context. Furthermore, the term based on or determined by can be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for the existence of additional factors not necessarily expressly described, again, depending at least on. Petition 870250083397, dated 09 / 16 / 2025, pp. 69 / 112 7 / 40th part, of the context.

[0022] Radio Resource Control (RRC) is a protocol layer between the UE and the base station at the IP level (Radio Network Layer). There can be several Radio Resource Control (RRC) states, such as a connected RRC state (RRC_CONNECTED), inactive RRC state (RRC_INACTIVE), and idle RRC state (RRC_IDLE). RRC messages are transported via the Packet Data Convergence Protocol (PDCP). The UE can transmit infrequent data (periodic and / or non-periodic) in the RRC_INACTIVE state without moving to an RRC_CONNECTED state. This can save power consumption and signaling overhead on the UE. This can be done via a Random Access Channel (RACH) protocol scheme or a Configured Lease (CG) scheme. The wireless communications described here can be via radio access.Figures 1-2 show exemplary radio access network (RAN) nodes (e.g., base stations) and user equipment and messaging environments, which may be applicable to the user plane (UP) functions and communications described below.

[0023] With the most recent development of wireless communication systems (e.g., 5G-NR and 6G wireless systems), along with various distributed computing, intelligence, storage, and security systems, integration can be a challenge. Integration with each other can be in terms of architecture or capacity, or uses of network resources and air interface, etc. 5G-Advanced (5G-A) and 6G wireless systems may attempt to integrate various new functions and services with pre-existing systems, including, but not limited to, computing services, intelligence services, storage services, and / or security systems. As a result, core network (CN) and RAN nodes may not be able to handle them. Petition 870250083397, dated 09 / 16 / 2025, p. 70 / 112 8 / 40 not only provide a wireless communication service, but also provide computing services, intelligence services, storage services and / or security services, etc.

[0024] User plane (UP) data processing and forwarding functions can be used to process and transfer user data associated with different mobile user services, such as mobile apps and web services. As a result, UP data processing and forwarding functions on a network node may not be concerned with the type / content or characteristics of the user data. Instead, it can process and forward them from the input port to the output port based on the internal UP processing unit. As described below, additional service data types can be processed and transferred based on an extension of the UP data processing and forwarding functions. This extension can cover different service types.The wireless network node can distinguish different types of service data and adopt different approach and processing strategies for different types of service data processing and forwarding, so that the goal of network interface resource efficiency can be achieved.

[0025] Figure 1 shows an exemplary RAN node or base station 102. The RAN node may also be referred to as a wireless network node. The RAN node 102 may also be identified as a nodeB (NB, for example, an eNB or gNB) in the context of mobile telecommunications. The exemplary RAN node may include a radio Tx / Rx circuit 113 for receiving and transmitting with user equipment (UEs) 104. The RAN node may also include a network interface circuit 116 for coupling the RAN node to the core network 110, for example, optical or wired interconnects, Ethernet and / or other data transmission means / protocols. Petition 870250083397, dated 09 / 16 / 2025, pp. 71 / 112 9 / 40

[0026] The RAN node may also include system circuits 122. System circuits 122 may include processor(s) 124 and / or memory 126. Memory 126 may include operations 128 and control parameters 130. Operations 128 may include instructions for execution on one or more of the processors 124 to support the operation of the RAN node. For example, operations may handle random access transmission requests from multiple UEs. Control parameters 130 may include parameters or support the execution of operations 128. For example, control parameters may include network protocol settings, random access message format rules, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0027] Figure 2 shows an exemplary random access messaging environment 200. In the random access messaging environment, a UE 104 can communicate with a RAN node 102 through a 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 the rest of the user equipment hardware, for example, through the system bus 210.

[0028] Mobile device 200 includes communication interfaces 212, system logic 214, and a user interface 218. System logic 214 may include any combination of hardware, software, firmware, or other logic. System logic 214 may 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. System logic 214 is part of the implementation of any desired functionality in UE 104. In this respect, system logic 214 may include logic that facilitates, Petition 870250083397, dated 09 / 16 / 2025, pp. 72 / 112 10 / 40 as examples, decoding and playing music and video, for example, MP3, MP4, MPEG, AVI, FLAC, AC3 or WAV; running applications; accepting user input; saving and retrieving application data; establishing, maintaining and terminating cellular phone calls or data connections for, for example, 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 the inputs 228 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements.Additional examples of 228 inputs include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output connectors, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0029] The system logic 214 may include one or more processors 216 and memories 220. The memory 220 stores, for example, control instructions 222 that the processor 216 executes to perform the desired functionality for the UE 104. The control parameters 224 provide and specify configuration and operation options for the control instructions 222. The memory 220 may also store any BT, WiFi, 3G, 4G, 5G or other data 226 that the UE 104 will send or receive through the communication interfaces 212. In various implementations, system power may be supplied by an energy storage device, such as a battery 282. Petition 870250083397, dated 09 / 16 / 2025, pp. 73 / 112 11 / 40

[0030] In communication interfaces 212, the radio frequency (RF) transmission (Tx) and reception (Rx) circuit 230 controls the transmission and reception of signals through one or more antennas 232. The communication interface 212 may include one or more transceivers. Transceivers may be wireless transceivers that include modulation / demodulation circuits, digital-to-analog converters (DACs), modeling tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers and / or other logic for transmission and reception through one or more antennas, or (for some devices) through a physical medium (e.g., fixed network).

[0031] Transmitted and received signals may adhere to any of a diverse range of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interfaces 212 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunication System (UMTS), High-Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. The techniques described below, however, are applicable to other wireless communication technologies, whether these originate from the 3GPP Partnership Project, the GSM Association, 3GPP2, IEEE, or other partnerships or standardization bodies.

[0032] Figure 3 shows a single-connectivity wireless communication system. Single connectivity (SC) can include a UE that only has a master radio connection (M-RL), but no radio connection on the secondary RAN node side. On the other hand, dual connectivity (DC) includes a UE with a secondary communication radio connection (S-RL) on the secondary RAN node side. In IMT wireless communication systems (such as 4G-LTE and 5G) Petition 870250083397, dated 09 / 16 / 2025, pp. 74 / 112 12 / 40 As shown in Figure 3, the Radio Access Network (RAN) node can transmit downlink (DL) pilot reference signals, such as SSB, CSI-RS, etc. The UE receives, measures, and processes these signals so that the UE can determine the radio connection quality (RL) over the air. This can be the communication between the server RAN node and the UE, in order to maintain continuity of communication service. This is an example with single connectivity (SC).

[0033] Figure 4 shows a split-case single-connectivity wireless communication system. Figure 3 shows a non-split case, while Figure 4 illustrates a split CU-CP node and a split CU-UP node. In IMT wireless communication systems (such as 5GNR specified by 3GPP), as shown in Figures 3-4, the Core Network (CN) can include several types of control plane (CP) nodes or entities (e.g., 5G AMF / SMF) and one user plane (UP) node or entity (e.g., 5G UPF). In the non-split RAN case in Figure 3, the RAN node (e.g., 5G aggregated base station) includes a CP portion and a UP portion and then terminates in the UE via an over-the-air radio connection (RL). In the split RAN case of Figure 4, the RAN node (e.g., 5G disaggregated base station) includes a CU-CP node, a CU-UP node, and a DU node or entities, and then terminates in the UE via an air RL.The CP node may be responsible for generating, processing, and transferring control signaling (e.g., to (re)configure and monitor other nodes). The UP node is responsible for processing and transferring user data (e.g., associated with mobile apps and web services, etc.). For both the CP and UP planes, there may be a separate interface and protocol stack, typically extending from the CN domain to the RAN network and then to the UE. The UP functions are further described below and can be implemented in the systems shown in the diagrams. Petition 870250083397, dated 09 / 16 / 2025, pp. 75 / 112 13 / 40 Figures 1-2 or in the system described in Figure 5 below.

[0034] Figure 5 shows one embodiment of a wireless network system architecture. This architecture is merely an example, and there may be more or fewer components to implement the embodiments described herein. The interconnections or communications between the components are identified as N1, N2, N4, N6, N7, N8, N10, and N11, which may be referred to in the description or in other figures. Figure 2 illustrates an exemplary user equipment (UE) 104. The UE 502 is a device that accesses a wireless network (e.g., 5GS) and obtains service through an NG-RAN node or base station 504. The UE 502 interacts with an Access Control and Mobility Function (AMF) 506 of the core network via NAS signaling. Figure 1 illustrates an exemplary base station or NG-RAN 102. The NG-RAN 504 node is responsible for scheduling air interface resources and managing the air interface connection of the network to which the UE accesses.The AMF 506 includes the following functionalities: registration management, connection management, accessibility management, and mobility management. The AMF 506 also performs access authentication and access authorization. The AMF 506 is the NAS security endpoint and relays the NAS session management between the UE 502 and SMF 508, etc.

[0035] The SMF 508 includes the following functionalities: session management, for example, session establishment, modification and release, EU IP address allocation & management (including optional authorization), uplink function selection and control, downlink data notification, etc. The User Plane Function (UPF) 510 includes the following functionalities: anchoring point for intra / inter-RAT mobility, packet routing and forwarding, traffic utilization reports, QoS handling for the user plane, temporary storage of downlink packets and Petition 870250083397, dated 09 / 16 / 2025, pp. 76 / 112 14 / 40 triggering of downlink data notification, etc. Unified Data Management (UDM) 512 manages the subscription profile for UEs. The subscription includes data used for mobility management (e.g., sandboxing), session management (e.g., QoS profile). Subscription data also includes slice selection parameters, which are used by AMF 506 to select an appropriate SMF 508. AMF 506 and SMF 508 obtain the subscription from UDM 512. Subscription data can be stored in a Unified Data Repository with UDM 512, which uses this data when receiving a request from AMF 506 or SMF 508.The Policy Control Function (PCF) 514 includes the following functionalities: support for a unified policy framework to govern network behavior, provision of policy rules for control plane function(s) to enforce policy rules, and implementation of an initial interface to access subscription information relevant to policy decisions in the User Data Store. The Network Exposure Function (NEF) 516 is optionally deployed for information exchange with an external third party. In one embodiment, an Application Function (AF) 516 can store application information in the Unified Data Store via the NEF. The UPF 510 communicates with the data network 518.

[0036] The Access Mobility Function (AMF) and the Function of Session Management (SMF) refers to the control plane entities, and User Plane Function (UPF) is the user plane entity in the new radio (NR) or 5GC. The signaling connection between AMF / SMF and MN can be a Next Generation Control Plane (NG-C) / MN interface. The signaling connection between MN and SN can be an Xn Control Plane (Xn-C) interface. The signaling connection between MN and UE can be an RRC interface. Petition 870250083397, dated 09 / 16 / 2025, pp. 77 / 112 15 / 40 Uu Control Plane (Uu-C). As described below, there may be additional components or entities for UP processing and data routing functions.

[0037] Figure 6 shows user plane (UP) processing and data forwarding in an example. Either the UP part integrated into the network node or the UP node as a separate network node can be (re)configured by the CP part or CP node, with UP processing strategies and various protocol parameters. As soon as the UP part or UP node obtains incoming user data (i.e., DL / UL packet streams), they process it accordingly based on the CP configurations and then forward / forward it to the next UP part or UP node in the sequence. Without the additional functions, in pre-existing wireless communication systems (such as 4G-LTE and 5G-NR), user data can always be terminated at a specific UE in the DL direction or at a data network server in the UL direction; therefore, it is always an end-to-end (E2E) communication service that serves only to transfer user data.The mechanism for UP processing and data forwarding is shown in Figure 6. In the modalities below, there are additional functions / services for UP processing and data forwarding.

[0038] In some modes, the UP functions (for example, (UP and data forwarding) are used for various services, instead of just the E2E communication service, as was the standard. Similarly, services are more than just transferring user data from the UE (i.e., data associated with the UE) to the end nodes. Instead, user data transfer can now be terminated at any intermediate network node, in addition to the UE or the network server / data DN.

[0039] In some forms, the intermediate node or entity Petition 870250083397, dated 09 / 16 / 2025, pp. 78 / 112 16 / 40 network nodes (e.g., 5G UPF, part of CU-UP and DU-UP) can both trigger and initiate UP functions themselves. This can occur without requiring user input data from an upstream or downstream node. For data generated by the intermediate network node, its transfer can be based on the current UP function or on tunnels.

[0040] In some embodiments, the intermediate network node can dynamically process and then forward user data to upstream or downstream target nodes. The target may not be static based on 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 an UP transfer path and is capable of being dynamic or adjusted, rather than static / fixed.

[0041] In some embodiments, for any given UP entity, the UP processing mode, the forwarding mode and their respective interface protocol stacks may be used for different services, rather than being required only to forward any user data from any UE, regardless of different traffic characteristics. SERVICES

[0042] As mentioned, extended / expanded services, in addition to E2E communication, may include computing services, intelligence services, storage services, and / or security services, etc. The resources of these services can be integrated into wireless communication systems. Various data from different service types can be processed and forwarded during their distributed service operations. The traffic characteristics with these services may flow differently from the pre-existing E2E communication service. Exemplary differences include data generator and size. Petition 870250083397, dated 09 / 16 / 2025, pp. 79 / 112 17 / 40 / frequency / packet period, etc. As described in the modalities here, there may be changes to the UP mechanism to incorporate additional services / functions. This may be referred to as an extension or extended functions of UP processing and data routing.

[0043] Figure 7 shows a single base station system diagram with extended user plane (UP) processing and data routing. This diagram is a centralized model for extending the use of UP processing and data routing functions. The single base station has a single CP entity in one mode. Although the CP entity and the UP entity are shown separately, they can be physically joined. There can be several blocks in the UP entity, including routing modes and processing modes. The pre-existing UP entity (for communication only) does not have as many modes as we have here. The CP entity can configure the appropriate UP processing mode and / or UP routing mode. Extending the UP entity's function includes providing additional services (beyond communication).

[0044] The following are terms relevant to the extension of other UP functions:

[0045] · CP entity: refers to the part of the control plane (CP) integrated into a certain network node or dedicated CP node as a separate network node.

[0046] · UP entity: refers to the user plan (UP) portion integrated into a certain network node or dedicated UP node as a separate network node.

[0047] · UP functions: refers to user plane (UP) packet processing, data forwarding, and the related UP interface protocol stack. Petition 870250083397, dated 09 / 16 / 2025, pages 80 / 112 18 / 40

[0048] · Communication Service Data: user data generated by the data network server or by the UE, associated with certain E2E communication services.

[0049] · Computing Service Data: intermediate data generated by any network node, associated with certain computing services.

[0050] · Intelligence Service Data: intermediate data generated by any network node, associated with certain intelligence services.

[0051] • Storage Service Data: intermediate data generated by any network node, associated with certain storage services.

[0052] • Security Service Data: intermediate data generated by any network node, associated with certain security services.

[0053] · Multi-Service Node: a network node capable of multiple types of services other than the pre-existing E2E communication service alone.

[0054] • Service Type: at least refers to additional services, including but not limited to: communication, computing, intelligence, storage, and security services supported by the network.

[0055] • UP Processing Mode: the way in which the UP entity processes the input data of a certain service type.

[0056] · UP Routing Mode: the way in which the UP entity routes the output data of a certain type of service.

[0057] · UP configuration: the settings and configurations of Type of Service, UP Processing Mode, UP Routing Mode, and other parameters related to the UP function.

[0058] Figure 8 shows a station system diagram of Petition 870250083397, dated 09 / 16 / 2025, pp. 81 / 112 19 / 40 dual base with extended user plane (UP) processing and data forwarding. As in Figure 7, the diagram is a decentralized model for extending the use of UP data processing and forwarding functions. As shown, there can be two separate base stations, each with a CP entity. In this example, Xn signaling can exist between CP entities. For the split base station, the CP entity and the UP entity can be physically separated.

[0059] Referring to Figure 7 or Figure 8, the following are characteristics of the UP function extension. The CP entity can configure one or more UP entities with parameters such as Service Type, UP Processing Mode, and UP Routing Mode through internal signaling or interface-based signaling. The content of the parameters: Service Type, UP Processing Mode, and UP Routing Mode can take the form of an index ID or explicit indication. The meaning of each index ID or indication can be predefined by normative specifications. The UP configuration configured by the CP entity can be adapted to different types of services, such as the communication, computing, intelligence, storage, and / or security services described herein.To decouple from existing parameters similar to Service Type, UP Processing Mode, and UP Routing Mode, new parameters may exist, including but not limited to: New Service Type, New UP Processing Mode, and New UP Routing Mode, which may be additionally defined and used instead.

[0060] The two neighboring CP entities can synchronize the contents of Service Type, UP Processing Mode and UP Routing Mode, etc., through base signaling. Petition 870250083397, dated 09 / 16 / 2025, pp. 82-112 20 / 40 ada in interface, so that the handling of UP in neighboring UP entities can be synchronized or adapted to each other.

[0061] The Multi-Service Node is capable of supporting multiple services, such as communication, computing, intelligence, storage and / or security services described herein, and is capable of supporting one or multiple UP Processing Modes and UP Forwarding Modes, as well as multiple relative interface protocol stacks described below with respect to Figure 9.

[0062] UP Processing Modes may include at least: transparent delivery of received packets, compression of received packets, concatenation of received packets, segmentation of received packets and / or local backup of packets, etc. UP Forwarding Modes may include at least: PDU Session type, DRB type, CP Signaling type, TCP type, QUIC type, etc. Furthermore, their relative interface protocol stacks are shown in Figure 9.

[0063] Figure 9 shows protocol stacks for different user plane routing (UP) modes. Examples of different UP Routing Modes and corresponding protocol stacks are shown. These protocols are merely examples that can be used for various services. NG uses session PDU. QUIC can be a combination of TCP and PDU. New UP functions may support at least these protocol stacks, but there may be additional protocol stacks that will be supported in the future. As described, the protocol stack that is supported can be configured as part of the UP function extension. This configuration allows support for multiple protocol stacks.

[0064] After configuration by the controlling CP entity, the UP entity in the Multiple Service Node performs the UP processing and corresponding UP data forwarding activities. Petition 870250083397, dated 09 / 16 / 2025, pp. 83 / 112 21 / 40 teeth, as configured. The two neighboring UP entities can exchange different types of service data through different types of UP Routing Modes or relative UP interface protocol stacks, based on different types of data transfer tunnels configured by the CP entity.

[0065] As described and shown in Figures 7-8, the configuration can include the Service Type, the UP Processing Mode, and / or the UP Forwarding Mode. Due to the configurability provided, any of these types / modes can be varied. Furthermore, the tunnel type between CU-UPs and the signaling procedure with the CP (and between CPs for Figure 8) can also be varied. When multiple services are simultaneously configured, different tunnel types can be established and coexist between the same CUUPs in question, and any combination is possible for these configurable parameters. Below are exemplary embodiments describing specific combinations of these configurable parameters. These are merely examples, and many other combinations are possible in other examples.

[0066] In a first mode, as in Figure 7, the CU entity communicates through the E1AP signaling procedure. The tunnel type is the PDU session. For this example, the Service Type is compute service, deep packet inspection (DPI) operation, the UP Processing Mode is received packet compression, and the UP Forwarding Mode is the PDU Session Type. This is merely an example of the parameters that can be configured.

[0067] UP entities are capable of performing certain types of computing tasks, for example, running a specific DPI algorithm for received packets. Due to a lack of local computing resources or to obtain better analysis results of Petition 870250083397, dated 09 / 16 / 2025, pp. 84 / 112 22 / 40 In DPI, the CP entity can allow the upstream UP entity and the downstream UP entity to perform the computation task together. For example, the upstream UP entity performs the DPI operation for some of the odd-numbered QoS flow packets, and the downstream UP entity performs the DPI operation for some of the even-numbered QoS flow packets, in one example. Compute Service Data is transferred from the upstream UP entity to the downstream UP entity through a type of routing tunnel.

[0068] As the control node, the CP entity configures the upstream UP entity and the downstream UP entity individually through the E1AP signaling procedure, which includes the following parameters:

[0069] Type of Service: computing service, operation of DPI,

[0070] UP Processing Mode: compression of received packets and

[0071] UP Routing Mode: Session Type PDU.

[0072] After configuration by the CP entity, the entity of The upstream UP entity performs a computation task as indicated (e.g., DPI operation) and should compress the received QoS Flow packets as indicated. Furthermore, it may transfer some of the Computation Service Data (e.g., user data packet) to the neighboring downstream UP entity to offload the computation task. Similarly, the downstream UP entity knows it will perform a type of computation task as indicated (e.g., DPI operation) and may compress the incoming QoS Flow packets as indicated and receive some of the Computation Service Data from the upstream UP entity. Petition 870250083397, dated 09 / 16 / 2025, page 85 / 112 23 / 40 neighbor. After configuration by the CP entity, the upstream UP entity can establish the PDU Session Type Tunnel with the neighboring downstream UP entity. Subsequently, the upstream UP entity and the downstream UP entity individually perform the computation task as indicated (e.g., DPI operation), and the Computation Service Data is transferred through the established PDU Session Type Tunnel and subsequently processed by the downstream UP entity.

[0073] In a second mode, multiple CU entities can exist, as in Figure 8. This differs from mode 1 due to the multiple CU entities and because the tunnel type and forwarding mode are DRB. The CU entities communicate through an Xn interface. For this example, the Service Type is a compute service, deep packet inspection (DPI) operation, the UP Processing Mode is received packet compression, and the UP Forwarding Mode is DRB Type. This is merely an example of the parameters that can be configured.

[0074] A CP entity is connecting with the entity of Upstream UP, and the other CP entity is connecting to the downstream UP entity through the standardized E1 interface. The neighboring upstream UP entity and downstream UP entity are both capable of performing a certain type of computation task (e.g., executing a specific DPI algorithm) towards the received packets. Due to a lack of local computing power resources or in order to obtain better DPI analysis results, a CP entity decides to allow the upstream UP entity and the downstream UP entity connected to the other CP entity to perform the computation task jointly. In one example, the upstream UP entity performs the DPI operation towards some of the odd-numbered QoS flow packets, and the downstream UP entity performs Petition 870250083397, dated 09 / 16 / 2025, page 86 / 112 24 / 40 DPI operation towards some of the even-numbered QoS flow packets. Computing Service Data can be transferred from the upstream UP entity to the downstream UP entity through an appropriate type of routing tunnel.

[0075] As the control node, the first CP entity configures the upstream UP entity through the E1AP signaling procedure, which includes the following parameters in this example:

[0076] Service Type: computing service, operation of DPI,

[0077] UP Processing Mode: compression of received packets,

[0078] UP Routing Mode: DRB Type.

[0079] The first CP entity transmits the configuration parameters to the other CP entity via the Xn signaling procedure. Then, the second / other CP entity configures the downstream UP entity via the E1AP signaling procedure, which includes the following parameters in this example:

[0080] Type of Service: computing service, operation of DPI,

[0081] UP Processing Mode: compression of received packets,

[0082] UP Routing Mode: DRB Type.

[0083] After configuration by the first CP entity, the upstream UP entity determines whether to execute the computation task as indicated (e.g., DPI operation) and may compress the received QoS flow packets. It may transfer some of the Computation Service Data towards the neighboring downstream UP entity to offload the computation task. Similarly, the downstream UP entity determines whether to execute the computation task as indicated (e.g., DPI operation). This po Petition 870250083397, dated 09 / 16 / 2025, page 87 / 112 25 / 40 of compressing the received QoS flow packets as indicated and receiving some of the Compute Service Data from the neighboring upstream UP entity. After configuration by the first CP entity, the upstream UP entity can establish the DRB Type Tunnel with the neighboring downstream UP entity, as indicated. Subsequently, the upstream UP entity and the downstream UP entity individually perform the compute task as indicated (e.g., DPI operation), and the Compute Service Data is transferred through the established DRB Type Tunnel and subsequently processed by the downstream UP entity.

[0084] In a third mode, as in Figure 7, the CU entity communicates via the E1AP signaling procedure. The tunnel type is DRB. For this example, the Service Type is an intelligence service. The UP Processing Mode is for local packet backup, and the UP Forwarding Mode is DRB. This is merely an example of the parameters that can be configured. The intelligent service used in this example may be associated with machine learning and / or artificial intelligence, including a training feature. Multiple UPs can transfer tasks between each other. This is merely an example of the parameters that can be configured.

[0085] The CP entity is connecting to two neighboring base station UPs via an E1 interface. The upstream UP entity and the downstream UP entity are both capable of performing intelligence service and backup tasks (e.g., running a specific AI Training operation with received packets). Due to the accuracy and reliability requirements of AI training, the CP entity may allow the upstream UP entity and the downstream UP entity to perform the task together. For example, the upstream UP entity performs an opera Petition 870250083397, dated 09 / 16 / 2025, pp. 88 / 112 26 / 40 compression is applied to received packets to collect statistics on packet delay and jitter, then transmitted to the downstream UP entity. The downstream UP entity performs a local backup operation to save sample data for future AI training. Intelligence Service Data needs to be transferred from the upstream UP entity to the downstream UP entity via the appropriate type of routing tunnel.

[0086] As the control node, the CP entity configures the upstream UP entity and the downstream UP entity individually through the E1AP signaling procedure. The following parameters are configured for the upstream UP entity in an example:

[0087] Type of Service: Intelligence service with AI training,

[0088] UP Processing Mode: compression of received packets,

[0089] UP Routing Mode: DRB Type.

[0090] The following parameters are configured for the downstream UP entity in an example:

[0091] Type of Service: Intelligence service with AI training,

[0092] UP Processing Mode: Local backup of received packets,

[0093] UP Routing Mode: DRB Type.

[0094] After configuration by the CP entity, the entity of The upstream UP determines whether to execute the intelligence task as directed (e.g., AI training for vertical industrial application). This may compress the received packets as directed and transfer some of the sample data towards the neighboring downstream UP entity for Intelligence Service Data. From the same Petition 870250083397, dated 09 / 16 / 2025, pp. 89 / 112 In mode 27 / 40, the downstream UP entity determines whether to perform the backup task as indicated (e.g., AI training for vertical industrial application) and must back up the received packets as indicated. This entity may receive some of the Intelligence Service Data from the neighboring upstream UP entity. After configuration by the CP entity, the upstream UP entity must establish the DRB Type Tunnel with the neighboring downstream UP entity, as indicated. Subsequently, the upstream UP entity and the downstream UP entity individually perform the intelligence AI training and backup task as indicated (e.g., for vertical industrial application), and the Intelligence Service Data is transferred through the established DRB Type Tunnel and subsequently processed by the downstream UP entity.

[0095] In a fourth mode, multiple CU entities may exist, as in Figure 8. This differs from mode 3 due to the multiple CU entities. The tunnel type and routing mode are DRB. The CU entities communicate through an Xn interface. For this example, the Service Type is intelligence service. The UP Processing Mode is different for the two UP entities, being local backup packets for the downstream UP entity and compression of received packets for the upstream UP entity. This is merely an example of the parameters that can be configured.

[0096] As shown in Figure 8, two CP entities are connected to each other via a standardized Xn interface. A first CP entity is connecting to the upstream UP entity, and a second CP entity is connecting to the downstream UP entity via a standardized E1 interface. The upstream UP entity and the downstream UP entity are both capable of performing the AI ​​intelligence or training service and task. Petition 870250083397, dated 09 / 16 / 2025, pp. 90-112 28 / 40 backup (e.g., running AI Training with received packets). Due to the accuracy and reliability requirements of AI Training, the CP entity determines whether to allow the upstream UP entity and the downstream UP entity to perform the task together. In this example, the upstream UP entity performs the compression operation towards received packets to collect statistics on packet delay and jitter, then transmits the packets to the downstream UP entity and performs the local backup operation to save sample data for future training. Intelligence Service Data can be transferred from the upstream UP entity to the downstream UP entity via the appropriate type of routing tunnel.

[0097] As the control node, the first CP entity can configure the upstream UP entity via the E1AP signaling procedure. This might include the following parameters in an example:

[0098] Service Type: Intelligence service, AI training for vertical industrial application,

[0099] UP Processing Mode: compression of received packets,

[00100] UP Routing Mode: DRB Type.

[00101] The first CP entity transmits the configuration parameters to the second CP entity via the Xn signaling procedure. Then, the second CP entity configures the downstream UP entity via the E1AP signaling procedure, which includes the following parameters in an example:

[00102] Service Type: Intelligence Service, AI training for vertical industrial application,

[00103] UP Processing Mode: local backup of received packets, Petition 870250083397, dated 09 / 16 / 2025, pages 91 / 112 29 / 40

[00104] UP Routing Mode: DRB Type.

[00105] After configuration by the first CP entity, the upstream UP entity becomes aware that it will perform the AI ​​intelligence training task as indicated (e.g., AI training for vertical industrial application), and may compress the received packets as indicated and transfer some of the sample data to the neighboring downstream UP entity for Intelligence Service Data. Similarly, the downstream UP entity determines whether to perform the backup task as indicated (e.g., AI training for vertical industrial application), and may back up the received packets as indicated. It may receive some of the Intelligence Service Data from the neighboring upstream UP entity. After configuration by the first CP entity, the upstream UP entity must establish the DRB Type Tunnel with the neighboring downstream UP entity, as indicated.Subsequently, the upstream UP entity and the downstream UP entity individually perform the intelligence AI training and backup task as indicated (e.g., AI training for vertical industrial application), and the Intelligence Service Data is transferred through the established DRB Type Tunnel and subsequently processed by the downstream UP entity.

[00106] In a fifth mode, as in Figure 7, the CU entity communicates through the E1AP signaling procedure. The forwarding mode and UP tunnel type are TCP, and the Service Type is an intelligence service. In this example, the UP Processing Mode is to segment the received packets. Segmenting the received packets can allow for different training. The intelligent service used in this example may be associated with machine learning and / or artificial intelligence, including a training feature. This is merely one example of the parameters. Petition 870250083397, dated 09 / 16 / 2025, pages 92 / 112 30 / 40 meters that can be configured.

[00107] The CP entity is connecting with two neighboring UP entities via an E1 interface. The upstream UP entity and the downstream UP entity are both capable of performing the intelligence service or AI training task (e.g., performing a specific segmentation operation towards received packets for XR services). Due to computing power limitations and user experience requirements, the CP entity determines whether to allow the upstream UP entity and the downstream UP entity to perform the intelligence AI training task jointly (e.g., the upstream UP entity can split video and voice-related data and perform the segmentation operation towards video-related packets for AI codec training). The downstream UP entity performs the segmentation operation towards voice-related packets for AI codec training.Intelligence Service Data can be transferred from the upstream UP entity to the downstream UP entity via the appropriate type of routing tunnel.

[00108] As the control node, the CP entity configures the upstream UP entity and the downstream UP entity individually through the E1AP signaling procedure, which includes the following parameters in an example:

[00109] Service Type: intelligence service, AI codec training for XR application,

[00110] UP Processing Mode: segmentation of received packets,

[00111] UP Forwarding Mode: TCP type.

[00112] After configuration by the CP entity, the upstream UP entity determines whether to execute the AI ​​intelligence training task as indicated (e.g., AI codec training). Petition 870250083397, dated 09 / 16 / 2025, pp. 93 / 112 31 / 40 for XR application). This can segment the received packets as indicated and transfer some of the Intelligence Service Data towards the neighboring downstream UP entity to offload the AI ​​training task. Similarly, the downstream UP entity determines whether to execute the intelligence AI training task as indicated (e.g., AI codec training for XR application). This can segment the received packets as indicated and receive some of the Intelligence Service Data from the neighboring upstream UP entity. After configuration by the CP entity, the upstream UP entity must establish the TCP Type Tunnel with the neighboring downstream UP entity.Subsequently, the upstream UP entity and the downstream UP entity individually perform the intelligence AI training task as indicated (e.g., AI codec training for XR application), and the Intelligence Service Data is transferred through the established TCP Type Tunnel and subsequently processed by the downstream UP entity.

[00113] In a sixth mode, multiple CU entities may exist, as in Figure 8. This differs from mode 5 due to the multiple CU entities. The tunnel type and forwarding mode are TCP. The CU entities communicate through an Xn interface. For this example, the Service Type is intelligence service. The UP Processing Mode is segment received packets. This is merely an example of the parameters that can be configured.

[00114] The first CP entity is connecting to the upstream UP entity, and the second CP entity is connecting to the downstream UP entity via the standardized E1 interface. The upstream UP entity and the downstream UP entity are both capable of performing the AI ​​intelligence training task (by Petition 870250083397, dated 09 / 16 / 2025, pp. 94 / 112 32 / 40 example, AI codec training for XR services). Due to computing power limitations and user experience requirements, the CP entity determines whether to allow the upstream UP entity and the downstream UP entity to perform the AI ​​intelligence training task jointly. For example, the upstream UP entity will split the relative video and voice data and perform the segmentation operation towards relative video packets for AI codec training, while the downstream UP entity performs the segmentation operation towards relative voice packets for AI codec training. The Intelligence Service Data needs to be transferred from the upstream UP entity to the downstream UP entity through the appropriate type of routing tunnel.

[00115] As the control node, the first CP entity configures the upstream UP entity through the E1AP signaling procedure, which includes the following parameters in an example:

[00116] Service Type: Intelligence service, AI intelligence training for XR application,

[00117] UP Processing Mode: segmentation of received packets,

[00118] UP Forwarding Mode: TCP Type.

[00119] The first CP entity transmits the configuration parameters to the second CP entity via the Xn signaling procedure. The second CP entity configures the downstream UP entity via the E1AP signaling procedure, which includes the following parameters in an example:

[00120] Service Type: Intelligence service, AI intelligence training for XR application,

[00121] UP Processing Mode: segmentation of received packets, Petition 870250083397, dated 09 / 16 / 2025, pages 95 / 112 33 / 40

[00122] UP Forwarding Mode: TCP Type.

[00123] After configuration by the first CP entity, the upstream UP entity determines whether to execute the intelligence service or AI training task as indicated (e.g., AI training for XR application), and it may segment the received packets as indicated and transfer some of the Intelligence Service Data towards the neighboring downstream UP entity to offload the intelligence AI training task. Similarly, the downstream UP entity determines whether to execute the intelligence AI training task as indicated (e.g., AI training for XR application), and it must segment the received packets and receive some of the Intelligence Service Data from the neighboring upstream UP entity. After configuration by the first CP entity, the upstream UP entity establishes the TCP Type Tunnel with the neighboring downstream UP entity.Subsequently, the upstream UP entity and the downstream UP entity individually perform the intelligence AI training task (e.g., AI training for XR application), and the Intelligence Service Data is transferred through the established TCP Type Tunnel and subsequently processed by the downstream UP entity.

[00124] In a seventh mode, as in Figure 7, the CU entity communicates via the E1AP signaling procedure. The UP forwarding mode and tunnel type are QUICP in this example. The Service Type is an intelligence service, but with federated learning execution. The UP Processing Mode is concatenation of received packets. The intelligent service used in this example may be associated with machine learning and / or artificial intelligence, including a training feature. This is merely an example of the parameters that can be configured. Petition 870250083397, dated 09 / 16 / 2025, pp. 96 / 112 34 / 40

[00125] The upstream UP entity and the downstream UP entity are both capable of performing the intelligence service or AI training task, such as performing federated learning. Due to sample data privacy requirements, the CP entity determines whether to allow the upstream UP entity and the downstream UP entity to perform the intelligence AI training task jointly. The upstream UP entity and the downstream UP entity may not transmit sample data to each other for data privacy protection; therefore, they use their own local sample data to obtain gradient information and then combine it into a node. Consequently, Intelligence Service Data needs to be bidirectional to be transferred between the upstream UP entity and the downstream UP entity through the appropriate type of routing tunnel.

[00126] As the control node, the CP entity configures the upstream UP entity and the downstream UP entity individually through the E1AP signaling procedure, which includes the following parameters in an example:

[00127] Type of Service: intelligence service, federated learning application,

[00128] UP Processing Mode: concatenation of received packets,

[00129] UP Routing Mode: QUIC type.

[00130] After configuration by the CP entity, the upstream UP entity determines whether to execute the intelligence service or the AI ​​training task. In this example, the service / task includes a federated learning application. This can concatenate received packets and transfer / receive gradient information as Intelligence Service Data towards or from the neighboring downstream UP entity. Similarly, the downstream UP entity Petition 870250083397, dated 09 / 16 / 2025, pp. 97 / 112 35 / 40 determines whether to execute the intelligence AI training task (e.g., federated learning application). This can concatenate the received packets and transfer or receive gradient information as Intelligence Service Data to or from the neighboring upstream UP entity. After configuration by the CP entity, the upstream UP entity establishes the QUIC Type Tunnel with the neighboring downstream UP entity. Subsequently, the upstream UP entity and the downstream UP entity individually execute the intelligence AI training task (e.g., federated learning application), and gradient information as Intelligence Service Data is transferred through the established QUIC Type Tunnel and subsequently processed by the upstream UP entity or the downstream UP entity.

[00131] The following is a list of abbreviations: Abbreviation Term 5G Fifth Generation 5QI QoS Identifier 5G QoS Quality of Service LTE Long-Term Evolution EPC Evolved Packet Core NR New Radio RNL Radio Network Layer TNL Transport Network Layer GTP-U GPRS Tunneling Protocol SCTP Flow Control Transport Protocol AMF Access Mobility Function SMF Session Management Function UPF User Plane Function CU Centralized Unit DU Distributed Unit Petition 870250083397, dated 09 / 16 / 2025, pages 98 / 112 36 / 40 Abbreviation Term RU Radio Unit CP Control Plane UP User Plane BSR Temporary Storage Status Report PHR Power Tolerance Report PDCP Packet Data Convergence Protocol SDAP Service Data Adaptation Protocol RLC Radio Connection Control MAC Medium Access Control SRB Signaling Radio Carrier DRB Data Radio Carrier GBR Guaranteed Bit Rate AMBR Maximum Aggregate Bit Rate RB Radio Carrier LCH Logical Channel LCP Prioritized Logical Channel DRX Discontinuous Reception HARQ Hybrid ARQ DCI Downlink Control Information eMBB Enhanced Mobile Broadband mMTC Massive Machine Type Communications URLLC Ultra-Reliable Low Latency Communications OAM Operation Administration and Maintenance MN Master Node SN Secondary Node MCG Master Cell Group SCG Secondary Cell Group RRC Radio Resource Control Petition 870250083397, dated 09 / 16 / 2025, pp. 99 / 112 37 / 40 Abbreviation Term RRM Radio Resource Management Uu-C Uu - Control Plane Uu-U Uu - User Plane NG-C Next Generation - Control Plane NG-U Next Generation - User Plane Xn-C Xn - Control Plane Xn-U Xn - User Plane RNA RAN Notification Area NTN Non-Terrestrial Network MR-DC Dual Connectivity Multi-RAT EN-DC Dual Connectivity E-UTRA-NR NR-DC Dual Connectivity Intra-NR NGEN-DC Dual Connectivity NG E-UTRA-NR NE-DC Dual Connectivity NR-E-UTRA CHO Conditional Transfer DNN Deep Neutral Network MEC Mobile Edge Computing RLM Radio Connection Monitoring BFR Beam Fault Recovery MBS Multicast Transmission Service SIB System Information Block QUIC Internet Connection UDP Fast UDP User Datagram Protocol TCP DPI Transmission Control Protocol Deep Packet Inspection Table 1 - Abbreviations.

[00132] The system and process described above can be encoded in a signal carrier medium, a computer-readable medium such as memory, programmed into a device such as a Petition 870250083397, dated 09 / 16 / 2025, pages 100 / 112 38 / 40 or more integrated circuits, one or more processors, or processed by a controller or a computer. This data can be analyzed in a computer system and used to generate a spectrum. If the methods are executed by software, the software may reside in resident memory or interfaced to a storage device, synchronizer, a communication interface, or non-volatile or volatile memory in communication with a transmitter. An electronic circuit or device designed to send data to another location. The memory may include an ordered list of executable instructions to implement logical functions. A logical function or any described system element may be implemented through optical circuits, digital circuits, through source code, through analog circuits, through an analog source, such as an electrical, audio, or analog video signal, or a combination thereof.Software may be incorporated into any computer-readable or signal-carrying medium for use by, or in connection with, an instruction-executable system, apparatus, or device. Such a system may 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.

[00133] A computer-readable medium, machine-readable medium, propagated signal medium and / or signal carrier medium may comprise any device that includes, stores, communicates, propagates or transports software for use by, or in connection with, an executable instruction system, apparatus or device. The machine-readable medium may be selectively, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus, device or propagation medium. A non-exhaustive list of examples of a machine-readable medium Petition 870250083397, dated 09 / 16 / 2025, pages 101 / 112 39 / 40 would include: an electronic electrical connection that has one or more wires, a portable magnetic or optical disk, volatile memory such as Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM or Instant Memory), or an optical fiber. A machine-readable medium may also include a tangible medium on which the software is printed, since the software may be electronically stored as an image or in another format (e.g., through an optical scan), and then compiled and / or interpreted or otherwise processed. The processed medium may then be stored in a computer and / or machine memory.

[00134] The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the 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 may be apparent to those skilled in the art when reviewing the description. Other embodiments may be used and derived from the description, so that structural and logical substitutions and alterations may be made without departing from the scope of the description. Furthermore, the illustrations are merely representational and may not be drawn to scale. Certain proportions in the illustrations may be exaggerated, while other proportions may be minimized. Consequently, the description and figures should be considered illustrative rather than restrictive.

[00135] One or more embodiments of this description may be referred to herein, individually and / or collectively, by the term invention merely for convenience and without the intention of willfully limiting the scope of this application to any specific invention or inventive concept. Furthermore, despite specific embodiments Petition 870250083397, dated 09 / 16 / 2025, pp. 102 / 112 The 40 / 40 arrangements illustrated and described herein should be appreciated, and any subsequent arrangement designed to achieve the same or similar purpose may be superseded by the specific arrangements shown. This description is intended to cover any and all subsequent adaptations or variations of various arrangements. Combinations of the above arrangements and other arrangements not specifically described herein will be apparent to those skilled in the art upon review of the description.

[00136] The phrase "coupled to" is defined to mean directly connected to or indirectly connected through one or more intermediate components. Such 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 as presented here. Additional, different, or fewer components may be provided.

[00137] The subject matter described above should be considered illustrative and not restrictive, and the appended claims are intended to cover all such modifications, improvements, and other embodiments that fall within the true spirit and scope of the present invention. Thus, to the maximum extent permitted by law, the scope of the present invention shall be determined by the broadest permissible interpretation of the claims and their equivalents below, and shall not be restricted or limited by the detailed description above. Although several embodiments of the invention have been described, it will be apparent to those skilled in the art that many other embodiments and implementations are possible within the scope of the invention. Consequently, the invention shall not be restricted except in light of the appended claims and their equivalents. Petition 870250083397, dated 09 / 16 / 2025, pages 103 / 112

Claims

1 / 5 CLAIMS 1. A method for wireless communication, characterized in that it comprises: determining user plane (UP) settings for at least one UP network entity to perform user plane (UP) functions on at least one UP network entity; and transmitting the UP settings to at least one UP network entity to perform the UP functions, wherein the UP functions comprise at least one function other than or in addition to data packet forwarding.

2. Method according to claim 1, characterized in that each of the UP configurations indicates a type of data service and / or a UP function mode that includes one of a UP processing mode or a UP data forwarding mode.

3. A method according to claim 2, characterized in that the UP functions support services other than or in addition to a communication service, which includes at least one of a computing, intelligence, storage, or security service.

4. Method according to claim 1, characterized in that at least one UP network entity comprises two or more UP network entities that are configured to collaborate in performing UP functions.

5. Method according to claim 2, characterized in that each of the UP configurations indicates the data service type, the UP processing mode, or the UP data forwarding mode using an explicit predefined index identifier or indicator.

6. Method according to claim 1, characterized in that at least one of the UP configurations is provided Petition 870250083397, dated 09 / 16 / 2025, pp. 104 / 112 2 / 5 to allow a data transfer service to terminate at an intermediate node instead of an end node.

7. A method according to claim 6, characterized in that the intermediate node is configured to forward user data of different data service types to any other network node.

8. Method according to claim 2, characterized in that the UP processing mode indicates one or more of the following: transparently delivering received packets; compressing received packets; concatenating received packets; segmenting received packets; or making a local backup of received packets.

9. Method according to claim 2, characterized in that the UP data forwarding mode is associated with one or more of the following: a protocol data unit (PDU) session type; a data radio carrier (DRB) type; a CP signaling type; a Transmission Control Protocol (TCP) type; or a Fast User Datagram Protocol (QUIC) Internet connection type.

10. A method executed by a user plane (UP) network entity, characterized in that it comprises: receiving at least one UP configuration from a control plane (CP) network entity to support different types of data services; and executing UP functions based on at least one UP configuration, wherein the UP functions comprise at least one function other than or in addition to data packet forwarding.

11. A method according to claim 10, characterized in that the supported data services comprise one or more of the following: communication services, computing services, intelligence services, storage services, or security services.

12. Method according to claim 10, characterized in that the reception is via internal signaling or communication interface-based signaling.

13. Method according to claim 10, characterized in that each of the at least one UP configurations indicates a data service type and / or a UP function mode that includes one of a UP processing mode or a UP data forwarding mode.

14. Method according to claim 13, characterized in that each of at least one UP configuration indicates the data service type, UP processing mode, or UP data forwarding mode using an index identifier or an explicit predefined indicator.

15. Method according to claim 10, characterized in that at least one UP configuration allows a data transfer service to terminate at an intermediate node instead of at an end node.

16. Method according to claim 15, characterized in that the intermediate node is configured to forward user data of different data service types to any other network node.

17. The method according to claim 13, characterized by the fact that the UP processing mode indicates one or more of the following: transparently delivering received packets; compressing received packets; concatenating received packets; segmenting received packets; or local backup of received packets.

18. Method according to claim 13, characterized in that the UP data forwarding modes at least comprise: Protocol Data Unit (PDU) session type; Data Radio Carrier (DRB) type; CP signaling type; Transmission Control Protocol (TCP) type; or Fast User Datagram Protocol (QUIC) Internet connection type.

19. Method according to claim 10, characterized in that when multiple types of data services are configured simultaneously for the UP network entity, multiple and different sets of UP configurations are applied simultaneously.

20. Wireless communications apparatus characterized in that it comprises at least one processor and one memory, wherein the at least one processor is configured to read code from memory to: determine user plane (UP) settings for at least one UP network entity; to perform user plane (UP) functions on at least one first UP network entity; and to transmit the UP settings to at least one UP network entity to perform the UP functions, wherein the UP functions comprise at least one function other than or in addition to data packet forwarding.

Images