Patent Description:
Aspects of wireless communication may comprise direct communication between devices, such as in vehicle-to-everything (V2X) and/or other device-to-device (D2D) communication. There exists a need for further improvements in V2X and/or other D2D technology.

<NPL>" discusses the NR QoS framework, and the RANI aspects of QoS management. It also identifies where the likely RANI impacts of changes to the QoS framework in NR may be expected. <NPL>" discusses how to support QoS management in NR V2X.

In accordance with the present invention, there is provided a method for wireless communication as set out in claim <NUM> and an apparatus for wireless communication as set out in claim <NUM> Embodiments are defined in the dependent claims.

Accordingly, in one or more examples, the functions described may be implemented in hardware, software, or any combination thereof.

In some aspects, a UE <NUM> in the communication system may comprise a QoS Flow management component <NUM> configured to assign at least one QoS flow ID for the data traffic using at least one of radio resources information and/or traffic type information for the data traffic, wherein data packets for transmission with different radio resources are assigned different QoS flow IDs. The QoS flow management component <NUM> may assign the QoS flow ID(s) further based on additional considerations, as described herein. Similar to the illustration for UE <NUM>, an RSU <NUM> or other device communicating based on D2D/V2D/PC5 etc., may comprise a similar QoS Flow management component <NUM>.

Some wireless communication networks may include vehicle-based communication devices that can communicate based on vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from the vehicle-based communication device to road infrastructure nodes such as a Road Side Unit (RSU)), vehicle-to-pedestrian (V2P), vehicle-to-network (V2N) (e.g., from the vehicle-based communication device to one or more network nodes, such as a base station), cellular vehicle-to-everything (CV2X), enhanced vehicle-to-everything (eV2X)), etc., which can be collectively referred to herein as vehicle-to-everything (V2X) communication. Referring again to <FIG>, in certain aspects, a UE <NUM>, e.g., a transmitting Vehicle User Equipment (VUE) or other UE, may be configured to transmit messages directly to another UE <NUM>. The communication may be based on V2X or other D2D communication, such as Proximity Services (ProSe), etc. Communication based on V2X and/or other D2D communication may also be transmitted and received by other transmitting and receiving devices, such as Road Side Unit (RSU) <NUM>, etc. Aspects of the communication may be based on PC5 or sidelink communication e.g., as described in connection with the example in <FIG>. Although the following description may provide examples for V2X/D2D communication in connection with <NUM> NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

Some UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>.

The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations <NUM>, UEs <NUM>, an Evolved Packet Core (EPC) <NUM>, and a Core Network (e.g., 5GC) <NUM>.

The base stations <NUM> configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., S1 interface). The base stations <NUM> configured for NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with Core Network <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or Core Network <NUM>) with each other over backhaul links <NUM> (e.g., X2 interface).

A network that includes both small cell and macro cells may be known as a heterogeneous network. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

A base station <NUM>, whether a small cell <NUM>' or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or other type of base station. Some base stations <NUM>, such as a gNB, may operate in a traditional sub <NUM> spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE <NUM>. When the gNB operates in mmW or near mmW frequencies, the gNB may be referred to as an mmW base station. The mmW base station, e.g., base station <NUM>, may utilize beamforming <NUM> with the UE <NUM> to compensate for the extremely high path loss and short range.

Devices may use beamforming to transmit and receive communication. For example, <FIG> illustrates that a base station <NUM> may transmit a beamformed signal to the UE <NUM> in one or more transmit directions <NUM>'. Although beamformed signals are illustrated between UE <NUM> and base station <NUM>/<NUM>, aspects of beamforming may similarly may be applied by UE <NUM> or RSU <NUM> to communicate with another UE <NUM> or RSU <NUM>, such as based on V2X, V2V, or D2D communication.

The Core Network <NUM> may include an Access and Mobility Management Function (AMF) <NUM>, other AMFs <NUM>, a Session Management Function (SMF) <NUM>, and a User Plane Function (UPF) <NUM>. The AMF <NUM> is the control node that processes the signaling between the UEs <NUM> and the Core Network <NUM>. Generally, the SMF <NUM> provides QoS flow and session management.

The base station <NUM> provides an access point to the EPC <NUM> or Core Network <NUM> for a UE <NUM>.

<FIG> illustrates example diagrams <NUM> and <NUM> illustrating examples slot structures that may be used for wireless communication between UE <NUM> and UE <NUM>', e.g., for sidelink communication. The slot structure may be within a <NUM>/NR frame structure. Although the following description may be focused on 5GNR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. This is merely one example, and other wireless communication technologies may have a different frame structure and/or different channels. Diagram <NUM> illustrates a single slot transmission, e.g., which may correspond to a <NUM> transmission time interval (TTI). Diagram <NUM> illustrates an example two-slot aggregation, e.g., an aggregation of two <NUM> TTIs. Diagram <NUM> illustrates a single RB, whereas diagram <NUM> illustrates N RBs. In diagram <NUM>, <NUM> RBs being used for control is merely one example. The number of RBs may differ.

Each time slot may include a resource block (RB) (also referred to as physical RBs (PRBs)) that extends <NUM> consecutive subcarriers. As illustrated in <FIG>, some of the REs may comprise control information, e.g., along with demodulation RS (DMRS). <FIG> also illustrates that symbol(s) may comprise CSI-RS. The symbols in <FIG> that are indicated for DMRS or CSI-RS indicate that the symbol comprises DMRS or CSI-RS REs. Such symbols may also comprise REs that include data. For example, if a number of ports for DMRS or CSI-RS is <NUM> and a comb-<NUM> pattern is used for DMRS/CSI-RS, then half of the REs may comprise the RS and the other half of the REs may comprise data. A CSI-RS resource may start at any symbol of a slot, and may occupy <NUM>, <NUM>, or <NUM> symbols depending on a configured number of ports. CSI-RS can be periodic, semi-persistent, or aperiodic (e.g., based on DCI triggering). For time/frequency tracking, CSI-RS may be either periodic or aperiodic. CSI-RS may be transmitted in busts of two or four symbols that are spread across one or two slots. The control information may comprise Sidelink Control Information (SCI). At least one symbol may be used for feedback, as described herein. A symbol prior to and/or after the feedback may be used for turnaround between reception of data and transmission of the feedback. Although symbol <NUM> is illustrated for data, it may instead be a gap symbol to enable turnaround for feedback in symbol <NUM>. Another symbol, e.g., at the end of the slot may be used as a gap. The gap enables a device to switch from operating as a transmitting device to prepare to operate as a receiving device, e.g., in the following slot. Data may be transmitted in the remaining REs, as illustrated. The data may comprise the data message described herein. The position of any of the SCI, feedback, and LBT symbols may be different than the example illustrated in <FIG>. Multiple slots may be aggregated together. <FIG> also illustrates an example aggregation of two slot. The aggregated number of slots may also be larger than two. When slots are aggregated, the symbols used for feedback and/or a gap symbol may be different that for a single slot. While feedback is not illustrated for the aggregated example, symbol(s) in a multiple slot aggregation may also be allocated for feedback, as illustrated in the one slot example.

<FIG> is a block diagram <NUM> of a first wireless communication device <NUM> in communication with a second wireless communication device <NUM>, e.g., via V2X or other D2D communication. The device <NUM> may comprise a transmitting device communicating with a receiving device, e.g., device <NUM>, via V2X or other D2D communication. The communication may be based, e.g., on sidelink. The device <NUM> may comprise a UE, an RSU, etc. The device <NUM> may comprise a UE, an RSU, etc. Packets may be provided to a controller/processor <NUM> that implements layer <NUM> and layer <NUM> functionality.

At least one of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM> of device <NUM> or the TX <NUM>, the RX processor <NUM>, or the controller/processor <NUM> may be configured to perform aspects described in connection with <NUM> of <FIG>.

<FIG> illustrates an example <NUM> of wireless communication between devices based on V2X or other D2D communication. The communication may be based on a slot structure comprising aspects described in connection with <FIG>. For example, transmitting UE <NUM> may transmit a transmission <NUM>, e.g., comprising a control channel and/or a corresponding data channel, that may be received by receiving UEs <NUM>, <NUM>, <NUM>. A control channel may include information for decoding a data channel and may also be used by receiving device to avoid interference by refraining from transmitting on the occupied resources during a data transmission. The number of TTIs, as well as the RBs that will be occupied by the data transmission, may be indicated in a control message from the transmitting device. The UEs <NUM>, <NUM>, <NUM>, <NUM> may each be capable of operating as a transmitting device in addition to operating as a receiving device. Thus, UEs <NUM>, <NUM> are illustrated as transmitting a transmissions <NUM>, <NUM>. The transmissions <NUM>, <NUM>, <NUM>, <NUM> may be broadcast or multicast to nearby devices. For example, UE <NUM> may transmit communication intended for receipt by other UEs within a range <NUM> of UE <NUM>. Additionally/alternatively, RSU <NUM> may receive communication from and/or transmit communication to UEs <NUM>, <NUM>, <NUM>, <NUM>.

UE <NUM>, <NUM>, <NUM>, <NUM> or RSU <NUM> may comprise a QoS flow management component, similar to <NUM> described in connection with <FIG>.

A V2X QoS flow management model (e.g., for enhanced V2X (eV2X)) may support different QoS flow IDs for different services. Services may be identified by a service type ID such as a provider service ID (PSID) or an intelligent transportation system application identifier (ITS-AID). <FIG> illustrates an example <NUM> showing data traffic processed by a user plane protocol stack for two different applications V2X App _1 and V2X App _2. V2X App_1 may generate communication associated with a first service type ID, e.g., PSID_1, and a second service type ID, e.g., PSID_2. V2X App_2 may generate communication associated with the second service type ID, e.g., PSID_2, and a third service type ID, e.g., PSID_3. <FIG> also illustrates an example control plane protocol stack <NUM>. The control plane protocol stack generates control signaling messages, e.g. PC5 Signaling message, or PC5 RRC messages, to manage the link between UEs for unicast type of communication.

Communication associated with PSID_1, PSID_2, and PSID_3 may be separated into different QoS flows. A per flow QoS management may be applied to broadcast communication, groupcast communication, and/or unicast communication. For example, communication generated by each of the services types may be assigned a separate QoS flow ID. As illustrated in <FIG>, data traffic from an application layer, e.g., V2X App_1 or V2X App_2, may be processed by a V2X layer based on QoS rules to be separated into different QoS flows. Each QoS flow may have a different PC5 QoS flow ID (PFI) and corresponding QoS parameters. The QoS parameters associated with a PFI may include any of a PC5 5QI (PQI), a range, bit rates, etc. Thus, the PFI could be different than the PQI, which may be one parameter associated with an assigned PFI. A QoS flow configuration may be configured by V2X layer <NUM> to the AS layer <NUM> (e.g., to RRC, MAC, and/or physical layer(s)) prior to processing data traffic from the application layer. An access stratum (AS) layer may comprise a PDCP layer, an RLC layer, a MAC layer, and a PHY layer, as illustrated in example, <NUM>. <FIG> illustrates a AS layer protocol stack for LTE and another protocol stack for NR. The protocol stack for NR is illustrated with an additional Service Data Adaptation Protocol (SDAP) layer. In the control plane example <NUM>, the AS layer <NUM> may comprise an additional PC5 RRC layer for NR communication. The AS layer may determine a mapping of the QoS flows to a radio bearer, e.g., to a PC5 radio bearer. For example, the SDAP may determine the mapping for the QoS flows. The radio bearer mapping may be performed based on the PFI by the SDAP layer. The radio bearer mapping may be determined by the UE, e.g. the PC5 RRC layer, and informed to the SDAP layer. The radio bearer mapping may be configured, e.g., for a broadcast or groupcast. The radio bearer may be negotiated between UEs, e.g., for a unicast or groupcast.

For unicast communication, different services may be supported over the same layer <NUM> link between two UEs. As well, communication associated with different services, e.g., with a different PSID/ITS-AID, may be allocated with different frequencies. For example, regulators may assign dedicated frequency resources for certain services. As an example, <NUM> may be assigned for safety services, <NUM> or <NUM>+<NUM> or Frequency Range <NUM> (FR2) may be assigned for advanced services, etc. A V2X UE may be configured with frequency band allocation information, e.g., at the V2X layer <NUM>. The UE may be preconfigured with such information or may be provisioned with the information from the network, e.g. via OMA-DM from the V2X Control Function, or via control plane signaling (NAS signaling) from the PCF. The frequency band allocation information may specify the frequency band(s) that a particular PSID is allowed to use, for example. At times, there may be a conflict between configurations using different frequency resources for different services and a configuration that supports the transmission of different services over a same layer <NUM> link, e.g., when a QoS flow comprises multiple services. If the services contained in the QoS flow are associated with different frequency resources, there may be a problem mapping the QoS flow to radio resources, especially if the QoS rules for filtering data traffic into QoS flows is based on QoS requirements without considering frequency band information. Multiple services (with different PSIDs/ITS-AIDs) may be placed in the same QoS flow based on similar QoS requirements for the services. For example, a PFI may be set to be equal to PQI, i.e. all packets sharing the same PQI is placed into the same QoS flow. This could lead to multiple services being grouped into a same QoS flow without differentiation for the different services. Thus, the different services would be mapped to the same radio bearer. Furthermore, PC5 communication, e.g., NR PC5 communication, may be limited to supporting a single frequency carrier depending on configuration. In that case, the different services in the same radio bearer will be sent over the same frequency band, which may conflict with the specific frequency bands assigned for different services.

Aspects presented herein enable QoS flow management that applies QoS rules based on additional information and parameters. A filter applied at the V2X layer for QoS flow management of data traffic from the application layer may assign PFI(s) based on PQI, range, and any combination of frequency band information, data type, communication mode, destination ID, service ID, IP packet filters, or QoS requirements from the application layer. PC5 QoS flow parameters may comprise a guaranteed bit rate (GBR), a guaranteed flow bit rate (GFBR), a maximum flow bit rate (MFBR), and/or a PC5 link aggregated maximum bit rate (PC5 link AMBR).

For example, a different PFI may be assigned based on frequency band information, e.g., if provided for data traffic associated with a particular frequency band. Thus, data traffic associated with different frequency bands may be assigned different PFIs. A different PFI may be assigned based on data type, e.g., whether the data traffic is IP data traffic or non-IP data traffic. A PFI may be assigned based on a communication mode, e.g., whether the data traffic is broadcast data traffic, groupcast data traffic, or unicast data traffic. A PFI may be assigned based on a service type ID, e.g., based on a PSID or an ITS-AID. Thus, data traffic for different service types may be assigned different PFIs. A PFI may be assigned based on destination for the data traffic. For example, a destination ID for broadcast traffic may comprise a broadcast L2 ID. A destination ID for groupcast traffic may comprise a group ID or a translated groupcast L2 ID. A destination ID for unicast data traffic may comprise a target UE application layer ID, a Link ID, or a translated unicast L2 ID. A PFI may be assigned based on QoS requirements received at the V2X layer from the application layer. As an example, the QoS requirements may comprise any of a packet delay budget (PDB) for the data traffic, packet error rate (PER) for the data traffic, a range for the data traffic, etc. A PFI may be assigned based on IP packet filter information, e.g., if provided for the data traffic. The V2X layer may use any of the example parameters/information for the data traffic to determine whether to group the data traffic into an existing QoS flow or to assign a new PFI.

At least some of the information used to determine the PFI may be passed from the V2X layer to the AS layer. The information may be used at the AS layer to determine whether data traffic for different PFIs can be combined when mapping to radio bearer(s). As an example, the data type information for the data traffic may be passed from the V2X layer to the AS layer along with the assigned PFI. The AS layer may use the data type information so that the AS layer does not combine IP data traffic and non-IP data traffic into the same radio bearer(s). As another example, the frequency information may be passed to the AS layer, where it can be used in mapping QoS flows to the radio bearer(s). The AS layer may use the frequency information to avoid combining data traffic associated with different frequency bands when mapping the data traffic to radio bearer(s). The AS layer may also use the frequency information for the data traffic to map the QoS flow to the correct dedicated radio bearer (DRB), e.g., to a PC5 radio bearer that does not have a conflict with the data traffic comprised in the QoS.

Thus, based on the new QoS flow management aspects presented here, the V2X layer may filter data traffic from the application layer based on frequencies associated with the related applications and/or a data type so that services with conflicting frequencies and/or data types can be allocated to different QoS flows.

<FIG> illustrates a diagram <NUM> of an example of filtering data traffic from an application layer and mapping to radio bearers. As illustrated, multiple data packets <NUM> may be received at the V2X layer from an application layer, e.g., from various applications of a UE. The V2X layer may filter the data traffic and assign PFIs to the filtered data traffic. For example, <FIG> illustrates the data traffic being filtered into/assigned four different PFIs 604a, 604b, 604c, 604d. Each of PFIs 604a, 604b, 604c, 604d has a different PFI ID. Thus, the data traffic including multiple data packets <NUM> from the application layer would be separated into QoS flows comprising V2X data packets marked with the same PFI. The V2X layer may incorporate frequency band mapping into the QoS rules generation/negotiation. Thus, services with different frequency bands can be given different QoS flow IDs. Additionally or alternatively, the QoS rules may be based on a data type, a communication mode, a destination ID, a service ID, IP packet filter(s), or QoS requirements from the application layer. As illustrated at 606a, 606b, the data packets may be filtered for/remain separated according to the type of data. Thus, IP data and non-IP data may be assigned to different PFIs. The communication type information may be passed to the AS layer. The AS layer may map the QoS flows to AS layer resources. As part of the mapping, the AS layer may map the data traffic to radio bearers based on the PFI(s). The AS layer may combine data traffic as part of the mapping. For example, <FIG> illustrates that data traffic for PFI 604c and 604d are combined by the AS layer into QoS flow 608c. Data traffic marked with PFI 604b is illustrated as being mapped separately as QoS flow 608b. Similarly, PFI 604a is illustrated as being mapped separately as QoS flow 608a. While QoS flows 608b and 608c are mapped to separate radio bearers, the AS layer is illustrated as mapping the two QoS flows to a shared L2 link 610a. The different radio bearers in L2 link <NUM> (610a) may comprise different frequency bands from each other. QoS flow 608a is mapped to a separate radio bearer and a separate L2 link <NUM> (610b). As an example, the AS layer may map IP data traffic to a separate L2 link than non-IP data traffic. As well, the AS layer may determine to map data traffic for different QoS flows to different radio bearers within a shared L2 link based on whether an assigned frequency band for the QoS flows will allow for the same L2 link. The AS layer, e.g., SDAP or RRC layer may determine a mapping between a QoS flow and a radio bearer. The frequency band information may be added to QoS flow parameters so that the AS layer will determine the mapping accordingly. As an example, the AS layer may determine whether there are overlapping bands associated with the QoS flows, and may map the QoS flows to a shared radio bearer or a shared link when there are overlapping frequency bands. When the AS determines the QoS flow information for a QoS flow associated with a PFI, the AS may determine if multiple QoS flows can be merged into the same radio bearer based on frequency band information for the QoS flow.

As an example for a broadcast or connection-less groupcast transmission, a V2X layer may apply preconfigured QoS rules to filter data traffic from the application layer for transmission, e.g., from a UE. If there is a service type to QoS mapping, different QoS rules may be generated for each QoS level. A service type may be based on a PSID/ITS-AID. A first example QoS rule may be:
<MAT>.

Thus, PFI of <NUM> would be applied to data traffic for services PSID_1 and PSID <NUM> that has a PQI of <NUM>. Data traffic for a different PSID and/or different PQI may have a PFI assigned according to a different rule.

The rule may further be based on a range, e.g.,
<MAT>.

In this example, a PFI of <NUM> may be applied to the data traffic for services PSID_1 and PSID <NUM> that has a PQI of <NUM> and an intended range of reception of <NUM>.

The V2X layer may determine whether the service type (e.g., PSID_1 and/or PSID_2 has a frequency mapping, e.g., an assigned radio bearer. As an example, if PSID_1 and PSID_2 have different frequency bands, the QoS rule may be split into the following example QoS rules:
<MAT>
<MAT>.

The QoS rules may also be applied without the range parameter. The Application layer may use APIs to request specific QoS level(s) for a particular service type, e.g. to request an increased priority for a particular PSID. In this example, the V2X layer may determine if the QoS Rule is to be updated, or if a new QoS rule is to be generated.

At the AS layer, each QoS flow may be given a different virtual radio bearer, e.g., there may be different queues if there are different frequency bands.

As an example for managed groupcast V2X communication, there may be QoS rules created based on the group(s) with which the UE communicates. A set of QoS rules may be generated for each group based on application layer requirement(s) of the related service types. For example, the application layer may call an API to provide to the V2X layer any of a group ID, a service type (e.g., PSID/ITS-AID), or associated QoS requirements for each service type. If no QoS requirements are provided, the UE may use a preconfigured QoS level for the PSID/ITS-AID or a default QoS level for unknown PSID(s)/ITS-AID(s). An example QoS rule may be:
<MAT>.

Thus, a first PFI may be applied to data traffic at the V2X layer that is associated with Group ID "Group ID_1" for services PSID_1 and PSID_2 and having a PQI of <NUM>. Data traffic for other groups (i.e., having a different Group ID), from other services, or having a different QoS parameter may have a different PFI applied at the V2X layer. The Group ID may comprise a mapped L2 ID that is made known to the application that generates the data traffic. After considering the group ID, the V2X layer may then check the service ID to determine whether there is a frequency mapping to a particular frequency, e.g., a dedicated radio bearer. If there are different frequency bands, multiple PFI rules may be applied. As an example,
<MAT> and
<MAT>.

Thus, data traffic intended for the group of UEs identified by Group ID_1 for service PSID_1 and having QoS parameter PQI=<NUM>, a PFI <NUM> may be applied to data traffic for frequency band <NUM>, and PFI <NUM> may be applied to data traffic for frequency band <NUM>. The AS layer may map this QoS flow to two different radio bearers, as the frequency bands are different, i.e., frequency band <NUM> and frequency band <NUM>.

As another example, unicast signaling may involve signaling between two UEs. The unicast communication may comprise managed unicast communication. The unicast communication may use a PC5_S protocol for negotiating QoS flow information. The V2X layer may make determinations regarding the QoS flow and QoS rules before the signaling, e.g., before transmitting data traffic. The QoS flow information may be passed down from the V2X layer after confirmation of a link set up by the peer UE that will receive the data traffic.

For unicast, a link ID may be generated when a layer <NUM> link is determined to be established with the target UE. This Link ID may be local and may stay constant during the lifetime of the unicast link (whereas the L2 IDs may change). The Link ID may be passed back to the application. Then, the application may use this Link ID when passing the data packets down to V2X layer. The QoS rule filter may use the link ID as a parameter for filtering data traffic at the V2X layer. The link ID may be applied as one of the filter fields when determining the QoS Flow such that packets to different Link IDs are separated in to different QoS flows. Additionally, the AS might not merge QoS flows of different Link IDs into the same radio bearer. Thus, the link ID information may be passed to the AS layer. Thus, the Link ID may be also included as part of the QoS flow parameters. The following is an example QoS rule including Link ID: <MAT>.

Thus, a particular PFI (e.g. <NUM>) may be applied for unicast data traffic associated with Link ID <NUM> for service PSID_1 and PQI=<NUM>. As described for broadcast and groupcast communication, the rule may optionally be further based on frequency band so that a different PFI rule is applied for Link ID <NUM> for service PSID_1 and PQI=<NUM> and a first frequency band than for Link ID <NUM> for service PSID_1 and PQI=<NUM> and frequency band <NUM>.

With the same Link ID (i.e. between the same pair of UEs), there could be multiple QoS flows that mapped to the different frequency bands, as long as the QoS flows in the same radio bearers are using the same frequency bands.

The AS layer (e.g. RRC, or SDAP) may determine the QoS flow to radio bearer mapping taking both Link ID, and frequency into consideration.

If the Application Layer does not use the Link ID, it may still indicate the target UE Application Layer ID (e.g. a Station ID or "StationID") when passing the packet down to the V2X layer. In this example, the filter, or QoS rule applied at the V2X layer, may be based on an Application Layer ID. The V2X layer may convert the Application Layer ID into a link ID, or l2 ID when passing the QoS Flow info down to the AS layer. An example QoS rule may include: <MAT>.

For IP traffic, the Service Type info (PSID/ITS-AID) might not be known to the V2X layer. The application layer may use IP sockets to deliver the packets down to V2X layer. In this example, several potential filtering rules may be used to identify the frequency bands information.

As a first example, the application Layer may set the service type information in the flow label of the IPv6 header (or by extending that with a TC field) for the data traffic. As a flow label field may comprise <NUM> bits, (with TC field, <NUM> bits), the number of bits may represent a certain range of service types.

As a second example, the application layer may directly indicate the frequency band information to the V2X layer. In order to enable the application layer to indicate the frequency band information, the V2X layer may expose the frequency band mapping configuration to Application layer.

As a third example, the application layer may use an IPv6 extension header to identify the Service Type. The PC5 QoS Rule may be able to read such extension header.

As a fourth example, a source IP prefix may be used to indicate the service type to the V2X layer. The V2X layer may replace the source IP prefix with the actual IP prefix (e.g. link local IP prefix) before passing such information down to a lower layer. This example may involve IP socket support, e.g., the application layer may indicate the source address when creating the IP socket, e.g. by calling the bind function to perform a binding of the IP prefix with the data traffic.

In another example, each service ID may map to an individual QoS flows or QoS rules. In this example, each QoS flow would service one service ID (e.g., PSID/ITS-AID). Thus, a rule may be indicated, e.g., as PFI !=PQI. A larger PFI number space may be used to accommodate the larger number of QoS flows. In this example, the AS layer (e.g. SDAP, or RRC) may determine, based on the frequency band info associated with the QoS flow, whether to merge the QoS Flows into the same radio bearer when mapping QoS flows to radio bearers. For example, if two QoS Flows have the same Frequency band information and the same QoS parameters (e.g. PQI), the two QoS flows can be merged.

<FIG> is a flowchart <NUM> of a method of wireless communication. The method may be performed by a UE (e.g., the UE <NUM>, the device <NUM>, the apparatus <NUM>/<NUM>'; the processing system <NUM>, which may include memory <NUM>, <NUM> and which may be an entire UE or a component of a UE, such as TX processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM> or TX processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>). Optional aspects are illustrated with a dashed line. The method may enable a UE to more effectively perform QoS flow management.

At <NUM>, the UE receives data traffic from an application layer for transmission in device-to-device communication, such as V2X communication. For example, <NUM> may be performed by data component <NUM> from <FIG>. <FIG> and <FIG> illustrate examples of data traffic from the application layer that may be received at a V2X layer of a UE.

At <NUM>, the UE assigns at least one Quality of Service (QoS) flow identifier (ID) for the data traffic based on radio resources information for the data traffic. The QoS flow identifier may be assigned based on both radio resources information and traffic type information. Data packets for transmission with different radio resources are assigned different QoS flow IDs. The device-to-device communication comprises V2X communication and the at least one QoS flow ID may be assigned at a V2X layer based on the radio resources information for the data traffic. For example, <NUM> may be performed by QoS assignment component <NUM> from <FIG>. In one aspect, the radio resources information may comprise a frequency band to be used for the transmission of the data packets, e.g., such as a DRB.

At <NUM>, after assigning the QoS flow ID, the UE may pass the radio resources information for the data traffic associated with the QoS flow ID to a lower layer. At <NUM>, the UE may use the radio resources information at the lower layer to determine a mapping of the data traffic associated with the QoS flow ID to at least one radio bearer. For example, <NUM> may be performed by radio resources information component <NUM> from <FIG>, and <NUM> may be performed by radio bearer mapping component <NUM> from <FIG>.

In one aspect, the radio resources information may be determined based on a mapping of service type information received from the application layer to the radio resources information. The mapping of service type information to radio resources information may be configured at a user equipment (UE). In certain aspects, the service type information for the data traffic may be indicated from the application layer based on a header for the data traffic. In other aspects, the service type information for the data traffic may be indicated from the application layer based on a header extension for the data traffic, where the header extension comprises one of a flow label or an Internet Protocol (IP) version <NUM> (IPv6) extension header. In further aspects, the service type information for the data traffic may be indicated from the application layer based on a source identifier. In additional aspects, the radio resources information for the data traffic is indicated from the application layer based on a frequency band indication for the data traffic.

In another aspect, the QoS flow ID may be assigned further based on a communication mode for the data traffic such that the data packets are assigned different QoS flow IDs based on the communication mode. The communication mode comprises one of broadcast communication, groupcast communication, and unicast communication.

In further aspects, the at least one QoS flow ID may be assigned further based on a destination ID for the data traffic such that the data packets with different destination IDs are assigned the different QoS flow IDs. In one aspect regarding the destination ID, the data traffic may be for broadcast communication and the destination ID may comprise a broadcast layer <NUM> (L2) ID.

In another aspect regarding the destination ID, the data traffic may be for groupcast communication, and the destination ID may comprise a group ID or a translated groupcast layer <NUM> (L2) ID.

In an additional aspect regarding the destination ID, the data traffic may be for unicast communication, and the destination ID may comprise one of a target UE application layer ID or a link ID.

In another aspect, the at least one QoS flow ID may be assigned further based on one or more QoS requirements from the application layer for the data traffic such that the data packets with different QoS requirements from the application layer are assigned the different QoS flow IDs. The QoS requirements from the application layer may comprise at least one of a packet delay budget (PDB) for the data traffic, a packet error rate (PER) for the data traffic, or a range for the data traffic.

In a further aspect, the at least one QoS flow ID may be assigned further based on a service type ID for the data traffic such that the data packets with different service type IDs are assigned the different QoS flow IDs. The service type ID may comprise a PSID or an ITS-AID.

In some aspects, the at least one QoS flow ID may be assigned based on a one-to-one mapping between the service type ID and the QoS flow ID. Therefore, at <NUM>, the UE may determine, based on the radio resources information, whether to merge QoS flows having different QoS flow IDs into a same radio bearer at an access stratum layer. For example, <NUM> may be performed by radio bearer merging component <NUM> from <FIG>.

The at least one QoS flow ID may be assigned, at <NUM>, further based on traffic type information for the data traffic. For example, at <NUM>, the UE passes the traffic type information for the data traffic to a lower layer, and finally, at <NUM>, the UE uses the traffic type information at the lower layer to map the data traffic to at least one radio bearer. For example, <NUM> may be performed by traffic type information component <NUM> from <FIG>, and <NUM> may be performed by radio bearer mapping component <NUM> from <FIG>. Internet Protocol (IP) data packets and non-IP data packets are assigned different QoS flow IDs.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different means/components in an example apparatus <NUM>. The apparatus may be a UE or a component of a UE (e.g. the UE <NUM>, <NUM>, <NUM>). The apparatus <NUM> includes a reception component <NUM> that receives data traffic from one or more V2X applications <NUM> and device-to-device (e.g. V2X communications) from one or more other UEs <NUM>. The apparatus <NUM> includes a data component <NUM> that receives, via the reception component <NUM>, data traffic from an application layer for transmission in device-to-device communication. The apparatus <NUM> includes a QoS assignment component <NUM> that assigns at least one QoS flow ID for the data traffic based on resources information for the data traffic. The apparatus <NUM> includes a radio resources information component <NUM> that passes the radio resources information for the data traffic associated with the QoS flow ID to a lower layer, and a traffic type information component <NUM> that passes the traffic type information for the data traffic to a lower layer. The apparatus <NUM> includes a radio bearer mapping component <NUM> that uses the radio resources information sent from the radio resources information component <NUM> and/or the traffic type information sent from the traffic type information component <NUM> at the lower layer to determine a mapping of the data traffic associated with the QoS flow ID to at least one radio bearer. The apparatus <NUM> includes a radio bearer merging component <NUM> that determines, based on the radio resources information sent from the radio resources information component <NUM>, whether to merge QoS flows having different QoS flow IDs into a same radio bearer at an access stratum layer. The apparatus <NUM> further includes a transmission component <NUM> that sends D2D communications and data traffic to the one or more other UEs <NUM> via the radio bearers mapped by the radio bearer mapping component <NUM> or merged by the radio bearer merging component <NUM>.

The apparatus <NUM> may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of <FIG>. As such, each block in the aforementioned flowchart of <FIG> may be performed by a component (e.g. <NUM>-<NUM>) and the apparatus <NUM> may include one or more of those components.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus <NUM>' employing a processing system <NUM>. The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors and/or hardware components, represented by the processor <NUM>, the components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. The components may be software components running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the device <NUM> or the device <NUM> and may include the memory <NUM>, <NUM> and/or at least one of the TX processor <NUM>, <NUM>, the RX processor <NUM>, <NUM>, and the controller/processor <NUM>, <NUM>. Alternatively, the processing system <NUM> may be the entire UE (e.g., see device <NUM> or <NUM> of <FIG>).

In one configuration, the apparatus <NUM>/<NUM>' for wireless communication includes means for receiving data traffic from an application layer for transmission in device-to-device communication, and means for assigning at least one QoS flow ID for the data traffic based on radio resources information for the data traffic, wherein data packets for transmission with different radio resources are assigned different QoS flow IDs. The apparatus <NUM>/<NUM>' may also include means for passing the radio resources information for the data traffic associated with the QoS flow ID to a lower layer, means for determining a mapping of the data traffic associated with the QoS flow ID to at least one radio bearer based on the radio resources information at the lower layer, means for passing the traffic type information for the data traffic to a lower layer, means for mapping the data traffic to at least one radio bearer based on the traffic type information at the lower layer to, and means for determining, based on the radio resources information, whether to merge QoS flows having different QoS flow IDs into a same radio bearer at an access stratum layer.

As described supra, the processing system <NUM> may include the TX processor <NUM>, <NUM>, the RX processor <NUM>, <NUM>, and the controller/processor <NUM>, <NUM>. As such, in one configuration, the aforementioned means may be the TX processor <NUM>, <NUM>, the RX processor <NUM>, <NUM>, and the controller/processor <NUM>, <NUM> configured to perform the functions recited by the aforementioned means.

Claim 1:
A method of wireless communication, comprising:
receiving (<NUM>) data traffic from an application layer for transmission in device-to-device communication;
assigning (<NUM>) at least one Quality of Service, QoS, flow identifier, ID, for the data traffic based on radio resources information for the data traffic, wherein the data traffic comprises data packets for transmission, and wherein data packets for transmission with different radio resources are assigned different QoS flow IDs and, wherein the radio resources information comprises a frequency band used for the transmission of the data packets;
passing (<NUM>) the radio resources information for the data traffic associated with the at least one QoS flow ID to a lower layer; and
determining (<NUM>) a mapping of the data traffic associated with the at least one QoS flow ID to at least one radio bearer based on the radio resources information at the lower layer.