SYSTEM AND METHOD FOR DATA PLANE ARCHITECTURE IN A WIRELESS COMMUNICATION SYSTEM - Patent application

Abstract

The present disclosure provides a system and method for a data plane architecture of a wireless communications system. According to one aspect, a method is provided. The method may include receiving, by at least one Data Plane Gateway (DP GW), a request from a caller based on a first service-based interface format of the caller. The request may indicate one or more of a procedure to be performed by the callee and parameters of the procedure. The method may further include sending, by the at least one Data Plane Gateway (DP GW), a second request to the callee based on a second service-based interface format of the callee, the second request indicating one or more of the procedure and one or more parameters of the procedure.

Description

[Technical Field]

[0001] The present disclosure relates to the field of communication networks, and more particularly to a system and method for data plane architecture of a wireless communication system. [Background technology]

[0002] Existing wireless communication systems, such as 5G or 4G, offer data connection services to user equipment (UE), and packet encapsulation is performed to support data communication. During data communication, tunnel headers may be added to and removed from protocol data units (PDUs), which may cause communication overhead. Such overhead is undesirable in future wireless communication systems.

[0003] Future wireless communication systems are expected to offer data processing services. Traditionally, data processing services are provided and managed by entities external to the wireless communication system. As a result, guaranteeing end-to-end performance, e.g., data rate, delay, etc., can be difficult to maintain. How such data processing services can be provided in future wireless communication systems has yet to be determined.

[0004] Therefore, what is needed is a system and method for a data plane architecture for a wireless communications system that avoids or mitigates one or more limitations of the prior art. Summary of the Invention [Means for solving the problem]

[0005] This background information is provided to identify information believed by the applicant to be of possible relevance to the present invention. No admission is necessarily intended, nor should it be construed, that any of the above information constitutes prior art against the present invention.

[0006] The present disclosure provides a system and method for a data plane architecture of a wireless communication system. According to one aspect, a method is provided. The method includes receiving, by at least one data plane (DP) gateway (GW), a request from a caller based on a first service-based interface format of the caller. The request indicates one or more of a procedure to be performed by the callee and parameters of the procedure. The method further includes sending, by the at least one DP GW, a second request to the callee based on a second service-based interface format of the callee, the second request indicating one or more of the procedure and parameters of the procedure.

[0007] The method may further include mapping, by the at least one DP GW, the request to a second request. Receiving, by the at least one DP GW, the request from the caller may include receiving, by the at least one DP GW, at least one PDU from the caller that includes the request.

[0008] Mapping the request to the second request by the at least one DP GW may include mapping the request to the second request by a first DP GW of the at least one DP GW. Sending the second request to the callee by the at least one DP GW may include sending, by the first DP GW, at least one PDU including the second request to a second DP GW of the at least one DP GW.

[0009] Mapping, by the at least one DP GW, the request to a second request may include transmitting, by a first DP GW of the at least one DP GW, at least one PDU including the request to a second DP GW of the at least one DP GW. Mapping, by the at least one DP GW, the request to a second DP GW may further include mapping, by the second DP GW, the request to the second request.

[0010] The step of sending, by the first DP GW, at least one PDU to the second DP GW may include segmenting, by the first DP GW, the request into a plurality of request segments. The step of sending, by the first DP GW, at least one PDU to the second DP GW may further include sending, by the first DP GW, a plurality of PDUs, each PDU including a plurality of request segments, to the second DP GW.

[0011] Mapping, by the second DP GW, the request into a second request may further include reassembling, by the second DP GW, the multiple PDUs to obtain the request.

[0012] The request may include a first set of identifiers (IDs) based on a first service-based interface format of the caller, the first set of IDs indicating one or more of a procedure and parameters of the procedure, and the second request may include a second set of IDs based on a second service-based interface format of the callee, the second set of IDs indicating one or more of a procedure and parameters of the procedure.

[0013] The method may further include receiving, by the at least one DP GW, a response from the callee based on the second service-based interface format, the response indicating one or more of a result of the procedure and a result value. The method may further include sending, by the at least one DP GW, a second response based on the first service-based interface format to the caller, the response indicating one or more of a result of the procedure and a result value. The method may further include mapping, by the at least one DP GW, the response to the second response.

[0014] Receiving a response from the caller by the at least one DP GW may include receiving, by the at least one DP GW, at least one PDU from the callee, including the response.

[0015] Mapping the response to a second response by the at least one DP GW may include mapping the response to the second response by a third DP GW of the at least one DP GW. Sending the second response to the caller by the at least one DP GW may include sending, by the third DP GW, at least one PDU including the second response to a fourth DP GW of the at least one DP GW.

[0016] Mapping the response to a second response, by the at least one DP GW, may include transmitting, by a third DP GW of the at least one DP GW, the at least one PDU including the response to a fourth DP GW of the at least one DP GW. Mapping the response to a second response, by the at least one DP GW, may further include mapping the response to the second response by the fourth DP GW.

[0017] The step of sending, by the third DP GW, at least one PDU to the fourth DP GW may include segmenting, by the third DP GW, the response into multiple response segments. The step of sending, by the third DP GW, at least one PDU to the fourth DP GW may further include sending, by the third DP GW, multiple PDUs, each PDU including multiple response segments, to the fourth DP GW.

[0018] Mapping the response into a second response, by the fourth DP GW, may further include reassembling, by the second DP GW, the multiple PDUs to obtain the request.

[0019] The response can include a third set of identifiers based on the callee's second service-based interface format, the third set of identifiers indicating one or more of the results of the procedure. The second response can include a fourth set of identifiers based on the caller's first service-based interface format, the fourth set of identifiers indicating one or more of the results of the procedure.

[0020] According to another aspect, another method is provided. The method includes receiving, by a data plane (DP) gateway (GW), a PDU associated with a service from a first network entity via an inbound tunnel, where the PDU is routed through a second network entity. The method further includes processing, by the DP GW, the PDU based on the service. The method further includes transmitting, by the DP GW, the PDU to the second network entity.

[0021] The PDU may include a first L3 header that includes a source address, a destination address, and one or more of quality of service (QoS) information indicating a class of the PDU, a priority of the PDU, and one of the QoS flows to which the PDU belongs.

[0022] The source address may indicate one of the following: the address of the PDU sender, the address of the Radio Access Network (RAN) node to which the sender belongs, the address of the PDU originator, and the address of the processing service. The destination address is one of the following: the address of the DP GW, the address of the RAN node to which the DP GW belongs, and the address of the processing service.

[0023] The PDU may further include a first L4 header, the first L4 header including a connection identifier (ID) that identifies the receiving tunnel over which the PDU is received.

[0024] The receiving tunnel can be associated with a processing service, and the connection ID identifies the connection between the originator of the PDU and the final destination of the PDU. The receiving tunnel can be associated with a connection service that connects two network entities, and the connection ID identifies the connection between the two network entities.

[0025] The step of sending, by the DP GW, the PDU to the second network entity may include determining, by the DP GW, a transmission tunnel. The step of sending, by the DP GW, the PDU to the second network entity may further include sending, by the DP GW, the PDU to the second network entity via the transmission tunnel.

[0026] The transmission tunnel can be determined based on one of a mapping between the receiving tunnel and the transmission tunnel, a mapping between the connection ID and a second connection ID that identifies the transmission tunnel, a mapping between the connection ID, the QoS information, and the second connection ID, and a mapping provided by a network controller in the RAN.

[0027] The transmission tunnel may include a transmitting end and a receiving end, where the transmitting end is a DP GW and the receiving end is a second network entity.

[0028] The DP GW may be a central unit (CU) within the RAN DP. The PDU may be associated with a processing service. The receiving tunnel may be a T3 tunnel. The transmitting tunnel may be an M2 tunnel. The receiving end of the transmitting tunnel may be the RAN DP GW.

[0029] The PDU may be associated with a processing service. The receiving tunnel may be an M2 tunnel. The transmitting tunnel may be a T3 tunnel. The receiving end of the transmitting tunnel may be a core network (CN) DP GW.

[0030] The PDU may be associated with a connection service. The receiving tunnel may be a T3 tunnel. The transmitting tunnel may be a data radio bearer (DRB) associated with a device. The receiving end of the transmitting tunnel may be the device.

[0031] The DP GW may be a processing unit (PU) within the RAN DP, and the PDU may be associated with a processing service. The receiving tunnel may be one of a T3 tunnel, an M2 tunnel, or an M5 tunnel. The transmitting tunnel may be an M4 tunnel. The receiving end of the transmitting tunnel may be the RAN DP GW.

[0032] The receiving tunnel may be one of a T3 tunnel, an M2 tunnel, an M4 tunnel, and an M5 tunnel. The transmitting tunnel may be a processing radio bearer (XRB) associated with the device. The receiving end of the transmitting tunnel may be the device.

[0033] The receiving tunnel may be one of a T3 tunnel, an M2 tunnel, and an M4 tunnel. The transmitting tunnel may be an M5 tunnel. The receiving end of the transmitting tunnel may be a RAN Processing Services Function (PSF).

[0034] The method may further include processing, by the Datagram Protocol GW, the PDU to obtain a modified PDU. Sending, by the Datagram Protocol GW, the PDU to the second network entity through the transmission tunnel may include sending, by the Datagram Protocol GW, the modified PDU to the second network entity through the transmission tunnel.

[0035] Processing the PDU to obtain a modified PDU, by the DP GW, may include one of replacing the first L3 header with a second L3 header and modifying the first L3 header with the second L3 header, where the second L3 header may include one or more of a second source address, a second destination address, and second QoS information.

[0036] The second source address may be one of the following: the same address as the source address in the first L3 header, an address different from the source address in the first L3 header, an address of the RAN DP GW, or an address of the processing service from which the PDU originated.

[0037] The second destination address may be one of the following: the same address as the destination address in the first L3 header, an address different from the destination address in the first L3 header, an address of the receiving end of the transmission tunnel, an address of a processing service to which the PDU is targeted, or an address of a device to which the transmission tunnel is a radio bearer associated with the device.

[0038] The second QoS information may be one of the following: the same QoS information as the QoS information in the first L3 header; or different QoS information than the QoS information in the first L3 header.

[0039] The step of processing the PDU to obtain a modified PDU, by the DP GW, may further include one of replacing the first L4 header with a second L4 header and modifying the first L4 header with the second L4 header. The second L4 header may include a third connection ID, where the third connection ID is one or more of a connection ID different from the connection ID in the first L4 header, an ID identifying the transmission tunnel, and a second connection ID.

[0040] The transmission tunnel can be associated with a processing service, and the third connection ID identifies a connection between the originator of the PDU and the final destination of the PDU. The transmission tunnel can be associated with a connection service that connects two network entities, and the connection ID identifies a connection between the two network entities.

[0041] The receiving tunnel may be a radio bearer associated with the device, the radio bearer being one of a data radio bearer (DRB) and a processing radio bearer (XRB). The PDU may include a first L3 header, the first L3 header including one or more of a source address, a destination address, and quality of service (QoS) information indicating a class of the PDU, a priority of the PDU, and one of a QoS flow to which the PDU belongs.

[0042] The source address may indicate the address of the originator of the PDU, where the originator is a device. In some cases, the destination address may be one of the addresses of the processing service or the processing service function (PSF) that provides at least a part of the processing service if the receiving tunnel is associated with the processing service, if the receiving tunnel is an XRB, or if the PDU targets the processing service. In some cases, the destination address may be one of the addresses of the DP GW or the radio access network (RAN) node to which the DP GW belongs.

[0043] The method can further include a first L4 header, the first L4 header including a connection identifier (ID) that identifies a receiving tunnel over which the PDU is received.

[0044] The connection ID may identify a connection between the device and the processing service, or a PSF providing at least a portion of the processing service, if the receiving tunnel is associated with the processing service, if the receiving tunnel is an XRB that the device uses to access the processing service, or if the PDU is associated with a processing service.

[0045] The connection ID can identify a connection between a device and a data network (DN) or an application server of a DN if the incoming tunnel is associated with a connection service, if the incoming tunnel is a DRB that the device uses to access the connection service, or if the PDU is associated with a connection service, and the connection service connects the device to the DN or AS.

[0046] The step of sending, by the DP GW, the PDU to the second network entity may include determining, by the DP GW, a transmission tunnel. The step of sending, by the DP GW, the PDU to the second network entity may further include sending, by the DP GW, the PDU to the second network entity via the transmission tunnel.

[0047] The transmission tunnel can be determined based on one of a mapping between the receiving tunnel and the transmission tunnel, a mapping between the connection ID and a second connection ID that identifies the transmission tunnel, a mapping between the connection ID, the QoS information, and the second connection ID, and a mapping provided by a network controller in the RAN.

[0048] In some aspects, the transmission tunnel may include a transmitting end and a receiving end, where the transmitting end is a DP GW. The DP GW may be a central unit (CU) in a RAN DP. The PDU may be associated with a connectivity service. The transmission tunnel may be a T3 tunnel. The receiving end of the transmission tunnel may be a core network (CN) DP GW in a CN DP. The second network entity may be the receiving end of the transmission tunnel.

[0049] The DP GW may be a processing unit (PU) in the RAN DP. If the PDU is associated with a processing service, the transmission tunnel may be one of an M2 tunnel, an M4 tunnel, or an M5 tunnel.

[0050] If the transport tunnel is a T3 tunnel, the receiving end of the transport tunnel may be a core network (CN) DP GW in the CN DP, and the second network entity is the receiving end of the transport tunnel.

[0051] If the transmission tunnel is an M2 tunnel, the receiving end of the transmission tunnel is a central unit (CU) in the RAN DP, and the second network entity is the receiving end of the transmission tunnel.

[0052] If the transmission tunnel is an M4 tunnel, the receiving end of the transmission tunnel may be another PU that is communicatively coupled to a Processing Services Function (PSF) within the RAN that at least partially provides the processing services. If the transmission tunnel is an M4 tunnel, the second network entity may be the receiving end of the transmission tunnel.

[0053] If the transmission tunnel is an M5 tunnel, the receiving end of the transmission tunnel may be a RAN Processing Service Function (PSF), and the RAN PSF at least partially provides the processing services. If the transmission tunnel is an M5 tunnel, the second network entity is the receiving end of the transmission tunnel.

[0054] The method may further include processing, by the Datagram Protocol GW, the PDU to obtain a modified PDU. Sending, by the Datagram Protocol GW, the PDU to the second network entity through the transmission tunnel may include sending, by the Datagram Protocol GW, the modified PDU to the second network entity through the transmission tunnel.

[0055] Processing the PDU to obtain a modified PDU, by the DP GW, can include one of replacing the first L3 header with a second L3 header and modifying the first L3 header with the second L3 header. The second L3 header can include a second source address, where the second source address is one of the same address as the source address in the first L3 header, a different address from the source address in the first L3 header, and an address of the DP GW.

[0056] The second L3 header may further include a second destination address, the second destination address being one of the same address as the destination address in the first L3 header, an address different from the destination address in the first L3 header, an address of a receiving end of the transmission tunnel, or an address of a processing service function that provides at least a portion of the processing service, and the PDU is targeted to the processing service.

[0057] The second L3 header may further include second QoS information, the second QoS information being one of the same QoS information as the QoS information in the first L3 header and different QoS information from the QoS information in the first L3 header.

[0058] The step of processing the PDU to obtain a modified PDU, by the DP GW, may further include one of the steps of replacing the first L4 header with a second L4 header, or modifying the first L4 header with the second L4 header, where the second L4 header may be a tunnel header of the transmission tunnel.

[0059] The second L4 header can include a third connection ID, where the third connection ID is one or more of a connection ID different from the connection ID in the first L4 header, an ID identifying the transmission tunnel, and the second connection ID.

[0060] If the DP GW is a core network (CN) DP GW, the receiving end of the receiving tunnel may be the CN DP GW, and the transmitting end of the receiving tunnel may be in one of a radio access network (RAN), a CN, and a data network (DN).

[0061] The PDU may include a first L3 header, the first L3 header including one or more of a source address and a destination address, wherein the source address may indicate one of an address of a transmitting end, an address of a radio access network (RAN) node to which the transmitting end belongs, an address of an originator, and an address of a processing service from which the PDU originates.

[0062] The destination address may be one of the addresses of the CN DP GW and the processing service if the PDU targets the processing service.

[0063] The PDU may further include quality of service (QoS) information that indicates the class of the PDU, the priority of the PDU, and one of the QoS flows to which the PDU belongs.

[0064] The PDU may further include a first L4 header, the first L4 header including a connection identifier (ID) that identifies the receiving tunnel over which the PDU is received.

[0065] The connection ID may identify a connection between the originator of the PDU and the final destination of the PDU if the receiving tunnel is associated with a processing service or if the PDU is associated with a processing service. In some cases, the connection ID may identify a connection between two network entities if the receiving tunnel or PDU is associated with a connectivity service and the connectivity service connects the two network entities.

[0066] The step of sending, by the DP GW, the PDU to the second network entity may include determining, by the CN DP GW, a transmission tunnel. The step of sending, by the DP GW, the PDU to the second network entity may further include, by the CN DP GW, sending, by the CN DP GW, the PDU to the second network entity through the transmission tunnel.

[0067] The transmission tunnel can be determined based on one of a mapping between the receiving tunnel and the transmission tunnel, a mapping between the connection ID and a second connection ID that identifies the transmission tunnel, a mapping between the connection ID, QoS information, and the second connection ID, and a mapping provided by a network controller in the CN.

[0068] The transmission tunnel may include a transmitting end and a receiving end, where the transmitting end is a CN DP GW and the receiving end is in one of the RAN, CN, and DN.

[0069] If the transmission tunnel is a T3 tunnel, the receiving end of the transmission tunnel may be a RAN DP GW in the RAN DP, and the second network entity is the receiving end of the transmission tunnel.

[0070] If the transmission tunnel is a T4 tunnel, the receiving end of the transmission tunnel is another CN DP GW in the RAN DP, and the second network entity is the receiving end of the transmission tunnel.

[0071] If the PDU is associated with a processing service and the transmission tunnel is a T5 tunnel, the receiving end of the transmission tunnel may be a CN Processing Service Function (PSF) that at least partially provides the processing service. In such a case, the second network entity may be the receiving end of the transmission tunnel.

[0072] If the transmission tunnel is a T6 tunnel, the receiving end of the transmission tunnel is within the DN, and the second network entity may be the receiving end of the transmission tunnel.

[0073] The method may further include processing, by the CN DP GW, the PDU to obtain a modified PDU. Sending, by the CN DP GW, the PDU to the second network entity through the transmission tunnel may include sending, by the CN DP GW, the modified PDU to the second network entity through the transmission tunnel.

[0074] The step of processing the PDU to obtain a modified PDU, by the CN DP GW, includes one of the steps of replacing the first L3 header with a second L3 header and modifying the first L3 header with the second L3 header.

[0075] The second L3 header may include a second source address, which is one of the following: the same address as the source address in the first L3 header, a different address from the source address in the first L3 header, an address of the CN DP GW, an address of the originator of the PDU, and an address of the processing service if the PDU originated from the processing service.

[0076] The second L3 header may further include a second destination address, which is one of the following: the same address as the destination address in the first L3 header, a different address than the destination address in the first L3 header, an address of a receiving end of the transmission tunnel, or an address of a processing service function that provides at least a portion of the processing service if the PDU is targeted for the processing service.

[0077] The second L3 header may further include second QoS information, the second QoS information being one of the same QoS information as the QoS information in the first L3 header or different QoS information from the QoS information in the first L3 header.

[0078] Processing the PDU by the CN DP GW to obtain a modified PDU may further include replacing the first L4 header with a second L4 header. Optionally, processing the PDU by the CN DP GW to obtain a modified PDU may further include modifying the first L4 header with a second L4 header, where the second L4 header is a tunnel header of the transmission tunnel.

[0079] The second L4 header can include a third connection ID, where the third connection ID is one or more of a connection ID different from the connection ID in the first L4 header, an ID identifying the transmission tunnel, and the second connection ID.

[0080] The third connection ID may identify a connection between the originator of the PDU and the final destination of the PDU if the transmission tunnel or PDU is associated with a processing service. In some cases, the third connection ID may identify a connection between two network entities if the transmission tunnel or PDU is associated with a connectivity service that connects the two network entities.

[0081] According to another aspect, another method is provided. The method includes receiving, by a first network controller of a radio access network (RAN), information regarding a device from a second network controller of a core network (CN), the information indicating one or more of: that the device requires a process radio bearer (XRB) and that the device is accessing a process service. The method further includes allocating, by the first network controller, the XRB based on the information regarding the device. The method further includes configuring, by the first network controller, one or more network nodes to support the XRB.

[0082] Allocating the XRB by the first network controller based on the information about the device may include generating an identifier (ID) for identifying the XRB.

[0083] Configuring, by the first network controller, one or more network nodes to support the XRB may include configuring, by the first network controller, a RAN Data Plane (DP) Gateway (GW) associated with the XRB.

[0084] If the RAN DP GW is a processing unit (PU), configuring the RAN DP GW by the first network controller may include providing, by the first network controller, the generated ID to the PU. Configuring the RAN DP GW by the first network controller may further include configuring, by the first network controller, the PU to disable XRB to perform one or more of PDCP security and PDCP sequencing.

[0085] Configuring, by the first network controller, one or more network nodes to support the XRB may further include configuring, by the first network controller, a distributed unit (DU) associated with the XRB.

[0086] Configuring, by the first network controller, the DU associated with the XRB may include providing, by the first network controller, the generated ID to the DU. Configuring, by the first network controller, the DU associated with the XRB may further include configuring, by the first network controller, the DU to disable the XRB to perform one or more of RLC segmentation and RLC acknowledgment.

[0087] Configuring, by the first network controller, one or more network nodes to support XRB may further include configuring, by the first network controller, a device to support XRB.

[0088] Configuring, by the first network controller, the device to support XRB may include providing, by the first network controller, the generated ID to the device. Configuring, by the first network controller, the device to support XRB may further include configuring, by the first network controller, the device to disable XRB to perform one or more of RLC segmentation, RLC acknowledgment, PDCP security, and PDCP sequencing.

[0089] According to one aspect, another method is provided. The method includes receiving, by a processing unit (PU) in a radio access network (RAN) data plane (DP), from a first network node via a first interface between the PU and the network node, a protocol data unit (PDU) associated with a service. The method may further include processing, by the PU, the PDU to obtain a processed PDU. The method may further include transmitting, by the PU, the processed PDU to the second network node via a second interface between the PU and the second network node.

[0090] The first network node may be a device, and the first interface may be one of a data radio bearer and a processing radio bearer.

[0091] The second network node and the second interface may, more specifically, be another PU and an M4 interface in the RAN DP. In some cases, the second network node and the second interface may, more specifically, be a PU backend and an M5 interface in the RAN DP. In some cases, the second network node and the second interface may, more specifically, be a central unit (CU) and an M2 interface in the RAN DP. In some cases, the second network node and the second interface may, more specifically, be a DP gateway (GW) and a T3 interface in a core network (CN) DP.

[0092] If the first network node is another PU in the RAN DP, the first interface may be an M4 interface. The second network node and the second interface may be, in particular, one of a device and data radio bearer, a device and processing radio bearer, a PU backend and an M5 interface in the RAN DP, a central unit (CU) and an M2 interface in the RAN DP, and a DP gateway (GW) and a T3 interface in the core network (CN) DP.

[0093] In some cases, the first network node is a PU backend in a RAN DP and the first interface is an M5 interface. The second network node and the second interface may be, in particular, one of a device and data radio bearer, a device and processing radio bearer, another PU and an M4 interface in the RAN DP, a central unit (CU) and an M2 interface in the RAN DP, and a DP gateway (GW) and a T3 interface in a core network (CN) DP.

[0094] In some cases, the first network node is a central unit (CU) in a RAN DP, and the first interface is an M2 interface. The second network node and the second interface may be, in particular, one of a device and data radio bearer, a device and processing radio bearer, another PU and an M4 interface in the RAN DP, a PU backend and an M5 interface in the RAN DP, and a DP gateway (GW) and a T3 interface in a core network (CN) DP.

[0095] In some cases, the first network node may be a DP Gateway (GW) in a Core Network (CN) DP, and the first interface may be a T3 interface. The second network node and the second interface may be, in particular, one of a device and data radio bearer, a device and processing radio bearer, another PU and M4 interface in the RAN DP, a PU backend and M5 interface in the RAN DP, and a central unit (CU) and M2 interface in the RAN DP.

[0096] According to another aspect, an apparatus is provided, the apparatus including modules configured to implement one or more of the methods and systems described herein.

[0097] According to one aspect, an apparatus is provided, the apparatus including: a memory configured to store a program; and a processor configured to execute the program stored in the memory, wherein when the program stored in the memory is executed, the processor is configured to implement one or more of the methods and systems described herein.

[0098] According to another aspect, a computer-readable medium is provided, the computer-readable medium storing program code for execution by a device, the program code being used to implement one or more of the methods and systems described herein.

[0099] According to one aspect, a chip is provided, the chip including a processor and a data interface, wherein the processor reads instructions stored in a memory by using the data interface to implement one or more of the methods and systems described herein.

[0100] Another aspect of the present disclosure provides apparatuses and systems configured to implement the method according to the first aspect disclosed herein. For example, wireless stations and access points can be configured with machine-readable memories containing instructions that, when executed by a processor of the devices, configure the devices to perform one or more of the methods and systems described herein.

[0101] The embodiments have been described above in conjunction with aspects of the invention in which they may be implemented. Those skilled in the art will understand that an embodiment may be implemented in conjunction with the described aspect, but may also be implemented with other embodiments of that aspect. Where embodiments are mutually exclusive or contradictory, this will be apparent to those skilled in the art. Some embodiments may be described in relation to one aspect, but may also be applicable to other aspects, as will be apparent to those skilled in the art.

[0102] Further features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0103] [Figure 1] 1 illustrates an architecture of a communication system, according to one aspect. [Figure 2] 1 illustrates a core network (CN) data plane architecture, according to one aspect. [Figure 3] 1 illustrates a RAN data plane architecture, according to one aspect. [Figure 4] 1 illustrates another RAN data plane architecture, according to one aspect. [Figure 5] 1 illustrates an overall data plane architecture, according to one aspect. [Figure 6] 1 illustrates a remote procedure call (RPC), according to one embodiment. [Figure 7] 1 illustrates a procedure for allocating a radio bearer to a device, according to one aspect. [Figure 8] Illustrated are apparatuses that may perform any or all of the operations of the above methods and features explicitly or implicitly described herein, according to different aspects of the present disclosure. [Figure 9] 1 illustrates a method for processing data in a DP GW, according to one embodiment. [Figure 10] 1 illustrates another method for processing data, according to one aspect. [Figure 11] 1 illustrates a method for allocating radio bearers to a device, according to an aspect. [Figure 12] 1 illustrates another method for processing data, according to one aspect. DETAILED DESCRIPTION OF THE INVENTION

[0104] It should be noted that throughout the accompanying drawings, like features are identified by like numerals.

[0105] The present disclosure provides a system and method for a data plane architecture of a wireless communication system. According to one aspect, a method for data processing in a data plane (DP) gateway (GW) is provided.

[0106] The method (e.g., method 900) includes receiving, by the at least one DP GW, a request from a caller based on a first service-based interface format of the caller. The request may indicate one or more of a procedure to be performed by the callee and parameters of the procedure. The method may further include sending, by the at least one DP GW, a second request to the callee based on a second service-based interface format of the callee, the second request indicating one or more of the procedure and parameters of the procedure.

[0107] According to another aspect, another method for processing data may be provided. The method (e.g., method 1000) includes receiving, by a data plane (DP) gateway (GW), a PDU associated with a service from a first network entity via an inbound tunnel, where the PDU is routed through a second network entity. The method further includes processing, by the DP GW, the PDU based on the service. The method further includes transmitting, by the DP GW, the PDU to the second network entity.

[0108] According to another aspect, a method for allocating a radio bearer to a device may be provided. The method (e.g., method 1100) includes receiving, by a first network controller (e.g., network controller 710) of a radio access network (RAN) from a second network controller (e.g., network controller) 712 of a core network (CN), information about the device. The information may indicate one or more of: that the device requires a process radio bearer (XRB) and that the device is accessing a process service. In some aspects, the method further includes allocating, by the first network controller, the XRB based on the information about the device. In some aspects, the method further includes configuring, by the first network controller, one or more network nodes to support the XRB.

[0109] A data connection service (or simply, connection service) provided by a communication system (e.g., a wireless communication system) is a service that routes or transports data traffic of a first network entity or from a first network entity to a second network entity. The first network entity may be part of the communication system, e.g., a device (e.g., a first user equipment (UE)), or the first network entity may not be part of the communication system, e.g., a first application server (AS) in a data network (DN). The second network entity may be part of the communication system, e.g., a second device (e.g., a second UE), or the second network entity may not be part of the communication system, e.g., a second AS in a DN. During the routing of data traffic, in a data connection service, the communication system does not process (e.g., retrieve, modify, or store) the content of the data traffic.

[0110] A data processing service (or simply, a processing service) provided by a communication system (e.g., a wireless communication system) to a first network entity may be a service, and a second network entity receives data traffic from the first network entity and processes (e.g., retrieves, modifies, or stores, or analyzes) the content of the data traffic. The first network entity may be part of the communication system, e.g., a device (e.g., a UE), or the first network entity may not be part of the communication system, e.g., an AS in a DN. The second network entity may be part of the communication system, e.g., a data plane function (DPF) in a data plane (DP) of the communication system. When providing a data processing service to the first network entity, the communication system (e.g., the second network entity) may generate data traffic and transmit the generated data traffic to the first network entity. The data processing service as described above is also known as a computing service.

[0111] Current or previous wireless communication systems, such as 5G or 4G, offer data connectivity services to UEs, and packet encapsulation is performed in the data plane to support communication between UEs or between UEs and DNs (e.g., ASs within the DN). During communication, protocol data units (PDUs) generated by UEs or network entities (e.g., ASs within the DN that are external to the system) are transported through the data plane of the communication system, and the PDUs are routed through one or more tunnels in the data plane.

[0112] The data plane may be known as the user plane. When a PDU enters a tunnel with two tunnel endpoints, a first DPF (such as a first UPF in 5G) and a second DPF (such as a second UPF in 5G), a tunnel header is added to the PDU by the first DPF, and the entire PDU is treated as data. The tunnel header contains QoS information. When the PDU exits the tunnel, the tunnel header is removed by the second DPF. The tunnel header may add additional overhead to the communication.

[0113] Future wireless communication systems, such as 6G, may offer data processing services in addition to data connectivity services. Traditionally, data processing services are managed and offered or provided by an entity external to the communication system, for example, an AS or a data center or cloud system located in the DN, and the system provides the data connectivity service(s) to the UE so that the UE can use the service(s) to connect to and access the data processing services. When a wireless communication system natively offers or provides data processing services, the data processing services are offered or provided by one or more network entities in the data plane of the communication system.

[0114] When offering or providing a data processing service, one or more network entities may process the content of a communication related to the processing service, e.g., data contained in a PDU, and the communication may not necessarily involve a UE. For example, the communication may be between an AS and one or more network entities, or between a UE and one or more network entities.

[0115] While such data processing services are envisioned in future systems, it is unclear and yet to be determined what the data plane architecture might look like and how the data plane will operate or behave to enable or support the data processing services.

[0116] In current and previous wireless communication systems, packet encapsulation is performed in the data plane. During packet encapsulation, a tunnel header is added to the PDU, and the entire PDU is treated as data. The added tunnel header can result in additional communication overhead.

[0117] When processing services are offered by entities external to the wireless communications system, the processing services and the wireless communications system are likely to be managed separately by different parties. As a result, guaranteeing end-to-end performance (e.g., data rate, delay, including both communication delay and computational delay) may be difficult to maintain.

[0118] According to one aspect, a data plane (DP) architecture for future wireless communication systems (e.g., 6G) is provided. The DP architecture can enable or support native data processing. Network entities within the DP and their behaviors are described with reference to one or more aspects. The network entities within the DP may be referred to as a DPF. In some aspects, the DPF may include a DP Gateway (GW) and a Processing Service Function (PSF).

[0119] A wireless communication system to which one or more aspects may be applied may include a radio access network (RAN) and a core network (CN). Aspects of the present disclosure may provide a DP GW including a DP GW in the RAN (i.e., a RAN DP GW) and a DP GW in the CN (i.e., a CN DP GW). One or more functions of the DP GW, such as a header processing function and a content processing function, according to one or more aspects are described.

[0120] Some aspects may provide an enhanced data bearer (transaction radio bearer (XRB)) to support processing services offered by the system. According to some aspects, allocation of the XRB for a UE to access processing services offered by the system is described.

[0121] According to one aspect, an XRB may have simplified protocol behavior in the RLC sublayer and PDCP sublayer (no RLC segmentation, no RLC acknowledgment, no PDCP security, no PDCP sequencing) compared to a conventional data radio bearer (DRB). In some aspects, the protocol behavior of an XRB may exclude one or more of RLC segmentation, RLC acknowledgment, PDCP security, and PDCP sequencing.

[0122] In some aspects, a reference to an "entity" may refer to "a plurality of such entities." For example, the existence or inclusion of an entity may indicate the existence or inclusion of a plurality of such entities.

[0123] FIG. 1 illustrates an architecture of a communication system according to one aspect. The communication system may include a RAN 110 and a CN 120. The CN 120 may include a control plane (CP) 124 and a data plane (DP) 122. The CN's CP (i.e., CN CP) may include one or more control plane functions (CPFs). The RAN 110 may also include a CP 114 and a DP 112. The RAN's CP (i.e., RAN CP) may include one or more centralized units (CUs). To distinguish it from the CU in the RAN's DP (i.e., RAN DP) described herein, in some aspects, the CU in the RAN CP may be referred to as a CU-CP. The communication system may be connected to a DN 130 (i.e., one or more DNs). The DN may be connected to the CN's DP (i.e., CN DP 122) via a T6 connection (or interface) 106.

[0124] The communication system may further include a device 102 (i.e., one or more devices). The device may be connected to a RAN's Data Plane Function (DP) (i.e., RAN DP 112) via an air interface 101. The RAN DP 112 may be connected to a CN DP 122 via a T3 connection (or interface) 103. Via the RAN DP 112, the device 102 may further be connected to the CN DP 122 such that the device 102 may interact or communicate with a data plane function (DPF) in the CN DP 122, e.g., a processing function (PF) as described herein, or with a DN 130 (e.g., a server in the DN 130) connected to the CN DP 122 via a T6 connection (or interface) 106. A detailed diagram of the CN DP 122 according to one embodiment is shown in FIG. 2, and detailed diagrams of the RAN DP 112 according to one embodiment are shown in FIGS. 3 and 4.

[0125] 2 illustrates a CN data plane architecture, according to one aspect. The CN DP 122 may include a connectivity subplane 210 and a processing subplane 220. The connectivity subplane 210 may include one or more connectivity subplane functions (NPFs) 212. The processing subplane 220 may include one or more processing functions (PFs) 222. The NPF(s) 212 and the PF(s) 222 are DPFs.

[0126] In some aspects, the NPF 212 can be considered a gateway for the CN DP 122 and can be referred to as a CN DP GW. In some aspects, the NPF 212 can connect with the RAN DP via a T3 connection (or interface) 203. In some aspects, the NPF 212 can connect with another NPF in the CN DP via a T4 connection (or interface) 204. In some aspects, the NPF 212 can connect with a PF in the CN DP via a T5 connection (or interface) 205. In some aspects, the NPF 212 can connect with the DN 130 via a T6 connection (or interface) 206, as illustrated. The T3 connection 203, the T6 connection 206, and the air interface 201 in FIG. 2 correspond to the T3 connection 103, the T6 connection 106, and the air interface 101 in FIG. 1, respectively.

[0127] In some aspects, each of the T3 connection 203, the T4 connection 304, and the T5 connection 206 may be implemented or supported by a tunnel (referred to as a CN tunnel). The CN tunnel may be a Layer 4 (L4) tunnel, and the tunneling protocol(s) for the CN tunnel may be any of QUIC, QUIC / UDP, and GTP-U / UDP. In some aspects, the CN tunnel may be supported by IPv4 routing or IPv6 routing at Layer 3 (L3, IP layer). In some aspects, the T6 connection 206 may also be implemented by a tunnel. Like the CN tunnel, the tunnel corresponding to the T6 connection may also be an L4 tunnel, and the tunneling protocol(s) for the tunnel corresponding to the T6 connection may be the same as the tunneling protocol(s) of the CN tunnel (e.g., any of QUIC, QUIC / UDP, and GTP-U / UDP). The tunnel corresponding to the T6 connection may be supported by IPv4 routing or IPv6 routing at Layer 3 (L3, IP layer).

[0128] A T3 tunnel, a T4 tunnel, a T5 tunnel, or a T6 tunnel refers to a tunnel that implements or supports a T3 connection, a T4 connection, a T5 connection, or a T6 connection, respectively. Thus, in this application, the terms T3 tunnel and T3 connection are equivalent, the terms T4 tunnel and T4 connection are equivalent, the terms T5 tunnel and T5 connection are equivalent, and the terms T6 tunnel and T6 connection are equivalent.

[0129] 3 illustrates a RAN data plane architecture according to one aspect. The RAN DP 300 (which may be similar to the RAN DP 112) may include a connectivity subplane 310 and a processing subplane 320. The connectivity subplane 310 may include one or more of a distributed unit (DU) 312 (i.e., one or more DUs), a centralized unit (CU) 314 (i.e., one or more CUs), and a processing unit (PU) 316 (i.e., one or more PUs). In some aspects, the DU 312 may include a transmission and reception point (TRP) (i.e., one or more TRPs). The TRP may be equipped with one or more antennas or antenna arrays and may transmit and receive radio signals. In some aspects, the TRP may be separate (distinct) from the DU. To distinguish it from the CU in the RAN CP described herein, the centralized unit (CU) in the RAN DP may be referred to as the CU-DP 314.

[0130] In some aspects, the processing subplane 320 may include one or more PU backends 322. The PU backends (PU-BEs) 322 may be communicatively coupled, i.e., connected, to the PUs 316 via an M5 connection (or interface) 305. The PU-BEs 322 may also be communicatively coupled to other PU(s) in the RAN DP through different M5 connection(s).

[0131] In some aspects, a PU (e.g., PU 316) is a type of DP GW, while a PU-BE 322 is similar to a PF. In some aspects, a processing function in a CN may be denoted as a PF, and a processing function in a RAN may be denoted as a PU-BE. A PF in a CN connects to an NPF (which is a CN DP GW). A PU-BE in a RAN connects to a PU (which is a RAN DP GW).

[0132] In some aspects, each of the CU-DP 314 and the PU 316 may be considered a gateway of the RAN DP 300 and may be referred to as a RAN DP GW. In some aspects, the CU-DP 314 may have a T3 connection (or interface) 303 with the CN 120 (e.g., the CN DP 122) that connects the CU-DP 314 with the NPF 212 in the CN DP 122.

[0133] In some aspects, the PU 316 may have a T3 connection 303 with the CN DP 122, as illustrated in Figure 3. In some aspects, a PU (e.g., PU 416) may not have a T3 connection with the CN DP 122, as illustrated in Figure 4. Figure 4 illustrates another RAN data plane architecture, according to one aspect.

[0134] The RAN DP 400 may be similar to the RAN DP 300, but the PU 416 may have an M2 connection 402 with the CU-DP 414 without a T3 connection with the CN 120. Meanwhile, the PU 316 may have a T3 connection 303 with the CN 120 without an M2 connection with the CU-DP 314. In some aspects, the PU 518 in the RAN DP may have one or both of an M2 connection and a T3 connection, as shown in FIG.

[0135] Similar to the RAN DP 300, the RAN DP 400 (which may be similar to the RAN DP 112) may include a connectivity subplane 410 (similar to the connectivity subplane 310) and a processing subplane 420 (similar to the processing subplane 320). The connectivity subplane 410 may include one or more of a DU 412 (similar to the DU 312), a CU 414 (similar to the CU 314), and a PU 416 (similar to the PU 316). In some aspects, the processing subplane 420 may include one or more PU-BEs 422 (similar to the PU-BE 322). The PU-BE 422 may be communicatively coupled, i.e., connected, to the PU 416 via an M5 connection (or interface) 405 (similar to the M5 305). The PU-BE 422 may also be communicatively coupled to other PU(s) within the RAN DP through different M5 connection(s).

[0136] In some aspects, an M2 connection (e.g., M2 connection 402) or an M5 connection (e.g., M5 connection 305 or 405) as described above may be implemented or supported by a tunnel (referred to as a RAN tunnel). The RAN tunnel may be a Layer 4 (L4) tunnel, and the tunneling protocol(s) for the RAN tunnel may be any of QUIC, QUIC / UDP, and GTP-U / UDP. In some aspects, the RAN tunnel may be supported by IPv4 routing or IPv6 routing at Layer 3 (L3, IP layer).

[0137] An M2 tunnel or an M5 tunnel refers to a tunnel that implements or supports an M2 connection or an M5 connection. Thus, in this application, the terms M2 tunnel and M2 connection are equivalent, and the terms M5 tunnel and M5 connection are equivalent.

[0138] In some aspects, T3 connection 303 in Figure 3 and T3 connection 403 in Figure 4 may correspond to T3 connection 203 in Figure 2 and T3 connection 103 in Figure 1. Each of the T3 connections may be implemented or supported by a tunnel. Thus, as used herein, the terms T3 connection and T3 tunnel may be equivalent.

[0139] In some aspects, referring to FIG. 3, the PU 316 may have a T3 connection 303 connecting the PU 316 to the NPF 212 in the CN DP 122, and the PU 316 may use the T3 connection 303 to interact or communicate with the NPF 212, i.e., to send data traffic to and receive data traffic from the NPF 212. In some aspects, referring to FIG. 4, the PU 416 may not have such a T3 connection with the NPF 212, and may interact or communicate with the NPF 212 in the CN DP 122 via the CU-DP 414, i.e., to send data traffic to and receive data traffic from the NPF 212 via the CU-DP 414. As shown in FIG. 4, the PU 416 may connect to the CU-DP 414 via an M2 connection (or interface) 402. In some aspects, when the PU 416 interacts or communicates with the NPF 212 via the CU-DP 414, data traffic may be transported between the PU and the NPF 212 through a T3 connection 403 (between the CU-DP 414 and the NPF 212) and an M2 connection 402 (between the PU 416 and the CU-DP 414).

[0140] In some aspects, the RAN 110 may include one or more RAN nodes. Each RAN node may include a CU-CP, a CU-DP (e.g., CU-DP 314 or 414), and one or more PUs (e.g., PU 316 or 416). In some aspects, if there are multiple CU-DP(s) or PU(s) within the RAN DP, the multiple CU-DPs or PUs may belong to different RAN nodes within the RAN 110. In some aspects, if a PU-BE (e.g., PU-BE 322 or PU-BE 422) is communicatively coupled to multiple PUs belonging to different RAN nodes, the PU-BE may be shared by different RAN nodes. Similarly, if there are multiple DUs (e.g., DU 312 or 412) within the RAN DP, the multiple DUs may belong to different RAN nodes.

[0141] In some aspects, when there are multiple CU-CPs in a RAN CP, the multiple CU-CPs may belong to different RAN nodes. Generally, a CU-CP of a RAN node can manage or control one or more of the DU, CU-DP(s), and PU(s) of the RAN node. In some aspects, a CU-CP may belong to (i.e., be shared with) multiple RAN nodes, and the CU-CP can manage or control the DU, CU-DP(s), and PU(s) of all these multiple RAN nodes.

[0142] As will be understood by those skilled in the art, a CU-CP, CU-DP, PU, ​​or PU-BE as described herein may be a logical network entity. Any two, three, or all of these may be combined or integrated into a single network entity. Because each of the CU-DP, PU, ​​and PU-BE is part of the RAN DP, each may be a DPF.

[0143] The device 102 can connect to the RAN DP 300 or 400 through an air interface 301 or 401, respectively. As illustrated in FIGS. 3 and 4, the air interface 301 or 401 may be between the device 102 and a distributed unit (DU) 312 or 412 in the RAN DP 300 or 400. In some aspects, when the device 301 accesses a connectivity service offered or provided by a communication system (e.g., a data connectivity service provided by a PDU session in a 5G system), the device may be assigned a data radio bearer (DRB) 307 or 407 over the air interface. In some aspects, when the device 102 accesses a processing service offered or provided by the communication system, the device 102 may be assigned a processing radio bearer (XRB) 308 or 408 over the air interface. The processing service may be offered or provided at least in part by a PF (e.g., PF 222) in the CN DP 122 or a PU-BE 322 or 422 in the RAN DP 300 or 400. The DRB 307 or 407 and the XRB 308 or 408 may both be radio bearers.

[0144] In some aspects, a radio bearer (e.g., the DRB 307 or 308 or XRB 407 or 408 described above) may correspond to a Layer 2 logical channel or tunnel connecting a device (e.g., the device 102) and a RAN DP (e.g., the RAN DP 300 or 400). The radio protocol stack for the radio bearer (i.e., the corresponding Layer 2 logical channel or tunnel) may include a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer, for example, as defined in a 5G system. In the RAN DP, the MAC layer and the RLC layer may be located (executed) in a DU (e.g., the DU 312 or 412), and the PDCP layer and the SDAP layer may be located (executed) in a CU-DP (e.g., the CU-DP 314 or 414) or a PU (e.g., the PU 316 or 416) depending on whether the radio bearer is a DRB or an XRB. For example, if the radio bearer is the DRB 307 or 407, the PDCP layer and the SDAP layer may be located (executed) in the CU-DP 314 or 414. If the radio bearer is the XRB 308 or 408, the PDCP layer and the SDAP layer may be located (executed) in the PU 316 or 416.

[0145] As illustrated in FIGS. 3 and 4 , the DRB 307 or 308 (i.e., the corresponding layer 2 logical channel or tunnel) may connect the device 102 to the CU-DP 314 or 414, while the XRB 308 or 408 (i.e., the corresponding layer 2 logical channel or tunnel) may connect the device 102 to the PU 316 or 416. Compared to the DRB 307 or 407, the XRB 308 or 408 may have simplified protocol behavior at the RLC layer and the PDCP layer. For example, the RLC layer in the XRB 308 or 408 may be in transparent mode (TM) (i.e., no RLC segmentation, no RLC acknowledgement). In some aspects, the PDCP layer in the XRB 308 and 408 may operate without performing one or more of PDCP sequencing and PDCP security. Thus, the protocol stack in the XRB 308 or 408 may operate without performing one or more of PDCP sequencing, PDCP security, RLC segmentation, and RLC acknowledgment. In some aspects, the XRB 308 or 408 may be considered a special type of DRB.

[0146] In some aspects, the DRB 307 or 407 may be assigned to the device 102 by a first RAN controller, which may be part of the CU-CP or separate from the CU-CP. In some aspects, the XRB 308 or 408 may be assigned to the device 102 by a second RAN controller, which may be part of the CU-CP or separate from the CU-CP. In some aspects, the first RAN controller and the second RAN controller may be the same entity, e.g., the first network controller described with reference to FIG. 7.

[0147] 5 illustrates an overall data plane architecture according to one aspect. In one aspect, the overall DP of a communication system may comprise a RAN DP 510 and a CN DP 540. In one aspect, the RAN DP 510 may be similar to the RAN DP 112, 300, or 400. In one aspect, the CN DP 540 may be similar to the CN DP 122.

[0148] In one aspect, a connectivity subplane of the DP as a whole (i.e., a connectivity subplane of the communication system) may include a connectivity subplane of the RAN DP 510 and a connectivity subplane of the CN DP 540. In one aspect, a processing subplane of the DP as a whole (i.e., a processing subplane of the communication system) may include a processing subplane of the RAN DP 510 and a processing subplane of the CN DP 540.

[0149] In one aspect, the RAN DP 510 of the overall DP architecture may have features of both the RAN DP 300 and 400. For example, both the RAN DP architectures 300 and 400 may exist in combination in the overall DP architecture. As illustrated, in one aspect, a first PU 518 in the RAN DP 510 may have a T3 connection 503 with the CN DP 540 (i.e., the NPF 542 in the CN DP 540), while a second PU 516 in the RAN DP 510 may not have a T3 connection with the CN DP 540. The first PU 518 may be similar to the PU 316 (of FIG. 3) that has a T3 connection 303 with the NPF 212. The second PU 516 may be similar to the PU 416 (of FIG. 4) that does not have a T3 connection with the NPF 212. In some embodiments, in addition to the T3 503 connection, the PU 518 may have an M2 502 connection with the CU-DP 514.

[0150] In some aspects, the PF 526 in the CN DP 540 may be shared by the RAN DP 510 in the form of a PU-BE 526. Similarly, the PU-BE 526 in the RAN DP 510 may be shared by the CN DP 540 in the form of a PF 526. Sharing is illustrated in FIG. 5 as indicated by the dashed box. In some aspects, in sharing, a network entity (e.g., the PF 526) connects to the NPF 544 in the CN DP 540 as a PF via a T5 connection 555, and the network entity (e.g., the PU-BE 526) connects to the PU 518 in the RAN DP 510 as a PU-BE via an M5 connection 505.

[0151] In some aspects, each of the PU-BE(s) and PF(s) may be referred to as a Processing Service Function or Processing Subplane Function (PSF) and collectively referred to as a PSF. In some aspects, a PU-BE located in the RAN may be referred to as a RAN PSF, and a PF located in the CN may be referred to as a CN PSF. In some aspects, each of the RAN DP GW(s) (i.e., each of the CU-DP(s), PU(s)) and the CN DP GW(s) (i.e., NPF(s)) may be referred to as a DP GW (and may collectively be referred to as DP GWs). In some aspects, each of the PSF and DP GW may be referred to as a DPF, as described herein.

[0152] According to one aspect, a RAN architecture provides a PU entity as a system component in a RAN node. In some aspects, a RAN controller (e.g., a CU-CP) can configure a PU for PDU header processing and PDU content processing. With this configuration, the PU can perform PDU header processing and PDU content processing.

[0153] In some aspects, a RAN controller (eg, a CU-CP) may configure a CU-DP for PDU header processing, and according to this configuration, the CU-DP may perform PDU header processing accordingly.

[0154] In some aspects, the RAN controller (eg, CU-CP) may allocate an XRB for a device and configure the XRB in the device and the PU according to information received from the CN controller.

[0155] In some aspects, a CN controller (e.g., an SMF in a 5G architecture) may configure an NPF (e.g., an UPF in 5G) for PDU header processing and PDU content processing. According to this configuration, the NPF can perform PDU header processing and PDU content processing. In some aspects, the CN controller can send an instruction to the RAN controller, and the RAN controller can allocate one or more of the DRB or the XRB to the device accordingly.

[0156] One or more aspects of the disclosure described herein may be associated with one or more of the system architectures described with reference to FIGS. 1, 2, 3, 4, and 5.

[0157] A PDU associated with or related to a connectivity service may be a PDU that the connectivity service is routing or transporting. In some aspects, the connectivity service may be provided, for example, as a PDU session in 5G or in the form of a PDU session in 5G.

[0158] A PDU originating from a processing service may be a PDU originating from a PSF as a result of the PSF offering or providing at least a portion of a processing service. A PDU targeted to a processing service may be a PDU sent to a PSF for processing, where the processing is part of the PSF offering or providing at least a portion of a processing service. A PDU associated with or related to a processing service may originate from or target a processing service. In some aspects, a processing service may be associated with an address. The address of the processing service may be used as a source address (e.g., in PDUs originating from a processing service) or a destination address (e.g., in PDUs targeted to a processing service) in data plane traffic, as described in one or more aspects herein.

[0159] A network entity can access processing services offered or provided by the communication system. The network entity may be a device such as UE 102, a server such as an AS in DN 130, a DPF (a network entity in a DP) such as a DP GW, or a PSF. As described herein, a DP GW may be a RAN DP GW 314, 316, 414, 416, 514, 516, 518, or a CN DP GW 212, 542, 544, 546. As further described herein, a PSF may be a RAN PSF 322, 422, 520, 522, 524, and 526, or a CN PSF 222, 526, 548, 550, and 552. When accessing a processing service, the network entity may interact or communicate with a PSF in the processing subplane of the communications system (e.g., which may be a CN PSF 222, 526, 548, 550, and 552, or a RAN PSF 322, 422, 520, 522, 524, and 526), ​​and the PSF may at least partially offer or provide the processing service.

[0160] A network entity may be associated with a DP GW (e.g., DP GW 601 or DP GW 602 in FIG. 6 ) in a connectivity subplane (e.g., RAN DP GWs 314, 316, 414, 416, 514, 516, 518 or CN DP GWs 212, 542, 544, 546) of a communication system and may be connected to the DP GW through a tunnel. In some aspects, if the network entity is a device or a RAN PSF, the DP GW may be a RAN DP GW (e.g., a PU), and if not, it may be a CN DP GW. In some aspects, if the network entity is a device, the tunnel may be (or may correspond to) an XRB. In some aspects, if the network entity is a RAN PSF, the tunnel may correspond to an M5 connection. In some aspects, if the network entity is a CN PSF, the tunnel may correspond to a T5 connection. In some aspects, if the network entity is an AS (in a DN), the tunnel may correspond to a T6 connection.

[0161] In some aspects, the PSF may be associated with a DP GW (e.g., DP GW 601 or DP GW 602 in FIG. 6) in a connectivity subplane of the communication system and may be connected to the DP GW through a connection. The connection is supported by or implemented as a tunnel between the PSF and the DP GW. If the PSF is a RAN PSF, the DP GW may be a RAN DP GW (e.g., a PU), and the connection is an M5 connection. If the PSF is a CN PSF, the DP GW is an NPF, and the connection is a T5 connection. In some aspects, the DP GW associated with a network entity and the DP GW associated with the PSF may be the same or different network entities.

[0162] In some aspects, when a network entity communicates or interacts with a PSF (e.g., using a service-based interface (SBI) as described herein, including with reference to FIG. 6), data may be exchanged or transported between the network entity and the PSF. The data may include, for example, requests and responses as described in connection with FIG. 6. During the exchange or transport of data, the data may be routed through a connectivity subplane of the communication system between the network entity and the PSF, for example, through a DP GW associated with the network entity and a DP GW associated with the PSF. The data may be routed through a tunnel between the network entity and its associated DP GW, and a tunnel between the PSF and its associated DP GW. In some aspects, if the DP GW associated with the network entity and the DP GW associated with the PSF are not the same network entity, the data may be further routed through one or more tunnels connecting the two DP GWs.

[0163] In some aspects, interactions or communications between network entities and PSFs may be based on one or more service-based interfaces (SBIs) in the processing sub-plane above L4 (i.e., on top of the connectivity sub-plane of the communication system through their associated DP GWs). In some aspects, the SBIs may be in the form of remote procedure calls (RPCs), as illustrated in FIG.

[0164] 6 illustrates a remote procedure call (RPC) procedure 600, according to one embodiment. The procedure 600 may be executed in a processing subplane of a communication system.

[0165] For example, one of the network entity and the PSF may execute or initiate an RPC and is referred to as the caller 604. When executing or initiating an RPC, the caller 604 may remotely invoke a procedure (or function or API) supported or implemented by the other of the network entity and the PSF (referred to as the callee 606) and receive one or more results of the execution of the procedure from the callee 606.

[0166] In one aspect, when invoking a procedure (e.g., to execute a corresponding RPC), the caller 604 may send a request 612 (e.g., an HTTP (Hypertext Transfer Protocol) request) to the callee 606. The request may include information identifying the procedure (e.g., a name or ID) and information regarding the procedure's input parameter(s), such as one or more of the name(s) or ID(s) and their respective values. Upon receiving the request 612, the callee 606 may use the information regarding the input parameter(s) included in the request to execute or perform the procedure (as identified in the request) according to the request (614). The callee 606 may then send a response 616 (e.g., an HTTP response) to the caller 604. The response 616 may include one or more results of the execution of the procedure. For each of the one or more results, the response may include the name or ID of the result and a respective result value.

[0167] In some aspects, the format of the SBI from the perspective of the caller may not be the same as the format of the SBI from the perspective of the callee. For example, if the SBI is implemented as a PRC as described herein, information indicating one or more of the procedure (e.g., the name or ID of the procedure) and the input parameters of the procedure (e.g., the name(s) or ID(s) of the input parameter(s)) may not be understood, or may not be understood as expected, by the callee 606. Similarly, a response including information indicating one or more of the results (e.g., the name(s) or ID(s) of the result) may not be understood, or may not be understood as expected, by the caller 604. Thus, in some aspects, SBI adaptation may be required so that the caller 604 and the callee 606 can understand each other (i.e., understand the information in the request or the information in the response, as described herein).

[0168] In some aspects, the DP GW associated with the caller 604 may be denoted as DP GW601, and the DP GW associated with the callee may be denoted as DP GW602.

[0169] In some aspects, DP GW601 and DP GW602 may be the same or different network entities. SBI adaptation may be performed by one or more DP GWs, e.g., DP GW601 and DP GW602. In one aspect, caller 604 may execute or initiate an RPC in its own format. When request 612 associated with an RPC is transported to callee 606 through one or more DP GWs (e.g., DP GW601 and DP GW602), in one aspect, the DP GW may convert, translate, or map some or all of the information in the request (i.e., a first name or ID of the procedure, a first name or ID of an input parameter of the procedure) to information that can be understood by callee 606 (i.e., a second name or ID of the procedure, a second name or ID of an input parameter of the procedure). Thus, when callee 606 receives request 612, the request includes the converted information (i.e., a second name or ID of the procedure, a second name or ID of an input parameter of the procedure).

[0170] After performing the procedure identified in the request, callee 606 can send response 616 in its own format. When the response is transported to caller 604 through one or more DP GWs (e.g., DP GW 602 and DP GW 601), in one aspect, the DP GWs can translate, transform, or map information in the response (i.e., the first name or ID of the result) to information that can be understood by caller 604 (i.e., the second name or ID of the result). Thus, when caller 604 receives response 616, response 616 includes the translated information (i.e., the second name or ID of the result).

[0171] As can be appreciated by those skilled in the art, when performing SBI adaptation as described herein, one or more DP GWs (e.g., DP GW 601 and DP GW 602) can process the content of communications (i.e., data exchanged or transported) between the caller 604 and the callee 606. The data exchanged or transported between the caller 604 and the callee 606 can include a request 612 and a response 616, as described in connection with FIG. 6. When transported, the data is carried or included within data traffic. The data traffic can include one or more PDUs. Each of these PDUs can include a PDU header and a PDU payload, where the PDU header can include information related to routing and the PDU payload can include at least a portion of the data.

[0172] In one aspect, when request 612 is being transported from caller 604 to callee 606 through DP GW 601 and DP GW 602, request 612 may be included in one PDU or segmented into multiple fragments, with each fragment being included in a different PDU at DP GW 601 (thus resulting in multiple PDUs). DP GW 601 may then transmit one or more PDUs to DP GW 602. In some aspects, DP GW 601 may be configured to perform SBI adaptation for the request prior to transmission of the one or more PDUs. In some aspects, once request 612 is segmented into multiple PDUs by DP GW 601, DP GW 602 may reassemble the multiple PDUs (i.e., data included in the payloads of the multiple PDUs) to obtain the request. In some aspects, DP GW 602 may be configured to perform SBI adaptation for the request (i.e., transform information in the request) after reassembly.

[0173] In some aspects, when response 616 is being transported from callee 606 to caller 604 through DP GW 602 and DP GW 601, response 616 may be included in one PDU or segmented into multiple pieces, with each piece being included in a different PDU at DP GW 602 (thus resulting in multiple PDUs). DP GW 602 may then transmit one or more PDUs to DP GW 601. In some aspects, DP GW 602 may be configured to perform SBI adaptation for the response prior to transmission of the one or more PDUs. In some aspects, if response 616 may be segmented into multiple PDUs by DP GW 602, DP GW 601 may reassemble the multiple PDUs to obtain response 616. In some aspects, DP GW 601 may be configured to perform SBI adaptation for response 616 (i.e., transform information in the response) after reassembly.

[0174] The connectivity subplane of a communication system may include one or more DP GWs, as illustrated in FIG. 5, for example. When a PDU is routed through the connectivity subplane, the DP GW may handle the PDU, including receiving, processing, and retransmitting the PDU. The PDU may be associated with a network entity, such as the network entity described in connection with FIG. 6. The PDU may originate from the network entity or may be targeted to the network entity (i.e., the network entity is the destination of the PDU). For example, the PDU may be part of data traffic carrying data exchanged between the caller 604 and the callee 606 of FIG. 6, and the DP GW may be DP GW 601 or 602 of FIG. 6.

[0175] In some aspects, when processing a PDU, the DP GW may process a PDU header of the PDU, where the processing of the header may cause content or information in the PDU header to be updated or modified. According to one aspect, how the DP GW may process a PDU header of a PDU, i.e., the behavior of the DP GW related to the processing of the PDU header, is described.

[0176] According to one or more aspects, the behavior of the DP GW is described when the DP GW is a RAN DP GW (i.e., RAN DP GW behavior) and the DP GW is, for example, a RAN DP GW as described in connection with FIGS. 3, 4, and 5, and when the DP GW is a CN DP GW (i.e., CN DP GW behavior) and the CN GW is, for example, a CN DP GW as described in connection with FIGS. 2 and 5.

[0177] According to one aspect, the RAN DP GW behavior is described when a PDU is received from a tunnel other than a radio bearer (e.g., the PDU is not received from a radio bearer). For example, the RAN DP GW may receive a PDU from a tunnel that is not a radio bearer (e.g., a DRB or XRB). In one aspect, the PDU may originate from a network entity, which may be a PSF, an AS (in a DN), or a device (e.g., a UE). The network entity may be referred to as the originator. The tunnel may be referred to as a receiving tunnel. The receiving tunnel may have two endpoints. The endpoint that receives the PDU is referred to as the receiving end, and the endpoint that transmits the PDU is referred to as the transmitting end. The receiving end of the receiving tunnel is the RAN DP GW, and the transmitting end may or may not be within the RAN as described herein.

[0178] The receiving tunnel may be (1) a T3 tunnel and the transmitting end is a CN DP GW. In some aspects, the receiving tunnel may be (2) an M4 tunnel and the transmitting end is a second RAN DP GW. In some aspects, the receiving tunnel may be (3) an M5 tunnel and the transmitting end is a RAN PSF. In some aspects, the receiving tunnel may be (4) an M2 tunnel and the transmitting end is a third RAN DP GW.

[0179] The RAN DP GW may be a CU-DP or a PU if the receiving tunnel is a T3 tunnel (e.g., the transmitting end is a CN DP GW) or an M2 tunnel (e.g., the transmitting end is a third RAN DP GW). The RAN DP GW may be a PU if the receiving tunnel is an M4 tunnel (e.g., the transmitting end is a second RAN DP GW) or an M5 tunnel (e.g., the transmitting end is a RAN PSF). Thus, the RAN DP GW may be a CU-DP or a PU in cases (1) and (4), and a PU in cases (2) and (3).

[0180] The source may be an AS or PSF in case (1), a RAN PSF communicatively coupled to the second RAN DP GW in case (2), a RAN PSF in case (3), or an AS or PSF in case (4). Those skilled in the art can understand that in case (3), the transmitting end of the receiving tunnel is the source.

[0181] In some aspects, the PDU header of the PDU includes a first L3 header and a first L4 header. The first L3 header may include one or more of a source address referred to as SRC1 and a destination address referred to as DST1. The first L3 header may further include QoS information referred to as QoS1. QoS1 may identify a class or priority of the PDU or a QoS flow to which the PDU belongs.

[0182] In some aspects, SRC1 is the address of the transmitting end. If the transmitting end belongs to a RAN node (e.g., when the transmitting end is a RAN DP GW belonging to that RAN node), the address of the transmitting end may be the address of that RAN node. In some aspects, SRC1 is the address of the originator. In some embodiments, if the PDU originates from a processing service, SRC1 may be the address of the processing service.

[0183] In some aspects, DST1 is the address of the RAN DP GW. If the RAN DP GW belongs to a RAN node, the address of the RAN DP GW may be the address of the RAN node. In some aspects, if the PDU is targeted to a processing service, DST1 may be the address of the processing service.

[0184] The first L4 header may include a connection ID referred to as CON1. ​​In some aspects, CON1 may identify an incoming tunnel. In some aspects, if the incoming tunnel is associated with a processing service or if the PDU is associated with a processing service, CON1 identifies or corresponds to a connection between the originator of the PDU and the final destination of the PDU. In some aspects, if the incoming tunnel is associated with a connectivity service or if the PDU is associated with a connectivity service, CON1 identifies or corresponds to a connection between the two network entities when the connectivity service connects two network entities (e.g., a device in a DN and an AS). The first L4 header may further include a stream ID referred to as STR1. In some aspects, STR1 may identify a stream of traffic associated with the connection identified by CON1.

[0185] In some aspects, after receiving the PDU, the RAN DP GW may identify another tunnel, referred to as a transmission tunnel. The RAN DP GW can transmit or send the PDU using the transmission tunnel. In some aspects, the reception tunnel is mapped to the transmission tunnel, and the RAN DP GW identifies the transmission tunnel according to the mapping.

[0186] In some aspects, the RAN DP GW may identify the transmission tunnel using information in the PDU header of the PDU. In some aspects, CON1 (i.e., the connection ID in the first L4 header) corresponds to or maps to another connection ID CON2 that identifies the transmission tunnel, and according to the mapping, the RAN DP GW identifies the transmission tunnel.

[0187] In some aspects, CON1 and QoS1 (ie, the QoS information in the first L3 header) both correspond to or map to CON2, and according to the mapping, the RAN DP GW identifies the transport tunnel.

[0188] In some aspects, the mapping used by the RAN DP GW to identify a transport tunnel as described herein may be provided to the RAN DP GW from a network controller, such as the first network controller of FIG. 7.

[0189] In one aspect, the transmission tunnel has two endpoints. The endpoint that receives the PDU is called the receiving end, and the endpoint that transmits the PDU is called the transmitting end. The transmitting end is a RAN DP GW. The receiving end may or may not be within the RAN, as described in one or more aspects herein.

[0190] In one aspect, the RAN DP GW is a CU-DP (e.g., CU-DP 414 or 514). As an example, if the PDU is related to or associated with a processing service and if the receiving tunnel is a T3 tunnel (e.g., T3 403 or 503), the transmitting tunnel may be an M2 tunnel (e.g., M2 402 or 502), and the receiving end is another RAN DP GW (a PU, e.g., PU 416 or 518). When the RAN DP GW transmits or sends a PDU using the transmitting tunnel, the PDU is sent to the other RAN DP GW.

[0191] In one aspect, the RAN DP GW is a CU-DP (e.g., CU-DP 414 or 514). As an example, if the PDU is related to or associated with a processing service, and if the receiving tunnel is an M2 tunnel, e.g., M2 402 or 502, the transmission tunnel may be a T3 tunnel (e.g., T3 403 or 503), and the receiving end of the transmission tunnel is a CN DP GW (e.g., NPF 212 or 542). When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the CN DP GW (e.g., NPF 212 or 542).

[0192] In one aspect, the RAN DP GW is a CU-DP (e.g., CU-DP 314 or 414). As an example, if the PDU is related to or associated with a connectivity service (and in this case the receiving tunnel is a T3 tunnel (e.g., 303 or 403)), the transmission tunnel may be a DRB (e.g., DRB 307 or 407) associated with a device, and the receiving end is the device (e.g., device 102). When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the device. The device may be the final destination of the PDU.

[0193] In one aspect, the RAN DP GW is a PU, and the PDU is associated with or related to a processing service. As an example, the transmission tunnel is an M4 tunnel (e.g., M4 304, 404, or 504), and the receiving end is another RAN DP GW (also a PU). When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the other RAN DP GW. The receiving tunnel may be a T3 tunnel (e.g., T3 303, 304, or 503), an M2 (e.g., M2 402 or 502), or an M5 tunnel (e.g., M5 305, 405, or 505).

[0194] In one aspect, the RAN DP GW is a PU, and the PDU is associated with or associated with a processing service. As an example, the transmission tunnel may be an XRB (e.g., XRB 308 or 408) associated with a device, and the receiving end is the device 102. When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the device. The device may be the final destination of the PDU. The receiving tunnel may be a T3 tunnel (e.g., T3 303 or 503), an M2 tunnel (e.g., M2 402 or 502), an M4 tunnel (e.g., M4 304, 404, or 504), or an M5 tunnel (e.g., M4 304, 404, or 504).

[0195] In one aspect, the RAN DP GW is a PU, and the PDU is associated with or associated with a processing service. As an example, the transmission tunnel may be an M5 tunnel (e.g., M5 305, 405, or 505), and the receiving end is a RAN PSF (e.g., PUE-BE 322, 422, or 524). When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the RAN PSF. The RAN PSF may be the final destination of the PDU. The receiving tunnel may be a T3 tunnel (e.g., 303 or 503), an M2 tunnel (e.g., M2 402 or 502), or an M4 tunnel (e.g., M4 304, 404, or 504).

[0196] In some aspects, the RAN DP GW may process a PDU header of a PDU before transmitting or sending the PDU using the transmission tunnel.

[0197] When processing the PDU header, the RAN DP GW may perform an L3 proxy. In some embodiments, when performing the L3 proxy, the RAN DP GW replaces a first L3 header with a second L3 header (e.g., removes the first L3 header from the PDU header and adds the second L3 header to the PDU header). In some aspects, when performing the L3 proxy, the RAN DP GW modifies or changes the first L3 header to the second L3 header.

[0198] In some aspects, the second L3 header includes a source address (referred to as SRC2). In some aspects, SRC2 may be the same as SRC1 (i.e., the source address in the first L3 header). In some aspects, SRC2 may be different from SRC1. In some aspects, SRC2 is the address of the RAN DP GW. In some aspects, if the PDU originates from a processing service, SRC2 is the address of the processing service.

[0199] In some aspects, the second L3 header may further include a destination address (referred to as DST2). In some embodiments, DST2 may be the same as DST1 (i.e., the destination address in the first L3 header). In some aspects, DST2 is different from DST1. In some aspects, DST2 is the address of the receiving end of the transmission tunnel. In some embodiments, if the PDU is targeted to a processing service, DST2 is the address of the processing service. In some embodiments, if the transmission tunnel is a radio bearer (e.g., a DRB or XRB) associated with a device, DST2 is the address of the device, and the device may be the final destination of the PDU.

[0200] In some aspects, the second L3 header may further include QoS information (referred to as QoS2). QoS2 may identify the class or priority of the PDU or the QoS flow to which the PDU belongs. In some aspects, QoS2 is the same as QoS1 (i.e., the QoS information in the first L3 header). In some aspects, QoS2 is different from QoS1. When QoS2 and QoS1 are different, the difference can enable or allow the PDU to be moved between different classes, priorities, or QoS flows and to treat the PDU differently at different locations in the network, for example, due to different network conditions (e.g., delay, delay jitter, throughput, bandwidth, congestion) at those locations. The difference in QoS information can further enable or allow the PDU to be treated differently at different locations in the network to ensure end-to-end QoS performance of the PDU and to balance the QoS performance of different PDUs.

[0201] In some aspects, the RAN DP GW further performs an L4 proxy when processing the PDU header. In some aspects, when performing the L4 proxy, the RAN DP GW replaces the first L4 header with a second L4 header (e.g., removes the first L4 header from the PDU header and adds the second L4 header to the PDU header). In some aspects, when performing the L4 proxy, the RAN DP GW modifies or changes the first L4 header to the second L4 header. In some aspects, if the transmission tunnel is not a DRB or an XRB, the second L4 header is a tunnel header of the transmission tunnel.

[0202] In some aspects, the second L4 header may include a connection ID. The connection ID in the second L4 header may be different from the connection ID (CON1) in the first L4 header. The connection ID in the second L4 header may identify a transmission tunnel. In some aspects, the connection ID in the second L4 header is CON2 (which identifies a transmission tunnel) as described herein.

[0203] In some aspects, when the transmission tunnel is associated with a processing service or when the PDU is associated with a processing service, CON2 identifies or corresponds to a connection between the originator of the PDU and the final destination of the PDU. In some aspects, when the transmission tunnel is associated with a connectivity service or when the PDU is associated with a connectivity service, when the connectivity service connects two network entities (e.g., a device in a DN and an AS), CON2 identifies or corresponds to a connection between the two network entities.

[0204] In some aspects, the second L4 header may further include a stream ID referred to as STR2. In some aspects, STR2 may identify a stream of traffic associated with the connection identified by CON2. In some aspects, STR2 is the same as STR1 (i.e., the stream ID in the first L4 header). In some aspects, STR2 is different from and is mapped from STR1. In some aspects, the mapping from STR1 to STR2 is provided to the RAN DP GW from a network controller, e.g., the first network controller or the second network controller of FIG. 7. In some aspects, the stream of traffic identified by STR2 is the stream of traffic identified by STR1.

[0205] According to one aspect, the RAN DP GW behavior is described when a PDU is received from a radio bearer.

[0206] The RAN DP GW may receive a PDU from a radio bearer associated with the device 102, e.g., the DRB 307 or 407 or the XRB 308 or 408. The radio bearer may correspond to or be considered as a logical tunnel between the device and the RAN DP GW. In some aspects, the PDU may be considered to originate from the device, and the device may be referred to as the originator. The radio bearer may be referred to as a receiving tunnel. In one aspect, the receiving tunnel has two endpoints. The endpoint that receives the PDU is referred to as the receiving end, and the endpoint that transmits the PDU is referred to as the transmitting end. The transmitting end is the originator (i.e., the device), and the receiving end is the RAN DP GW.

[0207] In some aspects, if the RAN DP GW is a CU-DP (e.g., CU-DP 314 or 414), the receiving tunnel may be (1) a DRB (e.g., DRB 307 or 407). In some aspects, if the RAN DP GW is a PU (e.g., PU 316 or 416), the receiving tunnel may be (2) an XRB (e.g., XRB 308 or 408). The PDU may be associated with a connection service in case (1) where the receiving tunnel is a DRB, and with a processing service in case (2) where the receiving tunnel is an XRB.

[0208] In one aspect, the PDU header of the PDU includes a first L3 header and a first L4 header. The first L3 header may include one or more of a source address referred to as SRC1 and a destination address referred to as DST1. The first L3 header may further include QoS information referred to as QoS1. QoS1 may identify a class or priority of the PDU or a QoS flow to which the PDU belongs.

[0209] In some aspects, SRC1 is the address of the transmitting end, the device (i.e., the source). In some aspects, if the receiving tunnel is associated with a processing service (e.g., if the receiving tunnel is an XRB that the device uses to access the processing service) or if the PDU is targeted at a processing service, DST1 may be the address of the processing service or the address of a PSF that offers or provides at least a portion of the processing service. In some aspects, DST1 may be the address of a RAN DP GW. If the RAN DP GW belongs to a RAN node, the address of the RAN DP GW may be the address of the RAN node.

[0210] The first L4 header may include a connection ID referred to as CON1. ​​In some aspects, if the incoming tunnel is associated with a processing service (e.g., if the incoming tunnel is an XRB that the device uses to access the processing service) or if the PDU is associated with a processing service, CON1 identifies or corresponds to a connection between the device and the processing service (e.g., a PSF that offers or provides at least a portion of the processing service). In some aspects, if the incoming tunnel is associated with a connectivity service (e.g., if the incoming tunnel is a DRB that the device uses to access the connectivity service) or if the PDU is associated with a connectivity service, CON1 identifies or corresponds to a connection between the device and the DN (i.e., an AS) when the connectivity service connects the device and the DN (e.g., an AS within the DN). The first L4 header may further include a stream ID referred to as STR1. In some aspects, STR1 may identify a stream of traffic associated with the connection identified by CON1.

[0211] In some aspects, after receiving the PDU, the RAN DP GW identifies another tunnel, referred to as a transmission tunnel, and transmits or sends the PDU using the transmission tunnel.

[0212] In some aspects, a receive tunnel is mapped to a transmit tunnel, and the RAN DP GW may identify the transmit tunnel according to the mapping. In some aspects, the RAN DP GW may identify the transmit tunnel using information in a PDU header of the PDU. In some aspects, CON1 (i.e., a connection ID in the first L4 header) corresponds to or maps to another connection ID CON2 that identifies the transmit tunnel, and the RAN DP GW identifies the transmit tunnel according to the mapping. In some aspects, CON1 and QoS1 (i.e., QoS information in the first L3 header) both correspond to or map to CON2, and the RAN DP GW identifies the transmit tunnel according to the mapping. In some aspects, the mapping that the RAN DP GW uses to identify the transmit tunnel as described herein is provided to the RAN DP GW from a network controller, such as the first network controller of FIG. 7.

[0213] A transmission tunnel may have two endpoints: the endpoint that receives the PDU is called the receiving end, and the endpoint that transmits the PDU is called the transmitting end. The transmitting end is a RAN DP GW, and the receiving end may or may not be within the RAN as described herein.

[0214] In one aspect, the RAN DP GW may be a CU-DP (e.g., CU-DP 314, 414, or 514). The PDU may be related or associated with a connectivity service, the transmission tunnel may be a T3 tunnel (e.g., T3 303, 403, or 503), and the receiving end is a CN DP GW (e.g., NPF 212 or 542) in the CN DP. When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the CN DP GW.

[0215] In one aspect, the RAN DP GW is a PU (e.g., PU 316, 416, 516, or 518). The PDU may be associated with or associated with a processing service, and the transmission tunnel may be an M2 tunnel (e.g., M2 402 or 504), an M4 tunnel (e.g., 304, 404, 504), or an M5 tunnel (M5 305, 405, or 505).

[0216] In one aspect, the RAN DP GW is a PU (e.g., PU 316 or 518). As an example, the transmission tunnel is a T3 tunnel (e.g., 303 or 503), and the receiving end is a CN DP GW (e.g., NPF 212 or 542). When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the CN DP GW.

[0217] In one aspect, the RAN DP GW is a PU (e.g., PU 416 or 518). As an example, the transmission tunnel is an M2 tunnel (M2 414 or 502), and the receiving end is a CU-DP (e.g., CU-DP 414 or 514). When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the CU-DP.

[0218] In one aspect, the RAN DP GW is a PU (e.g., PU 316, 416, 516, or 518). As an example, the transmission tunnel is an M4 tunnel (e.g., M4 304, 404, or 504), and the receiving end is another PU. The other PU may be communicatively coupled to a RAN PSF that at least partially provides or offers processing services, and the RAN PSF may be the final destination of the PDU. When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the other PU.

[0219] In one aspect, the RAN DP GW is a PU (e.g., PU 316, 416, 516, or 518). As an example, the transmission tunnel is an M5 tunnel (e.g., M5 305, 405, or 505), and the receiving end is a RAN PSF (e.g., PU-BE 322, 422, or 524). The RAN PSF can at least partially provide or offer the processing service. When the RAN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the RAN PSF. The RAN PSF can be the final destination of the PDU.

[0220] In one aspect, the RAN DP GW may process the PDU header of the PDU before transmitting or sending the PDU using the transport tunnel.

[0221] When processing the PDU header, the RAN DP GW may perform an L3 proxy. In some aspects, when performing the L3 proxy, the RAN DP GW replaces a first L3 header with a second L3 header (e.g., removes the first L3 header from the PDU header and adds the second L3 header to the PDU header). In some aspects, when performing the L3 proxy, the RAN DP GW modifies or changes the first L3 header to the second L3 header.

[0222] In some aspects, the second L3 header includes a source address (referred to as SRC2). In some aspects, SRC2 is the same as SRC1 (i.e., the source address in the first L3 header). In some aspects, SRC2 is different from SRC1. In some aspects, SRC2 is the address of the RAN DP GW.

[0223] In some aspects, the second L3 header includes a destination address (referred to as DST2). In some aspects, DST2 is the same as DST1 (i.e., the destination address in the first L3 header). In some aspects, DST2 is different from DST1. In some aspects, DST2 is an address of the receiving end of the transmission tunnel. In some aspects, if the PDU is targeted for a processing service, DST2 is an address of an NSF offering or providing at least a portion of the processing service.

[0224] In some aspects, the second L3 header includes QoS information (referred to as QoS2). QoS2 may identify the class or priority of the PDU or the QoS flow to which the PDU belongs. In some aspects, QoS2 is the same as QoS1 (i.e., the QoS information in the first L3 header). In some aspects, QoS2 is different from QoS1. When QoS2 and QoS1 are different, the difference enables or allows the PDU to move between different class, priority, or QoS flows and to be treated differently in different tunnels, for example, due to different network conditions (e.g., delay, delay jitter, throughput, bandwidth, congestion) at the locations through which the different tunnels traverse. The difference in QoS information may further enable or allow the PDU to be treated differently in different tunnels to ensure end-to-end QoS performance of the PDU and to balance the QoS performance of different PDUs.

[0225] When processing the PDU header, the RAN DP GW may further perform an L4 proxy. In some aspects, when performing the L4 proxy, the RAN DP GW replaces the first L4 header with a second L4 header (e.g., removes the first L4 header from the PDU header and adds the second L4 header to the PDU header). In some aspects, when performing the L4 proxy, the RAN DP GW modifies or changes the first L4 header to a second L4 header. The second L4 header may be a tunnel header of the transmission tunnel.

[0226] The second L4 header may include a connection ID. The connection ID in the second L4 header may be different from CON1 (i.e., the connection ID in the first L4 header). The connection ID in the second L4 header may identify a transmission tunnel. In some aspects, the connection ID in the second L4 header is CON2 (which identifies a transmission tunnel) as described herein.

[0227] In some aspects, the second L4 header may further include a stream ID referred to as STR2. In some aspects, STR2 may identify a stream of traffic associated with the connection identified by CON2. In some aspects, STR2 is the same as STR1 (i.e., the stream ID in the first L4 header). In some aspects, STR2 is different from and is mapped from STR1. In some aspects, the mapping from STR1 to STR2 is provided to the RAN DP GW from a network controller, e.g., the first network controller or the second network controller of FIG. 7. In some aspects, the stream of traffic identified by STR2 is the stream of traffic identified by STR1.

[0228] According to one or more embodiments, CN DP GW behavior is described.

[0229] In one aspect, the CN DP GW can receive the PDU. The PDU can be received from a tunnel referred to as a receive tunnel. The receive tunnel can have two endpoints. The endpoint that receives the PDU can be referred to as a receive end, and the endpoint that transmits the PDU is referred to as a transmit end. The receive end can be a CN DP GW. The transmit end can be within the RAN, the CN, or the DN, as described herein.

[0230] In some aspects, the receiving tunnel may be (1) a T3 tunnel, with the transmitting end in the RAN, e.g., a RAN DP GW. In some aspects, the receiving tunnel may be (2) a T4 tunnel, with the transmitting end in another CN DP GW. In some aspects, the receiving tunnel may be (3) a T5 tunnel, with the transmitting end in a CN PSF. In some aspects, the receiving tunnel may be (4) a T6 tunnel, with the transmitting end in a DN (e.g., an AS).

[0231] In one aspect, the PDU may originate from a network entity, which may be a device, a PSF, or an AS (within the DN). The network entity may be referred to as an originator. In some aspects, the origin of the PDU may be a device or a RAN PSF, the receiving tunnel is a T3 tunnel, and the transmitting end is within the RAN. In some aspects, the origin of the PDU may be a device, a RAN PSF, a CN PSF, or an AS, the receiving tunnel is a T4 tunnel, and the transmitting end is another CN DP GW. In some aspects, the origin of the PDU may be a CN PSF, the receiving tunnel is a T5 tunnel, and the transmitting end is within the CN PSF. In some aspects, the origin of the PDU may be an AS, the receiving tunnel is a T6 tunnel, and the transmitting end is within the DN.

[0232] Thus, the source of the PDU may be a device or a RAN PSF in case (1), a device, a RAN PSF, a CN PSF, or an AS in case (2), a CN PSF in case (3), or an AS in case (4). In case (4), the source may be the source. If the source of the PDU is an AS, the AS is within the first DN. The PDU may target a device, a PSF (RAN PSF or CN PSF), or a second DN (e.g., an AS within the second DN).

[0233] In one aspect, the PDU header of the PDU includes a first L3 header and a first L4 header. The first L3 header may include one or more of a source address referred to as SRC1 and a destination address referred to as DST1.

[0234] In some aspects, SRC1 may be the address of the transmitting end. If the transmitting end belongs to a RAN node (e.g., when the transmitting end is a RAN DP GW belonging to the RAN node), the address of the transmitting end may be the address of the RAN node.

[0235] In some aspects, SRC1 may be the address of the originator. In some aspects, the PDU may originate from a processing service (e.g., a PSF that offers or provides the processing service), and SRC1 may be the address of the processing service.

[0236] In some aspects, DST1 may be the address of a CN DP GW. In some aspects, the PDU may target a processing service (e.g., a PSF that offers or provides the processing service), and DST1 may be the address of the processing service.

[0237] The first L3 header may further include QoS information referred to as QoS1, which may identify the class or priority of the PDU or the QoS flow to which the PDU belongs.

[0238] The first L4 header may include a connection ID referred to as CON1. ​​In some aspects, CON1 identifies an incoming tunnel. In some aspects, if the incoming tunnel is associated with a processing service or if the PDU is associated with a processing service, CON1 identifies or corresponds to a connection between the originator of the PDU and the final destination of the PDU. In some aspects, if the incoming tunnel is associated with a connectivity service or if the PDU is associated with a connectivity service, CON1 identifies or corresponds to a connection between the two network entities when the connectivity service connects two network entities (e.g., a device in a DN and an AS). The first L4 header may further include a stream ID referred to as STR1. In some aspects, STR1 may identify a stream of traffic associated with the connection identified by CON1.

[0239] After receiving the PDU, the CN DP GW may identify another tunnel, referred to as a transmission tunnel. The CN DP GW can transmit or send the PDU using the transmission tunnel. In some aspects, the reception tunnel is mapped to the transmission tunnel, and the CN DP GW identifies the transmission tunnel according to the mapping.

[0240] In some aspects, the CN DP GW may identify the transmission tunnel using information in the PDU header of the PDU. In some aspects, CON1 (i.e., the connection ID in the first L4 header) corresponds to or maps to another connection ID CON2 that identifies the transmission tunnel, and the CN DP GW identifies the transmission tunnel according to the mapping. In some aspects, CON1 and QoS1 (i.e., the QoS information in the first L3 header) both correspond to or map to CON2, and the CN DP GW identifies the transmission tunnel according to the mapping. In some aspects, the mapping that the CN DP GW uses to identify the transmission tunnel as described above is provided to the CN DP GW from a network controller, such as the second network controller of FIG. 7.

[0241] A transmission tunnel may have two endpoints: the endpoint that receives the PDU is called the receiving end, and the endpoint that transmits the PDU is called the transmitting end. The transmitting end is the CN DP GW, and the receiving end may be in the RAN, CN, or DN as described herein.

[0242] In some aspects, the transmission tunnel is a T3 tunnel (e.g., T3 303, 403, or 503), and the receiving end is a RAN DP GW in the RAN DP (e.g., CU-DP 314, 414, 514, or PU 316 or 518). When the CN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the RAN DP GW.

[0243] In some aspects, the transmission tunnel is a T4 tunnel (e.g., T4 204 or 554) and the receiving end is another CN DP GW. When a CN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the other CN DP GW.

[0244] In some aspects, when a PDU is associated or associated (targeted) with a processing service, the transmission tunnel is a T5 tunnel (e.g., T5 205 or 555) and the receiving end is a CN PSF (e.g., PF 222 or 548). The CN PSF can at least partially provide or offer the processing service. When the CN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the CN PSF. In some aspects, the CN PSF can be the final destination of the PDU.

[0245] In some aspects, the transmission tunnel is a T6 tunnel (e.g., T6 206 or 556) and the receiving end is at the DN 130 (e.g., an AS within the DN). When the CN DP GW transmits or sends a PDU using the transmission tunnel, the PDU is sent to the AS. The AS may or may not be the final destination of the PDU.

[0246] In some aspects, the CN DP GW may process a PDU header of a PDU before transmitting or sending the PDU using the transmission tunnel.

[0247] When processing the PDU header, the CN DP GW may perform an L3 proxy. In some aspects, when performing the L3 proxy, the CN DP GW replaces a first L3 header with a second L3 header (e.g., removes the first L3 header from the PDU header and adds the second L3 header to the PDU header). In some embodiments, when performing the L3 proxy, the CN DP GW modifies or changes the first L3 header to the second L3 header.

[0248] In some aspects, the second L3 header may include a source address (referred to as SRC2). In some aspects, SRC2 is the same as SRC1 (i.e., the source address in the first L3 header). In some aspects, SRC2 is different from SRC1. In some aspects, SRC2 is an address of the CN DP GW. In some aspects, SRC2 is an address of the originator of the PDU. In some aspects, if the PDU originates from a processing service (e.g., a PSF that offers or provides the processing service), SRC2 is the address of the processing service.

[0249] In some aspects, the second L3 header may include a destination address (referred to as DST2). In some aspects, DST2 is the same as DST1 (i.e., the destination address in the first L3 header). In some aspects, DST2 is different from DST1. In some aspects, DST2 is an address of the receiving end of the transmission tunnel. In some aspects, if the PDU is targeted at a processing service, DST2 is an address of a processing service or PSF that offers or provides at least a portion of the processing service.

[0250] The second L3 header may further include QoS information (referred to as QoS2). QoS2 may identify the class or priority of the PDU or the QoS flow to which the PDU belongs. In some aspects, QoS2 is the same as QoS1 (i.e., the QoS information in the first L3 header). In some aspects, QoS2 is different from QoS1. When QoS2 and QoS1 are different, the difference may enable or allow PDUs to move between different class, priority, or QoS flows and treat PDUs differently in different tunnels due to, for example, different network conditions (e.g., delay, delay jitter, throughput, bandwidth, congestion) at the locations through which the different tunnels traverse. The difference in QoS information may further enable or allow PDUs to be treated differently in different tunnels to ensure end-to-end QoS performance of the PDUs and balance the QoS performance of different PDUs.

[0251] In some aspects, the CN DP GW may further perform an L4 proxy when processing the PDU header. In some aspects, when performing the L4 proxy, the CN DP GW replaces the first L4 header with a second L4 header (e.g., removes the first L4 header from the PDU header and adds the second L4 header to the PDU header). In some aspects, when performing the L4 proxy, the CN DP GW modifies or changes the first L4 header to a second L4 header. In some aspects, the second L4 header may be a tunnel header of a transmission tunnel.

[0252] The second L4 header may include a connection ID. The connection ID in the second L4 header may be different from CON1 (i.e., the connection ID in the first L4 header). The connection ID in the second L4 header may identify a transmission tunnel. In some aspects, the connection ID in the second L4 header is CON2, which identifies a transmission tunnel as described herein.

[0253] In some aspects, when the transmission tunnel is associated with a processing service or when the PDU is associated with a processing service, CON2 identifies or corresponds to a connection between the originator of the PDU and the final destination of the PDU. In some aspects, when the transmission tunnel is associated with a connectivity service or when the PDU is associated with a connectivity service, when the connectivity service connects two network entities (e.g., a device in a DN and an AS), CON2 identifies or corresponds to a connection between the two network entities.

[0254] In some aspects, the second L4 header may further include a stream ID referred to as STR2. In some aspects, STR2 may identify a stream of traffic associated with the connection identified by CON2. In some aspects, STR2 is the same as STR1 (i.e., the stream ID in the first L4 header). In some aspects, STR2 is different from and is mapped from STR1. In some aspects, the mapping from STR1 to STR2 is provided to the CN DP GW from a network controller, e.g., the second network controller of FIG. 7. In some aspects, the stream of traffic identified by STR2 is the stream of traffic identified by STR1.

[0255] According to one or more aspects, allocation of radio bearers is described. As described in connection with Figures 3 and 4, there may be two types of radio bearers in the data plane of a communication system: DRB 307 or 407 and XRB 308 or 408.

[0256] In one aspect, the DRB 307 or 407 may connect the device 102 to a CU-DP 314 or 414 in the RAN, while the XRB 308 or 408 may connect the device 102 to a PU 316 or 416 in the RAN.

[0257] FIG. 7 illustrates a procedure for allocating a radio bearer (DRB or XRB) for a device according to one aspect. In one aspect, the first network controller 710 may be located within the RAN. In some aspects, the first network controller 710 may be part of the CU-CP. In some aspects, the first network controller 710 may be a network entity separate from the CU-CP. In some aspects, the CU-CP, CU-DP, and PU may belong to the same RAN node. In some aspects, the PU and CU-DP belong to the same RAN node. In some aspects, each of the CU-CP, CU-DP, and PU belong to different RAN nodes.

[0258] In one aspect, the first network controller 710 may allocate a DRB or an XRB for a device according to information received from the second network controller 712. The information may indicate whether the device is accessing a data connection service or a processing service. Alternatively, the information may indicate whether the device needs a DRB or an XRB. In some aspects, the second network controller 712 may be located within the CN and may be a control plane function (CPF). The second network controller 712 may receive information (e.g., from the device or another network entity) regarding which service the device 102 is accessing. According to this information, the second network controller 712 can know whether the device is accessing a data connection service or a processing service, and therefore whether the device needs a DRB or an XRB. Thus, the second network controller can indicate this information (i.e., whether the device is accessing a data connection service or a processing service, or whether the device needs a DRB or an XRB) to the first network controller 710.

[0259] According to one aspect, procedure 700 may include step 701 in which a first network controller 710 receives information from a second network controller 712. This information may indicate whether a DRB or an XRB is required for the device 102, or whether the device 102 is accessing a connectivity service or a processing service.

[0260] The procedure 700 may further include a step 702 in which the first network controller 710 allocates a radio bearer to the device 102 according to the information received from the second network controller 712. The radio bearer may be associated with the DU 714 and the RAN DP GW 716. The first network controller may generate an ID to identify the radio bearer.

[0261] In some aspects, if the information received from the second network controller indicates that the device needs a DRB or that the device is accessing a data connection service, the first network controller allocates a DRB to the device 102. In some aspects, if the information received from the second network controller indicates that the device needs an XRB or that the device is accessing a processing service, the first network controller 710 allocates an XRB to the device 102.

[0262] The procedure 700 may further include a step 703 in which the first network controller 710 configures a RAN DP GW 716 associated with the radio bearer, where the radio bearer is allocated by the first network controller 702. Thus, the first network controller 710 may configure the radio bearer in the RAN DP GW 703. In some aspects, the first network controller 710 may provide the RAN DP GW 716 with an ID of the radio bearer (generated when allocating the radio bearer 702) when configuring 703 the RAN DP GW 716.

[0263] In some aspects, the first network controller 710 may configure the RAN DP GW to enable or disable certain functions in the PDCP sublayer for a radio bearer 703. The first network controller 710 may configure the RAN DP GW to enable or disable any one or more of the following functions: PDCP security, PDCP sequencing 703. In response, the RAN DP GW 716 may enable or disable those function(s) as configured by the first network controller.

[0264] In some aspects, when PDCP security is enabled, the PDCP sublayer in the RAN DP GW may perform security measures (e.g., encryption, decryption) for PDCP SDUs or PDCP PDUs associated with a radio bearer. In some aspects, when PDCP security is disabled, the PDCP sublayer in the RAN DP GW may not perform security measures for PDCP SDUs or PDCP PDUs associated with a radio bearer.

[0265] In some aspects, when PDCP sequencing is enabled, the PDCP sublayer in the RAN DP GW can include a sequence number in the PDCP PDU of the radio bearer, or alternatively, the PDCP sublayer in the RAN DP GW can include a PDCP header in the PDCP PDU associated with the radio bearer. When PDCP sequencing is enabled, the PDCP sublayer in the RAN DP GW can perform retransmission of PDCP PDUs transmitted to the device 102 to ensure reliable delivery of the PDCP PDUs. When PDCP sequencing is enabled, the PDCP sublayer in the RAN DP GW can perform reordering of PDCP PDUs received from the device 102 to ensure that the PDCP PDUs are sent in order.

[0266] In some aspects, when PDCP sequencing is disabled, the PDCP sublayer in the RAN DP GW may exclude or not include sequence numbers in PDCP PDUs of a radio bearer, or alternatively, the PDCP sublayer in the RAN DP GW may exclude or not include PDCP headers in PDCP PDUs associated with a radio bearer. When PDCP sequencing is disabled, the PDCP sublayer in the RAN DP GW does not perform retransmission of PDCP PDUs transmitted to the device 102. When PDCP sequencing is disabled, the PDCP sublayer in the RAN DP GW does not perform reordering of PDCP PDUs received from the device 102.

[0267] If the radio bearer is a DRB, the RAN DP GW 716 may be a CU-DP. When configuring 703 the RAN DP GW, the first network controller 710 may configure 703 the RAN DP GW 716 to enable one or more of PDCP security and PDCP sequencing for the radio bearer.

[0268] If the radio bearer is an XRB, the RAN DP GW 716 may be a PU. When configuring 703 the RAN DP GW 716, the first network controller 710 may configure 703 the RAN DP GW 716 to disable one or more of PDCP security and PDCP sequencing for the radio bearer.

[0269] In some aspects, the procedure 700 may further include a step 704 of the first network controller 710 configuring the DU 714 associated with the radio bearer, the radio bearer being allocated 702 by the first network controller 710. Thus, the first network controller 710 may configure 704 the radio bearer at the DU 714. In some aspects, the first network controller 710 may provide the ID of the radio bearer (generated when allocating 702 the radio bearer) to the DU 714 when configuring the DU 714.

[0270] In some aspects, the first network controller 710 may configure the DU 714 to enable or disable certain functions in the RLC sub-layer for a radio bearer 704. The first network controller 710 may configure the DU 704 to enable or disable any one or more of the following functions: RLC segmentation, RLC acknowledgment 704. In response, the DU 714 can enable or disable those function(s) as configured by the first network controller 710.

[0271] In some aspects, when RLC segmentation is enabled, the RLC sub-layer in the DU 714 may segment an RLC SDU associated with a radio bearer. In some aspects, when RLC segmentation is disabled, the RLC sub-layer in the DU 714 may not segment an RLC SDU associated with a radio bearer.

[0272] In some aspects, when RLC acknowledgments are enabled, the RLC sub-layer in the DU 714 may transmit or expect to receive acknowledgments for RLC PDUs associated with a radio bearer. In some aspects, when RLC acknowledgments are disabled, the RLC sub-layer in the DU 714 may not transmit or expect to receive acknowledgments for RLC PDUs associated with a radio bearer.

[0273] If the radio bearer is a DRB, when configuring 704 the DU 714, the first network controller 710 may configure 704 the DU 714 to enable one or more of RLC segmentation and RLC acknowledgment of the radio bearer.

[0274] If the radio bearer is an XRB, when configuring 704 the DU 714, the first network controller 710 may configure 704 the DU 714 to disable one or more of RLC segmentation and RLC acknowledgment of the radio bearer.

[0275] The procedure 700 may further include a step 705 in which the first network controller 710 notifies the device 102 to configure a radio bearer. In some aspects, the first network controller may configure 705 the radio bearer at the device 102. The first network controller 710 may provide the device 102 with an ID of the radio bearer (generated when allocating 702 the radio bearer).

[0276] The first network controller 710 may configure the device to enable or disable certain functions in the RLC and PDCP sublayers for the radio bearer 705. In some aspects, the configuring step 705 may be similar to or coincide with the configuring step 704 in the DU 714 and the configuring step 703 in the RAN DP GW 716.

[0277] The first network controller 710 may configure the device 102 to enable or disable any one or more of the following functions: RLC segmentation, RLC acknowledgment, PDCP security, PDCP sequencing 705. Thus, the device 102 may enable or disable one or more functions in the corresponding RLC and PDCP sublayers as configured by the first network controller 710.

[0278] In some aspects, when RLC segmentation is enabled, the RLC sublayer in the device 102 may segment an RLC SDU associated with a radio bearer. In some aspects, when RLC segmentation is disabled, the RLC sublayer in the device 102 may not segment an RLC SDU associated with a radio bearer.

[0279] In some aspects, when RLC acknowledgments are enabled, the RLC sublayer in the device 102 may transmit or expect to receive acknowledgments for RLC PDUs associated with a radio bearer. In some aspects, when RLC acknowledgments are disabled, the RLC sublayer in the device 102 may not transmit or expect to receive acknowledgments for RLC PDUs associated with a radio bearer.

[0280] In some aspects, when PDCP security is enabled, the PDCP sublayer in the device 102 may perform security measures (e.g., encryption, decryption) for PDCP SDUs or PDCP PDUs associated with a radio bearer. In some aspects, when PDCP security is disabled, the PDCP sublayer in the device 102 may not perform security measures for PDCP SDUs or PDCP PDUs associated with a radio bearer.

[0281] In some aspects, when PDCP sequencing is enabled, the PDCP sublayer in the device 102 can include a sequence number in the PDCP PDU of the radio bearer, or alternatively, the PDCP sublayer in the device 102 can include a PDCP header in the PDCP PDU associated with the radio bearer. When PDCP sequencing is enabled, the PDCP sublayer in the device 102 can perform retransmission of PDCP PDUs transmitted to the RAN DP GW to ensure reliable delivery of the PDCP PDUs. When PDCP sequencing is enabled, the PDCP sublayer in the device 102 can perform reordering of PDCP PDUs received from the RAN DP GW to ensure that the PDCP PDUs are sent in order.

[0282] In some aspects, when PDCP sequencing is disabled, the PDCP sublayer in the device 102 may not include sequence numbers in PDCP PDUs of a radio bearer, or alternatively, the PDCP sublayer in the device 102 may exclude or not include a PDCP header in PDCP PDUs associated with a radio bearer. When PDCP sequencing is disabled, the PDCP sublayer in the device 102 may not perform retransmission of PDCP PDUs transmitted to the RAN DP GW. When PDCP sequencing is disabled, the PDCP sublayer in the device 102 may not perform reordering of PDCP PDUs received from the RAN DP GW.

[0283] If the radio bearer is a DRB, when configuring 705 the device 102, the first network controller 710 may configure 705 the device 102 to enable one or more of RLC segmentation, RLC acknowledgment, PDCP security, and PDCP sequencing for the radio bearer.

[0284] If the radio bearer is an XRB, when configuring 705 the device 102, the first network controller may configure 705 the device 102 to disable one or more of RLC segmentation, RLC acknowledgment, PDCP security, and PDCP sequencing of the radio bearer.

[0285] According to some aspects, one or more PUs and their corresponding functions in the RAN architecture may be provided. The PUs may enable the RAN to natively provide data processing. According to some aspects, header processing in the DP GW (i.e., L3 proxy and L4 proxy as described elsewhere in this application) may be provided. The header processing may reduce protocol overhead.

[0286] According to some aspects, QoS information may be modified when performing an L3 proxy. The modification of QoS information may support end-to-end QoS provisioning. According to some aspects, content processing at the DP GW (e.g., SBI adaptation as described elsewhere in this application with reference to FIG. 6) may be provided. The content processing may support non-standardized SBI in the data plane. According to some aspects, enhanced radio bearers, e.g., XRBs (as described with reference to FIGS. 3 and 4), and allocation of one or more radio bearers based on information received from the CN (as described with reference to FIG. 7) may be provided. The provisioning and allocation of radio bearers including XRBs may simplify radio protocol behavior and reduce protocol overhead.

[0287] FIG. 8 illustrates an apparatus 800 that can perform any or all of the operations of the above methods and features explicitly or implicitly described herein according to different aspects of the present disclosure. For example, a computer with network capabilities may be configured as the apparatus 800. In some aspects, the apparatus 800 may be a network function, a network node (e.g., a RAN node, a CN node), or a device. The RAN node may include a calling party, a calling party, a DP GW (e.g., a RAN DP GW, a CN DP GW), a DU (TP), a CU-DP, a PU, a PU-BE, a PF, an NPF, a PSF, or any other network node or entity described herein that may be configured to perform one or more operations described herein. In some aspects, the apparatus 800 may be a device that connects to a network infrastructure via a radio interface, such as a mobile phone, smartphone, or other such device that may be classified as a user equipment (UE). In some aspects, the apparatus 800 may be a machine-type communication (MTC) device (also referred to as a machine-to-machine (m2m) device) or another such device that may be classified as a UE despite not directly providing service to a user. In some aspects, the apparatus 800 may be used to implement one or more aspects described herein. For example, the apparatus 800 may be configured to perform the operations and functions performed by one or more entities described herein.

[0288] As shown, device 800 may include a processor 810, such as a central processing unit (CPU), or a dedicated processor such as a graphics processing unit (GPU), or other such processor unit, memory 820, non-transitory mass storage 830, input / output interface 840, network interface 850, and transceiver 860, all communicatively coupled via a bidirectional bus 870. According to particular aspects, any or all of the illustrated elements may be utilized, or only a subset of the elements may be utilized. Furthermore, device 800 may include multiple instances of a particular element, such as multiple processors, memories, or transceivers. Elements of a hardware device may also be directly coupled to other elements without a bidirectional bus. In addition to or in place of the processor and memory, other electronic devices, such as integrated circuits, may be employed to perform the required logical operations.

[0289] The memory 820 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or any combination of the like. The mass storage element 830 may include any type of non-transitory storage device, such as a solid-state drive, a hard disk drive, a magnetic disk drive, an optical disk drive, a USB drive, or any computer program product configured to store data and machine-executable program code. According to certain aspects, the memory 820 or mass storage 830 may store statements and instructions executable by the processor 810 to perform any of the aforementioned method operations described above.

[0290] 9 illustrates a method for processing data at a Data Port Gateway (DP GW) according to one aspect. The DP GW may be a RAN Data Port Gateway (DP GW) 314, 316, 414, 416, 514, 516, or 518 or a CN Data Port Gateway (DP GW) 212, 542, 544, or 546. The method 900 includes receiving, by at least one DP GW, a request from a caller based on the caller's first service-based interface format. The request may indicate one or more of a procedure to be performed by the callee and parameters of the procedure.

[0291] The method 900 may further include sending 902, by the at least one DP GW, to the callee, a second request based on the callee's second service-based interface format, the second request indicating one or more of the procedure and one or more parameters of the procedure.

[0292] In some aspects, the method may further include mapping, by the at least one DP GW, the request to a second request. In some aspects, receiving, by the at least one DP GW, the request from the caller may include receiving, by the at least one DP GW, at least one PDU from the caller that includes the request.

[0293] In some aspects, mapping the request to the second request by the at least one DP GW may include mapping the request to the second request by a first DP GW of the at least one DP GW. In some aspects, sending the second request to the callee by the at least one DP GW may include sending, by the first DP GW, at least one PDU including the second request to a second DP GW of the at least one DP GW.

[0294] In some aspects, mapping, by the at least one DP GW, the request to a second request may include transmitting, by a first DP GW of the at least one DP GW, at least one PDU including the request to a second DP GW of the at least one DP GW. In some aspects, mapping, by the at least one DP GW, the request to a second request may further include mapping, by the second DP GW, the request to the second request.

[0295] In some aspects, transmitting, by the first DP GW, at least one PDU to the second DP GW may include segmenting, by the first DP GW, the request into multiple request segments. In some aspects, transmitting, by the first DP GW, at least one PDU to the second DP GW may further include transmitting, by the first DP GW, multiple PDUs, each PDU including multiple request segments, to the second DP GW.

[0296] In some aspects, mapping, by the second DP GW, the request to a second request may further include reassembling, by the second DP GW, the multiple PDUs to obtain the request.

[0297] In some aspects, the request may include a first set of identifiers (IDs) based on a first service-based interface format of the caller, the first set of IDs indicating one or more of a procedure and parameters of the procedure, and the second request may include a second set of IDs based on a second service-based interface format of the callee, the second set of IDs indicating one or more of a procedure and parameters of the procedure.

[0298] In some aspects, the method may further include receiving, by the at least one DP GW, a response from the callee based on the second service-based interface format, the response indicating one or more of a result of the procedure and a result value. In some aspects, the method may further include sending, by the at least one DP GW, a second response based on the first service-based interface format to the caller, the response indicating one or more of a result of the procedure and a result value. The method may further include mapping, by the at least one DP GW, the response to the second response.

[0299] In some aspects, receiving a response from the caller, by the at least one DP GW, can include receiving, by the at least one DP GW, at least one PDU from the callee, the PDU including the response. In some aspects, mapping the response to a second response, by the at least one DP GW, can include mapping the response to the second response by a third DP GW of the at least one DP GW. In some aspects, sending the second response to the caller, by the at least one DP GW, can include sending, by the third DP GW, the at least one PDU including the second response to a fourth DP GW of the at least one DP GW.

[0300] In some aspects, mapping the response to a second response, by the at least one DP GW, may include transmitting, by a third DP GW of the at least one DP GW, the at least one PDU including the response to a fourth DP GW of the at least one DP GW. In some aspects, mapping the response to a second response, by the at least one DP GW, may further include mapping the response to the second response by the fourth DP GW.

[0301] In some aspects, transmitting, by the third DP GW, the at least one PDU to the fourth DP GW may include segmenting, by the third DP GW, the response into multiple response segments. In some aspects, transmitting, by the third DP GW, the at least one PDU to the fourth DP GW may further include transmitting, by the third DP GW to the fourth DP GW, multiple PDUs including multiple response segments.

[0302] In some aspects, mapping, by the fourth DP GW, the response to the second response may further include reassembling, by the second DP GW, the multiple PDUs to obtain the request.

[0303] In some aspects, the response can include a third set of identifiers based on the callee's second service-based interface format, the third set of identifiers indicating one or more of the results of the procedure. In some aspects, the second response can include a fourth set of identifiers based on the caller's first service-based interface format, the fourth set of identifiers indicating one or more of the results of the procedure.

[0304] 10 illustrates another method for processing data according to one aspect. Method 1000 may be performed by a Data Plane Gateway (DP) (e.g., a RAN DP GW 314, 316, 414, 416, 514, 516, 518 or a CN DP GW 212, 542, 544, 546). Method 1000 includes step 1001 of receiving, by a data plane (DP) gateway (GW), a PDU associated with a service from a first network entity via an inbound tunnel, where the PDU is routed through a second network entity. Method 1000 further includes step 1002 of processing, by the DP GW, the PDU based on the service. Method 1000 further includes step 1003 of transmitting, by the DP GW, the PDU to the second network entity.

[0305] In some aspects, the PDU may include a first L3 header that may include a source address, a destination address, and one or more of quality of service (QoS) information indicating a class of the PDU, a priority of the PDU, and one of a QoS flow to which the PDU belongs.

[0306] In some aspects, the source address may indicate one of an address of a sender of the PDU, an address of a Radio Access Network (RAN) node to which the sender belongs, an address of an originator of the PDU, and an address of a processing service. In some aspects, the destination address may be one of an address of a DP GW, an address of a RAN node to which the DP GW belongs, and an address of a processing service.

[0307] In some aspects, the PDU may further include a first L4 header, the first L4 header including a connection identifier (ID) that identifies a receiving tunnel over which the PDU is received. In some aspects, the receiving tunnel may be associated with a processing service, the connection ID identifying a connection between an originator of the PDU and a final destination of the PDU. In some aspects, the receiving tunnel may be associated with a connection service connecting two network entities, the connection ID identifying a connection between the two network entities.

[0308] In some aspects, transmitting 1003, by the DP GW, the PDU to the second network entity may include determining, by the DP GW, a transmission tunnel. In some aspects, transmitting 1003, by the DP GW, the PDU to the second network entity may further include transmitting, by the DP GW, the PDU to the second network entity via the transmission tunnel.

[0309] In some aspects, the transmission tunnel can be determined based on one of a mapping between a receiving tunnel and a transmission tunnel, a mapping between a connection ID and a second connection ID that identifies the transmission tunnel, a mapping between the connection ID, the QoS information, and the second connection ID, and a mapping provided by a network controller in the RAN.

[0310] In some aspects, the transmission tunnel may include a transmitting end and a receiving end, where the transmitting end is a DP GW and the receiving end is a second network entity.

[0311] In some aspects, the DP GW may be a central unit (CU) within the RAN DP (e.g., CU-DP 314, 414, and 514), and the PDUs may be associated with a processing service. In some aspects, the receiving tunnel may be a T3 tunnel (e.g., T3 303, 403, and 503). In some aspects, the transmitting tunnel may be an M2 tunnel (e.g., M2 402 and 502). In some aspects, the receiving end of the transmitting tunnel may be a RAN DP GW (e.g., DP GW 416, 516, 518).

[0312] In some aspects, the PDU may be associated with a processing service. The receiving tunnel may be an M2 tunnel (e.g., M2 402 and 502). The transmitting tunnel may be a T3 tunnel (e.g., T3 303, 403 and 503). The receiving end of the transmitting tunnel may be a core network (CN) DP GW (e.g., NPF 212, 542).

[0313] In some aspects, the PDU may be associated with a connection service. The receiving tunnel may be a T3 tunnel (e.g., T3 303, 403, and 503). The transmitting tunnel may be a data radio bearer (DRB) (e.g., DRB 307, 407) associated with a device. The receiving end of the transmitting tunnel may be the device 102.

[0314] In some aspects, the DP GW may be a processing unit (PU) within the RAN DP (e.g., PU 316, 416, 516, 518), and the PDU may be associated with a processing service. The receiving tunnel may be one of a T3 tunnel (e.g., T3 303, 403, and 503), an M2 tunnel (e.g., M2 402 and 502), or an M5 tunnel (e.g., M5 305, 405, and 505). In some aspects, the transmitting tunnel may be an M4 tunnel (e.g., 304, 404, and 504). In some aspects, the receiving end of the transmitting tunnel may be a RAN DP GW (e.g., DP GW 316, 416, 516, 518).

[0315] In some aspects, the receiving tunnel may be one of a T3 tunnel (e.g., T3 303, 403, and 503), an M2 tunnel (e.g., M2 402 and 502), an M4 tunnel (e.g., M4 304, 404, and 504), and an M5 tunnel (e.g., M5 305, 405, and 505). In some aspects, the transmission tunnel may be an XRB (XRB 308 and 408) associated with a device. The receiving end of the transmission tunnel may be the device.

[0316] In some aspects, the receiving tunnel may be one of a T3 tunnel (e.g., T3 303, 403, and 503), an M2 tunnel (e.g., M2 402 and 502), and an M4 tunnel (e.g., M4 304, 404, and 504). In some aspects, the transmitting tunnel may be an M5 tunnel (e.g., M5 305, 405, and 505). In some aspects, the receiving end of the transmitting tunnel may be a RAN Processing Service Function (PSF) (e.g., RAN PSFs 322, 422, 520, 522, 524, and 526).

[0317] In some aspects, method 1000 may further include processing, by the DP GW, the PDU to obtain a modified PDU. In some aspects, sending 1003, by the DP GW, the PDU via the transmission tunnel to the second network entity may include sending, by the DP GW, the modified PDU via the transmission tunnel to the second network entity.

[0318] In some aspects, processing the PDU, by the DP GW, to obtain a modified PDU may include one of replacing the first L3 header with a second L3 header, modifying the first L3 header with the second L3 header, In some aspects, the second L3 header may include one or more of a second source address, a second destination address, and second QoS information.

[0319] In some aspects, the second source address may be one of the following: the same address as the source address in the first L3 header, a different address than the source address in the first L3 header, an address of the RAN DP GW, or an address of the processing service from which the PDU originated.

[0320] In some aspects, the second destination address may be one of: the same address as the destination address in the first L3 header; a different address than the destination address in the first L3 header; an address of the receiving end of the transmission tunnel; an address of a processing service for which the PDU is targeted; or an address of a device for which the transmission tunnel is a radio bearer associated with the device.

[0321] In some aspects, the second QoS information may be one of the same as the QoS information in the first L3 header, different from the QoS information in the first L3 header.

[0322] In some aspects, processing the PDU, by the DP GW, to obtain a modified PDU may further include one of replacing the first L4 header with a second L4 header and modifying the first L4 header with the second L4 header. In some aspects, the second L4 header may include a third connection ID, where the third connection ID is one or more of an ID identifying a transmission tunnel that is different from the connection ID in the first L4 header and the second connection ID.

[0323] In some aspects, the transmission tunnel can be associated with a processing service, and the third connection ID identifies a connection between an originator of the PDU and a final destination of the PDU. In some aspects, the transmission tunnel can be associated with a connection service that connects two network entities, and the connection ID identifies a connection between the two network entities.

[0324] In some aspects, the receiving tunnel may be a radio bearer associated with the device, the radio bearer being one of a data radio bearer (DRB) and a processing radio bearer (XRB). In some aspects, the PDU may include a first L3 header, the first L3 header including one or more of a source address, a destination address, and quality of service (QoS) information indicating one of a class of the PDU, a priority of the PDU, and a QoS flow to which the PDU belongs.

[0325] In some aspects, the source address may indicate an address of the originator of the PDU, where the originator is a device. In some cases, the destination address may be one of the addresses of a processing service or a processing service function (PSF) that provides at least a portion of the processing service if the receiving tunnel is associated with the processing service, if the receiving tunnel is an XRB, or if the PDU targets the processing service. In some cases, the destination address may be one of the addresses of a DP GW or a Radio Access Network (RAN) node to which the DP GW belongs.

[0326] In some aspects, the method 1000 can further include a first L4 header, the first L4 header including a connection identifier (ID) that identifies a receiving tunnel over which the PDU is received.

[0327] In some aspects, the connection ID may identify a connection between a device and a processing service. In some aspects, the connection ID may identify a connection between a device and a PSF that provides at least a portion of a processing service if the receiving tunnel is associated with the processing service, if the receiving tunnel is an XRB that the device uses to access the processing service, or if the PDU is associated with the processing service.

[0328] In some aspects, the connection ID may identify a connection between the device and the DN. In some aspects, the connection ID can identify a connection between the device and an application server of the DN if the incoming tunnel is associated with a connection service, if the incoming tunnel is a DRB that the device uses to access the connection service, or if the PDU is associated with a connection service, and the connection service connects the device to the DN or AS.

[0329] In some aspects, transmitting 1003, by the DP GW, the PDU to the second network entity may include determining, by the DP GW, a transmission tunnel. In some aspects, transmitting 1003, by the DP GW, the PDU to the second network entity may further include transmitting, by the DP GW, the PDU to the second network entity via the transmission tunnel.

[0330] In some aspects, the transmission tunnel can be determined based on one of a mapping between a receiving tunnel and a transmission tunnel, a mapping between a connection ID and a second connection ID that identifies the transmission tunnel, a mapping between the connection ID, the QoS information, and the second connection ID, and a mapping provided by a network controller in the RAN.

[0331] In some aspects, the transmission tunnel may include a transmitting end and a receiving end, and the transmitting end is a DP GW. In some aspects, the DP GW may be a central unit (CU) in a RAN DP (e.g., CU-DP 314, 414, and 514). In some aspects, the PDU may be associated with a connectivity service, and the transmission tunnel may be a T3 tunnel (e.g., T3 303, 403, and 503). The receiving end of the transmission tunnel may be a core network (CN) DP GW (e.g., NPF 212, 542) in a CN DP. The second network entity may be the receiving end of the transmission tunnel.

[0332] In some aspects, the DP GW may be a processing unit (PU) within the RAN DP (e.g., PU 316, 416, 516, 518). If the PDU is associated with a processing service, the transmission tunnel may be one of an M2 tunnel (e.g., M2 402 and 502), an M4 tunnel (e.g., M4 304, 404 and 504), or an M5 tunnel (e.g., M5 305, 405 and 505).

[0333] In some aspects, the transmission tunnel is a T3 tunnel (e.g., T3 303, 403, and 503), the receiving end of the transmission tunnel may be a core network (CN) DP GW (e.g., NPF 212, 542) within the CN DP, and the second network entity is the receiving end of the transmission tunnel.

[0334] In some aspects, the transmission tunnel is an M2 tunnel (e.g., M2 402 and 502), the receiving end of the transmission tunnel is a central unit (CU) within a RAN DP (e.g., CU-DP 314, 414 and 514), and the second network entity is the receiving end of the transmission tunnel.

[0335] In some aspects, the transmission tunnel is an M4 tunnel (e.g., M4 304, 404, and 504), and the receiving end of the transmission tunnel may be another PU, which is communicatively coupled to a Processing Services Function (PSF) within the RAN that at least partially provides the processing services. In some aspects, the transmission tunnel is an M4 tunnel (e.g., M4 304, 404, and 504), and the second network entity may be the receiving end of the transmission tunnel.

[0336] In some aspects, the transmission tunnel is an M5 tunnel (e.g., M5 305, 405, and 505), and the receiving end of the transmission tunnel can be a RAN Processing Service Function (PSF) (e.g., RAN PSF 322, 422, 520, 522, 524, and 526). The RAN PSF provides at least a portion of the processing services. In some aspects, the transmission tunnel is an M5 tunnel (e.g., M5 305, 405, and 505), and the second network entity is the receiving end of the transmission tunnel.

[0337] In some aspects, method 1000 may further include processing, by the DP GW, the PDU to obtain a modified PDU. In some aspects, sending 1003, by the DP GW, the PDU via the transmission tunnel to the second network entity may include sending, by the DP GW, the modified PDU via the transmission tunnel to the second network entity.

[0338] In some aspects, processing the PDU, by the DP GW, to obtain a modified PDU may include one of replacing the first L3 header with a second L3 header and modifying the first L3 header with the second L3 header. In some aspects, the second L3 header may include a second source address, where the second source address is one of the same address as the source address in the first L3 header, a different address from the source address in the first L3 header, or an address of the DP GW.

[0339] In some aspects, the second L3 header may further include a second destination address, where the second destination address is one of the following: the same address as the destination address in the first L3 header, a different address than the destination address in the first L3 header, an address of the receiving end of the transmission tunnel, or an address of a processing service function that provides at least a portion of the processing service for which the PDU is targeted.

[0340] In some aspects, the second L3 header may further include second QoS information, the second QoS information being one of the same as the QoS information in the first L3 header and different from the QoS information in the first L3 header.

[0341] In some aspects, processing the PDU, by the DP GW, to obtain a modified PDU may further include one of replacing the first L4 header with a second L4 header, modifying the first L4 header with the second L4 header, In some aspects, the second L4 header may be a tunnel header of the transmission tunnel.

[0342] In some aspects, the second L4 header may include a third connection ID, the third connection ID being one or more of an ID identifying the transmission tunnel that is different from the connection ID in the first L4 header and the second connection ID.

[0343] In some aspects, the DP GW is a core network (CN) DP GW (e.g., NPF 212, 542). The receiving end of the receiving tunnel may be a CN DP GW, and the transmitting end of the receiving tunnel may be one of the RAN, CN, and DN.

[0344] In some aspects, the PDU may include a first L3 header, the first L3 header including one or more of a source address and a destination address. In some aspects, the source address may indicate one of an address of the transmitting end, an address of the RAN node to which the transmitting end belongs, an address of the originator, and an address of a processing service from which the PDU originated.

[0345] In some aspects, the destination address may be one of the address of the CN DP GW and, if the PDU is targeted to a processing service, the address of the processing service.

[0346] In some aspects, the PDU may further include QoS information indicating one of the class of the PDU, the priority of the PDU, and the QoS flow to which the PDU belongs.

[0347] In some aspects, the PDU may further include a first L4 header, the first L4 header including a connection ID that identifies a receiving tunnel over which the PDU is received.

[0348] In some aspects, the connection ID may identify a connection between the originator of the PDU and the final destination of the PDU if the receiving tunnel is associated with a processing service or the PDU is associated with a processing service. In some aspects, the connection ID may identify a connection between two network entities if the receiving tunnel or the PDU is associated with a connectivity service and the connectivity service connects two network entities.

[0349] In some aspects, transmitting 1003, by the DP GW, the PDU to the second network entity may include determining, by the CN DP GW, a transmission tunnel. In some aspects, transmitting 1003, by the DP GW, the PDU to the second network entity may further include transmitting, by the CN DP GW, the PDU to the second network entity via the transmission tunnel.

[0350] In some aspects, the transmission tunnel may be determined based on one of a mapping between the receiving tunnel and the transmission tunnel, a mapping between the connection ID and a second connection ID that identifies the transmission tunnel, a mapping between the connection ID, the QoS information, and the second connection ID, and a mapping provided by a network controller at the CN.

[0351] In some aspects, the transmission tunnel may include a transmitting end and a receiving end, where the transmitting end is a CN DP GW and the receiving end is in one of the RAN, the CN, and the DN.

[0352] In some aspects, the transmission tunnel is a T3 tunnel (e.g., T3 303, 403, and 503), the receiving end of the transmission tunnel may be a RAN DP GW (e.g., DP GW 316, 416, 516, 518) in the RAN DP, and the second network entity is the receiving end of the transmission tunnel.

[0353] In some aspects, the transport tunnel is a T4 tunnel (eg, T4 204,554), the receiving end of the transport tunnel is another CN DP GW in the RAN DP, and the second network entity is the receiving end of the transport tunnel.

[0354] In some aspects, the PDU is associated with a processing service, the transmission tunnel is a T5 tunnel (e.g., T5 205 and 555), and the receiving end of the transmission tunnel may be a CN Processing Service Function (PSF) that at least partially provides the processing service. In such cases, the second network entity may be the receiving end of the transmission tunnel.

[0355] In some aspects, the transmission tunnel is a T6 tunnel (eg, T6 206,556), the receiving end of the transmission tunnel is within DN 130, and the second network entity may be the receiving end of the transmission tunnel.

[0356] In some aspects, method 1000 may further include processing, by the CN DP GW, the PDU to obtain a modified PDU. In some aspects, transmitting, by the CN DP GW, the PDU to the second network entity via the transmission tunnel may include transmitting, by the CN DP GW, the modified PDU to the second network entity via the transmission tunnel.

[0357] In some aspects, processing the PDU by the CN DP GW to obtain a modified PDU includes one of replacing the first L3 header with the second L3 header, modifying the first L3 header with the second L3 header.

[0358] In some aspects, the second L3 header may include a second source address, which is one of the following: the same address as the source address in the first L3 header, a different address than the source address in the first L3 header, an address of the CN DP GW, an address of the originator of the PDU, and an address of the processing service if the PDU originated from the processing service.

[0359] In some aspects, the second L3 header may further include a second destination address, which is one of the following: the same address as the destination address in the first L3 header, a different address than the destination address in the first L3 header, an address of a receiving end of the transmission tunnel, or an address of a processing service function that provides at least a portion of the processing service if the PDU is targeted for the processing service.

[0360] In some aspects, the second L3 header may further include second QoS information, where the second QoS information is one of the same as the QoS information in the first L3 header or different from the QoS information in the first L3 header.

[0361] In some aspects, processing the PDU by the CN DP GW to obtain a modified PDU may further include replacing the first L4 header with a second L4 header. In some aspects, processing the PDU by the CN DP GW to obtain a modified PDU may further include modifying the first L4 header with a second L4 header, where the second L4 header is a tunnel header of the transmission tunnel.

[0362] In some aspects, the second L4 header may include a third connection ID, the third connection ID being one or more of an ID identifying the transmission tunnel that is different from the connection ID in the first L4 header and the second connection ID.

[0363] In some aspects, the third connection ID may identify a connection between an originator of the PDU and a final destination of the PDU if the transmission tunnel or PDU is associated with a processing service. In some aspects, the third connection ID may identify a connection between two network entities if the transmission tunnel or PDU is associated with a connectivity service connecting two network entities.

[0364] FIG. 11 illustrates a method for allocating a radio bearer to a device according to one aspect. Method 1100 may be similar to method 700. According to another aspect, method 1100 includes receiving 1101 information about the device 102 by a first network controller (e.g., network controller 710) of a radio access network (RAN) from a second network controller (e.g., network controller 712) of a core network (CN). The information may indicate one or more of: that the device requires a process radio bearer (XRB) and that the device is accessing a process service. In some aspects, method 1100 may further include allocating 1102, by the first network controller, an XRB based on the information about the device. In some aspects, method 1100 further includes configuring 1103, by the first network controller, one or more network nodes to support XRB.

[0365] In some aspects, allocating 1102, by the first network controller, the XRB based on information about the device may include generating an ID to identify the XRB. In some aspects, configuring 1103, by the first network controller, one or more network nodes to support the XRB may include configuring, by the first network controller, a RAN Data Plane (DP) Gateway (GW) associated with the XRB.

[0366] In some aspects, the RAN DP GW is a processing unit (PU) (e.g., PU 316, 416, 516, 518). In some aspects, configuring the RAN DP GW by the first network controller may include providing, by the first network controller, the generated ID to the PU. In some aspects, configuring the RAN DP GW by the first network controller may further include configuring, by the first network controller, the PU to disable XRB to perform one or more of PDCP security and PDCP sequencing.

[0367] In some aspects, configuring 1103, by the first network controller, one or more network nodes to support the XRB may further include configuring, by the first network controller, a distributed unit (DU) associated with the XRB.

[0368] In some aspects, configuring the DU associated with the XRB by the first network controller may include providing, by the first network controller, the generated ID to the DU. In some aspects, configuring the DU associated with the XRB by the first network controller may further include configuring, by the first network controller, the DU to disable the XRB to perform one or more of RLC segmentation and RLC acknowledgment.

[0369] In some aspects, configuring 1103, by the first network controller, one or more network nodes to support XRB, may further include configuring, by the first network controller, a device to support XRB.

[0370] In some aspects, configuring the device, by the first network controller, to support XRB may include providing, by the first network controller, the generated ID to the device. In some aspects, configuring the device, by the first network controller, to support XRB may further include configuring, by the first network controller, the device to disable XRB to perform one or more of RLC segmentation, RLC acknowledgment, PDCP security, and PDCP sequencing.

[0371] 12 illustrates another method for processing data, according to an aspect. Method 1200 may include step 1201 of receiving, by a processing unit (PU) in a radio access network (RAN) data plane (DP), a protocol data unit (PDU) associated with a service from a first network node via a first interface between the PU and the network node. In some aspects, the PU in the RAN may refer to any one of PUs 316, 416, 516, and 518. In some aspects, method 1200 may further include step 1202 of processing, by the PU, the PDU to obtain a processed PDU. In some aspects, method 1200 may further include step 1203 of transmitting, by the PU, the processed PDU to a second network node via a second interface between the PU and the second network node.

[0372] In some aspects, the first network node is a device, and the first interface may be one of a data radio bearer (e.g., DRB 307 and 407) and a processing radio bearer (e.g., XRB 308 and 408).

[0373] In some aspects, the second network node and the second interface may be, more specifically, one of another PU and an M4 interface (e.g., M4 304, 404, and 504) in the RAN DP, a PU backend (e.g., PU-BE 322, 422, 520, 522, 524, 526) and an M5 interface (e.g., M5 305, 405, and 505) in the RAN DP, a central unit (CU) (e.g., CU-DP 314, 414, and 514) and an M2 interface (e.g., M2 402 and 502) in the RAN DP, a DP gateway (GW) (e.g., NPF 212, 542) and a T3 interface (e.g., T3 303, 403, and 503) in the core network (CN) DP.

[0374] In some aspects, the first network node may be another PU in the RAN DP, and the first interface may be an M4 interface (eg, M4 304, 404, and 504). In some aspects, the second network node and the second interface may be, specifically, one of the device 102 and a data radio bearer (e.g., DRB 307 and 407), the device 102 and a processing radio bearer (e.g., XRB 308 and 408), a PU backend (e.g., PU-BE 322, 422, 520, 522, 524, 526) and an M5 interface (e.g., M5 305, 405, and 505) in the RAN DP, a central unit (CU) (e.g., CU-DP 314, 414, and 514) and an M2 interface (e.g., M2 402 and 502) in the RAN DP, and a DP gateway (GW) (e.g., NPF 212, 542) and a T3 interface (e.g., T3 303, 403, and 503) in the core network (CN) DP.

[0375] In some aspects, the first network node is a PU backend (e.g., PU-BE 322, 422, 520, 522, 524, 526) in the RAN DP, and the first interface is an M5 interface (e.g., M5 305, 405, and 505). In some aspects, the second network node and second interface may be, specifically, one of the device 102 and a data radio bearer (e.g., DRB 307 and 407), the device 102 and a processing radio bearer (e.g., XRB 308 and 408), another PU and an M4 interface in the RAN DP (e.g., M4 304, 404 and 504), a central unit (CU) in the RAN DP (e.g., CU-DP 314, 414 and 514) and an M2 interface (e.g., M2 402 and 502), and a DP gateway (GW) in the core network (CN) DP (e.g., NPF 212, 542) and a T3 interface (e.g., T3 303, 403 and 503).

[0376] In some aspects, the first network node is a central unit (CU) in a RAN DP (eg, CU-DP 314, 414, and 514), and the first interface is an M2 interface (eg, M2 402 and 502). In some aspects, the second network node and second interface may be, specifically, one of the device 102 and a data radio bearer (e.g., DRB 307 and 407), the device 102 and a processing radio bearer (e.g., XRB 308 and 408), another PU and an M4 interface in the RAN DP (e.g., M4 304, 404 and 504), a PU backend (e.g., PU 316, 416, 516, 518) and an M5 interface (e.g., M5 305, 405 and 505) in the RAN DP, and a DP gateway (GW) (e.g., NPF 212, 542) and a T3 interface (e.g., T3 303, 403 and 503) in a core network (CN) DP.

[0377] In some aspects, the first network node may be a DP gateway (GW) (e.g., NPF 212, 542) in a core network (CN) DP, and the first interface is a T3 interface (e.g., T3 303, 403, and 503). The second network node and the second interface may be, specifically, one of the device 102 and a data radio bearer (e.g., DRB 307 and 407), the device 102 and a processing radio bearer (e.g., XRB 308 and 408), another PU and an M4 interface (e.g., M4 304, 404, and 504) in the RAN DP, a PU backend and an M5 interface (e.g., M5 305, 405, and 505) in the RAN DP, and a central unit (CU) (e.g., CU-DP 314, 414, and 514) and an M2 interface (e.g., M2 402 and 502) in the RAN DP.

[0378] Aspects of the present disclosure may be implemented using electronic hardware, software, or a combination thereof. In some aspects, this may be implemented by one or more computer processors executing program instructions stored in memory. In some aspects, the invention is implemented partially or fully in hardware, for example, using one or more field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs) to rapidly perform processing operations.

[0379] While specific aspects of the present technology have been described herein for illustrative purposes, it should be understood that various modifications can be made without departing from the scope of the present technology. The specification and drawings should therefore be considered merely as illustrative of the invention, as defined by the appended claims, and are intended to encompass any modifications, permutations, combinations, or equivalents that fall within the scope of the invention. In particular, it is within the scope of the present technology to provide a computer program product or program element, or a program storage or memory device, such as a magnetic or optical wire, tape, or disk, for storing machine-readable signals, for controlling the operation of a computer in accordance with the methods of the present technology, and / or for structuring some or all of its components in accordance with the systems of the present technology.

[0380] The operations associated with the methods described herein may be implemented as coded instructions in a computer program product, which is a computer-readable medium having software code recorded thereon for performing the methods when the computer program product is loaded into memory and executed on a microprocessor of a wireless communication device.

[0381] Furthermore, each operation of the method may be executed according to one or more, or one or more partial program elements, modules, or objects created from any programming language such as C++, Java, etc. on any computing device such as a personal computer, a server, a PDA, etc. In addition, each operation, or a file or object that executes each of the operations, may be executed by dedicated hardware or a circuit module designed for that purpose.

[0382] Through the description of the foregoing aspects, the present invention may be implemented using hardware alone or using software and a required universal hardware platform. Based on such understanding, the technical solutions of the present invention can be embodied in the form of a software product. The software product may be stored in a non-volatile or non-transitory storage medium, which may be a compact disc read-only memory (CD-ROM), a USB flash disk, or a removable hard disk. The software product includes several instructions that enable a computing device (a personal computer, a server, or a network device) to execute the methods provided in the aspects of the present invention. For example, such execution may correspond to simulating the logical operations described herein. The software product may additionally or alternatively include several instructions that enable a computing device to execute operations that configure, i.e., program, a digital logic device according to the aspects of the present invention.

[0383] While the invention has been described with reference to particular features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the invention. The specification and drawings are therefore to be considered merely as illustrative of the invention as defined by the appended claims, and are intended to cover any modifications, variations, combinations, or equivalents that fall within the scope of the invention. [Explanation of symbols]

[0384] 101 Air Interface 102 Devices (UE) 103 T3 106 T6 110 RAN 112 RAN DP 114 RAN CP 120CN 124CNCP 122CNDP 130DN 201 Air Interface 203 T3 204 T4 205 T5 206 T6 210 Connection Subplane 212 NPF(DP GW) 220 Processing Subplane 222 PF 300 RAN DP 301 Air Interface 303 T3 304 TM4 305 M5 307 DRB 308 XRB 310 Connection Subplane 312 DU(TRP) 314 CU-DP(DP GW) 316 PU(DP GW) 320 Processing Subplane 322 PU-BE(PF) 401 Air Interface 402 M2 403 T3 404 M4 405 M5 407 DRB 408 XRB 410 Connection Subplane 412 DU(TRP) 414 CU-DP(DP GW) 416 PU(DP GW) 420 Processing Subplane 422 PU-BE(PF) 502 M2 503 T3 504 M4 505 M5 512 DU(TP) 514 CU-DP(DP GW) 516 PU(DP GW) 518 PU(DP GW) 520 PU-BE(PF) 522 PU-BE(PF) 524 PU-BE(PF) 526 PU-BE(PF) 540CNDP 542 NPF(DP GW) 544 NPF(DP GW) 546 NPF(DP GW) 548 PF 550 PF 552 PF 554 T4 555 T5 556 T6 601 DP GW 602 DP GW 604 Caller 606 Callee 612 request 614 Performing Procedures 616 Response 710 First Network Controller 712 Second Network Controller 714 DU 716 RAN DP GW 800 equipment 810 processor 820 memory 830 Mass Storage 840 Input / Output IO Interface 850 network interface 860 TxRx Transceiver 870 Two-Way Bus

Claims

1. receiving, by at least one data plane (DP) gateway (GW), from a caller, a request based on a first service-based interface format of the caller, the request indicating one or more of a procedure to be performed by a callee and parameters of the procedure; sending, by the at least one DP GW, to the callee, a second request based on a second service-based interface format of the callee, the second request indicating one or more of the procedure and the one or more parameters of the procedure; A method comprising:

2. mapping, by the at least one DP GW, the request to the second request; 10. The method of claim 1, further comprising:

3. receiving, by the at least one DP GW, the request from the caller; receiving, by said at least one DP GW, from said caller, at least one PDU containing said request; 3. The method of claim 2, comprising:

4. wherein mapping the request to the second request by the at least one Data Gateway (DP GW) comprises mapping the request to the second request by a first Data Gateway (DP GW) of the at least one Data Gateway (DP GW); wherein the step of sending the second request to the callee by the at least one DP GW comprises the step of sending, by the first DP GW, the at least one PDU including the second request to a second DP GW of the at least one DP GW. The method of claim 3.

5. Mapping, by the at least one DP GW, the request to the second request, sending, by a first one of the at least one DP GWs, the at least one PDU including the request to a second one of the at least one DP GWs; mapping, by the second DP GW, the request to the second request; 4. The method of claim 3, comprising:

6. transmitting the at least one PDU by the first DP GW to the second DP GW; segmenting, by the first DP GW, the request into a plurality of request segments; transmitting, by the first DP GW, a plurality of PDUs including the plurality of request segments to the second DP GW; 6. The method of claim 5, comprising:

7. mapping, by the second DP GW, the request to the second request; and reassembling the plurality of PDUs by the second DP GW to obtain the request.

7. The method of claim 6, further comprising:

8. the request includes a first set of identifiers (IDs) based on the first service-based interface format of the caller, the first set of IDs indicating one or more of the procedure and the parameters of the procedure; the second request includes a second set of IDs based on the second service-based interface format of the callee, the second set of IDs indicating one or more of the procedure and the parameters of the procedure; 8. The method according to any one of claims 1 to 7.

9. receiving, by the at least one DP GW, a response from the callee based on the second service-based interface format, the response indicating one or more of a result of the procedure and a result value; sending, by the at least one DP GW, to the caller a second response based on the first service-based interface format, the second response indicating one or more of the result of the procedure and the result value; 9. The method of claim 1, further comprising:

10. mapping, by the at least one DP GW, the response to the second response; 10. The method of claim 9, further comprising:

11. receiving, by the at least one DP GW, the response from the callee; receiving, by said at least one DP GW, from said callee, at least one PDU containing said response; 11. The method of claim 10, comprising:

12. wherein mapping the response to the second response by the at least one DP GW comprises mapping the response to the second response by a third DP GW of the at least one DP GW; wherein the step of sending a second response by the at least one DP GW to the caller comprises the step of sending, by the third DP GW, the at least one PDU including the second response to a fourth DP GW of the at least one DP GW. The method of claim 11.

13. mapping, by the at least one DP GW, the response to the second response; sending, by a third DP GW of the at least one DP GW, the at least one PDU including the response to a fourth DP GW of the at least one DP GW; mapping, by the fourth DP GW, the response to the second response; 12. The method of claim 11, comprising:

14. transmitting the at least one PDU by the third DP GW to the fourth DP GW; segmenting, by the third DP GW, the response into a plurality of response segments; sending, by the third DP GW, a plurality of PDUs including the plurality of response segments to the fourth DP GW; 14. The method of claim 13, comprising:

15. mapping, by the fourth DP GW, the response to the second response; and reassembling the plurality of PDUs by the fourth DP GW to obtain the request.

15. The method of claim 14, further comprising:

16. the response includes a third set of identifiers based on the second service-based interface format of the callee, the third set of identifiers indicating one or more of the results of the procedure; the second response includes a fourth set of identifiers based on the first service-based interface format of the caller, the fourth set of identifiers indicating one or more of the results of the procedure; 16. The method according to any one of claims 9 to 15.

17. receiving, by a Data Plane (DP) Gateway (GW), from a first network entity via an inbound tunnel, a PDU associated with a service, wherein the PDU is routed via a second network entity; processing, by the DP GW, the PDU according to the service; sending, by the DP GW, the PDU to the second network entity; A method comprising:

18. 18. The method of claim 17, wherein the PDU includes a first L3 header, the first L3 header including one or more of a source address, a destination address, and quality of service (QoS) information indicating one of a class of the PDU, a priority of the PDU, and a QoS flow to which the PDU belongs.

19. 20. The method of claim 18, wherein the source address indicates one of an address of a sender of the PDU, an address of a Radio Access Network (RAN) node to which the sender belongs, an address of an originator of the PDU, and an address of a processing service.

20. 20. The method of claim 18 or 19, wherein the destination address is one of an address of the DP GW, an address of a RAN node to which the DP GW belongs, and an address of a processing service.

21. 21. The method of claim 18, wherein the PDU further comprises a first L4 header, the first L4 header comprising a connection identifier (ID) that identifies the receiving tunnel over which the PDU is received.

22. the receiving tunnel is associated with a processing service, and the connection ID identifies a connection between an originator of the PDU and a final destination of the PDU; the inbound tunnel is associated with a connection service connecting two network entities, and the connection ID identifies a connection between the two network entities; 22. The method of claim 21.

23. transmitting, by the DP GW, the PDU to the second network entity; determining, by the DP GW, a transmission tunnel; transmitting, by the DP GW, the PDU to the second network entity via the transmission tunnel; 23. The method of claim 21 or 22, comprising:

24. the transmission tunnel: a mapping between the receiving tunnel and the transmitting tunnel; a mapping between the connection ID and a second connection ID that identifies the transmission tunnel; a mapping between the connection ID, the QoS information, and the second connection ID; a mapping provided by a network controller in the RAN; 23. The method of claim 22, wherein the determination is based on one of:

25. 25. The method of claim 24, wherein the transmission tunnel includes a sending end and a receiving end, the sending end being the DP GW, and the receiving end being the second network entity.

26. 26. The method of claim 25, wherein the DP GW is a central unit (CU) in a RAN DP.

27. the PDU is associated with a processing service; the receiving tunnel is a T3 tunnel; the transmission tunnel is an M2 tunnel; The receiving end of the transmission tunnel is a RAN DP GW; 27. The method of claim 26.

28. the PDU is associated with a processing service; the receiving tunnel is an M2 tunnel, the transmission tunnel is a T3 tunnel; the receiving end of the transmission tunnel is a core network (CN) DP GW; 27. The method of claim 26.

29. the PDU is associated with a connectivity service; the receiving tunnel is a T3 tunnel; the transmission tunnel is a data radio bearer (DRB) associated with a device; the receiving end of the transmission tunnel is the device; 27. The method of claim 26.

30. 26. The method of claim 25, wherein the DP GW is a processing unit (PU) in a RAN DP, and the PDU is associated with a processing service.

31. the receiving tunnel is one of a T3 tunnel, an M2 tunnel, and an M5 tunnel; the transmission tunnel is an M4 tunnel; The receiving end of the transmission tunnel is a RAN DP GW; The method of claim 30.

32. the receiving tunnel is one of a T3 tunnel, an M2 tunnel, an M4 tunnel, and an M5 tunnel; the transmission tunnel is a transaction radio bearer (XRB) associated with the device; the receiving end of the transmission tunnel is the device; The method of claim 30.

33. the receiving tunnel is one of a T3 tunnel, an M2 tunnel, and an M4 tunnel; the transmission tunnel is the M5 tunnel; the receiving end of the transmission tunnel is a RAN Processing Service Function (PSF); The method of claim 30.

34. processing the PDU by the DP GW to obtain a modified PDU; further comprising the step of transmitting, by the DP GW, the PDU to the second network entity through the transmission tunnel comprises the step of transmitting, by the DP GW, the modified PDU to the second network entity through the transmission tunnel; 26. The method of claim 25.

35. processing, by the DP GW, the PDU to obtain a modified PDU; replacing the first L3 header with a second L3 header; modifying the first L3 header to the second L3 header; 35. The method of claim 34, comprising one of:

36. 36. The method of claim 35, wherein the second L3 header includes one or more of a second source address, a second destination address, and second QoS information.

37. 37. The method of claim 36, wherein the second source address is one of: an address that is the same as the source address in the first L3 header; an address that is different from the source address in the first L3 header; an address of a RAN DP GW; and an address of a processing service from which the PDU originated.

38. 38. The method of claim 36 or 37, wherein the second destination address is one of: an address that is the same as the destination address in the first L3 header; an address that is different from the destination address in the first L3 header; an address of the receiving end of the transmission tunnel; an address of a processing service to which the PDU is targeted; and an address of the device to which the transmission tunnel is a radio bearer associated with the device.

39. 39. The method of claim 36, wherein the second QoS information is one of the same QoS information as the QoS information in the first L3 header and different QoS information from the QoS information in the first L3 header.

40. processing, by the DP GW, the PDU to obtain a modified PDU; replacing the first L4 header with a second L4 header; modifying the first L4 header to the second L4 header; 40. The method of any one of claims 34 to 39, further comprising one of:

41. 41. The method of claim 40, wherein the second L4 header includes a third connection ID, the third connection ID being one or more of a connection ID different from the connection ID in the first L4 header, an ID identifying the transmission tunnel, and the second connection ID.

42. the transmission tunnel is associated with a processing service, and the third connection ID identifies a connection between an originator of the PDU and a final destination of the PDU; the transmission tunnel is associated with a connection service connecting two network entities, and the connection ID identifies a connection between the two network entities; 42. The method of claim 40 or 41.

43. 18. The method of claim 17, wherein the receiving tunnel is a radio bearer associated with a device, the radio bearer being one of a data radio bearer (DRB) and a processing radio bearer (XRB).

44. 44. The method of claim 43, wherein the PDU includes a first L3 header, the first L3 header including one or more of a source address, a destination address, and quality of service (QoS) information indicating one of a class of the PDU, a priority of the PDU, and a QoS flow to which the PDU belongs.

45. 45. The method of claim 44, wherein the source address indicates an address of an originator of the PDU, the originator being the device.

46. The destination address is If the receiving tunnel is associated with a processing service, if the receiving tunnel is the XRB, or if the PDU is targeted to the processing service, the address of the processing service or the address of a Processing Service Function (PSF) that provides at least a part of the processing service; the address of the DP GW or the address of the Radio Access Network (RAN) node to which the DP GW belongs; 46. ​​The method of claim 44 or 45, wherein the method is one of:

47. 47. The method of any one of claims 43 to 46, further comprising a first L4 header, the first L4 header comprising a connection identifier (ID) that identifies the receiving tunnel over which the PDU is received.

48. The connection ID is If the receiving tunnel is associated with a processing service, if the receiving tunnel is an XRB used by the device to access the processing service, or if the PDU is associated with the processing service, a connection between the device and a PSF that provides a processing service or at least a portion of the processing service; If the receiving tunnel is associated with a connectivity service, if the receiving tunnel is a DRB that the device uses to access the connectivity service, or if the PDU is associated with the connectivity service and the connectivity service connects the device to the DN or the AS, the PDU is a connection between the device and a data network (DN) or an application server of the DN.

48. The method of claim 47, wherein the method identifies one of:

49. transmitting, by the DP GW, the PDU to the second network entity; determining, by the DP GW, a transmission tunnel; transmitting, by the DP GW, the PDU to the second network entity via the transmission tunnel; 49. The method of claim 47 or 48, comprising:

50. the transmission tunnel: a mapping between the receiving tunnel and the transmitting tunnel; a mapping between the connection ID and a second connection ID that identifies the transmission tunnel; a mapping between the connection ID, the QoS information, and the second connection ID; a mapping provided by a network controller in the RAN; 50. The method of claim 49, wherein the determination is based on one of:

51. 51. The method of claim 50, wherein the transmission tunnel includes a sending end and a receiving end, the sending end being the DP GW.

52. the DP GW is a central unit (CU) in the RAN DP; the PDU is associated with a connectivity service; the transmission tunnel is a T3 tunnel; the receiving end of the transmission tunnel is a Core Network (CN) DP GW in a CN DP; the second network entity is the receiving end of the transmission tunnel; 52. The method of claim 51.

53. 52. The method of claim 51, wherein the DP GW is a processing unit (PU) in a RAN DP.

54. the PDU is associated with a processing service; the transmission tunnel is one of an M2 tunnel, an M4 tunnel, and an M5 tunnel; 54. The method of claim 53.

55. the transmission tunnel is a T3 tunnel; the receiving end of the transmission tunnel is a Core Network (CN) DP GW in a CN DP; the second network entity is the receiving end of the transmission tunnel; 54. The method of claim 53.

56. the transmission tunnel is an M2 tunnel; the receiving end of the transmission tunnel is a central unit (CU) in the RAN DP; the second network entity is the receiving end of the transmission tunnel; 54. The method of claim 53.

57. the transmission tunnel is an M4 tunnel; the receiving end of the transmission tunnel is another PU, the other PU being communicatively coupled to a Processing Services Function (PSF) within the RAN that at least partially provides the processing service; the second network entity is the receiving end of the transmission tunnel; 54. The method of claim 53.

58. the transmission tunnel is the M5 tunnel; the receiving end of the transmission tunnel is a RAN Processing Services Function (PSF), the RAN PSF at least partially providing the processing services; the second network entity is the receiving end of the transmission tunnel; 54. The method of claim 53.

59. processing the PDU by the DP GW to obtain a modified PDU; further comprising the step of transmitting, by the DP GW, the PDU to the second network entity through the transmission tunnel comprises the step of transmitting, by the DP GW, the modified PDU to the second network entity through the transmission tunnel; 52. The method of claim 51.

60. processing, by the DP GW, the PDU to obtain a modified PDU; replacing the first L3 header with a second L3 header; modifying the first L3 header to the second L3 header; 60. The method of claim 59, comprising one of:

61. 61. The method of claim 60, wherein the second L3 header includes a second source address, the second source address being one of: an address that is the same as the source address in the first L3 header, an address that is different from the source address in the first L3 header, and an address of the DP GW.

62. 62. The method of claim 60 or 61, wherein the second L3 header further includes a second destination address, the second destination address being one of: an address that is the same as the destination address in the first L3 header; an address that is different from the destination address in the first L3 header; an address of the receiving end of the transmission tunnel; and an address of a processing service function that provides at least a portion of the processing service targeted by the PDU.

63. 63. The method of claim 60, wherein the second L3 header further includes second QoS information, the second QoS information being one of the same QoS information as the QoS information in the first L3 header and different QoS information from the QoS information in the first L3 header.

64. processing, by the DP GW, the PDU to obtain a modified PDU; replacing the first L4 header with a second L4 header; modifying the first L4 header to the second L4 header; and The second L4 header is a tunnel header of the transmission tunnel.

64. The method of any one of claims 59 to 63.

65. 65. The method of claim 64, wherein the second L4 header includes a third connection ID, the third connection ID being one or more of a connection ID different from the connection ID in the first L4 header, an ID identifying the transmission tunnel, and the second connection ID.

66. the DP GW is a core network (CN) DP GW; The receiving end of the receiving tunnel is the CN DP GW; the transmitting end of the receiving tunnel is in one of a radio access network (RAN), a CN, and a data network (DN); 18. The method according to claim 17.

67. 67. The method of claim 66, wherein the PDU includes a first L3 header, the first L3 header including one or more of a source address and a destination address.

68. 68. The method of claim 67, wherein the source address indicates one of an address of the transmitting end, an address of a radio access network (RAN) node to which the transmitting end belongs, an address of an originator, and an address of a processing service from which the PDU originates.

69. 69. The method of claim 67 or 68, wherein the destination address is one of an address of the CN DP GW and an address of a processing service if the PDU is targeted to a processing service.

70. 70. The method of any one of claims 67 to 69, wherein the PDU further includes quality of service (QoS) information indicating one of a class of the PDU, a priority of the PDU, and a QoS flow to which the PDU belongs.

71. 71. The method of claim 70, wherein the PDU further comprises a first L4 header, the first L4 header comprising a connection identifier (ID) that identifies a receiving tunnel over which the PDU is received.

72. The connection ID is If the receiving tunnel is associated with a processing service or the PDU is associated with a processing service, a connection between the source of the PDU and a final destination of the PDU; If the receiving tunnel or the PDU is associated with a connectivity service, and the connectivity service connects two network entities, 72. The method of claim 71, wherein the method identifies one of:

73. transmitting, by the DP GW, the PDU to the second network entity; determining a transmission tunnel by the CN DP GW; transmitting, by the CN DP GW, the PDU to the second network entity via the transmission tunnel; 73. The method of claim 71 or 72, comprising:

74. the transmission tunnel: a mapping between the receiving tunnel and the transmitting tunnel; a mapping between the connection ID and a second connection ID that identifies the transmission tunnel; a mapping between the connection ID, the QoS information, and the second connection ID; a mapping provided by a network controller at the CN; 74. The method of claim 73, wherein the determination is based on one of:

75. 75. The method of claim 74, wherein the transmission tunnel includes a transmitting end and a receiving end, the transmitting end being the CN DP GW, and the receiving end being in one of the RAN, the CN, and the DN.

76. the transmission tunnel is a T3 tunnel; the receiving end of the transmission tunnel is a RAN DP GW in a RAN DP; the second network entity is the receiving end of the transmission tunnel; 76. The method of claim 75.

77. the transmission tunnel is a T4 tunnel; the receiving end of the transmission tunnel is another CN DP GW in a RAN DP; the second network entity is the receiving end of the transmission tunnel; 76. The method of claim 75.

78. the PDU is associated with a processing service; the transmission tunnel is a T5 tunnel; the receiving end of the transmission tunnel is a CN Processing Service Function (PSF) that at least partially provides the processing service; the second network entity is the receiving end of the transmission tunnel; 76. The method of claim 75.

79. the transmission tunnel is a T6 tunnel; the receiving end of the transmission tunnel is within a DN; the second network entity is the receiving end of the transmission tunnel; 76. The method of claim 75.

80. processing the PDU by the CN DP GW to obtain a modified PDU; further comprising the step of transmitting, by the CN DP GW, the PDU to the second network entity through the transmission tunnel comprises the step of transmitting, by the CN DP GW, the modified PDU to the second network entity through the transmission tunnel; 76. The method of claim 75.

81. processing the PDU by the CN DP GW to obtain a modified PDU; replacing the first L3 header with a second L3 header; modifying the first L3 header to the second L3 header; 81. The method of claim 80, comprising one of:

82. 82. The method of claim 81, wherein the second L3 header includes a second source address, the second source address being one of: an address that is the same as the source address in the first L3 header, an address that is different from the source address in the first L3 header, an address of the CN DP GW, an address of an originator of the PDU, or an address of a processing service if the PDU originated from a processing service.

83. 83. The method of claim 81 or 82, wherein the second L3 header further includes a second destination address, the second destination address being one of: an address that is the same as the destination address in the first L3 header; an address that is different from the destination address in the first L3 header; an address of the receiving end of the transmission tunnel; and an address of a processing service function that provides at least a portion of the processing service if the PDU is targeted for a processing service.

84. 84. The method of claim 81, wherein the second L3 header further includes second QoS information, the second QoS information being one of the same QoS information as the QoS information in the first L3 header and different QoS information from the QoS information in the first L3 header.

85. processing the PDU by the CN DP GW to obtain a modified PDU; replacing the first L4 header with a second L4 header; modifying the first L4 header to the second L4 header; and The second L4 header is a tunnel header of the transmission tunnel.

85. The method of any one of claims 80 to 84.

86. 86. The method of claim 85, wherein the second L4 header includes a third connection ID, the third connection ID being one or more of a connection ID different from the connection ID in the first L4 header, an ID identifying the transmission tunnel, and the second connection ID.

87. The third connection ID is If the transmission tunnel or the PDU is associated with a processing service, a connection between the source of the PDU and the final destination of the PDU; and If the transmission tunnel or the PDU is associated with a connectivity service connecting two network entities, a connection between the two network entities 87. The method of claim 85 or 86, wherein the method identifies:

88. receiving, by a first network controller of a radio access network (RAN), information about a device from a second network controller of a core network (CN), the information indicating one or more of: that the device requires a process radio bearer (XRB); and that the device is accessing a process service; allocating, by the first network controller, the XRB based on the information about the device; configuring, by the first network controller, one or more network nodes to support the XRB; A method comprising:

89. 90. The method of claim 88, wherein allocating, by the first network controller, the XRB based on the information about the device includes generating an identifier (ID) for identifying the XRB.

90. configuring, by the first network controller, one or more network nodes to support the XRB; configuring, by the first network controller, a RAN Data Plane (DP) Gateway (GW) associated with the XRB; 90. The method of claim 88 or 89, comprising:

91. the RAN DP GW is a processing unit (PU); configuring the RAN DP GW by the first network controller, providing, by the first network controller, the generated ID to the PU; configuring, by the first network controller, the PU to disable the XRB to perform one or more of PDCP security and PDCP sequencing; 91. The method of claim 90, comprising:

92. configuring, by the first network controller, one or more network nodes to support the XRB; configuring, by said first network controller, a distributed unit (DU) associated with said XRB; 92. The method of any one of claims 88 to 91, further comprising:

93. configuring, by the first network controller, the DU associated with the XRB; providing, by the first network controller, the generated ID to the DU; configuring, by the first network controller, the DU to disable the XRB to perform one or more of RLC segmentation and RLC acknowledgment; 93. The method of claim 92, comprising:

94. configuring, by the first network controller, one or more network nodes to support the XRB; configuring, by the first network controller, the device to support the XRB; 94. The method of any one of claims 88 to 93, further comprising:

95. configuring, by the first network controller, the device to support the XRB; providing, by the first network controller, the generated ID to the device; configuring, by the first network controller, the device to disable the XRB to perform one or more of RLC segmentation, RLC acknowledgment, PDCP security, and PDCP sequencing; 95. The method of any one of claims 88 to 94, comprising:

96. receiving, by a processing unit (PU) in a radio access network (RAN) data plane (DP), from a first network node via a first interface between the PU and the network node, a protocol data unit (PDU) associated with a service; processing, by the PU, the PDU to obtain a processed PDU; transmitting, by the PU, the processed PDU to the second network node via a second interface between the PU and the second network node; A method comprising:

97. the first network node is the device; the first interface is one of a data radio bearer and a transaction radio bearer; 97. The method of claim 96.

98. The second network node and the second interface, in particular: Another PU and M4 interface in the RAN DP; a PU backend and an M5 interface in the RAN DP; a central unit (CU) and M2 interface in the RAN DP; DP Gateway (GW) and T3 interface in the Core Network (CN) DP 98. The method of claim 97, wherein the method is one of:

99. the first network node is another PU in the RAN DP; The first interface is an M4 interface.

97. The method of claim 96.

100. The second network node and the second interface, in particular: the device and a data radio bearer; the device and processing radio bearers; a PU backend and an M5 interface in the RAN DP; a central unit (CU) and M2 interface in the RAN DP; DP Gateway (GW) and T3 interface in the Core Network (CN) DP 100. The method of claim 99, wherein the method is one of:

101. the first network node is a PU backend in the RAN DP; The first interface is an M5 interface; 97. The method of claim 96.

102. The second network node and the second interface, in particular: the device and a data radio bearer; the device and processing radio bearers; Another PU and M4 interface in the RAN DP; a central unit (CU) and M2 interface in the RAN DP; DP Gateway (GW) and T3 interface in the Core Network (CN) DP 102. The method of claim 101, wherein the method is one of:

103. the first network node is a central unit (CU) in the RAN DP; The first interface is an M2 interface.

97. The method of claim 96.

104. The second network node and the second interface, in particular: the device and a data radio bearer; the device and processing radio bearers; Another PU and M4 interface in the RAN DP; a PU backend and an M5 interface in the RAN DP; DP Gateway (GW) and T3 interface in the Core Network (CN) DP 104. The method of claim 103, wherein the method is one of:

105. the first network node is a DP Gateway (GW) in a Core Network (CN) DP; the first interface is a T3 interface; 97. The method of claim 96.

106. The second network node and the second interface, in particular: the device and a data radio bearer; the device and processing radio bearers; Another PU and M4 interface in the RAN DP; a PU backend and an M5 interface in the RAN DP; a central unit (CU) and M2 interface in the RAN DP; 104. The method of claim 103, wherein the method is one of:

107. 1. An apparatus comprising: at least one processor; at least one machine-readable medium storing executable instructions that, when executed by the at least one processor, configure the apparatus to perform the method of any one of claims 1 to 106; and An apparatus comprising:

108. 107. A computing device comprising a non-transitory computer-readable medium having instructions stored thereon, the instructions, when executed by a computer processor, causing the computing device to perform the method of any one of claims 1 to 106.

Images