Patent Description:
Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. A wireless multiple-access communication system may include a number of base stations or access network nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE). In some cases, UEs may communicate directly with other UEs using communication protocols associated with proximity-based service (ProSe) communications, D2D communications, and the like.

<CIT> relates to a relay station and a relay method for relaying communication between a user apparatus and a base station. <CIT> relates to a system and method for using mobile wireless network information to modify network protocol performance.

A UE (e.g., a remote UE) may move out of coverage area of a base station and, instead, rely on a relay link with a neighboring UE (e.g., a relay UE) to continue communicating with the network. Alternatively, the remote UE may try to use the relay link for other considerations, e.g. uplink transmission power limitation, etc. Generally, the remote UE may discover the existence of the neighboring UE using a ProSe discovery process and select the neighboring UE as a relay UE. The remote UE may establish a relay link with the relay UE in order for the traffic from the remote UE to be forwarded to the network, and so that traffic from the network can be relayed to the remote UE. In some cases, the relay UE may support relay links with more than one remote UE.

In such a relay environment, the remote UE may have its own S1 interface, e.g., the control plane S1 mobility management entity (S1-MME) and/or S1 user plane (S1-U) that is different from the S1 interface of the relay UE. In some aspects, e.g., a <NUM> wireless communication system, the S1-MME may correspond to an N2 interface and S1-U may correspond to an N3 interface. For example, non-access stratum (NAS) signaling between the remote UE and mobility management entity (MME) may be exchanged without processing by the relay UE. As another example, the remote UEs data may be sent to the base station using a sidelink user-plane and an Uu (uplink) user-plane. Moreover, different bearers may be established for the remote UE than those that are established for the relay UE, however the relay UE may only support a limited number of bearers with the base station. With multiple remote UEs, this may result in different UE bearers (of remote UEs and/or relay UE) being multiplexed together during a transmission. Each bearer, however, may have its own associated QoS requirements, priority level, and the like. Current protocols, however, do not support differentiation of these bearers over the relay UE's Uu radio interface link between the relay UE and the base station or over the PC5 radio interface link between the relay UE and the remote UE. Conventional protocols also may not support different priority levels between bearers, e.g., a prioritized signaling radio bearer (SRB) over a data radio bearer (DRB).

Wireless devices (e.g., UEs) are generally mobile and may, at times, lose connection to a base station, which by extension disconnects the UE from accessing certain network functions. Existing ProSe, D2D, etc., services generally provide a mechanism for UEs to communicate directly with one another to exchange information, for example, a remote UE may benefit from leveraging a ProSe connection to a neighboring UE as a relay link. For example, a remote UE outside the coverage area of a base station may establish a ProSe connection with a neighboring UE that is within the coverage area of the base station. In some aspects, the remote UE to may use of the relay link even when in the coverage area of the base station. For example, by making use of the relay link (which may require much lower transmission power due to the short range), the remote UE with limited transmission capability may reach the network via the relay UE. It may also help to preserve power for those low power remote UEs, e.g., internet-of-things (IoT) devices. The neighboring UE (or relay UE) may provide a relay link to the remote UE that permits the remote UE to reconnect with the base station and, by extension, to network functions. To support relay operations, a PC5 radio interface link may be established between the remote UE and the relay UE and a Uu radio interface link may be established between the relay UE and the base station. In some examples, the relay UE may support relay links with multiple remote UEs.

Conventional techniques may not support bearer differentiation in a relay wireless communication link scenarios. For example, UEs typically use bearers that are established for communicating different types of information. Examples of bearers may include, but are not limited to, a SRB, which exchanges various signaling and overhead information, and evolved packet system (EPS) bearers and a DRB that is used to exchange data, user traffic, Internet Protocol (IP) packets, and the like. Each bearer may be identified using a logical channel identifier (LCID) and may have an associated QoS parameter set, e.g., maximum bit rate, guaranteed bit rate, and the like. Moreover, each UE may support only a certain number of bearers, e.g., eight radio bearers. Differentiation between bearers in a relay environment may not be supported using conventional relay wireless communication links, but may be necessary to ensure each bearer is treated according to its associated QoS parameter set.

Aspects of the disclosure are initially described in the context of a wireless communication system, such as a system that supports relay wireless communication link(s). Generally, the wireless communication system may be a packet-based wireless communication system such that information is exchanged between the remote UE and the relay UE and also between the relay UE and the base station using one or more packets. Multiple packets may be multiplexed during a transmission using different time/frequency resources where individual packet(s) may be associated with a relay UE or the remote UE. In some aspects, differentiation between bearers may be accomplished on a per-packet basis. Broadly, the described techniques provide for different approaches for bearer differentiation per packet. In a first approach, each packet may carry the corresponding QoS information for the associated bearer, e.g., QoS class identifier (QCI), allocation and retention policy (ARP), etc., in a packet header. This may be implemented using a mapping configuration (e.g., without additional signaling) and may provide a coarse degree of differentiation. Additional indicator(s) may optionally be used to further differentiate between SRBs and DRBs, for example. In a second approach, the packet header may include a special identifier used to create virtual radio bearers, where each virtual radio bearer maps to a corresponding bearer (e.g., SRB, DRB, etc.). This may be implemented using additional signaling over the relay link(s), but may provide a finer degree of differentiation between bearers and, when appropriate, bearers for different remote UEs. In some aspects, some or all of the aspects from the first approach and the second approach may be combined in a hybrid approach for bearer differentiation.

Thus, in certain aspects a relay wireless communication link may be used for wireless communication between a remote UE and a relay UE (e.g., a PC5 radio interface) and/or between the relay UE and a base station (e.g., a Uu radio interface). The relay link may use multiple bearers (e.g., SRB(s) and/or DRB(s)) for the relay UE and/or the remote UE). Each bearer may have an associated QoS parameter set and the relay link may use packet(s) for wireless communications. In one approach, a transmitting device (which could be the remote UE, the relay UE, and/or the base station, depending on the situation) may identify a particular packet for transmission on the relay link, the packet belonging to a first bearer. The transmitting device may configure a header of the packet (e.g., a L2 header that is processed by the relay UE) to carry or otherwise convey an indication of the QoS parameter set. The transmitting device transmits the packet and the receiving device (which could be the remote UE, relay UE, and/or base station, depending upon the situation) may use the QoS information in the header to identify the first bearer and/or otherwise treat the packet according to the QoS parameter set.

Additionally or alternatively, the transmitting device may identify a bearer mapping configuration associated with the relay link. The transmitting device may select an identifier of a first virtual bearer corresponding to the first bearer (e.g., according to the bearer mapping configuration) and configure the header to carry or otherwise convey the identifier. The transmitting device may transmit the packet and the receiving device may use the identifier and the bearer mapping configuration to identify the first bearer.

Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to QoS support for L2 based D2D relay.

<FIG> illustrates an example of a wireless communication system <NUM>, in accordance with one or more aspects of the present disclosure. The wireless communication system <NUM> may include network devices <NUM> (e.g., gNodeBs (gNBs), evolved node Bs (eNBs)), UEs <NUM>, and a core network <NUM>. In some examples, the wireless communication system <NUM> may be a LTE (or LTE-Advanced (LTE-A) network, or a NR network. In some cases, wireless communication system <NUM> may support enhanced broadband communications, ultra-reliable (i.e., mission critical) communications, low latency communications, and communications with low-cost and low-complexity devices.

The core network <NUM> may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. At least some of the network devices <NUM> (e.g., network device <NUM>-a), which may be an example of a base station (e.g., eNB, network access devices, gNB), or network device <NUM>-b, which may be an example of an access node controller (ANC)), may interface with the core network <NUM> through backhaul links <NUM> (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communication with the UEs <NUM>. In various examples, the network devices <NUM>-b may communicate, either directly or indirectly (e.g., through core network <NUM>), with each other over backhaul links <NUM> (e.g., X1, X2, etc.), which may be wired or wireless communication links.

Each network device <NUM>-b may also additionally or alternatively communicate with a number of UEs <NUM> through a number of other network devices <NUM>-c, where network device <NUM>-c may be an example of a smart radio head (or through a number of smart radio heads). In alternative configurations, various functions of each network device <NUM> may be distributed across various network devices <NUM> (e.g., radio heads and access network controllers) or consolidated into a single network device <NUM> (e.g., a base station).

The communication networks that may accommodate some of the various disclosed examples may be packet-based networks that operate according to a layered protocol stack. In the user plane, communications at the bearer over packet data convergence protocol (PDCP) layer may be IP-based or non-IP based. The MAC layer may also use Hybrid Automatic Repeat Request (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE <NUM> and a network device <NUM>-c, network device <NUM>-b, or core network <NUM> supporting radio bearers for user plane data.

The UEs <NUM> may be dispersed throughout the wireless communication system <NUM>, and each UE <NUM> may be stationary or mobile. A UE <NUM> may also include or be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, a wireless node, or some other suitable terminology. A UE <NUM> may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, an IoT device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, or the like. A UE <NUM> may be able to communicate with various types of network devices <NUM>-a, network devices <NUM>-c, base stations, access points, or other network devices, including macro eNBs, small cell eNBs, relay base stations, and the like. A UE <NUM> may communicate with the core network <NUM> through communication link <NUM>.

In some cases, a UE <NUM> may also be able to communicate directly with other UEs (e.g., using a peer-to-peer (P2P) or D2D protocol). Other UEs <NUM> in such a group may be outside the coverage area <NUM> of a cell, or otherwise unable to receive transmissions from a network device <NUM>. In some cases, a network device <NUM> facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out independent of a core network <NUM>. Another example of direct UE <NUM> communications may include V2X and/or V2V communications.

In some cases, an MTC device may operate using half-duplex (one-way) communications at a reduced peak rate. MTC devices may also be configured to enter a power saving "deep sleep" mode when not engaging in active communications. In some cases, MTC or IoT devices may be designed to support mission critical functions and wireless communications system may be configured to provide ultra-reliable communications for these functions.

In some aspects, the described techniques refer to a requesting device and a responding device. The requesting device may refer to a UE <NUM> and/or a network device <NUM> (also referred to as a base station) when configured or otherwise acting as a device requesting data from a responding device. The responding device may refer to a UE <NUM> and/or a network device <NUM> when configured or otherwise acting as a device providing the data to the requesting device.

The communication links <NUM> shown in wireless communication system <NUM> may include uplink (UL) channels from a UE <NUM> to a network device <NUM>-c, and/or downlink (DL) channels, from a network device <NUM>-c to a UE <NUM>. The DL channels may also be called forward link channels, while the UL channels may also be called reverse link channels. Control information and data may be multiplexed on an UL channel or DL according to various techniques. Control information and data may be multiplexed on a DL channel, for example, using time-division multiplexing (TDM) techniques, frequency-division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, the control information transmitted during a transmit time interval (TTI) of a DL channel may be distributed between different control regions in a cascaded manner (e.g., between a common control region and one or more UE-specific control regions).

Wireless communication system <NUM> may operate in an ultra high frequency (UHF) frequency region using frequency bands from <NUM> to <NUM> (<NUM>), although in some cases wireless local area networks (WLANs) may use frequencies as high as <NUM>. This region may also be known as the decimeter band, since the wavelengths range from approximately one decimeter to one meter in length. UHF waves may propagate mainly by line of sight, and may be blocked by buildings and environmental features. However, the waves may penetrate walls sufficiently to provide service to UEs <NUM> located indoors. Transmission of UHF waves is characterized by smaller antennas and shorter range (e.g., less than <NUM>) compared to transmission using the smaller frequencies (and longer waves) of the high frequency (HF) or very high frequency (VHF) portion of the spectrum. In some cases, wireless communication system <NUM> may also utilize extremely high frequency (EHF) portions of the spectrum (e.g., from <NUM> to <NUM>). This region may also be known as the millimeter band, since the wavelengths range from approximately one millimeter to one centimeter in length. Thus, EHF antennas may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a UE <NUM> (e.g., for directional beamforming). However, EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than UHF transmissions.

Thus, wireless communication system <NUM> may support millimeter wave (mmW) communications between UEs <NUM> and network devices <NUM>. Devices operating in mmW or EHF bands may have multiple antennas to allow beamforming. That is, a network device <NUM> may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE <NUM>. Beamforming (which may also be referred to as spatial filtering or directional transmission) is a signal processing technique that may be used at a transmitter (e.g., a network device <NUM>) to shape and/or steer an overall antenna beam in the direction of a target receiver (e.g., a UE <NUM>). This may be achieved by combining elements in an antenna array in such a way that transmitted signals at particular angles experience constructive interference while others experience destructive interference.

In some cases, wireless communication system <NUM> may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system <NUM> may employ LTE License Assisted Access (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NR technology in an unlicensed band such as the <NUM> Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, wireless devices such as network devices <NUM> and UEs <NUM> may employ listen-before-talk (LBT) procedures to ensure the channel is clear before transmitting data. In some cases, operations in unlicensed bands may be based on a carrier aggregation (CA) configuration in conjunction with component carriers (CCs) operating in a licensed band. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, or both. Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD) or a combination of both.

Wireless communication system <NUM> may include or support networks used for vehicle based communications, also referred to as V2X, V2V networks, and/or C-V2X networks. Vehicle based communication networks may provide always on telematics where UEs, e.g., v-UEs, communicate to V2N, to V2P UEs, to V2I, and to other v-UEs (e.g., via the network). The vehicle based communication networks may support a safe, always-connected driving experience by providing intelligent connectivity where traffic signal/timing, real-time traffic and routing, safety alerts to pedestrians/bicyclist, collision avoidance information, etc., are exchanged.

In some cases, a UE <NUM> may also be able to communicate directly with other UEs (e.g., using a P2P, ProSe, or D2D protocols). In some cases, groups of UEs <NUM> communicating via D2D communications may utilize a <NUM>:M system in which each UE <NUM> transmits to every other UE <NUM> in the group.

Generally, aspects of the described techniques may refer to a transmitting device and/or receiving device. Within the context of a relay wireless communication link (e.g., a D2D or ProSe-based relay link), a transmitting device may refer to one or more of a remote UE <NUM> (e.g., transmitting to a relay UE <NUM>), a relay UE <NUM> (e.g., transmitting to either or both of the remote UE <NUM> and base station <NUM>), and/or a base station <NUM> (e.g., transmitting to a relay UE <NUM>). Similarly, a receiving device may refer to one or more of a remote UE <NUM> (e.g., receiving a transmission from a relay UE <NUM>), a relay UE <NUM> (e.g., receiving a transmission from either or both of the remote UE <NUM> and base station <NUM>), and/or a base station <NUM> (e.g., receiving a transmission from a relay UE <NUM>).

One or more of network devices <NUM> may include a base station (BS) QoS support manager <NUM>. One or more of the UEs <NUM> may include a UE QoS support manager <NUM>. The functions of the BS QoS support manager <NUM> and/or the UE QoS support manager <NUM> may be similar, depending upon whether the network device <NUM> and/or the UE <NUM> is acting as a transmitting device or a receiving device. Thus, a UE <NUM> and/or network device <NUM> may support one or more aspects of the described techniques for bearer differentiation. For example, a transmitting device (UE <NUM> and/or network device <NUM>, depending upon the situation) may be communicating via a relay wireless communication link. The communications may use a plurality of bearers. The transmitting device may identify packet for transmission on the relay link, the packet belonging to a first bearer. The first bearer may have an associated QoS parameter set. The transmitting device may configure a header of the packet to convey an indication of the QoS parameter set. The packet may be processed by the relay wireless device (e.g., relay UE <NUM>), e.g., processed by the L2 of the relay wireless device. The transmitting device may transmit the packet with the header on the relay link and according to the QoS parameter set (e.g., the packet being afforded the same QoS as the associated bearer). A receiving device may receive the packet and use the indicated QoS parameter set to identify the first bearer that was used to convey the packet on the relay link.

Additionally or alternatively, the transmitting device may configure a header of a packet for transmission on the relay wireless communication link. Additionally or alternatively, the transmitting device may identify a bearer mapping configuration associated with the relay link. The transmitting device may identify a packet for transmission on the relay link, the packet belonging to a first bearer. The transmitting device may use the bearer mapping configuration to select an identifier associated with a first virtual radio bearer. The first virtual radio bearer may correspond to the first bearer and the relay link may correspond to a radio bearer. The transmitting device may configure, according to the bearer mapping configuration, a header of the packet that is processed by the relay wireless device to include an identifier. The identifier may carry or otherwise convey information associated with the first bearer. The transmitting device may transmit the packet with the header on the relay link. A receiving device may receive the packet and determine that the identifier is associated with the first virtual radio bearer. The receiving device may identify the first bearer based at least in part on the identifier.

<FIG> illustrates an example of a system for wireless communication <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Wireless communication system <NUM> may implement aspect(s) of wireless communication system <NUM>. Wireless communication system <NUM> may include a base station <NUM>-a, a remote UE <NUM>-a and a relay UE <NUM>-b, which may be examples of the corresponding devices described herein. The base station <NUM>-a, the remote UE <NUM>-a, and/or the relay UE <NUM>-b may be examples of a transmitting device and/or a receiving device. Wireless communication system <NUM> may support a relay wireless communication link.

Wireless communication system <NUM> may include relay UE <NUM>-b providing a relay link connecting remote UE <NUM>-a to base station <NUM>-a and other network elements. In one example, the relay wireless communication link may include a link <NUM> between the base station <NUM>-a and the relay UE <NUM>-b and a link <NUM> between the relay UE <NUM>-b and the remote UE <NUM>-a. Link <NUM> may be an example of a radio interface between the base station <NUM>-a and the relay UE <NUM>-b and may be, in some examples, a Uu radio interface, a LTE-Uu radio interface, and the link. Link <NUM> may be an example of a link established using D2D, ProSe, and other UE-to-UE direct communication protocols. In some examples, link <NUM> may include a PC5 radio interface link. In some example, link <NUM> may be a subset of the Uu radio interface.

The relay wireless communication link may also provide connectivity for each of the remote UE <NUM>-a and the relay UE <NUM>-b to other network functions associated with a core network (such as the core network <NUM>). For example, the relay wireless communication link may provide connectivity between the remote UE <NUM>-a and the relay UE <NUM>-b to a MME, a S-GW, a P-GW, and the like. Each of remote UE <NUM>-a and relay UE <NUM>-b may have an individual S1 interface established between the UE <NUM> and the MME, S-GW, etc., via the base station <NUM>-a. Within the relay link, remote UE <NUM>-a may send NAS information directly to the MME (e.g., without being processed by the relay UE <NUM>-b). Data from the remote UE <NUM>-a may be transmitted to the base station <NUM>-a using a sidelink user-plane and/or Uu user-plane link.

In some aspects, one or more of the remote UE <NUM>-a, relay UE <NUM>-b, and/or base station <NUM>-a may use a layer protocol architecture that includes different layers, e.g., Layer <NUM> (L1), L2, and Layer <NUM> (L3). Broadly, L1 may be the lowest layer (or physical layer) and implements various physical layer signaling functions. L2 is generally above the physical layer and may implement the link between the UE <NUM> and the base station <NUM>-a. L2 may be broken down into the user-plane and the control-plane. L3 may be considered the IP layer.

In the user-plane, L2 may include a MAC sublayer (e.g., priority handling and multiplexing of logical channels into transport channels), a RLC sublayer (e.g., packet segmentation and reassembly to communicate over logical channels), a PDCP sublayer (e.g., multiplexing between different radio bearers and logical channels), and/or an adaptation sublayer (e.g., manages aspect(s) of a P2P link). In the control plane, L2 may include a RRC protocol layer that provides establishment, configuration, and maintenance of an RRC connection supporting radio bearers for user-plane data.

Wireless communication system <NUM> may also use a plurality of bearers for communicating. Example bearers may include, but are not limited to, a radio bearer (e.g., an SRB and/or DRB), an S1 bearer, an e-radio access bearer, an EPS bearer, and end-to-end bearer, and the like. Each bearer may have an associated LCID, an associated QoS parameter set, and the like. Moreover, each of the remote UE <NUM>-a and the relay UE <NUM>-b may have their own respective bearers. Typically, the bearers associated with a particular UE <NUM> may be tracked according to their LCID and are communicated according to their associated QoS parameter set. In a relay wireless communication link, bearer differentiation and associated QoS support may introduce additional considerations. Such considerations may be heightened by configurations limiting the number of bearers that can be associated with a particular UE.

Aspects of the present disclosure may provide for improved techniques for bearer differentiation, e.g., how to differentiate between relay UE <NUM>-b and remote UE <NUM>-a bearers and how to afford each bearer the appropriate QoS treatment during communications. Thus, for example a high priority bearer of the remote UE <NUM>-a may be communicated using the appropriate priority level even though the communication relies on a radio bearer between the relay UE <NUM>-b and the base station <NUM>-a. Aspects of the described techniques may be used individually or may be combined, in some examples.

In a first approach, each packet may carry the corresponding QoS information for a bearer, e.g., QCI, ARP, etc., in a header of the packet, e.g., an adaptation header, a PDCP header, and the like. This may use a bearer mapping configuration rather than additional signaling and may use additional parameter(s) to provide for differentiation between different bearer types.

In a downlink example for the Uu radio interface, this approach may include each packet carrying the QoS information. For example, the user plane packet coming down from the serving gateway (SGW) to the eNB may be associated with an EPS bearer, which has an associated QoS profile on the eNB. The eNB may identify the EPS bearer identifier of the packet based on the S1-U tunnel, or transport protocol marking. Using the EPS bearer identifier, it would be able to retrieve the corresponding QoS parameters (e.g., QoS parameter set) from the corresponding remote UE context. The eNB may also determine the radio bearer to send the packet based on the remote UE context. In this particular example, the remote UE may be associated with the relay UE, and therefore, the packets may be sent via a radio bearer of the relay UE associated with this remote UE, or the EPS bearer of this remote UE. The packet sent via the relay UE's radio bearer may carry the QCI and ARP value in the adaptation (or PDCP) header and the relay UE <NUM>-b may process each packet accordingly. The bit rate metrics for the packet (e.g., AMBR, GBR, maximum bitrate (MBR), etc.) may be managed or selected by base station <NUM>-a, rather than by the relay UE <NUM>-b. The adaptation layer may include an identifier to differentiate packets of different remote UEs.

In the downlink example for the PC5 radio interface, QoS handling may again be on a per packet basis. For example, the relay UE <NUM>-b may map QCI and ARP indications corresponding to a PPPP indicator when planning transmission of the packet to the remote UE <NUM>-a on the PC5 radio link. The mapping of the QCI/ARP to the PPPP may be based on a configuration established or managed by base station <NUM>-a and/or based on ProSe functions provisioned information. The relay UE <NUM>-b may re-order packets of different bearers based on the PPPP and the associated/derived packet delay budget (PDB).

In an uplink example for the Uu radio interface, QoS handling may again be on a per-packet basis. The relay UE <NUM>-b may receive a packet on the PC5 radio interface, which includes in the L2 header, e.g., adaptation layer header or PDCP header to the QoS indication, e.g., QCI or ARP. The relay UE <NUM>-b may decide the uplink DRB to use based on the QCI/ARP carried in the packet header. The QCI/ARP to DRB mapping may be configured by the base station <NUM>-a, e.g., in a RRC connection reconfiguration message during DRB setup/update. The uplink GBR, MBR and AMBR may be selected or managed by the base station <NUM>-a, rather than the relay UE <NUM>-b, during admission control and after obtaining the PDCP protocol data unit (PDU) of the remote UE <NUM>-a or the relay UE <NUM>-b. In the uplink example for the PC5 radio interface, QoS handling may again be on a per-packet basis. The remote UE <NUM>-a may map the QoS provided of a DRB to PPPP and PDB and transmit the packet over the PC5 relay link. The corresponding QCI and ARP may be carried in the header of the adaption layer (or PDCP layer) over the PC5 relay link. The GBR, MBR and/or AMBR may be selected or otherwise managed by the remote UE <NUM>-a, e.g., to avoid packet loss at the relay UE <NUM>-b. The QCI/ARP to PPPP/PDB mapping may be obtained via the UE configuration or as part of the PC5 link setup from the relay UE <NUM>-b.

Admission control in the first approach may include the base station <NUM>-a aggregating different DRB requirements into relay DRBs, e.g., the base station <NUM>-a may promote the QCI of a particular DRB or increase the AMBR/GBR/MBR. The base station <NUM>-a may select or otherwise manage uplink GBR/MBR/AMBR when obtaining the PDCP PDU of the remote UE <NUM>-a. Admission control in the first approach may include the relay UE <NUM>-b not managing GBR/MBR/AMBR enforcement. The relay UE <NUM>-b may use the ARP do selective packet transmission in the uplink.

RRC connection related messages according to the first approach may include each packet carrying additional information in the RRC connection reconfiguration message when each of the eight available DRBs is setup via the Uu radio interface. Additionally, when the DRB is used for the remote UE <NUM>-a, the mapping of the QCI and ARP to PPP may be provided in the RRC connection reconfiguration message.

Thus, aspects of the first approach may include the remote UE <NUM>-a, the relay UE <NUM>-b, and the base station <NUM>-a communicating via a relay wireless communication link (e.g., either or both of links <NUM> and <NUM>). The communications may include communicating using a plurality of bearers, e.g., radio bearers and non-radio bearers. A transmitting device may configure a header of a packet for transmission on the relay wireless communication link. A transmitting device (e.g., any of the remote UE <NUM>-a, the relay UE <NUM>-b, or the base station <NUM>-a, depending on the situation) may identify a packet for transmission on the relay link. The packet may belong to or otherwise be associated with a first bearer that has an associated QoS parameter set. The transmitting device may configure a header of the packet (e.g., a L2 header processed by the relay UE <NUM>-b) to convey an indication of the QoS parameter set and transmit the packet with the header on the relay link. The packet may be transmitted according to the QoS parameter set, e.g., at the appropriate priority level, with the appropriate bit rate, etc. Thus, QoS support may be provided for packets of bearers of the remote UE <NUM>-a during transmission between the remote UE <NUM>-a to the relay UE <NUM>-b and between the relay UE <NUM>-b to the base station <NUM>-a.

In a second approach, the header of the packet may include a special identifier that is used to create virtual bearers, with each virtual bearer mapping to a bearer of the plurality of bearers. The packet header may be an adaptation header and/or a PDCP header. The second approach may include additional signaling over the PC5 and Uu radio interfaces, but may also provide increased QoS control and a more refined granularity for bearer differentiation.

In a downlink example of the Uu radio interface, the identifier may support using more than a predetermined number of virtual bearers, e.g., more than eight. For example, when a bearer, e.g., EPS bearer is setup for the remote UE, signaling from the MME may inform the eNB (or base station) regarding the QoS profile and bearer identifications, e.g. the E-RAB ID. As the eNB is aware of the association of the remote UE and relay UE, it understands the need to carry the corresponding bearer of the remote UE in a relay UE's radio bearer. After identified the corresponding radio bearer of the relay UE, the eNB may send a RRC connection reconfiguration message to inform the relay UE of such arrangement, and the corresponding identifier to be used in the L2 header of the packets for this bearer, EPS bearer. The RRC connection reconfiguration message may also inform the relay UE regarding the QoS profile of this particular bearer. Similarly, the eNB may inform the remote UE of the identifier to use via an RRC connection reconfiguration message directly or via the relay UE. This identifier allows the bearer of the remote UE to be transferred within the radio bearer of the relay UE as a virtual radio bearer. The adaptation (or PDCP) layer header may include an identifier for each of the EPS bearers, DRBs, etc. The relay UE <NUM>-b may map the identifier to the corresponding EPS bearer/DRB(s) and their corresponding QoS profiles or parameters. The base station <NUM>-a may configure the relay UE <NUM>-b with a bearer mapping for the virtual bearers (e.g., QCI, ARP, etc.) in a RRC connection reconfiguration message, for example. In the downlink example for the PC5 radio interface, the relay UE <NUM>-b may map the identifier to the corresponding link <NUM> with the remote UE <NUM>-a. For each remote UE, the relay UE <NUM>-b may setup a virtual link whenever it receives a RRC connection reconfiguration message for the virtual DRB(s) over the Uu radio interface. This may use a PC5 signaling protocol (PC5-SP) that includes a mechanism to allow the relay UE <NUM>-b triggered link setup. The relay UE <NUM>-b may transmit the packets over the PC5 radio interface based on the associated QoS parameter set for the virtual link, e.g., extending beyond the traditional PPPP functions. For example, this may allow configuring the remote UE to include additional information on the QoS in the message header.

In an uplink example of Uu radio interface, the remote UE <NUM>-a may maintain a mapping of the virtual link of the PC5 interface and its own DRBs. The QoS profile associated with the virtual link may be configured by the base station <NUM>-a or negotiated with the relay UE <NUM>-b during the link setup over the PC5 interface. In some examples, no special QoS indicator may need to be carried in the packet header over the PC5 radio interface other than the identifier of the virtual link. In the uplink example for the Uu radio interface, the relay UE <NUM>-b may manage each virtual link separately and therefore may use a buffer status report (BSR) to indicate the virtual link identifier. The virtual link may be mapped by the base station <NUM>-a to actual DRBs, and the associated QoS for each bearer may be implemented accordingly. Such mapping may also be used for SRB(s) of the remote UE <NUM>-a.

Admission control in the second approach may include the base station <NUM>-a selecting or managing the QoS profiles with the virtual DRBs over the Uu radio interface. The base station <NUM>-a may store the mapping of the virtual DRB identifier and the actual DRB QoS parameter or DRB QoS parameter set. The base station <NUM>-a may use the virtual identifier in the BSR for scheduling according to the QoS parameter or QoS parameter set. The relay UE <NUM>-b may associate the QoS parameter set with the PC5 radio interface link of the corresponding virtual Uu DRBs. The relay UE <NUM>-b may maintain a mapping of the PC5 virtual link and the Uu virtual DRB identifiers. The relay UE <NUM>-a may report additional PC5 status information to base station <NUM>-a to implement the virtual DRB admission.

RRC connection related messages according to the second approach may include an additional information element (IE) introduced in the RRC connection reconfiguration message. The additional IE may identify the additional QoS configuration for each virtual link/bearer. Thus, a RRC connection reconfiguration message may not be needed for each new virtual DRB ID. In some aspects, a "VirtualDRB-ToAddMod" IE may be added to a "RadioResourceConfigDedicated" IE, and with the associated virtual DRB identifier. The relay UE <NUM>-b may use this virtual DRB identifier to request resources in the BSR, for example.

Thus, aspects of the second approach may include the remote UE <NUM>-a, the relay UE <NUM>-b, and the base station <NUM>-a communicating via a relay wireless communication link (e.g., either or both of links <NUM> and <NUM>). The communications may include communicating using a plurality of bearers, e.g., radio bearers and non-radio bearers. A transmitting device may configure a header of a packet for transmission on the relay wireless communication link. A transmitting device (e.g., any of the remote UE <NUM>-a, the relay UE <NUM>-b, or the base station <NUM>-a, depending on the situation) may identify a bearer mapping configuration associated with the relay link. The transmitting device may identify a packet for transmission on the relay link. The packet may belong to or otherwise be associated with a first bearer that has an associated QoS parameter or QoS parameter set (or profile). The transmitting device may select an identifier associated with a first virtual radio bearer that corresponds to the first bearer. The transmitting device may configure a header of the packet (e.g., a L2 header processed by the relay UE <NUM>-b) to convey an indication of the identifier and transmit the packet with the header on the relay link. The packet may be transmitted according to the QoS parameter or QoS parameter set, e.g., at the appropriate priority level, with the appropriate bit rate, etc. Thus, QoS support may be provided for differentiation of bearer packets of the remote UE <NUM>-a during transmission between the remote UE <NUM>-a to the relay UE <NUM>-b and between the relay UE <NUM>-b to the base station <NUM>-a.

As is discussed above, some or all of the aspects of the first and second approaches may be used in combination to support QoS support for L2 based D2D relay. For example, the header may carry the QoS parameter or QoS parameter set in combination with the virtual ink identifier. This may improve the granularity of the bearer identification and treatment at the remote UE <NUM>-a, the relay UE <NUM>-b, and/or the base station <NUM>-a. In addition, the above examples focused on the user plane traffic, i.e., EPS bearers and DRBs. However, similar techniques can be used for the differentiation of the SRBs. For SRBs of the remote UE, some default configuration of the QoS treatment can be provided to the eNB or default QoS handling can be standardized. In this case, the packets that is used for carrying the signaling message could carry the corresponding QoS indication, e.g. other than the normal QCI value or ARP value. Similarly, when a second approach is used for virtual radio bearer identifier, the eNB or relay UE could use a special identifier to represent the signaling bearers and the RRC Connection Reconfiguration message can carry some special IEs just for virtual SRB binding.

<FIG> illustrates an example of a header configuration <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Header configuration <NUM> may implement aspect(s) of wireless communication system <NUM> and/or <NUM>, as described herein. For example, a remote UE, a relay UE, and/or a base station may implement aspect(s) of header configuration <NUM>. A remote UE, relay UE, and/or base station may be examples of the corresponding devices described herein. Generally, the header configuration <NUM> may implement aspect(s) of the first approach for QoS support in L2 based D2D relay, as is described herein.

Broadly, header configuration <NUM> may include a header of the packet belonging to a particular bearer. The packet header may include a RLC header <NUM> (e.g., a header configured by the RLC sublayer of the L2), an adaptation header <NUM> (e.g., a header configured by the adaptation sublayer of the L2), a PDCP PDU <NUM> (e.g., a PDU added by the PDCP sublayer of the L2). It is to be understood that the packet will also contain additional information, such as a data payload, control information, and the like.

The adaptation header <NUM> may be configured to convey an indication of the QoS parameter or QoS parameter set for the packet belonging to the bearer. That is, the QoS parameter or QoS parameter set may provide information used to support the packet being transmitted according to the QoS profile for the bearer, e.g., at the appropriate priority level, using the appropriate bit rate, and the like. In the example header configuration <NUM>, the adaptation header <NUM> may convey the QoS parameter or QoS parameter set by including a QCI indicator <NUM> and/or an ARP indicator <NUM>. The adaptation sublayer may carry the QoS parameter or QoS parameter set over the PC5 and/or Uu radio interface from the remote UE, which may be processed or otherwise used by the relay UE to map the packet to the correct bearer. Thus, a transmitting device may configure a header of a packet to carry or otherwise convey an indication of the QoS parameter or QoS parameter set using header configuration <NUM>.

Although the header configuration <NUM> shows the QoS parameter or QoS parameter set being carried in the adaptation header <NUM>, it is to be understood that the PDCP PDU <NUM> may be used to carry the QoS parameter or QoS parameter set.

<FIG> illustrates an example of a header configuration <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Header configuration <NUM> may implement aspect(s) of wireless communication system <NUM> and/or <NUM>, as described herein. For example, a remote UE, a relay UE, and/or a base station may implement aspect(s) of header configuration <NUM>. A remote UE, relay UE, and/or base station may be examples of the corresponding devices described herein. Generally, the header configuration <NUM> may implement aspect(s) of the second approach for QoS support in L2 based D2D relay, as is described herein.

The adaptation header <NUM> may be configured to convey an indication of the virtual link identifier for the packet belonging to the bearer. That is, the virtual ink identifier (or simply identifier) may provide information used to support the packet being transmitted according to the QoS profile for the particular bearer, e.g., at the appropriate priority level, using the appropriate bit rate, and the like.

In the example header configuration <NUM>, the adaptation header <NUM> may convey the virtual link identifier using a various examples. In one example, the virtual link identifier may be carried by a particular pair, e.g., a source L2 identifier and a destination L2 identifier pair. This may provide for bearer differentiation per remote UE. In another example, the virtual link identifier may be conveyed by the source/destination L2 identifier pair and may also include an additional virtual link identifier added in the adaptation sublayer (or PDCP sublayer) between the RLC header <NUM> and the PDCP PDU <NUM>. This may support differentiation of the different EPS bearers (e.g., default bearer and dedicated bearers) of a remote UE. The virtual link identifier may correspond to the EPS bearer ID of the remote UE, for example. Thus, a transmitting device may configure a header of a packet to carry or otherwise convey an indication of the identifier (e.g., virtual link identifier) using header configuration <NUM>.

Although the header configuration <NUM> shows the virtual link identifier being carried in the adaptation header <NUM>, it is to be understood that the PDCP PDU <NUM> may be used to carry the virtual link identifier.

<FIG> illustrates an example of a header configuration <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Header configuration <NUM> may implement aspect(s) of wireless communication system <NUM> and/or <NUM>, as described herein. Header configuration <NUM> may implement aspects of header configuration <NUM>, as described herein. For example, a remote UE, a relay UE, and/or a base station may implement aspect(s) of header configuration <NUM>. A remote UE, relay UE, and/or base station may be examples of the corresponding devices described herein. Generally, the header configuration <NUM> may implement aspect(s) of the second approach for QoS support in L2 based D2D relay, as is described herein.

Broadly, header configuration <NUM> may be used in a header of the packet belonging to a particular bearer. Header configuration <NUM> illustrates two examples of a header configuration. A first example may include a Uu radio interface header and the second example may include a PC5 radio interface header. The packet header may include a header having one or more control elements (CEs). Header configuration <NUM> in the Uu radio interface may include a logical channel group identifier (LCGID) CE <NUM> which may have five bits, a virtual DRB identifier CE <NUM> which may include N bits, and a buffer size CE <NUM> which may include six bits. Header configuration <NUM> in the PC5 radio interface may further include a destination CE <NUM>, which includes or otherwise conveys an indication of the destination address of the header. As is discussed above, aspects of the described techniques may include conveying an identifier indicator using a BSR. For example, a relay UE may associate a QoS profile with the PC5 virtual link of the corresponding virtual Uu DRBs.

In some aspects, the LCGID CE <NUM> and the virtual DRB identifier CE <NUM> may be used together to category a virtual link established over the PC5 radio interface. For example, the relay UE may sent the mapping of LCGID and virtual DRB identifier and the UE identifier and bearer identifier to the base station using a UE information message, e.g., per ProSe/D2D protocols. The UE identifier may be a cell radio network temporary identifier (C-RNTI), in some examples. The buffer size CE <NUM> (e.g., the BSR) may carry an indication of the aggregated traffic from different remote UEs. The header configuration <NUM> may be used to distinguish the BSR between the relay UEs own Uu uplink request and the BSR for mode <NUM> scheduling over PC5.

In some aspects, the number of bits (e.g., value of N) for the virtual DRB identifier CE <NUM> may be selected according to a variety of factors. As one example, a large value of N may be selected to unique identify each different QoS bearer in each remote UE. In another example, a smaller value of N may be selected and the relay UE may aggregate similar traffic into the same virtual DRB identifier for scheduling.

<FIG> shows a diagram <NUM> of a wireless device <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a UE <NUM> (e.g., a relay UE and/or remote UE) or base station <NUM> as described herein. Wireless device <NUM> may include a receiver <NUM>, a QoS support manager <NUM>, and a transmitter <NUM>. wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to QoS support for L2 based D2D relay, etc.). Information may be passed on to other components of the device. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>.

QoS support manager <NUM> may be an example of aspects of the QoS support manager <NUM> described with reference to <FIG>.

QoS support manager <NUM> and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the QoS support manager <NUM> and/or at least some of its various sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure. The QoS support manager <NUM> and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices. In some examples, QoS support manager <NUM> and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, QoS support manager <NUM> and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

QoS support manager <NUM> may communicate via a relay wireless communication link, the communicating including communications using a set of bearers. QoS support manager <NUM> may configure a header of a packet for transmission on the relay wireless communication link. QoS support manager <NUM> may also identify a packet for transmission on the relay wireless communication link belonging to a first bearer, the first bearer having an associated QoS parameter. QoS support manager <NUM> may configure a header of the packet that is processed by a relay wireless device to convey an indication of the QoS parameter or QoS parameter set. QoS support manager <NUM> may transmit the packet including the configured header on the relay wireless communication link according to the QoS parameter or QoS parameter set.

The QoS support manager <NUM> may also communicate via a relay wireless communication link, the communicating including communications using a set of bearers. QoS support manager <NUM> may receive a packet on the relay wireless communication link belongs to a first bearer, the packet including a header processed by a relay wireless device that is configured to convey an indication of a QoS parameter or QoS parameter set. QoS support manager <NUM> may identify, based on the QoS parameter or QoS parameter set, the first bearer used to convey the packet on the relay wireless communication link, the first bearer being associated with the QoS parameter or QoS parameter set.

The QoS support manager <NUM> may also communicate via a relay wireless communication link, the communicating including communications using a set of bearers. QoS support manager <NUM> may configure a header of a packet for transmission on the relay wireless communication link. QoS support manager <NUM> may identify a bearer mapping configuration associated with the relay wireless communication link. QoS support manager <NUM> may identify a packet for transmission on the relay wireless communication link belonging to the a first bearer. QoS support manager <NUM> may select an identifier associated with a first virtual radio bearer, where the first virtual radio bearer corresponds to the first bearer and the relay wireless communication corresponds to a radio bearer. QoS support manager <NUM> may configure, according to the bearer mapping configuration, a header of the packet that is processed by a relay wireless device to include an identifier, the identifier conveying information associated with the first bearer. QoS support manager <NUM> may transmit the packet including the header on the relay wireless communication link.

The QoS support manager <NUM> may also communicate via a relay wireless communication link, the communicating including communications using a set of bearers. QoS support manager <NUM> may identify a bearer mapping configuration associated with the relay wireless communication link. QoS support manager <NUM> may receive a packet on a first bearer of the relay wireless communication link, the packet including a header that is processed by a relay wireless device and is configured, according to the radio bearer mapping configuration, to include an identifier that conveys information associated with the first bearer. QoS support manager <NUM> may determine that the identifier is associated with a first virtual radio bearer, where the first virtual radio bearer corresponds to the first bearer and the relay wireless communication link corresponds to a radio bearer. QoS support manager <NUM> may identify the first bearer based on the identifier.

<FIG> shows a diagram <NUM> of a wireless device <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a wireless device <NUM> or a UE <NUM> or base station <NUM> as described herein. Wireless device <NUM> may include a receiver <NUM>, a QoS support manager <NUM>, and a transmitter <NUM>. wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

QoS support manager <NUM> may be an example of aspects of the QoS support manager <NUM> described with reference to <FIG>. QoS support manager <NUM> may also include a relay link communication manager <NUM>, a packet manager <NUM>, a header configuration manager <NUM>, a mapping manager <NUM>, and an identification manager <NUM>.

Relay link communication manager <NUM> may communicate via a relay wireless communication link, the communicating including communications using a set of bearers. Relay link communication manager <NUM> may transmit the packet including the configured header on the relay wireless communication link according to the QoS parameter or QoS parameter set. Relay link communication manager <NUM> may transmit the packet including the header on the relay wireless communication link. In some cases, the relay wireless communication link includes one of an uplink or a downlink connection using a PC5 radio interface between the relay wireless device and a remote wireless device. In some cases, the relay wireless communication link includes one of an uplink or a downlink connection using a Uu radio interface between a base station and the relay wireless device. In some cases, the first bearer includes one of a SRB or a DRB.

Packet manager <NUM> may identify a packet for transmission on the relay wireless communication link belonging to a first bearer, the first bearer having an associated QoS parameter or QoS parameter set. Packet manager <NUM> may receive a packet on the relay wireless communication link belongs to a first bearer, the packet including a header processed by a relay wireless device that is configured to convey an indication of a QoS parameter or QoS parameter set. Packet manager <NUM> may identify a packet for transmission on the relay wireless communication link belonging to the a first bearer. Packet manager <NUM> may receive a packet on a first bearer of the relay wireless communication link, the packet including a header that is processed by a relay wireless device and is configured, according to the radio bearer mapping configuration, to include an identifier that conveys information associated with the first bearer. In some cases, the QoS parameter or QoS parameter set may include a QCI. In some cases, the first bearer includes one of a SRB or a DRB.

Header configuration manager <NUM> may configure a header of the packet that is processed by a relay wireless device, for example, to convey an indication of the QoS parameter or QoS parameter set. Header configuration manager <NUM> may identify, based on the QoS parameter or QoS parameter set, the first bearer used to convey the packet on the relay wireless communication link, the first bearer being associated with the QoS parameter or QoS parameter set. Header configuration manager <NUM> may configure, according to the bearer mapping configuration, a header of the packet that is processed by a relay wireless device to include an identifier, the identifier conveying information associated with the first bearer. Header configuration manager <NUM> may configure the header to include a set of identifiers, each identifier conveying information associated with a corresponding bearer. Header configuration manager <NUM> may determine that the header includes a set of identifiers, each identifier conveying information associated with a corresponding bearer. Header configuration manager <NUM> may identify the first bearer from among the set of identifiers. In some cases, the header includes one of an adaptation header or a PDCP header.

Mapping manager <NUM> may identify a bearer mapping configuration associated with the relay wireless communication link. Mapping manager <NUM> may establish a mapping between a set of identifiers and a corresponding set of virtual radio bearers, where each virtual radio bearer corresponds to a bearer of the set of bearers. Mapping manager <NUM> may identify, during a connection establishment procedure, a mapping between the QoS parameter or QoS parameter set of the set of bearers and the radio bearers of the relay wireless communication link. Mapping manager <NUM> may identify, in the header of the packet and according to the bearer mapping configuration, an identifier that further conveys an indication of the first bearer. Mapping manager <NUM> may identify, during a connection establishment procedure, a mapping between the QoS parameter (or QoS parameter set) of the set of bearers and the set of radio bearers of the relay wireless communication link. Mapping manager <NUM> may configure, according to the bearer mapping configuration, the header of the packet to include an identifier that conveys an indication of the first bearer. In some cases, the mapping is identified according to a RRC configuration message exchanged during the connection establishment procedure. In some cases, each bearer of the set of bearers includes an associated QoS parameter or QoS parameter set. In some cases, the mapping is established during a connection establishment procedure and is exchanged using a RRC configuration message.

Identification manager <NUM> may select an identifier associated with a first virtual radio bearer, where the first virtual radio bearer corresponds to the first bearer and the relay wireless communication corresponds to a radio bearer. Identification manager <NUM> may determine that the identifier is associated with a first virtual radio bearer, where the first virtual radio bearer corresponds to the first bearer and the relay wireless communication link corresponds to a radio bearer. Identification manager <NUM> may identify the first bearer based on the identifier.

<FIG> shows a diagram <NUM> of a QoS support manager <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. The QoS support manager <NUM> may be an example of aspects of a QoS support manager <NUM>, a QoS support manager <NUM>, or a QoS support manager <NUM> described with reference to <FIG>, <FIG>, and <FIG>. The QoS support manager <NUM> may include a relay link communication manager <NUM>, a packet manager <NUM>, a header configuration manager <NUM>, a mapping manager <NUM>, an identification manager <NUM>, an ARP manager <NUM>, a PPPP manager <NUM>, a bearer aggregation manager <NUM>, a QoS manager <NUM>, and a BSR manager <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Packet manager <NUM> may identify a packet for transmission on the relay wireless communication link belonging to a first bearer, the first bearer having an associated QoS parameter or QoS parameter set. Packet manager <NUM> may receive a packet on the relay wireless communication link belongs to a first bearer, the packet including a header processed by a relay wireless device that is configured to convey an indication of a QoS parameter or QoS parameter set. Packet manager <NUM> may identify a packet for transmission on the relay wireless communication link belonging to the a first bearer. Packet manager <NUM> may receive a packet on a first bearer of the relay wireless communication link, the packet including a header that is processed by a relay wireless device and is configured, according to the radio bearer mapping configuration, to include an identifier that conveys information associated with the first bearer. In some cases, the QoS parameter or QoS parameter set includes a QCI. In some cases, the first bearer includes one of a SRB or a DRB.

Header configuration manager <NUM> may configure a header of the packet that is processed by a relay wireless device to convey an indication of the QoS parameter or QoS parameter set. Header configuration manager <NUM> may identify, based on the QoS parameter or QoS parameter set, the first bearer used to convey the packet on the relay wireless communication link, the first bearer being associated with the QoS parameter or QoS parameter set. Header configuration manager <NUM> may configure, according to the bearer mapping configuration, a header of the packet that is processed by a relay wireless device to include an identifier, the identifier conveying information associated with the first bearer, configure the header to include a set of identifiers, each identifier conveying information associated with a corresponding bearer. Header configuration manager <NUM> may determine that the header includes a set of identifiers, each identifier conveying information associated with a corresponding bearer. Header configuration manager <NUM> may identify the first bearer from among the set of identifiers. In some cases, the header includes one of an adaptation header or a PDCP header.

Mapping manager <NUM> may identify a bearer mapping configuration associated with the relay wireless communication link. Mapping manager <NUM> may establish a mapping between a set of identifiers and a corresponding set of virtual radio bearers, where each virtual radio bearer corresponds to a bearer of the set of bearers. Mapping manager <NUM> may identify, during a connection establishment procedure, a mapping between the QoS parameter (or QoS parameter set) of the set of bearers and the radio bearers of the relay wireless communication link. Mapping manager <NUM> may identify, in the header of the packet and according to the bearer mapping configuration, an identifier that further conveys an indication of the first bearer. Mapping manager <NUM> may identify, during a connection establishment procedure, a mapping between the QoS parameter (or QoS parameter set) of the set of bearers and the set of radio bearers of the relay wireless communication link. Mapping manager <NUM> may configure, according to the bearer mapping configuration, the header of the packet to include an identifier that conveys an indication of the first bearer. In some cases, the mapping is identified according to a RRC configuration message exchanged during the connection establishment procedure. In some cases, each bearer of the set of bearers includes an associated QoS parameter or QoS parameter set. In some cases, the mapping is established during a connection establishment procedure and is exchanged using a RRC configuration message. In some cases, the mapping is identified according to a RRC configuration message exchanged during the connection establishment procedure.

Identification manager <NUM> may select an identifier associated with a first virtual radio bearer, where the first virtual radio bearer corresponds to the first bearer and the relay wireless communication corresponds to a radio bearer. Identification manager <NUM> may determine that the identifier is associated with a first virtual radio bearer, where the first virtual radio bearer corresponds to the first bearer and the relay wireless communication link corresponds to a radio bearer, and identify the first bearer based on the identifier.

ARP manager <NUM> may configure the header to include the indication of the QoS parameter or QoS parameter set and an ARP indicator of the first bearer. ARP manager <NUM> may determine an ARP parameter associated with the packet of the first bearer. ARP manager <NUM> may determine the transmission of the packet according to the determined ARP parameter. ARP manager <NUM> may identify the first bearer based on the QoS parameter indication (or QoS parameter set indication) and an ARP indicator of the first bearer. In some cases, the relay wireless communication link includes one of an uplink connection or a downlink connection using a Uu radio interface between a base station and the relay wireless device.

PPPP manager <NUM> may configure the header to include the QoS parameter indication (or QoS parameter set indication) and a PPPP indicator of the first bearer. PPPP manager <NUM> may identify the first bearer based on the QoS parameter indication (or QoS parameter set indication) and a PPPP indicator of the first bearer. In some cases, the relay wireless communication link includes one of an uplink connection or a downlink connection using a PC5 radio interface between the relay wireless device and a remote wireless device.

Bearer aggregation manager <NUM> may aggregate two or more bearers into a relay bearer and select at least one of the QoS parameter (or QoS parameter set) associated with the first bearer or a bitrate parameter to apply to the relay bearer. In some cases, the bitrate parameter includes one of an AMBR or a GBR.

QoS manager <NUM> may identify a QoS parameter or QoS parameter set for the first bearer. QoS manager <NUM> may select the identifier based on the QoS parameter or QoS parameter set for the first bearer. QoS manager <NUM> may determine, based on the identifier, a QoS parameter or QoS parameter set for the first bearer. In some cases, the QoS parameter or QoS parameter set includes a QCI.

BSR manager <NUM> may configure a BSR to convey the identifier, where the identifier is associated with a virtual radio bearer. BSR manager <NUM> may configure a BSR to convey an aggregated traffic status from a set of remote wireless devices.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Device <NUM> may be an example of or include the components of wireless device <NUM>, wireless device <NUM>, or a UE <NUM> as described herein. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a UE QoS support manager <NUM>, a processor <NUM>, a memory <NUM>, a software <NUM>, a transceiver <NUM>, an antenna <NUM>, and an I/O controller <NUM>. These components may be in electronic communication via one or more busses (e.g., bus <NUM>). Device <NUM> may communicate wirelessly with one or more base stations <NUM>.

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting QoS support for L2 based D2D relay).

Software <NUM> may include code to implement aspects of the present disclosure, including code to support QoS support for L2 based D2D relay. Software <NUM> may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software <NUM> may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. Device <NUM> may be an example of or include the components of wireless device <NUM>, wireless device <NUM>, or a base station <NUM> as described herein. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a base station QoS support manager <NUM>, a processor <NUM>, a memory <NUM>, a software <NUM>, a transceiver <NUM>, an antenna <NUM>, a network communications manager <NUM>, and a base station communications manager <NUM>. These components may be in electronic communication via one or more busses (e.g., bus <NUM>). Device <NUM> may communicate wirelessly with one or more UEs <NUM>.

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting QoS support for L2 based D2D relay).

Base station communications manager <NUM> may manage communications with other base station <NUM>, and may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>. For example, the base station communications manager <NUM> may coordinate scheduling for transmissions to UEs <NUM> for various interference mitigation techniques such as beamforming or joint transmission. In some examples, base station communications manager <NUM> may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> for QoS support for L2 based D2D relay, in accordance with one or more aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a QoS support manager as described with reference to <FIG>. In some examples, a UE <NUM> or base station <NUM> may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE <NUM> or base station <NUM> may perform aspects of the functions described below using special-purpose hardware.

At <NUM> the UE <NUM> or base station <NUM> may communicate via a relay wireless communication link, the communicating comprising communications using a plurality of bearers. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a relay link communication manager as described with reference to <FIG> and <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may configure a header of the packet that is processed by a relay wireless device to convey an indication of the QoS parameter or QoS parameter set. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a header configuration manager as described with reference to <FIG> and <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may transmit the packet comprising the configured header on the relay wireless communication link according to the QoS parameter or QoS parameter set. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a relay link communication manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may communicate via a relay wireless communication link, the communicating comprising communications using a plurality of bearers. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a relay link communication manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may identify a packet for transmission on the relay wireless communication link belonging to a first bearer, the first bearer having an associated QoS parameter or QoS parameter set. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a packet manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may identify a bearer mapping configuration associated with the relay wireless communication link. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a mapping manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may configure a header of the packet that is processed by a relay wireless device to convey an indication of the QoS parameter or QoS parameter set. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a header configuration manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may configure, according to the bearer mapping configuration, the header of the packet to include an identifier that conveys an indication of the first bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a mapping manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may receive a packet on the relay wireless communication link belongs to a first bearer, the packet comprising a header processed by a relay wireless device that is configured to convey an indication of a QoS parameter or QoS parameter set. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a packet manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may identify, based at least in part on the QoS parameter or QoS parameter set, the first bearer used to convey the packet on the relay wireless communication link, the first bearer being associated with the QoS parameter or QoS parameter set. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a header configuration manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may identify a packet for transmission on the relay wireless communication link belonging to the a first bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a packet manager as described with reference to <FIG>.

At <NUM>, the UE <NUM> or base station <NUM> may configure, according to the bearer mapping configuration, a header of the packet that is processed by a relay wireless device to include an identifier, the identifier conveying information associated with the first bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a header configuration manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may transmit the packet comprising the header on the relay wireless communication link. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a relay link communication manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may establish a mapping between a plurality of identifiers and a corresponding plurality of virtual radio bearers, wherein each virtual radio bearer corresponds to a bearer of the plurality of bearers. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a mapping manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may select an identifier associated with a first virtual radio bearer, wherein the first virtual radio bearer corresponds to the first bearer and the relay wireless communication corresponds to a radio bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by an identification manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may configure, according to the bearer mapping configuration, a header of the packet that is processed by a relay wireless device to include an identifier, the identifier conveying information associated with the first bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a header configuration manager as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> for QoS support for L2 based D2D relay in accordance with various aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a QoS support manager as described with reference to <FIG>. In some examples, a UE <NUM> or base station <NUM> may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE <NUM> or base station <NUM> may perform aspects of the functions described below using special-purpose hardware.

At <NUM> the UE <NUM> or base station <NUM> may receive a packet on a first bearer of the relay wireless communication link, the packet comprising a header that is processed by a relay wireless device and is configured, according to the radio bearer mapping configuration, to include an identifier that conveys information associated with the first bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a packet manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may determine that the identifier is associated with a first virtual radio bearer, wherein the first virtual radio bearer corresponds to the first bearer and the relay wireless communication link corresponds to a radio bearer. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by an identification manager as described with reference to <FIG>.

At <NUM> the UE <NUM> or base station <NUM> may identify the first bearer based at least in part on the identifier. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by an identification manager as described with reference to <FIG>.

In some examples, aspects from two or more of the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> described with reference to <FIG> may be combined. It should be noted that the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> are just example implementations, and that the operations of the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may be rearranged or otherwise modified such that other implementations are possible.

Techniques described herein may be used for various wireless communications systems such as CDMA, TDMA, FDMA, OFDMA, single carrier frequency division multiple access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably.

An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications system (UMTS). 3GPP LTE and LTE-A are releases of Universal Mobile Telecommunications System (UMTS) that use E-UTRA. While aspects an LTE or an NR system may be described for purposes of example, and LTE or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE or NR applications.

In LTE/LTE-A networks, including such networks described herein, the term eNB may be generally used to describe the base stations. The wireless communications system or systems described herein may include a heterogeneous LTE/LTE-A or NR network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB, gNB, or base station may provide communication coverage for a macro cell, a small cell, or other types of cell. The term "cell" may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

Base stations may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNB, next generation NodeB (gNB), Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area for a base station may be divided into sectors making up only a portion of the coverage area. The wireless communications system or systems described herein may include base stations of different types (e.g., macro or small cell base stations). The UEs described herein may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.

A gNB for a macro cell may be referred to as a macro gNB. A gNB for a small cell may be referred to as a small cell gNB, a pico gNB, a femto gNB, or a home gNB. A gNB may support one or multiple (e.g., two, three, four, and the like) cells (e.g., component carriers). A UE may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, relay base stations, and the like.

Each communication link described herein-including, for example, wireless communication systems <NUM> and <NUM> of <FIG> and <FIG>-may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies).

In some instances, well-known structures and devices are shown in diagram form in order to avoid obscuring the concepts of the described examples.

Due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these.

Claim 1:
A method (<NUM>) for wireless communication, the method comprising:
communicating (<NUM>) via a relay wireless communication link, the communicating comprising communications using a plurality of bearers;
identifying that a packet belongs to a first bearer, the first bearer being associated with a quality of service, QoS, parameter set;
configuring (<NUM>) a header of the packet for transmission on the relay wireless communication link that is processed by a relay wireless device to convey an indication of the QoS parameter set, wherein the header is further configured to convey an indication of an allocation and retention policy, ARP, of the first bearer; and
transmitting (<NUM>) the packet comprising the configured header on the relay wireless communication link according to the QoS parameter set.