Multi-Radio Access Technology Communication

Abstract

Apparatus, method, and system for communication in multiple radio access technologies are disclosed. A method (900) includes receiving (902) control information at a device using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which the sidelink resource allocation is applied for the second radio access technology.

Description

[0001] This application claims priority to U.S. Patent Application Serial No. 62 / 827,698, filed Apr. 1, 2019, by Joachim Loehr, entitled “APPARATUSES, METHODS, AND SYSTEMS FOR CROSS-RAT V2X COMMUNICATION,” which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The subject matter disclosed herein generally relates to wireless communication and, more particularly, to communication among multiple radio access technologies. BACKGROUND OF THE INVENTION

[0003] The following abbreviations are defined herein, at least some of which are referenced in the following description: 3rd Generation Partnership Project (“3GPP”), 5th Generation (“5G”), QoS for NR V2X communication (“5QI / PQI”), Authentication, Authorization, and Accounting (“AAA”), Acknowledgement (“ACK”), Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Access Stratum (“AS”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Contention-Based Random Access (“CBRA”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Closed Loop (“CL”), Coordinated Multi-Point (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Channel State Information - Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Spread (“DFTS”), Dual Connectivity (“DC”), Downlink Control Information (“DCI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short Range Communications (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplexing (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”), Frequency Range 1 – below 6 GHz and / or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2 – 24.25 GHz to 52.6 GHz (“FR2”), General Area Description (“GAD”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”).Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), Global System for Mobile Communications (“GSM”), Global Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat reQuest (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hashed Expected Response (“HXRES”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed-Assisted Access (“LAA”), Local Area Network (“LAN”), Load-Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Priority (“LCP”), Log-Likelihood Ratio (“LLR”), Long-Term Evolution (“LTE”), Multiple Access (“MA”), Media Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Minimum Communication Range (“MCR”), Modulation and Coding Scheme (“MCS”), Master Information Block (“MIB”), Multiple-Input Multiple-Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Massive Machine-Type Communication (“mMTC”), Maximum Power Reduction (“MPR”), Machine-Type Communication (“MTC”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrow Band (“NB”), Negative ACKnowledgement (“NACK”) or (“NAK”), Network Entity (“NE”), Network Function (“NF”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Unlicensed NR (“NR-U”), Network Repository Function (“NRF”), Network Scheduling Mode (“NS Mode”) (e.g., the network scheduling mode for V2X communication resource allocation - Mode-1 in NR V2X and Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operations, Administration and Maintenance System or Operations and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open Loop (“OL”), Other System Information (“OSI”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”)Power Control (“PC”), UE-to-UE Interface (“PC5”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell Identifier (“PCI”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), PC5 QoS Class Identifier (“PQI”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), Quasi-Co-Location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (for Uu service), Other RAT (“RAT-2”) (for non-Uu service), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Element Group (“REG”), Radio Link Control (“RLC”), RLC Acknowledged Mode (“RLC-AM”), RLC Unacknowledged Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Spread Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Round-Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Service Data Unit (“SDU”)Safety Anchor Function (“SEAF”), Sidelink Feedback Content Information (“SFCI”), Serving Gateway (“SGW”), System Information Block (“SIB”), SystemInformationBlockType1 (“SIB1”), SystemInformationBlockType2 (“SIB2”), Subscriber Identity / Identity Module (“SIM”), Signal-to-Interference plus Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signal (“SLSS”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI RS”), Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Subscription Concealed Identifier (“SUCI”), Scheduled User Equipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Advance Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmission Power Control (“TPC”), Transmission and Reception Point (“TRP”), Transmission Time Interval (“TTI”), Transmission (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”) (e.g., V2X UE), UE Autonomous Mode (UE autonomously selects V2X communication resources - e.g., Mode 2 in NR V2X and Mode 4 in LTE V2X. The UE autonomous selection can be based or not based on resource sensing operations), Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”), Ultra-Reliable and Low-Latency Communication (“URLLC”), UE Routing Selection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Everything (“V2X”), V2X UE (e.g., UE capable of in-vehicle communication using 3GPP protocols), Access AMF (“vAMF”)Access to the NSSF (“vNSSF”), access to the PLMN (“VPLMN”), wide area network (“WAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0004] In some wireless communication networks, multiple RATs may be used. SUMMARY OF THE INVENTION

[0005] Methods for communication using multiple radio access technologies are disclosed. Apparatus and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a device, control information using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0006] An apparatus for communication using multiple radio access technologies includes a receiver that receives control information using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0007] Another embodiment of a method for communication using multiple radio access technologies includes transmitting, to a device, control information using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology, and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0008] Another apparatus for communication using multiple radio access technologies includes a transmitter that transmits control information to a device using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more specific description of the embodiments briefly described above will be presented by reference to specific embodiments shown in the accompanying drawings. Understanding that these drawings depict only some embodiments and are not to be considered limiting of the scope, the embodiments will be described and explained with additional features and details by using the drawings, wherein:

[0010] Figure 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for communication using multiple radio access technologies;

[0011] Figure 2 is a schematic block diagram illustrating an embodiment of a device that can be used for communication using multiple radio access technologies;

[0012] Figure 3 is a schematic block diagram illustrating an embodiment of a device that can be used for communication using multiple radio access technologies;

[0013] Figure 4 is a schematic block diagram illustrating an embodiment of communication involving multiple radio access technologies;

[0014] Figure 5 is a schematic block diagram illustrating another embodiment of communication involving multiple radio access technologies;

[0015] Figure 6 is a schematic block diagram illustrating an embodiment of timing for communication using multiple radio access technologies;

[0016] Figure 7 is a schematic block diagram illustrating another embodiment of timing for communication using multiple radio access technologies;

[0017] Figure 8 is a schematic block diagram illustrating an embodiment of a system configured with multiple radio access technologies;

[0018] Figure 9 is a schematic block diagram illustrating another embodiment of a system configured with multiple radio access technologies;

[0019] Figure 10 is a flowchart illustrating an embodiment of a method for communication using multiple radio access technologies; and

[0020] Figure 11 is a flowchart illustrating another embodiment of a method for communication using multiple radio access technologies. Detailed Description of the Embodiments

[0021] As will be understood by those of ordinary skill in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “circuit,” “module,” or “system.” In addition, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code referred to hereinafter as code. The storage device may be tangible, non-transitory, and / or non-transmissive. The storage device may not embody a signal. In certain embodiments, the storage device merely comprises a signal for accessing the code.

[0022] Certain functional units described in this specification may be labeled as modules for the purpose of emphasizing their implementation independence more particularly. For example, a module may be implemented as a hardware circuit comprising a custom very large scale integration (“VLSI”) circuit or gate array, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like.

[0023] A module may also be implemented in code and / or software for execution by various types of processors. The identified code of a module may, for example, comprise one or more physical or logical blocks of executable code that may be organized, for example, as an object, procedure, or function. However, the executable files of the identified module need not be physically located together, but may include disparate instructions stored in different locations that, when logically combined, include the module and implement the stated purpose of the module.

[0024] In fact, a code module may be a single instruction or many instructions, and may even be distributed over several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data may be identified and illustrated within a module and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations, including on different computer-readable storage devices. Where a module or portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0025] Any combination of one or more computer-readable media may be utilized. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device that stores code. The storage device may be, by way of example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

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

[0027] The code for performing the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, and the like, and conventional procedural programming languages such as the “C” programming language, and / or machine languages such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, partly on the user's computer as a stand-alone software package, partly on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network including a local area network (“LAN”) or a wide area network (“WAN”), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0028] References in this specification to “one embodiment,” “an embodiment,” or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless expressly stated otherwise, the appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do 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, a list of enumerated items does not imply that any or all of the items are mutually exclusive. Unless expressly stated otherwise, the terms “a,” “an,” and “the” also refer to “one or more.”

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

[0030] Aspects of the embodiments are described below with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, 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, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device create a means for implementing the functions / operations specified in the block or blocks of the schematic flowchart and / or schematic block diagram.

[0031] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other device to operate in a specific manner, such that the instructions stored in the storage device produce an article of manufacture that includes instructions for implementing the functions / operations specified in the block or blocks of the schematic flowchart and / or schematic block diagram.

[0032] The code can also be loaded onto a computer, other programmable data processing device, or other device, so that a series of operational steps are performed on the computer, other programmable device, or other device to produce a computer-implemented process, such that the code executed on the computer or other programmable device provides a process for implementing the functions / operations specified in the block or blocks of the flowchart and / or block diagram.

[0033] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to different embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams can represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function(s).

[0034] It should also be noted that, in some alternative embodiments, the functions annotated in the blocks may not occur in the order annotated in the figures. For example, depending on the functions involved, two consecutively shown blocks may actually be executed substantially simultaneously, or these blocks may sometimes be executed in the reverse order. It is conceivable that other steps and methods are equivalent in function, logic, or effect to one or more blocks or portions of the illustrated figures.

[0035] Although various arrow types and line types may be employed in flowcharts and / or block diagrams, it is understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the recited steps of the 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 that performs a particular function or operation, or by a combination of dedicated hardware and code. Although a flowchart depicts a series of sequential steps, unless explicitly stated, no inference should be made from that sequence regarding the order of a particular execution, the sequential execution rather than simultaneous or overlapping execution of steps or portions thereof, or the execution of the depicted steps without intervening or intermediate steps.

[0036] The description of the elements in each figure may refer to the elements of the foregoing figures. In all the figures, the same numerals refer to the same elements, including alternative embodiments of the same element.

[0037] Figure 1 Embodiments of a wireless communication system 100 for communication using multiple radio access technologies are depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 a specific number of remote units 102 and network units 104 are depicted, 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.

[0038] In one embodiment, the remote unit 102 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including surveillance cameras), an in-vehicle computer, a network device (e.g., a router, a switch, a modem), an aerial vehicle, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. Additionally, the remote unit 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In certain embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0039] The network units 104 may be distributed over a geographical area. In certain embodiments, the network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a home Node-B, a relay node, a device, a core network, an air server, a radio access node, an AP, an NR, a network entity, an AMF, a UDM, a UDR, a UDM / UDR, a PCF, a RAN, a NSSF, or any other term used in the art. The network unit 104 is generally 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 generally 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, and other networks. These and other elements of the radio access and core networks are not shown, but are generally well known to those of ordinary skill in the art.

[0040] In one embodiment, the wireless communication system 100 complies with the NR protocol standardized in 3GPP, where the network unit 104 transmits on the DL using an OFDM modulation scheme, and the remote unit 102 transmits on the UL using an SC-FDMA scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols, e.g., WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfox, and other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0041] The network unit 104 can serve multiple remote units 102 within a service area such as a cell or a cell sector via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, frequency domain, and / or spatial domain.

[0042] In various embodiments, the remote unit 102 can receive control information using a first radio access technology, where: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology, and where the timing offset information is used to determine the time at which the sidelink resource allocation is applied for the second radio access technology. Thus, the remote unit 102 can be used for multi-radio access technology communication.

[0043] In some embodiments, the network unit 104 can transmit control information to a device using a first radio access technology, where: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology. And where the timing offset information is used in the device to determine the time at which the sidelink resource allocation is applied for the second radio access technology. Thus, the network unit 104 can be used for multi-radio access technology communication.

[0044] Figure 2 An embodiment of an apparatus 200 that can be used for multi-radio access technology communication is depicted. The apparatus 200 includes an embodiment of the remote unit 102. Additionally, the remote unit 102 can 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 touch screen. In certain embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 can include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0045] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field-programmable gate array (“FPGA”), or a 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.

[0046] 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 associated data, such as an operating system or other controller algorithms operating on remote unit 102.

[0047] In one embodiment, input device 206 may include any known computer input device, including a touchpad, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or a similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen such that text may be 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 touch panel.

[0048] In one embodiment, the display 208 may include any known electronically controllable display or display device. The display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 208 may include a wearable display such as a smartwatch, smart glasses, a heads-up display, etc. Additionally, the display 208 may be a component of a smartphone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

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

[0050] The transmitter 210 is used to provide an UL communication signal to the network unit 104, and the receiver 212 is used to receive a DL communication signal from the network unit 104, as described herein. In some embodiments, the receiver 212 may receive control information using a first radio access technology, where: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology, and where the timing offset information is used to determine the time at which the sidelink resource allocation is applied for the second radio access technology.

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

[0052] Figure 3FIG. 0 depicts an embodiment of an apparatus 300 that can be used for communication with multiple radio access technologies. The apparatus 300 includes an embodiment of a network unit 104. In addition, the 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 can be understood that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0053] In various embodiments, the transmitter 310 may transmit control information to a device using a first radio access technology, where: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and where the timing offset information is used in the device to determine the time at which the sidelink resource allocation for the second radio access technology is applied.

[0054] Although only one transmitter 310 and one receiver 312 are illustrated, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and the receiver 312 may be of any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and the receiver 312 may be part of a transceiver.

[0055] In various embodiments, two resource allocation modes can be used for NR and LTE V2X communication. In such embodiments, the two resource allocation modes for LTE may be referred to as mode 3 and mode 4; for NR, they may be referred to as mode 1 and mode 2. These different modes support direct V2X communication but differ in the way radio resources are allocated. In some modes, the cellular network allocates resources (e.g., the gNB allocates mode 1 resources, and the eNB allocates mode 3 resources). In various modes (e.g., mode 2 and mode 4), no cellular coverage is required, and the vehicle autonomously selects its radio resources using a distributed scheduling scheme that is supported by a congestion control mechanism in a preconfigured resource pool. In some embodiments, the RAN within the coverage area may also allocate mode 2 and mode 4 resources. In certain embodiments, mode 2 and / or mode 4 are considered baseline modes and represent an alternative to 802.11p or DSRC.

[0056] In some embodiments, all resource allocation patterns have been designed to meet latency requirements and / or to accommodate high Doppler spread and high density of vehicles for V2X communication. In some embodiments, Mode 1 and Mode 3 may use a centralized RAN (e.g., gNB / eNB) scheduler. In various embodiments, the vehicle UE and the RAN may communicate using the Uu interface (e.g., sending a BSR / SR from the transmitting V2X UE to the RAN and receiving an SL grant on the PDCCH (e.g., DCI) as a response). In some embodiments, Mode 2 and Mode 4 may use the PC5 interface to facilitate direct LTE SL communication between two on-vehicle UEs. In such embodiments, distributed UE scheduling may be used. In some embodiments, V2X Mode 2 and Mode 4 may operate without infrastructure support even when the UE is within the RAN coverage. In various embodiments, resources may be shared with the Uu uplink. In some embodiments, such as in LTE V2X, only broadcast type transmissions may be supported, while in other embodiments, such as in NR-based V2X, unicast and multicast transmissions may be supported.

[0057] In some embodiments, the operator may see the benefit of using the available LTE coverage to control the NR PC5 for network scheduling operation modes. In other embodiments, the NR (e.g., gNB) that controls the LTE PC5 may be used for network scheduling and / or UE autonomous operation modes.

[0058] In various embodiments, through dynamic cross-RAT scheduling, the DCI received on one RAT may indicate the SL resource allocation for another RAT. Thus, new DCI formats may be used. In some embodiments, since the timing (e.g., slot and / or frame boundaries) of NR cells and LTE cells / carriers may be significantly different (e.g., asynchronous network operation) and / or LTE operates at the TTI level (e.g., potentially having a different SCS from NR cells and / or BWPs), while the NR PHY operates at the slot level or OFM symbol level, the DCI received on one RAT may need to be delivered to another RAT at some predefined timing (e.g., some timing transitions from one RAT to another may be used).

[0059] It can be understood that eNB and / or gNB may be used for the base station, but may be replaced by any other radio access node (e.g., BS, eNB, gNB, AP, NR, etc.). Moreover, although various embodiments herein are described in the context of 5G NR, these embodiments may equally apply to other mobile communication systems that support serving cells / carriers, such as systems configured for SL communication through the PC5 interface.

[0060] In a first embodiment, if, for example, NR Uu (e.g., gNB) provides SL resources (e.g., SPS resources) for LTE SL UE mode 3 operation, a new DCI format may be introduced for NR Uu. The new DCI format may contain SL resource allocation information for the LTE PC5 interface. In addition, the new DCI format may include a DCI indicating activation and / or deactivation of the SL SPS configuration (e.g., the SPS configuration may be signaled via RRC signaling) and / or may dynamically assign SL resources on the PC5 interface. In one implementation of the first embodiment, the new NR DCI format may have the same fields as the LTE DCI format (e.g., DCI format 5_A) that allocates SL resources. Such an implementation may enable the new NR DCI format to be understood by the LTE protocol stack of the NR V2X UE. In another implementation of the first embodiment, the new NR DCI format may be received on the PDCCH that allocates resources for the LTE PC5 interface (LTE V2X) and may include an indicator (e.g., a one-bit flag) indicating that the information field contained in the DCI will apply to the LTE PC5 interface. In a further implementation of the first embodiment, a new RNTI may be used to indicate that the DCI conveys SL resource allocation information for another RAT, e.g., scrambling the CRC of the DCI with the new RNTI. According to one implementation of the first embodiment, if the flag in the received DCI indicates that the DCI allocates SL resources for LTE PC5 if the received DCI is the new NR DCI, the PHY layer of the NR protocol stack of the NR V2X UE may deliver the received NR DCI (e.g., on the PDCCH) to the LTE PHY of the LTE protocol stack. If the LTE PHY layer of the NR V2X UE receives a DCI and the fields of the DCI (e.g., in-UE communication) from the NR PHY layer, the LTE PHY may process the DCI in the same manner as if the DCI had been received on LTE Uu (e.g., PDCCH).

[0061] In another implementation of the first embodiment, the NR V2X UE may determine that the received NR DCI is for LTE PC5 SL based on the cross-RAT flag in the new NR DCI format and may transform the received NR DCI format (e.g., the fields in the DCI) into an LTE DCI format (e.g., DCI format 5A) to be understood by the LTE PHY and / or MAC layer.

[0062] Figure 4 FIG. is a schematic block diagram illustrating an embodiment of a communication 400 involving multiple radio access technologies. Figure 4FIG. illustrates one embodiment of a signaling flow for configuration (e.g., NR), where the gNB provides dynamic SL resources for LTE SL UE mode 3 operation. It should be noted that Figure 4 Only one embodiment of dynamic cross-RAT scheduling is depicted. Communication 400 includes communications transmitted between gNB 402, V2XTX UE 404 (NR side), V2X TX UE 406 (LTE side), and V2X RX UE408. Each of the described communications 400 may include one or more messages.

[0063] In a first communication 410 transmitted from V2X TX UE 406 to V2X TX UE 404, V2X TX UE 406 transmits an LTE BSR to V2X TX UE 404. In a second communication 412 transmitted from V2X TX UE 404 to gNB 402, V2X TXUE 404 transmits an SL BSR (e.g., reporting LTE information) to gNB 402. In the second communication 412, the NR V2X TX UE 404 initiates a request for SL resources on the LTE PC5 interface via an indication to be sent to gNB 402 over the NR Uu interface. In one embodiment, such a request may be signaled by means of a buffer status report indicating the amount of LTE SL data available for transmission (e.g., a new BSR MAC CE format for conveying LTE buffer status information to gNB 402). In another embodiment, sidelink assistance information (e.g., for SL SPS allocation) may be provided to gNB 402 via RRC signaling. Additionally, in the second communication 412, the LTE sidelink assistance information message reported by the NR V2X UE 404 may be sent to gNB 402 by encapsulating it in an NR Uu RRC message having additional bits and / or flags indicating that the assistance information is for LTE PC5 scheduling. Upon receiving the SL request information from the NR V2X UE 404, gNB 402 may determine the SL resource allocation for the LTE PC5 interface. Such an SL resource allocation message may be signaled to the N2 V2X UE 404 in a third communication 414 via NR DCI on the PDCH. The NR DCI conveying the SL resource allocation information for LTE PC5 may be signaled via a new DCI format. In a third communication 414 transmitted from gNB 402 to V2X TX UE 404, gNB 402 transmits an SL grant (e.g., for cross-RAT) to V2X TX UE404. Additionally, the SL grant for LTE PC5 may further include DCI to activate or deactivate the LTEV2X SPS configuration.

[0064] In the fourth communication 416 transmitted from V2X TX UE 404 to V2X TX UE 406, V2X TX UE 404 transmits an SL grant (LTE) to V2X TX UE 406. In other words, upon receiving the NR DCI, the PHY layer of the NR protocol stack of NR V2X UE 404 delivers the received DCI fields within the DCI to the LTE PHY of the LTE protocol stack of V2X TX UE 406, respectively. In response to the LTE PHY layer of V2X TX UE 406 receiving the DCI (e.g., the fields of the DCI) from the NR PHY layer, the LTE PHY can process the DCI in the same manner as it processes the LTE DCI received on the LTE Uu (e.g., PDCCH). In the fifth communication 418 transmitted from V2X TX UE 406 to V2X RX UE 408, V2X TX UE 406 transmits an SCI to V2X RX UE 408. In the sixth communication 420 transmitted from V2X TX UE 406 to V2X RX UE 408, V2X TX UE 406 transmits a PSSCH (e.g., the first TB (A) with RV = 0) to V2X RX UE 408. In the seventh communication 422 transmitted from V2X TX UE 406 to V2X RX UE 408, V2X TX UE 406 transmits a PSSCH (e.g., the first TB (A) with RV = 1) to V2X RX UE 408. In the eighth communication 424 transmitted from V2X TX UE 406 to V2X RX UE 408, V2X TX UE 406 transmits a PSSCH (e.g., the first TB (A) with RV = 2) to V2X RX UE 408.

[0065] In a second embodiment, if DCI on LTE Uu (e.g., eNB) provides SL resources for NR SL UE mode 1 operation, a new LTE DCI format can be used for LTE Uu, which includes SL resource allocation information for the NR PC5 interface. In such an embodiment, the new LTE DCI format can include DCI indicating activation and / or release of SL SPS configuration, or SL resources can be dynamically allocated on the NR PC5 interface. In one implementation of the second embodiment, the new LTE DCI format can have the same fields as the NR DCI that allocates SL resources. Such an implementation can enable the new LTE DCI to be understood by the NR protocol stack of the NR V2X UE. In another implementation of the second embodiment, the new LTE DCI received on the PDCCH that allocates resources for the NR PC5 interface includes an indicator (e.g., a one-bit cross-RAT flag) that indicates that the information fields contained in the DCI can be applied to the NR PC5 interface. In some embodiments, a new RNTI can be used to indicate that the DCI conveys SL resource allocation information for another RAT. In various implementations of the second embodiment, if the flag in the received DCI indicates that the DCI allocates SL resources for the NR PC5 or if the received DCI is the new LTE DCI, the PHY layer of the LTE protocol stack of the NR V2X UE delivers the received LTE DCI to the NR PHY of the NR protocol stack. In some embodiments, if the NR PHY layer of the NR V2X UE receives DCI (e.g., fields of the DCI) from the LTE PHY layer (e.g., in-UE communication), the NR PHY can process the DCI as it does on the NR protocol (e.g., the same as if the DCI had been received on NR Uu (e.g., PDCCH)).

[0066] Figure 5 is a schematic block diagram illustrating another embodiment of a communication 500 involving multiple radio access technologies. In Figure 5 it, the communication 500 involves an eNB (e.g., LTE) that provides SL resources for NR SL UE mode 1 operation. The communication 500 includes communications transmitted between the eNB 502, the V2X TX UE 504 (LTE side), the V2X TX UE 506 (NR side), and the V2X RX UE 508. Each of the described communications 500 can include one or more messages.

[0067] In a first communication 510 transmitted from the V2X TX UE 504 to the eNB 502, the V2X TX UE 504 transmits an SL BSR to the eNB 502 (e.g., a request for SL resources on the NR PC5 interface over the LTE Uu interface). The SL BSR (e.g., the request) may be signaled by a buffer status report indicating the amount of NR SL data available for transmission (e.g., a new LTE BSR MAC CE format for conveying NR BS information to the eNB 502). In some embodiments, the first communication 510 may provide the eNB 502 with NR side-link assistance information (e.g., for SL SPS allocation) via RRC signaling. The NR side-link assistance information message reported by the V2X TX UE 504 may be sent to the eNB 502 by encapsulating it in an LTE RRC message with additional bits and / or flags indicating that the assistance message is for NR PC5 scheduling.

[0068] In a second communication 512 transmitted from the eNB 502 to the V2X TX UE 504, the eNB 502 transmits an SL grant to the V2X TX UE 504 (e.g., HARQ process ID = X, NDI = 1, LTE PUCCH ACK / NACK resource). In one embodiment of the second communication 512, in response to receiving a scheduling request from the V2X TX UE 504, the eNB 502 sends a DCI containing NR SL resource allocation information (e.g., on the PDCCH) to the V2X TX UE 504. In certain embodiments, the DCI assigns resources and / or timing information for a feedback message on the LTE Uu interface to indicate whether an SL transmission on the NR PC5 has been successfully received or whether a retransmission on the NR PC5 is required. Such feedback may be transmitted in the form of ACK / NACK on the PUCCH.

[0069] In a third communication 514 transmitted from the V2X TX UE 504 to the V2X TX UE 506, the V2X TX UE 504 transmits an SL grant (NR) to the V2X TX UE 506 (e.g., HARQ process ID = X, NDI = 1). In some embodiments, when an LTE DCI is received on the PDCCH of the LTE protocol stack, the V2X TX UE 504 delivers the NR SL grant (e.g., information) to the V2X TX UE (NR protocol stack) 506, and then the V2X TX UE (NR protocol stack) 506 further executes the NR SL grant. It should be noted that the eNB 502 may allocate SL feedback resources to the V2X RX UE 508 via the V2X TX UE 506. This may be done at the establishment of the SLRB.

[0070] In the fourth communication 516 transmitted from the V2X TX UE 506 to the V2X RX UE 508, the V2X TX UE 506 transmits an SCI (e.g., HARQ process ID = Y, NDI = 1) to the V2X RX UE 508. In the fifth communication 518 transmitted from the V2X TX UE 506 to the V2X RX UE 508, the V2X TX UE 506 transmits a PSSCH (e.g., the first TB (A) with RV = 0) to the V2X RX UE 508. In the communication 520 transmitted from the V2X RX UE 508 to the V2X TX UE 506, the V2X RX UE 508 transmits a NACK for TB A to the V2X TX UE 506. In the seventh communication 522 transmitted from the V2X TX UE 506 to the V2X TX UE 504, a NACK for TB A is transmitted from the V2X TX UE 506 to the V2X TX UE 504. In the eighth communication 524 transmitted from the V2X TX UE 504 to the eNB 502, the V2X TX UE 504 transmits a NACK for the SL grant to the eNB 502.

[0071] In the ninth communication 526 transmitted from the eNB 502 to the V2X TX UE 504, the eNB 502 transmits an SL grant (e.g., HARQ process ID = X, NDI = 1, LTE PUCCH ACK / NACK resource) to the V2X TX UE 504. In the tenth communication 528 transmitted from the V2X TX UE 506 to the V2X RX UE 508, the V2X TX UE 506 transmits an SCI (e.g., HARQ process ID = Y, NDI = 1) to the V2X RX UE 508. In the eleventh communication 530 transmitted from the V2X TX UE 506 to the V2X RX UE 508, the V2X TX UE 506 transmits a PSSCH (e.g., the first TB (A) with RV = 1) to the V2X RX UE 508. In the twelfth communication 532 transmitted from the V2X RX UE 508 to the V2X TX UE 506, the V2X RX UE 508 transmits an ACK for TB A to the V2X TX UE 506. In the thirteenth communication 534 transmitted from the V2X TX UE 506 to the V2X UE 504, the V2X TX UE 506 transmits an ACK for TB A to the V2X TX UE 504. In the fourteenth communication 536 transmitted from the V2X TX UE 504 to the eNB 502, the V2X TX UE 504 transmits an ACK for the SL grant to the eNB 502.

[0072] In various embodiments, since the timing of the NR cell and the LTE cell and / or carrier (e.g., slot and / or frame boundaries) may be significantly different (e.g., asynchronous network operation), and LTE can operate at the TTI level (e.g., may have a different SCS compared to the NR cell and / or BWP) and the NR PHY can operate at the slot level or OFM symbol level, the DCI received on one RAT can be delivered to another RAT at some predefined timings (e.g., some timing transitions from one RAT to another RAT can be performed). It can be understood that even though the following description may apply to LTE PC5SL resource allocation done via NR DCI, the described aspects also apply equally if the NR SL PC5 allocation is signaled via LTE DCI.

[0073] In some embodiments, the DCI information received on the NR PDCCH can be delivered to the LTE PHY layer of the NR V2X UE at some predefined timings. In various embodiments, the NR PHY can deliver the received DCI to the LTE PHY at some predefined timings. In other embodiments, the LTE PHY can consider that it has received the DCI allocating the SL resources in a predefined TTI / subframe. Such a timing offset can be fixed in the standard (e.g., if the NR DCI containing the LTE SL grant is received in slot n, the UE can consider that the LTE SL grant is received in the first LTE subframe x that starts at least T offset after and then is slot n) or it can be preconfigured by higher layer signaling. The timing offset can be defined in terms of ms or the number of slots / subframes / symbols. In some embodiments, the DCI can contain some information indicating the LTE subframe in which the SL resources (e.g., resources for PSCCH / PSSCH) are allocated. It should be noted that the timing of the DCI can be important for the efficient scheduling of resources among multiple UEs. In certain embodiments, the reception timing of the DCI may affect the start instance of a timer in the MAC layer of the UE (e.g., DRX-related timer). Figure 6 and Figure 7 Illustrates various timing relationships between receiving the NR DCI on the Uu interface and the timing of performing the grant on the LTE part of the V2X UE. In Figure 6 it, the NR DCI containing the LTE SL grant is received in slot n. According to Figure 6 it, the UE (e.g., the LTE protocol stack of the TX UE) behaves as if it has received the LTE SL grant in TTI x+1 on the PDCCH (e.g., the NR PHY of the UE delivers the received SL grant to the LTE PHY at TTI x+1). It should be noted that in as Figure 7There may be different timing relationships between the reception of the defined NR SL DCI (e.g., including LTE SL DCI) as shown and the corresponding LTE SL DCI reception / execution.

[0074] Figure 6 FIG. is a schematic block diagram illustrating an embodiment of timing 600 for communication of multiple radio access technologies. Timing 600 illustrates NR information 602 and LTE information 604 at time 606. The slot size 608 of the NR information 602 may be 0.5 ms, and the subframe / TTI size 610 of the LTE information 604 may be 1 ms. At time 612, an NR DCI (LTE SL grant) is received on the NR Uu interface, and at time 614, the UE considers that the LTE SL grant (on the LTE Uu interface) included in the NR DCI is received and processes the SL grant accordingly.

[0075] Figure 7 FIG. is a schematic block diagram illustrating another embodiment of timing 700 for communication of multiple radio access technologies. Timing 700 illustrates NR information 702 and LTE information 704 at time 706. The slot size 708 of the NR information 702 may be 1.0 ms, and the sTTI size 710 of the LTE information 704 may be 0.5 ms. At time 712, an NR DCI (LTE SL grant) is received, and at time 714, the UE considers that the LTE SL grant (on the LTE Uu interface) included in the NR DCI is received and processes the SL grant accordingly.

[0076] In various embodiments, the timing relationship may be deterministic and known to the UE and the gNB, and may be the same across all UEs scheduled by different RATs. In one embodiment, the NR SLDCI that allocates SL resources on the LTE PC5 interface includes some timing information indicating the time at which the SL grant can be executed by the NR V2X UE. Such timing information may indicate the subframe number in which the LTE SL grant can be executed (e.g., the UE behaves as if it has received the LTE SL grant in the indicated subframe on the PDCCH).

[0077] Figure 8 FIG. is a schematic block diagram illustrating an embodiment of a system 800 configured with multiple radio access technologies. The system 800 includes a gNB 802 and an NR V2X UE 804. Figure 8Illustrates how gNB 802 provides LTE PC5 V2X communication resources to NR V2X UE 804. gNB 802 transmits 806 RRC signaling (or broadcast signaling) containing LTE PC5 resources. NR V2X UE 804 uses C-RNTI (e.g., for dedicated RRC signaling) or SI-RNTI (e.g., for broadcast signaling) to receive the LTE PC5 resources. The NR-RRC 808 of NR V2X UE 804 receives the RRC signaling (or broadcast signaling) containing the LTE PC5 resources. NR-RRC808 transmits 810 BITSTRING (e.g., containing RRC signaling for LTE PC5 resources) to the LTE-RRC 812 of NR V2X UE 804. It can be understood that both NR-RRC 808 and LTE-RRC 812 can be implemented together (e.g., the illustrated separation can be logical). LTE-RRC 812 can interpret the BITSTRIG (e.g., configuration), check for consistency (e.g., whether the configuration is valid), and configure the lower layers. Then the LTE PC5 communication resources can be configured to the physical layer. Specifically, LTE-RRC 812 transmits configuration information 814 to LTE-PDCP 816, LTE-RLC 818, LTE-MAC 820, and LTE-Phy 822.

[0078] Figure 9 Is a schematic block diagram illustrating another embodiment of a system 900 configured with multiple radio access technologies. System 900 includes eNB 902 and NR V2X UE 904. Figure 9 Illustrates cross-RAT communication, where eNB 902 provides resources for NR PC5 communication to NR V2X UE 904. eNB 902 transmits 906 RRC signaling (or broadcast signaling) that contains LTE PC5 resources. The LTE-RRC 908 of N RV2X UE 904 receives the RRC signaling (or broadcast signaling) containing the LTE PC5 resources. LTE-RRC 908 transmits 910 BITSTRING to the NR-RRC 912 of NR V2X UE 904. NR-RRC 912 transmits configuration information 914 to NR-PDCP 916, NR-RLC 918, NR-MAC 920, and NR-Phy 922.

[0079] In some embodiments, the NR V2X UE can be notified via a paging message that the system information regarding cross-RAT PC5 resources has changed and the updated system information for cross-RAT PC5 resources can be obtained immediately. In various embodiments, the modification cycles of the two RATs are aligned such that the actual change in the system information of cross-RAT PC5 resources occurs simultaneously.

[0080] In some embodiments, if there is no available HARQ process for SL in the V2X RX UE, the V2X RX UE may reject V2X communication with the V2X TX UE. In such an embodiment, the V2X RX UE may send (e.g., via PC5 RRC) a rejection message indicating that it does not have sufficient resources for V2X communication. The rejection message may be sent in response to receiving an RRC PC5 establishment message from the V2X TX UE. The RRC PC5 establishment message may be used to establish a unicast connection between the V2X TX UE and the V2X RX UE and may assign SL resources for HARQ feedback sent from the V2X RX UE.

[0081] Figure 10 FIG. is a flowchart illustrating an embodiment of method 1000 for communication using multiple radio access technologies. In some embodiments, method 1000 is performed by a device such as remote unit 102. In certain embodiments, method 1000 may be performed by a processor executing program code such as, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0082] In various embodiments, method 1000 includes receiving 1002 control information at a device using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0083] In various embodiments, the sidelink resource allocation information and the timing offset information are part of downlink control information. In some embodiments, the radio access technology information includes a radio network temporary identifier indicating that the sidelink resource allocation information is for a second radio access technology. In certain embodiments, the control information includes a downlink control information format.

[0084] In one embodiment, the downlink control information format includes a flag indicating that the sidelink resource allocation information is for a second radio access technology. In various embodiments, the use of the downlink control information format indicates that the sidelink resource allocation information is for a second radio access technology. In some embodiments, the sidelink resource allocation information activates a sidelink semi-persistent scheduling configuration, releases a sidelink semi-persistent scheduling configuration, dynamically allocates sidelink resources, or some combination thereof.

[0085] In some embodiments, the first radio access technology is a new radio interface and the second radio access technology is a Long-Term Evolution (LTE) interface. In one embodiment, the first radio access technology is an LTE interface and the second radio access technology is a new radio interface. In various embodiments, the timing offset information includes time, number of time slots, number of subframes, number of symbols, or some combination thereof.

[0086] Figure 11 FIG. is a flowchart illustrating another embodiment of method 1100 for communication using multiple radio access technologies. In some embodiments, method 1100 is performed by a device such as network unit 104. In certain embodiments, method 1100 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0087] In various embodiments, method 1100 includes transmitting 1102 control information to a device using a first radio access technology, where: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and where the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0088] In various embodiments, the sidelink resource allocation information and the timing offset information are part of the downlink control information. In some embodiments, the radio access technology information includes a radio network temporary identifier indicating that the sidelink resource allocation information is for a second radio access technology. In certain embodiments, the control information includes a downlink control information format.

[0089] In one embodiment, the downlink control information format includes a flag indicating that the sidelink resource allocation information is for a second radio access technology. In various embodiments, the use of the downlink control information format indicates that the sidelink resource allocation information is for a second radio access technology. In some embodiments, the sidelink resource allocation information activates a sidelink semi-persistent scheduling configuration, releases a sidelink semi-persistent scheduling configuration, dynamically assigns sidelink resources, or some combination thereof.

[0090] In certain embodiments, the first radio access technology is a new radio interface, while the second radio access technology is an LTE interface. In one embodiment, the first radio access technology is an LTE interface and the second radio access technology is a new radio interface. In various embodiments, the timing offset information includes time, number of time slots, number of subframes, number of symbols, or some combination thereof.

[0091] In one embodiment, a method includes: receiving, at a device, control information using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0092] In various embodiments, the sidelink resource allocation information and the timing offset information are part of the downlink control information.

[0093] In some embodiments, the radio access technology information includes a radio network temporary identifier indicating that the sidelink resource allocation information is for a second radio access technology.

[0094] In certain embodiments, the control information includes a downlink control information format.

[0095] In one embodiment, the downlink control information format includes a flag indicating that the sidelink resource allocation information is for a second radio access technology.

[0096] In various embodiments, the use of the downlink control information format indicates that the sidelink resource allocation information is for a second radio access technology.

[0097] In some embodiments, the sidelink resource allocation information activates a sidelink semi-persistent scheduling configuration, releases a sidelink semi-persistent scheduling configuration, dynamically assigns sidelink resources, or some combination thereof.

[0098] In certain embodiments, the first radio access technology is a new radio interface and the second radio access technology is a long term evolution interface.

[0099] In one embodiment, the first radio access technology is a long term evolution interface and the second radio access technology is a new radio interface.

[0100] In various embodiments, the timing offset information includes time, number of time slots, number of subframes, number of symbols, or some combination thereof.

[0101] In one embodiment, a device includes: a receiver that receives control information using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0102] In various embodiments, the sidelink resource allocation information and the timing offset information are part of the downlink control information.

[0103] In some embodiments, the radio access technology information includes a radio network temporary identifier indicating that the sidelink resource allocation information is for a second radio access technology.

[0104] In certain embodiments, the control information includes a downlink control information format.

[0105] In one embodiment, the downlink control information format includes a flag indicating that the sidelink resource allocation information is for a second radio access technology.

[0106] In various embodiments, the use of the downlink control information format indicates that the sidelink resource allocation information is for a second radio access technology.

[0107] In some embodiments, the sidelink resource allocation information activates a sidelink semi-persistent scheduling configuration, releases a sidelink semi-persistent scheduling configuration, dynamically allocates sidelink resources, or some combination thereof.

[0108] In certain embodiments, the first radio access technology is a new radio interface and the second radio access technology is a long term evolution interface.

[0109] In one embodiment, the first radio access technology is a long term evolution interface and the second radio access technology is a new radio interface.

[0110] In various embodiments, the timing offset information includes time, number of time slots, number of subframes, number of symbols, or some combination thereof.

[0111] In one embodiment, a method includes: transmitting control information to a device using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time for applying the sidelink resource allocation for the second radio access technology.

[0112] In various embodiments, the sidelink resource allocation information and the timing offset information are part of the downlink control information.

[0113] In some embodiments, the radio access technology information includes a radio network temporary identifier indicating that the sidelink resource allocation information is for a second radio access technology.

[0114] In some embodiments, the control information includes a downlink control information format.

[0115] In one embodiment, the downlink control information format includes a flag indicating sidelink resource allocation information for a second radio access technology.

[0116] In various embodiments, the use of the downlink control information format indicates sidelink resource allocation information for a second radio access technology.

[0117] In some embodiments, the sidelink resource allocation information activates a sidelink semi-persistent scheduling configuration, releases a sidelink semi-persistent scheduling configuration, dynamically allocates sidelink resources, or some combination thereof.

[0118] In certain embodiments, the first radio access technology is a new radio interface and the second radio access technology is a long term evolution interface.

[0119] In one embodiment, the first radio access technology is a long term evolution interface and the second radio access technology is a new radio interface.

[0120] In various embodiments, the timing offset information includes time, number of time slots, number of subframes, number of symbols, or some combination thereof.

[0121] In one embodiment, an apparatus includes: a transmitter that transmits control information to a device using a first radio access technology, wherein: the control information includes radio access technology information, sidelink resource allocation information, and timing offset information; the radio access technology information indicates that the sidelink resource allocation information is for a second radio access technology; and the first radio access technology is different from the second radio access technology; and wherein the timing offset information is used in the device to determine the time at which to apply the sidelink resource allocation for the second radio access technology.

[0122] In various embodiments, the sidelink resource allocation information and the timing offset information are part of the downlink control information.

[0123] In some embodiments, the radio access technology information includes a radio network temporary identifier indicating that the sidelink resource allocation information is for a second radio access technology.

[0124] In certain embodiments, the control information includes a downlink control information format.

[0125] In one embodiment, the downlink control information format includes a flag indicating sidelink resource allocation information for a second radio access technology.

[0126] In various embodiments, the use of the downlink control information format indicates sidelink resource allocation information for a second radio access technology.

[0127] In some embodiments, the sidelink resource allocation information activates a sidelink semi-persistent scheduling configuration, releases a sidelink semi-persistent scheduling configuration, dynamically assigns sidelink resources, or some combination thereof.

[0128] In certain embodiments, the first radio access technology is a new radio interface and the second radio access technology is a long term evolution interface.

[0129] In one embodiment, the first radio access technology is a long term evolution interface and the second radio access technology is a new radio interface.

[0130] In various embodiments, the timing offset information includes time, number of time slots, number of subframes, number of symbols, or some combination thereof.

[0131] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. Thus, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes within the meaning and range of equivalency of the claims are embraced within their scope.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receiving downlink control information (DCI) at a first time using a first radio access technology (RAT), wherein the first RAT is a new radio (NR) RAT, wherein the DCI has a DCI format that indicates sidelink resource allocation information and timing offset information for a second RAT, wherein the second RAT is a long term evolution (LTE) RAT, wherein the sidelink resource allocation information is used to schedule an LTE physical sidelink control channel (PSCCH) or an LTE physical sidelink shared channel (PSSCH), wherein the timing offset information is used to determine a second time at which to apply the sidelink resource allocation to the second RAT, wherein the second time is greater than or equal to an offset time plus the first time, and wherein the timing offset is at least one of a time, a number of time slots, a number of subframes, or a number of symbols.

2. The method according to claim 1, wherein A radio network temporary identifier (RNTI) associated with the received DCI indicates that the sidelink resource allocation information is for the second RAT.

3. The method according to claim 1, wherein, The sidelink resource allocation information activates a sidelink semi-persistent scheduling (SPS) configuration, releases a sidelink SPS configuration, or dynamically assigns sidelink resources, or a combination thereof.

4. A user equipment (UE) comprising: A processor; And A memory coupled to the processor, the processor being configured to cause the UE to: Receive downlink control information (DCI) at a first time using a first radio access technology (RAT), wherein the first RAT is a new radio (NR) RAT, wherein the DCI has a DCI format that indicates sidelink resource allocation information and timing offset information for a second RAT, wherein the second RAT is a long term evolution (LTE) RAT, wherein the sidelink resource allocation information is used to schedule an LTE physical sidelink control channel (PSCCH) or an LTE physical sidelink shared channel (PSSCH), wherein the timing offset information is used to determine a second time at which to apply the sidelink resource allocation to the second RAT, wherein the second time is greater than or equal to an offset time plus the first time, and wherein the timing offset is at least one of a time, a number of time slots, a number of subframes, or a number of symbols.

5. The UE according to claim 4, wherein, A radio network temporary identifier (RNTI) associated with the received DCI indicates that the sidelink resource allocation information is for the second RAT.

6. The UE according to claim 4, wherein, The sidelink resource allocation information activates a sidelink semi-persistent scheduling (SPS) configuration, releases a sidelink SPS configuration, or dynamically assigns sidelink resources, or a combination thereof.

7. A method performed by a base station, the method comprising: Transmitting downlink control information (DCI) at a first time using a first radio access technology (RAT), wherein the first RAT is a new radio (NR) RAT, wherein the DCI has a DCI format that indicates sidelink resource allocation information and timing offset information for a second RAT, Wherein, the second RAT is a Long-Term Evolution (LTE) RAT. Wherein, the sidelink resource allocation information is used to schedule the LTE Physical Sidelink Control Channel (PSCCH) or the LTE Physical Sidelink Shared Channel (PSSCH). Wherein, the timing offset information is used to determine a second time at which the sidelink resource allocation is applied to the second RAT. Wherein, the second time is greater than or equal to the offset time plus the first time, and wherein, the timing offset is at least one of time, number of time slots, number of subframes, or number of symbols.

8. The method according to claim 7, wherein A Radio Network Temporary Identifier (RNTI) associated with the received DCI indicates that the sidelink resource allocation information is for the second RAT.

9. The method according to claim 7, wherein The sidelink resource allocation information activates a sidelink semi-persistent scheduling (SPS) configuration, releases a sidelink SPS configuration, or dynamically assigns sidelink resources, or a combination thereof.

10. A base station, comprising: a processor; and a memory coupled to the processor, the processor being configured to cause the base station to: transmit a Downlink Control Information (DCI) at a first time using a first Radio Access Technology (RAT), wherein the first RAT is a New Radio (NR) RAT, wherein, the DCI has a DCI format that indicates sidelink resource allocation information and timing offset information for a second RAT, wherein, the second RAT is a Long-Term Evolution (LTE) RAT, wherein, the sidelink resource allocation information is used to schedule the LTE Physical Sidelink Control Channel (PSCCH) or the LTE Physical Sidelink Shared Channel (PSSCH), wherein, the timing offset information is used to determine a second time at which the sidelink resource allocation is applied to the second RAT, wherein, the second time is greater than or equal to the offset time plus the first time, and wherein, the timing offset is at least one of time, number of time slots, number of subframes, or number of symbols.

11. The base station according to claim 10, wherein, A Radio Network Temporary Identifier (RNTI) associated with the received DCI indicates that the sidelink resource allocation information is for the second RAT.

12. The base station according to claim 10, wherein, The sidelink resource allocation information activates a sidelink semi-persistent scheduling (SPS) configuration, releases a sidelink SPS configuration, or dynamically assigns sidelink resources, or a combination thereof.

Images