Sidelink relay routing options for transmitting data from a wireless communication device to a network

Abstract

In one aspect, a remote device generates data for transmission to a network based on an application, selects a data routing option of a set of data routing options for routing the data to the network based on policy control information, each data routing option of the set of data routing options including routing the data via a relay device, and communicates the data to the relay device for routing the data via the selected data routing option. In another aspect, a relay establishes a protocol data unit (PDU) session with a network based on policy control information for relaying data received from a remote device, receives the data from the remote device, and communicates the data to a base station coupled to the network via the PDU session. Another aspect relates to base station operations with respect to the above aspects.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of Greek patent application S / N.20200100247, filed on May 12, 2020, which is incorporated herein by reference. Technical Field

[0003] The techniques discussed below generally relate to wireless communication networks, and more particularly to sidelink relay routing options for transmitting data from wireless communication devices (e.g., user equipment (UE)) to the network.

[0004] background

[0005] Various network configurations can facilitate wireless communication between devices. In one configuration, a cellular network enables wireless communication devices (e.g., User Equipment (UE)) to communicate with each other via signaling to a nearby base station or cell. Another wireless communication network configuration is a device-to-device (D2D) network, where wireless communication devices can signal directly to each other instead of via an intermediary base station or cell. For example, a D2D communication network can utilize sidelink signaling to facilitate direct communication between wireless communication devices. In some sidelink network configurations, wireless communication devices can further communicate within the cellular network (typically under the control of a base station). Thus, wireless communication devices can be configured for uplink and downlink signaling via a base station, and further for direct sidelink signaling between wireless communication devices without transmission through a base station.

[0006] A brief overview of some examples

[0007] The following provides an overview of one or more aspects of this disclosure to provide a basic understanding of these aspects. This overview is not an exhaustive summary of all the features conceived in this disclosure, and is neither intended to identify key or decisive elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its sole purpose is to provide some concepts of one or more aspects of this disclosure in one form as a prelude to the more detailed description that follows.

[0008] In one example, a first wireless communication device is disclosed. The first wireless communication device includes a wireless transceiver, a memory, and a processor communicatively coupled to the wireless transceiver and the memory. The processor and the memory can be configured to generate data for transmission to a network based on an application. The processor and the memory can be further configured to select a data routing option from a set of data routing options as a selected data routing option for routing data to the network based on policy control information, wherein each data routing option in the set of data routing options includes routing the data to the network via a second wireless communication device. Additionally, the processor and the memory can be configured to use the wireless transceiver to transmit the data to the second wireless communication device for routing the data via the selected data routing option.

[0009] Another example provides a method for wireless communication at a first wireless communication device. The method includes generating data for transmission to a network based on an application, and selecting a data routing option from a set of data routing options based on policy control information for routing the data to the network. Each data routing option in the set of data routing options includes routing the data via a second wireless communication device. The method further includes transmitting the data to the second wireless communication device for routing the data via the selected data routing option.

[0010] Another example provides a first wireless communication device. The first wireless communication device includes means for generating data for transmission to a network based on an application, and means for selecting a data routing option from a set of data routing options based on policy control information for routing the data to the network. Each data routing option in the set of data routing options includes routing the data via a second wireless communication device. The first wireless communication device further includes means for transmitting the data to the second wireless communication device for routing the data via the selected data routing option.

[0011] Another example provides an article of manufacture for use by a first wireless communication device. The article of manufacture includes a computer-readable medium storing instructions executable by one or more processors of the first wireless communication device to generate data for transmission to a network based on an application, and to select a data routing option from a set of data routing options based on policy control information for routing the data to the network. Each data routing option in the set of data routing options includes routing the data via a second wireless communication device. These instructions are executable by the one or more processors of the first wireless communication device to further transmit the data to the second wireless communication device for routing the data via the selected data routing option.

[0012] Another example provides a first wireless communication device. The first wireless communication device includes a wireless transceiver, a memory, and a processor communicatively coupled to the wireless transceiver and the memory. The processor and the memory can be configured to establish a Protocol Data Unit (PDU) session with a network based on policy control information for relaying data received from a second wireless communication device, receiving data from the second wireless communication device using the wireless transceiver, and transmitting the data to a base station coupled to the network via the PDU session using the wireless transceiver.

[0013] Another example provides a method for performing wireless communication at a first wireless communication device. The method includes establishing a Protocol Data Unit (PDU) session with a network based on policy control information for relaying data received from a second wireless communication device, receiving data from the second wireless communication device, and transmitting the data via the PDU session to a base station coupled to the network.

[0014] Another example provides a first wireless communication device. The first wireless communication device includes: means for establishing a Protocol Data Unit (PDU) session with a network based on policy control information for relaying data received from a second wireless communication device; means for receiving data from the second wireless communication device; and means for transmitting the data to a base station coupled to the network via the PDU session.

[0015] Another example provides an article of manufacture for use by a first wireless communication device. The article of manufacture includes a computer-readable medium storing instructions executable by one or more processors of the first wireless communication device to establish a Protocol Data Unit (PDU) session with a network based on policy control information for relaying data received from a second wireless communication device, receiving data from the second wireless communication device, and transmitting the data via the PDU session to a base station coupled to the network.

[0016] Another example provides a base station. The base station includes a wireless transceiver, a memory, and a processor communicatively coupled to the wireless transceiver and the memory. The processor and the memory are configured to establish a Protocol Data Unit (PDU) session with a first wireless communication device and a network device for receiving data from the first wireless communication device and forwarding the data to the network device, and to receive data from the first wireless communication device via the PDU session using the wireless transceiver. The data originates from a second wireless communication device. The processor and the memory are further configured to transmit the data to the network device via the PDU session using a network interface.

[0017] Another example provides a method for implementing wireless communication at a base station. The method includes establishing a Protocol Data Unit (PDU) session with a first wireless communication device and a network device for receiving data from the first wireless communication device and forwarding the data to the network device, and receiving data from the first wireless communication device via the PDU session. The data originates from a second wireless communication device. The method further includes transmitting the data to the network device via the PDU session.

[0018] Another example provides a base station. The base station includes means for establishing a Protocol Data Unit (PDU) session with a first wireless communication device and a network device to receive data from the first wireless communication device and forward the data to the network device, and means for receiving data from the first wireless communication device via the PDU session. The data originates from a second wireless communication device. The base station further includes means for transmitting the data to the network device via the PDU session.

[0019] Another example provides an article of manufacture for use by a base station. The article of manufacture includes a computer-readable medium storing instructions executable by one or more processors of the base station to establish a Protocol Data Unit (PDU) session with a first wireless communication device and a network device for receiving data from the first wireless communication device and forwarding the data to the network device, and receiving data from the first wireless communication device via the PDU session. The data originates from a second wireless communication device. These instructions are executable by the one or more processors of the base station to further transmit the data to the network device via the PDU session.

[0020] Another example provides a first wireless communication device. The first wireless communication device includes a wireless transceiver, a memory, and a processor communicatively coupled to the wireless transceiver and the memory. The processor and the memory are configured to: generate data for transmission based on an application; select a data routing option from a set of data routing options based on policy control information to route the data to a second wireless communication device; and use the wireless transceiver to transmit the data to the second wireless communication device.

[0021] Another example provides a method for wireless communication implemented at a first wireless communication device. The method includes generating data for transmission based on an application, selecting a data routing option from a set of data routing options based on policy control information to route the data to a second wireless communication device, and transmitting the data to the second wireless communication device.

[0022] Another example provides a first wireless communication device. The first wireless communication device includes means for generating data for transmission based on an application, means for selecting a data routing option from a set of data routing options based on policy control information to route the data to a second wireless communication device, and means for transmitting the data to the second wireless communication device.

[0023] Another example provides an article of manufacture for use by a first wireless communication device. The article of manufacture includes a computer-readable medium storing instructions executable by one or more processors of the wireless communication device to: generate data for transmission based on an application; select a data routing option from a set of data routing options based on policy control information to route the data to a second wireless communication device; and transmit the data to the second wireless communication device.

[0024] These and other aspects will be more fully understood after reading the following detailed description. Other aspects, features, and examples will become apparent to those skilled in the art after reading the following description of specific exemplary examples in conjunction with the accompanying drawings. Although features may be discussed below with reference to certain examples and drawings, all examples may include one or more of the advantageous features discussed herein. In other words, while one or more examples may be discussed having certain advantageous features, one or more such features may also be used according to the various examples discussed herein. Similarly, although exemplary examples may be discussed below as examples of devices, systems, or methods, such exemplary examples can be implemented in various devices, systems, and methods. Brief description of the attached diagram

[0026] Figure 1 This is a diagram illustrating an example of a wireless radio access network based on some aspects.

[0027] Figure 2 This is a diagram illustrating examples of frame structures for use in wireless communication networks, based on several aspects.

[0028] Figure 3 This is a diagram illustrating an example of a wireless communication network employing sidelink communication based on some aspects.

[0029] Figure 4 This is a block diagram illustrating a wireless communication system that communicates with a remote wireless communication device via at least one relay wireless communication device to a network, supported by several factors.

[0030] Figure 5 This is a block diagram illustrating another wireless communication system that communicates with a network via a remote wireless communication device through at least one relay wireless communication device, supported by several aspects.

[0031] Figures 6A-6B It is a control plane and user plane protocol stack diagram associated with Layer 3 (L3) relay data routing options based on some aspects.

[0032] Figures 7A-7B It is a control plane and user plane protocol stack diagram associated with Layer 3 (L3) relays with non-3GPP Networking Functions (N3IWF) data routing options, based on some aspects.

[0033] Figures 8A-8B It is a control plane and user plane protocol stack diagram associated with Layer 2 (L2) relay data routing options based on some aspects.

[0034] Figure 9 This is a flowchart of an exemplary signaling diagram illustrating how data transmission is routed from a remote wireless communication device to a network using L3 relay data routing options, based on several aspects.

[0035] Figure 10 This is a flowchart of an exemplary signaling diagram illustrating the use of an L3 relay with N3IWF data routing options to route data transmission from a remote wireless communication device to a network, based on some aspects.

[0036] Figure 11 This is a flowchart of an exemplary signaling diagram illustrating how data is routed from a remote wireless communication device to a network using L2 relay data routing options, based on several aspects.

[0037] Figure 12 This is a block diagram illustrating an example of the hardware implementation of a wireless communication device based on some aspects of the processing system.

[0038] Figure 13 This is a flowchart of an exemplary method for sending data to a network via a relay data routing option, based on some aspects.

[0039] Figure 14 This is a flowchart illustrating an exemplary method for relaying data from a remote wireless communication device to a network via a relay data routing option, according to some aspects.

[0040] Figure 15 This is a flowchart illustrating an exemplary method for transmitting data from a first wireless communication device to a second wireless communication device via a sidelink routing option, based on some aspects.

[0041] Figure 16 This is a block diagram illustrating an example of the hardware implementation of a base station using a processing system based on certain aspects.

[0042] Figure 17This is a flowchart of another exemplary method for relaying data received from a remote wireless communication device via a relay wireless communication device to a network, based on some aspects of a relay data routing option.

[0043] Figure 18 It is a flowchart depicting a method for routing application data to a target device based on several factors.

[0044] Detailed description

[0045] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent only the configurations in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0046] While aspects and examples are described herein by way of illustration of a few examples, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or uses may arise via integrated chip examples and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, broad applicability of the described innovations can emerge. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals requires several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a wide variety of devices, chip-level components, systems, distributed deployments, end-user devices, etc., of various sizes, shapes, and configurations.

[0047] The various concepts presented throughout this disclosure can be implemented across a wide range of telecommunications systems, network architectures, and communication standards. Now refer to... Figure 1This illustration of a radio access network 100 is provided as an illustrative example and not a limitation. The RAN 100 can implement any one or more suitable wireless communication technologies to provide radio access. As an example, the RAN 100 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, the RAN 100 can operate in a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (commonly referred to as LTE). 3GPP refers to this hybrid RAN as a Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0048] The geographic area covered by the radio access network 100 can be divided into several cellular areas (cells), which can be uniquely identified by the user equipment (UE) based on an identifier broadcast across the geographic area from an access point or base station. Figure 1 Cells 102, 104, 106, and 108 are described, each of which may include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. Radio links within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by an antenna array, where each antenna is responsible for communication with UEs within a portion of the cell.

[0049] Generally, each base station (BS) serves its respective cell. More broadly, a base station is a network element in a radio access network responsible for radio transmissions to and from a UE in one or more cells. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), B node (NB), evolved B node (eNB), g B node (gNB), transmit / receive point (TRP), or any other suitable term. In some examples, a base station may include two or more coexisting or non-coexisting TRPs. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN100 operates according to both LTE and 5G NR standards, one of these base stations may be an LTE base station, while the other may be a 5G NR base station.

[0050] It can be deployed using various base stations. For example, in Figure 1In the illustration, two base stations 110 and 112 are shown in cells 102 and 104, and a third base station 114 is shown as a remote radio head (RRH) 116 controlling cell 106. That is, the base stations may have integrated antennas, or they may be connected to the antenna or RRH via a feed cable. In the illustrated example, cells 102, 104, and 106 may be referred to as macrocells because base stations 110, 112, and 114 support cells with large sizes. Furthermore, base station 118 is shown in cell 108, where cell 308 may overlap with one or more macrocells. In this example, cell 108 may be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home B-node, home evolved B-node, etc.) because base station 118 supports cells with relatively small sizes. Cell size settings can be determined based on system design and component constraints.

[0051] To understand, the radio access network 100 may include any number of radio base stations and cells. Furthermore, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 110, 112, 114, and 118 provide radio access points to the core network for any number of mobile devices.

[0052] Figure 1 This further includes an unmanned aerial vehicle (UAV) 120, which may be a drone or a quadcopter. The UAV 120 may be configured to function as a base station, or more specifically as a mobile base station. That is, in some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station (such as the UAV 120).

[0053] Generally, a base station may include a backhaul interface for communicating with the backhaul portion (not shown) of the network. The backhaul provides a link between the base station and the core network (not shown), and in some examples, the backhaul provides interconnection between respective base stations. The core network may be part of a wireless communication system and may be independent of the radio access technology used in the radio access network. Any suitable transport network can be used to employ various types of backhaul interfaces, such as direct physical connections, virtual networks, etc.

[0054] RAN 100 is defined as supporting wireless communication for multiple mobile devices. Mobile devices are typically referred to as User Equipment (UE) in standards and specifications issued by the 3rd Generation Partnership Project (3GPP), but may also be referred to by those skilled in the art as Mobile Station (MS), Subscriber Station, Mobile Unit, Subscriber Unit, Radio Unit, Remote Unit, Mobile Equipment, Radio Equipment, Wireless Communication Equipment, Remote Equipment, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handheld Device, Terminal, User Agent, Mobile Client, Client, or any other suitable term. A UE can be a device that provides users with access to network services.

[0055] Within this document, a “mobile” device does not necessarily need to be mobile and may be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. For example, some non-limiting examples of mobile devices include mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), laptops, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those corresponding to the “Internet of Things” (IoT). Additionally, a mobile device can be an automobile or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, consumer and / or wearable devices (such as glasses), wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Additionally, mobile devices can be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting equipment, home security systems, smart meters, etc. Additionally, mobile devices can be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity, lighting, water, etc. (e.g., smart grids), industrial automation and enterprise equipment, logistics controllers, agricultural equipment, etc. Furthermore, mobile devices can provide networked healthcare or telemedicine support, i.e., remote health care. Remote health care devices can include remote health monitoring devices and remote health supervision devices, whose communications can be given priority over other types of information, for example, in the form of prioritized access for critical service data transmission and / or relevant QoS for critical service data transmission.

[0056] Within RAN 100, a cell may include UEs capable of communicating with one or more sectors of each cell. For example, UEs 122 and 124 may communicate with base station 110; UEs 126 and 128 may communicate with base station 112; UEs 130 and 132 may communicate with base station 114 via RRH 116; UE 134 may communicate with base station 118; and UE 136 may communicate with mobile base station 120. Here, each base station 110, 112, 114, 118, and 120 may be configured as an access point provided to the core network (not shown) for all UEs in the respective cell. In some examples, UAV 120 (e.g., a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, UAV 120 may operate within cell 102 by communicating with base station 110.

[0057] Wireless communication between RAN 100 and UEs (e.g., UE 122 or 124) can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating at a scheduling entity (further described below; e.g., base station 110). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 122) to a base station (e.g., base station 110) can be referred to as uplink (UL) transmissions. According to a further aspect of this disclosure, the term uplink can refer to point-to-point transmissions originating at a scheduled entity (further described below; e.g., UE 122).

[0058] For example, DL transmission may include unicast or broadcast transmission of control information and / or traffic information (e.g., user data traffic) from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124), while UL transmission may include transmission of control information and / or traffic information originating at a UE (e.g., UE 122). Additionally, uplink and / or downlink control information and / or traffic information may be temporally divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit carrying one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Within this disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame comprises, for example, 10 subframes, each 1 ms in length. Of course, these definitions are not required, and any suitable scheme can be used to organize the waveform, and the various time divisions of the waveform can have any suitable duration.

[0059] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication among some or all of its equipment and apparatus within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, the UE or the scheduled entity utilizes resources allocated by the scheduling entity.

[0060] A base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). For example, two or more UEs (e.g., UEs 138, 140, and 142) can communicate with each other using sidelink signal 137 without relaying the communication through a base station. In some examples, UEs 138, 140, and 142 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and relay sidelink signal 137 therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 126 and 128) within the coverage area of ​​a base station (e.g., base station 112) can also relay sidelink signal 127 on a direct link (sidelink) without relaying the communication through base station 112. In this example, base station 112 can allocate resources to UEs 126 and 128 for sidelink communication. In either case, such sidelink signaling 127 and 137 can be implemented in peer-to-peer (P2P) networks, device-to-device (D2D) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, mesh networks, or other suitable direct link networks.

[0061] In some examples, a D2D relay framework may be included within the cellular network to facilitate the relay of communications to / from base station 112 via a D2D link (e.g., side link 127 or 137). For example, one or more UEs (e.g., UE 128) within the coverage area of ​​base station 112 may operate as relay UEs to extend the coverage of base station 112, improve transmission reliability for one or more UEs (e.g., UE 126), and / or allow the base station to recover from failed UE links due to, for example, congestion or fading.

[0062] Two main technologies that can be used by V2X networks include Dedicated Short Range Communication (DSRC) based on the IEEE 802.11p standard and cellular V2X based on LTE and / or 5G (New Radio) standards. Various aspects of this disclosure may relate to New Radio (NR) cellular V2X networks, which, for simplicity, are referred to herein as V2X networks. However, it should be understood that the concepts disclosed herein are not limited to specific V2X standards, or may refer to sidelink networks other than V2X networks.

[0063] To achieve a low block error rate (BLER) while still maintaining a very high data rate over the air interface, channel coding can be used. That is, wireless communication typically utilizes appropriate error-correcting block codes. In a typical block code, an information message or sequence is broken down into code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message improves the reliability of the message, thereby enabling the correction of any bit errors that may occur due to noise.

[0064] Data encoding can be implemented in several ways. In earlier 5G NR specifications, user data was encoded using quasi-cyclic low-density parity-check (LDPC) with two different base maps: one base map was used for large code blocks and / or high code rates, while the other base map was used for other cases. Polar coding was used to encode control information and the Physical Broadcast Channel (PBCH) based on nested sequences. For these channels, puncturing, shortening, and repetition were used for rate matching.

[0065] Various aspects of this disclosure can be implemented using any suitable channel code. Various implementations of the base station and UE may include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0066] In RAN 100, the ability of a UE to communicate independently of its location while on the move is referred to as mobility. The various physical channels between the UE and the RAN are generally established, maintained, and released under the control of the Access and Mobility Management Function (AMF). In some scenarios, the AMF may include a Security Context Management Function (SCMF) and a Security Anchor Function (SEAF) that performs authentication. The SCMF can manage the security context of both the control plane and user plane functionalities, either entirely or partially.

[0067] In some examples, RAN 100 enables mobility and handover (i.e., the UE's connection is transferred from one radio channel to another). For example, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 124 can move from a geographic area corresponding to its serving cell 102 to a geographic area corresponding to a neighboring cell 106. When the signal strength or quality from neighboring cell 106 exceeds the signal strength or quality from its serving cell 102 for a given amount of time, UE 124 can transmit a report message indicating this condition to its serving base station 110. In response, UE 124 can receive a handover command, and the UE can undergo a handover to cell 106.

[0068] In various implementations, the air interface in RAN 100 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. While some technical rules generally still apply to accessing unlicensed spectrum, access is available to any operator or device. Shared spectrum falls between licensed and unlicensed spectrum, where technical rules or restrictions may be required for spectrum access, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide Licensed Shared Access (LSA) to share that spectrum with other parties, for example, by utilizing conditions determined by the appropriate licensee.

[0069] The air interface in RAN 100 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication between individual devices. For example, the 5G NR specification provides multiple access for UL or reverse link transmissions from UEs 122 and 124 to base station 110, and utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) to provide multiplexing for DL ​​or forward link transmissions from base station 110 to UEs 122 and 124. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 110 to UEs 122 and 124 can be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0070] Furthermore, the air interface in RAN 100 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex simulation is typically implemented for wireless links using Time Division Duplex (TDD). In TDD, transmissions in different directions on a given channel are separated using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, it is dedicated to transmissions in the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation between the transmitter and receiver, and appropriate interference cancellation techniques. Full-duplex simulation is typically implemented for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as Subband Full-Duplex (SBFD), also known as flexible duplex.

[0071] Reference Figure 2The OFDM waveforms illustrated herein are used to describe various aspects of this disclosure. Those skilled in the art will understand that various aspects of this disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0072] Now refer to Figure 2 An expanded view of exemplary subframe 202 is illustrated, showing the OFDM resource grid. However, as those skilled in the art will readily appreciate, the PHY transport structure for any particular application can vary from the example described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; while frequency is in the vertical direction in units of the carrier's subcarriers.

[0073] Resource grid 204 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, there can be a corresponding number of resource grids 204 available for communication. Resource grid 204 is divided into multiple resource elements (REs) 206. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE may represent one or more information bits. In some examples, an RE block may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 208, which contains any suitable number of coherent subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the parameter design used. In some examples, depending on the parameter design, an RB may include any suitable number of coherent OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 208) corresponds exactly to a single communication direction (transmission or reception for a given device).

[0074] A set of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth portion (BWP). A set of subbands or BWPs may span the entire bandwidth. Scheduling of downlink, uplink, or sidelink transmissions to a UE or sidelink device (hereinafter collectively referred to as UE) typically involves scheduling one or more resource elements 206 within one or more subbands or bandwidth portions (BWPs). Thus, the UE generally utilizes only a subset of the resource grid 204. In some examples, an RB may be the smallest unit of resource that can be allocated to the UE. Therefore, the more RBs scheduled for the UE and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE. RBs can be scheduled by the base station (e.g., gNB, eNB, etc.) or can be self-scheduled by the UE / sidelink device implementing D2D sidelink communication.

[0075] In this explanation, RB 208 is shown to occupy less than the entire bandwidth of subframe 202, where some subcarriers above and below RB 208 are explained. In a given implementation, subframe 202 may have bandwidth corresponding to any number of one or more RB 208s. Furthermore, in this explanation, RB 208 is shown to occupy less than the entire duration of subframe 202, but this is merely one possible example.

[0076] Each 1ms subframe 202 may include one or more adjacent time slots. As an illustrative example, in... Figure 2 In the example shown, a subframe 202 includes four time slots 210. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, with a nominal CP, a time slot may include 7 or 12 OFDM symbols. Additional examples may include mini time slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). In some cases, these mini time slots or shortened transmission time intervals (TTIs) may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0077] An expanded view of one of these time slots 210 illustrates that time slot 210 includes a control region 212 and a data region 214. Generally, control region 212 can carry control channels, while data region 214 can carry data channels. Of course, the time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 2 The structure described herein is merely exemplary in nature and may utilize different time-slot structures, and may include one or more for each of the control region and data region.

[0078] Although not in Figure 2The explanation is as follows: Each RE 206 within RB 208 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 206 within RB 208 can carry pilot or reference signals. These pilot or reference signals can be used by the receiver equipment to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 208.

[0079] In some examples, time slot 210 can be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications can refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple target receiving devices. Unicast communications can refer to point-to-point transmissions from one device to a single other device.

[0080] In an example of cellular communication over a cellular carrier via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 206 (e.g., within control area 212) to carry DL control information to one or more scheduled entities (e.g., UEs), including one or more DL control channels (such as the Physical Downlink Control Channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands for DL ​​and UL transmissions (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or RE assignments. The PDCCH may further carry HARQ feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well known to those skilled in the art, where, for accuracy, any suitable integrity verification mechanism (such as a checksum or cyclic redundancy check (CRC)) may be used to verify the integrity of packet transmissions at the receiving side. If the integrity of the transmission is acknowledged, an ACK may be transmitted, and if it is not acknowledged, a NACK may be transmitted. In response to NACK, the transmitting device can send a HARQ retransmission, which enables catch-up retransmission, incremental redundancy, and so on.

[0081] The base station may further allocate one or more REs 206 (e.g., in control area 212 or data area 214) to carry other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signals (PT-RS); channel state information (CSI) reference signals (CSI-RS); and synchronization signal blocks (SSBs). SSBs may be broadcast at regular intervals based on periodicity (e.g., 5, 10, 20, 20, 80, or 120 milliseconds). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0082] The PBCH in the SSB may further include: a Master Information Block (MIB), which includes various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, System Information Type 1 (SIB1), which may include various additional system information. Together, the MIB and SIB1 provide the minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to: subcarrier spacing (e.g., default downlink parameter design), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell prohibition indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of residual minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information.

[0083] In UL transmissions, the scheduled entity (e.g., the UE) may use one or more RE 206s to carry UL control information (UCI) to the scheduling entity. This UL control information includes one or more UL control channels, such as the Physical Uplink Control Channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include probe reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI), which can schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as CSI reports), or any other suitable UCI.

[0084] In addition to control information, one or more REs 214 (e.g., within data area 206) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions, or the Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some examples, one or more REs 206 within data area 214 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0085] In an example of sidelink communication on a sidelink carrier via the PC5 interface, the control area 210 of time slot 212 may include a Physical Sidelink Control Channel (PSCCH), which includes sidelink control information (SCI) transmitted from an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., Rx V2X devices or other Rx UEs). The data area 214 of time slot 210 may include a Physical Sidelink Shared Channel (PSSCH), which includes sidelink data traffic transmitted by the transmitting sidelink device within resources reserved on the sidelink carrier by the initiating (transmitting) sidelink device via the SCI. Further information may be transmitted on various REs 206 within time slot 210. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in the Physical Sidelink Feedback Channel (PSFCH) within time slot 210. In addition, one or more reference signals, such as sidelink SSB, sidelink CSI-RS, sidelink SRS and / or sidelink positioning reference signal (PRS), can be transmitted in time slot 210.

[0086] These physical channels are typically multiplexed and mapped to transport channels for processing by the Media Access Control (MAC) layer. The transport channel carries blocks of information, called transport blocks (TBs). The transport block size (TBS) (which may correspond to the number of information bits) can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0087] Figure 2 The channels or carriers described are not necessarily all the channels or carriers available between devices, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be available in addition to those described.

[0088] Figure 3Examples of wireless communication networks 300 configured to support D2D or sidelink communication are described. In some examples, sidelink communication may include V2X communication. V2X communication involves not only direct radio information exchange between vehicles (e.g., vehicles 302 and 304) themselves, but also direct radio information exchange between vehicles 302 / 304 and infrastructure (e.g., roadside units (RSUs) 306) (such as streetlights, buildings, traffic cameras, toll booths, or other stationary objects), between vehicles 302 / 304 and pedestrians 308, and between vehicles 302 / 304 and wireless communication networks (e.g., base station 310). In some examples, V2X communication may be implemented according to the New Radio (NR) Cellular V2X standard defined by 3GPP (Release 16) or other suitable standards.

[0089] V2X communication enables vehicles 302 and 304 to acquire information related to weather, nearby accidents, road conditions, the activities of nearby vehicles and pedestrians, objects near the vehicles, and other relevant information that can be used to improve the driving experience and enhance vehicle safety. For example, such V2X data can enable autonomous driving and improve road safety and traffic efficiency. For instance, V2X-connected vehicles 302 and 304 can use the exchanged V2X data to provide collision warnings, road hazard warnings, approach emergency vehicle warnings, pre-collision / post-collision warnings and information, emergency braking warnings, traffic congestion warnings, lane change warnings, intelligent navigation services, and other similar information. Additionally, V2X data received by a pedestrian / cyclist's V2X-connected mobile device can be used to trigger warning sounds, vibrations, flashing lights, etc., in situations where a hazard is imminent.

[0090] Sidelink communication between vehicle UEs (V-UEs) 302 and 304, or between V-UEs 302 or 304 and RSUs 306 or pedestrian UEs (P-UEs) 308, can occur on sidelink 312 using the Proximity Service (ProSe) PC5 interface. In various aspects of this disclosure, the PC5 interface can be further used to support D2D sidelink 312 communication in other proximity use cases, such as V2X. Examples of other proximity use cases may include smart wearable devices, public safety, or commercially based proximity services (e.g., entertainment, education, office, healthcare, and / or interaction). Figure 3 In the example shown, ProSe communication may further occur between UEs 314 and 316.

[0091] ProSe communication supports different operating scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario where a UE (e.g., UEs 314 and 316) is outside the coverage area of ​​a base station (e.g., base station 210), but each UE is still configured for ProSe communication. Partial coverage refers to a scenario where some UEs (e.g., V-UE 304) are outside the coverage area of ​​base station 310, while other UEs (e.g., V-UE 302 and P-UE 308) are communicating with base station 310. In-coverage refers to a scenario where a UE (e.g., V-UE 302 and P-UE 308) is communicating with base station 310 (e.g., gNB) via a Uu (e.g., cellular interface) connection to receive ProSe service authorization and provisioning information to support ProSe operation.

[0092] To facilitate D2D sidelink communication on sidelink 312 between, for example, UEs 314 and 316, UEs 314 and 316 may transmit discovery signals between them. In some examples, each discovery signal may include synchronization signals, such as a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS), which facilitate device discovery and communication synchronization on sidelink 312. For example, the discovery signal may be used by UE 316 to measure the signal strength and channel state of a potential sidelink (e.g., sidelink 314) with another UE (e.g., UE 312). UE 316 may use these measurements to select a UE (e.g., UE 314) for sidelink communication or relay communication.

[0093] In 5G NR sidelinks, sidelink communication can utilize transmit or receive resource pools. For example, the minimum resource allocation unit in frequency can be a subchannel (e.g., which may include, for example, 10, 15, 20, 25, 50, 75, or 100 coherent resource blocks), and the minimum resource allocation unit in time can be a time slot. The radio resource control (RRC) configuration of the resource pool can be pre-configured (e.g., factory settings on the UE, for example, as determined by the sidelink standard or specification) or configured by the base station (e.g., base station 310).

[0094] Additionally, sidelink (e.g., PC5) communication can have two main resource allocation operation modes. In the first mode (Mode 1), the base station (e.g., gNB) 310 can allocate resources to sidelink devices (e.g., V2X devices or other sidelink devices) for sidelink communication between the sidelink devices in various ways. For example, the base station 310 can dynamically allocate sidelink resources to the sidelink devices in response to sidelink resource requests from the sidelink devices (e.g., dynamic granting). The base station 310 can further activate pre-configured sidelink grants (e.g., configured granting) for sidelink communication between the sidelink devices. In Mode 1, the transmitting sidelink device can report sidelink feedback to the base station 310.

[0095] In the second mode (Mode 2), sidelink devices can autonomously select sidelink resources for their sidelink communication. In some examples, the transmitting sidelink device can perform resource / channel sensing to select unoccupied resources (e.g., subchannels) on the sidelink channel. Signaling on the sidelink is identical between the two modes. Therefore, from the receiver's perspective, there is no difference between these modes.

[0096] In some examples, sidelink (e.g., PC5) communication can be scheduled using sidelink control information (SCI). An SCI may comprise two phases. Phase 1 sidelink control information (phase one SCI) may be referred to herein as SCI-1. Phase 2 sidelink control information (phase two SCI) may be referred to herein as SCI-2.

[0097] SCI-1 can be transmitted on the Physical Sidelink Control Channel (PSCCH). SCI-1 may include resource allocation for sidelink resources and information for decoding the second-stage sidelink control information (i.e., SCI-2). SCI-1 may further identify the priority level of the PSSCH (e.g., Quality of Service (QoS)). For example, Ultra-Reliable Low Latency Communication (URLLC) traffic may have a higher priority than Short Message Service (SMS) traffic. SCI-1 may also include PSSCH resource assignment and resource reservation period (if enabled). Additionally, SCI-1 may include PSSCH demodulation reference signal (DMRS) modes (if more than one mode is configured). DMRS can be used by the receiver for radio channel estimation to demodulate the associated physical channel. As indicated, SCI-1 may also include information about SCI-2; for example, SCI-1 may disclose the format of SCI-2. Here, the format indicates the resource size of SCI-2 (e.g., the number of REs allocated for SCI-2), the number of PSSCH DMRS ports, and the modulation and coding scheme (MCS) index. In some examples, SCI-1 can use two bits to indicate the SCI-2 format. Therefore, in this example, four different SCI-2 formats can be supported. SCI-1 may include additional information useful for establishing and decoding PSSCH resources.

[0098] SCI-2 can also be transmitted on the PSSCH and may contain information for decoding the PSSCH. Depending on some aspects, SCI-2 includes a 16-bit Layer 1 (L1) destination identifier (ID), an 8-bit L1 source ID, a Hybrid Automatic Repeat Request (HARQ) process ID, a New Data Indicator (NDI), and a Redundancy Version (RV). For unicast communication, SCI-2 may further include a CSI report trigger. For multicast communication, SCI-2 may further include a zone identifier and the maximum communication range for NACK. SCI-2 may include other information useful for establishing and decoding PSSCH resources.

[0099] Figure 4 This is a block diagram illustrating a wireless communication system 400 that communicates with a remote wireless communication device via at least one relay wireless communication device to a network, supported by several aspects. The wireless communication system 400 includes a remote wireless communication device 420 (e.g., a UE), a relay wireless communication device 425 (e.g., a UE), a first base station (e.g., a gNB) 410, a second base station 415 (e.g., a gNB), and a core network 405 (e.g., a 5G NR network).

[0100] The remote wireless communication device 420 may communicatively couple to the first base station 410 via a cellular link 445 (e.g., Uu). Similarly, the relay wireless communication device 425 may communicatively couple to the second base station 415 via a cellular link 450 (e.g., Uu). In the example described herein, the remote and relay wireless communication devices 420 and 425 may communicatively couple to each other via a side link 455 (e.g., PC5). However, it should be understood that the remote and relay wireless communication devices 420 and 425 may communicatively couple to each other via other types of links, such as via WiFi or Bluetooth. The first and second base stations 410 and 415 may communicatively couple to each other via a signaling link 440 (e.g., Xn). The first base station 410 is coupled to the core network 405 via control plane (e.g., N2) and user plane (e.g., N3) links (collectively referred to as 430). Similarly, the second base station 415 is coupled to the core network 405 via control plane (e.g., N2) and user plane (e.g., N3) links (collectively referred to as 435).

[0101] In many scenarios, remote wireless communication device 420 uses cellular link 445 to transmit traffic or user plane data to core network 405 via a first base station. However, in some situations, cellular link 445 between remote wireless communication device 420 and first base station 410 may be compromised for all or some services (e.g., due to interference, noise, low signal-to-noise ratio (SNR), equipment failure, etc.). In such scenarios, remote wireless communication device 420 may seek to transmit data to core network 405 via relay wireless communication device 425. In this case, data is transmitted from remote wireless communication device 420 to relay wireless communication device 425 via side link 455; relay wireless communication device 425 then relays the data to second base station 415 via cellular link 450; and base station 415 forwards the data to core network 405 via user plane (e.g., N3) link 435.

[0102] The 5G NR specification includes policy control information for wireless communication devices to control how data can be routed to the core network 405 based on certain criteria. The Access Network Discovery and Selection Policy (ANDSP) specification includes some policy control information. The ANDSP specification provides rules for wireless communication devices to route data to the core network 405 using non-3GPP access networks (e.g., WiFi networks). The UE Routing Policy (URSP) specification includes other policy control information. The URSP specification provides rules on how wireless communication devices should route data via 3GPP and non-3GPP networks based on the specific application generating the data (e.g., voice calls, social media, games, etc.) and characteristics associated with the data routing session. The URSP specification can provide traffic descriptors specifying trunk operations, including routing descriptors specifying Protocol Data Unit (PDU) session parameters.

[0103] Other policy control information provides rules on how to route data between wireless communication devices (outside the 5G NR network) via Proximity Service (ProSe) test link communication. ProSe policies are typically tailored for public safety services (e.g., firefighters, police, emergency responders, etc.) and certain commercial applications (such as interactive games). When it comes to routing data from a remote wireless communication device (e.g., device 420) to the core network 405 via one or more other relay wireless communication devices (e.g., device 425), the aforementioned policy control information lacks data routing rules. Here, device 420 is referred to as the "remote" device because it generates data to be transmitted to the core network 405, and the other device 425 is referred to as the "relay" device because it relays data from the remote device 420 to the core network 405 via its cellular link 450 to the second base station 415.

[0104] These policy control information enhancements provide rules for three (3) types of relay data routing options. First, there is a Layer 3 (L3) relay data routing option, where data is routed from the remote wireless communication device 420 via side link 455, relay wireless communication device 425, cellular link 450, second base station 415, and user plane (N3) link 435 to the core network 405 via Internet Protocol (IP) or L3 routing.

[0105] Secondly, there exists a Layer 3 (L3) relay with non-3GPP Networking Function (N3IWF) data routing options, where data is routed via Internet Protocol (IP) or L3 routing from the remote wireless communication device 420 to the core network 405 via side link 455, relay wireless communication device 425, cellular link 450, second base station 415, and user plane (N3) link 435, as further discussed herein.

[0106] Third, there is a Layer 2 (L2) relay data routing option, where data is routed via L2 routing from the remote wireless communication device 420 to the user plane network device on the core network 405 via side link 455, relay wireless communication device 425, cellular link 450, second base station 415 and user plane (N3) link 435 to the core network 405, as discussed further herein.

[0107] Additionally, the policy control information can be enhanced to specify the PC5 path type, where the first wireless communication device 420 communicates with the second wireless communication device 425 via a side link 455 (e.g., PC5), rather than in the context of relaying data to the core network. In such cases, the policy control information may include a non-seamless offload indication indicating that data associated with an application identifier is to be transmitted to the second wireless communication device 425 outside of the PDU session. For example, the non-seamless offload indication in UE Routing Policy (URSP) rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1 can be modified to identify the PC5 data routing option. Alternatively, URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1 can be modified to add new parameters, such as a side link (SL) relay non-seamless offload indication identifying the PC5 routing option. Policy control information can also be enhanced to specify the access type that identifies PC5 data routing options. For example, the access type in URSP rule table 6.6.2.1-3 in 3GPP TS 23.503v16.4.1 can be modified to add PC5 routing options to the access type.

[0108] Figure 5This is a block diagram illustrating another wireless communication system 500 that communicates to a network via a remote wireless communication device through at least one relay wireless communication device, supported by several aspects. Wireless communication system 500 is an exemplary implementation of the previously discussed wireless communication system 400. Wireless communication system 500 was mentioned in the discussion of the three (3) relay data routing options above.

[0109] The wireless communication system 500 includes a remote wireless communication device 520 (e.g., a remote UE), a relay wireless communication device 525 (e.g., a relay UE), a first base station 510, a second base station 515, and a core network. The core network includes an Access and Mobility Management Function (AMF) 560, a First User Plane Function (UPF) network device 565, an N3IWF network device 570, and a second UPF network device 590. The core network is coupled to a backhaul data network 598 via a user plane link 595 (e.g., N6).

[0110] Similarly, the remote wireless communication device 520 may be communicatively coupled to the first base station 510 via a cellular link 545 (e.g., Uu). The relay wireless communication device 525 may be communicatively coupled to the second base station 515 via a cellular link 550 (e.g., Uu). The remote and relay wireless communication devices 520 and 525 may be communicatively coupled to each other via a side link 555 (e.g., PC5).

[0111] The first base station 510 is coupled to the AMF network device 560 via a control plane link 530a (e.g., N2). The first base station 510 is also coupled to the second UPF network device 590 via a user plane link 530b (e.g., N3). The second base station 515 is coupled to the AMF network device 560 via a control plane link 535a (e.g., N2). The second base station 515 is also coupled to the first UPF network device 565 via a user plane link 535b (e.g., N3). The first UPF network device 565 is coupled to the N3IWF network device 570 via a user plane link 580 (e.g., N6). The N3IWF network device 570 is coupled to the second UPF network device 590 via a user plane link 585 (e.g., N3). Additionally, the second UPF network device 590 is coupled to the backhaul data network 598 via a user plane link 595 (e.g., N6).

[0112] The N3IWF network device 570 allows wireless communication devices to communicate with the N3IWF via a PDU session over non-3GPP networks (such as WiFi networks). Prior to the inclusion of the N3IWF network device 570, wireless communication devices communicating with the core network over non-3GPP networks could not do so via a PDU session. Consequently, the security, privacy, and other features provided for PDU sessions could not be provided to such wireless communication devices. For example, such wireless communication devices rely on the security and privacy features provided by non-3GPP networks through which data traverses. By including the N3IWF network device 570, a PDU session can be established between the wireless communication device and the N3IWF network device 570, even if data traverses a non-3GPP network.

[0113] Figure 6A This is a control plane protocol stack diagram associated with Layer 3 (L3) relay data routing options, based on several aspects. The control protocol stack on the left relates to remote wireless communication devices (e.g., remote UEs). The control protocol stack on the right relates to relay wireless communication devices (e.g., relay UEs). The communication interface between the remote communication devices and the relay communication devices is a sidelink interface (e.g., a PC5 interface).

[0114] The remote UE includes a control plane protocol stack, which includes: PC5 physical layer (PC5-PHY) 602 to form layer 1 (L1) of the protocol stack; PC5 media access control (PC5-MAC) 604, PC5 radio link control (PC5-RLC) 606 and PC5 packet data convergence protocol (PC5-PDCP) 608 to form layer 2 (L2) of the protocol stack; and PC5 radio resource control (PC5-RRC) 610 and PC5 signaling (PC5-S) 612 to form layer 3 (L3) of the protocol stack.

[0115] Similarly, the relay UE includes a control plane protocol stack, which includes: PC5 physical layer (PC5-PHY) 620 to form layer 1 (L1) of the protocol stack; PC5 media access control (PC5-MAC) 622, PC5 radio link control (PC5-RLC) 624 and PC5 packet data convergence protocol (PC5-PDCP) 626 to form layer 2 (L2) of the protocol stack; and PC5 radio resource control (PC5-RRC) 630 and PC5 signaling (PC5-S) 630 to form layer 3 (L3) of the protocol stack.

[0116] According to the L3 relay data routing options, the remote wireless communication device establishes a sidelink (e.g., a PC5 link or a unicast link) with the relay wireless communication device. The remote wireless communication device establishes the sidelink by sending a sidelink establishment signaling to the relay wireless communication device, which is processed by Layer 3, 2, and 1 Proximity Service (ProSe) protocol stack operations. This involves the remote wireless communication device performing Layer 3 protocol stack operations (such as PC5-S 612 and PC5-RRC 610 operations) on the signaling; performing Layer 2 protocol stack operations (including PC5-PDCP 608, PC5-RLC 606, and PCT5-MAC 604 operations) on the signaling; and performing Layer 1 protocol stack operations (including PC5-PHY 602 operations) on the signaling.

[0117] The relay wireless communication device performs complementary layer 1, 2, and 3 operations on signaling received from a remote wireless communication device to establish a side link with the remote wireless communication device. For example, these include performing layer 1 protocol stack operations, including PC5-PHY layer 620 operations, on signaling received from the remote wireless communication device; performing layer 2 protocol stack operations, including operations performed by PC5-MAC layer 622, PC5-RLC layer 624, and PC5-PDCP layer 626, on signaling received from the PC5-PHY layer; and performing layer 3 protocol stack operations, including PC5-S layer 630 and PC5-RRC layer 628 operations, on signaling from layer 2 operations.

[0118] although Figure 6A Not shown, but the relay wireless communication device establishes a PDU session to relay data from the remote wireless communication device to the core network via the corresponding base station. Note that in the L3 relay data routing option, the PDU session does not extend to the remote wireless communication device. The relay wireless communication device merely offloads data from the remote wireless communication device via the established side link for subsequent forwarding or relaying by the relay wireless communication device via the PDU session. In L3 relay routing operations, the remote wireless communication device may not include either a non-access stratum (NAS) connection to the core network (e.g., AMF) or an access stratum (AS) connection to a base station coupled to the core network. Furthermore, in L3 relay routing operations, the relay wireless communication device reports the presence of the remote wireless communication device to the core network (e.g., AMF).

[0119] Figure 6B This is a user plane protocol stack diagram associated with Layer 3 (L3) relay data routing options based on several aspects. The protocol stack on the left relates to remote wireless communication devices (e.g., remote UEs), the second protocol stack from the left relates to relay wireless communication devices (e.g., relay UEs), the third protocol stack from the left relates to base stations, and the rightmost protocol stack relates to UPF network devices on the core network.

[0120] The remote UE includes a user plane protocol stack, which includes: PC5-PHY 602 to form layer 1 (L1) of the protocol stack; PC5-MAC 604, PC5-RLC 606, PC5-PDCP 608 and PC5 Serving Data Adaptation Protocol (PC5-SDAP) 614 to form layer 2 (L2) of the protocol stack; Internet Protocol (IP) 616 to form layer 3 (L3) of the protocol stack; and application layer 618.

[0121] The relay UE includes a user plane protocol stack comprising: PC5-PHY 620 to form Layer 1 (L1) of the protocol stack; PC5-MAC 622, PC5-RLC 624, PC5-PDCP 626, and PC5-SDAP 632 to form Layer 2 (L2) of the protocol stack; and IP relay 634 to form Layer 3 (L3) of the protocol stack. The relay UE further includes: New Radio (NR) Service Data Adaptation Protocol (NR-SDAP) 636, NR-PDCP 638, NR-RLC 640, and NR-MAC 642 to form Layer 2 (L2) of the protocol stack; and NR-PHY 644 to form Layer 1 (L1) of the protocol stack.

[0122] The base station includes a user plane protocol stack comprising: NR-PHY 650 to form Layer 1 (L1) of the protocol stack; NR-MAC 652, NR-RLC 654, NR-PDCP 656, and NR-SDAP 658 to form Layer 2 (L2) of the protocol stack; and a relay 660 to form Layer 3 (L3) of the protocol stack. The base station further includes a General Packet Radio Service (GPRS) tunneling protocol for user plane (GTP-U) 662, User Datagram Protocol (UDP) / IP 664, L2 layer 666, and L1 layer 668. The UPF includes L1 layer 670, L2 layer 672, UDP / IP 674, GTP-U 676, and IP layer 678.

[0123] As the name suggests, L3 relay data routing operations route application-generated data from a remote wireless communication device to the core network via L3 routing (such as Internet Protocol (IP) routing). For example, a specific application running on a remote wireless communication device generates data that needs to be routed to the core network and may be further routed down to external data networks. IP protocol stack operations generate IP packets containing this data. The remote wireless communication device may have already received an IP address that identifies the remote wireless communication device as the originator of the IP packet. This IP packet is then processed by the remote wireless communication device's PC5 protocol stack (such as Serving Data Application Protocol (PC5-SDAP) layer 614, Packet Data Convergence Protocol (PC5-PDCP) layer 608, PC5-RLC layer 606, PC5-MAC layer 604, and PC5-PHY layer 602).

[0124] The relay wireless communication device performs complementary PC5 protocol stack operations on IP packets received from a remote wireless communication device via a side link (e.g., PC5). These include PC5-PHY layer 620, PC5-MAC layer 622, PC5-RLC layer 624, PC5-PDCP layer 626, and PC5-SDAP layer 632 operations. The IP relay processing component transmits IP packets for transmission to the base station via the Uu link through the NR protocol processing stack (such as NR-SDAP 636, NR-PDCP 638, NR-RLC 640, NR-MAC 642, and NR-PHY 644 layers).

[0125] The base station performs complementary NR protocol stack operations on IP packets received from relay wireless communication equipment via cellular links (e.g., Uu). These include NR-PHY 650, NR-MAC 652, NR-RLC 654, NR-PDCP 656, and NR-SDAP 658 layer operations. The IP relay processing component uses, for example, GTP-U 662, UDP / IP 664, L2 666, and L1 668 layer operations to send IP packets to the core network user plane protocol processing stack.

[0126] UPF network devices perform complementary core network user plane protocol operations on IP packets received from base stations via the N3 user plane link, including L1 670, L2 672, UDP / IP 674, GTP-U 676, and IP 678 layer operations. The UPF network devices can then forward the IP packets to external data networks via the N6 user plane link. As previously discussed, the transmission of IP packets from the relay wireless communication device to the core network can be performed according to a PDU session. In this example, the PDU session does not extend to the remote wireless communication device because the relay wireless communication device is merely offloading data to / from the remote wireless communication device for L3 relay purposes, which occurs outside the PDU session.

[0127] Figure 7A This is based on a control plane protocol stack diagram associated with a Layer 3 (L3) relay with N3IWF data routing options. In an L3 relay with N3IWF data routing options, the remote wireless communication device is visible to the core network as if it were behind a non-3GPP network. Thus, in this scenario, the remote wireless communication device has a NAS connection to the core network (e.g., AMF) via the relay wireless communication device, and an AS connection to the base station via the relay wireless communication device. Accordingly, the remote wireless communication device can establish IP PDU sessions with N3IWF network devices on the core network.

[0128] The control protocol stack on the left involves the remote wireless communication device (e.g., a remote UE). The control protocol stack in the middle involves the relay wireless communication device (e.g., a relay UE). The control protocol stack on the right involves the base station. The communication interface between the remote wireless communication device and the relay wireless communication device is a sidelink interface (e.g., a PC5 interface). The communication interface between the relay wireless communication device and the base station is a cellular interface (e.g., a Uu interface).

[0129] The remote UE includes a control plane protocol stack, which includes: PC5-PHY 702 to form layer 1 (L1) of the protocol stack; PC5-MAC 704, PC5-RLC 706, and PC5-PDCP 708 to form layer 2 (L2) of the protocol stack; and NR-RRC 710, NAS Mobility Management (NAS-MM) 712, and NAS Session Management (NAS-SM) 714 to form layer 3 (L3) of the protocol stack.

[0130] The relay UE includes a control plane protocol stack, comprising: PC5-PHY 720 to form Layer 1 (L1) of the protocol stack; PC5-MAC 722, PC5-RLC 724, and PC5-PDCP 726 to form Layer 2 (L2) of the protocol stack; and PC5-RRC 728, PC5-S730, and an adapted relay 732 to form Layer 3 (L3) of the protocol stack. The relay UE further includes: NR-RLC 734 and NR-MAC 736 to form Layer 2 (L2) of the protocol stack; and NR-PHY 738 to form Layer 1 (L1) of the protocol stack.

[0131] The base station includes a control plane protocol stack, comprising: NR-PHY 740 to form Layer 1 (L1) of the protocol stack; NR-MAC 742, NR-RLC 744, adaptation layer 746, and NR-PDCP 748 to form Layer 2 (L2) of the protocol stack; and NR-RRC 750 to form Layer 3 (L3) of the protocol stack. The base station further includes an N2 protocol stack 752.

[0132] According to the L3 relay with N3IWF data routing options, the remote wireless communication device establishes an IP PDU session with the N3IWF network device in the following ways: performing NAS protocol stack processing operations on the signaling, such as NAS-SM 714 and NAS-MM 712 operations; performing NR protocol processing operations on the signaling, such as NR-RRC 710 and NR-PDCP 708 operations; and performing PC5 protocol processing operations, such as PC5-RLC 706, PC5-MAC 704 and PC5-PHY 702 operations.

[0133] The relay wireless communication device then performs complementary PC5 protocol stack processing operations on signaling received from remote wireless communication devices via a side link (e.g., PC5). These operations include PC5-PHY 720, PC5-MAC 722, and PC5-RLC 724 operations. This signaling is then provided to an adapted relay layer 732 for the relay wireless communication device to enhance the PC5 session, multiplexing data from one or more other remote wireless communication devices for transmission to the core network. This signaling is then processed via lower NR protocol layer stacks such as NR-RLC 734, NR-MAC 736, and NR-PHY 738.

[0134] The base station then performs complementary NR protocol stack processing operations on signaling received from the relay wireless communication device via a cellular link (e.g., Uu). These operations include NR-PHY 740, NR-MAC 742, and NR-RLC 744. The signaling is then provided to the adaptive relay layer 746 so that the base station can demultiplex data from all remote wireless communication devices (one or more) for transmission to the core network. The signaling is then processed via higher NR protocol layer stacks (such as NR-PDCP 748 and NR-RRC 750). The base station then processes the signaling via the N2 control plane protocol stack 752 and provides it to the AMF via control plane link N2. The AMF then establishes an IP PDU session between the remote wireless communication device and the N3IWF network device.

[0135] Figure 7BThis is a user plane protocol stack diagram associated with a Layer 3 (L3) relay with N3IWF data routing options, based on several aspects. As previously discussed, the IP PDU session extends from the remote wireless communication device to the N3IWF network device. The protocol stack on the left relates to the remote wireless communication device (e.g., a remote UE), the second protocol stack from the left relates to the relay wireless communication device (e.g., a relay UE), the third protocol stack from the left relates to the base station, the fourth protocol stack from the left relates to the UPF network device, and the rightmost protocol stack relates to the N3IWF network device on the core network.

[0136] The remote UE includes a user plane protocol stack, which includes: PC5-PHY 702 to form layer 1 (L1) of the protocol stack; PC5-MAC 704 and PC5-RLC 706 to form layer 2 (L2) of the protocol stack; and PDU layer 716 and application layer 718 to form layer 3 (L3) of the protocol stack.

[0137] The relay UE includes a user plane protocol stack, which includes: PC5-PHY 720 to form Layer 1 (L1) of the protocol stack; PC5-MAC 722, PC5-RLC 724 and adapted relay 732 to form Layer 2 (L2) of the protocol stack. The user plane protocol stack further includes: NR-RLC 734 and NR-MAC 736 to form Layer 2 (L2) protocol stack; and NR-PHY 738 to form Layer 1 (L1) of the protocol stack.

[0138] The base station includes a user plane protocol stack, comprising: NR-PHY 740 to form Layer 1 (L1) of the protocol stack; and NR-MAC 742, NR-RLC 744, and an adaptation relay layer 746 to form Layer 2 (L2) of the protocol stack. The base station further includes an N3 protocol stack 754. The UPF includes an N3 / N6 protocol stack 760. The N3IWF includes an N6 / N3 protocol stack 770 and a PDU layer 772.

[0139] As the name suggests, L3 relay with N3IWF data routing operations routes application-generated data from a remote wireless communication device to an N3IWF network device via L3 (IP) routing per PDU session. For example, a specific application 718 running on a remote wireless communication device generates data to be routed to the N3IWF network device and subsequently further routed down to an external data network. The PDU layer 716 generates IP packets containing this data. The remote wireless communication device has an IP address because it has a NAS context with the core network. The IP packets are then processed by the remote wireless communication device's PC5 protocol stack (such as PC5-RLC 706, PC5-MAC 704, and PC5-PHY 702 layers).

[0140] The relay wireless communication device performs complementary PC5 protocol stack operations on IP packets received from remote wireless communication devices via a side link (e.g., PC5). These include PC5-PHY 720, PC5-MAC 722, and PC5-RLC 724 operations. The adapting relay layer 732 can multiplex data from the remote wireless communication device with data from one or more other remote wireless communication devices. The adapting relay layer 732 transmits IP packets for transmission to the base station via the Uu link through NR protocol processing stacks such as NR-RLC 734, NR-MAC 736, and NR-PHY 738 layers.

[0141] The base station performs complementary NR protocol stack operations on IP packets received from relay wireless communication equipment via cellular links (e.g., Uu). These include NR-PHY 740, NR-MAC 742, and NR-RLC 744. An adaptation layer 746 at the base station demultiplexes data from remote wireless communication equipment that has been multiplexed by the relay wireless communication equipment. The base station processes IP packets via the N3 user plane protocol stack 754.

[0142] The UPF network device performs complementary N3 user plane protocol stack operations on IP packets received from the base station via the N3 user plane link, and performs N6 user plane protocol stack operations via the N3 / N6 user plane protocol stack. The N3IWF network device then performs complementary N6 user plane protocol stack operations on IP packets received from the UPF network device via the N6 user plane link, and performs N3 user plane protocol stack operations via the N3 / N6 user plane protocol stack. The N3IWF network can then transmit IP packets to an external data network via another N3 interface, the UPF network device, and another N6 interface.

[0143] Figure 8A This is based on a control plane protocol stack diagram associated with Layer 2 (L2) relay data routing options. In L2 relay data routing options, remote wireless communication devices are visible to the core network. Therefore, in this scenario, the remote wireless communication device has a NAS connection to the core network (e.g., AMF) via the relay wireless communication device, and an AS connection to the base station via the relay wireless communication device. Accordingly, the remote wireless communication device can establish a PDU session with the core network.

[0144] The control protocol stack on the left involves the remote wireless communication device (e.g., a remote UE). The control protocol stack in the middle involves the relay wireless communication device (e.g., a relay UE). The control protocol stack on the right involves the base station. The communication interface between the remote wireless communication device and the relay wireless communication device is a sidelink interface (e.g., a PC5 interface). The communication interface between the relay wireless communication device and the base station is a cellular interface (e.g., a Uu interface).

[0145] The remote UE includes a control plane protocol stack, which includes: PC5-PHY 802 to form layer 1 (L1) of the protocol stack; PC5-MAC 804, PC5-RLC 806, and PC5-PDCP 808 to form layer 2 (L2) of the protocol stack; and NR-RRC 810, NAS-MM 812, and NAS-SM 814 to form layer 3 (L3) of the protocol stack.

[0146] The relay UE includes a control plane protocol stack, comprising: PC5-PHY 820 to form Layer 1 (L1) of the protocol stack; PC5-MAC 822, PC5-RLC 824, and PC5-PDCP 826 to form Layer 2 (L2) of the protocol stack; and PC5-RRC 828, PC5-S830, and an adapted relay 832 to form Layer 3 (L3) of the protocol stack. The relay UE further includes: NR-RLC 834 and NR-MAC 836 to form Layer 2 (L2) of the protocol stack; and NR-PHY 838 to form Layer 1 (L1) of the protocol stack.

[0147] The base station includes a control plane protocol stack, comprising: NR-PHY 840 to form Layer 1 (L1) of the protocol stack; NR-MAC 842, NR-RLC 844, adaptation layer 846, and NR-PDCP 848 to form Layer 2 (L2) of the protocol stack; and NR-RRC 850 to form Layer 3 (L3) of the protocol stack. The base station further includes an N2 protocol stack 852.

[0148] According to the L2 relay data routing options, remote wireless communication devices establish PDU sessions with the core network in the following ways: performing NAS protocol stack processing operations on the signaling, such as NAS-SM 814 and NAS-MM 812 operations; performing NR protocol processing operations on the signaling, such as NR-RRC 810 and NR-PDCP 808 operations; and performing PC5 protocol processing operations, such as PC5-RLC 806, PC5-MAC 804 and PC5-PHY 802 operations.

[0149] The relay wireless communication device then performs complementary PC5 protocol stack processing operations on signaling received from remote wireless communication devices via a side link (e.g., PC5). These operations include PC5-PHY 820, PC5-MAC 822, and PC5-RLC 824. This signaling is then provided to an adaptive relay layer for the relay wireless communication device to enhance the PC5 session, multiplexing data from one or more other remote wireless communication devices for transmission to the core network. This signaling is then processed by lower NR protocol layer stacks (such as NR-RLC 834, NR-MAC 836, and NR-PHY 838 layers) for transmission to the base station via the Uu link.

[0150] The base station then performs complementary NR protocol stack processing operations on signaling received from the relay wireless communication device via a cellular link (e.g., Uu). These operations include NR-PHY 840, NR-MAC 842, and NR-RLC 844. The signaling is then provided to the adaptive relay layer 846 for the base station to demultiplex data from all remote wireless communication devices (one or more) for transmission to the core network. The signaling is then processed via higher NR protocol layer stacks (such as NR-PDCP 848 and NR-RRC 850 layers). The base station then processes the signaling via the N2 control plane protocol stack 852 and provides it to the AMF via control plane link N2. The AMF then establishes a PDU session between the remote wireless communication device and the core network.

[0151] Figure 8B This is a user plane protocol stack diagram associated with Layer 2 (L2) relay data routing options, based on several aspects. As previously discussed, the PDU session extends from the remote wireless communication device to the core network. The protocol stack on the left relates to the remote wireless communication device (e.g., a remote UE), the second protocol stack from the left relates to the relay wireless communication device (e.g., a relay UE), the third protocol stack from the left relates to the base station, and the rightmost protocol stack relates to the UPF network device.

[0152] The remote UE includes a user plane protocol stack, which includes: PC5-PHY 802 to form layer 1 (L1) of the protocol stack; PC5-MAC 804, PC5-RLC 806, NR-PDCP 808 and NR-SDAP 816 to form layer 2 (L2) of the protocol stack; and PDU layer 818 and application layer 819 to form layer 3 (L3) of the protocol stack.

[0153] The relay UE includes a user plane protocol stack, which includes: PC5-PHY 820 to form Layer 1 (L1) of the protocol stack; PC5-MAC 822, PC5-RLC 824 and adapted relay 832 to form Layer 2 (L2) of the protocol stack. The user plane protocol stack further includes: NR-RLC 834 and NR-MAC 836 to form Layer 2 (L2) protocol stack; and NR-PHY 838 to form Layer 1 (L1) of the protocol stack.

[0154] The base station includes a user plane protocol stack, comprising: NR-PHY 840 to form Layer 1 (L1) of the protocol stack; and NR-MAC 842, NR-RLC 844, adaptation layer 846, NR-PDCP 848, and NR-SDAP 854 to form Layer 2 (L2) of the protocol stack. The base station further includes an N3 protocol stack 856. The UPF includes an N3 protocol layer 860.

[0155] As the name suggests, L2 relay data routing operations route application-generated data from remote wireless communication devices to core network devices via L2 routing according to PDU sessions. For example, a specific application 819 running on a remote wireless communication device generates data to be routed to the core network and then further routed down to external data networks. The PDU session layer 818 generates PDU packets containing this data. The PDU packets are then processed by the NR-SDAP 816 and NRPDCP 808 layers of the remote wireless communication device and the PC5 protocol stack (such as PC5-RLC 806, PC5-MAC 804, and PC5-PHY 802 layers).

[0156] The relay wireless communication device performs complementary PC5 protocol stack operations on PDU packets received from remote wireless communication devices via a side link (e.g., PC5). These include PC5-PHY 820, PC5-MAC 822, and PC5-RLC 824 operations. The adapting relay layer 832 can multiplex data from the remote wireless communication device with data from one or more other remote wireless communication devices. The adapting relay layer 832 transmits PDU packets for transmission to the base station via the Uu link through NR protocol processing stacks such as NR-RLC 834 / NR-MAC 836 and NR-PHY 838 layers.

[0157] The base station performs complementary lower-layer NR protocol stack operations on PDU packets received from relay wireless communication equipment via cellular links (e.g., Uu). These include NR-PHY 840, NR-MAC 842, and NR-RLC 844 operations. Adaptation layer 846 demultiplexes data from remote wireless communication equipment that may have been multiplexed by the relay wireless communication equipment. The base station processes PDU packets via higher NR protocol layers (such as NR-SDAP 854 and NR-PDCP 848) and subsequently performs N3 user plane protocol stack processing via N3 user plane protocol stack 856.

[0158] The UPF network device performs complementary N3 user plane protocol stack layer 860 operations on PDU packets received from the base station via the N3 user plane link, and performs N6 user plane protocol stack operations. The UPF network device can then send data to an external data network via IP packets through the N6 interface.

[0159] Figure 9 This is a flowchart of an exemplary signaling diagram 900 illustrating the use of L3 relay data routing options to route data from a remote wireless communication device to a network, based on several aspects. According to diagram 900, the remote wireless communication device (e.g., a remote UE) generates data for transmission to the network at 902 based on an application.

[0160] Subsequently, at 904, the remote wireless communication device selects an L3 relay data routing option from a set of data routing options (e.g., L3 relay, L3 relay with N3IWF, and L2 relay options) based on policy control information to route the data to the network. For example, the policy control information may include an application identifier (ID) that identifies the application that generated the data as per operation 902. The policy control information may further include a list of routing descriptors that identifies a list of data routing options that the remote wireless communication device will use to send the data to the network. In this example, the routing descriptor list identifies the L3 relay data routing option, but it may also identify both L3 relay and L2 relay data routing options with N3IWF. As an example, URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1 can be modified to include L3 trunks, L3 trunks with N2IWF, and L2 trunk data routing options as available data routing options for applications identified by the corresponding application identifiers in the table.

[0161] Because L3 relay data routing options do not have a PDU session extending to the remote wireless communication device, policy control information can include a non-seamless offload indication that indicates data associated with the application identifier is to be transmitted to the relay wireless communication device outside the PDU session. For example, the non-seamless offload indication in URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1 can be modified to identify both the PC5 L3 relay data routing option and the PC5 routing option (UE-to-UE without relay). Alternatively, URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1 can be modified to add new parameters, such as a side-link (SL) relay non-seamless offload indication that identifies both the PC5 L3 relay data routing option and the PC5 routing option.

[0162] Subsequently, at 906, the remote wireless communication device transmits or offloads data to a relay wireless communication device (e.g., a relay UE) via a sidelink according to the L3 relay data routing option for routing the data to the network. Furthermore, at 908, the relay wireless communication device establishes a PDU session with the network via the base station based on policy control information according to the L3 relay data routing option for relaying data from the remote wireless communication device to the network. The policy control information may specify Session and Service Continuity (SSC) Mode 1 to preserve the IP address of the relay wireless communication device identified by the PDU session. The policy control information may also specify a Network Slice Selection (NSS), which identifies one or more network slices on which the PDU session is taking place. Additionally, the policy control information may specify the Data Network Name (DNN) of the PDU session. As an example, this policy control information may be included in URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1.

[0163] Subsequently, the relay wireless communication device receives data from the remote wireless communication device and transmits the data to the base station in a PDU session at 910. At 912, the base station receives data from the relay wireless communication device and transmits the data to the network (e.g., a UPF network device) in a PDU session.

[0164] Figure 10 This is a flowchart of an exemplary signaling diagram 1000 illustrating the use of an L3 relay with N3IWF data routing options to route data from a remote wireless communication device to a network, based on some aspects. According to diagram 1000, the remote wireless communication device (e.g., a remote UE) generates data for transmission to the network at 1002 based on an application.

[0165] Subsequently, at 1004, the remote wireless communication device selects an L3 relay with the N3IWF data routing option from a set of data routing options (e.g., L3 relay, L3 relay with N3IWF, and L2 relay options) based on policy control information to route the data to the network. For example, the policy control information may include an application identifier (ID) that identifies the application that generated the data according to operation 1002. The policy control information may further include a list of routing descriptors that identify a list of data routing options that the remote wireless communication device will use to send data to the network. In this example, the routing descriptor list identifies an L3 relay with the N3IWF data routing option, but it may also identify both L3 and L2 relay data routing options. As an example, URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 in 3GPP TS 23.503v16.4.1 can be modified to include L3 trunks, L3 trunks with N2IWF, and L2 trunk data routing options as available data routing options for applications identified by the corresponding application identifiers in the table.

[0166] Because an L3 relay with N3IWF data routing options has PDU sessions extending from a remote wireless communication device through the relay wireless communication device and base station to the network, policy control information can specify Session and Service Continuity (SSC) Mode 1 to preserve the IP address of the remote wireless communication device identified by the PDU session. The policy control information can also specify Network Slice Selection (NSS), which identifies one or more network slices on which the PDU session is taking place. Additionally, the policy control information can specify the Data Network Name (DNN) of the PDU session. The policy control information can specify access type preferences for PC5 Layer 3 with N3IWF data routing options. The policy control information can further specify service criteria for the PDU session, such as security, privacy, Quality of Service (QoS), and network load criteria. The policy control information can further specify authentication criteria, such as the time window for the L3 relay with N3IWF data routing options to be available, and / or the location where the remote wireless communication device needs to be present to make the L3 relay with N3IWF data routing options available. As an example, this policy control information may be included in URSP rule tables 6.6.2.1-1, 6.6.2.1-2 and / or 6.6.2.1-3 from TS23.503.

[0167] Subsequently, at 1006, the remote wireless communication device establishes a PDU session with the N3IWF network device coupled to the network via a relay wireless communication device and a base station. Then, at 1008, the remote wireless communication device transmits data to the relay wireless communication device (e.g., a relay UE) via a side link according to an L3 relay with N3IWF data routing options for routing the data to the network. Furthermore, the relay wireless communication device receives data from the remote wireless communication device and transmits the data to the base station in a PDU session at 1010. Subsequently, the base station receives data from the relay wireless communication device and transmits the data to the N3IWF network device in a PDU session at 1012.

[0168] Figure 11 This is a flowchart illustrating an exemplary signaling diagram for implementing data transmission from a remote wireless communication device to a network using L2 relay data routing options, based on several aspects. According to Figure 1100, the remote wireless communication device (e.g., a remote UE) generates data for transmission to the network at 1102 based on an application.

[0169] Subsequently, in 1104, the remote wireless communication device selects an L2 relay data routing option from a set of data routing options (e.g., L3 relay, L3 relay with N3IWF, and L2 relay options) based on policy control information to route the data to the network. For example, the policy control information may include an application identifier (ID) that identifies the application that generated the data according to operation 1102. The policy control information may further include a list of routing descriptors that identify a list of data routing options that the remote wireless communication device will use to send data to the network. In this example, the routing descriptor list identifies the L2 relay data routing option, but it may also identify both L3 and L2 relay data routing options. As an example, URSP rule tables 6.6.2.1-1 and 6.6.2.1-2 from TS 23.503 can be modified to include L3 relay, L3 relay with N2IWF, and L2 relay data routing options as available data routing options for the application identified by the corresponding application identifier in the table.

[0170] Policy control information can specify access type preferences that identify PC5 Layer 2 data routing options. Policy control information can further specify service criteria for PDU sessions, such as security, privacy, quality of service (QoS), and network load criteria. Policy control information can further specify authentication criteria, such as the time window in which L2 data routing options are available, and / or the location where remote wireless communication devices need to be present to make L2 relay data routing options available. As an example, this policy control information can be included in URSP rule tables 6.6.2.1-1, 6.6.2.1-2, and / or 6.6.2.1-3 from TS 23.503.

[0171] Subsequently, at 1106, the remote wireless communication device establishes a PDU session with a network device (e.g., a UPF device) coupled to the network via a relay wireless communication device and a base station. Furthermore, at 1108, the remote wireless communication device transmits data to the relay wireless communication device (e.g., a relay UE) via a side link according to an L2 relay data routing option for routing the data to the network. Additionally, the relay wireless communication device receives data from the remote wireless communication device and transmits the data to the base station in a PDU session at 1110. Subsequently, the base station receives data from the relay wireless communication device and transmits the data to the network device (e.g., a UPF device) in a PDU session at 1112.

[0172] In any of the data routing signaling diagrams 900, 1000, and 1100 described above, the remote wireless communication device may select a data routing option from the data routing option set for transmitting data to the network via one of these relay options in response to a switch from a cellular routing option (via Uu link) connection with the base station to a side link (PC5). Alternatively, the remote wireless communication device may select a data routing option from the data routing option set when no data routing option is activated. Furthermore, the remote wireless communication device may select a data routing option from the data routing option set based on service criteria associated with the selected option. Alternatively, the remote wireless communication device may establish the option using the corresponding service criteria after selecting the data routing option.

[0173] Furthermore, in any of the aforementioned data routing signaling diagrams 900, 1000, and 1100, the aforementioned policy control information may be located in the URSP policy, in the ProSe policy, or partially in both the URSP and ProSe policies. Additionally, in cases where remote wireless communication devices multiplex data from a set of remote wireless communication devices through an adaptation operation, the base station may perform complementary demultiplexing of the data through a complementary adaptation operation.

[0174] Figure 12 This is a conceptual diagram illustrating an example hardware implementation of an exemplary wireless communication device 1200 employing processing system 1214. For example, wireless communication device 1200 may be as follows: Figure 1 , 2 User equipment (UE) or other scheduled entities configured to communicate in a wireless communication network (e.g., a 5G NR access network), as described in any one or more of 4 and / or 5.

[0175] The wireless communication device 1200 may be implemented using a processing system 1214 including one or more processors 1204. Examples of processors 1204 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, the wireless communication device 1200 may be configured to perform any one or more of the functions described herein. That is, the processor 1204 utilized in the wireless communication device 1200 may be used to implement any or more of the processes described below. In some instances, the processor 1204 may be implemented via a baseband or modem chip, while in other implementations, the processor 1204 itself may include several devices that are different from and distinct from the baseband or modem chip (e.g., in such scenarios they may work together to achieve the examples discussed herein). Furthermore, as mentioned above, various hardware arrangements and components beyond the baseband modem processor can be used in the implementation, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0176] In this example, processing system 1214 can be implemented using a bus architecture generally represented by bus 1202. Depending on the specific application and overall design constraints of processing system 1214, bus 1202 may include any number of interconnect buses and bridges. Bus 1202 communicatively couples together various circuits including one or more processors (generally represented by processor 1204), memory 1205, and computer-readable media (generally represented by computer-readable media 1206). Bus 1202 may also link various other circuits, such as timing sources, peripherals, regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1208 provides an interface between bus 1202 and wireless transceiver 1210. Wireless transceiver 1210 provides means for communicating with various other devices via a transmission medium (e.g., an air interface). User interface 1212 (e.g., keypad, display, touchscreen, speaker, microphone, control knob, etc.) may also be provided. Of course, this type of user interface 1212 is optional and may be omitted in some examples.

[0177] Processor 1204 is responsible for managing bus 1202 and general processing, including the execution of software stored on computer-readable medium 1206. When executed by processor 1204, the software causes processing system 1214 to perform various functions described below for any particular device. Computer-readable medium 1206 and memory 1205 can also be used to store data manipulated by processor 1204 during software execution.

[0178] One or more processors 1204 in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Software may reside on a computer-readable medium 1206.

[0179] Computer-readable medium 1206 may be a non-transient computer-readable medium. As examples, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital multi-purpose discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions accessible and readable by a computer. As examples, computer-readable media may also include carrier waves, transmission lines, and any other suitable medium for transmitting software and / or instructions accessible and readable by a computer. Computer-readable medium 1206 may reside in processing system 1214, be external to processing system 1214, or be distributed across multiple entities including processing system 1214. Computer-readable medium 1206 may be implemented in a computer program product. In some examples, computer-readable medium 1206 may be part of memory 1205. As an example, a computer program product may include a computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented, depending on the specific application and the overall design constraints imposed on the system.

[0180] In some aspects of this disclosure, processor 1204 may include circuitry configured for various functions. For example, processor 1204 may include communication and processing circuitry 1242 configured to communicate with another wireless communication device (e.g., a relay or remote wireless communication device) or a base station via wireless transceiver 1210.

[0181] For example, the communication and processing circuitry system 1242 may be configured to communicate with a base station (e.g., a gNB or eNB) via a Uu link and with another wireless communication device via a side link. In some examples, the communication and processing circuitry system 1242 may include one or more hardware components that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuitry system 1242 may include one or more transmit / receive chains.

[0182] In some implementations where communication involves receiving information, communication and processing circuitry system 1242 may obtain information from components of wireless communication device 1200 (e.g., from transceiver 1210 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry system 1242 may output information to another component of processor 1204, to memory 1205, or to bus interface 1208. In some examples, communication and processing circuitry system 1242 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry system 1242 may receive information via one or more channels. In some examples, communication and processing circuitry system 1242 may include functionality for receiving means. In some examples, communication and processing circuitry system 1242 may include functionality for processing means, including means for demodulation, means for decoding, etc.

[0183] In some implementations where communication involves sending (e.g., transmitting) information, the communication and processing circuitry system 1242 may obtain information from (e.g., from another component of processor 1204, memory 1205, or bus interface 1208), process (e.g., modulate, encode) that information, and output the processed information. For example, the communication and processing circuitry system 1242 may output information to transceiver 1210 (e.g., to transmit information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry system 1242 may send one or more of signals, messages, other information, or any combination thereof. In some examples, the communication and processing circuitry system 1242 may send information via one or more channels. In some examples, the communication and processing circuitry system 1242 may include the functionality of means for sending (e.g., means for transmitting). In some examples, the communication and processing circuitry system 1242 may include the functionality of means for generating, including means for modulation, means for encoding, etc.

[0184] In an example where the wireless communication device 1200 is a remote wireless communication device, the communication and processing circuitry system 1242 can transmit data to the relay wireless communication device via a side link according to a selected data routing option from the set of data routing options. In another example where the wireless communication device 1200 is a relay wireless communication device, the communication and processing circuitry system 1242 can transmit data received from the relay wireless communication device via a side link to a base station via a cellular link according to a selected data routing option from the set of data routing options. The communication and processing circuitry system 1242 is further configured to execute communication and processing instructions (software) 1252 stored in the computer-readable medium 1206 to implement one or more of the functions described herein.

[0185] Processor 1204 may further include a sidelink (SL) generation and processing circuitry 1244 configured to establish a sidelink with another wireless communication device via wireless transceiver 1210. In an example where wireless communication device 1200 is a remote wireless communication device, SL generation and processing circuitry 1244 may send control signaling to a relay wireless communication device to establish a sidelink according to a selected data routing option from a set of data routing options. In an example where wireless communication device 1200 is a relay wireless communication device, SL generation and processing circuitry 1244 may send control signaling to a remote wireless communication device to establish a sidelink according to a selected data routing option from a set of data routing options. SL generation and processing circuitry 1244 is further configured to execute SL generation and processing instructions (software) 1254 stored in computer-readable medium 1206 to implement one or more of the functions described herein.

[0186] The processor 1204 may further include a relay management circuitry 1246 configured to relay data from one or more wireless communication devices via the radio transceiver 1210. For example, the relay management circuitry 1246 may relay data received from one or more remote wireless communication devices via one or more sidelinks to a base station, respectively, according to a selected data routing option in a set of data routing options. The relay management circuitry 1246 is configured to execute relay management software 1256 stored in the computer-readable medium 1206 to implement one or more of the functions described herein.

[0187] The memory 1205 may include policy control information 1222 for controlling data routing from a remote wireless communication device to a core network or base station via a relay wireless communication device. The policy control information 1222 may include a UE routing selection policy (URSP) 1218 and / or a ProSe policy 1216. A communication and processing circuitry 1242 executing the communication and processing software 1252 in the computer-readable medium 1206 can access the policy control information to select and configure data routing options from a set of data routing options.

[0188] Figure 13 This is a flowchart of an exemplary method 1300 for sending data from a first communication device to a network via a relay data routing option, according to some aspects. As described below, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features are not required to be used in implementing all examples. In some examples, process 1300 may be... Figure 12 The process 1300 is performed by the wireless communication device 1200 described in the text. In some examples, the process 1300 may be performed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0189] Method 1300 includes: a wireless communication device generating data for transmission to a network based on an application (box 1302). For example, in conjunction with the above... Figure 12 The communication and processing circuitry system 1242 shown and described can provide means for generating data.

[0190] Method 1300 further includes: the wireless communication device selecting a data routing option from a set of data routing options based on policy control information for routing data to the network (box 1304). Each data routing option in the set of data routing options includes routing data via a second wireless communication device. For example, in conjunction with the above... Figure 12 The communication and processing circuitry system 1242 shown and described provides means for selecting a data routing option from a set of data routing options.

[0191] Additionally, method 1300 includes: the wireless communication device transmitting data to a second wireless communication device to route the data via a selected data routing option (box 1306). For example, in conjunction with the above... Figure 12 The SL generation and processing circuit system 1244 shown and described can provide means for transmitting data to a second wireless communication device.

[0192] Figure 14This is a flowchart of an exemplary method 1400 for routing data from a second wireless communication device to a network via a data routing option, according to some aspects of a first wireless device. As described below, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features are not required to be used in implementing all examples. In some examples, process 1400 may be... Figure 12 The process 1400 is performed by the wireless communication device 1200 described in the text. In some examples, the process 1400 may be performed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0193] Method 1400 includes: a wireless communication device establishing a Protocol Data Unit (PDU) session with a network based on policy control information for relaying data received from a second wireless communication device (box 1402). For example, in conjunction with the above... Figure 12 The communication and processing circuitry system 1242 shown and described provides means for establishing Protocol Data Unit (PDU) sessions.

[0194] Method 1400 further includes: the wireless communication device receiving data from the second wireless communication device (block 1404). For example, in conjunction with the above... Figure 12 The SL generation and processing circuitry system 1244 shown and described can provide means for receiving data from a second wireless communication device via a side link.

[0195] Method 1400 further includes: the wireless communication device transmitting data to a base station coupled to the network via a PDU session (box 1406). For example, in conjunction with the above... Figure 12 The communication and processing circuitry system 1242 shown and described can provide means for transmitting data to a base station.

[0196] Figure 15 This is a flowchart of an exemplary method 1500 for transmitting data from a first communication device to a second wireless communication device via data routing options, according to some aspects. As described below, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features are not required to be used in implementing all examples. In some examples, process 1500 may be... Figure 12 The process 1500 is performed by the wireless communication device 1200 described in the text. In some examples, the process 1500 may be performed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0197] Method 1500 includes: a first wireless communication device generating data for transmission based on an application (box 1502). For example, in conjunction with the above... Figure 12 The communication and processing circuitry system 1242 shown and described can provide means for generating data.

[0198] Method 1500 further includes: the first wireless communication device selecting a data routing option from a set of data routing options based on policy control information for routing data to the second wireless communication device (block 1504). For example, in conjunction with the above... Figure 12 The communication and processing circuitry system 1242 shown and described provides means for selecting a data routing option from a set of data routing options.

[0199] Additionally, method 1500 includes: a first wireless communication device transmitting data to a second wireless communication device (block 1506). For example, in conjunction with the above... Figure 12 The SL generation and processing circuit system 1244 shown and described can provide means for transmitting data to a second wireless communication device.

[0200] Figure 16 This is a conceptual diagram illustrating an example hardware implementation of an exemplary base station 1600 employing the processing system 1614. For example, base station 1600 could be as follows: Figure 1 , 2 User equipment (UE) or other scheduled entities configured to communicate in a wireless communication network (e.g., a 5G NR access network), as described in any one or more of 4 and / or 5.

[0201] Base station 1600 may be implemented using a processing system 1614 including one or more processors 1604. Examples of processors 1604 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, base station 1600 may be configured to perform any or more of the functions described herein. That is, processor 1600, as utilized in base station 1604, may be used to implement any or more of the processes described below. In some instances, processor 1604 may be implemented via a baseband or modem chip, while in other implementations, processor 1604 itself may include several devices that are different from and distinct from the baseband or modem chip (e.g., in such scenarios they may work together to achieve the examples discussed herein). Furthermore, as mentioned above, various hardware arrangements and components beyond the baseband modem processor can be used in the implementation, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0202] In this example, processing system 1614 can be implemented using a bus architecture generally represented by bus 1602. Depending on the specific application and overall design constraints of processing system 1614, bus 1602 may include any number of interconnect buses and bridges. Bus 1602 communicatively couples together various circuits including one or more processors (generally represented by processor 1604), memory 1605, and computer-readable media (generally represented by computer-readable media 1606). Bus 1602 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1608 provides an interface between bus 1602, wireless transceiver 1610, and network interface 1620. Wireless transceiver 1610 provides means for communicating with various other devices via a transmission medium (e.g., an air interface). Network interface 1620 provides means for communicating with various other network devices via control plane (e.g., N2) and user plane (e.g., N3) communication links. User interface 1612 (e.g., keypad, display, touchscreen, speaker, microphone, control knob, etc.) may also be provided. Of course, such user interface 1612 is optional and may be omitted in some examples.

[0203] Processor 1604 is responsible for managing bus 1602 and general processing, including the execution of software stored on computer-readable medium 1606. When executed by processor 1604, the software causes processing system 1614 to perform various functions described below for any particular device. Computer-readable medium 1606 and memory 1605 can also be used to store data manipulated by processor 1604 during software execution.

[0204] One or more processors 604 in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Software may reside on computer-readable media 1606.

[0205] Computer-readable medium 1606 may be a non-transitory computer-readable medium. As examples, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital multi-purpose discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions accessible and readable by a computer. As examples, computer-readable media may also include carrier waves, transmission lines, and any other suitable medium for transmitting software and / or instructions accessible and readable by a computer. Computer-readable medium 1606 may reside in processing system 1614, be external to processing system 1614, or be distributed across multiple entities including processing system 1614. Computer-readable medium 1606 may be implemented in a computer program product. In some examples, computer-readable medium 1606 may be part of memory 1605. As an example, a computer program product may include a computer-readable medium within packaging material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented, depending on the specific application and the overall design constraints imposed on the system.

[0206] In some aspects of this disclosure, processor 1604 may include circuitry configured for various functions. For example, processor 1604 may include communication and processing circuitry 1642 configured to communicate with a relay wireless communication device via a wireless transceiver 1610 and with a network device via a network interface 1620. For example, communication and processing circuitry 1642 may receive data from the relay wireless communication device via a cellular link (Uu) according to a selected data routing option from a set of data routing options. This data originates from a remote wireless communication device. Communication and processing circuitry 1642 may transmit data from the relay wireless communication device to the network device via the network interface 1620 according to a selected data routing option from the set of data routing options. Communication and processing circuitry 1642 is configured to execute communication and processing software 1652 stored in a computer-readable medium 1606 to implement one or more of the functions described herein.

[0207] Figure 17This is a flowchart of another exemplary method 1700 for relaying data received from a remote wireless communication device via a relay wireless communication device to a network via selected data routing options, according to some aspects. As described below, some or all of the described features may be omitted in a particular implementation within the scope of this disclosure, and some described features may not be required to implement all examples. In some examples, process 1700 may be... Figure 16 The process 1700 is performed by the wireless communication device 1600 described in the text. In some examples, the process 1700 may be performed by any suitable equipment or apparatus for performing the functions or algorithms described below.

[0208] Method 1700 includes: a base station establishing a Protocol Data Unit (PDU) session with a first wireless communication device and a network device for receiving data from the first wireless communication device and forwarding the data to the network device (box 1702). For example, in conjunction with the above... Figure 16 The communication and processing circuitry system 1642 shown and described provides means for establishing Protocol Data Unit (PDU) sessions.

[0209] Method 1700 further includes: the base station receiving data from the first wireless communication device via a PDU session (box 1704). This data may originate from a second wireless communication device. For example, in conjunction with the above... Figure 16 The communication and processing circuitry system 1642 shown and described may provide means for receiving data from a first wireless communication device via a PDU session.

[0210] Additionally, method 1700 includes: the base station transmitting data to a network device via a PDU session (box 1706). For example, in conjunction with the above... Figure 16 The communication and processing circuit system 1642 shown and described can provide means for transmitting data to network devices.

[0211] Figure 18 This is a flowchart depicting a method 1800 for routing application data to a target device based on several factors. According to method 1800, the UE may be running an application that generates data for transmission to the target device or entity (box 1802). Subsequently, according to method 1800, the UE may consult a ProSe path selection policy stored in internal memory (box 1804). If the application data is to be directly routed to another UE via a direct sidelink (e.g., a PCT link) without being routed through the network, the UE then performs a sidelink (PC5) direct device discovery (box 1806). If the UE discovers the target device in box 1806, according to method 1800, the UE establishes a PC5 communication link (sidelink) to the target device (box 1808). If the UE does not discover the target device in box 1806, the UE proceeds to box 1810 according to method 1800.

[0212] If, in box 1804, it is determined after consulting the ProSe routing policy that the application data will not be routed via a direct PC5 link, or if no direct PC5 target device is found in box 1806 (e.g., the application data must reach the target device or entity via the network), then according to method 1800, the UE may consult the UE routing policy (URSP) stored in internal memory (box 1810). Based on consulting the URSP, the UE may perform non-seamless offloading (NSO) to the wireless local area network (WLAN) via the access network discovery and selection policy (ANDSP) (box 1812). If the WLAN is found, the UE establishes a non-3GPP communication link via the WLAN to route the data to the target device or entity via the network (box 1814). If the WLAN is not found in box 1812, the UE may proceed to box 1822.

[0213] Alternatively, based on the URSP referenced in box 1810, the UE may perform a Layer 3 (L3) relay non-seamless offload to the relay wireless communication device (box 1816). Figures 6A-6B The description discusses L3 relay non-seamless offloading in detail. In this regard, the UE performs relay wireless communication device discovery based on the ProSe policy (Box 1816). If a relay wireless communication device is found, the UE can establish a sidelink with that device (as described in [reference]). Figure 6A (As discussed), and via this relay wireless communication device and network, the application data is routed to the target device or entity (as referred to). Figure 6B (Discussed in box 1820). If no relay wireless communication device is found by box 1816, the UE may proceed to box 1822. As discussed above, in non-seamless offloading scenarios, the PDU session may not extend to the UE.

[0214] Furthermore, according to method 1800, if non-seamless offloading is unavailable in block 1810, the UE can consult a URSP routing descriptor (RSD), which can also be stored in internal memory (block 1822). Based on consulting the URSP RSD, the UE can prefer to transmit data to the target device or entity via ANDSP 1822 for WLAN using a non-3GPP access type. If a WLAN is found in block 1822, the UE establishes a communication link with a trusted or untrusted non-3GPP device via that WLAN to route data to the target device or entity via a PDU session (block 1824). If no WLAN is found in block 1822, the UE can return to block 1822 to determine if another option is available.

[0215] In box 1822, according to method 1800, the UE can select an L3 trunk with N3IWF access type data routing options, as shown in reference... Figures 7A-7B This is discussed in detail. In this regard, the UE performs relay wireless communication device discovery based on the ProSe policy (Box 1826). If a relay wireless communication device is found, the UE establishes a PDU session communication link with the N3IWF network equipment via that relay wireless communication device, base station, and network (as shown in reference). Figure 7A (explained), and performs application data communication in the PDU session via the relay wireless communication device, base station, UPF and N3IWF network device (as described in the reference). Figure 7B (See box 1828 for explanation). If no relay wireless communication device is found in box 1826, the UE may return to box 1822 to determine if another option is available.

[0216] In box 1822, according to method 1800, the UE can select the L2 trunk access type data routing option, as shown in reference... Figures 8A-8B This will be discussed in detail. In this regard, the UE uses the ProSe policy to discover relay wireless communication devices and establishes a NAS communication link with the network (as per [reference]). Figure 8A (discussed in detail); and performing application data communication with the network via relay wireless communication equipment and base stations (as shown in reference). Figure 8B (See box 1830 for a detailed discussion)

[0217] The following provides an overview of the various aspects of this disclosure:

[0218] Aspect 1: A method for wireless communication implemented at a first wireless communication device, the method comprising: generating data for transmission to a network based on an application; selecting a data routing option from a set of data routing options based on policy control information for routing the data to the network, wherein each data routing option in the set of data routing options includes routing the data via a second wireless communication device; and transmitting the data to the second wireless communication device for routing the data via the selected data routing option.

[0219] Aspect 2: The method of aspect 1, wherein selecting data routing options from the set of data routing options includes selecting layer 3 relay routing options.

[0220] Aspect 3: The method of aspect 2, wherein the policy control information includes an application identifier that identifies the application, and a list of route selection descriptors that identify the Layer 3 relay routing option as available for routing data generated by the application.

[0221] Aspect 4: The method of aspect 2 or 3, wherein the policy control information includes a non-seamless offload indication indicating that the data associated with the application identifier is to be transmitted to a second wireless communication device outside of a protocol data unit (PDU) session.

[0222] Aspect 5: The method of any of Aspects 2-4, wherein the policy control information includes a sidelink relay non-seamless offload indication indicating that the data associated with the application identifier is to be transmitted to a second wireless communication device outside of a Protocol Data Unit (PDU) session.

[0223] Aspect 6: The method of any of Aspects 3-5 further includes establishing a side link to the second wireless communication device, wherein establishing the side link to the second wireless communication device includes performing Layer 1, 2 and 3 Proximity Service (ProSe) (PC5) protocol stack operations.

[0224] Aspect 7: The method as described in Aspect 6, wherein: the execution layer 3 PC5 protocol operation includes the execution of signaling (PC5-S) operation and radio resource control (PC5-RRC) operation; the execution layer 2 PC5 protocol operation includes the execution of packet data convergence protocol (PC5-PDCP) operation, radio link control (PC5-RLC) operation and media access control (PC5-MAC) operation; and the execution layer 1 PC5 protocol operation includes the execution of physical (PC5-PHY) operation.

[0225] Aspect 8: The method of any of Aspects 1-7, wherein the Layer 3 relay routing options do not include non-access stratum (NAS) connections to the network or access stratum (AS) connections to base stations coupled to the network.

[0226] Aspect 9: The method of any of Aspects 1-7 further includes: generating an Internet Protocol (IP) packet including the data; and processing the IP packet via a Proximity Service (ProSe) (PC5) protocol stack operation before transmitting the IP packet to a second wireless communication device.

[0227] Aspect 10: The method of aspect 9 further includes: receiving an IP address from a second wireless communication device, wherein the IP address identifies the first wireless communication device as the originator of the IP packet, wherein generating the IP address includes including the IP address in the IP packet.

[0228] Aspect 11: The method of aspect 1, wherein selecting data routing options from the set of data routing options includes selecting a Layer 3 relay with non-3GPP Networking Function (N3IWF) routing options.

[0229] Aspect 12: The method of aspect 11, wherein the data routed via a layer 3 relay with N3IWF data routing options occurs on a protocol data unit (PDU) session with an N3IWF network device coupled to the network.

[0230] Aspect 13: The method of aspect 12, wherein the policy control information includes a Session and Service Continuity (SSC) mode that specifies that the IP address of the first wireless communication device, identified by the PDU session, should be retained.

[0231] Aspect 14: The method of Aspect 12 or 13, wherein the policy control information includes a network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place.

[0232] Aspect 15: The method of any of Aspects 12-14, wherein the policy control information includes a data network name (DNN) that identifies the PDU session.

[0233] Aspect 16: The method of any of Aspects 12-15, wherein the policy control information includes an access type preference for a Layer 3 relay with N3IWF data routing options.

[0234] Aspect 17: The method of any of Aspects 12-16, wherein the policy control information specifies one or more of the following: a time window in which a Layer 3 relay with N3IWF data routing options is available, a location in which a first wireless communication device needs to exist to make a Layer 3 relay with N3IWF routing options available, or a service criterion for a Layer 3 relay with N3IWF data routing options.

[0235] Aspect 18: The method of aspect 17, wherein the service criteria include one or more of the following: security criteria, privacy criteria, quality of service (QoS) criteria, or network load criteria.

[0236] Aspect 19: The method of Aspect 17 or 18, wherein the selection of a Layer 3 relay with N3IWF data routing options is based on the service criterion.

[0237] Aspect 20: The method of any of Aspects 17-19 further includes: configuring the PDU session using the service criteria after selecting a Layer 3 relay with N3IWF data routing options.

[0238] Aspect 21: The method of any of Aspects 12-20, wherein the Layer 3 relay having the N3IWF data routing option includes a non-access stratum (NAS) connection to the network and an access stratum (AS) connection to the base station via a second wireless communication device.

[0239] Aspect 22: The method of any of Aspects 12-21 further includes establishing a side link to the second wireless communication device, wherein establishing the side link to the second wireless communication device includes performing Layer 1 and 2 Proximity Service (ProSe) (PC5) protocol stack operations.

[0240] Aspect 23: The method of any of Aspects 12-22 further includes: generating a PDU packet including the data; and processing the PDU packet via a Proximity Service (ProSe) (PC5) protocol stack operation before transmitting the PDU packet to a second wireless communication device.

[0241] Aspect 24: The method of aspect 1, wherein selecting data routing options from the set of data routing options includes selecting layer 2 relay routing options.

[0242] Aspect 25: The method of aspect 24, wherein the policy control information includes network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place.

[0243] Aspect 26: The method of Aspect 24 or 25, wherein the policy control information includes the data network name (DNN) that identifies the PDU session.

[0244] Aspect 27: The method of any of Aspects 24-26, wherein the policy control information includes access type preferences for relay routing options in Identification Layer 2.

[0245] Aspect 28: The method of any of Aspects 24-27, wherein the policy control information specifies one or more of the following: a time window in which the Layer 2 relay routing option is available, a location where the first wireless communication device needs to be present to use the Layer 2 relay routing option, or a service criterion for the Layer 2 relay routing option.

[0246] Aspect 29: The method of any of Aspects 24-28, wherein the selection of Layer 2 relay routing options is based on the service criterion.

[0247] Aspect 30: The method of any of Aspects 24-29 further includes: configuring the PDU session using the service criterion after selecting a Layer 2 relay routing option.

[0248] Aspect 31: The method of any of Aspects 24-30, wherein the Layer 2 routing options include non-access layer (NAS) connection and access layer (AS) connection to the network via a second wireless communication device.

[0249] Aspect 32: The method of any of Aspects 24-31 further includes establishing a side link to the second wireless communication device, wherein establishing the side link to the second wireless communication device includes performing Layer 1 and 2 Proximity Service (ProSe) (PC5) protocol stack operations.

[0250] Aspect 33: The method of any of Aspects 24-32 further includes: generating a PDU packet including the data; and processing the PDU packet via New Radio (NR) protocol stack operation and (ProSe)(PC5) protocol stack operation before transmitting the PDU packet to a second wireless communication device.

[0251] Aspect 34: The method of any of Aspects 1-33, wherein the data routing option selected from the set of data routing options is in response to switching from the cellular routing option.

[0252] Aspect 35: The method of any of Aspects 1-34, wherein the selection of the data routing option from the set of data routing options occurs when no routing option for the data is activated.

[0253] Aspect 36: The method of any of Aspects 1-35, wherein the policy control information is located in one or more of the following: UE routing policy (URSP) or proximity service (ProSe) policy.

[0254] Aspect 37: A first wireless communication device in a wireless communication network, comprising: a wireless transceiver, a memory, and a processor coupled to the wireless transceiver and the memory, the processor and the memory being configured to perform a method as described in any of Aspects 1 to 36.

[0255] Aspect 38: A first wireless communication device in a wireless communication network, comprising: at least one means for performing a method as described in any one of aspects 1 to 36.

[0256] Aspect 39: A non-transient computer-readable medium storing computer-executable code, the computer-executable code including code for causing a first wireless communication device to perform a method as described in any of Aspects 1 to 36.

[0257] Aspect 40: A method for wireless communication implemented at a first wireless communication device, the method comprising: establishing a Protocol Data Unit (PDU) session with a network based on policy control information for relaying data received from a second wireless communication device; receiving data from the second wireless communication device via a side link; and transmitting the data to a base station coupled to the network via the PDU session.

[0258] Aspect 41: The method of aspect 40, wherein the policy control information includes a session and service continuity (SSC) mode that specifies that service continuity of the PDU session should be preserved.

[0259] Aspect 42: The method of aspect 40 or 41, wherein the policy control information includes network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place.

[0260] Aspect 43: The method of any of Aspects 40-42, wherein the policy control information includes a data network name (DNN) that identifies the PDU session.

[0261] Aspect 44: The method of any of Aspects 40-43, wherein the policy control information is located in the UE routing policy (URSP).

[0262] Aspect 45: The method of any of Aspects 40-44, wherein receiving the data from the second wireless communication device occurs outside the PDU session.

[0263] Aspect 46: The method of aspect 45 further includes: processing data received from the second wireless communication device via operation of the layer 1, 2 and 3 Proximity Service (ProSe) (PC5) protocol stack; and processing the data via operation of the layer 1, 2 and 3 New Radio (NR) protocol stack for transmission to the base station.

[0264] Aspect 47: The method of aspect 45 or 46 further includes: processing data received from the second wireless communication device via operation of the Layer 1 and 2 Proximity Service (ProSe) (PC5) protocol stack; and processing the data via operation of the Layer 1 and 2 New Radio (NR) protocol stack for transmission to the base station.

[0265] Aspect 48: The method of any of Aspects 40-47 further includes: performing adaptation relay processing to multiplex data received from the second wireless communication device with data received from one or more other wireless communication devices for transmission to the base station via the PDU session.

[0266] Aspect 49: A first wireless communication device in a wireless communication network, comprising: a wireless transceiver, a memory, and a processor coupled to the wireless transceiver and the memory, the processor and the memory being configured to perform a method as described in any of Aspects 40 to 48.

[0267] Aspect 50: A first wireless communication device in a wireless communication network, comprising: at least one means for performing the method as described in any one of aspects 40 to 48.

[0268] Aspect 51: A non-transient computer-readable medium storing computer-executable code, the computer-executable code including code for causing a first wireless communication device to perform a method as described in any of Aspects 40 to 48.

[0269] Aspect 52: A method for wireless communication implemented at a base station, the method comprising: establishing a Protocol Data Unit (PDU) session with a first wireless communication device and a network device for receiving data from the first wireless communication device and forwarding the data to the network device; receiving data from the first wireless communication device via the PDU session, wherein the data originates from a second wireless communication device; and transmitting the data to the network device via the PDU session.

[0270] Aspect 53: The method of aspect 52, wherein the network device includes a non-3GPP (3rd Generation Partnership Project) Networking Function (N3IWF) network device.

[0271] Aspect 54: The method of aspects 52 or 53, wherein the PDU session extends to a second wireless communication device.

[0272] Aspect 55: The method of aspects 52 or 54, wherein the PDU session does not extend to a second wireless communication device.

[0273] Aspect 56: The method of any of Aspects 52-55 further includes: performing adaptation layer processing to demultiplex data originating from a second wireless communication device with data originating from one or more other wireless communication devices.

[0274] Aspect 57: A base station in a wireless communication network, comprising: a wireless transceiver, a memory, and a processor coupled to the wireless transceiver and the memory, the processor and the memory being configured to perform a method as described in any of Aspects 52 to 56.

[0275] Aspect 58: A base station in a wireless communication network, comprising: at least one means for performing the method of any one of aspects 52 to 56.

[0276] Aspect 59: A non-transient computer-readable medium storing computer-executable code, the computer-executable code including code for causing a base station to perform methods as described in any of Aspects 52 to 56.

[0277] Aspect 60: A method for wireless communication implemented at a first wireless communication device, the method comprising: generating data for transmission based on an application; selecting a data routing option from a set of data routing options based on policy control information for routing the data to a second wireless communication device; and transmitting the data to the second wireless communication device via a side link.

[0278] Aspect 61: The method of aspect 60, wherein the policy control information includes a non-seamless offload indication indicating that the data associated with the application identifier is to be transmitted to a second wireless communication device outside of a protocol data unit (PDU) session.

[0279] Aspect 62: The method of aspect 60 or 61, wherein the policy control information includes a sidelink relay non-seamless offload indication indicating that the data associated with the application identifier is to be transmitted to a second wireless communication device outside of a protocol data unit (PDU) session.

[0280] Aspect 63: The method of any of Aspects 60-62, wherein the policy control information includes an access type preference that identifies the PC5 data routing options.

[0281] Aspect 64: A first wireless communication device in a wireless communication network, comprising: a wireless transceiver, a memory, and a processor coupled to the wireless transceiver and the memory, the processor and the memory being configured to perform a method as described in any of Aspects 60 to 63.

[0282] Aspect 65: A first wireless communication device in a wireless communication network, comprising: at least one means for performing the method of any one of aspects 60 to 63.

[0283] Aspect 66: A non-transient computer-readable medium storing computer-executable code, the computer-executable code including code for causing a first wireless communication device to perform methods as described in any of Aspects 60 to 63.

[0284] Several aspects of wireless communication networks have been described with reference to exemplary implementations. As will be readily apparent to those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0285] As examples, various aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2 (3GPP2), such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0286] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior to or better than other aspects of this disclosure. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered coupled to each other—even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never directly contacts the second object. The terms "circuit" and "circuit system" are used broadly and are intended to include both hardware implementations of electronic devices and conductors, and software implementations of information and instructions, which, when connected and configured, enable the performance of the functions described in this disclosure, without limitation on the type of electronic circuit, and which, when executed by a processor, enable the performance of the functions described in this disclosure.

[0287] Figure 1-16 One or more of the components, steps, features and / or functions described herein may be rearranged and / or combined into a single component, step, feature or function, or implemented in several components, steps or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2 The apparatus, devices, and / or components described in sections 4 and / or 5 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and / or embedded in hardware.

[0288] It should be understood that the specific order or hierarchy of the steps in the disclosed methods is an illustration of an exemplary process. Based on design preferences, it will be understood that the specific order or hierarchy of the steps in these methods can be rearranged. The appended method claims present the elements of various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented, unless specifically stated herein.

[0289] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element are not intended to mean “one and only one”—unless specifically stated otherwise—but are intended to mean “one or more.” Unless specifically stated otherwise, the term “some / a” refers to one or more. The phrase “at least one of” a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the aspects described throughout this disclosure that are currently or hereafter known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be donated to the public, whether or not such disclosure is expressly stated in the claims.

Claims

1. A first wireless communication device, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, wherein the one or more processors are configured to enable the first wireless communication device to: Data is generated based on the application and used for transmission to the network; Based on policy control information, a data routing option from a set of data routing options is selected as the chosen data routing option for routing the data to the network, wherein each data routing option in the set of data routing options includes routing the data to the network via a second wireless communication device, wherein each data routing option in the set of data routing options utilizes different combinations of layer options and protocol data unit (PDU) options, wherein the layer options relate to which layer to use for routing communication from the second wireless communication device to the network, and the PDU options relate to whether to utilize a PDU session; as well as The data is transmitted to the second wireless communication device for routing via the selected data routing option.

2. The first wireless communication device of claim 1, wherein the one or more processors are configured to cause the first wireless communication device to transmit the data to the second wireless communication device via a side link.

3. The first wireless communication device as claimed in claim 1, wherein the selected data routing option includes a Layer 3 relay routing option.

4. The first wireless communication device as claimed in claim 3, wherein the policy control information includes: An application identifier that identifies the application, and a list of route selection descriptors that identifies the Layer 3 relay routing options as available for routing data generated by the application; Non-seamless offload indication, which indicates that the data associated with the application identifier is to be transmitted to the second wireless communication device outside of the Protocol Data Unit (PDU) session; as well as Sidelink relay non-seamless offload indication indicates that the data associated with the application identifier is to be transmitted to the second wireless communication device outside of the protocol data unit (PDU) session.

5. The first wireless communication device of claim 3, wherein the one or more processors are configured to cause the first wireless communication device to perform layer 1, 2, and 3 proximity service (ProSe) (PC5) protocol stack operations to establish a sidelink to the second wireless communication device; wherein: The Layer 3 PC5 protocol operation includes signaling (PC5-S) operation and radio resource control (PC5-RRC) operation; The Layer 2 PC5 protocol operations include Packet Data Convergence Protocol (PC5-PDCP) operations, Radio Link Control (PC5-RLC) operations, and Media Access Control (PC5-MAC) operations; and The Layer 1 PC5 protocol operation includes PC5 physical layer (PC5-PHY) operation.

6. The first wireless communication device of claim 3, wherein the one or more processors are configured to cause the first wireless communication device to: Generate Internet Protocol (IP) packets that include the data; The IP packet is processed via the Proximity Service (ProSe) (PC5) protocol stack operation before being transmitted to the second wireless communication device; Receive an IP address from the second wireless communication device, wherein the IP address identifies the first wireless communication device as the originator of the IP packet; as well as Generate the IP packet to include the IP address.

7. The first wireless communication device of claim 1, wherein the selected data routing option in the set of data routing options includes a Layer 3 relay with a non-3GPP Networking Function (N3IWF) routing option.

8. The first wireless communication device of claim 7, wherein the data routed via the Layer 3 relay having an N3IWF data routing option occurs on a Protocol Data Unit (PDU) session with an N3IWF network device coupled to the network.

9. The first wireless communication device as claimed in claim 8, wherein the policy control information includes: Session and Service Continuity (SSC) mode, wherein the SSC mode specifies that the IP address of the first wireless communication device, which identifies the PDU session, should be retained; Network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place. The data network name (DNN) that identifies the PDU session; and Identify the access type preference of the Layer 3 relay with the N3IWF data routing option.

10. The first wireless communication device of claim 1, wherein the selected data routing option in the set of data routing options includes a Layer 2 relay routing option.

11. A method for wireless communication implemented at a first wireless communication device, the method comprising: Data is generated based on the application and used for transmission to the network; Based on policy control information, a data routing option from a set of data routing options is selected as the chosen data routing option for routing the data to the network, wherein each data routing option in the set of data routing options includes routing the data to the network via a second wireless communication device, wherein each data routing option in the set of data routing options utilizes different combinations of layer options and protocol data unit (PDU) options, wherein the layer options relate to which layer to use for routing communication from the second wireless communication device to the network, and the PDU options relate to whether to utilize a PDU session; as well as The data is transmitted to the second wireless communication device for routing via the selected data routing option.

12. The method of claim 11, wherein the data is transmitted to the second wireless communication device via a side link.

13. The method of claim 11, wherein the selected data routing option includes a Layer 3 relay routing option.

14. The method of claim 13, wherein the policy control information includes: An application identifier that identifies the application, and a list of route selection descriptors that identifies the Layer 3 relay routing options as available for routing data generated by the application; Non-seamless offload indication, which indicates that the data associated with the application identifier is to be transmitted to the second wireless communication device outside of the Protocol Data Unit (PDU) session; as well as Sidelink relay non-seamless offload indication indicates that the data associated with the application identifier is to be transmitted to the second wireless communication device outside of the protocol data unit (PDU) session.

15. The method of claim 13, further comprising establishing a sidelink to the second wireless communication device, wherein establishing the sidelink to the second wireless communication device includes performing Layer 1, 2, and 3 Proximity Service (ProSe) (PC5) protocol stack operations, wherein: Performing the Layer 3 PC5 protocol operation includes performing signaling (PC5-S) operations and radio resource control (PC5-RRC) operations; Performing the Layer 2 PC5 protocol operations includes performing Packet Data Convergence Protocol (PC5-PDCP) operations, Radio Link Control (PC5-RLC) operations, and Media Access Control (PC5-MAC) operations; and Performing the Layer 1 PC5 protocol operation includes performing physical (PC5-PHY) operations.

16. The method of claim 13, further comprising: Generate Internet Protocol (IP) packets that include the data; The IP packet is processed via the Proximity Service (ProSe) (PC5) protocol stack operation before being transmitted to the second wireless communication device; Receive an IP address from the second wireless communication device, wherein the IP address identifies the first wireless communication device as the originator of the IP packet, and generating the IP address includes including the IP address in the IP packet.

17. The method of claim 11, wherein selecting a data routing option from the set of data routing options includes selecting a Layer 3 relay with a non-3GPP Networking Function (N3IWF) routing option.

18. The method of claim 17, wherein the data routed via the Layer 3 relay having N3IWF data routing options occurs on a Protocol Data Unit (PDU) session with an N3IWF network device coupled to the network.

19. The method of claim 18, wherein the policy control information includes: Session and Service Continuity (SSC) mode, wherein the SSC mode specifies that the IP address of the first wireless communication device, which identifies the PDU session, should be retained; Network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place. The data network name (DNN) that identifies the PDU session; and Identify the access type preference of the Layer 3 relay with the N3IWF data routing option.

20. The method of claim 11, wherein the policy control information includes access type preferences for relay routing options in identification layer 2.

21. The method of claim 11, further comprising: Access User Equipment Routing Policy (URSP), and select data routing options from the set of data routing options based on the URSP.

22. The method of claim 11, further comprising: Access the User Equipment Routing Policy (URSP) Route Descriptor (RSD), and select a data routing option from the set of data routing options based on the URSP RSD.

23. A first wireless communication device, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, wherein the one or more processors are configured to enable the first wireless communication device to: Based on policy control information, a Protocol Data Unit (PDU) session is established with the network according to data routing options for relaying data received from a second wireless communication device. The data routing options are selected from a set of data routing options, each of which utilizes a different combination of layer options and PDU options. The layer options relate to which layer to use to route communication from the second wireless communication device to the network, and the PDU options relate to whether to utilize a PDU session. Receive data from the second wireless communication device; as well as The data is transmitted to network entities coupled to the network via the PDU session.

24. The first wireless communication device as claimed in claim 23, wherein the policy control information includes: Specify the Session and Service Continuity (SSC) mode for the service continuity of the PDU session; Network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place. as well as The data network name (DNN) that identifies the PDU session.

25. The first wireless communication device of claim 23, wherein the one or more processors are configured to enable the first wireless communication device to receive the data from the second wireless communication device outside the PDU session.

26. The first wireless communication device of claim 25, wherein the one or more processors are configured to cause the first wireless communication device to: The data received from the second wireless communication device is processed via the Proximity Service (ProSe) (PC5) protocol stack operation at layers 1, 2, and 3; and The data is processed via Layer 1, 2 and 3 New Radio (NR) protocol stack operations for transmission to the network entity.

27. The first wireless communication device of claim 25, wherein the one or more processors are configured to cause the first wireless communication device to: The data received from the second wireless communication device is processed via Layer 1 and 2 Proximity Service (ProSe) (PC5) protocol stack operations; and The data is processed via Layer 1 and 2 New Radio (NR) protocol stack operations for transmission to the network entity.

28. A method for wireless communication implemented at a first wireless communication device, the method comprising: Based on policy control information, a Protocol Data Unit (PDU) session is established with the network according to data routing options for relaying data received from a second wireless communication device. The data routing options are selected from a set of data routing options, each of which utilizes a different combination of layer options and PDU options. The layer options relate to which layer to use to route communication from the second wireless communication device to the network, and the PDU options relate to whether to utilize a PDU session. Receive the data from the second wireless communication device; as well as The data is transmitted to network entities coupled to the network via the PDU session.

29. The method of claim 28, wherein the policy control information includes: Specify the Session and Service Continuity (SSC) mode for which the service continuity of the PDU session should be preserved; Network slice selection (NSS) that identifies one or more network slices on which the PDU session is taking place. as well as The data network name (DNN) that identifies the PDU session.

30. The method of claim 28, wherein receiving the data from the second wireless communication device occurs outside the PDU session.

31. The method of claim 30, further comprising: The data received from the second wireless communication device is processed via the Proximity Service (ProSe) (PC5) protocol stack operation of layers 1, 2 and 3; as well as The data is processed via Layer 1, 2 and 3 New Radio (NR) protocol stack operations for transmission to the network entity.

32. The method of claim 30, further comprising: The data received from the second wireless communication device is processed via Layer 1 and 2 Proximity Service (ProSe) (PC5) protocol stack operations; as well as The data is processed via Layer 1 and 2 New Radio (NR) protocol stack operations for transmission to the network entity.

Images