System and method for RAN protocol for future x-centric serving networks

Abstract

Systems and methods are provided for a radio access network (RAN) protocol for a future X-centric serving network. According to one aspect, a method for providing a network service is provided. The method includes a first device receiving at least one protocol data unit (PDU) from a second device, the at least one PDU including at least one service data unit (SDU) associated with the network service. The method also includes the first device retrieving the at least one SDU from the at least one PDU. The method further comprises the step that the first device processes the at least one SDU to obtain a processed version of the at least one SDU. The method further includes the first device constructing at least one additional PDU, the at least one additional PDU comprising the processed version of the at least one SDU. The method also includes the first device transmitting the at least one additional PDU to the second device.

Description

Technical Field

[0001] The present invention relates to the field of communication networks, and in particular to a system and method for RAN protocols in an X-centric service network. Background Art

[0002] In addition to traditional connection-oriented communication services, the sixth generation (6G) wireless network may also include new service types for network-native data processing. Such new services may require data parsing and processing within the network, which may not be supported by current 5G wireless networks. For example, current 5G wireless networks may have restrictions on which operations can be performed within the network, which may reduce the availability and provision of new service types that may be included in 6G wireless networks. Some limitations of 5G wireless networks may include limited operations performed at different layers of the radio access network (RAN) and user plane (UP) protocol stack.

[0003] Therefore, there is a need for systems and methods for RAN protocols for future X-centric service networks that can obviate or mitigate one or more limitations of the prior art.

[0004] This background information is provided to reveal information believed by the applicant to be potentially relevant to the present invention. It is not necessarily intended, nor should it be construed, that any of the foregoing information constitutes prior art against the present invention. Summary of the invention

[0005] The present invention provides a system and method for a RAN protocol for a future X-centric service network. According to one aspect, a method for providing network services is provided. The method includes: a first device receives at least one protocol data unit (PDU) from a second device, and the at least one PDU contains at least one service data unit (SDU) associated with the network service. The method also includes: the first device retrieves the at least one SDU from the at least one PDU. The method also includes: the first device processes the at least one SDU to obtain a processed version of the at least one SDU. The method also includes: the first device constructs at least one additional PDU, and the at least one additional PDU includes the processed version of the at least one SDU. The method also includes: the first device sends the at least one additional PDU to the second device.

[0006] The first device may be a radio access network (RAN) node, and the second device may be a user equipment (UE), or the first device may be a UE and the second device may be a RAN node.

[0007] The first device may be a radio access network (RAN) node, and the second device may be a core network function (CNF).

[0008] The first device may be a CNF, and the second device may be a RAN node.

[0009] The first device may be a CNF, and the second device may be a UE.

[0010] The first device may be a UE, and the second device may be a CNF.

[0011] Retrieving the at least one SDU, processing the at least one SDU, and constructing the at least one additional PDU may be performed at the first device by a processing function (PF) at the first device.

[0012] Receiving the at least one PDU at the first device may include: receiving the at least one PDU via at least one network service data bearer (XDB) established between the first device and the second device, where the at least one XDB is for the network service.

[0013] The method may be performed in a communication network in which the first device and the second device are deployed. The communication network may include a PF protocol sublayer. Retrieving the at least one SDU, processing the at least one SDU, and constructing the at least one additional PDU at the first device may be performed by the PF at the first device in the PF protocol sublayer.

[0014] The UE may include a UE PF deployed at the UE in the PF protocol sublayer. Receiving the at least one PDU from the UE may include: receiving the at least one PDU from the UE PF via at least one network service data bearer (servicedata bearer, XDB) established between the first device and the second device. The at least one XDB may be supported by the PF protocol sublayer.

[0015] The network service may include one or more of the following: data analysis, artificial intelligence (AI) training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

[0016] The communication network may further include a Packet Data Convergence Protocol (PDCP) sublayer, and the PF protocol sublayer is deployed above the PDCP sublayer.

[0017] The communication network may further include a Service Data Adaptation Protocol (SDAP) sublayer, and the PF protocol sublayer is deployed below the SDAP sublayer.

[0018] The PDCP sublayer may provide at least one Data Radio Bearer (DRB) to the PF protocol sublayer between the first device and the second device.

[0019] The PF protocol sublayer may provide the at least one Network Service Data Bearer (XDB) to the SDAP sublayer.

[0020] The communication network may include a Radio Link Control (RLC) sublayer, a Medium Access Control (MAC) sublayer, and a Physical (PHY) layer, and the PDCP sublayer is located above the RLC sublayer, the MAC sublayer, and the PHY layer.

[0021] Each XDB in the at least one XDB may have a corresponding PF entity in the PF protocol sublayer, and each PF entity is for the corresponding XDB.

[0022] For each DRB in the at least one DRB, the PDCP sublayer may include a corresponding PDCP entity in the PDCP sublayer.

[0023] The SDAP sublayer may include an SDAP entity for at least one session of the network service. Any one of the at least one session of the network service may be established between the UE and a core network function (CNF). The method may further include establishing a CN session tunnel between the RAN node and the CNF.

[0024] Any one of the at least one session of the network service may include at least one quality-of-service (QoS) flow of the network service, and a single QoS flow among the at least one QoS flow of the network service has the smallest granularity with QoS differentiation in the session of the at least one session of the network service. Traffic in the same QoS flow among the at least one QoS flow of the network service receives the same data forwarding handling and data processing handling.

[0025] The parameters of the data processing handling may include one or more of the following: data processing scheduling policy, data calculation accuracy, data calculation latency, artificial intelligence (AI) model type, AI model privacy level, AI model accuracy level, AI training method, AI inference method, privacy protection method, data management policy, data purification policy, data compression policy, data embedding policy, data representation learning policy, data feature extraction policy, data preprocessing policy, privacy level, data storage duration, data processing policy, data cleaning policy, data normalization policy, data quality level, and data processing priority.

[0026] The parameters of the data forwarding handling parameters may include one or more of the following: data transmission resource scheduling policy, data queue management policy, data transmission priority level, link layer protocol configuration, access threshold, data loss rate, data transmission latency, data forwarding security protection method, and security level.

[0027] The at least one XDB may be used to serve only the UE. The at least one XDB may also be used to transmit PF protocol sublayer PDUs to the UE and receive PF protocol sublayer PDUs from the UE via a wireless interface.

[0028] The UE is configured with the at least one XDB. One or more PF entities in the at least one XDB are connected to one or more PDCP entities dedicated to the UE.

[0029] The at least one XDB of the UE may be mapped to one or more DRBs of the same UE. The at least one session of the network service may be mapped by the SDAP entity to the at least one XDB dedicated to the UE.

[0030] The at least one QoS flow of the at least one session of the network service may be mapped by the SDAP entity to the at least one XDB dedicated to the UE.

[0031] The at least one XDB may be used for a group of UEs to transmit PF protocol sub-layer PDUs to the group of UEs including the UE, to transmit at least one PF protocol sub-layer PDU to the group of UEs, and to receive the at least one PF protocol sub-layer PDU from the group of UEs.

[0032] The at least one XDB may use one of a broadcast method and a multicast method to transmit a copy of the at least one PF protocol sub-layer PDU to the group of UEs via a radio interface. The UE in the group of UEs may be configured with the at least one XDB.

[0033] At least one PF entity in the at least one XDB for the group of UEs may be connected to at least one PDCP entity for the group of UEs. The at least one PDCP entity may be used for a multimedia broadcast multicast service (MBMS) point-to-multipoint radio bearer (MRB). The at least one PDCP entity may be used for a point-to-multipoint radio bearer (NRB).

[0034] The at least one session of the network service may be mapped by the SDAP entity to the at least one XDB of the group of UEs.

[0035] The at least one QoS flow of the at least one session of the network service may be mapped by the SDAP entity to the at least one XDB of the group of UEs.

[0036] The at least one XDB may transmit to different UEs in the group of UEs via a radio interface: different PF protocol sub-layer PDUs; or separate copies of PF protocol sub-layer PDUs. The group of UEs may be configured with the at least one XDB.

[0037] At least one PF entity in the at least one XDB for the group of UEs may be connected to at least one PDCP entity. Any one of the at least one PDCP entities may be used for at least one UE in the group of UEs. Any one of the at least one PDCP entities may be connected to at least one radio link control (RLC) entity. Any one of the at least one PDCP entities may be used for one or more of the following: DRB, multicast / broadcast service radio bearer (MRB), point-to-multipoint radio bearer (NRB).

[0038] At least one session of the network service may be mapped by an SDAP entity to the at least one XDB of the group of UEs. At least one QoS flow of at least one session of the network service may be mapped by an SDAP entity in the SDAP sublayer to the at least one XDB of the group of UEs.

[0039] The PF protocol sublayer may include a PF entity. The PF entity may include one or more of the following: a data buffer component, a data processing component, a routing component, and a data transmission component.

[0040] The data buffer component may be used to perform one or more of the following: store data, cache data, and accumulate data for the data processing component to perform data processing.

[0041] The data processing component may be used to perform data processing using one or more of the following various methods: data analysis, artificial intelligence (AI) training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

[0042] The routing component of the PF entity may be used to add routing information to the header of a PF PDU to help another PF entity determine a routing action. The routing component may also be used to determine the routing action of the PF entity based on the routing information included in the header of the PF PDU.

[0043] The routing action of the PF entity or the routing action of the other entity may include one or more of the following: stopping data transmission, transmitting data to a PF entity residing on the same node as the PF entity, transmitting data to a PF entity residing on the same node as the other PF entity, transmitting data to a PF entity of a peer node, transmitting data to an entity of an upper layer, or transmitting data to an entity of a lower layer, where the data includes one or more of the following: the PF SDU contained in the PF PDU, a processed version of the PF SDU contained in the PF PDU, a constructed PF PDU including the PF SDU contained in the PF PDU, or a constructed PF PDU including the processed version of the PF SDU contained in the PF PDU.

[0044] The data transmission component may be used to perform one or more of the following on the data: mapping or transmitting the data to a corresponding transmission tunnel or channel; sequentially numbering the data; sequentially transmitting the data to the PF protocol sublayer, the upper layer, or the lower layer.

[0045] The PF entity may perform one or more of the following: receiving at least one PF SDU from an upper layer or transmitting at least one PF SDU to an upper layer. The PF entity may perform one or more of the following: receiving the at least one PF SDU from a lower layer or transmitting the at least one PF SDU to a lower layer. The PF entity may perform one or more of the following: receiving the at least one PF SDU from another PF entity or transmitting the at least one PF SDU to another PF entity. The PF entity may perform one or more of the following: submitting at least one PF PDU to the lower layer or receiving at least one PF PDU from the lower layer. The PF entity may perform one or more of the following: submitting at least one PF PDU to the other entity or receiving at least one PF PDU from the other entity. The at least one PF PDU may include one or more of a header and a PF SDU.

[0046] A PF PDU among the at least one PF PDUs may include a header indicating one or more of the following: the type of the network service to which the one PF PDU belongs, the sequence number of the one PF PDU, an indication to further process the one PF SDU contained in the one PF PDU, the type of data processing of the one PF SDU contained in the one PF PDU, an indication to directly forward the PF SDU contained in the one PF PDU, routing information, a network service QFI identifying the QoS flow to which the one PF PDU belongs.

[0047] The type of data processing may include one or more methods of the following: data analysis, AI training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

[0048] The routing information may indicate the destination to which the PF entity receiving the PF PDU is to transmit the data, where the data includes one or more of the following: the PF SDU included in the PF PDU, the processed version of the PF SDU included in the PF PDU, the constructed PF PDU including the PF SDU included in the PF PDU, or the constructed PF PDU including the processed version of the PF SDU included in the PF PDU.

[0049] The destination may be one or more of the following: the PF entity, another PF entity residing on the same node as the PF entity, another PF entity of a peer node, an entity of an upper layer, and an entity of a lower layer.

[0050] Retrieving the at least one SDU from the at least one PDU may include the PF entity retrieving the at least one PF SDU from the at least one PF PDU. Retrieving the at least one PF SDU from the at least one PF PDU may further include deleting one or more headers included in the at least one PF PDU.

[0051] Constructing the at least one additional PF PDU may be performed by the PF entity after retrieving the at least one PF SDU from the at least one PF PDU. Constructing the at least one additional PDU may include one or more of the following: parsing and processing the raw data encapsulated in one or more payloads of the at least one PF SDU using one or more methods of the following: data analysis, AI training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

[0052] For the at least one XDB of the network service, a dedicated type of one or more of the following may be defined, reserved, or configured: associated DRB, RLC channel, logical channel, transport channel, and physical channel. Similarly, dedicated physical radio resources may be allocated for the at least one XDB of the network service.

[0053] The at least one XDB and the associated DRB may configure the same MAC entity of the associated MAC sublayer to multiplex relevant radio resources.

[0054] The at least one XDB may be configured by a dedicated signaling message for the network service or a radio resource control (RRC) message for the network service. The dedicated signaling message for the network service may be sent by a control entity of a control protocol layer above the associated PDCP sublayer via a signaling radio bearer between the RAN node and the UE.

[0055] The PF entity may include one or more of a transmitting part and a receiving part, and each of the transmitting part and the receiving part performs one or more functions of the PF entity.

[0056] The PF protocol sublayer may be configured at one or more of the RAN node and the UE node. When the RAN node performs data forwarding, the PF protocol sublayer may operate in transparent mode.

[0057] The PF protocol sublayer may be configured at the RAN node and the UE without configuring a session tunnel between the RAN node and the CNF. The network service may involve the RAN node and the UE and not involve the CNF.

[0058] The PF protocol sublayer may be configured at the RAN node without configuring an SDAP sublayer, a radio L2 sublayer, and a PHY layer at the RAN node. The network service may involve the RAN node and the CNF and not involve the UE.

[0059] Sub-layers including the SDAP sublayer, the PF protocol sublayer, the associated PDCP sublayer, the associated RLC sublayer, the associated MAC sublayer, and the associated PHY layer may be configured at the RAN node and the UE. When the network service involves the RAN node, the UE, and the CNF, a session tunnel between the CNF and the RAN node may be configured.

[0060] The RAN node, the UE, and the CNF may be configured without the SDAP sublayer. The traffic granularity of the QoS flow of the network service may be the same as the traffic granularity of the at least one XDB.

[0061] A CNF PF entity may be configured in an associated PF protocol layer at the CNF. The CNF PF entity performs at least one function of the RAN PF entity at the RAN node and the UE PF entity at the UE.

[0062] The FP sublayer may be deployed in one of the following various locations: above the PDCP sublayer, between the SDAP sublayer and the PDCP sublayer, between the PDCP sublayer and the RLC sublayer, between the RLC sublayer and the MAC sublayer, between the MAC sublayer and the PHY layer, above the SDAP sublayer, above the PDU layer, above the GTP-U layer, above the UDP layer, above the IP layer, above the QUIC layer, above the hypertext transfer protocol (HTTP) layer, above the segment routing over IPv6 (SRv6) layer, within the PDU layer, within the SDAP sublayer, within the PDCP sublayer, within the RLC sublayer, within the MAC sublayer, within the PHY layer, within the GTP-U layer, within the UDP layer, within the IP layer, within the application layer, within the HTTP layer, within the SRv6 layer, and within the QUIC layer.

[0063] Traffic in the same XDB of the at least one SDB receives the same data forwarding handling and data processing handling, where one or more data processing handling parameters and data forwarding handling parameters are configured for each XDB of the at least one XDB.

[0064] According to another aspect, another method is provided. The method includes: a radio access network (RAN) node receives a first message from a user equipment (UE) that includes a service data unit (SDU) associated with a network service. The method further includes: the RAN node retrieves the SDU from the first message. The method further includes: the RAN node sends a second message to the UE based on the SDU.

[0065] The first message may include a quality-of-service flow identifier (QFI). The method may further include: the RAN node sends a third message including the SDU to a core network (CN) function (CNF) through a session established between the UE and the CNF. The method may further include: the RAN node receives a fourth message from the CNF through the session, the fourth message including a processed version of the SDU obtained based on the handling indicated by the QFI.

[0066] The QFI may indicate processing and handling, and the method may further include: the RAN node processes the SDU according to the processing and handling to obtain a processed version of the SDU.

[0067] The method may further include: the RAN node constructs a set of packet data units (PDUs) including the processed version of the SDU, where the second message includes the set of PDUs.

[0068] At least one PDU in the set of PDUs may include a header indicating one or more of the following: the type of the network service, a sequence number, an indication of whether further processing is required, an indication of directly forwarding the PDU, routing information, the QFI to which the PDU belongs.

[0069] Receiving the message, retrieving the SDU, and constructing the set of PDUs may be performed by a processing function at the RAN node.

[0070] The first message may be received through a data bearer established between the RAN node and the UE, and the data bearer is for the network service. The data bearer may be configured through an RRC message or a signaling message received from a control plane function.

[0071] The data bearer may be a dedicated data bearer of the UE. The UE may be part of a UE group, and the data bearer may be used for the UE group. The data bearer may be mapped to one or more of multicast / broadcast service (MBS) radio bearers (MRBs).

[0072] The RAN node sending the second message to the UE may include: the RAN node sends the second message to each UE in the UE group through an MRB.

[0073] The network service may be a NET4AI service, and the first message may indicate local model parameters of the UE. In the case where the network service is NET4AI, retrieving the SDU from the message includes: the RAN node retrieves the local model parameters.

[0074] In the case where the first message includes a QFI, the method may further include: the RAN node aggregates local model parameters of multiple UEs including the UE based on the processing and handling indicated by the QFI. The method may further include: the RAN node obtains global model parameters based on the aggregation and the processing and handling.

[0075] The method may further include: the RAN node sending a third message to a core network function (CNF) via a session established between the UE and the CNF, the third message including the local model parameters. The method may further include: the RAN node receiving a fourth message from the CNF, the fourth message including global-local parameters determined based on the local model parameters of multiple UEs including the UE.

[0076] The method may further include: the RAN node constructing a set of PDUs including the global-local parameters, wherein the second message includes the set of PDUs.

[0077] The network service may be a DAM service, and the first message may indicate an output of an adversarial model based on training the adversarial model. In the case where the network service is a DAM service, retrieving the SDU from the first message may include: the RAN node retrieving the output of the adversarial model.

[0078] In the case where the network service is a DAM service and the first message may include a QFI, the method may further include: the RAN node training a generative model using the output of the adversarial model based on the processing and handling indicated by the QFI. The method may further include: the RAN node obtaining an output of the generative model based on the training and the processing and handling.

[0079] In the case where the network service is a DAM service, the method may further include: the RAN node sending a third message to a core network (CN) function (CNF) via a session established between the UE and the CNF, the third message including the output of the adversarial model. The method may further include: the RAN node receiving a fourth message from the CNF, the fourth message including an output of a generative model trained at least in part based on the output of the adversarial model.

[0080] In the case where the network service is a DAM service, the method may further include: the RAN node constructing a set of PDUs including the output of the generative model, wherein the second message includes the set of PDUs.

[0081] According to another aspect, another method is provided. The method includes: a radio access network (RAN) node receiving a first message including data associated with a network service from a network node (NN). The method may further include: the RAN node processing the data according to the network service to obtain a processed version of the data. The method may further include: the RAN node sending a message including the processed version of the data to a second NN.

[0082] The NN may be one of a core network (CN) function (CNF), a second RAN node, and a user equipment (UE). The second NN may be one of the CNF, a second CNF, a second RAN node, a third RAN node, the UE, and a second UE.

[0083] The method may further include: the RAN node retrieving the data including a first set of service data units (SDUs); wherein processing the data includes processing the first set of SDUs.

[0084] According to another aspect, another method is provided. The method includes: a receiving processing function (PF) at a network node (NN) receiving one or more protocol data units (PDUs) associated with a network service from a sending PF at a second NN. The method may further include: the receiving PF at the NN retrieving one or more service data units (SDUs) from the PDUs. The method may further include: the receiving PF at the NN sending the one or more SDUs to one of a sending PF at the NN and an upper layer of the NN.

[0085] The method may further include: the receiving PF at the NN processing the one or more SDUs to obtain processed SDUs, the processing being performed according to a data processing disposition associated with quality of service (QoS) requirements. Sending the one or more SDUs includes: sending the processed SDUs.

[0086] The method may further include: the receiving PF at the NN caching the retrieved one or more PDUs.

[0087] The method may further include: the receiving PF at the NN numbering the one or more SDUs in sequence. Transmitting the one or more SDUs includes: transmitting the one or more SDUs according to the sequence numbering.

[0088] The one or more SDUs may be transmitted according to routing information, where the routing information is determined by one of the following: the configuration at the receiving PF at the NN, the header of the one or more PDUs, and the receiving PF at the NN by generating the routing information.

[0089] The NN may be a radio access network (RAN) node, and the second NN may be one of a user equipment (UE) and a second (RAN) node.

[0090] The receiving PF at the NN may be configured by one of RRC signaling or a signaling message. At least one of the one or more PDUs may include a header indicating one or more of the following: service type, sequence number, an indication for determining whether further processing is required, an indication for directly forwarding the PDU, routing information, the quality of service (QoS) flow identifier (ID) to which the PDU belongs.

[0091] The second NN may be a UE; and the one or more PDUs may be received via a data bearer established between the RAN node and the UE.

[0092] The data bearer may be configured by an RRC message or a signaling message received from a control plane function. The data bearer may be a dedicated data bearer of the UE. The UE may be part of a UE group, and the data bearer may be used for the UE group.

[0093] The data bearer may be mapped to one or more of a multicast / broadcast service (MBS) radio bearer (MRB). The one or more PDUs may be received via the one or more MRBs.

[0094] According to another aspect, another method is provided. The method includes: a transmission processing function (PF) at a network node (NN) receives one or more service data units (SDUs) associated with a network service. The method may further include: the transmission PF at the NN constructs one or more protocol data units (PDUs) corresponding to the one or more SDUs. The method may further include: the transmission PF at the NN sends the one or more PDUs to a reception PF at a second NN.

[0095] The method may further include: the transmission PF at the NN caches the one or more SDUs for further processing. The method may further include: the transmission PF at the NN processes the one or more SDUs to obtain processed SDUs, and the processing is performed according to a data processing disposition associated with quality of service (QoS) requirements. The one or more PDUs may include the processed SDUs.

[0096] The method may further include: the transmission PF at the NN sequence numbers the one or more PDUs. Sending the one or more PDUs may include: sending the one or more PDUs according to the sequence numbers.

[0097] The method may further include: adding routing information to the header of the one or more PDUs. The routing information may be determined by one of the following: configuration at the transmission PF at the NN, and the transmission PF at the NN generates the routing information.

[0098] The NN may be a radio access network (RAN) node. The one or more SDUs may be received from one of the following: a reception PF at the NN and an upper layer of the NN.

[0099] The transmission PF at the NN may be configured by one of RRC signaling or a signaling message.

[0100] At least one of the one or more PUDs includes a header indicating one or more of the following: service type, sequence number, an indication for determining whether further processing is required, an indication for directly forwarding the PDU, routing information, a quality of service (QoS) flow identifier (ID) to which the PDU belongs.

[0101] The second NN may be a user equipment, and the one or more PDUs may be sent through a data bearer established between the RAN node and the UE.

[0102] The data bearer may be configured through an RRC message or a signaling message received from a control plane function. The data bearer may be a dedicated data bearer of the UE. The UE is part of a UE group, and the data bearer is for the UE group.

[0103] The data bearer is mapped to one or more of multicast / broadcast service (MBS) radio bearers (MRBs). The one or more PDUs may be sent through the one or more MRBs.

[0104] According to another aspect, there is provided another method for providing network services in a network. The network may include a first network element and a second network element. The method may be performed by the first network element. The method includes: obtaining a service data unit (SDU). The method further includes: generating a protocol data unit (PDU) including the SDU. The method further includes: providing the PDU to the second element. The first element may be one of a user equipment (UE) and a radio access network (RAN) node. The second element may be the other of the UE and the RAN node.

[0105] According to another aspect, there is provided an apparatus. The apparatus includes modules for performing one or more of the methods and systems described herein.

[0106] According to one aspect, there is provided an apparatus, wherein the apparatus includes: a memory for storing a program; a processor for executing the program stored in the memory, and when the program stored in the memory is executed, the processor is for performing one or more of the methods and systems described herein.

[0107] According to another aspect, there is provided a computer-readable medium, wherein the computer-readable medium stores program code executed by a device, and the program code is for performing one or more of the methods and systems described herein.

[0108] According to one aspect, there is provided a chip, wherein the chip includes a processor and a data interface, and the processor reads instructions stored in a memory through the data interface to perform one or more of the methods and systems described herein.

[0109] Other aspects of the present invention provide apparatuses and systems for implementing the methods according to the first aspect disclosed herein. For example, a wireless station and an access point may be configured with a machine-readable memory including instructions that, when executed by a processor of these devices, configure the devices to perform one or more of the methods and systems described herein.

[0110] Embodiments have been described above in connection with aspects of the present invention, and these embodiments may be implemented based on these aspects. Those skilled in the art will understand that embodiments may be implemented in combination with the aspects describing these embodiments, but may also be implemented together with other embodiments of that aspect. When embodiments are mutually exclusive or incompatible with each other, it will be obvious to those skilled in the art. Some embodiments may be described in connection with one aspect, but may also be applicable to other aspects, which will be obvious to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0111] In conjunction with the accompanying drawings, further features and advantages of the present invention will become apparent from the following detailed description.

[0112] FIG. 1 shows a user plane protocol stack between a user equipment (UE) and a user plane function (UPF).

[0113] FIG. 2 shows a user plane protocol stack between a UE and a radio access network (RAN).

[0114] Figure 3 Shows an enhanced UP protocol stack between a UE and a RAN provided by one aspect.

[0115] Figure 4 Shows an XaaS bearer in 6G provided by one aspect.

[0116] Figure 5 Shows 6G data handling provided by one aspect.

[0117] Figure 6 Shows dynamic configuration in different cases provided by one aspect.

[0118] Figure 7 Shows a functional view of the PF sublayer provided by one aspect.

[0119] Figure 8 Shows another functional view of the PF sublayer provided by one aspect.

[0120] Figure 9 Shows a data path in the PF sublayer provided by one aspect.

[0121] Figure 10 Shows the process of the XaaS task related to the PF sublayer provided by one aspect.

[0122] Figure 11 Shows a structural view of the PF sublayer provided by one aspect.

[0123] Figure 12 Shows the data flow provided by one aspect.

[0124] Figure 13 Shows the format of the PF PDU provided by one aspect.

[0125] Figure 14 Shows a table indicating the description of the Xs field provided by one aspect.

[0126] Figure 15 Shows a table indicating the description of the P / F field provided by one aspect.

[0127] Figure 16 Shows the DL layer 2 architecture for XaaS and PDU connection services provided by one aspect.

[0128] Figure 17 Shows a model of a PF entity provided by one aspect, the PF entity including a transmitting part (Tx part) and a receiving part (Rx part).

[0129] Figure 18 Shows another PF entity including a Tx part and an Rx part provided by one aspect.

[0130] Figure 19 Shows the service data adaptation protocol (SDAP) protocol data unit (PDU) format having an XaaS quality of service flow identifier (XQFI) field in the SDAP header provided by one aspect.

[0131] Figure 20 Shows another DL layer 2 architecture 2060 for PDU connection services provided by one aspect.

[0132] Figure 21 Shows an apparatus provided by different aspects of the present invention, the apparatus being capable of performing any or all of the operations of the above-described methods and features explicitly or implicitly described herein.

[0133] It should be noted that in all the drawings, the same features are identified by the same reference numerals. Detailed implementation manners

[0134] The present invention provides a system and method for a RAN protocol for a future X-centric service network. According to one aspect, an enhanced RAN node is provided, including one or more processing functions. In addition to the existing data forwarding function, the enhanced RAN node can also support performing operations at the RAN node. For example, the RAN node can parse and process data through its one or more processing functions and other functions described in one or more aspects herein. According to one aspect, an enhanced user plane protocol stack can be provided to support the enhanced RAN node and one or more processing functions therein. According to another aspect, enhanced bearers can be provided to further support the functions of the enhanced RAN node.

[0135] According to one aspect, a method is provided. The method includes: a radio access network (RAN) node receiving data traffic associated with a network service and having a quality-of-service flow identifier (QFI) from a user equipment (UE). The QFI can indicate the processing disposition of the associated traffic. The method further includes: the RAN node retrieving a first set of service data units (SDUs) from the data traffic. The method further includes: the RAN node sending a second data traffic to the UE at least partially based on the first set of SDUs. The method may further include: the RAN node constructing a set of protocol data units (PDUs) including a processed version of the first set of SDUs, wherein the second data traffic includes the set of PDUs.

[0136] The method may further include: the RAN node processing the first set of SDUs according to the processing disposition to obtain a processed version of the first set of SDUs. The method may further include: the RAN node constructing a set of PDUs including the processed version of the first set of SDUs, wherein the second data traffic includes the set of PDUs. The method can enhance the functions of the RAN node, thereby improving the availability and provision of 6G services.

[0137] In addition to traditional connection-oriented communication services, 6G also includes new service types for network-native data processing, such as data analysis, artificial intelligence (AI) training, AI inference, data privacy protection, data storage, data cleaning, data normalization, useless data filtering, and data feature engineering.

[0138] 6G can propose a network centered around X to provide X as a service (XaaS). In some aspects, XaaS can be data analytics and management (DAM) as a service, NET4AI as a service, NET4Data as a service, NET4meta as a service, etc. In some aspects, these services can be provided by one or more service providers. The one or more service providers include one or more of operators, vendors, network functions, network devices, and third parties.

[0139] In one aspect, the DAM service can include (by one or more service providers) collecting data from data sources and providing the collected data to data consumers in a privacy-protected form (e.g., de-identified data or anonymized data, etc.). The data consumers can use the collected data to perform tasks such as data analysis, AI training, and AI inference.

[0140] In some aspects, the NET4AI service can include providing connection and intelligent computing services, e.g., for AI training and AI inference. In some aspects, the NET4Data service can include providing data storage services and performing data access control. In some aspects, two or more of these services can be combined and provided to customers. For the combined services, one or more service providers can cooperate with each other to provide the combined services.

[0141] Each XaaS may involve one or more functions when providing services. In some aspects, each XaaS may involve a service controller (XC). The XaaS XC (or XC) can control and manage the service. For example, the XC can control and configure the XaaS processing function (PF) to perform specific tasks involved in the XaaS.

[0142] In some aspects, each XaaS can also involve one or more PFs. The XaaS PF (or PF) can perform one or more XaaS tasks under the control of the XC. Some examples of XaaS tasks can include data preprocessing and data privacy protection tasks in the DAM service, AI training and AI inference tasks in the NET4AI service, and data storage and access control tasks in the NET4Data service.

[0143] In some aspects, each XaaS can be provided by an XaaS module. Each module can be associated with an XC and one or more PFs.

[0144] In some aspects, one or more XaaS functions (e.g., XC, PF) can be deployed in one or more of a radio access network (RAN), a core network (CN), and a user equipment (UE) side. For example, XC can be deployed in the network control plane, and PF can be deployed in the network user plane or data plane. Some aspects of the present invention can deploy PF into the network, for example, into the RAN and the UE side.

[0145] Figure 1 shows the user plane protocol stack between a user equipment (UE) and a user plane function (UPF). As shown, the protocol stack at UE 102 can include an application layer 104, a PDU layer 106, and a 5G access network (AN) protocol layer 108. UE 102 can be connected to a 5G-AN node 110 as shown. The protocol stack at the 5G-AN node 110 can include a 5G-AN protocol layer 112, a GTP-U layer 114, a UDP / IP layer 116, an L2 layer 117, and an L1 layer 118.

[0146] The 5G-AN node 110 can be connected to the UPF 120 through an N3 interface 140. The protocol stack of the UPF 120 connected to the 5G-AN node 110 can include a GTP-U layer 121, a UDP / IP layer 122, an L2 layer 123, and an L1 layer 124. The UPF 120 can use an N9 interface 142 to connect to a UPF PDU session anchor 130. As shown, the protocol stack of the UPF 120 connected to the UPF PDU session anchor 130 can include a GTP-U layer 125, a UDP / IP layer 126, an L2 layer 127, and an L1 layer 128. The UPF PDU session anchor 130 can be connected to a data network through an N6 interface 144. The protocol stack at the UPF PDU session anchor 130 can include a PDU layer 131, a GTP-U layer 132, a UDP / IP layer 133, an L2 layer 134, and an L1 layer 135.

[0147] Referring to Figure 1, taking the following downlink data traffic (which can be similar to the uplink data traffic from the application layer on the UE side) as an example, for a traditional connection-oriented communication network, the data traffic flow and the data mapping between different protocol layers can be as follows.

[0148] Application data (e.g., service data flow (SDF)) can be encapsulated into protocol data unit (PDU) layer data or packets (e.g., TCP or IP packets) and sent to one or more core network (CN) functions (e.g., user plane function (UPF)).

[0149] One or more CN functions (e.g., UPF) can classify the PDU layer data for Quality of Service (QoS) flow marking (e.g., based on packet detection rules) and further map the QoS flow to a GTP-U tunnel. One or more CN functions can map the PDU layer data to GTP-U layer data. If the PDU session resources are established under the control of one or more of the AMF, SMF, and RAN, the mapping between the GTP-U tunnel on the N3 interface and the PDU session / QoS flow can be aligned between the UPF 130 and 120 and the RAN (e.g., 5G-AN node 110).

[0150] The RAN can map the QoS flow received through a specific GTU-U tunnel to access network resources (e.g., DRB). Then, the UE 102 can map the QoS flow to the DRB based on its local configuration or notification information from the RAN or CN (e.g., the mapping information between the QoS flow and the DRB). For example, the UE 102 can map the downlink data of a specific DRB to a PDU session (QoS flow) for submission to the PDU layer and the application layer. In some cases, the UE 102 can map the uplink application data and PDU layer data to the PDU session / QoS flow and then map it to a specific DRB for sending to the peer RAN.

[0151] For the RAN (e.g., 5G-AN node 110), perform the mapping between QoS flows and DRBs. Referring to FIG. 2, a DRB may be configured with a service data adaptation protocol (SDAP) sublayer, a packet data convergence protocol (PDCP) sublayer, a radio link control (RLC) sublayer, a medium access control (MAC) sublayer, and a physical layer (PHY). A PDU session may be configured with one SDAP entity. A DRB may be configured with one PDCP entity. The data of a PDU session including one or more QoS flows may be mapped by the SDAP sublayer to one or more DRBs.

[0152] FIG. 2 shows the user plane protocol stack between the UE and the radio access network (RAN). As shown, the 5G-AN protocol layer 108 at the UE 102 may include an SDAP sublayer 202, a PDCP sublayer 203, an RLC sublayer 204, a MAC sublayer 205, and a PHY layer 206. The 5G-AN protocol layer 112 at the RAN may include an SDAP sublayer 212, a PDCP sublayer 213, an RLC sublayer 214, a MAC sublayer 215, and a PHY layer 216.

[0153] For downlink transmission, the UE SDAP entity may receive an SDAP SDU from the upper layer and submit an SDAP PDU to its peer SDAP entity through the lower layer. For uplink transmission, the UE SDAP entity of the UE may transmit an SDAP SDU to the upper layer and receive an SDAP PDU from its peer SDAP entity through the lower layer.

[0154] Those skilled in the art can understand that the processes or operations described with reference to FIGS. 1 and 2 are designed for the purpose of data forwarding. In these processes, data is transparently processed in each layer without the need to parse and understand the payload (except that the UE application layer may parse the data). For example, a service data unit (SDU) may be processed by each layer (e.g., encrypted, segmented, sorted) without the need to parse and understand the SDU payload. Thereafter, the processed data (e.g., PDU) may be sent to the next layer based on the data mapping scheme.

[0155] Data processing (e.g., encryption, segmentation, sorting) and data mapping processes can be understood as connection-oriented. However, for 6G, it may be desirable to parse and process data within the network (e.g., by the RAN) rather than within the application layer. Such functionality (e.g., parsing and processing data) may be required when the network (e.g., the RAN) natively provides XaaS.

[0156] In addition, it may be desirable to parse and process data through XaaS functionality, for example, in processes related to AI training, AI inference, data privacy protection, etc. However, as shown in FIGS. 1 and 2, one or more sub-layers and layers in the current 5G RAN may lack the functionality required to support XaaS and perform one or more tasks in XaaS.

[0157] In addition, in 5G, the RAN may not be the source or destination of user plane (UP) data. On the data source side, the RAN may not generate UP data. Instead, in the 5G RAN, UP data is received from the CN (e.g., UPF) or the UE. On the data destination side, when receiving UP data, the RAN may not intercept, retain, and use the received UP data. Instead, the RAN may forward the received UP data to the CN (if it is an uplink) or the UE (if it is a downlink) as soon as possible.

[0158] Referring to FIGS. 1 and 2, each sub-layer or layer on the UP in the current 5G RAN may not be the source or destination of UP data. In the current 5G RAN, after receiving UP data, each sub-layer or layer on the UP may forward the received UP data to its lower layer or upper layer (without intercepting, retaining, and using the received UP data).

[0159] However, in 6G, the RAN can be the source or destination of UP data. In some aspects, the RAN itself can generate entirely new data (e.g., the RAN, as a sensor, can sense and generate sensed data, and the RAN can generate a trained AI model by transforming training data). In some aspects, the RAN can be the destination of uplink data received from the UE. For example, uplink data received from the UE (e.g., intermediate AI parameters) can be aggregated, terminated, and used by the RAN (e.g., for the RAN to obtain a final AI model, which can be used by the RAN to optimize the network) instead of being forwarded to the CN.

[0160] As can be understood by those skilled in the art, the current RAN protocol stack may not support 6G new requirements, such as XaaS. Aspects of the present invention can provide improved RAN functionality rather than data forwarding. According to one aspect, the RAN can support providing XaaS. For example, the RAN can parse and process data, and the RAN can be used as the source or destination of UP data.

[0161] For the air interface related to the current 5G air interface, there are two types of radio bearers: signaling radio bearers (SRBs) that carry radio resource control (RRC) signaling on the control plane, and data radio bearers (DRBs) that carry data traffic on the user plane. However, SRBs and DRBs may not carry XaaS data because these radio bearers may be limited to forwarding PDU layer data. According to one aspect, an improved bearer is provided that can support XaaS data (e.g., AI data, DAM data, private data, blockchain data, etc.).

[0162] According to one aspect, a data PF for XaaS on the RAN side can be provided. Figure 3 An embodiment of an enhanced UP protocol stack between a UE and a RAN provided by one aspect of the present invention is shown. According to one aspect, the PF in the RAN can be deployed as a RAN radio layer 2 protocol sublayer between the SDAP sublayer 313 and the PDCP sublayer 315, such as the PF sublayer 314, as shown.

[0163] In some aspects, the protocol stack at the UE 300 may include an application layer 301, a PDU layer 302, an SDAP sublayer 303, a PF sublayer 304, a PDCP sublayer 305, an RLC sublayer 306, a MAC sublayer 307, and a PHY layer 308. In some aspects, the protocol stack at the RAN 310 may include an SDAP sublayer 313, a PF sublayer 314, a PDCP sublayer 315, an RLC sublayer 316, a MAC sublayer 317, and a PHY layer 318.

[0164] In some aspects, based on the PF sublayers 304 and 314, one or more enhanced bearers for supporting 6G services can be provided.

[0165] Figure 4 An embodiment of an XaaS bearer in 6G provided by one aspect of the present invention is shown. In one aspect, the protocol layers at the RAN 310 and the UE 300 can be enhanced to support XaaS data bearers 450 and XaaS signaling bearers 452 in 6G. To support the XaaS data bearer 450, the protocol stacks at the RAN 310 and the UE 300 can respectively include the PF sublayers 314 and 304 as described herein. To support the XaaS signaling bearer 452, the protocol stacks at the RAN 310 and the UE 300 can respectively include XC sublayers 414 and 404.

[0166] As shown in the figure, data forwarding in 5G can involve SRB 440 and DRB 442 between RAN 310 and UE 300.

[0167] The data forwarding service in 5G can also involve PDU connection services, which can be defined and provided by the 5G network, for example. The PDU connection service can refer to a service that provides PDU exchange between the UE and the data network.

[0168] The data forwarding service in 5G can also involve one or more PDU sessions, such as PDU session 446, as defined in the 5G network. A PDU session can refer to the association between the UE and the data network that provides the PDU connection service.

[0169] According to one aspect, 6G can involve XaaS. XaaS can be a service that provides data processing between the UE and the CN XaaS function (e.g., PF or data network deployed in the CN).

[0170] In some aspects, XaaS can be a service that provides data processing between the XaaS customer and the XaaS network function, such as between the UE and the CN XaaS function, between a third-party server and the CN XaaS function, between the UE and the DN, between the DN and the CN PF, and between the server and the RAN node, etc.

[0171] In some aspects, XaaS in 6G can further involve the XaaS session 420. The XaaS session can refer to the association between the XaaS customer and the XaaS network function that provides XaaS. In some aspects, the XaaS session 420 can be the association between UE 300 and the CN XaaS function that provides XaaS (e.g., PF deployed in the CN, or data network). In some aspects, the XaaS session 420 can be established between the UE and the CNPF unit, or between the UE and the DN.

[0172] In some aspects, 6G XaaS can be implemented on top of the 5G PDU connection service. In some aspects, establishing an XaaS session can include: establishing relevant resources (e.g., connection resources, computing resources, and storage resources) for completing XaaS tasks. In some aspects, the XaaS session can be regarded as an improved PDU session, the purpose of which is to perform data processing in addition to data forwarding.

[0173] In some aspects, through the XaaS session, data can be flexibly processed in different nodes. For example, in the CN PF unit, in the PF sublayer 314 of the RAN, and in the PF sublayer 304 of the UE. The number of participating nodes (e.g., RAN, UE, and CN functions) in the XaaS session can be unrestricted. Therefore, the XaaS session can pass through several RAN nodes, and these RAN nodes can cooperate to process XaaS data sequentially or in parallel.

[0174] In some aspects, XaaS in 6G can also involve the XaaS bearer ( Figure 5 510 in), which can include the XaaS data bearer 450 and the XaaS signaling bearer 452). The XaaS bearer can refer to the service provided by the RAN radio layer 2 (including the PF sublayer and the XC sublayer) for both data transmission and data processing between the UE 300 and the RAN 310. In some aspects, the XaaS bearer can refer to the channel provided by the RAN radio layer 2 (including the PF and XC sublayers) to the upper layer for both data transmission and data processing. Therefore, the PF and XC sublayers can provide data forwarding and data processing services between the UE and the RAN to the upper layer through the XaaS bearer. The service access point between the PF sublayer and the upper layer (or between the XC sublayer and the upper layer) can be the XaaS bearer.

[0175] In some aspects, the XaaS bearer can include the XaaS data bearer (XDB) 450 for user plane data. In some aspects, each XDB can be configured with the PF sublayer 314 at the RAN and the PF sublayer 304 at the UE, the PDCP sublayer 315 at the RAN and the PDCP sublayer 305 at the UE, the RLC sublayer 316 at the RAN and the RLC sublayer 306 at the UE, the MAC sublayer 317 at the RAN and the MAC sublayer 307 at the UE, and the PHY layer 318 at the RAN and the PHY layer 308 at the UE.

[0176] In some aspects, XaaS bearer can include an XaaS signaling bearer (XSB) 452 for control plane data. In some aspects, as shown in the figure, each XSB 452 can be configured with an XC sublayer 414 at the RAN and an XC sublayer 404 at the UE (instead of a PF sublayer), a PDCP sublayer 415 at the RAN and a PDCP sublayer 405 at the UE, an RLC sublayer 416 at the RAN and an RLC sublayer 406 at the UE, a MAC sublayer 417 at the RAN and a MAC sublayer 407 at the UE, and a PHY layer 418 at the RAN and a PHY layer 408 at the UE. In some aspects, the XC sublayer 414 at the RAN and the XC sublayer 404 at the UE can be located above the PDCP sublayer 415 at the RAN and the PDCP sublayer 405 at the UE to transmit signaling messages between the RAN and the UE, for example, to configure and control the PF sublayer.

[0177] In some aspects, XaaS in 6G can also involve XaaS QoS flows. According to one aspect, an XaaS QoS flow can be the finest granularity of QoS differentiation in an XaaS session 420. In some aspects, traffic mapped to the same XaaS QoS flow can receive the same data forwarding treatment and data processing treatment.

[0178] Providing different XaaS QoS data processing treatments and data forwarding treatments may require separate XaaS QoS flows. An XaaS QoS flow ID (XQFI) can be used to identify an XaaS QoS flow. The XQFI can be a scalar ID used as a reference for a specific XaaS QoS characteristic. Traffic (e.g., user plane traffic) within an XaaS session with the same XQFI can receive the same data processing treatment and data forwarding treatment. Data processing treatment can refer to computing precision, computing latency, privacy level, storage duration, data processing strategy, data cleaning strategy, data normalization strategy, etc. Data forwarding treatment can include scheduling strategy, queue management strategy, link layer protocol configuration (e.g., MAC / RLC configuration), access threshold, etc. In some aspects, the XQFI can be carried in the encapsulation header of a CN, UE, or RAN message (e.g., GTP-U message header, SDAP message header, segment routing over IPv6 (SRv6) message header, quick UDP internet connections (QUIC) message header).

[0179] In some aspects, XaaS in 6G can also involve XaaS QoS parameters. The XaaS QoS parameters can include parameters regarding data forwarding handling and parameters regarding data processing handling. In some aspects, the XaaS QoS parameters can be configured per node (e.g., per UE), per network function, per XaaS session, per XaaS QoS flow, or per XaaS bearer.

[0180] In some aspects, the data forwarding handling parameters can include one or more of the following: data transmission resource scheduling policy, data queue management policy, data transmission priority level, link layer protocol configuration (e.g., MAC / RLC configuration), access threshold, data loss rate, data transmission delay, data forwarding security protection method, security level, etc. The data forwarding handling parameters can relate to data forwarding in the data plane, e.g., data forwarding in the RAN L2 / L1 layer and data forwarding in the CN UPF.

[0181] In some aspects, the data processing handling parameters can include one or more of the following: data processing scheduling policy, computing precision, computing delay, AI model type, privacy protection method, privacy level, data storage duration, data processing policy, data cleaning policy, data normalization policy, data quality level, data processing priority, etc. The data processing handling parameters can be related to data processing in the UE PF sublayer, RAN PF sublayer, or CN PF.

[0182] In some aspects, the data forwarding handling parameters and the data processing handling parameters can be cross - adjusted and dynamically adapted, for example, under the control of the XC or other control plane functions. For example, the data transmission delay and the computing delay can be cross - adjusted to ensure the total delay threshold of the XaaS task, e.g., so as to reduce the data transmission delay while increasing the computing delay to achieve balance.

[0183] In some aspects, one or more data forwarding handling parameters can be associated with one or more data processing handling parameters. For example, ensuring a data forwarding handling parameter (e.g., data loss rate) can be a prerequisite for ensuring a data processing handling parameter (e.g., computing precision).

[0184] In some aspects, an XaaS session can be configured with an SDAP entity. Each XaaS bearer can be configured with a PF entity. Each DRB can be associated with a PDCP entity. In some aspects, the SDAP sublayer can perform the mapping between data of one or more XaaS QoS flows and one or more XaaS bearers. One or more XaaS QoS flows can be mapped to one XaaS bearer. One or more XaaS bearers can be further mapped to one or more DRBs.

[0185] In some aspects, if the traffic granularity of the XaaS QoS flow is the same as the traffic granularity carried by the XaaS, the mapping between the XaaS QoS flow and the XaaS bearer may not be required, and thus the SDAP entity may not be configured.

[0186] Figure 5 An embodiment of 6G data handling provided by one aspect of the present invention is shown. For traditional connection-oriented services, such as service 502, a PDU session is established between the UE and the DN, where UL or DL data is transmitted between the UE and the CN DN without bifurcation (e.g., without changing the traffic direction). Thus, in traditional connection-oriented services, the RAN node can act as a pipeline, forwarding the data (DL or UL) received from the CN or the UE to the lower or upper layer without intercepting or retaining the data. The UL or DL data traffic received by the RAN is unidirectionally forwarded. For example, the RAN cannot directly send the UL UP data received from the UE back to the UE, or directly send the DL UP data received from the CN DN back to the CN DN.

[0187] According to one aspect, for 6G XaaS, due in part to one or more of the PF sublayer, the XaaS bearer 510, and the XaaS session 420, the UL or DL data traffic received by the RAN 310 can be bidirectionally or multi-directionally forwarded. For example, the RAN 310 can send the UL UP data received from the UE 506 (which can be similar to the UE 300) back to the UE 506 or another UE 508 (which can also be similar to the UE 300) after data processing. The RAN 310 can also send the DL UP data received from the CN (e.g., CN PF or CN DN) back to the CN after data processing. As another example, the RAN 310 can send the UL UP data received from the UE to another RAN through the PF sublayer after data processing. The RAN 310 can also send the DL UP data received from the CN function (e.g., CN PF or CN DN) to another CN function through the PF sublayer after data processing.

[0188] According to one aspect, through the XaaS session, data can be flexibly processed between different nodes, such as in the PF sublayer of the RAN, in the PF sublayer of the UE, in the CN PF unit, etc. The number of nodes participating in the XaaS session (e.g., RAN, UE, and CN function) can be unrestricted. For example, the XaaS session can pass through one or more RAN nodes, and these RAN nodes can cooperate to process the XaaS data sequentially or in parallel. In some aspects, the participation order and routine of different nodes can be flexible.

[0189] In addition, different from deploying the PF outside the RAN (e.g., in the MEC or cloud), deploying the PF in the RAN radio layer 2 enables the RAN to understand and adjust the performance of the XaaS. For example, the RAN can understand to adjust the performance of the XaaS based on one or more of the following: the combined consideration of XaaS requirements (e.g., data processing and forwarding requirements), the XaaS resource status (e.g., data processing resources (e.g., computing load)), and the data forwarding radio resources (e.g., wireless CSI status).

[0190] Figure 6 Embodiments of the dynamic configuration in different cases provided by one aspect of the present invention are shown. In some aspects, it may be only necessary for the RAN to perform the data forwarding service without XaaS capabilities, or the RAN does not need to participate in the XaaS, such as in case 602. In this case, there is no need to process data at the RAN, so the PF sublayer may not be configured in the RAN, and the RAN can operate according to the 5G RAN capabilities. As shown, in case 602, a PDU session tunnel can be established between the CN and the RAN, and a DRB can be established between the RAN and the UE.

[0191] In some aspects, the RAN can have XaaS capabilities, and the XaaS can only involve the RAN and the UE (not involving the CN), such as in case 604. In this case, the PF sublayer 314 can be configured at the RAN, however, the RAN SDAP sublayer and the XaaS session tunnel between the RAN and the CN may not be configured. In addition, the PF sublayer 304 can be configured at the UE, as shown. Additionally, an XaaS bearer can be established between the RAN and the UE.

[0192] In some aspects, the RAN can have XaaS capabilities, and the XaaS can only be processed in the RAN and the CN, such as in case 606. In this case, the PF sublayer can be configured at the RAN. However, the SDAP sublayer, the radio L2 sublayer, and the PHY layer may not be configured at the RAN.

[0193] In some aspects of case 606, the SDAP sublayer can be configured at the RAN (where the SDAP PDU at the SDAP layer can be configured to include a data field and not include a header (e.g., no DL SDAP header or UL SDAP header), while the radio L2 sublayer and the PHY layer may not be configured at the RAN simultaneously. The PF can also be configured at the CN. In addition, an XaaS session tunnel can be established between the RAN and the CN to support the RAN XaaS capabilities.

[0194] In some aspects, XaaS can be processed by the CN, RAN, and UE in sequence, such as in case 608. In this case, sub-layers can be configured at the RAN and UE, and the sub-layers include an SDAP sub-layer, a PF sub-layer, a PDCP sub-layer, an RLC sub-layer, a MAC sub-layer, and a PHY layer. In addition, an XaaS session tunnel can be configured between the CN and the RAN. Similarly, as shown in the figure, an XaaS bearer can be established between the RAN and the UE.

[0195] According to one aspect, data mapping can be provided between the upper layer (e.g., PDU layer, GTP-U layer), the SDAP sub-layer, the PF sub-layer, and the PDCP sub-layer. According to another aspect, a functional view of the PF sub-layer can be provided. According to another aspect, a structural view of the PF sub-layer can be provided. According to another aspect, the format and parameters of the protocol data unit (PDU) of the PF sub-layer can be provided. According to another aspect, a data mapping scheme can be provided for different cases (e.g., where a UE or a group of UEs and RAN-PF are involved in XaaS tasks). In some aspects, the XaaS bearer can be configured per UE or per UE group.

[0196] Figure 7 An embodiment of the functional view of the PF sub-layer provided by one aspect of the present invention is shown. As shown in the figure, the PF sub-layer 700 can include one or more PF entities. In some aspects, one or more PF entities (e.g., a transmitting PF (Tx-PF) entity 702 or a receiving PF (Rx-PF) entity 712) can be deployed or configured in nodes (e.g., UE, CN side, and RAN side).

[0197] In one aspect, if the Tx-PF entity 702 is deployed in the UE, the Rx-PF entity 712 can be deployed in the RAN. Similarly, if the Tx-PF entity 702 is deployed in the RAN, the Rx-PF entity 712 can be deployed in the UE.

[0198] Figure 7 It can be based on the radio interface protocol architecture. Those skilled in the art can understand that Figure 7 This is only an illustration of the PF sub-layer according to one aspect, and thus does not limit how the PF sub-layer can be implemented. Other reasonable implementations of the PF sub-layer 700 can be known to those skilled in the art and are part of the scope of one or more aspects of the present invention.

[0199] In some aspects, if the transmitting PF entity is deployed in the UE, the receiving PF entity can be deployed in the RAN. Similarly, if the transmitting PF entity is deployed in the RAN node, the receiving PF entity can be deployed in the UE.

[0200] In one aspect, PF entities 702 and 712 can be located in the PF sub-layer of XaaS. In some aspects, several PF entities can be configured for a UE or a RAN node. In some aspects, in 6G, for each individual XaaS bearer on the air interface, a PF entity can be configured.

[0201] In some aspects, a PF entity can receive (or transmit) a PF SDU from (or to) an upper layer or another PF entity, and can submit (or receive) a PF PDU to (or from) its peer PF entity via a lower layer.

[0202] In some aspects, the transmitting PF entity 702 can receive a PF SDU from an upper layer and submit or send a PF PDU to its peer PF entity via a lower layer. In some aspects, the transmitting PF entity 702 can receive a PF SDU from another PF entity (e.g., from a receiving PF entity residing in the same node) and submit or send a PF PDU to its peer PF entity via a lower layer.

[0203] In some aspects, the receiving PF entity 712 can transmit a PF SDU to an upper layer and receive a PF PDU from its peer PF entity via a lower layer. In some aspects, the receiving PF entity 712 can transmit a PF SDU to another PF entity (e.g., to a transmitting PF entity residing in the same node) and receive a PF PDU from its peer PF entity via a lower layer.

[0204] Those skilled in the art can understand that in the 5G data forwarding method, each sub-layer of the RAN can only receive data from an upper layer or a lower layer and forward the received data to a lower layer or an upper layer. Therefore, in 5G, the RAN can act as an intermediate pipeline for forwarding data.

[0205] According to one aspect, in the XaaS of 6G, the RAN (e.g., the PF sub-layer) can be a data destination and a data source. In some aspects, a PF entity can receive (or transmit) data from (or to) an upper layer or a lower layer. In some aspects, a PF entity can also receive (or transmit) data from (or to) another PF entity in the same PF sub-layer and the same node. In some aspects, a PF entity can enable XaaS data traffic to be initiated, terminated, or both initiated and terminated at the RAN in the PF sub-layer. For example, 6G sensing data can be initiated at the RAN.

[0206] In some aspects, the PF entity can operate as one or both of a transmitting PF (PF-Tx) entity 702 and a receiving PF (PF-Rx) entity 712, or as one or both of them. Thus, one or more PF entities can be deployed on the same node, and each PF entity can operate as a PF-TX entity or a PF-RX entity.

[0207] According to one aspect, the PF sublayer (via one or more PF entities) can include data buffer components 704 and 714 for supporting data buffering operations (e.g., user plane data). In some aspects, the PF sublayer can include data processing components 705 and 715 for supporting data processing operations (e.g., user plane data). The data processing operations can include operations related to AI and data privacy protection, etc. In some aspects, the PF sublayer can include data transmission components 706 and 716 for supporting data transmission operations (e.g., user plane data). The data transmission operations can include one or more of the following: PF header addition or deletion; maintenance of PF sequence number (SN), e.g., sequence numbering; and reordering and in-order transmission. In some aspects, the PF sublayer can include routing components 707 and 717 for supporting routing operations.

[0208] Although the components (e.g., data buffering, data processing, routing, and data transmission) are shown as separate from each other, in some aspects, one component can serve the functions of two or more components.

[0209] In some aspects, on the same node where the PF entity can reside, the corresponding PF entity can also reside. For example, in the same node where the Tx-PF entity 702 can reside, the Rx-PF entity 701 can also reside. Similarly, in the same node where the Rx-PF entity 712 can reside, the Tx-PF entity 711 can also reside. Thus, according to one aspect, the Tx-PF entity 702 can receive data from one or more upper layers (e.g., CN, when the PF sublayer is deployed below the SDAP sublayer, the SDAP sublayer), and can also receive data from the same layer (e.g., the Rx-PF entity 701), as Figure 9 Further shown.

[0210] According to one aspect, the PF entity can cache data through the data buffer components 704 and 714 to implement "big data" (as can be understood by those skilled in the art). Then, the obtained "big data" can be used for data processing 705 and 715. For example, the Tx-PF entity 702 can cache the PF SDUs received from the upper layer or another PF entity (e.g., from the Rx-PF entity residing in the same node 701). Similarly, the Rx-PF entity 733 can cache the PF PDUs received from its peer sending PF entity through the lower layer.

[0211] For example, in the NET4Data service, DAM service, and NET4AI service, the Rx-PF entity 712 can cache data from one or more Rx-PF entities to achieve the purpose of "big data" data processing. The data processing can include AI training, data privacy protection (e.g., privacy protection using the K-anonymity method). Similarly, the Tx-PF entity can cache the data received from the upper layer or another PF entity (e.g., from the Rx-PF entity residing in the same node 701) to implement "big data" for subsequent data processing.

[0212] According to one aspect, the data processing can involve the PF entity using one or more of the methods such as AI training, AI inference, data analysis, privacy protection, and data preprocessing (e.g., data cleaning, data normalization, useless data filtering, and data feature engineering) to parse and process the data.

[0213] According to one aspect, on the sending side, when the PF entity (e.g., the Tx-PF entity 702) receives one or more PF SDUs from the upper layer or another PF entity (e.g., from the Rx-PF entity residing in the same node 701), the PF entity can construct the corresponding PF PDU and submit it to the lower layer.

[0214] According to one aspect, constructing the PF PDU can include: using one or more methods (e.g., AI training, AI inference, data privacy protection) to parse and process the raw data encapsulated in the payloads of one or more PF SDUs. The construction of the PF PDU is different from the traditional connection-oriented 5G network, where the PDU of each RAN sublayer is constructed without parsing the payload of the SDU.

[0215] In some aspects, upon receiving a PF SDU, one or more parameters associated with the data processing and handling of the PF SDU can be triggered by a PF entity. The one or more parameters can be related to QoS requirements on the XaaS bearer and are optionally preconfigured by the XC at the PF entity. The one or more parameters can include: a time count threshold at which a PF PDU can be constructed, a precision level at which a PF SDU can be processed, and a privacy level that can be guaranteed for the PF PDU.

[0216] According to one aspect, on the receiving side, when a PF entity (e.g., the Rx-PF entity 712) receives a PF PDU from the lower layer, the PF entity can retrieve the corresponding PF SDU. In some aspects, the PF entity can transmit the PF SDU to the upper layer or to another PF entity (e.g., to the transmitting PF entity 711 residing in the same node (e.g., RAN) as the receiving PF entity).

[0217] In some aspects, after retrieving the corresponding PF SDU from the lower layer, the PF entity can parse and process the retrieved one or more PF SDUs. The PF entity can transmit the processed PF SDU to the upper layer or to another PF entity (e.g., to the transmitting PF entity 711 residing in the same node (e.g., RAN) as the receiving PF entity).

[0218] In some aspects, after retrieving the PF SDU, the raw data encapsulated in the one or more retrieved PF SDUs can be parsed and processed using a specific method (e.g., AI training, AI inference, data privacy protection). As can be understood by those skilled in the art, the parsing and processing of the PF SDU can be different from that of a traditional connection-oriented 5G network, where the retrieved SDU is directly forwarded without being parsed and processed.

[0219] As described herein, the PF SDU or the processed PF SDU can be forwarded by the Rx-PF entity 712 to the Tx-PF entity residing in the same node 711 (e.g., RAN) as the receiving PF entity. In some aspects, the transmitting PF entity 711 can forward the PF SDU or the processed PF SDU to a receiving PF entity residing in a peer node (e.g., one or more UEs or another RAN). These operations performed by the Rx-PF entity 712 and the transmitting PF entity 711 can be different from those of a traditional connection-oriented 5G network, where the retrieved SDU is forwarded to the upper layer. The operations of the PF entities (Rx-PF entity and Tx-PF entity) described herein can be applicable to scenarios where XaaS tasks are executed between the UE and the RAN and the XaaS tasks terminate at the RAN without the CN being involved.

[0220] In some aspects, after receiving a PF PDU, one or more parameters associated with the data processing and handling of the PF PDU can be triggered by a PF entity. The one or more parameters can be related to XaaS bearer QoS and are optionally preconfigured by XC for the PF entity. The one or more parameters can include: a time count threshold at which the PF PDU should be processed, a precision level at which the retrieved PF SDU can be processed, and a privacy level that can be guaranteed for the processed PF SDU.

[0221] For example, in the NET4AI service, the PF entity can parse the payload of the received SDU and use it to train an AI model. For example, the Tx-PF entity on the RAN side and the Rx-PF entity on the UE side can cooperate with each other to train an AI model.

[0222] As another example, in the DAM service, the PF entity can process data (which can include or indicate identification information) to protect data privacy. For example, the PF entity can process the payload of the SDU using one or more operations (such as privacy protection methods based on obfuscation, cryptography, hardware, or AI) to delete or hide identification information or anonymize the data.

[0223] In some aspects, data privacy protection can be performed in the Tx-PF entity or the Rx-PF entity or both. In addition, the PF entity can also process non-directly available, useless, and redundant data, such as performing data cleaning, data normalization, useless data filtering, data feature engineering, etc.

[0224] As another example, in the NET4Data or DAM service, the PF entity can receive sensed data from a sensor and cache the received sensed data in local memory, for example, for further use of the sensed data.

[0225] According to one aspect, the PF sublayer through one or more PF entities can support data transmission operations performed by data transmission components 706 and 716. In some aspects, functions related to data transmission can include sequence numbering and addition or deletion of the PF header.

[0226] In some aspects, when receiving a PF SDU from an upper layer or another PF entity (e.g., from an Rx-PF entity residing in the same node 701), the Tx-PF entity 702 may store the received PF SDU in a receive buffer. In some aspects, the Tx-PF entity may process the received PF SDU. In some aspects, the Tx-PF entity may also construct a corresponding PF PDU. In some aspects, the Tx-PF entity may also perform sequence numbering to set the PF SN. In some aspects, the Tx-PF entity may also submit the PF PDU to the lower layer in sequence. The PF PDU may be used to transport one or more of the following: a PF header and a payload encapsulating user plane data (i.e., the received PF SDU or the processed PF SDU). In some aspects, the PF SN may be included in the PF header.

[0227] According to some aspects, when receiving a PF PDU from the lower layer, the Rx-PF entity 712 may remove the PF header and retrieve the PF SDU. In some aspects, the Rx-PF entity 712 may also store the resulting PF SDU in a receive buffer. The Rx-PF entity 712 may also process the resulting PF SDU and transmit the resulting PF SDU or the processed PF SDU to the upper layer or another PF entity (e.g., transmit to a Tx-PF entity residing in the same node 711) in sequence.

[0228] In some aspects, the Tx-PF entity 702 may add packet routing information to the header of the PF PDU. In some aspects, at the Rx-PF entity 712, the routing information may be retained in the header of the PF SDU for the routing module to determine a routing action, e.g., determine whether to submit the packet to the upper layer or another Tx-PF entity.

[0229] According to one aspect, the PF sublayer may also support routing 710 through one or more PF entities. In some aspects, the Tx-PF entity 702 may add routing information to a PF sublayer packet (e.g., add to the header of the PF PDU) to help the Rx-PF entity of the peer node determine a routing action, i.e., determine whether the processed data (e.g., the originally retrieved SDU or the processed SDU) should be submitted to the upper layer or another PF entity.

[0230] According to one aspect, the routing information may be configured to the Tx-PF entity through the control plane (e.g., through an XC controller).

[0231] In some aspects, the routing information can be generated by the Tx-PF entity 702 itself based on the processing result (e.g., generated by the data processing component 705 of the Tx-PF entity). For example, if the processing result does not meet the required data processing disposal parameters (e.g., the accuracy level or privacy level of the AI model) or the AI model does not converge (e.g., in federated learning or generative adversarial network training), then the Tx-PF entity 702 may need the collaboration of peer nodes to continue with one or more further rounds of data processing. Then, the Tx-PF entity 702 can generate the routing information (e.g., the data processing component 705 of the Tx-PF entity can generate the routing information) and add the routing information to the PF sublayer message (e.g., add it to the header of the PF PDU) to notify or indicate to the peer node that continuous data processing is required in the peer node, and submit the processing result to the PF sublayer and send it back to the sending PF entity instead of submitting it to the upper layer.

[0232] In some aspects, the Rx-PF entity 712 can decide on the routing action based on the routing information. The Rx-PF entity 712 can decide whether the processed data (e.g., the originally retrieved SDU or the processed SDU) should be submitted to the upper layer or to another PF entity (e.g., the sending PF entity residing in the same node 711).

[0233] According to one aspect, the routing information can be configured in the Rx-PF entity 712 via the control plane (e.g., via the XC controller). In some aspects, the routing information can be included in the PF sublayer message by the peer Tx-PF entity that adds the routing information (e.g., in the header of the PF PDU).

[0234] In some aspects, the routing information can be generated by the Rx-PF entity 712 itself based on the processing result (e.g., generated by the data processing component 715 of the Rx-PF entity). In some aspects, if the processing result does not meet the required data processing disposal parameters (e.g., the accuracy level or privacy level of the AI model) or the AI model has not converged (e.g., in federated learning or generative adversarial network training), then the Rx-PF entity 712 may need the collaboration of peer nodes to continue with several rounds of data processing. Then, the Rx-PF entity 712 can generate the routing information (via the data processing component 715) and notify the routing component 717 to submit the processing result to the PF sublayer instead of submitting it to the upper layer.

[0235] In some aspects, the Rx-PF entity 712 can use the routing information to determine the address of the next-hop node.

[0236] While in some aspects, the PF sublayer (and the corresponding implementations of one or more PF entities and the PF sublayer) can be described as being deployed between the SDAP sublayer and the PDCP sublayer, the PF sublayer is not limited to this deployment and can be deployed in any reasonable location. For example, the PF sublayer can be deployed between the PDCP and the RLC sublayers, between the RLC and the MAC sublayers, between the MAC and the PHY sublayers, above the SDAP sublayer, above the PDU layer, above the GPRS tunneling protocol for the user plane (GTP-U) layer of the user plane, above the user datagram protocol (UDP) layer, above the internet protocol (IP) layer, above the quick UDP internet connections (QUIC) layer, or deployed within any one of the following: the PDU layer, the SDAP sublayer, the PDCP sublayer, the RLC sublayer, the MAC sublayer, the PHY layer, the GTP-U layer, the DUP layer, the IP layer, and the QUIC layer.

[0237] The order of participation of the different functions of the PF entity (whether it is the Tx-PF entity 702 or the Rx-PF entity 712), which are performed by different components such as the data buffer components 704 and 714, the data processing components 705 and 715, the routing components 707 and 717, and the data transmission components 706 and 716, is not limited to the figures shown. Any reasonable order of one or more operations performed by one or more components in the PF entity can fall within the scope of an aspect of the present invention.

[0238] According to one aspect, the order of participation of one or more operations performed by one or more components in the PF entity can be flexibly adjusted. For example, the order of operations involved in determining whether a retrieved SDU (i.e., the retrieved SDU processed by the data processing component 715) should be processed in the Rx-PF entity 712 before being forwarded to the sending PF entity residing in the same node 711 can be flexibly adjusted. Figure 8 An embodiment of another sequence of different components of the Rx-PF entity 812 in the PF sublayer provided by the present invention is shown.

[0239] Figure 8FIG. 0 shows another functional view of the PF sublayer provided by one aspect. As shown, similar to the PF sublayer 700, the PF sublayer 800 may include one or more PF entities (Tx-PF entity 802 and Rx-PF entity 812). The Tx-PF entity 802 may have a participation order similar to that of one or more PF entity components of the Tx-PF entity 702 of the PF sublayer 700. The Tx-PF entity 802 may include one or more of a data buffer component 804, a data processing component 805, a routing component 807, and a data transmission component 806. As shown, the Rx-PF entity 812 may have a different participation order of one or more components compared to the participation order of one or more components in the Rx-PF entity 712 (of the PF sublayer 700). For example, the Rx-PF entity 712 may determine data routing through the routing component 717 after the data buffer component 714 performs a data buffering operation, while the Rx-PF entity 812 may determine data routing through the routing component 817 without first performing a data buffering operation (by the data buffer component 814). Another example of the different participation orders at the Rx-PF entity 812 and the Rx-PF entity 712 may involve data transmission operations. At the Rx-PF entity 812, the data transmission operation (performed by the data transmission 806) may occur after the routing component 817 makes a routing decision, while at the Rx-PF entity 712, the data transmission operation performed by the data transmission component 717 is performed before (e.g., by the routing component 717) making a routing decision.

[0240] Figure 9 FIG. 4 shows an embodiment of a data path in the PF sublayer provided by one aspect of the present invention. The PF sublayer 900 at the UE may include a Tx-PF entity 902 and an Rx-PF entity 911 residing in the same node (e.g., the UE). The PF sublayer 940 at the RAN may include a Tx-PF entity 942 and an Rx-PF entity 951 residing in the same node (e.g., the RAN node).

[0241] According to one aspect, the UE Rx-PF entity 911 may send data 922 (which may be processed data) to the UE Tx-PF entity 902 (e.g., to the data buffer component 904 of the UE Tx-PF entity 902). Similarly, the RAN Rx-PF entity 951 may send data 943 (which may be processed data) to the RAN Tx-PF entity 942 (e.g., to the data buffer component 944 of the RAN Tx-PF entity 942).

[0242] In some aspects, the UE Tx-PF entity 902 may receive data 924 from the UE upper layer 920, and process the data 924 to obtain processed data 926. The UE Tx-PF entity 902 may also send the processed data 926 to the RAN Rx-PF entity 951 of the RAN PF sublayer 940 via the radio interface 930.

[0243] In some aspects, the UE Tx-PF 902 may send the data 928 (which may be processed data) cached at the data buffer component 904 to the RAN PF sublayer 940 (RAN Rx-PF 951) via the radio interface 930. In some aspects, the RAN Rx-PF entity 951 may send the data 932 (which may be processed data) to one or both of the RAN upper layer 960 and the RAN Tx-PF entity 942. In some aspects, the RAN Tx-PF entity 942 may send the data 934 (e.g., the data stored at the data buffer component 944) to the UE PF sublayer 900 (e.g., to the UE Rx-PF 911) via the radio interface 930.

[0244] In some aspects, the UE Tx-PF entity 902 can receive data 924 from the UE upper layer 920 and perform processing on the data through, for example, the data processing component 905 to obtain processed data 926. Then, the processed data 926 can be sent to the RAN Rx-PF entity 951 of the RAN PF sublayer 940 through the radio interface 930. In some aspects, the RAN Rx-PF entity 951 of the RAN PF sublayer 940 can perform further processing on the processed data 926 through, for example, the data processing component 955 to obtain further processed data 943. The RAN Rx-PF entity 951 of the RAN PF sublayer 940 can also send the further processed data 943 to the RAN Tx-PF entity 942 of the RAN PF sublayer 940. In some aspects, the RAN Tx-PF entity 942 of the RAN PF sublayer 940 can also process the processed data 943 through the data processing component 945 to obtain further processed data 934. The RAN Tx-PF entity 942 of the RAN PF sublayer 940 can also send the processed data 934 to the UE PF sublayer 900 (e.g., to the UE Rx-PF 911) through the radio interface 930. In some aspects, the UE Rx-PF entity 911 of the UE PF sublayer 900 can also process the received processed data 934 through the data processing component 915 to obtain further processed data 922. In some aspects, the UE Rx-PF entity 911 of the UE PF sublayer 900 can also send the processed data 922 to the UE Tx-PF entity 902 (e.g., the data buffer 904) of the UE PF sublayer 900. The UE Tx-PF entity 902 of the UE PF sublayer 900 can also process the received processed data 922 through the data processing component 905 to obtain processed data 928. In some aspects, the UE Tx-PF entity 902 of the UE PF sublayer 900 can also send the processed data 928 to the RAN Rx-PF entity 951 of the RAN PF sublayer 940 through the radio interface 930. In some aspects, the RAN Rx-PF entity 951 of the RAN PF sublayer 940 can also process the processed data 928 through the data processing component 955 to obtain processed data 932. The RAN Rx-PF entity 951 of the RAN PF sublayer 940 can also send the processed data 932 to the RAN upper layer 960.

[0245] In some aspects, a PF entity at the UE, e.g., the UE Tx-PF entity 902, can receive raw data 924 from a protocol layer of the UE and perform processing on the raw data 924 through, e.g., a data processing component 905 to obtain processed data 926. The protocol layer of the UE can be one of the following: a network sensing layer, a PF sublayer, a PHY layer, an RLC sublayer, a MAC sublayer, a PDCP sublayer, an SDAP sublayer, a PDU layer, and a reconfigurable intelligent surface (RIS) layer. In some aspects, the raw data 924 can be sensing data, RIS data, Internet of Things data, positioning data, or other types of data collected (e.g., collected from one or more RAN nodes or CNFs) by the protocol layer of the UE. Then, the processed data 926 can be sent to the RAN Rx-PF entity 951 of the RAN PF sublayer 940 through a radio interface 930. In some aspects, the RAN Rx-PF entity 951 of the RAN PF sublayer 940 can perform further processing on the processed data 926 through, e.g., a data processing component 955 to obtain further processed data 943. The RAN Rx-PF entity 951 of the RAN PF sublayer 940 can also send the further processed data 943 to the RAN Tx-PF entity 942 of the RAN PF sublayer 940. In some aspects, the RAN Tx-PF entity 942 of the RAN PF sublayer 940 can also process the processed data 943 through a data processing component 945 to obtain further processed data 934. The RAN Tx-PF entity 942 of the RAN PF sublayer 940 can also send the processed data 934 to the UE PF sublayer 900 (e.g., to the UE Rx-PF 911) through the radio interface 930. In some aspects, the UE Rx-PF entity 911 of the UE PF sublayer 900 can also process the received processed data 934 through a data processing component 915 to obtain further processed data 922. In some aspects, the UE Rx-PF entity 911 of the UE PF sublayer 900 can also send the processed data 922 to the UE Tx-PF entity 902 (e.g., a data buffer 904) of the UE PF sublayer 900. The UE Tx-PF entity 902 of the UE PF sublayer 900 can also process the received processed data 922 through a data processing component 905 to obtain processed data 928. In some aspects, the UE Tx-PF entity 902 of the UE PF sublayer 900 can also send the processed data 928 to the RAN Rx-PF entity 951 of the RAN PF sublayer 940 through the radio interface 930.In some aspects, the RAN Rx-PF entity 951 of the RAN PF sublayer 940 may also process the processed data 928 through the data processing component 955 to obtain the processed data 932. The RAN Rx-PF entity 951 of the RAN PF sublayer 940 may also send the processed data 932 to the RAN upper layer 960.

[0246] In some aspects, the process can start from the PF entity at the RAN. For example, the RAN Tx-PF entity 942 of the RAN PF sublayer 940 can receive the raw data 943 from the protocol layer of the RAN. The protocol layer of the RAN can be one of the following: network sensing layer, PF sublayer, PHY layer, RLC sublayer, MAC sublayer, PDCP sublayer, SDAP sublayer, PDU layer, reconfigurable intelligent surface (RIS) layer, GTP-U layer, QUIC layer, SRv6 layer, UDP layer, and hypertext transfer protocol (HTTP) layer. In some aspects, the raw data 943 can be sensing data, RIS data, Internet of Things data, positioning data, or other types of data collected by the protocol layer of the RAN (e.g., collected from one or more UEs or CNFs). In some aspects, the RAN Tx-PF entity 942 of the RAN PF sublayer 940 can also process the raw data 943 through the data processing component 945 to obtain the further processed data 934. The RAN Tx-PF entity 942 of the RAN PF sublayer 940 can also send the processed data 934 to the UE PF sublayer 900 (e.g., to the UE Rx-PF 911) through the wireless interface 930. In some aspects, the UE Rx-PF entity 911 of the UE PF sublayer 900 can also process the received processed data 934 through the data processing component 915 to obtain the further processed data 922. In some aspects, the UE Rx-PF entity 911 of the UE PF sublayer 900 can also send the processed data 922 to the UE Tx-PF entity 902 (e.g., the data buffer 904) of the UE PF sublayer 900. The UE Tx-PF entity 902 of the UE PF sublayer 900 can also process the received processed data 922 through the data processing component 905 to obtain the processed data 928. In some aspects, the UE Tx-PF entity 902 of the UE PF sublayer 900 can also send the processed data 928 to the RAN Rx-PF entity 951 of the RAN PF sublayer 940 through the wireless interface 930. In some aspects, the RAN Rx-PF entity 951 of the RAN PF sublayer 940 can also process the processed data 928 through the data processing component 955 to obtain the processed data 932. The RAN Rx-PF entity 951 of the RAN PF sublayer 940 can also send the processed data 932 to the RAN upper layer 960.

[0247] Figure 10 FIG. shows a sequence diagram of the process 1022 of the XaaS task of the PF sublayer provided by an embodiment of the present invention. Refer to Figure 10, on the UE side, one or more upper layers 1004 and the UE PF sublayer (Rx-PF entity 1006 and Tx-PF entity 1008) can be deployed. Similarly, on the RAN side, the upper layer 1014 and the RAN PF sublayer (Tx-PF entity 1018 and Rx-PF entity 1016) can be deployed. In some aspects, Figure 10 the UE PF sublayer and the RAN PF sublayer can be similar to Figure 9 the UE PF sublayer 900 and the RAN PF sublayer 940.

[0248] According to one aspect, the XaaS task can involve the receiving side (e.g., RAN node 1010) sending the processed data received from the sending side (e.g., UE 1002) back to the sending side instead of forwarding it to the upper layer (e.g., RAN SDAP, PDU layer, or CN). For example, the RX-PF entity 1016 residing in the RAN node 1010 can receive one or more PF PDUs from the Tx-PF entity 1008 residing in the UE 1002. The Rx-PF entity 1016 can retrieve and process some or all of the one or more PF SDUs to obtain the processed PF SDU. In one aspect, according to process 1022, it may be necessary to send the processed PF SDU in the RAN node 1010 back to the UE 1002 instead of the upper layer (e.g., RAN SDAP, PDU layer, or CN).

[0249] According to one aspect, process 1022 can involve forwarding the processed data (e.g., processed PF SDU) of the Rx-PF entity 1016 to the Tx-PF entity 1018 residing in the same node (e.g., RAN node 1010). The Tx-PF entity 1018 can transmit the processed data encapsulated in one or more PF PDUs to the Rx-PF entity 1006 residing in the peer node (e.g., UE 1002) through the lower layer. In one aspect, process 1022 can be executed based on the configuration of the associated XC, and the configuration indicates that the XaaS associated with process 1022 can terminate at RAN-PF, e.g., indicating that only the UE and the RAN rather than the CN may be involved in the XaaS task.

[0250] According to one aspect, process 1022 can involve the PF sublayers at the UE 1002, RAN node 1010, and CN 1020. Process 1022 can include: the UE upper layer 1004 (e.g., SDAP sublayer, PDU layer) transmitting or sending (1024) one or more PF SDUs of XaaS to the Tx-PF entity 1008 (e.g., UE Tx-PF 1008) residing in the UE 1002.

[0251] In one aspect, one or more PF SDUs can be used for one or more of the following: AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, junk data filtering, data feature engineering, etc.

[0252] Procedure 1022 may further include: The UE Tx-PF entity 1008 constructs (1026) one or more PF PDUs based on the received one or more PF SDUs. In some aspects, constructing one or more PF PDUs may include: The UE Tx-PF entity 1008 performing one or more of the following: data caching, data processing, PF header addition, and data sequence numbering.

[0253] In some aspects, one or more methods can be used to perform data processing, and the methods include: AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, junk data filtering, or data feature engineering, etc.

[0254] In some aspects, procedure 1022 may further include: The UE Tx-PF entity 1008 sends (1028) the constructed one or more PF PDUs to the peer RAN Rx-PF entity 1016 through a lower layer such as the XaaS bearer 510.

[0255] In some aspects, procedure 1022 may further include: The RAN Rx-PF entity 1016 retrieves (1030) one or more PF SDUs from the received one or more PF PDUs. In some aspects, the RAN Rx-PF entity 1016 may also process the retrieved one or more PF SDUs. The RAN Rx-PF entity 1016 may perform one or more of the following: PF header deletion, SN-based reordering, data caching, and data processing.

[0256] In some aspects, data processing can be performed based on one or more methods: AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, junk data filtering, data feature engineering, etc.

[0257] In some aspects, if the CN 1020 needs to participate in the XaaS, procedure 1022 may include: The RAN Rx-PF entity 1016 forwards (1032) the retrieved or processed one or more PF SDUs to the Tx-PF entity 1018 (RAN Tx-PF entity 1018) residing in the RAN.

[0258] In some aspects, if CN 1020 needs to participate in the XaaS task, process 1022 may include: the RAN Rx-PF entity 1016 submitting or sending (1034) one or more retrieved or processed PF SDUs to one or more RAN upper layers 1014 (e.g., the SDAP sublayer, the GTP-U layer, the UDP layer, the IP layer, the QUIC layer, or the PDU layer).

[0259] In some aspects, process 1022 may further include: one or more RAN upper layers 1014 transmitting or sending (1036) upper layer data encapsulating one or more PF SDUs to the CN (e.g., the UPF or PF deployed in the CN) via, for example, the XaaS QoS flow or the XaaS session tunnel between the RAN and the CN.

[0260] In some aspects, process 1022 may further include: CN 1020 using the PF SDU to perform data processing (1038). The data processing may be performed based on one or more methods: AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, useless data filtering, or data feature engineering, etc.

[0261] In some aspects, process 1022 may further include: CN 1020 transmitting or sending (1040) the processed data to the RAN upper layer 1014 (e.g., the SDAP sublayer, the GTP-U layer, the UDP layer, the IP layer, the QUIC layer, or the PDU layer) via, for example, the XaaS QoS flow or the XaaS session tunnel between the RAN and the CN. Then, the RAN upper layer 1014 may transmit or send (1042) one or more PF SDUs encapsulating the processed data of the CN to the RAN Tx-PF entity 1018.

[0262] In some aspects, process 1022 may further include: the RAN Tx-PF entity constructing (1044) one or more PFPDUs corresponding to the PF SDU. Constructing one or more PF PDUs may include: the RAN Tx-PF entity 1018 performing one or more of the following: data caching, data processing, PF header addition, and data sequence numbering.

[0263] In some aspects, the data processing may be performed based on one or more methods, including: AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, useless data filtering, or data feature engineering, etc.

[0264] In some aspects, process 1022 may further include: the RAN Tx-PF entity 1018 transmits or sends (1046) one or more constructed PF PDUs to the peer UE Rx-PF entity 1006 via a lower layer such as an XaaS bearer.

[0265] In some aspects, process 1022 may further include: the UE Rx-PF entity 1006 retrieves (048) one or more PF SDUs from the received one or more PF PDUs. In some aspects, the UE Rx-PF entity 1006 may also process one or more PF SUDs.

[0266] In some aspects, if the UE upper layer 1004 (e.g., the application layer) does not need to participate in the XaaS, i.e., when the data terminates at the UE PF sublayer, then process 1022 may further include: the UE Rx-PF 1006 forwards or sends (1050) the retrieved or processed PF SDU to the UE Tx-PF entity 1008.

[0267] In some aspects, if the UE upper layer (e.g., the application layer) needs to participate in the XaaS, i.e., when the data does not terminate at the PF sublayer, then process 1022 may further include: the UE Rx-PF entity 1006 submits or sends (1052) the retrieved or processed one or more PF SDUs to one or more UE upper layers 1004 (e.g., the SDAP sublayer, the PDU layer, or the application layer).

[0268] In some aspects, process 1022 may further include: one or more UE upper layers (e.g., the application layer) 1004 perform data processing (1054) using one or more PF SDUs. The data processing may be performed based on one or more methods, and the one or more methods include AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, useless data filtering, data feature engineering, etc.

[0269] In some aspects, process 1022 may further include: one or more UE upper layers send (1056) one or more PF SDUs encapsulating the processed data of the UE to the UE Tx-PF entity 1008.

[0270] In some aspects, process 1022 may further include: the UE Tx-PF entity 1008 constructs (1058) one or more PF PDUs corresponding to one or more PF SDUs. To construct one or more PF PDUs, the RAN Tx-PF entity 1008 may perform one or more of the following: data caching, data processing, PF header addition, and data sequence numbering.

[0271] In some aspects, data processing can be performed based on one or more methods, which include AI training, AI inference, data analysis, data privacy protection, data cleaning, data normalization, useless data filtering, data feature engineering, etc.

[0272] In some aspects, process 1022 may further include: the UE Tx-PF entity 1008 sending one or more constructed PF PDUs to the peer RAN Tx-PF entity 1016 through the lower layer of, for example, XaaS bearer.

[0273] In some aspects, process 1022 may further include one or more repeated operations until the XaaS task is completed. The one or more operations may include the operations of references 1030, 1032, 1034, 1036, 1038, 1040, 1042, 1044, 1046, 1048, 1050, 1052, 1054, 1056, 1058, and 1060.

[0274] The workflow or process 1022 can be used to perform XaaS tasks. According to one aspect, the workflow 1022 can be used to perform XaaS tasks associated with the NET4AI service.

[0275] According to one aspect, one or more UEs (e.g., UE 1002) can act as participants in federated learning, and the RAN (e.g., RAN node 1010) can act as an aggregator for federated learning. In one aspect, referring to Figure 10 , the UE upper layer (e.g., SDAP sublayer, PDU layer) can transmit (1024) one or more PF SDUs encapsulating local private data to the UE Tx-PF entity 1008. The UE Tx-PF entity 1008 can use the private data to train the local model when constructing (1026) one or more PF PDUs, and then encapsulate the trained local model parameters into the payloads of one or more PF PDUs. Then, the UE Tx-PF entity 1008 can transmit or send (1028) one or more PF PDUs to the RAN Rx-PF entity 1016 through the lower layer of, for example, XaaS bearer.

[0276] In some aspects, the RAN Rx-PF entity 1016 can retrieve (1030) the local model parameters of the UE from the one or more received PF PDUs. The RAN Rx-PF entity 1016 can also aggregate one or more local parameters of multiple UEs and obtain the global model parameters.

[0277] In some aspects, the RAN Rx-PF entity 1016 may also forward (1032) one or more PF SDUs including global model parameters to the RAN Tx-PF entity 1018.

[0278] In some aspects, the RAN Tx-PF entity 1016 may submit or send (1034) one or more PF SDUs including local parameters of the UE to the RAN upper layer 1014.

[0279] 1036. Then, the RAN upper layer may transmit (1036) one or more PF SDUs to the CN 1020, e.g., the UPF or PF deployed in the CN. The CN 1020 may aggregate (1038) the local parameters of multiple UEs to obtain global model parameters. The CN1020 may also transmit (1040) the global model parameters to the RAN upper layer 1014 (e.g., the SDAP sublayer, the GTP-U layer) via, for example, an XaaS QoS flow or an XaaS session tunnel. Then, the RAN upper layer 1014 may send (1042) one or more PF SDUs encapsulating the global model parameters to the RAN Tx-PF 1018.

[0280] In some aspects, the RAN Tx-PF entity 1018 may construct (1044) one or more PF PDUs corresponding to one or more PF SDUs including global model parameters. The RAN Tx-PF entity 1018 may also add one or more PF PDU headers and SNs.

[0281] In some aspects, the RAN Tx-PF entity 1018 may transmit or send (1046) one or more constructed PF PDUs including global model parameters to the peer UE Rx-PF entity 1006 via, for example, the lower layer of an XaaS bearer.

[0282] The UE Rx-PF entity 1006 may retrieve (1048) the global model parameters from the received one or more PF PDUs. In some aspects, the UE Rx-PF entity 1006 may also use the received latest global model parameters and local private data to train a local model. The local private data may be cached at the Rx-PF entity 1006. In some aspects, the local private data may be a part of the private data previously received (e.g., received (1024) from the upper layer 1004) or received from the upper layer 1004 at some moment after the reception (1024).

[0283] In some aspects, the UE Rx-PF entity 1006 may forward (1050) one or more PF SDUs including the latest trained local model parameters to the Tx-PF entity 1008 resident in the UE.

[0284] In some aspects, the UE Rx-PF entity 1006 may submit or send (1052) the retrieved global model parameters to the UE upper layer 1004. In one aspect, the UE upper layer 1004 (e.g., the application layer) may use the received latest global model parameters and local private data to train (1054) the local model. The UE upper layer 1004 may also send (1056) one or more PF SDUs including the latest trained local model parameters to the UE Tx-PF entity 1008.

[0285] In some aspects, the UE Tx-PF entity 1008 may construct (1058) one or more PFPDUs corresponding to one or more PF SDUs. The UE Tx-PF entity 1008 may also add a PF PDU header and SN. The UE Tx-PF entity 1008 may also send (1060) the constructed one or more PF PDUs including the latest local model parameters to the peer RAN Rx-PF entity 1016 through the lower layer of, for example, the XaaS bearer.

[0286] In some aspects, one or more operations may be performed until the federated learning model training task is completed. The one or more operations may include the operations of reference 1030, 1032, 1034, 1036, 1038, 1040, 1042, 1044, 1046, 1048, 1050, 1052, 1054, 1056, 1058, and 1060.

[0287] According to one aspect, the workflow 1022 may be used to perform XaaS tasks associated with the DAM service. For example, in the DAM service, the UE (e.g., UE 1002) may act as a data source and report data to be collected to the RAN (e.g., RAN node 1010). The DAM service may include one or more of the following: protection of data privacy (e.g., location information); and cleaning, filtering, or normalization of non-directly available, useless, and redundant data.

[0288] In one aspect, the UE and the RAN may cooperate to protect the privacy of the reported data (the identification information of the UE) based on one or more methods (e.g., generative adversarial network (GAN)).

[0289] In one aspect, performing the XaaS tasks associated with the DAM service may include: the UE upper layer 1004 (e.g., the SDAP sublayer, the PDU layer) feeding or sending (1024) one or more PF SDUs encapsulating the private data to the UE Tx-PF entity 1008.

[0290] The UE Tx-PF entity 1008 can use the PF SDU to train the adversarial network. In one aspect, the UE Tx-PF entity 1008 can construct (1026) one or more PF PDUs and encapsulate the output of the adversarial model into the payload of one or more PF PDUs.

[0291] The UE Tx-PF entity 1008 can transmit or send (1028) one or more PF PDUs to the RAN Rx-PF entity 1016 through the lower layer of, for example, XaaS bearer. The RAN Rx-PF entity 1016 can retrieve (1030) the output of the adversarial model from the received one or more PF PDUs. Then, the RAN Rx-PF entity 1016 can use the retrieved output of the adversarial model to train the generative model.

[0292] In some aspects, the RAN Rx-PF entity 1016 can forward (1032) one or more PF SDUs including the output of the generative model to the RAN Tx-PF entity 1018.

[0293] In some aspects, the RAN Rx-PF entity 1016 can submit (1034) one or more PF SUDs including the output of the adversarial model to the RAN upper layer 1014. The RAN upper layer 1014 can transmit (1036) one or more PF SDUs to the CN 1020, for example, the UPF or PF deployed in the CN. In some aspects, the CN 1020 can use (1038) the output of the adversarial model to train the generative model. The CN 1020 can also transmit or send (1040) the output of the generative model to the RAN upper layer 1014 (e.g., the SDAP sublayer, the GTP-U layer). In one aspect, the RAN upper layer 1014 can send one or more PF SDUs encapsulating the output of the generative model to the RAN Tx-PF entity 1018.

[0294] The RAN Tx-PF entity 1018 can construct (1044) one or more PF PDUs corresponding to one or more PF SDUs including the output of the generative model. The RAN Tx-PF entity 1018 can also add a PF PDU header and an SN. The RAN Tx-PF entity 1018 can also transmit (1046) the constructed one or more PF PDUs including the output of the generative model to the peer UE Rx-PF entity 1006 through the lower layer of, for example, XaaS bearer.

[0295] In one aspect, the UE Rx-PF entity 1006 may retrieve (1048) the output of the generation model from one or more received PF PDUs. The UE Rx-PF entity 1006 may also use the most recently received output of the generation model and local private data to train a local adversarial model. The local private data may be cached at the Rx-PF entity 1006. In some aspects, the local private data may be a portion of private data previously received (e.g., from the upper layer 1004 at (1024)) or received from the upper layer 1004 at some point after the reception (1024).

[0296] In some aspects, the UE Rx-PF 1006 may forward (1050) one or more PF SDUs including the most recently received output of the adversarial model to the UE Tx-PF entity 1008. In some aspects, the UE Rx-PF entity 1006 may submit or send (1052) the output of the generation model to the UE upper layer 1004.

[0297] In some aspects, the UE upper layer 1004 (e.g., the application layer) may use the most recently received output of the generation model and local private data to train (1054) the adversarial model. In some aspects, the UE upper layer 1004 may also send (1056) one or more PF SDUs including the most recently received output of the adversarial model to the UE Tx-PF entity 1008.

[0298] The UE Tx-PF entity 1008 may construct (1058) one or more PF PDUs corresponding to one or more PF SDUs. The UE Tx-PF entity 1008 may also add a PF PDU header and SN. The UE Tx-PF entity 1008 may also send (1060) the constructed one or more PF PDUs including the most recently received output of the adversarial model to the peer RAN Rx-PF entity 1016 via, for example, the lower layer of the XaaS bearer.

[0299] In some aspects, one or more operations may be performed until the GAN training task is completed. The one or more operations may include the operations of reference 1030, 1032, 1034, 1036, 1038, 1040, 1042, 1044, 1046, 1048, 1050, 1052, 1054, 1056, 1058, and 1060.

[0300] In some aspects, after training is completed, the trained generative model at the RAN Rx-PF entity 1016 can output generated data that may have the same attributes as the original UE private data. Thereafter, in some aspects, the RAN Rx-PF entity 1016 can forward one or more PF SDUs to the RAN upper layer 1014, where the one or more PF SDUs include the latest output of the trained adversarial model (i.e., the generated data) or the parameters of the trained generative model. In some aspects, the RAN upper layer 1014 can transmit the generated data or the generative model to the CN 1020, e.g., a UPF or PF deployed in the CN.

[0301] In some aspects, the CN 1020 can be a data consumer that retains the generated data or the generative model for further use, e.g., for performing data analysis. As a data consumer, the CN 1020 can also expose the generated data or the generative model to other data consumers, such as third parties, for further use. In this way, the generated data, or the generative model, rather than the original UE private data, can be exposed to data consumers, thereby protecting the privacy of the UE.

[0302] According to one aspect, the workflow 1022 can be used to perform XaaS associated with the DAM service. In one aspect, the UE upper layer 1004 (e.g., the SDAP sublayer, the PDU layer) can transmit (1024) one or more PF SDUs encapsulating data (to be reported to the RAN) to the UE Tx-PF entity 1008.

[0303] The UE Tx-PF entity 1008 can clean, normalize, or filter non-directly available, useless, and redundant data included in the one or more PF SDUs, e.g., based on pre-configured data processing rules. In some aspects, the UE Tx-PF entity 1008 can also provide a privacy protection level to the information included in the one or more PF SDUs (e.g., by deleting or replacing identifying information from the information). The UE Tx-PF entity 1008 can also construct (1026) one or more PF PDUs and encapsulate the processed data into the payloads of the one or more PF PDUs.

[0304] In some aspects, the UE Tx-PF entity 1008 may transmit or send (1028) one or more PF PDUs to the RAN Rx-PF entity 1016 via a lower layer such as an XaaS bearer. The RAN Rx-PF entity 1016 may retrieve (1030) one or more PF SDUs. The RAN Rx-PF entity 1016 may also clean, normalize, or filter non-directly available, useless, and redundant data included in one or more retrieved PF SDUs. The RAN Rx-PF entity 1016 may also perform feature engineering, for example, based on pre-configured data processing rules. The RAN Rx-PF entity 1016 may also provide a privacy protection level to the information included in one or more PF SDUs (e.g., by deleting or replacing identity information from the information). When providing the privacy protection level, the RAN Rx-PF entity 1016 may use one or more methods of privacy protection. For example, the RAN Rx-PF entity may cache one or more PF SDUs from K UEs and use the K-anonymity method to protect data privacy.

[0305] In some aspects, the RAN Rx-PF entity may forward (1034) one or more PF SDUs including the processed data to the RAN upper layer 1014. The RAN upper layer 1014 may transmit (1036) the processed data to the CN 1020 (e.g., a UPF or PF deployed in the CN) via, for example, an XaaS QoS flow or an XaaS session tunnel. The CN 1020 may be a data consumer that retains the processed data, for example, for performing data analysis. In some aspects, the CN 1020 may also expose the data to other data consumers, such as third parties, for further use.

[0306] Figure 11 An example of a structural view of the PF sublayer provided by one aspect of the present invention is shown. The structural view 1100 is a possible structure of the PF sublayer and is not limited to this implementation, as can be understood by those skilled in the art.

[0307] The PF sublayer 1102 may be deployed between the SDAP sublayer 1104 and the PDCP sublayer 1106. The PDCP sublayer 1106 may provide a radio bearer 1108 to the PF sublayer 1102. The PF sublayer 1102 may provide an XaaS bearer 1110 to the SDAP sublayer 1104.

[0308] The SDAP sublayer 1104 may deploy one or more SDAP entities 1112 and 1114. The PF sublayer 1102 may deploy one or more of the PF entities 1116 and 1118. The PDCP sublayer 1106 may deploy one or more PDCP entities 1120, 1122, 1124, 1126, and 1128.

[0309] According to one aspect, the XaaS session 1130 may include different XaaS QoS flows. Each XaaS session 1130 may be configured with an SDAP entity (e.g., SDAP entity 1112). The SDAP entity may map the data included in the XaaS QoS flow to one or more PF entities. For example, an SDAP entity 1112 may map the data included in the XaaS QoS flow to two PF entities 1116 and 1118. The PF entity may also map the data to one or more PDCP entities. For example, PF entity 1116 may map the data to two different PDCP entities 1120 and 1122, and PF entity 1118 may map the data to a PDCP entity 11124.

[0310] According to one aspect, the SDAP entity 1112 may support the XaaS session 1130. In some aspects, the SDAP entity 1114 may support the 5G PDU session connection 1132.

[0311] In one aspect, the 5G PDU session connection 1132 may not be configured with a PF entity. For example, the SDAP entity 1114 (for the 5G PDU session connection 1132) may be directly connected to the PDCP sublayer 1106 (one or more PDCP entities). In one aspect, the SDAP entity 1114 may map the 5G PDU session connection data to three PDCP entities 1124, 1126, and 1128.

[0312] In some aspects, the PDCP entity 1124 may carry data from both the XaaS session 1130 and the 5G PDU session connection 1132. Therefore, the PDCP entity 1124 may be reused by the XaaS session 1130 and the 5G PDU session 1132.

[0313] According to one aspect, from a structural perspective, the PF sublayer 1102 may be an anchor point for one or more XaaS bearers 1110. The functions of one or more PF entities 1116 and 1118 in the PF sublayer 1102 may be configured, for example, by the XC sublayer via XSB, by RRC, or by dedicated XaaS signaling messages.

[0314] In one aspect, Figure 11 An architecture for the downlink and uplink associated with XaaS and 5G PDU session connection services is described.

[0315] According to one aspect, for XaaS, the PDCP sublayer 1106 may provide one or more radio bearers to the PF sublayer 1102. In some aspects, the PF sublayer 1102 may provide the XaaS bearer 1110 to the SDAP sublayer 1104. The SDAP sublayer may provide the XaaS QoS flow of the XaaS session to the CN.

[0316] In some aspects, if the traffic granularity of the XaaS QoS flow or the XaaS session is the same as that of the XaaS bearer, the SDAP sublayer 1104 may not be configured (or configured without a DL SDAP header or a UL SDAP header). That is, the XaaS QoS flow or the XaaS session is in a one-to-one mapping with the XaaS bearer. According to one aspect, the XaaS QoS flow or the XaaS session may be mapped one-to-one to the XaaS bearer. For example, an XaaS session or an XaaS QoS flow may be established between the UE and the CN PF, rather than between the UE and the DN. The CN PF within the network itself may generate the XaaS QoS flow data traffic based on the granularity of the XaaS bearer. Therefore, in some aspects, the data traffic granularity may be aligned between the CN PF and the RAN, and the XaaS session or the XaaS QoS flow may be mapped one-to-one to the XaaS bearer without the SDAP sublayer.

[0317] In some aspects, if XaaS only involves the UE and the RAN, the SDAP sublayer 1104 may not be configured (or may be configured without a DL SDAP header or a UL SDAP header). For example, in an XaaS task, the UP may only involve the UE and the RAN, and the CN does not need to participate in the XaaS task. The XaaS data may only be processed between the UE and the RAN, initiated or terminated at the RAN-PF. Then the XaaS data does not need to be received from the CN or the upper layer of the UE (e.g., the application layer) or forwarded to the CN or the UE, so there may be no need for data mapping between the CN and the RAN. Only an air interface may need to be established. Therefore, there may be no need to configure the SDAP sublayer 1104. In this case, there may only be an XaaS bearer between the UE and the RAN, without an XaaS QoS flow.

[0318] In some aspects, if XaaS is only processed in the RAN and the CN, the SDAP sublayer 1104 may not be configured (or may be configured without a DL SDAP header or a UL SDAP header). For example, the PF sublayer on the RAN and the CN tunnel between the RAN and the CN may be configured, while the RAN SDAP sublayer and other wireless L2 sublayers and the PHY layer may not be configured.

[0319] In some aspects, for connection services, the PDCP sublayer 1106 may provide radio bearers 1108 to the SDAP sublayer 1104. In some aspects, for connection services, the PDCP sublayer 1106 may provide radio bearers to the PF sublayer 1102, and the PF sublayer 1102 may provide XaaS bearers 1110 to the SDAP sublayer 1104, but the PF sublayer 1102 may operate in transparent mode (TM), that is, the PF PDUs at the PF layer are configured to contain only data fields and no headers. The data passes through the PF layer transparently without any processing. In some aspects, for connection services, the SDAP sublayer 1104 may provide connection QoS flows of the PDU session to the CN.

[0320] In some aspects, a radio bearer (e.g., DRB) may transmit only XaaS data, only connection service data, or both XaaS data and connection data. That is, for XaaS, only one or more PF entities of the PF sublayer, for connection services, only one or more SDAP entities of the SDAP sublayer, or both of the above may map data to the same PDCP entity in the PDCP sublayer.

[0321] In some aspects, as can be understood by those skilled in the art, for both XaaS and PDU connection services, the RLC sublayer may provide an RLC channel to the PDCP sublayer. In some aspects, for both XaaS and PDU connection services, the MAC sublayer may provide a logical channel to the RLC sublayer. In some aspects, for both XaaS and PDU connection services, the physical layer may provide a transport channel to the MAC sublayer. In some aspects, resources in the RLC sublayer, MAC sublayer, and physical layer (e.g., MAC entities, physical resource blocks) may be multiplexed by XaaS data and connection service data.

[0322] Figure 12 An embodiment of the data flow provided by one aspect of the present invention is shown. In one aspect, the CN may send one or more packets associated with XaaS (e.g., CN packet n 1202, CN packet n+1 1204, and CN packet n+2 1206).

[0323] The SDAP layer (through one or more SDAP entities) can receive CN packets and process them into SDAP SDUs. For example, the SDAP layer processes CN packet n 1202 into SDAP SDU 1212, CN packet n+1 1204 into SDAP SDU 1214, and CN packet n+2 1216 into SDAP SDU 1216. Then, the SDAP layer adds an SDAP packet header to each SDAP SDU and encapsulates an SDAP SDU and an SDAP packet header into an SDAP PDU. In some aspects, the SDAP PDU can contain only the SDAP SDU without the SDAP packet header.

[0324] The SDAP layer 1104 can send the SDAP PDU to the PF sublayer for further processing. The PF sublayer 1102 (through one or more PF entities) can process the SDAP SDU into a PF SDU. In one aspect, the PF sublayer can process the packets SDAP SDU 1212 (corresponding to CN packet n 1202) and SDAP SDU 1214 (corresponding to CN packet n+1 1204) into PF SDU 1218. The PF sublayer 1102 can also process the SDPA SDU 1216 (corresponding to CN packet n+2 1206) into PF SDU 1220. The PF sublayer 1102 can send the PF SDU to the PDCP sublayer 1106 for further processing. The PDCP sublayer 1106 (through one or more PDCP entities) can process the PF SDU into a PDCP SDU. The PDCP sublayer can process PF SDU 1218 into PDCP SDU 1222 and PF SDU 1220 into PDCP SDU 1224.

[0325] The PDCP sublayer 1106 can send the PDCP SDU to the RLC sublayer 1226, and the RLC sublayer 1226 further processes the PDCP SDUs 1222 and 1224 into RLC SDUs 1228 and 1230 respectively. In some aspects, one PDCP SDU can also be decoupled into multiple RLC SDUs (although not shown).

[0326] The RLC sublayer 1226 can send the RLC SDUs 1228 and 1230 to the MAC sublayer 1232, and the MAC sublayer 1232 processes the RLC SDUs 1228 and 1230 into MAC SDUs 1234 and 1236 respectively.

[0327] Reference Figure 12, a DN (e.g., a third party) can send one or more packets, such as IP packet m 1238, through radio bearer 1240. The IP packet m 1238 can be processed in the PDCP sublayer 1106 and encapsulated into a PDCP SDU 1242. The PDCP SDU 1242 can be further processed (e.g., encapsulated or decoupled) by the RLC sublayer 1226 into RLC SDUs 1244 and 1246. The RLC sublayer 1226 can send the RLC SDUs 1244 and 1246 to the MAC layer 1232. The MAC sublayer 1232 can process the RLC SDUs 1244 and 1246 into MAC SDUs 1248 and 1250, respectively.

[0328] Reference Figure 12 , box 'H' can describe one or more headers or sub - headers of the packets of each sublayer.

[0329] According to one aspect, the MAC sublayer 1232 can generate a MAC PDU 1252 based on one or more MAC SDUs received through bearer 1208 centered on X and radio bearer 1240. In one aspect, the MAC sublayer 1232 can generate a MAC PDU 1252 based on the MAC SDUs (e.g., MAC SDUs 1234 and 1236) received through bearer 1208 centered on X and the MAC SDU 1238 received through radio bearer 1240.

[0330] Thus, the transport block 1252 can be generated by the MAC 1232 by concatenating three RLC PDUs: two RLC PDUs 1228 and 1230 from the XaaS bearer 1208, and one RLC PDU 1244 from the radio bearer 1240. The transport block 1252 can be transmitted through physical resource blocks.

[0331] Those skilled in the art can understand that the upper-layer PDU (e.g., RLC PDU) can be the SDU of the lower layer (e.g., MAC SDU). The lower layer (e.g., MAC 1232) can add a header (the 'H' in the figure) to the SDU to obtain the lower-layer PDU (e.g., MAC SDU + MAC header (H) = MAC PDU). For example, in traditional connection services (5G), SDAP SDU + SDAPH = SDAP PDU; SDAP PDU = PDCP SDU; PDCP SDU + PDCD H = PDCP PDU. In some aspects, the PDCP PDU can be decoupled into one or more RLC SDUs. Additionally, RLC SDU + RLC H = RCL PDU; RLC PDU = MAC SDU; MAC SDU + MAC H = MAC PDU. In traditional connection services, the lower layer may not be able to parse and understand the meaning in the upper-layer PDU.

[0332] According to one aspect, the PF layer can be provided in XaaS (6G). In some aspects, one or more SDAP PDUs can be processed to obtain a PF SDU. For example, one or more SDAP PDUs can be a training dataset, which can be fed into the PF layer. The PF layer can parse and understand the meaning of the training dataset (e.g., by performing one or more operations on the training dataset to evaluate the training dataset, including processing the training dataset). In one aspect, the PF layer can use the training dataset (i.e., the SDAP PDU or the SDAP SUD contained in the SDAP PDU) to obtain a trained model result, which can be in the form of a PF SDU. The PF layer can add a header to the PF SDU to obtain a PF PDU (e.g., PF SDU + PF H = PF PDU). In some aspects, the PF PDU can be a PDCP SDU or can be decoupled into multiple PDCP SDUs. Then, the PDCP layer can add a PDCP header to each PDCP SDU to obtain a PDCP PDU (e.g., PDCP SDU + PDCP H = PDCP PDU).

[0333] In some aspects, one or more PF PDUs can be processed to obtain a new PF SDU, and then a second PDU can be constructed. For example, the one or more PF PDUs can be a training data set, which can be fed to the PF layer by a lower layer, such as the lower layer of a peer node. The PF layer can parse and understand the meaning of the training data set (e.g., by performing one or more operations on the training data set to evaluate the training data set, including processing the training data set). In one aspect, the PF layer can use the training data set (i.e., the PF PDU or the PF SDU contained in the PF PDU) to obtain a trained model result, which can be in the form of a new PF SDU. The PF layer can add a header to the new PF SDU to obtain a second PF PDU (e.g., PF SDU + PF H = PF PDU). In some aspects, the PF PDU can be a PDCP PDU or can be decoupled into multiple PDCP SDUs. Then, the PDCP layer can add a PDCP header to each PDCP SDU to obtain a PDCP PDU (e.g., PDCP SDU + PDCP H = PDCP PDU).

[0334] According to one aspect, the RLC PDU 1244 from the radio bearer 1240 can be a segment of the IP packet (m) 1238. For example, the IP packet can come from the DN. Two RLC PDUs 1228 and 1230 from the XaaS bearer 1208 respectively correspond to one PDCP PDU, PDCP SDUs 1222 and 1224.

[0335] One of the two PDCP PDUs from the XaaS bearer 1208 (e.g., PDCP SDU 1222) can correspond to the data processing result of the PF sublayer 1102 based on two CN packets (n 1202 and n+1 1204). For example, these two CN packets can come from CN PF. The other PDCP SDU 1224 can correspond to the data processing result of the PF sublayer 1102 based on one CN packet (n+2) 1206, and this CN packet can come from CN PF. In some aspects, the CN packet (n+2) 1206 can be transparently transmitted by the PF sublayer 1102 to the PDCP sublayer 1106 without data processing or PF header addition, that is, PF can be in transparent mode.

[0336] According to one aspect, the PDU format of the PF sublayer and one or more PDU parameters can be provided. In one aspect, the PF PDU can have two types: data PDU and control PDU.

[0337] According to one aspect, a data PDU can be used to transport one or more of the following: a PF header, user plane or data plane data. A control PDU can be used to transport control information, e.g., only the PF header without encapsulating user or data plane data.

[0338] Figure 13 An embodiment showing the format of a PF PDU provided by one aspect of the present invention is shown. The PF PDU format 1300 can indicate one or more of control information (according to the packet header 1302) and the payload 1304. The packet header 1302 can include one or more fields to indicate one or more of the following: Xs 1306, sequence number (SN) 1308, direct processing or forwarding (P / F) 1310, destination (De) 1312, and XaaS QoS flow identifier (XQFI) 1314. The payload can indicate data. The data can be raw data or processed data.

[0339] According to one aspect, a PF PDU can be a bit string that is length-aligned (e.g., bytes aligned in multiples of 8 bits). Refer to Figure 13 , the bit string can be represented by a table, and the first and most significant bit of the bit string can be the leftmost bit of the first row of the table. Generally, the bit string can be read from left to right and then in the reading order of the rows.

[0340] In one aspect, a PF PDU can include one or more fields for indicating data. The length of the data can be variable. In some aspects, the one or more fields indicating data can also include a PF SDU.

[0341] According to one aspect, taking UL data on the UE side (or DL data on the RAN side) as an example, a PF SDU can refer to the raw data received by the PF entity from the upper layer (i.e., the original PF SDU), e.g., from the SDAP sublayer. In some aspects, a PF SDU can refer to the result of processing performed by the PF entity using the original PF SDU.

[0342] In some aspects, for XaaS, the original PF SDU can be processed by the PF sublayer according to one or more methods (e.g., AI training, data privacy protection), and the processing result can be included in the PF PDU instead of the original PF SDU. The PF SDU can be included in the PF PDU starting from the first bit. In some aspects, the original PF SDU can be included in the PF PDU, e.g., when the PF sublayer of the XaaS bearer operates in transparent mode to provide connection services.

[0343] According to one aspect, taking the DL data on the UE side (or the UL data on the RAN side) as an example, the PF SDU may refer to the original data retrieved by the PF entity from the received PF PDU (i.e., the originally retrieved PF SDU) from the lower layer (e.g., from the PDCP sublayer). In some aspects, the PF SDU may refer to the result of the processing performed by the PF entity using the originally retrieved PF SDU.

[0344] In some aspects, for XaaS, the PF sublayer may use one or more methods (e.g., AI training, data privacy protection) to process the originally retrieved PF SDU, and may forward the processing result instead of the originally retrieved PF SDU to the upper layer or another PF entity. In some aspects, the originally retrieved PF SDU may be forwarded to the upper layer, e.g., when the PF sublayer carried by XaaS operates in transparent mode to provide connection services.

[0345] In some aspects, the length of the Xs field 1306 may be x bits. The Xs field 1306 may indicate the type of XaaS to which the PF data may belong. In some aspects, when establishing an XaaS bearer (e.g., a PF entity) (e.g., when established under the control of the control plane) (e.g., the XaaS bearer is established as a common or default XaaS bearer for all service types), in the case where the XaaS type is not configured or specified for the XaaS bearer, the Xs field 1306 may indicate the type of XaaS. The type of XaaS to which the PF PDU may belong may be indicated to the peer node for correct data processing. For example, the UE may indicate to the peer RAN node to provide a privacy-protected DAM service on the PF sublayer.

[0346] In some aspects, the data processing type (e.g., data collection, data purification, data preprocessing, etc.) may be included in the Xs field 1306. In some aspects, the Xs field 1306 may be defined with a finer granularity to further indicate the data processing type. For example, the granularity may be at the "process type" level to indicate data collection, data purification, or other process types corresponding to the XaaS.

[0347] According to one aspect, the data processing type may be used for the PF sublayer through the control plane (e.g., through the XaaS controller (XC) sublayer). When establishing a PF entity during the XaaS bearer establishment process, the PF entity may be configured by the XC to indicate which process type can be selected to process the data.

[0348] Figure 14An embodiment of a table showing a description of the Xs field provided by one aspect of the present invention is shown. In some aspects, the Xs field 1306 may have a size of 3 bits (although other sizes may apply) for indicating one or more XaaSs. For example, the Xs field may be set to '001' to indicate that the message belongs to the NET4AI service. The Xs field may be set to '010', which may indicate that the message belongs to the DAM service. The Xs field may be set to '011', which may indicate that the message belongs to a task involving multiple XaaSs.

[0349] According to one aspect, the length of the SN field 1308 is y bits. The SN field 1308 may indicate the sequence number of the PFPDU for data sorting or reordering. In some aspects, the data size of XaaS (AI training dataset, AI-trained model parameters) may be large, so the order of data traffic (e.g., AI inference results) may be important. In the case of large data sizes, SN may be required for correct data sorting. In some aspects, the SN may also include the task ID or data processing step ID (e.g., round ID) to which the PF PDU belongs for synchronization in case of data processing delay or data forwarding delay.

[0350] According to one aspect, the length of the P / F field 1310 may be 1 bit. The P / F field 1310 (through the P / F bit) may indicate whether the PF SDU needs to be processed or only directly forwarded. For example, due to limitations in computing or wireless channel conditions, or due to service logic requirements, the PF entity of the peer node may already need to participate in the processing of the previous PF PDU, while the current PFPDU does not. That is, in some aspects, it may be necessary for the peer PF entity to perform data processing dynamically on demand or conditionally, rather than always processing all data passing through the PF sublayer.

[0351] Taking AI as an example, due to computing latency, the UE or RAN may not participate in AI training in some training rounds. The UE or RAN may only need to retrieve the PF SDU from the PF PDU and forward the PF SDU to the UE application layer or the CN without data processing. In some aspects, for specific AI service logic, the UE may cooperate with the CN PF or the DN to perform AI training on the PF sublayer in multiple steps or rounds. In some of these steps or rounds, the RAN may participate to help the UE and the CN process the intermediate data of the PF sublayer, while in other steps or rounds, the RAN may not participate.

[0352] In some aspects, the XaaS bearer can operate in transparent mode and can be used as a DRB. The P / F bit can indicate that the PF entity of the peer node switches between the XaaS bearer and the DRB. Therefore, the PF entity of the peer node can be flexibly activated or deactivated via the P / F bit to switch between the XaaS bearer and the DRB. In some aspects, the DRB can be configured with a PF entity that operates in transparent mode (TM). For example, if the P / F field 1310 indicates that the data field of the PF PDU does not need to be processed by the PF sublayer and only needs to be directly forwarded to the upper layer or the lower layer by the PF sublayer, the PF sublayer of the XaaS bearer can operate in transparent mode.

[0353] Figure 15 An embodiment of a table showing a description of the P / F field provided by one aspect of the present invention is shown. In one aspect, the P / F field can be set to '0' to indicate that the data field of the PF PDU can only be forwarded without being processed, thereby deactivating the PF sublayer into transparent mode. In some aspects, the P / F field can be set to '1' to indicate that data processing of the data field of the PF PDU may be required.

[0354] According to one aspect, the length of the destination (De) field 1312 can be z bits. The De field 1312 can indicate routing information (e.g., destination address) of the PF SDU used by the PF entity to transmit, retrieve, or process the PF PDU, e.g., transmitted to another PF entity residing in the same node, another PF entity of the peer node, or one or more in the upper layer. In some aspects, the PF entity (e.g., the Rx-PF entity) can transmit the De field together with the PF SDU retrieved or processed from the PF PDU. In some aspects, the De field may not be deleted, or only the information part included in the De field may be deleted. In some aspects, when the PF entity performs PF PDU de-encapsulation, for example, if the De field indicates routing information with a source routing scheme or a bit index explicit replication (BIER) scheme, the De field can be updated.

[0355] In some aspects, through the XaaS session, data can be flexibly processed between different nodes, for example, in the CN PF unit, in the PF sub-layer of the RAN, and in the PF sub-layer of the UE. One or more of the RAN, UE, and CN functions may participate in the XaaS session. For example, an XaaS session may pass through several RAN nodes, and these RAN nodes can cooperate to process XaaS data sequentially or in parallel. In some aspects, the Rx-PF entity within a node (e.g., within a RAN node or UE) can submit the PF SDU retrieved or processed from the PF PDU to the upper layer or send it to the Tx-PF entity residing in the same node. In some aspects, different routing actions can be indicated to peer nodes on the PF PDU. In some aspects, the De field can provide flexible and correct data forwarding between different nodes. The data forwarding can be unicast transmission or multicast transmission. The De field can also provide flexible and correct data forwarding between different protocol layers.

[0356] According to one aspect, the header 1302 may include routing information, for example, the destination address (one or more of the next-hop address and the address of the last node to complete the task). For example, the destination address may refer to one or more of the following: the address of the PF entity residing in the UE, the address of the PF entity residing in the RAN node, and the address of the PF entity residing in the CN node. In some aspects, a globally unique address may be pre-allocated (e.g., through the control plane) to each PF entity in the PF sub-layer. In some aspects, the routing table may be pre-configured (e.g., through the control plane) for each node for a specific task of XaaS. Based on the destination address and the pre-configured routing table, the current PF entity can know or determine the next hop (which node can be the next hop, e.g., the hop to another PF entity residing in the same or different node or to the upper layer).

[0357] According to one aspect, the length of the XQFI field 1314 may be t bits. The XQFI field 1314 may indicate the ID of the XaaS QoS flow to which the PF PDU belongs. The XaaS QoS flow ID may indicate to other protocol layers (e.g., the PDCP sub-layer) what data forwarding disposition may be appropriate to perform. The XaaS QoS flow ID may also indicate to PF entities (e.g., PF entities residing in the same node, PF entities of peer nodes) what data processing disposition is appropriate to perform.

[0358] In some aspects, the PF PDU may include one or more parameters indicated by one or more of the Xs field, SN field, P / F field, De field 1312, XQFI field 1314, and data field. In some aspects, the DL PDU header may indicate one or more parameters indicated in the UL PF PDU and vice versa, as would be understood by those skilled in the art.

[0359] According to one aspect, the XaaS bearer may be configured per UE. That is, one XaaS bearer may serve a dedicated UE and thus transmit (and receive) dedicated PF packets to (and from) a dedicated UE over the radio interface.

[0360] Figure 16 An embodiment of the DL layer 2 architecture for XaaS and PDU connection services provided by one aspect of the present invention is shown. Figure 16 A possible DL layer 2 architecture for XaaS in other possible implementations (i.e., the solid-line box) is shown, as would be understood by those skilled in the art. Figure 16 The DL layer 2 architecture for PDU connection services (i.e., the dotted-line box) is further shown.

[0361] According to one aspect, one XaaS bearer per UE may have one or more characteristics. One SDAP entity may be configured per XaaS session, i.e., SDAP:XaaS session = 1:1. For example, SDAP entity 1602 may be configured for XaaS session 1604 of UE1. One XaaS session may include one or more XaaS QoS flows.

[0362] In some aspects, one XaaS session (e.g., 1604) may be mapped, for example, by the SDAP sublayer 1104 to one or more XaaS data bearers (XDB), such as XaaS B1 1606 and XaaS B2 1608. The mapping of an XaaS session to one or more XaaS data bearers may be based on XaaS QoS requirements, such as data forwarding handling requirements and data processing handling requirements. In some aspects, one XaaS bearer may transmit the data of one or more XaaS sessions, i.e., XaaS session:XDB = Q:M.

[0363] According to one aspect, one PF entity may be configured for each individual XaaS bearer, i.e., XDB:PF entity = 1:1. For example, a PF entity (e.g., data processing 1610) may be configured for XaaS B1 1606, and PF entity 1612 may be configured for XaaS B2 1608.

[0364] In some aspects, each PF entity (e.g., data processors 1610 and 1612) may perform one or more functions of the Tx-PF entities (e.g., Tx PF entities 702, 802) and Rx-PF entities (e.g., Rx-PF entities 702, 812) related to XaaS bearers, as described herein. Thus, PF entity 1610 or 1612 may include a transmitting part and a receiving part as shown and described herein. Figure 17 as shown and described herein.

[0365] In some aspects, an XaaS bearer may be configured with one of the Tx-PF entity and the Rx-PF entity. In some aspects, when needed, the XaaS bearer of a node (e.g., RAN, UE) may be configured only with the Tx-PF entity, and may receive data from another XaaS bearer of the node that is configured only with the Rx-PF entity through an associated PF sublayer.

[0366] Similarly, in some aspects, the XaaS bearer of a node (e.g., RAN, UE) may be configured only with the Rx-PF entity, and may transmit data to another XaaS bearer of the node that is configured only with the Tx-PF entity through the PF sublayer.

[0367] According to one aspect, one XaaS bearer may serve only one dedicated UE, but one UE may be configured with multiple XaaS bearers. For example, each of XaaS B1 1606 and XaaS B2 1608 may be configured with a UE1 1614, while UE1 1614 may be configured with XaaS B1 1606 and XaaS B2 1608.

[0368] According to one aspect, one XaaS bearer may be mapped to one or more DRBs of the same UE, and each DRB may be configured with a PDCP entity. Thus, the data of one PF entity may be mapped to one or more PDCP entities configured for the same UE. In some aspects, the mapping may be based on XaaS QoS requirements, e.g., data forwarding handling requirements and data processing handling requirements. In some aspects, the mapping information between the XaaS bearer and the DRB may be configured through dedicated XaaS signaling messages or RRC messages, e.g., configured by the XC sublayer or other control plane functions through XSB. In some aspects, one DRB may carry the data of one or more XaaS bearers, i.e., XaaS bearer:DRB = M:N.

[0369] According to one aspect, the DRB carrying PDU session data and the DRB carrying XaaS session data can reuse radio resources. Therefore, the data from the XaaS session and the PDU session can be mapped to the same MAC sublayer 1232 to reuse radio resources. For example, the XaaS session data of UE1, the PDU session data of UE1, the XaaS session data of UEn, and the PDU session data of UEn can reuse radio resources.

[0370] According to one aspect, for a UE, the ratio of the number of XaaS sessions, SDAP entities, XaaS bearers, PF entities, DRBs, and PDCP entities can be as follows: XaaS session:SDAP entity:XaaS bearer:PF entity:DRB:PDCP entity:UE = Q:Q:M:M:N:N.

[0371] In some aspects, one or more dedicated types of radio bearers, RLC channels, logical channels, transport channels, and physical channels can be defined, reserved, or configured for XaaS. In some aspects, dedicated physical radio resources (e.g., radio spectrum) can be allocated to XaaS.

[0372] In some aspects, the XaaS bearer can be configured through dedicated XaaS signaling messages or RRC messages, e.g., configured by the XC sublayer or other control plane functions through XSB.

[0373] In some aspects, if the traffic granularity of the XaaS QoS flow or the XaaS session is the same as that of the XaaS bearer, the mapping relationship between the XaaS QoS flow and the XaaS bearer may not be required, and the SDAP entity may not be configured. Therefore, the XaaS QoS flow or the XaaS session can be mapped to the XaaS bearer one-to-one without the SDAP entity.

[0374] In some aspects, if the XaaS is initiated or terminated at the RAN node without the participation of the CN, the SDAP sublayer may not be configured, and the service can be terminated at the PF sublayer between the RAN node and the UE.

[0375] In some aspects, if the XaaS is only processed in the RAN and the CN and the UE does not participate, the SDAP sublayer may not be configured (or configured without a DL SDAP header or a UL SDAP header).

[0376] Figure 17An embodiment of a PF entity model including a transmitting part (Tx part) and a receiving part (Rx part) provided by one aspect of the present invention is shown. The PF entity 1700 may include a Tx part 1702 and an Rx part 1712. The Tx part 1702 may be similar to the Tx-PF entity described herein, and the Rx part 1712 may be similar to the Rx-PF entity described herein. According to one aspect, each of the Tx part 1702 and the Rx part 1712 may execute one or more components for performing one or more functions. For example, the Tx part 1702 may include a data buffer component 1704, a data processing component 1705, and a data transmission component 1706. The Rx part 1712 may include a routing component 1717, a data processing component 1715, a data buffer component 1714, and a data transmission component 1716. The functions of each component are described herein in connection with the PF entity.

[0377] Figure 18 Another embodiment of a PF entity including a Tx part and an Rx part provided by one aspect of the present invention is shown. The PF entity 1800 may include a Tx part 1802 and an Rx part 1812. The Tx part 1802 may be similar to the Tx-PF entity described herein, and the Rx part 1812 may be similar to the Rx-PF entity described herein. According to one aspect, each of the Tx part 1802 and the Rx part 1812 may execute one or more components for performing one or more functions. For example, the Tx part 1802 may include a data buffer component 1804, a data processing component 1805, a routing component 1807, and a data transmission component 1806. The Rx part 1812 may include a routing component 1817, a data processing component 1815, a data buffer component 1814, and a data transmission component 1816. The functions of each component are described herein in connection with the PF entity.

[0378] According to one aspect, if an XaaS QoS flow included in an XaaS session is received from a tunnel bound to an XaaS bearer (e.g., a GTP-U tunnel) or from an XaaS function of the CN (e.g., CN XaaS PF), the SDAP entity may know the mapping information between the XaaS QoS flow and the XaaS bearer. In some aspects, the binding information may be pre-configured when the XaaS QoS flow and the XaaS bearer are established.

[0379] In some aspects, a CN message received by the SDAP sublayer (through the SDAP entity) may contain indication information (e.g., in the data header) to indicate that the message is XaaS data rather than connection service data. In some aspects, the indication information may be a bit value, a boolean value, a specific QFI (i.e., XQFI), or a specific PDU session ID. Based on the indication information, the SDAP sublayer may decide or determine the mapping information.

[0380] In some aspects, indication information (e.g., a bit value, a boolean value, a specific QFI (i.e., XQFI), or a specific PDU session ID) may be included in the header of an SDAP PDU or a GTP-U message to indicate which XaaS QoS flow an SDAP PDU or an SDAP SDU retrieved from the SDAP PDU may belong to. In some aspects, when an XaaS bearer transports data of multiple XaaS QoS flows based on, for example, pre-configured XaaS QoS flow and XaaS bearer mapping rules (i.e., multiple XaaS QoS flows may be mapped to one XaaS bearer), data mapping (UL data mapping on the RAN side, or DL data mapping on the UE side) may be required by the SDAP sublayer.

[0381] Figure 19 An embodiment of an SDAP PDU format having an XQFI field in the SDAP header provided by one aspect of the present invention is shown. The SDAP PDU format 1900 may include a header 1902 and a payload 1904. The header 1902 may include an XQFI field 1914 to indicate that the message is XaaS data.

[0382] In some aspects, an XaaS bearer may be configured per UE group. That is, one XaaS bearer may serve a UE group and transmit (and receive) dedicated PF data packets to (and from) the UE group via a radio interface. A UE group may include one or more participating UEs.

[0383] According to one aspect, if an XaaS bearer is configured for a UE group, a first transmission method for transmitting XaaS data packets between the RAN and one or more UEs in the UE group via a radio interface may involve: transmitting a single copy of a PF data packet (e.g., a PF PDU) to multiple UEs via the radio interface (e.g., using a broadcast or multicast method).

[0384] In some aspects, if an XaaS bearer is configured for a UE group, a second transmission method for transmitting XaaS data packets between the RAN and one or more UEs in the UE group via a radio interface may involve: transmitting a separate copy of the same PF data packet (e.g., a PF PDU) to each of one or more UEs in the UE group via the radio interface.

[0385] In some aspects, if an XaaS bearer is configured for a UE group, a second transmission method for transmitting XaaS data packets between the RAN and one or more UEs in the UE group via a radio interface may involve: transmitting different PF data packets (e.g., different data processing results) generated by a PF entity to different UEs among one or more UEs in the UE group via the radio interface.

[0386] Figure 20 Another embodiment of the DL layer 2 architecture for XaaS and PDU connection services provided by one aspect of the present invention is shown. The DL layer 2 architecture for XaaS is shown for UE group 1 2038 (refer to the dashed box), PF entity (data processing entity 2006), PDCP entity (ROHC entity 2010 and security entity 2018), and RLC entity (segmentation entity 2026). In some aspects, the security entity 2018 may not be deployed. A second DL layer 2 architecture for XaaS is shown for UE group 2 2046, UE1 2046, and UEn 2050, refer to the bold box: PF entity (data processing entity 2008), PDCP entity (for UE group 2 2044: ROHC entity 2012, security entity 2020; for UE1 2046: ROHC entity 2012, ROHC entity 2014, security entity 2020, and security entity 2022; for UEn 2050: ROHC entity 2016 and security entity 2024). In some aspects, the security entity 2020 and RLC entity (for UE group 2 2044: segmentation entity 2028; for UE1 2046: segmentation ARQ entity 2030 and segmentation entity 2032; for UEn 2050: segmentation ARQ entity 2034) may not be deployed. Those skilled in the art can understand that the implementation manner of the DL layer 2 architecture for XaaS is not limited to the illustrated implementation manner, and there may be other implementation manners.

[0387] Figure 20 Another embodiment of the DL layer 2 architecture 2060 for PDU connection services provided by one aspect of the present invention is shown. In some aspects, in the first transmission method, the transmission of XaaS data may involve: for example, using the broadcast or multicast method, transmitting a single copy of the PF data packet (e.g., PF PDU) to multiple UEs through the wireless interface. The mode 1 of the XaaS bearer for the UE group (refer to the dashed box) may have one or more characteristics. In some aspects, similar to the aspect Figure 16 described, an SDAP entity can be configured for each individual XaaS session, that is, SDAP:XaaS session = 1:1. For example, the SDAP entity 2004 (XaaS QoS flow processing entity 2004) can be configured for the XaaS session 2002. One XaaS session, such as the XaaS session 2002, may include one or more XaaS QoS flows.

[0388] In some aspects, referring to the first transmission method, similar to the reference Figure 16In the aspect described above, an XaaS session 2002 can be mapped to one or more XaaS data bearers (XaaS bearer 1 2040) by, for example, the SDAP sublayer 1104. The mapping of an XaaS session to one or more XaaS bearers can be based on XaaS QoS requirements, such as data forwarding handling requirements and data processing handling requirements. In some aspects, one XaaS bearer can transmit data of one or more XaaS sessions. XaaS session:XDB = Q:M.

[0389] In some aspects, referring to the first transmission method, similar to the reference Figure 16 In the aspect described above, a PF entity can be configured for each individual XaaS bearer, that is, XDB:PF entity = 1:1. For example, a PF entity (such as data processing 2006) can be configured for XaaS bearer 1 2040.

[0390] In some aspects, referring to the first transmission method, an XaaS bearer 2040 can serve a UE group (such as UE group 1 2038) including one or more UEs. In some aspects, one UE can join multiple groups. In some aspects, one UE can be configured with multiple XaaS bearers.

[0391] In some aspects, an XaaS bearer can be mapped to a new type of radio bearer (NRB) to carry the data of the XaaS bearer. The NRB can be used for point-to-multipoint data transmission between the network and the UE, for example, using multicast or broadcast methods.

[0392] According to one aspect, the NRB can be configured with a PDCP entity. Therefore, the data of a PF entity can be mapped to a PDCP entity configured for the UE group. In some aspects, the mapping can be based on XaaS QoS requirements, such as data forwarding handling requirements and data processing handling requirements. The mapping information between the XaaS bearer and the NRB can be configured through dedicated XaaS signaling messages or RRC messages, for example, configured by the XC sublayer or other control plane functions through XSB. In some aspects, one NRB may only carry the data of one XaaS bearer. XaaS bearer:NRB = 1:1. In some aspects, the DRB carrying PDU session data and the NRB carrying XaaS session data can multiplex radio resources.

[0393] Therefore, for the UE, referring to the first transmission method, the ratio of the number of XaaS sessions, SDAP entities, XaaS bearers, PF entities, NRBs, and NRB PDCP entities can be: XaaS session:SDAP entity:XaaS bearer:PF entity:NRB:PDCP entity = Q:M:M:M:M.

[0394] According to one aspect, the NRB can be configured as a Multicast / Broadcast Service (MBS) Radio Bearer (MRB).

[0395] As described herein, the second transmission method for transmitting XaaS data can involve: transmitting a separate copy of the same PF data packet (e.g., PF PDU) to each UE in a UE group via a radio interface; or transmitting different PF data packets (e.g., different data processing results) generated by a PF entity to different UEs among one or more UEs in a UE group via a radio interface.

[0396] According to one aspect, in the second transmission method, the XaaS bearer for each UE group (e.g., referring to the bold box in Figure 20 can have one or more characteristics. In some aspects, similar to the aspects described in reference Figure 16 , an SDAP entity can be configured for each individual XaaS session, i.e., SDAP:XaaS session = 1:1. For example, an SDAP entity 2004 (XaaS QoS flow processing entity 2004) can be configured for XaaS session 2002. An XaaS session (XaaS session 2002) can include one or more XaaS QoS flows.

[0397] In some aspects, referring to the second transmission method, similar to the aspects described in reference Figure 16 , an XaaS session can be mapped to one or more XaaS data bearers by the SDAP sublayer, for example. The mapping of an XaaS session to one or more XaaS bearers can be based on XaaS QoS requirements. At the same time, one XaaS bearer can transmit data of one or more XaaS sessions, i.e., XaaS session:XDB = Q:M.

[0398] In some aspects, referring to the second transmission method, similar to the aspects described in reference Figure 16 , a PF entity can be configured for each individual XaaS bearer. XDB:PF entity = 1:1. For example, a PF entity (e.g., data processing 2008) can be configured for XaaS bearer 2 2042.

[0399] In some aspects, referring to the second transmission method, an XaaS bearer (e.g., XaaS bearer 2 2042) can serve a UE group (e.g., UE group 2 2044, UE1 2046, UEn 2050). In some aspects, a UE can be configured with multiple XaaS bearers.

[0400] According to one aspect, an XaaS bearer can be mapped to one or more DRBs and (optionally) to one or more NRBs. Each DRB or NRB can be configured with a PDCP entity, e.g., based on the XaaS QoS requirements and the UE's radio channel state. Thus, a PF entity can be mapped to one or more PDCP entities, and each PDCP entity can be configured for a dedicated UE or UE group. As described herein, the mapping between the PF entity and the PDCP entities and the configuration of the PDCP entities can support flexible priority and scheduling handling. The mapping of the PF entity to one or more PDCP entities can be based on the XaaS QoS requirements, such as data forwarding handling requirements and data processing handling requirements. The mapping information between the XaaS bearer and the NRB and the mapping information between the XaaS bearer and the DRB can be configured via dedicated XaaS signaling messages or RRC messages, e.g., configured by the XC sublayer or other control plane functions via XSB. In some aspects, a DRB / NRB can carry data of one or more XaaS bearers, i.e., XaaS bearer:DRB / NRB = M:N.

[0401] According to one aspect, the XaaS traffic in the second transmission method can be split. In some aspects, the XaaS service can be split in the PF sublayer 1102, i.e., a PF entity can be configured with multiple PDCP entities. For example, the data processing entity 2008 can be configured with multiple PDCP entities (e.g., ROHC entity 2012, ROHC entity 2014, and ROHC entity 2016). The XaaS data carried by a PF entity can be mapped to multiple PDCP entities configured for a dedicated UE or UE group. For example, separate copies of the same PF packet (e.g., PF SDU) carried by a PF entity can be mapped to multiple PDCP entities. As another example, different PF packets (e.g., different data processing results) generated by the PF entity can be mapped to multiple PDCP entities.

[0402] According to one aspect, the XaaS traffic can be split in the PDCP sublayer 1106, i.e., a PF entity can be configured with one or more PDCP entities, and each PDCP entity can be configured with multiple RLC entities. Refer to Figure 20, the PDCP entity 2020 may be configured with multiple RLC entities (e.g., the segmentation entity 2028 and the segmentation ARQ entity 2030). In some aspects, when a security entity (e.g., the security entity 2020) is not deployed, the ROHC entity (e.g., the ROHC entity 2012) may be configured with multiple RLC entities (e.g., the segmentation entity 2028 and the segmentation ARQ entity 2030). For example, separate copies of the same XaaS data packet carried by one PDCP entity (e.g., the security entity 2020, the ROHC entity 2012) may be mapped to one or more RLCs configured for one or more UEs. As another example, different XaaS data packets carried by one PDCP entity may be mapped to multiple RLC entities.

[0403] According to one aspect, the traffic divided in the PF sublayer 1102 and the traffic divided in the PDCP sublayer 116 may be deployed as a whole. For example, referring to Figure 20 , one PF entity (e.g., the data processing entity 2008) may be configured with multiple PDCP entities (e.g., the ROHC entity 2012, the ROHC entity 2014, and the ROHC entity 2016). At the same time, the PDCP entity (e.g., the security entity 2020, the ROHC entity 2012) may be configured with multiple RLC entities (e.g., the segmentation entity 2028 and the segmentation ARQ entity 2030).

[0404] In some aspects, one or more of the DRBs and NRBs carrying PDU session data and one or more of the DRBs and NRBs carrying XaaS session data may multiplex radio resources.

[0405] According to one aspect, for the UE in the second transmission method, the ratio of the number of XaaS sessions, SDAP entities, XaaS bearers, PF entities, DRBs, DRB PDCP entities, NRBs, and NRB PDCP entities may be as follows: XaaS session:SDAP entity:XaaS bearer:PF entity:DRB:DRB PDCP entity:NRB:NRB PDCP entity:UE = Q:Q:M:M:N:N:K:K.

[0406] In some aspects, for both the first transmission method and the second transmission method, one or more dedicated types of the following may be defined, reserved, or configured for XaaS: radio bearers, RLC channels (e.g., an XaaS traffic channel (XTCH) that can be mapped to a downlink shared channel (DL-SCH); or reusing an MB traffic channel (MTCH)), logical channels, transport channels, and physical channels. In some aspects, dedicated physical radio resources (e.g., radio spectrum) may be allocated to XaaS.

[0407] In some aspects, the XaaS bearers for each UE and the XaaS bearers for each UE group may be deployed as a whole. For example, some XaaS bearers in the network may be configured for UEs based on the scheme of the XaaS bearers for each UE as shown in Figure 16 while some XaaS bearers in the network may be configured for UEs based on the scheme of the XaaS bearers for each UE group as shown in Figure 20 In some aspects, one or more UEs configured with one or more XaaS bearers based on the per-UE scheme may be the same as or different from one or more UEs configured with one or more XaaS bearers based on the per-UE group scheme. In some aspects, if XaaS is initiated or terminated at the RAN node without the need for CN participation, the SDAP sublayer may not be required, and the service may be terminated at the PF sublayer.

[0408] In some aspects, if the traffic granularity of the XaaS QoS flow or the XaaS session is the same as the traffic granularity of the XaaS bearer, the mapping relationship between the XaaS QoS flow and the XaaS bearer may not be required, and the SDAP entity may not be configured. Therefore, the XaaS QoS flow or the XaaS session can be mapped one-to-one to the XaaS bearer without the SDAP entity.

[0409] In some aspects, the PDCP sublayer may not be configured, e.g., for signaling broadcast via XSB. In some aspects, compared with traditional multicast / broadcast, the data partitioned at the PF entity can support security protection on the PDCP sublayer (e.g., at the per-UE granularity).

[0410] In some aspects, if the RLC entity is configured for a UE group, the RLC entity may operate in the unacknowledged mode (UM), where the RLC entity may not perform the ARQ process.

[0411] In some aspects, if RLC is configured for a UE, the RLC can operate in unacknowledged mode (UM) or acknowledged mode (AM). The RLC entity in acknowledged mode can perform ARQ procedures.

[0412] Aspects of the present invention can provide one or more of an XaaS session, an XaaS QoS flow, and an XaaS bearer. Some aspects can provide one or more XaaS QoS parameters, the one or more XaaS QoS parameters including one or more data processing and handling parameters and one or more data forwarding parameters. One or more aspects described with reference to an XaaS session, an XaaS QoS flow, an XaaS bearer, and XaaS QoS parameters can enable 6G XaaS on the CN, RAN, and UE sides. According to some aspects described herein, a new type of air interface bearer can be provided.

[0413] According to one aspect, a functional view of PF can be provided. Aspects can provide a functional design of a Tx-PF entity and an Rx-PF entity. Some aspects can provide a PF PDU format and associated parameters included in the PDU. Aspects described with reference to one or more of the following: a PF entity, a PF PDU format, and associated parameters can make the RAN a data source and a data destination, where XaaS data can be initiated or terminated at the RAN.

[0414] According to one aspect, a structural view of a PF entity can be provided, showing how entities of a PF sublayer, a PDCP sublayer, an SDAP sublayer, and an RLC sublayer can be connected. Some aspects can provide a design of XaaS bearer configuration for each UE or UE group. Aspects described with reference to the structural views of PF and XaaS bearer configuration can implement data mapping between an XaaS session, an XaaS QoS flow, an XaaS bearer, a DRB, and an NRB.

[0415] According to one aspect, a PF entity is configured in a PF protocol layer at a CNF node, and the PF entity on the CNF node has the same functions as PF entities on a RAN node and a UE. Different PF entities at one or more of the CNF node, the RAN node, and the UE can work together.

[0416] According to one aspect, the PF sublayer is deployed in one of the following various scenarios, but not limited to one of the following: above the PDCP sublayer, between the SDAP sublayer and the PDCP sublayer, between the PDCP sublayer and the RLC sublayer, between the RLC sublayer and the MAC sublayer, between the MAC sublayer and the PHY layer, above the SDAP sublayer, above the PDU layer, above the GTP-U layer, above the UDP layer, above the IP layer, above the QUIC layer, above the hypertext transfer protocol (HTTP) layer, above the segment routing over IPv6 (SRv6) layer, within the PDU layer, within the SDAP sublayer, within the PDCP sublayer, within the RLC sublayer, within the MAC sublayer, within the PHY layer, within the GTP-U layer, within the UDP layer, within the IP layer, within the application layer, within the HTTP layer, within the SRv6 layer, and within the QUIC layer.

[0417] Figure 21 Embodiments of apparatus 2100 provided by different aspects of the present invention are shown, and the apparatus may perform any or all of the operations of the above-described methods and features explicitly or implicitly described herein. For example, a computer equipped with network functions can be configured as apparatus 2100. In some aspects, apparatus 2100 can be a PF (e.g., Tx-PF, Rx-PF), a transmitting part, a receiving part, a user equipment, a RAN node, a CN function, or any other entity that can be described herein. In some aspects, apparatus 2100 can be a device connected to a network infrastructure through a wireless interface, such as a mobile phone, a smartphone, or other devices that can be classified as user equipment (UE). In some aspects, apparatus 2100 can be a machine-type communications (MTC) device (also known as a machine-to-machine (m2m) device), or other such devices that can be classified as UE although they do not provide direct services to users. In some aspects, apparatus 2100 can be used to implement one or more aspects described herein. For example, apparatus 2100 can be used to perform operations executed by one or more entities and functions described herein.

[0418] As shown in the figure, the apparatus 2100 may include a processor 2110, such as a central processing unit (CPU) or a dedicated processor, such as a graphics processing unit (GPU) or other such processing unit, a memory 2120, a non-transitory mass storage 2130, an input-output interface 2140, a network interface 2150, and a transceiver 2160, all of which are communicatively coupled via a bidirectional bus 2170. According to some aspects, any or all of the described elements may be used, or only a subset of these elements. Additionally, the apparatus 2100 may include multiple instances of some of the elements, such as multiple processors, memories, or transceivers. Further, the elements of the hardware device may be directly coupled to other elements without a bidirectional bus. In addition to or in place of the processor and the memory, other electronic components, such as integrated circuits, may be used to perform the required logical operations.

[0419] The memory 2120 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 thereof, etc. The mass storage element 2130 may include any type of non-transitory storage device, such as a solid state disk, a hard disk drive, a disk drive, an optical disk drive, a USB drive, or any computer program product for storing data and machine-executable program code. According to some aspects, the memory 2120 or the mass storage 2130 may record statements and instructions executable by the processor 2110 for performing any of the method operations described above.

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

[0421] It should be understood that although specific aspects of the technology have been described herein for purposes of illustration, various modifications can be made without departing from the scope of the technology. Accordingly, the specification and drawings are to be regarded only as an illustration of the invention as defined by the appended claims and are considered to cover all modifications, variations, combinations or equivalents falling within the scope of the invention. In particular, within the scope of the present technology, a computer program product or program element, or a program storage device such as a magnetic or optical, magnetic tape or optical disk, etc., is provided for storing machine-readable signals for controlling the operation of a computer according to the method of the present technology and / or constructing some or all of its components according to the system of the present technology.

[0422] The actions associated with the methods described herein can be implemented as encoded instructions in a computer program product. In other words, a computer program product is a computer-readable medium having software code recorded thereon, and when the computer program product is loaded into a memory and executed on a microprocessor of a wireless communication device, the software code executes the method.

[0423] Furthermore, each operation of the method can be performed on any computing device (such as a personal computer, server, PDA, etc.) according to one or more of one or more program elements, modules or objects generated from any programming language (such as C++, Java, etc.), or a part of one or more program elements, modules or objects. In addition, each operation or a file or object, etc. implementing each of the said operations can be performed by a dedicated hardware or circuit module designed for this purpose.

[0424] Through the description of the above embodiments, the present invention can be implemented only using hardware, or can be implemented using software and a necessary general hardware platform. Based on such an understanding, the technical solution of the present invention can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transitory storage medium, and the non-volatile or non-transitory storage medium can be a compact disk read-only memory (CD-ROM), USB, flash drive or external hard drive. The software product includes many instructions that enable a computer device (personal computer, server or network device) to execute the methods provided in various aspects of the present invention. For example, such execution can correspond to the simulation of the logical operations described herein. According to various aspects of the present invention, additionally or alternatively, the software product can include a plurality of instructions that enable a computer device to perform operations for configuring or programming a digital logic device.

[0425] Although the present invention has been described with reference to specific features and embodiments of the present invention, it will be apparent that various modifications and combinations of the present invention can be made without departing from the present invention. Accordingly, the specification and drawings are to be regarded only as illustrative of the invention as defined by the appended claims and are considered to cover any and all modifications, variations, combinations or equivalents falling within the scope of the present invention.

Claims

1. A method for providing network services, characterized in that, The method includes: A first device receives at least one protocol data unit (PDU) from a second device, the at least one PDU including at least one service data unit (SDU) associated with the network service; The first device retrieves the at least one SDU from the at least one PDU; The first device processes the at least one SDU to obtain a processed version of the at least one SDU; The first device constructs at least one additional PDU, the at least one additional PDU including the processed version of the at least one SDU; The first device sends the at least one additional PDU to the second device.

2. The method according to claim 1, characterized in that, The first device is a radio access network (RAN) node, and the second device is a user equipment (UE).

3. The method according to claim 1, characterized in that The first device is a UE, and the second device is a RAN node.

4. The method according to claim 2 or 3, characterized in that Retrieving the at least one SDU, processing the at least one SDU, and constructing the at least one additional PDU are performed at the first device by a processing function (PF) at the first device.

5. The method according to claim 1 or 4, characterized in that Receiving the at least one PDU at the first device includes: receiving the at least one PDU through at least one network service data bearer (XDB) established between the first device and the second device, the at least one XDB being for the network service.

6. The method according to claim 4, characterized in that The communication network in which the first device and the second device are deployed includes a PF protocol sublayer, and the retrieval of the at least one SDU, the processing of the at least one SDU, and the construction of the at least one additional PDU at the first device are performed by the PF at the first device in the PF protocol sublayer.

7. The method according to claim 6, wherein: The second device includes a PF deployed in the PF protocol sublayer at the second device; Receiving the at least one PDU from the second device includes: receiving the at least one PDU from the PF deployed at the second device through at least one XDB established between the first device and the second device.

8. The method according to claim 7, wherein The at least one XDB is supported by the PF protocol sublayer.

9. The method according to any one of claims 1 to 8, characterized in that The network service includes one or more of the following: data analysis, artificial intelligence (AI) training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

10. The method according to claim 6, characterized in that The communication network further includes a packet data convergence protocol (PDCP) sublayer, and the PF protocol sublayer is deployed above the PDCP sublayer.

11. The method according to claim 10, wherein The communication network further includes a service data adaptation protocol (SDAP) sublayer, and the PF protocol sublayer is deployed below the SDAP sublayer.

12. The method according to claim 10 or 11, characterized in that, The PDCP sublayer provides at least one data radio bearer (DRB) to the PF protocol sublayer between the first device and the second device.

13. The method according to claim 11, characterized in that, The PF protocol sublayer provides the at least one XDB to the SDAP sublayer.

14. The method according to claim 10 or 11, characterized in that, The communication network includes a radio link control RLC sublayer, a medium access control MAC sublayer and a physical PHY layer, and the PDCP sublayer is located above the RLC sublayer, the MAC sublayer and the PHY layer.

15. The method according to any one of claims 5, 7, 8 or 13, characterized in that, Each XDB in the at least one XDB has a corresponding PF entity in the PF protocol sublayer, and each PF entity is used for a corresponding XDB.

16. The method according to claim 12, wherein For each DRB of the at least one DRB, the PDCP sublayer includes a corresponding PDCP entity in the PDCP sublayer.

17. The method according to claim 13, wherein The SDAP entity in the SDAP sublayer is used for at least one session of the network service, any one of the at least one session of the network service is between the UE and the core network function CNF, and the method also includes establishing a CN session tunnel between the RAN node and the CNF.

18. The method according to claim 17, characterized in that: any one of the at least one session of the network service comprises at least one quality of service QoS flow of the network service, a single QoS flow of the at least one QoS flow of the network service having a minimum granularity of QoS differentiation among the sessions of the at least one session of the network service, Traffic in a same QoS flow of the at least one QoS flow of the network service receives the same data forwarding treatment and data processing treatment.

19. The method according to claim 18, wherein The parameters of the data processing and disposal include one or more of the following: data processing scheduling strategy, data calculation accuracy, data calculation delay, AI model type, AI model privacy level, AI model accuracy level, AI training method, AI reasoning method, privacy protection method, data management strategy, data purification strategy, data compression strategy, data embedding strategy, data representation learning strategy, data feature extraction strategy, data preprocessing strategy, privacy level, data storage time, data processing strategy, data cleaning strategy, data normalization strategy, data quality level and data processing priority.

20. The method according to claim 18 or 19, characterized in that, The parameters of the data forwarding handling parameters include one or more of the following: data transmission resource scheduling strategy, data queue management strategy, data transmission priority level, link layer protocol configuration, access threshold, data loss rate, data transmission delay, data forwarding security protection method and security level.

21. The method according to any one of claims 7, 8 or 13, characterized in that, The at least one XDB is used to serve only the UE, and the at least one XDB is also used to transmit a PF protocol sublayer PDU to the UE and receive a PF protocol sublayer PDU from the UE through a wireless interface.

22. The method according to claim 21, wherein The UE is configured with the at least one XDB.

23. The method according to claim 21 or 22, characterized in that: One or more PF entities in the at least one XDB are connected to one or more PDCP entities, and the one or more PDCP entities are dedicated to the UE.

24. The method according to claim 21 or 22, characterized in that, The at least one XDB of the UE is mapped to one or more DRBs of the same UE.

25. The method according to claim 17 or 18, characterized in that The at least one session of the network service is mapped by the SDAP entity to the at least one XDB dedicated to the UE.

26. The method according to claim 18, wherein At least one QoS flow of at least one session of the network service is mapped by the SDAP entity to at least one XDB dedicated to the UE.

27. The method according to any one of claims 7, 8 or 13, characterized in that, The at least one XDB is for a group of UEs including the UE, to transmit at least one PF protocol sublayer PDU to the group of UEs and receive the at least one PF protocol sublayer PDU from the group of UEs.

28. The method according to claim 27, characterized in that, The at least one XDB uses one of a broadcast method and a multicast method to transmit a copy of the at least one PF protocol sublayer PDU to the group of UEs via a radio interface.

29. The method according to claim 27, wherein The UE in the group of UEs is configured with the at least one XDB.

30. The method according to claim 27 or 28, characterized in that, At least one PF entity in the at least one XDB for the group of UEs is connected to at least one PDCP entity for the group of UEs.

31. The method according to claim 30, wherein The at least one PDCP entity is for a multimedia broadcast multicast service (MBMS) point-to-multipoint radio bearer.

32. The method according to claim 30, wherein The at least one PDCP entity is for a point-to-multipoint radio bearer.

33. The method according to claim 27 or 28, characterized in that, At least one session of the network service is mapped by the SDAP entity to the at least one XDB of the group of UEs.

34. The method according to claim 18, wherein At least one QoS flow of at least one session of the network service is mapped by the SDAP entity to the at least one XDB of a group of UEs including the UE.

35. The method according to claim 27, wherein The at least one XDB transmits via a radio interface to different UEs in the group of UEs: Different PF protocol sublayer PDUs; or Separate copies of PF protocol sublayer PDUs.

36. The method according to claim 35, wherein The group of UEs is configured with the at least one XDB.

37. The method according to claim 35 or 36, characterized in that, At least one PF entity in the at least one XDB for the group of UEs is connected to at least one PDCP entity.

38. The method according to claim 37, wherein Any one of the at least one PDCP entity is for at least one UE in the group of UEs.

39. The method according to claim 38, wherein Any one of the at least one PDCP entity is connected to at least one RLC entity.

40. The method according to claim 37 or 38, characterized in that, Any one of the at least one PDCP entity is for one or more of the following: DRB, multicast / broadcast service radio bearer, and point-to-multipoint radio bearer.

41. The method according to claim 35 or 36, characterized in that, At least one session of the network service is mapped by the SDAP entity to the at least one XDB of the group of UEs.

42. The method according to claim 35 or 36, characterized in that, At least one QoS flow of at least one session of the network service is mapped by the SDAP entity in the SDAP sublayer to the at least one XDB of the group of UEs.

43. The method according to any one of claims 6 to 8 or 10 to 42, characterized in that, The PF protocol sublayer includes a PF entity, and the PF entity includes one or more of the following: a data buffer component, a data processing component, a routing component, and a data transmission component.

44. The method according to claim 43, wherein The data buffer component is for performing one or more of the following: storing data, caching data, and accumulating data for the data processing component to perform data processing.

45. The method according to claim 43 or 44, characterized in that, The data processing component is used to perform data processing using one or more of the following various methods: data analysis, AI training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

46. The method according to any one of claims 43 to 45, characterized in that The routing component of the PF entity is used to add routing information to the header of the PF PDU to help another PF entity determine a routing action, or to determine the routing action of the PF entity based on the routing information included in the header of the PF PDU.

47. The method according to claim 46, characterized in that, The routing action of the PF entity or the routing action of the other PF entity includes one or more of the following: stopping data transmission, transmitting data to a PF entity residing on the same node as the PF entity, transmitting data to a PF entity residing on the same node as the other PF entity, transmitting data to a PF entity of a peer node, transmitting data to an entity of an upper layer, or transmitting data to an entity of a lower layer, where the data includes one or more of the following: the PF SDU included in the PF PDU, a processed version of the PF SDU included in the PF PDU, a constructed PF PDU including the PF SDU included in the PF PDU, or a constructed PF PDU including a processed version of the PF SDU included in the PF PDU.

48. The method according to any one of claims 43 to 47, characterized in that, The data transmission component is used to perform one or more of the following for the data: mapping or transmitting the data to a corresponding transmission tunnel or channel; sequentially numbering the data; sequentially transmitting the data to the PF protocol sublayer, the upper layer, or the lower layer.

49. The method according to any one of claims 43 to 48, characterized in that, The PF entity performs one or more of the following: Receiving or transmitting at least one PF SDU from or to the following: The upper layer; The lower layer; Another PF entity; Submitting or receiving at least one PF PDU to or from the following: The lower layer, or Another PF entity.

50. The method according to claim 49, wherein, The at least one PF PDU includes one or more of the following: a message header and a PF SDU.

51. The method according to claim 50, wherein, One PF PDU in the at least one PF PDU includes a message header indicating one or more of the following: the type of the network service to which the one PF PDU belongs, the sequence number of the one PF PDU, an indication to further process the one PF SDU included in the one PF PDU, the type of data processing of the one PF SDU included in the one PF PDU, an indication to directly forward the PF SDU included in the one PF PDU, routing information, and the network service QFI identifying the QoS flow to which the one PF PDU belongs.

52. The method according to claim 51, characterized in that, The types of the data processing include one or more methods among the following: data analysis, AI training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

53. The method according to claim 51 or 52, wherein: The routing information indicates the destination to which the PF entity receiving the PF PDU transfers the data, and the data includes one or more of the following: the PF SDU included in the PF PDU, the processed version of the PF SDU included in the PF PDU, the constructed PF PDU including the PF SDU included in the PF PDU, or the constructed PF PDU including the processed version of the PF SDU included in the PF PDU; The destination is one or more of the following: the PF entity, another PF entity residing on the same node as the PF entity, another PF entity of a peer node, an entity of an upper layer, and an entity of a lower layer.

54. The method according to any one of claims 49 to 53, wherein: Retrieving the at least one SDU from the at least one PDU includes: the PF entity retrieving the at least one PF SDU from the at least one PF PDU; Retrieving the at least one PF SDU from the at least one PF PDU includes: deleting one or more headers included in the at least one PF PDU.

55. The method according to claim 54, wherein: Constructing the at least one additional PDU is performed by the PF entity after retrieving the at least one PF SDU from the at least one PF PDU; The constructing the at least one additional PDU includes one or more of the following: parsing and processing the raw data encapsulated in one or more payloads of the at least one PF SDU using one or more methods among the following: data analysis, AI training, AI inference, data privacy protection, data purification, data processing, data management, data cleaning, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

56. The method according to any one of claims 5, 7, 8, 13, 15 or 17 to 55, wherein, Defining, reserving or configuring a dedicated type of one or more of the following for the at least one XDB of the network service: an associated DRB, an associated RLC channel, a logical channel, a transport channel, and a physical channel; Allocating dedicated physical radio resources for the at least one XDB of the network service.

57. The method according to claim 56, wherein The at least one XDB and the associated DRB are configured with the same MAC entity of the associated MAC sublayer to multiplex the relevant radio resources.

58. The method according to claim 56 or 57, characterized in that, The at least one XDB is configured by a dedicated signaling message for the network service or a Radio Resource Control (RRC) message for the network service.

59. The method according to claim 58, characterized in that, The dedicated signaling message for the network service is sent by a control entity of a control protocol layer above an associated PDCP sublayer via a signaling radio bearer between the RAN node and the UE.

60. The method according to claim 59, wherein, The PF entity includes one or more of a transmitting part and a receiving part, and each of the transmitting part and the receiving part performs one or more functions of the PF entity.

61. The method according to claim 60, wherein, The PF protocol sublayer is configured at one or more of the RAN node and the UE node, and when the RAN node performs data forwarding, the PF protocol sublayer operates in transparent mode.

62. The method according to claim 60, wherein: The PF protocol sublayer is configured at the RAN node and the UE, and no session tunnel is configured between the RAN node and the CNF; The network service involves the RAN node and the UE and does not involve the CNF.

63. The method according to claim 60, wherein: The PF protocol sublayer is configured at the RAN node, and no SDAP sublayer, radio L2 sublayer, and PHY layer are configured at the RAN node; The network service involves the RAN node and the CNF and does not involve the UE.

64. The method according to claim 60, wherein: A sublayer including the SDAP sublayer, the PF protocol sublayer, the associated PDCP sublayer, the associated RLC sublayer, the associated MAC sublayer, and the associated PHY layer is configured at the RAN node and the UE; When the network service involves the RAN node, the UE, and the CNF, a session tunnel is configured between the CNF and the RAN node.

65. The method according to claim 64, wherein The RAN node, the UE, and the CNF are configured without an SDAP sublayer; the traffic granularity of the QoS flow of the network service is the same as the traffic granularity of the at least one XDB.

66. The method according to claim 64 or 65, characterized in that, A CNF PF entity is configured in an associated PF protocol layer at the CNF, where the CNF PF entity performs at least one function of a RAN PF entity at the RAN node and a UE PF entity at the UE.

67. The method according to any one of claims 64 to 66, characterized in that, The PF protocol sublayer is deployed in one of the following: above the PDCP sublayer, between the SDAP sublayer and the PDCP sublayer, between the PDCP sublayer and the RLC sublayer, between the RLC sublayer and the MAC sublayer, between the MAC sublayer and the PHY layer, above the SDAP sublayer, above the PDU layer, above the GTP-U layer, above the UDP layer, above the IP layer, above the QUIC layer, above the Hypertext Transfer Protocol HTTP layer, above the Segment Routing over IPv6 SRv6 layer, within the PDU layer, within the SDAP sublayer, within the PDCP sublayer, within the RLC sublayer, within the MAC sublayer, within the PHY layer, within the GTP-U layer, within the UDP layer, within the IP layer, within the application layer, within the HTTP layer, within the SRv6 layer, and within the QUIC layer.

68. The method according to any one of claims 5, 7, 8, 13, 15 or 17 to 67, characterized in that, Traffic in the same XDB of the at least one SDB receives the same data forwarding handling and data processing handling, where one or more data processing handling parameters and data forwarding handling parameters are configured per each XDB of the at least one XDB.

69. The method according to claim 1, characterized in that, The first device is a RAN node and the second device is a CNF.

70. The method according to claim 1, characterized in that, The first device is a CNF and the second device is a RAN node.

71. The method according to claim 1, wherein The first device is a CNF and the second device is a UE.

72. The method according to claim 1, characterized in that, The first device is a UE and the second device is a CNF.

73. A device, characterized in that, Comprising: a memory for storing instructions; a processor for executing the instructions stored in the memory, and when the instructions stored in the memory are executed, the processor is for the method according to any one of claims 1 to 72.

Images