Supporting quality of service flow mapping processing for V2X communications

Abstract

Wireless communication systems and methods related to quality of service mapping are provided. A first user equipment determines a sidelink radio bearer identifier (SLRB ID) for a quality of service (QoS) flow based on multiple rules. The rules identify different characteristics of the QoS flow. The SLRB ID is inserted into the header of the packet in the QoS flow. The QoS flow is mapped to a radio bearer, which is mapped to an L2 link with other radio bearers mapped to other QoS flows. The L2 link sends the radio bearer to a second UE as part of a broadcast, multicast, or unicast sidelink communication. Based on the SLRB ID, the second UE identifies the requirements of the QoS flow.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefits of U.S. Patent Application No. 16 / 948,840 filed on October 1, 2020 and U.S. Provisional Patent Application No. 62 / 910,299 filed on October 3, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to wireless communication systems, and more particularly, to quality of service flow mapping for supporting vehicle-to-everything communications. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Long Term Evolution (LTE) systems, 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.

[0005] In some examples, a wireless multiple access communication system may include multiple base stations, each base station simultaneously supporting communication for multiple communication devices (also referred to as user equipment (UE)). In an LTE or advanced LTE (LTE-A) network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation or 5G network), a wireless multiple access communication system may include multiple distributed units (DU) (e.g., edge units (EU), edge nodes (EN), radio heads (RH), smart radio heads (SRH), transmission reception points (TRP), etc.) communicating with multiple central units (Cu) (e.g., central nodes (CN), access node controllers (ANC), etc.), wherein a set of one or more distributed units communicating with a central unit may define an access node (e.g., a new radio base station (NR BS), a new radio node B (NR NB), a network node, a 5GNB, an eNB, a next generation node B (gNB), etc.). A base station or DU may communicate with a group of UEs on downlink channels (eg, for transmissions from the base station or to the UE) and uplink channels (eg, for transmissions from the UE to the base station or distributed unit).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example of an emerging telecommunication standard is New Radio (NR), such as 5G radio access. NR is a set of enhancements to the LTE mobile standard released by the 3rd Generation Partnership Project (3GPP). It aims to better support mobile broadband Internet access by increasing spectral efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL), and supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as demand for mobile broadband access continues to grow, there is a desire for further improvements in NR technology, such as ultra-reliability, low latency, and fast recovery. Summary of the invention

[0008] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an extensive review of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its only purpose is to present some concepts of one or more aspects of the present disclosure in an overview form as a preface to the specific embodiments presented later.

[0009] In one example, a method of wireless communication includes: at a first user equipment (UE), determining a quality of service (QoS) flow's SLRB ID using multiple rules mapped to multiple sidelink radio bearer identifiers (SLRB IDs), inserting the determined SLRB ID into a header of a packet of the QoS flow, using the SLRB ID to identify a radio bearer, wherein the radio bearer carries packets of the QoS flow; mapping the radio bearer to an L2 link, and transmitting the packets of the radio bearer in the L2 link together with at least one other packet from at least one other radio bearer to at least one second UE, the at least one other radio bearer having different SLRB IDs corresponding to different QoS flows.

[0010] In another example, the first UE and at least one second UE are pre-configured with the plurality of rules.

[0011] In another example, the first UE and the at least one second UE receive the plurality of rules from the base station using a base station signal.

[0012] In another example, the first UE and the at least one second UE receive the plurality of rules from the base station using dedicated broadcast signaling.

[0013] In another example, the communication is via a vehicle-to-everything (V2X) communication connection.

[0014] In another example, a rule in the plurality of rules maps at least one characteristic of a QoS flow.

[0015] In another example, the characteristic is a range between the first UE and at least one second UE.

[0016] In another example, the communication is a multicast transmission in a V2X communication connection to at least one second UE that is proximate to the first UE in a group with the first UE.

[0017] In another example, the communication is a broadcast transmission to at least one second UE in a V2X communication connection, the at least one second communication being proximate to the first UE.

[0018] In another example, inserting further comprises inserting the SLRB ID into sidelink control information (SCI) in a header of the packet.

[0019] In yet another example, a method of wireless communication, receiving, at a first user equipment (UE) from a second UE, at least one radio bearer in an L2 link configured to carry packets from multiple radio bearers corresponding to QoS flows having different characteristics, identifying a packet from the at least one radio bearer, identifying a sidelink radio bearer identifier (SLRB ID) from a header of the packet, identifying a rule mapped to the SLRB ID from a plurality of rules, wherein the rule includes at least one characteristic of the QoS flow associated with the packet, and determining an action at the first UE based on the at least one characteristic in the rule.

[0020] In another example, the action causes the first UE to issue a retransmission request to the second UE.

[0021] In another example, the reception using the at least one radio bearer in the L2 link is a multicast transmission from the second UE.

[0022] In another example, the reception using the at least one radio bearer in the L2 link is a broadcast transmission from the second UE.

[0023] In another example, the at least one characteristic is a range between the first UE and the second UE.

[0024] In another example, the first UE and the second UE are pre-configured with the plurality of rules.

[0025] In another example, the first UE and the second UE receive the plurality of rules from the base station using a base station broadcast signal.

[0026] In another example, the first UE and the second UE receive the plurality of rules from the base station using dedicated broadcast signaling.

[0027] In another example, the receiving is via a vehicle-to-everything (V2X) communication connection.

[0028] In another example, identifying the SLRB ID from a header of the packet further includes identifying the SLRB ID from a SCI in the header. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 and Figure 2 A wireless communication network according to an embodiment of the present disclosure is shown.

[0030] Figure 3 The layers of a V2X communication model according to an embodiment of the present disclosure are shown.

[0031] Figure 4 A block diagram of an SLRB mapping table according to an embodiment of the present disclosure is shown.

[0032] Figure 5 is a block diagram of an exemplary user equipment (UE) according to an embodiment of the present disclosure.

[0033] Figure 6 is a block diagram of an exemplary base station (BS) according to an embodiment of the present disclosure.

[0034] Figure 7 is a flow chart for mapping QoS flows to sidelink radio bearer identifiers for sidelink communications according to an embodiment of the present disclosure.

[0035] Figure 8 is a flow chart for identifying characteristics in a QoS flow received via sidelink communications according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] The specific embodiments described below, in conjunction with the accompanying drawings, are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. The specific embodiments include specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, in order to avoid confusion with these concepts, well-known structures and components are shown in block diagram form.

[0037] The technology described herein can adopt various wireless communication networks, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier FDMA (SC-FDMA) and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP 2). The techniques described herein can be used for the above wireless networks and radio technologies as well as other wireless networks and radio technologies, such as next generation (e.g., fifth generation (5G)) networks.

[0038] Various aspects of the present disclosure describe a V2X communication system in which multiple user equipments (UEs) communicate via a side link. A first user equipment (UE) determines a SLRB ID for a quality of service (QoS) flow using a rule table mapped to multiple side link radio bearer identifiers (SLRB IDs). The SLRB ID is inserted into a header of a packet in the QoS flow or into an SCI in the header. The QoS flow is mapped to a radio bearer. The radio bearer is mapped to an L2 link in a V2X communication with other radio bearers and their QoS flows. The L2 link transmits the radio bearer to at least one second UE in a broadcast, multicast, or unicast transmission.

[0039] Various aspects of the present disclosure describe how a second UE identifies characteristics of a QoS flow and uses these characteristics to determine whether to generate an action, such as transmitting a HARQ NACK to a first UE. The second UE receives at least one radio bearer in an L2 link from the first UE in a broadcast, multicast, or unicast transmission. The second UE identifies a packet from the at least one radio bearer in the L2 link. From a header of the packet or an SCI in the header, the second UE identifies a SLRB ID. From the SLRB ID, the second UE identifies a rule, and from the rule, the UE identifies characteristics associated with the QoS flow including the packet. The second UE determines an action to send a communication to the first UE based on these characteristics.

[0040] Figure 1 A wireless communication network 100 is shown that facilitates vehicle-to-everything communications (V2X) according to an embodiment of the present disclosure. Example V2X communications may be vehicle-to-vehicle (V2V) communications, vehicle-to-pedestrian (V2P) communications, vehicle-to-infrastructure (V2I) communications, and vehicle-to-network (V2N) communications.

[0041] The network 100 may include a plurality of vehicles 102 (e.g., shown as 102a to 102f) and a plurality of base stations 104. The BS 104 may include an evolved Node B (eNodeB) or a next generation Node B (gNB). The BS 104 may be a station that communicates with the vehicle 102 and may also be referred to as a base transceiver station, a Node B, an access point, etc.

[0042] The BS 104 communicates with the vehicle 102. The vehicle 102 may communicate with the BS 104 via an uplink (UL) and a downlink (DL). The downlink (or forward link) refers to the communication link from the BS 104 to the vehicle 102. The UL (or reverse link) refers to the communication link from the vehicle 102 to the BS 104. The BS 104 may also communicate with each other directly or indirectly via wired and / or wireless connections.

[0043] Vehicle 102 may travel on road 130. Vehicle 102 may pass through different coverage areas or cells 110 in network 100. Vehicle 102 may have on-board wireless communication devices for communicating with each other and with BS 104 via side links. Vehicle 102 may have a receiver for communicating with a global navigation satellite system (GNSS), which may provide location tracking and timing information. Vehicle 102 may have sensors for various sensing, which may be used for navigation, safety, and / or performance. Some examples of sensors may include Lidar, radar, and high-definition cameras. Network 100 is an example of a network to which various aspects of the present disclosure may be applied.

[0044] Each BS 104 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the specific geographic coverage area of ​​the BS and / or the BS subsystem serving the coverage area, depending on the context in which the term is used. In this regard, BS 104 can provide communication coverage for macrocells, microcells, femtocells and / or other types of cells with different coverage areas and access restrictions. As shown, base stations 104a, 104b and 104c provide communication coverage in cells 110a, 110b and 110c, respectively. In some embodiments, BS 104 can support one or more (e.g., two, three, four, etc.) cells.

[0045] The network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs 104 may have similar frame timing, and transmissions from different BSs 104 may be approximately aligned in time. For asynchronous operation, the BSs 104 may have different frame timing, and transmissions from different BSs 104 may not be aligned in time.

[0046] In some implementations, the network 100 utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the UL. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are sent in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, for corresponding system bandwidths of 1.4, 3, 5, 10, 15, or 20 megahertz (MHz), K can be equal to 72, 180, 300, 600, 900, and 1200, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz, and there may be 1, 2, 4, 8 or 16 subbands for corresponding system bandwidths of 1.4, 3, 5, 10, 15 or 20 MHz, respectively.

[0047] In some aspects, communication in the network 100 may be performed in the form of radio frames. A radio frame may include multiple subframes. Each subframe may include multiple symbols across frequency bands and time intervals. The network 100 may employ various transmission configurations. For example, each radio frame may include one or more subframes for DL ​​transmission and one or more subframes for UL transmission.

[0048] In the network 100, the vehicle 102 can use various wireless communication technologies. In some embodiments, the network 100 can support LTE-based V2X, V2V, LTE-based V2I, LTE-based device-to-device (D2D) or direct short-range communication (DSRC) communication.

[0049] The network 100 may also include a plurality of user equipments (UEs) 106a, 106b that communicate with the BS 104 and perform sidelink communications with each other or with the vehicle 102. The UE may be a cellular phone, a smart phone, a personal digital assistant, a wireless modem, a laptop computer, a tablet computer, etc. In some embodiments, the UE and the vehicle 102 may employ similar initial attachment procedures to initiate communications with the BS 104. For example, the initial attachment procedure may be similar to an LTE random access procedure.

[0050] Figure 2 An example of a wireless communication network 200 providing side link communication according to an embodiment of the present disclosure is shown. Although shown using a UE, the embodiments may also be applied to Figure 1 For the purpose of simplifying the discussion, Figure 2 One BS 204 and four UEs 206 are shown, but it will be appreciated that embodiments of the present disclosure may be extended to any suitable number of UEs 206 and / or BSs 204 (eg, approximately 2, 3, 6, 7, 8, or more).

[0051] In network 200, some UE 206 can communicate with each other in peer-to-peer communication. For example, UE 206a can communicate with UE 206b through side link 208a, and UE 206c can communicate with UE 206d through another side link 208b. In some instances, side link 208a can be a unicast bidirectional link between a pair of UEs 206a and 206b. In some other instances, side links 208b and 208c can be broadcast and multicast links supporting multicast side link services between UE 206c, 206f and 206d. In broadcast transmission, UE 206c can transmit to all UEs 206, and in multicast transmission, UE 206c can transmit to members of the group. Some UE 206 can also communicate with BS 204 in UL direction and / or DL ​​direction via communication link 210. For example, UEs 206a, 206b, and 206c are within coverage area 212 of BS 204 and may therefore communicate with BS 204. UEs 206d and 206f are outside of coverage area 212 and may therefore not communicate directly with BS 204. In some instances, UE 206c may act as a relay for UE 206d to reach BS 204. In some aspects, some UEs 206 are associated with vehicles (e.g., Figure 1 As shown), the communication on the side link 208a-108c can be C-V2X communication. C-V2X communication can refer to the communication between the vehicle and any other wireless communication device in the cellular network.

[0052] In some aspects, BS 204 may communicate with UE 206a using HARQ technology to improve communication reliability. BS 204 may schedule UE 206a for PDSCH communication by sending DL grant in PDCCH. BS 204 may send DL data packets to UE 206a according to the scheduling in PDSCH. DL data packets may be sent in the form of transport blocks (TBs). If UE 206a successfully receives the DL data packet, UE 206a may send HARQ ACK to BS 204. Conversely, if UE 206a fails to successfully receive the DL transmission, UE 206a may send HARQ NACK to BS 204. When HARQ NACK is received from UE 206a, BS 204 may retransmit the DL data packet to UE 206a. The retransmission may include the same DL data codec version as the initial transmission. Alternatively, the retransmission may include a DL data codec version different from the initial transmission. UE 206a may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. BS 204 and UE 206a may also apply HARQ to UL communications using a mechanism substantially similar to DL HARQ. Similarly, UE 206 may also apply similar HARDQ to sidelink communications between each other ( Figure 1 The same is true for vehicle 102 discussed in ).

[0053] As described above, the networks 100, 200 may be used for sidelink communications, including device-to-device (D2D) communications, vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, vehicle-to-pedestrian (V2P) communications, vehicle-to-infrastructure (V2I) communications, and vehicle-to-network (V2N) communications. It is noteworthy that the vehicle 102 may also be included in the network 200 (not shown) and communicate with the UE 206 via a sidelink. Although the embodiments described below describe sidelink communications using a V2X model, these embodiments may also be applied to other types of sidelink communications.

[0054] Figure 3 is a block diagram of a V2X communication module 300 according to an embodiment of the present disclosure. The V2X communication module 300 may be implemented by a vehicle 102 or a UE 206 (collectively referred to as a UE 206). Figure 3As shown, the V2X communication module 300 includes a V2X application layer 302, a V2X layer 304, and an AS layer 306. The V2X application layer 302 may receive data packets 308 from various applications executing on the UE 206 and pass the packets 308 to the V2X layer 304 for eventual transmission to other UEs 206.

[0055] In some aspects, the V2X layer 304 may classify the packet 308 using filters 310A-310D. The filters 310A-310D may include rules for classifying the packet 308 into QoS flows 312A-312D. For example, the packet 308 may include a service type field, such as a PSID or an ITS-AID, and the filters 310A-312D may use the service type field to classify the packet 308 into one of the QoS flows 312A-312D. The QoS flows 312A-312D may have different service levels, with some QoS flows having faster delivery than other QoS flows. In another example, the packet 308 may include a destination field, and the filters 310A-312D may use the destination field to classify the packet 308 into the QoS flows 312A-312D. In another example, the packet 308 may include a group field for multicast transmission, and the filters 310A-310D may use the group field to classify the packet 308 into the QoS flows 312A-D. In yet another example, the filters 310A-310D may be associated with a range between the transmitting and receiving UEs 206. For example, assume that UE 206a wants to communicate with UE 206b within a specific range. Therefore, the V2X layer 304 may classify the packet 308 from UE 206a to UE 206b into the QoS flow 312A using the filter 310B that is capable of sending the packet 308 within the range.

[0056] In some aspects, the AS layer 306 may receive the QoS flows 312A-312D from the V2X layer 304. The AS layer 306 may include filters 314A-C that may map the QoS flows 312A-312D to radio bearers 316A-C. For simplicity, assume that the AS layer 306 maps the QoS flows 312A-312B to the radio bearer 316A, maps the QoS flow 312C to the radio bearer 316B, and maps the QoS flow 312D to the radio bearer 316C. The radio bearers 316A-316C may transmit the packets 308 in the QoS flows 312A-D to one or more destinations, such as the receiving UE 206. The radio bearers 316A-C that transmit the packets 308 between the UEs 206 are referred to as sidelink radio bearers. In some aspects, the AS layer 306 may map the QoS flows 312A-312D to the radio bearers 316A-C based on the radio bearer mapping. The radio bearer mapping may be pre-configured in the UE 206 and stored in a mobile equipment (ME) or a universal integrated circuit card (UICC). The mapping may also be pre-configured using provisioning via an upper layer protocol. On the other hand, when the UE 206 is in idle or inactive mode, the UE 206 may receive the radio bearer mapping on the network 100, 200 via a base station broadcast (e.g., a system information block (“SIB”)). For example, when the UE 206 is in connected mode, the UE 206 may also receive the radio bearer mapping from the base station via the network 100, 200 using dedicated radio resource control (RRC) signaling.

[0057] In some embodiments, the AS layer 306 may further aggregate the radio bearers 316A-316C into L2 links 318A-318B. The L2 links 318A-318B may be identified by a source and a destination, which may be an L2 ID pair. Because the L2 links 318A-318B are identified by a source and a destination, the AS layer 306 may map different radio bearers 316A-316C to the L2 links 318A-318B according to the source and the destination. Figure 3As shown, the AS layer 306 can map the radio bearers 316A and 316B to the L2 link 318A because the radio bearers 316A and 316B have the same source and destination, and the AS layer 306 can map the radio bearer 316C to the L2 link 318B having a different source and destination than the radio bearers 316A-316B. In another example, assuming that the radio bearers 316A and 316B are part of a broadcast transmission, the AS layer 306 can map the radio bearers 316A and 316B to the L2 link 318A that sends the radio bearers 316A and 316B to all UEs 206. In another example, if the radio bearers 316A and 316B are part of a multicast transmission, the AS layer 306 can map the radio bearers 316A and 316B to the L2 link 318A that sends the radio bearers 316A and 316B to the UEs 206 included in the multicast. In yet another example, if the radio bearers 315A and 315B are part of a unicast transmission, the AS layer 306 may map the radio bearers 316A and 316B to an L2 link 318A that transmits the radio bearers 316A and 316B to the receiving UE 206 .

[0058] As described above, the radio bearers 316A and 316B may have different levels of QoS flows 312 in the same L2 link 318A. In this case, the receiving UE 206 may not be able to derive the levels of the QoS flows 312A, 312B, and 312C from the L2 link 318A. This is often a problem in V2X communications, especially in multicast communications, in which the UE 206 sends packets 308 to other UEs 206 within a certain range from the sending UE 206. For example, UE 206c may send packets 308 about an event (e.g., UE 206c is a vehicle turning right) to UEs 206d and 206f. As described above, when UEs 206d, 206f receive the packets 308, the UEs 206d, 206f may send HARQ ACK if the transmission is successful, or send HARQ NACK if the transmission is unsuccessful. Assume that UE 206d does not receive packet 308 correctly and attempts to request a retransmission from UE 206c using HARQ NACK. However, in V2X communication, UE 206d may not be able to successfully request a retransmission from UE 206c by issuing a HARQ NACK because UE 206c may not be within the range of UE 206d. Even if UE 206d issues a HARQ NACK, the request may be useless because the information (e.g., UE 206c is turning right) is irrelevant to UE 206d when UE 206d is not nearby but one kilometer away.

[0059] In some embodiments, UE 206c includes range control in QoS flow 312 so that UE 206d can send a HARQ NACK when UE 206d is within range of UE 206c. In this way, UE 206d will not unnecessarily request retransmissions and waste network resources.

[0060] As described above, different ranges may be associated with different QoS flows 312A-312D. For example, an intersection management service application may include a packet 308 in a QoS flow 312A of a UE 206c, with a range that the QoS flow 312A may reach UEs 206d, 206f near an intersection. In another example, a highway service application may include a packet 308 in a QoS flow 312B of a UE 206a, with a greater range that the QoS flow 312B may reach UE 206b when the UE 206b is far away. Thus, there may be different ranges for different types of services.

[0061] In some aspects, assume that the receiving UE 206d may need to issue a HARQ NACK to request a retransmission of a packet 308 that the UE 206d received from the UE 206c via the L2 link 318A. However, the UE 206d may need to know the range requirement to determine whether to issue a HARQ NACK, or whether the range between the UEs 206c and 206d is too large and issuing a HARQ NACK would be useless. Further assume that the L2 link 318A includes radio bearers 316A, 316B, where the radio bearer 316A includes the QoS flow 312A, and the radio bearer 316B includes the QoS flow 312B and the QoS flow 312C. In this case, the UE 206d may need to distinguish between the radio bearers 316A, 316B to determine which of the QoS flows 312A, 312B, 312C includes the packet 308. This is because the radio bearers 316A, 316B and the corresponding QoS flows 312A, 312B, 312C may have different range requirements. Thus, if the packet 308 belongs to the QoS flow 312A that meets the range requirements, the UE 206d may issue a HARQ NACK. On the other hand, if the packet 308 belongs to the QoS flow 312B or 312C that does not meet the range requirements, the UE 206d may not issue a HARQ NACK.

[0062] To differentiate the QoS flows 312, the UE 206 may be pre-configured with sidelink radio bearer (SLRB) mapping rules. The SLRB mapping rules may be configured on the UE 206, stored in a SIM card of the UE 206, or received by the UE 206 using application layer signaling from the BS 204 or another UE 206. In a non-limiting embodiment, the SLRB mapping rules may be stored in a table, a configuration file, etc. within the UE 206.

[0063] Figure 4 is a block diagram of an SLRB mapping table 400 according to an embodiment of the present disclosure. The SLRB table 400 may include multiple SLRB identifiers or SLRB IDs, such as SLRB ID 1-SLRB ID 6. The SLRB IDs may be pre-assigned, or may be added to or deleted from the SLRB table 400. The SLRB IDs may also be associated with radio bearers, one SLRB ID per radio bearer. For example, SLRB ID 1 may be associated with radio bearer 316A, and SLRB ID 2 may be associated with radio bearer 316B.

[0064] In some aspects, each SLRB ID may be associated with a rule for mapping the QoS flow 312. Example rules in the SLRB table 400 may be rules 1-6. These rules may include one or more characteristics or QoS requirements, such as packet delay budget (PDB), bit error rate (PER), UE range, prevention quality indicator (PQI), priority, etc. In addition, one of the rules may be a "catchall" rule that assigns a SLRB ID to a QoS flow 312 when the QoS flow 312 does not meet the characteristics in other rules. Example rules may be:

[0065] When the PDB of the QoS flow is > 25 milliseconds, the range is between [100 meters, 150 meters], and the priority is > 3, SLRB ID = 1.

[0066] When the PDB of the QoS flow is > 50 milliseconds, the range is between [150 meters, 200 meters], and the priority is > 5, SLRB ID = 2.

[0067] When PQI=1, 2, and the range is between [100m, 150m], SLRB ID=3.

[0068] It is important to note that the format of SLRB table 400 is exemplary and is not subject to Figure 4 or the limitations of the formats shown above.

[0069] In some aspects, the AS layer 306 may identify a rule that complies with the characteristics in the QoS flow 312A from the SLRB table 400 and identify the SLRB ID associated with the rule. Assume that the SLRB table 400 identifies a rule that maps to SLRB ID 1. In this case, the QoS flow 312A may be mapped to the radio bearer 316A. The UE 206c may then include the SLRB ID 1 in the header of the packet 308 of the QoS flow 312A. In some embodiments, the header of the packet 308 may include sidelink control information. In this case, the UE 206c sending the packet 308 may include the SLRB ID 1 in the sidelink control information (SCI) within the control resource block corresponding to the header of the packet 308. The AS layer 306 includes the SLRB ID in the header or SCI because the receiving UE 206 can read the header or SCI without parsing the rest of the packet 308.

[0070] In some aspects, the UE 206c may use a similar process to map the QoS flows 312B, 312C to the radio bearer 316B. For example, the AS layer 306 may identify a rule that matches the characteristics of the QoS flows 312B, 312C from the SLRB table 400 and identify the SLRB ID 2 associated with the rule. As described above, because the SLRB ID 2 may be associated with the radio bearer 316B, the AS layer 306 may map the QoS flows 312B, 312C to the radio bearer 316B.

[0071] As described above, UE 206c sends QoS flow 312A in radio bearer 316A to UE 206d along with radio bearer 316B in L2 link 318A. Once UE 206d receives L2 link 318A including packet 308, UE 206d can read the header of packet 308 or SCI and identify the SLRB ID. Using the SLRB ID, UE 206d can check the rule corresponding to the SLRB ID in SLRB table 400. Therefore, if UE 206d identifies that packet 308 has SLRB ID 1, UE 206d can identify that the range in the above rule is between 100 meters and 150 meters. UE 206d can also determine the distance between UE 206c and 206d. If the distance between UE 206c and 206d is between 100 meters and 150 meters, UE 206d can issue a HARQ NACK to request retransmission of QoS flow 312A. Otherwise, UE 206d does not send a HARQ NACK. In another example, if UE 206d identifies that packet 308 has SLRB ID 2, UE 206d may identify that the range in the above rule is between 150m and 200m. In this case, if the distance between UE 206c and 206d is between 100 meters and 150 meters, UE 206d may not send a HARQ NACK.

[0072] In some aspects, assume that UE 206c sends QoS flow 312A to UE 206d in radio bearer 316A using broadcast mode. Whether UE 206d issues a HARQ NACK in response to the message will depend on the characteristics of QoS flow 312A identified using SLRB ID 1. Similarly, assume that UE 206c sends QoS flow 312A to UE 206d in radio bearer 316A using groupcast mode. Whether UE 206d issues a HARQ NACK in response to the message will depend on the characteristics of QoS flow 312A identified using SLRB ID 1 and whether UE 206d is a member of the group. In addition, assume that UE 206c sends QoS flow 312A to UE 206d in radio bearer 316A using unicast mode. Whether UE 206d issues a HARQ NACK in response to the message will depend on the characteristics of QoS flow 312A identified using SLRB ID 1 and whether UE 206d is the second party in the unicast communication.

[0073] Utilizing the rules in the SLRB table 400, UEs 206 receiving broadcast, multicast, and unicast transmissions will interpret the SLRB ID and QoS requirements of a QoS flow 312 consistently, even when multiple QoS flows 312 are mapped to the same radio bearer 316. The receiving UE 206 can then determine whether to take action based on the characteristics associated with the QoS flow as described in the rules corresponding to the SLRB ID.

[0074] In some aspects, the rules in the SLRB table 400 may also indicate the type of HARQ feedback that may be used. For example, Option 1 HARQ feedback may be a NACK sent by all UEs 206 in the group in the same physical sidelink feedback channel (PSFCH) resource, while Option 2 HARQ feedback may be an ACK for different UEs 206 using different PSFCH resources.

[0075] Figure 5 is a block diagram of an exemplary UE 500 according to an embodiment of the present disclosure. As described above, the UE 500 may be the UE 206 or the vehicle 102. As shown, the UE 500 may include a processor 502, a memory 504, a SLRB module 508, a transceiver 510 including a modem subsystem 512 and a radio frequency (RF) unit 514, and one or more antennas 516. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0076] The processor 502 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0077] The memory 504 may include a cache memory (e.g., a cache memory of the processor 502), a random access memory (RAM), a magnetoresistive RAM (MRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a solid-state memory device, a hard disk drive, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 504 includes a non-transitory computer-readable medium. The memory 504 may store instructions 506. The instructions 506 may include instructions that, when executed by the processor 502, cause the processor 502 to perform the operations described herein with reference to the UE 500 in conjunction with embodiments of the present disclosure. The instructions 506 may also be referred to as code. The terms "instructions" and "code" should be broadly interpreted to include any type of (multiple) computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, processes, etc. "Instructions" and "code" may include a single computer-readable statement or multiple computer-readable statements. The memory 504 can also store Figure 4 SLRB Table 400 discussed in.

[0078] The SLRB module 508 may be used in various aspects of the present disclosure. When the UE 500 prepares a QoS flow 312 for transmission, the SLRB module 508 is configured to use the rules in the SLRB table 400 to identify the SLRB ID of the QoS flow 312 and include the SLRB ID in the SCI or header of the packet 308 before sending the packet 308. When the UE 500 is receiving the packet 308, the SLRB module 508 is configured to use the SLRB ID in the SCI or header of the packet 308 to identify the corresponding rule that matches the requirements of the QoS flow 312. As described above, the characteristics of the QoS flow 312 may match one or more rules in the SLRB table 400.

[0079] As shown, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices such as the BS 104, 204. The modem subsystem 512 may be configured to modulate and / or encode data from the memory 504 and / or the SLRB module 508 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (on outbound transmissions) from the modem subsystem 512 or a transmission originating from another source (e.g., the UE 206 or the BS 104, 204). The RF unit 514 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as integrated together in the transceiver 510, the modem subsystem 512 and the RF unit 514 may be separate devices that are coupled together at the UE 206 to enable the UE 206 to communicate with other devices.

[0080] The RF unit 514 can provide modulated and / or processed data, such as data packets (or, more generally, data messages that can contain one or more data packets and other information) to the antenna 516 for transmission to one or more other devices. According to an embodiment of the present disclosure, this may include, for example, the transmission of link switching indications and buffer status reports (BSRs). The antenna 516 may also receive data messages sent from other devices. The antenna 516 may provide received data messages for processing and / or demodulation at the transceiver 510. The antenna 516 may include multiple antennas of similar or different designs to maintain multiple transmission links. The RF unit 514 may configure the antenna 516.

[0081] Figure 6 6 is a block diagram of an exemplary BS 600 according to an embodiment of the present disclosure. As described above, BS 600 may be BS 104, 204. As shown, BS 600 may include a processor 602, a memory 604, a SLRB module 608, a transceiver 610 including a modem subsystem 612 and an RF unit 614, and one or more antennas 616. These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0082] The processor 602 may have various characteristics as a specific type of processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 602 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0083] Memory 604 may include cache memory (e.g., cache memory of processor 602), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some embodiments, memory 604 may include non-transitory computer-readable media. Memory 604 may store instructions 606. Instructions 606 may include instructions that, when executed by processor 602, cause processor 602 to perform the operations described herein. Instructions 606 may also be referred to as code, which may be broadly interpreted to include any type of (multiple) computer-readable statements, such as those described above with reference to the computer readable medium. Figure 6 The memory 604 may also store Figure 4 SLRB Table 400 discussed in.

[0084] The SLRB module 608 can be used in various aspects of the present disclosure. The BS 600 can use the SLRB module 608 to select a SLRB ID for the UE 206 to include in the QoS flow 312. The SLRB module 608 is configured to use the rules in the SLRB table 400 to identify the SLRB ID of the QoS flow 312 and include the SLRB ID in the SCI for transmission to the UE 206 or the vehicle 102. Similarly, the SLRB module 608 can also use the SLRB table 400 and the SLRB ID to identify the rules for the UE 206 or the vehicle 102. In some aspects, the SLRB module 608 can also generate a SLRB table 400 having different rules corresponding to different SLRB IDs and different characteristics of the QoS flow 312.

[0085] As shown, the transceiver 610 may include a modem subsystem 612 and an RF unit 614. The transceiver 610 may be configured to communicate bidirectionally with other devices, such as UE 206 and / or another core network element. The modem subsystem 612 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 614 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data from the modem subsystem 612 (on outbound transmissions) or from another source such as UE 120. The RF unit 614 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 610, the modem subsystem 612 and the RF unit 614 may be separate devices coupled together at the BS 104, 204 to enable the BS 104, 204 to communicate with other devices.

[0086] The RF unit 614 may provide modulated and / or processed data, such as data packets (or, more generally, data messages that may include one or more data packets and other information), to the antenna 616 for transmission to one or more other devices. According to an embodiment of the present disclosure, this may include, for example, the transmission of information to complete attachment to a network and communication with a resident UE 206. The antenna 616 may also receive data messages sent from other devices and provide received data messages for processing and / or demodulation at the transceiver 610. The antenna 616 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0087] Figure 7 1100 is a flowchart of a method 700 according to some aspects of the present disclosure. The steps of method 700 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or other suitable components for performing the steps. For example, a wireless communication device such as UE 206 or vehicle 102 may perform the steps of method 1100 using one or more components such as a processor 502, a memory 504, a SLRB module 508, a transceiver 510, a modem 512, and one or more antennas 516. As shown, method 700 includes a plurality of enumerated steps, but aspects of method 1100 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0088] At step 702, a SLRB ID for the QoS flow is selected. For example, the SLRB module 508 of the UE 206c that sends the QoS flow 312A in broadcast, multicast, or unicast mode determines the SLRB ID by mapping the characteristics in the QoS flow 312A to the rules in the SLRB table 400, and selects the SLRB ID associated with the rule that complies with the characteristics. As described above, the rules for mapping the QoS flow 312 to the SLRB ID based on the QoS characteristics are stored in the SLRB table 400. In addition, as described above, different SLRB IDs are associated with different radio bearers 316 carrying the QoS flow 312.

[0089] At step 704, the SLRB ID is inserted into the header of the packet. For example, the SLRB module 508 can insert the SLRB ID selected for the QoS flow 312A into the header of the packet 308 in the QoS flow 312A at the AS layer 306. In another example, the SLRB module 508 can insert the SLRB ID into the SCI included in the header. In addition, the SLRB module 508 can insert the SLRB ID in the header because the receiving UE 206 can read the header or the SCI without parsing the rest of the packet 308. For illustration purposes, the SLRB module 508 can map the QoS flow 312A to SLRB ID 1.

[0090] At step 706, the QoS flows are mapped to radio bearers. For example, at the AS layer 306, the SLRB module 508 may map the QoS flow 312A associated with SLRB ID 1 to the radio bearer 316A. It is worth noting that the AS layer 306 may map other QoS flows 312 (e.g., QoS flow 312B) to the radio bearer 316B. Unlike QoS flow 312A, QoS flow 312B may be associated with SLRB ID 2 and mapped to a different corresponding radio bearer 316B.

[0091] At step 708, the radio bearers are mapped to the L2 links. For example, at the AS layer 306, the SLRB module 508 may map the radio bearer 316A and other radio bearers (e.g., the radio bearer 316B) to the L2 link 318A. The radio bearer 316B may include different QoS flows, such as the QoS flow 312B, which has different QoS and different SLRB IDs, such as SLRB ID 2. However, because the radio bearers 316A and 316B include the SLRB IDs, the UE 206 receiving the packet 308 in the L2 link 318A may distinguish the QoS of the packets 308 from the different QoS flows 312A, 312B according to the SLRB IDs. In addition, the UE 206 may use the SLRB IDs to process the packets 308 from the QoS flows 312A, 312B differently because different SLRB IDs are mapped to different rules.

[0092] The QoS flows in the radio bearers are transmitted using the L2 links at step 710. For example, the radio bearers 316A and 316B are transmitted from the UE 206c to the UEs 206d, 206f via the L2 links.

[0093] Figure 8 800 according to some aspects of the present disclosure. The steps of method 800 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable components for performing these steps. For example, a wireless communication device (e.g., UE 206) may utilize one or more components (e.g., a processor 502, a memory 504, a SLRB module 508, a transceiver 510, a modem 512, and one or more antennas 516) to perform the steps of method 1100. As shown, method 700 includes a plurality of enumerated steps, but aspects of method 1100 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0094] At step 802, one or more radio bearers in an L2 link are received. For example, the receiving UE 206d, 206f may receive the L2 link 318A as part of a broadcast, multicast, or unicast transmission. As described above, the L2 link 318A may include radio bearers 316A, 316B, where the radio bearer 316A corresponds to the packet 308 with SLRB ID 1, and the radio bearer 316B corresponds to the packet 308 with SLRB ID 2.

[0095] At step 804, the packet is identified. For example, at the AS layer 306, the SLRB module 508 in the UE 206d, 206f may identify the packet 308 in the L2 link 318A. At this point, the AS layer 306 may identify whether the packet 308 is from the radio bearer 316A or 316B.

[0096] At step 806, the SLRB ID is identified. For example, the SLRB module 508 in the AS layer 306 may identify the SLRB ID from a header in the packet 308 or an SCI in the header. As described above, the SLRB module 508 may identify the SLRB ID in the packet 308 only from the header without parsing the rest of the packet 308. Specifically, the SLRB module 508 may identify that the packet 308 includes SLRB ID1 or SLRB ID 2.

[0097] At step 808, rules associated with the SLRB are identified. For example, the SLRB module 508 may identify a rule associated with the SLRB ID in the SLRB table. As described above, the rule may include characteristics of the QoS flow 312A or the QoS flow 312B. Specifically, if the SLRB ID is set to 1, the SLRB module 508 may use the SLRB table 400 to determine one or more rules corresponding to the SLRB ID 1 and that may be used to process the QoS flow 312A. Alternatively, if the SLRB ID is set to 2, the SLRB module 508 may use the SLRB table 400 to determine one or more rules corresponding to the SLRB ID 2, which may be used to process the QoS flow 312B as defined in the rules. As described above, the UE 206 may have an SLRB table 400 with the same rules, and may use the SLRB ID to access these rules. In this way, QoS flows 312A, 312B with different characteristics may be processed differently according to different rules.

[0098] At step 810, an action is determined based on the rule. For example, UE 206d may use the rule associated with QoS flow 312A to determine an action specific to the characteristics of QoS flow 312A as defined in the rule. More specifically, if the range between UE 206c and 206d is within the range characteristics of QoS flow 312A specified in the rule, UE 206d may determine an action to generate a HARQ NACK. Otherwise, UE 206d may determine an action to not generate a HARQ NACK.

[0099] Information and signals may be represented using any of a variety of different processes and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0100] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0101] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, these functions can be stored or transmitted as one or more instructions or codes on a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the above functions can be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. The features that implement the functions can also be physically located in various locations, including being distributed so that some functions are implemented in different physical locations. In addition, as used herein, including in the claims, the "or" used in the list of items (e.g., a list of items starting with a phrase such as "at least one" or "one or more") indicates a list of inclusions, so that, for example, a list of [at least one of A, B, or C] represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0102] As those skilled in the art will now appreciate, and depending on the particular application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific embodiments shown and described herein, as they are merely some examples thereof, but should be fully commensurate with the scope of the appended claims and their functional equivalents.

Claims

1. A user equipment UE for wireless communication, comprising: The processor is configured as: determining a SLRBID of a quality of service (QoS) flow according to a plurality of rules mapped to a plurality of sidelink radio bearer identifiers (SLRB IDs), wherein a rule in the plurality of rules corresponds to a characteristic of the QoS flow; inserting the determined SLRB ID into a header of a packet of the QoS flow; identifying a radio bearer using the SLRBID, wherein the radio bearer carries the packets of the QoS flow; mapping the radio bearer to an L2 link; and The transceiver is configured as: The packet of the radio bearer in the L2 link is transmitted to at least one other UE together with at least one other packet from a different QoS flow included in at least one other radio bearer having a different SLRB ID.

2. The UE according to claim 1, wherein: The UE is configured with the plurality of rules mapped to the plurality of SLRB IDs corresponding to different characteristics of different QoS flows.

3. The UE according to claim 1, wherein: The characteristic is a range between the UE and the at least one other UE.

4. The UE according to claim 1, wherein: The transceiver is further configured to receive the plurality of rules from a base station using a base station signal or dedicated broadcast signaling.

5. The UE according to claim 1, wherein: The processor is further configured to store the plurality of rules in a SLRB table in a SIM card of the UE.

6. The UE according to claim 1, wherein: The transceiver is also configured to communicate via a vehicle-to-everything V2X communication connection.

7. The UE according to claim 1, wherein: The transceiver is also configured to communicate with another UE in a unicast transmission.

8. The UE according to claim 1, wherein: The transceiver is also configured to communicate in a V2X communication connection in a multicast transmission or a broadcast transmission with at least one other UE within a preconfigured range from the UE.

9. The UE according to claim 1, wherein: In order to insert the SLRB ID into the header, the processor is further configured to insert the SLRB ID into sidelink control information SCI in the header of the packet.

10. A user equipment UE for wireless communication, comprising: The transceiver is configured as: receiving, from a second UE, at least one radio bearer in an L2 link configured to carry packets from a plurality of radio bearers corresponding to QoS flows having different characteristics; The processor is configured as: identifying a packet from the at least one radio bearer; identifying a sidelink radio bearer identifier SLRB ID from a header of the packet; identifying a rule from a plurality of rules that maps to the SLRB ID, wherein the rule includes at least one characteristic of a QoS flow associated with the packet; as well as An action is determined based on the at least one characteristic in the rule.

11. The UE according to claim 10, wherein: The processor is further configured to: Processing causes the transceiver to issue a retransmission request to the second UE.

12. The UE according to claim 10, wherein: The transceiver is further configured to receive the at least one radio bearer in the L2 link in a groupcast or broadcast transmission of the second UE within a preconfigured range from the UE.

13. The UE according to claim 10, wherein: The transceiver is further configured to receive at least one radio bearer in the L2 link in a unicast transmission from the second UE.

14. The UE according to claim 10, wherein: The UE is pre-configured with the multiple rules, or the transceiver is further configured to receive the multiple rules from a base station in a base station broadcast signal or through dedicated signaling.

15. The UE according to claim 10, wherein: In order to identify the SLRBID from the header of the packet, the processor is further configured to identify the SLRB ID from sidelink control information SCI in the header.

16. The UE according to claim 10, wherein: The at least one characteristic is a range between the UE and a second UE.

17. The UE according to claim 10, wherein: The UE and the second UE are pre-configured with the multiple rules.

18. The UE according to claim 10, wherein: The processor is further configured to store the plurality of rules in a SLRB table in a SIM card of the UE.

19. A method of wireless communication, comprising: At a first user equipment UE, determining a SLRB ID of a quality of service QoS flow according to a plurality of rules mapped to a plurality of sidelink radio bearer identifiers SLRB IDs; inserting the determined SLRB ID into a header of a packet of the QoS flow; identifying a radio bearer using the SLRBID, wherein the radio bearer carries the packets of the QoS flow; mapping the radio bearer to an L2 link; as well as The packets of the radio bearer in the L2 link are transmitted to at least one second UE together with at least one other packet from at least one other radio bearer having a different SLRB ID corresponding to a different QoS flow.

20. The method according to claim 19, wherein: The first UE and the at least one second UE are pre-configured with the plurality of rules mapped to a plurality of SLRB IDs based on different characteristics of the QoS flow.

21. The method according to claim 19, wherein: The first UE and the at least one second UE receive the plurality of rules from a base station using a base station signal or dedicated broadcast signaling.

22. The method according to claim 19, wherein: A rule of the plurality of rules maps at least one characteristic of the QoS flow.

23. The method according to claim 19, wherein: The communication is a unicast, broadcast, or multicast transmission to the at least one second UE within a preconfigured range from the first UE in a V2X communication connection.

24. The method according to claim 19, wherein: The inserting further comprises inserting the SLRB ID into sidelink control information SCI in the header of the packet.

25. A method of wireless communication, comprising: receiving, at a first user equipment UE, from a second UE, at least one radio bearer in an L2 link configured to carry packets from a plurality of radio bearers corresponding to QoS flows having different characteristics; identifying a packet from the at least one radio bearer; identifying a sidelink radio bearer identifier SLRB ID from a header of the packet; identifying a rule from a plurality of rules that maps to the SLRB ID, wherein the rule includes at least one characteristic of a QoS flow associated with the packet; as well as An action at the first UE is determined based on the at least one characteristic in the rule.

26. The method according to claim 25, further comprising: Processing the action, wherein the action causes the first UE to issue a retransmission request to the second UE.

27. The method according to claim 25, wherein: The reception using the at least one radio bearer in the L2 link is a multicast transmission, a broadcast transmission or a unicast transmission from the second UE.

28. The method according to claim 25, wherein: The first UE and the second UE are pre-configured with the plurality of rules.

29. The method according to claim 25, wherein: The first UE and the second UE receive the plurality of rules from a base station using a base station broadcast signal or using dedicated signaling.

30. The method of claim 25, storing the plurality of rules in a SLRB table in a SIM card of the first UE.

Images