Determine uplink licenses for multiple modes

Abstract

Apparatus, methods, and systems for determining uplink licenses for multiple modes are disclosed. One method (600) includes determining (602) a first-mode uplink license corresponding to a first mode during a first time period. Determining the first-mode uplink license includes receiving the first-mode uplink license. The method (600) also includes autonomously determining (604) a second-mode uplink license corresponding to a second mode during a second time period. The second mode is different from the first mode. The method (600) further includes transmitting data using (606) the first-mode uplink license and the second-mode uplink license based on the availability of uplink licenses corresponding to the first-mode and second-mode uplink licenses.

Description

Technical Field

[0001] The topics disclosed in this article generally relate to wireless communication, and more specifically to determining uplink licenses for various modes. Background Technology

[0002] The following abbreviations are defined herein, and at least some of them are referenced in the following description: 3rd Generation Partnership Project (“3GPP”), 5G QoS Indicator (“5QI”), Acknowledgment Mode (“AM”), Backhaul (“BH”), Broadcast Multicast (“BM”), Buffer Occupancy Rate (“BO”), Base Station (“BS”), Basic Security Message (“BSM”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Portion (“BWP”), Cooperative Awareness Message (“CAM”), Channel Busy Rate (“CBR”), Component Carrier (“CC”), Common Control Channel (“CCCH”), Code Division Multiplexing (“CDM”), Control Element (“CE”), Cooperative Multipoint (“CoMP”), Demand Category (“CoR”), Control Resource Set (“CORESET”), Control Plane (“CP”), CSI-RS Resource Indicator (“CRI”), Cell RNTI (“C-RNTI”), Channel State Information (“CSI”), CSI IM (“CSI-IM”), CSI RS (“CSI-RS”), Channel Quality Indicator (“CQI”), Central Unit (“CU”), Codeword (“CW”), Downlink Assignment Index (“DAI”), Dedicated Control Channel (“DCCH”), Downlink Control Information (“DCI”), Distributed Environment Notification (“DENM”), Downlink (“DL”), Demodulation Reference Signal (“DMRS” or “DM-RS”), Data Radio Bearer (“DRB”), Dedicated Short Range Communication (“DSRC”), Distributed Unit (“DU”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Enhanced Subscriber Identification Module (… “eSIM”, Enhanced (“E”), Frequency Division Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”), Frequency Range (“FR”), 450MHz–6000MHz (“FR1”), 24250MHz–52600MHz (“FR2”), Hybrid Automatic Repeat Request (“HARQ”), Integrated Access Backhaul (“IAB”), Identity or Identifier or Marker (“ID”), Interference Measurement (“IM”), International Mobile Subscriber Identity (“IMSI”), Internet of Things (“IoT”), Internet Protocol (“IP”), Joint Transport (“JT”), Level 1 or Layer 1 (“L1”), L1 SINR (“L1-SINR”), Level 2 or Layer 2 (“L2”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel ID (“LCID”), Logical Channel Priority (“LCP”), Long Term Evolution (“LTE”), Level of Automation (“LoA”), Mode 1 and Mode 2 (“M1M2”), Media Access Control (“MAC”), Modulation and Coding Scheme (“MCS”), Multiple-Input Multiple-Output (“MIMO”), Mobile Terminal (“MT”)Machine Type Communication (“MTC”), Multi-User (“MU”), Multi-User MIMO (“MU-MIMO”), Negative Acknowledgment (“NACK”) or (“NAK”), Next Generation (“NG”), Next Generation Node B (“gNB”), New Radio (“NR”), Non-Zero Power (“NZP”), NZP CSI-RS (“NZP-CSI-RS”), Orthogonal Frequency Division Multiplexing (“OFDM”), Peak-to-Average Power Ratio (“PAPR”), Physical Broadcast Channel (“PBCH”), Physical Downlink Control Channel (“PDCCH”), Physical Downlink Shared Channel (“PDSCH”), UE-to-UE Interface (“PC5”), Policy Control Function (“PCF”), Packet Delay Budget (“PDB”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network (“PDN”), Protocol Data Unit (“PDU”), Public Land Mobile Network (“PLMN”), Precoding Matrix Indication The following are listed: ProSe Per Packet Priority (“PPPP”), ProSe Per Packet Reliability (“PPPR”), PC5 QoS Class Identifier (“PQI”), Physical Resource Block (“PRB”), Packet Switching (“PS”), Physical Side Link Control Channel (“PSCCH”), Physical Side Link Shared Channel (“PSSCH”), Phase Tracking RS (“PTRS” or “PT-RS”), Physical Uplink Shared Channel (“PUSCH”), Quasi-Co-location (“QCL”), Quality of Service (“QoS”), Random Access Channel (“RACH”), and Radio Access Network. (“RAN”), Radio Access Technology (“RAT”), Resource Element (“RE”), Rank Indicator (“RI”), Radio Link Control (“RLC”), Radio Link Fault (“RLF”), Radio Network (“RN”), Radio Network Temporary Identifier (“RNTI”), Resource Pool (“RP”), Radio Resource Control (“RRC”), Reference Signal (“RS”), Reference Signal Received Power (“RSRP”), Reference Signal Received Quality (“RSRQ”), Receive (“RX”), Secondary Cell (“SCell”), Subcarrier Spacing (“SCS”), Serving Data Unit (“SDU”), Subscriber Identification Module (“SIM”), Signal-to-Noise Ratio (“SINR”), Side Link (“SL”), Serial Number (“SN”), Scheduling Request (“SR”), SRS Resource Indicator (“SRI”), Sound Reference Signal (“SRS”), Synchronization Signal (“SS”), SS / PBCH Block (“SSB”), Transport Block (“TB”), Transmission Control Information (“TCI”), Time Division Duplex (“TDD”), Temporary Mobile Subscriber Identity (“TMSI”), Transmitted Precoding Matrix Indicator (“TPMI”), Transmit Receive Point (“TRP”), Transmit (“TX”)User Entity / Equipment (Mobile Terminal) (“UE”), Universal Integrated Circuit Card (“UICC”), Uplink (“UL”), Non-Acknowledgment Mode (“UM”), Universal Mobile Telecommunications System (“UMTS”), Subscriber Plane (“UP”), Universal Subscriber Identity Module (“USIM”), Universal Terrestrial Radio Access Network (“UTRAN”), Cellular Interface (“Uu”), Vehicle-to-Everything (“V2X”), Voice over IP (“VoIP”), Visited Public Land Mobile Network (“VPLMN”), Vehicle QoS Class Identifier (“VQI”), Vehicle RNTI (“V-RNTI”), Global Microwave Access Interoperability (“WiMAX”), Zero Power (“ZP”), and ZP CSI-RS (“ZP-CSI-RS”). As used herein, “HARQ-ACK” can collectively represent a positive response (“ACK”) and a negative response (“NAK”). ACK indicates that the TB was received correctly, while NAK indicates that the TB was received incorrectly.

[0003] In some wireless communication networks, multiple modes can be used. In such networks, one or more of these modes can be used to transmit data. Summary of the Invention

[0004] A method for determining uplink licenses for multiple modes is disclosed. Apparatus and systems also perform the functions of the apparatus. In one embodiment, the method includes determining a first-mode uplink license corresponding to a first mode during a first time period. In such an embodiment, determining the first-mode uplink license includes receiving the first-mode uplink license. In some embodiments, the method includes autonomously determining a second-mode uplink license corresponding to a second mode during a second time period. In such an embodiment, the second mode is different from the first mode. In various embodiments, the method includes transmitting data using the first-mode uplink license and the second-mode uplink license based on the availability of uplink licenses corresponding to the first-mode uplink license and the second-mode uplink license.

[0005] In one embodiment, an apparatus for determining uplink licenses for multiple modes includes a processor that: in a first time period, determines a first-mode uplink license corresponding to a first mode, wherein determining the first-mode uplink license includes receiving the first-mode uplink license; and in a second time period, autonomously determines a second-mode uplink license corresponding to a second mode, wherein the second mode is different from the first mode. In some embodiments, the apparatus includes a transmitter that transmits data using the first-mode uplink license and the second-mode uplink license based on the availability of uplink licenses corresponding to the first-mode uplink license and the second-mode uplink license. Attached Figure Description

[0006] 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 features and details using the drawings, wherein:

[0007] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for determining uplink clearance for multiple modes;

[0008] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used to determine uplink permissions for multiple modes;

[0009] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used to receive data;

[0010] Figure 4 This is a schematic flowchart illustrating one embodiment of a method for determining uplink permissions for multiple modes;

[0011] Figure 5 This is a schematic block diagram illustrating one embodiment of communication between devices in a network; and

[0012] Figure 6 This is a schematic flowchart illustrating another embodiment of a method for determining uplink permissions for multiple modes. Detailed Implementation

[0013] As those skilled in the art will understand, 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, which are generally referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can 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 can be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device only employs signals for accessing the code.

[0014] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as hardware circuitry comprising custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0015] Modules can also be implemented in code and / or software to be executed by various types of processors. An identified code module may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of an identified module do not need to be physically located together; instead, they may include unrelated instructions stored in different locations, which, when logically connected together, constitute the module and fulfill its purpose.

[0016] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and span multiple memory devices. Similarly, in this document, operational data can be identified and described within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0017] 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.

[0018] 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 compact 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.

[0019] 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, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed 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 case, 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).

[0020] 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 "including," "comprising," "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."

[0021] 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 using 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 some aspects of the embodiments.

[0022] The following description of various aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the 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. The 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 / operations specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0023] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing apparatus 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 function / operation specified in blocks or blocks of a schematic flowchart and / or schematic block diagram.

[0024] 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 functions / operations specified in blocks or blocks of flowcharts and / or block diagrams.

[0025] The schematic flowcharts and / or schematic 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 schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

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

[0027] 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 respective 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 wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block of 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, performing a specific function or operation.

[0028] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0029] Figure 1 An embodiment of a wireless communication system 100 for determining uplink clearance for multiple modes is described. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Even Figure 1 The diagram depicts a specific number of remote units 102 and network units 104, and those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0030] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), IoT devices, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals and / or remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0031] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as an access point, access terminal, base station, node-B, eNB, gNB, home node-B, RAN, relay node, device, network device, IAB node, donor IAB node, or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, etc. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0032] In one implementation, the wireless communication system 100 conforms to the 5G or NG (Next Generation) standard of the 3GPP protocol, wherein the network element 104 uses NG RAN technology for transmission. However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX and other protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0033] Network unit 104 can serve multiple remote units 102 within a service area (e.g., a cell or cell sector) via a wireless communication link. Network unit 104 transmits DL communication signals in the time domain, frequency domain, and / or spatial domain to serve the remote units 102.

[0034] In some embodiments, remote unit 102 may determine a first-mode uplink license corresponding to a first mode during a first time period. In such embodiments, determining the first-mode uplink license includes receiving the first-mode uplink license. In some embodiments, remote unit 102 may autonomously determine a second-mode uplink license corresponding to a second mode during a second time period. In such embodiments, the second mode is different from the first mode. In various embodiments, remote unit 102 may use the first-mode uplink license and the second-mode uplink license to send data based on the availability of uplink licenses corresponding to the first-mode uplink license and the second-mode uplink license. Therefore, remote unit 102 can be used to determine uplink licenses for multiple modes.

[0035] Figure 2One embodiment of a device 200 that can be used to determine uplink permissions for multiple modes is depicted. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or display 208.

[0036] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 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 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0037] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

[0038] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 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 206 includes two or more different devices such as a keyboard and a touchpad.

[0039] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual signals, auditory signals, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 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, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

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

[0041] Transmitter 210 provides UL communication signals to network unit 104, and receiver 212 receives DL communication signals from network unit 104. In one embodiment, processor 202: determines a first-mode uplink license corresponding to a first mode in a first time period, wherein determining the first-mode uplink license includes receiving the first-mode uplink license; and autonomously determines a second-mode uplink license corresponding to a second mode in a second time period, wherein the second mode is different from the first mode. In some embodiments, transmitter 210 transmits data using the first-mode uplink license and the second-mode uplink license based on the availability of uplink licenses corresponding to the first-mode uplink license and the second-mode uplink license.

[0042] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 can have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 can be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 can be part of a transceiver.

[0043] Figure 3 An embodiment of a device 300 for receiving data is depicted. Device 300 includes one embodiment of a network unit 104. Furthermore, network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It will be understood that the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0044] In various embodiments, receiver 312 receives data from remote unit 102. Although only one transmitter 310 and one receiver 312 are illustrated, network unit 104 may have any suitable number of transmitters 310 and receivers 312. Transmitters 310 and receivers 312 may be of any suitable type. In one embodiment, transmitters 310 and receivers 312 may be part of a transceiver.

[0045] In some embodiments, there are two resource allocation modes for LTE, referred to as Mode 3 and Mode 4; and two resource allocation modes for NR, referred to as Mode 1 and Mode 2. All Modes 1, 2, 3, and 4 support direct V2X communication, but the allocation of radio resources differs. In various embodiments, the cellular network allocates Mode 1 and Mode 3 resources (e.g., gNBs allocate Mode 1 resources, while eNBs allocate Mode 3 resources). In some embodiments, Modes 2 and 4 do not require cellular coverage, and the corresponding radio resources are determined autonomously (e.g., by a remote unit 102 such as a UE, vehicle, etc.). In some embodiments, the remote unit 102 autonomously determines radio resources based on a pre-configured resource pool using a distributed scheduling scheme supported by congestion control mechanisms. In various embodiments, the RAN (e.g., for UEs within coverage area) may also allocate Mode 2 and Mode 4 resources.

[0046] In some embodiments, a V2X UE may use only one mode for its transmission at any given time (e.g., mode 1 or mode 2), while in other embodiments, a V2X UE may use more than one mode simultaneously, such as to meet different requirements of V2X applications, to increase system (e.g., radio resource) efficiency and / or increase diversity.

[0047] To facilitate the simultaneous use of more than one mode, logical channels for V2X sidelink communication can be configured accordingly. In some embodiments, the RN configures mode restrictions for each SL LCH. The logical channel is configured with either mode 1 or mode 2 transmission. The UE then only considers the LCH with mode 1 transmission for its BSR, and therefore completely ignores data in other LCHs during the BSR triggering and reporting process. In various embodiments, the RN configures some logical channels with both mode 1 and mode 2 transmission (e.g., M1M2 or no specific mode restriction). Data from these logical channels can be transmitted using mode 1 as well as using mode 2. In some embodiments, the RN can configure a preferred mode for the M1M2 LCH. In such an embodiment, if mode 1 is configured as the preferred mode, the UE can maximize data transmission on that particular logical channel using only mode 1 resources. Similarly, mode 2 can be configured as the preferred transmission mode for the M1M2 LCH. Furthermore, for M1M2 LCH, if the channel used for the preferred mode is congested or in poor radio condition (e.g., if Uu is in poor radio condition for mode 1, or the resource pool for mode 2 is congested), the UE can use the non-preferred mode for transmission.

[0048] In one embodiment, the RN configures mode restrictions for each SL LCH. In such an embodiment, some logical channels can be configured for both mode 1 and mode 2 transmission (e.g., M1M2). Data from these logical channels can be transmitted using both mode 1 and mode 2. The UE can initiate resource acquisition for data transmission on a specific M1M2 configured logical channel using both mode 1 and mode 2 resources. Thus, whenever data becomes available for transmission in the second-layer buffer (e.g., PDCP, RLC, MAC) of this logical channel, the UE can: initiate a mode 2 sensing procedure (or otherwise autonomously determine uplink clearance (or available transmission resources) for mode 2), if not already initiated and search for mode 2 UL clearance; and send a scheduling request to network device 104 (e.g., using a dedicated scheduling request if configured, by initiating a RACH procedure, or by sending an SL BSR if mode 1 UL clearance is already available), such as if no mode 1 resources for transmission are already available.

[0049] In some embodiments, for actual data transmission, the UE may use a Mode 1 UL license or a Mode 2 UL license based on which UL license is available earlier in time to transmit data (e.g., the UL license that will transmit data earliest and / or fastest, or the UL license that is determined as the first UL license and is determined to be prior to the second UL license). In some embodiments, a later UL license (e.g., a UL license that is not the earliest and / or fastest to transmit data, or a UL license that is determined to be the second UL license after the first UL license) may be returned to the system (e.g., using physical-level signaling for the Mode 1 UL license, or providing an indication that the resource is not reserved via SCI signaling for the Mode 2 UL license). In various embodiments, the later license may be used for data retransmission, with or without waiting for HARQ feedback from the receiver UE.

[0050] Figure 4 This is a schematic flowchart illustrating one embodiment of a method 400 for determining uplink clearance for multiple modes. Method 400 can be performed by a remote unit 102 (e.g., a UE). In the illustrated embodiment, method 400 determines 402 that V2X data is available for the M1M2 bearer (e.g., for transmission). Then, method 400 concurrently triggers 404BSR (or otherwise determines mode 1 UL clearance, e.g., by determining that mode 1 UL clearance has been received) and initiates 406 mode 2 sensing (or otherwise determines mode 2 UL clearance, such as by randomly selecting UL resources) in response to data becoming available for the M1M2 bearer. Method 400 then uses the earlier available uplink clearance at 408. Thus, as Figure 4As shown, the UE initiates resource acquisition for both modes 1 and 2, but uses the earlier available UL license to send the request.

[0051] In some embodiments, the UE determines how much data to send for each mode, calculates the buffer state based on the UE determination, and reports the buffer state.

[0052] In one embodiment, for mode 1, the following formula can be used: [the sum of the BOs of all LCHs transmitted under mode 1] + [((the sum of the BOs of the i-th M1M2 LCH) * (the mode 1 ratio for the i-th M1M2 LCH))].

[0053] In another embodiment, for mode 2, the following formula can be used: [the sum of the BOs of all LCHs transmitted under mode 2] + [((the sum of the BOs of the i-th M1M2 LCH) * (the mode 2 ratio of the i-th M1M2 LCH))].

[0054] In the aforementioned formula, the counter "i" runs from 1 to N, where "N" is the total number of M1M2 bearers. BOs in the PDCP and RLC buffers are calculated using any suitable method. For M1M2 bearers, the UE can use a "ratio" to determine the relevant BO for mode 1 (e.g., mode 1 ratio, and the remaining BO is used to determine the mode 2 ratio). For example, if the mode 1 ratio is 40%, then 40% of the corresponding M1M2 bearer data will be considered the mode 1 BO, while the remaining 60% (e.g., mode 2 ratio) data will be considered the mode 2 BO. It is understood that the example of a mode 1 ratio of 40% and a mode 2 ratio of 60% is merely an example. For example, another ratio could be 60% as the mode 1 ratio and 40% as the mode 2 ratio. Therefore, any suitable ratio for mode 1 and mode 2 can be used. In some embodiments, the UE uses Uu and / or PC5 channel conditions, channel traffic and / or occupancy rates of the mode 1 and / or mode 2 resource pools, and / or opportunity scheduling (e.g., allocating the higher portion of the buffer for a specific mode permission for the corresponding better channel). In some embodiments, the ratio is pre-configured at the UE and / or configured at the UE by the network unit 104 (e.g., as part of a bearer configuration using RRC signaling).

[0055] In some embodiments, the BSR transmitted from the UE may include the complete BO of the M1M2 LCH. Network unit 104 may use the mode 1 ratio and / or mode 2 ratio to calculate the mode 1 BO and / or mode 2 BO. The mode 1 ratio and / or mode 2 ratio may be known at network unit 104, or the UE may indicate the mode 1 ratio and / or mode 2 ratio to network unit 104 if the UE determines the mode 1 ratio and / or mode 2 ratio (e.g., in the BSR or separately by the UE via signaling).

[0056] In some embodiments, the Mode 1 ratio and / or Mode 2 ratio may be determined (or re-determined) by the UE if one of the following occurs: data in the M1M2 LCH arrives at the L2 buffer (e.g., in PDCP and / or RLC), when Mode 1 or Mode 2 UL permission is available, or when the data available for transmission (e.g., compared to the last time point when the Mode 1 ratio and / or Mode 2 ratio were determined) changes by a certain threshold (predefined, specified, or configured by network element 104).

[0057] In some embodiments, the UE performs an LCP procedure. For LCP, the UE considers all logical channels configured to transmit data using this mode for a given mode (e.g., mode 1 or mode 2). Next, for M1M2 bearers, the UE determines the amount of V2X data to be transmitted using each of the two modes. A “ratio” similar to the BSR calculation described above can be used to allocate licenses for these bearers for each mode. For example, if the ratio for mode 1 is 40%, then 40% of the data for the corresponding M1M2 bearer will be transmitted via mode 1, while the remaining 60% (e.g., the mode 2 ratio) of data will be transmitted using mode 2. Therefore, in this example, performing LCP for mode 1 licenses will only consider 40% of the corresponding M1M2 bearer, and for mode 2 licenses, only 60% of the corresponding M1M2 bearer will be considered. However, if UL licensed resources are still available for transmission at the end of the LCP procedure but no other valid data from either of the same or higher priority logical channels is available, the remaining buffer size of the LCH can be considered for allocation (e.g., padding can be minimized). It is understood that the example of a 40% ratio for Mode 1 and a 60% ratio for Mode 2 is merely an example. For instance, another ratio could be 60% for Mode 1 and 40% for Mode 2. Therefore, any suitable ratio for Mode 1 and Mode 2 can be used. In some embodiments, the UE uses Uu and / or PC5 channel conditions, channel traffic and / or occupancy rates of the Mode 1 and / or Mode 2 resource pools, and / or opportunity scheduling (e.g., allocating the higher portion of a buffer for a specific mode license to the corresponding better channel). In some embodiments, this ratio is pre-configured at the UE and / or configured at the UE by the network element 104 (e.g., as part of a bearer configuration using RRC signaling).

[0058] In various embodiments, the Mode 1 ratio and / or Mode 2 ratio may be determined (or re-determined) by the UE if one of the following occurs: data in the M1M2 LCH arrives at the L2 buffer (e.g., in PDCP and / or RLC), when Mode 1 or Mode 2 UL permission is available, or when the data available for transmission (e.g., compared to the last time point when the Mode 1 ratio and / or Mode 2 ratio were determined) changes (by a threshold predefined, specified, or configured by network element 104).

[0059] In some embodiments, if both Mode 1 and Mode 2 licenses are available, a prioritization process can be used instead of a ratio, and it is necessary to determine which UL license resources are used for data transmitted from the M1M2 bearer. The prioritization process can use one or more of the following prioritization factors for each M1M2 bearer: 1) Always Mode 1: For a given M1M2 bearer, the network is configured to consider only the Mode 1 license if both Mode 1 and Mode 2 licenses are available; 2) Always Mode 2: For a given M1M2 bearer, the network is configured to consider only the Mode 2 license if both Mode 1 and Mode 2 licenses are available; 3) Depends on LCH priority: For a given M1M2 bearer, if the LCH priority is less than a configured (or pre-configured) value, then... Mode 2, otherwise Mode 1 (or vice versa); 4) PDB-based: If the remaining packet delay budget (e.g., part or all of the allowed end-to-end delay for the corresponding packet) is low, the UE will use the license for the M1M2 bearer, which ends earlier in time (e.g., the corresponding parameter set and / or PUSCH duration allows for earlier delivery to the RN); and / or 5) Reliability-based: For example, if the required reliability is very high (e.g., 4 nines (99.99%) or 5 nines (99.999%)), the UE will use the Mode 1 license. It is understood that one or more prioritization factors can be specified. In such embodiments, configuration or pre-configuration can override the specified priority factors for the UE.

[0060] In some embodiments, the V2X sidelink communication mode restriction on the LCH applies only to the LCP procedure (e.g., the first transmission of data). For data retransmissions (e.g., HARQ retransmissions), the UE may use UL permission (e.g., mode 1 or mode 2) that is available and / or ends earlier in time (as described herein) and better meets the required QoS of the logical channel with the highest priority in the corresponding MAC TB (e.g., mode 1 is preferred for very high reliability requirements).

[0061] In various embodiments, the UE uses packet replication to increase the reliability of V2X transmissions. The V2X bearer requiring high reliability may depend on the replication of its corresponding PQI and / or VQI. Once the UE is configured for replication by the RN (e.g., network element 104) or by the UE itself based on a pre-configuration, the UE considers replication active until explicitly disabled by the RN or when replication is disabled under certain conditions. Replication activation can also be initiated if a lower layer in the UE indicates that "n" consecutive PDCP PDU (or SDU) transmissions have failed. If this occurs, the UE can activate replication. Conversely, replication deactivation can be initiated if a lower layer in the UE indicates that "m" consecutive PDCP PDU (or SDU) transmissions have been successful. If this occurs, the UE can deactivate replication. In some embodiments, MAC, PDCP, or RRC signaling (e.g., via a new or previously used MAC CE to carry explicit indications of replication activation and / or replication deactivation for the corresponding V2X bearer) can be used to indicate replication activation and / or replication deactivation to the RN. It is understood that the numbers “n” and “m” can be configured (e.g., via signaling to the UE), pre-configured (e.g., via default configuration in the UE), specified, or otherwise implemented in the UE.

[0062] In some embodiments, replication using both Mode 1 and Mode 2 can be performed. In such an embodiment, the UE can replicate V2X data on SL licenses received for both Mode 1 and Mode 2.

[0063] In various embodiments, replication can be performed using Uu and PC5 (e.g., one or both of Mode 1 and Mode 2). In such embodiments, the UE uses UL permission to send V2X data to the RN, and uses Mode 1 or Mode 2 UL permission (e.g., PC5 permission) to send the same V2X data directly to one or more receivers. In some embodiments, the V2X data belongs to a V2X bearer configured by the RN for replication. Upon receiving V2X data, the RN can send the data to the receivers of interest or a group of receivers via unicast, multicast, or another broadcast method (e.g., using a suitable RNTI). Figure 5 The figure shows one embodiment of it.

[0064] Figure 5 This is a schematic block diagram illustrating one embodiment of communication 500 between devices in an illustrated network. The network devices include a first sidelink device 502 (e.g., remote unit 102, UE), a second sidelink device 504 (e.g., remote unit 102, UE), and a network device 506 (e.g., network unit 104, gNB). Any communication described herein may include one or more messages.

[0065] In a first communication 508, from a first sidelink device 502 to a second sidelink device 504, the first sidelink device 502 sends V2X data to the second sidelink device 504 using Mode 1 and / or Mode 2 UL permissions. In a second communication 510, from the first sidelink device 502 to a network device 506, the first sidelink device 502 sends V2X data (e.g., a copy of the V2X data sent during the first communication 508) to the network device 506 via the Uu interface. The network device 506 determines 512 whether replication is active. If replication is active, in a third communication 514, from the network device 506 to the second sidelink device 504, the network device 506 sends the V2X data (e.g., the copied data) received from the first sidelink device 502 to the second sidelink device 504. Communication 500 illustrates one embodiment of packet replication.

[0066] Other embodiments of packet replication can use any combination of replication legs (e.g., interfaces, channels, resources, or RATs). Here are some examples of paired replication legs in the format "Leg 1 – Leg 2": Mode 1 – Mode 1; Mode 1 – Mode 2; Mode 2 – Mode 2; Mode 1 – V2X on LTE Uu; Mode 2 – V2X on LTE Uu; Mode 1 – V2X on NR Uu; Mode 2 – V2X on NR Uu; V2X on NR Uu – V2X on LTE Uu; or any combination of the above not enumerated.

[0067] In some embodiments, replication is implemented in the PDCP layer of the UE. If replication is activated, the PDCP can replicate the PDCPPDU to more than one linked RLC entity. The MAC entity in the UE can ensure that the replicated RLC PDU is sent to different carriers or on sufficiently separate resources (e.g., resource pools) to facilitate frequency diversity. If the two branches used for replication terminate in two different RATs, the MAC entity disposing of the replication can transparently transmit them on different channels and / or RATs.

[0068] In various embodiments, the PDCP can use security keys, such as security keys for PC5 security. In such embodiments, the RN can use a PC5 security security key suitable for that particular transport UE to decrypt and check the integrity protection of V2X data configured for replication of the V2X bearer. It is understood that the security key can be available to the gNB from the V2X server and / or upper layers including the non-access stratum and / or directly / indirectly from the corresponding V2X application such as CAM, DENM, BSM, etc.

[0069] In some embodiments, if the required reliability for one or more V2X messages received from the upper layer is very high (e.g., four nines (99.99%) or five nines (99.999%)), the UE may initiate an RRC connection establishment procedure and request Mode 1 resources from the RN. For this purpose, a new RRC connection establishment procedure triggering event (e.g., a cause value) may be used. The RN may use this RRC connection establishment procedure triggering event for access control purposes. It is understood that access control parameters for NR V2X Mode 1 may be broadcast in the V2X system information. In some embodiments, if the RRC connection request is triggered by Mode 1, the UE may execute an access control procedure. The access control procedure may be executed before the RACH procedure and the RRC connection request are issued. In various embodiments, an RRC connection rejection procedure may be used. If congestion exists in resources and / or processing, the RN may reject the RRC connection request and send the RRC connection rejection back to the V2X UE. A new RRC connection establishment reason (such as a specific LCID (in the MAC) of the CCCH or DCCH message and / or a reserved PRACH parameter) can be used to send a request to the RN to establish an RRC connection and / or Mode 1 resources. The RN can use appropriate indications to control access to such a request (allow or deny). Upon receiving an RRC connection denial, the UE can use Mode 2 for additional V2X communication.

[0070] In some embodiments, the UE may exhibit new behaviors in response to a lack of network coverage (e.g., RLF). In such embodiments, the access layer may notify upper layers of possible changes in the QoS implementation, indicating that Uu-based (e.g., Mode 1) scheduling is no longer available. The upper layer may take actions including terminating one or more existing QoS flows, replacing one or more QoS flows, and / or establishing one or more QoS flows. The access layer may then execute QoS flows with updated bearer mappings (e.g., no longer mapping old QoS flows to bearers and mapping new QoS flows to bearers carrying packets with the same and / or similar PQI and / or VQI for a specific target L2 destination). Mode 1 bearers are mapped to Mode 2-based transports and may use abnormal or normal Mode 2 resource pools pre-configured to the UE or broadcast by the current and / or previous serving cells. In some embodiments, Mode 1 bearers are dropped (e.g., if the corresponding QoS flow is dropped by the upper layer or simply dropped directly at the access layer).

[0071] Figure 6This is a schematic flowchart illustrating another embodiment of a method 600 for determining uplink clearance for multiple modes. In some embodiments, method 600 is performed by a device such as remote unit 102. In some embodiments, method 600 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0072] Method 600 may include determining 602 a first-mode uplink license corresponding to a first mode during a first time period. In such embodiments, determining the first-mode uplink license includes receiving the first-mode uplink license. In some embodiments, method 600 includes autonomously determining 604 a second-mode uplink license corresponding to a second mode during a second time period. In such embodiments, the second mode is different from the first mode. In various embodiments, method 600 includes using 606 the first-mode uplink license and the second-mode uplink license to transmit data based on the availability of uplink licenses corresponding to the first-mode uplink license and the second-mode uplink license.

[0073] In some embodiments, the second time period overlaps with the first time period. In some embodiments, method 600 further includes retransmitting data using a first mode, a second mode, or a combination thereof, based on the earliest available license time, quality of service requirements, or a combination thereof. In various embodiments, determining the first mode uplink license includes triggering a buffer status report.

[0074] In one embodiment, method 600 further includes calculating a buffer status report based on a buffer occupancy rate corresponding to at least one logical channel configured to use a first mode. In some embodiments, the at least one logical channel includes an exclusive logical channel limited to the first mode. In some embodiments, the at least one logical channel includes a shared logical channel configured to use both the first and second modes.

[0075] In various embodiments, the buffer occupancy rate comprises a portion of a first buffer occupancy rate corresponding to an exclusive logical channel and a portion of a second buffer occupancy rate corresponding to a shared logical channel. In one embodiment, a portion of the second buffer occupancy rate is determined based on the ratio between a first mode and a second mode for each shared logical channel. In some embodiments, the ratio is determined based on a configured ratio, a pre-configured ratio, or a calculated ratio. In one calculation, the UE may determine the time taken for successful delivery of each mode 1 and mode 2 transmission over a certain time period. The transmission ratio of the time taken for successful delivery can then be used as the determined ratio. For example, if the average time for successful delivery for mode 1 and mode 2 is 5 ms and 10 ms, respectively, then mode 1 can be used to send twice the amount of packets (e.g., in bytes) compared to the amount of packets sent using mode 1. Therefore, the ratio between mode 1 and mode 2 is 1:2 or 33% to 67%. Another calculation of the ratio may depend on channel conditions. For example, if the PC5 channel is better than a certain threshold (based on using CBR), it will send x% of the data. Similarly, if the Uu and / or Mode 1 resource pools exceed a certain threshold (for Uu using RSRP / QoS and for Mode 2 resource pools using CBR), then it will send y% of the data. Other calculations include using only one mode for a certain V2X data buffer size threshold, and then using both modes if the buffer grows, either instructing the RN to send 100% BO or splitting the BO using a ratio. Changes in buffer data within the buffers carried by M1M2 exceeding a certain threshold can be used as a new trigger for calculating and / or reporting a BSR to the RN.

[0076] In some embodiments, the ratio is determined based on a configured ratio or a calculated ratio. In various embodiments, the calculated ratio is calculated based on PC5 channel conditions, Uu channel conditions, PC5 channel delay, Uu channel delay, the amount of data in the buffer, a comparison between the amount of data and a threshold, or some combination thereof.

[0077] In some embodiments, a first-mode uplink license is available at a first time, and a second-mode uplink license is available at a second time. Using the first-mode uplink license and the second-mode uplink license to send data based on uplink license availability includes: using the first-mode uplink license if the first time is earlier than the second time, or using the second-mode uplink license if the second time is earlier than the first time. In various embodiments, method 600 further includes discarding the first-mode uplink license if the second time is earlier than the first time, or discarding the second-mode uplink license if the first time is earlier than the second time. In one embodiment, method 600 further includes: using the first-mode uplink license for data retransmission if the second time is earlier than the first time; or using the second-mode uplink license for data retransmission if the first time is earlier than the second time.

[0078] In some embodiments, method 600 further includes performing packet replication by transmitting a copy of data using a first mode, a second mode, vehicle-to-everything transmission, or some combination thereof. In some embodiments, method 600 further includes receiving information instructing the performance of packet replication. In various embodiments, method 600 further includes determining whether to perform packet replication.

[0079] In one embodiment, method 600 further includes: in response to determining that packet replication will be performed, sending information indicating that packet replication will be performed. In some embodiments, method 600 further includes initiating a radio resource control connection establishment based on reliability requirements. In some embodiments, method 600 further includes determining a radio link failure.

[0080] In various embodiments, method 600 further includes modifying the Quality of Service (QoS) flow based on a radio link failure. In one embodiment, modifying the QoS flow includes terminating one or more QoS flows, establishing one or more QoS flows, discarding a first-mode bearer, or some combination thereof. In some embodiments, determining a second-mode uplink license includes randomly selecting resources for the second-mode uplink license. In some embodiments, determining a second-mode uplink license includes performing a sensing process.

[0081] In various embodiments, method 600 further includes performing a logical channel prioritization process based on at least one logical channel configured to transmit data using a first mode, a second mode, or a combination thereof. In one embodiment, the at least one logical channel includes a shared logical channel configured to use a first mode and a second mode. In some embodiments, each shared logical channel includes a ratio indicating a first portion of the logical channel used to transmit data using the first mode and a second portion of the logical channel used to transmit data using the second mode.

[0082] In some embodiments, the ratio is determined based on a configured ratio or a calculated ratio. In various embodiments, the calculated ratio is calculated based on PC5 channel conditions, Uu channel conditions, PC5 channel delay, Uu channel delay, the amount of data in the buffer, a comparison between the amount of data and a threshold, or some combination thereof.

[0083] In one embodiment, a method includes: determining a first mode uplink license corresponding to a first mode in a first time period, wherein determining the first mode uplink license includes receiving the first mode uplink license; autonomously determining a second mode uplink license corresponding to a second mode in a second time period, wherein the second mode is different from the first mode; and using the first mode uplink license and the second mode uplink license to send data based on the availability of uplink licenses corresponding to the first mode uplink license and the second mode uplink license.

[0084] In some embodiments, the second time period overlaps with the first time period.

[0085] In some embodiments, the method further includes retransmitting the data using the first mode, the second mode, or a combination thereof, based on the earliest available license time, quality of service requirements, or a combination thereof.

[0086] In various embodiments, determining the first mode uplink permission includes triggering a buffer status report.

[0087] In one embodiment, the method further includes calculating the buffer status report based on the buffer occupancy rate corresponding to at least one logical channel configured to use the first mode.

[0088] In some embodiments, the at least one logical channel includes an exclusive logical channel limited to the first mode.

[0089] In some embodiments, the at least one logical channel includes a shared logical channel configured to use the first mode and the second mode.

[0090] In various embodiments, the buffer occupancy rate includes the sum of a portion of a first buffer occupancy rate corresponding to the exclusive logical channel and a portion of a second buffer occupancy rate corresponding to the shared logical channel.

[0091] In one embodiment, a portion of the second buffer occupancy rate is determined based on the ratio between the first mode and the second mode of each shared logical channel in the shared logical channel.

[0092] In some embodiments, the ratio is determined based on a configured ratio or a calculated ratio.

[0093] In various embodiments, the calculated ratio is based on PC5 channel status, Uu channel status, PC5 channel delay, Uu channel delay, the amount of data in the buffer, a comparison between the amount of data and a threshold, or some combination thereof.

[0094] In some embodiments, the first mode uplink license is available at a first time, and the second mode uplink license is available at a second time. Based on the availability of the uplink license, sending data using the first mode uplink license and the second mode uplink license includes: using the first mode uplink license if the first time is earlier than the second time; or using the second mode uplink license if the second time is earlier than the first time.

[0095] In various embodiments, the method further includes: discarding the first mode uplink license if the second time is earlier than the first time; or discarding the second mode uplink license if the first time is earlier than the second time.

[0096] In one embodiment, the method further includes: using the first mode uplink license for retransmission of the data if the second time is earlier than the first time; or using the second mode uplink license for retransmission of the data if the first time is earlier than the second time.

[0097] In some embodiments, the method further includes performing packet replication by using the first mode, the second mode, vehicle-to-everything transmission, or some combination thereof to transmit a copy of the data.

[0098] In some embodiments, the method further includes: receiving information instructing the group replication to be performed.

[0099] In various embodiments, the method further includes determining whether to perform the grouped replication.

[0100] In one embodiment, the method further includes: in response to determining that the packet replication should be performed, sending information indicating that the packet replication should be performed.

[0101] In some embodiments, the method further includes initiating a radio resource control connection establishment based on reliability requirements.

[0102] In some embodiments, the method further includes determining a radio link failure.

[0103] In various embodiments, the method further includes modifying the quality of service flow based on the radio link failure.

[0104] In one embodiment, modifying the Quality of Service (QoS) flow includes terminating one or more QoS flows, establishing one or more QoS flows, discarding the first mode bearer, or some combination thereof.

[0105] In some embodiments, determining the second mode uplink license includes: randomly selecting resources for the second mode uplink license.

[0106] In some embodiments, determining the second mode uplink permission includes performing a sensing process.

[0107] In various embodiments, the method further includes performing a logical channel prioritization process based on at least one logical channel configured to transmit data using the first mode, the second mode, or a combination thereof.

[0108] In one embodiment, the at least one logical channel includes a shared logical channel configured to use the first mode and the second mode.

[0109] In some embodiments, each of the shared logical channels includes a ratio indicating a first portion of the logical channel for transmitting data using the first mode and a second portion of the logical channel for transmitting data using the second mode.

[0110] In some embodiments, the ratio is determined based on a configured ratio or a calculated ratio.

[0111] In various embodiments, the calculated ratio is based on PC5 channel status, Uu channel status, PC5 channel delay, Uu channel delay, the amount of data in the buffer, a comparison between the amount of data and a threshold, or some combination thereof.

[0112] In one embodiment, a method includes: determining a first mode uplink license corresponding to a first mode in a first time period, wherein determining the first mode uplink license includes receiving the first mode uplink license; autonomously determining a second mode uplink license corresponding to a second mode in a second time period, wherein the second mode is different from the first mode; and transmitting data using the first mode uplink license and the second mode uplink license based on an indication of prioritizing which of the first mode uplink license and the second mode uplink license is configured to use a bearer of the first mode and the second mode.

[0113] In some embodiments, the prioritization is determined based on the first mode that always has priority, the second mode that always has priority, the priority value assigned to the bearer, packet delay budget, reliability, or some combination thereof.

[0114] In some embodiments, the first mode uplink license overlaps with the second mode uplink license in time.

[0115] In one embodiment, an apparatus includes: a processor, the processor: determining, during a first time period, a first mode uplink license corresponding to a first mode, wherein determining the first mode uplink license includes receiving the first mode uplink license; and autonomously determining, during a second time period, a second mode uplink license corresponding to a second mode, wherein the second mode is different from the first mode; and a transmitter, the transmitter transmitting data using the first mode uplink license and the second mode uplink license based on the availability of uplink licenses corresponding to the first mode uplink license and the second mode uplink license.

[0116] In some embodiments, the second time period overlaps with the first time period.

[0117] In some embodiments, the transmitter retransmits the data using the first mode, the second mode, or a combination thereof, based on the earliest available license time, quality of service requirements, or a combination thereof.

[0118] In various embodiments, the processor determines the first mode uplink permission by triggering a buffer status report.

[0119] In one embodiment, the processor calculates the buffer status report based on the buffer occupancy rate corresponding to at least one logical channel configured to use the first mode.

[0120] In some embodiments, the at least one logical channel includes an exclusive logical channel limited to the first mode.

[0121] In some embodiments, the at least one logical channel includes a shared logical channel configured to use the first mode and the second mode.

[0122] In various embodiments, the buffer occupancy rate includes the sum of a portion of a first buffer occupancy rate corresponding to the exclusive logical channel and a portion of a second buffer occupancy rate corresponding to the shared logical channel.

[0123] In one embodiment, a portion of the second buffer occupancy rate is determined based on the ratio between the first mode and the second mode of each shared logical channel in the shared logical channel.

[0124] In some embodiments, the ratio is determined based on a configured ratio or a calculated ratio.

[0125] In one embodiment, the calculated ratio is based on PC5 channel status, Uu channel status, PC5 channel delay, Uu channel delay, the amount of data in the buffer, a comparison between the amount of data and a threshold, or some combination thereof.

[0126] In some embodiments, the first mode uplink license is available at a first time, and the second mode uplink license is available at a second time, and the transmitter uses the first mode uplink license and the second mode uplink license to send the data based on the availability of the uplink license, including: using the first mode uplink license if the first time is earlier than the second time; or using the second mode uplink license if the second time is earlier than the first time.

[0127] In various embodiments, if the second time is earlier than the first time, the processor discards the first mode uplink license, or if the first time is earlier than the second time, the processor discards the second mode uplink license.

[0128] In one embodiment, if the second time is earlier than the first time, the transmitter uses the first mode uplink license for retransmission of the data; or if the first time is earlier than the second time, the transmitter uses the second mode uplink license for retransmission of the data.

[0129] In some embodiments, the processor performs packet replication by sending copies of the data using the first mode, the second mode, vehicle-to-everything transmission, or some combination thereof.

[0130] In some embodiments, the apparatus further includes a receiver that receives information instructing the execution of the packet replication.

[0131] In various embodiments, the processor determines whether to perform the grouped replication.

[0132] In one embodiment, in response to determining that the packet replication should be performed, the transmitter sends information indicating that the packet replication should be performed.

[0133] In some embodiments, the processor initiates the establishment of a radio resource control connection based on reliability requirements.

[0134] In some embodiments, the processor determines a radio link failure.

[0135] In various embodiments, the processor modifies the quality of service flow based on the radio link failure.

[0136] In one embodiment, the processor modifying the Quality of Service (QoS) flow includes the processor terminating one or more QoS flows, establishing one or more QoS flows, discarding the first mode bearer, or some combination thereof.

[0137] In some embodiments, the processor determining the second mode uplink license includes the processor randomly selecting resources for the second mode uplink license.

[0138] In some embodiments, the processor determining the second mode uplink permission includes the processor performing a sensing process.

[0139] In various embodiments, the processor performs a logical channel prioritization process based on at least one logical channel configured to transmit data using the first mode, the second mode, or a combination thereof.

[0140] In one embodiment, the at least one logical channel includes a shared logical channel configured to use the first mode and the second mode.

[0141] In some embodiments, each of the shared logical channels includes a ratio indicating a first portion of the logical channel for transmitting data using the first mode and a second portion of the logical channel for transmitting data using the second mode.

[0142] In some embodiments, the ratio is determined based on a configured ratio or a calculated ratio.

[0143] In various embodiments, the calculated ratio is based on PC5 channel status, Uu channel status, PC5 channel delay, Uu channel delay, the amount of data in the buffer, a comparison between the amount of data and a threshold, or some combination thereof.

[0144] In one embodiment, an apparatus includes: a processor, the processor: determining a first mode uplink license corresponding to a first mode in a first time period, wherein determining the first mode uplink license includes receiving the first mode uplink license; and autonomously determining a second mode uplink license corresponding to a second mode in a second time period, wherein the second mode is different from the first mode; and a transmitter, the transmitter transmitting data using the first mode uplink license and the second mode uplink license based on an indication of prioritizing which of the first mode uplink license and the second mode uplink license is configured to use the bearer of the first mode and the second mode.

[0145] In some embodiments, the prioritization is determined based on the first mode that always has priority, the second mode that always has priority, the priority value assigned to the bearer, packet delay budget, reliability, or some combination thereof.

[0146] In some embodiments, the first mode uplink license overlaps with the second mode uplink license in time.

[0147] Other specific forms of the embodiments may be practiced. The described embodiments should be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All variations within the meaning and equivalents of the claims are included within their scope.

Claims

1. A method executed by a user equipment (UE), comprising: A first mode uplink permission for sending data packets corresponding to a first mode is determined in a first time period, wherein the first mode uplink permission is determined based on receiving the first mode uplink permission; Autonomously determine, during a second time period, a second uplink permission corresponding to the second mode for sending the data packet, wherein the second mode differs from the first mode; and Based on the uplink license availability corresponding to the first mode uplink license and the second mode uplink license, the data packet is sent using the first mode uplink license and the second mode uplink license. Specifically, in response to a first time resource allocated for the first mode uplink license preceding a second time resource allocated for the second mode uplink license, the first mode uplink license is used to send the data packet, and the second mode uplink license is used for retransmission of the data packet. Specifically, in response to the second time resource for the second mode uplink license being used before the first time resource for the first mode uplink license, the data packet is sent using the second mode uplink license, and the first mode uplink license is used for retransmission of the data packet.

2. The method according to claim 1, wherein, The second time period overlaps with the first time period.

3. The method according to claim 1, further comprising: The data is retransmitted using the first mode, the second mode, or a combination thereof, based on the earliest available license time, the Quality of Service (QoS) requirements, or a combination thereof.

4. The method according to claim 1, wherein, Determining the uplink permission for the first mode includes triggering a buffer status report (BSR).

5. The method of claim 4, further comprising calculating the BSR based on the buffer occupancy rate corresponding to at least one logical channel LCH configured for the first mode.

6. The method according to claim 5, wherein, The at least one LCH includes an exclusive LCH limited to the first mode.

7. The method according to claim 6, wherein, The at least one LCH includes a shared LCH, which is configured for use in both the first mode and the second mode.

8. The method according to claim 7, wherein, The buffer occupancy rate includes the sum of a portion of the first buffer occupancy rate corresponding to the exclusive LCH and a portion of the second buffer occupancy rate corresponding to the shared LCH.

9. The method according to claim 8, wherein, The portion of the second buffer occupancy rate is determined based on the ratio between the first mode and the second mode of each shared LCH in the shared LCH.

10. The method of claim 1, further comprising: Based on reliability requirements, a Radio Resource Control (RRC) connection establishment is initiated.

11. The method of claim 1, further comprising: Identify radio link failure (RLF).

12. The method of claim 11, further comprising: Modify the QoS flow based on the RLF.

13. The method according to claim 12, wherein, Modifying the QoS flow includes: terminating one or more QoS flows, establishing one or more QoS flows, discarding one or more bearers or combinations thereof associated with the first mode.

14. The method according to claim 1, wherein, Determining uplink clearance for the second mode includes performing a sensing process.

15. The method of claim 1, further comprising: An LCH prioritization process is performed based on at least one logical channel (LCH) configured for the first mode, the second mode, or a combination thereof.

16. The method according to claim 15, wherein, The at least one LCH includes a shared LCH, which is configured to use the first mode and the second mode.

17. A method performed by a user equipment (UE), comprising: A first mode uplink permission for sending data packets corresponding to a first mode is determined in a first time period, wherein the first mode uplink permission is determined based on receiving the first mode uplink permission; Autonomously determine, during a second time period, a second uplink permission corresponding to the second mode for sending the data packet, wherein the second mode differs from the first mode; and Based on the indication of which of the first mode uplink license and the second mode uplink license is prioritized for use with the first mode and the second mode bearer, the data packets are sent using both the first mode uplink license and the second mode uplink license. Specifically, in response to a first time resource allocated for the first mode uplink license preceding a second time resource allocated for the second mode uplink license, the first mode uplink license is used to send the data packet, and the second mode uplink license is used for retransmission of the data packet. Specifically, in response to the second time resource for the second mode uplink license being used before the first time resource for the first mode uplink license, the data packet is sent using the second mode uplink license, and the first mode uplink license is used for retransmission of the data packet.

18. The method according to claim 17, wherein, The prioritization is determined based on the first mode that always has priority, the second mode that always has priority, the priority value assigned to the bearer, the packet delay budget, reliability, or some combination thereof.

19. The method according to claim 18, wherein, The uplink license for the first mode overlaps with the uplink license for the second mode in terms of time.

20. A user equipment (UE), comprising: Processor, the processor: In a first time period, a first-mode uplink permission for sending data packets corresponding to a first mode is determined, wherein the first-mode uplink permission is determined based on receiving the first-mode uplink permission; and Autonomously determine, during a second time period, a second uplink permission corresponding to the second mode for sending the data packet, wherein the second mode differs from the first mode; and A transmitter, based on the uplink license availability corresponding to the first mode uplink license and the second mode uplink license, transmits the data packet using the first mode uplink license and the second mode uplink license. Specifically, in response to a first time resource allocated for the first mode uplink license preceding a second time resource allocated for the second mode uplink license, the first mode uplink license is used to send the data packet, and the second mode uplink license is used for retransmission of the data packet. Specifically, in response to the second time resource for the second mode uplink license being used before the first time resource for the first mode uplink license, the data packet is sent using the second mode uplink license, and the first mode uplink license is used for retransmission of the data packet.

21. The UE according to claim 20, wherein, The second time period overlaps with the first time period.

22. The UE according to claim 20, wherein, The transmitter retransmits the data using the first mode, the second mode, or a combination thereof, based on the earliest available license time, Quality of Service (QoS) requirements, or a combination thereof.

23. The UE according to claim 20, wherein, The processor determines the uplink permission for the first mode by triggering a buffer status report (BSR).

24. The UE according to claim 23, wherein, The processor calculates the BSR based on the buffer occupancy rate corresponding to at least one LCH configured for the first mode.

25. The UE according to claim 24, wherein, The at least one LCH includes an exclusive LCH limited to the first mode.

26. The UE according to claim 25, wherein, The at least one LCH includes a shared LCH, which is configured for use in both the first mode and the second mode.

27. The UE according to claim 26, wherein, The buffer occupancy rate includes the sum of a portion of the first buffer occupancy rate corresponding to the exclusive LCH and a portion of the second buffer occupancy rate corresponding to the shared LCH.

28. The UE according to claim 27, wherein, The portion of the second buffer occupancy rate is determined based on the ratio between the first mode and the second mode of each shared LCH in the shared LCH.

29. The UE according to claim 20, wherein, Based on reliability requirements, the processor initiates the establishment of a Radio Resource Control (RRC) connection.

30. The UE according to claim 20, wherein, The processor determines a radio link failure (RLF).

31. The UE according to claim 30, wherein, The processor modifies the Quality of Service (QoS) flow based on the RLF.

32. The UE according to claim 31, wherein, The processor modifies the QoS flow by: terminating one or more QoS flows, establishing one or more QoS flows, discarding one or more bearers or combinations thereof associated with the first mode.

33. The UE according to claim 20, wherein, The processor determines the uplink permission for the second mode by performing a sensing process.

34. The UE according to claim 20, wherein, The processor performs an LCH prioritization process based on at least one logical channel (LCH) configured for the first mode, the second mode, or a combination thereof.

35. The UE according to claim 34, wherein, The at least one LCH includes a shared LCH, which is configured for use in both the first mode and the second mode.

36. A remote unit (UE), comprising: Processor, the processor: In a first time period, a first-mode uplink permission for sending data packets corresponding to a first mode is determined, wherein the first-mode uplink permission is determined based on receiving the first-mode uplink permission; and Autonomously determine, during a second time period, a second uplink permission corresponding to the second mode for sending the data packet, wherein the second mode differs from the first mode; and The transmitter, based on an indication of which of the first-mode uplink license and the second-mode uplink license is prioritized for use with the first-mode and second-mode bearers, transmits the data packets using the first-mode uplink license and the second-mode uplink license. Specifically, in response to a first time resource allocated for the first mode uplink license preceding a second time resource allocated for the second mode uplink license, the first mode uplink license is used to send the data packet, and the second mode uplink license is used for retransmission of the data packet. Specifically, in response to the second time resource for the second mode uplink license being used before the first time resource for the first mode uplink license, the data packet is sent using the second mode uplink license, and the first mode uplink license is used for retransmission of the data packet.

37. The UE according to claim 36, wherein, The prioritization is determined based on the first mode that always has priority, the second mode that always has priority, the priority value assigned to the bearer, the packet delay budget, reliability, or some combination thereof.

38. The UE according to claim 37, wherein, The uplink license for the first mode overlaps with the uplink license for the second mode in terms of time.

Images