Control plane and user plane subnet technology

Abstract

The invention relates to control plane and user plane subnet technology. The application relates to devices and components including apparatuses, systems, and methods for employing subnets to communicate with cellular networks.

Description

Technical Field

[0001] The present application relates to the field of wireless technology, and in particular to control plane and user plane subnet technologies. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) define the air interface for the radio access network. These 3GPP TSs specify that the base station controls the resource management, admission control, mobility, and scheduling that occur within the radio access network. While centralized control of the air interface provides some advantages, it also reduces deployment flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1 A network environment according to some embodiments is illustrated.

[0004] Figure 2 A network environment and corresponding protocol configuration according to some embodiments are illustrated.

[0005] Figure 3 A network environment and corresponding protocol configuration according to some embodiments are illustrated.

[0006] Figure 4 A network environment and corresponding protocol configuration according to some embodiments are illustrated.

[0007] Figure 5 A network environment and corresponding protocol configuration according to some embodiments are illustrated.

[0008] Figure 6 Protocol configurations according to some embodiments are illustrated.

[0009] Figure 7 Protocol configurations according to some embodiments are illustrated.

[0010] Figure 8 Protocol configurations according to some embodiments are illustrated.

[0011] Fig. 9 Protocol configurations according to some embodiments are illustrated.

[0012] Fig.10 Protocol configurations according to some embodiments are illustrated.

[0013] Fig.11 Protocol configurations according to some embodiments are illustrated.

[0014] Fig.12 Protocol configurations according to some embodiments are illustrated.

[0015] Fig.13 A protocol header according to some embodiments is illustrated.

[0016] Fig.14 is an operational flow / algorithm structure according to some implementation schemes.

[0017] Fig.15 is another operational flow / algorithm structure according to some embodiments.

[0018] Fig.16 is an example UE according to some embodiments.

[0019] Fig.17 is an example base station according to some embodiments. DETAILED DESCRIPTION

[0020] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration rather than limitation, so as to provide a thorough understanding of various aspects of various embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the descriptions of various embodiments due to unnecessary details. For the purposes of this document, the phrases "A / B" and "A or B" refer to (A), (B), or (A and B); the phrase "(A) B" refers to (B) or (A and B), i.e., A is optional; and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0021] The following is a glossary of terms that may be used in this disclosure.

[0022] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0023] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0024] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0025] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0026] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0027] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0028] As used herein, the term "channel" refers to any tangible or intangible transmission medium for communicating data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is communicated. In addition, as used herein, the term "link" refers to a connection made between two devices for sending and receiving information.

[0029] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0030] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0031] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0032] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0033] As wireless networks evolve to the sixth generation (6G) and beyond, new immersive services and a wide range of applications with different latency, jitter, and throughput requirements can be expected. These networks can support a variety of services such as extended reality (XR), vehicle-to-everything (V2X) communications, sensing, etc. In addition, new types of devices with limited computing power or extreme battery constraints can be envisioned, which may require additional computing support.

[0034] Local networks or "subnets" can be used to enable communication between local devices and enhance performance or power savings on low-capability devices. Some potential use cases include in-plant subnets (e.g., collaborative robots in industrial environments), in-vehicle subnets (e.g., wireless interconnection of sensors / components to avoid wiring), in-body subnets (e.g., healthcare applications), and indoor subnets (e.g., entertainment / education applications)

[0035] Co-located devices can create subnets to achieve different aspects. Quality of service (QoS) can be improved when co-located devices create subnets to achieve higher data rates, lower latency, or better reliability (e.g., lower block error rate (BER)). Power savings can be achieved through subnets that enable local devices to reduce power consumption. Local communications can be enabled by co-located devices that create subnets to exchange data locally within the subnet (e.g., exchange collected metrics or make local calls). Subnets can enable co-located devices that share computing power with each other through subnets to use distributed computing. This can be beneficial when a device cannot offload its computation to an edge server (e.g., due to limited latency, power consumption, operator support, privacy, etc.). Co-located devices can create subnets to improve mobility performance (e.g., provide better mobility decisions). Co-located devices can create subnets to extend cellular coverage. This can provide access to a wider cellular network to co-located UEs that are out of coverage. Co-located devices can create subnets to enable new devices with limited computing power or extreme battery constraints to support simplified versions of the control and user planes.

[0036] In some cases, some goals of creating a subnet may conflict with other goals. For example, improving QoS may conflict with power saving. Therefore, in order to achieve these different goals, different deployment options may be expected for the design of the entire network / subnet architecture. The embodiments of the present disclosure describe a subnet architecture for both the control plane and the user plane to achieve deployment flexibility. The embodiments describe a control plane (CP) and user plane (UP) architecture that allows one or more nodes of a subnet to communicate with a node of a radio access network (RAN) in a manner similar to the current 3GPP New Radio (NR) CP / UP architecture. The embodiments also describe a subnet control plane (snCP), which represents a simplified and independent CP architecture with significantly reduced complexity compared to the current NR CP architecture. This may include, for example, more streamlined information elements (IEs) for simplified protocol stack logic and different processes. The embodiments also describe a subnet user plane (snUP), which represents a simplified and independent UP architecture with significantly reduced complexity and enhanced flexibility compared to the current NR UP architecture. This may include, for example, reduction and merging of different UP layer 2 (L2) layers.

[0037] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include a base station 108 that provides one or more serving cells with which a user equipment (UE) may communicate using a cellular network. The base station 108 may be part of a RAN coupled to a core network (CN) 112. The RAN and CN 116 may be generally referred to as a network (NW) 114.

[0038] The UE and the base station 108 may communicate over an air interface compatible with fifth generation (5G), 6G (or later) system standards as provided by the 3GPP technical specifications.

[0039] The network environment 100 may include a management node (MN) 104 communicatively coupled with a base station 108 via a physical connection provided by a serving cell of the base station 108. The MN 104 may be a UE that provides a coordination role within the subnet 106.

[0040] Subnet 106 may include multiple UEs coupled to MN 104. For example, subnet 106 may include UE 1, UE 2, and UE 3. Each of these UEs may include a physical connection with MN 104 and a virtual connection with BS 108. Network environment 100 may also include UE 4 having a physical connection with base station 108.

[0041] As used herein, a physical connection may refer to a direct wireless connection between two devices at the physical layer of a network protocol stack. As used herein, a virtual connection may refer to a logical link between two devices. The logical link may include a connection at a layer above the physical layer of a network protocol stack.

[0042] Subnet 106 can be controlled by MN 104 independently of a wider network (e.g., a RAN controlled by base station 108 or CN 112). For example, subnet 106 can utilize technology independent of RAN technology. Subnet 106 can use licensed or unlicensed spectrum, with resources authorized, scheduled, or otherwise controlled by MN 104, independent of direct control by base station 108.

[0043] MN 104 can form a subnet 106 for UEs without (or with limited) configuration or knowledge by base station 108. Base station 108 can communicate with MN 104 via a physical connection, and can logically communicate with UEs of subnet 106 via a virtual connection. In some embodiments, the subnet topology and mobility within subnet 106 can be transparent to the wider network (e.g., base station 108), which can reduce the complexity of the wider network. MN 104 can control various aspects of subnet 106, including, for example, routing and resource management. MN 104 can provide quality of service (QoS) with reliable end-to-end (E2E) links. This can be achieved by utilizing a fair scheduling mechanism for all UEs across subnet 106 and relative to other UEs of network environment 100.

[0044] The CP and UP aspects of the subnet 106 can facilitate flexible and efficient communication of the components of the subnet 106. For example, the CP entity can be flexibly deployed on the MN 104 or the local device, and can be transferred between subnet nodes. These deployments can be transparent to the wider network. Regarding the UP aspect, the higher layers can be terminated at the local device (e.g., protocol data unit (PDU) session / Internet protocol (IP) address), and the lower layers can be terminated at the MN 104 or other subnet nodes and can be subnet-specific within the subnet 106 according to the technology used (e.g., licensed vs. unlicensed, device-to-device (D2D), etc.).

[0045] In some embodiments, the UE may be associated with a wider network. For example, the UEs of subnet 106 may remain registered with the wider network and have some aspects managed by base station 108. For example, base station 108 may include a UE context and may control resource and mobility decisions with respect to the wider network (e.g., handovers between base stations such as a cellular network).

[0046] In some embodiments, the UE may be able to move seamlessly between the subnet 106 and a wider network controlled by the base station 108. For example, the network environment 100 may include a UE 4 that is able to transition into and out of the subnet 106.

[0047] MN 104 may cooperate with base station 108 to establish subnet 106. MN 104 and base station 108 may each include a MN interface configuration to facilitate establishment of subnet 106 and downlink / uplink signaling.

[0048] The first aspect of the present disclosure describes snCP. Figure 2 In the first option described, the subnet UE routes CP traffic through the subnet 206 in a manner transparent to the wider network. Figure 3 In the second option described, CP traffic may be aggregated at the CP layer at the MN 204. Figure 4 In the third option described, the CP traffic of one subnet UE may be offloaded to the CP layer at another subnet UE.

[0049] Figure 2 A network environment 100 and a corresponding protocol configuration 200 with respect to a UE 3 according to some embodiments are illustrated.

[0050] The protocol configuration includes a CP layer at the base station 108 coupled to the CP layer at the UE 3. Thus, the UE CP is terminated at the UE 3. The CP layer, which may also be referred to as a network CP (nwCP) layer to distinguish it from the snCP layer, may communicate CP data from the network 114 to the UE 3 and vice versa. The MN 104 may transparently forward the CP data to the network 114 or the UE 3.

[0051] In the network 114, the nwCP layer may include a plurality of sublayers placed on the base station 108 or the CN 112. For example, the base station 108 may include a packet data convergence protocol (PDCP), a radio link control (RLC), a medium access control (MAC), and a radio resource control (RRC) sublayer, and the CN 112 may include, for example, a non-access stratum (NAS) sublayer at an access and mobility management function (AMF). The nwCP layer of the UE 3 may have sublayers corresponding to those of the network 114.

[0052] In short, the RRC sublayer can be used to control: the transmission of system and paging information; RRC connection; security, mobility and QoS management functions; signaling radio bearers (SRBs) and data radio bearers (DRBs); link measurements; and radio link failures. The MAC sublayer can manage scheduling / priority handling, (de)multiplexing and HARQ processes between logical channels and transport channels. The RLC sublayer can manage (re)segmentation and error correction through automatic repeat requests (ARQ) between logical channels and RLC channels. The PDCP sublayer can manage robust header (de)compression and security between radio bearers and RLC channels. The NAS sublayer can perform operations such as authentication, mobility management and security control.

[0053] Unless otherwise described herein, the MAC, RLC, and PDCP sublayers may perform CP functions similar to those described in clause 6 of 3GPP TS 38.300 v17.5.0 (2023-06-30), the RRC sublayer may perform CP functions similar to those described in clause 7 of 3GPP TS 38.300, and the NAS sublayer may perform CP functions similar to those described in 3GPP TS 23.501 v18.2.2 (2023-07-07).

[0054] The protocol configuration 200 may also include a snCP layer at the MN 104 coupled to the snCP layer at the UE 3. The snCP layer may be used to communicate CP messages dedicated to managing communications within the subnet. The snCP layer may include sublayers similar to one or more of the sublayers described above with respect to the nwCP, except from the perspective of the subnet 106 instead of the NW 114. The snCP signaling between the snCP layers at the MN 104 and the UE 3 may be transparent to the NW 114.

[0055] The protocol configuration 200 may also include an L2 layer and a physical (PHY) layer at the MN 104 coupled to the L2 layer and the PHY layer at the NW 114, respectively. These L2 layers may be used to send UP traffic over the access network. The UP traffic may be sent over a local link (e.g., a wireless local area network (WLAN) link) via snUP as described elsewhere herein.

[0056] Figure 3 A network environment 100 and a corresponding protocol configuration 300 with respect to a UE 3 according to some embodiments are illustrated.

[0057] The protocol configuration 300 includes an nwCP layer at the network 114 coupled to an nwCP layer at the MN 104. Thus, the UE 3 nwCP is terminated at the MN 104. In this way, the UE 3 can offload its nwCP operations (or portions thereof) to the MN 104.

[0058] MN 104 may also have a snCP layer coupled with the snCP layer of UE 3. The snCP may be transparent to network 114 and may overlay the functionality of subnet 106. MN 104 and UE 3 may communicate nwCP information that needs to be delivered to or originated from UE 3 using snCP signaling.

[0059] The nwCP and snCP layers can be compared with the above Figure 2 The description is similar.

[0060] The protocol configuration 300 may also include an L2 layer and a PHY layer at the MN 104 coupled to the L2 layer and the PHY layer at the NW 114, respectively. These L2 layers may be used to send UP traffic over the access network. The UP traffic may be sent over a local link (e.g., a WLAN link) via snUP as described elsewhere herein.

[0061] Figure 4 A network environment 100 and a corresponding protocol configuration 400 with respect to a UE 3 according to some embodiments are illustrated.

[0062] Protocol configuration 400 includes an nwCP layer at network 114 coupled to an nwCP layer at UE 2. Thus, UE 3 nwCP terminates at UE 2. In this way, UE 3 may offload its nwCP operations (or portions thereof) to UE 2, which may operate in a supporting role.

[0063] In this embodiment, the base station 108 can communicate with UE 3 via a virtual connection. In the downlink, UE 3 can transparently forward the nwCP message to UE 2. The nwCP layer at UE 2 can decode the nwCP message. The snCP layer at UE 2 can then forward the relevant information to the snCP layer at UE 3 coupled thereto. The transmission of CP information in the uplink can work in a similar manner in the opposite direction.

[0064] Unless otherwise described, the nwCP and snCP layers can be the same as described above for Figure 2 The description is similar.

[0065] The protocol configuration 400 may also include an L2 layer and a PHY layer at the MN 104, respectively coupled to the L2 layer and the PHY layer at the NW 114. These L2 layers may be used to send UP traffic over the access network.

[0066] UP traffic may be sent over a local link (eg, a WLAN link) between MN 104, UE 3, and UE 2 via snUP as described elsewhere herein.

[0067] Figure 5Portions of a network environment 100 and a corresponding protocol configuration 500 with respect to a UE 3 are illustrated according to some embodiments.

[0068] Protocol configuration 500 may include UE 3 offloading nwCP operations (or portions thereof) to UE 2 in a manner similar to protocol configuration 400. However, in this embodiment, MN 104 is not involved, and base station 108 has a direct connection with UE 3. Communications between the nwCP layer at network 114 and the nwCP layer at UE 2, and between the snCP layer at UE 2 and the snCP layer at UE 3 may be similar to those described with respect to FIG. Figure 4 The communication described.

[0069] Figure 6 The protocol configuration 600 of the snUP with flexible and transparent layer deployment of RAN terminating protocol entities according to the second aspect of the present disclosure is illustrated. The protocol configuration 600 may describe components of a user plane protocol stack distributed throughout the devices of the network environment 100.

[0070] The protocol configuration 600 may include a transport / application (T / A) layer (eg, Transmit Control Protocol (TCP), etc.) of UE 1 coupled to a T / A layer of another device 604 (eg, server, UE, etc.) with which UE 1 is communicating.

[0071] Protocol configuration 600 may also include an IP layer at a user plane function (UPF), which may be located in CN 112, coupled with corresponding IP layers in UE 1 and device 604. The IP layer may be used to transmit IP packets across network boundaries using IP addresses in packet headers.

[0072] The protocol configuration 600 may also include a service data adaptation protocol (SDAP) sublayer on the base station 108 coupled to a SDAP sublayer on the subnet UE. The SDAP sublayer may provide mapping between QoS flows and data radio bearers (DRBs) and may mark QoS flow IDs (QFIs) in uplink and downlink packets.

[0073] The protocol configuration 600 may also include a PDCP sublayer on the base station 108 coupled to a PDCP sublayer on the subnet UE. The PDCP sublayer may handle, for example, data transfer, PDCP sequence numbers, header (de)compression, (de)ciphering, integrity checking, in-order delivery of packets, etc.

[0074] The protocol configuration 600 may also include an RLC sublayer on the base station 108 coupled to an RLC sublayer on the subnet UE. The RLC sublayer may handle, for example, upper layer PDU delivery, sequence numbering, error correction, (re)segmentation, service data unit (SDU) reassembly / discarding, etc.

[0075] The protocol configuration 600 may also include a MAC sublayer on the base station 108 coupled to the MAC sublayer on the MN 104. The MAC sublayer may handle, for example, mapping between logical channels and transport channels, (de)multiplexing MAC SDUs, hybrid automatic repeat request (HARQ) transmissions, priority handling, etc.

[0076] Unless otherwise described herein, SDAP, PDCP, RLC, and MAC may perform Layer 2 (L2) user plane functions, such as described in clause 6 of 3GPP TS 38.300.

[0077] The subnet endpoints for RAN-terminated UP protocols (e.g., SDAP, PDCP, or RLC) may be dynamically configured on different subnet UEs based on the goals of a particular implementation. This may be controlled by MN 104 and agreed upon within subnet 106 without any involvement from network 114. Thus, the deployment of the L2 sublayer within subnet 106 may be transparent to base station 108.

[0078] The independent / transparent nature of the L2 sublayer deployment enables different subnet solutions that may only involve alignment between subnet UEs. No additional agreement / negotiation with the network 114 is required.

[0079] A number of factors may be weighted when determining the most desirable agreement within the subnet 106. For example, depending on the subnet technology used, RLC signaling may be used to cover more than a cellular link interface on the Uu. Thus, the RLC reestablishment process may be used to cover a path through a subnet that includes one or more local links.

[0080] Depending on the capabilities of the specific technology and the local link, different deployments may be preferred. For example, if, for example, the intermediate node is not trusted or the L2 does not provide sufficient security, some subnet UEs may want to rely on E2E PDCP encryption for privacy reasons. Such subnet UEs may agree with MN 104 to host the PDCP / SDAP sublayer. For another example, some subnet UEs may have a higher level of trust between each other, or the lower / higher layers may provide strong encryption, and those subnet UEs may want to offload PDCP encryption to MN 104. As another example, some subnet UEs may have restrictive latency requirements (e.g., using a low-latency guaranteed bit rate bearer) and may want to terminate SDAP on the subnet UE in order to perform appropriate mapping. Other subnet UEs may have more relaxed latency requirements (e.g., only best-effort traffic without specific prioritization or mapping to different bearers), so SDAP functionality may not be required at the UE.

[0081] In case of RAN terminating UP protocol, devices other than the target located in subnet 106 (e.g. Figure 6In terms of UE 1), a subnet routing protocol (SN-RP) layer can be placed on the device and the target to forward relevant information to the target. The SN-RP layer can deliver the route through the subnet 106 by, for example, generating an SN-RP packet with route-related information. The SN-RP can carry in-band mapping information for each packet. This mapping information can be used to perform the next mapping step.

[0082] Figures 7 to 12 Examples of various deployments of RAN terminating protocol entities within the subnet 106 according to some embodiments are provided. These examples illustrate how different sublayers within the snUP can be flexibly deployed to exploit different link characteristics and UE capabilities. This enables a wide range of use cases.

[0083] Figure 7 A protocol configuration 700 with an SN-RP layer placed below the IP layer on the UE 1 is illustrated according to some embodiments.

[0084] The IP / PDU session may be terminated at UE 1, which may maintain QoS flow filtering per PDU session. At the PDU session level, packets may be filtered and associated with certain QoS flows at UE 1 before being provided to SDAP on MN 104 to perform QoS flow to RB mapping.

[0085] The protocol configuration 700 may include a RAN-terminated UP protocol that terminates at the MN 104. For example, the MN 104 may include SDAP, PDCP, RLC, and MAC sublayers coupled to the corresponding sublayers in the base station 108. The MN 104 may include an SN-RP layer that may be used to route / receive information to / from the SN-RP layer of the UE 1. As shown, routing may be performed via an intermediate UE (e.g., UE 2) that includes an SN-RP layer coupled to the SN-RP layers in the MN 104 and the UE 1. In other embodiments, routing may be performed via multiple intermediate UEs, or the MN 104 may have a direct connection with the UE 1. Each of the MN 104, the UE 2, and the UE 1 may have an L1 / L2 layer (e.g., PHY, MAC, or RLC) that enables direct connection to each other via a technology-specific local link. For example, the local link technology may be a WLAN technology, a wireless personal area network (WPAN) technology, a sidelink technology, etc.

[0086] The protocol configuration 700 may perform uplink communication as follows. UE 1 may assign a QoS flow ID by applying a PDU session QoS filtering rule. The SN-RP layer of UE 1 may mark the SN-RP packet to identify the QoS flow or SRB ID. For example, the header of the SN-RP packet may include a UE ID (e.g., a source UE ID for identifying a packet originator along a path within a subnet); and a PDU session ID together with a QoS flow ID or SRB ID. SN-RP signaling may carry packets to MN 104 via subnet 106. Nodes within the subnet may use routing / priority policies based on SN-RP information elements. For example, an SRB may take precedence over a QoS flow, or vice versa. Upon receiving the SN-RP packet, the SN-RP layer at MN 104 may use the UE ID and the PDU session ID to perform mapping to the SDAP sublayer. The SDAP sublayer may use the QoS flow ID to map the user data carried in the SN-RP packet to the appropriate DRB / PDCP entity.

[0087] The protocol configuration 700 may perform uplink communication as follows. The MN 104 may receive packets from an access network (e.g., base station 108) via a Uu interface. The SN-RP layer of the MN 104 may generate an SN-RP packet marked with information carried in the SN-RP. For example, the SN-RP layer of the MN 104 may mark the SN-RP packet to identify a QoS flow or an SRB ID. For example, the header of the SN-RP packet may include: a UE ID (associated with UE 1); and a PDU session ID together with a QoS flow ID or an SRB ID. SN-RP signaling may carry packets to UE 1 via subnet 106. Nodes within the subnet may use routing / priority policies based on SN-RP information elements. For example, an SRB may take precedence over a QoS flow, or vice versa.

[0088] Figure 8 A protocol configuration 800 with an SN-RP layer placed just below the IP layer on the UE 1 is illustrated according to some embodiments.

[0089] The IP / PDU session may be terminated at UE 1 which may maintain QoS flow filtering per PDU session.

[0090] Protocol configuration 800 may include some RAN-terminated UP protocols terminated at MN 104 and other RAN-terminated UP protocols terminated at an intermediate node (e.g., UE 2). For example, UE 2 may include SDAP and PDCP sublayers, while MN 104 includes RLC and MAC sublayers. MN 104 may include an SN-RP layer coupled to the SN-RP layer of UE 2, and UE 2 may include an additional SN-RP layer coupled to the SN-RP layer of UE 1.

[0091] The protocol configuration 800 may perform uplink communication as follows. UE 1 may assign a QoS flow ID by applying a PDU session QoS filtering rule. The SN-RP layer of UE 1 may generate an SN-RP packet tagged with information for identifying a QoS flow and an SRB ID. For example, the SN-RP packet may include a UE ID (e.g., a source UE ID for identifying a packet originator along a path within a subnet); and a PDU session ID together with a QoS flow ID or an SRB ID. SN-RP signaling may carry packets to UE 2 via subnet 106. UE 2 may be configured to perform security measures on behalf of UE 1. For example, the SN-RP layer of UE 2 may perform a mapping to SDAP using the UE ID and the PDU session ID. The SDAP layer of UE 2 may identify the correct PDCP entity using a mapping of a QoS flow ID to a DRB. Another SN-RP layer of UE 2 may generate an SN-RP packet tagged with information for identifying a radio bearer (RB). For example, the SN-RP packet may include a UE ID (associated with a subnet target of the packet, e.g., MN 104) and an RB ID. The SN-RP also carries packets to the MN 104 through the subnet 106. The MN 104 can then use the UE ID and RB ID for RB to RLC mapping.

[0092] The protocol configuration 800 may perform downlink communications as follows. The MN 104 may receive packets via an access network (e.g., base station 108) via a Uu interface. The SN-RP layer of the MN 104 may generate an SN-RP packet marked with information to be carried by the SN-RP. For example, the packet may include a UE ID (associated with the subnet target of the packet, e.g., UE 2) and an RB ID. SN-RP signaling may carry the packet to the UE 2 via the subnet 106. Nodes within the subnet may use routing / priority policies based on SN-RP information elements (e.g., prioritizing SRBs over QoS flows, or vice versa). UE 2 may perform security measures on behalf of UE 1. The SN-RP layer of UE 2 may map the packet to an appropriate PDCP entity based on the UE ID and DRB ID, and the PDCP / SDAP sublayer may perform PDCP / SDAP functionality. The other SN-RP layers of UE 2 may generate SN-RP packets tagged with information carried in the SN-RP, such as the UE ID (associated with the subnet destination of the packet, e.g., UE 1); and the PDU session ID along with the QoS flow ID or SRB ID. The SN-RP signaling may carry the packet over subnet 106 to UE 1, which may then perform IP / T / A functions.

[0093] Fig. 9A protocol configuration 900 with an SN-RP layer placed just below the SDAP layer on the UE 1 is illustrated according to some embodiments.

[0094] The IP / PDU session may be terminated at UE 1 which may maintain QoS flow filtering per PDU session.

[0095] The operation of protocol configuration 900 may be similar to the operation described above with respect to protocol configuration 700 or 800. However, protocol configuration 900 may include SDAP terminating at UE 1 (rather than terminating at UE 2 or MN 104), which may allow QoS flow ID mapping to occur at UE 1. Protocol configuration 900 may also include RLC terminating at UE 2 (rather than terminating at MN 104), which may allow RLC ARQ and RLC triggered re-establishment procedures to cover Uu and the local link between UE 2 and MN 104.

[0096] Fig.10 A protocol configuration 1000 with an SN-RP layer placed just below the PDCP sublayer on the UE 1 is illustrated according to some embodiments.

[0097] The operation of protocol configuration 1000 may be similar to the operation described above with respect to protocol configuration 900. However, protocol configuration 1000 may include PDCP termination at UE 1 (rather than at UE 2). This may allow PDCP functionality (e.g., CP / UP data delivery, header compression, ciphering, and integrity protection) to be performed at UE 1.

[0098] Fig.11 A protocol configuration 1100 with an SN-RP layer placed just below the PDCP sublayer on UE 1 is illustrated according to some embodiments.

[0099] The operation of protocol configuration 1100 may be similar to the operation described above with respect to protocol configuration 1000. However, protocol configuration 1100 may include RLC termination at MN 104 (rather than termination at UE 2). This may offload RLC functionality to MN 104 and rely on MN 104 to route through the SN-RP of the subnet to pass relevant information.

[0100] Fig.12 A protocol configuration 1200 with an SN-RP layer placed directly below the RLC sublayer on UE 1 is illustrated according to some embodiments.

[0101] The operation of protocol configuration 1200 may be similar to the operation described above with respect to protocol configuration 1100. However, protocol configuration 1200 may include RLC termination at UE 1 (rather than at MN 104). This may provide RLC functionality at UE 1, while MAC functionality is offloaded to MN 104, which may then route relevant information via the SN-RP of the subnet.

[0102] Fig.13 An SN-RP header 1300 is illustrated that may be used according to some embodiments.

[0103] The SN-RP header 1300 may include a field for a UE ID, which identifies the target subnet node to which the SN-RP packet is to be sent. In some embodiments, the UE ID may be eight bits. However, in other embodiments, the UE ID may be other sizes.

[0104] The SN-RP header 1300 may also include a field for a mapping information type. In some embodiments, the mapping information type may be seven bits. However, in other embodiments, the mapping information type may be other sizes.

[0105] The mapping information type can be a definition of how to interpret the next x Therefore, the SN-RP header 1300 may use a tag (eg, mapping information type) + value (eg, mapping information) scheme to provide a flexible way to convey relevant information for SN-RP signaling.

[0106] Example tag+value pairs include: a mapping information tag of 0x00 may indicate that the mapping information includes PDU session information (e.g., 32-bit PDU session information); a mapping information tag of 0x01 may indicate that the mapping information includes DRB information (e.g., 16-bit DRBID), and a mapping information tag of 0x002 may indicate that the mapping information includes SRB information (e.g., 8-bit SRB ID). In other embodiments, other mappings, information types, and mapping information sizes may be used.

[0107] The size of the Map Info field may be variable and may be specified by the previous Map Info Type.

[0108] An extension bit (E) may be provided after each mapping information type field. A first value of the extension bit (e.g., E=1) may indicate an additional tag-value pair (e.g., an additional mapping information type+mapping information pair). A second value of the extension bit (e.g., UE=0) may mark that the mapping information type plus mapping information pair is the last one in the SN-RP header 1300.

[0109] Providing the snCP and snUP techniques described herein may be associated with a number of benefits compared to integrated access backhaul (IAB) and sidelink (SL) relays. For example, the subnet controlled by the MN may use any technology and licensed / unlicensed spectrum, which may increase flexibility.

[0110] In addition, compared to IAB / SL relay, intra-subnet link scheduling, node configuration, and mobility may not be visible to the global NW. This can increase subnet transparency. For example, Uu layer deployment within a subnet can be completely flexible and transparent to the NW. This can also reduce complexity in the global NW. For example, the base station 108 remains an anchor point for the UE and schedules the UE behind the MN 104 in the same way as if the UE was directly connected to the BS 108. For another example, the subnet 106 is not controlled by the global NW, and therefore, the internals can be transparent. Topology changes in the subnet do not need to involve the global NW, with the possible exception of inter-MN mobility or UE entering / leaving the subnet 106.

[0111] In some embodiments, MN controlled subnets move subnet formation / control towards the UE. In these embodiments, the use case may change from a network operator owned use case to a UE / subscriber owned use case.

[0112] Compared to IAB / SL relay, the QoS of the MN-controlled subnet can be managed by the base station from outside the subnet without full control of the subnet. In IAB, the base station handles the aggregated traffic from its child IAB nodes and configures and controls all IAB nodes along the path. In SL relay, the base station schedules PC5 links along the path (mode 1), or UEs communicate autonomously in a D2D manner (mode 2), and there is no MN-controlled subnet.

[0113] In the subnet controlled by the MN, the base stations of the RAN can maintain E2E QoS for each UE and each UE's LC. This can be done by scheduling UEs individually while abstracting the subnet characteristics (e.g., bandwidth limitations and latency / scheduling constraints) to the wider network.

[0114] Fig.14 It is an operation flow / algorithm structure 1400 according to some embodiments. For example, the operation flow / algorithm structure 1400 may be executed by a subnet UE (such as MN 104, UE 1, UE 2, UE 3, UE 1600) or a component thereof (eg, processor 1604).

[0115] The operation flow / algorithm structure 1400 may include: at 1404, performing control plane signaling with a node of the subnet. The node may be a MN of the subnet or a subnet UE. The control plane signaling may be snCP signaling performed by a snCP layer of a UE implementing the operation flow / algorithm structure 1400. The implementing UE may be a MN of the subnet or a subnet UE coupled to the MN.

[0116] The operation flow / algorithm structure 1400 may also include data received from or sent to the RAN at 1408. The processed data may be CP data (eg, control signaling) or UP data (eg, user data).

[0117] In some embodiments, in addition to snCP signaling, the operating flow / algorithm structure may include nwCP signaling. The nwCP signaling may be performed by the nwCP layer of the UE implementing the operating flow / algorithm structure 1400 and the nwCP in the network (e.g., a base station or a core network). The snCP signaling may be based on the nwCP signaling, and vice versa. For example, if the UE receives a message via nwCP signaling, it may then use snCP signaling to send the message through the subnet. The message sent by the snCP signaling may include at least some of the information from the message received via the nwCP signaling. Conversely, if the UE receives a message via the snCP signaling, it may then use nwCP signaling to send the message to the network. The message sent by the nwCP signaling may include at least some of the information from the message received via the snCP signaling.

[0118] In some embodiments, the UE may offload a sublayer of the nwCP layer associated with the UE to another node. The other node may be a MN or another subnet UE. When the UE is initially connected to the subnet, the offloading of the sublayer may be negotiated with other nodes. If the UE receives a message directed to the offload layer, the UE may transparently forward the message to the other node and receive information from the other node via snCP signaling.

[0119] Fig.15 1500 according to some embodiments. For example, the operation flow / algorithm structure 1500 may be performed by the MN 104, the UE 1600, or a component thereof (eg, the processor 1604).

[0120] Operational flow / algorithm structure 1500 may include receiving a subnet configuration preference at 1504. The subnet configuration preference may be received from a UE joining a subnet managed by the MN. The subnet configuration preference may indicate a preference of the joining UE for a specific protocol configuration for snUP signaling.

[0121] The operational flow / algorithm structure 1500 may also include: generating subnet configuration parameters based on the indicated preferences at 1508. The configuration parameters may provide a protocol configuration for the snUP. The generated configuration parameters may be based on the subnet configuration preferences. However, the snUP configured by the configuration parameters may or may not fully satisfy the requested preferences. This may be the case if the MN needs to consider other conditions or constraints of the subnet.

[0122] The operation flow / algorithm structure 1500 may further include: outputting the subnet configuration parameters for sending to the UE at 1512. Thereafter, the MN and the UE may perform snUP signaling on the snUP configured by the configuration parameters.

[0123] The snUP may include a snUP layer at the UE that communicates with a snUP layer at the MN.In some embodiments, one or more intermediate nodes may have a snUP layer that facilitates indirect connections between the UE and the MN.

[0124] Although Fig.14 and Fig.15 The order of operations may be implied, but it should be understood that in other embodiments, these operations are performed in a different order, or one or more of these operations can be performed simultaneously. In addition, it should be understood that in other embodiments, one or more additional operations may be included in the operational flow / algorithm structure, or one or more of these operations may be omitted.

[0125] Fig.16 An example UE 1600 according to some embodiments is illustrated. UE 1600 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a camcorder, etc.), a wearable device (e.g., a smart watch), a loose IoT device.

[0126] UE 1600 may include a processor 1604, RF interface circuitry 1608, memory / storage 1612, a user interface 1616, a sensor 1620, a driver circuit 1622, a power management integrated circuit (PMIC) 1624, antenna structures 1626, and a battery 1628. The components of UE 1600 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.16The block diagram of UE 1600 is intended to show a simplified view of some of the components of UE 1600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0127] Components of UE 1600 may be coupled to various other components via one or more interconnects 1632, which may represent any type of interface, input / output, bus (local, system, or extended), transmission line, trace, optical connection, etc. that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0128] The processor 1604 may include processor circuits, such as, for example, a baseband processor circuit (BB) 1604A, a central processor unit circuit (CPU) 1604B, and a graphics processor unit circuit (GPU) 1604C. The processor 1604 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1612) to cause the UE 1600 to perform operations, such as reference Fig.14 and Fig.15 Or those operations described elsewhere herein. In some embodiments, the instructions may implement the CP / UP (sub)layer to perform some or all of these operations.

[0129] In some embodiments, the baseband processor circuit 1604A can access the communication protocol stack 1636 in the memory / storage device 1612 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1604A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, SN-TP layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, snCP / UP layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1608.

[0130] The baseband processor circuit 1604A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network.

[0131] The memory / storage 1612 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1636) that may be executed by one or more processors in the processor 1604 to cause the UE 1600 to perform various operations described herein. The memory / storage 1612 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1600. In some embodiments, some of the memory / storage 1612 may be located on the processor 1604 itself (e.g., L1 cache and L2 cache), while other memory / storage 1612 is located external to the processor 1604 but accessible via a memory interface. The memory / storage 1612 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0132] The RF interface circuit 1608 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1600 to communicate with other devices through a radio access network. The RF interface circuit 1608 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0133] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1626 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1604.

[0134] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the signal through a power amplifier before the RF signal is radiated across the air interface via the antenna structure 1626.

[0135] In various embodiments, the RF interface circuit 1608 may be configured to send / receive signals in a manner compatible with NR access technology.

[0136] The antenna structure 1626 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. The antenna structure 1626 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input / multiple output communications. The antenna structure 1626 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, and the like. The antenna structure 1626 may have one or more panels that are designed for a specific frequency band including a band in FR1 or FR2.

[0137] The user interface 1616 includes various input / output (I / O) devices designed to enable the user to interact with the UE 1600. The user interface circuit 1616 includes an input device circuit and an output device circuit. The input device circuit includes any physical or virtual component for accepting input, and in particular includes one or more physical or virtual buttons (e.g., reset button), a physical keyboard, a keypad, a mouse, a touch pad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual component for displaying information or otherwise conveying information (such as sensor readings, (multiple) actuator positions or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1600.

[0138] Sensor 1620 may include a device, module, or subsystem that is designed to detect events or changes in its environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0139] The driver circuit 1622 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1600. The driver circuit 1622 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1600. For example, the driver circuit 1622 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor 1620 and controlling and allowing access to the sensor 1620, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0140] The PMIC 1624 may manage the power provided to various components of the UE 1600. Specifically, with respect to the processor 1604, the PMIC 1624 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0141] In some embodiments, the PMIC 1624 may control or otherwise be part of various power saving mechanisms of the UE 1600. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1600 may be powered off for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1600 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The UE 1600 enters a very low power state and performs paging, in which it wakes up again periodically to listen to the network, and then powers off again. The UE 1600 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0142] The battery 1628 can power the UE 1600, but in some examples, the UE 1600 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 1628 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1628 can be a typical lead-acid car battery.

[0143] Fig.17 An example base station 1700 is illustrated in accordance with some embodiments. The base station 1700 may include a processor 1704, RF interface circuitry 1708, core network (CN) interface circuitry 1712, memory / storage 1716, and antenna structures 1726.

[0144] The components of base station 1700 may be coupled to various other components via one or more interconnects 1728 .

[0145] The processor 1704, RF interface circuit 1708, memory / storage 1716 (including communication protocol stack 1710), antenna structure 1726 and interconnect 1728 may be similar to those of reference Fig.16 Like named elements are shown and described.

[0146] Processor 1704 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 1716) to cause base station 1700 to perform operations, such as those described with reference to base station 108 described elsewhere herein.

[0147] The CN interface circuit 1712 may provide connectivity to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the base station 1700 via optical fiber or wireless backhaul. The CN interface circuit 1712 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1712 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0148] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0149] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below. Example

[0150] In the following sections, additional exemplary embodiments are provided.

[0151] Embodiment 1 includes a method to be implemented by a user equipment (UE), the method comprising: utilizing a subnet control plane (snCP) layer of the UE, performing control plane signaling with an snCP layer of a node of a subnet, the subnet being coupled to a radio access network (RAN), wherein the subnet is managed by a management node (MN); and processing data received from or sent to the RAN based on the control plane signaling.

[0152] Embodiment 2 includes a method according to embodiment 1 or some other embodiment of the present invention, wherein the node is the MN, the control plane signaling is a second control plane signaling, and the method further includes: utilizing the network control plane (nwCP) layer of the UE to perform a first control plane signaling with the nwCP layer of the base station of the RAN.

[0153] Embodiment 3 includes a method according to embodiment 2 or some other embodiment herein, wherein the second control plane signaling is based on the first control plane signaling.

[0154] Embodiment 4 includes the method according to embodiment 1 or some other embodiment herein, the method further comprising: offloading a sublayer of a network control plane (nwCP) layer of the UE to the node.

[0155] Embodiment 5 includes the method according to embodiment 4 or some other embodiment herein, the method further comprising: negotiating the offloading of the sublayer with the node upon initial connection with the subnet.

[0156] Embodiment 6 includes a method according to embodiment 4 or some other embodiment of the present invention, wherein the node is another UE connected to the MN, and the method further includes: receiving a message from the nwCP layer of the base station of the RAN; and transparently forwarding the message to the sublayer, wherein the control plane signaling includes receiving information contained in the message from another UE.

[0157] Embodiment 7 includes the method according to embodiment 1 or some other embodiment herein, wherein the data is received from or sent to the RAN via a user plane of the subnet.

[0158] Embodiment 8 includes a method to be implemented by a management node (MN) of a subnet, the method comprising: receiving a subnet configuration preference from a user equipment (UE); generating a configuration parameter based on the subnet configuration preference, the configuration parameter being used to configure a subnet user plane for sending data to the UE via the subnet or receiving data from the UE via the subnet; and outputting the configuration parameter for sending to the UE.

[0159] Embodiment 9 includes a method according to embodiment 8 or some other embodiment of the present invention, wherein the subnet user plane includes: a subnet routing protocol (SN-RP) layer at the UE; and an SN-RP layer at the MN for communicating with the SN-RP layer at the UE.

[0160] Embodiment 10 includes a method according to embodiment 9 or some other embodiment herein, wherein the SN-RP layer at the UE is directly below the Internet Protocol (IP) layer at the UE, and the method further includes: receiving an SN-RP packet including user data, a UE identity (ID), and a protocol data unit (PDU) session ID or a quality of service (QoS) flow ID at the SN-RP layer of the MN; and mapping the user data to a data radio bearer based on the PDU session ID or the QoS flow ID using a service adaptation protocol (SDAP) layer of the MN.

[0161] Embodiment 11 includes a method according to embodiment 9 or some other embodiment herein, wherein the SN-RP layer is directly below the Internet Protocol (IP) layer at the UE, and the method further includes: receiving user data via packets associated with a data radio bearer (DRB) at a service adaptation protocol (SDAP) layer of the MN; mapping the user data to a quality of service (QoS) flow or a protocol data unit (PDU) session based on the DRB using the SDAP layer of the MN; generating, using the SN-RP layer of the MN, an SN-RP packet to include the user data and an ID associated with the PDU session or an ID associated with the QoS flow; and outputting the SN-RP packet for sending to the SN-RP layer of the UE.

[0162] Embodiment 12 includes a method according to embodiment 8 or some other embodiment of the present invention, wherein the UE is a first UE, and the subnet user plane includes: a subnet routing protocol (SN-RP) layer at the first UE; a first SN-RP layer at a second UE for communicating with the SN-RP at the first UE; a second SN-RP layer at the second UE; and an SN-RP layer at the MN for communicating with the second SN-RP layer at the second UE.

[0163] Embodiment 13 includes a method according to embodiment 12 or some other embodiment herein, wherein the SN-RP layer at the first UE is directly below an Internet Protocol (IP) layer of the first UE, and the second SN-RP layer at the second UE is directly below a Packet Data Convergence Protocol (PDCP) layer of the second UE.

[0164] Embodiment 14 includes a method according to embodiment 12 or some other embodiment herein, wherein the SN-RP layer at the first UE is directly below a packet data convergence protocol (PDCP) layer of the first UE, and the second SN-RP layer at the second UE is directly below a radio link control (RLC) layer of the second UE.

[0165] Embodiment 15 includes a method according to embodiment 12 or some other embodiment herein, wherein the SN-RP layer at the first UE is directly below the packet data convergence protocol (PDCP) layer of the first UE, and the SN-RP layer of the MN is to interact with the radio link control (RLC) layer of the MN.

[0166] Embodiment 16 includes a method according to embodiment 12 or some other embodiment herein, wherein the SN-RP layer at the first UE is directly below the radio link control (RLC) layer of the first UE, and the SN-RP layer of the MN is to interact with the medium access control (MAC) layer of the MN.

[0167] Embodiment 17 includes a method according to embodiment 8 or some other embodiment of the present invention, wherein the subnet user plane includes a subnet routing protocol (SN-RP) layer at the UE, and the method further includes: generating an SN-RP packet including a header, the header having a first field for indicating a UE identification (ID), a second field for indicating a type of mapping information; and a third field for including the type of mapping information.

[0168] Embodiment 18 includes the method of embodiment 17 or some other embodiment herein, wherein the type is a protocol data unit (PDU) session information type, a data radio bearer ID type, or a signaling radio bearer ID type.

[0169] Embodiment 19 includes a method, the method comprising: utilizing a subnet routing protocol (SN-RP) layer, generating an SN-RP packet including a header, the header having a first field for indicating a user equipment (UE) identification (ID), a second field for indicating a type of mapping information; and a third field for including the type of mapping information; and sending the SN-RP to a subnet node via a direct connection on a local link.

[0170] Embodiment 20 includes the method according to embodiment 19 or some other embodiment herein, wherein the UEID is used to identify the UE that generates the SN-RP packet.

[0171] Embodiment 21 includes a method as described in embodiment 19 or some other embodiment herein, wherein the type is a protocol data unit (PDU) session information type, a data radio bearer ID type, or a signaling radio bearer ID type. Another embodiment may include an apparatus including means for performing one or more elements of a method as described in or related to any one of embodiments 1 to 21, or any other method or process described herein.

[0172] Another embodiment may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Embodiments 1 to 21 or any other method or process described herein.

[0173] Another embodiment may include an apparatus comprising logical components, modules, or circuits for performing one or more elements of a method as described or related to any of Embodiments 1 to 21, or any other method or process described herein.

[0174] Another embodiment may include a method, technique or process described or related to any one of Embodiments 1 to 21 or a portion or component thereof.

[0175] Another embodiment may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one of embodiments 1 to 21 or portions thereof.

[0176] Another embodiment may include a signal according to or in connection with any one of embodiments 1 to 21 or parts or components thereof.

[0177] Another embodiment may include a datagram, information element, packet, frame, segment, PDU or message as described or related to any one of embodiments 1 to 21 or parts or components thereof or otherwise described in the present disclosure.

[0178] Another embodiment may include a signal encoded with data as described or associated with any one of embodiments 1 to 21, or parts or components thereof, or otherwise described in this disclosure.

[0179] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described or related to any one of embodiments 1 to 21, or parts or components thereof, or otherwise described in the present disclosure.

[0180] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of these computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described or related to any one or part of Embodiments 1 to 21.

[0181] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described or related to any one of Embodiments 1 to 21, or a portion thereof.

[0182] Another embodiment may include a signal in a wireless network as shown and described herein.

[0183]

[0013] Another embodiment may include a method of communicating in a wireless network as shown and described herein.

[0184]

[0013] Another embodiment may include a system for providing wireless communications as shown and described herein.

[0185]

[0013] Another embodiment may include an apparatus for providing wireless communications as shown and described herein.

[0186] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0187] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

[0188] Related Applications

[0189] This application claims priority to U.S. Provisional Patent Application No. 63 / 583,177, filed on September 15, 2023, entitled “CONTROL PLANE AND USER PLANE SUBNET TECHNOLOGY,” and U.S. Non-Provisional Patent Application No. 18 / 806,596, filed on August 15, 2024, entitled “CONTROL PLANE AND USER PLANE SUBNET TECHNOLOGY,” the entire contents of which are incorporated herein by reference.

Claims

1. A method comprising: performing, using a first subnet control plane (snCP) layer, control plane signaling with a second snCP layer, the second snCP layer being associated with a node of a subnet coupled to a radio access network (RAN), wherein the subnet is managed by a management node (MN); and Data received from or sent to the RAN is processed based on the control plane signaling.

2. The method according to claim 1, wherein the node is the MN, the control plane signaling is second control plane signaling, and the method further comprises: Using a first network control plane (nwCP) layer, first control plane signaling with a second nwCP layer is performed, wherein the second nwCP layer is associated with a base station of the RAN. 3 . The method according to claim 2 , wherein the second control plane signaling is based on the first control plane signaling.

4. The method according to claim 1, further comprising: A sublayer of a network control plane (nwCP) layer is offloaded to the node.

5. The method according to claim 4, further comprising: The offloading of the sublayer is negotiated with the node upon initial connection to the subnet.

6. The method of claim 4, wherein the node is a user equipment (UE) connected to the MN, and the method further comprises: receiving a message from an nwCP layer of a base station of the RAN; as well as forwarding the message transparently to the sublayer, The control plane signaling includes receiving information contained in the message from the UE. The method according to claim 1 , wherein the data is received from or sent to the RAN via a user plane of the subnet.

8. One or more computer-readable media having instructions that, when executed, cause a processing circuit to: receiving a subnet configuration preference from a user equipment (UE); generating a configuration parameter based on the subnet configuration preference, the configuration parameter being used to configure a subnet user plane for sending data to the UE via a subnet or receiving data from the UE via a subnet; and The configuration parameters are output for sending to the UE.

9. The one or more computer-readable media of claim 8, wherein the subnet user plane comprises: a sub-network routing protocol (SN-RP) layer at the UE; as well as The SN-RP layer at a management node (MN) is configured to communicate with the SN-RP layer at the UE.

10. The one or more computer-readable media of claim 9, wherein the SN-RP layer at the UE is directly below an Internet Protocol (IP) layer at the UE, and the instructions, when executed, cause a processing circuit to: receiving, at the SN-RP layer of the MN, an SN-RP packet including user data, a UE identity (ID), and a protocol data unit (PDU) session ID or a quality of service (QoS) flow ID; and The user data is mapped to a data radio bearer based on the PDU session ID or QoS flow ID using a service adaptation protocol (SDAP) layer of the MN.

11. The one or more computer-readable media of claim 9, wherein the SN-RP layer is directly below an Internet Protocol (IP) layer at the UE, and the instructions, when executed, cause a processing circuit to: receiving, at a service adaptation protocol (SDAP) layer of the MN, user data via packets associated with a data radio bearer (DRB); Mapping the user data to a quality of service (QoS) flow or a protocol data unit (PDU) session based on the DRB using the SDAP layer of the MN; generating, using the SN-RP layer of the MN, an SN-RP packet to include the user data and an ID associated with the PDU session or an ID associated with the QoS flow; and The SN-RP packet is outputted for sending to the SN-RP layer of the UE.

12. The one or more computer-readable media of claim 8, wherein the UE is a first UE, and the subnet user plane comprises: a sub-network routing protocol (SN-RP) layer at the first UE; a first SN-RP layer at a second UE configured to communicate with the SN-RP layer at the first UE; a second SN-RP layer at the second UE; as well as An SN-RP layer at a management node (MN) for communicating with the second SN-RP layer at the second UE.

13. The one or more computer-readable media of claim 12, wherein the SN-RP layer at the first UE is directly below an Internet Protocol (IP) layer of the first UE, and the second SN-RP layer at the second UE is directly below a Packet Data Convergence Protocol (PDCP) layer of the second UE.

14. The one or more computer-readable media of claim 12, wherein the SN-RP layer at the first UE is directly below a Packet Data Convergence Protocol (PDCP) layer of the first UE, and the second SN-RP layer at the second UE is directly below a Radio Link Control (RLC) layer of the second UE.

15. The one or more computer-readable media of claim 12, wherein the SN-RP layer at the first UE is directly below a Packet Data Convergence Protocol (PDCP) layer of the first UE, and the SN-RP layer of the MN is to interact with a Radio Link Control (RLC) layer of the MN.

16. The one or more computer-readable media of claim 12, wherein the SN-RP layer at the first UE is directly below a radio link control (RLC) layer of the first UE, and the SN-RP layer of the MN is to interact with a medium access control (MAC) layer of the MN.

17. The one or more computer-readable media of claim 8, wherein the subnet user plane comprises a subnet routing protocol (SN-RP) layer at the UE, and the instructions, when executed, further cause a processing circuit to: An SN-RP packet is generated including a header having a first field indicating a UE identification (ID), a second field indicating a type of mapping information, and a third field including the mapping information of the type, wherein the type is a protocol data unit (PDU) session information type, a data radio bearer ID type, or a signaling radio bearer ID type.

18. A device comprising a processing circuit, the processing circuit being configured to: generating, using a subnetwork routing protocol (SN-RP) layer, a SN-RP packet including a header having a first field indicating a user equipment (UE) identification (ID), a second field indicating a type of mapping information; and a third field including the type of mapping information; and The SN-RP packet is output via the interface circuit for transmission to a subnet node via a direct connection on a local link.

19. The apparatus according to claim 18, wherein the UE ID is used to identify a UE that generates the SN-RP packet.

20. The apparatus of claim 18, wherein the type is a protocol data unit (PDU) session information type, a data radio bearer ID type, or a signaling radio bearer ID type.

Images