Device-to-device sync
The WTRU adapts D2D communication scheduling based on network conditions to maintain reliable device-to-device synchronization in areas with limited coverage, addressing synchronization challenges in existing systems.
Patent Information
- Application Number
- JP2022140749
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2014-11-05
- Filing Date
- 2022-09-05
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2035-03-19
AI Technical Summary
Existing wireless communication systems face challenges in maintaining consistent device-to-device synchronization, particularly in areas with limited or no network coverage, such as tunnels, basements, or during natural disasters, which can disrupt network services.
A wireless transmit/receive unit (WTRU) determines an appropriate scheduling mode for device-to-device (D2D) communications based on radio link coverage conditions, using trigger events like RRC timers and radio link failures to switch between scheduling modes and select resources from a resource pool for D2D communications.
Enhances D2D communication reliability and consistency by adapting scheduling modes based on network conditions, ensuring seamless communication even in areas with limited or no network coverage.
Smart Images

Figure 0007583768000001 
Figure 0007583768000002 
Figure 0007583768000003
Abstract
Description
[Technical field]
[0001] The present invention relates to device-to-device synchronization. [Background technology]
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 61 / 955,747, filed March 19, 2014, U.S. Provisional Patent Application No. 61 / 955,746, filed March 19, 2014, U.S. Provisional Patent Application No. 61 / 990,049, filed May 7, 2014, U.S. Provisional Patent Application No. 62 / 032,373, filed August 1, 2014, and U.S. Provisional Patent Application No. 62 / 075,524, filed November 5, 2014, the disclosures of which are incorporated herein by reference in their entireties.
[0003] Direct device-to-device (D2D) communication may be used in wireless networks. D2D communication may refer to wireless communication transmissions exchanged directly between two or more wireless transmit / receive units (WTRUs) without the communication being routed through a wireless communication infrastructure such as a base station or access point (although, for example, the wireless infrastructure may be used to configure a D2D session and / or schedule a D2D transmission). D2D communication may be used to provide proximity-based services (Pro-Se) between WTRUs. D2D communication may provide support for commercial, social, and public safety communications. The D2D infrastructure provides consistency in user experience, including, for example, reachability and mobility aspects. D2D may provide network offloading in high traffic cells. For example, D2D may provide support for various services and / or applications when network coverage is limited or unavailable.
[0004] With respect to supporting public safety communications, there may be a need to harmonize radio access technologies across jurisdictions and lower the cost of radio access technologies to public safety (PS) personnel. For example, a first responder may require communications in an area that may not be under radio coverage of an LTE network. For example, a WTRU may be out of coverage in a tunnel, basement, or an area where network services are disrupted by natural disasters, terrorist attacks, etc. D2D communications may be PS supported. For example, D2D may provide push-to-talk services directly to a first responder who may be dealing with a time-sensitive emergency.
[0005] D2D communication may be available for commercial use, such as for utility companies. For example, D2D communication techniques may be used to improve communication in areas that may have insufficient coverage from the network infrastructure. Commercial and social users may request D2D communication, for example, to ensure consistency of their user experience. For example, users may request D2D communication to improve user reachability and / or mobility. Summary of the Invention
[0006] One or more example embodiments described more fully below provide apparatus, functions, procedures, processes, execution of computer program instructions that tangibly embody computer-readable memory, functions, and method operations for one or more of the following: To facilitate scheduling of D2D communications, the WTRU may be configured to determine an appropriate scheduling mode to use in D2D communications based on conditions associated with radio link coverage from a cellular network, such as a Long Term Evolution (LTE) Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN). For example, the WTRU may determine coverage conditions associated with E-UTRAN coverage based on one or more trigger events and / or one or more trigger updates to select an appropriate mode in which to utilize D2D resources.
[0007] The WTRU D2D scheduling mode of operation may be determined based on one or more triggering events observed at the WTRU. The triggering event may be related to detected radio conditions or network coverage. The triggering event may be related to the state of a WTRU radio resource control (RRC) timer (e.g., detecting that an RRC timer has been started, detecting that an RRC timer is running, detecting that an RRC timer has been stopped, detecting that an RRC timer has expired, or detecting that an RRC timer has been reset). An example of an RRC timer may include a radio link failure (RLF) timer. For purposes of illustration and description, the examples described herein may be described with respect to an RLF timer, but the examples may also be applicable to an RRC timer (and vice versa). Instead of, or in addition to, performing a traditional timer procedure upon the occurrence of an RRC-related triggering event, the WTRU may also be configured to switch D2D modes of operation based on the occurrence of an RRC-related triggering event. The WTRU may evaluate and re-evaluate the WTRU mode of operation based on different types of triggers depending on whether the WTRU is connected to the network or in IDLE mode. Resource pool selection for WTRU transmission (Tx) and / or reception (Rx) for D2D communication may be performed by the WTRU, which may select D2D communication parameters using resource pool configuration and message content, for example, based on a change in WTRU mode of operation, based on various triggering events, or based on RLF related trigger events. Time domain D2D transmission and / or reception patterns may be configured based on various triggering events.
[0008] The WTRU may determine a type of scheduling mode for D2D communication based on detected radio link conditions and / or other triggering conditions associated with the E-UTRAN network. For example, the WTRU may operate in a first scheduling mode for device-to-device communication. In the first scheduling mode, a network entity may schedule resources to be used by the WTRU for device-to-device communication. The WTRU may detect that a radio link failure (RLF) timer is running or has been started. In response to detecting that the radio link failure timer is running or has been started, the WTRU may switch from the first scheduling mode for device-to-device communication to a second scheduling mode for device-to-device communication. In the second scheduling mode, the WTRU may select resources from a resource pool for the WTRU to use for one or more device-to-device communications.
[0009] For example, the RRC timer may correspond to timer T310. The WTRU may start an RRC timer (e.g., timer T310) in response to detecting that a number of consecutive out-of-synch transmission time intervals (TTIs) exceed a threshold. In an example, the RRC timer may correspond to timer T311. The WTRU may start an RRC timer (e.g., timer T311) in response to an RRC connection re-establishment procedure being initiated. The RRC timer may correspond to timer T301. The WTRU may cease operating in the second scheduling mode upon expiration of timer T301. The WTRU may be configured to start an RRC timer (e.g., timer T301) in response to the WTRU sending a radio resource control (RRC) connection re-establishment request message. Starting the RRC timer may trigger the WTRU to change the D2D scheduling mode from the first mode to the second mode. The WTRU may change the D2D scheduling mode from the second mode to the first mode upon successful re-establishment of the RRC connection. Operating the WTRU in the second scheduling mode may include operating the WTRU using fixed power control. The decision to operate as a relay may act as a trigger. For example, the WTRU may decide to operate as a relay WTRU and start operating in the second scheduling mode for D2D communication.
[0010] The WTRU may determine a type of scheduling mode for D2D communication based on detecting a connection failure with the E-UTRAN network. For example, a WTRU in IDLE mode may initiate a connection establishment procedure to request D2D resources for transmission. The WTRU may start an RRC timer (e.g., connection establishment timer T300). Upon expiration of the connection establishment timer, the WTRU may decide to use a second scheduling mode. In the second scheduling mode, the WTRU may select resources from a resource pool for the WTRU to use for one or more device-to-device communications. For example, the WTRU may decide to use the second scheduling mode until it is configured by the network with resources for the first scheduling mode.
[0011] The WTRU may switch from a first scheduling mode for D2D communication to a second scheduling mode for D2D communication in response to the detected condition. The WTRU may operate in the first scheduling mode for D2D communication. In the first scheduling mode, a network entity may schedule resources to be used by the WTRU for D2D communication. The WTRU may detect a condition to switch the WTRU from the first scheduling mode to a second scheduling mode for D2D communication. In response to detecting the condition, the WTRU may operate in the second scheduling mode. In the second scheduling mode, the WTRU may select resources from a resource pool for the WTRU to use for the D2D communication.
[0012] The WTRU may detect a condition to switch from the first scheduling mode to the second scheduling mode by determining that the WTRU has not selected a cell that supports D2D communication. The WTRU may detect a condition to switch from the first scheduling mode to the second scheduling mode by determining that the WTRU is out of cell coverage. The WTRU may detect a condition to switch from the first scheduling mode to the second scheduling mode by determining that a number of radio link communication (RLC) retransmissions exceed a threshold.
[0013] The WTRU may detect a condition to switch from the first scheduling mode to the second scheduling mode by detecting a failure to decode a serving cell system information block (SIB) within a time period. The WTRU may detect a condition to switch from the first scheduling mode to the second scheduling mode by determining that the WTRU is in an RRC_IDLE state. The WTRU may switch to use fixed power control in response to switching from the first scheduling mode to the second scheduling mode.
[0014] The WTRU may be configured to operate in a first scheduling mode for D2D communication. In the first scheduling mode, a network entity may schedule resources to be used by the WTRU for D2D communication. The WTRU may detect a condition to select a second scheduling mode for D2D communication. In the second scheduling mode, the WTRU may select resources from a resource pool for the WTRU to use for D2D communication. The WTRU may operate in the second scheduling mode for D2D communication in response to detecting the condition. The WTRU may detect the condition based on one or more triggers described herein. For example, as described herein, the WTRU may detect the condition based on the state of a timer (e.g., an RRC timer, an RLF timer, timer 300, timer 301, timer 310, and / or timer 311). The WTRU may be configured to operate in the first scheduling mode using broadcast signaling or dedicated signaling. The WTRU may detect the condition by determining that the WTRU is unable to identify a cell that satisfies a suitability criterion. The WTRU may select a pre-configured resource pool associated with the second scheduling mode when it is unable to identify a cell that satisfies the suitability criterion. The WTRU may be configured to switch from the second scheduling mode to the first scheduling mode upon determining that timer T310 is stopped and timer T311 is not running.
[0015] A D2D synchronization signal (D2DSS) may be transmitted and / or received by the WTRU. For example, the D2DSS may be communicated using one or more D2D frame configurations. The content of the synchronization frame may be determined from the D2DSS and / or hop count. The WTRU may use rules to prioritize synchronization sources and prioritize data reception. The WTRU may be configured to transmit one or more D2DSS, which may include preamble and postamble configurations. The WTRU may be configured to determine when to stop and / or change transmission of D2DSS and / or other types of D2D messages, for example, based on the occurrence of a triggering condition. The WTRU may be configured to determine an appropriate format for a physical D2D synchronization channel (PD2DSCH) transmission, which may include determining message content, D2DSS content, and / or conditions for transmission of PD2DSCH. [Brief description of the drawings]
[0016] [Figure 1A] FIG. 1 is a system diagram of an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] FIG. 1B is a system diagram of an example wireless transmit / receive unit (WTRU) that may be used within the communications system shown in FIG. 1A. [Figure 1C] A system diagram of an example radio access network and an example core network that may be used within the communication system shown in FIG. 1A. [Figure 1D] A system diagram of another example radio access network and an example core network that may be used within the communication system shown in FIG. 1A. [Figure 1E] A system diagram of another example radio access network and an example core network that may be used within the communication system shown in FIG. 1A. [Figure 1F]FIG. 1B is a system diagram of an example of a device-to-device synchronization signal broadcast by a base station (BS) and distributed to various devices in the communication system shown in FIG. 1A. [Figure 1G] FIG. 1B is a system diagram of an example of propagation of a synchronization cluster head (SCH) between two synchronization clusters (eg, two-hop synchronization) in the communication system shown in FIG. 1A. [Diagram 2] FIG. 11 is a state transition diagram of an example of one or more D2D_CS states configured to be sub-states of an existing state machine in accordance with an example embodiment. [Diagram 3] 13 is an example system diagram of a WTRU determining a power control mode based on a SIB when moving to the edge of coverage or into coverage. [Figure 4] FIG. 11 is a state transition diagram of one or more example D2D_CS states configured to be considered as separate state variables or conditions and used to determine actions that may be performed in conjunction with existing or newly defined procedures in accordance with an exemplary embodiment. [Diagram 5] FIG. 1 illustrates a device-to-device time domain synchronization frame suitable for implementing one or more exemplary embodiments. [Figure 6] FIG. 1 illustrates a device-to-device time and frequency domain synchronization frame suitable for implementing one or more exemplary embodiments. [Figure 7] FIG. 1 is a diagram of a device-to-device time domain synchronization frame using multiple frame formats suitable for implementing one or more exemplary embodiments. [Figure 8] FIG. 2 is a diagram of a device-to-device sync source ID suitable for implementing one or more exemplary embodiments. [Figure 9] FIG. 1 is a diagram of a device-to-device synchronization signal transmission preamble / postamble suitable for implementing one or more exemplary embodiments. [Figure 10]FIG. 1 is a diagram of an example PD2DSCH scheduling assignment (SA) timeline and data association compared to a "regular" SA timeline and associated data. [Figure 11] FIG. 11 is an example PD2DSCH-SA timeline and data association diagram in which values of the SA associated with the PD2DSCH are set and transmitted within a PD2DSCH transmission subframe. [Figure 12] FIG. 11 is an example PD2DSCH-SA timeline and data association diagram in which an SA associated with a PD2DSCH is transmitted within a SA transmission subframe. [Figure 13] FIG. 13 is a diagram of an example PD2DSCH-SA timeline and data association based on an explicit indication that the location of the SA associated with the PD2DSCH is carried within the PD2DSCH. [Figure 14] 1A-1D are diagrams of example scenarios for in-coverage, out-of-coverage, and partial coverage D2D discovery and / or communication. [Figure 15] 1 is a diagram of an example scenario of communication between an in-coverage WTRU and an out-of-coverage WTRU. [Figure 16] 11A-11C are diagrams of example signals that may be used by an out-of-coverage WTRU to determine and / or drive resource allocation. [Figure 17] 11 is an example of signaling that may be used by an eNB and / or an in-coverage WTRU to determine and / or drive resource allocation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] Next, a detailed description of the exemplary embodiments will be described with reference to various figures. Although the present specification provides detailed examples of possible implementations, it should be noted that the details are intended to be illustrative and in no way limit the scope of application.
[0018] 1A is a diagram of an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messages, broadcasts, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may use 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), etc.
[0019] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and / or 102d (which may be referred to generally or collectively as WTRUs 102), a radio access network (RAN) 103 / 104 / 105, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, home appliances, and the like.
[0020] The communication system 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 / 107 / 109, the Internet 110, and / or the network 112. By way of example, 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, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0021] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals within a particular geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In another embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and thus utilize multiple transceivers for each sector of the cell.
[0022] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 115 / 116 / 117, which may be any suitable wireless communications link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).
[0023] More specifically, as mentioned above, the communication system 100 may be a multiple access system and may use one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 103 / 104 / 105 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 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).
[0024] In another embodiment, 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 115 / 116 / 117 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A).
[0025] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.16 (e.g., 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), or the like.
[0026] The base station 114b of FIG. 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity within a localized area, such as a business office, a home, a vehicle, a campus, etc. In one embodiment, 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). In another embodiment, 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). In yet another embodiment, 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. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not be required to access the Internet 110 via the core network 106 / 107 / 109.
[0027] The RAN 103 / 104 / 105 may communicate with the core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be understood that the RAN 103 / 104 / 105 and / or the core network 106 / 107 / 109 may communicate directly or indirectly with other RANs that use the same RAT as the RAN 103 / 104 / 105 or a different RAT. For example, in addition to being connected to RAN 03 / 104 / 105, which may be utilizing E-UTRA radio technology, core network 106 / 107 / 109 may also communicate with another RAN (not shown) using GSM radio technology.
[0028] The core network 106 / 107 / 109 may also act 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 a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP / IP Internet protocol suite. The network 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the network 112 may include another core network connected to one or more RANs, which may use the same RAT as the RANs 103 / 104 / 105 or a different RAT.
[0029] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a that may use a cellular-based radio technology and a base station 114b that may use an IEEE 802 radio technology.
[0030] 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B, 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 130, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while still being consistent with an embodiment. Also, embodiments contemplate that the base stations 114a and 114b and / or nodes which they may represent, such as, but not limited to, a BTS, a Node-B, a site controller, an access point (AP), a home Node-B, an evolved home Node-B (eNodeB), a home evolved Node-B (HeNB), a home evolved Node-B gateway, and a proxy node, among others, may include some or all of the elements shown in FIG. 1B and described herein.
[0031] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. 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. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated within an electronic package or chip.
[0032] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 115 / 116 / 117. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0033] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.
[0034] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, UTRA and IEEE 802.11.
[0035] 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 an 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. Additionally, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random access memory (RAM), read only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. In other embodiments, 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 home computer (not shown).
[0036] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control this power to other components within the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, 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, etc.
[0037] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 and / or may determine its location based on the timing of when signals are received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by way of any suitable location determination method while still being consistent with an embodiment.
[0038] 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. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos or videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, etc.
[0039] 1C is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As previously mentioned, the RAN 103 may communicate with the WTRUs 102a, 102b, 102c over the air interface 115 using UTRA radio technology. The RAN 103 may also communicate with the core network 106. As shown in FIG. 1C, the RAN 103 may include Node-Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while still being consistent with an embodiment.
[0040] As shown in FIG. 1C, the Node-Bs 140a, 140b may communicate with the RNC 142a. Additionally, the Node-Bs 140c may communicate with the RNC 142b. The Node-Bs 140a, 140b, 140c may communicate with their respective RNCs 142a, 142b via an Iub interface. The RNCs 142a, 142b may communicate with each other via an Iur interface. Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected. Additionally, each of the RNCs 142a, 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.
[0041] 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. Although each of the foregoing elements is shown as part of the core network 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than a core network operator.
[0042] The RNC 142a in the RAN 103 may be connected to an 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 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.
[0043] The RNC 142a in the RAN 103 may also be connected to an SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to a GGSN 150. The SGSN 148 and GGSN 150 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.
[0044] As mentioned above, the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0045] 1D is a system diagram of the RAN 104 and the core network 107 according to an embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 104b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the core network 107.
[0046] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while still being 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. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a may, for example, use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
[0047] Each of the eNode-Bs 160a, 160b, 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, etc. As shown in FIG 1D, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
[0048] The core network 107 shown in Figure 1D may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is shown as part of the core network 107, it will be understood that any one of these elements may be owned and / or operated by an entity other than a core network operator.
[0049] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, etc. 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.
[0050] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 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 the user plane during inter-eNode B handover, triggering pages when downlink data is available to the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.
[0051] The serving gateway 164 may also be connected to a 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.
[0052] The core network 107 may facilitate communication with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communication between the WTRUs 102a, 102b, 102c and traditional land-line communication devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 107 and the PSTN 108. Additionally, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0053] 1E is a system diagram of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 may be an Access Service Network (ASN) that communicates with the WTRUs 102a, 102b, 102c over the air interface 117 using IEEE 802.16 radio technology. As described further below, communication links between different functional entities, the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109, may be defined as reference points.
[0054] 1E, the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182, although it will be understood that the RAN 105 may include any number of base stations and ASN gateways while still being consistent with an embodiment. The base stations 180a, 180b, 180c may each be associated with a particular cell (not shown) in the RAN 105 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In one embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a may, for example, use multiple antennas to transmit wireless signals to and receive wireless signals from the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, etc. The ASN gateway 182 may act as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, etc.
[0055] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 standard. Additionally, each of the WTRUs 102a, 102b, 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.
[0056] The communication link between each of the base stations 180a, 180b, 180c 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 180a, 180b, 180c and the ASN gateway 182 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, 102c.
[0057] As shown in FIG. 1E, the RAN 105 may be connected to a core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point, including protocols for facilitating data transfer and mobility management capabilities, for example. The core network 109 may include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, and Accounting (AAA) server 186, and a gateway 188. Although each of the aforementioned elements are shown as part of the core network 109, it will be understood that any one of these elements may be owned and / or operated by an entity other than a core network operator.
[0058] The MIP-HA may be responsible for IP address management and may enable the WTRUs 102a, 102b, 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 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 186 may be responsible for supporting user authentication and user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 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. Additionally, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0059] Although not shown in FIG. 1E, it will be understood that the RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN 105 and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between a home core network and a visited core network.
[0060] 1A-1E, it will be appreciated that the communications system 100 may include synchronization signals (SS) (not shown) that are broadcast by the base stations 114a and 114b to the WTRUs 102a, 102b, 102c, and 102d over the air interfaces 115, 116, and 117. The SS may enable the WTRUs 102a, 102b, 102c, and 102d to determine the time and frequency parameters used to demodulate downlink and transmit uplink signals at the appropriate times, as well as whether the target cell supports frequency division duplexing (FDD) or time division duplexing (TDD). These synchronization signals may be designated as primary synchronization signals (PSS) and secondary synchronization signals (SSS). 1A-1G, it will be appreciated that the WTRUs 102a, 102b, 102c, 102d, and the WTRUs 102e, 102f, 102g, 102h, 102i, and 102j may support device-to-device (D2D) communications between two or more nearest neighboring WTRUs according to one or more embodiments. Thus, a D2D synchronization signal (D2DSS) may be broadcast between the D2D-enabled WTRUs, which may be designated as a first D2D synchronization signal (P-D2DSS) and a second D2D synchronization signal (S-D2DSS).
[0061] FIG. 1F is a system diagram of an example of D2DSS broadcast by a base station (BS) and a synchronization cluster head (SCH). The BS and / or SCH transmitting the D2DSS may be referred to as a synchronization source (SS). The D2DSS may be relayed to a synchronization cluster head (SCH), such as the SCH 103, and / or the WTRUs 102e, 102f, 102g, 102h, 102i, and 102j, as described herein. The SCH may be a synchronization source other than a base station (e.g., an eNB) that does not derive the transmitted synchronization from another synchronization source. A non-SCH WTRU that receives D2DSS from an SCH and / or a base station. A non-SCH WTRU may be a synchronization source by transmitting D2DSS based on the synchronization derived from its SCH or base station. A WTRU may communicate D2DSS using a sidelink synchronization signal. A WTRU may communicate D2DSS using two sidelink synchronization signals. For example, the WTRU may communicate D2DSS using a first sidelink synchronization signal and a second sidelink synchronization signal.
[0062] FIG. 1G is a system diagram illustrating an example propagation of SCH synchronization between two synchronization clusters (e.g., between synchronization zone 1 and synchronization zone 2). This two-hop synchronization example may be performed by the communication system illustrated in FIG. 1A. Although FIG. 1G illustrates an example two-hop synchronization, SCH synchronization may be propagated over more than two hops.
[0063] Specifically, FIG. 1F illustrates an example of a distributed synchronization scheme in which a serving base station (S-BS) may broadcast an indication of one or more pools of D2D resources to one or more WTRUs for discovery and communication within its own cell (e.g., cell 1) for reception and / or transmission. A receiver disposed within the WTRU may determine a time and / or frequency reference, for example, such that receiver windows and frequency corrections may be aligned when detecting D2D channels and / or transceiver timing, and parameters may be aligned when transmitting D2D channels. As illustrated in FIG. 1F, an example embodiment described below provides information to WTRUs exposed to D2D channels transmitted by neighboring WTRUs camping on different cells (e.g., N-BS in cell No. 2), PLMNs (not shown), and clusters (e.g., SCH synchronization cluster No. 1). WTRUs camping on neighboring cells, PLMNs, and / or clusters may signal their own D2D resource pools along with their synchronization references to enable detection of D2D communication resources. This objective is served by various synchronization protocols described below by one or more exemplary embodiments. In other words, the WTRU may relay the synchronization reference and the D2D resource pool to be monitored by neighboring WTRUs. Furthermore, the exemplary embodiments may enable the WTRU to perform direct transmission to retransmit synchronization signals to other neighboring WTRUs to enable synchronization of potential receivers within the network (e.g., as well as outside the network coverage area).
[0064] A D2D-enabled WTRU may perform various operations based on the state of the WTRU. Exemplary states may include the location of the WTRU in the network, whether neighboring WTRUs are near the WTRU, radio resource control (RRC) state, D2D configuration, etc. For example, a mode selection (e.g., scheduling mode selection) may be performed when the WTRU moves out of the coverage of a cell. The WTRU may, for example, start / stop relaying synchronization based on certain conditions. Examples may be such that the WTRU may select a synchronization source based on certain conditions or the WTRU may select a resource pool based on the same or other conditions. The WTRU may determine whether to transmit a D2DSS and / or relay a PD2DSCH message based on the same or other conditions. The WTRU may relay a PSBCH (Physical Sidelink Broadcast Channel) message, which may include a MasterInformationBlock-SL message. In other words, the D2D-enabled WTRU may determine multiple parameters to perform D2D communication based on the detected radio link conditions. A D2D-enabled WTRU may initiate procedures to evaluate or re-evaluate these parameters when there is a change in WTRU state. For example, a change in the WTRU's location in the network, a change in the identity of nearby neighboring WTRUs, an RRC state change, a D2D configuration update, etc. may trigger the WTRU to evaluate which scheduling mode to use and / or whether to relay a synchronization signal. Non-limiting example scenarios that may illustrate operations and procedures that may be performed by a D2D-enabled WTRU are provided herein.
[0065] A D2D-enabled WTRU may determine resources that the D2D-enabled WTRU may use for D2D communication. The resources may depend on the scheduling mode in which the WTRU is operating. For example, the WTRU may operate in Mode 1. In Mode 1, the WTRU may dynamically request resources from a network entity (e.g., a base station or eNB). In Mode 1, which may be referred to as a scheduled mode of operation, the eNB may schedule resources that the WTRU may use for D2D transmissions. The WTRU may operate in Mode 2, which may be referred to as a WTRU-selected scheduling mode. In Mode 2 (e.g., a WTRU-selected mode), the WTRU autonomously selects D2D resources to use from a resource pool that may be semi-statically signaled by the network or pre-configured in the WTRU. As described herein, the WTRU may decide whether to select Mode 1 or Mode 2 based on a network configuration and / or one or more conditions or triggers, for example, in response to detecting that an RRC timer is running or has been started. The WTRU may select a resource pool based on the WTRU's current conditions (eg, RRC conditions, coverage conditions, channel conditions, etc.).
[0066] A D2D-capable WTRU may determine when to transmit (e.g., generate or forward) a D2D synchronization signal (D2DSS) and / or a D2D synchronization message (PD2DSCH). The WTRU may determine when to transmit the D2DSS and / or D2D synchronization message based on nearby nodes from which the WTRU may detect configuration parameters and / or other triggers described herein.
[0067] A D2D-enabled WTRU may select a master synchronization source (MSS). The MSS may be a base station (e.g., an eNode B). The MSS may be another D2D-enabled WTRU that may be suitable to use for reference timing in supporting D2D operations. The D2D-enabled WTRU may perform MSS selection or reselection based on updates to WTRU conditions (e.g., detection of D2D neighbor nodes and / or WTRU mobility).
[0068] A D2D-enabled WTRU may determine a resource pool that the WTRU may use for D2D transmission and reception. For example, the WTRU may use resources provided by the network or pre-configured resources depending on its configuration and conditions (e.g., when the WTRU is operating in Mode 1). The WTRU may stop using the pre-configured resources (e.g., due to mobility or network reconfiguration) and obtain resources from the serving cell base station or eNB (e.g., when the WTRU transitions from Mode 2 to Mode 1). The D2D-enabled WTRU may determine changes in network conditions and perform resource pool selection / reselection based on the changed network conditions.
[0069] A D2D-enabled WTRU may, for example, determine a time pattern for reception and transmission of D2D communications and / or exchange information with a second WTRU to ensure that a pair of WTRUs can communicate with each other. An in-coverage D2D-enabled WTRU may initiate a procedure to provide a time domain transmission and / or reception pattern when the in-coverage D2D-enabled WTRU detects an out-of-coverage WTRU in the vicinity of the in-coverage D2D-enabled WTRU.
[0070] The WTRU may identify resources on which it may monitor discovery and communication. For example, the WTRU may monitor resources associated with a serving cell or cluster. The WTRU may monitor resources associated with a neighboring cell, cluster, or PLMN. The WTRU may determine a coverage condition of the WTRU. For example, the WTRU may determine that the WTRU is in-coverage, at the edge of coverage, or out-of-coverage. In determining the coverage condition, the WTRU may utilize one or more trigger events (e.g., an RRC timer, e.g., an RLF timer). The WTRU may determine the coverage condition by detecting one or more trigger updates associated with the coverage condition. The WTRU may detect the trigger updates by detecting one or more trigger events.
[0071] The WTRU may select resources based on the coverage condition of the WTRU. The coverage conditions (e.g., each coverage condition) may be associated with WTRU resources, and the WTRU may select resources associated with the coverage condition of the WTRU. The WTRU may determine a mode of operation (e.g., a scheduling mode for D2D communication) based on, for example, one or more triggering events. Exemplary triggering events may include detecting that an RRC timer (e.g., an RLF timer) is running or started. The WTRU may determine a scheduling mode for D2D communication based on additional triggering events. The WTRU may select a resource pool for WTRU transmission (Tx) and / or reception (Rx). Resource pool selection may include configuration of resource pools and message content based on various triggering events. The WTRU may select one or more resource pools that may have been forwarded to other WTRUs.
[0072] The WTRU may configure a time domain D2D transmission and / or reception pattern, for example, based on various triggering events. The WTRU may perform D2DSS transmission and / or D2DSS reception, for example, based on one or more D2D frame configurations. The WTRU may determine the content of the synchronization frame from the D2DSS and hop count. The WTRU may use rules to prioritize synchronization sources. The WTRU may use rules to prioritize, for example, data reception from different synchronization sources. The WTRU may transmit D2DSS. The D2DSS transmission may include configuration of a preamble and / or postamble. The WTRU may determine when to stop or change the transmission of D2DSS or messages. The WTRU may format the physical D2D synchronization (PD2DSCH), for example, to include message content, rules for determining content, D2DSS content, and / or conditions for transmitting PD2DSCH.
[0073] The WTRU may determine a coverage condition of the WTRU based on a triggering event that may be associated with the coverage condition. For example, the WTRU may determine whether the WTRU is in-coverage, at the edge of coverage, or in an out-of-coverage condition, for example, by determining that a timer (e.g., an RRC timer, e.g., an RLF timer) is running or started.
[0074] The WTRU may determine the coverage condition by determining one or more triggered updates of the WTRU coverage condition. The WTRU may determine the triggered update by detecting one or more trigger events associated with the triggered update. The WTRU may determine the coverage condition based on the proximity of the WTRU to a cell that may transmit a radio frequency signal. Exemplary cells may include LTE cells (e.g., macrocells), picocells, femtocells, etc. For example, the WTRU may determine that the WTRU is in-coverage when the WTRU is located within a boundary of the cell. The WTRU may determine that the WTRU is not in-coverage when the WTRU is close to an edge of the cell. The WTRU may determine that the WTRU is at the edge of coverage when the WTRU is located close to the edge of the cell. The WTRU may determine that the WTRU is out-of-coverage when the WTRU is neither in-coverage nor at the edge of coverage.
[0075] The WTRU may be configured to initiate evaluation or re-evaluation of multiple D2D operating parameters, for example, when there is a change in the coverage conditions of the WTRU. For example, the D2D operating parameters may include a resource pool, a mode of operation (e.g., a D2D scheduling mode, a D2D operating mode, e.g., a relay WTRU, a remote WTRU, or a normal WTRU), synchronization transmission, synchronization source selection, etc.
[0076] The WTRU may detect a change in coverage conditions by detecting one or more event triggers. The WTRU may detect the triggers based on measurements. For example, the WTRU may be configured to determine its coverage conditions by measuring signals received from one or more base stations (e.g., eNBs). The WTRU may be configured to determine that the WTRU is in-coverage or on the edge of coverage by comparing a measured Reference Signal Received Power (RSRP) value or a Received Signal Strength Indication (RSSI) value of its associated cell (e.g., a serving cell) to one or more thresholds stored in a memory. The WTRU may determine that the WTRU is located in-coverage, for example, if a measured RSRP value or a measured RSSI value exceeds a preconfigured threshold. A measured RSRP value or an RSSI value exceeding a preconfigured threshold may indicate that the signal power is above a threshold. The WTRU may determine that the WTRU is in an out-of-coverage condition based, for example, on the absence of an RSSI or RSRP signal value.
[0077] A WTRU may determine that it is in-coverage, on the edge of coverage, or out-of-coverage by comparing the measured RSRP value of its associated cell (e.g., a serving cell) with the measured RSRP values of one or more cells (e.g., neighboring cells). The WTRU may determine that it is located in-coverage or on the edge of coverage, for example, if it is determined that the RSRP value of its associated cell exceeds the RSRP measurements from other cells by a preconfigured value. The WTRU may determine that the WTRU is in-coverage or on the edge of coverage, for example, when the RSRP value of its associated cell is within a preconfigured range that exceeds a preconfigured range of the RSRP measurements from other cells. The WTRU may determine that the WTRU is in an out-of-coverage condition based, for example, on the absence of an RSSI or RSRP signal value.
[0078] The WTRU may determine whether it is in coverage or at the edge of coverage. The WTRU may determine that it is in coverage or on the edge of coverage based on the presence of hysteresis. The WTRU may determine that it is in coverage or on the edge of coverage based on a triggering time, measurements that the WTR may make over a period of time, etc. The WTRU may be configured to avoid undesirable ping-pong effects. A WTRU that is on the edge of coverage may refer to a WTRU that is close to the edge of the cell with which the WTRU is associated (e.g., the edge of the serving cell).
[0079] The WTRU may be configured to determine the coverage condition of the WTRU based on the event trigger (e.g., by detecting the event trigger). The WTRU may determine that it is in the edge of coverage when the event A3 is triggered with a positive or negative value of the cell range extension (CRE) bias (e.g., an offset value). The WTRU may determine that it is in the edge of coverage by comparing a measured RSRP value or a reference signal received quality (RSRQ) value of its associated cell with a neighboring cell. For example, the WTRU may determine that the WTRU is in the edge of coverage when the difference between the RSRP / RSRQ values of the serving cell and the neighboring cell is equal to or less than the configured CRE bias.
[0080] The WTRU may be configured to determine the coverage condition by detecting an event trigger, which may be based on a D2D resource (grant) request failure. The WTRU may determine that it is on the edge of coverage of a cell when the number of random access channel (RACH) failures reaches a preconfigured threshold. An in-coverage WTRU may transmit RACH, scheduling requests (SRs) and / or buffer status reports (BSRs) to request resources for D2D transmission. The WTRU may determine that it is an edge of coverage condition, for example, when the number of RACH attempts exceeds a preconfigured threshold. The WTRU may be configured to determine that it is an edge of coverage condition, for example, when the number of SRs exceeds a preconfigured threshold. The WTRU may be configured to determine that it is an edge of coverage condition when the WTRU does not receive a grant for a configured time duration since transmitting a first SR that may have triggered a D2D transmission. The WTRU may determine that it is in the edge of coverage, for example, when it does not receive a grant for a preconfigured duration after transmitting a BSR for D2D resources. The WTRU may determine that it is in the edge of coverage, for example, if a retxBSR timer expires after transmitting a BSR for D2D communication. The WTRU may determine that it is in the edge of coverage after a predefined number of retransmissions of the initial BSR. An edge of coverage WTRU may be configured to attempt uplink communication (e.g., periodically attempt).
[0081] The WTRU may determine its coverage condition by detecting an event trigger, which may be based on HARQ A / N feedback. The WTRU may determine that it is an edge of coverage condition, for example, when hybrid automatic repeat request (HARQ) negative feedback on uplink transmissions is above, below, or equal to a configured threshold. For example, an in-coverage WTRU may be configured to determine that it is in the edge of coverage when the number of NACKs received within a particular window (e.g., time period) reaches or exceeds a configured threshold.
[0082] The WTRU may determine its coverage condition by detecting an event trigger, which may be based on an RLF condition. The WTRU may determine that it is in the edge of coverage, for example, if one or more of the specified triggers cause the WTRU to detect a radio link failure (RLF) condition. For example, the WTRU may determine that it is in an edge of coverage condition when an RRC timer is started, e.g., timer T310 or T312 is started or expired. The WTRU may be configured to determine that it is in the edge of coverage based on a preconfigured number of consecutive out-of-sync or in-sync (e.g., N TTIs). The WTRU may determine that it is in the edge of coverage, for example, if a radio resource control (RRC) re-establishment procedure is triggered or initiated. The WTRU may determine that it is in the edge of coverage if a re-establishment timer (e.g., an RRC timer) is started, e.g., timer T311 is started or T301 is started.
[0083] The WTRU may start a timer (e.g., an RRC timer, e.g., an RLF timer), such as timer 311 or timer 301, when an RRC re-establishment procedure is triggered or initiated. The WTRU may determine that it is in edge of coverage, for example, if a command to re-establish RRC is sent. The WTRU may determine that it is in coverage, for example, if the RRC re-establishment procedure is successful. The WTRU may determine that it is an edge of coverage condition when the number of radio link control (RLC) re-transmissions equals or exceeds a preconfigured threshold. The WTRU may determine that it is an edge of coverage condition when the number of radio link control (RLC) re-transmissions is within a preconfigured range of values.
[0084] The WTRU may determine its coverage condition by detecting an event trigger based on cell suitability criteria. The WTRU may determine that it is in an out-of-coverage condition when it cannot find a cell that meets one or more predefined suitability criteria. The WTRU may determine that a cell is suitable, for example, if the cell advertises support for D2D communication. An edge-of-coverage WTRU may determine that it is in an out-of-coverage condition when the WTRU cannot decode a serving cell system information block (SIB), for example, within a predefined time window. For example, the WTRU may determine the coverage condition of the WTRU upon detecting a transition to RRC_IDLE.Any-Cell-Selection.
[0085] The WTRU may determine its coverage condition by detecting an event trigger, which may be based on the D2D synchronization signal / channel. The WTRU may determine that it is in an out-of-coverage condition by detecting one or more neighboring WTRUs that may be able to relay D2D resource pool information. The WTRU may determine that it is in an out-of-coverage condition upon entering a Camped_on_D2DUE state. The Camped_on_D2DUE state may indicate that the D2D-capable WTRU can successfully decode a control message carrying D2D configuration information from a neighboring WTRU.
[0086] An in-coverage WTRU may be configured to begin transmitting synchronization signals and / or messages, for example, once the in-coverage WTRU detects D2DSS from a neighboring out-of-coverage WTRU.
[0087] The WTRU may evaluate and / or re-evaluate whether the WTRU will be a synchronization source and / or relay. The WTRU may select and / or re-select a new synchronization source upon receiving a D2D synchronization signal, e.g., as shown in Figures 5, 6, and 7. The WTRU may evaluate / re-evaluate its master synchronization source, e.g., if the WTRU detects a new neighboring WTRU that is transmitting one or more alternative D2D synchronization signals with better signal strength.
[0088] The WTRU may determine its coverage condition by detecting an event trigger, which may be based on downlink channel conditions. The WTRU may determine its coverage condition based on one or more detected downlink signal errors. The WTRU may detect the event trigger, for example, when a downlink block error rate (DL BLER) is less than, equal to, or exceeds a configured threshold. The WTRU may determine that it is an edge of coverage condition in response to the DL BLER being less than, equal to, or exceeding a configured threshold.
[0089] The WTRU may determine its coverage condition by detecting an event trigger, which may be based on a handover event. The WTRU may determine its coverage condition based on one or more mobility events. The WTRU may detect an event trigger, for example, if a mobility event is triggered (e.g., event A3) or if a (radio resource control) RRC Reconfiguration with mobilityControlInfo message is received, which may cause the WTRU to determine that it is in an edge of coverage condition. The WTRU may determine that it is in an in-coverage condition upon detecting an event trigger, for example, when an RRC Reconfiguration Complete message is successfully sent by lower layers.
[0090] The WTRU may determine its coverage condition by detecting an event trigger, which may be based on a periodic UL procedure. The WTRU may determine its coverage condition by periodically attempting to perform one or more uplink procedures to determine if it can transition from another coverage condition to an in-coverage condition. For example, the WTRU may periodically attempt to perform one or more uplink procedures. The WTRU may determine that it is in-coverage if, for example, the uplink procedures are successful.
[0091] The WTRU may determine its coverage conditions based on its current state information. The WTRU may maintain state information based on its current location relative to the base station or eNB and / or other D2D-enabled WTRUs. The WTRU may select a mode of operation and a resource pool based on the state information. The WTRU may receive an explicit indication of its coverage state, for example, from the network. The WTRU may implicitly determine its coverage state.
[0092] The WTRU may determine its D2D coverage state. A D2D-capable WTRU may be configured, for example, into one of the following states based on its coverage conditions: The state information may be referred to as D2D-CoverageState (D2D_CS). The D2D_CS may include a D2D_CS called In-coverage. A WTRU may be in-coverage when it is in RRC_IDLE and camped on a suitable cell. A WTRU may be in-coverage when it is in RRC_COVECTED mode, is served with a cell that supports D2D services, and the WTRU determines that the conditions for being in edge of coverage are not met.
[0093] The WTRU may determine that it is at the edge of coverage. The D2D CS may include a D2D_CS sub-state called edge-of-coverage. The WTRU may be in the edge-of-coverage state when it has an unreliable link in downlink unicast and / or uplink unicast and / or cannot exchange request / response communications with the base station or eNB. For example, the WTRU may decode DL system information from the base station or eNB because DL system information may be relatively more robust than normal unicast communications. The WTRU may be in an RRC_IDLE state or an RRC_CONNECTED state (e.g., while the WTRU is at the edge of coverage).
[0094] The WTRU may determine that it is out of coverage. The D2D_CS may include a D2D_CS sub-state called Out-of-coverage. The WTRU may determine that it is in an out-of-coverage state when it cannot find a serving cell that meets a cell suitability criterion. The WTRU may determine that it is in an out-of-coverage state when it cannot find a serving cell that supports the D2D service. If the WTRU cannot find a suitable cell and is in the Any Cell Selection state, the WTRU may determine that it is in an out-of-coverage state. The WTRU may be configured to search (e.g., periodically) for a suitable cell in a configured PLMN. An out-of-coverage WTRU may operate in an EMM-REGISTERED.NO-CELL-AVAILABLE state or an EMM-DEREGISTERED.NO-CELL-AVAILABLE state.
[0095] The WTRU may be configured to determine a sub-state. The D2D-capable WTRU out-of-coverage state may include two or more sub-states. For example, a sub-state of the out-of-coverage state may be Camped_on_D2D_UE state. The WTRU may be in Camped_on_D2D_UE state when the WTRU is unable to locate a suitable cell but the WTRU successfully decodes D2D configuration information being transmitted by another WTRU, which may be in-coverage WTRU relay / transmit information from the network. A sub-state of the out-of-coverage state may be No_D2D Source state. The WTRU may be in No_D2D Source state when it is unable to find a suitable cell supporting the D2D service and / or a neighboring WTRU transmitting D2D configuration information.
[0096] 2 is a state transition diagram illustrating an example embodiment in which the D2D_CS state may include, for example, sub-states of an existing state machine. As shown in FIG. 4, the D2D_CS state may be considered a separate state variable or condition. The WTRU may use the D2D_CS state to determine actions that may be taken using existing or newly defined procedures. The WTRU may use the D2D_CS state to determine one or more transmission modes that the WTRU may use when the separate state variable or condition is satisfied.
[0097] A WTRU may be configured to determine its coverage condition by detecting updates regarding a trigger event. A WTRU may be configured to determine its coverage state by detecting an independent trigger. A WTRU may trigger an evaluation / re-evaluation of its coverage condition based on one or more trigger events described herein. For example, when a WTRU is in a particular state, the WTRU may monitor the condition to determine a coverage state or an operating mode to use.
[0098] The WTRU may be configured to determine the coverage state based on a base station or eNB command trigger. The WTRU may trigger an evaluation / re-evaluation of its coverage condition based on a command received from the base station or eNB. Upon successful RLF re-establishment, the base station or eNB may send a command to the edge-of-coverage D2D-enabled WTRU to transition back to an in-coverage state. The WTRU may implicitly determine that it is in the in-coverage state upon completion (e.g., successful completion) of the re-establishment procedure or when performing an RRC connection setup. The WTRU may be configured, for example, to attempt to operate as an in-coverage state upon successful completion of the re-establishment procedure. The transition to in-coverage may trigger the WTRU to send an uplink message (e.g., a service or RRC request, a dedicated RACH request, or a scheduling request). The WTRU may continue to operate as an in-coverage WTRU, for example, if the uplink procedure is successful. If the uplink procedure is unsuccessful, the WTRU may return to an edge of coverage or out of coverage state.
[0099] The WTRU may be configured to perform one or more procedures upon a change in coverage state. For example, upon a change in coverage state, the WTRU may be configured to determine a mode of operation (e.g., a scheduling mode for D2D communication) (e.g., mode 1 or mode 2) that the WTRU may use to acquire D2D resources. For example, the WTRU may detect a change in the edge of coverage, and the WTRU may transition to mode 2 transmission. For example, the WTRU may detect a change in the WTRU's coverage conditions, and the WTRU may assume a role of a master synchronization source (MSS). Assuming the role of the MSS, the WTRU may start transmitting synchronization signals (e.g., D2DSS and / or synchronization messages on the PD2DSCH).
[0100] The WTRU may be configured to perform a resource selection procedure upon detecting a change in coverage conditions. The D2D-enabled WTRU may perform a resource selection procedure to determine resources for D2D transmission and / or reception. The D2D-enabled WTRU may determine the D2D resources to be physical resource blocks (PRBs) in time and frequency for D2D operation. The D2D-enabled WTRU may be configured with one or more D2D resources, such as a D2D resource pool. The D2D-enabled WTRU may select a pattern of transmission and reception opportunities from the resource pool within a defined duration based on the D2D resource selection. The pattern may include a D2D transmission pattern and / or a D2D reception pattern.
[0101] The WTRU may be configured to perform a WTRU resource selection procedure upon entering an in-coverage condition. A D2D-enabled WTRU transitioning from an out-of-network coverage zone or an edge-of-network coverage zone to an in-network coverage zone may be configured to send a report. The report may include a request to perform D2D communications and / or a change of state. The D2D-enabled WTRU may identify the network coverage or condition by a trigger event as described herein.
[0102] A D2D-enabled WTRU transitioning from an out-of-network coverage zone or edge-of-network coverage zone to an in-network coverage zone, or upon handover to a new cell, may stop transmitting in existing resources N from a previous mode of operation (e.g., previous D2D scheduling mode) or cell. For example, a WTRU switching from mode 1 to mode 2 may cease transmitting in existing resources from mode 1. The WTRU may determine a network configuration for a D2D communication mode for a D2D device in a cell (e.g., by reading one or more system information blocks (SIBs) or by using an existing configuration of the cell in the D2D-enabled WTRU). The WTRU may connect (e.g., register) with the network. The D2D-enabled WTRU may, for example, request resources for D2D transmissions after connecting with the network. The WTRU may connect with the network if the WTRU is configured for mode 1. If no configuration is available, the WTRU may connect with the network. For example, if a cell indicates that it is D2D capable, the WTRU may connect with the network. The WTRU may stop using Mode 2 transmission resources that the WTRU may have used when in an out-of-network coverage zone or an edge-of-network coverage zone.
[0103] A D2D-enabled WTRU transitioning from an out-of-network coverage zone or an edge-of-network coverage zone to an in-network coverage zone may identify the resource M, resource pattern, and / or allowed transmission pattern for in-coverage transmissions, for example, based on one or more of the following: The WTRU may use a predefined mapping between N and M signaled on the SIB. The WTRU may use a configured or received (e.g., from the SIB of the eNB, if available, or via RRC signaling) transmission resource pool. For example, if there is an explicit indication by the network to continue the existing configuration, the WTRU may continue to use the previous transmission pool. The WTRU may use an explicit indication received from the network (e.g., via RRC signaling, or via a media access control (MAC) control element (CE), or via a physical downlink control channel (PDCCH) using special downlink control information (DCI)). The WTRU may use the configured transmission resource pool or transmission opportunity pattern from the eNB.
[0104] A D2D-enabled WTRU transitioning from an out-of-network coverage zone or an edge-of-network coverage zone to an in-network coverage zone may identify new resources, time patterns, and / or allowed reception opportunities for in-coverage reception, for example, based on at least one of the following: The WTRU may identify resources using an explicit reception resource pool received from the network (e.g., via RRC signaling, via MAC CE, or via PDCCH using a special DCI). The WTRU may identify a pre-configured resource pool for reception based on a provided configuration and / or resources using a pre-defined mapping (e.g., a time pattern calculated based on a WTRU-specific identifier). A D2D-enabled WTRU transitioning from an out-of-network coverage zone or an edge-of-network coverage zone to an in-network coverage zone may send a report to the eNB indicating the result of the resource selection process, for example, based on the procedures described below.
[0105] The WTRU may perform a resource selection procedure upon entering a coverage edge condition. A WTRU transitioning from an in-network coverage zone to an edge zone of network coverage may be configured to identify network coverage, for example, by detecting a trigger event as described herein. The WTRU may stop transmitting in the existing resource N or may stop transmitting when the grant expires (e.g., at the end of the scheduling period). The WTRU may read a system information block (SIB) and determine the network configuration for the D2D communication mode. For example, if the WTRU is configured or permitted to operate in Mode 2, or if no configuration is available, the WTRU may select Mode 2.
[0106] A WTRU transitioning from an in-network coverage zone to an edge of network coverage zone may identify new resources M for edge of coverage transmission, for example, based on at least one or more of the following: The WTRU may identify new resources based on a predefined mapping between N and M signaled on the SIB. The WTRU may identify new resources based on a resource configuration from the SIB. The WTRU may identify new resources based on a preconfigured resource pool for transmission. The WTRU may identify new resources based on a time pattern (e.g., a transmission pool) to be used for transmission. The WTRU may determine a time pattern from the SIB, a preconfigured pattern, and / or a predefined mapping (e.g., a time pattern calculated based on a WTRU-specific identifier) based on a provided configuration. A WTRU transitioning from an in-network coverage zone to an edge of network coverage zone may identify new resources for edge of coverage reception, for example, based on at least one or more of the following: The WTRU may identify new resources based on a resource configuration from the SIB. The WTRU may identify new resources based on a preconfigured resource pool for reception. The WTRU may identify new resources based on a time pattern to be used for transmission. The WTRU may select a timing pattern derived from the SIB, a preconfigured pattern, and / or a predefined mapping (e.g., a time pattern calculated based on a WTRU-specific identifier) based on the provided configuration.
[0107] A WTRU that has transitioned from an in-network coverage zone to an edge of network coverage zone may, for example, initiate a UL message to determine a change in the current state (e.g., to determine whether the WTRU may return to an in-coverage mode). Initiating the UL message may include reading the SIB to determine the periodic message configuration (e.g., RACH configuration, periodic BSR configuration, timeout window duration, gap between successive attempts, etc.). Initiating the UL message may include performing a periodic transmission to the network having the configured configuration.
[0108] The WTRU may be configured to perform a resource selection procedure upon entering the Out-Of-Coverage state. A WTRU transitioning from an in-network coverage zone to an edge zone of network coverage may identify the network coverage as described herein. The WTRU may stop transmitting in the existing resource N or using an existing scheduling mode and determine a new set of resources and a new scheduling mode to use. The WTRU may listen to neighboring eNBs and check suitability. The suitability check may include checking whether the cell supports D2D services. In the event that no suitable cell is found, the WTRU may listen to any neighboring D2D synchronization signals. The WTRU may evaluate the suitability of the D2DSS based on one or more D2D WTRU suitability criteria. The suitability criteria may include source ID priority (e.g., if source ID is prioritized), hop count, etc. A WTRU transitioning from an in-network coverage zone to an edge zone of network coverage may start performing a Mode 2 transmission procedure. The WTRU may identify new resources M for out-of-coverage or edge-of-coverage transmissions, for example, based on at least one of the following: The WTRU may identify new resources based on a predefined configuration for the scheduling assignment and the D2D transmission. For example, the WTRU may receive the configuration by reading the SIB. The WTRU may identify new resources based on a time pattern (e.g., a time pattern calculated based on a WTRU-specific identifier) to be used for transmission of a predefined mapping based on the provided configuration. The WTRU may identify new resources based on a preconfigured pattern (e.g., a preconfigured transmission pool), for example, if provided.The WTRU may identify new resources for in-coverage reception based on, for example, at least one of a pre-configured resource pool for reception, a time pattern to be used for reception, a pre-defined mapping based on a provided configuration (e.g., a time pattern calculated based on a WTRU-specific identifier), and / or a pre-configured pattern.
[0109] The WTRU may initiate a UL message to determine a change in the current state. The WTRU may initiate a UL message by reading the SIB to determine the periodic message configuration (e.g., RACH configuration, periodic BSR configuration, timeout window duration, gap between successive attempts, etc.) and attempting periodic transmissions to the network with the configured configuration.
[0110] The WTRU may be configured to select a type of power control mode upon a change in coverage. The WTRU may be configured with one or more power control modes to operate with D2D communications.
[0111] The WTRU may be configured with a closed-loop power control mode. For example, a node (e.g., an eNB, a cluster head, or a controlling node, etc.) may control the WTRU transmit power for D2D communication and / or discovery. The WTRU may select a power control mode that may be based in part on a closed-loop approach. For example, the WTRU may receive a power control signal indication from a node (e.g., an eNB, a cluster head, or a controlling node, etc.) with a power control command. The WTRU may receive the power control signal, etc., for example, as part of a D2D communication grant control signal (e.g., via a PDCCH, ePDCCH, and / or other control signal).
[0112] The WTRU may be configured with an open-loop power control mode (e.g., with respect to a reference node). The WTRU may determine its power based on one or more measurements, such as RSRP, from a node (e.g., a reference node, a controlling node, an eNB, a D2D WTRU, a synchronization source, a cluster head, etc.). For example, the WTRU may estimate a path loss to a node based on measurements and a node transmit power value, which may be pre-configured or determined based on control signaling, such as a SIB in the case of an eNB. The WTRU may adjust the power to reach a minimum or maximum received power at the node. The WTRU may be configured with a power control mode based on parameters (e.g., on a USIM). The node (e.g., an eNB, a D2D WTRU, a synchronization source, a cluster head, etc.) may configure parameters for power control, for example, via RRC signaling or on a SIB.
[0113] The WTRU may be configured with a fixed power control mode. The WTRU may be configured with a fixed transmit power. The WTRU may be configured with a transmit power parameter, e.g., from the USIM or via RRC / SIB. The transmit power parameter may be fixed. For example, the WTRU may be configured with multiple fixed transmit power parameters, e.g., with individual values associated with configured ranges of operation of the D2D service. The WTRU may select a value within multiple transmit power values, e.g., based on the configured range. The discovery service may be configured with a range of operation (e.g., short, medium, long). The WTRU may select a transmit power for transmitting a D2D discovery payload, e.g., based on the range of operation. The WTRU may obtain the range of operation and / or the D2D discovery payload as an indication from higher layers.
[0114] The WTRU may be configured to perform power control related actions when changing coverage conditions. The WTRU may be configured, for example, to determine a D2D power control mode based on the D2D WTRU coverage conditions.
[0115] The communication between the WTRU and the eNB may be applicable to communication between the WTRU and a node such as a resource node, a control node, a cluster head, a synchronization source, a D2D WTRU, etc. The communication between the WTRU and a node such as a resource node, a control node, a cluster head, a synchronization source, a D2D WTRU, etc. may be applicable to communication between the WTRU and the eNB.
[0116] The WTRU may be configured to change its power control mode to a fixed power control mode, such as when it moves out of coverage. The WTRU may be configured to autonomously change its power control mode (e.g., when it detects that it is out of network coverage or outside a node and / or a reference node). For example, the WTRU may be configured to autonomously change its power control mode to a fixed power control mode, such as when it moves out of coverage. The WTRU may be configured to determine power control parameters from a configuration. The WTRU may be configured to maintain parameters configured by the network. The WTRU uses configuration parameters forwarded from an in-coverage D2D WTRU, such as provided by a node (e.g., an eNB, a controlling node, a reference node, a cluster head, a D2D WTRU, a synchronization source, etc.) associated with the in-coverage WTRU.
[0117] FIG. 3 may show an example system diagram in which a WTRU determines a power control mode based on a SIB when moving to the edge of coverage or in-coverage. The WTRU may be configured to determine a power control mode based on a SIB when moving to the edge of coverage and / or in-coverage. The WTRU may be configured to autonomously change its power control mode when it detects that it moves within the coverage of a node (e.g., an eNB, a controlling node, a reference node, a cluster head, a D2D WTRU, a synchronization source, etc.). For example, the WTRU may be configured to change its power control mode to an open-loop power control mode (e.g., a reference node power control mode) with the nearest eNB and / or a serving eNB as the reference node. The WTRU may use power control parameters received from the SIB, from the eNB, or from the broadcast control of the node.
[0118] The WTRU may determine the power control mode to use when moving within the coverage of a node (e.g., an eNB, a controlling node, a reference node, a cluster head, a D2D WTRU, a synchronization source, etc.) by reading the configuration in the SIB. The WTRU may receive an indication on the SIB to use fixed power control with associated parameters such as power parameters for SA transmissions, D2D data, and / or discovery transmit power.
[0119] The WTRU may be configured, via the SIB, to use, for example, closed-loop power control. The WTRU may be configured, for example, to attempt to connect to a node (e.g., an eNB, a controlling node, a reference node, a cluster head, a D2D WTRU, a synchronization source, etc.) when using closed-loop power control. The WTRU may be configured to use open-loop power control with parameters configured on the SIB, for example, in the event of a connection failure or during the time that the WTRU is attempting to connect.
[0120] The WTRU may be configured, for example, via the SIB to use open loop power control, with parameters signaled on the SIB.
[0121] The WTRU may be configured to determine a power control mode based on a configuration from the network, e.g., when in coverage. The WTRU may be configured to connect to the network. The WTRU may be configured to receive a power control configuration, e.g., via dedicated RRC signaling, such as when the WTRU moves within network coverage. The WTRU may be configured to use fixed power control, e.g., during times when the WTRU is not connected. The WTRU may be configured to use parameters signaled on the SIB, e.g., during times when the WTRU is not connected.
[0122] The WTRU may be configured to determine the power control mode based on the D2D mode of operation (e.g., the D2D scheduling mode, e.g., mode 1 or mode 2). For example, the WTRU may evaluate and / or select a power control mode that may be used when the WTRU changes the D2D mode of operation. The WTRU may move from closed-loop power control to open-loop power control and / or fixed power control, for example, when the WTRU switches from mode 1 to mode 2 (e.g., when the RRC connection is released). The WTRU may use parameters signaled on the SIB, for example, when the WTRU switches from mode 1 to mode 2 (e.g., when the RRC connection is released).
[0123] The WTRU may be configured to determine the power control mode based on the role transition. The WTRU may evaluate and select a power control mode that may be used when the WTRU starts operating, for example, as a synchronization source or cluster head, or stops operating as an MSS or cluster head. For example, the WTRU may be operating in a closed power control mode that obtains at least a portion of the transmit power parameters from a reference node, such as when the WTRU is operating as a general WTRU obtaining synchronization from a reference node (e.g., a synchronization source or cluster head). The WTRU may change the power control mode to fixed power control, for example, due to changing conditions, such as when the WTRU decides to start operating as a synchronization source. The WTRU may use parameters configured in the WTRU, for example, due to changing conditions, such as when the WTRU decides to start operating as a synchronization source.
[0124] The WTRU may be configured to select a mode of operation (e.g., a scheduling mode for D2D communication). When the WTRU is in RRC_CONNECTED state, the WTRU is performing D2D communication using mode 1 scheduling (e.g., an eNB schedules D2D transmissions), and the WTRU detects a connection problem, the WTRU may determine that a radio link failure (RLF) condition has occurred based on existing triggers. The WTRU may attempt to restore the link (e.g., by attempting to perform a re-establishment). However, there may be some delay while the WTRU is attempting to restore the link. For example, repeated out-of-sync indications in the downlink may trigger an RRC timer (e.g., an RLF timer, e.g., timer T310 or timer T312), which may have a large value (e.g., up to 2s). The threshold for detecting an uplink problem may include a large value that avoids frequent ping-pong when the WTRU cannot communicate with the network, cannot obtain a grant for D2D, and / or cannot perform important D2D communication, which may lead to long delays. To avoid such interruptions, the D2D WTRU may continue to operate during this time frame. The WTRU may be configured to determine the problem (e.g., by detecting that T310 is running) and transition to Mode 2 resource selection.
[0125] The base station or eNB and the WTRU may determine a change in conditions and trigger the WTRU to change its procedures to acquire D2D resources. The WTRU may determine a change in conditions and trigger the WTRU to change its procedures to acquire D2D resources (e.g., switch from Mode 1 to Mode 2).
[0126] The WTRU may evaluate / re-evaluate the D2D mode of operation based on a trigger (e.g., a condition). The WTRU may be configured to select a scheduling mode based on an independent trigger. The WTRU may trigger evaluation / re-evaluation of its mode of operation (e.g., Mode 1 or Mode 2) based on one or more trigger events (e.g., conditions) described herein. When the WTRU detects (e.g., determines) that it is in an out-of-coverage state, the WTRU may use Mode 2 resources. When the WTRU cannot find a cell that meets a cell suitability criterion and / or when the WTRU cannot detect a cell, the WTRU may determine that it is in an out-of-coverage state. For example, the WTRU may use Mode 2 resources when it is unable to decode a serving cell SIB within a predefined time window. When the WTRU transitions to RRC_IDLE.Any-Cell-Selection, the WTRU may use Mode 2 resources. When the WTRU determines to change the coverage state based on starting or expiring an RRC timer (e.g., timer T300), the WTRU may use Mode 2 resources. When the WTRU determines that a re-establishment procedure has been initiated (e.g., when an RRC timer starts or expires, e.g., when T311 or T301 starts or expires), the WTRU may use Mode 2 resources. If the RRC Connection Request procedure fails, the WTRU may use Mode 2 resources.
[0127] The WTRU may be configured to perform a mode selection / switching procedure based on an attempt / fallback method. If D2D resources are used, the WTRU may attempt to use a mode configured by the base station or eNB. If the WTRU is not successful in acquiring resources within the configured duration, the WTRU may fall back to a semi-static or pre-configured resource pool using Mode 2.
[0128] A WTRU camped on a suitable serving cell (e.g., RRC_IDLE or RRC_CONNECTED) may be configured to begin D2D resource selection by using Mode 1. When new D2D data arrives, the WTRU may initiate a request to obtain resources from the base station or eNB. If the procedure is unsuccessful, the WTRU may attempt to use Mode 2 with a resource pool configured using broadcast signaling. If resources are not available in the broadcast signaling or are not configured (e.g., explicitly) for Mode 2 operation, the WTRU may not perform D2D operation. If resources are not indicated or the WTRU is unable to decode the SIB, it may transition to Mode 2 with a preconfigured resource pool.
[0129] The WTRU may be configured to establish an RRC connection and may request resources for D2D operation. The WTRU may be configured to establish an RRC connection by receiving a signal from the eNB on the SIB D2D configuration. When D2D data (e.g., new D2D data) arrives, the WTRU in RRC_IDLE mode may initiate an RRC connection establishment procedure. If the RRC connection establishment procedure is unsuccessful, the WTRU may attempt to use the configured Mode 2 resources. The WTRU may use the configured Mode 2 resources under specified conditions, such as one or more of the following conditions:
[0130] The WTRU may be configured to operate in Mode 2 and use Mode 2 resources when a timer is running or has expired, e.g., when T300 is running or has expired (e.g., upon transmission of an RRCConnectionRequest). The WTRU may use Mode 2 resources upon receipt of an RRC Connection Reject. The WTRU may use Mode 2 resources when T302 (e.g., TBarring) is running (e.g., upon receipt of an RRCConnectionReject while performing an RRC connection establishment). The WTRU may use Mode 2 resources when T303 or T305 is running (e.g., when access is barred while performing an RRC connection establishment for a mobile originating call or signaling). For example, the WTRU may use Mode 2 resources if the WTRU is configured to inform higher layers about an RRC connection establishment failure. The WTRU may use Mode 2 resources when an access barring check in the RRC determines the cell to be barred and / or after a timer (e.g., a new timer) has expired. The timer may have been started at the beginning of the RRC connection request. The timer may start when the RRC connection request is initiated. The timer may be stopped when an RRC connection setup is received. Upon receipt of the RRC connection setup or an indication from higher layers to stop transmission, the WTRU may use Mode 1 operation or a network provided configuration.
[0131] For example, the WTRU may send a BSR requesting a grant for D2D transmission. For example, if the WTRU does not receive a response from the eNB in time, the WTRU may attempt to use Mode 2. For example, a timer may start when the BSR is triggered and / or sent. The WTRU may be triggered to transition to Mode 2, for example, by expiration of the timer. The WTRU may be triggered to transition to Mode 2 by expiration of a timer, such as retxBSR-Timer. For example, after several retransmissions of the D2D BSR, the WTRU may begin Mode 2.
[0132] The WTRU may send an SR requesting a grant, for example, as a result of a triggered D2D BSR. For example, if the WTRU does not receive a PUSCH resource to transmit a BSR, the WTRU may transition to using Mode 2. For example, if a D2D BSR over a defined duration does not include an assembled MAC PDU, the WTRU may transition to using Mode 2. A timer may be started when a D2D BSR is triggered and / or an SR is transmitted. Expiration of the timer may trigger the WTRU to transition to Mode 2. For example, if the WTRU retransmits an SR more than a configured amount of time, the WTRU may transition to Mode 2. The WTRU may be triggered to transition to Mode 2 transmission by expiration of an sr-Prohibit timer. For example, a WTRU using Mode 2 transmission may be configured to attempt (e.g., periodically attempt) uplink communication. The WTRU may be configured to periodically attempt UL communication, such as when it is still in connected mode and / or when the network has configured it for Mode 1 transmission. The WTRU may retry communication (eg, periodically and / or when a BSR is triggered). The WTRU may wait a period of time before attempting communication.
[0133] The WTRU may be configured to perform a mode selection / switching procedure based on resource grant duration expiration. For example, if the mode selection / switching procedure is not triggered by resource grant duration expiration, the WTRU may detect resource grant deactivation. For example, if D2D resources are used, the WTRU may be configured with information regarding the mode selection. For example, when D2D resources may be disabled and / or may become disabled, the WTRU may be configured with information regarding the resource pool. For example, the WTRU may be configured with D2D resources that may be valid for a duration (e.g., a time duration during which the resources may be considered valid). The WTRU may be configured to perform a mode switch, for example, when the duration expires. The duration may be configured, for example, in terms of time, number of frames, number of subframes, as a resource time pattern, etc. The WTRU may be configured to switch modes, for example, from Mode 1 to Mode 2, such as when Mode 1 resources are deactivated by the network.
[0134] The WTRU may switch from Mode 1 to Mode 2 based on lack of response to a BSR transmission. For example, the WTRU may send a BSR requesting a grant for D2D transmission. If the WTRU does not receive a response from the eNB in time, for example, the WTRU may attempt to use Mode 2. A timer may start when the BSR is sent. The WTRU may be configured to transition from Mode 1 to Mode 2 upon expiration of an existing timer, retxBSR-Timer.
[0135] The WTRU may be configured to perform mode selection / switching procedures based on RRC state transitions. If D2D resources are used, the WTRU may be configured with rules for mode and resource pool selection based on the RRC state. The WTRU may be configured to operate in mode 2 when it is in RRC_IDLE mode. The WTRU may be configured with rules that take precedence over modes defined by the base station or eNB.
[0136] The WTRU may be configured to perform a mode selection / switching procedure based on a change in the D2D Coverage-State. The WTRU may be configured with rules for mode and resource pool selection based on the current D2D Coverage-State. The WTRU may detect the state change based on one or more trigger events described herein.
[0137] When a WTRU determines that it is in-coverage, it may be configured to obtain a resource pool and mode configuration for D2D transmission. The WTRU may receive resource pool and mode configuration information via an informed configuration, which may be received from a base station or eNB. A WTRU operating within the edge of coverage may be configured to obtain resource allocation from the network and perform autonomous resource selection for D2D transmission. A WTRU operating in an out-of-coverage state (e.g., No_D2D_Source_Available) may use a pre-configured resource allocation and perform autonomous resource selection. A WTRU operating in Out-of-Coverage.Camped_on_another_UE may obtain a resource pool for control messages from one or more neighboring WTRUs and perform autonomous resource selection from the control configuration.
[0138] The WTRU may be configured to perform mode selection / switching based on one or more base station or eNB commands. The base station or eNB may send a Mode Selection command with a Mode to be used in the cell using dedicated or broadcast signaling. The base station or eNB may send a Mode Selection command with a Mode plus one or more resources to be used for the WTRU in the cell using dedicated or broadcast signaling. The base station or eNB may send the Mode Selection command as an RRC message, a Layer 2 message, and / or a Layer 1 message (e.g., PDCCH). The WTRU may request resources from the network in Mode 1. The network may send a Layer 1 message that may indicate to the WTRU to transition to Mode 2. The network may indicate (e.g., explicitly indicate) to the WTRU whether to attempt Mode 1 or Mode 2 operation. When the WTRU is configured for Mode 1 operation, one or more conditions described herein may trigger the WTRU to transition to Mode 2 operation.
[0139] When an in-coverage WTRU is triggered to perform D2D communication, the WTRU may send a request to the base station or eNB requesting one or more resources, and the base station or eNB may respond with a mode (e.g., mode 1 or mode 2) in which the WTRU may operate.
[0140] The WTRU may receive rules to perform mode selection for D2D communication. For example, the base station or eNB may use broadcast signaling to inform all WTRUs in the cell of the rules indicating the modes that may be used.
[0141] The WTRU may be configured to perform mode selection / switching based on UL success. For example, a WTRU operating in Mode 2 may be configured to evaluate / re-evaluate the resource selection mode when the RACH is successful. A WTRU operating in Mode 2 may be configured to evaluate / re-evaluate the resource selection mode when a UL grant is received within a configured duration after a scheduling grant is sent.
[0142] The WTRU may be configured to perform mode selection / switching based on time alignment timer (TAT) expiration. For example, a WTRU operating in mode 1 may be configured to evaluate / re-evaluate modes when the WTRU loses timing with the network. The WTRU may be configured to transition to mode 2, for example, when the WTRU is triggered by expiration of the TAT (e.g., timeAUgnmentTimer).
[0143] The WTRU may be configured to perform other procedures after selecting a scheduling mode for D2D communication: A Mode 2 WTRU may select a pre-configured resource pool or resources configured by the base station or eNB.
[0144] A change in WTRU mode selection may trigger the WTRU to send an indication to a node, for example, so that the network may release resources. For example, the WTRU may send an indication to the eNB, such as when the WTRU moves from Mode 1 to Mode 2. The indication to the eNB may include a pattern that the WTRU may use when it begins Mode 2 operation. A WTRU configured with active Mode 1 (e.g., semi-static) resources may not use and / or need the resources at the time (e.g., when data is still no longer being transmitted). The WTRU may autonomously release and / or deactivate resources (e.g., Mode 1 resources) when configured, for example, in Mode 2. The WTRU may send an indication to the eNB that the WTRU has released the resources. The WTRU may wait for an indication by the network to release the resources. The eNB may release resources and / or provide an indication to the WTRU that it may release and / or deactivate resources, such as upon an indication from the WTRU that the resources are no longer occupied and / or needed. The indication may enable the eNB to perform management of the resources.
[0145] The WTRU may be configured to release the Mode 1 resources by releasing the grant and / or not performing a D2D transmission (e.g., when the WTRU has no data to transmit but may have an active grant). For example, the WTRU may have the MAC CE indicate to the network that it has released the Mode 1 resources. The WTRU may use a buffer status report with a small buffer size (e.g., set to zero) to indicate that the WTRU may not use the resources and / or has released the grant. In some examples, the WTRU may send an indication when it releases the resources (e.g., after impUcitReleaseAfter consecutive MAC PDUs, each containing a zero MAC SDU, have been provided for D2D data traffic), such as for semi-persistent resource allocation.
[0146] The WTRU may be configured with one to more procedures to change the scheduling mode for D2D communication. As described herein, the WTRU may be configured by the eNB to use Mode 1 resources (e.g., using RRC signaling) and may start using Mode 2 resources in response to one or more conditions described herein. The one or more conditions may include resource configuration, allowed application type, allowed usage area, index ID, control, and / or data usage. The one or more conditions may include activation / deactivation triggers, time windows, measurement-based triggers, and / or cell range extension-based triggers. The one or more conditions may include D2D resource grant request failure, HARQ A / N feedback. The one or more conditions may include a trigger based on an RLF condition. The WTRU may be configured to detect an RLF condition by detecting that a timer (e.g., an RRC timer, timer 310, timer 311, and / or timer 301) is running or started. The one or more conditions may include cell suitability criteria, D2D synchronization signals / channels, downlink channel conditions, handover events, and / or trigger periodic uplink procedures. The WTRU may be configured to use and / or request Mode 1 resources unless a failure condition is detected.
[0147] A WTRU in connected mode may be configured with a procedure for changing the scheduling mode for D2D communication. The one or more triggers may indicate starting to perform Mode 2 operation and / or may indicate that the WTRU is in a failure condition (e.g., a Radio Link Failure (RLF) condition, e.g., when an RRC timer (e.g., an RLF timer, e.g., T310, T311, or T301) is running or started).
[0148] An RRC_CONNECTED WTRU may be configured to detect a failure condition (e.g., by detecting an RLF condition, e.g., an RRC timer is running). When an RRC_CONNECTED WTRU has D2D data to transmit and is configured to request Mode 1 resources, the RRC_CONNECTED WTRU may detect a failure condition if it is unable to acquire Mode 1 resources due to one or more conditions or triggers described herein. For example, an RRC_CONNECTED WTRU may detect a failure condition (e.g., a condition to switch from Mode 1 to Mode 2) when one or more of the following conditions are met: The RRC_CONNECTED WTRU may detect a condition upon failure to receive a grant after a predefined duration after a D2D BSR is sent. The RRC_CONNECTED WTRU may detect a condition upon failure to receive a grant after a predefined duration after a D2D SR is sent. An RRC_CONNECTED WTRU may detect the condition when one or more RLF triggers are met (e.g., RACH failure, RLC retransmission failure, etc.). An RRC_CONNECTED WTRU may detect the condition when T310 is running (e.g., detecting N asynchronous TTIs) or has expired. An RRC_CONNECTED WTRU may detect the condition when T311 is running (e.g., detecting that an RRC connection re-establishment procedure has been initiated). An RRC_ CONNECTED WTRU may detect the condition when T301 is running (e.g., detecting that a request to re-establish an RRC connection has been sent).
[0149] When the WTRU detects a failure condition (e.g., a condition to switch from Mode 1 to Mode 2), the WTRU may initiate Mode 2 operation. The WTRU may detect a failure condition and initiate Mode 2 operation, for example, if an RRC re-establishment procedure is initiated while the WTRU has UL D2D data to transmit (e.g., an RRC timer is running, e.g., T311 or T301 is running).
[0150] A WTRU in Mode 2 operation may continue to use Mode 2 until one or more of the following conditions occur: the WTRU has data to send, the WTRU receives an RRC re-establishment message from the network and completes the re-establishment, the WTRU receives an RRC re-establishment message, T301 stops, the WTRU transitions to idle mode (e.g., when an RRC timer stops or expires, e.g., when T311 or T301 stops or expires, or when an RRC connection rejection occurs), and / or a timer expires and the WTRU attempts to access the network (e.g., retries) or attempts a grant request (e.g., retries).
[0151] The WTRU may be configured to stop operating in Mode 2 upon successful re-establishment. Upon successful reception of the re-establishment message, the WTRU may stop using Mode 2 operation and may stop D2D data transmission until an explicit configuration is received from the serving eNB. The RRC re-establishment message may include D2D configuration information. The WTRU may continue D2D data transmission with the D2D configuration information included in the RRC re-establishment message.
[0152] The WTRU may use Mode 2 resources until RRC re-establishment is successful. Upon successful reception of the re-establishment message, the WTRU may continue with Mode 2 operation until the WTRU successfully completes RRC re-establishment (e.g., an RRC re-establishment complete message is sent). Upon completion of the re-establishment procedure, the WTRU may start operating using the configuration provided in the re-establishment procedure. If the re-establishment procedure is unable to provide a D2D configuration (e.g., a new D2D configuration) upon completion of the re-establishment procedure, the WTRU may stop performing D2D data transmission until an explicit configuration is received in the RRC configuration message (e.g., if the cell indicates that the WTRU should request Mode 1 operation). Upon completion of the re-establishment procedure, the WTRU may continue to use Mode 2 until an RRC reconfiguration message provides the WTRU with a D2D configuration to use.
[0153] The WTRU may be configured to transition to idle mode upon unsuccessful re-establishment. If the re-establishment procedure is unsuccessful and the WTRU transitions to idle mode, the WTRU may perform one or more of the following: If the re-establishment procedure is unsuccessful and the WTRU transitions to idle mode, the WTRU may continue to perform Mode 2 operation (e.g., if data is still unavailable) and may inform one or more higher layers of the unsuccessful re-establishment (e.g., failure). If the re-establishment procedure is unsuccessful and the WTRU transitions to idle mode, the WTRU may inform one or more higher layers that D2D data transmission is ongoing. The one or more higher layers may trigger a service request (e.g., a new service request) and an RRC connection establishment procedure (e.g., a new RRC connection establishment procedure) where the D2D data is being transmitted using Mode 2. If the re-establishment procedure is unsuccessful and the WTRU transitions to idle mode, the WTRU may stop D2D data transmission, may stop operating in Mode 2, and may notify one or more higher layers of the unsuccessful re-establishment (e.g., failure). The one or more higher layers may initiate (e.g., immediately) an RRC connection request requesting service for the D2D application. If the re-establishment procedure is unsuccessful and the WTRU transitions to idle mode, the WTRU may perform one or more of the WTRU procedures for idle mode described herein.
[0154] The WTRU may be configured to detect an idle mode failure condition. When the WTRU is in idle mode, the WTRU may trigger Mode 2 operation and / or the WTRU may detect a failure condition. When the RRC_IDLE WTRU has D2D data to transmit and is configured to request Mode 1 resources, the WTRU may initiate an RRC connection request to request D2D service and configuration. The WTRU may not be able to successfully perform an RRC connection and may not be able to perform D2D data transmission. The WTRU may detect a failure condition (e.g., a condition to switch from Mode 1 to Mode 2) when one or more of the following conditions are met: The WTRU may detect the condition when T300 expires (e.g., a request to establish an RRC connection was unsuccessful). The WTRU may detect a condition upon receipt of an RRC connection rejection or an RRC connection release, or when T302 or Tbarring is running (e.g., an RRCConnectionReject message is received while performing an RRC connection establishment). The WTRU may detect the condition when an access barring check in the RRC determines that the cell is barred. The WTRU may detect the condition when T303 or T305 is running (e.g., when access is barred while performing an RRC connection establishment for a mobile originating call or signaling). The WTRU may detect the condition if the WTRU must notify one or more higher layers about an RRC connection establishment failure. The WTRU may detect the condition after expiration of a timer started at the initiation of an RRC connection request. The timer may start when the RRC connection request begins. The timer may be stopped when an RRC connection setup message is received.
[0155] The WTRU may select from Mode 2 resources identified by the network. When the WTRU is in idle mode, the WTRU may start using Mode 2 using broadcast Mode 2 resources. The WTRU may start using Mode 2 operation upon detection of one or more failure conditions described herein. The network may broadcast a set of Mode 2D 2D resources that a WTRU in a failure condition may utilize in idle mode. For example, a set of Mode 2D 2D resources may be reserved for use by a WTRU in a failure condition (e.g., a WTRU not experiencing a failure condition may not be permitted to use these resources). The network may broadcast an indication that the WTRU uses Mode 1 under normal conditions (e.g., attempts to connect to the network).
[0156] When the WTRU is in idle mode, the WTRU may start using pre-configured Mode 2 resources. For example, the network may not broadcast Mode 2 resources (e.g., if the network commands all idle mode WTRUs to perform Mode 1 access). When the WTRU is in idle mode, the WTRU may begin D2D data transmission using a set of pre-configured resources to transmit (e.g., not stop) a higher priority D2D data transmission (e.g., D2D emergency data service, e.g., public safety service). When performing D2D data transmission using a set of pre-configured resources, the WTRU may be configured to readjust the network's resources back to monitor and ensure proper reception of paging messages.
[0157] When the WTRU is in idle mode, the WTRU may retry the RRC connection request access with an RRC retry timer (e.g., new RRC retry timer). For example, a timer (e.g., D2D exception state timer) may be defined by the network or the WTRU to retry connecting to and / or requesting the network, e.g., requesting D2D resources from the network. The timer may start when one or more of the triggers described herein are met. When the timer is started, the WTRU begins to use configured Mode 2 resources (e.g., Mode 2 resources configured for use during an exception scenario). Upon expiration of the timer, the RRC may be configured to retry sending a request in the uplink to establish a connection (e.g., RRC_IDLE) or request a grant (e.g., RRC_CONNECTED). The RRC may be configured to start the timer and continue to retry connecting to the network for a preconfigured number of times (e.g., max attempts) before informing one or more higher layers of the failure.
[0158] When the WTRU is in idle mode, the WTRU may interact with higher layers upon RRC connection establishment failure. When the WTRU is in RRC_IDLE mode and fails to establish a connection to the network (e.g., the WTRU detects the failure due to any of the conditions specified herein), the WTRU may be configured to indicate the failure to one or more higher layers (e.g., NAS or ProSe client) and may start performing D2D data transmission using Mode 2 resources. The WTRU may inform one or more higher layers that the WTRU is configured to perform D2D data transmission using Mode 2 even if the one or more higher layers (e.g., NAS or ProSe client) may not have received a service request response. The one or more higher layers (e.g., NAS or ProSe client) may retry the connection based on existing mechanisms (e.g., while allowing the application to continue transmitting). The WTRU may be configured to continue using Mode 2 resources until Mode 1 resources are available (e.g., until RRC connection establishment is successful in a cell that supports D2D communication).
[0159] When the WTRU is in idle mode upon RRC connection establishment failure and the WTRU interacts with one or more higher layers, the WTRU may continue Mode 2 transmission of D2D data until one or more of the following conditions are met: The WTRU may continue Mode 2 transmission of D2D data until a subsequent successful completion of the RRC connection request. Upon completion of the RRC connection, the WTRU may act according to the serving cell configuration or a provided dedicated configuration (e.g., Mode 1 or Mode 2). The WTRU may continue Mode 2 transmission of D2D data until an RRC connection request message (e.g., a new RRC connection request message) is initiated. The WTRU may stop using Mode 2 and may stop performing D2D transmission until the procedure is successful or one or more of the failure conditions described herein are met. The WTRU may continue Mode 2 transmission of D2D data until no D2D data is transmitted for a predefined period of time. One or more higher layers (e.g., NAS or application layer) may be notified that the WTRU has stopped Mode 2 transmission. If new data arrives, a service request (e.g., a new service request) may be triggered. If an application is terminated by the user, the WTRU may continue Mode 2 transmission of D2D data when the WTRU moves out of Mode 2 transmission. An application (e.g., a new application) or data (e.g., new data) may trigger the WTRU to initiate an RRC connection request. The WTRU may continue Mode 2 transmission of D2D data until there is no D2D data in the WTRU D2D transmission buffer.
[0160] The WTRU may be configured with power control procedures that the WTRU may execute when changing a scheduling mode in D2D communications. The WTRU may be configured to determine a power control mode of operation when the WTRU detects a change in a D2D mode of operation. Methods and procedures related to power control when the WTRU changes coverage conditions may be applicable to situations in which the WTRU changes its D2D mode of operation. Methods and procedures related to power control when the WTRU changes its D2D mode of operation may be applicable when the WTRU changes coverage conditions.
[0161] The WTRU may be configured to use CLPC (e.g., with an indication signaling along the grant signal) when using, for example, Mode 1. The WTRU may be configured to determine which power control mode to use when the WTRU moves to Mode 1. The WTRU may be configured to autonomously use a closed-loop power control mode, such as when the WTRU determines that it is operating in D2D communication mode 1. The SIB may indicate semi-static power control parameters. The D2D grant may carry a dynamic closed-loop indication.
[0162] The WTRU may be configured to determine which power control mode to use when the WTRU moves from Mode 1 to Mode 2. The WTRU may be configured, for example, to determine which power control mode to use when the WTRU moves out of Mode 1. The WTRU may be configured to read the SIB. The WTRU may be configured to determine which power control mode to use based on the SIB configuration (e.g., the WTRU may be configured to use open loop power control). The WTRU may be configured, for example, to autonomously use fixed power control if the WTRU is unable to read the SIB.
[0163] The WTRU may be configured to select a resource pool for WTRU transmission (Tx) and / or reception (Rx). A D2D-enabled WTRU may be configured with at least a resource pool for reception (e.g., i.e., a receive pool) and / or at least a resource pool for transmission (e.g., i.e., a transmit pool). A D2D-enabled WTRU may be configured to use the resource pools. The WTRU may be configured to determine the receive pool as a collection of resource pools from different received synchronization sources / relays and the transmit pool from a resource pool received from a serving (e.g., i.e., master) synchronization source / relay. The transmit pool may refer to a transmit pattern. The receive pool may refer to a receive pattern. The transmit pattern may refer to a transmit pool. The receive pattern may refer to a receive pool.
[0164] A WTRU may be configured with a resource pool configuration. The resource pool configuration may include and / or may be defined by one or more resource pool parameters. Exemplary resource pool parameters that may be associated with or used to define a given resource pool may include one or more resource configurations (e.g., this may include one or more D2D reception parameters and / or D2D transmission parameters). Exemplary resource pool parameters may include one or more allowed application types, allowed usage rears, and / or index ids. Exemplary resource pool parameters may indicate whether the pool is available for control use and / or whether the pool is available for data use. Exemplary resource pool parameters may include one or more activation or deactivation triggers, time windows, priorities, transmit powers, transmission control indications, traffic types, types of devices (e.g., D2D relays), and / or types of services. For example, a D2D resource configuration may include D2D reception parameters. The D2D reception parameters may include or indicate, for example, a subset of time-frequency (T / F) resources to be monitored for reception of D2D signaling from other devices when operating in both Mode 1 and Mode 2. The D2D reception parameters may include or indicate a separate set of T / F resources for Mode 1 and Mode 2 and / or a subset of T / F resources to be listened for D2D control messages (e.g., scheduling assignment messages or D2D synchronization messages). The D2D resource configuration may include D2D transmission parameters. The D2D transmission parameters may include or indicate a subset of T / F resources to be used for D2D transmission when operating in both Mode 1 and Mode 2. The D2D transmission parameters may include or indicate a separate set of T / F resources for Mode 1 and Mode 2 and / or a subset of T / F resources to be used for transmission of D2D control messages.The D2D transmission parameters or D2D reception parameters may include one or more time domain patterns.
[0165] An example of a resource pool parameter may include an allowed application type. For example, the allowed application type resource pool parameter may include an indication of whether the pool is available for commercial applications, public safety applications, or both. The allowed application type resource pool parameter may include an indication of whether the resource pool may be used to relay, for example, by a relay WTRU or a remote WTRU using a relay service. The allowed application type resource pool parameter may include an indication of a group of applications or services for which the resources are applicable. For example, the resource pool configuration may be used for a public safety firefighting application. An example of a resource pool parameter may include an allowed area of use. For example, the allowed area of use may be an indication of a PLMN, eNB, cell id, and / or tracking area id for which the resources are authorized to be used. When the WTRU is within the coverage of a base station or eNB operating with one or more of the associated PLMNs, the WTRU may be configured to use the corresponding resource pool.
[0166] An example of a resource pool parameter may include an index Id. For example, the resource pool information may include an index id, which may identify a resource pool. The index id may identify a resource pool via a resource configuration index. A resource pool may be characterized by an index id. A base station or eNB may signal a resource pool that may be used by a WTRU using a resource pool index.
[0167] A resource pool may be associated with a control usage and / or a data usage. For example, the resource pool information may include an indication of whether the resource pool is applicable to D2D control messages (e.g., synchronization messages on PD2DSCH), D2D data messages, or both.
[0168] A resource pool may be associated with an Activation / Deactivation trigger. If resources are pre-configured or semi-statically allocated, the resource pool may include an indication to configure the WTRU to use the resources when desired and / or to use the resources once they are activated / deactivated. The base station or eNB may configure the WTRU using RRC signaling to explicitly activate and / or deactivate a resource pool.
[0169] A resource pool may be associated with a time window: a resource pool configuration may indicate a time duration during which a resource may be valid.
[0170] The WTRU may receive an indication that may indicate whether the WTRU will attempt (eg, always attempt) Mode 1 transmission before using the Mode 2 transmission pool.
[0171] The resource pools may be associated with a priority, which may indicate a priority level, and the WTRU may be configured to select a resource pool based on the priority.
[0172] A resource pool may be associated with a transmit power and / or control information. A resource pool may be characterized by a maximum transmit power and / or a transmission range. A WTRU may determine a transmit power based on the transmit power and / or control parameters (e.g., when using a resource pool for transmission).
[0173] A resource pool may be associated with a traffic type. The traffic type may include unicast and / or broadcast / multicast. For example, a WTRU may transmit unicast traffic over a resource pool having a unicast traffic type. A resource pool having a unicast traffic type may be reserved such that non-unicast traffic may be barred in the resource pool. As another example, a WTRU passes any type of traffic over a resource pool having a non-unicast traffic type. As another example, a WTRU may transmit broadcast and / or multicast traffic over a resource pool having a broadcast / multicast traffic type.
[0174] A resource pool may be associated with a type of device and / or service. A resource pool may be reserved for a type of device. A resource pool may be reserved for a type of service. For example, a resource pool may be reserved for a relay device that supports a relay service. A resource pool may be initialized / reinitialized individually by higher layers.
[0175] As described herein, each resource pool may be associated with an index. A WTRU may be configured with one or more resource pools. A WTRU may be configured with one or more resource pools via higher layer signaling (e.g., RRC). One or more resource pools may be defined via a specification. A WTRU may determine one or more characteristics of a resource pool. A WTRU may find resource pool information associated with a received resource pool index.
[0176] The WTRU may be configured to select a resource pool, for example, from multiple resource pools. The WTRU may be configured to select a resource pool for D2D Tx / Rx. The WTRU may be configured with separate pools to be used for receiving and transmitting D2D communications. The WTRU may receive one or more receive and / or transmit resource pools from one or more sources. The WTRU may select a resource pool based on one or more resource pool selection criteria. The WTRU may receive multiple resource pool configurations, for example, based on resource pool selection criteria. The WTRU may select a resource pool configuration based on an application that is running or a group in which the WTRU is currently a participant. If the WTRU is part of a fire and public safety group, it may be configured to first identify a resource pool (e.g., defined by a configured group ID) dedicated to fire and public safety. The resource pool configuration may be aligned for one group across multiple synchronization sources. If the WTRU selects a resource pool from multiple synchronization sources, the WTRU may select a resource pool advertised to support a group or application in which the WTRU is participating or is a part of.
[0177] Based on the resource pool selection criteria, the WTRU may determine a receive pool as the aggregation of resource pools from the same or different received synchronization sources / relays, and a transmit pool from the resource pool received from the serving (e.g., i.e., master) synchronization source / relay.
[0178] Based on the resource pool selection criteria, the WTRU may be configured to prioritize resource pools based on the origin of the resource pool configuration. For example, the WTRU may prioritize resource configurations obtained from a base station or eNB over resource configurations originating from other D2D WTRUs (e.g., other synchronization sources).
[0179] Based on the resource pool selection criteria, the WTRU may be configured to prioritize resource pools from a master or serving synchronization source, the selection of a master or serving synchronization source being described in more detail below.
[0180] Based on the resource pool selection criteria, the WTRU may be configured to prioritize more recent resource pool information.
[0181] Based on the resource pool selection criteria, the WTRU may be configured to prioritize resource pool configurations from the highest priority source or from the relay source.
[0182] Based on the selection criteria resource pool, the WTRU may be configured with one or more of the priority rules described herein and the relative order among them. The WTRU may be configured, for example, to default to a common resource pool if a previous prioritized selection is unavailable. The WTRU may be configured, for example, to a randomly selected resource pool selected from a predefined set of resources.
[0183] A WTRU may be configured to select a resource pool associated with a relay service, for example, based on a resource pool selection criterion. For example, a WTRU configured to act as a relay may be configured with one or more resource pools for relay transmission / reception. A WTRU configured as a remote WTRU using a relay service provided by a relay WTRU may be configured to select a resource pool associated with the relay service when transmitting data targeted to this relay service.
[0184] The WTRU may be configured to forward (e.g., transmit) the resource pool selection to other WTRUs. As described herein, the WTRU may determine to transmit information about the resource pool to other WTRUs. The WTRU may determine that the resource pool may be transmitted to other WTRUs when the WTRU is a synchronization source or a relay source.
[0185] A WTRU may be configured to be the source of a D2D resource configuration when it becomes a synchronization source as described herein. The WTRU may be configured to determine a resource pool to transmit on based on resource configurations detected from other sources. In a non-limiting example, an out-of-coverage WTRU may select its resource pool based on messages received from neighboring D2D WTRUs (e.g., based on synchronization messages received from neighboring WTRUs).
[0186] The WTRU may prioritize resource pools used by its neighbors and select a non-overlapping resource block or pool within the allowed pool that is not advertised by other D2D WTRUs. If no such resource block is available, the WTRU may be further configured to select the resource pool associated with the synchronization message with the weakest signal.
[0187] A WTRU may be configured to align its resource pool with a synchronization zone associated with a neighboring WTRU or the same group as the WTRU. A WTRU that is part of a fire public safety application / group may align its resource pool with detected resource pool information from neighboring fire group WTRUs.
[0188] The WTRU may be configured to, for example, randomly select a resource pool if no other rules are available. The resource pool may be selected from a predefined set that may be transmitted in a synchronization message.
[0189] The WTRU may use a resource pool identified by the eNB (e.g., when the WTRU is in coverage). For example, the network (e.g., an eNB) may configure the WTRU with a resource pool index. As another example, the network may configure the WTRU with a set of resource pool parameters.
[0190] The WTRU may determine that the resource pool is to be transmitted for other WTRUs, for example, when the WTRU is forwarding information from other synchronization sources.
[0191] The WTRU may send the resource configuration and resource pool assignment as part of a synchronization message or a relay message. The resource configuration may include a set of parameters and / or a resource configuration index.
[0192] The WTRU may be configured separately with a resource pool configuration that will be forwarded as part of the synchronization message. An in-coverage WTRU may be configured with in-band resources for its own D2D communication. An in-coverage WTRU may use a pre-configured out-of-band resource pool that will be sent in the synchronization message.
[0193] The WTRU may be configured to forward a subset of the resources that are to be forwarded as part of the synchronization message.
[0194] The WTRU may be configured to evaluate / re-evaluate the D2D Rx / Tx resources based on a trigger. The WTRU may be configured to evaluate and / or re-evaluate the set of D2D Rx / Tx resources based on one or more of the following triggers: The WTRU may be configured to evaluate and / or re-evaluate the set of D2D Rx / Tx resources based on one or more of the trigger events described herein.
[0195] The WTRU may trigger an evaluation / re-evaluation of resources to be used for D2D Tx / Rx (eg, Mode 1 or Mode 2) based on one or more triggering events described herein.
[0196] The WTRU may be configured with rules for resource selection based on the current D2D Coverage-State.
[0197] The WTRU may be configured with rules for selection of resources based on a change in operation mode (e.g., based on a change between Mode 1 and Mode 2, e.g., based on a change from Mode 1 to Mode 2) that will be used to acquire D2D resources.
[0198] If one or more D2D resources are used, the WTRU may be configured with rules for resource selection based on the RRC state. The WTRU may be configured to use resources signaled by one or more base stations or eNBs (e.g., signaled via SIBs) when the WTRU is in RRC_IDLE mode.
[0199] When new data arrives within the Access Stratum (AS) from a D2D application, the reception of the new data may trigger the AS to determine (e.g., search for) D2D resources, and if the resources are not available, the WTRU may be triggered with a procedure to acquire the D2D resources.
[0200] The WTRU may receive signaling from higher layers indicating that a new D2D service has been configured.
[0201] The WTRU may be configured to select resources, for example, when the WTRU is configured to operate as a relay WTRU.
[0202] The WTRU may be configured to select resources, for example, when the WTRU is configured as a remote WTRU, which may refer to a WTRU that may use relay services from a relay WTRU.
[0203] If D2D resources are used and the WTRU is operating in Mode 1, the WTRU may be configured to first attempt to request resources from the network. If resources are not available within a configured duration, the WTRU may be configured to fall back to a semi-static or pre-configured resource pool (e.g., use Mode 2).
[0204] An RRC_IDLE WTRU or an RRC_O ECTED WTRU camped on a suitable serving cell may be configured to initiate D2D resource selection by using Mode 1. In such a scenario, when new D2D data arrives, the WTRU may initiate a request to obtain resources from the base station or eNB. If the procedure is unsuccessful (e.g., no response to a scheduling request or RRC connection request for a preconfigured duration), the WTRU may attempt to use a resource pool configured using broadcast signaling. If no resources are available in the broadcast or the WTRU is unable to decode the SIB, the WTRU may transition to the preconfigured resource pool.
[0205] If D2D resources are used, the WTRU may be configured with rules for mode and resource pool selection based on the RRC state. In a non-limiting example, the WTRU may be configured to operate in mode 2 when it is in RRC_IDLE mode. This rule may take precedence over the base station or eNB defined mode.
[0206] A change in the selected D2D resources may further trigger the WTRU to perform one or more additional D2D procedures. An update in the selected resources may further trigger the WTRU to transmit the new resource configuration to other neighboring WTRUs.
[0207] A WTRU may be configured with a time domain D2D transmission / reception pattern. A D2D WTRU may perform D2D transmission / reception according to a D2D pattern (e.g., transmission / reception may be possible at certain times / subframes and barred at other times / subframes). A D2D pattern may define reception opportunities for a WTRU (e.g., times at which a WTRU is expected to receive on a selected resource pool). A D2D pattern may define transmission opportunities (e.g., times at which a WTRU may transmit). A D2D pattern may define reception opportunities and may define transmission opportunities for a WTRU (e.g., a time pattern indicates times at which a D2D WTRU may perform D2D reception and / or transmission). A WTRU may be configured with one or more patterns associated with a priority. A WTRU may be configured with rules to select a pattern to use based on the priority of the data to be transmitted or received. For example, pattern 1 may be associated with high priority data, pattern 2 may be associated with medium priority data, etc. A WTRU may be configured with rules to select a pattern based on the role of the WTRU. For example, the WTRU may select a given pattern when the WTRU acts as a relay. The transmit pattern may refer to a transmit pool. The receive pattern may refer to a receive pool. The transmit pool may refer to a transmit pattern. The receive pool may refer to a receive pattern. As described herein, the D2D pattern and the transmit pool may be used interchangeably.
[0208] The WTRU may be configured to use the D2D pattern when the WTRU has normal UL communication with a base station or eNB and the WTRU decides to perform D2D communication (e.g., in another spectrum, or in the same spectrum but limited to a single receiver). The WTRU may be limited to a single receiver when it must not coordinate with eNB reception to receive data. The WTRU may use the D2D pattern when the WTRU is expected to perform communication on a different frequency or when the WTRU is operating in an out-of-coverage mode to enable some form of battery saving while performing D2D communication. The triggers for when to start using the pattern are described below.
[0209] When a WTRU is out of coverage, it may be expected to receive continuously within resources with a resource pool. The WTRU may be configured to use a DRX-like pattern.
[0210] The WTRU may be configured to determine when to use a pattern (e.g., a pool) based on the detected trigger. The WTRU may receive an explicit indication to use a transmission pattern (e.g., a transmission pool) or a reception pattern (e.g., a reception pool) according to one or more criteria. For example, when a synchronization message (e.g., a selected synchronization source or a relay synchronization message) includes the pattern and / or the WTRU may explicitly receive the pattern from a base station, an eNB, or another control entity. When the WTRU receives the explicit indication, the WTRU may begin using the pattern and / or the associated pool. For example, when the WTRU is configured to operate as a relay, the WTRU may begin using the pattern. The WTRU may be configured to operate as a relay when the WTRU receives an instruction to start operating as a relay. The WTRU may receive a request or pattern transmission from an entity (e.g., another WTRU) that is authorized to communicate with the WTRU (e.g., a group ID corresponds to at least one of the receiving WTRU's authorized / configured group IDs). The WTRU may receive an explicit indication that it may begin using a transmission or reception pattern when a D2D discovery or communication session is initiated. The WTRU may be configured with different patterns when the WTRU is configured to operate as a relay WTRU or when the WTRU is configured to communicate with a relay WTRU.
[0211] A WTRU may be configured to determine when to transmit or communicate a pattern usage to one or more other WTRUs based on a trigger. The WTRU may determine that it will use a pattern and may potentially begin transmitting at least a transmitted or received pattern indication as part of its synchronization message. The WTRU's decision to begin transmitting a pattern indication and / or request a pattern for transmission may be based on triggers described below (e.g., a trigger for deciding to become a synchronization source or a relay). The WTRU's decision to begin transmitting a pattern indication and / or request a pattern for transmission may be based on one or more additional triggers. The triggers may include a time pattern resource usage trigger, a frequency of operation trigger, a trigger based on a state of the WTRU, a trigger based on a hop of a received pattern, a trigger indicating that the WTRU may be configured with a power saving mode of operation, and a trigger indicating that the WTRU detects a pattern. When the WTRU is operating as a relay node, the WTRU may transmit one or more selected patterns. A WTRU acting as a relay may start transmitting patterns based on a change in the WTRU's role (e.g., operation as a relay node) or based on a change in the data / services supported by the WTRU (e.g., when the WTRU starts forwarding a new MBMS service).
[0212] The first WTRU may receive an indication of a time pattern / resource usage trigger when the WTRU determines that the second WTRU is using a different time pattern than the first WTRU. For example, the WTRU may decide to align the pattern or request a new pattern as described herein. The WTRU may further determine to transmit a pattern indication in a synchronization message. The WTRU may receive an indication of a frequency of operation trigger when the WTRU may be connected for communication on a frequency other than the frequency of operation of the second detected WTRU. The WTRU may request a pattern and begin using the pattern or transmit a pattern indication in a synchronization message. A WTRU that receives a pattern to use may further determine whether to transmit (e.g., send) a pattern indication in a synchronization message, for example, if the WTRU determines to communicate with the WTRU on another frequency. The WTRU may receive an indication of a trigger based on the state of the WTRU, e.g., if the WTRU is in-coverage, the WTRU may use the pattern provided by the eNB, and if the above criteria are met, the WTRU may transmit the pattern indication. If the WTRU is out of coverage and it receives the pattern indication, in some examples, the WTRU may use it to determine transmission and / or reception opportunities, but may not further forward or relay the pattern indication in its own synchronization message.
[0213] The WTRU may receive an indication of the trigger based on hops of the received pattern (e.g., based on a detected hop count). When the receiving WTRU receives the pattern indication, the receiving WTRU may use the pattern indication to determine whether to forward the pattern indication in a synchronization message. The WTRU's decision to forward may depend on the hop count or the source from which the synchronization message may be received. In some examples, if the WTRU receives a pattern from a synchronization source (e.g., from a base station or eNB), the WTRU may transmit the pattern indication in its synchronization message. If the WTRU receives a pattern indication from a transmitting relay with a hop count greater than a configured hop count, the WTRU may decide not to further transmit the pattern indication in its synchronization message.
[0214] The WTRU may detect a trigger indicating that the WTRU may be configured for a power saving mode of operation. For example, if the WTRU is configured with a power saving mode of operation, upon detecting the trigger, the WTRU may use a pattern indication and further transmit this in a synchronization message that the WTRU may receive during the configured time pattern. A trigger indicating that the WTRU detects (e.g., uses or transmits) a pattern (e.g., a particular type of pattern) may occur when the WTRU determines that it may be a synchronization source or relay, or may communicate to another WTRU and begin using and transmitting a pattern indication on a synchronization message. The trigger for operating as a synchronization source may be different from the trigger for operating as a relay. One or more of the triggers described herein may be used by the WTRU to determine whether the WTRU may operate as a synchronization source, a relay, or both.
[0215] For example, the WTRU may determine whether to become a synchronization source based on the measured signal strength of a source (e.g., an eNB) falling below a predetermined threshold. For example, if the WTRU is in an in-coverage state or connected to a base station or an eNB and detects a synchronization signal (e.g., D2DSS or control message) from a lower priority source or from a source that is not a base station or an eNB (e.g., the second WTRU is an out-of-coverage WTRU), the WTRU may become a synchronization source. In another example embodiment, the WTRU may initiate this procedure if it determines that the second WTRU belongs to an allowed group for the WTRU.
[0216] For example, an in-coverage WTRU that decides to communicate with an out-of-coverage WTRU may coordinate and transmit a receive / transmit pool on a control or synchronization message to enable communication.
[0217] A WTRU may determine whether a neighboring WTRU is in-coverage or out-of-coverage based on a detected D2D control signal or message (e.g., D2DSS or PD2DSCH). For example, a first WTRU (e.g., an in-coverage WTRU) may detect a second WTRU and determine that it corresponds to an out-of-coverage WTRU based on one or more characteristics or identities of the received D2DSS.
[0218] For example, the WTRU may decide to operate as a relay, or the WTRU may decide to provide relay service, based on one or more of the following example conditions: The WTRU may decide to operate as a relay when it detects another out-of-coverage WTRU requesting relay service (e.g., the out-of-coverage WTRU may request a relay WTRU for a service that the relay WTRU may be configured to provide as a relay service). The WTRU may decide to operate as a relay when it is connected to one or more remote WTRUs (e.g., via a series of control message exchanges). The WTRU may decide to operate as a relay when it determines that it has relay data and / or a network to transmit. The WTRU may decide to operate as a relay when it determines that it has relay data to receive (e.g., when the WTRU may be connected to at least one remote WTRU). The WTRU may decide to act as a relay when it receives an explicit command by the network to act as a relay or when it is configured by higher layers to act as a relay. The WTRU may decide to act as a relay based on signal strength measurements with eNBs and / or other out-of-coverage WTRUs, etc.
[0219] When the WTRU determines that it will act as a synchronization source or relay, the WTRU may initiate transmission of one or more indications, e.g., on a synchronization message. When the WTRU is acting as a relay and the allocated resources are not sufficient to support all remote UEs, the WTRU may initiate an indication to the network.
[0220] When the first WTRU detects that a trigger or combination of triggers described herein is met, the WTRU may begin transmitting a control message or synchronization message (e.g., PD2DSCH) that includes a transmission and / or reception pattern / pool indication. The content of the synchronization message may be determined based on the role being performed by the WTRU. For example, when the first WTRU detects a trigger to become a relay, the synchronization message content may include one or more resource pattern / pool indications.
[0221] A WTRU may receive a message (e.g., a control message, a synchronization message, or a PD2DSCH) that may include the contents of a pattern / resource pool. The synchronization message, the control message, and the PD2DSCH may be equivalent. The pattern included in the synchronization message (e.g., PD2DSCH) may correspond to one or a combination of the following: The pattern in the synchronization message may correspond to a transmission pool. A WTRU receiving the synchronization message may use the transmission pool to determine one or more transmission opportunities. The one or more transmission opportunities may be for D2D transmissions (e.g., all D2D transmissions), or the one or more transmission opportunities may correspond to transmission opportunities for services that are allowed to be received by the WTRU transmitting the synchronization message (e.g., based on an identity transmitted on PD2DSCH or based on higher layer signaling). Transmissions performed by other WTRUs (e.g., out-of-coverage WTRUs) may be received by the in-coverage WTRU. The transmission pool indication to be transmitted on the PD2DSCH or another control message may be determined by the WTRU based on an explicit configuration received by the network (e.g., a transmission pool configuration for transmitting on the PD2DSCH or in another control message). The transmission pool indication to be transmitted on the PD2DSCH may directly correspond to the pool used by the in-coverage WTRU in the current cell (e.g., a reception pool received by the eNB).
[0222] The pattern indicated in the synchronization message may correspond to a reception pool. A WTRU receiving the synchronization message may use the reception pool to determine at least a subset of reception opportunities. The reception pool indication to be transmitted on the PD2DSCH may be determined and may correspond to an explicit configuration received by the network (e.g., a reception pool configuration for transmitting on the PD2DSCH). If the WTRU is configured with a Mode 2 configuration, the reception pool indication to be transmitted on the PD2DSCH may directly correspond to the pool (e.g., a transmission pool received by the eNB) that the in-coverage WTRU uses in the current cell. The pattern in the synchronization message may correspond to what is provided in the following example embodiment.
[0223] The WTRU may explicitly request that the network enable the WTRU to begin pattern indication transmission or resource pool indication transmission. When the first WTRU detects that one or a combination of the above-described triggers are met, the first WTRU may send a request or message to the eNB to report detection of one or a combination of the triggers (e.g., an out-of-coverage WTRU is detected, an out-of-coverage WTRU detects that it is requesting relay service, the WTRU decides that it will act as a relay (e.g., configured by higher layers to be a relay), or a trigger for the WTRU to become a synchronization source from the eNB). The WTRU may include one or more of information regarding the trigger for the message in the request message, including, for example, one or more of a cause, a measurement, a WTRU identity, etc. The WTRU may include information regarding the relay-related service request in the request message, including, for example, an identity of the remote WTRU requesting relay service, a service type, QoS, etc. The first WTRU may start transmitting a pattern indication or resource pool on the PD2DSCH or other control messages regarding confirmation and configuration from the network. The first WTRU may indicate one or a combination of the following information to the network: The first WTRU may indicate the reason for the request (e.g., an out-of-coverage WTRU detected or the first WTRU received a request for relay service), the identity of the detected WTRU, the group ID to which the detected WTRU belongs, the ProSe ID, the number of WTRUs requesting service. The first WTRU may indicate a unique identifier of the detected WTRU, the detected D2DSS of the WTRU that triggered the report, the recommended resource pool or pattern, the frequency of operation of the detected WTRU. The first WTRU may indicate a request to start serving as a relay. The first WTRU may request to stop transmitting PD2DSCH (e.g., an out-of-coverage WTRU that is no longer detected, or a trigger that becomes a synchronization source that is no longer satisfied, or a relay service that is no longer required).
[0224] The WTRU may wait for an explicit indication (e.g., a message) from the eNB or primary synchronization source to do one or more of the following: The WTRU may begin transmitting one or more resource pool indications (e.g., start transmitting synchronization messages and / or signals). The WTRU may receive resource pool information on which the WTRU may be configured to transmit. The WTRU may be configured with resources and periodicity (e.g., PD2DSCH and SA resources) on which synchronization messages and / or signals may be transmitted. The WTRU may include additional information in the synchronization messages and / or signals. The WTRU may wait for a request for an in-coverage WTRU to provide the WTRU identity of an out-of-coverage WTRU when available.
[0225] Upon receiving a start synchronization message from the eNB, the WTRU may begin transmitting or configure (eg, reconfigure) a synchronization message, which may include one or more resource pool or pattern indications.
[0226] If the WTRU identity of a detected WTRU (e.g., out of WTRU coverage) that triggered the initiation of the synchronization message was not initially known, the WTRU may continue to monitor until it can detect the identity of the detected WTRU. The WTRU may report the identity of the detected WTRU to the network when available.
[0227] The network may use the identity of the detected WTRU to decide whether the in-coverage WTRU should start transmitting, continue transmitting, or stop transmitting synchronization messages (e.g., if the corresponding WTRUs cannot communicate with each other or do not belong to the same group or service, or if the corresponding WTRUs are authorized for such services). The network may further use the identity of the detected WTRU or the D2DSS to determine whether any other in-coverage WTRUs are transmitting the same resource pool to enable communication with the detected WTRU. The network may decide to stop the PD2DSCH transmission of at least one of the other in-coverage WTRUs that perform PD2DSCH transmission.
[0228] Based on the determined identity, the WTRU may determine (e.g., on its own) whether it can communicate with the detected WTRU and may implicitly stop. If the WTRU detects at least one nearby WTRU whose identity it has not determined or with which it can communicate, the WTRU may continue transmitting.
[0229] The WTRU may decide to stop transmitting synchronization messages (e.g., when no more out-of-coverage signals are detected). The WTRU may stop transmitting and indicate to the network that the WTRU has stopped transmitting synchronization messages. The WTRU may indicate to the network that there are no more detected out-of-coverage D2D signals, and the WTRU may wait for an explicit command to start or stop. The WTRU may indicate to the network that there are no more remote WTRUs using relay service or that the WTRU is not configured to provide relay service (e.g., once the WTRU determines that it is not required to provide relay service). The WTRU may wait for an explicit command to start or stop transmitting PD2DSCH or control messages. The WTRU may autonomously decide to stop transmitting PD2DSCH or control messages.
[0230] Upon receiving a pattern or upon determining that the WTRU must use a pattern, the WTRU may perform one or more of the following actions: The WTRU may restrict all transmission opportunities to be included in the given pattern. This may ensure that the WTRU that relayed or transmitted the message may be able to receive the message. Another action may include restricting all reception opportunities in a given pool of resources to be within the given pattern. The reception opportunities may be a collection of different resource pools or patterns received. This action may be beneficial as it may promote battery life. Depending on the coverage state, the WTRU's behavior may differ. For example, an in-coverage state WTRU may use a pattern to perform reception within a given resource pool. Depending on the mode (e.g., mode 1 or mode 2) that the WTRU is using, the WTRU may either transmit during some of those opportunities (e.g., in mode 2) or rely on the eNB to dynamically schedule the actual transmission opportunities (e.g., in mode 1). For example, as described herein, an out-of-coverage WTRU may use a pattern to determine available transmission opportunities. An out-of-coverage WTRU may always receive, e.g., to ensure proper reception of data from all other WTRUs. An out-of-coverage WTRU configured with power savings may receive during a configured pattern or a collection of different configured patterns (e.g., if there are multiple sources).
[0231] Based on the received pattern, the WTRU may determine transmission time opportunities (e.g., TTIs) that the WTRU can use to transmit and / or receive. For example, if the pattern includes a duration (e.g., number of consecutive TTIs), a cycle, and / or a number of subframes, the WTRU may determine the time instances (system frame numbers (SFNs) and subframes) in which the WTRU is allowed to receive transmissions / receptions.
[0232] To align with the transmission pattern, the SFN or reference time that the receiving WTRU may be using (eg, an in-coverage WTRU or an out-of-coverage WTRU) may be provided along with the pattern in the synchronization message.
[0233] The pattern may be a bitmap or a fixed pattern having a relationship to subframes within a frame or within several frames. The reference frame may be a specific frame that may be specially defined within the synchronization channel.
[0234] The WTRU may detect different patterns. The WTRU may be connected to a selected synchronization source or relay, however, it may be able to receive and decode synchronization messages from multiple sources. The WTRU may determine that the patterns used from different synchronization sources may be different. This may cause a WTRU connected to a different synchronization source to potentially not be able to receive data from other clusters. To avoid data loss, the WTRU may report this inconsistency to the cluster head and transmit the same pattern upon detection of the inconsistency that results in a synchronization source. The WTRU may trigger the start of a synchronization message and indicate that a message is being transmitted to align the patterns. The WTRU may transmit the pattern of the source or relay that is detected with the highest priority. The WTRU may determine transmission opportunities for both detected patterns and transmit the message twice in both transmission opportunities. The WTRU may limit transmission to overlapping transmission opportunities between different received patterns (e.g., if there is no overlap, the WTRU may perform one of the actions described above).
[0235] The WTRU may receive the pattern explicitly. For example, the WTRU may receive the pattern via dedicated signaling or a broadcast message that may be broadcast from a base station or eNB. The pattern may be included in a synchronization message received from a synchronization source or a synchronization relay. The WTRU may receive the pattern via a dedicated message from another WTRU. The WTRU may receive the pattern from a pre-configured WTRU (e.g., the WTRU may be configured with a set of patterns from which it can select).
[0236] The WTRU may determine the pattern to use and transmit using the determined pattern. The WTRU may determine the pattern to be used based on the WTRU capabilities and the D2D services configured from one or more higher layers. For example, if the WTRU is equipped with a single receiver, the WTRU may determine the pattern to be used for the WTRU to TDM receive from DL and D2D links. For example, to avoid self-interference, the pattern the WTRU uses to TDM between Uu Tx and D2D Tx / Rx.
[0237] The WTRU may be configured to determine (e.g., select) a pattern to use based on the type of traffic to be transmitted and / or received. For example, a relay WTRU may be configured to use a transmission pattern for relay traffic when relaying such traffic. A remote WTRU may be configured to use a pattern or resource pool associated with the relay when transmitting or receiving data to / from the relay and another pattern or resource pool when transmitting other data (e.g., non-relayed D2D transmissions). For example, the selection of a pattern may be based on a priority associated with the received pattern and / or a priority of the data or service determined by the WTRU. The priority of the WTRU service or data may be determined with respect to several factors including user priority, static priority configured in the WTRU, priority of the application generating the data or the highest priority of one or more applications generating the data, services running in the WTRU, etc.
[0238] The WTRU may determine the number of transmission subframes that may be used in case of discovery, for example, based on the number of discovery sessions initiated. The WTRU selects the transmission subframes based on one or more of the following factors: The WTRU may select the transmission subframes using several discovery sessions initiated by higher layers. The WTRU selects the subframe transmission based on the ratio of the number of sessions in which the WTRU is announcing WTRU to the number of sessions in which the WTRU is a monitoring WTRU. The WTRU may select the transmission subframes from a list of configured patterns (e.g., even subframe patterns or odd subframe patterns). The WTRU may select the transmission subframes based on the D2D-RNTI.
[0239] The WTRU may send an indication when it uses the determined pattern. The WTRU may be configured to send an indication when it determines the pattern. The WTRU may send an indication to the eNB, a synchronization source, or another WTRU. The indication may include one or more of the following: The indication may include the pattern selected by the WTRU. The indication may indicate a subframe in which the WTRU is configured to perform D2D Tx and / or D2D Rx. The indication may indicate when the WTRU is configured to start using the pattern, for example, this information may be indicated using a SFN index and / or a subframe index when D2D tx / rx may be performed. The indication may include a duration for which the WTRU may use the pattern. The indication may indicate when the WTRU is configured to stop using the pattern.
[0240] The WTRU may be configured to detect a trigger indicating when to send an indication regarding using the determined pattern. The WTRU may be configured to send an indication in the following conditions: The indication may be sent based on an explicit command by the eNB (e.g., the eNB may send a message requesting the WTRU to transmit the pattern). The indication may be sent when a D2D discovery or communication session is started or stopped by one or more higher layers. The indication may be sent when the WTRU is able to perform a service (e.g., a new service) that may require the pattern to be changed.
[0241] The WTRU may be configured to perform a synchronization procedure, for example, using synchronization principles. To simplify signal detection and demodulation, one or more exemplary embodiments provide a predefined frame structure for D2D communication. The predefined frame structure may be defined and used by all D2D WTRUs. The frame structure may be defined such that the location (e.g., in time and / or frequency) of one or more of the Scheduling Assignment (SA), D2D Synchronization Signal (D2DSS), Physical D2D Synchronization Channel (PD2DSCH) (e.g., a broadcast control channel for D2D), discovery signal, and data transmission may be easily determined (e.g., well known). Exemplary D2D synchronization frame structures may be illustrated in FIG. 5 (time domain) and FIG. 6 (time-frequency domain).
[0242] The WTRU may be configured to use multiple frame formatted D2D synchronization frames. The WTRU may be configured with multiple frame formats. The frame formats may define different locations for different elements of D2D communication. Some non-limiting examples may include D2DSS, P2D2SCH, Scheduling Address (SA) area, discovery area, D2D data, etc.
[0243] The different frame formats may be configured such that the D2DSS locations (e.g., in time) do not overlap between the different formats. This may allow multiple D2DSS hops to have the same format. This example embodiment may be shown (e.g., in the time domain) in FIG. 7. A similar concept may be applied in the time-frequency domain when designing frame formats configured to allow for non-overlapping D2DSS locations (e.g., in time and frequency) between the different formats.
[0244] The WTRU may decide to use a fixed format. For example, the WTRU may be configured to use a fixed format based on a specification. The format may depend on the frequency band, WTRU category, or other fixed criteria, in non-limiting examples. The WTRU may determine the frame format to use based on a pre-configuration, for example, the WTRU may be pre-configured by the network or via its USIM or other internal configuration with the D2D synchronization frame format to use. The WTRU may be configured with a particular D2D synchronization frame format to use, for example, when the WTRU becomes a synchronization source. The WTRU may determine the frame format to use based on an implicit format, for example, the WTRU may be configured to determine the frame format being received based on synchronization signal characteristics and / or the PD2DSCH (e.g., content and / or resource location). The WTRU may determine the frame format to use based on an explicit format, for example, the WTRU may be configured to determine the frame format based on explicit signaling from the PD2DSCH.
[0245] The WTRU may determine frame timing based on the frame format and the D2DSS characteristics. The WTRU may be configured to determine the frame timing and synchronize to the associated D2D synchronization frame. The D2D synchronization frame format may be determined, where the WTRU determines the D2D synchronization frame format, which then determines the time location of the D2D synchronization frame. The D2DSS characteristics are determined, where the WTRU may determine the D2D synchronization frame based on the D2DSS characteristics. The D2DSS characteristics may include the D2DSS receive timing. Information received from the synchronization signal hop count and / or PD2DSCH may be used to determine the frame timing and synchronize to the associated D2D synchronization frame.
[0246] WTRUs in the same synchronization zone may have the same synchronization frame. To facilitate communication between WTRUs in the same vicinity, WTRUs in the same vicinity may share the same D2D synchronization frame. Some WTRUs may relay D2DSS up to a maximum number of hops. As mentioned above, the number of hops can be more than two hops, for example, as shown in the synchronization protocol of FIG. 4. A synchronization source (SS) may be a device that transmits D2DSS with an independent synchronization reference. An SS may be a network source (e.g., a base station or an eNB), in which case it may be referred to as a network SS (NSS). An SS may be an unconnected independent source (e.g., a WTRU), in which case it may be referred to as an independent SS (ISS). A relayed synchronization source (RSS) may be a device that may transmit D2DSS but derive a synchronization reference from another source, for example, either an ISS or an NSS. An RSS may use another RSS as a synchronization reference, up to a maximum hop count. An area in which all WTRUs are synchronized to the same SS may be referred to as a synchronization zone (SZ).
[0247] The WTRU may be configured to receive an indication of a synchronization source identity and hop count from the D2DSS. The synchronization frame for the RSS may be configured to be the same as the synchronization frame from its associated SS. In order for WTRUs in the same synchronization zone to have the same synchronization frame, the synchronization frame for the RSS may be required to be the same as the synchronization frame from its associated SS.
[0248] The WTRU may determine the synchronization frame from the D2DSS and the hop count. The WTRU may derive the synchronization frame timing from the received D2DSS timing and / or from the associated hop count. The relayed D2DSS may carry an indication that ensures that the WTRU can derive the synchronization frame timing of the synchronization source therefrom (e.g., to prevent the WTRU from tracking multiple synchronization zones that are the same).
[0249] Since synchronization frame timing may be associated with a synchronization source, for example, the WTRU may identify the synchronization source from the D2DSS such that a receiving WTRU may detect the presence of multiple synchronization sources / frame timings.
[0250] The D2DSS may carry information regarding one or more of a synchronization source ID, a synchronization source type (e.g., a base station, a source connected to an eNB, or an independent source), and / or a hop count.
[0251] The WTRU D2DSS signal may be based on a Zadoff-Chu signal of known, predefined length and known, predefined bandwidth (e.g., number of PRBs) and duration (e.g., number of OFDM symbols, which may be, for example, one OFDM symbol). D2DSS may be transmitted multiple times during a D2D synchronization frame, or even multiple times during a subframe. Similarly, D2DSS may be augmented by a second synchronization signal (e.g., S-D2DSS), which may be used to carry additional implicit information.
[0252] A D2D WTRU may be configured with multiple sets of ZC root sequences for D2DSS. Each set of ZC root sequences may be associated with a synchronization source type. For example, a D2D may be configured with two sets of ZC roots, each set may include one or more ZC root sequences, and the ZC roots from each set may be different. The first set may correspond to sources associated with an eNB or a network. The second set of ZC roots may correspond to sources associated with an independent synchronization source. A D2D WTRU configured to relay a synchronization source may be configured to use a ZC root from the same set as the synchronization it may be relaying. When a WTRU becomes its own synchronization source, it may be configured to select a ZC root for its D2DSS from a particular set, e.g., from a set associated with an independent synchronization source.
[0253] For example, a second D2DSS may be used to improve synchronization. The sequence used for this second D2DSS (S-D2DSS) may be used to further indicate the source identity. The S-D2DSS may consist of another ZC sequence or an m-sequence. The set of acceptable sequences may be indexed. The set of acceptable sequences may be associated with at least a portion of the synchronization source identity. With reference to FIG. 8, a diagram of an exemplary synchronization source ID according to an exemplary embodiment is shown. As illustrated in FIG. 8, the complete synchronization source identity may consist of an aggregate of the first D2DSS (P-D2DSS), for example, by collecting the type, the type ID index, and the S-D2DSS.
[0254] D2DSS may carry (e.g., implicitly carry) a hop count. The hop count may be indicated by an S-D2DSS index. For example, a small number of bits from the S-D2DSS index may be used to indicate the hop count. A cyclic shift associated with the D2DSS may be used to indicate the hop count. A pair of symbols carrying D2DSS may be used to carry hop count information. For example, the difference in cyclic shift between two D2DSS symbols may indicate the hop count.
[0255] Other combinations based on the techniques described above may be used to implicitly convey synchronization source information.
[0256] The WTRU may be configured to select or reselect a synchronization source. Because there may be a limited number of hop counts and because the WTRU may be close to the eNB, the WTRU may be able to acquire synchronization from multiple synchronization sources (e.g., NSS, ISS, or RSS). The WTRU may prioritize among the synchronization sources, for example, to determine a synchronization frame for data reception / transmission.
[0257] The WTRU may be configured with prioritization rules. The synchronization source may include an eNB. The synchronization source may include a WTRU. The rules for prioritizing between ISSs may be used by the WTRU. If the WTRU detects D2DSS from multiple ISSs, the WTRU may prioritize between ISSs based on measured signal strength of the received D2DSS, and the D2DSS with higher signal strength may be preferred.
[0258] The WTRU may be configured with rules for prioritizing among the RSSs. If the WTRU detects the D2DSS from multiple RSSs, the WTRU may prioritize among the RSSs based on the hop count value indicated by the D2DSS. The RSS with the smaller hop count value may be given priority.
[0259] The WTRU may be configured with rules to prioritize between WTRUs connected to the network and the ISS. The WTRU may prioritize between synchronization sources that are WTRUs in network coverage that relay D2DSS from an eNB that may be out of coverage and an ISS. The prioritization rules may be based on several aspects. For example, the WTRU may communicate with a WTRU connected to the network. In such a case, if the signal strength of D2DSS from a synchronization source that is a network connected WTRU is above a predefined threshold, it may be beneficial for the WTRU to prioritize such a source. If the measured strength of D2DSS is significantly stronger than that from a network connected synchronization source, the WTRU may prioritize the ISS (e.g., the measured energy level from the ISS's D2DSS is X dB higher than the D2DSS from a network connected synchronization source, where X may be predefined).
[0260] The WTRU may be configured to maintain a prioritized list. The WTRU may be configured to maintain a prioritized list of synchronization sources that the WTRU detects. The WTRU may be configured to maintain the prioritized list based on, for example, one or more of the following triggers (e.g., in any order and / or combination): The WTRU may use the conditions / triggers to perform the prioritization / reselection.
[0261] The WTRU may perform synchronization source prioritization periodically (e.g., the WTRU may perform prioritization after a certain amount of time has expired). The amount of time may be explicitly configured by the network or it may be pre-configured in the WTRU. The WTRU may perform synchronization source prioritization aperiodically (e.g., not periodically). Aperiodic prioritization may include detection of a new source. The WTRU may perform a prioritization list update upon detection of a new synchronization source. Detection of a new synchronization source may be declared when D2DSS from a new SS (e.g., identified from D2DSS) is detected and the measured energy is above a certain threshold for a given period of time. A timeout for a given source trigger may be used such that the WTRU may perform prioritization when a given synchronization source is timed out and stops transmitting D2DSS.
[0262] A hop count change may act as a trigger. For example, the WTRU may perform prioritization when it detects a change in the hop count (e.g., the identity of the SS from the D2DSS is the same but the associated hop count is changed).
[0263] The absence of certain data in the buffer can act as a trigger. The WTRU may perform prioritization when it determines that no data has been transmitted for a certain period of time and there is new data in the buffer to transmit. The WTRU performs prioritization when it has no data or has D2D data to transmit for a certain period of time and there is new UL data to transmit.
[0264] The WTRU may use other modifications / measurements. The WTRU may measure the energy level of the D2DSS of the current SS, which may occur continuously or at a certain specified time period. If the measured signal strength falls below a predefined threshold, the WTRU may perform prioritization and / or the WTRU may decide to become a synchronization source.
[0265] The WTRU may perform an update of the prioritization list when the measured energy level of D2DSS from an SS other than the current SS changes. An example would be when the measured energy level of D2DSS from the other SS increases above a predefined threshold or becomes greater than the energy level of D2DSS of the current SS.
[0266] The measured energy level may be weighted (eg, divided in the dB domain, subtracted in the dB domain, or otherwise modified) by a thermal noise measurement / estimation performed by the WTRU.
[0267] The WTRU may apply prioritization. The WTRU may apply the new timing at a particular synchronization frame time instant (e.g., the WTRU may not apply the new timing to the current synchronization frame, but to the beginning of the next synchronization frame). Given that there may be a timing difference between the old and new synchronization timing references, a gap in the synchronization frame may correspond to such a difference.
[0268] The WTRU may be configured to not update the prioritization list when one or more of the following triggers are met: The WTRU may not update the prioritization list when it is transmitting or receiving data. The WTRU may not update the prioritization list when the WTRU is within a timer-triggered period.
[0269] The WTRU may be configured to prioritize data reception. Due to practical hardware considerations, the WTRU may not be able to simultaneously track an unlimited number of synchronization zones in practice. A practical WTRU may be able to decode a limited number of scheduling announcements (SAs) in a subframe. The WTRU may be configured to prioritize synchronization zones for data reception. The WTRU may be configured to prioritize synchronization zones for data reception based on one or more prioritization information.
[0270] The synchronization ID associated with a synchronization source may be prioritization information used by the WTRU to prioritize synchronization zones for data reception. The WTRU may be configured to determine the synchronization source ID and decide whether to prioritize this synchronization source ID based on, for example, a predefined rule / configuration.
[0271] The synchronization type associated with a synchronization source may be prioritization information used by the WTRU to configure to prioritize synchronization zones for data reception. The WTRU may be configured to determine the synchronization type and determine a priority based on the type. The WTRU may be configured to prioritize data reception sources that are base stations, eNBs, or sources connected to the base station or eNB over independent sources (e.g., independent sources may have a lower priority).
[0272] The group ID associated with a synchronization zone may be prioritization information used by the WTRU to prioritize synchronization zones for data reception. The WTRU may determine the group ID associated with a synchronization zone by decoding the PD2DSCH. The group ID may be within a detected SA associated with that synchronization zone. The WTRU may prioritize synchronization zones for which one or more group IDs associated with the WTRU may be configured and / or supported.
[0273] The WTRU hardware capabilities may be prioritization information used by the WTRU to configure the prioritization of synchronization zones for data reception. The WTRU may prioritize when the number of sources is greater than the WTRU is capable of decoding within a set time / latency.
[0274] The WTRU reception / transmission pattern may be prioritization information used by the WTRU to configure the prioritization of synchronization zones for data reception. Due to its reception / transmission pattern, the WTRU may not be able to receive data from another synchronization zone. In such a case, this synchronization zone may not be prioritized.
[0275] The WTRU may be configured to transmit a synchronization signal (D2DSS). The D2D WTRU may be configured to transmit a synchronization signal. The following describes methods related to transmitting a synchronization signal (e.g., D2DSS).
[0276] The WTRU may be configured to determine the frame synchronization timing. The D2D WTRU may be configured to transmit a synchronization source synchronization signal (e.g., D2DSS) and be a synchronization source. In such a case, the WTRU may be configured to determine its own synchronization frame timing. The WTRU may be configured to determine the D2D synchronization frame using one or more of the following:
[0277] The WTRU may determine the D2D synchronization frame based on its internal timing. The WTRU may arbitrarily determine the D2D synchronization frame timing based on, for example, an internal clock of the WTRU.
[0278] The WTRU may determine the D2D synchronization frame based on external timing. The WTRU transmitting the D2D synchronization frame may be in the vicinity of other devices transmitting synchronization signals (e.g., other D2D WTRUs, network synchronization sources such as eNBs, etc.). In such a case, if the WTRU is configured to be a synchronization source, it may be configured to base the D2D synchronization frame based on these signals. This configuration may provide the benefit of aligning adjacent D2D synchronization zones, for example, to mitigate interference.
[0279] The WTRU may align its D2D synchronization frame to another received D2D synchronization frame. The WTRU may align its D2D synchronization frame to a received reference D2D synchronization frame (e.g., the D2D synchronization frame corresponding to the highest priority D2DSS).
[0280] The WTRU may align its D2D synchronization frames such that overlapping control channel regions are reduced. This configuration may provide the benefit of mitigating interference between control channels.
[0281] The frame format may be based on the WTRU ID. When a D2D WTRU becomes a synchronization source, the D2D WTRU may be configured to determine an initial value of a D2D synchronization frame counter or D2D synchronization frame number (D-SFN). The WTRU may be configured to initialize a value of the D-SFN based on a WTRU identifier (e.g., IMSI, D2D Association ID, RNTI, etc.). This configuration may provide the benefit of randomizing the D-SFN between adjacent synchronization zones and potential associated frequency-time resource configurations.
[0282] A WTRU may be configured to transmit a preamble and / or a postamble. A WTRU monitoring D2D data transmission may receive data from multiple synchronization zones. The receiving WTRU in this case may acquire an associated synchronization frame for its transmission. A D2D transmitting WTRU (e.g., a WTRU transmitting D2D data) may be configured to transmit a D2DSS, for example, when transmitting a data communication to not limit the range of the D2D communication.
[0283] The WTRU may transmit a synchronization preamble before sending data. A WTRU for D2D transmission may be configured to transmit a synchronization preamble before transmitting actual data. The WTRU may be configured to transmit D2DSS or other information (e.g., PD2DSCH) for a preconfigured period of time before starting to transmit data, e.g., as shown in FIG. 9.
[0284] The WTRU may transmit a synchronization postamble after transmitting data. The WTRU may be configured to transmit a D2DSS for a predetermined period of time after transmitting its last data packet. This configuration may have the benefit of ensuring that the WTRU does not stop transmitting a synchronization signal, for example, if more data is to arrive in the buffer and if the WTRU synchronization signal is being relayed by other WTRUs.
[0285] The WTRU may be configured to start an inactivity timer when the last data packet is transmitted. The WTRU may reset the timer when new data is being transmitted. When the timer expires, the WTRU may be configured to stop transmitting the synchronization signal.
[0286] The WTRU may determine when to start transmitting synchronization signals or messages. The WTRU may trigger the transmission of synchronization messages and / or signals (e.g., as either a source or forwarding / cooperating WTRU) due to one or more of the following triggers:
[0287] The WTRU may detect a trigger based on an explicit indication from the network. The trigger may be received by the WTRU from an eNB / ProSe function / application to start / stop operation of the PS mode or explicit configuration by the base station or eNB to detect any of the triggers described herein.
[0288] A WTRU may detect a trigger based on detection of another synchronization signal. A WTRU may detect another WTRU transmitting a synchronization signal originating from a source with a lower priority than the WTRU's serving synchronization source. A WTRU connected to an eNB (e.g., in an in-coverage state) may decide to start transmitting a synchronization signal or message when it detects a synchronization message or signal from an out-of-coverage WTRU. This may enable an out-of-coverage WTRU to find an in-coverage WTRU and synchronize to the WTRU's reception / transmission opportunity.
[0289] The WTRU may detect at least one of: another WTRU transmitting a synchronization signal originating from a source of lower priority than the WTRU's serving synchronization source; and a group ID of a second WTRU that belongs to the same group ID as the first WTRU.
[0290] The WTRU may be an in-coverage WTRU and may detect a synchronization signal of an out-of-coverage WTRU or an out-of-coverage WTRU.
[0291] The WTRU may use group IDs, where at least one of the communication group IDs of the second WTRU belongs to at least one of the group IDs of the first WTRU.
[0292] The WTRU may receive data from a second WTRU and determine that the second WTRU is not in coverage of the base station or eNB, for example, using some indication in the SA that the WTRU is not in coverage in the absence of a D2DSS or message.
[0293] The WTRU may use a timer based on the lack of other synchronization signals. The timer from the last synchronization signal reception may have expired. If the WTRU has not received a synchronization signal or message from the source, the WTRU may decide to become the source signal.
[0294] The WTRU may decide to become a synchronization source based on, for example, the measured power falling below a threshold.
[0295] The WTRU may decide to begin transmitting a synchronization signal if the following is detected (eg, as described herein):
[0296] The WTRUs may use a time pattern / resource. The first WTRU may determine that the second WTRU is using a different time pattern than the first WTRU.
[0297] The WTRUs may be configured to detect differences in frequency of operation such that the first WTRU may be connected for communication at a frequency other than the frequency of operation of the second WTRU.
[0298] The WTRU may determine when to stop and / or change transmission of synchronization signals and / or messages. The WTRU may stop and / or change transmission of synchronization signals when one or more of the following triggers (e.g., conditions) are met: The trigger may be an explicit configuration from the network (e.g., the network explicitly configures the WTRU to stop transmitting); A timer-based trigger, where the WTRU may stop transmitting synchronization signals after a configured period of time; The trigger may be based on data activity, which may include an indication that the WTRU has not performed data transmission for a configured period of time; The trigger may be based on an indication that an application process no longer requires service; The trigger may be based on an indication that the WTRU has not detected data activity (e.g., no SA detected) from any neighboring WTRU; Detection of another synchronization signal, where detection of a higher priority source or another WTRU may trigger the WTRU to stop transmitting its current synchronization signal and / or change the transmitted synchronization message and / or signal.
[0299] The WTRU determines that it may stop and / or a change may be performed, for example, based on the transmission of a synchronization signal. For example, if one or a combination of the following conditions are met, the WTRU determines that it may stop and / or a change may be performed. For example, if the WTRU detects a synchronization signal from a higher priority source (e.g., the originating source is a base station or an eNB), the WTRU determines that it may stop and / or a change may be performed. This metric may include received synchronization signal power above or below a configured threshold. For example, if the WTRU detects a synchronization signal from a second WTRU, the WTRU determines that it may stop and / or a change may be performed. The WTRU may determine that the synchronization signal from the second WTRU has the same originating source and has a smaller hop count than its current hop count. This metric may include received synchronization signal power above or below a configured threshold.
[0300] For example, if the WTRU detects a synchronization signal from a source of the same priority and a hop count less than the current WTRU hop count, the WTRU determines that it may shut down and / or a change may be performed. This metric may include a received synchronization signal power above or below a configured threshold. The WTRU determines that it may shut down and / or a change may be performed in response to determining that the re-evaluated hop count has reached (e.g., or is greater than) a maximum allowed value. For example, if the detected WTRU (e.g., based on a synchronization signal or SA) is connected to a base station or eNB, the WTRU determines that it may shut down and / or a change may be performed. For example, if the detected WTRU (e.g., based on a synchronization signal or SA) belongs to the same group as the first WTRU, the WTRU determines that it may shut down and / or a change may be performed.
[0301] For example, the WTRU may stop D2DSS transmission if one or more of the following criteria are met. The WTRU may stop D2DSS transmission in response to determining that the synchronization timer has expired and is not running. The WTRU may start a synchronization timer when one or more of the following conditions are met. The WTRU may start a synchronization timer when the WTRU becomes a synchronization source and starts a synchronization signal / message transmission. The WTRU may start a synchronization timer when the WTRU becomes a synchronization source based on other detected synchronization signals (e.g., as described herein). The WTRU may start a synchronization timer when the timer is restarted, e.g., when the WTRU receives data or detects a scheduling assignment between transmissions (e.g., there may be other WTRUs connected to this cluster). The WTRU may start a synchronization timer based on data activity, e.g., as described herein. The WTRU may start a synchronization timer based on a determination that other WTRUs are not relaying a synchronization message being transmitted by the WTRU, e.g., as determined from measuring a higher hop count while being D2DSS of the same source ID.
[0302] If one or more of the criteria for stopping transmitting synchronization messages are met but the synchronization timer is running, the WTRU may decide to modify the synchronization signals and messages it is transmitting, which may be used, for example, to reflect or relay at least a portion of a detected synchronization message of higher priority.
[0303] When the WTRU determines that it should cease to be a synchronization source, the WTRU stops transmitting synchronization signals and / or determines that a synchronization signal change has been triggered. When the measurements exceed a predefined threshold, the WTRU may determine that it no longer needs to be a synchronization source.
[0304] In response to determining that other WTRUs are not relaying the WTRU's synchronization message, the WTRU may determine whether other WTRUs are relaying the message by doing one or more of the following: The WTRU may monitor D2DSS signals with the same source ID but a higher hop count to determine whether there is an associated synchronization message. The WTRU may detect a synchronization message by detecting a synchronization message carrying the same content, possibly indicating a higher hop count and / or having the same source ID.
[0305] The WTRU may receive a synchronization channel message. The synchronization source and / or the synchronization forwarding entity may transmit a synchronization message. The synchronization information may be explicitly transmitted as a message or the information may be implicitly derived from the synchronization reference signal characteristics.
[0306] For example, the synchronization message may be sent on a D2D data channel (e.g., a traffic channel). The synchronization message may be transmitted by the WTRU using a traffic MAC PDU. For example, an indication in the MAC header may be included to allow the receiving WTRU to identify this message as a control message. The WTRU may decode this message and / or use the contents of the message. Control messages (e.g., RRC, SIB, etc.) may be transmitted on a MAC PDU. The logical channel value reserved for the control message may indicate to the receiving WTRU that this is a control message.
[0307] The WTRU may use the PD2DSCH transmission format and characteristics. The PD2DSCH may be associated with a particular synchronization signal. To enable the receiving WTRU to determine the PD2DSCH associated with the received D2DSS, the WTRU may use one or more of the following:
[0308] PD2DSCH may be transmitted within the same frequency resources as D2DSS. Once the D2D synchronization frame is acquired, the WTRU may unambiguously search for PD2DSCH. This example embodiment may not be too complex to implement, but may not be robust enough to withstand interference from other PD2DSCH or data transmitted within the same set of T / F resources.
[0309] The PD2DSCH scrambling sequence may be based on a synchronization source ID. The WTRU may be configured to use a scrambling sequence associated with the D2DSS (e.g., or a synchronization zone ID, group ID, etc.) for the PD2DSCH. The synchronization source ID may be used to index a particular scrambling sequence for the PD2DSCH. This example embodiment may provide the benefit of interference whitening and may mitigate the possibility of adjacent synchronization sources using the same synchronization source ID.
[0310] The SA may indicate the PD2DSCH resource using a special identifier that links the synchronization source ID. The T / F location of the PD2DSCH may not be predefined, but may be transmitted along with the Scheduling Assignment (SA), e.g., as with D2D data transmissions. The WTRU may be configured to use one or more special values (e.g., special destination group IDs) in the SA to ensure that other WTRUs can properly decode the PD2DSCH. The contents of the SA (e.g., source ID) may be associated with the D2DSS or synchronization source in order for the receiving WTRU to associate the PD2DSCH with the appropriate synchronization source or frame.
[0311] The PD2DSCH may be explicitly indicated based on a logical channel ID in the MAC header. The WTRU may receive the PD2DSCH over a normal D2D communication channel. The WTRU may decode the channel based on the SA destination ID or source ID code. The WTRU may determine, for example, based on the MAC header (e.g., via a special logical channel ID, or other explicit MAC indication), that the content of the communication is a D2D synchronization message.
[0312] The WTRU may detect, select, or receive an indication of a PD2DSCH format. The WTRU may be configured to transmit the PD2DSCH in multiple physical layer formats. For example, the physical layer format may include one or more PRBs, one or more OFDM symbols, a coding scheme, a coding rate, puncturing, CRC, etc. The physical layer format may support different payload sizes (e.g., depending on the content). Different payload sizes in the PD2DSCH may support a PD2DSCH that may carry more (e.g., or less) information based on the coverage status of the WTRU. The coverage status of the WTRU may include in coverage, out of coverage, etc.
[0313] The WTRU may determine the PD2DSCH format to use. For example, a WTRU transmitting a PD2DSCH may be configured to determine the PD2DSCH format based on a payload size. The WTRU may be configured with a set (e.g., a fixed set) of PD2DSCH formats that support corresponding payloads (e.g., a fixed set payload). The WTRU may select a format (e.g., to maintain an appropriate coding rate). The WTRU may determine the contents of the PD2DSCH payload based on the coverage state. The WTRU may be configured to select a PD2DSCH format based on the coverage state. For example, the WTRU may select a first PD2DSCH format when the WTRU is in coverage. As another example, the WTRU may select a second PD2DSCH format when the WTRU is out of coverage.
[0314] The WTRU may determine the PD2DSCH based on the associated D2DSS signal. A WTRU transmitting the PD2DSCH may be configured to select one or more parameters of the associated D2DSS. The one or more selected parameters may indicate a PD2DSCH format. For example, the WTRU may be configured to select a primary synchronization signal (PSS) portion of the D2DSS to indicate that the source is out of coverage and / or to indicate (e.g., implicitly indicate) the PD2DSCH format. A WTRU monitoring the PD2DSCH may be configured to determine the format of the PD2DSCH based on the D2DSS signal associated with the PD2DSCH. For example, the WTRU may determine one or more characteristics of the D2DSS (e.g., a Zadoff-Chu root associated with a signal, such as a PSS, of the D2DSS). The WTRU may determine the format of the associated PD2DSCH via a predefined associated rule. For example, the WTRU may be configured to determine whether a WTRU transmitting a D2DSS is in-coverage or out-of-coverage (e.g., out of network coverage). The WTRU may determine (e.g., implicitly determine) the format of the associated PD2DSCH based on the coverage state of the transmitting WTRU.
[0315] The WTRU transmits the PD2DSCH using different resources when retransmitting with a different hop count. When the WTRU retransmits or relays the PD2DSCH with a different hop count (e.g., in the same synchronization zone), the WTRU may be configured to mitigate interference using different time-frequency resources. The WTRU may be configured to transmit the PD2DSCH in a specific time location, which may depend on the hop count. The WTRU may transmit the PD2DSCH in a specific D2D sync frame number associated with the hop count. The WTRU may be configured to transmit the PD2DSCH in a specific frequency location, which may depend on the hop count. The WTRU may transmit the PD2DSCH in a specific frequency offset associated with the hop count. The WTRU may be configured to transmit the PD2DSCH using a predefined time-frequency pattern, which may depend on the hop count.
[0316] The WTRU may determine the content of the synchronization message. The synchronization message may include one or more of the following content information: The synchronization message may include a resource pool, indicating that the WTRU may have a receiving pool and / or a transmitting pool. The WTRU may be configured to use the resource pool. The WTRU may determine the receiving pool as the collection of resource pools from different received synchronization sources / relays and the transmitting pool from the resource pool received from the serving synchronization source / relay. The synchronization message may include a resource pool index (e.g., a resource pool configuration index).
[0317] The synchronization message may include a subset of resources in a resource pool or a D2D pattern usable by the receiving WTRU for D2D transmissions and / or D2D scheduling assignments. The message may include a proposed time pattern (e.g., cycle, duration, etc.), a frequency that the remote WTRU may use for D2D transmissions. The proposed time pattern may include a time pattern received from a base station or eNB (e.g., or another source entity). The proposed time pattern may be determined autonomously within the cooperating WTRU based on information available to the WTRU. For example, the cooperating WTRU may determine the proposed time pattern based on services supported by the WTRU. For example, in the case of a single receiver WTRU, the cooperating WTRU may be receiving an MBMS transmission and the cooperating WTRU may determine the proposed time pattern to enable WTRU reception on MBMS subframes configured by the eNB.
[0318] The resources may include an index (e.g., index) that describes the resources (e.g., in time / frequency) in the resource pool that the remote WTRU may use. The synchronization message may include a source identifier that may include an identity of a source node generating the resource configuration. The identity may include one or more of a BS ID, an eNB ID, a cell ID, a PCI number, the PLMN of the cell, a WTRU-specific ID, a ProSe ID, a ProSe group ID, a ProSe application ID, and / or an indication of whether the source is a base station or an eNB or another type of source (e.g., another WTRU or a cluster head). The synchronization message may include a WTRU identifier to identify the WTRU performing the transmission. The identity may include one or more of a BS ID, an eNB ID, a cell ID, the PLMN of the cell, a WTRU-specific ID, a ProSe ID, a ProSe group ID, a ProSe application ID.
[0319] The synchronization message may include location information. The location information may be associated with an in-coverage WTRU. The WTRU (e.g., transmitting and / or receiving) may determine its location based on, for example, a cell ID, GPS information, or other location information, and append the location information to the control message. The synchronization message may include a hop count indicating the number of hops from the source node, or an indication of whether the transmitting entity is the source entity. The synchronization message may include a frame number (e.g., SFN number) and / or a time reference number used as a reference to synchronize the receiving and / or transmitting patterns.
[0320] The synchronization message may include an indication that the WTRU is within the coverage of a base station or eNB. The synchronization message may include a data relay indicating whether the WTRU is a data relay and an associated ID. Further configuration related to the relay network may be indicated, for example, a set of supported APNs or network IDs. The synchronization message may include a last link condition, which may indicate that the WTRU may transmit a value characterizing the channel, or a link condition for that link to a previous hop or synchronization source / network, depending on the scenario. The value may be based on a measurement. The measurement may be RSRP averaged over a certain period of time or may represent an error rate.
[0321] The synchronization message may include an aggregate link condition, where the WTRU may send a value characterizing the aggregate channel, or link condition considering all links to the synchronization source / network, depending on the scenario. The value may be based on measurements, e.g., RSRP averaged over a certain period of time. The value may represent an error rate. The WTRU may determine this value by adding the conditions transmitted on the previous hop PD2DSCH and the previous hop conditions measured by the WTRU.
[0322] The synchronization message may include a scheduling period. The WTRU may transmit within the scheduling period.
[0323] The WTRU may be configured to detect conditions for transmitting PD2DSCH. The WTRU may transmit PD2DSCH when it becomes an independent synchronization source and transmits D2DSS. The WTRU may transmit D2DSCH when it relays synchronization from another source. The WTRU may transmit PD2DSCH when it determines that it must transmit using a particular pattern (e.g., the WTRU has limited transmit / receive opportunities). The WTRU may transmit PD2DSCH when the WTRU is in-coverage state and is triggered to become a synchronization signal / message transmitter.
[0324] The WTRU may use rules to determine the contents of the PD2DSCH. When transmitting the PD2DSCH, the WTRU may be configured with a set of predefined values for one or more of the parameters carried on the PD2DSCH, and the WTRU may be further configured to determine values for the one or more parameters.
[0325] For example, the WTRU may determine the resource pool as described herein. The WTRU may transmit the resource pool configuration in a PD2DSCH.
[0326] The WTRU may determine a transmission and / or reception pattern to use to communicate. This configuration may be beneficial to ensure that the WTR may be able to operate as a relay and / or that the WTRU may maintain a connection with a base station or eNB or another synchronization zone. The WTRU may determine a transmission and / or reception pattern to use and send a configuration for PD2DSCH. The new pattern may be determined, for example, from a set of allowed predefined patterns (e.g., indexed in a specification).
[0327] The WTRU may determine (e.g., autonomously determine) a pattern based on one or more of the following: The WTRU may select a pattern based on patterns already configured to communicate with the network, e.g., the WTRU may select a pattern that maximizes the WTRU's opportunity to communicate with a base station or eNB. The WTRU may select a pattern based on adjacent synchronization zones. For example, the WTRU may determine patterns in adjacent zones and determine a pattern to use that minimizes interference with adjacent synchronization zones. The WTRU may select a pattern that does not overlap with its paging occasions when in IDLE mode and in coverage.
[0328] The WTRU may be configured to extend the PD2DSCH content. The PD2DSCH may be configured to carry information (e.g., a small amount of information), e.g., a subset of the information elements described herein. The PD2DSCH may be configured with a fixed, known physical transport format. The WTRU transmitting the PD2DSCH may be configured to broadcast control information, e.g., to indicate additional information related to radio resource management, support for relaying, configuration information, measurement information, etc. The PD2DSCH may be configured to carry a larger amount of information. The larger amount of information may vary in size. The WTRU may be configured to extend the content of the PD2DSCH.
[0329] As shown in FIG. 10, the PD2DSCH may include a scheduling assignment (e.g., a special form of a scheduling assignment). The PD2DSCH may include a format of a scheduling assignment (e.g., a special form of a scheduling assignment). The PD2DSCH carrying the scheduling assignment may be referred to herein as a PD2DSCH-SA. For example, the PD2DSCH-SA may be transmitted using the same rules as a regular SA. The PD2DSCH-SA may carry additional information than a regular SA, for example, the PD2DSCH-SA may carry one or more of the following elements: a resource pool, a subset of resources, a source identifier, a WTRU identifier, location information, a hop count, an SFN number or a time reference number, an indication that the WTRU is in coverage, a data relay, a last link condition, and / or an aggregated link condition.
[0330] The scheduling assignment component of the PD2DSCH-SA may carry additional information. Data associated with the PD2DSCH-SA may carry additional PD2DSCH elements or other information. With reference to Figure 10, the PD2DSCH may carry both a PD2DSCH section and an SA section that may point to additional PD2DSCH related data. Examples of regular SAs and data associated with regular SAs are shown in Figure 10.
[0331] The receiving WTRU may be configured to distinguish between a regular SA and a PD2DSCH-SA. The receiving WTRU may distinguish between a regular SA and a PD2DSCH-SA based on one or more of the following approaches: The receiving WTRU may distinguish between a regular SA and a PD2DSCH-SA based on an identifier. An identifier (e.g., a special identifier, e.g., PD2DSCH-SA-ID) may be associated with the PD2DSCH-SA (e.g., replacing a conventional target identifier carried in the SA) and may be used to distinguish the PD2DSCH-SA from a normal SA. Upon reception of the identifier (e.g., PD2DSCH-SA-ID), the receiving WTRU may determine that the received SA is a PD2DSCH-SA that carries PD2DSCH-related information. The receiving WTRU may interpret the received bits according to the PD2DSCH-SA content. The transmitting UE may be configured to transmit a PD2DSCH-SA with an appropriate configured identifier.
[0332] The receiving WTRU may distinguish between regular SA and PD2DSCH-SA based on the format or CRC check. The receiving WTRU may be configured to blindly accept the distinction between PD2DSCH-SA and conventional SA based on the format and CRC of the received signal. For example, if the channel coder CRC checks, the receiving WTRU may be configured to attempt to receive the SA and PD2DSCH-SA and determine whether the received signal is regular SA or PD2DSCH-SA. The receiving WTRU may distinguish between regular SA and PD2DSCH-SA based on the resource on which the signal is received. The receiving WTRU may be configured to accept the distinction between PD2DSCH-SA and conventional SA based on the resource (e.g., time, frequency, or time / frequency combination) on which the signal is received. The WTRU may be configured with a set of resources that may be reserved for transmission of PD2DSCH-SA. When receiving a signal on these resources, the receiving WTRU may be configured to decode using the PD2DSCH-SA format. The transmitting WTRU may transmit the PD2DSCH-SA on resources reserved for PD2DSCH-SA transmission. The resources for PD2DSCH-SA transmission may be predefined (e.g., in the specification, via semi-static configuration, or on the USIM / application).
[0333] When the receiving WTRU determines that the received SA is a PD2DSCH-SA, the receiving WTRU may be configured to receive associated payload data. The associated payload data may be indicated within the SA portion of the PD2DSCH-SA. The receiving WTRU may apply one or more parameters of the PD2DSCH that the receiving WTRU receives. The transmitting WTRU may be configured to transmit an additional data payload associated with the PD2DSCH at an appropriate location within the time / frequency indicated in the SA portion of the PD2DSCH-SA. For example, one or more transmission parameters for the PD2DSCH data payload may be taken from a subset or a different set than conventional parameters for data transmission. The additional payload may consist of a limited amount of data and may not require multiple transmissions.
[0334] As shown in FIG. 11, the PD2DSCH may include (e.g., carry) a scheduling assignment. The PD2DSCH may be transmitted with one or more known, predetermined formats and may carry an SA. The SA carried in the PD2DSCH may include the same information as a conventional SA. The SA carried in the PD2DSCH may have a smaller payload. One or more of the fields in a conventional SA (e.g., target ID) may not be included in the SA carried in the PD2DSCH.
[0335] The receiving WTRU may be configured to receive the PD2DSCH and determine whether there is an SA carried in the PD2DSCH. If there is an SA carried in the PD2DSCH, the receiving WTRU may be configured to determine a location of the associated data, further decode the data, and interpret the information as additional PD2DSCH payload and / or data.
[0336] The D2D UE may be configured to determine whether additional PD2DSCH data is transmittable. The D2D UE may determine the format of PD2DSCH and / or the content of SA in PD2DSCH according to whether additional PD2DSCH information is transmittable. The D2D UE may appropriately set the value of SA in PD2DSCH and may transmit the additional data at the location indicated in the SA in PD2DSCH.
[0337] The WTRU may use PD2DSCH pointing to or associated with the SA. PD2DSCH may point to or be associated with the SA. PD2DSCH may point to the SA or be associated with the SA pointing to additional data. PD2DSCH and SA association may be determined based on PD2DSCH time / frequency or another parameter. SA location in time or frequency may be explicitly transmitted in PD2DSCH. Other WTRUs may not be allowed to select SA resources pointed to or associated with PD2DSCH. The pattern may be selected from a control-only pattern design or a special pattern design with a small number of transmissions.
[0338] The PD2DSCH may be associated with an SA, which refers to a data resource carrying additional PD2DSCH content. Solutions for associating the SA with the PD2DSCH may be described. The association between the SA and the PD2DSCH is implicit (e.g., based on one or more characteristics of the PD2DSCH). The transmitting WTRU may determine one or more transmit SA resources and / or parameters based on one or more of the PD2DSCH timing, the PD2DSCH physical resources (e.g., subframes, PRB indexes, etc.), the PD2DSCH identifier, and / or the associated D2DSS ID, physical resources, or timing. The receiving WTRU may determine one or more receive SA resources and / or parameters based on one or more of the PD2DSCH timing, the PD2DSCH physical resources (e.g., subframes, PRB indexes, etc.), the PD2DSCH identifier, and / or the associated D2DSS ID, physical resources, or timing.
[0339] The WTRU may be configured to determine a frequency resource for the SA associated with the PD2DSCH by determining a frequency (e.g., PRB) index associated with the PD2DSCH. The WTRU may be configured to determine a frequency resource for the SA associated with the PD2DSCH by determining a frequency (e.g., PRB) index associated with the PD2DSCH and may apply a mapping function thereto. For example, as shown in FIG. 12, the SA associated with the PD2DSCH may be transmitted in the same frequency resource in a subsequent subframe reserved for SA transmission (e.g., a 1-1 mapping function).
[0340] To avoid SA collisions, the transmitting WTRU may be configured to monitor the PD2DSCH and not transmit an SA on one or more resources associated with the PD2DSCH.
[0341] As shown in FIG. 13, the receiving WTRU may be configured to determine the location of the SA associated with the PD2DSCH based on an explicit indication carried in the PD2DSCH. Index The PD2DSCH may be referred to as the SA. The PD2DSCH may carry an explicit indication that the receiving WTRU may use to determine association to the PD2DSCH. The transmitting WTRU may be configured to select resources for transmitting the SA with the same rules as a normal SA, and the SA Index For example, an SA associated with a PD2DSCH may be transmitted in a subframe (e.g., a special subframe reserved for an SA associated with control information).
[0342] SA Index may be an index into the PRB. The receiving WTRU may implicitly determine the subframe information based on the transmission time of the PD2DSCH. For example, the subframe information may be the next available SA transmission subframe or the next available SA transmission subframe after a time (e.g., a minimum time) after the PD2DSCH is received (e.g., 2 ms).
[0343] SA index may carry time and frequency information for the receiving WTRU to determine resources (eg, exact resources) for the SA.
[0344] The transmitting WTRU may be configured to select an SA resource associated with the PD2DSCH from a reserved set of one or more SA resources, which may be reserved for transmission of control information.
[0345] The transmitting WTRU may be configured to monitor the PD2DSCH and determine one or more SA resources to be used for an SA transmission associated with the PD2DSCH. IndexThe PD2DSCH may use information carried in the SA resource assignment and may avoid selecting an SA resource from a set of SA resources known to be used for SA transmissions associated with the PD2DSCH.
[0346] The WTRU may be configured to select a data time pattern in which the PD2DSCH is extended. The transmitting WTRU may be configured to select a transmission pattern for transmission of an extended payload associated with the PD2DSCH or control data using a different mechanism than normal data. The transmitting WTRU may be configured to select one or more transmission parameters from a special set. For example, the transmitting WTRU may be configured to use a number (e.g., a special number) of HARQ transmissions and a repetition pattern reserved for transmission of control information or information requiring large coverage with a high probability.
[0347] The WTRU may be configured to coordinate resource usage. Once the WTRU is configured with resources for transmission of discovery signals, the WTRU may perform transmission accordingly. Once the WTRU is in coverage with an eNB, the resource pool and / or dedicated resources may be pre-configured and / or dynamically configured by the network. If the WTRU is out of coverage of the eNB, the WTRU may obtain the resource configuration from a stored pre-configuration and / or from a coordinating entity (e.g., a cluster head). For example, when the WTRU is in coverage of the same configuration entity and / or associated with configuration entities that are coordinated with each other, if discovery / communication is supported, the resources used by the transmitting and receiving entities may be coordinated. Problems may arise when the WTRU transmits and / or receives in multiple domains simultaneously, e.g., if discovery / communication is supported in an uncoordinated scenario.
[0348] For resource allocation, the WTRU may be pre-configured with a resource pool to transmit / receive when operating in out-of-coverage mode. In particular, every WTRU may also be pre-configured with resources to transmit and receive resource configuration information (e.g., where to transmit control information messages, e.g., synchronization messages). The WTRU may also be configured by a controlling entity which resources in the resource pool to use.
[0349] FIG. 14 illustrates example scenarios for in-coverage, out-of-coverage, and partial coverage D2D discovery and / or communication.
[0350] An in-coverage WTRU may discover and / or be discovered by neighboring WTRUs that may be controlled by other uncoordinated control entities and / or may operate in different spectra. Because the eNB may provide a resource pool for in-coverage discovery, a WTRU may not be able to discover and / or be discovered by neighboring WTRUs, for example, if the neighboring WTRUs are not monitoring the same resource pool. An in-coverage WTRU may move (e.g., move autonomously) into a public safety (PS) spectrum and / or an out-of-coverage spectrum to perform reception and / or transmission, which, for example, may result in loss of data and / or loss of paging reception, without network coordination. An in-coverage WTRU may be configured to coordinate the eNB and the in-coverage WTRUs.
[0351] An in-coverage WTRU may decide to communicate with an out-of-coverage WTRU acting as a WTRU-to-network relay with another WTRU, and / or may decide to communicate with a neighboring WTRU, which may determine the set of resources to use by pre-configuration and / or by a controlling entity (e.g., a cluster head) that may not be coordinated with the serving eNB. The resources and / or time used for transmission by the neighboring WTRU may correspond to subframes during which the in-coverage WTRU may be conducting normal cellular communications. The in-coverage WTRU may coordinate with the eNB to request times and / or resources during which it may communicate with the neighboring WTRU without adversely affecting the cellular connection with the eNB.
[0352] A WTRU may switch (e.g., autonomously switch) to transmitting and / or receiving on resources on which neighboring WTRUs are expecting to receive and / or transmit. This may result in data loss, the WTRU not transmitting in the UL, and / or missing paging occasions while in idle mode. To avoid data loss and / or missing paging, coordination between eNBs, in-coverage WTRUs, out-of-coverage WTRUs, and / or controlling entity out-of-coverage WTRUs may be provided, for example, for WTRUs using single transmission and / or reception. Coordination may include coordination of the time pattern on which this communication is expected to occur and / or coordination of resources (e.g., frequency and / or time) on which this communication and / or discovery may occur.
[0353] The coordination may be intended to allow the controlling entity to align resources in use by the WTRUs involved in the communication and / or be aware of scheduling restrictions during these time periods.
[0354] The network and / or coordinating entity may be made aware of resource allocation conflicts, so that, for example, the network may reallocate resources and / or schedule WTRUs accordingly. For example, this may be performed for communication across different clusters that may be controlled by different entities. An eNB may refer to a cluster head and / or controlling entity in a group and / or cluster. An in-coverage WTRU may refer to a WTRU connected to a cluster head and / or controlling entity. A neighboring WTRU, a PS WTRU, and / or an out-of-coverage WTRU may refer to a WTRU configured to operate in direct communication. The resource pool and / or configuration for neighboring WTRUs, a PS WTRU, and / or an out-of-coverage WTRU may be controlled by a different, and / or uncoordinated, controlling entity than the in-coverage WTRU and / or resources are pre-configured.
[0355] The methods described herein relating to in-coverage and out-of-coverage may be applicable to enable coordination between WTRUs that may be controlled by different uncoordinated controlling entities or eNBs, etc.
[0356] An in-coverage WTRU may coordinate, request gaps, and / or request resources to communicate with an out-of-coverage WTRU. FIG. 15 is a diagram of an example scenario of communication between an in-coverage WTRU and an out-of-coverage WTRU. The WTRU may be configured to perform interactions between the in-coverage WTRU and the out-of-coverage WTRU, for example, to negotiate resource allocation for an out-of-network link (e.g., PC5). The WTRU may be configured to perform interactions between the in-coverage WTRU and the eNB, for example, to support resource reconfiguration and / or gap / pattern configuration. The examples described herein may apply when an in-coverage WTRU performs public safety communication directly over public safety resources.
[0357] The WTRU may be configured to negotiate resource allocation for the out-of-coverage link. The in-coverage WTRU may have a coordinated time and / or gap pattern, e.g., so it may not coordinate with the cellular link without risk of losing data. The out-of-coverage WTRU may know when and / or where to expect to receive and / or transmit, e.g., to ensure that the interested parties can receive the communication.
[0358] A pattern for communication may refer to a time pattern (e.g., a period, a cycle, a duration, etc.) in which a WTRU may transmit and / or receive. A pattern for communication may refer to a time pattern for reception and a time pattern for transmission. A pattern for communication may include resource information such as, for example, frequencies, subframes, PRBs, etc.
[0359] An out-of-coverage WTRU may determine and / or drive resource allocation. FIG. 16 is a diagram of an example of signals that an out-of-coverage WTRU may use to determine and / or drive resource allocation. Resource allocation may refer to time, gap pattern, and / or time and / or frequency configuration for the PS link. For example, an out-of-coverage WTRU may provide and / or broadcast (e.g., within known pre-configured resources) the resource allocation configuration that it is configured to use and / or be in use for communication. Resource allocation may take the form of an SA, a broadcast synchronization message, a control message, etc. The resource configuration may include the time and / or frequency pattern that the PS WTRU expects to transmit and / or receive.
[0360] The WTRU may provide the resource configuration when it determines that an in-coverage WTRU is present. The WTRU may provide the resource configuration periodically or always and / or before data transmission. The WTRU may provide the resource configuration when a WTRU operating in a different spectrum is expected.
[0361] A WTRU (e.g., an in-coverage WTRU) may receive a configuration and / or a time pattern (e.g., from an out-of-coverage WTRU). The WTRU may communicate the configuration information to the eNB in a report. The information communicated to the eNB may include a recommended gap pattern and / or frequency resources for the out-of-coverage WTRU, e.g., for the out-of-coverage WTRU to use to communicate. The in-coverage WTRU may decide to send this information to the eNB, e.g., if it determines that the out-of-coverage WTRU is a WTRU that belongs to the same group as the in-coverage WTRU (e.g., the WTRU is allowed to receive from this device). The eNB may, for example, reconfigure a resource pool that it uses (e.g., for discovery and / or communication) and / or provides gaps and / or scheduling opportunities for the in-coverage WTRU to listen to the out-of-coverage link, with the resources provided by the out-of-coverage WTRU. The eNB may provide the gap pattern. The eNB may approve the use of the proposed gap pattern.
[0362] For example, if the timing and / or reference frame numbers used to determine scheduling opportunities differ between in-coverage WTRUs and neighboring WTRUs, the gap pattern may be translated and / or adjusted depending on the timing used by the controlling entity.
[0363] The WTRU may determine and / or be driven by the eNB and / or in-coverage WTRU. FIG. 17 is a diagram of an example of signaling that the eNB and / or in-coverage WTRU may use to determine and / or drive resource allocation. Resource usage allocation for the out-of-coverage link may be driven by the in-coverage WTRU and / or the eNB. For example, the out-of-coverage WTRU may transmit (e.g., broadcast) a resource allocation pool that it may use to select resources for operation, and / or the in-coverage WTRU may know the resource pool via pre-configured information. The in-coverage WTRU may determine the resource pool that the neighboring WTRU is using, for example, once it detects the out-of-coverage WTRU. The in-coverage WTRU may not receive this information from the out-of-coverage WTRU, and / or it may rely on a pre-configured resource pool for the PS it has. The network may be aware of the pre-configured resource pool for the PS WTRU.
[0364] A WTRU (e.g., an in-coverage WTRU) may, for example, send a report to the eNB based on one or a combination of triggers described herein (e.g., upon deciding to communicate as a PS WTRU and / or to a neighboring or remote WTRU, or upon deciding to act as a relay). The contents of the report may be described herein, for example, the report may include a resource pool that the neighboring PS WTRU may use, a recommended time pattern, a preconfigured time pattern, a request for resources to act as a relay, a request for a service (e.g., an MBMS service group requested by the remote WTRU), etc.
[0365] The eNB, for example upon receiving this request, may determine scheduling opportunities and / or gaps to allocate to the in-coverage WTRU for PS communication and / or discovery, and / or may transmit a gap pattern and / or time pattern and / or resource configuration to the WTRU or may authorize the use of the requested time pattern.
[0366] In the case of idle mode operation, the in-coverage WTRU may determine a time pattern that enables the in-coverage WTRU to be out of sync with the serving eNB and successfully perform communications with neighboring WTRUs, for example based on a discovery resource pool (e.g., time pattern and / or frequency) allocated for in-coverage and / or a paging occasion.
[0367] An in-coverage WTRU may be configured by the eNB with a reception time pattern for communication with other WTRUs (e.g., in-coverage and / or out-of-coverage to the eNB) and / or the in-coverage WTRU may have a pre-configured pattern.
[0368] The in-coverage WTRU may, for example, transmit messages and / or report to neighboring WTRUs based on a determined pattern (e.g., from an eNB and / or determined internally). The messages may be transmitted as broadcast messages, as synchronization messages, and / or as dedicated messages to the WTRUs and / or by using control messages that may be received by WTRUs belonging to the same group. The messages and / or reports may indicate resource allocations, time patterns, and / or frequencies on which the in-coverage WTRUs may transmit and / or receive. The neighboring WTRUs may relay and / or transmit (e.g., broadcast) the messages and / or patterns to its controlling entity, which may, for example, adjust and / or configure neighboring WTRUs with the requested pattern and / or transmit a new proposed pattern.
[0369] The eNB may provide the WTRU with a special resource configuration (e.g., by specifying the frequency and / or time, e.g., subframes and / or PRBs) that the out-of-coverage WTRU may transmit and / or receive with the in-coverage WTRU, in addition to, for example, the gap pattern and / or time pattern, where, for example, the frequency may correspond to the in-coverage resource pool. An out-of-coverage WTRU may be a standalone unattached out-of-coverage WTRU that may attempt to connect to a network using an in-coverage WTRU as a WTRU-NW (network) relay. An out-of-coverage WTRU may be in communication with other in-coverage WTRUs and / or out-of-coverage WTRUs.
[0370] A WTRU may be configured to facilitate interaction between in-coverage and out-of-coverage WTRUs. When a WTRU starts operating in a relay and / or PS mode, the WTRU may transmit one or more D2D synchronization signals (D2DSS) and / or control messages (e.g., synchronization messages). The WTRU may advertise its ability to operate as a relay and / or PS node in the control message. Neighboring WTRUs operating nearby that are looking for a cooperating entity may monitor (e.g., periodically monitor) the D2DSS control symbols and / or detect the WTRU (e.g., an in-coverage WTRU, an out-of-coverage WTRU, a relay WTRU, etc.). A trigger for a WTRU to start operating as a relay node may be based on pre-configuration, based on measurements, based on an explicit trigger from the network and / or from a ProSe server, etc.
[0371] An in-coverage WTRU may send resource pool information, get a positive response, send a report to the eNB, etc. A WTRU that is triggered to operate as a relay and / or as a PS node may operate in an unsolicited mode. For example, a WTRU may advertise itself as a relay and / or a PS node. The WTRU may send an advertisement message with one or more ProSe parameters (e.g., ProSe WTRU id, security, ProSe group ID, etc.) and / or the resource pool that it may be in use for links with out-of-coverage WTRUs and / or other PS nodes. The WTRU may operate as a cluster head and / or add this information as part of a cluster configuration message, for example for a synchronization message. This may be used by the WTRU to support open discovery. A control message may carry the resource configuration indicated by the eNB.
[0372] The out-of-coverage WTRU may send a response accepting the configuration parameters. The response message may indicate one or more (e.g., a subset) of the resources in the pool that are acceptable to the out-of-coverage WTRU. For example, as described herein, the relay and / or PS node WTRU may send a report with this information to the eNB. The eNB may accept this configuration. The eNB may configure the gap and / or reconfigure resources to enable the relay WTRU and / or PS node to operate with the out-of-coverage WTRU and / or PS node that uses the gap.
[0373] The WTRU may use resources to relay control messages (e.g., synchronization messages). A WTRU acting as a relay may request resources to relay control messages. A WTRU acting as a relay may relay control messages using semi-statically allocated resources informed by the eNB (e.g., using SIB signaling). A WTRU acting as a relay may relay control messages using pre-configured resources. Resources may be explicitly pre-configured for control messages and / or the WTRU may select (e.g., autonomously select) resources from a resource pool that will be used to relay the control message.
[0374] An out-of-coverage WTRU may request resource pool information, obtain the information, send a report to the eNB, etc. A remote WTRU and / or a PS node WTRU may send a solicitation message requesting any neighboring WTRUs capable of operating in relay and / or PS mode. The remote WTRU may request a special service in the solicitation message (e.g., request to forward an MBMS service indicated using MBMS TMGI). The WTRU may operate as a cluster head. The WTRU may include the resource pools it expects to use for transmission and / or reception and / or are in use in the cluster configuration message, e.g., for synchronization messages. A WTRU (e.g., operating in relay and / or PS mode and / or having the capability to operate in the requested mode) may detect this node and / or respond by declaring itself a relay and / or PS node. The response message may indicate parameters identifying itself as a ProSe node (e.g., ProSe WTRU id, ProSe group ID, etc.), security configuration, etc. The responding WTRU may request a different resource pool based on, for example, capabilities and / or existing gap pattern configurations.
[0375] The relay and / or PS node WTRU may, for example, send a report to the eNB with this information (e.g., as described herein) once resource negotiation is completed. This mode may support targeted discovery. The eNB may allow configuration and / or configure gaps and / or reconfigure resources to enable the relay WTRU and / or PS node to operate with out-of-coverage WTRUs and / or PS nodes that use the gaps.
[0376] The WTRU may be configured to coordinate communications from cooperating WTRUs. The WTRU may send a report. The WTRU may identify one or more (e.g., all) of the resources in the report. The reporting mechanism, the WTRU, and / or the WTRU sending the message may be used to enable coordination of time and / or resources used by WTRUs in the coverage of different cells and / or clusters controlled by uncoordinated entities. The reporting may include resource allocations where the out-of-coverage link assists the controlling entity and / or transmitting entity to determine scheduling opportunities and / or resource allocations. The resource allocation information may include information relayed, transmitted, broadcasted by neighboring WTRUs, and / or available (e.g., configured or pre-configured) in the in-coverage WTRU.
[0377] The reporting (which may include, for example, format, triggers, time windows, etc.) may be configured by the network (e.g., by a network node such as an eNB). The network node may configure one or more WTRUs configured to operate in a particular D2D communication mode. Receipt of this report by the network may trigger an action.
[0378] The report may be transmitted to the cooperating entity and / or may be transmitted in the form of a broadcast message, as part of a synchronization message, as a dedicated message by the cooperating (eg, in-coverage) WTRU, etc.
[0379] The report and / or the transmitted message triggered by the WTRU may include resource configurations from neighboring WTRUs. For example, the report may indicate resource pool information obtained from neighboring entities (e.g., the WTRU, the cluster head and / or eNB, and / or the out-of-coverage WTRU).
[0380] The reported configuration may include a resource set intended for D2D discovery (e.g., frequency, bandwidth, subframe, PRB, time, etc.), a resource set intended for D2D communication (e.g., frequency, bandwidth, subframe, PRB, time, etc.), and / or the identity of the cooperating entity and / or the WTRU providing the configuration information (e.g., cluster head id, eNB id, and / or WTRU id, group id, Prose ID, etc.).
[0381] A WTRU-triggered report may, for example, include resources (e.g., a subset of resources) within a resource pool or resource pattern that the in-coverage WTRU requests from the eNB (e.g., or may use as previously received from the eNB and / or already configured within the WTRU) so that it may communicate with the out-of-coverage WTRU. For example, the report may include the proposed and / or used time pattern (e.g., cycle, duration, etc.), frequency, etc. The report may indicate a controlling entity that may take into account and / or provide to the reporting WTRU. The proposed time pattern may be determined (e.g., autonomously) by the in-coverage WTRU based on information received from and / or prepared by neighboring WTRUs. For example, the report may include one or more indices that describe resources (e.g., in time and / or frequency) within a resource pool that the out-of-coverage WTRU and the in-coverage WTRU have negotiated and / or pre-configured to use for the out-of-network link.
[0382] A report triggered by a WTRU may include location information. The location information may be associated with the reporting WTRU and / or associated with the report. A WTRU (e.g., transmitting and / or receiving) may determine its location based on, for example, a cell ID, GPS information, and / or other location information and append the location information to the report.
[0383] The WTRU-triggered report may include identity information. The identity information may include the identity of the detected out-of-coverage WTRU and / or the identity of the WTRU transmitting the message (e.g., on a synchronization channel). The identity may include a WTRU-specific ID, a ProSe ID, a ProSe group ID, a ProSe application ID, etc. The triggered report may include information related to one or more services (e.g., one or more service entities) for the detected out-of-coverage WTRU and / or for the WTRU transmitting the message. This information may be used, for example, to establish a relay service.
[0384] The report may include specific resources, subframes, and / or durations during which it may receive data and / or expect to receive data (e.g., as determined by a control message, a scheduling assignment, a broadcast message, etc.).
[0385] The report triggered by the WTRU may include information related to the presence and / or absence of out-of-coverage WTRUs. An indication may be included in the report when an in-coverage WTRU is detected on an out-of-coverage WTRU requesting and / or providing PS services, when an in-coverage WTRU stops detecting an out-of-coverage WTRU (e.g., using measurements), and / or when an out-of-coverage WTRU stops requesting relay services and / or when a WTRU detects D2DSS from a neighboring WTRU.
[0386] The WTRU may use a system frame number (SFN) and / or a timer reference.
[0387] A report triggered by a WTRU may include information related to the reason for triggering the transmission of a report, request, and / or transmit message (e.g., on a synchronization message). Reasons for triggering a report may include a request to initiate ProSe discovery and / or communication for a device that may be operating on another frequency, detection of a neighboring WTRU to initiate communication, a neighboring WTRU is no longer available, a new WTRU is detected, a change in pattern and / or configuration request, a request to stop the ProSe service, etc.
[0388] The WTRU may use triggers. The WTRU may trigger the transmission of reports, requests for patterns, and / or patterns based on configuration (e.g., on a sync message). The WTRU may begin transmission when it receives an L3 signal requesting the WTRU to begin reporting and / or message transmission and / or when the WTRU is configured for such reporting and another trigger begins the transmission of the report. The signals may be specific to D2D and / or prose services (e.g., communication and / or discovery) and / or WTRU specific (e.g., applicable to any identity).
[0389] The trigger for reporting may be event-based, for example, based on detection of a neighboring WTRU, a neighboring WTRU leaving, a request to start a ProSe service and / or to start discovery, a change in the pattern and / or resource allocation used by a neighboring WTRU, etc.
[0390] A report may be triggered when an in-coverage WTRU detects an out-of-coverage WTRU. The WTRU may detect neighboring WTRUs based on received D2DSS, synchronization messages, and / or data received from neighboring WTRUs requesting a connection (e.g., solicited and / or unsolicited modes) and / or WTRUs performing PS communication with which the in-coverage WTRU can communicate (e.g., WTRUs belonging to the same group and / or allowed to communicate via a ProSe configuration). A report may be triggered when an in-coverage WTRU detects that an out-of-coverage WTRU is no longer available and / or no longer requests service.
[0391] When an application request from a server to initiate a ProSe service is received, the WTRU may trigger a request and / or a report. A request and / or pattern request and / or report from an in-coverage WTRU may enable the WTRU to detect and / or discover an out-of-coverage WTRU. For example, when a neighboring WTRU reports a request for an opportunity to communicate with a detected and / or discovered WTRU to the network, the network may configure the WTRU for additional reporting. The WTRU may trigger a report when it determines that a neighboring WTRU has changed its pattern and / or resource allocation.
[0392] The trigger may be based on measurements and / or other detected WTRUs. A WTRU may trigger a report, a request for a pattern, and / or a transmission of a pattern (e.g., on a synchronization message) when it is connected to a higher priority synchronization source and / or when it detects that another WTRU is transmitting synchronization originating from a lower priority source synchronization (e.g., when a first WTRU is connected to an eNB and a second WTRU detects that it is sending a synchronization signal and is connected to another WTRU and / or another synchronization source). A trigger may be when a WTRU detects a second WTRU that is not connected to an eNB. A trigger may be when a WTRU detects a second WTRU operating on a frequency other than its frequency of operation. A trigger may be when a WTRU detects a second WTRU that belongs to the same group (e.g., the second WTRU is allowed to communicate with the first WTRU). The trigger may be when the WTRU receives data from a second WTRU and determines that the WTRU is not in coverage of the eNB (e.g., this may use an indication in the SA that the WTRU is not in coverage in the absence of D2DSS, SCI, SSS, other control signals and / or messages). The trigger may be when the WTRU detects different transmission patterns from different synchronization sources.
[0393] The trigger for reporting may be periodic. The WTRU may begin reporting periodically, for example, when there are one or more (e.g., a possibly configurable number) transmissions applicable for the reporting period. Reporting may be stopped when the WTRU detects that the out-of-coverage WTRU is no longer available (e.g., based on measurements) and / or that the out-of-coverage WTRU does not stop requesting service.
[0394] The trigger for reporting may be aperiodic. The WTRU may begin reporting from the receipt of a control signal requesting the WTRU to perform a report. The signaling may be received from a network node and / or may be dedicated signaling and / or signaling applicable to multiple WTRUs (e.g., received on a broadcast channel and / or a common control channel).
[0395] The WTRU may transmit the report using L2 (e.g., MAC) signaling (e.g., as a MAC control element), L3 (e.g., RRC) signaling (e.g., as an RRC PDU that is part of the reporting procedure), and / or higher layer signaling (e.g., such as NAS signaling and / or application signaling). For example, the WTRU may receive a control signal on the PDCCH (e.g., an aperiodic request) that may trigger such a report. The WTRU may assemble the report as a MAC control element and / or include it in an uplink transmission (e.g., its next uplink transmission). The eNB may be the end point of the reporting procedure.
[0396] The WTRU may receive a request on a signaling radio bearer (SRB) as an RRC PDU that triggers such a report. The WTRU may assemble the report as an RRC PDU and / or make it available for transmission on the associated SRB.
[0397] The WTRU may trigger the reporting at the application level. For example, the WTRU may assemble an application layer control packet and / or make it available for transmission, e.g., as an RRC PDU, for transmission on the related SRB (e.g., if NAS is used) and / or as user plane data, and may make it available for transmission for the corresponding DRB. The ProSe and / or application server may be the end point of the reporting procedure.
[0398] The WTRU may trigger the report. When the WTRU is in RRC IDLE mode, the WTRU may initiate a transition to CONNECTED mode and / or send the report via an applicable signaling method. The WTRU may still remain in IDLE mode and / or delay sending the report until it moves to CONNECTED mode, e.g., if RRC and / or higher layer protocols are used.
[0399] The WTRU may perform one or more of the following actions upon receipt of the report: The network and / or controlling node receiving the report may analyze the resource pool information, e.g., from reports received from multiple sources, and perform one or more of the following: The network and / or controlling node may determine which resources it may allow the in-coverage WTRU to communicate within the resource pool. The network and / or controlling node may initiate a procedure to reconfigure resources for one or more WTRUs. The network and / or controlling node may use this information to avoid scheduling the WTRU within a given resource and / or time period. For example, the eNB may determine a gap pattern for the in-coverage WTRU and configure the WTRU with the gap pattern.
[0400] Upon receiving the report, the eNB may determine, provide, and / or configure a gap and / or time pattern for the WTRU. The gap pattern may be a bit mask and may indicate the TTIs when the WTRU may not be scheduled for normal communication, and / or the pattern may correspond to a period, cycle, and / or duration within a period (e.g., each period) during which the WTRU may not be scheduled for communication with the eNB. Upon receiving the report, the eNB may analyze the requested gap pattern, and if it is not deemed efficient, the eNB may provide a new gap pattern to the WTRU.
[0401] The WTRU may use the gap pattern to switch to an out-of-coverage link with a neighboring WTRU. The WTRU may send the gap pattern to the out-of-coverage WTRU and / or a new gap pattern received from the eNB to the out-of-coverage WTRU.
[0402] For example, when the report includes an indication informing the eNB that the out-of-coverage WTRU is unavailable and / or no longer requires service, the eNB may remove the gap configuration.
[0403] Although the features and elements are described above in certain combinations, one skilled in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. Furthermore, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, 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 associated with software may be used to implement a radio frequency transceiver for use in a WTRU, a terminal, a base station, an RNC, or any host computer.
Claims
1. 1. A method implemented by a wireless transmit / receive unit (WTRU), comprising: receiving a system information block (SIB) from a network device; Based on at least the information included in the SIB and a determination that the WTRU has data to transmit to another WTRU, sending a connection establishment request to the network device; transmitting the data to the other WTRU for a time period after the connection establishment request is sent to the network device and before an indication regarding a resource rejection or resource allocation is received from the network device based on the connection establishment request, the data being transmitted using one or more resources autonomously selected by the WTRU from a resource pool; 23. A method comprising:
2. 10. The method of claim 1, wherein the data is further transmitted to the other WTRU based on a determination that the WTRU is in coverage of the network device.
3. 2. The method of claim 1, wherein the transmission of the data occurs while a radio resource control timer associated with the connection establishment request is running.
4. 2. The method of claim 1, further comprising: if the resource allocation is received from the network device, switching from using the resource pool for communications to using resources indicated by the resource allocation for communications.
5. 10. The method of claim 1, wherein the resource pool is configured to be used by the WTRU for communication during an exception scenario.
6. 2. The method of claim 1, wherein the SIB is received from the network device while the WTRU is in radio resource control (RRC) idle operation.
7. 2. The method of claim 1, wherein transmitting the data to the other WTRU comprises transmitting the data to the other WTRU based on a fixed power control.
8. The method of claim 1 , wherein the resource pool is indicated by the SIB.
9. 1. A wireless transmit / receive unit (WTRU), comprising: Receive a system information block (SIB) from a network device; Based on at least the information included in the SIB and a determination that the WTRU has data to transmit to another WTRU, Sending a connection establishment request to the network device; transmit the data to the other WTRU for a time period after the connection establishment request is sent to the network device before an indication regarding a resource rejection or resource allocation is received from the network device based on the connection establishment request, the data being transmitted using one or more resources autonomously selected by the WTRU from a resource pool. Processor configured to A WTRU comprising:
10. 10. The WTRU of claim 9, wherein the data is further transmitted to the other WTRU based on a determination that the WTRU is in coverage of the network device.
11. 10. The WTRU of claim 9, wherein the transmission of the data occurs while a radio resource control timer associated with the connection establishment request is running.
12. 10. The WTRU of claim 9, wherein the processor is further configured to switch from using the resource pool for communication to using resources indicated by the resource allocation for communication when the resource allocation is received from the network device.
13. 10. The WTRU of claim 9, wherein the resource pool is configured to be used by the WTRU for communications during an exception scenario.
14. 10. The WTRU of claim 9, wherein the processor is configured to receive the SIB from the network device while the WTRU is in a radio resource control (RRC) idle operation.
15. The WTRU of claim 9 , wherein the resource pool is indicated by the SIB.
