Minimum communication range of MAC TB

Abstract

Apparatuses, methods, and systems for MAC TB formation and MCR selection are disclosed. One apparatus (500) includes a processor (505) that identifies (705) sidelink (“SL”) logical channel (“LCH”) data having different minimum communication ranges (“MCRs”) and multiplexes (710) the SL LCH data having different MCRs into a same medium access control (“MAC”) transport block (“TB”). The apparatus (500) includes a transceiver (525) that transmits (715) the MAC TB according to a longest MCR among the SL LCHs included in the MAC TB.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 877,802, filed July 23, 2019, entitled “MAC TB Formation and MCR Selection for V2X Communication”, by Prateek Basu Mallick, Joachim Loehr, Karthikeyan Ganesan, and Ravi Kuchibhotla, which is incorporated herein by reference. This application claims priority to International Patent Application No. PCT / CN2019 / 085478, filed May 5, 2019, entitled "SIDELINK DATA PACKET ACKNOWLEDGMENT" by Prateek Basu Mallick, Karthikeyan Ganesan, Ravi Kuchibhotla, Alexander Golitschek, Xiaodong Yu, Hyejung Jung, Joachim Loehr, and Vijay Nangia, which is incorporated herein by reference. This application also claims priority to International Patent Application No. PCT / CN2019 / 074845, filed February 12, 2019, entitled "FEEDBACK REQUEST DETERMINATION" by Prateek Basu Mallick, Xiaodong Yu, Karthikeyan Ganesan, Joachim Loehr, and Haipeng Lei, which is incorporated herein by reference. This application claims priority to U.S. Patent Application No. 16 / 866,090, filed May 4, 2020, entitled "Unicast Session Over a Direct Communication Link" by Dimitrios Karampatsis, Prateek Basu Mallick, and Joachim Loehr, which claims priority to U.S. Provisional Patent Application No. 62 / 842,406, filed May 2, 2019, also entitled "Unicast Session Over a Direct Communication Link" by Dimitrios Karampatsis, Prateek Basu Mallick, and Joachim Loehr, which are incorporated herein by reference. Technical Field

[0003] The topics disclosed herein generally relate to wireless communication, and more specifically to MAC TB formation and minimum communication range (“MCR”) selection for V2X communication. Background Technology

[0004] The following abbreviations are defined herein, and at least some of them are referenced in the following description: 3rd Generation Partnership Project (“3GPP”), 5th Generation Core Network (“5CG”), 5th Generation Quality of Service Identifier (“5QI”), 5th Generation System (“5GS”), 5th Generation Absolute Radio Channel Number (“ARFCN”), Authentication, Authorization and Accounting (“AAA”), Access and Mobility Management Function (“AMF”), Access Restricted Local Operator Services (“ARLOS”), Positive Acknowledgment (“ACK”), Application Programming Interface (“API”), Certification Authority (“AuC”), Access Layer (“AS”), Autonomous Uplink (“AUL”), AUL Downlink Feedback Information (“AUL-DFI”), Base Station (“BS”), Binary Phase Shift Keying (“BPSK”), Bandwidth Component (“BWP”), Buffer State Report (“BSR”), Cryptographic Key (“CK”), Clear Channel Assessment (“CCA”), Control Element (“C”). E”, Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Common Search Space (“CSS”), Connectivity Mode (“CM”, which is the NAS state in 5GS), Core Network (“CN”), Control Plane (“CP”), Data Radio Bearer (“DRB”), Dedicated Short Range Communications (“DSRC”), Discrete Fourier Transform Extended (“DFTS”), Downlink (“DL”), DL Control Information (“DCI”), DL Pilot Time Slots (“DwPTS”), Dual Connectivity (“DC”), Dual Registration Mode (“DR Mode”), Discontinuous Transmission (“DTX”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Licensed Assisted Access (“eLAA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Evolved Packet Core (“EPC”), Evolved Packet System (“EPS”), EPS Mobility Management (“EMM”),This refers to the NAS status in EPS, Evolved UMTS Terrestrial Radio Access (“E-UTRA”), E-UTRA Absolute Radio Channel Number (“EARFCN”), Evolved UMTS Terrestrial Radio Access Network (“E-UTRAN”), European Telecommunications Standards Institute (“ETSI”), Frame-Based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Coverage Code (“FD-OCC”), General Packet Radio Service (“GPRS”), General Public Service Identifier (“GPSI”), Protection Period (“GP”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), and hybrid... Automatic Repeat Request (“HARQ”), Home Subscriber Server (“HSS”), Home Public Land Mobile Network (“HPLMN”), Information Element (“IE”), Integrity Key (“IK”), Internet of Things (“IoT”), International Mobile Subscriber Identity (“IMSI”), Key Derivation Function (“KDF”), Licensed Assisted Access (“LAA”), Load-Based Equipment (“LBE”), Logical Channel (“LCH”), Logical Channel Priority (“LCP”), Talk-After-Listen (“LBT”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Media Access Control (“MAC”), MAC Control Element (“MACCE”), MAC Service Data Unit (“MAC”) SDU), MAC Protocol Data Unit (“MAC PDU”), Minimum Communication Range (“MCR”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Modulation and Compilation Scheme (“MCS”), Machine Type Communication (“MTC”), Multiple-Input Multiple-Output (“MIMO”), Mobile Station International Subscriber Directory Number (“MSISDN”), Multi-User Shared Access (“MUSA”), Narrowband (“NB”), Negative Acknowledgment (“NACK”) or (“NAK”), Next Generation (5G) Node-B (“gNB”), Next Generation Radio Access Network (“NG-RAN”, RAN for 5GS networks), New Radio (“NR”, 5G Radio Access Technology; also known as “5G”) NR), Next Hop (NH), Next Hop Link Counter (NCC), Non-Access Stratum (NAS), Network Open Functions (NEF), Non-Orthogonal Multiplexing Access (NOMA), Network Slice Selection Auxiliary Information (NSSAI), Operation and Maintenance System (OAM), Orthogonal Frequency Division Multiplexing (OFDM), 5QI of PC5 Interface (PQI), Packet Data Unit (PDU, used in conjunction with a PDU session), Packet Switching (PS, for example,Packet switching domain or packet switching service), Pattern Division Multiple Access (“PDMA”), Primary Cell (“PCell”), Physical Broadcast Channel (“PBCH”), Physical Cell Identifier (“PCI”), Physical Downlink Control Channel (“PDCCH”), Physical Downlink Shared Channel (“PDSCH”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Physical Sidelink Control Channel (“PSCCH”), Physical Sidelink Shared Channel (“PSSCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), Public Land Mobile Network (“PLMN”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Radio Access Network (“RAN”), Radio Access Technology (“RAT”), Radio Resource Control (RART) “RRC”, Random Access Channel (“RACH”), Random Access Response (“RAR”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Registration Area (“RA”, similar to the Tracking Area List used in LTE / EPC), Registration Management (“RM”, referring to NAS layer procedures and status), Remaining Minimum System Information (“RMSI”), Resource Extended Multiple Access (“RSMA”), Round Trip Time (“RTT”), Receive (“RX”), Radio Link Control (“RLC”), Secondary Cell (“SCell”), Shared Channel (“SCH”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Sparse Code Multiple Access (“SCMA”), System Information Block (“SIB”), Subscriber Identification Module (“SIM”), Signal-to-Interference-plus-Noise Ratio (“SINR”), Side Link (“SL”), SL Control Information (“SCI”), SL Logical Channel (“SL”) LCH”, Session Management (“SM”), Session Management Function (“SMF”), Single Network Slice Selection Auxiliary Information (“S-NSSAI”), Service Provider (“SP”), Scheduling Request (“SR”), Single Registration Mode (“SR Mode”), Probe Reference Signal (“SRS”), Synchronization Signal (“SS”), Supplementary Uplink (“SUL”), Tracking Area (“TA”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Transmission Time Interval (“TTI”), Transmission (“TX”), Unified Access Control (“UAC”), Unified Data Management (“UDM”), User Data Repository (“UDR”),This includes features such as UDM (user entity / equipment, mobile terminal) (“UE”), UE configuration update (“UCU”), UE routing policy (“URSP”), uplink (“UL”), UL control information (“UCI”), UL pilot slots (“UpPTS”), Universal Mobile Telecommunications System (“UMTS”), UMTS / Universal Subscriber Identification Module (“USIM”), UMTS Terrestrial Radio Access (“UTRA”), UMTS Terrestrial Radio Access Network (“UTRAN”), User Plane (“UP”), Ultra Reliability and Low Latency Communication (“URLLC”), Vehicle-to-Everything (“V2X”), Access to Public Land Mobile Networks (“VPLMN”), and Global Microwave Access Interoperability (“WiMAX”). As used herein, “HARQ-ACK” can collectively represent positive acknowledgment (“ACK”), negative acknowledgment (“NACK”), and discontinuous transmission (“DTX”). ACK means that the TB was correctly received, while NACK (or NAK) means that the TB was incorrectly received. DTX means that the TB was not detected.

[0005] In some wireless communication systems, V2X communication allows vehicles to communicate with the moving parts of the surrounding transportation system. Two resource allocation modes are used in LTE V2X communication, which are also considered the baseline for the corresponding resource allocation modes in NR V2X communication. Mode-1 corresponds to the V2X communication mode scheduled by the NR network. Mode-2 corresponds to the V2X communication mode scheduled by the LTE network. Mode-3 corresponds to the V2X communication mode scheduled by the NR UE. Mode-4 corresponds to the V2X communication mode scheduled by the LTE UE.

[0006] V2X considers four different interaction scenarios: vehicle-to-vehicle (“V2V”), vehicle-to-pedestrian (“V2P”), vehicle-to-infrastructure (“V2I”), and vehicle-to-network (“V2N”) communication. For V2V, two main technologies are currently being developed for short-range radio communication: IEEE Dedicated Short-Range Communication (“DSRC”, based on the IEEE 802.11p standard) and 3GPP PC5 (also known as LTE-V at the physical layer or sidelink (“SL”) standard). PC5 refers to a reference point where one UE communicates directly with another UE via a direct channel. For V2I and V2N, cellular links (i.e., cellular V2X or “C-V2X”) can be used to enable communication between vehicles and roadside equipment (roadside units, traffic lights, etc.).

[0007] The Minimum Communication Range (MCR), or minimum communication range, is the distance (range) in meters from the transmitter V2X UE (or device) within which QoS is satisfied for the actual application. The MCR is assigned by the V2X layer / application and is signaled to the Access Layer (AS) along with QoS (indicated using PQI – i.e., the 5G QoS indicator for the PC5 interface). QoS applicable to V2X messages (indicated using PQI) must be satisfied within this range. Therefore, the MCR is important in seeking HARQ feedback from the receiver UE (“Rx UE”). Summary of the Invention

[0008] A method for MAC TB formation and MCR selection is disclosed. Apparatus and systems also perform the functions of the method.

[0009] A first method for a remote unit (i.e., the UE) to form a MAC TB and select an MCR includes identifying SL LCH data with different MCRs and multiplexing the SL LCH data with different MCRs into the same MAC TB. The first method also includes transmitting the MAC TB based on the longest MCR among the SL LCHs included in the MAC TB.

[0010] A second method for remote units to use in MAC TB formation and MCR selection includes detecting temporal conflicts between SL and UL transmissions, where the remote unit does not support simultaneous transmissions on both SL and UL. The second method includes identifying the QoS priority of the SL transmission and the QoS priority of the UL transmission. The second method includes prioritizing the SL transmission over the UL transmission in response to a QoS priority less than an SL priority threshold and a QoS priority not less than a UL priority threshold.

[0011] A third method for remote units to form MAC TBs and select MCRs involves identifying LCH data for V2Xs with different destinations and multiplexing the LCH data for V2Xs with different destinations into the same MAC TB. This third method also involves transmitting the MAC TB according to a common MCR.

[0012] A fourth method for remote units to form MAC TBs and select MCRs involves multiplexing SL LCH data with different MCRs into the same MAC TB and identifying the highest priority SL LCH with the SL LCH data included in the MAC TB. This fourth method involves transmitting the MAC TB based on the MCR of the highest priority SL LCH. Attached Figure Description

[0013] A more detailed description of the embodiments briefly described above will be presented by referring to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not intended to limit the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0014] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for MAC TB formation and MCR selection;

[0015] Figure 2 This is a schematic diagram illustrating one embodiment of data transmission from two destinations (D1 and D2) when the LCH has different MCRs;

[0016] Figure 3 This is a diagram illustrating one embodiment of a V2X MAC sub-header;

[0017] Figure 4 This is a diagram illustrating one embodiment of a V2X MAC PDU;

[0018] Figure 5 This is a diagram illustrating one embodiment of a user equipment device that can be used for MAC TB formation and MCR selection; and

[0019] Figure 6 This diagram illustrates one embodiment of a network device apparatus that can be used for MAC TB formation and MCR selection;

[0020] Figure 7 This is a flowchart illustrating an embodiment of a first method that can be used for MAC TB formation and MCR selection;

[0021] Figure 8 This is a flowchart illustrating an embodiment of a second method that can be used for MAC TB formation and MCR selection;

[0022] Figure 9 This is a flowchart illustrating an embodiment of a third method that can be used for MAC TB formation and MCR selection; and

[0023] Figure 10 This is a flowchart illustrating an embodiment of a fourth method that can be used for MAC TB formation and MCR selection. Detailed Implementation

[0024] As those skilled in the art will recognize, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects.

[0025] For example, the disclosed embodiments can be implemented as hardware circuitry including custom very large-scale integration (“VLSI”) circuitry or gate arrays, existing semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, processes, or functions.

[0026] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device employs only signals for accessing the code.

[0027] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0028] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in connection with an instruction execution system, apparatus, or device.

[0029] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0030] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0031] References to "an embodiment," "embodiment," or similar language in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language appearing throughout this specification may, but not necessarily all, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0032] As used herein, a list containing the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A; only B; only C; a combination of A and B; a combination of B and C; a combination of A and C; or a combination of A, B, and C. As used herein, a list using the term “one or more” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A; only B; only C; a combination of A and B; a combination of B and C; a combination of A and C; or a combination of A, B, and C. As used herein, a list using the term “one of…” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C, excluding combinations of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C” includes one or only one of A, B, or C, excluding combinations of A, B, and C. As used in this document, “members selected from a group consisting of A, B, and C and combinations thereof” includes only A; only B; only C; combinations of A and B; combinations of B and C; combinations of A and C; or combinations of A, B, and C.

[0033] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0034] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art that implements the functions / actions specified in the flowchart and / or block diagram.

[0035] The code may also be loaded onto a computer, other programmable data processing apparatus or other device, causing a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the function / action specified in the flowchart and / or block diagram.

[0036] The flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing one or more specified logical functions.

[0037] It should also be noted that in some alternative embodiments, the functions annotated in the boxes may occur in a different order than those annotated in the figures. For example, depending on the functions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Other steps and methods are conceivable that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures.

[0038] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware, or a combination of dedicated hardware and code, that performs a specific function or action.

[0039] The description of elements in each figure may refer to elements in the preceding figures. In all figures, the same numbers refer to the same elements, and the figures include alternative embodiments of the same elements.

[0040] Generally, this disclosure describes systems, methods, and apparatuses for MAC TB formation and MCR selection for V2X communication, such as systems, methods, and apparatuses for UEs participating in V2X communication. MCR, or minimum communication range, is the distance (range) in meters from the actual applicable transmitter V2X UE (or device) where QoS satisfaction is required. MCR is assigned by the V2X layer / application and is signaled to the access layer (AS) along with QoS (indicated using PQI). Within this range, the QoS applicable to V2X messages (indicated using PQI) must be satisfied. Therefore, MCR is important in probing HARQ feedback from Rx UEs.

[0041] In some embodiments, the sender and receiver UEs provide PC5 HARQ feedback for PSSCH transmission requests made by the sender UE (i.e., the source UE) to one or more receiver UEs. For SL unicast and multicast, HARQ feedback and HARQ combinations at the physical layer can be supported. In various embodiments, HARQ-ACK feedback for PSSCH is carried via PSFCH in one or more SFCI formats under resource allocation modes 1 and 2.

[0042] When SL HARQ feedback is enabled for unicast, in non-CBG operation, if the receiving UE successfully decodes the corresponding TB, it generates HARQ-ACK. If the receiving UE fails to decode the corresponding TB after decoding the associated PSCCH targeted by the receiving UE, it generates HARQ-NACK.

[0043] When SL HARQ feedback is enabled for multicast, the use of TX-RX distance and / or RSRP is supported when deciding whether to send HARQ feedback. In non-CBG operation, two options are supported:

[0044] According to SL HARQ feedback option 1, if the receiver UE (i.e., the target UE) fails to decode the corresponding TB after decoding the associated PSCCH, it transmits HARQ-NACK on the PSFCH; otherwise, it does not transmit a signal on the PSFCH (i.e., if the Rx UE successfully decodes the corresponding TB, it does not transmit HARQ-ACK on the PSFCH).

[0045] According to SL HARQ feedback option 2, if the receiving UE (“Rx UE”) successfully decodes the corresponding TB, it transmits HARQ-ACK on the PSFCH. Additionally, if the Rx UE fails to decode the corresponding TB after decoding the associated PSCCH targeted by the receiving UE, it transmits HARQ-NACK on the PSFCH.

[0046] A NACK feedback from a UE within the MCR limit is likely to trigger a retransmission from the transmitting UE (“Tx UE”); or from an Rx UE that successfully received and decoded the transmission. Typically, in LTE-based vehicular communications as described in 3GPP TS36.331 (v15.5.0), the Tx UE prepares a TB for a specific (ProSe) destination. If, due to MCR constraints, it may not be possible to accommodate data from all LCHs belonging to the same destination within the same TB, even assuming sufficient license size, the Tx UE may need to form a separate TB for the same destination.

[0047] Given the number of V2X applications, their varying requirements, automation levels, etc., there will inevitably be many destinations that Tx UEs need to address. This, along with MCR constraints, can further multiply the number of TBs required at the Tx UE, and increase system inefficiency due to unnecessary padding. If the Tx UE cannot acquire or select resources (mode 1 or mode 2 licenses, respectively) to transmit as many TBs as it requires within its latency requirements, this is not only a waste of Tx UE processing and system physical resources, but also affects QoS satisfaction, especially in terms of latency. Therefore, resource (no)efficiency is only one aspect; another is PDB (Packet Delay Budget). If the Tx UE can only transmit one LCH to one destination on a sidelink (SL) opportunity, catering to all LCHs / destination will take longer—this could hinder, as referenced below. Figure 2 The latency requirements under discussion.

[0048] On the other hand, while a MAC TB is formed for a specific destination (e.g., an L2 destination), there is no definition of how to consider the MCR for data from each LCH that is part of the MAC TB if the MCR is different for each or some LCHs. Because these LCHs will become part of the same MAC TB after the logical channel prioritization process, the Tx UE can apply and signal only one MCR in the PSCCH (e.g., SCI).

[0049] Suboptimal selection of the MCR can lead to poor or unmet QoS for one or more V2X applications, and in some cases, MAC TB formation toward a single destination can also be inefficient. This document outlines the procedures for MAC TB formation and MCR selection for V2X communications. In particular, a V2X UE can multiplex more than one destination in the same PC5 MAC TB. Here, the Layer 1 (“L1”) identity used for filtering can be: a) a dummy value (e.g., no L1 filtering), b) the presence of the same number of L1 identities, or c) a combination of L1 identities that allow “partial” L1 filtering. Various MAC header / subheader and PDU structures for multiplexing more than one destination in the same PC5 MAC TB are described below.

[0050] For MCR determination, in one embodiment, the normal logical channel priority (“LCP”) can be determined first, and then the MCR corresponding to the highest priority LCH included in the TB can be determined. In another embodiment, the normal LCP can be determined first, and then the MCR can be determined as the MCR of the LCH with the highest MCR among the LCHs included in the TB. In other embodiments, the MCR determination can be based first on the highest priority LCH with the most available data for transmission.

[0051] In some embodiments, LCP is performed among LCHs having the same MCR. In some embodiments, LCP is performed among LCHs having the same or lower MCR. In some embodiments, one or more MAC CEs may not have an associated MCR. In some embodiments, the MCR of the combined TB is determined after TB generation using one or more of the arithmetic mean, median, or mode of the MCR values ​​corresponding to one or more LCHs that are part of the TB.

[0052] If more than one destination is multiplexed in the TB, then: a) the MCR determines to ignore the destination; b) if the destination priority has been signaled from the upper layer, the MCR determines to guide only the highest priority destination; or c) the MCR determines to guide only the highest priority projection type. In some embodiments, the V2X UE places V2X SDUs received from the upper layer in the corresponding SL radio bearer / SL LCH. The UE places only packets with the same MCR in one SL LCH / SL radio bearer.

[0053] In various embodiments, the V2X UE sends a buffer status report and initiates the acquisition of Mode 2 permission only when at least one receiving UE is present. Here, the upper layer may notify the AS layer of the number of one or more Rx UEs.

[0054] In various embodiments, the Tx UE learns the total number of Rx UEs based on upper-layer information, for example, one or more upper layers provide one or more lower layers with the total number of SL UEs in the group. Here, this knowledge at the physical layer is accurate to the extent required for the physical layer to function at any given point in time; even if group membership is updated, the physical layer is notified within a fairly fast time frame.

[0055] Figure 1A wireless communication system 100 for V2X communication, including MAC TB formation and MCR selection, is depicted according to embodiments of the present disclosure for a wireless device transmitting V2X messages 125. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may consist of a base station unit 110, with which the remote unit 105 communicates using a wireless communication link 115. Even in Figure 1 The document describes a specific number of remote units 105, base station units 110, wireless communication links 115, RAN 120, and mobile core network 140. Those skilled in the art will recognize that any number of remote units 105, base station units 110, wireless communication links 115, RAN 120, and mobile core network 140 can be included in the wireless communication system 100.

[0056] In one implementation, RAN 120 conforms to a 5G system as defined in the 3GPP specification. In another implementation, RAN 120 conforms to an LTE system as defined in the 3GPP specification. However, more generally, the wireless communication system 100 can implement other open or proprietary communication networks, such as WiMAX. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0057] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart home appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 may include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as a UE, subscriber unit, mobile phone, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art.

[0058] Remote unit 105 can communicate directly with one or more base station units 110 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals can be carried on wireless communication link 115. Here, RAN 120 is an intermediate network providing access to mobile core network 140 for remote unit 105.

[0059] In some embodiments, remote unit 105 communicates with application server 151 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., web browser, media client, telephone / VoIP application) can trigger remote unit 105 to establish a PDU session (or other data connection) with mobile core network 140 via RAN 120. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150. Note that remote unit 105 can establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 can simultaneously have at least one PDU session for communicating with packet data network 150 and at least one PDU session for communicating with another data network (not shown).

[0060] Base station unit 110 may be distributed over a geographical area. In some embodiments, base station unit 110 may also be referred to as access terminal, access point, base station, base station, Node B, eNB, gNB, home Node B, relay node, RNA node, or any other term used in the art. Base station unit 110 is typically part of radio access network 120 (“RAN”) (such as RAN 120), which may include one or more controllers communicatively coupled to one or more corresponding base station units 110. These and other elements of the radio access network are not shown but are well known to those skilled in the art. Base station unit 110 is connected to mobile core network 140 via RAN 120.

[0061] Base station unit 110 can serve multiple remote units 105 within a service area (e.g., a cell or cell sector) via wireless communication link 115. Base station unit 110 can communicate directly with one or more remote units 105 via communication signals. Typically, base station unit 110 transmits DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried on wireless communication link 115. Wireless communication link 115 can be any suitable carrier in the licensed or unlicensed radio spectrum. Wireless communication link 115 facilitates communication between one or more remote units 105 and / or one or more base station units 110.

[0062] In one embodiment, the mobile core network 140 is a 5G core (“5GC”) or an evolved packet core (“EPC”), which may be coupled to a packet data network 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with the mobile core network 140. Each mobile core network 140 belongs to a single Public Land Mobile Network (“PLMN”). This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0063] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes multiple user plane functions (“UPFs”) 145. Mobile core network 140 also includes multiple control plane functions, including but not limited to access and mobility management functions (“AMFs”) 141, session management functions (“SMFs”) 143, and policy control functions (“PCFs”) 147 serving RAN 120. In some embodiments, mobile core network 140 may also include authentication server functions (“AUSFs”), unified data management functions (“UDMs”) 149, network repository functions (“NRFs”) used by various NFs to discover and communicate with each other via APIs, or other NFs defined for 5GC.

[0064] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for certain service types or communication services. In some embodiments, various network slices may include instances of individual network functions, such as SMF 143 and UPF 145. In some embodiments, different network slices may share some common network functions, such as AMF 141. For ease of illustration, Figure 1 Different network slices are not shown, but their support is assumed.

[0065] Despite Figure 1 A specific number and type of network functions are described, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Furthermore, in the case where the mobile core network 140 is an EPC, the described network functions can be replaced with appropriate EPC entities, such as MME, S-GW, P-GW, HSS, etc. In some embodiments, the mobile core network 140 may include an AAA server.

[0066] In various embodiments, remote units 105 can communicate directly with each other using V2X communication signals 125 (e.g., device-to-device communication). Here, V2X transmissions can occur on V2X resources. As described above, different V2X communication resources can be provided to remote unit 105 for different V2X modes. Mode-1 corresponds to the V2X communication mode scheduled by the NR network. Mode-2 corresponds to the V2X communication mode scheduled by the LTE network.

[0067] Although Figure 1 The components of the 5G RAN and 5G core network are described, but the embodiments described for MAC TB formation and MCR selection for V2X communication are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfoxx, etc. For example, in LTE variants involving EPC, AMF 135 can be mapped to MME, SMF can be mapped to the control plane portion of PGW and / or MME, UPF can be mapped to SGW and user plane portion of PGW, UDM / UDR can be mapped to HSS, etc.

[0068] In the following description, the term eNB / gNB is used for the base station, but it can be replaced by any other radio access node, such as BS, eNB, gNB, AP, NR, etc. Furthermore, the operation is primarily described in the context of 5G NR. However, the proposed solution / method is equally applicable to other mobile communication systems that support serving cells / carriers configured for sidelink communication via the PC5 interface.

[0069] Figure 2 Figure 200 illustrates data delivery from two destinations (D1 and D2) in the case where the LCH has different MCRs. Here, it is assumed that a V2X application running on UE 205 has data for destinations D1 and D2 with MCRs of MCR1 and MCR2, and all data is available before the first transmission opportunity 210. In Figure 200, data for destination D2 is shaded, while data for destination D1 is not shaded. Furthermore, data with an MCR of MCR1 is indicated by the symbol '|', data with an MCR of MCR1 is indicated by the symbol 'o', and data with an MCR of MCR1 is indicated by the symbol '+'.

[0070] According to a technique, a unique packet is formed for each combination of destination and MCR. As depicted, at a first transmission opportunity 210, UE 205 may transmit a first TB 215 for destination D1 with MCR1. At a second transmission opportunity 220, UE may transmit a second TB 225 for destination D1 with MCR2. Furthermore, at a third transmission opportunity 230, UE 205 may transmit a third TB 235 for destination D2 and MCR1, and at a fourth transmission opportunity 240, transmit a fourth TB 245 for destination D2 with MCR2. This first technique introduces a first delay 250 in the transmission of data from destination D2 with MCR2 (i.e., measured as the time between the first transmission opportunity 210 and the fourth transmission opportunity 240). However, the first delay 250 may result in poor or unmet QoS for at least some V2X applications.

[0071] To improve data delivery efficiency, UE 205 can reuse data with different destinations and / or different MCRs. Various solutions for improving data delivery efficiency are described below.

[0072] According to the first solution, the transmitter UE 205 multiplexes data destined for more than one destination within the same MAC TB. This is depicted in delivery scheme 255, where data destined for destination D1 is multiplexed together with data destined for destination D2 into TB 260 and TB 265, thereby reducing delivery latency. Delivery scheme 255 allows for better packing of MAC TBs, thereby improving system efficiency, latency, and reducing resource waste in padding. Note that the embodiments presented herein apply regardless of the projection type, i.e., regardless of whether the transmission is made for one or more of unicast, multicast, and / or broadcast services. While delivery scheme 255 shows data with the same MCR grouped into the same TB (i.e., TB 260 has MCR1 and TB 265 has MCR2), in other embodiments, UE 205 may multiplex data destined for more than one destination and having more than one MCR.

[0073] According to an alternative multiplexing scheme 270, UE 205 can multiplex data with different MCRs into TB 275 and transmit TB 275 according to the longest MCR of the multiplexed data. In the depicted embodiment, it is assumed that MCR1 is a longer distance than MCR2. Therefore, even if some data (i.e., LCH3) has a shorter MCR, TB 275 is transmitted with MCR1. While delivery scheme 270 shows data with the same destination grouped into the same TB (i.e., TB 275 only has data for destination D1), in other embodiments, UE 205 can multiplex data destined for more than one destination and having multiple MCRs.

[0074] In another alternative multiplexing scheme 280, the transmitter UE 205 can multiplex data with different MCRs into TB 285 and transmit TB 285 according to the MCR of the highest priority LCH containing data in TB 285. In the depicted embodiment, it is assumed that LCH4 has a higher priority than LCH2. Therefore, even if some data (i.e., LCH2's) has a longer MCR, TB 285 is transmitted with MCR2. While delivery scheme 280 shows data with the same destination grouped into the same TB (i.e., TB 285 only contains data for destination D2), in other embodiments, UE 205 can multiplex data destined for more than one destination and having more than one MCR.

[0075] The determined MCRs are signaled to the Rx UE in the SCI. After determining their distance from the transmitter (i.e., TxUE 205), the Rx UE checks if they are within the MCRs (as received in the SCI). If so, the Rx UE provides HARQ feedback to the Tx UE 205 depending on the feedback option currently in use. If not within the signaled MCRs, the Rx UE does not provide HARQ feedback to the Tx UE 205. According to the first option, the Rx UE only transmits HARQ NACK (Option 1). According to the second option, the Rx UE transmits both HARQ ACK and HARQ NACK feedback (Option 2). The solution for assigning MCRs to MAC TBs with a single destination is described in more detail below.

[0076] Figure 3 A V2X MAC subheader 300 according to an embodiment of the present disclosure is depicted. The MAC subheader 300 can be used to implement a first solution, namely, multiplexing data destined for more than one destination within the same TB. In some embodiments, multiple Layer 2 (L2) destination IDs are carried in the MAC subheader 300. The content of the MAC subheader 300 may include the following:

[0077] V: Version of the NR V2X protocol. In the depicted embodiment, the version is indicated using a 4-bit field (e.g., bits 0-3) of the first octet ('Oct1').

[0078] SRC: This is the source ID, such as a 24-bit (3 octets) source address. This can be a single value if the same source ID applies to all destinations addressed in this MAC PDU; otherwise, it can be multiple source identities (note that...). Figure 3 The embodiments shown depict a single source ID. In the depicted embodiments, the SRC field includes the second to fourth octets.

[0079] DST: This is the destination ID, for example, a 24-bit (3 octets) destination address. In the depicted embodiment, the first DST field includes the fifth through seventh octets.

[0080] AMD: Any additional destination flags. For example, a 1-bit flag indicating whether more than one destination ID is included. If this flag is set (i.e., has a value of 'true'), then another destination ID follows (note that the first destination ID is always present). In one embodiment, a value of 'true' is indicated using a bit value of '1' and a value of 'false' is indicated using a bit value of '0'. In another embodiment, a value of 'true' is indicated using a bit value of '0' and a value of 'false' is indicated using a bit value of '1'.

[0081] In the depicted embodiment, the AMD flag is set to 'true' for both the first and second cases. Note that because the first AMD flag is set to 'true', the Rx UE knows that the second set of V, AMD, and R fields will follow the first DST field. Similarly, the Rx UE knows that the third set of V, AMD, and R fields will follow the second DST field because the second AMD flag is set to 'true'. However, in the third case, since only three DST fields exist in the MAC subheading 300, the AMD flag is set to 'false'.

[0082] R: Reserved bit.

[0083] In some embodiments, the MAC sub-header 300 includes an 'L' field (length field, in...). Figure 3 (Not depicted in the text). Note that there may be N-1 "L" fields.

[0084] Notice, Figure 3 This is just one possible implementation of the V2X MAC subheader 300. In a variant, the second and additional 'V' fields can be omitted (i.e., replaced with reserved bits) and the AMD flag appears before a specific octet.

[0085] In another variation, the 'V' and 'R' fields in the first octet are retained, but the 'V' and 'R' fields in the other octets (e.g., the eighth and twelfth octets) are replaced with a length field, which indicates the length of all data sent together in a signal for the corresponding destination. In this variation, the AMD field still exists. The final 'L' field for each destination can also be omitted in this variation.

[0086] In another variation, the 'V' and 'R' fields in the first octet are retained, but the 'V' and 'R' fields in the other octets are replaced with a subheader count field, which is used to signal the number of all subheaders sent for the corresponding destination. In this variation, the AMD field still exists. Similarly, there may be many other implementations that achieve the same purpose; only a few examples have been mentioned above.

[0087] Figure 4 An example of a MAC PDU 400 according to an embodiment of the present disclosure is depicted. Here, the MAC PDU 400 consists of a MAC header 405 and a MAC payload 410 including a plurality of MAC SDUs 430 and (optionally) padding bits (e.g., to make the MAC PDU 400 achieve a fixed size). The MAC header 405 may consist of a plurality of subheaders including (but not limited to) an SL-SCH subheader 415 and a plurality of MACPDU subheaders 420. Optionally, the MAC header 405 may include a padding subheader 425.

[0088] In various embodiments, the SL-SCH subheader 415 can be as referenced above. Figure 3 The V2X MAC subheader 300 is described. Each MAC PDU subheader 420 contains the fields R / R / E / LCID / F / L. The MAC PDU subheader corresponding to the padding consists of four header fields R / R / E / LCID. Here, fields 'R' and 'L' are as described above. Field 'E' (Extension Flag) indicates whether there is another set of fields following subheader 420. Field 'LCID' (Logical Channel ID) indicates the logical channel number. In some embodiments, the 'LCID' field has a 5-bit length. Field 'F' (Format Flag) may be used to indicate the length of the 'L' field. In various embodiments, fields E, F, and LCID have the same meaning as in 3GPP TS 36.321.

[0089] In some embodiments, it is possible to Figure 4 The two 'R' fields shown are used as a destination index of size 2 bits (i.e., there may be a total of 4 destinations). Here, the destination index (one of the 4) of the corresponding MAC SDU can be determined from the combination of the two (bit) R bits. The first DST appearing in the V2X MAC subheader is the first index, the next DST appearing in the V2X MAC subheader is the second index, and so on. If V2X data for more than four destinations needs to be reused, two 'R' bits alone will not be sufficient, and a larger destination index field will be used. In one embodiment, additional adjacent bits can be used to further shift the subsequent fields.

[0090] In some embodiments of the first solution, the receiving-side MAC layer filters out (i.e., discards) any MAC SDUs corresponding to destinations that do not belong to the RxUE. The remainder of one or more MAC SDUs (if any) is forwarded directly or indirectly through an intermediate layer to an upper layer such as the Non-Access Layer (“NAS”) or to a V2X layer including V2X application layers (e.g., Cooperation Aware Messages (“CAM”), Distributed Environment Notification Messages (“DENM”), Basic Security Messages (“BSM”), etc.).

[0091] As a first implementation of the first solution, more than one L1 ID is carried in the SCI. This allows the receiver-side physical layer to filter out irrelevant V2X transmissions, i.e., transmissions that do not go to a specific V2X UE (which may just be a V2X device). However, this first implementation can be signaling overloaded.

[0092] As a second implementation of the first solution, only one L1 ID is carried in the SCI. This L1 ID can be a dummy value when data for multiple destinations is multiplexed into the MAC TB. Here, the dummy value is (pre)configured or specified and is therefore known to both the Tx UE and any possible Rx UE. The dummy value indicates to the Rx UE that the received TB will be forwarded directly to an upper layer like NAS or directly or indirectly through an intermediate layer to a V2X layer including the V2X application layer (CAM, DENM, BSM); that is, no L1 filtering is performed. Note that in some embodiments, the MAC entity can perform L1 filtering. For example, based on the MAC subheader, the Rx UE only forwards the relevant data to a higher layer.

[0093] Alternatively, and according to some additional implementations of the first solution, only one L1 ID is carried in the SCI, and this ID can be a pre-configured or specified value known to the Tx UE and any possible Rx UE. The pre-configured value can indicate that the received TB will be forwarded to the MAC layer, where filtering is performed accordingly, for example, based on one or more destination IDs carried in the MAC header (as described above). The receiving-side MAC layer filters out (i.e., discards) MAC SDUs corresponding to destinations that do not belong to the Rx UE. The remainder of the one or more MAC SDUs (if any) should be forwarded directly or indirectly through an intermediate layer to an upper layer such as NAS (Non-Access Stratum) or to a V2X layer including the V2X application layer (CAM, DENM, BSM). However, the above implementation can be overloaded because there is no filtering at L1 and the MAC layer needs to process all incoming packets received on PC5.

[0094] As a third implementation of the first solution, only one L1 ID is carried in the SCI, and this is a combination of individual L1 IDs. As an example of the simplest operation, in the case of multiplexing two destinations together, the L1 ID in the SCI carries half of each individual L1 ID appended together (e.g., 4 MSB / LSB). Therefore, the L1 layer can perform some "partial" filtering at the L1 layer using the portions of the individual L1 IDs. As a variation, in addition to appending individual L1 IDs, bitwise operations can be used, for example, in the case of placing the first L1 ID and the second L1 ID together using one or more bitwise operations such as OR, AND, XOR, etc. Therefore, this third implementation is an intermediate zone between two earlier implementations of the first solution.

[0095] According to the second solution, UE 205 determines the MCR associated with the TB transmitted on the SL PSSCH as the MCR associated with the highest priority SL LCH for which the TB contains the MAC SDU. (Refer to the above...) Figure 2 The reuse scheme 280 discusses an example determined by the MCR according to the second solution. Note that the second solution can be applied to both MAC TBs with a single destination and MAC TBs that reuse multiple destinations, as discussed above with reference to the first solution.

[0096] In the second solution, TB formation can be completed regardless of the MCR of the MAC SDU (i.e., LCP is completed before the MCR is determined). In various embodiments, TB formation is based on the LCP procedure for SL described in 3GPP TS 36.321 and / or the LCP procedure for Uu described in 3GPP TS 38.321 and adapted to V2X, i.e., taking into account other LCH constraints that can be introduced for V2XLCH. As discussed above, UE 205 can signal the determined MCR in the sidelink control information (“SCI”), which is signaled on the SL PSSCH corresponding to the TB. It is assumed that, in addition to some potential MAC CEs, the MAC SDU of the highest priority SL LCH (i.e., the SL LCH with the highest logical channel priority) is reused first in the TB.

[0097] As a variant, in addition to logical channel priority, any characteristic of PQI (such as delay, priority, or other characteristics) can be used as the basis for determining the so-called "highest priority" LCH, the corresponding MCR of which can be used and signaled to the Rx UE.

[0098] According to the third solution, the MCR is first determined by taking the MCR of the highest priority logical channel among the LCHs that have data available for transmission (i.e., before TB generation). The third solution can be applied to both MAC TBs with a single destination and MAC TBs that multiplex multiple destinations, as discussed above with reference to the first solution.

[0099] According to one implementation of the third solution, UE 205 is only allowed to multiplex MAC SDUs of one or more SL LCHs in a TB having the same associated MCR as the MCR determined for this transport block. During the LCP procedure (i.e., the TB generation procedure), UE 205 determines the MCR associated with the TB in a first step, for example, the MCR of the SL LCH with the highest priority available for transmission. In a second step, UE 205 selects all SL LCHs with available data for transmission whose associated MCR is the same as the MCR determined in the first step. Sidelink resources are shared among the selected SL LCHs; that is, the LCP procedure is performed as usual in the selected SL LCHs, for example, similar to that done for Uu but taking into account LCH restrictions applicable to sidelink logical channels.

[0100] According to an alternative implementation of the third solution, UE 205 is only allowed to multiplex MAC SDUs of one or more SL LCHs in a TB having an associated MCR that is the same as or smaller than the MCR determined for this transport block. During the LCP procedure (i.e., the TB generation procedure), UE 205 determines the MCR associated with the TB according to the above implementation in a first step, i.e., the MCR of the SL LCH with the highest priority available for transmission. In a second step, UE 205 selects all SL LCHs with available data for transmission whose associated MCR is the same as or smaller than the MCR determined in the first step. Sidelink resources are shared among the selected SL LCHs, i.e., the LCP procedure is performed as usual within the selected SL LCHs.

[0101] According to an additional aspect of the third solution, (one or more) MAC CEs have no associated MCR and can be reused in the TB, regardless of the TB's "determined MCR". Note that the third solution differs from the second solution in when the MCR is determined (i.e., before or after the LCP process).

[0102] According to the fourth solution, UE 205 first performs LCP and TB formation, and then determines the MCR associated with the generated TB as the highest MCR (i.e., the longest distance) among the SL LCHs that reuse the MAC SDU in this TB. (Refer to the above...) Figure 2 The reuse scheme 270 discusses an example determined by the MCR according to the fourth solution. Note that the fourth solution can be applied to both MAC TBs with a single destination and MAC TBs that reuse multiple destinations, as discussed above with reference to the first solution.

[0103] According to one implementation of this solution, UE 205 generates a TB, i.e., performs an LCP procedure, and determines the associated MCR for the generated TB based on one or more MCRs associated with the SLLCH being multiplexed within the generated TB. Here, UE 205 selects the highest MCR among the one or more MCRs multiplexed within the TB. UE 205 can signal the determined MCR of the TB within the SCI.

[0104] In various embodiments, if HARQ feedback is enabled for multicast and the location information of the transmitter UE 205 is available, the transmitter UE 205 sets the communication range to the value of the longest communication range of (one or more) logical channels in the MAC PDU.

[0105] According to the fifth solution, UE 205 uses one or more of the arithmetic mean, median, or mode of the MCR values ​​corresponding to one or more LCHs that are part of the TB to determine the MCR of the combined TB. Similar to the second and fourth solutions, TB generation is completed regardless of the MCR of the MAC SDU (i.e., LCP is completed before the MCR is determined). Next, UE 205 determines the associated MCR for the generated TB based on the arithmetic mean, median, and / or mode of the MCR values ​​corresponding to the MAC SDUs that form the TB. Note that the fifth solution can be applied to both MAC TBs with a single destination and MAC TBs that reuse multiple destinations, as discussed above with reference to the first solution.

[0106] According to the sixth solution, if there are more than one destination multiplexed together in the same TB, UE 205 determines the MCR in the same manner as any (or all) of the embodiments disclosed above, regardless of the corresponding destination ID, i.e., assuming that all data that appears to be available for transmission from any LCH actually belongs to the same destination. In other words, the second, third, fourth, and fifth solutions can be applied to both MAC TBs with a single destination and MAC TBs multiplexed with multiple destinations, as discussed above with reference to the first solution.

[0107] According to the seventh solution, if multiple destinations are multiplexed together in the same TB, the MCR determination is guided only by the highest priority destination. In one embodiment, the seventh solution applies when destination priorities have been signaled from any upper layer, including V2X applications and sublayers. After identifying the highest priority destination, the MCR can be determined based on any of the following: the longest MCR of the MAC SDU for the highest priority destination, the MCR of the highest priority LCH for the highest priority destination, or the average MCR considering only the highest priority destination, according to the concepts described above in the second, fourth, and fifth solutions.

[0108] According to the eighth solution, if multiple destinations are multiplexed together in the same TB and if data for more than one projection type (unicast, multicast, and / or broadcast services) is multiplexed in the same TB, the MCR determination is guided only by the highest priority projection type. Here, UE 205 can determine the L1 identity as in some implementations of the first embodiment. Furthermore, the priority of projection types can be specified or (pre)configured. For example, if broadcast services have a higher priority than multicast services, and both broadcast and multicast services have a higher priority than unicast services, the MCR included in the broadcast service can be used. After identifying the highest priority projection type, the MCR can be determined based on any one of the following: the longest MCR of the MAC SDU for the highest priority projection type, the MCR of the highest priority LCH for the highest priority projection type, or only considering the average MCR of the highest priority projection type, according to the concepts described above in the second, fourth, and fifth solutions.

[0109] In all the above embodiments, it is assumed that each LCH only carries packets with the same MCR (otherwise the MAC would have to check every MAC SDU), so the MCR is associated with each SL LCH. According to the ninth solution, the MCR is configured for the SL LCH when the SL LCH is established (for Mode 1). Here, the MCR is attached to each packet from the higher layer, and UE 205 associates the packet with the corresponding SL radio bearer / SL LCH (similar to LTE V2X). According to the ninth solution, the UE only places packets with the same MCR in a given SL LCH / SL radio bearer.

[0110] In various embodiments, the transmitter UE 205 can request HARQ feedback for certain TBs based on QoS priority and / or MCR range. In that case, a MAC TB can be formed by only allowing the MAC layer to multiplex data from one or more LCHs that require HARQ feedback, and the SCI indicates that the TB requires HARQ feedback. Conversely, a MAC TB can be formed by multiplexing data from one or more LCHs that do not require any HARQ feedback. This technique is applicable to Tx UE 205 transmitting data to one or more destinations. UE 205 can multiplex data from one or more different LCHs with the same MCR value to form a MAC TB and require HARQ feedback; otherwise, UE 205 can multiplex data from different LCHs with different MCRs but require HARQ feedback.

[0111] In various embodiments, a logical channel configured with the parameter sl-HARQ-FeedbackEnabled set to "Enabled" and a logical channel configured with the parameter sl-HARQ-FeedbackEnabled set to "Disabled" cannot be multiplexed into the same MAC PDU.

[0112] In some embodiments, determining whether HARQ feedback is required is based on the number of Rx UEs configured to receive communication from UE 205. For example, if the target number of Rx UEs (e.g., regardless of projection type) is less than a predetermined number "N", UE 205 may request HARQ feedback. Furthermore, if the target number of Rx UEs is greater than or equal to N, UE 205 may not request HARQ feedback. The number N can be predefined or configured. In other embodiments, determining whether to request HARQ feedback is based on one or more of the following factors: the communication range corresponding to the V2X UE; the latency corresponding to the V2X UE; and / or the quality of service parameters corresponding to the V2X UE. In one embodiment, these factors may be part of a policy.

[0113] In some embodiments, UE 205 (the transmitting UE) counts the number of HARQ responses and determines the number of DTX Rx UEs if not all Rx UEs responded to the first transmission. For retransmissions, the transmitting UE determines the number of DTX receiving UEs if all receiving UEs that provided a specific HARQ NACK in response to the first transmission also responded with HARQ feedback. The transmitting UE must remember which UE provided NACK feedback in previous transmissions and / or retransmissions to appropriately determine the number of DTX receiving UEs.

[0114] In another embodiment, regardless of whether it is transmission or retransmission, if not all receiving UEs respond (e.g., ACK or NACK is not sent), the transmitter determines the number of DTX receiving UEs.

[0115] According to the tenth solution, UE 205 triggers / sends a buffer status report and initiates the acquisition of mode 2 permission only when at least one Rx UE is present for corresponding communication, as notified by the upper layer using the PC5 communication protocol or a similar protocol. Here, the upper layer notifies the access layer (“AS”) of the number of Rx UEs.

[0116] The number of Rx UEs can be determined through application-level discovery, physical layer discovery, and / or sensing procedures. Application-level discovery can be performed by determining the number of SL UEs in a group at the application level (e.g., V2X application, V2X layer) and internally notifying the access layer. Physical layer discovery can be performed by sending requests (e.g., "Who is there?" requests) to sidelink devices through a discovery mechanism at the physical layer.

[0117] The sensing process can be performed as an extension of the sensing process executed by SCI decoding. For example, each sidelink device can share its own geographic location information, relative location information, or a portion of the geographic location information identifying the relative or absolute location of the UE in its SCI (e.g., current area ID), and the remote unit 102 can decode the sidelink device SCI as part of a continuous sensing process. Furthermore, the remote unit 102 can determine the relative distance between the remote unit 102 and the sidelink devices and can determine the number of sidelink devices in a nearby area. The remote unit can include only sidelink devices with specific levels of QoS parameters (e.g., minimum communication parameters).

[0118] Additionally, based on knowledge of the total number of member UEs in the group, the physical layer of Tx UE 205 can determine the amount of feedback resources required. The required feedback resources will be determined according to the physical layer architecture still to be finalized in 3GPP. The transmitter UE that has made this determination will compare the number of group member UEs, the number of available feedback resources, and the reliability required for a specific V2X message. Reliability can be directly derived from the PQI / priority indicated by the upper layer for the corresponding packet used for transmission. As an example, if the required reliability is five "9s," for example, for "emergency trajectory alignment between UEs supporting V2X applications" and "sensor information sharing between UEs supporting V2X application scenarios," then feedback option 2 must be used only. For lower reliability requirements, if the total number of member UEs in the group is higher than the available feedback resources, option 1 can be used alone; or, a mixture of options 1 and 2 can be used.

[0119] As indicated above, the resources actually utilized for HARQ feedback can be less than the resources already determined by the transmitter. This is because only the receiver UEs within the MCR (Minimum Communication Range) are required to provide HARQ feedback. This may initially sound like a waste of resources, but it actually avoids the greater complexity that would arise if the transmitter had to know the real-time distance of every receiver UE in advance.

[0120] The following three aspects are considered for choosing between Option 1 and Option 2 (or a mixture) to reveal detailed (transmitter) UE behavior: 1) the total number of member UEs in the group, 2) the amount of available HARQ feedback resources, and 3) the reliability required for the corresponding V2X PSSCH packet transmission. Different thresholds for each of those items can lead to using any combination of the options or some mixture of those combinations.

[0121] As a first example, if Reliability > Threshold_reliability, then Option 2 is used for as many UEs as possible. In case of shortage of feedback resources, Option 1 - based on distance_threshold is used for the remaining UEs closer to the transmitter. distance_threshold is calculated as the ratio of the remaining UEs to the total receiver UEs in the group multiplied by the MCR (Minimum Communication Range).

[0122] As a second example, if Reliability < Threshold_reliability and the total number of receiver UEs in the group is greater than threshold_max_option2, then Option 1 is used.

[0123] In Mode 1 V2X communication (i.e., network-scheduled NR-based V2X), in addition to the (re)transmission resources, the transmitter UE also needs to request feedback resources from the gNB. For this reason, the transmitter UE needs to inform the gNB about the number of member UEs in the group destination where the transmitter wishes to send the scheduled V2X message(s). This information needs to be informed to the gNB together with the size, period, etc. of the V2X message for each group destination where the transmitter intends to make a transmission. This information can be carried in a message similar to the sidelink UE information and / or NR UE assistance information defined in the LTE RRC specification (i.e., 3GPP TS 36.331). These messages carry the number of member UEs in the group, the corresponding size, period, priority / VQI, etc. of the V2X message for each group for which the transmitter is interested in transmitting data to the gNB.

[0124] This document describes an eleventh solution to the priority rules for situations involving conflicts, such as between sidelink and uplink transmissions (Uu interface) in the time domain. Due to UE capabilities, UE 205 may not be able to perform both sidelink and uplink transmissions simultaneously. Therefore, some prioritization between sidelink and uplink transmissions is necessary.

[0125] According to one implementation of the eleventh scheme, prioritization is determined based on the QoS of SL transmissions and uplink transmissions on Uu (i.e., the QoS of data contained in SL TB and Uu TB). In one implementation, two thresholds are configured or pre-configured, one for SL data / QoS and the other for Uu data / QoS. Prioritization rules are defined based on these two thresholds.

[0126] For example, if SL data has a QoS priority (PQI value) below the SL-related threshold (a lower PQI value indicates a higher QoS priority) and Uu data has a higher Uu-related threshold (indicating less stringent QoS requirements for Uu data), then SL data transmission should take precedence over Uu data transmission. In cases where the SL TB contains data with high QoS priority (PQI value below the threshold) and the Uu TB contains data with high QoS requirements (QCI value below the threshold), one possible implementation could prioritize Uu data.

[0127] In various embodiments, for regular and periodic SL-BSRs, the MAC entity should:

[0128] If the parameter sl-PrioritizationThres is configured and the highest priority value of the logical channel belonging to the logical channel group (“LCG”) and containing SL data for any destination is lower than the value of the parameter sl-PrioritizationThres; and

[0129] If 1) the parameter ul-PrioritizationThres is not configured or 2) the parameter ul-PrioritizationThres is configured and the highest priority value of any LCG and logical channel containing UL data is equal to or higher than the value of parameter ul-PrioritizationThres is not configured, then for (e.g., SL) destination(s) of (one or more) LCGs.

[0130] If the buffer status reporting procedure determines that at least one BSR (i.e., indicating the amount of data in the LCH buffer) has been triggered and not canceled, and the UL license cannot accommodate an SL-BSR MAC CE containing only buffer states for all prioritized LCGs with data available for transmission plus an SL-BSR subheader, then, considering the number of bits in the UL license, UE 205 prioritizes the SL-BSR for logical channel prioritization and reports a truncated SL-BSR containing buffer states for as many prioritized LCGs with data available for transmission as possible.

[0131] When multiple QoS flows are multiplexed into a single SL LCH, it is necessary to define their corresponding QoS values / priorities and the associated PQI value of the LCH. In one possible implementation, the highest QoS flow (e.g., the flow with the lowest PQI value) is required to determine the QoS value of the SL LCH. Note that in various embodiments, lower QoS priority values ​​indicate higher priority data.

[0132] Similarly, when multiple SL LCHs are reused in an SL TB, the QoS priority / value of the TB is determined based on the QoS value of the SL LCH with the highest requirement within the SL TB. For example, the lowest PQI value among (one or more) SL LCHs within the TB determines the QoS priority / value of the TB, which is signaled as a priority value in the SCI (PSCCH) and used for SL / UL prioritization.

[0133] Figure 5 User equipment device 500, which can be used for V2X communication, is depicted according to embodiments of this disclosure for MAC TB formation and MCR selection. In various embodiments, user equipment device 500 is used to implement one or more of the solutions described above. User equipment device 500 may be an embodiment of the remote unit 105 and / or UE 205 described above. Furthermore, user equipment device 500 may include processor 505, memory 510, input device 515, output device 520, and transceiver 525.

[0134] In some embodiments, input device 515 and output device 520 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 500 may not include any input device 515 and / or output device 520. In various embodiments, user equipment device 500 may include one or more of the following: processor 505, memory 510, and transceiver 525, and may not include input device 515 and / or output device 520.

[0135] As described, transceiver 525 includes at least one transmitter 530 and at least one receiver 635. Here, transceiver 525 communicates with one or more base station units 110 and / or one or more UEs (e.g., remote unit 105). Additionally, transceiver 525 may support at least one network interface 540. In some embodiments, transceiver 525 supports a first interface (e.g., Uu interface) for communicating with a base station unit (e.g., gNB) via an access network and a second interface (e.g., PC5 interface) for direct communication with a UE via a direct channel.

[0136] In one embodiment, processor 505 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 505 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 505 executes instructions stored in memory 510 to perform the methods and routines described herein. Processor 505 is communicatively coupled to memory 510, input device 515, output device 520, and transceiver 525.

[0137] In various embodiments, processor 505 controls user equipment device 500 to implement the UE behavior described above. In some embodiments, processor 505 identifies SL LCH data with different MCRs and multiplexes SL LCH data with different MCRs into the same MAC TB. Processor 505 controls transceiver 525 to transmit the MAC TB according to the longest MCR among the SL LCHs included in the MAC TB.

[0138] In some embodiments, multiplexing SL LCH data includes multiplexing V2XLCH data with different destinations into the same MAC TB. In some embodiments, multiplexing SL LCH data includes multiplexing SL LCH data with an MCR having the same length as or shorter than the MCR of the highest priority LCH. In some embodiments, the MAC TB further multiplexes at least one MAC CE, wherein at least one MAC CE is not associated with an MCR.

[0139] In some embodiments, when an SL LCH is established, an MCR is configured for the SL LCH. In some embodiments, the MCR is indicated by a higher layer (i.e., internally) to the access layer for each QoS flow. In some embodiments, the processor 505 indicates the longest MCR among the SL LCHs included in the MAC TB within the SCI.

[0140] In some embodiments, the SL data for the MAC TB is selected from multiple LCHs. In such embodiments, processor 505 determines whether each LCH requires HARQ feedback. In some embodiments, processor 505 multiplexes SL LCH data into the same MAC TB by multiplexing data only from LCHs that require HARQ feedback. In other embodiments, processor 505 multiplexes SL LCH data into the same MAC TB by multiplexing data only from LCHs that do not require HARQ feedback.

[0141] In various embodiments, processor 505 detects a time-domain conflict between SL and UL transmissions. Here, user equipment device 500 does not support simultaneous transmission on SL and UL. Processor 505 identifies the QoS priority of SL transmissions and the QoS priority of UL transmissions. Additionally, processor 505 prioritizes SL transmissions over UL transmissions in response to a QoS priority of SL transmissions being less than an SL priority threshold and a QoS priority of UL transmissions being not less than a UL priority threshold.

[0142] In some embodiments, processor 505 prioritizes UL transmissions over SL transmissions in response to UL transmissions having a QoS priority lower than a UL priority threshold. In some embodiments, data from multiple SL LCHs is available and multiplexed into SL transmissions. In such embodiments, processor 505 identifies the QoS priority of SL transmissions by selecting the priority value of the highest priority SL LCH.

[0143] In some embodiments, data from multiple UL LCHs is available and multiplexed into the UL transmission. In such embodiments, identifying the QoS priority of the UL transmission includes selecting the priority value of the highest priority UL LCH. In various embodiments, processor 505 signals the priority value selected in the SCI transmitted on the PSCCH. In some embodiments, a lower QoS priority value indicates higher priority data.

[0144] In various embodiments, processor 505 identifies LCH data from V2X with different destinations and multiplexes the LCH data from V2X with different destinations into the same MAC TB. Transceiver 525 transmits the MAC TB according to a common MCR.

[0145] In some embodiments, the MAC TB includes multiple Layer 2 identities corresponding to different destinations. In some embodiments, a single Layer 1 identity containing a portion of the Layer 2 identities corresponding to different destinations is transmitted at the physical layer. In some embodiments, a specific Layer 1 identity is used in the SCI, indicating that Layer 1 filtering should be skipped for the MAC TB. In such embodiments, the processor 505 controls the transceiver 525 to transmit the SCI.

[0146] In some embodiments, processor 505 determines the common MCR of the MAC TB in response to multiplexing LCH data from V2X with different destinations. In some embodiments, the common MCR is determined to be the LCH corresponding to the highest priority sidelink included in the MAC TB. In some embodiments, the common MCR is determined to be the MCR of the LCH with the longest MCR among the LCHs included in the TB.

[0147] In some embodiments, the common MCR is determined without considering the destination of the MAC TB. In some embodiments, the common MCR is determined only considering the highest priority destination of the MAC TB. In some embodiments, the common MCR is determined considering the highest priority projection type of the MAC TB.

[0148] In various embodiments, processor 505 multiplexes SL LCH data with different MCRs into the same MAC TB and identifies the highest priority SL LCH with SL LCH data included in the MAC TB. Transceiver 525 transmits the MAC TB according to the MCR of the highest priority SL LCH.

[0149] In one embodiment, memory 510 is a computer-readable storage medium. In some embodiments, memory 510 includes volatile computer storage media. For example, memory 510 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 510 includes non-volatile computer storage media. For example, memory 510 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 510 includes both volatile and non-volatile computer storage media.

[0150] In some embodiments, memory 510 stores data related to MAC TB formation and MCR selection. For example, memory 510 may store LCH data, MAC PDU, TB, LCP results, MCR, etc. In some embodiments, memory 510 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 105.

[0151] In one embodiment, input device 515 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 515 may be integrated with output device 520, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 515 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 515 includes two or more different devices, such as a keyboard and a touch panel.

[0152] In one embodiment, output device 520 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 520 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 520 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 520 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., which is separate from but communicatively coupled to the rest of user equipment device 500. Furthermore, output device 520 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0153] In some embodiments, output device 520 includes one or more speakers for generating sound. For example, output device 520 may generate an audible alarm or notification (e.g., a buzzer or alert tone). In some embodiments, output device 520 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 520 may be integrated with input device 515. For example, input device 515 and output device 520 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 520 may be located near input device 515.

[0154] Transceiver 525 includes at least a transmitter 530 and at least one receiver 535. One or more transmitters 530 can be used to provide UL communication signals to base station unit 100, such as the UL transmissions described herein. Similarly, one or more receivers 535 can be used to receive DL communication signals from base station unit 100, as described herein. Although only one transmitter 530 and one receiver 535 are illustrated, user equipment device 500 can have any suitable number of transmitters 530 and receivers 535. Furthermore, the transmitter(s) 530 and receiver(s) 535 can be of any suitable type. In one embodiment, transceiver 525 includes a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum.

[0155] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 525, transmitters 530, and receivers 535 may be implemented as physically separate components that access shared hardware and / or software resources, such as network interface 540.

[0156] In various embodiments, one or more transmitters 530 and / or one or more receivers 535 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, system-on-a-chip, ASIC, or other type of hardware component. In some embodiments, one or more transmitters 530 and / or one or more receivers 535 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as a network interface 540 or other hardware components / circuit, may be integrated with any number of transmitters 530 and / or receivers 535 into a single chip. In such embodiments, transmitters 530 and receivers 535 may be logically configured as transceivers 525 using one or more common control signals or as modular transmitters 530 and receivers 535 implemented in the same hardware chip or multi-chip module.

[0157] Figure 6An embodiment of a network device apparatus 600, which can be used for MAC TB formation and MCR selection according to embodiments of the present disclosure, is depicted. In some embodiments, the network device apparatus 600 may be an embodiment of base station unit 121 and / or RAN node 305. Furthermore, the network device apparatus 600 may include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625. In some embodiments, the input device 615 and the output device 620 are combined into a single device, such as a touchscreen. In some embodiments, the network device apparatus 600 does not include any input device 615 and / or output device 620.

[0158] As described, transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, transceiver 625 communicates with one or more remote units 105. Additionally, transceiver 625 may support at least one network interface 640. In some embodiments, transceiver 625 supports a first interface (e.g., Uu interface) for communicating with a remote unit (e.g., UE) via an access network, a second interface (e.g., N2 interface) for communicating with control plane functions (e.g., SMF) in a mobile core network (e.g., 5GC), and a third interface (e.g., N3 interface) for communicating with user plane functions (e.g., UPF) in the mobile core network.

[0159] In one embodiment, processor 605 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 605 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 605 executes instructions stored in memory 610 to perform the methods and routines described herein. Processor 605 is communicatively coupled to memory 610, input device 615, output device 620, and transceiver 625.

[0160] In various embodiments, processor 605 controls network device apparatus 600 to implement the RAN node behavior described above. For example, transceiver 625 may receive scheduling requests from a V2X UE operating in mode 1 (or mode 3), and processor 605 may allocate SL resources to the requesting V2X UE.

[0161] In one embodiment, memory 610 is a computer-readable storage medium. In some embodiments, memory 610 includes volatile computer storage media. For example, memory 610 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 610 includes non-volatile computer storage media. For example, memory 610 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 610 includes both volatile and non-volatile computer storage media.

[0162] In some embodiments, memory 610 stores data related to MAC TB formation and MCR selection, such as subscriber identity, SL license, etc. In some embodiments, memory 610 also stores program code and related data, such as operating system (“OS”) or other controller algorithms operating on network device device 600, and one or more software applications.

[0163] In one embodiment, input device 615 may include any known computer input device, including a touch panel, button, keyboard, stylus, microphone, etc. In some embodiments, input device 615 may be integrated with output device 620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 615 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 615 includes two or more different devices, such as a keyboard and a touch panel.

[0164] In one embodiment, output device 620 may include any known electronically controllable display or display device. Output device 620 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 620 includes an electronic display capable of outputting visual data to a user. For example, output device 620 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 620 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, output device 620 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0165] In some embodiments, output device 620 includes one or more speakers for generating sound. For example, output device 620 may generate an audible alarm or notification (e.g., a buzzer or alert tone). In some embodiments, output device 620 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 620 may be integrated with input device 615. For example, input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of output device 620 may be located near input device 615.

[0166] As discussed above, transceiver 625 can communicate with one or more remote units and / or with one or more interoperability functions that provide access to one or more PLMNs. Transceiver 625 can also communicate with one or more network functions (e.g., in mobile core network 140). Transceiver 625 operates under the control of processor 605 to transmit and receive messages, data, and other signals. For example, processor 605 can selectively activate the transceiver (or a portion thereof) at specific times to send and receive messages.

[0167] Transceiver 625 may include one or more transmitters 630 and one or more receivers 635. In some embodiments, one or more transmitters 630 and / or one or more receivers 635 may share transceiver hardware and / or circuitry. For example, one or more transmitters 630 and / or one or more receivers 635 may share one or more antennas, one or more antenna tuners, one or more amplifiers, one or more filters, one or more oscillators, one or more mixers, one or more modulators / demodulators, power supplies, etc. In one embodiment, transceiver 625 uses different communication protocols or protocol stacks to implement multiple logical transceivers while using common physical hardware.

[0168] Figure 7 One embodiment of a method 700 for MAC TB formation and MCR selection according to embodiments of the present disclosure is depicted. In various embodiments, method 700 is performed by a UE, such as remote unit 105, UE 205 and / or user equipment device 500 as described above. In some embodiments, method 700 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0169] Method 700 begins and identifies 705 SL LCH data with different MCRs. Method 700 includes multiplexing 710 SL LCH data with different MCRs into the same MAC TB. The first method includes transmitting 715 MAC TB based on the longest MCR among the SL LCHs included in the MAC TB. Method 700 ends.

[0170] Figure 8 One embodiment of a method 800 for MAC TB formation and MCR selection according to embodiments of the present disclosure is depicted. In various embodiments, method 800 is performed by a UE, such as remote unit 105, UE 205 and / or user equipment device 500 as described above. In some embodiments, method 800 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0171] Method 800 begins and detects a time-domain conflict between 805 SL and UL transmissions, where the remote unit does not support simultaneous transmissions on SL and UL. Method 800 includes identifying the QoS priority of 810 SL transmissions. Method 800 includes identifying the QoS priority of 815 UL transmissions. Method 800 includes prioritizing SL transmissions over 820 UL transmissions in response to a QoS priority less than an SL priority threshold and a QoS priority not less than a UL priority threshold. Method 800 ends.

[0172] Figure 9 One embodiment of a method 900 for MAC TB formation and MCR selection according to embodiments of the present disclosure is depicted. In various embodiments, method 900 is performed by a UE, such as remote unit 105, UE 205 and / or user equipment device 500 as described above. In some embodiments, method 900 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0173] Method 900 begins and identifies (905) LCH data from V2X with different destinations. Method 900 includes multiplexing (910) the LCH data from V2X with different destinations into the same MAC TB. Method 900 includes transmitting (915) the MAC TB according to a common MCR. Method 900 ends.

[0174] Figure 10An embodiment of a method 1000 for MAC TB formation and MCR selection according to embodiments of the present disclosure is depicted. In various embodiments, method 1000 is performed by a UE, such as remote unit 105, UE 205 and / or user equipment device 500 as described above. In some embodiments, method 1000 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0175] Method 1000 begins by multiplexing SL LCH data with different MCRs 1005 to the same MAC TB. A fourth method involves identifying 1010 the highest priority SL LCH with SL LCH data included in the MAC TB. Method 1000 includes transmitting 1015 MAC TB based on the MCR of the highest priority SL LCH. Method 1000 ends.

[0176] This document discloses a first apparatus for MAC TB formation and MCR selection according to embodiments of the present disclosure. The first apparatus may be implemented by a UE, such as remote unit 105, UE 205, and / or user equipment apparatus 500. The first apparatus includes a transceiver and a processor that identifies SL LCH data with different MCRs and multiplexes SL LCH data with different MCRs into the same MAC TB. The processor controls the transceiver to transmit the MAC TB based on the longest MCR among the SL LCHs included in the MAC TB.

[0177] In some embodiments, multiplexing SL LCH data includes multiplexing V2X LCH data with different destinations into the same MAC TB. In some embodiments, multiplexing SL LCH data includes multiplexing SL LCH data with an MCR having the same length as or shorter than the MCR of the highest priority LCH. In some embodiments, the MAC TB further multiplexes at least one MACCE, wherein at least one MAC CE is not associated with an MCR.

[0178] In some embodiments, when an SL LCH is established, the MCR is configured for the SL LCH. In some embodiments, the MCR is indicated by a higher layer (i.e., internally) to the access layer for each QoS flow. In some embodiments, the processor indicates the longest MCR among the SL LCHs included in the MAC TB within the SCI.

[0179] In some embodiments, the SL data for the MAC TB is selected from multiple LCHs. In such embodiments, the processor determines whether each LCH requires HARQ feedback. In some embodiments, the processor multiplexes SL LCH data into the same MAC TB by multiplexing data only from LCHs that require HARQ feedback. In other embodiments, the processor multiplexes SL LCH data into the same MAC TB by multiplexing data only from LCHs that do not require HARQ feedback.

[0180] According to embodiments of this disclosure, a first method for MAC TB formation and MCR selection is disclosed herein. The first method can be performed by a UE, such as remote unit 105, UE 205, and / or user equipment device 500. The first method includes identifying SL LCH data with different MCRs and multiplexing the SL LCH data with different MCRs into the same MAC TB. The first method includes transmitting the MAC TB based on the longest MCR among the SL LCHs included in the MAC TB.

[0181] In some embodiments, multiplexing SL LCH data includes multiplexing V2X LCH data with different destinations into the same MAC TB. In some embodiments, multiplexing SL LCH data includes multiplexing SL LCH data with an MCR having the same length as or shorter than the MCR of the highest priority LCH. In some embodiments, the MAC TB further multiplexes at least one MACCE, wherein at least one MAC CE is not associated with an MCR.

[0182] In some embodiments, when the SL LCH is established, the MCR is configured for the SL LCH. In some embodiments, the MCR is indicated by a higher layer (i.e., internally) to the access layer for each QoS flow. In some embodiments, a first approach includes indicating the longest MCR among the SL LCHs included in the MAC TB in the sidelink control information.

[0183] In some embodiments, the SL data used for the MAC TB is selected from a plurality of LCHs. In such embodiments, a first method includes determining whether each LCH requires HARQ feedback. In some embodiments, multiplexing SL LCH data to the same MAC TB includes multiplexing only data from LCHs that require HARQ feedback. In other embodiments, multiplexing SL LCH data to the same MAC TB includes multiplexing only data from LCHs that do not require HARQ feedback.

[0184] This document discloses a second apparatus for MAC TB formation and MCR selection according to embodiments of the present disclosure. The second apparatus may be implemented by a UE such as remote unit 105, UE 205, and / or user equipment apparatus 500. The second apparatus includes a processor and a transceiver communicating with a radio access network. The processor detects a time-domain conflict between SL and UL transmissions. Here, the transceiver does not support simultaneous transmission on SL and UL. The processor identifies the QoS priority of the SL transmission and the QoS priority of the UL transmission. Furthermore, in response to a QoS priority of the SL transmission being less than an SL priority threshold and a QoS priority of the UL transmission not being less than a UL priority threshold, the processor prioritizes the SL transmission over the UL transmission.

[0185] In some embodiments, the processor prioritizes UL (Ultra-Low) transmissions over SL (Single-Low) transmissions in response to UL transmissions having a QoS priority lower than a UL priority threshold. In some embodiments, data from multiple SL LCHs (Single-Low) are available and multiplexed into SL transmissions. In such embodiments, the processor identifies the QoS priority of SL transmissions by selecting the priority value of the highest-priority SL LCH.

[0186] In some embodiments, data from multiple UL LCHs is available and multiplexed into the UL transmission. In such embodiments, identifying the QoS priority of the UL transmission includes selecting the priority value of the highest priority UL LCH. In various embodiments, the processor signals the selected priority value in the SCI transmitted on the PSCCH. In some embodiments, a lower QoS priority value indicates higher priority data.

[0187] According to embodiments of this disclosure, a second method for MAC TB formation and MCR selection is disclosed herein. The second method can be performed by a UE, such as remote unit 105, UE 205, and / or user equipment device 500. The second method includes detecting a temporal conflict between a SL transmission and a UL transmission, wherein the remote unit does not support simultaneous transmission on SL and UL. The second method includes identifying a QoS priority for the SL transmission and identifying a QoS priority for the UL transmission. The second method includes prioritizing the SL transmission over the UL transmission in response to a QoS priority less than an SL priority threshold and a QoS priority not less than a UL priority threshold for the UL transmission.

[0188] In some embodiments, the second method includes prioritizing UL transmissions over SL transmissions in response to a QoS priority lower than a UL priority threshold. In some embodiments, data from multiple SL LCHs is available and multiplexed into SL transmissions. In such embodiments, identifying the QoS priority of SL transmissions includes selecting the priority value of the highest priority SL LCH.

[0189] In some embodiments, data from multiple UL LCHs is available and multiplexed into the UL transmission. In such embodiments, identifying the QoS priority of the UL transmission includes selecting the priority value of the highest priority UL LCH. In various embodiments, a second method further includes signaling the selected priority value in the SCI transmitted on the PSCCH. In some embodiments, a lower QoS priority value indicates higher priority data.

[0190] This document discloses a third apparatus for MAC TB formation and MCR selection according to embodiments of the present disclosure. The third apparatus may be implemented by a UE such as remote unit 105, UE 205, and / or user equipment apparatus 500. The third apparatus includes a transceiver and a processor that identifies LCH data for V2X with different destinations and multiplexes the LCH data for V2X with different destinations to the same MAC TB. The transceiver transmits the MAC TB according to a common MCR.

[0191] In some embodiments, the MAC TB contains multiple Layer 2 identities corresponding to different destinations. In some embodiments, a single Layer 1 identity containing a portion of the Layer 2 identities corresponding to different destinations is transmitted at the physical layer. In some embodiments, a specific Layer 1 identity is used in the SCI, indicating that Layer 1 filtering should be skipped for the MAC TB. In such embodiments, the processor controls the transceiver to transmit the SCI.

[0192] In some embodiments, the processor determines the common MCR of the MACTB in response to multiplexing LCH data from V2X with different destinations. In some embodiments, the common MCR is determined to be the LCH corresponding to the highest priority sidelink included in the MACTB. In some embodiments, the common MCR is determined to be the MCR of the LCH with the longest MCR among the LCHs included in the TB.

[0193] In some embodiments, the common MCR is determined without considering the destination of the MAC TB. In some embodiments, the common MCR is determined only considering the highest priority destination of the MAC TB. In some embodiments, the common MCR is determined considering the highest priority projection type of the MAC TB.

[0194] According to embodiments of this disclosure, a third method for MAC TB formation and MCR selection is disclosed herein. The third method can be performed by a UE such as remote unit 105, UE 205, and / or user equipment device 500. The third method includes identifying LCH data for V2X with different destinations and multiplexing the LCH data for V2X with different destinations to the same MAC TB. The third method includes transmitting the MAC TB according to a common MCR.

[0195] In some embodiments, the MAC TB contains multiple Layer 2 identities corresponding to different destinations. In some embodiments, a single Layer 1 identity containing a portion of the Layer 2 identities corresponding to different destinations is transmitted at the physical layer. In some embodiments, a specific Layer 1 identity is used in the SCI, indicating that Layer 1 filtering should be skipped for the MAC TB. In such embodiments, a third method includes transmitting the SCI.

[0196] In some embodiments, the third method includes determining a common MCR of the MAC TB in response to multiplexing LCH data from V2X with different destinations. In some embodiments, the common MCR is determined to be the LCH corresponding to the highest priority sidelink included in the MAC TB. In some embodiments, the common MCR is determined to be the MCR of the LCH with the longest MCR among the LCHs included in the TB.

[0197] In some embodiments, the common MCR is determined without considering the destination of the MAC TB. In some embodiments, the common MCR is determined only considering the highest priority destination of the MAC TB. In some embodiments, the common MCR is determined considering the highest priority projection type of the MAC TB.

[0198] According to embodiments of this disclosure, a fourth means for MAC TB formation and MCR selection is disclosed herein. The fourth means may be implemented by a UE, such as remote unit 105, UE 205, and / or user equipment device 500. The fourth means includes a transceiver and a processor that multiplexes SL LCH data with different MCRs to the same MAC TB and identifies the highest priority SL LCH having SL LCH data included in the MAC TB. The transceiver transmits the MAC TB according to the MCR of the highest priority SL LCH.

[0199] According to embodiments of this disclosure, a fourth method for MAC TB formation and MCR selection is disclosed herein. The fourth method can be performed by a UE, such as remote unit 105, UE 205, and / or user equipment device 500. The fourth method includes multiplexing SL LCH data with different MCRs into the same MAC TB and identifying the highest priority SL LCH among the SL LCH data included in the MAC TB. The fourth method includes transmitting the MAC TB according to the MCR of the highest priority SL LCH.

[0200] The embodiments may be practiced in other specific forms. The described embodiments should be considered illustrative rather than restrictive in all respects. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All modifications falling within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A method of a user equipment (UE), the method comprising: identifying sidelink (SL) logical channel (LCH) data for a plurality of SL LCHs having different minimum communication ranges (MCRs), wherein the MCRs are ranges from the UE at which a quality of service (QoS) application is satisfied; determining whether each of the plurality of SL LCHs requires hybrid automatic repeat request (HARQ) feedback; multiplexing the SL LCH data for the plurality of SL LCHs into a same medium access control (MAC) transport block (TB), wherein the multiplexing comprises multiplexing the SL LCH data from only the SL LCHs that require HARQ feedback or multiplexing the SL LCH data from only the SL LCHs that do not require HARQ feedback; and transmitting the MAC TB according to a longest MCR among the SL LCHs included in the MAC TB.

2. The method of claim 1, wherein, multiplexing the SL LCH data comprises multiplexing vehicle-to-anything (V2X) logical channel data having different destinations into the same MAC TB.

3. The method of claim 1, wherein, multiplexing the SL LCH data comprises multiplexing SL LCH data having an MCR that is the same length or shorter than an MCR of a logical channel having a highest priority.

4. The method of claim 2, wherein, the MAC TB further multiplexes at least one MAC control element (CE), wherein the at least one MAC CE is not associated with an MCR.

5. The method of claim 1, wherein, the MCR is configured for a logical channel when the logical channel is established.

6. The method of claim 1, wherein, the MCR is indicated by a higher layer to an access stratum for each QoS flow.

7. The method of claim 2, further comprising: a longest MCR among the logical channels included in the MAC TB is indicated in sidelink control information.

8. A user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: identify sidelink (SL) logical channel (LCH) data for a plurality of SL LCHs having different minimum communication ranges (MCRs), wherein the MCRs are ranges from the UE at which a quality of service (QoS) application is satisfied; determine whether each of the plurality of SL LCHs requires hybrid automatic repeat request (HARQ) feedback; multiplex the SL LCH data for the plurality of SL LCHs into a same medium access control (MAC) transport block (TB), wherein the multiplexing comprises multiplexing the SL LCH data from only the SL LCHs that require HARQ feedback or multiplexing the SL LCH data from only the SL LCHs that do not require HARQ feedback; and transmit the MAC TB according to a longest MCR among the SL LCHs included in the MAC TB.

9. The UE of claim 8, wherein, the at least one processor is further configured to cause the UE to multiplex vehicle-to-anything (V2X) logical channel data having different destinations into the same MAC TB.

10. The UE of claim 8, wherein, the at least one processor is further configured to cause the UE to multiplex SL LCH data having an MCR that is the same length or shorter than an MCR of a logical channel having a highest priority.

11. The UE of claim 9, wherein, The MAC TB is further multiplexed with at least one MAC control element (CE), wherein the at least one MAC CE is not associated with the MCR.

12. The UE of claim 8, wherein, The MCR is configured for a logical channel when the logical channel is established.

13. The UE of claim 8, wherein, The MCR is indicated by a higher layer to an access stratum for each QoS flow.

14. The UE of claim 9, the at least one processor is further configured to cause the UE to indicate, in sidelink control information, a longest MCR among the logical channels included in the MAC TB.

Images