阅读说明：本技术 调度用户设备的选择 (Scheduling selection of user equipment ) 是由 凯斯基延·盖内森 普拉泰克·巴苏马利克 约阿希姆·勒尔 拉维·库奇波特拉 于 2020-03-11 设计创作，主要内容包括：公开了用于选择调度用户设备的装置、方法和系统。一种方法(400)包括从多个用户设备接收(402)第一信息,其中该第一信息指示与多个用户设备中的每个用户设备通信的至少一个侧链路用户设备。方法(400)包括基于第一信息中指示的多个用户设备中的每个用户设备的第一连接接口和第二连接接口的质量从多个用户设备中选择(404)调度用户设备。(Apparatus, methods, and systems for selecting scheduling user equipment are disclosed. A method (400) includes receiving (402) first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipments. The method (400) comprises selecting (404) a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.)

1. A method, comprising:

receiving first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipments; and

selecting a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

2. The method of claim 1, wherein the first connection interface comprises an interface between a user device and a network device.

3. The method of claim 1, wherein the second connection interface comprises an interface between a first user device and a second user device.

4. The method of claim 1, wherein the scheduled user equipment is selected from the plurality of user equipment in response to a first quality of the first connection interface being greater than a first threshold and a second quality of the second connection interface being greater than a second threshold.

5. The method of claim 1, wherein the quality of the first connection interface and the second connection interface is determined by measuring a sidelink reference signal received power.

6. The method of claim 1, wherein the first information is determined based on a sidelink reference signal received power, a sidelink positioning, or a combination thereof.

7. The method of claim 6, wherein the sidelink location is determined based on a global position location or a relative location.

8. The method of claim 7, wherein the relative position is based on time of arrival, time of flight, spatial measurements, angular measurements, angle of arrival, or some combination thereof.

9. The method of claim 1, further comprising: transmitting second information indicating the scheduled user equipment.

10. The method of claim 9, wherein the second information is transmitted via unicast or multicast signaling.

11. The method of claim 9, wherein the second information comprises a user equipment identifier corresponding to the scheduled user equipment, an allocation of a common resource, an allocation of user equipment specific resources, a type of broadcast allowed, an indication of sensing operation, sensing information corresponding to the common resource, a validity of the common resource, a scheduled user equipment communication range, a fallback mode of operation, a fallback side link carrier frequency, a fallback side link resource pool, or some combination thereof.

12. The method of claim 9, wherein the second information comprises short-term sensing parameters, time and frequency locations of sidelink control channels in a resource pool, demodulation reference signal configurations, or some combination thereof.

13. The method of claim 12, wherein the short-term sensing parameters comprise a threshold, a sensing window, a time and frequency location of a sidelink control channel in a resource pool, or some combination thereof.

14. The method of claim 1, further comprising: receiving updated first information from the plurality of user equipments.

15. The method of claim 14, further comprising: reselecting the scheduled user equipment from the plurality of user equipments based on the updated first information.

16. The method of claim 1, further comprising: transition to fallback mode in response to mode 2d resource allocation not being available and radio link failure or handover occurring.

17. The method of claim 16, wherein the fallback mode comprises mode 1, mode 2, a configured resource pool, a pre-configured resource pool, or some combination thereof.

18. The method of claim 1, wherein the scheduling user equipment indicates a group identifier, a resource pool resource, a priority value, or some combination thereof to one or more sidelink user equipment.

19. An apparatus, comprising:

a receiver that receives first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment that communicates with each of the plurality of user equipments; and

a processor that selects a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

20. The apparatus of claim 19, wherein the first connection interface comprises an interface between a user device and a network device.

Technical Field

The subject matter disclosed herein relates generally to wireless communications, and more particularly to scheduling selection of user equipment.

Background

The following abbreviations are defined herein, at least some of which are referred to in the following description: third generation partnership project ("3 GPP"), fifth generation ("5G"), authentication, admission 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 layer ("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"),(s), 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 multipoint ("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 extension ("DFTS"), downlink control information ("DCI"), downlink ("DL"), demodulation reference signal ("DMRS"), data radio bearer ("DRB"), discontinuous reception ("DRX"), "and, Downlink pilot time slots ("DwPTS"), enhanced clear channel assessment ("eCCA"), enhanced mobile broadband ("eMBB"), evolved node B ("eNB"), extensible authentication protocol ("EAP"), effective omni-directional 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 bands below the frequency range of 1-6 GHz and/or 410MHz to 7125MHz ("FR 1"), frequency range 2-24.25 GHz to 52.6GHz ("FR 2"), general geographic area description ("GAD"), group leader ("GL"), 5G node B or next generation node B ("gbb"), global navigation satellite system ("GNSS"), general packet radio service ("GPRS"), "enhanced mobile broadband (" eMBB "), enhanced mobile broadband (" eNB "), extended authentication protocol (" EAP "), extended orthogonal cover code division multiple access (" FD-OCC "), frequency division multiple access (" FDMA "), frequency division multiple access (" fdc "), frequency division multiple access (" gb "), or next generation node B (" gb "), or global navigation satellite system (" GNSS "), and/or a combination thereof, A guard period ("GP"), a global positioning system ("GPs"), a global system for mobile communications ("GSM"), a globally unique temporary UE identifier ("GUTI"), a home AMF ("hAMF"), a hybrid automatic repeat request ("HARQ"), a home location register ("HLR"), a handover ("HO"), a home PLMN ("HPLMN"), a home subscriber server ("HSS"), a hash expected response ("HXRES"), an identification or identifier ("ID"), an information element ("IE"), an international mobile equipment identification ("IMEI"), an international mobile subscriber identification ("IMSI"), an international mobile telecommunications ("IMT"), an internet of things ("IoT"), layer 1 ("L1"), layer 2 ("L2"), layer 3 ("L3"), a licensed assisted access ("LAA"), a local area network ("LAN"), a load-based device ("LBE"),(s), 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"), modulation coding scheme ("MCS"), master information block ("MIB"), multiple-input multiple-output ("MIMO"), mobility management ("MM"), mobility management entity ("MME"), mobile network operator ("MNO"), large-scale MTC ("MTC"), maximum power reduction ("MPR"), machine type communication ("MTC"), multi-user shared access ("MUSA"), non-access stratum ("NAS"), narrowband ("NB"), negative acknowledgement ("NACK") or NAK, "network entity (" NE "), network function (" NF "),(s), 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 slice instance ("NSI"), network slice selection assistance information ("NSSAI"), network slice selection function ("NSSF"), network slice selection policy ("NSSP"), operation, management, and maintenance system or operation and maintenance center ("OAM"), orthogonal frequency division multiplexing ("OFDM"), open loop ("OL"), other system information ("OSI"), power angular spectrum ("PAS"), physical broadcast channel ("PBCH"), power control ("PC"), UE-to-UE interface ("PC 5"), primary cell ("PCell"), policy control function ("PCF"), and/or a combination thereof, Physical cell identification ("PCI"), physical downlink control channel ("PDCCH"), packet data convergence protocol ("PDCP"), packet data network gateway ("PGW"), physical downlink shared channel ("PDSCH"), mode 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"), physical random access channel ("PRACH"), physical resource block ("PRB"), positioning reference signal ("PRS"), physical sidelink control channel ("PSCCH"), primary secondary cell ("PSCell"), physical sidelink feedback control channel ("PSFCH"), physical uplink control channel ("PUCCH"), physical uplink shared channel ("PUSCH"), ", and the like, 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"), 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"), RAN notification area ("RNA"), radio network temporary identifier ("RNTI"), reference signal ("RS"), remaining minimum system information ("RMSI"), (RST-RNTI, and radio access control information, Radio resource control ("RRC"), radio resource management ("RRM"), resource spreading 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"), security anchor function ("SEAF"), sidelink feedback content information ("SFCI"), service gateway ("SGW"), system information block ("SIB"), systemlnformationblocktype 1 ("SIB 1"), systemlnformationblocktype 2 ("SIB 2"), subscriber identification/identification module ("SIM"), signal-to-interference-plus-noise ratio ("SINR"), sidechain ("SL"), service level agreement ("SLA"), sidechain 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"), sidechain CSI RS ("S-CSI RS"), sidechain PRS ("S-PRS"), sidechain SSB ("S-SSB"), synchronization signal block ("SSB"), hidden identifier ("SUCI"), scheduling user equipment ("SUE"), supplemental uplink ("SUL"), (S-S-, A subscriber permanent identifier ("SUPI"), a tracking area ("TA"), a TA identifier ("TAI"), a TA update ("TAU"), a timing alignment timer ("TAT"), a transport block ("TB"), a transport block size ("TBs"), time division duplexing ("TDD"), time division multiplexing ("TDM"), time division-orthogonal cover code ("TD-OCC"), a temporary mobile subscriber identity ("TMSI"), a time of flight ("ToF"), a transmission power control ("TPC"), a transmission reception point ("TRP"), a transmission time interval ("TTI"), a transmission ("TX"), uplink control information ("UCI"), a unified data management function ("UDM"), a unified data repository ("UDR"), a user entity/device (mobile terminal) ("UE"), an uplink ("UL"), an UL SCH ("UL-SCH"), a TA-update ("TAU"), a timing alignment timer ("TAT"), a temporary mobile subscriber identity ("TMSI"), a transmission time offset (offset), a time offset, and/offset (offset) of a mobile terminal, a user equipment (mobile terminal) ("UE"), a mobile terminal, "UL SCH (" UL-SCH "") is transmitted over a transmission time offset, a mobile terminal, a terminal, Universal mobile telecommunications system ("UMTS"), user plane ("UP"), UP function ("UPF"), uplink pilot time slot ("UpPTS"), ultra-reliable and low-delay communications ("URLLC"), UE routing policy ("URSP"), vehicle-to-vehicle ("V2V"), vehicle-to-all ("V2X"), access NSSF ("vnsss"), access PLMN ("VPLMN"), wide area network ("WAN"), and worldwide interoperability for microwave access ("WiMAX").

In some wireless communication networks, user equipment may be used for scheduling.

Disclosure of Invention

A method for selecting scheduling user equipments is disclosed. The apparatus and system also perform the functions of the method. One embodiment of a method includes receiving first information from a plurality of user equipment, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipment. In some embodiments, the method comprises selecting a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

An apparatus for selecting a scheduled user equipment includes a receiver that receives first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipments. In some embodiments, the apparatus includes a processor that selects a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

Drawings

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for selecting a scheduled user equipment;

FIG. 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to schedule user equipment;

FIG. 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to select scheduling user equipment; and

figure 4 is a flow diagram illustrating one embodiment of a method for selecting to schedule user equipment.

Detailed Description

As will be appreciated by one skilled 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, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," module "or" system. Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store 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 the signal. In a certain embodiment, the storage device only employs signals for the access codes.

Some of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration ("VLSI") circuits or gate arrays, 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 or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, 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 over different computer-readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.

Any combination of one or more computer-readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. A storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, 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.

The code for performing the operations of an embodiment may be any number of lines and may be written in any combination including one or more of an object oriented programming language such as Python, Ruby, Java, Smalltalk, C + +, etc., and conventional procedural programming languages, such as the "C" programming language, and/or a machine language, such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer, partly on a remote computer or entirely on the 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 the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

Reference in the specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, 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 mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise. The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" also mean "one or more", unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics of the embodiments may 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 embodiments. One skilled in the relevant art will recognize, however, that an embodiment may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

Aspects of the embodiments are described below with reference to schematic flow charts 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 flow chart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow chart diagrams 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 produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart and/or schematic block diagram block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart and/or schematic block diagram block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The schematic flow charts and/or schematic block diagrams in the figures 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 flow chart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is contemplated that other steps and methods may be equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated figures.

Although various arrow types and line types may be employed in the flow chart diagrams and/or block diagram blocks, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of the elements in each figure may refer to elements of the previous figures. Throughout the drawings, like numerals refer to like elements, including alternative embodiments of the same elements.

Fig. 1 depicts an embodiment of a wireless communication system 100 for selecting scheduled user equipments. In one embodiment, wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a particular number of remote units 102 and network units 104 are depicted in fig. 1, 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.

In one embodiment, remote unit 102 may include a computing device such as a desktop computer, laptop computer, personal digital assistant ("PDA"), tablet computer, smart phone, smart television (e.g., television connected to the internet), set-top box, game console, security system (including surveillance cameras), on-board computer, networking device (e.g., router, switch, modem), airborne vehicle, drone, or the like. In some embodiments, remote unit 102 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, and so forth. Moreover, 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 terminology used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote units 102 may communicate directly with other remote units 102 via sidelink communications.

The network elements 104 may be distributed over a geographic area. In certain embodiments, the network element 104 may also be referred to as an access point, access terminal, base station, node-B, eNB, gNB, home node-B, relay node, device, core network, over-the-air server, radio access node, AP, NR, network entity, AMF, UDM, UDR, UDM/UDR, PCF, RAN, NSSF, or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 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 public switched telephone networks, among others. These and other elements of the radio access and core networks are not illustrated but are generally well known to those of ordinary skill in the art.

In one embodimentThe wireless communication system 100 conforms to the NR protocol standardized in 3GPP, where the network elements 104 transmit on the DL using an OFDM modulation scheme and the remote units 102 transmit on the UL using an SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, CDMA, GSM, CDMA, and/or GSM, and/or UMTS, and/or GSM, and/or UMTS, and/or LTE, and/or CDMA, variants,ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to implementation by any particular wireless communication system architecture or protocol.

Network element 104 may serve multiple remote units 102 within a service area, e.g., a cell or cell sector, via a wireless communication link. The network unit 104 transmits DL communication signals to serve the remote unit 102 in the time, frequency, and/or spatial domains.

In various embodiments, the network element 104 may receive first information from a plurality of user equipment (e.g., the remote unit 102), wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipment. In some embodiments, the network element 104 may select the scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information. Thus, the network element 104 may be used to schedule the selection of user equipments.

Fig. 2 depicts one embodiment of an apparatus 200 that may be used as a scheduling user equipment. The apparatus 200 includes one embodiment of the remote unit 102. In addition, remote unit 102 may include a processor 202, memory 204, input device 206, display 208, transmitter 210, and 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 some embodiments, remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and/or display 208.

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, the processor 202 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processor ("GPU"), auxiliary processing unit, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212.

In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, the 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 drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and nonvolatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system and other controller algorithms operating on remote unit 102.

In one embodiment, input device 206 may comprise any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, and the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touch screen or similar touch sensitive display. In some embodiments, the input device 206 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

In one embodiment, the display 208 may comprise any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or tactile signals. In some embodiments, display 208 comprises 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 similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, display 208 may include a wearable display such as a smart watch, smart glasses, heads-up display, and the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alarm or notification (e.g., a buzz or beep). In some embodiments, the display 208 includes one or more haptic devices for generating vibrations, motions, 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 touch screen or similar touch sensitive display. In other embodiments, the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to the network element 104 and the receiver 212 is used to receive DL communication signals from the network element 104, as described herein.

In some embodiments, the transmitter 210 may transmit messages to other remote units 102. Although only one transmitter 210 and one receiver 212 are illustrated, remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

Fig. 3 depicts one embodiment of an apparatus 300 that may be used to schedule a selection of user equipment. The apparatus 300 includes one embodiment of the network element 104. Further, the network element 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It is to be appreciated that processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212, respectively, of remote unit 102.

In various embodiments, the receiver 312 may receive first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipments. In some embodiments, the processor 302 may select a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

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

In some embodiments, V2X resource allocation may be based on mode 2d operational procedures in the physical layer (e.g., such as an indication of interest to become a SUE, selection of a SUE, creation of neighbor lists based on L1 measurements or SL positioning, resource allocation, and fallback operational modes). In such embodiments, the application layer may not know the radio link quality of the UE and may not select the correct scheduling UE for the group. Further, in such embodiments, the BS may be involved to select the SUE in the selection process.

In some embodiments, there may be two SL resource allocation patterns: mode 1, in which a BS schedules SL resources to be used by a UE for SL transmission; and mode 2, in which the UE determines (e.g., the BS does not schedule) SL transmission resources within SL resources configured by the BS, the network, or pre-configured SL resources.

In various embodiments, the definition of SL resource allocation pattern 2 may include: a) UE autonomously selects SL resources for transmission; b) the UE assists other UEs to select SL resources; c) the UE is configured with NR configured grants (e.g., as type-1) for SL transmission; and/or d) the UE schedules SL transmissions for other UEs.

In some embodiments, in the context of mode 2(d), NR V2X may support the following functionality: a) the UE informs the gNB of the group members, and the gNB provides a separate resource pool configuration and/or a separate resource configuration to each group member UE in the same group through the same UE-it may not require a connection between the member UE and the gNB; b) the UE cannot modify the configuration provided by the gNB; c) higher layer signaling may be used to provide configuration-physical layer signaling is not used; d) one or two resource pool configurations and resource configurations may be supported; and/or e) the functionality defined as part of mode 2 may be applicable to this feature. It will be appreciated that the functionality described herein may depend on the UE capabilities.

In some embodiments, such as for group-based SL communication, UE-A may inform its serving gNB of the group's members UE-B, UE-C, etc., and the gNB may provide each group member with a separate resource pool configuration and/or a separate resource configuration via UE-A. In such an embodiment, UE-a cannot modify the configuration and no direct connection between any member UE and the gNB is required. The configuration may be provided using higher layer only signaling, and such functionality may depend on the UE capabilities.

As used herein, the terms eNB and/or gNB may be used for a base station, but it may be replaced by any other radio access node (e.g., BS, eNB, gNB, AP, NR, etc.). Furthermore, various methods can be described in the context of 5G NR; however, these methods are equally applicable to other mobile communication systems supporting serving cells and/or carriers configured for sidelink communications via a PC5 interface.

In various embodiments, the V2X transmitting UE may periodically receive and/or decode SCIs from other neighboring UEs, and the SCI content may include information about the source ID, destination ID, and/or group ID. In some embodiments, group V2X formation may occur in two ways: 1) groups are formed semi-statically based on layer 2ID or in the application layer of a session-specific application (e.g., queue, etc.); and 2) dynamically configuring the group based on a certain communication range.

In some embodiments, each V2X UE may be aware of neighbor UEs that may be members of its group. In such embodiments, the V2X UE may create and/or maintain one or more neighbor lists for each layer 2 group ID or application ID based on SL 1 RSRP and/or RSSI measured from PSCCH DMRS.

In various embodiments, as part of the SUE selection process criteria, the UEs may nominate themselves to assume the role of SUE by communicating an interest indication to the gNB. In such embodiments, if there are many UEs of interest, as part of the selection process, the gNB may select a SUE based on the quality of the Uu and/or PC5 connections of the UE (e.g., as determined by measuring the SL RSRP of the group members), where the quality is above a corresponding threshold.

In some embodiments, as part of signaling an interest indication to the gNB regarding the intent of the UE to be a SUE, the UE may transmit additional information such as a group ID, the number of identified group members that may be included in the neighbor list, the number of active transmitters that may be part of the group members, the minimum QoS and/or maximum QoS range of the group members, the degree of automation of the group members (e.g., may be a higher degree of low automation and/or a highest degree of automation, possibly indirectly related to the delay and/or reliability requirements of the group members), the rate of transmission of the message, the size of the message, the type of dissemination (cast type), and so forth. In such embodiments, the interest indication signaling from the UE to the gNB may be performed using RRC signaling, using MAC CE signaling, using L1 signaling, in conjunction with additional information, as part of a UE-assisted report, and/or as part of a measurement report. Further, in such embodiments, the gNB provides SL L1 RSRP and/or RSSI thresholds for group member identification to the UE, or the gNB filters the group members shared by interested UEs and/or the required communication range provided by higher layers based on the RSRP and/or RSSI thresholds.

In one embodiment, the UE may share a neighbor cell list and/or a number of neighbor group members with the BS with or without the PC5 link quality as needed and when needed (e.g., for SUEs seeking resources to schedule group members, indicating member UEs interested in becoming SUEs, etc.). In some embodiments, the BS may explicitly query UEs belonging to a certain group, a certain geographical area, and/or communication range to transmit the interest indication. In some embodiments, the UE (e.g., based on UE capabilities) may include one or more features with transmission of an indication of interest to the BS (e.g., relay capability, more number of antennas for Uu and/or SL, high transmit power, ability to form multiple beams, and/or automobile capability (such as height of automobile, high battery capacity, etc.).

In some embodiments, a sidelink location method may be used to determine group members within a communication range. With the SL positioning method, the TX UE may determine the location of the RX UEs in the group or may infer information of the RX UE location therefrom. The information used to infer the RX UE location may be the global location coordinates of the RX UE from the latest received transmission of the TX UE or some relative positioning information, which may be based on time of arrival, flight measurements, spatial measurements, and/or angle measurements (e.g., AoA, AoD).

In some embodiments, the RX UE may be configured to report time of arrival, AoA, and/or AoD measurements from the configured set of RSs, and the RSs may be S-SSB, S-CSI RS, or S-PRS transmissions from the TX UE. The TX UE may perform beam scanning transmission of RSs from multiple antenna panels and may indicate that relative positioning measurement reports are reported in the SCI. In one embodiment, the RX UE reports the beam ID and relative positioning report to the TX UE. The number of beams used for RS transmission may vary from antenna panel to antenna panel (e.g., depending on the size of the antenna panel-the number of antenna elements, the directivity and/or launch angle capabilities of the antenna panel, and/or the placement of the antenna panel on the vehicle). In various embodiments, a set of resources including an RS resource identifier and a sequence ID configured for beam scanning transmission may be indicated in the SCI by the TX UE using multicast or broadcast transmission. In some embodiments, the RX UE reports the beam index of the strongest received RS and the Tx UE maps the index of the strongest received RS beam to the beam direction. The beam direction may be used to calculate AoD. In some embodiments, the RX UE may report the ToF and/or AoA to the TX UE. The feedback resources and/or feedback timing of the RX UE may be semi-statically or dynamically configured by the TX UE or BS.

In various embodiments, as part of the selection process, the gNB determines (e.g., selects) the SUE based on the radio link quality in Uu and/or PC 5. In such embodiments, the SUE may identify a greater number of member UEs than other UEs in the group. In certain embodiments, after the gNB receives an interest indication signaling that the UE is interested in becoming a SUE, the gNB checks whether mode 2d operation can be enabled in its cellular region, its geographic region, and/or based on the availability of resources. If mode 2d operation is not enabled, the gNB may transmit a reject message to the UE, and if there are not enough resources available, the gNB may notify the UE of the transmission request after a certain period of time. If mode 2d operation is enabled, the gNB transmits information indicating the selection of the SUE to its group members via unicast or multicast signaling with additional information (e.g., the UE ID of the SUE, the common resources allocated for the group members and/or the resources allocated to each member of the group, the type of dissemination allowed, a flag indicating whether the member UEs are able to perform a sensing operation to select a resource, the long-term and/or short-term sensing required by the group members to select a resource from the common resources, the validity of the resource, the communication range of the SUE, the fallback mode of operation due to mobility events, the fallback SL carrier frequency and/or the resource pool). In some embodiments, signaling to the member UEs may be performed directly by the gNB (e.g., to in-coverage UEs and/or RRC-connected UEs) and/or directly via the selected SUE (e.g., to out-of-coverage UEs, RRC-idle UEs, or UEs in neighboring cells — because the SUE may not be aware of the member's Uu state, it performs multicast transmissions). In some embodiments, the gsb notifies the SUE using one or more of RRC signaling, MAC CE signaling, and/or SCI signaling. In various embodiments, the gNB may use a flag in the RRC, MIB, and/or SIB to indicate whether mode 2d operation is enabled. In some embodiments, the SUE may relay messages to the group members using multicast transmissions in PC5RRC, PSBCH, PSCCH, and/or pscsch. In some embodiments, the SUE may facilitate reception of group members using beam-sweeping transmissions and/or multicast HARQ ACK/NACK feedback. In various embodiments, the dedicated resources provided by the gNB to each group member may be relayed by the SUE via PC5 unicast transmissions via PC5RRC, psch, PSCCH, and/or MAC CE. In some embodiments, the fallback mode of operation and the resource pool may be indicated by the gNB in one SIB message.

In some embodiments, the resource selection method of group members on a common resource may depend on the availability of the resource provided by the gNB or the SUE. The UE autonomously uses short-term sensing and/or random selection of common resources if the validity of the resources is less than the long-term sensing window size. In such embodiments, the gNB or SUE may provide information about short-term sensing parameters (e.g., thresholds, sensing windows, psch times, and/or frequency locations in a common resource pool). In various embodiments, the gNB or SUE may provide the time and frequency location of the PSCCH and the DMRS configuration in the resource pool (e.g., assuming that the PSCCH and PSCCH are located in the same resource pool). In such embodiments, the member UE may use this information about PSCCH-DMRS to perform short-term energy sensing within a configured sensing window and determine whether resources are available for transmission. In some embodiments, if the gNB or SUE provides multiple patterns and/or configured grant type1 (e.g., the pattern is defined by the size and location of resources in time and frequency and the number of resources) for group members to select via multicast or unicast signaling (e.g., via SCI, MAC CE, and/or PC5 RRC), then the group members perform short term energy sensing on the psch-DMRS to select the unused pattern. It may be appreciated that each mode may use the same configured DMRS location; otherwise, if the location of the DMRS in each pattern is different, the group member UE may be signaled. In some embodiments, the SUE may configure the sidelink mode of operation for the group members via multicast or unicast signaling, which may be SCI, MAC CE, and/or PC5RRC based. In various embodiments, the sidechain sub-pattern may include sidechain dynamic scheduling by SUEs. The operation of this sub-mode may be similar to the resource allocation of mode 1. The concept of SR/BSR to request resources and transmit buffer status reports may be used for this sub-mode. New sidelink physical channels may be used to carry SR, BSR, PHR, and/or power control commands may be defined for information exchange between SUEs and group members. The power control commands may be indicated in SFCI, PSFCH, PSCCH, and/or pscsch. In some embodiments, the SUE may transmit resources such as configured grant type1 and/or configured grant type2 of the resources to each group member UE via multicast or unicast signaling and via SCI, MAC CE, and/or SCI formatted activation and/or deactivation messages. The SCI format may be defined for any of the SUE procedures described herein.

In some embodiments, the gNB (e.g., in addition to selecting a SUE) may select a candidate SUE or a list of candidate SUEs based on interest indication messages received from one or more UEs. The gNB may notify the group members of the list of candidate SUEs. The candidate SUE list may be periodically evaluated and refreshed based on the radio link quality of Uu and/or PC5 (e.g., PC5 radio link quality may be based on neighbor measurements which may be RSRP-based or location-based). If the link quality of the candidate SUE is better than the serving SUE, the gNB may reselect the SUE. In various embodiments, monitoring link quality may include Uu quality of candidate SUEs for RRC connections and/or PC5 link quality of group members with which the candidate UE is identified.

In some embodiments, a fallback mode of operation may exist due to mobility events such as RLF and/or handover. If mode 2d based resource allocation is not available, a fallback mode of operation is used. The fallback mode of operation can fallback to any other scheduling method, including mode 1, mode 2 (e.g., any mode 2 sub-mode), and/or a preconfigured resource pool with or without sensing operations.

In various embodiments, for a SUE's radio link failure with respect to the gNB, the gNB may reselect the SUE from the candidate list as the next serving SUE, or because the SUE is aware of the candidate SUE list, the SUE may multicast to the candidate SUE a SUE regarding the impending radio link failure. Each candidate SUE may evaluate the link quality for the gNB and then multicast to the group members with their UE IDs will become the serving SUE. In one embodiment, if there is more than one candidate SUE, the candidate SUE of the group member UE with the largest number of identifications is selected.

In some embodiments, if one of the group members UE or SUE initiates a handover, the serving gNB may signal a grant in a handover command as part of the UE context information for mode 2d operation in the target gNB with additional information such as number of active transmitters, QoS, resource requirements, etc. If the target gNB accepts the handover request and provides new resources from its cell, the serving gNB may inform the SUE and/or the group member UEs of the configuration of the target gNB. If mode 2d operation is not possible in the target gNB and/or the target gNB does not have sufficient resources, the source gNB can switch the group to a fallback mode of operation, such as mode 1, mode 2a, or mode 2 c. In some embodiments, the SUE may notify group members of the change in operating mode via sidelink signaling, which may be SCI, MAC CE, and/or PC5 RRC. If SCI is used, a bit field may be used to indicate the mode and/or a particular SCI format may be used to distinguish between each mode.

In some embodiments, SUE selection may be based on PC5 link quality with its neighboring UEs. The neighboring UEs may be synchronization reference UEs, or any other UEs in the group, in a particular geographic area, and/or based on group members identified from their neighbors. In one embodiment, a UE acting as a synchronization reference UE (e.g., providing sidelink timing information to a group of UEs) or any other UE may explicitly transmit a request message via a multicast PSCCH to transmit SL RSRP and/or RSSI measurements based on configured RSs, which may be S-SSBs, S-CSI RSs, S-DMRS-PSCCH, and/or SL positioning. In some embodiments, the UE may transmit the interest indication to other neighboring UEs via PC5RRC, MAC CE, PDCP control, SCI, etc., via sidelink multicast or broadcast transmission with various parameters.

In various embodiments, the resource selection of the SUE may be performed by a sensing operation, which may include receiving and/or decoding SCIs on the indicated resource pool. In some embodiments, the SUE may indicate a group ID (e.g., layer 1 group ID, layer 2 group ID, etc.) in the source ID field and/or the required resources (e.g., in terms of number of resource pools, validity period of the resources, etc.) in SCI transmissions to other UEs. The SUE may also indicate a priority value in the QoS priority that indicates to other UEs to reserve resources for mode 2d operation. In some embodiments, the SCI format may be used to indicate mode 2d operation to other UEs. In some embodiments, only SUEs in a group may sense and reserve resources on behalf of group members.

In some embodiments, SUE selection is based on the quality of the Uu and/or PC5 connections (e.g., obtained by measuring the SL RSRP of the group members) being above a respective threshold.

In some embodiments, the SUE may create a neighbor list (e.g., corresponding to an L2 ID or application layer group ID) for each destination group based on SL RSRP and/or SL positioning.

In various embodiments, the UE may share a neighbor cell list and/or a number of neighbor group members with the BS with or without PC5 link quality as needed and when needed (e.g., for SUEs seeking resources to schedule group members, for member UEs indicating an interest in becoming SUEs, etc.).

In some embodiments, the gNB selects a SUE and notifies the group members using the L2 ID of the selected SUE. In such embodiments, additional parameters may also be signaled, such as the type of broadcast allowed, the duration of resource pool validity, and so forth. Signaling member UEs may be done directly by the gNB (e.g., to in-coverage and/or RRC-connected UEs) and/or through a selected SUE (e.g., to out-of-coverage UEs, RRC-idle UEs, and/or UEs in a neighboring cell). The SUE may perform multicast transmission because the SUE may not be aware of the Uu status of the member UEs.

In some embodiments, the gNB may maintain a list of candidate SUEs and may continuously monitor the link quality of the candidate SUEs. This may result in a SUE being reselected.

In various embodiments, monitoring link quality may include Uu quality of candidate SUEs for RRC connection of group members identified thereby and/or PC5 link quality of the candidate SUEs.

In some embodiments, a fallback mode of operation may exist due to mobility events such as RLF and/or handover. In such embodiments, if mode 2d based resource allocation is not available, a fallback mode of operation may be used, enabling fallback to any other scheduling method including mode 1, mode 2, and/or a preconfigured resource pool with or without inductive operation.

In certain embodiments, the SUE reports member UEs within a minimum communication range indicated by upper layers and/or reports active member UEs within a minimum communication range. As can be appreciated, an active member UE may refer to a group member with potential V2X messaging needs.

Figure 4 is a flow diagram illustrating one embodiment of a method 400 for selecting a scheduled user equipment. In some embodiments, the method 400 is performed by an apparatus, such as the network element 104. In certain embodiments, the method 400 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

The method 400 may include receiving 402 first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipments. In some embodiments, the method 400 includes selecting 404 a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

In some embodiments, the first connection interface comprises an interface between the user device and the network device. In some embodiments, the second connection interface comprises an interface between the first user device and the second user device. In various embodiments, a scheduled user equipment is selected from a plurality of user equipments in response to a first quality of a first connection interface being greater than a first threshold and a second quality of a second connection interface being greater than a second threshold.

In one embodiment, the quality of the first connection interface and the second connection interface is determined by measuring the sidelink reference signal received power. In certain embodiments, the first information is determined based on sidelink reference signal received power, sidelink positioning, or a combination thereof.

In some embodiments, the sidelink location is determined based on a global position location or a relative location. In various embodiments, the relative position is based on time of arrival, time of flight, spatial measurements, angular measurements, angle of arrival, or some combination thereof. In one embodiment, the method 400 further comprises transmitting second information indicating scheduling of the user equipment.

In some embodiments, the second information is transmitted via unicast or multicast signaling. In some embodiments, the second information comprises a user equipment identity corresponding to a scheduled user equipment, an allocation of a common resource, an allocation of user equipment specific resources, an allowed broadcast type, a sensing operation indication, sensing information corresponding to a common resource, a validity of a common resource, a scheduled user equipment communication range, a fallback operation mode, a fallback sidelink carrier frequency, a fallback sidelink resource pool, or some combination thereof. In various embodiments, the second information includes short-term sensing parameters, time and frequency locations of sidelink control channels in the resource pool, demodulation reference signal configurations, or some combination thereof.

In one embodiment, the short-term sensing parameters include a threshold, a sensing window, a time and frequency location of a sidelink control channel in the resource pool, or some combination thereof. In some embodiments, the method 400 further comprises receiving updated first information from a plurality of user devices. In some embodiments, the method 400 further comprises reselecting a scheduled user equipment from the plurality of user equipments based on the updated first information.

In various embodiments, the method 400 further comprises transitioning to a fallback mode in response to the mode 2d resource allocation not being available and an occurrence of a radio link failure or handover. In one embodiment, the fallback mode comprises mode 1, mode 2, a configured resource pool, a pre-configured resource pool, or some combination thereof. In some embodiments, the scheduling user equipment indicates a group identifier, resource pool resources, priority value, or some combination thereof to one or more side link user equipments.

In one embodiment, a method comprises: receiving first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each of the plurality of user equipments; and selecting a scheduling user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

In some embodiments, the first connection interface comprises an interface between the user device and the network device.

In some embodiments, the second connection interface comprises an interface between the first user device and the second user device.

In various embodiments, a scheduled user equipment is selected from a plurality of user equipments in response to a first quality of a first connection interface being greater than a first threshold and a second quality of a second connection interface being greater than a second threshold.

In one embodiment, the quality of the first connection interface and the second connection interface is determined by measuring a side link reference signal received power.

In certain embodiments, the first information is determined based on sidelink reference signal received power, sidelink positioning, or a combination thereof.

In some embodiments, the sidelink location is determined based on a global position location or a relative location.

In various embodiments, the relative position is based on time of arrival, time of flight, spatial measurements, angular measurements, angle of arrival, or some combination thereof.

In one embodiment, the method further comprises transmitting second information indicating that the user equipment is scheduled.

In some embodiments, the second information is transmitted via unicast or multicast signaling.

In some embodiments, the second information comprises a user equipment identifier corresponding to a scheduled user equipment, an allocation of a common resource, an allocation of user equipment specific resources, a type of broadcast allowed, a sensing operation indication, sensing information corresponding to a common resource, a validity of a common resource, a scheduled user equipment communication range, a fallback mode of operation, a fallback sidelink carrier frequency, a fallback sidelink resource pool, or some combination thereof.

In various embodiments, the second information includes short-term sensing parameters, time and frequency locations of sidelink control channels in the resource pool, demodulation reference signal configurations, or some combination thereof.

In one embodiment, the short-term sensing parameters include a threshold, a sensing window, a time and frequency location of a sidelink control channel in the resource pool, or some combination thereof.

In some embodiments, the method further comprises receiving updated first information from a plurality of user devices.

In some embodiments, the method further comprises reselecting a scheduled user equipment from the plurality of user equipments based on the updated first information.

In various embodiments, the method further comprises transitioning to a fallback mode in response to the mode 2d resource allocation not being available and an occurrence of a radio link failure or handover.

In one embodiment, the fallback mode comprises mode 1, mode 2, a configured resource pool, a pre-configured resource pool, or some combination thereof.

In some embodiments, the scheduling user equipment indicates a group identifier, resource pool resources, priority value, or some combination thereof to one or more side link user equipments.

In one embodiment, an apparatus comprises: a receiver that receives first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment that communicates with each of the plurality of user equipments; and a processor that selects a scheduled user equipment from the plurality of user equipments based on the quality of the first connection interface and the second connection interface of each of the plurality of user equipments indicated in the first information.

In some embodiments, the first connection interface comprises an interface between the user device and the network device.

In some embodiments, the second connection interface comprises an interface between the first user device and the second user device.

In various embodiments, a scheduled user equipment is selected from a plurality of user equipments in response to a first quality of a first connection interface being greater than a first threshold and a second quality of a second connection interface being greater than a second threshold.

In one embodiment, the quality of the first connection interface and the second connection interface is determined by measuring the sidelink reference signal received power.

In certain embodiments, the first information is determined based on sidelink reference signal received power, sidelink positioning, or a combination thereof.

In some embodiments, the sidelink location is determined based on a global position location or a relative location.

In various embodiments, the relative position is based on time of arrival, time of flight, spatial measurements, angular measurements, angle of arrival, or some combination thereof.

In one embodiment, the apparatus further comprises a transmitter that transmits second information indicating that the user equipment is scheduled.

In some embodiments, the second information is transmitted via unicast or multicast signaling.

In some embodiments, the second information comprises a user equipment identity corresponding to a scheduled user equipment, an allocation of a common resource, an allocation of user equipment specific resources, an allowed broadcast type, a sensing operation indication, sensing information corresponding to a common resource, a validity of a common resource, a scheduled user equipment communication range, a fallback operation mode, a fallback sidelink carrier frequency, a fallback sidelink resource pool, or some combination thereof.

In various embodiments, the second information includes short-term sensing parameters, time and frequency locations of sidelink control channels in the resource pool, demodulation reference signal configurations, or some combination thereof.

In one embodiment, the short-term sensing parameters include a threshold, a sensing window, a time and frequency location of a sidelink control channel in the resource pool, or some combination thereof.

In some embodiments, the receiver receives updated first information from a plurality of user equipments.

In some embodiments, the processor reselects the scheduled user equipment from the plurality of user equipments based on the updated first information.

In various embodiments, the processor transitions to the fallback mode in response to the mode 2d resource allocation not being available and an occurrence of a radio link failure or handover.

In one embodiment, the fallback mode comprises mode 1, mode 2, a configured resource pool, a pre-configured resource pool, or some combination thereof.

In some embodiments, the scheduling user equipment indicates a group identifier, resource pool resources, priority value, or some combination thereof to one or more side link user equipments.

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