Inter-device quality of service flow management

Abstract

A method, a computer-readable medium, and an apparatus for wireless communication are provided. The apparatus receives data traffic from an application layer and assigns at least one Quality of Service (QoS) flow identifier (ID) to the data traffic based on radio resource information of the data traffic. Data packets for transmission on different radio resources are assigned different QoS flow IDs.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 62 / 861,207, filed June 13, 2019, entitled "Device-to-Device Quality of Service Flow Management," and U.S. Patent Application No. 16 / 870,529, filed May 8, 2020, entitled "Device-to-Device Quality of Service Flow Management," which are hereby expressly incorporated by reference in their entireties.

[0002] The present disclosure relates generally to communication systems, and more particularly, to wireless communications including quality of service (QoS) flow management. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional, or even global scale. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Aspects of wireless communication may include direct communication between devices, such as vehicle-to-everything (V2X) communication and / or other device-to-device (D2D) communication. Further improvements are needed for V2X and / or other D2D technologies. These improvements may also be applicable to other multiple access technologies and telecommunications standards employing these technologies. Summary of the Invention [Means for solving the problem]

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication are provided. The apparatus receives data traffic from an application layer and assigns at least one QoS flow identifier (ID) to the data traffic based on radio resource information of the data traffic. Data packets for transmission on different radio resources are assigned different QoS flow IDs.

[0007] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed and the description is intended to include all such aspects and their equivalents. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a wireless communication system and access network. [Diagram 2] FIG. 1 illustrates an example of a side link slot structure. [Diagram 3] FIG. 1 illustrates an example of a first device and a second device engaged in wireless communication, for example, based on V2V, V2X, and / or other device-to-device communication. [Figure 4] FIG. 1 illustrates an example of V2X and / or other device-to-device communication. [Diagram 5] FIG. 1 illustrates an example protocol stack for wireless communications, including V2X communications. [Figure 6] FIG. 1 illustrates an example of QoS flow management for V2X communication. [Figure 7] 1 is a flow chart of a method of wireless communication. [Figure 8]FIG. 2 is a conceptual data flow diagram illustrating data flows between different means / components in an exemplary apparatus. [Figure 9] FIG. 1 illustrates an example of a hardware implementation for an apparatus utilizing a processing system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The detailed description, set forth below in connection with the accompanying drawings, describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0010] Several aspects of a telecommunications system are now presented with reference to various apparatus and methods that are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0011] As an example, an element or any portion of an element or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chips (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0012] Thus, in one or more examples, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the above types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0013] FIG. 1 illustrates an example of a wireless communication system and access network 100. In some aspects, a UE 104 in the communication system may include a QoS flow management component 198 configured to assign at least one QoS flow ID to data traffic using at least one of radio resource information and / or traffic type information of the data traffic, where data packets for transmission on different radio resources are assigned different QoS flow IDs. The QoS flow management component 198 may assign the QoS flow ID further based on additional considerations as described herein. Similar to the example of the UE 104, the RSU 107 or other devices communicating based on D2D / V2D / PC5, etc. may include a similar QoS flow management component 198.

[0014] 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 a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle-to-pedestrian (V2P), vehicle-to-network (V2N) (e.g., from a 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 may be collectively referred to herein as vehicle-to-everything (V2X) communications. Referring again to FIG. 1, in some aspects, a UE 104, e.g., a transmitting vehicular user equipment (VUE) or other UE, may be configured to transmit a message directly to another UE 104. The communication may be based on V2X or other D2D communication such as Proximity Services (ProSe). The communication based on V2X and / or other D2D communication may be transmitted and received by other transmitting / receiving devices such as Road Side Units (RSUs) 107. The communication aspects may be based on PC5 or sidelink communication, for example, as described with respect to the example of FIG. 2. The following description may provide an example of V2X / D2D communication related to 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0015] Several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0016] The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, and an evolved packet core (EPC) 160 and a core network (e.g., 5GC) 190. The base stations 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

[0017] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through a backhaul link 132 (e.g., an S1 interface). A base station 102 configured for NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 via a backhaul link 184. In addition to other functions, the base station 102 may perform one or more of the following functions: forwarding of user data, encryption and decryption of radio channels, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast services (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) via backhaul links 134 (e.g., X2 interfaces). The backhaul links 134 may be wired or wireless.

[0018] The base stations 102 may wirelessly communicate with the UE 104. Each of the base stations 102 may provide communication coverage in a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include a Home evolved Node B (eNB) (HeNB), which may serve a closed group called a Closed Subscriber Group (CSG). A communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102, and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use spectrum with bandwidth up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier allocated in carrier aggregation with up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. The carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0019] The wireless communication system may further include a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STA 152 / AP 150 may perform clear channel assessment (CCA) prior to communicating to determine if a channel is available.

[0020] The small cell 102' may operate in licensed and / or unlicensed frequency spectrums. When operating in the unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed frequency spectrum may extend coverage to and / or increase capacity of the access network. The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an eNB, a gNodeB (gNB), or other type of base station. Some base stations 180, such as gNBs, may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or sub-mmW frequencies when communicating with UEs 104. When a gNB operates in mmW or sub-mmW frequencies, it may be referred to as an mmW base station. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has a wavelength between 1 and 10 millimeters. Radio waves in that band may be referred to as millimeter waves. Sub-mmW may extend down to frequencies of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter wave. Communications using mmW / sub-mmW radio frequency bands have extremely high path loss and short distances. A mmW base station such as base station 180 may use beamforming 182 towards UE 104 to compensate for extremely high path loss and short distances.

[0021] A device may transmit and receive communications using beamforming. For example, FIG. 1 shows that the base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive a beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive a beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit direction and receive direction for the base station 180 may be the same or different. The transmit direction and receive direction for the UE 104 may be the same or different. Although a beamformed signal is shown between the UE 104 and the base station 102 / 180, the beamforming aspect may similarly be applied by the UE 104 or RSU 107 to communicate with another UE 104 or RSU 107 based on V2X, V2V, or D2D communications, etc.

[0022] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 is responsible for bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and activate MBMS bearer services in the Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions.The MBMS gateway 168 may be used to deliver MBMS traffic to base stations 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0023] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with an integrated data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the SMF 194 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.

[0024] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), enhanced service set (ESS), transmit / receive point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UEs 104. Examples of the UEs 104 include mobile phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, gaming consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small cooking appliances, health management devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0025] FIG. 2 illustrates example diagrams 200 and 210 illustrating example slot structures that may be used for wireless communication between UE 104 and UE 104′, for example, for sidelink communication. The slot structures may be within a 5G / NR frame structure. The following description may focus on 5G NR, but the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. This is only an example, and other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include minislots that may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols depending on the slot configuration. In slot configuration 0, each slot may include 14 symbols, and in slot configuration 1, each slot may include 7 symbols. Diagram 200 illustrates a single slot transmission, which may correspond, for example, to a 0.5 ms transmission time interval (TTI). Diagram 210 illustrates an exemplary two-slot aggregation, for example, an aggregation of two 0.5 ms TTIs. Diagram 200 illustrates a single RB, while diagram 210 illustrates N RBs. The 10 RBs used for control in diagram 210 are just an example. The number of RBs may vary.

[0026] A resource grid may be used to represent a frame structure. Each time slot may include a resource block (RB) (also called a physical RB (PRB)) spanning 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. As shown in FIG. 2, some of the REs may include control information, e.g., along with demodulation RS (DMRS). FIG. 2 also shows that a symbol may include a CSI-RS. The symbols in FIG. 2 shown for DMRS or CSI-RS indicate that the symbol includes a DMRS or CSI-RS RE. Such a symbol may also include an RE that includes data. For example, if the number of ports for DMRS or CSI-RS is 1 and a comb 2 pattern is used for DMRS / CSI-RS, half of the REs may include RS and the other half of the REs may include data. A CSI-RS resource may start in any symbol of a slot and occupy one, two, or four symbols depending on the 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 can be either periodic or aperiodic. CSI-RS may be transmitted in bursts of two or four symbols spread across one or two slots. The control information may include sidelink control information (SCI). As described herein, at least one symbol may be used for feedback. Symbols before and / or after the feedback may be used for turnaround between receiving data and transmitting feedback. Symbol 12 is shown for data, but may instead be a gap symbol to allow for turnaround for feedback in symbol 13. For example, another symbol at the end of the slot may be used as a gap. The gap allows a device to switch from operating as a transmitting device, for example, to prepare to operate as a receiving device in the next slot. Data may be transmitted in the remaining REs as shown.The data may include a data message as described herein. The location of any of the SCI symbols, feedback symbols, and LBT symbols may differ from the example shown in FIG. 2. Multiple slots may be aggregated together. FIG. 2 also shows an example aggregation of two slots. The aggregated number of slots may be greater than two. When slots are aggregated, the symbols used for feedback and / or gap symbols may differ from those for a single slot. Although feedback is not shown in the aggregated example, symbols in the aggregation of multiple slots may also be allocated for feedback, as shown in the one slot example.

[0027] 3 is a block diagram 300 of a first wireless communication device 310 communicating with a second wireless communication device 350, e.g., via V2X or other D2D communication. The device 310 may include a transmitting device that communicates with a receiving device, e.g., the device 350, via V2X or other D2D communication. The communication may be based on a sidelink, for example. The device 310 may include a UE, an RSU, etc. The device 350 may include a UE, an RSU, etc. The packets may be provided to a controller / processor 375 that implements Layer 3 and Layer 2 functions. Layer 3 includes a Radio Resource Control (RRC) layer, and Layer 2 includes a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer.

[0028] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 processes mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-ary quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the device 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

[0029] In the device 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions related to various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the device 350. Multiple spatial streams may be combined by the RX processor 356 into a single OFDM symbol stream if destined for the device 350. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the device 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the device 310 on the physical channel. The data and control signals are then provided to a controller / processor 359, which performs Layer 3 and Layer 2 functions.

[0030] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. The controller / processor 359 may provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0031] Similar to the functions described with respect to transmission by the device 310, the controller / processor 359 may provide RRC layer functions related to system information (e.g., MIBs, SIBs) collection, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto the TB, demultiplexing of MAC SDUs from the TB, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0032] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the device 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0033] Transmissions are processed in device 310 in a similar manner as described with respect to the receiver functions in device 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers the information modulated onto an RF carrier and provides the information to a RX processor 370.

[0034] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. The controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0035] At least one of the TX processor 368, RX processor 356, or controller / processor 359 of the device 350, or the TX processor 316, RX processor 370, or controller / processor 375 may be configured to perform the aspects described with respect to 198 of FIG.

[0036] FIG. 4 illustrates an example 400 of wireless communication between devices based on V2X or other D2D communication. The communication may be based on a slot structure including aspects described with respect to FIG. 2. For example, a transmitting UE 402 may transmit a transmission 414 including, for example, a control channel and / or a corresponding data channel, which may be received by a receiving UE 404, 406, 408. The control channel may include information for decoding the data channel and may be used by the receiving device to avoid interference by refraining from transmitting on resources occupied during the data transmission. The number of TTIs, as well as the RBs occupied by the data transmission, may be indicated in a control message from the transmitting device. In addition to operating as a receiving device, each of the UEs 402, 404, 406, 408 may be capable of operating as a transmitting device. Thus, the UEs 406, 408 are shown as transmitting transmissions 416, 420. The transmissions 414, 416, 418, 420 may be broadcast or multicast to nearby devices. For example, the UE 414 may transmit communications intended for reception by other UEs within range 401 of the UE 414. Additionally / alternatively, the RSU 407 may receive communications from and / or transmit communications to the UEs 402, 404, 406, 408.

[0037] The UE 402, 404, 406, 408, or the RSU 407 may include a QoS flow management component similar to 198 described with respect to FIG.

[0038] A V2X QoS flow management model (e.g., for enhanced V2X (eV2X)) may support different QoS flow IDs for different services. The 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. 5 illustrates an example 500 illustrating data traffic processed by user plane protocol stacks of two different applications V2X App_1 and V2X App_2. V2X App_1 may generate communications 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 communications associated with a second service type ID, e.g., PSID_2, and a third service type ID, e.g., PSID_3. FIG. 5 also illustrates an example control plane protocol stack 550. The control plane protocol stack generates control signaling messages, e.g., PC5 signaling messages, or PC5 RRC messages, to manage links between UEs for unicast type communication.

[0039] Communications associated with PSID_1, PSID_2, and PSID_3 may be separated into different QoS flows. Per-flow QoS management may be applied to broadcast, groupcast, and / or unicast communications. For example, communications generated by each of the service types may be assigned a separate QoS flow ID. As shown in FIG. 5, data traffic from an application layer, e.g., V2X App_1 or V2X App_2, may be processed by the 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 PC5 5QI (PQI), range, bit rate, etc. Thus, the PFI may be different from the PQI, which may be one parameter associated with the assigned PFI. The QoS flow configuration may be configured by the V2X layer 502 to the AS layer 504 (e.g., to the RRC, MAC, and / or physical layers) before processing the data traffic from the application layer. The access stratum (AS) layer may include a PDCP layer, an RLC layer, a MAC layer, and a PHY layer, as shown in example 500. FIG. 5 shows an AS layer protocol stack for LTE and another protocol stack for NR. The protocol stack for NR is shown with an additional Service Data Adaptation Protocol (SDAP) layer. In the control plane example 550, the AS layer 506 may include an additional PC5 RRC layer for NR communication. The AS layer may determine the mapping of QoS flows to radio bearers, e.g., PC5 radio bearers. For example, the SDAP may determine the mapping of 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 notified to the SDAP layer. The radio bearer mapping may be configured for broadcast or groupcast, for example.Radio bearers may be negotiated between the UEs, for example, for unicast or groupcast.

[0040] In the case of unicast communication, different services can be supported over the same Layer 2 link between two UEs. Similarly, different services, e.g., communications associated with different PSIDs / ITS-AIDs, may be allocated at different frequencies. For example, the coordinator may allocate dedicated frequency resources to a particular service. As an example, safety services may be allocated 20 MHz and advanced services may be allocated 30 MHz or 30+20 MHz or Frequency Range 2 (FR2). A V2X UE may be configured with frequency band allocation information, e.g., at the V2X layer 502. The UE may be pre-configured with such information or the information may be provisioned from the network, e.g., from a V2X control function via OMA-DM or from a PCF via control plane signaling (NAS signaling). The frequency band allocation information may specify, for example, the frequency bands that a particular PSID is allowed to use. Sometimes, for example, when a QoS flow includes multiple services, there may be a conflict between a configuration that uses different frequency resources for different services and a configuration that supports the transmission of different services on the same Layer 2 link. When services included in a QoS flow are associated with different frequency resources, there may be a problem of mapping the QoS flows to radio resources, especially when the QoS rules for filtering data traffic into QoS flows are based on QoS requirements without considering frequency band information. Multiple services (with different PSID / ITS-AID) may be placed in the same QoS flow based on similar QoS requirements for the services. For example, the PFI may be set to be equal to the PQI, i.e., all packets sharing the same PQI are placed in the same QoS flow. This allows multiple services to be grouped into the same QoS flow without distinguishing between different services. Thus, different services are 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 the configuration.In that case, different services on the same radio bearer are transmitted on the same frequency band, which may conflict with specific frequency bands allocated to different services.

[0041] Aspects presented herein enable QoS flow management that applies QoS rules based on additional information and parameters. Filters applied at the V2X layer for QoS flow management of data traffic from the application layer may assign PFIs based on PQI, range, and frequency band information, data type, communication mode, destination ID, service ID, IP packet filters, or any combination of QoS requirements from the application layer. PC5 QoS flow parameters may include Guaranteed Bit Rate (GBR), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), and / or PC5 Link Aggregated Maximum Bit Rate (PC5 Link AMBR).

[0042] For example, different PFIs 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. Different PFIs may be assigned based on data type, e.g., whether the data traffic is IP data traffic or non-IP data traffic. PFIs may be assigned based on communication mode, e.g., whether the data traffic is broadcast data traffic, groupcast data traffic, or unicast data traffic. PFIs may be assigned based on service type ID, e.g., PSID or ITS-AID. Thus, data traffic of different service types may be assigned different PFIs. PFIs may be assigned based on destination of data traffic. For example, destination ID of broadcast traffic may include broadcast L2 ID. Destination ID of groupcast traffic may include group ID or translated groupcast L2 ID. Destination ID of unicast data traffic may include target UE application layer ID, link ID, or translated unicast L2 ID. PFIs may be assigned based on QoS requirements received at the V2X layer from the application layer. As an example, the QoS requirements may include any of the packet delay budget (PDB) of the data traffic, the packet error rate (PER) of the data traffic, the range of the data traffic, etc. The PFI may be assigned based on, for example, IP packet filter information, if provided for the data traffic. The V2X layer may use any of the example parameters / information of the data traffic to determine whether to group the data traffic into an existing QoS flow or assign a new PFI.

[0043] 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 in the AS layer to determine whether data traffic of different PFIs can be combined when mapping to radio bearers. As an example, data type information of 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 to the same radio bearer. As another example, frequency information may be passed to the AS layer and may be used in mapping QoS flows to radio bearers. The AS layer may use the frequency information to avoid combining data traffic associated with different frequency bands when mapping data traffic to radio bearers. The AS layer may also use the frequency information of the data traffic to map the QoS flow to the correct Dedicated Radio Bearer (DRB), e.g., a PC5 radio bearer that does not conflict with data traffic included in the QoS.

[0044] Thus, based on the new QoS flow management aspects presented herein, the V2X layer may filter data traffic from the application layer based on frequencies associated with the relevant applications and / or data types such that services with competing frequencies and / or data types can be assigned to different QoS flows.

[0045] FIG. 6 illustrates an example diagram 600 of filtering and mapping data traffic to radio bearers from an application layer. As illustrated, multiple data packets 602 may be received at the V2X layer from an application layer, such as, for example, various applications of a UE. The V2X layer may filter the data traffic and assign PFIs to the filtered data traffic. For example, FIG. 6 illustrates data traffic that is filtered / assigned to four different PFIs 604a, 604b, 604c, 604d. Each of the PFIs 604a, 604b, 604c, 604d has a different PFI ID. Thus, the data traffic including multiple data packets 602 from the application layer is separated into QoS flows including V2X data packets marked with the same PFI. The V2X layer may incorporate frequency band mapping into the QoS rule generation / negotiation. Thus, services with different frequency bands may be given different QoS flow IDs. Additionally or alternatively, the QoS rules may be based on data type, communication mode, destination ID, service ID, IP packet filters, or QoS requirements from the application layer. As shown at 606a, 606b, data packets may be filtered / kept separate 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. The AS layer may combine the data traffic as part of the mapping. For example, FIG. 6 shows that data traffic for PFIs 604c and 604d are combined by the AS layer into QoS flow 608c. Data traffic marked with PFI 604b is shown as being separately mapped as QoS flow 608b. Similarly, PFI 604a is shown as being separately mapped as QoS flow 608a.QoS flows 608b and 608c are mapped to separate radio bearers, but the AS layer is shown mapping the two QoS flows to a shared L2 link 610a. Different radio bearers in L2 link 1 (610a) may include different frequency bands from each other. QoS flow 608a is mapped to separate radio bearers and separate L2 link 2 (610b). As an example, the AS layer may map IP data traffic to a separate L2 link from non-IP data traffic. Similarly, the AS layer may decide to map data traffic of different QoS flows to different radio bearers in a shared L2 link based on whether the frequency bands assigned to the QoS flows allow the same L2 link. The AS layer, e.g., SDAP or RRC layer, may determine the mapping between QoS flows and radio bearers. Frequency band information may be added to the QoS flow parameters so that the AS layer determines the mapping accordingly. As an example, the AS layer can determine whether there are overlapping bands associated with the QoS flows, and when there are overlapping frequency bands, can map the QoS flows to a shared radio bearer or shared link. Once the AS determines the QoS flow information for the QoS flows associated with the PFI, the AS can determine whether multiple QoS flows can be merged into the same radio bearer based on the frequency band information for the QoS flows.

[0046] As an example of broadcast or connectionless groupcast transmission, the V2X layer may apply pre-configured QoS rules to filter data traffic from the application layer, e.g., for transmission from the UE. If there is a mapping between service type and QoS, different QoS rules may be generated for each QoS level. The service type may be based on the PSID / ITS-AID. A first exemplary QoS rule may be as follows:

[0047] [PFI=1][Filter: PSID_1, PSID_2]+[QoS parameters: PQI=1]

[0048] Thus, a PFI of 1 is applied to data traffic of services PSID_1 and PSID 2 with PQI of 1. Data traffic of different PSIDs and / or different PQIs may have PFIs assigned according to different rules.

[0049] The rules may further be based on ranges, such as, for example:

[0050] [PFI=1][Filter: PSID_1, PSID_2]+[QoS parameters: PQI=1, Range=100m]

[0051] In this example, a PFI of 1 may be applied to data traffic of services PSID_1 and PSID_2 with a PQI of 1 and an intended reception range of 100m.

[0052] The V2X layer may determine whether a service type (e.g., PSID_1 and / or PSID_2) has a frequency mapping, e.g., a radio bearer assigned. As an example, if PSID_1 and PSID_2 have different frequency bands, the QoS rules may be divided into the following example QoS rules:

[0053] [PFI=11][Filter: PSID_1]+[QoS parameters: PQI=1, Range=100m, Frequency band 1]

[0054] [PFI=12][Filter: PSID_2]+[QoS parameters: PQI=1, Range=100m, Frequency band 2]

[0055] QoS rules may also be applied without a scope parameter. The application layer may use the API to request a specific QoS level for a particular service type, such as requesting increased priority for a particular PSID. In this example, the V2X layer may decide whether the QoS rules should be updated or whether new QoS rules should be generated.

[0056] At the AS layer, each QoS flow may be given a different virtual radio bearer and, for example, if there are different frequency bands, there may be different queues.

[0057] An example of managed groupcast V2X communication may be QoS rules created based on the groups with which the UE communicates. A set of QoS rules may be generated for each group based on the application layer requirements of the associated service type. For example, the application layer may call an API to provide the V2X layer with either a group ID, a service type (e.g., PSID / ITS-AID), or associated QoS requirements per service type. If no QoS requirements are provided, the UE may use pre-configured QoS levels for the PSID / ITS-AID or default QoS levels for unknown PSID / ITS-AID. An example of a QoS rule may be as follows:

[0058] [PFI=1][Filter: Group ID_1; PSID_1, PSID_2]+[QoS parameters: PQI=1]

[0059] Thus, a first PFI may be applied to data traffic at the V2X layer associated with group ID "Group ID_1" of services PSID_1 and PSID_2 and having a PQI of 1. Data traffic from other groups (i.e., with different group IDs), other services, or with different QoS parameters may have different PFIs applied at the V2X layer. The group ID may include a mapped L2 ID that is known to the application generating 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 specific frequency, e.g., a dedicated radio bearer. If there are different frequency bands, multiple PFI rules may be applied. As an example, it is as follows:

[0060] [PFI=11][Filter: Group ID_1; PSID_1]+[QoS parameters: PQI=1, Frequency band 1]; and

[0061] [PFI=12][Filter: Group ID_1; PSID_1]+[QoS parameters: PQI=1, Frequency band 2]

[0062] Thus, for data traffic targeted to a group of UEs identified by Group ID_1 of service PSID_1 and having QoS parameter PQI=1, PFI 11 may be applied to the data traffic in frequency band 1 and PFI 12 may be applied to the data traffic in frequency band 2. Since the frequency bands are different, i.e. frequency band 1 and frequency band 2, the AS layer may map this QoS flow to two different radio bearers.

[0063] As another example, unicast signaling may include signaling between two UEs. Unicast communication may include managed unicast communication. Unicast communication may use PC5_S protocol to negotiate QoS flow information. The V2X layer may make decisions regarding QoS flows and QoS rules before signaling, e.g., before transmitting data traffic. QoS flow information may be passed from the V2X layer after verifying that the link has been set up by the peer UE that will receive the data traffic.

[0064] In the case of unicast, a link ID may be generated once it is determined that a layer 2 link with the target UE is established. This link ID may be local and may remain constant for the life of the unicast link (whereas the L2 ID may change). The link ID may be returned to the application. The application may then use this link ID when passing data packets to the V2X layer. The QoS rule filter may use the link ID as a parameter to filter 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 into different QoS flows. In addition, the AS may 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 also be included as part of the QoS flow parameters. Below is an example QoS rule that includes a link ID:

[0065] [PFI=1][Filter: Link ID 1; PSID_1]+[QoS parameters: PQI=1, Frequency band 1, Link ID 1]

[0066] Thus, a particular PFI (e.g., 1) may be applied to unicast data traffic associated with Link ID 1 and PQI = 1 of service PSID_1. As described for broadcast and groupcast communications, the rules may optionally be further based on frequency band, such that a different PFI rule applies to Link ID 1 and PQI = 1 of service PSID_1 and frequency band 1 than to Link ID 1 and PQI = 1 of service PSID_1 and frequency band 2.

[0067] For the same link ID (ie, between the same pair of UEs), there can be multiple QoS flows in the same radio bearer that are mapped to different frequency bands, as long as the QoS flows use the same frequency band.

[0068] The AS layer (eg, RRC, or SDAP) may determine the QoS flow to radio bearer mapping, taking into account both the link ID and the frequency.

[0069] If the application layer does not use a link ID, it may still indicate the target UE application layer ID (e.g., station ID or "StationID") when passing the packet to the V2X layer. In this example, the filter or QoS rule applied at the V2X layer may be based on the application layer ID. The V2X layer may convert the application layer ID to a link ID, or l2 ID, when passing the QoS flow information to the AS layer. Exemplary QoS rules may include the following:

[0070] [QFI=1][Filter: Application Layer ID; PSID_1]+[QoS parameters: PQI=1, Frequency band 1, Link ID 1 / L2 ID]

[0071] For IP traffic, the service type information (PSID / ITS-AID) may not be known to the V2X layer. The application layer may use IP sockets to deliver packets to the V2X layer. In this example, some potential filtering rules may be used to identify the frequency band information.

[0072] As a first example, the application layer may set the service type information in the flow label (or by extending it in the TC field) of the IPv6 header of the data traffic. Since the flow label field may contain 20 bits (28 bits in the TC field), the number of bits may represent a range of service types.

[0073] As a second example, the application layer may directly indicate frequency band information to the V2X layer. To enable the application layer to indicate frequency band information, the V2X layer may expose a frequency band mapping configuration to the application layer.

[0074] As a third example, the application layer may use IPv6 extension headers to identify the service type, and PC5 QoS rules may be able to read such extension headers.

[0075] As a fourth example, a source IP prefix may be used to indicate a service type to the V2X layer, which may replace the source IP prefix with an actual IP prefix (e.g., a link-local IP prefix) before passing such information to lower layers. An example of this may include IP socket support, where, for example, an application layer may indicate a source address when creating an IP socket, for example, by calling a bind function to perform binding of the IP prefix with the data traffic.

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

[0077] 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a UE (e.g., a processing system 914 that may include the UE 104, the device 350, the apparatus 802 / 802′, the memory 360, 376, and may be the UE in its entirety or a component of the UE, such as the TX processor 316, the RX processor 370, and / or the controller / processor 375, or the TX processor 368, the RX processor 356, and / or the controller / processor 359). Optional aspects are indicated by dashed lines. The method may enable the UE to perform QoS flow management more effectively.

[0078] At 702, the UE receives data traffic from an application layer for transmission in device-to-device communication, such as V2X communication. For example, 702 may be performed by data component 805 from Figure 8. Figures 5 and 6 show examples of data traffic from an application layer that may be received at a V2X layer of the UE.

[0079] At 704, the UE assigns at least one Quality of Service (QoS) flow identifier (ID) to the data traffic based on the radio resource information of the data traffic. The QoS flow identifier may be assigned based on both the radio resource information and the traffic type information. Different QoS flow IDs are assigned to data packets for transmission on different radio resources. The device-to-device communication includes V2X communication, and the at least one QoS flow ID may be assigned at a V2X layer based on the radio resource information of the data traffic. For example, 704 may be performed by a QoS assignment component 806 from FIG. 8. In one aspect, the radio resource information may include a frequency band used for transmission of the data packets, such as, for example, a DRB.

[0080] At 708, after assigning the QoS flow ID, the UE may pass radio resource information of the data traffic associated with the QoS flow ID to a lower layer. At 710, the UE may use the radio resource information at the lower layer to determine mapping of the data traffic associated with the QoS flow ID to at least one radio bearer. For example, 708 may be performed by radio resource information component 808 from FIG. 8, and 710 may be performed by radio bearer mapping component 812 from FIG. 8.

[0081] In one aspect, the radio resource information may be determined based on a mapping of service type information received from an application layer to radio resource information. The mapping of service type information to radio resource information may be configured in a user equipment (UE). In some aspects, the service type information of the data traffic may be indicated from the application layer based on a header of the data traffic. In other aspects, the service type information of the data traffic may be indicated from the application layer based on a header extension of the data traffic, the header extension including one of a flow label or an Internet Protocol (IP) version 6 (IPv6) extension header. In a further aspect, the service type information of the data traffic may be indicated from the application layer based on a source identifier. In an additional aspect, the radio resource information of the data traffic is indicated from the application layer based on a frequency band indication of the data traffic.

[0082] In another aspect, the QoS Flow ID may be assigned further based on a communication mode of the data traffic such that data packets are assigned different QoS Flow IDs based on the communication mode, the communication mode including one of broadcast communication, groupcast communication, and unicast communication.

[0083] In a further aspect, the at least one QoS Flow ID may be assigned further based on a destination ID of the data traffic, such that data packets having different destination IDs are assigned different QoS Flow IDs. In one aspect regarding the destination ID, the data traffic is for broadcast communication and the destination ID may include a broadcast Layer 2 (L2) ID.

[0084] In another aspect regarding the destination ID, the data traffic is for groupcast communication and the destination ID may include a group ID or a translated groupcast Layer 2 (L2) ID.

[0085] In an additional aspect regarding the destination ID, the data traffic is for unicast communication and the destination ID may include one of a target UE application layer ID or a link ID.

[0086] In another aspect, the at least one QoS Flow ID may be assigned further based on one or more QoS requirements from an application layer of the data traffic, such that data packets having different QoS requirements from the application layer are assigned different QoS Flow IDs. The QoS requirements from the application layer may include at least one of a Packet Delay Budget (PDB) of the data traffic, a Packet Error Rate (PER) of the data traffic, or a range of the data traffic.

[0087] In a further aspect, the at least one QoS flow ID may be assigned further based on a service type ID of the data traffic such that data packets having different service type IDs are assigned different QoS flow IDs. The service type ID may include a PSID or an ITS-AID.

[0088] In some aspects, at least one QoS flow ID may be assigned based on a one-to-one mapping between a service type ID and a QoS flow ID. Thus, at 716, the UE may determine, based on the radio resource information, whether to merge QoS flows having different QoS flow IDs to the same radio bearer at the access stratum. For example, 716 may be performed by radio bearer merging component 814 from FIG. 8.

[0089] At 704, at least one QoS flow ID may be assigned further based on the traffic type information of the data traffic. For example, at 712, the UE passes the traffic type information of the data traffic to a lower layer, and finally, at 714, the UE uses the traffic type information in the lower layer to map the data traffic to at least one radio bearer. For example, 712 may be performed by the traffic type information component 810 from FIG. 8, and 714 may be performed by the radio bearer mapping component 812 from FIG. 8. Internet Protocol (IP) data packets and non-IP data packets are assigned different QoS flow IDs.

[0090] FIG. 8 is a conceptual data flow diagram 800 illustrating data flow between different means / components in an exemplary apparatus 802. The apparatus may be a UE or a component of a UE (e.g., UE 104, 350, 402). The apparatus 802 includes a receiving component 804 that receives data traffic from one or more V2X applications 850 and device-to-device (e.g., V2X communication) from one or more other UEs 860. The apparatus 802 includes a data component 805 that receives data traffic from an application layer via the receiving component 804 for transmission in device-to-device communication. The apparatus 802 includes a QoS assignment component 806 that assigns at least one QoS flow ID of the data traffic based on resource information of the data traffic. The apparatus 802 includes a radio resource information component 808 that passes radio resource information of the data traffic associated with the QoS flow ID to a lower layer, and a traffic type information component 810 that passes traffic type information of the data traffic to a lower layer. The apparatus 802 includes a radio bearer mapping component 812 that uses radio resource information sent from the radio resource information component 808 and / or traffic type information sent from the traffic type information component 810 in a lower layer to determine mapping of data traffic associated with a QoS flow ID to at least one radio bearer. The apparatus 802 includes a radio bearer merging component 814 that determines whether to merge QoS flows having different QoS flow IDs to the same radio bearer in an access stratum layer based on the radio resource information sent from the radio resource information component 808. The apparatus 802 further includes a transmitting component 816 that transmits D2D communication and data traffic to one or more other UEs 860 via the radio bearers mapped by the radio bearer mapping component 812 or merged by the radio bearer merging component 814.

[0091] The apparatus 802 may include additional components that perform each of the blocks of the algorithms in the above-described flowchart of Figure 7. Thus, each block in the above-described flowchart of Figure 7 may be performed by a component (e.g., 804-816), and the apparatus 802 may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process / algorithm, implemented by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0092] 9 is a diagram 900 illustrating an example of a hardware implementation of an apparatus 802' utilizing a processing system 914. The processing system 914 may be implemented using a bus architecture, generally represented by a bus 924. The bus 924 may include any number of interconnecting buses and bridges, depending on the particular application of the processing system 914 and the overall design constraints. The bus 924 links together various circuits, including the processor 904, components 804, 805, 806, 808, 810, 812, 814, 816, and one or more processors and / or hardware components, represented by a computer-readable medium / memory 906. The bus 924 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 further.

[0093] The processing system 914 may be coupled to a transceiver 910. The transceiver 910 is coupled to one or more antennas 920. The transceiver 910 provides a means for communicating with various other devices over a transmission medium. The transceiver 910 receives signals from one or more antennas 920, extracts information from the received signals, and provides the extracted information to the processing system 914, in particular to the receiving component 804. In addition, the transceiver 910 receives information from the processing system 914, in particular from the transmitting component 816, and generates signals to be applied to the one or more antennas 920 based on the received information. The processing system 914 includes a processor 904 coupled to a computer-readable medium / memory 906. The processor 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 906. The software, when executed by the processor 904, causes the processing system 914 to perform the various functions described above for any particular device. The computer readable medium / memory 906 may be used to store data manipulated by the processor 904 when executing software. The processing system 914 further includes at least one of the components 804, 805, 806, 808, 810, 812, 814, 816. The components may be software components running in the processor 904 and residing / stored in the computer readable medium / memory 906, one or more hardware components coupled to the processor 904, or some combination thereof. The processing system 914 may be a component of the device 310 or device 350 and may include the memory 376, 360 and / or at least one of the TX processor 316, 368, the RX processor 370, 356, and the controller / processor 375, 359. Alternatively, the processing system 914 may be an entire UE (e.g., see device 310 or 350 of FIG. 3).

[0094] In one configuration, an apparatus 802 / 802′ 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 to the data traffic based on radio resource information of the data traffic, where data packets for transmission on different radio resources are assigned different QoS flow IDs. The apparatus 802 / 802′ may also include means for passing radio resource information of 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 resource information at the lower layer, means for passing traffic type information of 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, and means for determining whether to merge QoS flows with different QoS flow IDs to a same radio bearer at an access stratum layer based on the radio resource information.

[0095] The aforementioned means may be one or more of the aforementioned components of the processing system 914 of the apparatus 802 and / or the apparatus 802' configured to perform the functions recited by the aforementioned means. As described above, the processing system 914 may include the TX processor 316, 368, the RX processor 370, 356, and the controller / processor 375, 359. Thus, in one configuration, the aforementioned means may be the TX processor 316, 368, the RX processor 370, 356, and the controller / processor 375, 359 configured to perform the functions recited by the aforementioned means.

[0096] The following examples are illustrative only and may be combined without limitation with other examples or aspects of the teachings described herein.

[0097] Example 1 is a method of wireless communication including receiving data traffic from an application layer for transmission in device-to-device communication; and assigning at least one Quality of Service (QoS) flow identifier (ID) to the data traffic based on radio resource information of the data traffic, where data packets for transmission on different radio resources are assigned different QoS flow IDs.

[0098] In Example 2, the method of Example 1 further includes the radio resource information including a frequency band used to transmit the data packet.

[0099] In Example 3, the method of any of Examples 1 to 2 further includes passing radio resource information of the data traffic associated with the QoS flow ID to a lower layer, and determining, based on the radio resource information in the lower layer, mapping of the data traffic associated with the QoS flow ID to at least one radio bearer.

[0100] In Example 4, the method of any of Examples 1-3 further includes, the device-to-device communication includes vehicle-to-everything (V2X) communication, and the at least one QoS flow ID is assigned at a V2X layer based on radio resource information of the data traffic.

[0101] In Example 5, the method of any of Examples 1-4 further includes determining the radio resource information based on mapping of the service type information received from the application layer to the radio resource information.

[0102] In Example 6, the method of any of Examples 1-5 further includes configuring a mapping of the service type information to the radio resource information in a user equipment (UE).

[0103] In Example 7, the method of any of Examples 1-6 further includes indicating the type of service information of the data traffic from an application layer based on a header of the data traffic.

[0104] In Example 8, the method of any of Examples 1-7 further includes: the service type information of the data traffic is indicated from the application layer based on a header extension of the data traffic, the header extension including one of a flow label or an Internet Protocol (IP) version 6 (IPv6) extension header.

[0105] In Example 9, the method of any of Examples 1-8 further includes indicating type of service information of the data traffic from an application layer based on the source identifier.

[0106] In Example 10, the method of any of Examples 1-9 further includes indicating radio resource information of the data traffic from an application layer based on a frequency band indication of the data traffic.

[0107] In Example 11, at least one QoS flow ID of the data traffic is assigned further based on the traffic type information, and Internet Protocol (IP) data packets and non-IP data packets are assigned different QoS flow IDs, according to any of Examples 1 to 10.

[0108] In Example 12, the method of any of Examples 1-11 further includes passing traffic type information of the data traffic to a lower layer; and mapping the data traffic to at least one radio bearer based on the traffic type information at the lower layer.

[0109] In Example 13, the method of any of Examples 1-12 further includes: the QoS flow ID is assigned further based on a communication mode of the data traffic, such that the data packets are assigned different QoS flow IDs based on the communication mode, the communication mode including one of broadcast communication, groupcast communication, and unicast communication.

[0110] In Example 14, the method of any of Examples 1-13 further includes assigning at least one QoS flow ID further based on a destination ID of the data traffic, such that data packets having different destination IDs are assigned different QoS flow IDs.

[0111] In Example 15, the method of any of Examples 1-14 further includes, wherein the data traffic is for broadcast communication and the destination ID includes a broadcast Layer 2 (L2) ID.

[0112] In Example 16, the method of any of Examples 1-15 further includes: the data traffic is for groupcast communication, and the destination ID includes a group ID or a translated groupcast Layer 2 (L2) ID.

[0113] In Example 17, the method of any of Examples 1-16 further includes: the data traffic is for unicast communication; and the destination ID includes one of a target user equipment (UE) application layer ID or a link ID.

[0114] In Example 18, the method of any of Examples 1-17 further includes assigning at least one QoS flow ID further based on a service type ID of the data traffic, such that data packets having different service type IDs are assigned different QoS flow IDs.

[0115] In Example 19, the method of any of Examples 1-18 further includes the service type ID including a Provider Service ID (PSID) or an Intelligent Transportation System Application Identifier (ITS-AID).

[0116] In Example 20, the method of any of Examples 1-19 further includes assigning the at least one QoS flow ID based on a one-to-one mapping between a service type ID and a QoS flow ID.

[0117] In Example 21, the method of any of Examples 1-20 further includes determining, based on the radio resource information, whether to merge QoS flows having different QoS flow IDs into a same radio bearer at the access stratum.

[0118] In Example 22, the method of any of Examples 1-21 further includes assigning at least one QoS flow ID further based on one or more QoS requirements from an application layer of the data traffic, such that data packets having different QoS requirements from the application layer are assigned different QoS flow IDs.

[0119] In Example 23, the method of any of Examples 1-22 further includes, the QoS requirements from the application layer include at least one of a packet delay budget (PDB) of the data traffic, a packet error rate (PER) of the data traffic, or a range of the data traffic.

[0120] Example 24 is a system or device including means for implementing a method or realizing a device according to any of Examples 1-23.

[0121] Example 25 is a device including one or more processors and one or more memories in electronic communication with the one or more processors that store instructions, the instructions being executable by the one or more processors to cause the system or apparatus to implement a method according to any of Examples 1-23.

[0122] Example 26 is a non-transitory computer-readable medium storing instructions, the instructions being executable by one or more processors to cause the one or more processors to implement a method according to any of Examples 1-23.

[0123] It should be understood that the particular order or hierarchy of the blocks in the disclosed processes / flow charts is illustrative of example approaches. Based on design preferences, it should be understood that the particular order or hierarchy of the blocks in the processes / flow charts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the particular order or hierarchy presented.

[0124] The above description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects shown herein but are to be accorded the widest scope consistent with the claim language, and references to elements in the singular do not mean "the only one" unless so expressly stated, but rather "one or more." The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects. Unless otherwise expressly stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," "A, B, C, or any combination thereof" include any combination of A, B, and / or C and may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or that later become known to those of skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is made publicly available, regardless of whether such disclosure is expressly recited in the claims.Words such as "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Thus, no claim element should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for." [Explanation of symbols]

[0125] 100 Access Network 102 Base station 104UE 107 Roadside unit (RSU) 110 Geographic Coverage Areas 120 Communication Links 132 backhaul links 150 Wi-Fi access points (AP) 152 Wi-Fi stations (STA) 154 Communication Links 158 Device-to-Device (D2D) Communication Links 160 Evolved Packet Core (EPC) 162 Mobility Management Entity (MME) 164 Other MMEs 166 Serving Gateway 168 Multimedia Broadcast Multicast Service (MBMS) Gateway 170 Broadcast Multicast Service Center (BM-SC) 172 Packet Data Network (PDN) Gateway 174 Home Subscriber Server (HSS) 176 IP Services 180 base station 182 Beamforming 182' Sending direction 184 backhaul links 190 Core Network 192 Access and Mobility Management Function (AMF) 193 Other AMF 194 Session Management Facility (SMF) 195 User Plane Function (UPF) 196 Unified Data Management (UDM) 197 IP Services 198 QoS Flow Management Components 310 First wireless communication device 316 Transmit (TX) Processor 318 Transmitter 318 Receiver 320 Antenna 350 Second wireless communication device 352 Antenna 354 Receiver 354 Transmitter 356 Receive (RX) Processor 358 Channel Estimator 359 Controller / Processor 360 Memory 368 TX Processor 370 Receive (RX) Processor 374 Channel Estimator 375 Controller / Processor 376 Memory 401 Range 402UE 404UE 406 UE 407 RSU 408 UE 414 Send 416 Send 418 Send 420 Send 502 V2X Layer 504 AS Layer 506 AS Layer 550 Control Plane Protocol Stack 602 Data Packets 604 PFI 608 QoS Flows 610 Shared L2 Link 802 equipment 804 Receiving Component 805 Data Components 806 QoS Allocation Components 808 Radio Resource Information Component 810 Traffic Type Information Component 812 Radio Bearer Mapping Component 814 Radio Bearer Merge Component 816 Transmission Components 850 V2X Applications 860UE 904 Processor 906 Computer Readable Medium / Memory 910 Transceiver 914 Processing System 920 Antenna 924 Bus

Claims

1. 1. A method executed by a processor included in an apparatus for wireless communication, comprising: receiving data traffic from an application layer for transmission in device-to-device communication; assigning at least one Quality of Service (QoS) flow identifier (ID) to the data traffic based on radio resource information of the data traffic, the data traffic including data packets for transmission, the data packets for transmission over different radio resources being assigned different QoS flow IDs, the radio resource information including frequency bands used for the transmission of the data packets; passing the radio resource information of the data traffic associated with the at least one QoS flow ID to a lower layer; determining 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 resource information at the lower layer; The method includes:

2. The device-to-device communication includes vehicle-to-everything (V2X) communication, and the at least one QoS flow ID is assigned in a V2X layer based on the radio resource information of the data traffic. The method of claim 1.

3. The method of claim 1 , wherein the radio resource information is determined based on a mapping of service type information received from the application layer to the radio resource information.

4. The method of claim 3, wherein the mapping of the service type information to the radio resource information is configured in a user equipment (UE).

5. The service type information of the data traffic is indicated from the application layer based on a header of the data traffic; or The service type information of the data traffic is indicated from the application layer based on a header extension of the data traffic, the header extension including one of a flow label or an Internet Protocol (IP) version 6 (IPv6) extension header; or The type of service information of the data traffic is indicated from the application layer based on a source identifier; or The method of claim 4, wherein the radio resource information of the data traffic is indicated from the application layer based on a frequency band indication of the data traffic.

6. 2. The method of claim 1, wherein the at least one QoS flow ID of the data traffic is assigned further based on traffic type information of the data traffic, and Internet Protocol (IP) data packets and non-IP data packets are assigned different QoS flow IDs.

7. passing said traffic type information of said data traffic to a lower layer; mapping the data traffic to at least one radio bearer based on the traffic type information in the lower layer; The method of claim 6, further comprising:

8. The at least one QoS flow ID is assigned further based on the communication mode of the data traffic such that the data packets are assigned different QoS flow IDs based on the communication mode, the communication mode comprising one of broadcast communication, groupcast communication, and unicast communication. The method of claim 1.

9. the at least one QoS flow ID is assigned further based on a destination ID of the data traffic, such that the data packets having different destination IDs are assigned the different QoS flow IDs; 2. The method of claim 1, wherein the at least one QoS flow ID is assigned further based on one or more QoS requirements from the application layer of the data traffic, such that the data packets having different QoS requirements from the application layer are assigned the different QoS flow IDs.

10. The data traffic is for broadcast communication and the destination ID includes a broadcast Layer 2 (L2) ID; or The data traffic is for groupcast communication and the destination ID includes a group ID or a translated groupcast Layer 2 (L2) ID; or 10. The method of claim 9, wherein the data traffic is for unicast communication and the destination ID includes one of a target user equipment (UE) application layer ID or a link ID.

11. The method of claim 1 , wherein the at least one QoS flow ID is assigned further based on a service type ID of the data traffic, such that the data packets having different service type IDs are assigned the different QoS flow IDs.

12. 12. The method of claim 11, wherein the service type ID comprises a Provider Service ID (PSID) or an Intelligent Transportation System Application Identifier (ITS-AID).

13. The method of claim 11 , wherein the at least one QoS flow ID is assigned based on a one-to-one mapping between the service type ID and the at least one QoS flow ID.

14. determining whether to merge QoS flows having different QoS flow IDs into the same radio bearer at an access stratum layer based on the radio resource information; The method of claim 13, further comprising:

15. 1. An apparatus for wireless communication, comprising: Memory, and at least one processor coupled to the memory, the at least one processor comprising: Apparatus configured to perform the method according to any one of claims 1 to 14.

Images