WO2020069182A1 - Procédés de synchronisation de liaison latérale pour v2x en nr - Google Patents

Procédés de synchronisation de liaison latérale pour v2x en nr Download PDF

Info

Publication number
WO2020069182A1
WO2020069182A1 PCT/US2019/053238 US2019053238W WO2020069182A1 WO 2020069182 A1 WO2020069182 A1 WO 2020069182A1 US 2019053238 W US2019053238 W US 2019053238W WO 2020069182 A1 WO2020069182 A1 WO 2020069182A1
Authority
WO
WIPO (PCT)
Prior art keywords
synchronization
sidelink
wtru
synchronization source
platoon
Prior art date
Application number
PCT/US2019/053238
Other languages
English (en)
Inventor
Kyle Jung-Lin Pan
Fengjun Xi
Chunxuan Ye
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2020069182A1 publication Critical patent/WO2020069182A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others

Definitions

  • Recent Third Generation Partnership Project (3GPP) standards discussions define several deployment scenarios such as indoor hotspot, dense urban, rural, urban macro, and high speed.
  • ITU-R International Telecommunication Union Radiocommunication Sector
  • Next Generation Mobile Networks (NGMN) and 3GPP use cases for emerging 5G systems may be broadly classified as enhanced mobile broadband (eMBB), massive machine type communications (mMTC) and ultra-reliable and low latency communications (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable and low latency communications
  • These use cases focus on meeting different performance requirements such as higher data rate, higher spectrum efficiency, low power and higher energy efficiency, and/or lower latency and higher reliability.
  • a wide range of spectrum bands ranging from 700 MHz to 80 GHz are being considered for a variety of deployment scenarios.
  • Methods for sidelink synchronization may be used by a wireless transmit/receive unit (WTRU) that wants to a join a group of WTRUs, such as a vehicle platoon, and may be used for vehicle-to-everything (V2X) in New Radio (NR).
  • the WTRU may receive configuration information for sidelink communications, wherein the configuration information includes measurement thresholds.
  • the WTRU may monitor a sidelink channel for signals from a plurality of synchronization sources.
  • the WTRU may perform a sidelink measurements on sidelink synchronization signals from each of the plurality of synchronization sources, and determine synchronization source type and hop number for each of the plurality of synchronization sources based on information carried in the respective sidelink synchronization signal.
  • the WTRU may compile a list of synchronization sources from the plurality of synchronization sources for which a value of the sidelink measurement is greater than a first sidelink measurement threshold.
  • the WTRU may select the synchronization source with synchronization source type that is platoon leader type. If no synchronization source in the list is a platoon leader synchronization source type, then the WTRU may select the synchronization source with hop number less than the first hop number threshold. If no synchronization source in the list of synchronization sources has a hop number less than a first hop number threshold, then the WTRU may select the synchronization source for which the value of the sidelink measurement is greater than a second sidelink measurement threshold. The WTRU may establish a link with the selected synchronization source.
  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit
  • WTRU that may be used within the communications system illustrated in FIG. 1A according to an embodiment
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment
  • FIG. 2 is a signaling diagram of an example sidelink WTRU information exchange procedure for communication between a (vehicle) WTRU and the eNB for vehicle-to-everything (V2X) sidelink transmissions;
  • V2X vehicle-to-everything
  • FIG. 3 is a network diagram of an example vehicle platoon including a platoon leader and platoon followers;
  • FIG. 4 is a flow diagram of an example synchronization source selection method based on measurement, measurement type and synchronization source type
  • FIG. 5 is a flow diagram of an example synchronization source selection method based on absolute and relative measurement, measurement type and synchronization source type
  • FIG. 6 is a flow diagram of an example synchronization source selection method based on measurement, measurement type, synchronization source type and number of hops;
  • FIG. 7 is a flow diagram of an example synchronization source selection method based on measurement, measurement type and synchronization source type, number of hops and link capacity
  • FIG. 8 is a flow diagram of an example synchronization source selection method based on measurement, measurement type, synchronization source type, number of hops, link capacity, and traffic load;
  • FIG. 9 is a flow diagram of an example synchronization source selection method based on measurement, measurement type and synchronization source type, and number of hops.
  • FIG. 10 is a flow diagram of an example synchronization assistance information method for NR V2X sidelink, which may be performed by a WTRU that is a member of a vehicle platoon.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/1 13, a ON 106/1 15, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 1 12, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 1 14a and/or a base station 114b.
  • Each of the base stations 1 14a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 1 10, and/or the other networks 112.
  • the base stations 1 14a, 1 14b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 1 14a, 1 14b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/1 13, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • the base station 1 14a and/or the base station 1 14b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 1 14a may be divided into three sectors.
  • the base station 1 14a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 1 14a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs
  • an air interface 1 16 which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 1 16 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 1 14a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 1 15/116/1 17 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High- Speed UL Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 1 16 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 1 16 using New Radio (NR).
  • a radio technology such as NR Radio Access , which may establish the air interface 1 16 using New Radio (NR).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.1 1 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.1 1 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-2000 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 1 14b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.1 1 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 1 14b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 1 14b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 1 14b may have a direct connection to the Internet 1 10.
  • the base station 1 14b may not be required to access the Internet 1 10 via the CN 106/115.
  • the RAN 104/1 13 may be in communication with the CN 106/1 15, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/1 15 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/1 15 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/1 13 or a different RAT.
  • the CN 106/1 15 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/1 15 may also serve as a gateway for the WTRUs 102a, 102b, 102c,
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 1 10 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • IP internet protocol
  • the networks 1 12 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 1 12 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links.
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 1 14a, which may employ a cellular-based radio technology, and with the base station 1 14b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG.
  • the WTRU 102 may include a processor 1 18, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.
  • GPS global positioning system
  • the processor 1 18 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 1 18 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 1 18 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 1 18 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 1 16.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 1 16.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.1 1 , for example.
  • the processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 1 18 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 1 18 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 1 16 from a base station (e.g., base stations 1 14a, 1 14b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 1 18).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell
  • the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME)
  • MME mobility management entity
  • a serving gateway (SGW) 164 a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SGW serving gateway
  • PDN packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs
  • 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 1 10
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 1 12 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • DS Distribution System
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer- to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.1 1e DLS or an 802.1 1 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an“ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.1 1 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.1 1 af and 802.1 1 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.1 1 af and 802.1 1 ah relative to those used in 802.1 1 h, and 802.11 ac.
  • 802.1 1 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 h, 802.1 1 ac, 802.11 af, and 802.1 1 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all ST As in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • 802.1 1 ah are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 1 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 1 15 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 1 13 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 1 13 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs
  • WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b,
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • the AMF 162 may provide a control plane function for switching between the RAN 1 13 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 1 15 via an N1 1 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b,
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • CN 1 15 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 1 15 and the PSTN 108.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • IMS IP multimedia subsystem
  • the CN 1 15 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 1 14a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • mmW millimeter wave
  • a base station and WTRU may need to overcome these high path losses and discover each other.
  • Beamforming techniques may include digital, analogue and hybrid beamforming.
  • V2X vehicle-to-everything
  • use case groups vehicle platooning, extended sensors, advanced driving and remote driving.
  • Each use case group may have different latency, reliability and data rate requirements such as the examples summarized in Table 1.
  • Use case within each use case group may have different latency, reliability and/or data rate requirements.
  • the lower degree of automation in a video sharing scenario which may be part of the extended sensors use case group, may have a 50 ms latency requirement, 90% reliability requirement and 10 Mbps data rate requirement.
  • a higher degree of automation in sensor information sharing between WTRUs supporting V2X application also part of the extended sensors use case group, may have a 3 ms latency requirements, a 99.999% reliability requirement, and a 25 Mbps data rate requirement.
  • a vehicle may be in transmission mode 3 (i.e., mode 3 user) or may be in transmission mode 4 (i.e., mode 4 user).
  • a mode 3 user may directly use the resources allocated by a base station for the sidelink (SL) communication among vehicles or between a vehicle and a pedestrian.
  • a mode 4 user may obtain a list of candidate resources allocated by a base station, and may select a resource among the candidate resources for its SL communication.
  • user, UE, WTRU, and vehicle WTRU may equivalently and interchangeably refer to a vehicle.
  • FIG. 2 is a signaling diagram of an example sidelink WTRU information exchange procedure 200 for communication between a (vehicle) WTRU 201 and the gNB and/or eNB 202 for V2X sidelink transmissions, for example according to 5G NR V2X and/or LTE V2X.
  • the WTRU 201 may receive system information block (SIB) type 21 (SIB21) 204, which may contain V2X sidelink communication configuration.
  • SIB system information block
  • SIB21 204 may include the SL-V2X-ConfigCommon information element (IE), which may include, but is not limited to include, components v2x-CommRxPool, M2X- CommTxPoolNormalCommon, v2-CommTxPoolExceptional, and/or v2x-lnterFreqlnfoList.
  • IE SL-V2X-ConfigCommon information element
  • v2x- InterFreqlnfoList may be a list of neighboring frequencies (e.g., up to seven neighboring frequencies) for V2X sidelink communications.
  • the WTRU 201 may send, to gNB/eNB 202, sidelink WTRU information 206 in one or more messages.
  • the vehicle WTRU 201 may send message(s) to the gNB/eNB 202 indicating to the gNB/eNB 202 that the WTRU 201 is (or is not) interested in receiving V2X sidelink communication and/or requesting assignment and/or release of transmission resources for V2X sidelink communication.
  • the WTRU 201 and gNB/eNB 202 may exchange one or more RRCConnectionReconfiguration messages 208, which may include the SL-V2X-ConfigDedicated IE.
  • the SL-V2X-ConfigDedicated IE may include, but is not limited to include, commTxResources and/or v2x-lnterFreqlnfoList.
  • GNSS satellites have atomic oscillators providing a stable and accurate time reference.
  • a GNSS receiver may track signals from multiple satellites and retrieve a local time reference with absolute error less than 1 ps for Global Positioning System (GPS) receivers.
  • GPS Global Positioning System
  • the residual error using GPS may be around 10 ns.
  • GNSS may be used for frequency synchronization by phase-locking the local oscillator to the incoming signal and stabilizing the carrier frequency.
  • GNSS solutions for synchronization may be used for V2X.
  • a WTRU may receive sidelink synchronization signals (SLSS) on a sidelink from other WTRUs.
  • the SLSS may include primary sidelink synchronization signals (PSSS), secondary sidelink synchronization signals (SSSS), and/or physical sidelink broadcast channel (PSBCH) signals, which may further include synchronization information.
  • PSSS primary sidelink synchronization signals
  • SSSS secondary sidelink synchronization signals
  • PSBCH physical sidelink broadcast channel
  • the WTRU may use the information carried in the SLSS to obtain timing information.
  • a threshold used for synchronization measurement e.g., Synch-Threshold
  • RRC signaling e.g. v2x-SyncConfig and/or SL-V2X-Preconfiguration lEs.
  • the SLSS may include, but are not limited to include, any one or more of the following example signals: PSSS, SSSS, PSBCH, and/or demodulation reference signal (DMRS) for demodulating the PSBCH.
  • PSSS and SSSS may be transmitted in adjacent time slots in the same subframe.
  • Sidelink-ID (SID) may be split into two sets.
  • SIDs in the range of ⁇ 0, 1, ...,167 ⁇ may be reserved for in-coverage WTRUs (i.e., WTRUs that can receive a signal strong enough to connect with a cell associated with the eNB) and SIDs in the range of ⁇ 168, 169, ...,335 ⁇ may be used for out-of-coverage WTRUs.
  • the subframes used as radio resources to transmit SLSS and PSBCH may be configured by higher layers
  • NR V2X requirements may be different from LTE V2X requirements. For example, for NR V2X services to be able support higher bandwidth, reliability and higher density of vehicles and users, existing LTE SLSS may not be sufficient. The capacity of the sidelink channels may need to be increased. For example, LTE V2X may not include beam-centric design and thus the LTE SLSS may be enhanced for NR V2X using directional beams. For certain use cases such as vehicle platooning, different handling for the synchronization timing reference and coverage may be used. Hence, modifications to NR synchronization may be implemented in order to apply NR synchronization for NR V2X.
  • a platoon may comprise a group of WTRUs, and one of the WTRUs in the group may be configured, assigned or selected as platoon leader, and the other WTRUs may be referred to as platoon followers.
  • the platoon leader may be responsible for managing the other WTRUs in the platoon.
  • the platoon leader may provide any of the following functions for one or more of the platoon followers: coordination between multiple WTRUs (platoon followers); unified synchronization timing reference; and/or scheduling of resources for other WTRUs.
  • the platoon leader may be a platoon manager.
  • FIG. 3 is a network diagram of an example vehicle platoon 300 including a platoon leader (PL) WTRU 302 (Hop 0), platoon follower WTRU 304 (Hop 1 because it is a neighbor to PL WTRU 302), platoon follower WTRU 306 (Hop 2 because it is two links away from PL WTRU 302), and a WTRU 301 that would like to join the vehicle platoon 300.
  • PL platoon leader
  • Hop 1 because it is a neighbor to PL WTRU 302
  • platoon follower WTRU 306 Hop 2 because it is two links away from PL WTRU 302
  • WTRU 301 that would like to join the vehicle platoon 300.
  • the WTRU 301 may use information (e.g., reference signal received power (RSRP), synchronization source type as leader or follower, hop #, threshold(s), and/or priority rules) based on the received SL synchronization signals PL SL-SYNC 310, H1 SL-SYNC 312 and H2 SL-SYNC 314 to select a synchronization source from among platoon member WTRUs 302, 304 and 306 in order to connect to the vehicle platoon 300.
  • RSRP reference signal received power
  • Methods of sidelink synchronization disclosed herein may be used in NR V2X for such use cases as vehicle platooning, and may also be used in other NR use cases. Any of the synchronization methods, access methods and/or signaling mechanisms described herein may be used by a WTRU to synchronize with a vehicle platoon in order to become a member of the vehicle platoon.
  • methods of sidelink synchronization may be based on measurement, measurement type and/or synchronization source type.
  • a WTRU may synchronize with one of the synchronization sources in a vehicle platoon. For example, a WTRU may attempt to synchronize with a platoon leader first. In an example, the WTRU may fail to synchronize with the platoon leader (e.g., because the WTRU does not receive SLSS from the platoon leader or the SLSS from the platoon leader are too weak for the WTRU to properly decode). The WTRU may synchronize with one of the platoon followers if the WTRU fails to synchronize with the platoon leader.
  • the WTRU may use signal measurement(s) to decide the source with which the WTRU may synchronize. For example, if a signal measurement from a synchronization source (e.g., a WTRU in the platoon) is above a threshold, the WTRU may synchronize with the synchronization source. Otherwise, the WTRU may choose to synchronize with another synchronization source. In an example, when multiple synchronization sources have signal measurements above a threshold, the WTRU may select the synchronization source with the highest measurement value.
  • a synchronization source e.g., a WTRU in the platoon
  • the configuration information for sidelink communications may be received from the eNB and/or from another WTRU (e.g., on a sidelink).
  • the configuration information for sidelink communications may be received in a SIB from the eNB.
  • the WTRU may search through synchronization sources by monitoring the sidelink channel(s) for signals from synchronization sources (e.g., members of the vehicle platoon).
  • the WTRU search through synchronization sources by monitoring sidelink channel(s) and receiving sidelink signals, such as any SLSS.
  • the WTRU may perform measurements on the same signals it received to search through the synchronization sources, or on different sidelink signals.
  • types of measurements that may be performed by a WTRU for sidelink synchronization may include, but are not limited to include, any one or more of the following measurements: RSRP (equivalently sidelink RSRP (S-RSRP)), reference signal received quality (RSRQ) (equivalently sidelink RSRQ (S-RSRQ)), received signal strength indication (RSSI) (equivalently sidelink RSSI (S-RSSI)), signal-to-noise ratio (SNR), correlation (equivalently SL correlation), and/or signal-to-interference-plus-noise ratio (SINR).
  • RSRP Equivalently sidelink RSRP
  • RSRQ reference signal received quality
  • RSSI received signal strength indication
  • S-RSSI signal-to-noise ratio
  • SNR signal-to-noise ratio
  • SINR signal-to-noise ratio
  • SINR signal-to-noise ratio
  • SINR signal-to-interference-plus-noise ratio
  • Synchronization source selection may be based on any one or more of the different types of measurements made on signals received from synchronization sources (e.g., platoon leader and/or one or more platoon followers).
  • the WTRU may perform the measurements on signals received from the synchronization sources, such as SLSS (e.g., including the same signals it received when searching through the synchronization sources and/or different signals).
  • a SLSS may include a sidelink synchronization signal block (SL-SSB), such that the WTRU may perform measurements (e.g., RSRP) and any one or more parts of the SL-SSB.
  • SL-SSB sidelink synchronization signal block
  • the SL-SSB may include any of the following parts: PSSS, SSSS and/or a PSBCH signal.
  • the WTRU may perform measurements on any one or more of the PSSS, SSSS and/or PSBCH signal.
  • the SLSS may include reference signals, such as channel state information reference signals (CSI- RS) and/or PSBCH demodulation reference signals (DMRS).
  • CSI- RS channel state information reference signals
  • DMRS PSBCH demodulation reference signals
  • the WTRU may perform measurements on any one or more of the CSI-RS and/or PSBCH DMRS received in SLSS from one or more synchronization sources.
  • the measurements using CSI-RS and/or PSBCH DMRS may be performed independently from measurements using SL-SSB or in conjunction or in combination with SL-SSB.
  • the synchronization source type may be one of platoon leader (and/or a platoon co-leader in the case that more than one WTRU may be platoon leader) or platoon follower.
  • the WTRU may determine the synchronization source type of a synchronization source based on information carried in (sidelink) signals received from the synchronization source. For example, the WTRU may determine the synchronization source type from information carried in any of the SLSS described above, and the synchronization source type may be implicitly or explicitly signaled.
  • the WTRU may determine the synchronization source type from information carried in any of the SLSS used for measurement (and/or for searching through the synchronization sources) and/or from other SLSS received from the synchronization sources.
  • the SLSS e.g., in the PSSS, SSSS, and/or PSBCH signal
  • may carry an explicit indication of source type e.g., a bit where‘T indicates platoon leader, and ⁇ ’ indicates a platoon follower).
  • the SLSS (e.g., in the PSSS, SSSS, and/or PSBCH signal) may carry a hop number associated with the synchronization source (e.g., hop number equal to 0 indicates a platoon leader, and hop number greater than 0 indicates a platoon follower and equals the minimum number of links to the platoon leader), such that the WTRU may determine the synchronization source type implicitly from the hop number information carried in the SL-SSB.
  • the hop number may be broadcasted using SL-SSB.
  • the hop number may be broadcasted in PSBCH.
  • the hop number may be included in information element in the PSBCH signal or carried in the payload of PSBCH signal.
  • the WTRU may determine the synchronization source type implicitly from the hop number broadcasted in PSBCH.
  • the hop number may be embedded in DMRS, which may be carried on the PSBCH.
  • the WTRU may determine the synchronization source type implicitly from the hop number information carried in the DMRS of PSBCH.
  • the hop number may be carried in the SPSS and/or SSSS and may be broadcasted in SPSS and/or SSSS in the SLSS.
  • the WTRU may determine the synchronization source type implicitly from the hop number information carried in the SPSS and/or SSSS.
  • the hop number may be broadcasted using any combination of PSBCH, DMRS, SPSS and/or SSSS (or other synchronization signals).
  • S-RSRP-based synchronization source selection alone does not take into account synchronization source type. For example, if a WTRU is closer to a platoon follower than a platoon leader, then S-RSRP from the platoon follower may be higher than S-RSRP from the platoon leader. If S-RSRP is the only criteria for synchronization source selection, then the WTRU may in some cases select a platoon follower over the platoon leader.
  • the synchronization source type may also be considered as part of selection criteria for a synchronization source. For example, a platoon leader may have higher priority than platoon followers.
  • synchronization source selection may depend on synchronization source type and measurements or measurement types (e.g., S-RSRP) and may be based on priorities between synchronization source type and measurements or measurement types.
  • the synchronization source selection may be based on any of the following criteria: measurements or measurement types (e.g., S-RSRP) measured from platoon leader or followers; synchronization source type (e.g., platoon leader type, platoon follower type); and/or priority and priority rules.
  • FIG. 4 is a flow diagram of an example synchronization source selection method 400 based on measurement, measurement type and synchronization source type.
  • the example synchronization source selection method 400 may be performed by a (vehicle) WTRU that wants to join a vehicle platoon.
  • the synchronization source type is prioritized over the measurement (e.g., RSRP) value.
  • the WTRU may receive configuration information for sidelink communications, which may include at least a sidelink measurement threshold.
  • the configuration information may be received in a SIB from the eNB.
  • the WTRU may search through synchronization sources (e.g., by monitoring the sidelink for signals from synchronization sources and/or successfully receiving sidelink signals, such as SLSS, from synchronization sources).
  • the WTRU may perform measurements (e.g., sidelink RSRP, sidelink correlation) on signals (e.g., SLSS) received from the synchronization sources.
  • the WTRU may compile a list of synchronization sources (from among the“candidate” synchronization sources on which the WTRU took measurements) with measurement value(s) (e.g., measured RSRP) greater than the sidelink measurement threshold.
  • the WTRU may check the synchronization source type (e.g., platoon leader or platoon follower). As described above, the synchronization source type may be determined based on implicit information (e.g., hop number) and/or explicit information (source type indication) carried in the SLSS received by the WTRU.
  • the WTRU may select the platoon leader as the synchronization source and, at 414, establish a (side) link with the platoon leader so that the WTRU may obtain timing information from the platoon leader. Otherwise, if there is no synchronization source in the list that is a platoon leader type (i.e., all synchronization sources in the list are platoon followers), then, at 416, the WTRU may select the synchronization source in the list having the highest measurement value (e.g., the highest RSRP). In this case, at 418, the WTRU may establish a communication (side) link with the selected platoon follower so that the WTRU may obtain timing information from the platoon follower.
  • the highest measurement value e.g., the highest RSRP
  • FIG. 5 is a flow diagram of an example synchronization source selection method
  • the example synchronization source selection method 500 may be performed by a (vehicle) WTRU that wants to join a vehicle platoon.
  • the synchronization source type is prioritized over the measurement (e.g., RSRP) value.
  • the measurement value e.g., RSRP
  • the priority of synchronization source type may be downgraded and the synchronization source with the highest measurement value (e.g., highest RSRP) may be selected.
  • the WTRU may receive configuration information for sidelink communications including one or more sidelink measurement threshold(s).
  • the sidelink measurement threshold(s) may include a first sidelink measurement threshold and a second sidelink measurement threshold.
  • the WTRU may search through synchronization sources.
  • the WTRU may perform measurements (e.g., RSRP, correlation) on signals (e.g., SLSS) received from the synchronization sources.
  • the WTRU may compile a first list of synchronization sources (from among the synchronization sources on which the WTRU took measurements) with measurement values (e.g., measured RSRP) greater than a first sidelink measurement threshold and a second list of synchronization sources with measurement values (e.g., measured RSRP) greater than a second sidelink measurement threshold, where the second threshold is greater than the first threshold.
  • measurement values e.g., measured RSRP
  • second sidelink measurement threshold e.g., measured RSRP
  • the WTRU may check the synchronization source type (e.g., platoon leader or platoon follower). If a synchronization source type is platoon leader, then, at 512, the WTRU may further check if the measurement value (e.g., measured RSRP) from platoon leader is above or below the second sidelink measurement threshold (i.e., whether or not the platoon leader is in the second list).
  • the measurement value e.g., measured RSRP
  • platoon leader’s measurement value is above the second sidelink measurement threshold, then, at 514, the WTRU may select platoon leader as the synchronization source and, at 516, establish a communication (side) link with the platoon leader (so that the WTRU may obtain timing information from the platoon leader). If the platoon leader’s measurement value is below the second sidelink measurement threshold, then, at 518, the WTRU may further check if the platoon followers’ measurement values are above or below the second sidelink measurement threshold (i.e., if there are platoon followers on the second list).
  • the WTRU may select the platoon leader as the synchronization source and, at 516, establish a communication (side) link with the platoon leader. If a platoon follower’s measurement value is above the second sidelink measurement threshold (i.e., the platoon follower is on the second list), then, at 520, the WTRU may select the platoon follower with the highest measurement value (e.g., highest RSRP) as the synchronization source and, at 522, establish a communication (side) link with the selected platoon follower (so that the WTRU may obtain timing information from the platoon follower).
  • the highest measurement value e.g., highest RSRP
  • the first and second sidelink measurement thresholds used for the platoon leader may be the same or different from the first and second sidelink measurement thresholds used for the platoon followers.
  • the thresholds may be configured, predetermined or indicated either semi-statically or dynamically.
  • the thresholds may be included in the configuration information, 502.
  • Another example synchronization source selection method may be based on measurement type, synchronization source type and/or number of hops.
  • the measurement value e.g., S-RSRP
  • measurement values e.g., S-RSRP
  • the WTRU may determine which platoon follower to select as the synchronization source.
  • the WTRU may select the platoon follower with the highest measurement value or S-RSRP (e.g., the platoon followers may all be the same synchronization source type).
  • S-RSRP a platoon follower that is closer to the platoon leader (i.e., has a lower hop number), even with a lower measurement value (S-RSRP), may be selected as the synchronization source over another platoon follower with higher measurement value but further away from the platoon leader (i.e., has a greater hop number).
  • the synchronization source selection may depend on the number of hops from the synchronization source (e.g., where the selected synchronization source is a platoon follower) to the platoon leader. If one platoon follower has less hops (e.g., one hop) to platoon leader while the other platoon followers have more hops (e.g., two hops or more) to the leader, then the WTRU may select the platoon follower with fewer hops even if the measurement value is lower (but above the acceptable threshold). Therefore, synchronization source selection may depend on number of hops from the synchronization source (or platoon follower) to the platoon leader in addition to measurement or measurement type and/or synchronization source type.
  • an example method for synchronization source selection may be based on the following: measurement or measurement type measured from the platoon leader or platoon followers; synchronization source type; and/or number of hops between the synchronization source (or platoon follower) and platoon leader.
  • FIG. 6 is a flow diagram of an example synchronization source selection method
  • the example synchronization source selection method 600 may be performed by a (vehicle) WTRU that wants to join a vehicle platoon.
  • the synchronization source type may have higher priority than measurement or measurement type (e.g., RSRP or S-RSRP).
  • the number of hops may have higher priority than measurement or measurement type. Other priority may be used.
  • the WTRU may receive configuration information for sidelink communications including one or more sidelink measurement threshold(s).
  • the sidelink measurement threshold(s) may include a sidelink measurement threshold T1 , a first hop number threshold H1 and/or a second hop threshold H2.
  • any of the thresholds may be preconfigured at the WTRU or received via other signaling.
  • the WTRU may search through synchronization sources.
  • the WTRU may perform measurement (e.g., RSRP, correlation) on signals (e.g., SLSS) received from the synchronization sources.
  • the WTRU may compile a list of synchronization sources with measurement and/or measurement type (e.g., measured RSRP or S-RSRP) greater than measurement threshold T1 and/or number of hops less than the first hop threshold, H1 (e.g., this may be a combined list or a first list based on measurement and a second list based on number of hops).
  • the number of hops may count the hops between the synchronization source and the platoon leader, with the platoon leader as a reference point. For example, if the synchronization source is the platoon leader, then the number of hops may be zero. If the synchronization source is platoon follower, then number of hops may be one or greater than one corresponding to the minimum number of links between the synchronization source and the platoon leader.
  • the WTRU may check the synchronization source type for the synchronization sources in the list. If the type of a synchronization source is platoon leader, then, at 612, the WTRU may select the platoon leader as the synchronization source and, at 614, establish a communication (side) link with the platoon leader (so that the WTRU may obtain timing information from the platoon leader).
  • the WTRU may further compare the measurement value and/or measurement type (e.g., RSRP or S- RSRP) and number of hops among synchronization sources.
  • the WTRU may determine for each synchronization source in the list if the number of hops (i.e., number of links to the platoon leader) is less than the second hop threshold H2.
  • the WTRU may select that synchronization source (e.g., the platoon follower) among synchronization sources with number of hops less than a second hop threshold H2 with the highest measurement value (RSRP or S-RSRP) and, at 626, establish a link with the selected synchronization source.
  • synchronization source e.g., the platoon follower
  • the WTRU may select any synchronization source (e.g., any platoon follower) with highest measurement values (e.g., highest RSRP) among synchronization sources with a number of hops that is less than a first hop threshold H1 (but not less than the second hop threshold H2) and, at 622, establish a link with the selected synchronization source with the highest measurement among synchronization sources with number of hops less than a first hop threshold H1 (but not less than the second hop threshold H2).
  • any synchronization source e.g., any platoon follower
  • highest measurement values e.g., highest RSRP
  • methods for sidelink synchronization source selection may be based on synchronization source type, number of hops, measurement type and/or link capacity. For example, if a platoon follower has fewer hops (to the platoon leader) but the link(s) between the platoon follower and the platoon leader is weak, then the platoon follower may not be selected even if the measurement value (e.g., S-RSRP) measured from signals from the platoon follower are high. In this case, a synchronization source may be selected with a lower measurement value (e.g., S- RSRP) but with links between the platoon follower and platoon leader that have higher measurement (e.g., S-RSRP).
  • the measurement value e.g., S-RSRP
  • the synchronization source selection method may depend on measurement and/or measurement type of links between the platoon follower and platoon leader in addition to the measurement and/or measurement type of the link measured from the platoon follower.
  • the synchronization source selection method may depend on number of hops from the synchronization source (e.g., platoon follower) to the platoon leader and the associated measurements and/or measurement types (e.g., S-RSRPs) that are associated with the hops/links in between the synchronization source and the platoon leader in addition to the measurements for the link between the WTRU and the synchronization source (platoon follower) and/or the synchronization source type.
  • the synchronization source e.g., platoon follower
  • the associated measurements and/or measurement types e.g., S-RSRPs
  • An example synchronization source selection method may be based on any one or more of the following criteria: measurement and/or measurement type (e.g., S-RSRP) measured from platoon leader or followers; synchronization source type (e.g., platoon leader, platoon follower); number of hops between the synchronization source (or platoon follower) and platoon leader; and/or measurement and/or measurement type (e.g., S-RSRPs) associated with the hops between the synchronization source (e.g., platoon follower) and platoon leader.
  • measurement and/or measurement type e.g., S-RSRP
  • measurement and/or measurement type e.g., S-RSRP
  • FIG. 7 is a flow diagram of an example synchronization source selection method 700 based on measurement, measurement type and synchronization source type, number of hops and link capacity.
  • the example synchronization source selection method 700 may be performed by a (vehicle) WTRU that wants to join a vehicle platoon.
  • synchronization source type may have higher priority than measurement or measurement type (e.g., S-RSRP).
  • the number of hops may have higher priority than measurement or measurement type.
  • the link capacity may also have higher priority than measurement or measurement type Other priority may be used.
  • the WTRU may receive configuration information for sidelink communications, which may include one or more sidelink measurement threshold(s), hop number threshold(s) and/or link capacity threshold(s).
  • the sidelink measurement threshold(s) may include a sidelink measurement threshold T1 , a first hop number threshold H1 , a second hop threshold H2, and/or a link capacity threshold C.
  • the WTRU may search through synchronization sources.
  • the WTRU may perform measurement (e.g., RSRP, correlation) on signals (e.g., on PSSS, SSSS, and or PSBSCFI signal, which may be received as part of SLSS) received from the synchronization sources.
  • measurement e.g., RSRP, correlation
  • the WTRU may compile a list of synchronization sources with measurements (e.g., measured RSRP or S-RSRP) greater than sidelink measurement threshold T 1 and/or number of hops less than the first hop threshold H1 and/or link capacity greater than capacity threshold C (e.g., this may be a combined list or separate lists such as a first list based on measurement, a second list based on number of hops and a third list based on link capacity).
  • the link capacity may be associated the hops or links between the synchronization source and the platoon leader.
  • the number of hops may be the hops between the synchronization source and the platoon leader, where the platoon leader has a number of hops equal to zero and a platoon follower has a number of hops greater than zero.
  • the link capacity for a platoon follower with a path including one or more links to the platoon leader may be calculated as any of the following example capacity calculations: the individual link capacity (e.g., the capacity of the link in the path with the lowest capacity that forms the bottleneck); the averaged link capacity over all links in the path; or the total capacity summing the capacity for all links associated with the path of hops between the synchronization source and the platoon leader.
  • the WTRU may check the synchronization source type for the synchronization sources in the list. If the type of synchronization source is platoon leader, then, at 712, the WTRU may select the platoon leader as the synchronization source and, at 714, establish a communication (side) link with the platoon leader (so that the WTRU may obtain timing information from the platoon leader).
  • the WTRU may further compare the measurement value and/or measurement type (e.g., RSRP or S- RSRP) and number of hops among synchronization sources.
  • the WTRU may determine for each synchronization source in the list if the number of hops (i.e., number of links to the platoon leader) is less than the second hop threshold H2.
  • the WTRU may select that synchronization source (e.g., the platoon follower) among synchronization sources with number of hops less than a second hop threshold H2 with the highest measurement value (RSRP or S-RSRP) and, at 726, establish a link with the selected synchronization source.
  • synchronization source e.g., the platoon follower
  • the WTRU may select any synchronization source (e.g., any platoon follower) with highest link capacity among synchronization sources with a number of hops that is less than a first hop threshold H1 (but not less than the second hop threshold H2) and, at 722, establish a link with the selected synchronization source with the highest link capacity among synchronization sources with number of hops less than a first hop threshold H1 (but not less than the second hop threshold H2).
  • any synchronization source e.g., any platoon follower
  • synchronization source selection methods may be based on synchronization source type, number of hops, measurement type, link capacity and/or traffic load associated with links to platoon leader.
  • a method for synchronization source selection may be based on the following: measurement or measurement type (e.g., S-RSRP) measured from a platoon leader and/or platoon followers; synchronization source type (e.g., platoon leader type, platoon follower type); number of hops between the synchronization source and platoon leader; measurement and/or measurement type associated with links between the synchronization source and platoon leader; average measurement (e.g., average RSRP) associated with links between the synchronization source and platoon leader; link capacity associated with links between the synchronization source and platoon leader; and/or traffic load associated with links between the synchronization source and platoon leader.
  • measurement or measurement type e.g., S-RSRP
  • synchronization source type e.g., platoon leader type, plato
  • FIG. 8 is a flow diagram of an example synchronization source selection method 800 based on measurement, measurement type, synchronization source type, number of hops, link capacity, and traffic load.
  • the example synchronization source selection method 800 may be performed by a (vehicle) WTRU that wants to join a vehicle platoon.
  • synchronization source type may have higher priority than measurement or measurement type (e.g., S-RSRP).
  • the number of hops may have higher priority than measurement or measurement type.
  • the link capacity and/or traffic load may have higher priority than measurement or measurement type. Other priority may be used.
  • the WTRU may receive configuration information for sidelink communications, which may include one or more sidelink measurement threshold(s), hop number threshold(s) and/or link capacity threshold(s).
  • the sidelink measurement threshold(s) may include a sidelink measurement threshold T1 , a first hop number threshold H1 , a second hop threshold H2, and/or a link capacity threshold C.
  • the WTRU may search through synchronization sources.
  • the WTRU may perform measurement (e.g., RSRP, correlation) on signals (e.g., on PSSS, SSSS, and or PSBSCFI signal, which may be received as part of SLSS) received from the synchronization sources.
  • measurement e.g., RSRP, correlation
  • the WTRU may compile a list of synchronization sources with measurements (e.g., measured RSRP or S-RSRP) greater than sidelink measurement threshold T 1 and/or number of hops less than the first hop threshold H1 and/or link capacity greater than capacity threshold C (e.g., this may be a combined list or separate lists such as a first list based on measurement, a second list based on number of hops and a third list based on link capacity).
  • the link capacity may be associated the hops or links between the synchronization source and the platoon leader.
  • the number of hops may be the hops between the synchronization source and the platoon leader, where the platoon leader has a number of hops equal to zero and a platoon follower has a number of hops greater than zero.
  • the link capacity for a platoon follower with a path including one or more links to the platoon leader may be calculated as any of the following example capacity calculations: the individual link capacity (e.g., the capacity of the link in the path with the lowest capacity that forms the bottleneck); the averaged link capacity over all links in the path; or the total capacity summing the capacity for all links associated with the path of hops between the synchronization source and the platoon leader.
  • the traffic load may be calculated over the links between the synchronization source and the platoon leader.
  • the WTRU may check the synchronization source type for the synchronization sources in the list. If the type of synchronization source is platoon leader, then, at 712, the WTRU may select the platoon leader as the synchronization source and, at 714, establish a communication (side) link with the platoon leader (so that the WTRU may obtain timing information from the platoon leader).
  • the WTRU may further compare signal measurement value (e.g., RSRP), and number of hops (and/or link capacity and/or traffic load) associated with hops/links among synchronization sources.
  • the WTRU may determine for each synchronization source in the list if the number of hops (i.e., number of links to the platoon leader) is less than the second hop threshold H2.
  • the WTRU may select the synchronization source (e.g., the platoon follower) among synchronization sources with a number of hops less than a second hop threshold H2 and the lowest traffic load and, at 826, establish a link with the selected synchronization source.
  • the synchronization source e.g., the platoon follower
  • the WTRU may select any synchronization source (e.g., any platoon follower) with highest link capacity among synchronization sources with a number of hops that is less than a first hop threshold H1 (but not less than the second hop threshold H2) and, at 822, establish a link with the selected synchronization source with the highest link capacity among synchronization sources with number of hops less than a first hop threshold H1 (but not less than the second hop threshold H2).
  • any synchronization source e.g., any platoon follower
  • FIG. 9 is a flow diagram of an example synchronization source selection method 900 based on measurement, measurement type and synchronization source type, and number of hops.
  • the example synchronization source selection method 900 may be performed by a (vehicle) WTRU that wants to join a vehicle platoon.
  • the WTRU may receive configuration information for sidelink communications, which may include sidelink measurement threshold(s), hop number thresholds, and/or link capacity thresholds.
  • the sidelink configuration information may include a first sidelink measurement threshold T1 , a second sidelink measurement threshold T2, and a hop count (hop number) threshold H.
  • the second sidelink measurement threshold T2 is greater than the first sidelink measurement threshold T 1.
  • the WTRU may search through synchronization sources.
  • the WTRU may perform measurements (e.g., RSRP, correlation) on signals (e.g., SLSS) received from the synchronization sources.
  • the WTRU may determine the synchronization source type for each of the synchronization sources, and at 909 the WTRU may determine the hop number for each of the synchronization sources.
  • the WTRU may determine the synchronization source type and/or hop number of each synchronization source based on information carried in SLSS received from the respective synchronization source, for example based on information carried in the SPSS, SSSS and/or PSBCH signal.
  • the SPSS, SSSS and/or PSBCH signal may carry a synchronization source type indicator that explicitly indicates to the WTRU the synchronization source type (e.g., platoon leader type or platoon follower type).
  • the SPSS, SSSS and/or PSBCH signal may carry a hop number field than indicates to the WTRU the number of hops or links between the synchronization source and the platoon leader.
  • the SLSS may not include synchronization source type indicator and the WTRU may determine the synchronization source type for each synchronization source based on the hop number field received in the SLSS (e.g., hop number equal to 0 indicates a platoon leader, and hop number greater than 0 indicates a platoon follower).
  • the WTRU may compile a list of synchronization sources (from among the synchronization sources on which the WTRU took measurements) with measurement value (e.g., measured RSRP) greater than a first sidelink measurement threshold T1.
  • the WTRU may consider the synchronization source type for the synchronization sources in the list. If the type of a synchronization source is platoon leader, then, at 914, the WTRU may select the platoon leader as the synchronization source and, at 916, establish a communication (side) link with the platoon leader (so that the WTRU may obtain timing information from the platoon leader).
  • the WTRU may further compare the hop numbers for the synchronization sources.
  • the WTRU may determine for each synchronization source in the list if the number of hops (i.e., number of links to the platoon leader) is less than the hop threshold H.
  • the WTRU may select the synchronization source (e.g., the platoon follower) among synchronization sources with a number of hops less than the hop threshold H and, at 916, establish a link with the selected synchronization source (in this case, a platoon follower).
  • the synchronization source e.g., the platoon follower
  • the WTRU may select a synchronization source (platoon follower) with a measurement value (e.g., measured RSRP) greater than the second measurement threshold T2 and, at 916, establish a link with the selected synchronization source (in this case, a platoon follower).
  • a synchronization source platoon follower
  • a measurement value e.g., measured RSRP
  • methods for sidelink synchronization and source selection may be based on any one or more of source type, number of hops, numerology (e.g., subcarrier spacing (SCS), cyclic prefix (CP)), bandwidth part (BWP), link capacity and/or traffic load (associated with hops between the synchronization source and the platoon leader).
  • a WTRU may receive sidelink configuration information, which may include one or the threshold(s) corresponding to measurement, number of hops, link capacity, and/or traffic load.
  • Methods for sidelink synchronization and source selection may be based on any of the following criteria: measurement and/or measurement type (e.g., S-RSRP or RSRP) measured from platoon leader or follower; synchronization source type (e.g., platoon leader type, platoon follower type); number of hops between the synchronization source or platoon follower and platoon leader; measurement and/or measurement type (e.g., S-RSRP) associated with hops or path of hops between the synchronization source or platoon follower and platoon leader; average measurement (e.g., averaged S-RSRP) associated with hops between the synchronization source or platoon follower and platoon leader; link capacity associated with hops and/or the path of hops between the synchronization source or platoon follower and platoon leader; traffic load associated with hops and/or path of hops between the synchronization source or platoon follower and platoon leader; bandwidth associated with hops and/or the path of
  • Synchronization assistance information may include any one or more of the following information: the measurement and/or measurement type; synchronization source type; number of hops or hop order: average or total measurement (e.g., S-RSRP) associated with hops or path of hops; link capacity associated with hops or path of hops; and/or traffic load associated with hops or path of hops.
  • S-RSRP average or total measurement
  • any of the following information may be gathered by or signaled to the WTRU: measurement and/or measurement type (e.g., S-RSRP or RSRP) measured from platoon leader or platoon followers; synchronization source type (e.g., platoon leader type, platoon follower type); number of hops between the synchronization source and platoon leader; measurement and/or measurement type (e.g., S-RSRPs) associated with hops and/or path of hops between the synchronization source and platoon leader; average and/or total measurement and/or measurement type (e.g., S-RSRP) associated with hops and/or path of hops between the synchronization source (e.g., platoon follower) and platoon leader; capacity associated with hops and/or path of hops between the synchronization source and platoon leader; and/or load associated with hops and/or path of hops between the synchronization source and platoon leader.
  • measurement and/or measurement type e.g
  • the following information may be broadcasted or communicated to WTRUs for V2X sidelink synchronization source selection: measurement and/or measurement type (e.g., S-RSRP); number of hops or hop order from synchronization source to platoon leader; capacity associated with the path of hops; traffic load associated with the path of hops; numerology associated with the path of hops; BWP information associated with the path of hops; and/or priority including synchronization source priority.
  • measurement and/or measurement type e.g., S-RSRP
  • number of hops or hop order from synchronization source to platoon leader e.g., S-RSRP
  • capacity associated with the path of hops
  • traffic load associated with the path of hops
  • numerology associated with the path of hops e.g., OFD
  • BWP information e.g., BWP information associated with the path of hops
  • priority including synchronization source priority e.g., the hop number, synchronization source type and/or synchron
  • a platoon leader (or any WTRU including a platoon follower) may communicate synchronization assistance information to a WTRU.
  • a platoon leader may broadcast, groupcast or unicast the synchronization assistance information to one, multiple or all WTRUs.
  • a WTRU may report the information related to synchronization assistance information to the platoon leader.
  • the platoon leader may aggregate all the information reported from the WTRUs and convert the received information into a set of synchronization assistance information and communicate the updated synchronization assistance information back to the WTRUs.
  • Example methods may be used for communicating the synchronization assistance information to the WTRUs.
  • an NR physical sidelink control channel (NR-PSCCFI) may be used to communicate synchronization assistance information to WTRUs.
  • SLSS or PSBCH may be used to send the synchronization assistance information to WTRUs.
  • a sidelink group common control channel which may be a physical downlink control channel (PDCCFI) (e.g., SL-GC-PDCCFI) may be used to send synchronization assistance information to WTRUs.
  • PDCCFI physical downlink control channel
  • a group common control physical sidelink control channel (GC-SL-PSCCFI or GC-PSCCFI) or a group common control physical sidelink shared channel (GC-SL-PSSCFI or GC-PSSCFI) may be used, and may be groupcast, unicast or broadcast, or transmitted on-demand.
  • sidelink system information may be used. Sidelink system information may include sidelink remaining minimum system information (SL-RMSI) and/or sidelink other system information (SL-OSI), which may be broadcast, groupcast, unicast or transmitted on- demand.
  • sidelink random access channel (SL-RACH) may be used. SL-RACH may include two-step or four-step RACH approach.
  • sidelink message 1 (SL-MSG1 ) and/or message 2 (SL-MSG2) may be used in a two-step RACH approach.
  • sidelink message 3 (SL-MSG3) and/or message 4 (SL-MSG4) may be used in a four-step RACH approach.
  • SL-RACH may be used to request the synchronization assistance information for broadcast, groupcast, unicast or on-demand for synchronization assistance information.
  • SL-RACH may be used to send the synchronization assistance information via broadcast, groupcast, unicast or on- demand.
  • synchronization information may be partitioned into two (or more) sets, for example the first synchronization assistance information and the second synchronization assistance information.
  • the second synchronization assistance information may have higher priority than the first synchronization assistance information.
  • Additional priority rules may be applied to each set of synchronization assistance information. For example, one set of priority rules may be used within the first synchronization assistance information. Another set of priority rules may be used for the second synchronization assistance information.
  • the first synchronization assistance information may be delivered in a semi-static or dynamic manner and the second synchronization assistance information may be delivered in a dynamic manner (or semi-static manner).
  • the second synchronization assistance information may override the first synchronization assistance information.
  • An override indicator may be carried in the synchronization assistance information.
  • an override indicator may be carried in the second synchronization assistance information.
  • the WTRU may check the override indicator. If the override indicator indicates override or“on”, the WTRU may replace the first synchronization assistance information with the second synchronization assistance information.
  • the WTRU may use the second synchronization assistance information for synchronization source selection.
  • the WTRU may append the second synchronization assistance information to the first synchronization assistance information. In this case, the WTRU may use both the first and the second synchronization assistance information for assisting synchronization source selection.
  • the first synchronization assistance information and the second synchronization assistance information may be delivered in different periodicities, resources and/or via different signals or channels.
  • the first synchronization assistance information may be delivered in less frequently (e.g., with a greater periodicity) while the second synchronization assistance information may be delivered more frequently (e.g., with a smaller periodicity).
  • the first synchronization assistance information may be delivered using NR-PSCCH while the second synchronization assistance information may be delivered using SL-GC-PDCCH.
  • the first synchronization assistance information may be delivered using PSSS, SSSS and/or PSBCH while the second synchronization assistance information may be delivered using PSCCH or SL-GC- PDCCH.
  • the first synchronization assistance information may be delivered in a periodic manner while the second synchronization assistance information may be delivered in an aperiodic manner or event triggered manner. Different combinations above may be to optimize the V2X sidelink synchronization.
  • FIG. 10 is a flow diagram of an example synchronization assistance information method 1000 for NR V2X sidelink, which may be performed by a WTRU that is a member of a vehicle platoon.
  • WTRU may receive sidelink synchronization configuration.
  • the WTRU may receive the first sidelink synchronization assistance information.
  • the WTRU may receive priority rules for the first sidelink synchronization parameters.
  • the WTRU may receive the second sidelink synchronization assistance information.
  • the WTRU may receive priority rules for the second sidelink synchronization parameters.
  • the WTRU may select the synchronization source based on the synchronization assistance information and priority rules associated with the first and second synchronization assistance information. Synchronization methods and synchronization source selection methods for V2X sidelink may be based any combination, subset of subcomponent of the methods and techniques described herein.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, WTRU, terminal, base station, RNC, or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés de synchronisation de liaison latérale susceptibles d'être utilisés par une unité d'émission/réception sans fil (WTRU) qui souhaite rejoindre un groupe de WTRU, comme un peloton de véhicules. La WTRU peut recevoir des informations de configuration pour des communications en liaison latérale, comprenant des seuils de mesure. La WTRU peut surveiller un canal de liaison latérale pour déceler des signaux provenant de sources de synchronisation. La WTRU peut effectuer des mesures de liaison latérale et déterminer un type de source de synchronisation et un nombre de sauts se rapportant aux sources de synchronisation. La WTRU peut compiler une liste de sources de synchronisation dont la mesure de liaison latérale est supérieure à un premier seuil et sélectionner un type de chef de peloton. S'il n'existe aucun chef de peloton dans la liste, la WTRU peut sélectionner la source de synchronisation dont le nombre de sauts est inférieur à un seuil de sauts. Si ce n'est pas le cas, la WTRU peut sélectionner la source de synchronisation pour laquelle la valeur de la mesure de liaison latérale est supérieure à un second seuil de mesure de liaison latérale. La WTRU peut établir une liaison avec la source de synchronisation sélectionnée.
PCT/US2019/053238 2018-09-26 2019-09-26 Procédés de synchronisation de liaison latérale pour v2x en nr WO2020069182A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862736795P 2018-09-26 2018-09-26
US62/736,795 2018-09-26

Publications (1)

Publication Number Publication Date
WO2020069182A1 true WO2020069182A1 (fr) 2020-04-02

Family

ID=68172287

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/053238 WO2020069182A1 (fr) 2018-09-26 2019-09-26 Procédés de synchronisation de liaison latérale pour v2x en nr

Country Status (2)

Country Link
TW (1) TW202037210A (fr)
WO (1) WO2020069182A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220053439A1 (en) * 2018-10-11 2022-02-17 Lenovo (Beijing) Limited Method and apparatus for synchronization reference source selection
EP3975603A1 (fr) * 2020-09-25 2022-03-30 INTEL Corporation Procédés pour atténuer des attaques par déni de service sur une synchronisation temporelle à l'aide de redondance de liaison pour systèmes industriels/autonomes
WO2022155262A1 (fr) * 2021-01-12 2022-07-21 Idac Holdings, Inc. Procédés et appareils de positionnement de liaison latérale
WO2022220929A1 (fr) * 2021-04-15 2022-10-20 Qualcomm Incorporated Détection de canal pour communications de liaison latérale en duplex intégral

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170331620A1 (en) * 2016-05-12 2017-11-16 Industrial Technology Research Institute Method for receiving and transmitting synchronization signal and wireless communication device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170331620A1 (en) * 2016-05-12 2017-11-16 Industrial Technology Research Institute Method for receiving and transmitting synchronization signal and wireless communication device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 36.331, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.2.2, 10 July 2018 (2018-07-10), pages 1 - 791, XP051474963 *
INTERDIGITAL INC: "On V2X Synchronization in NR", vol. RAN WG1, no. Gothenburg, Sweden; 20180820 - 20180824, 11 August 2018 (2018-08-11), XP051516464, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F94/Docs/R1%2D1809095%2Ezip> [retrieved on 20180811] *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220053439A1 (en) * 2018-10-11 2022-02-17 Lenovo (Beijing) Limited Method and apparatus for synchronization reference source selection
US11910341B2 (en) * 2018-10-11 2024-02-20 Lenovo (Beijing) Limited Method and apparatus for synchronization reference source selection
EP3975603A1 (fr) * 2020-09-25 2022-03-30 INTEL Corporation Procédés pour atténuer des attaques par déni de service sur une synchronisation temporelle à l'aide de redondance de liaison pour systèmes industriels/autonomes
US11570732B2 (en) 2020-09-25 2023-01-31 Intel Corporation Methods to mitigate denial of service attacks on time synchronization using link redundancy for industrial/autonomous systems
WO2022155262A1 (fr) * 2021-01-12 2022-07-21 Idac Holdings, Inc. Procédés et appareils de positionnement de liaison latérale
WO2022220929A1 (fr) * 2021-04-15 2022-10-20 Qualcomm Incorporated Détection de canal pour communications de liaison latérale en duplex intégral
US11617205B2 (en) 2021-04-15 2023-03-28 Qualcomm Incorporated Channel sensing for full-duplex sidelink communications

Also Published As

Publication number Publication date
TW202037210A (zh) 2020-10-01

Similar Documents

Publication Publication Date Title
US20200053835A1 (en) Uu interface enhancement for nr v2x
EP3643116B1 (fr) Relocalisation de plan d&#39;utilisateur
US11083010B2 (en) Integrated access and backhaul associated with NR
US20210176735A1 (en) Control information transmission and sensing in wireless systems
US11412446B2 (en) Network energy efficiency
WO2020033622A1 (fr) Transmission fiable de données de liaison latérale
WO2022155262A1 (fr) Procédés et appareils de positionnement de liaison latérale
WO2020033562A1 (fr) Procédés et appareils de synchronisation dans un système sans fil
WO2020069182A1 (fr) Procédés de synchronisation de liaison latérale pour v2x en nr
WO2018204351A1 (fr) Multiplexage et mappage de signaux de synchronisation en nr
EP4316167A1 (fr) Procédés de positionnement de nouvelle radio (nr) pour la fourniture de ressources dans un positionnement de liaison latérale
WO2019195445A1 (fr) Procédés destinés à la gestion d&#39;une partie de largeur de bande dans des systèmes sans fil
WO2023055934A1 (fr) Approches de partie bwp robustes pour atténuer l&#39;impact d&#39;un brouilleur à bande étroite haute puissance
US20230308840A1 (en) Multicast-broadcast services support for network relay
WO2024039843A1 (fr) Politique de sélection de réseau local sans fil (wlan)
WO2024030625A1 (fr) Sélection de porteuse basée sur une mesure dans une liaison latérale à porteuses multiples
WO2023147049A1 (fr) Connectivité d&#39;un réseau personnel d&#39;internet des objets
WO2023192303A1 (fr) Système et procédés pour prendre en charge un flux et un profil de qos auto-adaptatifs
WO2023147059A1 (fr) Mobilité améliorée en mode inactif et connecté entre snpn
WO2024031093A1 (fr) Coordination de l&#39;utilisation de porteuses dans une liaison latérale multiporteuse
WO2024025922A1 (fr) Contrôle d&#39;accès à un réseau d&#39;hébergement et gestion de congestion
WO2024026082A1 (fr) Procédé et appareil d&#39;activation de communication n3gpp entre une wtru distante et une wtru relais
WO2024107823A1 (fr) Sélection de cellule/plmn
WO2023192146A1 (fr) Sélection d&#39;une route dans un système de communication sans fil
WO2023212308A1 (fr) Procédés, appareil et systèmes pour mesure d&#39;étalement de retards, comptes-rendus et détermination de préfixe cyclique

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19784194

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19784194

Country of ref document: EP

Kind code of ref document: A1