WO2016144574A1 - Procédés, appareils et systèmes d'adaptation de liaison pour des communications de monodiffusion de dispositif à dispositif (d2d) - Google Patents

Procédés, appareils et systèmes d'adaptation de liaison pour des communications de monodiffusion de dispositif à dispositif (d2d) Download PDF

Info

Publication number
WO2016144574A1
WO2016144574A1 PCT/US2016/019886 US2016019886W WO2016144574A1 WO 2016144574 A1 WO2016144574 A1 WO 2016144574A1 US 2016019886 W US2016019886 W US 2016019886W WO 2016144574 A1 WO2016144574 A1 WO 2016144574A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
resources
rsl
sidelink
information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2016/019886
Other languages
English (en)
Inventor
Chao-cheng TU
Paul Marinier
Benoit Pelletier
Aata EL HAMSS
Martino M. Freda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent 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 InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2016144574A1 publication Critical patent/WO2016144574A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the present disclosure relates generally to wireless communications and, more particularly to methods, apparatus and systems for link adaptation for device-to-device (D2D) communications.
  • D2D device-to-device
  • D2D communications are likely to be an important component of future (e.g., 5G) wireless networks.
  • 5G wireless networks For example, one envisioned application of D2D communications is peer-to-peer inter- vehicular communications, which would enable direct communications among vehicles for exchange of information (e.g., road safety, traffic congestion, etc.).
  • One representative method includes: receiving, by a first Wireless Transmit/Receive Unit (WTRU), information indicating Return Sidelink (RSL) resources associated with RSL D2D communication between the first WTRU and a second WTRU; determining, by the first WTRU, the RSL resources based on the received information; and transmitting, by the first WTRU to the second WTRU, sidelink information using the determined RSL resources.
  • WTRU Wireless Transmit/Receive Unit
  • RSL Return Sidelink
  • Another representative method includes: triggering a D2D link adaptation procedure; generating link adaptation information after triggering the D2D link adaptation procedure; and sending the link adaptation information to a second WTRU to configure a return sidelink (RSL) between the first WTRU and the second WTRU.
  • RSL return sidelink
  • a further representative method includes: determining a set of resources for RSL D2D communication from a first WTRU to a relay WTRU; and transmitting data to the relay WTRU using the set of resources for RSL D2D communication.
  • An additional representative method includes: generating, by a first WTRU, information indicating Return Sidelink (RSL) resources associated with RSL D2D communication between the first WTRU and a second WTRU; sending, by the first WTRU to a second WTRU, the information indicating the RSL resources; and receiving and decoding, by the first WTRU, sidelink information using the RSL resources indicated in the sent information.
  • RSL Return Sidelink
  • a yet further representative method includes: receiving, by a first WTRU, link adaptation information to configure a return sidelink (RSL) between the first WTRU and a second WTRU; triggering a D2D link adaptation procedure in response to reception of the link adaptation information; and encoding and sending, by the first WTRU, sidelink information using the link adaptation information.
  • RSL return sidelink
  • a still further representative method includes: determining a set of resources for RSL D2D communication from a first WTRU to a relay WTRU; and receiving data, by the relay WTRU from the first WTRU, using the determined set of resources for the RSL D2D communication.
  • FIG. 1 A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented;
  • FIG. IB is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A;
  • WTRU wireless transmit/receive unit
  • FIGS. 1C, ID, and IE are system diagrams of example radio access networks and example core networks that may be used within the communications system illustrated in FIG. 1A;
  • FIG. 2 is an example D2D communications environment in which embodiments may be practiced or implemented
  • FIGS. 3, 4 and 5 illustrate example scheduling periods for D2D communications according to example embodiments
  • FIG. 6 is a flowchart illustrating a representative sidelink configuration method
  • FIG. 7 is a flowchart illustrating a representative link adaptation method
  • FIG. 8 is a flowchart illustrating a representative sidelink configuration method involving a relay WTRU
  • FIG. 9 is a flowchart illustrating another representative sidelink configuration method
  • FIG. 10 is a flowchart illustrating another representative link adaptation method
  • FIG. 11 is a flowchart illustrating another representative sidelink configuration method involving a relay WTRU.
  • FIG. 1A is a diagram of an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • Example communications system 100 is provided for the purpose of illustration only and is not limiting of the disclosed embodiments.
  • 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), 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
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, 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 user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • netbook a personal computer
  • a wireless sensor consumer electronics, and the like.
  • the communications systems 100 may also include a base station 114a and a base station 114b.
  • Each of the base stations 114a, 114b 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 core network 106, the Internet 110, and/or the networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode-B, a Home Node B, a Home eNode-B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104, 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.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown).
  • the cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple- input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple- input multiple output
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 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 114a in the RAN 104 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 116 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 Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA), among others.
  • 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 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE- Advanced
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GERAN GSM EDGERAN
  • the base station 114b in FIG. 1 A 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, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular- based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.
  • a cellular- based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the core network 106.
  • the RAN 104 may be in communication with the core network 106, 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 core network 106 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 and/ or the core network 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 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 the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., 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 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram of an example WTRU 102.
  • Example WTRU 102 is provided for the purpose of illustration only and is not limiting of the disclosed embodiments.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 106, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138.
  • GPS global positioning system
  • the processor 118 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 Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 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 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 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 116.
  • a base station e.g., the base station 114a
  • 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 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. In certain representative embodiments, 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 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and/or 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 UTRA and IEEE 802.11, for example.
  • the processor 118 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 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 106 and/or the removable memory 132.
  • the non-removable memory 106 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 118 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 memory may be non-transitory memory.
  • 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 118 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.
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) 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 various representative embodiments.
  • a base station e.g., base stations 114a, 114b
  • the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with various representative embodiments.
  • 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 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, and the like.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs 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
  • FIG. 1C is a system diagram of the RAN 104 and the core network 106 according to an embodiment.
  • the RAN 104 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116.
  • the RAN 104 may also be in communication with the core network 106.
  • the RAN 104 may include Node-Bs 140a, 140b, 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • TheNode-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 104.
  • the RAN 104 may also include RNCs 142a, 142b. It will be appreciated that the RAN 104 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.
  • the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC142b.
  • the Node-Bs 140a, 140b, 140c may communicate with the respective RNCs 142a, 142b via an Iub interface.
  • the RNCs 142a, 142b may be in communication with one another via an lur interface.
  • Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected.
  • each of the RNCs 142a, 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macrodiversity, security functions, data encryption, and the like.
  • the core network 106 shown in FIG. 1C may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and/or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MGW media gateway
  • MSC mobile switching center
  • SGSN serving GPRS support node
  • GGSN gateway GPRS support node
  • the RNC 142a in the RAN 104 may be connected to the MSC 146 in the core network 106 via an IuCS interface.
  • the MSC 146 may be connected to the MGW 144.
  • the MSC 146 and the MGW 144 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 RNC 142a in the RAN 104 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface.
  • the SGSN 148 may be connected to the GGSN 150.
  • the SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • FIG. ID is a system diagram of the RAN 104 and the core network 106 according to another embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116.
  • the RAN 104 may also be in communication with the core network 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 116.
  • 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 receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, and 160c 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 uplink and/or downlink, and the like. As shown in FIG. ID, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the core network 106 shown in FIG. ID may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MME mobility management gateway
  • PDN packet data network
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node.
  • 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 also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
  • the serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the S 1 interface.
  • the serving gateway 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the serving gateway 164 may also perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the PDN gateway 166 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the core network 106 may facilitate communications with other networks.
  • the core network 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 core network 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 core network 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the core network 106 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • FIG. IE is a system diagram of the RAN 104 and the core network 106 according to another embodiment.
  • the RAN 104 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116.
  • ASN access service network
  • the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 104, and the core network 106 may be defined as reference points.
  • the RAN 104 may include base stations 170a, 170b, 170c, and an ASN gateway 172, though it will be appreciated that the RAN 104 may include any number of base stations and ASN gateways while remaining consistent with an embodiment.
  • the base stations 170a, 170b, 170c may each be associated with a particular cell (not shown) in the RAN 104 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the base stations 170a, 170b, 170c may implement MIMO technology.
  • the base station 170a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • the base stations 170a, 170b, 170c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like.
  • the ASN gateway 172 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 106, and the like.
  • the air interface 116 between the WTRUs 102a, 102b, 102c and the RAN 104 may be defined as an Rl reference point that implements the IEEE 802.16 specification.
  • each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 106.
  • the logical interface between the WTRUs 102a, 102b, 102c and the core network 106 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and/or mobility management.
  • the communication link between each of the base stations 170a, 170b, and 170c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations.
  • the communication link between the base stations 170a, 170b, 170c and the ASN gateway 172 may be defined as an R6 reference point.
  • the R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 100c.
  • the RAN 104 may be connected to the core network 106.
  • the communication link between the RAN 104 and the core network 106 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example.
  • the core network 106 may include a mobile IP home agent (MIP-HA) 174, an authentication, authorization, accounting (AAA) server 176, and a gateway 178. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MIP-HA mobile IP home agent
  • AAA authentication, authorization, accounting
  • the MIP-HA 174 may be responsible for IP address management, and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and/or different core networks.
  • the MIP-HA 174 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the AAA server 176 may be responsible for user authentication and for supporting user services.
  • the gateway 178 may facilitate interworking with other networks.
  • the gateway 178 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 gateway 178 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the RAN 104 may be connected to other ASNs and the core network 106 may be connected to other core networks.
  • the communication link between the RAN 104 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 104 and the other ASNs.
  • the communication link between the core network 106 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks.
  • FIG. 2 illustrates an example environment 200 in which embodiments may be practiced or implemented.
  • the example environment 200 is provided for the purpose of illustration only and is not limiting of disclosed embodiments.
  • the example environment 200 may include a base station 202, a WTRU 204a, and/or a WTRU 204b.
  • the example environment 200 may include additional components not shown in FIG. 2.
  • the base station 202 may be an embodiment of any one of base stations 114a and 114b described above with reference to FIG. 1 A, the Node-Bs 140a, 140b, and 140c described above with reference to FIG. 1C, the eNode-Bs 160a, 160b, and 160c described above with reference to FIG. ID, or the base stations 170a, 170b, and 170c described above with reference to FIG. IE, for example.
  • the WTRUs 204a and 204b may each be an embodiment of any one of the WTRUs 102a, 102b, and 102c described above with reference to FIGs. 1A-1E, for example.
  • the WTRU 204a is shown as being in-coverage (IC) (e.g., within the vicinity and/or coverage range) with respect to the base station 202 in the example environment 200.
  • the WTRU 204a may be Out-of-Coverage (OoC) with respect to the base station 202.
  • the WTRU 204b may be IC or OoC with respect to the base station 202.
  • communications between the WTRUs 204a and 204b and the base station 202 may take place in the example environment 200.
  • the WTRU 204a and the WTRU 204b may engage in communication with each other.
  • such communications are referred to as D2D communications.
  • the WTRU 204a may act as a relay between the WTRU 204b and the base station 202 when the WTRU 204b is OoC with respect to the base station 202.
  • communication between the WTRUs 204a and 204b may allow or may enable direct communication (e.g., direct data communication and/or control signaling for direct data communication) between the WTRUs 204a and 204b.
  • direct communication e.g., direct data communication and/or control signaling for direct data communication
  • D2D communications may be implemented to include one-to-one (e.g., unicast) duplex communications and/or relaying functionalities/operations (e.g., communications between, for example, the WTRUs 204a and 204b), which may accommodate applications such as File Transfer Protocol (FTP), web browsing, video streaming, and/or gaming, among others, for example for commercial uses.
  • FTP File Transfer Protocol
  • the D2D communication may support reliable low- latency communications, for example, among densely deployed devices. It is contemplated that the D2D communications may provide a reliability exceeding a threshold reliability, and/or a latency below a threshold latency, for example on condition that a number of devices are deployed with at least a threshold density. Such communications may be generally characterized by a certain transmit power constraint and may have to meet various data rate requirements.
  • D2D communication may support different WTRU mobility (e.g., high mobility, normal mobility and/or low mobility, and/or changing mobility of the WTRU 204a or 204b, among others), various traffic types, different coverage areas (e.g., large coverage areas, normal coverage areas, small coverage areas, and/or changing coverage areas of the WTRU 204a or 204b, among others), and/or public safety/commercial uses, among others.
  • WTRU mobility e.g., high mobility, normal mobility and/or low mobility, and/or changing mobility of the WTRU 204a or 204b, among others
  • various traffic types e.g., large coverage areas, normal coverage areas, small coverage areas, and/or changing coverage areas of the WTRU 204a or 204b, among others
  • different coverage areas e.g., large coverage areas, normal coverage areas, small coverage areas, and/or changing coverage areas of the WTRU 204a or 204b, among others
  • public safety/commercial uses among others.
  • Mobility support may include different mobility levels for high mobility to low mobility WTRU. It is contemplated that the D2D communications may be implemented in scenarios where the transmit WTRU (for example WTRU 204a) and/or the receive WTRUs (for example, WTRUs 204b) are stationary or semi- stationary (e.g., relative to each other and/or the environment). A higher data rate may be anticipated in such scenarios. In addition, D2D communications may be implemented in high mobility scenarios, such as in peer-to-peer inter-vehicular communication (e.g., where the transmit WTRU 204a and/or the receive WTRUs 204b are not stationary or are not semi- stationary (e.g., relative to each other and/or the environment). For non-stationary or non- semi-stationary scenarios a reduced and/or dynamic data rate may be used to cope with and/or provide for time-varying channel conditions.
  • the transmit WTRU for example WTRU 204a
  • the receive WTRUs for example, WTRU
  • Supported traffic types may vary (e.g., may vary drastically) in D2D communication contexts.
  • a reliable (e.g., more reliable) and/or periodic data transmission may be appropriate and/or required for machine-type D2D communications.
  • bursty data transmission support may be appropriate and/or required to enable applications similar to HTTP adaptive streaming (HAS).
  • HTTP adaptive streaming HTTP adaptive streaming
  • the coverage area size may vary (e.g., over a wide range) in D2D communication contexts.
  • transmission quality may vary depending on the coverage area (e.g., coverage area size).
  • transmission parameters and/or resource allocations may be adjusted (e.g., appropriately adjusted).
  • the D2D communications may support public safety scenarios and/or commercial use scenarios.
  • public safety uses a reliable, robust, and/or resilient communications framework may be appropriate/needed and may be relaxed for commercial uses.
  • dedicated resources to support public safety may be appropriate and/or required when implemented (e.g., when there is a need). These dedicated resources may be released when commercial uses are supported (e.g., when only commercial uses are operating).
  • D2D communications may include link adaptation.
  • certain representative embodiments may enable feedback and/or control channels between D2D WTRUs to enable link adaptation in the D2D communications.
  • a new supporting framework for link adaptation is described herein.
  • link adaptation may be implemented based on one or more of half-duplex, broadcast-based, and/or VoIP-oriented D2D communication frameworks. For example, procedures/operations to determine when to apply link adaptation in a D2D communication context may be implemented. For example, the procedures/operations may determine criteria for starting and/or stopping link adaptation (e.g., by a WTRU in the same context).
  • procedures/operations for performing link adaptation measurements and/or reporting in a D2D communication context may be implemented (for example, which may address challenges associated with D2D communications or that may be particular to D2D communications).
  • representative procedures/operations may accommodate connection-less transmissions and/or contention-based resource access that may occur in D2D communications (for example, in OoC scenarios).
  • Other representative embodiments may be equally applicable for IC scenarios, even though WTRU resources to be applied for transmit WTRUs may be determined by the network in the IC scenarios.
  • procedures/operations may implemented to manage, change, increase, decrease and/or maximize throughput and/or may be based on throughput.
  • the procedures/operations may be aggressive (e.g., more or most aggressive) in terms of resource access and/or may exploit a maximum of available resources.
  • procedures/operations may implemented to manage, change, increase, decrease and/or maximize reliability and/or may be based on reliability.
  • the procedures/operations may be conservative (e.g., more or most conservative) in terms of resource access and may be achieved by segregating resources based on priority, and may maintain a stable connection between WTRUs with a given QoS.
  • the terminology scheduling period generally refers to a period of time over which a scheduling assignment is transmitted and valid.
  • the scheduling period generally encompasses a control period and a data period.
  • SA scheduling assignment
  • a control signal may include modulation and coding schemes, sender/target identifiers (e.g., identifiers that may be associated with the sender/target WTRUs of D2D transmissions within a data period identified by the SA), and/or information regarding time/frequency resources to be applied for data transmission (e.g., within an associated data transmission period).
  • sender/target identifiers e.g., identifiers that may be associated with the sender/target WTRUs of D2D transmissions within a data period identified by the SA
  • information regarding time/frequency resources to be applied for data transmission e.g., within an associated data transmission period.
  • data transmission period generally refers to a period of time over which a D2D WTRU (a WTRU that is engaged in D2D communications) transmits/receives data, as indicated by an associated SA.
  • the term may be defined in terms of absolute time (e.g. 160ms) or in terms of D2D sub-frames allocated for D2D transmission.
  • Time Resource Pattern of Transmission generally refers to a set of sub-frames used by a WTRU for transmitting data.
  • a T-RPT may indicate resources for transmitting one or more MAC PDUs(for example, each MAC PDU). When multiple MAC PDUs are available, the T-RPT may indicate one or more transmission intervals between or among them.
  • forward sidelink generally refers to a transmission link established from a transmit WTRU to a receive WTRU in a D2D (unicast) communication context.
  • the FSL may or may not be part of an SA.
  • the terminology return sidelink generally refers to a transmission link established from a receive WTRU to (e.g., back to) a transmit WTRU in a D2D unicast communication context.
  • a RSL may be used for the transmission of: (1) sidelink control information (SCI); (2) reference signals (e.g., which may be used for sounding, demodulation and/or measurements, among others); and/or (3) data and/or higher layer control information (e.g., from a reacting WTRU to an initiating WTRU).
  • SCI sidelink control information
  • reference signals e.g., which may be used for sounding, demodulation and/or measurements, among others
  • data and/or higher layer control information e.g., from a reacting WTRU to an initiating WTRU.
  • the RSL may be used for transmission during a scheduling period associated with a FSL of a transmit WTRU.
  • SCI generally refers to control information communicated in a sidelink (SL) that may include, for example, Hybrid-Automatic Repeat Request (H-ARQ) feedback and/or channel state information, among others.
  • SL sidelink
  • H-ARQ Hybrid-Automatic Repeat Request
  • the terminology measuring WTRU generally refers to a WTRU that is configured to: (1) perform measurements, such as channel condition measurements and/or reception quality measurements, among others and/or (2) feedback information, for example in a link adaptation procedure/process.
  • actuating WTRU generally refers to a WTRU that is configured to: adjust transmission and/or reception related parameters (e.g., Modulation and Coding Scheme (MCS) and/or configurations of resource pools, among others), for example, based on information and/or signaling from another WTRU (e.g., a measuring WTRU).
  • MCS Modulation and Coding Scheme
  • an actuating WTRU may or may not be the same WTRU as a transmit WTRU.
  • reacting WTRU generally refers to a WTRU that is configured to react in response to an actuating WTRU, for example, in a link adaptation procedure/process.
  • a reacting WTRU may or may not be the same WTRU as a receive WTRU.
  • initiating WTRU generally refers to a WTRU that is configured to initiate transmission of an SA.
  • relay WTRU generally refers to a WTRU that is within network coverage and that provides and/or offers relay services to WTRUs that may be inside or outside of network coverage.
  • remote WTRU refers to a WTRU that is outside of network coverage.
  • a remote WTRU may seek and/or use relay services from a relay WTRU.
  • procedures are implemented to determine when to start/stop link adaptation in a D2D communication context.
  • a WTRU 204a or 204b may be configured to start/stop link adaptation based on one or more external indications.
  • the WTRU 204a or 204b may use one or more of the following example external indications to start and/or stop link adaptation, in any order and/or combination:
  • External indications from an eNode-B 202 and/or a reference source are obtained and/or received by the WTRU 204a or 204b.
  • the WTRU 204a or 204b may be instructed to start/stop link adaptation through, for example, Radio Resource Control (RRC) signaling, Physical Downlink Control Channel (PDCCH) signaling, Enhanced PDCCH (E-PDCCH) signaling, and/or a synchronization signal such as a Physical D2D Shared Channel (PD2DSCH), sent by the eNode- B 202 or other reference source.
  • RRC Radio Resource Control
  • PDCH Physical Downlink Control Channel
  • E-PDCCH Enhanced PDCCH
  • a synchronization signal such as a Physical D2D Shared Channel (PD2DSCH)
  • PD2DSCH Physical D2D Shared Channel
  • the E-PDCCH and/or PDCCH signaling may be used, for example for dynamic configurations, in the context of link adaptation.
  • the RRC signaling may be applied when a special high data-rate service is granted to a specific D2D WTRU 204a or 204b and/or a specific group of WTRUs 204a and 204b, for a certain subscription period (e.g., in the order of seconds).
  • the E-PDCCH and/or PDCCH may be used.
  • the E-PDCCH and/or PDCCH may be used when or on condition that interference exists exceeding a threshold (e.g., temporary, significant interference exists), for example, in a certain geographic area.
  • a threshold e.g., temporary, significant interference exists
  • External indications from other WTRUs may be obtained and/or received by the WTRU.
  • the WTRU may be instructed to start/stop link adaptation by other WTRUs. This may be achieved using one or more of the example procedures described herein.
  • explicit control messages (and/or signals) may be obtained by the WTRU.
  • a transmit WTRU 204a may send a special 7-bit activation/de-activation code in the SA (e.g., as part of the SCI) to a receive WTRU 204b.
  • a synchronization message e.g., received on the Physical Sidelink Broadcast Channel (PSBCH)
  • PSBCH Physical Sidelink Broadcast Channel
  • implicit control messages may be used.
  • a receive WTRU 204b may be configured to enable link adaptation if an MCS index indicated in the SA corresponds to a higher-order modulation and/or code rate than a currently used MCS.
  • the receive WTRU 204b may have flexibility to fall back to a lower order modulation and/or code-rate when transmission conditions become worse (for example, based on a rule which may be predefined and/or signaled via the transmit WTRU 204a).
  • an activation of the link adaptation may be associated with the reception of a special WTRU identifier, for example sent and/or received in the SA.
  • the WTRU 204a may be configured with one or more WTRU identifiers, a subset of which may be associated with communication using link adaptation, and other WTRU identifiers may be associated with communication without link adaptation.
  • the WTRU 204a or 204b may be configured to use (e.g., always use) link adaptation when sending and/or receiving unicast data communications, as identified by the identifier in the SA.
  • the WTRU 204b may be configured to not use link adaptation procedures and/or mechanisms for communications associated with broadcast and/or multicast identifiers.
  • the activation of the link adaptation may be associated with the reception of a synchronization signal and/or a synchronization message.
  • the WTRU 204a or 204b may activate link adaptation when the synchronization signal/message exhibits specific characteristics.
  • a WTRU 204a or 204b may determine autonomously when to start and/or stop link adaptation, for example, by using one or more of the triggers that are disclosed herein, in any order and/or combination.
  • the WTRU 204a may be configured to use the presence of Wide Area Network (WAN) uplink/downlink (UL/DL) traffic as a trigger for activating/deactivating the link adaptation.
  • WAN Wide Area Network
  • UL/DL Uplink/downlink
  • the WTRU 204a may be configured to determine whether or not D2D communications are taking place in the same subframes as WAN cellular communication (e.g., WTRU to eNode-B communications). This may be achieved, for example, by decoding the PDCCH or the EPDCCH and by checking whether concurrent transmissions of WAN and D2D traffic are present.
  • the WTRU 204a or 204b may rely on and/or use the signal quality of a received SA (e.g., power and/or Signal to Interference and Noise Ratio (SINR), among others) for triggering link adaptation.
  • a received SA e.g., power and/or Signal to Interference and Noise Ratio (SINR), among others
  • SINR Signal to Interference and Noise Ratio
  • the WTRU 204b may be configured to activate/deactivate link adaptation based on whether the received SA signal quality is below a certain pre-configured threshold.
  • the WTRU 204b may use the average signal quality (e.g., power, SINR, error rate, among others) of the previous one or more received data transmissions, or the average signal quality (e.g., power, SINR, among others) of discovery messages and/or responses thereto (received from one or more associated WTRUs in unicast communications) for activating/deactivating the link adaptation.
  • the average signal quality e.g., power, SINR, error rate, among others
  • the average signal quality e.g., power, SINR, among others
  • the WTRU 204a or 204b may be configured to determine whether a number of erroneously decoded packets in a given period of time (e.g., in one or more past scheduling periods) is above a certain pre-configured or configured threshold.
  • the WTRU 204a or 204b may activate/deactivation the link adaptation based on the determined result (e.g., if a threshold is exceeded, link adaptation may be started or stopped).
  • the WTRU 204a or 204b may be configured to activate/deactivate the link adaptation when configured in a public safety mode.
  • the WTRU 204a or 204b may be configured to activate/deactivate the link adaptation based on a buffer status. In one example, if a D2D transmit buffer of the WTRU 204a or 204b is full and/or above a threshold, the WTRU 204a or 204b may start using link adaptation.
  • the WTRU 204a or 204b may be configured to perform one or more of the following actions, in any order and/or combination: (1) employ a special SA/SCI format to support the link adaptation (for example, the WTRU 204a may be configured to transmit SAs with different Redundancy Vectors (RVs) and/or with a special SA format to carry additional link adaptation related parameters when link adaptation is activated); (2) use a different procedure/mechanism for transmit resource selection (for example, the WTRU 204a may be configured to employ a listen-before-talk procedure/mechanism, and/or may use resources indicated by a receive WTRU 204b (e.g., via new signaling); (3) change transmission/reception related parameters (for example, the WTRU 204a or 204b may be configured to use different MCS tables, resource pools (e.g., the WTRU 204a or 204b may
  • the WTRU 204a or 204b when a WTRU 204a or 204b is triggered to stop the link adaptation, the WTRU 204a or 204b may be configured to perform one or more of the following actions, in any order and/or combination:
  • [0096] (1) transmit an indication to notify other WTRUs of the link adaptation deactivation (for example, the indication may be a link adaptation deactivation message);
  • [0097] (2) employ a normal SA/SCI format (for example, the WTRU 204a or 204b may be configured to use a normal SA/SCI format when link adaptation is deactivated (e.g., the WTRU 204a or 204b may be configured to use a legacy SA format (for example, 3GPP Release 12 SA format)));
  • a legacy SA format for example, 3GPP Release 12 SA format
  • a conventional (e.g., 3GPP Release 12) resource selection mechanism for example, the WTRU 204a or 204b may be configured to employ a random selection mechanism without using listen-before-talk procedures/mechanisms);
  • (4) use a configured (e.g., pre-configured) set of transmission/reception related parameters (for example, such parameters may include an MCS table, resource pools, and/or power per resource block, among others for conventional (e.g., 3GPP Release 12) or non-link adaptation scenarios;
  • a configured (e.g., pre-configured) set of transmission/reception related parameters may include an MCS table, resource pools, and/or power per resource block, among others for conventional (e.g., 3GPP Release 12) or non-link adaptation scenarios;
  • (5) stop sending and receiving a link adaptation feedback signal for example, the WTRU 204a or 204b may stop sending control information related to the RSL (e.g., ACK/NACK information, Channel State Information (CSI) feedback, and/or Channel Quality Indicator (CQI) information, among others);
  • control information related to the RSL e.g., ACK/NACK information, Channel State Information (CSI) feedback, and/or Channel Quality Indicator (CQI) information, among others
  • Link adaptation may use measurements (e.g., measuring channel conditions, reception quality, and/or feedback information, among others).
  • the measurements may be performed at a transmit WTRU 204a (e.g., relying on reciprocity), at a receive WTRU 204b (e.g., relying on signaling to the transmit WTRU 204a), at an eNode-B 202, and/or other reference sources (e.g., relying on broadcast signaling such as SIB, other public safety D2D WTRUs such as D2D synchronization sources, among others).
  • SIB broadcast signaling
  • D2D WTRUs such as D2D synchronization sources
  • link adaptation measurements may be applied on known signals and/or reference sources that are transmitted to assist link adaptation directly.
  • the WTRU 204a or 204b may exploit DeModulation Reference Signal (DM-RS) signals and/or other reference signals (e.g., synchronization signals) for the determination of channel conditions (e.g., time-varying channel conditions).
  • DM-RS DeModulation Reference Signal
  • the WTRU 204a or 204b may then report CSI and/or select appropriate link adaptation parameters to report and/or use.
  • link adaptation measurements may be derived implicitly from signals and/or channels that are not used for (e.g., intended for) assisting with link adaptation.
  • the WTRU 204a or 204b may be configured to estimate channel conditions, for example, based on procedures other than pilot-based channel estimation.
  • a D2D WTRU 204a or 204b may be configured to use (e.g., exploit) one or more of the following signals and/or channels in any order and/or combination to infer link adaptation information:
  • a D2D discovery signal or signals for example, the WTRU 204a or 204b may gain knowledge of (e.g., obtain and/or determine) the number of surrounding transmit WTRUs based on the number of received D2D discovery signals which may allow the WTRU 204a or 204b to estimate potential interference for D2D unicast communications;
  • the D2D synchronization sources e.g., a D2D Synchronization Signal (D2DSS), a Physical D2D Synchronization Channel (PD2DSCH), and/or a Physical Sidelink Broadcast Channel (PSBCH), among others
  • D2DSS D2D Synchronization Signal
  • PD2DSCH Physical D2D Synchronization Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the WTRU 204a or 204b may be configured to check whether the accuracy of a carrier frequency received from a synchronization source meets a threshold (e.g., pre-determined threshold).
  • a threshold e.g., pre-determined threshold
  • the accuracy of the carrier frequency from the synchronization source may be compared to (e.g., against) the accuracy of a local modulated carrier frequency over one or more slots (e.g., one slot) to determine if the threshold (e.g., pre-determined threshold) is met. If the accuracy of the carrier frequency from the synchronization source is below the threshold (e.g. , pre-determined threshold), the WTRU 204a or 204b may infer a bad channel condition and may activate link adaptation; and/or
  • WAN UL/DL signals for example, in Interference Cancelation (IC) cases, a D2D WTRU 204a or 204b may use WAN UL/DL signals to infer position information, such as proximity to a cell-edge and/or proximity to one or more eNode-Bs 202. Based on the inferred position information, the WTRU 204a or 204b may infer about potential interference on a particular D2D communication sidelink.
  • position information such as proximity to a cell-edge and/or proximity to one or more eNode-Bs 202.
  • the WTRU 204a or 204b may infer about potential interference on a particular D2D communication sidelink.
  • link adaptation measurements and/or information may be derived implicitly from information and/or statistics gathered during reception/transmission procedures/processes.
  • One example includes relying on received ACK/NACK indications and/or information (e.g., a receive WTRU 204b sends a NACK to a transmit WTRU 204a when a Cyclic Redundancy Check (CRC) error is detected and an ACK, otherwise).
  • the transmit WTRU 204a may increase and/or may decrease the transmit power.
  • the transmit WTRU 204a may be configured to increase and/or decrease a MCS based on the received ACK/NACK indications/information (e.g., a large number of NACKs may be indicative of a bad channel condition, and may cause the transmit WTRU 204a to decrease the MCS and/or decrease the transport block size).
  • the measuring WTRU 204b may be configured to determine and/or measure one or more of the following information and/or statistics, in any order and/or combinations for the purpose of link adaptation (e.g., to start, stop and/or modify the FSLs and/or RSLs):
  • a number of H-ARQ re-transmissions (for example, if a D2D WTRU 204a or 204b is configured not to employ blind H-ARQ transmissions, the number of H-ARQ re-transmissions and/or statistics associated with the H-ARQ re-transmissions may be used to characterize a transmission link quality.
  • a measuring WTRU 204b may report the number of H- ARQ re-transmissions that occurs over a certain period of time.
  • the measurement reported may be based on the number of successful H-ARQ re-transmissions (e.g., 1, 2, or 3) over a certain period of time.
  • the WTRU 204a or 204b may use the number of successfully decoded packets as a statistic for link adaptation purposes);
  • a number of blindly decoded SAs may use information regarding a number of received SAs during, for example, one or more scheduling periods, as an estimate of interference.
  • the SAs that are counted may or may not include SAs with identifiers that do not match the WTRU' s ID. Similar interference metrics may also be determined from statistics associated with the selected T-RPT.
  • the WTRU 204a or 204b may use the number of attempts that a specific length of T- RPT (e.g., as determined from a set of received SAs) is employed to derive an interference metric);
  • a transmit D2D WTRU 204a may be configured to send SAs at a pre-determined interval, based on a trigger event and/or periodically (e.g., even when the communications between the WTRUs 204a and 204b are scheduled to last for a long time (e.g., longer than a threshold period of time)).
  • the transmit WTRU 204a may be configured to use and/or employ resources (e.g., resource blocks (RBs) that are less subject to interference to facilitate the periodic transmissions.
  • resources e.g., resource blocks (RBs) that are less subject to interference to facilitate the periodic transmissions.
  • a repeated failure to access a certain group ID or WTRU ID may indicate that the resources are to be more judiciously selected (e.g., resources may be selected based on a non- sporadic interference level being below a threshold and/or a sporadic interference level being below a threshold for the selected resources));
  • [0115] (4) a number of attempts to use specific initial RBs (or frequency resources) (e.g., as determined from a set of received SAs) (for example, if two or more WTRUs 204a and 204b randomly choose the same frequency resources in their associated SAs (e.g., initial RBs), collisions may occur throughout the transmission periods (e.g., with or without the use of frequency hopping). If the resource pool size is small, frequent collisions may occur. In one example, the WTRU 204a or 204b may be configured not to select (or to select with lower probability) initial RBs that have experienced frequent collisions. The RBs may be prioritized based on the number of collisions, for example to select the RBs with the highest probably of not colliding);
  • a number of collisions perceived by a measuring WTRU 204b (for example, the measurement may be carried out by analyzing resources associated with a set of received SAs);
  • timing adjustment (TA) for the TA field in an SA for example, the TA field in an SA may include bits to indicate the maximum cell deployment radius.
  • a change e.g., significant change above a threshold amount
  • transmission conditions may have changed (e.g., changed significantly));
  • [0118] (7) results from D2D WTRU discovery (for example, when a WTRU 204a is configured for Model-B discovery, the WTRU 204a may use responses of discovered D2D WTRUs 204b to select transmit power levels. From the responses of the discovered D2D WTRUs 204b, the WTRU 204a may apply different power levels, as appropriate, for unicast communications);
  • (8) status of the H-ARQ soft buffer (for example, the status of the H-ARQ soft buffer may be used for the purpose of link adaptation.
  • the WTRU 204a or 204b may employ link adaptation when the H-ARQ soft buffer is full and/or above a certain level to clear up the buffer faster);
  • D2D WTRU capabilities for example, link adaptation may be applicable (e.g., may only be applicable) for WTRUs 204a and 204b with link adaptation capabilities.
  • WTRUs 204a and 204b with link adaptation capabilities may be able to opt-out of link adaptation, for example by providing an opt-out indication to other WTRUs);
  • a WTRU ID and/or group ID (e.g., specific WTRU ID and/or specific group ID) (for example, for public safety, a WTRU 204a associated with an emergency personnel (e.g., fire department chief) may have a higher priority among other D2D WTRUs 204b (e.g., the WTRU 204a may be configured with more (e.g., many more) transmission resources or even dedicated transmission/reception resources). In one example, the WTRU 204a may be allowed to use (e.g., fully use all) the available frequency resources for data transmissions);
  • power density and/or power spectral density related measurements may be used to infer information, for example, for the purpose of link adaptation.
  • a WTRU 204b may measure and/or estimate the power spectral density for D2D and/or cellular communications.
  • the WTRU 204b may estimates the power spectral density by measuring reference signal received power (RSRP) in LTE or other radio access technologies, such as GERAN, HSPA+, WiFi and/or WLAN, among others); and/or
  • RSRP reference signal received power
  • a presence of cellular UL/DL transmissions may be used to determine whether link adaptation is applied and/or to select link adaptation parameters.
  • the WTRU 204a or 204b may be configured to determine the presence of cellular UL/DL transmissions that may interfere with D2D communications), among others.
  • the WTRU 204a may be configured to use one or more of the following parameters in determining link adaptation parameters:
  • TX/RX D2D transmit/receive
  • characteristics e.g. priority class, QoS), etc.
  • D2D communications e.g. PS/Non- PS, unicast/groupcast/broadcast, relaying/non-relaying
  • WTRU state e.g., Idle-mode or Connected-mode, among others.
  • Reporting may be a component of the link adaptation procedures/processes. Preceded by the measuring procedure/process, reporting may include transporting measurements or other control information from a measuring WTRU 204b (or other reference source) to an actuating WTRU 204a. It is contemplated that the measuring WTRU may be the same WTRU or a different WTRU from the actuating WTRU (in which case the reporting may be carried out internally in the same WTRU).
  • the WTRU 204b may be configured to report any one or more of: ACK/NACK messages, channel-related measurements (e.g., CSI, RSRP, and/or interference level, among others), and/or scheduling grant information, among others.
  • the WTRU 204b may be configured to report at specific time instants and/or periodically, for example, during a scheduling period (e.g., once every scheduling period).
  • D2D communications may include broadcast communications, multicast communications and/or unicast communications.
  • D2D broadcast communications feedback or control reporting mechanisms may not be included.
  • the WTRU 204a or 204b may rely on the FSL and/or the RSL for reporting, for example in OoC cases.
  • the WTRU 204a or 204b may be configured to use one or more of the following procedures for reporting, in any order and/or combination:
  • a WTRU 204b may use reporting transport procedures/mechanisms that may be based on explicit signaling via the SA.
  • the reporting transport procedures/mechanisms may include for example: (i) use of bits (e.g., additional bits) in the SA for link adaptation reporting (e.g., in certain representative embodiments, additional bits may be introduced in the existing SA to enable reporting in the FSLs and/or RSLs. In one example, an additional 1-bit may be introduced in the SA on the RSL for ACK/NACK feedback. Alternatively or additionally, multiple bits may be introduced to carry combined ACK/NACK feedback for multiple packets and/or to carry CSI information.
  • bits e.g., additional bits
  • link adaptation reporting e.g., additional bits
  • additional bits may be introduced in the existing SA to enable reporting in the FSLs and/or RSLs.
  • an additional 1-bit may be introduced in the SA on the RSL for ACK/NACK feedback.
  • multiple bits may be introduced to carry combined ACK/NACK feedback for
  • a modified S A format may be used, for example, to accommodate the additional information carried.
  • the WTRU 204b receiving the SA may determine the SA format used based on whether or not D2D unicast communications is used and/or employed.
  • the WTRU 204b receiving the SA may be configured to blindly decode the SA format from among a set of allowed SA formats in unicast operations); and/or (ii) use of an invalid indication and/or invalid indication information of one or more frequency resources for data in the SA (for example, an indication of initial frequency resources to be used for data in the SA may follow a 3GPP Release 8 UL Type 0 resource allocation.
  • the indications may be valid (e.g., only valid) when the specified frequency resources are contiguous in the frequency domain.
  • invalid indications and or invalid indication information may be used for reporting.
  • the WTRU may interpret the content of the SA differently than for a SA without such an indication (e.g., a conventional SA).
  • the WTRU 204b may process the invalid indication so as to extract measurements carried in the SA, instead of a regular scheduling assignment);
  • transport procedures/mechanisms based on a data channel e.g., a Physical Sidelink Shared Channel (PSSCH)
  • a WTRU 204b may use reporting transport procedures/mechanisms that are based on transmission of control information on a data channel.
  • Such transport procedures/mechanisms may include, for example: (i) use of reserved frequency and/or time resources for reporting purposes.
  • the WTRU 204b may be configured to use a special set of resources and/or a reserved set of resources on the data channel, for example as defined by a special resource pool for reporting (e.g., only for reporting purposes).
  • a WTRU 204b may be configured to transmit measurements (e.g., only measurements) over these resources.
  • a receive WTRU 204b may be configured to determine that the information transmitted over those resources consists of reports and/or measurements.
  • the receive WTRU 204b may be configured to interpret a received signal derived from the resources in a pre-defined way, for example to extract the signaled reports and/or measurements.
  • the set of resources allocated for reporting and/or transmission parameters associated with the set of resources allocated may be indicated using a conventional SA.
  • an initial frequency allocation indicated in the SA may infer, point to and/or be associated with the reserved resource pool, which may be used for reporting messages);
  • the WTRU 204a or 204b may determine resources for reporting based on resources used for an associated SA and/or for data transmission.
  • the WTRU 204a or 204b may be configured with a mapping function that may use the associated SA (and/or data) resource allocation parameters to determine resources parameters for reporting.
  • the WTRU 204a or 204b may be configured to use frequency resources that may be adjacent to the SA (and/or the data) frequency resources, for example, for reporting purposes.
  • the WTRU 204a or 204b may be configured to use the same frequency resources as the SA (and/or data) in a different, relative (e.g., known relative) time instant (e.g., N subframes after an event such as 4 subframes or more after the SA or a timing window after an event or trigger occurs)); and/or
  • the WTRU 204a or 204b may determine resources for reporting from the T-RPT. Examples may include: (i) reserving a subset of T-RPTs for reporting (for example, a set of T-RPTs may be reserved for transmission of reporting data. The set of reserved T-RPTs may be pre-defined and/or signaled, for example to enable unicast communications), (ii) using a complement subset of T-RPTs for reporting (for example, the WTRU 204a or 204b may be configured not to use a certain subset (e.g., a forbidden and/or barred subset of the T-RPTs for data transmission).
  • a subset of T-RPTs for reporting for example, a set of T-RPTs may be reserved for transmission of reporting data.
  • the set of reserved T-RPTs may be pre-defined and/or signaled, for example to enable unicast communications
  • using a complement subset of T-RPTs for reporting for example,
  • the forbidden subset of T-RPTs may be used for reporting); and/or (iii) deriving a T-RPT for reporting based on the T-RPT of an associated transmission
  • the WTRU 204a or 204b may be configured to determine a T-RPT for reporting based on a T-RPT selected for an associated data transmission (e.g., in the received S A).
  • the WTRU may be configured to use the next available T-RPT(s) (e.g., in order of indices) for the reporting), among others.
  • a WTRU 204b may be configured to send measurements through an eNode-B 202 or other reference source.
  • the eNode-B 202 or other reference source may configure an actuating WTRU 204a (e.g., via a grant or other resource allocation/assignment) based on the measurements.
  • the WTRU 204a may be configured, for example, with link adaptation parameters or related measurements by the eNode-B 202 or other reference source.
  • the WTRU 204a may be configured using one or more of the following: (1) a D2D grant (e.g., received on the PDCCH and/or the E-PDCCH); (2) an RRC signaling and/or higher layer signaling; and/or (3) the PDCCH and/or the E-PDCCH signaling, among others.
  • a D2D grant e.g., received on the PDCCH and/or the E-PDCCH
  • the WTRU 204a may be configured through a special downlink control information (DCI) format, for example, for link adaptation (e.g., used for link adaptation purposes).
  • DCI downlink control information
  • link adaptation e.g., used for link adaptation purposes
  • the WTRU 204a or 204b may be configured to employ and/or use one or more of the following, in any order and/or combination: (1) a WAN CQI report (for example, the WTRU 204a may use an extended or modified CQI table to signal D2D link adaptation reporting information to the eNode- B 202, for example, over the Physical Uplink Control Channel (PUCCH) and/or the Physical Uplink Shared Channel (PUSCH).
  • a WAN CQI report for example, the WTRU 204a may use an extended or modified CQI table to signal D2D link adaptation reporting information to the eNode- B 202, for example, over the Physical Uplink Control Channel (PUCCH) and/or the Physical Uplink Shared Channel (PUSCH).
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • the WTRU 204a may be configured to select a subband and/or a set of subbands (e.g., a specific set of subbands) that may be assigned for D2D communications.
  • the WTRU 204a may be configured by higher-layer-configured subband CQI (e.g., for aperiodic (e.g., more aperiodic) reporting purposes)); (2) WAN ACK/NACK (for example, D2D reporting may be combined with a WAN ACK/NACK indication over the PUCCH and/or the PUSCH); and/or (3) a Scheduling Request (SR) for D2D communications (for example, the SR may be used to carry reporting data to the eNode-B 202); (4) a Buffer status report (BSR) (for example, the BSR may be used to carry reporting data to an eNode-B 202); and/or (5) Reserved CSI and/or HARQ
  • SR Scheduling Request
  • a WTRU 204a may be configured to establish D2D unicast communications with more than one WTRU 204b.
  • the WTRU 204a may be configured to report to the eNode-B 202 (or the other reference source) an associated target user/group ID.
  • the report may include or be separate from measurements sent to the eNode-B 202 (e.g., any appropriate measurements).
  • the WTRU 204a may be configured with one set of resources for a target user/group ID (e.g., each target user/group ID) that the WTRU 204a is to report (e.g., which may be suitable when the WTRU 204a reports via a PUCCH procedure/mechanism.
  • a target user/group ID e.g., each target user/group ID
  • the WTRU 204a may explicitly indicate the user/group ID in the message, for example when reporting via MAC (e.g., BSR) or other higher layer messages.
  • reference sources may be considered as special-purpose D2D WTRUs 204 or mini-eNode-Bs 202 (e.g., with basic functionality, for example, not all eNode-B 202 functionality).
  • the other reference resources may be deployed over a certain coverage area, and may not be restricted to IC and/or OoC implementations.
  • the other reference sources may monitor surrounding D2D traffic and, for example, may send recommendations to one or more transmit/receive WTRUs 204a and 204b and/or the eNode-Bs 202 (e.g., for data traffic monitoring, congestion control, and/or priority administrations, among others).
  • the reference sources may communicate with each other to improve overall system throughput according to certain criteria or criterion, for example.
  • D2D unicast (e.g., two-way) communications may use a return data transmission procedure/ mechanism and may include a data transmission link established from a receive WTRU 204b to (e.g., back to) a transmit WTRU 204a (e.g., a RSL).
  • a transmit WTRU 204a e.g., a RSL.
  • procedures and apparatus may be implemented to determine appropriate time/frequency resources for the RSL and/or to manage an allocation of available resources between FSLs and RSLs.
  • RSL resources may be used to carry user data and/or control information.
  • RSL resources may be a subset of Time Resource Pattern of Transmissions (T-RPT) resources and may be defined by and/or may be identified in the SA. FSL transmission may not be allowed on the subset of T-RPT resources assigned to the RSL.
  • T-RPT Time Resource Pattern of Transmissions
  • FIGS. 3-5 illustrate example scheduling periods for D2D communications according to example embodiments.
  • FIG. 3 illustrates a representative sidelink transmission 300.
  • the transmit WTRU 204a and the receive WTRU 204b may use different portions (e.g., scheduled, contention free portions) of the representative sidelink transmission 300 to transmit and/or receive sidelink information during sidelink communication.
  • the representative sidelink transmission 300 may include a control period 301 and/or a data period 302.
  • the data period 302 may follow (e.g., in time) the control period 301.
  • the control period 301 may include one or more S As 310.
  • the data period 302 may include a plurality of (T-RPTs) resources (e.g., resource blocks).
  • the T-RPTs may include a first type of T-RPT (e.g. T-RPT-1) and/or a second type of T-RPT (e.g., T-RPT-2).
  • the first type of T- RPT may be used for FSL communication from a transmit WTRU 204a to a receive WTRU 204b.
  • the second type of T-RPT may be used for RSL communication from a receive WTRU 204b to a transmit WTRU 204a.
  • the T-RPTs e.g., the T-RPT-1 and the T-RPT-2) may include a plurality of intervals (e.g., subframes).
  • One or more of the intervals (e.g., subframes) in the TRPT-1 may include data 320 (e.g., FSL data and/or control signaling).
  • One or more of the intervals (e.g., subframes) in the TRPT-2 may include data 330 (e.g., RSL data and/or control signaling).
  • a T-RPT-2 may be reserved for RSL transmission.
  • the RSL T-RPT-2 may occur after N consecutive forward T-RPT-1 s.
  • the value of N may correspond to the number of subframes K available for transmission for the T-RPT pattern to ensure that at least one subframe is available for the RSL in the repeated T-RPT pattern (e.g., in every repetition of the T-RPT pattern).
  • the value of N may be pre-configured or signaled from higher layers. Other representative embodiments are equally possible and are not limited by this example.
  • the location in the T-RPT resources of the RSL and/or the duration of the RSL may be predetermined, signaled and/or based on a signaled rule.
  • the subset of RSL T-RPT-2s may include and/or consist of the last subframe or set of subframes (e.g. corresponding to the duration of one T-RPT-2) of the scheduling period that is available for transmission.
  • the subset of RSL T-RPT-2s may include and/or consist of the first subframe or first set of subframes of the scheduling period that is available for transmission.
  • FIG. 4 illustrates another representative sidelink transmission 400.
  • the transmit WTRU 204a and the receive WTRU 204b may use different portions (e.g., scheduled, contention free portions) of the representative sidelink transmission 400 to transmit and/or receive sidelink information during sidelink communication.
  • the representative sidelink transmission 400 may include a control period 401 and/or a data period 402.
  • the data period 402 may follow (e.g., in time) the control period 401.
  • the control period 401 may include one or more S As 410.
  • the data period 402 may include a plurality of (T-RPTs) resources (e.g., resource blocks).
  • the T-RPTs may include a first type of T-RPT (e.g. T-RPT-1) and/or a second type of T-RPT (e.g., T-RPT-2).
  • the first type of T- RPT may be used for FSL communication from a transmit WTRU 204a to a receive WTRU 204b.
  • the second type of T-RPT may be used for RSL communication from a receive WTRU 204b to a transmit WTRU 204a.
  • the T-RPTs (e.g., the T-RPT-1 and the T-RPT-2) may include a plurality of intervals (e.g., subframes).
  • One or more of the intervals (e.g., subframes) in the TRPT-1 may include data 420 (e.g., FSL data and/or FSL control signaling).
  • One or more of the intervals (e.g., subframes) in the TRPT-2 may include data 430 (e.g., RSL data and/or RSL control signaling).
  • the subset of RSL T-RPTs may include or consist of the last T-RPT repetition within a scheduling period or a data transmission period 402.
  • the WTRU 204a or 204b may be configured with a minimum guard interval between FSL resources and RSL resources (e.g., a minimum of 1 subframe).
  • the guard interval may, for example, enable (e.g., be for the purpose of allowing) the WTRU 204a or 204b to change its RF transmit/receive hardware configuration.
  • the WTRU 204a or 204b may be configured to select, as the one or more guard intervals, a set of subframes that correspond to transitions from FSL to RSL resources, and vice versa, (as switching points) in a scheduling period (e.g., a data period 402).
  • the WTRU 204a or 204b may be configured to not transmit and/or not receive during these intervals.
  • the WTRU 204a and 204b when configured for D2D unicast operations, may determine the FSL/RSL switching points and may apply a guard interval at relevant switching points (e.g., each relevant switching point).
  • the WTRU 204a or 204b may be configured to insert a guard period after N T-RPT-ls and/or after N+M+1 T-RPTs.
  • the guard period may include and/or consist of a fixed number of subframes, of a fixed number of D2D subframes (D2D subframes may be subframes that are designated for use for D2D communications. D2D subframes may or may not be consecutive in time (e.g., the D2D subframes may be interleaved in time with subframes designated for other procedures, such as WAN cellular traffic).
  • the T-RPT- 1 and/or T-RPT2 as described herein may or may not correspond to consecutive subframes and may or may not occur over a contiguous time period).
  • the WTRU 204a or 204b may be configured to provide and/or insert guard subframes based on the set of T-RPTs selected for the FSL and the RSL.
  • the WTRU 204a or 204b may be configured to select T-RPTs for the FSLs and/or RSLs from a set of compatible T-RPTs.
  • Forward T-RPT-ls and return T-RPT-2s may be compatible if, and/or when used together. The forward and return T-RPTs result in the one or more guard intervals (e.g., at the two switching points).
  • Table 1 illustrates examples of compatible T-RPT family pairs, where a "1" indicates a D2D transmission subframe, a "0” indicates a subframe that is not used for D2D transmissions, and an "x" indicates that the subframe may be a 1 or a 0).
  • RSL resources may be derived from the T-RPT included in the S A.
  • resources used for the RSL may be implicitly derived from the FSL T-RPT included in the SA.
  • the RSL resources may be a subset of the subframes that are not available for FSL transmission according to the forward T-RPT-1 included in the SA.
  • the subset may include or consist of, for instance, one or more of the following: (1) subframes (e.g., all subframes) that are not available for transmission according to the forward T- RPT-1 ; (2) a first subframe and/or a last subframe that are not available for transmission within the forward T-RPT-1 ; and/or (3) every N-th subframe that is not available for transmission following M subframes that are available for transmission.
  • subframes e.g., all subframes
  • the WTRU 204a or 204b may also be configured to determine the set of subframes for the return T-RPT-2s taking into account guard intervals (e.g., which may be achieved by the WTRU 204a or 204b determining from the set of subframes that are not available for D2D transmission (e.g., according to the forward T-RPT-1 or based on any of the above considerations) and subframes that result in sufficient guard time (e.g., 1 subframe after the last subframe used for FSL transmission according to the forward T-RPT-1, and 1 subframe before (e.g., prior to) the first subframe used for FSL transmission according to the forward T-RPT-1).
  • guard intervals e.g., which may be achieved by the WTRU 204a or 204b determining from the set of subframes that are not available for D2D transmission (e.g., according to the forward T-RPT-1 or based on any of the above considerations) and subframes that result in
  • the resources used for the RSL may be defined by a second T-RPT resource implicitly associated to the first (forward) T-RPT resource included in the SA.
  • the second T-RPT resource may be generally referred to as a return T-RPT-2
  • the first T-RPT may be generally referred to as a forward T-RPT-1.
  • a unique return T-RPT-2 may be derived from a forward T-RPT-1, such that a receive WTRU 204b may determine the return T-RPT-2 from the forward T-RPT-1 based on (e.g., only based on) the mapping.
  • a forward T-RPT-1 may be associated with more than one return T-RPT-2.
  • the reacting WTRU 204b may select one of the return T-RPT-2s from among the set of return T-RPT-2s mapped to the forward T-RPT-1.
  • the selection may be random, or may be based on measurements.
  • the selection may be based on an explicit indication in the SA. For instance, a 1-bit field of the SA may indicate to the reacting WTRU 204b which of two possible return T-RPT-2s associated to the forward T-RPT-1 may be used.
  • the RSL resources may be explicitly indicated in the SA.
  • the SA may include a first field for the forward T-RPT-1 and a second field for the return T-RPT-2.
  • a predefined value may indicate that no T-RPT is provided, for example to indicate that one of the sidelinks (e.g., FSL and/or RSL) is not to be used.
  • the SA may include a single field indicating both a forward T-RPT-l and a return T-RPT-2, and/ or whether a return T-RPT-2 (or a forward T-RPT-1 ) is indicated.
  • a field may be referred to as a generalized T-RPT field.
  • Values of a generalized T-RPT field may indicate one or more of: (1) that a forward T-RPT-1 (e.g., only a forward T- RPT-1) is provided, (2) that a return T-RPT-2 (e.g., only a return T-RPT-2) is provided and/or (3) that both the forward T-RPT-1 and the return T-RPT-2 are provided.
  • An initiating WTRU 204a may send an SA with a return T-RPT-2 and with no forward T-RPT-1 , for example to obtain SCI such as CSI and/or to trigger transmission of a sounding reference signal by the reacting WTRU 204b.
  • the RSL resources may be selected by the reacting WTRU 204b and may be indicated in the SA.
  • the resources may include a T-RPT resource which may be selected from a subset of T-RPT resources that may result in a maximum allowable overlap with forward T-RPT resources.
  • the selected return T-RPT resource may have a 1 subframe overlap (e.g., at most 1 subframe overlap) with the forward T- RPT resource or resources per T-RPT repetition.
  • the return T-RPT resource may be signaled by the network (e.g., by a network entity, for example by an eNode-B 202).
  • the WTRU 204a may determine that such procedures may be used when data needs to be transmitted.
  • RSL resources may be used to transmit various types of information, as disclosed herein.
  • a WTRU 204b may transmit at least one type of SCI and/or reference signal over a RSL resource during a scheduling period, for example, if (e.g., and/or on condition that) an indication to provide the SCI and/or the reference signal is received in the corresponding SA.
  • an indication to provide SCI and/or the reference signal may be provided in the SA.
  • the inclusion of a return T-RPT resource in the SA e.g., in a generalized T-RPT field
  • At least one subframe, and/or all subframes of the return T-RPT resource may be utilized for the transmission of the SCI and/or the reference signal. Transmission timing of the SCI and/or the reference signal may depend on the type of SCI and/or reference as disclosed herein.
  • a WTRU 204b may use RSL resources to transmit data (e.g., higher layer data) when data is available for the corresponding scheduling period.
  • the WTRU 204b may transmit data over any combination of a FSL resource indicated in the SA transmitted by the WTRU 204a itself and a RSL resource indicated in the SA received from another WTRU 204b.
  • the RSL resource or resources selected for transmission of data may be determined based on one or more of the following: (1) the WTRU 204b may transmit data over a return T-RPT resource, if an identity associated with the S A that includes the return T-RPT resource matches, or is mapped to, an identity associated with the data to be transmitted. For instance, an identity may be associated with a pair of WTRUs 204a and 204b involved in unicast communication (e.g., bidirectional unicast communication). The identity may be used, as a destination ID, in SAs and may be associated with data pertaining to the unicast communication between the WTRUs 204a and 204b.
  • unicast communication e.g., bidirectional unicast communication
  • the WTRU 204b may transmit data over a return T- RPT resource if (e.g., only if) an explicit indication is provided (e.g., in the SA and/or via higher layer signaling) indicating that the return T-RPT resource may be used for to transmit data over the return T-RPT resource.
  • the WTRU 204b may transmit data over a forward T-RPT resource if no return T-RPT resource is available (e.g., according to pre-defined or signaled rules associated with a return T-RPT configuration. For example, if no return T-RPT resources are available based on at least one of the representative return T-RPT configurations, the data may be transmitted over a forward T-RPT- 1.
  • the WTRU 204b may transmit data over a forward T-RPT resource when a return T-RPT resource is insufficient to transmit the data, for example, according to QoS thresholds/requirements and/or other parameters (e.g., bandwidth thresholds/requirements, and/or call priority, among others) associated with the data.
  • the WTRU 204b may use the forward T-RPT resource (e.g., only the forward T-RPT resource) to transmit data, or may use both the return T-RPT resource and the forward T-RPT resource to transmit the data.
  • the WTRU 204b may multiplex at least one of the data, the SCI, and/or the reference signals into a single subframe of a return resource or a forward resource (e.g., aT-RPT resource).
  • the multiplexing may be performed to multiplex the data, the SCI, and/or the reference signals into the PUSCH.
  • Sounding Reference Signal (SRS), DM-RS, and SCI may be multiplexed into the PUSCH.
  • a WTRU 204b may transmit data (e.g., may only transmit data) in subframes where SCI is not transmitted.
  • the D2D WTRUs 204a and 204b may use non-time overlapping resources to communicate efficiently, for example to establish a connection (e.g., maintain communications) between the WTRUs 204a and 204b.
  • Representative procedures/apparatus to determine a set of resources to use for a direct unicast communication between WTRUs 204a and 204b are disclosed herein. It is contemplated that the procedures/apparatus may be applicable for any type of unicast communications, and for example, may be useful where one of the WTRUs 204a may be a relay WTRU (e.g., in-coverage) and the other WTRU 204b may be a remote WTRU (i.e., outside of network coverage).
  • the remote WTRUs 204b may be configured to select non-overlapping resources, to avoid unnecessary interference and reception errors.
  • the relay procedures disclosed herein may be used for WTRUs that are inside the network coverage area, that transition from inside the network coverage area to outside the network coverage area and/or that transition from outside the network coverage area to inside the network coverage.
  • the relay WTRU may provide a new anchor location for coverage.
  • the new anchor location for coverage may be selected based on one or more of: (1) a channel condition between the selected relay WTRU 204a of a group of WTRUs 204a capable of relay functionality (e.g., after evaluation of the channel conditions associated with one or more WTRUs 204a of the group; (2) an estimate of the location of the WTRU 204a and/or the WTRU 204b; and/or (3) an estimate of the velocity of the WTRU 204a and/or WTRU 204b (e.g., to anticipate future locations of the WTRUs 204a and 204b), among others.
  • a channel condition between the selected relay WTRU 204a of a group of WTRUs 204a capable of relay functionality e.g., after evaluation of the channel conditions associated with one or more WTRUs 204a of the group
  • an estimate of the location of the WTRU 204a and/or the WTRU 204b e.g., to anticipate future locations of the WTRUs
  • the relay WTRU 204a may control a part (e.g., some or all) of the resource allocation (e.g., with or without the support of pre-configuration (e.g., the information may be static and may be stored by the WTRU 204a) and/orthe eNode-B 202 (e.g., the eNode-B 202 may configure the WTRU 204a with the resource allocation).
  • the eNode-B 202 e.g., the eNode-B 202 may configure the WTRU 204a with the resource allocation.
  • the remote WTRU 204b may be configured to use a subset of allocated resources based on one or more parameters. In certain examples, the remote WTRU 204b may be configured to use a subset of the resources available to transmit to the relay WTRU 204a.
  • the remote WTRU 204b may be configured with a resource pool to transmit using mode 2 transmission.
  • the resource pool may be: (1) pre-configured (e.g., in the Universal Subscriber Identity Module (USIM) or via an application); (2) configured by the network (e.g., using anetwork entity, such as the eNode-B 202 via the relay WTRU 204a); and/or (3) configured by the relay WTRU 204a itself.
  • USIM Universal Subscriber Identity Module
  • the remote WTRU 204b may be configured to use a subset of the resources available in the resource pool for transmission.
  • the remote WTRU 204b may, for example, receive a configuration (e.g., via RRC signaling) from the relay WTRU 204a and/or from the network via the relay WTRU 204a.
  • the subset of resources available for transmission by the remote WTRU 204b may be determined using one or more of the example schemes disclosed herein. As understood by a person of skill in the art based on the teachings herein, embodiments are not limited by these example schemes, and other resource selection schemes may be used.
  • the remote WTRU 204b may be configured with a set of allowed T-RPTs that can be used for transmission.
  • the remote WTRU 204b may be configured with a subset of the T-RPTs defined by an SA.
  • the WTRU 204a or 204b may be configured with one or more allowed values of TRP to use for communication.
  • the WTRU 204a or 204b may also be configured with one or more values of kTRP to use in selecting the T-RPT(s).
  • the WTRU 204a or 204b may be configured with a T-RPT mask and a value of kTRP.
  • the T-RPT mask may indicate one or more positions in the T-RPT pattern that the WTRU 204a or 204b may be allowed to use for transmission.
  • the kTRP value may determine the total number of allowed T-RPTs that may be used in a T-RPT pattern.
  • the WTRU 204a or 204b may be allowed to use any of the following T-RPTs: (1,0,0,0,0,0,0,0), (0,1,0,0,0,0,0,0), (0,0,1,0,0,0,0,0), (0,0,0,1,0,0,0,0,0).
  • the WTRU 204a or 204b may be configured to use for transmission a subset (e.g., only a subset) of scheduling periods.
  • the WTRU 204a or 204b may be configured to use for transmission one (e.g., only one) out of every N scheduling periods.
  • the parameters to determine which scheduling period is allowed may be configured by the relay WTRU 204a or by the network via the relay WTRU 204a.
  • the WTRU 204a or 204b may be provided with an offset and a periodicity parameter which may be used to determine the set of scheduling periods allowed for transmission.
  • the frame number (e.g., direct frame number) may be used as a reference point from which the offset may be applied.
  • the WTRU 204a or 204b may be configured with a repeating scheduling period pattern (e.g., a series of Is and 0s) indicating which scheduling period may be used for transmission (e.g., which may also use the frame number (e.g., direct frame number), as a reference point.
  • the WTRU 204a or 204b may be configured to use a subset (e.g., only a subset) of the allowed frequency resources from a configured pool.
  • the remote WTRU 204b may be configured by the relay WTRU 204a or by the network (e.g., via the eNode-B 202) via the relay WTRU 204a to use a range of (e.g., only a range of) Physical Resource Blocks (PRBs) from a configured resource pool.
  • PRBs Physical Resource Blocks
  • the remote WTRU 204b may be configured to only use (e.g., only use) a set of specific resources from the configured resource pool.
  • the remote WTRU 204b may be configured to select a starting PRB index and a number of PRBs from a configured list of allowed values.
  • the values of the starting PRB index and/or the number of PRB represent a subset of the allowed values according to the configured pool.
  • the WTRU 204a or 204b may be configured with a specific frequency hopping parameter, which may be used for example to orthogonalize resources in frequency.
  • the specific frequency hopping parameter may be configured by the relay WTRU 204a or by the network via the relay WTRU 204a.
  • the relay WTRU 204a may be configured to determine the parameters (e.g., used by the remote WTRU 204b to determine its transmission resources) and to configure, for example the remote WTRU 204b and/or the WTRU 204a itself with an appropriate configuration. For example, the relay WTRU 204a may configure the remote WTRU 204b upon connection and/or at any point after unicast communication has been initiated. In certain examples, the relay WTRU 204a may be configured to provide communication resource information immediately after being contacted by the remote WTRU 204b for service (e.g., as part of a discovery Model B "response" message). The relay WTRU 204a may use the "PC5" signaling interface to transmit the configuration to the remote WTRU 204b.
  • the relay WTRU 204a may use the "PC5" signaling interface to transmit the configuration to the remote WTRU 204b.
  • the relay WTRU 204a may be configured to indicate the resources for remote WTRU 204b transmission in the SA used for the relay WTRU data transmission (e.g., one scheduling period before the remote WTRU 204b may transmit data).
  • the remote WTRU 204b may be configured to use a set of resources that are related to the resources used by the associated relay WTRU 204a.
  • the relation between the resources used for transmission by the relay WTRU 204a to the remote WTRU 204b and the resources used by the remote WTRU 204b for transmission to the relay WTRU 204a may be predefined (e.g., static or semi-static) and/or may be configured via one or more parameters (e.g., chosen by the relay WTRU 204a, or by the network (e.g., via the eNode-B 202)) via the relay WTRU 204a.
  • the remote WTRU 204b may be configured to use the same resources as those used by the relay WTRU 204a to communicate to the remote WTRU 204b (e.g., based on the last set of resources used and/or based on a rule associated with previous resources used by the relay WTRU 204a), for example, during a subsequent scheduling period.
  • the remote WTRU 204b may be configured to use a set of resources determined by the set of resources used by the relay WTRU 204a (to communicate to the remote WTRU 204b) based on one or more offset parameters.
  • the relay WTRU 204a may be configured to use resources for transmission that start at the same PRB index as used for the previous relay WTRU transmission, which may be offset by a configured value (e.g., offset by 2 PRBs).
  • the offset values may be configured by the relay WTRU 204a and/or by the network, or may be implicitly based on the WTRU identities, for example. It is contemplated that the same or a similar procedure may be applied to other transmission parameters such as the T-RPT offset, for example, to determine resources for use by the remote WTRU 204b.
  • Example embodiments of D2D unicast communications are provided for the purpose of illustration only. These example embodiments may use a combination of various procedures disclosed herein. As understood by a person of skill in the art based on the teachings herein, embodiments are not limited by the examples provided herein.
  • the D2D WTRUs 204a and 204b may be configured (e.g., initially configured and/or preconfigured) to apply throughput-based link adaptation.
  • the link adaptation process/procedure may be initialized by a transmit WTRU 204a by transmitting a request to a receive WTRU 204b, for example indicated by an invalid yet pre-determined Release 8 UL type-0 resource allocation in an SA.
  • the receive WTRU 204b decodes (e.g., successfully decodes) the SA, the receive WTRU 204b may respond, for example with another invalid yet pre-determined Release 8 UL type-0 resource allocation in the SA.
  • WTRU 204a and/or WTRU 204b may use a listen- before-talk procedures/mechanism for resource selection for the FSLs and the RSLs.
  • the transmit WTRU 204a may specify (e.g., determine) the resources for the RSL during the initialization procedure/process.
  • the transmit WTRU 204a may acquire the link adaption status report and data from the receive WTRU 24b (e.g., without decoding any associated SAs). This may be equivalent to reserving the resources for the two WTRUs 204a and 204b during the link adaptation procedure/process.
  • FIG. 4 illustrates a further representative sidelink transmission 400.
  • the transmit WTRU 204a and the receive WTRU 204b may use different portions (e.g., scheduled, contention free portions) of the representative sidelink transmission 500 to transmit and/or receive sidelink information during sidelink communication.
  • the representative sidelink transmission 500 may include a control period 501 and/or a data period 502.
  • the data period 502 may follow (e.g., in time) the control period 501.
  • the control period 501 may include one or more SAs 510.
  • the data period 502 may include a plurality of (T-RPTs) resources (e.g., resource blocks).
  • the T-RPTs may include a first type of T-RPT (e.g. T-RPT-1) and/or a second type of T-RPT (e.g., T-RPT-2).
  • the first type of T- RPT (T-RPT-1) may be used for FSL communication from a transmit WTRU 204a to a receive WTRU 204b.
  • the second type of T-RPT (T-RPT-2) may be used for RSL communication from a receive WTRU 204b to a transmit WTRU 204a.
  • the T-RPTs (e. g. , the T-RPT- 1 and the T-RPT-2) may include a plurality of intervals (e.g., subframes).
  • One or more of the intervals (e.g., subframes) in the TRPT-1 may include data 520 (e.g., FSL data and/or FSL control signaling).
  • One or more of the intervals (e.g., subframes) in the TRPT-2 may include data 530 (e.g., RSL data and/or RSL control signaling).
  • the RSL resources may be fixed relative to the FSL resources (e.g., occurring at a fixed time and/or at a frequency offset from the FSL resources).
  • the RSL resources occur (e.g., happen) at regular intervals (e.g., short intervals that may have a similar interval as the T-RPT interval) within the data transmission period 502 and may occur between FSL resources.
  • the configuration and timing of the RSL resources may be predictable to the transmit WTRU 204a (and/or the receive WTRU 204b). For example, particular RSL resources may be offset from FSL resources.
  • the receive WTRU 204b may be configured as the measuring WTRU reporting reception performance (e.g., via a link adaptation report) to the transmit WTRU 204a.
  • the transmit WTRU 204a may be configured as the actuating WTRU adjusting link adaptation parameters, for example by varying the modulation order based on the received link adaptation report.
  • the transmit WTRU 204a may transmit a request (e.g., a stop request or LINK AD AP STOP REQ request) to the receive WTRU 204b.
  • the request may be indicated by an invalid yet pre-determined Release 8 UL type-0 resource allocation in the SA.
  • the receive WTRU 204b may respond with a response message (e.g., an acknowledgment message or LINK ADAP STOP ACK message) using, for example, another invalid yet pre-determined Release 8 UL type-0 resource allocation in the SA.
  • the receive WTRU 204b may: (1) stop monitoring reception performance; (2) cease sending link adaptation reports back to the transmit WTRU 204a; and/or (3) switch back, along with the transmit WTRU 204a, to a listen-before-talk mode/procedure/mechanism for resource selection.
  • the D2D WTRUs 204a and 204b may be configured (e.g., subsequently be configured) to apply reliability-based link adaptation to meet a certain pre-defined link quality threshold.
  • the link adaptation procedure/process may be initialized and/or re-configured using control signaling (e.g., RRC signaling) with additional information such as specific transmission parameters and/or a granted subscription period.
  • the WTRU 204a or 204b may be configured to set a timer to begin link adaptation according to the granted subscription period.
  • the transmission parameters may include, for example, any of: (1) resources and/or resource pools, for example reserved (e.g., exclusively reserved) for public safety uses.
  • the resources assigned may be dedicated for the two or more WTRUs 204a and/or 204b throughout the subscription period, to guarantee a certain level of transmission reliability.
  • the two or more WTRUs 204a and/or 204b may be configured to switch back to a commercial mode, resulting in the resources (e.g., exclusive resources) being released.
  • the two or more WTRUs 204a and/or 204b may be configured to use resources pools reserved for commercial uses (e.g., only commercial uses (e.g., which may be indicated via RRC signaling)).
  • FIG. 6 is a flowchart illustrating a representative sidelink configuration method 600.
  • the representative sidelink configuration method 600 may include, at block 610, a first WTRU 204b which receives information indicating RSL resources associated with RS D2D communication between the first WTRU 204b and a second WTRU 204a.
  • the first WTRU 204b may determine the RSL resources based on the received information.
  • the first WTRU 204b may transmit to the second WTRU 204a sidelink information using the determined RSL resources.
  • the first WTRU 204b may receive via the second WTRU 204a, a scheduling assignment (SA) 310, 410 or 510 that may include the information indicating the RSL resources.
  • SA scheduling assignment
  • the SA 310, 410 or 510 may define one or more T- RPT resources such that a subset of the T-RPT resources, as the RSL resources, may be used by the first WTRU 204b to transmit the sidelink information (e.g., RSL information) to the second WTRU 204a.
  • the sidelink information e.g., RSL information
  • the first WTRU 204b may determine one or more T-RPT resources associated with a FSL for a FSL D2D communication and one or more other T- RPT resources based on the determined one or more T-RPT resources associated with the FSL for the RSL D2D communication.
  • the one or more T-RPT resources defined by the SA 310, 410 or 510 may be associated with a sidelink communication period 302, 402 or 502.
  • a subset of the one or more T-RPT resources may be indicated in the SA 310, 410 or 510.
  • the RSL resources used to transmit the sidelink information by the first WTRU 204b to the second WTRU 204a may include any of: (1) one or more of the T-RPT resources explicitly assigned in the S A 310, 420, or 510 by the second WTRU 204a for the RSL D2D communication; (2) one or more of the T-RPT resources implicitly assigned using the SA 310, 410 or 510 by the second WTRU 204a for the RSL D2D communication; (3) one or more of the T-RPT resources that are not available for transmission according to the SA 310, 410 or 510; (4) a last T-RPT resource within a sidelink communication period 302, 402, or 502; or (5) periodically occurring T-RPT resources within the sidelink communication period 302, 402, or 502.
  • the periodically occurring T-RPT resources associated with the RSL may be interleaved with T-RPT resources associated with the FSL within the sidelink communication period 302, 402, or 502.
  • the information indicating the RSL resources may include a plurality of bits indicating resource blocks associated with the RSL D2D communication.
  • the first WTRU 204b may receive a radio resource control (RRC) message (e.g., from a network entity, for example eNode-B 202 or another reference device) that may include the information indicating the RSL resources for the RSL D2D communication between the first WTRU 204b and the second WTRU 204a.
  • RRC radio resource control
  • the information indicating the RSL resources may be implicitly indicated based on any of a format of the SA 310, 410 or 510 and/or a content of the SA 310, 410 or 510.
  • the first WTRU 204b may determine a sidelink mask from the received information of the SA 310, 410 or 510 and/ or may apply the sidelink mask to the one or more T-RPT resources within a sidelink communication period 302, 402 or 502 to determine the RSL resources and FSL resources for D2D unicast communication.
  • the sidelink information may include any of: (1) sidelink data; (2) sidelink control information (SCI); (4) one or more reference signals; or (5) multiplexed sidelink data and control information.
  • the first WTRU 204b may set a link parameter; may perform a measurement on a RSL D2D communication received from the second WTRU 204a; may estimate a value of the set link parameter based on the measurement; and/or may report the estimated value of the link parameter.
  • the link parameter may be one of : ( 1 ) a modulation and coding scheme index; and/or (2) a transport block size.
  • the measurement may be any of : ( 1 ) a measurement of an average number of transmissions or retransmissions of the FSL D2D communication received from the second WTRU 204a; (2) a measurement of block error rate (BLER) associated with the FSL D2D communication received from the second WTRU 204a; (3) a measurement of a number of successful packets of the FSL D2D communication received from the second WTRU
  • FIG. 7 is a flowchart illustrating a representative link adaptation method 700.
  • the representative sidelink configuration method 700 may include, at block 710, a first WTRU 204a triggering a D2D link adaptation procedure.
  • the first WTRU 204a triggering a D2D link adaptation procedure.
  • the WTRU 204b may generate link adaptation information after triggering the D2D link adaptation procedure.
  • the first WTRU 204a may send the link adaptation information to a second WTRU 204b to configure a RSL between the first WTRU 204a and the second WTRU
  • the first WTRU 204a may initiate the D2D link adaptation procedure responsive to reception of an indication from any of: (1) an eNode-B 202; (2) a network entity, (3) a reference source; or (4) a further WTRU 204a or 204b.
  • the indication may include a scheduling assignment (SA) with a modulation and coding scheme (MCS) index exceeding a threshold.
  • SA scheduling assignment
  • MCS modulation and coding scheme
  • the first WTRU 204a may start the D2D link adaptation procedure based on an internal indication from within the first WTRU 204a.
  • the internal indication may be based on any of: (1) a presence of Wide Area Network (WAN) traffic; (2) a signal quality of a received scheduling assignment (SA); (3) a signal quality of a previous data communication; (4) a signal quality of a previous sidelink communication (5) a signal quality of a discovery message; (6) a number of erroneously decoded packets in a given period of time; (7) a configuration of any of: the first WTRU or the second WTRU in a public safety mode; or (8) a transmit buffer status, among others.
  • WAN Wide Area Network
  • SA received scheduling assignment
  • the first WTRU 204a may direct the second WTRU 204b to perform measurements associated with at least the RSL, receive measurement information associated with the performed measurements, and trigger of the D2D link adaptation procedure based on the received measurement information.
  • the first WTRU 204a may perform a direct measurement on a received signal such that the D2D link adaptation procedure may be triggered based on the direct measurement performed by the first WTRU 204a.
  • the first WTRU 204a may configure the FSL and the RSL and may send the link adaptation information using any of: (1) the SA 310, 410 or 510; (2) the FSL and/or (3) the RSL.
  • the first WTRU 204a may select a format of the S A 310, 410 or 510 in accordance with the link adaptation information and may send the S A 310, 410 or 510 having the selected format.
  • the first WTRU 204a may transmit an invalid resource allocation in the SA 310, 410 or 510 (e.g., to indicate the link adaption information).
  • the first WTRU 204a may send the link adaptation information (e.g., or its indication) on a data channel.
  • the data channel may include a Physical Sidelink Shared Channel (PSSCH).
  • PSSCH Physical Sidelink Shared Channel
  • the first WTRU 204a may send the link adaption information using a predefined or signaled set of resources of the data channel.
  • the first WTRU 204a may send the link adaptation information in the SA 310, 410 or 510 such that FSL information and/or RSL information are communicated following the SA 310, 410 or 510.
  • the first WTRU 204a may send the link adaptation information to any of: (1) an eNode-B 202, (2) a network entity, and/or (3) a reference source, among others.
  • the first WTRU 204a may send the link adaptation information directly to the second WTRU 204b.
  • FIG. 8 is a flowchart illustrating a representative configuration method 800 involving a relay WTRU 204a.
  • the representative configuration method 800 may include, at block 810, a first WTRU 204b determining a set of resources for RSL D2D communication from the first WTRU 204b to a relay WTRU 204a.
  • the first WTRU 204b may transmit data to the relay WTRU 204a using the set of determined resources for RSL D2D communication.
  • the first WTRU 204b may receive a configuration of the set of resources (e.g., from any of: (1) the relay WTRU 204a, (2) a network entity, or (3) an evolved Node B 202).
  • the first WTRU 204b may receive one or more parameters and may determine the set of resources using the one or more received parameters. [0237] In certain representative embodiments, the first WTRU 204b may select the set of resources from a predetermined resource pool.
  • the first WTRU 204b may determine a set of allowed T-RPT resources using a T-RPT mask.
  • the first WTRU 204b may determine the set of resources for a return channel used by the first WTRU 204b to transmit to the relay WTRU 204a based on resources for a forward channel used by the first WTRU 204b to receive from the relay WTRU 204a.
  • the determined set of resources for the return channel used by the relay WTRU 204a to receive from the first WTRU 204b may be related by an offset to one or more of the resources for the forward channel used by the relay WTRU 204a to transmit to the first WTRU 204b.
  • the first WTRU 204b may set a link parameter, may perform a measurement on a D2D communication received from the relay WTRU 204a, may estimate a value of the set link parameter based on the measurement, and may report to the relay WTRU 204a the estimated value of the link parameter.
  • the link parameter may be one of: (1) a modulation and coding scheme index; or (2) a transport block size, among others.
  • the measurement may be any of: (1 ) a measurement of an average number of transmissions or retransmissions of the D2D communication received from the relay WTRU 204a; (2) a measurement of block error rate (BLER) associated with the D2D communication received from the relay WTRU 204a; (3) a measurement of a number of successful packets of the D2D communication received from the relay WTRU 204a (e.g., in a given period, for example and/or compared to a threshold established based on the expected number of successful packets received in the given period); and/or (4) a measurement of a number of received SAs 310, 410 or 510 (e.g., in a given period, for example and/or compared to a threshold established based on the expected number of received SAs 310, 410 or 510 in the given period), among others.
  • BLER block error rate
  • FIG. 9 is a flowchart illustrating another representative sidelink configuration method 900.
  • the representative configuration method 900 may include, at block 910, a first WTRU 204a generating information indicating RSL resources associated with RSL D2D communication between the first WTRU 204a and a second WTRU 204b; [0246] At block 920, the first WTRU 204a may send to the second WTRU 204b the information indicating the RSL resources. At block 930, the first WTRU 204a may receive and decode sidelink information using the RSL resources indicated in the sent information.
  • the first WTRU 204a may send a SA 310, 410 or 510 to the second WTRU 204b that may include the information indicating the RSL resources.
  • the SA 310, 410 or 510 may define one or more T- RPT resources.
  • the first WTRU 204a may determine a subset of the T-RPT resources, as the RSL resources, used by the first WTRU 204a to receive the sidelink information from the second WTRU 204b.
  • the first WTRU 204a may determine one or more T-RPT resources associated with a FSL for FSL D2D communication and one or more other T- RPT resources based on the determined one or more T-RPT resources associated with the FSL for the RSL D2D communication.
  • the one or more T-RPT resources defined by the SA 310, 410 or 510 may be associated with a sidelink communication period 302, 402 or 502.
  • the subset of the one or more T-RPT resources may be indicated in the SA 310, 410 or 510.
  • the RSL resources used to receive the sidelink information by the first WTRU 204a from the second WTRU 204b may include any of: (1) one or more of the T-RPT resources explicitly assigned in the SA 310, 410 or 510 by the first WTRU 204a for the RSL D2D communication; (2) one or more of the T-RPT resources implicitly assigned using the S A 310, 410 or 510 by the first WTRU 204a for the RSL D2D communication; (3) one or more of the T-RPT resources that are not available for transmission according to the S A 310, 410 or 510; (4) a last T-RPT resource within a sidelink communication period 302, 402 or 502; and/or (5) periodically occurring T-RPT resources within the sidelink communication period 302, 402 or 502, among others.
  • the periodically occurring T-RPT resources associated with the RSL may be interleaved with (and/or offset from) T-RPT resources associated with a FSL, for example, within the sidelink communication period 302, 402 or 502.
  • the information indicating the RSL resources may include a plurality of bits indicating resource blocks associated with the RSL D2D communication.
  • the first WTRU 204a may forward a radio resource control (RRC) message that may include the information indicating the RSL resources for the RSL communication between the first WTRU 204a and second WTRU 204b.
  • RRC radio resource control
  • the information indicating the RSL resources may be implicitly indicated based on any of a format of a SA 310, 410 or 510 or a content of the SA 310, 410 or 510.
  • the first WTRU 204a may determine a sidelink mask and may apply the sidelink mask to the one or more T-RPT resources within a sidelink communication period 302, 402 or 502 to determine the RSL resources and the FSL resources for D2D unicast communication.
  • the sidelink information may include any of: (1) sidelink data; (2) sidelink control information (SCI); (4) one or more reference signals; and/or (5) multiplexed sidelink data and control information, among others.
  • FIG. 10 is a flowchart illustrating another representative link adaptation method 1000.
  • the representative link adaptation method 1000 may include, at block 1010, a first WTRU 204b receiving link adaptation information to configure a RSL between the first WTRU 204b and a second WTRU 204a.
  • the first WTRU 204b may trigger a D2D link adaptation procedure in response to reception of the link adaptation information.
  • the first WTRU 204b may encode and may send sidelink information using the link adaptation information.
  • the first WTRU 204b may initiate the D2D link adaptation procedure responsive to reception of the link adaptation information from any of: (1) the second WTRU 204a; (2) an eNode-B 202; (3) a network entity, (4) a reference source; and/or (5) a further WTRU, among others.
  • the first WTRU 204b may start the D2D link adaptation procedure based on an internal indication from within the first WTRU 204b.
  • the internal indication may be based on any of: (1) a presence of Wide Area Network (WAN) traffic; (2) a signal quality of a received SA 310, 410 or 510; (3) a signal quality of a previous data communication; (4) a signal quality of a previous sidelink communication (5) a signal quality of a discovery message; (6) a number of erroneously decoded packets in a given period of time; (7) a configuration of any of: the first WTRU 204b or the second WTRU 204a in a public safety mode; and/or (8) a transmit buffer status, among others.
  • the first WTRU 204b may perform a measurement on a received signal associated with at least the RSL and may send measurement information associated with the performed measurement.
  • the first WTRU 204b may configure the FSL and the RSL and may receive the link adaptation information using any of: (1) a SA 310, 410 or 510; (2) the FSL and/or (3) the RSL, among others.
  • the first WTRU 204b may determine a format of the S A 310, 410 or 510 such that the D2D link adaptation procedure may be triggered on condition that the determined format matches one or more reference SA formats.
  • the first WTRU 204b may receive an invalid resource allocation in the SA 310, 410 or 510.
  • the first WTRU 204b may receive the link adaptation information on a data channel.
  • the data channel may include a Physical Sidelink Shared Channel (PSSCH).
  • PSSCH Physical Sidelink Shared Channel
  • the first WTRU 204b may receive the link adaption information using a predefined or signaled set of resources of the data channel.
  • the first WTRU 204b may receive the link adaptation information from any of: (1) an eNode-B 202, (2) a network entity, and/or (3) a reference source, among others.
  • the first WTRU 204b may receive the link adaptation information directly from the second WTRU 304a.
  • the first WTRU 204b may set a link parameter, may perform a measurement on a D2D communication received from the second WTRU 204a; may estimate a value of the set link parameter based on the measurement; and may reporting the estimated value of the link parameter.
  • the link parameter may include one of: (1) a modulation and coding scheme index; and/or (2) a transport block size, among others.
  • the measurement may include any of: (1) a measurement of an average number of transmissions or retransmissions of a FSL D2D communication received from the second WTRU 204a; (2) a measurement of block error rate (BLER) associated with the FSL D2D communication received from the second WTRU 204a; (3) a measurement of a number of successful packets of the FSL D2D communication received from the second WTRU 204a; or (4) a measurement of a number of received SAs 310, 410 or 510.
  • BLER block error rate
  • FIG. 11 is a flowchart illustrating another representative sidelink configuration method 1100 involving a relay WTRU 204a.
  • the representative configuration method 1100 may include, at block 1110, a first WTRU 204b determining a set of resources for RSL D2D communication from a first WTRU 204b to the relay WTRU 204b.
  • the WTRU 204b may receive data, by the relay WTRU 204a from the first WTRU 204b, using the determined set of resources for the RSL D2D communication.
  • the first WTRU 204b may send a configuration of the set of resources.
  • the first WTRU 204b may send the configuration of the set of resources from the relay WTRU 204a.
  • the first WTRU 204b may determine the set of resources using one or more parameters.
  • the first WTRU 204b may select the set of resources from a predetermined resource pool.
  • the first WTRU 204b may determine a set of allowed T-RPT resources using a T-RPT mask.
  • the first WTRU 204b may determine the set of resources for a return channel used by the relay WTRU 204a to receive from the first WTRU 204b based on resources for a forward channel used by the relay WTRU 204a to transmit to the first WTRU 204b.
  • the determined set of resources for the return channel used by the relay WTRU 204a to receive from the first WTRU 204b may be related by an offset to one or more of the resources for the forward channel used by the relay WTRU 204a to transmit to the first WTRU 204b.
  • 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 UE, WTRU, terminal, base station, RNC, or any host computer.
  • processing platforms, computing systems, controllers, and other devices including the constraint server and the rendezvous point/server containing processors are noted. These devices may contain at least one Central Processing Unit (“CPU”) and memory.
  • CPU Central Processing Unit
  • FIG. 1 A block diagram illustrating an exemplary computing system
  • FIG. 1 A block diagram illustrating an exemplary computing system
  • FIG. 1 A block diagram illustrating an exemplary computing system
  • FIG. 1 A block diagram illustrating an exemplary computing systems, controllers, and other devices including the constraint server and the rendezvous point/server containing processors.
  • CPU Central Processing Unit
  • an electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals.
  • the memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the exemplary embodiments are not limited to the above- mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.
  • the data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (“RAM”)) or nonvolatile (e.g., Read-Only Memory (“ROM”)) mass storage system readable by the CPU.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • the computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It is understood that the representative embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the described methods.
  • any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium.
  • the computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.
  • Suitable processors include, by way of example, 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), Application Specific Standard Products (ASSPs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • ASSPs Application Specific Standard Products
  • FPGAs Field Programmable Gate Arrays
  • the terms "user equipment” and its abbreviation "UE” may mean (i) a wireless transmit and/or receive unit (WTRU), such as described infra; (ii) any of a number of embodiments of a WTRU, such as described infra; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU, such as described infra; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU, such as described infra; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein.
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • DSPs digital signal processors
  • a signal bearing medium examples include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc.
  • a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • any two components so associated may also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being “operably couplable” to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
  • the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
  • the terms “any of followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include “any of,” “any combination of,” “any multiple of,” and/or “any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items.
  • the term “set” or “group” is intended to include any number of items, including zero.
  • the term “number” is intended to include any number, including zero.
  • a range includes each individual member.
  • a group having 1-3 cells refers to groups having 1, 2, or 3 cells.
  • a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, Mobility Management Entity (MME) or Evolved Packet Core (EPC), or any host computer.
  • WTRU wireless transmit receive unit
  • UE user equipment
  • MME Mobility Management Entity
  • EPC Evolved Packet Core
  • the WTRU may be used in conjunction with modules, implemented in hardware and/or software including a Software Defined Radio (SDR), and other components such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a Near Field Communication (NFC) Module, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any Wireless Local Area Network (WLAN) or Ultra Wide Band (UWB) module.
  • SDR Software Defined Radio
  • other components such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard
  • a method performed by a first WTRU comprises: receiving, by the first WTRU, information indicating Return Sidelink (RSL) resources associated with RSL D2D communication between the first WTRU and a second WTRU; determining, by the first WTRU, the RSL resources based on the received information; and transmitting, by the first WTRU to the second WTRU, sidelink information using the determined RSL resources.
  • RSL Return Sidelink
  • a method performed by a first WTRU comprises: triggering a D2D link adaptation procedure; generating link adaptation information after triggering the D2D link adaptation procedure; and sending the link adaptation information to a second WTRU to configure a return sidelink (RSL) between the first WTRU and the second WTRU.
  • RSL return sidelink
  • a method performed by a first WTRU comprises: determining a set of resources for RSL D2D communication from the first WTRU to a relay WTRU; and transmitting data to the relay WTRU using the set of resources for RSL D2D communication.
  • a method performed by a first WTRU comprises: generating, by first WTRU, information indicating Return Sidelink (RSL) resources associated with RSL D2D communication between the first WTRU and a second WTRU; sending, by the first WTRU to a second WTRU, the information indicating the RSL resources; and receiving and decoding, by the first WTRU, sidelink information using the RSL resources indicated in the sent information.
  • RSL Return Sidelink
  • a method performed by a first WTRU comprises: receiving, by the first WTRU, link adaptation information to configure a return sidelink (RSL) between the first WTRU and a second WTRU; triggering a D2D link adaptation procedure in response to reception of the link adaptation information; and encoding and sending, by the first WTRU, sidelink information using the link adaptation information.
  • RSL return sidelink
  • a method performed by a relay comprises: determining a set of resources for RSL D2D communication from a first WTRU to the relay WTRU; and receiving data, by the relay WTRU from the first WTRU, using the determined set of resources for the RSL D2D communication.
  • a WTRU comprises: a transmit/receive unit configured to receive information indicating Return Sidelink (RSL) resources associated with RSL D2D communication between the WTRU and a second WTRU; and a processor configured to determine the RSL resources based on the received information, wherein the transmit/receive unit is configured to transmit to the second WTRU sidelink information using the determined RSL resources.
  • RSL Return Sidelink
  • a WTRU comprises: a processor configured to trigger a D2D link adaptation procedure and generate link adaptation information on condition that the D2D link adaptation procedure is triggered; and atransmit/receive unit configured to send the link adaptation information to a second WTRU to configure a return sidelink (RSL) between the WTRU and the second WTRU.
  • a processor configured to trigger a D2D link adaptation procedure and generate link adaptation information on condition that the D2D link adaptation procedure is triggered
  • atransmit/receive unit configured to send the link adaptation information to a second WTRU to configure a return sidelink (RSL) between the WTRU and the second WTRU.
  • RSS return sidelink
  • a WTRU comprises: a processor configured to determine a set of resources for D2D communication from the WTRU to a relay WTRU; and a transmit/receive unit configured to transmit data to the relay WTRU using the set of resources for D2D communication.
  • a WTRU comprises: a processor configured to generate information indicating Return Sidelink (RSL) resources associated with RSL D2D communication between the first WTRU and a second WTRU; and a transmit/receive unit configured to send to a second WTRU information indicating the RSL resources, and receive sidelink information using the RSL resources indicated in the sent information, wherein the processor is configured to decode the sidelink information using the RSL resources indicated in the sent information.
  • RSL Return Sidelink
  • a WTRU comprises: a transmit/receive unit configured to receive link adaptation information to configure a return sidelink (RSL) between the WTRU and a second WTRU; and a processor is configured to trigger a D2D link adaptation procedure in response to reception of the link adaptation information, and encode sidelink information using the link adaptation information,
  • RSL return sidelink
  • the transmit/receive unit is configured to send the encoded sidelink information to the second WTRU.
  • arelay WTRU comprises: a processor configured to determine a set of resources for D2D communication from a first WTRU to the relay WTRU; and a transmit/receive unit configured to receive data from the first WTRU using the determined set of resources for RSL D2D communication.
  • the first or second WTRU may be a relay WTRU.
  • the receiving of the information indicating the RSL resources may include receiving, via the second WTRU, a scheduling assignment (SA) that includes the information indicating the RSL resources.
  • SA scheduling assignment
  • the SA may define one or more Time Resource Pattern of Transmission (T-RPT) resources such that the determining of the RSL resources based on the received information may include determining a subset of the T-RPT resources, as the RSL resources, used by the first WTRU to transmit the sidelink information to the second WTRU.
  • T-RPT Time Resource Pattern of Transmission
  • the determining of the subset of the T-RPT resources may include determining one or more T-RPT resources associated with a forward sidelink (FSL) for FSL D2D communication and one or more other T-RPT resources based on the determined one or more T-RPT resources associated with the FSL for the RSL D2D communication.
  • FSL forward sidelink
  • the determining of the subset of the T-RPT resources may include determining one or more T-RPT resources associated with the RSL sidelink for the RSL D2D communication using any of: (1) an index value associated with an index of lookup table or associated with one or more predetermined or signaled rules; (2) forward sidelink (FSL) or RSL T-RPT resource information and a fixed relationship between one or more T-RPT resources associated with the RSL sidelink for the RSL D2D communication and one or more T-RPT resources associated with (FSL) for FSL D2D communication; (3) FSL resource information associated with the lookup table or associated with the one or more predetermined rules or signaled rules.
  • the receiving of the information indicating the RSL resources may include receiving an index corresponding to a resource pattern for sidelink D2D communication; and the determining of the RSL resources based on the received information may include determining using the received index, which resources in a sidelink communication period are RSL resources and which of the resources in the sidelink communication period are forward sidelink (FSL) resources.
  • FSL forward sidelink
  • the one or more T-RPT resources defined by the SA may be associated with a sidelink communication period.
  • a subset of the one or more T-RPT resources may be indicated in the SA.
  • the RSL resources used to transmit the sidelink information by the first WTRU to the second WTRU may include any of: (1) one or more of the T-RPT resources explicitly assigned in the S A by the second WTRU for the RSL D2D communication; (2) one or more of the T-RPT resources implicitly assigned using the SA by the second WTRU for the RSL D2D communication; (3) one or more of the T-RPT resources that are not available for transmission according to the SA; (4) a last T-RPT resource within a sidelink communication period; or (5) periodically occurring T-RPT resources within the sidelink communication period.
  • the periodically occurring T-RPT resources associated with the RSL may be interleaved with T-RPT resources associated with a forward sidelink (FSL) within the sidelink communication period.
  • FSL forward sidelink
  • the information indicating the RSL resources may include a plurality of bits indicating resource blocks associated with the RSL D2D communication.
  • the receiving of the information indicating the RSL resources may include receiving a radio resource control (RRC) message that includes the information indicating the RSL resources for the RSL D2D communication between the first and second WTRUs.
  • RRC radio resource control
  • the information indicating the RSL resources may be implicitly indicated based on any of a format of a scheduling assignment (SA) and/or a content of the SA.
  • SA scheduling assignment
  • the determining of the RSL resources based on the received information may include: determining a sidelink mask from the received information of the SA; and applying the sidelink mask to the one or more T-RPT resources within a sidelink communication period to determine the RSL resources and forward sidelink resources for D2D unicast communication.
  • the sidelink information may include any of: (1) sidelink data; (2) sidelink control information (SCI); (3) one or more reference signals; or (4) multiplexed sidelink data and control information.
  • the method may further comprise: setting a link parameter; performing a measurement on a RSL D2D communication received from the second WTRU; estimating a value of the set link parameter based on the measurement; and reporting the estimated value of the link parameter.
  • the link parameter may be one of: (1) a modulation and coding scheme index; or (2) a transport block size; and the measurement may be any of: (1) a measurement of an average number of transmissions or retransmissions of the FSL D2D communication received from the second WTRU; (2) a measurement of block error rate (BLER) associated with the FSL D2D communication received from the second WTRU; (3) a measurement of a number of successful packets of the FSL D2D communication received from the second WTRU; or (4) a measurement of a number of received SAs.
  • BLER block error rate
  • the triggering of the D2D link adaptation procedure may include initiating the D2D link adaptation procedure responsive to reception of an indication from any of: (1) an eNode-B; (2) a network entity, (3) a reference source; or (3) a further WTRU.
  • the indication may include a scheduling assignment (SA) with a modulation and coding scheme (MCS) index exceeding a threshold.
  • SA scheduling assignment
  • MCS modulation and coding scheme
  • the triggering of the D2D link adaptation procedure may include starting the D2D link adaptation procedure based on an internal indication from within the first WTRU.
  • the internal indication may be based on any of: (1) a presence of Wide Area Network (WAN) traffic; (2) a signal quality of a received scheduling assignment (SA); (3) a signal quality of a previous data communication; (4) a signal quality of a previous sidelink communication (5) a signal quality of a discovery message; (6) a number of erroneously decoded packets in a given period of time; (7) a configuration of any of: the first WTRU or the second WTRU in a public safety mode; or (8) a transmit buffer status.
  • WAN Wide Area Network
  • SA received scheduling assignment
  • the method may further comprise: directing, by the first WTRU, the second WTRU to perform measurements associated with at least the RSL; and receiving, by the first WTRU, measurement information associated with the performed measurements, wherein the triggering of the D2D link adaptation procedure may be based on the received measurement information.
  • the method may further comprise performing a direct measurement on a received signal, wherein the triggering of the D2D link adaptation procedure may be based on the direct measurement.
  • the method may further comprise configuring a forward sidelink (FSL) and the RSL, wherein the sending of the link adaptation information may include sending the link adaptation information using any of: (1) a scheduling assignment (SA); (2) the FSL or (2) the RSL.
  • FSL forward sidelink
  • SA scheduling assignment
  • RSL the RSL
  • the generating of the link adaptation information may include selecting a format of a scheduling assignment (SA) in accordance with the link adaptation information; and the sending of the link adaptation information to configure the RSL between the first WTRU and the second WTRU may include sending the SA having the selected format.
  • SA scheduling assignment
  • the sending of the link adaptation information may include transmitting an invalid resource allocation in a scheduling assignment (SA).
  • SA scheduling assignment
  • the sending of the link adaptation information may include sending the link adaptation information on a data channel.
  • the data channel may include a Physical Sidelink Shared Channel (PSSCH).
  • PSSCH Physical Sidelink Shared Channel
  • the sending of the link adaptation information on the data channel may include sending the link adaption information using a predefined or signaled set of resources of the data channel.
  • the sending of the link adaptation information on the data channel may include sending the link adaptation information in a scheduling assignment (SA) such that forward and RSL information may be communicated following the SA.
  • SA scheduling assignment
  • the sending of the link adaptation information may include sending the link adaptation information to any of: (1) an eNode-B, (2) a network entity, or (3) a reference source.
  • the sending of the link adaptation information may include sending the link adaptation information directly to the second WTRU.
  • the generating of link adaptation information may include generating any of: (1) an index value; (2) forward sidelink resource information; or (3) RSL resource information.
  • the method may further comprise selecting the link adaption information including an index value associated with a sidelink resource pattern indicating which resources in a sidelink communication period are RSL resources and which of the resources in the sidelink communication period are forward sidelink (FSL) resources.
  • FSL forward sidelink
  • the method may further comprise: receiving a configuration of the set of resources.
  • the receiving of the configuration of the set of resources may include receiving the configuration of the set of resources from any of: (1) the relay WTRU, (2) a network entity, or (3) an evolved Node B (eNB).
  • eNB evolved Node B
  • the determining of the set of resources may include: receiving one or more parameters; and determining the set of resources using the one or more parameters.
  • the determining of the set of resources may include selecting the set of resources from a predetermined resource pool.
  • the determining of the set of resources may include determining a set of allowed Time Resource Pattern of Transmission (T- RPT) resources using a T-RPT mask.
  • T- RPT Time Resource Pattern of Transmission
  • the determining of the set of resources may include determining the set of resources for a return channel used by the first WTRU to transmit to the relay WTRU based on resources for a forward channel used by the first WTRU to receive from the relay WTRU.
  • the determined set of resources for the return channel used by the relay WTRU to receive from the first WTRU may be related by an offset to one or more of the resources for the forward channel used by the relay WTRU to transmit to the first WTRU.
  • the method may further comprise: setting a link parameter; performing a measurement on a D2D communication received from the relay WTRU; estimating a value of the set link parameter based on the measurement; and reporting, by the first WTRU to the relay WTRU, the estimated value of the link parameter.
  • the link parameter may be one of: (1) a modulation and coding scheme index; or (2) a transport block size; and the measurement may be any of: (1) a measurement of an average number of transmissions or retransmissions of the D2D communication received from the relay WTRU; (2) a measurement of block error rate (BLER) associated with the D2D communication received from the relay WTRU; (3) a measurement of a number of successful packets of the D2D communication received from the relay WTRU; or (4) a measurement of a number of received SAs.
  • BLER block error rate
  • the sending of the information indicating the RSL resources may include sending, to the second WTRU, a scheduling assignment (SA) that includes the information indicating the RSL resources.
  • SA scheduling assignment
  • the SA may define one or more Time Resource Pattern of Transmission (T-RPT) resources; and the generating of the information indicating RSL resources associated with the RSL D2D communication between the first WTRU and the second WTRU may include determining a subset of the T-RPT resources, as the RSL resources, used by the first WTRU to receive the sidelink information from the second WTRU.
  • T-RPT Time Resource Pattern of Transmission
  • the determining of the subset of the T-RPT resources may include determining one or more T-RPT resources associated with a forward sidelink (FSL) for FSL D2D communication and one or more other T-RPT resources based on the determined one or more T-RPT resources associated with the FSL for the RSL D2D communication.
  • FSL forward sidelink
  • the one or more T-RPT resources defined by the SA may be associated with a sidelink communication period.
  • the subset of the one or more T-RPT resources may be indicated in the SA.
  • the RSL resources used to receive the sidelink information by the first WTRU from the second WTRU may include any of: (1) one or more of the T-RPT resources explicitly assigned in the SA by the first WTRU for the RSL D2D communication; (2) one or more of the T-RPT resources implicitly assigned using the SA by the first WTRU for the RSL D2D communication; (3) one or more of the T-RPT resources that are not available for transmission according to the SA; (4) a last T-RPT resource within a sidelink communication period; or (5) periodically occurring T-RPT resources within the sidelink communication period.
  • the periodically occurring T- RPT resources associated with the RSL may be interleaved with T-RPT resources associated with a forward sidelink (FSL) within the sidelink communication period.
  • FSL forward sidelink
  • the information indicating the RSL resources may include a plurality of bits indicating resource blocks associated with the RSL D2D communication.
  • the sending of the information indicating the RSL resources may include forwarding a radio resource control (RRC) message that may include the information indicating the RSL resources for the RSL communication between the first and second WTRUs.
  • RRC radio resource control
  • the information indicating the RSL resources may be implicitly indicated based on any of a format of a scheduling assignment (SA) or a content of the SA.
  • SA scheduling assignment
  • the determining of the RSL resources may include: determining a sidelink mask; and applying the sidelink mask to the one or more T-RPT resources within a sidelink communication period to determine the RSL resources and the forward sidelink resources for D2D unicast communication.
  • the sidelink information may include any of: (1) sidelink data; (2) sidelink control information (SCI); (3) one or more reference signals; or (4) multiplexed sidelink data and control information.
  • the triggering of the D2D link adaptation procedure may include initiating the D2D link adaptation procedure responsive to reception of the link adaptation information from any of: (1) the second WTRU, (2) an eNode-B; (3) a network entity, (4) a reference source; or (5) a further WTRU.
  • the triggering of the D2D link adaptation procedure may include starting the D2D link adaptation procedure based on an internal indication from within the first WTRU.
  • the internal indication may be based on any of: (1) a presence of Wide Area Network (WAN) traffic; (2) a signal quality of a received scheduling assignment (SA); (3) a signal quality of a previous data communication; (4) a signal quality of a previous sidelink communication (5) a signal quality of a discovery message; (6) a number of erroneously decoded packets in a given period of time; (7) a configuration of any of: the first WTRU or the second WTRU in a public safety mode; or (8) a transmit buffer status.
  • WAN Wide Area Network
  • SA received scheduling assignment
  • the method may further comprise: performing a measurement on a received signal associated with at least the RSL; and sending, by the first WTRU, measurement information associated with the performed measurement.
  • the method may further comprise: configuring a forward sidelink (FSL) and the RSL, wherein the receiving of the link adaptation information may include receiving the link adaptation information using any of: (1) a scheduling assignment (SA); (2) the FSL or (2) the RSL.
  • FSL forward sidelink
  • SA scheduling assignment
  • the triggering of the D2D link adaptation procedure may include determining a format of a scheduling assignment (S A) such that the D2D link adaptation procedure may be triggered on condition that the determined format matches one or more reference SA formats.
  • the receiving of the link adaptation information may include receiving an invalid resource allocation in a scheduling assignment (SA).
  • SA scheduling assignment
  • the receiving of the link adaptation information may include receiving the link adaptation information on a data channel.
  • the data channel may include a Physical Sidelink Shared Channel (PSSCH).
  • PSSCH Physical Sidelink Shared Channel
  • the receiving of the link adaptation information on the data channel may include receiving the link adaption information using a predefined or signaled set of resources of the data channel.
  • the receiving of the link adaptation information may include receiving the link adaptation information from any of: (1) an eNode-B, (2) a network entity, or (3) a reference source.
  • the receiving of the link adaptation information may include receiving the link adaptation information directly from the second WTRU.
  • the method may further comprise: setting a link parameter; performing a measurement on a D2D communication received from the second WTRU; estimating a value of the set link parameter based on the measurement; and reporting the estimated value of the link parameter.
  • the link parameter may be one of: (1) a modulation and coding scheme index; or (2) a transport block size; and the measurement may be any of: (1) a measurement of an average number of transmissions or retransmissions of a FSL D2D communication received from the second WTRU; (2) a measurement of block error rate (BLER) associated with the FSL D2D communication received from the second WTRU; (3) a measurement of a number of successful packets of the FSL D2D communication received from the second WTRU; or (4) a measurement of a number of received SAs.
  • BLER block error rate
  • the method may further comprise sending a configuration of the set of resources.
  • the sending of the configuration of the set of resources may include sending the configuration of the set of resources from the relay WTRU.
  • the determining of the set of resources for the RSL D2D communication from the first WTRU to the relay WTRU may include determining the set of resources using one or more parameters.
  • the determining of the set of resources may include selecting the set of resources from a predetermined resource pool.
  • the determining of the set of resources may include determining a set of allowed Time Resource Pattern of Transmission (T- RPT) resources using a T-RPT mask.
  • T- RPT Time Resource Pattern of Transmission
  • the determining of the set of resources may include determining the set of resources for a return channel used by the relay WTRU to receive from the first WTRU based on resources for a forward channel used by the relay WTRU to transmit to the first WTRU.
  • the determined set of resources for the return channel used by the relay WTRU to receive from the first WTRU may be related by an offset to one or more of the resources for the forward channel used by the relay WTRU to transmit to the first WTRU.
  • the transmit/receive unit may be configured to receive, via the second WTRU, a scheduling assignment (SA) that may include the information indicating the RSL resources.
  • SA scheduling assignment
  • the SA may define one or more Time Resource Pattern of Transmission (T-RPT) resources; and the processor may be configured to determine a subset of the T-RPT resources, as the RSL resources used by the transmit/receive unit of the WTRU to transmit the sidelink information to the second WTRU.
  • T-RPT Time Resource Pattern of Transmission
  • the processor may be configured to determine one or more T-RPT resources associated with a forward sidelink (FSL) for FSL D2D communication and one or more other T-RPT resources based on the determined one or more T-RPT resources associated with the FSL for the RSL D2D communication.
  • FSL forward sidelink
  • the one or more T-RPT resources defined by the SA may be associated with a sidelink communication period.
  • the processor may be configured to determine one or more T-RPT resources associated with the RSL sidelink for the RSL D2D communication using any of: (1) an index value associated with an index of lookup table or associated with one or more predetermined or signaled rules; (2) forward sidelink (FSL) or RSL T-RPT resource information and a fixed relationship between one or more T-RPT resources associated with the RSL sidelink for the RSL D2D communication and one or more T-RPT resources associated with (FSL) for FSL D2D communication; (3) FSL resource information associated with the lookup table or associated with the one or more predetermined rules or signaled rules.
  • the transmit/receive unit may be configured to receive an index corresponding to a resource partem for sidelink D2D communication; and the processor may be configured to determine using the received index, which resources in a sidelink communication period are RSL resources and which of the resources in the sidelink communication period are forward sidelink (FSL) resources.
  • FSL forward sidelink
  • a subset of the one or more T-RPT resources may be indicated in the SA.
  • the RSL resources used to transmit the sidelink information by the transmit/receive unit of the WTRU to the second WTRU may include any of: (1) one or more of the T-RPT resources explicitly assigned in the SA by the second WTRU for the RSL D2D communication; (2) one or more of the T-RPT resources implicitly assigned using the SA by the second WTRU for the RSL D2D communication; (3) one or more of the T-RPT resources that are not available for transmission according to the S A; (4) a last T-RPT resource within a sidelink communication period; or (5) periodically occurring T-RPT resources within the sidelink communication period.
  • the periodically occurring T-RPT resources associated with the RSL may be interleaved with T-RPT resources associated with a forward sidelink (FSL) within the sidelink communication period.
  • FSL forward sidelink
  • the information indicating the RSL resources may include a plurality of bits indicating resource blocks associated with the RSL D2D communication.
  • the transmit/receive unit may be configured to receive a radio resource control (RRC) message that may include the information indicating the RSL resources for the RSL D2D communication between the WTRU and the second WTRU.
  • RRC radio resource control
  • the information indicating the RSL resources may be implicitly indicated based on any of a format of a scheduling assignment (SA) or a content of the SA.
  • SA scheduling assignment
  • the processor may be configured to: determine a sidelink mask from the received information of the SA; and apply the sidelink mask to the one or more T-RPT resources within a sidelink communication period to determine the RSL resources and the forward sidelink resources for D2D unicast communication.
  • the sidelink information may include any of: (1) sidelink data; (2) sidelink control information (SCI); (3) one or more reference signals; or (4) multiplexed sidelink data and control information.
  • the processor may be configured to initiate the D2D link adaptation procedure responsive to reception of an indication from any of: (1) an eNode-B; (2) a network entity, (3) a reference source; or (4) a further WTRU.
  • the indication may include a scheduling assignment (SA) with a modulation and coding scheme (MCS) index exceeding a threshold.
  • SA scheduling assignment
  • MCS modulation and coding scheme
  • the processor may be configured to start the D2D link adaptation procedure based on an internal indication from within the WTRU.
  • the internal indication may be based on any of: (1) a presence of Wide Area Network (WAN) traffic; (2) a signal quality of a received scheduling assignment (SA); (3) a signal quality of a previous data communication; (4) a signal quality of a previous sidelink communication (5) a signal quality of a discovery message; (6) a number of erroneously decoded packets in a given period of time; (7) a configuration of any of: the WTRU or the second WTRU in a public safety mode; or (8) a transmit buffer status.
  • WAN Wide Area Network
  • SA received scheduling assignment
  • the processor and the transmit/receive unit may be configured to direct the second WTRU to perform measurements associated with at least the RSL; the transmit/receive unit may be configured to receive measurement information associated with the performed measurements; and the processor may be configured to trigger the D2D link adaptation procedure based on the received measurement information.
  • the processor may be configured to perform a direct measurement on a received signal, and to trigger the D2D link adaptation procedure based on the direct measurement.
  • the processor may be configured to configure a forward sidelink (FSL) and the RSL; and the transmit/receive unit may be configured to send the link adaptation information using any of: (1) a scheduling assignment (SA); (2) the FSL or (3) the RSL.
  • FSL forward sidelink
  • SA scheduling assignment
  • the processor may be configured to select a format of a scheduling assignment (SA) in accordance with the link adaptation information; and the transmit/receive unit may be configured to send the S A having the selected format.
  • SA scheduling assignment
  • the transmit/receive unit may be configured to transmit an invalid resource allocation in a scheduling assignment (SA).
  • SA scheduling assignment
  • the transmit/receive unit may be configured to send the link adaptation information on a data channel.
  • the data channel may include a Physical Sidelink Shared Channel (PSSCH).
  • PSSCH Physical Sidelink Shared Channel
  • the transmit/receive unit may be configured to send the link adaption information using a predefined or signaled set of resources of the data channel.
  • the transmit/receive unit may be configured to send the link adaption information in a scheduling assignment (SA) such that forward sidelink information and RSL information are communicated following the SA.
  • SA scheduling assignment
  • the transmit/receive unit may be configured to send the link adaptation information to any of: (1) an eNode-B, (2) a network entity, or (3) a reference source.
  • the transmit/receive unit may be configured to send the link adaptation information directly to the second WTRU.
  • the processor may be configured to generate any of: (1) an index value associated with a sidelink resource pattern; (2) forward sidelink (FSL) resource information; or (3) RSL resource information.
  • FSL forward sidelink
  • the processor may be configured to select the link adaption information including an index value associated with a sidelink resource pattern indicating which resources in a sidelink communication period are RSL resources and which of the resources in the sidelink communication period are forward sidelink
  • the transmit/receive unit may be configured to receive a configuration of the set of resources.
  • the transmit/receive unit may be configured to receive the configuration of the set of resources from any of: (1) the relay WTRU, (2) a network entity, or (3) an evolved Node B (eNB).
  • eNB evolved Node B
  • the transmit/receive unit may be configured to receive one or more parameters; and the processor may be configured to determine the set of resources using the one or more parameters.
  • the processor may be configured to select the set of resources from a predetermined resource pool.
  • the processor may be configured to determine a set of allowed T-RPT resources using a T-RPT mask.
  • the processor may be configured to determine the set of resources for a return channel used by the WTRU to transmit to the relay WTRU based on resources for a forward channel used by the WTRU to receive from the relay WTRU.
  • the determined set of resources for the return channel used by the relay WTRU to receive from the WTRU may be related by an offset to one or more of the resources for the forward channel used by the relay WTRU to transmit to the WTRU.
  • the processor may be configured to: set a link parameter, perform a measurement on a D2D communication received from the relay WTRU, and estimate a value of the set link parameter based on the measurement; and the transmit/receive unit may be configured to report the estimated value of the link parameter to the relay WTRU.
  • the link parameter may be one of: (1) a modulation and coding scheme index; or (2) a transport block size; and the measurement may be any of: (1) a measurement of an average number of transmissions or retransmissions of the D2D communication received from the relay WTRU; (2) a measurement of block error rate (BLER) associated with the D2D communication received from the relay WTRU; (3) a measurement of a number of successful packets of the D2D communication received from the relay WTRU; or (4) a measurement of a number of received SAs.
  • BLER block error rate
  • the transmit/receive unit may be configured to send to the second WTRU a scheduling assignment (SA) that may include the information indicating the RSL resources.
  • SA scheduling assignment
  • the SA may define one or more T-RPT resources, and the processor may be configured to determine a subset of the T-RPT resources, as the RSL resources, used by the WTRU to receive the sidelink information from the second WTRU.
  • the processor may be configured to determine one or more T-RPT resources associated with a forward sidelink (FSL) for FSL D2D communication and one or more other T-RPT resources based on the determined one or more T-RPT resources associated with the FSL for the RSL D2D communication.
  • FSL forward sidelink
  • the one or more T-RPT resources defined by the SA may be associated with a sidelink communication period.
  • the subset of the one or more T-RPT resources is indicated in the SA.
  • the RSL resources used to receive the sidelink information by the WTRU from the second WTRU may include any of: (1) one or more of the T-RPT resources explicitly assigned in the S A by the WTRU for the RSL D2D communication; (2) one or more of the T-RPT resources implicitly assigned using the SA by the WTRU for the RSL D2D communication; (3) one or more of the T-RPT resources that are not available for transmission according to the SA; (4) a last T-RPT resource within a sidelink communication period; or (5) periodically occurring T-RPT resources within the sidelink communication period.
  • the periodically occurring T- RPT resources associated with the RSL may be interleaved with T-RPT resources associated with a FSL within the sidelink communication period.
  • the information indicating the RSL resources may include a plurality of bits indicating resource blocks associated with the RSL D2D communication.
  • the processor and the transmit/receive unit may be configured to forward a radio resource control (RRC) message that includes the information indicating the RSL resources for the RSL D2D communication between the WTRU and second WTRU.
  • RRC radio resource control
  • the information indicating the RSL resources may be implicitly indicated based on any of a format of a scheduling assignment (SA) and/or a content of the SA.
  • SA scheduling assignment
  • the processor may be configured to: determine a sidelink mask; and apply the sidelink mask to the one or more T-RPT resources within a sidelink communication period to determine the RSL resources and the forward sidelink resources for D2D unicast communication.
  • the sidelink information may include any of: (1) sidelink data; (2) sidelink control information (SCI); (3) one or more reference signals; or (4) multiplexed sidelink data and control information.
  • the processor may be configured to initiate the D2D link adaptation procedure responsive to reception of the link adaptation information from any of: (1) the second WTRU, (2) an eNode-B; (3) a network entity, (4) a reference source; or (5) a further WTRU.
  • the processor may be configured to start the D2D link adaptation procedure based on an internal indication from within the WTRU.
  • the internal indication may be based on any of: (1) a presence of Wide Area Network (WAN) traffic; (2) a signal quality of a received scheduling assignment (SA); (3) a signal quality of a previous data communication; (4) a signal quality of a previous sidelink communication (5) a signal quality of a discovery message; (6) a number of erroneously decoded packets in a given period of time; (7) a configuration of any of: the WTRU or the second WTRU in a public safety mode; or (8) a transmit buffer status.
  • WAN Wide Area Network
  • SA received scheduling assignment
  • the processor may be configured to perform a measurement on a received signal associated with at least the RSL; and the transmit/receive unit may be configured to send measurement information associated with the performed measurement.
  • the processor may be configured to configure a FSL and the RSL, and the transmit/receive unit may be configured to receive the link adaptation information using any of: (1) a scheduling assignment (SA); (2) the FSL or (3) the RSL.
  • SA scheduling assignment
  • the processor may be configured to determine a format of a scheduling assignment (SA) such that the D2D link adaptation procedure may be triggered on condition that the determined format matches one or more reference SA formats.
  • SA scheduling assignment
  • the transmit/receive unit may be configured to receive an invalid resource allocation in a scheduling assignment (SA).
  • SA scheduling assignment
  • the transmit/receive unit may be configured to receive the link adaptation information on a data channel.
  • the data channel may include a Physical Sidelink Shared Channel (PSSCH).
  • PSSCH Physical Sidelink Shared Channel
  • the transmit/receive unit may be configured to receive the link adaption information using a predefined or signaled set of resources of the data channel.
  • the transmit/receive unit may be configured to receive the link adaptation information from any of: (1) an eNode-B, (2) a network entity, or (3) a reference source.
  • the transmit/receive unit may be configured to receive the link adaptation information directly from the second WTRU.
  • the processor may be configured to: set a link parameter, perform a measurement on a D2D communication received from the second WTRU, and estimate a value of the set link parameter based on the measurement; and the transmit/receive unit may be configured to report the estimated value of the link parameter to the second WTRU.
  • the link parameter may be one of: (1) a modulation and coding scheme index; or (2) a transport block size; and the measurement may be any of: (1) a measurement of an average number of transmissions or retransmissions of a FSL D2D communication received from the second WTRU; (2) a measurement of block error rate (BLER) associated with the FSL D2D communication received from the second WTRU; (3) a measurement of a number of successful packets of the FSL D2D communication received from the second WTRU; or (4) a measurement of a number of received SAs.
  • BLER block error rate
  • the transmit/receive unit may be configured to send a configuration of the set of resources from the relay to the first WTRU.
  • the processor may be configured to determine the set of resources using one or more parameters.
  • the processor may be configured to select the set of resources from a predetermined resource pool.
  • the processor may be configured to determine a set of allowed T-RPT resources using a T-RPT mask.
  • the processor may be configured to determine the set of resources for a return channel used by the relay WTRU to receive from the first WTRU based on resources for a forward channel used by the relay WTRU to transmit to the first WTRU.
  • the determined set of resources for the return channel used by the relay WTRU to receive from the first WTRU may be related by an offset to one or more of the resources for the forward channel used by the relay WTRU to transmit to the first WTRU.

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, des appareils et des systèmes d'adaptation de liaison pour des communications de dispositif à dispositif (D2D). Un procédé représentatif consiste : à recevoir, par une première unité d'émission/réception sans fil (WTRU), des informations indiquant des ressources de liaison latérale de retour (RSL) associées à une communication RSL D2D entre la première WTRU et une seconde WTRU ; à déterminer, par la première WTRU, les ressources RSL sur la base des informations reçues ; et à transmettre, par la première WTRU à la seconde WTRU, des informations de liaison latérale à l'aide des ressources RSL déterminées.
PCT/US2016/019886 2015-03-06 2016-02-26 Procédés, appareils et systèmes d'adaptation de liaison pour des communications de monodiffusion de dispositif à dispositif (d2d) Ceased WO2016144574A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562129494P 2015-03-06 2015-03-06
US62/129,494 2015-03-06
US201562160978P 2015-05-13 2015-05-13
US62/160,978 2015-05-13

Publications (1)

Publication Number Publication Date
WO2016144574A1 true WO2016144574A1 (fr) 2016-09-15

Family

ID=55588556

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/019886 Ceased WO2016144574A1 (fr) 2015-03-06 2016-02-26 Procédés, appareils et systèmes d'adaptation de liaison pour des communications de monodiffusion de dispositif à dispositif (d2d)

Country Status (1)

Country Link
WO (1) WO2016144574A1 (fr)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019154239A1 (fr) * 2018-02-11 2019-08-15 中兴通讯股份有限公司 Procédé et appareil de détermination d'une ressource d'envoi de communication sans fil
WO2020028662A1 (fr) * 2018-08-01 2020-02-06 Intel Corporation Accès à un canal unifié pour communication de diffusion, de diffusion de groupe et de diffusion individuelle dans une communication de liaison latérale v2x nr
CN112753186A (zh) * 2018-08-08 2021-05-04 Idac控股公司 用于新无线电(nr)中物理侧链路控制信道(pscch)设计的方法和装置
US20210211239A1 (en) * 2018-09-18 2021-07-08 Huawei Tecnologies Co., Ltd. Data Transmission Method and Apparatus
CN113261312A (zh) * 2018-10-31 2021-08-13 弗劳恩霍夫应用研究促进协会 侧链路通信中的邻近意识
WO2021212514A1 (fr) * 2020-04-24 2021-10-28 华为技术有限公司 Procédé de détermination de ressources sur une base de dispositif à dispositif, et dispositif
CN114208264A (zh) * 2019-08-13 2022-03-18 高通股份有限公司 用于侧链路通信的csi报告传输
EP3937519A4 (fr) * 2019-03-28 2022-04-06 Huawei Technologies Co., Ltd. Procédé et appareil de communication
EP3952369A4 (fr) * 2019-03-29 2022-05-18 Huawei Technologies Co., Ltd. Procédé de communication et dispositif de communication
CN114616892A (zh) * 2019-08-13 2022-06-10 欧芬诺有限责任公司 无线装置侧链路信息
EP4007356A4 (fr) * 2019-07-24 2022-09-14 Vivo Mobile Communication Co., Ltd. Procédé de configuration de ressources, procédé de transmission d'informations, et équipement associé
US11595948B2 (en) 2016-09-23 2023-02-28 Qualcomm Incorporated Resource allocation patterns for scheduling services in a wireless network
US20230156574A1 (en) * 2020-03-27 2023-05-18 Huawei Technologies Co., Ltd. Signal transmission method and apparatus
EP3852410B1 (fr) * 2018-10-19 2023-12-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de configuration de paramètres et dispositif terminal
EP4336963A3 (fr) * 2018-01-19 2024-05-29 QUALCOMM Incorporated Technique de fourniture et/ou d'application de qualite de service dans communication sans fil
US20240259791A1 (en) * 2017-03-22 2024-08-01 Sony Group Corporation Terminal device, base station device, communication method, and storage medium

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013177447A1 (fr) * 2012-05-23 2013-11-28 Kyocera Corporation Attribution de ressources de communication de dispositif à dispositif (d2d)

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013177447A1 (fr) * 2012-05-23 2013-11-28 Kyocera Corporation Attribution de ressources de communication de dispositif à dispositif (d2d)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Proposed Correction to 36.213: Sidelink Resource Configuration", vol. RAN WG1, no. Athens, Greece; 20150209 - 20150213, 8 February 2015 (2015-02-08), XP050933852, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20150208] *
INTEL CORPORATION: "Discussion on Potential Enhancement of Positioning Techniques", vol. RAN WG1, no. Athens, Greece; 20150209 - 20150213, 8 February 2015 (2015-02-08), XP050933456, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20150208] *
QUALCOMM INCORPORATED: "Essential corrections for D2D", vol. RAN WG1, no. Athens, Greece; 20150209 - 20150213, 8 February 2015 (2015-02-08), XP050933670, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20150208] *

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12010688B2 (en) 2016-09-23 2024-06-11 Qualcomm Incorporated Resource allocation patterns for scheduling services in a wireless network
US11943771B2 (en) 2016-09-23 2024-03-26 Qualcomm Incorporated Resource allocation patterns for scheduling services in a wireless network
US11595948B2 (en) 2016-09-23 2023-02-28 Qualcomm Incorporated Resource allocation patterns for scheduling services in a wireless network
US20240259791A1 (en) * 2017-03-22 2024-08-01 Sony Group Corporation Terminal device, base station device, communication method, and storage medium
EP4336963A3 (fr) * 2018-01-19 2024-05-29 QUALCOMM Incorporated Technique de fourniture et/ou d'application de qualite de service dans communication sans fil
US12273801B2 (en) 2018-01-19 2025-04-08 Qualcomm Incorporated Techniques for providing and/or applying quality of service in wireless communication
WO2019154239A1 (fr) * 2018-02-11 2019-08-15 中兴通讯股份有限公司 Procédé et appareil de détermination d'une ressource d'envoi de communication sans fil
WO2020028662A1 (fr) * 2018-08-01 2020-02-06 Intel Corporation Accès à un canal unifié pour communication de diffusion, de diffusion de groupe et de diffusion individuelle dans une communication de liaison latérale v2x nr
CN112753186A (zh) * 2018-08-08 2021-05-04 Idac控股公司 用于新无线电(nr)中物理侧链路控制信道(pscch)设计的方法和装置
CN112753186B (zh) * 2018-08-08 2024-02-09 交互数字专利控股公司 用于新无线电(nr)中物理侧链路控制信道(pscch)设计的方法和装置
US12003326B2 (en) * 2018-09-18 2024-06-04 Huawei Technologies Co., Ltd. Data transmission method and apparatus
US20210211239A1 (en) * 2018-09-18 2021-07-08 Huawei Tecnologies Co., Ltd. Data Transmission Method and Apparatus
US11943097B2 (en) 2018-10-19 2024-03-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Parameter configuration method, terminal device and storage medium
EP3852410B1 (fr) * 2018-10-19 2023-12-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de configuration de paramètres et dispositif terminal
US12483857B2 (en) 2018-10-31 2025-11-25 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. Proximity awareness in sidelink communications
CN113261312A (zh) * 2018-10-31 2021-08-13 弗劳恩霍夫应用研究促进协会 侧链路通信中的邻近意识
US12035294B2 (en) 2019-03-28 2024-07-09 Huawei Technologies Co., Ltd. Communication method and apparatus
EP3937519A4 (fr) * 2019-03-28 2022-04-06 Huawei Technologies Co., Ltd. Procédé et appareil de communication
EP4280763A3 (fr) * 2019-03-28 2024-02-21 Huawei Technologies Co., Ltd. Procédé et appareil de communication
EP3952369A4 (fr) * 2019-03-29 2022-05-18 Huawei Technologies Co., Ltd. Procédé de communication et dispositif de communication
JP2023126773A (ja) * 2019-03-29 2023-09-12 華為技術有限公司 通信方法及び通信装置
JP7626798B2 (ja) 2019-03-29 2025-02-04 華為技術有限公司 通信方法及び通信装置
JP7295264B2 (ja) 2019-03-29 2023-06-20 華為技術有限公司 通信方法及び通信装置
JP2022528385A (ja) * 2019-03-29 2022-06-10 華為技術有限公司 通信方法及び通信装置
US12022541B2 (en) 2019-03-29 2024-06-25 Huawei Technologies Co., Ltd. Communication method and communications apparatus
US11470662B2 (en) 2019-03-29 2022-10-11 Huawei Technologies Co., Ltd. Communication method and communications apparatus
EP4007356A4 (fr) * 2019-07-24 2022-09-14 Vivo Mobile Communication Co., Ltd. Procédé de configuration de ressources, procédé de transmission d'informations, et équipement associé
US12414124B2 (en) 2019-07-24 2025-09-09 Vivo Mobile Communication Co., Ltd. Resource configuration method, information transmission method, and related device
CN114616892A (zh) * 2019-08-13 2022-06-10 欧芬诺有限责任公司 无线装置侧链路信息
CN114208264B (zh) * 2019-08-13 2024-04-02 高通股份有限公司 用于侧链路通信的csi报告传输
CN114208264A (zh) * 2019-08-13 2022-03-18 高通股份有限公司 用于侧链路通信的csi报告传输
US20230156574A1 (en) * 2020-03-27 2023-05-18 Huawei Technologies Co., Ltd. Signal transmission method and apparatus
EP4117344A4 (fr) * 2020-03-27 2023-08-30 Huawei Technologies Co., Ltd. Procédé et appareil d'émission de signal
WO2021212514A1 (fr) * 2020-04-24 2021-10-28 华为技术有限公司 Procédé de détermination de ressources sur une base de dispositif à dispositif, et dispositif

Similar Documents

Publication Publication Date Title
US20240373422A1 (en) Methods, apparatus, and systems for reliable channel state information reporting
US11743079B2 (en) Uplink operation for LTE in an unlicensed band
TWI899201B (zh) 下鏈小資料接收方法及裝置
US20230179341A1 (en) Receiver feedback in wireless systems
KR102856260B1 (ko) V2x에서 harq를 지원하기 위한 방법, 장치 및 시스템
US9654994B2 (en) Device-to-device (D2D) link adaptation
US20220303952A1 (en) New radio (nr) vehicle to everything (v2x) methods for sensing and resource allocation
US20240373431A1 (en) Methods, architectures, apparatuses and systems for network energy savings
KR20250093577A (ko) Nr sl psfch 전송 및 모니터링
JP7861188B2 (ja) ニューラジオ（ｎｒ）における物理サイドリンク制御チャネル（ｐｓｃｃｈ）設計に対する方法および装置

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: 16711405

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: 16711405

Country of ref document: EP

Kind code of ref document: A1