WO2018062850A1 - Procédé et dispositif de transmission et de réception de signal de synchronisation d'un terminal de communication dispositif à dispositif dans un système de communication sans fil - Google Patents

Procédé et dispositif de transmission et de réception de signal de synchronisation d'un terminal de communication dispositif à dispositif dans un système de communication sans fil Download PDF

Info

Publication number
WO2018062850A1
WO2018062850A1 PCT/KR2017/010726 KR2017010726W WO2018062850A1 WO 2018062850 A1 WO2018062850 A1 WO 2018062850A1 KR 2017010726 W KR2017010726 W KR 2017010726W WO 2018062850 A1 WO2018062850 A1 WO 2018062850A1
Authority
WO
WIPO (PCT)
Prior art keywords
gnss
slss
enb
synchronization
terminal
Prior art date
Application number
PCT/KR2017/010726
Other languages
English (en)
Korean (ko)
Inventor
채혁진
서한별
이승민
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to KR1020187021051A priority Critical patent/KR102063084B1/ko
Priority to EP17856736.8A priority patent/EP3522620A4/fr
Priority to US16/064,730 priority patent/US10575269B2/en
Priority to CN201780059636.5A priority patent/CN109804678B/zh
Publication of WO2018062850A1 publication Critical patent/WO2018062850A1/fr
Priority to US16/799,058 priority patent/US11388687B2/en
Priority to US17/861,965 priority patent/US11889442B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/18523—Satellite systems for providing broadcast service to terrestrial stations, i.e. broadcast satellite service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/18578—Satellite systems for providing broadband data service to individual earth stations
    • H04B7/18582—Arrangements for data linking, i.e. for data framing, for error recovery, for multiple access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/002—Mutual synchronization
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties

Definitions

  • the following description relates to a wireless communication system, and more particularly, to a method and apparatus for synchronizing signal transmission and reception when a satellite signal can be used for synchronization.
  • Wireless communication systems are widely deployed to provide various kinds of communication services such as voice and data.
  • a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.).
  • multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency (SC-FDMA).
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • MCD division multiple access
  • MCDMA multi-carrier frequency division multiple access
  • MC-FDMA multi-carrier frequency division multiple access
  • D2D communication establishes a direct link between user equipments (UEs), and directly communicates voice and data between terminals without passing through an evolved NodeB (eNB).
  • UEs user equipments
  • eNB evolved NodeB
  • the D2D communication may include a scheme such as UE-to-UE communication, Peer-to-Peer communication, and the like.
  • the D2D communication scheme may be applied to machine-to-machine (M2M) communication, machine type communication (MTC), and the like.
  • M2M machine-to-machine
  • MTC machine type communication
  • D2D communication has been considered as a way to solve the burden on the base station due to the rapidly increasing data traffic.
  • the D2D communication unlike the conventional wireless communication system, since the data is exchanged between devices without passing through a base station, the network can be overloaded.
  • the D2D communication it is possible to expect the effect of reducing the procedure of the base station, the power consumption of the devices participating in the D2D, increase the data transmission speed, increase the capacity of the network, load balancing, cell coverage expansion.
  • V2X is a concept including V2V between vehicle terminals, V2P between a vehicle and other types of terminals, and V2I communication between a vehicle and a roadside unit (RSU).
  • RSU roadside unit
  • the present invention provides a method of applying a priority in relation to a PLMN, selecting a synchronization source and receiving a synchronization signal when a satellite signal can be used for synchronization.
  • a method for receiving a sidelink synchronization signal (SLSS) in a wireless communication system comprising: receiving a physical sidelink broadcast channel (PSBCH); Determining which of the Global Navigation Satellite Systems (GNSS) or the eNB is the synchronization source according to the priority information included in the PSBCH; And receiving a SLSS related to the determined synchronization source, wherein the terminal is valid only when the Public Land Mobile Network (PLMN) related to the priority information matches the PLMN to which the terminal belongs.
  • PLMN Public Land Mobile Network
  • An embodiment of the present invention provides a terminal device for receiving a sidelink synchronization signal (SLSS) in a wireless communication system, comprising: a transmitting device and a receiving device; And a processor, wherein the processor receives a physical sidelink broadcast channel (PSBCH) through the receiving device, and synchronizes either Global Navigation Satellite Systems (GNSS) or eNB according to priority information included in the PSBCH.
  • PSBCH physical sidelink broadcast channel
  • GNSS Global Navigation Satellite Systems
  • eNB Global Navigation Satellite Systems
  • PLMN Public Land Mobile Network
  • the terminal may always select the SLSS ID in the range of 170 to 335 regardless of the number of synchronization resources set by the network or preset.
  • the PSBCH may include a PLMN ID.
  • the terminal When the terminal receives the SLSS having the GNSS as a synchronization source, the terminal may always transmit the SLSS.
  • the terminal may transmit the SLSS for a preset time even if the terminal loses the GNSS reception.
  • the synchronization source may be set for each resource pool.
  • the bitmap of the resource pool related to GNSS may be based on DFN (D2D Frame Number) 0.
  • the present invention it is possible to prevent the timing difference that may occur when the priority of the synchronization source is different according to the PLMN.
  • 1 is a diagram illustrating a structure of a radio frame.
  • FIG. 2 is a diagram illustrating a resource grid in a downlink slot.
  • 3 is a diagram illustrating a structure of a downlink subframe.
  • FIG. 4 is a diagram illustrating a structure of an uplink subframe.
  • FIG. 5 is a configuration diagram of a wireless communication system having multiple antennas.
  • FIG. 6 shows a subframe in which the D2D synchronization signal is transmitted.
  • FIG. 7 is a diagram for explaining a relay of a D2D signal.
  • FIG. 8 shows an example of a D2D resource pool for D2D communication.
  • FIG. 10 is an illustration of a situation in which GNSS may be used as a synchronization source.
  • FIG. 11 is a diagram illustrating an example of PLMN and synchronization source selection.
  • FIG. 12 is a diagram illustrating a configuration of a transmitting and receiving device.
  • each component or feature may be considered to be optional unless otherwise stated.
  • Each component or feature may be embodied in a form that is not combined with other components or features.
  • some components and / or features may be combined to form an embodiment of the present invention.
  • the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
  • the base station has a meaning as a terminal node of the network that directly communicates with the terminal.
  • the specific operation described as performed by the base station in this document may be performed by an upper node of the base station in some cases.
  • a 'base station (BS)' may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), an access point (AP), and the like.
  • the repeater may be replaced by terms such as relay node (RN) and relay station (RS).
  • the term “terminal” may be replaced with terms such as a user equipment (UE), a mobile station (MS), a mobile subscriber station (MSS), a subscriber station (SS), and the like.
  • a base station may also be used as a meaning of a scheduling node or a cluster header. If the base station or the relay also transmits a signal transmitted by the terminal, it can be regarded as a kind of terminal.
  • the cell names described below are applied to transmission and reception points such as a base station (eNB), a sector, a remote radio head (RRH), a relay, and the like. It may be used as a generic term for identifying a component carrier.
  • eNB base station
  • RRH remote radio head
  • Embodiments of the present invention may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802 system, 3GPP system, 3GPP LTE and LTE-Advanced (LTE-A) system and 3GPP2 system. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA may be implemented with a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA may be implemented with wireless technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE).
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA).
  • UTRA is part of the Universal Mobile Telecommunications System (UMTS).
  • 3rd Generation Partnership Project (3GPP) long term evolution (LTE) is part of an Evolved UMTS (E-UMTS) using E-UTRA, and employs OFDMA in downlink and SC-FDMA in uplink.
  • LTE-A Advanced
  • WiMAX can be described by the IEEE 802.16e standard (WirelessMAN-OFDMA Reference System) and the advanced IEEE 802.16m standard (WirelessMAN-OFDMA Advanced system). For clarity, the following description focuses on 3GPP LTE and 3GPP LTE-A systems, but the technical spirit of the present invention is not limited thereto.
  • a structure of a radio frame will be described with reference to FIG. 1.
  • uplink / downlink data packet transmission is performed in units of subframes, and one subframe is defined as a predetermined time interval including a plurality of OFDM symbols.
  • the 3GPP LTE standard supports a type 1 radio frame structure applicable to frequency division duplex (FDD) and a type 2 radio frame structure applicable to time division duplex (TDD).
  • the downlink radio frame consists of 10 subframes, and one subframe consists of two slots in the time domain.
  • the time it takes for one subframe to be transmitted is called a transmission time interval (TTI).
  • TTI transmission time interval
  • one subframe may have a length of 1 ms and one slot may have a length of 0.5 ms.
  • One slot includes a plurality of OFDM symbols in the time domain and a plurality of resource blocks (RBs) in the frequency domain.
  • RBs resource blocks
  • a resource block (RB) is a resource allocation unit and may include a plurality of consecutive subcarriers in one block.
  • the number of OFDM symbols included in one slot may vary depending on the configuration of a cyclic prefix (CP).
  • CP has an extended CP (normal CP) and a normal CP (normal CP).
  • normal CP normal CP
  • the number of OFDM symbols included in one slot may be seven.
  • the OFDM symbol is configured by an extended CP, since the length of one OFDM symbol is increased, the number of OFDM symbols included in one slot is smaller than that of the normal CP.
  • the number of OFDM symbols included in one slot may be six. If the channel state is unstable, such as when the terminal moves at a high speed, an extended CP may be used to further reduce intersymbol interference.
  • one subframe includes 14 OFDM symbols.
  • the first two or three OFDM symbols of each subframe may be allocated to a physical downlink control channel (PDCCH), and the remaining OFDM symbols may be allocated to a physical downlink shared channel (PDSCH).
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • Type 2 radio frames consist of two half frames, each of which has five subframes, a downlink pilot time slot (DwPTS), a guard period (GP), and an uplink pilot time slot (UpPTS).
  • DwPTS downlink pilot time slot
  • GP guard period
  • UpPTS uplink pilot time slot
  • One subframe consists of two slots.
  • DwPTS is used for initial cell search, synchronization or channel estimation at the terminal.
  • UpPTS is used for channel estimation at the base station and synchronization of uplink transmission of the terminal.
  • the guard period is a period for removing interference generated in the uplink due to the multipath delay of the downlink signal between the uplink and the downlink.
  • one subframe consists of two slots regardless of the radio frame type.
  • the structure of the radio frame is only an example, and the number of subframes included in the radio frame or the number of slots included in the subframe and the number of symbols included in the slot may be variously changed.
  • FIG. 2 is a diagram illustrating a resource grid in a downlink slot.
  • One downlink slot includes seven OFDM symbols in the time domain and one resource block (RB) is shown to include 12 subcarriers in the frequency domain, but the present invention is not limited thereto.
  • one slot includes 7 OFDM symbols in the case of a general cyclic prefix (CP), but one slot may include 6 OFDM symbols in the case of an extended-CP (CP).
  • Each element on the resource grid is called a resource element.
  • One resource block includes 12 ⁇ 7 resource elements.
  • the number N DL of resource blocks included in the downlink slot depends on the downlink transmission bandwidth.
  • the structure of the uplink slot may be the same as the structure of the downlink slot.
  • FIG. 3 is a diagram illustrating a structure of a downlink subframe.
  • Up to three OFDM symbols at the front of the first slot in one subframe correspond to a control region to which a control channel is allocated.
  • the remaining OFDM symbols correspond to data regions to which a Physical Downlink Shared Channel (PDSCH) is allocated.
  • Downlink control channels used in the 3GPP LTE / LTE-A system include, for example, a Physical Control Format Indicator Channel (PCFICH), a Physical Downlink Control Channel (PDCCH), Physical Hybrid Automatic Repeat Request Indicator Channel (PHICH).
  • PCFICH Physical Control Format Indicator Channel
  • PDCH Physical Downlink Control Channel
  • PHICH Physical Hybrid Automatic Repeat Request Indicator Channel
  • the PHICH includes a HARQ ACK / NACK signal as a response of uplink transmission.
  • Control information transmitted through the PDCCH is referred to as downlink control information (DCI).
  • the DCI includes uplink or downlink scheduling information or an uplink transmit power control command for a certain terminal group.
  • the PDCCH is a resource allocation and transmission format of the downlink shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information of the paging channel (PCH), system information on the DL-SCH, on the PDSCH Resource allocation of upper layer control messages such as random access responses transmitted to the network, a set of transmit power control commands for individual terminals in an arbitrary terminal group, transmission power control information, and activation of voice over IP (VoIP) And the like.
  • a plurality of PDCCHs may be transmitted in the control region.
  • the terminal may monitor the plurality of PDCCHs.
  • the PDCCH is transmitted in an aggregation of one or more consecutive Control Channel Elements (CCEs).
  • CCEs Control Channel Elements
  • CCE is a logical allocation unit used to provide a PDCCH at a coding rate based on the state of a radio channel.
  • the CCE corresponds to a plurality of resource element groups.
  • the number of CCEs required for the PDCCH may vary depending on the size and coding rate of the DCI. For example, any one of 1, 2, 4, and 8 CCEs (corresponding to PDCCH formats 0, 1, 2, and 3, respectively) may be used for PDCCH transmission, and when the size of DCI is large and / or channel state If a low coding rate is required due to poor quality, a relatively large number of CCEs may be used for one PDCCH transmission.
  • the base station determines the PDCCH format in consideration of the size of the DCI transmitted to the terminal, the cell bandwidth, the number of downlink antenna ports, the PHICH resource amount, and adds a cyclic redundancy check (CRC) to the control information.
  • the CRC is masked with an identifier called a Radio Network Temporary Identifier (RNTI) according to the owner or purpose of the PDCCH.
  • RNTI Radio Network Temporary Identifier
  • the PDCCH is for a specific terminal, the cell-RNTI (C-RNTI) identifier of the terminal may be masked to the CRC.
  • a paging indicator identifier P-RNTI
  • SI-RNTI system information identifier and system information RNTI
  • RA-RNTI Random Access-RNTI
  • the uplink subframe may be divided into a control region and a data region in the frequency domain.
  • a physical uplink control channel (PUCCH) including uplink control information is allocated to the control region.
  • a physical uplink shared channel (PUSCH) including user data is allocated.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • one UE does not simultaneously transmit a PUCCH and a PUSCH.
  • PUCCH for one UE is allocated to an RB pair in a subframe. Resource blocks belonging to a resource block pair occupy different subcarriers for two slots. This is called a resource block pair allocated to the PUCCH is frequency-hopped at the slot boundary.
  • the transmitted packet is transmitted through a wireless channel
  • signal distortion may occur during the transmission process.
  • the distortion In order to correctly receive the distorted signal at the receiving end, the distortion must be corrected in the received signal using the channel information.
  • a method of transmitting the signal known to both the transmitting side and the receiving side and finding the channel information with the distortion degree when the signal is received through the channel is mainly used.
  • the signal is called a pilot signal or a reference signal.
  • the reference signal may be divided into an uplink reference signal and a downlink reference signal.
  • an uplink reference signal as an uplink reference signal,
  • DM-RS Demodulation-Reference Signal
  • SRS sounding reference signal
  • DM-RS Demodulation-Reference Signal
  • CSI-RS Channel State Information Reference Signal
  • MBSFN Multimedia Broadcast Single Frequency Network
  • Reference signals can be classified into two types according to their purpose. There is a reference signal for obtaining channel information and a reference signal used for data demodulation. Since the former has a purpose for the UE to acquire channel information on the downlink, the UE should be transmitted over a wide band, and the UE should receive the reference signal even if the UE does not receive the downlink data in a specific subframe. It is also used in situations such as handover.
  • the latter is a reference signal transmitted together with a corresponding resource when the base station transmits a downlink, and the terminal can demodulate data by performing channel measurement by receiving the reference signal. This reference signal should be transmitted in the area where data is transmitted.
  • FIG. 5 is a configuration diagram of a wireless communication system having multiple antennas.
  • the transmission rate can be improved and the frequency efficiency can be significantly improved.
  • the transmission rate may theoretically increase as the rate of increase rate Ri multiplied by the maximum transmission rate Ro when using a single antenna.
  • a transmission rate four times higher than a single antenna system may be theoretically obtained. Since the theoretical capacity increase of multi-antenna systems was proved in the mid 90's, various techniques to actively lead to the actual data rate improvement have been actively studied. In addition, some technologies are already being reflected in various wireless communication standards such as 3G mobile communication and next generation WLAN.
  • the research trends related to multi-antennas to date include the study of information theory aspects related to the calculation of multi-antenna communication capacity in various channel environments and multi-access environments, the study of wireless channel measurement and model derivation of multi-antenna systems, improvement of transmission reliability, and improvement of transmission rate. Research is being actively conducted from various viewpoints, such as research on space-time signal processing technology.
  • the communication method in a multi-antenna system will be described in more detail using mathematical modeling. It is assumed that there are Nt transmit antennas and Nt receive antennas in the system.
  • the transmission signal when there are Nt transmit antennas, the maximum information that can be transmitted is NT.
  • the transmission information may be expressed as follows.
  • Each transmission information The transmit power may be different.
  • Each transmit power In this case, the transmission information whose transmission power is adjusted may be expressed as follows.
  • Weighting matrix Nt transmitted signals actually applied by applying Consider the case where is configured.
  • Weighting matrix Plays a role in properly distributing transmission information to each antenna according to a transmission channel situation.
  • Vector It can be expressed as follows.
  • Received signal is received signal of each antenna when there are Nr receiving antennas Can be expressed as a vector as
  • channels may be divided according to transmit / receive antenna indexes. From the transmit antenna j to the channel through the receive antenna i It is indicated by. Note that in the order of the index, the receiving antenna index is first, and the index of the transmitting antenna is later.
  • FIG. 5 (b) shows a channel from NR transmit antennas to receive antenna i .
  • the channels may be bundled and displayed in vector and matrix form.
  • a channel arriving from a total of NT transmit antennas to a receive antenna i may be represented as follows.
  • AWGN Additive White Gaussian Noise
  • the received signal may be expressed as follows through the above-described mathematical modeling.
  • the channel matrix indicating the channel state The number of rows and columns of is determined by the number of transmit and receive antennas.
  • Channel matrix The number of rows is equal to the number of receiving antennas NR, and the number of columns is equal to the number of transmitting antennas Nt. That is, the channel matrix The matrix is NR ⁇ Nt.
  • the rank of a matrix is defined as the minimum number of rows or columns that are independent of each other. Thus, the rank of the matrix cannot be greater than the number of rows or columns.
  • Channel matrix Rank of ( ) Is limited to
  • rank may be defined as the number of nonzero eigenvalues when the matrix is eigenvalue decomposition.
  • another definition of rank may be defined as the number of nonzero singular values when singular value decomposition is performed.
  • rank in the channel matrix The physical meaning of is the maximum number of different information that can be sent on a given channel.
  • 'rank' for MIMO transmission refers to the number of paths that can independently transmit signals at specific time points and specific frequency resources, and 'number of layers' denotes each path. It indicates the number of signal streams transmitted through the system. In general, since the transmitting end transmits the number of layers corresponding to the number of ranks used for signal transmission, unless otherwise specified, the rank has the same meaning as the number of layers.
  • some nodes may transmit a D2D signal (where the node may be referred to as an eNB, a UE, a synchronization reference node or a synchronization source), and transmit a D2D synchronization signal (D2DSS, D2D Synchronization Signal).
  • a method of transmitting and receiving signals in synchronization with the remaining terminals may be used.
  • the D2D synchronization signal may include a primary synchronization signal (Primary D2DSS or Primary Sidelink synchronization signal (PDSSDS)) and a secondary synchronization signal (Secondary D2DSS or Secondary Sidelink synchronization signal (SSSS)). It may be a Zadoff-chu sequence or a similar / modified / repeated structure to the PSS, etc. It is also possible to use other Zadoff Chu root indices (eg, 26, 37) unlike the DL PSS. May be a similar / modified / repeated structure to M-sequence or SSS, etc.
  • PDSSDS Primary Sidelink synchronization signal
  • SSSS Secondary Sidelink synchronization signal
  • PD2DSS Physical D2D synchronization channel
  • SRN becomes eNB
  • D2DSS becomes PSS / SSS
  • PD2DSS The / SD2DSS follows the UL subcarrier mapping scheme, and the subframe through which the D2D synchronization signal is transmitted is shown in Fig. 6.
  • the PD2DSCH Physical D2D synchronization channel
  • the PD2DSCH may be transmitted on the same subframe as the D2DSS or on a subsequent subframe DMRS may be used for demodulation of the PD2DSCH.
  • the SRN may be a node transmitting a D2DSS and a Physical D2D Synchronization Channel (PD2DSCH).
  • the D2DSS may be in the form of a specific sequence
  • the PD2DSCH may be in the form of a sequence representing specific information or a code word after a predetermined channel coding.
  • the SRN may be an eNB or a specific D2D terminal.
  • the UE may be an SRN.
  • the D2DSS may be relayed for D2D communication with an out of coverage terminal.
  • the D2DSS can be relayed over multiple hops.
  • relaying a synchronization signal is a concept including not only directly relaying a synchronization signal of a base station, but also transmitting a D2D synchronization signal of a separate format in accordance with the timing of receiving the synchronization signal. As such, since the D2D synchronization signal is relayed, the in-coverage terminal and the out-of-coverage terminal can directly perform communication.
  • a UE refers to a network equipment such as a base station that transmits and receives a signal according to a terminal or a D2D communication scheme.
  • the terminal may select a resource unit corresponding to a specific resource in a resource pool representing a set of resources and transmit a D2D signal using the corresponding resource unit.
  • the receiving terminal UE2 may be configured with a resource pool in which UE1 can transmit a signal, and detect a signal of UE1 in the corresponding pool.
  • the resource pool may be notified by the base station when UE1 is in the connection range of the base station.
  • a resource pool is composed of a plurality of resource units, each terminal may select one or a plurality of resource units and use them for transmitting their D2D signals.
  • the resource unit may be as illustrated in FIG. 8 (b). Referring to FIG. 8 (b), it can be seen that total frequency resources are divided into NFs and total time resources are divided into NTs so that a total of NF * NT resource units are defined.
  • the resource pool may be repeated every NT subframe. In particular, one resource unit may appear periodically and repeatedly as shown.
  • a resource pool may mean a set of resource units that can be used for transmission by a terminal that wants to transmit a D2D signal.
  • Resource pools can be divided into several types. First, they may be classified according to contents of D2D signals transmitted from each resource pool. For example, the contents of the D2D signal may be divided, and a separate resource pool may be configured for each.
  • As the content of the D2D signal there may be a scheduling assignment (SA), a D2D data channel, and a discovery channel (SA), where the location of a resource used for transmission of a subsequent D2D data channel by a transmitting terminal and others It may be a signal including information such as a modulation and coding scheme (MCS), a MIMO transmission scheme, a timing advance (TA), etc. required for demodulation of a data channel, which may be multiplexed and transmitted together with D2D data on the same resource unit.
  • MCS modulation and coding scheme
  • TA timing advance
  • the SA resource pool may mean a pool of resources in which the SA is multiplexed with the D2D data and transmitted, or may be referred to as a D2D control channel or a physical sidelink control channel (PSCCH).
  • the D2D data channel (or physical sidelink shared channel (PSSCH)) may be a pool of resources used by a transmitting terminal to transmit user data. If the SA is multiplexed and transmitted together with the D2D data on the same resource unit, only the D2D data channel except for the SA information may be transmitted in the resource pool for the D2D data channel, that is, individual resource units in the SA resource pool.
  • the REs used to transmit SA information on the D2D data channel resource pool can still be used to transmit D2D data in the discovery channel, where a transmitting terminal transmits information such as its own ID and the like so that a neighboring terminal can discover itself. It can be a resource pool for messages to be made.
  • the transmission timing determination method of the D2D signal for example, is it transmitted at the time of reception of a synchronization reference signal or is transmitted by applying a constant TA there
  • a resource allocation method for example, For example, whether an eNB assigns transmission resources of an individual signal to an individual transmitting UE or whether an individual transmitting UE selects an individual signaling resource on its own in a pool, and a signal format (for example, each D2D signal occupies one subframe).
  • the number of symbols, the number of subframes used for transmission of one D2D signal), the signal strength from the eNB, and the transmission power strength of the D2D UE may be further divided into different resource pools.
  • Mode 1 a transmission resource region is set in advance, or the eNB designates a transmission resource region, and the UE directly selects a transmission resource in a method of directly instructing the eNB to transmit resources of the D2D transmitting UE in D2D communication.
  • Mode 2 In the case of D2D discovery, when the eNB directly indicates a resource, a type 2 when a UE directly selects a transmission resource in a preset resource region or a resource region indicated by the eNB is called Type 1.
  • the mode 1 terminal may transmit an SA (or a D2D control signal, Sidelink Control Information (SCI)) through a resource configured from the base station.
  • SA or a D2D control signal, Sidelink Control Information (SCI)
  • SCI Sidelink Control Information
  • the mode 2 terminal is configured with a resource to be used for D2D transmission from the base station.
  • the SA may be transmitted by selecting a time frequency resource from the configured resource.
  • the first SA period may be started in a subframe away from a specific system frame by a predetermined offset SAOffsetIndicator indicated by higher layer signaling.
  • Each SA period may include a SA resource pool and a subframe pool for D2D data transmission.
  • the SA resource pool may include the last subframe of the subframes indicated by which the SA is transmitted in the subframe bitmap (saSubframeBitmap) from the first subframe of the SA period.
  • a subframe used for actual data transmission may be determined by applying a time-resource pattern for transmission or a time-resource pattern (TRP).
  • the T-RPT may be repeatedly applied, and the last applied T-RPT is the number of remaining subframes. As long as it is truncated, it can be applied.
  • the schemes related to the D2D synchronization signal described above are characterized by giving priority to the synchronization provided by the network. More specifically, the UE first selects the synchronization signal directly transmitted by the eNB in determining its transmission synchronization, and preferentially synchronizes with the D2DSS transmitted by the UE inside the eNB coverage if located outside the eNB coverage. That's right.
  • a wireless terminal installed in a vehicle or a terminal mounted in a vehicle has a relatively low battery consumption problem, and can use satellite signals such as GPS for navigation purposes so that the satellite signals can be set for time or frequency synchronization between terminals. Can be used.
  • the satellite signal may correspond to satellite signals such as Global Navigation Satellite Systems (GNSS), Global Navigation Satellite System (GLONAS), GALILEO, BEIDOU, etc.
  • V (vehicle) -UE may be a vehicle
  • P (pedestrian) -UE may be a terminal moving on foot or a terminal moving in a cycle.
  • GPS timing is set to a frame / subframe boundary based on an absolute time referred to as a time (eg, UTC: Coordinated Universal Time or GPS time) acquired when GPS is received, and some or all subframes of the D2D signal are selected. It may mean that it is set to a subframe for transmission.
  • UTC Coordinated Universal Time or GPS time
  • Cellular timing refers to a predetermined offset (e.g., at the point in time of receipt of a PSS / SSS or SLSS transmitted by a nearby eNB (e.g., where RSRP is received the largest) or at the point of reception of a PSS / SSS transmitted by an eNB.
  • a predetermined offset may be applied based on a PSS / SSS reception time point (in some cases, an offset value may be 0) to configure a radio frame / subframe boundary, and some subframes may be configured as D2D subframes.
  • SLSS id_net is a set of SLSS IDs used by terminals selected as a synchronization reference of a synchronization signal of a base station among physical layer SLSS IDs ⁇ 0, 1, ..., 335 ⁇ . , 167 ⁇ .
  • the SLSS id_oon is a set of SLSS IDs used when the base stations / out-of-coverage terminals transmit their own synchronization signals, and may be ⁇ 168, 169, ..., 335 ⁇ .
  • GNSS GNSS based UE
  • UE N-1 eNB based UE
  • UE G-2 two hop GNSS based UE
  • UE N-2 two hop eNB
  • GNSS based UE eNB based UE
  • the eNB based UE and the GNSS based UE may have the same priority.
  • an in-coverage terminal may select a SLSS ID and transmit a SLSS generated based on the selected SLSS ID.
  • the selected SLSS ID is the same as the terminal (ie, eNB based UE) used when transmitting the SLSS by receiving the synchronization signal (PSS / SSS) directly from the base station and selecting the synchronization as the timing and / or frequency reference of the eNB. It may be one selected from a SLSS ID set (eg, SLSS id_net).
  • one SLSS ID may be selected within a SLSSid_net (set of SLSS IDs selected by eNB based UEs) for the GNSS terminal, and this ID may be predetermined or signaled by a network.
  • a UE that receives a signal directly from the GNSS to acquire synchronization and selects a GNSS as a timing and / or frequency reference (that is, a GNSS based UE) is used when a UE that receives a PSS / SSS directly from a base station transmits an SLSS.
  • the same resource or a resource configured for a separate GNSS based UE may be transmitted, and the terminal may use the same PSBCH field as the predetermined PSBCH field used by the terminal that receives the PSS / SSS directly from the base station to transmit the SLSS.
  • the predetermined PSBCH field may be a coverage indicator field, and a value of the coverage indicator field may be set to 1.
  • the eNB based UE and the GNSS based UE thus use the SSID (and / or the same resource, the same coverage indicator) selected from the set of SLSS IDs used by the UEs of the priorities.
  • the SLSS transmitted by each of the GNSS based UEs may be seen as an equivalent signal (ie, a signal having the same priority) to the receiving terminals.
  • the receiving terminal may select a SLSS having a large RSRP / S-RSRP as a synchronization source. (The terminal transmitting the SLSS having the large S-RSRP is selected as the synchronization source among the terminals that receive the SLSS directly from the terminal and the base station.)
  • setting the eNB based UE and the GNSS based UE at the same priority may prevent the UE from selecting a UE having a bad synchronization signal as a synchronization source.
  • the eNB based UE has a higher priority than the GNSS based UE.
  • UE X receives a synchronization signal from UE G-1 (GNSS based UE) and UE N-1 (eNB based UE), respectively.
  • the SLSS transmitted by the UE G-1 near the distance will have a much larger S-RSRP than the signal transmitted by the UE N-1.
  • UE X should select UE N-1 having a low S-RSRP but high priority as a synchronization source according to the priority, in which case it will be difficult to obtain accurate synchronization. Furthermore, if UE X which obtained an incorrect synchronization transmits the SLSS based on the incorrect synchronization, this will cause a great interference to other UEs receiving synchronization from the GNSS. Therefore, this problem can be solved by placing the eNB based UE and the GNSS based UE at the same priority as in the above embodiment.
  • the eNB may be able to receive / use GNSS.
  • the UE detects the eNB, it may signal whether the eNB prioritizes GNSS or eNB. It is preferable that GNSS takes precedence for the purpose of reducing the frequency offset, but the eNB may take precedence according to signaling.
  • the two hop GNSS UE may use the SLSS id of the corresponding UE when the ID set in advance among the SLSS id_net, the ID signaled by the network, or the GNSS based UE selected by the user as the synchronization reference.
  • the SLSS resource used by the two hop GNSS UEs may be indicated by the (one hop or direct) GNSS based UE through the PSBCH, or may be determined in advance.
  • GNSS may have the highest priority.
  • the priority may be determined in consideration of whether GNSS reception is possible, a frequency offset request value when receiving GNSS, and the number of hops.
  • GNSS is not detected (tunnel, under an overpass)
  • GNSS (direct) GNSS based UE > eNB based UE > two hop GNSS based UE > two hop eNB based UE
  • This priority may be for the case where the eNB is capable of receiving GNSS. This takes into account whether the eNB is capable of receiving GNSS, how strict the frequency offset requirement is, and the like. Specifically, when the eNB can receive the GNSS and the eNB receives the GNSS, the frequency offset is 0.1 ppm, and when the UE also receives the GNSS directly, the frequency offset is equal to 0.1 ppm, two hop GNSS based UE and eNB based The UE has the same number of hops from GNSS to two hops, and the expected frequency offset requirement is the same.
  • the eNB based UE is configured to have a higher priority than the two hop GNSS based UEs.
  • GNSS (direct) GNSS based UE > eNB based UE > two hop GNSS based UE > two hop eNB based UE> three hop GNSS based UE> OON UE
  • the priority may be defined as above.
  • GNSS > (direct) GNSS based UE > eNB based UE two hop GNSS based UE > two hop eNB based UE> OON UE
  • This priority allows eNB-based UEs and two hop GNSS-based UEs to have the same priority.
  • the eNB based UE and the two hop GNSS based UE are considered to be the same hop based on the same GNSS, and that the timing difference is not so great. That is, by making the same priority, using the same resource / SLSS ID / PSBCH, other UEs transmit the same signal on the same resource by transmitting a signal such as a single frequency network (SFN), so that the signal is stable (high reception power) on the corresponding resource. This is because it is possible to obtain an effect and then set the priority without distinguishing the priority.
  • SFN single frequency network
  • the GNSS based UE and the two hop GNSS based UE may not be distinguished.
  • one hop / two hop GNSS based UEs can be distinguished through the SLSS ID.
  • the eNB related priority is preferably lower than the GNSS in that it maintains continuity in V2V operation.
  • the priority is i) GNSS> (direct) GNSS based UE, ii) GNSS> (direct) GNSS based UE> two hop GNSS based UE> eNB based UE> two hop eNB based UE> OON UE, iii) eNB> GNSS> (direct) GNSS based UE> two hop GNSS based UE> eNB based UE> two hop eNB based UE> OON UE, iv) eNB based UE> two hop eNB based UE> GNSS> GNSS based UE> two hop GNSS based UE> indirect (more than one hop) GNSS based UE> OON UE, v) GNSS> (direct) GNSS based based UE,
  • an eNB-based synchronization source (eNB, one hop eNB base UE, two hop eNB based UE) may not be used at the priority. .
  • This can eliminate timing discontinuity between different series of synchronization sources while using only GNSS-based synchronization sources.
  • not using the priority may mean that the corresponding synchronization signal is ignored even if visible, or may be instructed by the eNB not to transmit the D2D synchronization signal to the eNB based UE or the two hop eNB based UE.
  • id_net eg. 0 or 167.
  • Table 1 illustrates the priority, PSBCH, and SLSS Id settings in relation to the reception of the GNSS.
  • SLSS ID includes id_net, new indicator using reserved bit of new PSBCH to indicate GNSS direct.
  • Case 4 Priority GNSS> GNSS based UE> two hop
  • a higher priority rule can be determined: Among the SLSS IDs (used by GNSS), the coverage indicator is 1 (direct GNSS (GNSS based)). Since it is a UE, it has a higher priority.)
  • Case 5 Priority GNSS> eNB based UE> two hop eNB based UE> GNSS based UE> two hop GNSS based UE> OON UE (assuming there is an eNB nearby, but in this case GNSS is the highest priority, which is the coverage Other than to violate 3GPP RAN1 82bis agreement that GNSS is the highest priority.)
  • Case 6 Priority eNB based UE> two hop eNB based UE> GNSS> GNSS based UE> two hop GNSS based UE> OON UE (To do this, it is necessary to signal which type of synchronization is superior to the out-of-coverage UE by utilizing the PSBCH
  • GNSS type (GNSS, GNSS based UE, two hop GNSS based UE) is superior or eNB type is superior (eNB, eNB based, two hop eNB based), and this indication bit can be preconfigured to specific state.
  • eNB eNB based, two hop eNB based
  • This indication bit can be preconfigured to specific state.
  • Case 7 Priority The superiority over GNSS based and eNB based is determined using the S-RSRP of the received signal (in this case, it is regarded as equal priority for all SLSS IDs, without setting a separate priority, and using S-RSRP, Determine whether GNSS based is the superior or eNB based is the superior)
  • the PSBCH and SLSS Id settings may be similar to Case 3.
  • the Case 1 to Case 3 may correspond to the case where the eNB can receive the GNSS
  • the Case 4 to Case 7 correspond to the case where the eNB cannot receive the GNSS. That is, the priority may be divided according to whether the eNB receives the GNSS. Outside coverage, GNSS> GNSS based UE would be desirable.
  • Table 2 shows an example of a relationship between PSBCH (coverage indicator configuration) and SLSS ID configuration.
  • Case 3 Set SLSS ID GNSS based UE, two hop GNSS based UE: use the one reserved in advance for GNSS among id_net coverage indicator settings GNSS
  • the eNB based UE sets the PSBCH bit to be the same as the GNSS based UE, the eNB based UE and the GNSS based UE have the same priority. hop GNSS based UEs have the same priority. As such, the eNB may set the SLSS ID, coverage indicator, and PSBCH reserved bit as appropriate, and designate a priority relationship with the SLSS based on GNSS timing.
  • Table 3 below is an example of priorities in terms of prioritization.
  • a specific sync source may be excluded from the priority level.
  • RSRP to S-RSRP from an eNB or RSRP to GNSS signal reception quality from an eNB or a value obtained by applying a specific offset to each measurement metric, where an offset applied to each metric is determined in advance or physical layer by the network Or may be signaled to the UE through a higher layer signal) to determine the priority between the eNB and the GNSS based UE or the eNB and the GNSS.
  • the eNB signal follows the eNB timing within the strong coverage, the intercell GNSS to follow the synchronization problem in the asynchronous network with the help of GNSS, there is an advantage that no separate priority signaling is required.
  • the eNB may be indicated to have a higher priority than GNSS. If the GNSS based UE has a high priority, too often a synchronous reference change may occur. Thus, eNB may be higher priority than GNSS based UE. In this case, the network may indicate the priority of the eNB. At this time, if the UEs out of coverage use GNSS as the highest priority, the cell edge cellular terminals may be interfered with due to the D2D operation out of coverage. Therefore, in this case, as in case 8, the eNB based UE may have a higher priority than GNSS.
  • the SLSS id may be set differently between the UE that receives the GNSS in the out coverage and the UE that receives the GNSS in the in coverage.
  • the terminal receiving the GNSS in the coverage uses the ID set in advance in the SLSS id_net, and the terminal receiving the GNSS outside the coverage uses the ID set in the SLSS id_oon.
  • the eNB may be detected on a carrier in which V2V operation occurs, or may be detected on another carrier (eg, an existing LTE carrier).
  • the priority between the GNSS and the base station may be determined / set for each carrier. If the priorities are not set for each carrier in this manner, the carrier having no base station must follow priority priority setting operation (ie, setting the highest priority to GNSS) in out coverage. In this case, since the base station timing is used in the carrier in which the base station is installed (in the carrier aggregation situation) and the GNSS timing is used in the carrier in which the base station is not installed, a timing difference may occur between the two carriers.
  • the priority determined for each carrier may be signaled by the base station.
  • the eNB-based synchronization priority may be lower than the GNSS-based.
  • the priorities described above may be modified such that the eNB base is high priority. If the eNB is deployed in both the carrier and the LTE carrier V2V operation occurs, the eNB of the carrier V2V operation may have a higher synchronization priority than the LTE carrier.
  • the LTE carrier may be given a higher priority than the V2V carrier, which is to protect the operation of the existing LTE carrier.
  • the aforementioned priorities can be determined by the carriers in the order of X> Y> Z ... in carrier A and in the order of Z> Y> X in carrier B (where X, Y, Z means each synchronization source in the above-mentioned synchronization priority), and the network may signal the carrier-specific synchronization priority to the UE as a physical layer or a higher layer signal to the UE to determine this.
  • the UE when the UE does not receive such signaling, it may follow the priority order in out coverage, which may be predetermined.
  • the operator is different (different operator behavior)
  • the timing information of the GNSS can be transferred to another operator through signaling between the networks between the two operators, or the UE returns the fact that the GNSS-based SLSS is detected to the operator, and does not have the GNSS.
  • the eNB may reconfigure the subframe boundary to reduce the effects of V2V operation.
  • the timing of the eNB may not use the D2D subframe due to the GNSS due to the eNB of the other specific carrier does not receive the GNSS.
  • the offset value between the timing used by the eNB and the UTC timing may be signaled to the UE as a physical layer or a higher layer signal.
  • the proposed schemes implicitly signal that the eNB uses GNSS, which may be explicitly signaled to the terminal as a physical layer or a higher layer signal.
  • GNSS may be explicitly signaled to the terminal as a physical layer or a higher layer signal.
  • the synchronization priority may be determined in consideration of the following.
  • GNSS small hop counter has high priority, and maximum hop count is limited as in LTE release 12
  • Frequency offset frequency offset is related to hop count from eNB and UE and GNSS
  • Priority indication from the eNB the network may explicitly or implicitly indicate which timing has priority, eNB based timing or GNSS based timing
  • GNSS reception capability of the eNB if GNSS reception) Without capability, for better V2V operation, GNSS based timing may have higher priority than eNB based timing
  • Affects Uu (related to eNB's GNSS reception capability. Cell edge UE performance and Uu operation are considered) Should be)
  • GNSS has the highest priority. Then, in case of coverage, it is necessary to determine the priority of the GNSS based UE (UE G-1) and the eNB based UE (UE N-1).
  • UE G-1 When the eNB has GNSS reception capability, UE G-1 is one hop from GNSS and UE N-1 is two-hop from GNSS. Thus, UE G-1 may have a higher priority than UE N-1. However, when the eNB has GNSS reception capability, the frequency offset requirement of the eNB is very small, and UE G-1 may have the same priority as UE N-1. The same priority means that when multiple synchronization sources are seen at the same priority, the synchronization source is selected based on the S-RSRP measurement.
  • Another issue is determining whether the priority between UE G-1 and UE N-1 interferes with Uu. If UE G-1 has a higher priority than UE N-1, the cell edge performance in the TDD cell will be greatly reduced, and the V2V operation in FDD will not be well TDM. This issue is also related to the priority between GNSS and UE N-1. However, out of coverage, GNSS has the highest priority. In order for UE-N1 to have a higher priority than GNSS, a change of negotiation is required.
  • GNSS> UE G-1 UE N-1 or UE N-1> GNSS> UE G-1 (if the agreement can be eNBit prioritize synch source originated from Priorities may be considered, such as when the eNB is changed to (and preconfigured) that the network-based sink reference has a higher priority than the GNSS.
  • the priority between the two-hop GNSS based UE (UE G-2) and the eNB based UE (UE N-1) needs to be determined.
  • UE G-2 When the eNB is capable of receiving GNSS, UE G-2 is two-hop from GNSS, which is the same hop from GNSS to UE N-1. This means that UE G-2 and UE N-1 have the same priority. On the other hand, eNB is always a fixed position, UE G-1 can move. Therefore, since the total frequency offset of UE N-1 is smaller than UE-G2, UE-N1 has a higher priority than UE-G2.
  • the UE can detect the signal of the eNB.
  • the network may configure a priority between synchronization based on eNB and synchronization based on GNSS. Even if the network configures that the eNB has a higher priority than the synchronization based on GNSS, the prioritization of the eNB may be broken because of the existing negotiation (RAN1 # 82bis) if the UE is out of coverage. Thus, synchronization priority based on eNB may be difficult to fully implement unless the negotiation is modified. Moreover, if the eNB can properly set the SLSS ID and PSBCH content, explicit signaling for synchronization priority based on GNSS may not be needed. This will be described later.
  • one of various priorities may be used for out of coverage UEs.
  • option 5 GNSS> UE G-1> UE G-2> UE N-1> UE N-2> OON UENote: GNSS synchronization prioritization is preconfigured or signaled via PSBCH.
  • the eNB does not prevent the in-coverage UE from transmitting the GNSS based SLSS ID. For example, if the eNB can receive the GNSS, for in-coverage UE, it can instruct to use the GNSS based SLSS ID.
  • the PSBCH field may be set differently according to the priority option.
  • UE G-1 and N-1 have the same priority.
  • coverage indicator 1 is set for UE G-1
  • UE N-1 and UE G-1 can be SFNed (SFNed).
  • SFNed SFNed
  • Table 5 below shows the SLSS ID and PSBCH configuration for each option of Table 4.
  • Option 1 and option 2 do not require the use of reserved bits in the PSBCH.
  • the difference between Option 1 and Option 2 is whether or not prioritization of GNSS is performed on the same hop.
  • the UE determines a synchronization source based on the S-RSRP measurement.
  • the GNSS is prioritized at the same hop count.
  • the receiving UE prioritizes UE N-1. No option should be able to handle multiple timing issues when the eNB cannot receive GNSS.
  • Option SLSS ID and PSBCH setting for UE G-1 and UE G-2 option 1 Priority: GNSS> UE G-1> UE N-1> UE G-2> UE N-2> OON UESLSS ID for UE G-1: An ID in in_net is reserved for GNSS based synchronizationCoverage indicator for UE G-1: 1SLSS ID for UE G-2: An ID in in_net is reserved for GNSS based synchronizationCoverage indicator for UE G-2: 0Note: The ID reserved for GNSS based synchronization has higher priority than other IDs in id_net.
  • Option 1 or 2 does not require a new PSBCH field and can minimize the impact on the existing synchronization procedure. Therefore, Option 1 or 2 may be supported for V2V based on PC5.
  • high density DMRS and Comb type RS can be considered. Similar approach should be applied to PSBCH for V2V based PC5.
  • the PSBCH DMRS may be located in SC-FDMA symbol 5 of the first slot and SC-FDMA symbol 1 of the second slot.
  • the new PSBCH format can be used for high frequency carriers and the network can indicate which PSBCH format is used. That is, the PSBCH DMRS type, number, and position may be modified for V2V operation based on PC5.
  • the existing rel In order to maintain 12/13 operation, even if the UE receives the GNSS, the coverage indicator and / or the SLSS ID may be differently set according to the coverage state.
  • the eNB may indicate a specific ID among the SLSS IDs used by the UE that directly receives the GNSS.
  • the GNSS can be received while the uncovered UE is naturally GNSS capable and has a higher priority than the out of coverage UE.
  • the GNSS-based terminal naturally has a higher priority than the OON UE.
  • the eNB may perform signaling for configuring (in advance) one of the SLSS IDs among the SLSS id nets for the UE receiving the GNSS within the coverage, and the SLSS ID instructed by the eNB of the UE receiving the GNSS. Can be used to transmit.
  • the SLSS ID used for GNSS may be different from the configuration. If the UE outside the coverage receives the GNSS, the coverage indicator may be set to 0 or a predetermined one among the SLSS ID_oon may be used. Through this, the SLSS transmission operation of the UE receiving the GNSS in and out of the coverage may be different, and the UEs receiving the GNSS in the coverage may have higher priority.
  • This method reflects that the above-described priorities of the GNSS-based SLSS and the uncovered UE have the same priority, and in this case, even if the GNSS-based (direct receiving) terminal is out of coverage, It has a lower priority than a GNSS-based terminal in coverage, and has a higher priority than an OON.
  • the UE that receives the GNSS directly sets the incoverage indicator to 1, and the UE that does not receive the GNSS directly sets the incoverage indicator to 0, so that the SLSS does not transmit a reserved PSSS for the GNSS of the SLSS id_net
  • a root index eg, 38
  • priority with an existing SLSS may be predetermined or determined by signaling of an eNB.
  • this priority may be signaled through the PSBCH to be propagated to the UE outside the network coverage.
  • Methods 1 to 3 relate to the case where the P-UE is not turning on the GPS application.
  • the P-UE does not have a GPS-based application turned on, it can determine at what timing the P-UE will transmit the D2D signal based on the time the most recent application was turned on. For example, a terminal that successfully performs a GPS signal reception operation by turning on a recent GPS application may receive a D2D signal based on the timing of the GPS signal according to how far the point of view is from the current point of view, or how far the GPS timing is from the cellular timing. Or transmit a D2D signal based on cellular timing.
  • the D2D signal When the GPS signal is successfully received, the D2D signal is transmitted based on cellular timing when the difference from the current time point is greater than or equal to a certain threshold. When the GPS signal is within a certain threshold, the D2D signal is transmitted based on the GPS timing.
  • the threshold value used in this operation may be signaled from the network or a predetermined value.
  • the timing at which the P-UE attempts to transmit the D2D signal is greater than or equal to a predetermined threshold, the timing of the GPS signal may be determined to be inaccurate, and the SLSS and D2D signals based on cellular timing may be transmitted.
  • the P-UE When the P-UE receives a GPS signal, the P-UE can calculate how far this timing differs from cellular timing. If the calculation result is larger than a predetermined threshold, the P-UE may transmit the SLSS at a predetermined period in a predefined SLSS resource.
  • the threshold used for this operation may be signaled from the network or a predetermined value.
  • a P-UE that does not run a GPS-based application within a certain time or has no GPS reception capability can always transmit a cellular timing-based SLSS, assuming that it has not received a GPS signal.
  • the P-UE may be predetermined to always transmit the SLSS based on cellular timing. If the P-UE is in V (vehicle) mode, for example, when the P-UE is connected to a vehicle with a terminal, the P-UE may follow the SLSS transmission rule of the V-UE described below.
  • the SLSS resource and the SLSS ID may be predetermined or configured by the network.
  • the transmission of the SLSS by the P-UE may be indicated by the eNB or the RSU as a physical layer or a higher layer signal, or may selectively transmit only terminals whose RSRP from the eNB or the RSU is below a certain threshold (less than).
  • the purpose of transmitting the SLSS of the P-UE is for the neighboring V-UE to recognize the presence of the P-UE, and in this case, the SLSS may be transmitted at regular intervals even if the P-UE does not transmit data.
  • the GPS circuit can be turned on to receive GPS signals at predetermined intervals for tracking the timing of the GPS. Can be.
  • the P-UE basically performs GPS timing based D2D signal and SLSS signal transmission. To this end, the P-UE wakes up at a predetermined or configured time period by the network and performs an operation of receiving a GPS signal. In this case, it is not necessary to search all the GPS signals because it is to simply acquire the timing of GPS, rather than the purpose of position estimation when receiving GPS signals. Even if only one GPS signal is received, it is included in the navigation message of the GPS signal. GPS timing can be estimated by acquiring GPS time information.
  • GPS timing validity time can be defined for estimating GPS timing, which can be defined as the time since the last GPS-based application was turned on or the last time timing information was received from the GPS. If this valid time exceeds a certain threshold, the P-UE communicates to the upper layer that it needs to receive a GPS signal, or intermittently receives a GPS signal before the valid time exceeds a certain threshold, thereby timing the GPS. Can be estimated accurately. This method allows the P-UE and V-UE to align timing by intermittently estimating GPS timing directly.
  • the P-UE can transmit and receive GPS timing based SLSS and D2D signals.
  • the P-UE may transmit the SLSS in the same manner as the SLSS transmission rule transmitted by the V-UE.
  • the P-UE When the P-UE receives the SLSS of the V-UE, the SLSS resource and the SLSS ID transmitted by the V-UE may be signaled to the P-UE as a physical layer or higher layer signal.
  • the P-UE may perform an operation of searching for the SLSS in the corresponding resource.
  • the V-UE can transmit the SLSS at a predetermined resource location based on the GPS timing, and within +/- w based on the SLSS transmission offset to reduce the complexity of the P-UE searching for the SLSS transmitted by the V-UE.
  • the network may signal a window value indicating that the SLSS is transmitted.
  • the serving eNB or the camping eNB may signal the transmission period and offset of the SLSS transmitted by the V-UE based on SFN 0 of the serving cell or the camping cell of the P-UE as a physical layer or a higher layer signal. If the eNB or RSU can also receive a GPS signal, it can signal a small value of w to reduce the complexity required for the P-UE to discover the SLSS of the V-UE, and the eNB or RSU can receive the GPS signal. If it can not, it will be able to signal a large w value because only the approximate timing information is known.
  • the V-UE When the V-UE transmits the SLSS, not all UEs transmit but may be limited to the V-UE in which the measurement quality of the GPS is above a certain threshold. This is to increase the accuracy of timing by allowing only the terminal with high reliability to transmit the SLSS.
  • the threshold value may be predetermined or may be configured by a network.
  • all V-UEs transmitting data may transmit SLSS. This is to allow a more accurate synchronization estimation by receiving the SLSS even when the P-UE wakes up.
  • the network or the RSU may instruct the V-UE to transmit the SLSS transmission as a physical layer or a higher layer signal.
  • This method has an advantage of preventing the V-UE from transmitting the SLSS unnecessarily in an environment where there is no P-UE nearby.
  • V-UE measures GPS timing and cellular timing and the difference occurs more than a certain threshold
  • cellular timing-based SLSS transmission may be performed.
  • V-UE measures cellular timing and transmits cellular timing based D2D signal / SLSS for P-UE if the GPS timing is over a certain threshold.
  • the advantage of this approach is that the P-UE does not increase the additional complexity of receiving GPS signals.
  • the SLSS resource and the D2D resource pool transmitted by the V-UE may be signaled to the P-UE in advance.
  • the period and offset of the SLSS resource may be signaled based on SFN 0 of the serving cell, and in order to reduce the discovery complexity of the P-UE, the network may indicate that the SLSS is transmitted within +/ ⁇ w based on the SLSS transmission offset.
  • the value (w) may be signaled to the P-UE as a physical layer or higher layer signal.
  • the V-UE When the V-UE transmits an SLSS, not all UEs transmit but may be limited to a V-UE whose RSRP from the eNB or from the RSU is above a certain threshold. This is to prevent the UE at the boundary of the network to transmit the SLSS to prevent unnecessary P-UEs camping on the same eNB to receive the SLSS.
  • the threshold value may be predetermined or may be configured by a network.
  • all V-UEs transmitting data may transmit SLSS. This is to allow a more accurate synchronization estimation by receiving the SLSS even when the P-UE wakes up.
  • the network or the RSU may instruct the V-UE to transmit the SLSS transmission as a physical layer or a higher layer signal.
  • This method has an advantage of preventing the V-UE from transmitting the SLSS unnecessarily in an environment where there is no P-UE nearby.
  • This method can only be applied to certain information, such as alarm messages that the V-UE sends for the P-UE.
  • certain information such as alarm messages that the V-UE sends for the P-UE.
  • the P-UE In general V-UE communication, when the V-UE transmits for the P-UE using GPS timing, the P-UE easily detects / decodes the signal of the V-UE by using the timing for the P-UE. Do it.
  • the V-UE may transmit only SLSS at cellular timing, and then D2D data may be transmitted based on GPS timing.
  • the V-UE informs the receiving UE of the GPS timing by using the physical layer or the offset value between the GPS timing and the cellular timing, or the difference between the starting point of the SFN0 set based on the GPS timing and the starting point of the SFN0 set based on the cellular timing.
  • Signal to the P-UE as a higher layer signal. For example, an offset value between V-UE and GPS timing may be signaled using a reserved bit of PSBCH.
  • a separate channel for example, a new PSCCH format
  • the V-UE to transmit some kind of control information or some data information to the P-UE to signal an offset value between cellular timing and GPS timing in the channel.
  • This method sends a SLSS to the P-UE based on cellular timing, indicating the presence of the V-UE, signaling a timing offset value transmitted by the V-UE later on the PSBCH or other sidelink channel, so that the P-UE is then V The UE knows where the transmitted packet is sent.
  • This method has the advantage of receiving the signal of the V-UE without increasing the complexity of the P-UE.
  • the V-UE transmits a separate physical channel (eg, PSCCH) from the SLSS in cellular timing, and uses GPS timing values (eg, SFN0 as UTC time) in the physical channel transmitted at the same timing as the SLSS.
  • PSCCH physical channel
  • GPS timing values eg, SFN0 as UTC time
  • V-UEs that do not receive GPS signals also receive SLSS based on cellular timing and transmit GPS timing information at the same timing as the corresponding SLSS. (Or timing offset information) can be received and later used to receive packets.
  • a resource for transmitting a SLSS by the V-UE may coincide with a period of a resource for receiving an alarm message by the P-UE. This is to allow the P-UE to efficiently receive the synchronization signal by transmitting the synchronization signal to the position where the P-UE always wakes up and receives the signal.
  • the alarm message reception period means a resource area configured to receive specific data transmitted by the V-UE or RSU or another P-UE by always waking up the P-UE.
  • P-UE Since the operation of TX to V-UE or RX to V-UE message occurs intermittently in the form of an event trigger from a P-UE perspective, it may be inefficient that the P-UE is always searching for a synchronization signal of the V-UE. Therefore, P-UE is a method of maintaining synchronization only to enable immediate TX / RX by waking up from a predetermined resource and searching for SLSS of V-UE, or intermittently waking up to receive GPS signals. Through this, the P-UE may reduce battery consumption of the terminal.
  • the P-UE may transmit and receive a D2D signal based on GPS timing in a resource pool signaled by a serving cell or a camping cell. In this case, since the P-UE knows the GPS timing correctly, it can operate at the same timing as the V-UE.
  • Method 5. 6 is specifically for out of coverage cases.
  • the P-UE should basically search for SLSS on all resources. In this case, since the nearby V-UE will also be out of coverage, if the V-UE is out of coverage, the V-UE randomly selects one of the SLSS IDs or uses a predetermined SLSS ID to predetermine the SLSS resource based on GPS timing. You can send the SLSS at the location.
  • the SLSS resource location, period, and SLSS ID transmitted by the V-UE may be previously set in common by the V-UE. All V-UEs may transmit SLSS, and only some UEs of V-UEs may perform SLSS transmission. For example, only the V-UE transmitting data can transmit the SLSS.
  • the V-UE transmitting the SLSS may be limited to a V-UE in which the GNSS is turned on or updated within a predefined threshold time, or a V-UE having a predetermined GNSS measurement quality. Alternatively, only the V-UE that detects the SLSS transmitted by the P-UE may transmit the SLSS. For this operation, the V-UE must normally search for the SLSS of the P-UE.
  • Method 6- P-UE transmits SLSS for V-UE
  • the P-UE will perform a regular cycle of the predefined SLSS resource (the SLSS ID or dictionary selected by the UE). It is possible to transmit the SLSS (of the SLSS ID determined in the following). If the P-UE selects the SLSS ID, the V-UE has no way of knowing it, so it will have to search for all SLSS IDs. If the SLSS ID transmitted by the P-UE is determined in advance, the V-UE You only need to search for the corresponding SLSS ID. This method is to inform the SLSS that there is a P-UE around to prevent the V-UE from transmitting the SLSS unnecessarily.
  • a D2D terminal transmitting a signal based on cellular timing and a D2D terminal transmitting a signal based on GPS timing may coexist.
  • the SLSS transmitted by two different terminals needs to be distinguished in the physical layer.
  • the SLSS sequence used by the V-UE may be distinguished from the sequence used by the P-UE.
  • the V-UE may transmit the SLSS using a PSSS root sequence ID not used by the P-UE.
  • the root sequence ID used by the P-UE may be used in D2D of the existing LTE release 12/13, or a new root sequence ID may be determined while not being used in the existing D2D for the P-UE.
  • the UE may be set to be different from this P-UE and the root sequence ID used in the existing D2D.
  • the existing downlink PSS uses a ZC sequence having a root index of 25, 29, and 34
  • the PSSS of a sidelink uses a ZC sequence having a root index of 26, 37.
  • the D2D UE transmitting a signal based on GPS timing proposes to use a ZC sequence of 38 root indices. This has the advantage of recycling the existing downlink ZC sequence receiver in the complex conjugate relationship with the PSS 25 root index ZC sequence used in the existing downlink.
  • the terminal transmitting the SLSS and the legacy D2D terminal coexist with the GPS timing, coexistence is possible because the legacy terminal does not detect the GPS-based synchronization signal.
  • Some unused bits of the PSBCH may be used to indicate at what timing the corresponding SLSS is transmitted or which UE is transmitted. For example, coverage indicators may be set differently between a terminal transmitting at cellular timing and a terminal transmitting at GPS timing. Alternatively, the reserved bits of the PSBCH may be set differently to indicate that timing for transmitting the SLSS is different.
  • a D2D terminal using GPS as a timing reference may set a transmission period longer than the existing 40 ms.
  • the SLSS transmission period can be set differently according to a specific event or regional characteristics. For example, if an accident occurs between vehicles, the SLSS transmission period can be increased. Alternatively, if there are underground parking lots or tunnels in the surrounding area, the transmission period may be increased. Alternatively, some of the 40 ms SLSS resources may be divided into resources transmitted by a terminal using cellular timing.
  • the classification method may be set differently when the SLSS transmission timing (cellular timing or GPS timing) is different, but may be set differently depending on who is transmitting the SLSS.
  • the SLSS transmitted by the P-UE and the V-UE may be previously set differently in whole or in part from a sequence / PSBCH reserved bit / SLSS resource period / SLSS transmission resource location.
  • some of the methods may be used as a method of distinguishing between SLSS transmitted by the RSU and SLSS transmitted by another UE.
  • time synchronization is set based on GPS timing, it may be preferable to use SLSS or D2D RS transmitted between two terminals for frequency synchronization.
  • the frequency synchronization for the first D2D signal reception is most preferably adjusted using PSS / SSS / CRS / CSI-RS / DMRS of the cellular network in In-coverage. This is because, for the first time, if the frequency synchronization is not correct when receiving the D2D signal, the D2D signal reception performance is very poor. Therefore, it is preferable that the UE preliminarily adjusts frequency synchronization by using a reference signal transmitted by a fixed node such as an eNB or an RSU (also having a relatively small frequency offset). For example, the P-UE is set based on the SLSS transmitted by the V-UE or GPS timing, but the frequency synchronization of the initial state can be matched to the cellular network.
  • a method of using frequency synchronization of a GPS signal may be considered.
  • the GPS receiver tracks frequency synchronization by comparing the received PRN code with the PRN code generated by the receiver. Using this frequency synchronization value, the oscillator of the band where D2D communication occurs can be corrected.
  • This method may be used only if the band in which D2D communication occurs is within a certain frequency interval with the band of the GPS (eg, 1.575 GHz or 1.227 GHz). Even if the GPS frequency synchronization is accurately tracked, the accuracy of the carrier may be degraded if the carrier moves largely, and thus a band capable of using the GPS frequency synchronization may be determined in advance.
  • a P-UE transmitting and receiving a V-UE and / or V2X message may be determined to always transmit a message based on the frequency synchronization of the GPS.
  • This method is based on the frequency synchronization of the GPS regardless of the coverage situation, regardless of the type of message transmitted by the UE, and even by using the frequency synchronization of the GPS to the carrier transmitting the celluar signal.
  • the terminal since the terminal is generally equipped with one oscillator, if the V2X message is transmitted or the cellular message (Uu) is different in frequency synchronization, the method may be changed. Since the implementation burden will be greatly increased, always use the frequency synchronization of GPS.
  • the UE may signal a signal indicating whether the frequency synchronization is used by the eNB as a physical layer or a higher layer signal. For example, when the GPS is set as the frequency reference, the V-UE may use a reserved bit of the PSBCH or transmit an existing field by differently setting it to the eNB.
  • the UE transmitting the signal based on the frequency synchronization of the GPS in the method 9b does not receive the GPS signal, it can fall back to use the frequency synchronization of the eNB, and if the frequency synchronization of the eNB also does not receive GPS
  • the terminal may receive frequency synchronization with a D2D signal transmitted by the terminal. If the frequency synchronization transmitted by the terminal receiving the GPS is not transmitted, it may use its own local oscillator. In this case, the UE sets different sequence IDs of the SLSS, sets the SLSS resources differently, sets the D2D signal transmission resource region differently, or sets some fields of the PSBCH in order to indicate to the other UE which frequency synchronization the UE has matched. Can be set differently. Alternatively, combinations of the described methods may be included in the scope of the present invention.
  • UEs out of network coverage may not receive GPS signals in the vicinity and may not be able to achieve accurate frequency synchronization because there are no devices continuously transmitting signals such as eNBs, in which case they may be tighter than other UEs.
  • a frequency offset request value is set so that the frequency may not be set beyond a certain threshold in the initial transmission.
  • V-UE it is more likely that a transceiver is more expensive than P-UE, so it can be designed to set a stricter requirement and at least reduce the frequency offset generated in V-UE.
  • the RSU is a UE type (when the RSU is an eNB type, it will follow the frequency offset requirement of the eNB.)
  • a tighter requirement than that of other UEs is set, which may help frequency synchronization of the UE.
  • a UE having a strict frequency offset oscillator compared to another UE uses a separate SLSS resource / SLSS ID / sequence to inform the receiving UEs of the UE, or uses a separate physical channel (for example, a PSBCH or another separate Channel), a method of signaling information for notifying the type of UE, frequency requirement, frequency synchronization priority, and the like is proposed.
  • the receiving terminal adjusts frequency synchronization to the D2D signals of the terminal whose information has a higher priority.
  • the mobility is large, and thus it may be inappropriate to use frequency synchronization as a reference. Therefore, only a terminal that is a fixed node such as an RSU, a moving speed is below a certain speed in the V-UE, or a relative speed with a receiving terminal is below a certain speed (less than), or a terminal tighter than another UE having a frequency offset request selectively or Rules may be determined to set the frequency synchronization reference first.
  • the SLSS transmitted by the UE corresponding to the above-described condition has a different ID, a separate transmission resource is set, uses a different root sequence of PSSS / or SSSS, or sets a reserved bit of PSBCH differently.
  • an indicator may be transmitted in a separate physical channel. For example, a V-UE having a speed less than or equal to a certain speed may be transmitted including a transmission speed in a PSBCH or a separate physical channel, or may use a different SLSS ID according to a moving speed.
  • Priority may be given to the frequency synchronization setting.
  • Priority of frequency synchronization is predetermined in order, so that the UE may decide to hold frequency synchronization according to a predetermined priority even if several signals are visible.
  • Some of the above-described embodiments of the frequency synchronization priority may be excluded or the order may be changed.
  • the priority is not limited to the frequency but may be applied to the priority of time synchronization, and the priority of time and frequency synchronization may be the same, but may be different.
  • a signal transmitted by a terminal whose mobility is within a certain threshold among the UE or eNB with reference to GPS> GPS and a UE or UE type RSU with reference to GPS is not synchronized with GPS.
  • the UEs within the coverage of the eNB> GPS / eNB / eNB which are not synchronized to the eNB> GPS may be determined in the order of the UEs which have not received all the signals. This order of priority of time and / or frequency synchronization may have been previously signaled by the network as a physical layer or higher layer signal.
  • the synchronization is prioritized to the GPS because it is lower than the frequency offset request value of 0.1 ppm of the terminal to synchronize with the eNB.
  • the GPS has the highest priority, and then the signal transmitted by the terminal synchronized with the GPS may have the priority.
  • transmitting a SLSS by a terminal having poor GPS signal reception capability may cause interference to another terminal that receives the SLSS or a terminal that properly receives a GPS signal.
  • Method 12 can be used.
  • the SLSS is transmitted at high power, and the terminal has a low transmission power for a terminal having a poor GPS measurement quality.
  • the GPS measurement quality is below a certain threshold, the SLSS transmission may not be performed.
  • P_SLSS min (P_SLSS_max, P0 + alpha * (GPS measurement quality))
  • P_SLSS P_SLSSTxpw * delta (GPS measurement quality> threshold)
  • P_SLSS transmit power is multiple steps.
  • the SLSS transmission power may be determined by a method such as setting a step and determining a step according to measurement quality.
  • the measurement quality may be GPS measurement quality
  • P0 and alpha may be constants predetermined or signaled by the network.
  • the proposed method intends to reflect the measurement quality in the SLSS transmission power setting, which may be implemented in the form of adjusting the SLSS transmission power according to a synchronization error. For example, a terminal that is expected to have a large or large synchronization error transmits the SLSS at low power, and a terminal that has a small or low synchronization error transmits the SLSS at high power.
  • a terminal that directly receives a GPS signal is expected to have a small synchronization error, and transmits a SLSS at a high power
  • a terminal that does not directly receive a GPS or a terminal that synchronizes with a synchronization signal of an eNB may be used.
  • the SLSS transmission power may be determined in the same manner as Min (P0, Pmax-alpha * (measurement error)).
  • all or part of the P0, Pmax, and alpha values may be predetermined or may be signaled as a physical layer or higher layer signal by the network.
  • the SLSS transmission power may be determined in the following manner.
  • parameters such as N, an, and Pn may be predetermined or signaled by a network as a physical layer or a higher layer signal.
  • the following proposes a specific method for measuring the GPS measurement quality / error.
  • the reception power of the preamble / known sequence among the GPS signals can be considered as a factor of measurement quality.
  • the hop count for GPS synchronization can be considered as an element of GPS measurement. For example, a terminal that receives a GPS signal directly has a hop count of 0, and a terminal that synchronizes with a SLSS received by the eNB or an RSU in synchronization with the GPS signal is a hop count of 1 and a SLSS transmitted by a terminal synchronized with the SLSS. The terminal which resynchronizes with is considered as hop count 2. The larger the hop count, the more the measurement error can be assumed by giving a certain bias to the measured value.
  • Time missed GPS synchronization can be reflected in measurement quality.
  • the time may be increased, or the offset may be applied because of poor measurement quality or large measurement error.
  • the size of the offset may be determined in proportion to time, or may be determined as a constant function determined according to the size of the time interval missed by the GPS.
  • All or part of the above methods may be combined to measure GPS measurement quality or measurement error, and the SLSS transmission power may be determined by this value.
  • the SLSS transmission power determination method described above may also be used as a method of determining transmission power of a message transmitted by the V-UE. For example, if it is determined that the synchronization quality is low or the error is large, the message transmission power is reduced to reduce the interference to other terminals. Or when it is determined that the synchronization measurement quality is low or the measurement error is large (or when it is determined that the predetermined threshold is exceeded), the rule sets the UE to transmit the SLSS and / or the message in a separate resource / resource area. Can be done. This is because the V-UEs are not synchronized with other V-UEs, so that they can be transmitted in separate resource regions to reduce interference to or from other V-UEs.
  • the frequency synchronization setting method may be extended to a synchronization signal selection method.
  • the proposed method is applied to not only frequency but also timing.
  • the frequency synchronization setting method may be used in conjunction with one of the time synchronization setting methods.
  • FIG. 11 illustrates an example for explaining priority application in relation to PLMN in V2V.
  • UE A and UE B performing V2V communication are located in a common area of PLMN A and PLMN B.
  • PLMN A it is assumed that GNSS has higher priority than eNB
  • PLMN B eNB has higher priority than GNSS.
  • a problem may occur if UE A and UE B apply priority to synchronization source selection regardless of the PLMN.
  • UE A and UE B both belong to PLMN A.
  • UE A receives PSBCH related to PLMN A and selects GNSS having a high synchronization source priority as a synchronization source
  • UE B receives PSBCH related to PLMN B.
  • UE A and UE B belong to the same PLMN but apply different priorities and select different synchronization sources.
  • UE A and UE B which have synchronized with GNSS and eNB, respectively, have synchronization differences as much as timing differences between GNSS and eNB. If two UEs performing V2V communication have a synchronization difference with each other, it may cause a safety problem.
  • the terminal receives a PSBCH (Physical Sidelink Broadcast Channel), and according to the priority information included in the PSBCH, GNSS (Global Navigation Satellite Systems) or eNB After deciding which one to use as a synchronization source, the terminal may receive a SLSS related to the determined synchronization source, wherein the terminal may only receive a Public Land Mobile Network (PLMN) related to the priority information that matches the PLMN to which the terminal belongs. It may be determined that the priority information is valid.
  • the PSBCH may include a PLMN ID.
  • the SLSS related to the synchronization source may be directly received from the synchronization source or transmitted by another terminal receiving the SLSS from the synchronization source.
  • UE A and UE B of FIG. 11 may receive PSBCHs related to different PLMNs, thereby applying different priorities and selecting different synchronization sources (GNSS and eNB). Since the UE B has received the PSBCH related to the PLMN B, it will determine that the priority included therein is invalid and will not apply the priority to the synchronization source selection. Then, by receiving a PSBCH related to the PLMN A to which another UE transmits and applying a priority to the synchronization source selection, the UE can have the same synchronization source as the UE A.
  • PSBCHs related to different PLMNs thereby applying different priorities and selecting different synchronization sources (GNSS and eNB). Since the UE B has received the PSBCH related to the PLMN B, it will determine that the priority included therein is invalid and will not apply the priority to the synchronization source selection. Then, by receiving a PSBCH related to the PLMN A to which another UE transmits and applying a priority to the synchronization
  • Terminal GNSS Method of transmitting a synchronization signal of a terminal when selecting as synchronization
  • the terminal selects GNSS as the synchronization source, the transmission of the synchronization signal of the terminal that receives the SLSS will be described.
  • the GNSS is selected as the synchronization source but may be selected by applying the priority according to the PLMN matching described above, but is not necessarily limited thereto. That is, in addition to the priority application described above, the GNSS may be applied even when the synchronization source is selected.
  • the terminal When the terminal receives the SLSS having the GNSS as a synchronization source, the terminal may always transmit the SLSS. If UEs select an eNB as a synchronization source, they may follow the existing LTE release 12/13 synchronization signal transmission condition. As the GNSS is introduced as a new synchronization source, terminals synchronized with the GNSS may transmit a synchronization signal to transmit timing information to other terminals. In this case, terminals which have a predefined, sufficiently satisfactory level of sink reception capability may set the GNSS as a synchronization reference, and these terminals may always transmit the SLSS on a predetermined resource or a resource indicated by the network. . In this case, if the SLSS resource is not configured, synchronization signal transmission may not be possible.
  • the SLSS ID may be determined in advance, and a rule may be determined that a terminal that receives the SLSS ID does not relay the SLSS. This is because it is not necessary to separately set the resources for relaying the GNSS-based synchronization signal, and in most cases, if the terminal receives the GNSS even once, it may not need a separate sink relay if the clock can be maintained for a long time. to be.
  • the terminal may transmit the SLSS for a preset time even if the terminal loses the GNSS reception. That is, even if the UE which has successfully received the GNSS loses the GNSS reception, a rule may be determined to transmit the SLSS for a predetermined time. This is because even though the terminal does not receive the GNSS, it can maintain the clock for a certain time, thus allowing at least the SLSS transmission for a certain time during which the clock is maintained to help the terminal that has not received other GNSS to synchronize. can do.
  • the length of the timer capable of transmitting the SLSS may be signaled by a network as a physical layer or a higher layer signal or predetermined.
  • the terminal having a good ability to maintain a clock after receiving the GNSS may implement the SLSS for a longer time. For this, it may be determined whether to transmit the SLSS according to the GNSS reception quality. This is to determine whether to transmit the SLSS based on timing error, not to determine whether to transmit the SLSS based on the lost time of the GNSS. This has the advantage of ensuring a certain performance even when the degree of GNSS clock maintenance is different for each terminal. At this time, the magnitude of the timing error that determines whether to transmit the SLSS may be predetermined or may be signaled as a physical layer or higher layer signal by the network.
  • the terminal that successfully receives the GNSS may transmit the SLSS of the ID reserved for the GNSS to the UE whose RSRP is greater than or equal to the first threshold and less than the second threshold.
  • the first or second threshold may be infinity. This is to allow the network to successfully receive the GNSS and transmit GNSS-based synchronization signals to terminals located at a certain position within the network coverage.
  • the network may indicate whether the UE successfully receiving the GNSS transmits the SLSS as a physical layer or a higher layer signal.
  • the network may adjust / determine whether terminals in cell coverage transmit SLSS, thereby preventing unnecessary synchronization signal transmission or protecting Uu operation.
  • the terminal that successfully receives the GNSS may force the V2V operation by forcing the transmission of the SLSS.
  • the network may control the SLSS / PSBCH transmission.
  • Configuring the eNB to prioritize eNB timing can reuse the LTE Release 12/13 D2D mechanism. That is, network signaling or RSRP threshold to trigger SLSS / PSBCH transmission.
  • the UE may be configured to always send SLSS / PSBCH if the UE has GNSS timing with 'sufficient reliability'. The meaning of 'sufficient reliability' can be discussed in RAN4.
  • the LTE release 12/13 SLSS / PSBCH transmission condition may be reused.
  • the UE can always transmit the SLSS / PSBCH.
  • LTE release 12/13 mechanism reuse of SLSS / PSBCH transmission is reused when eNB prioritizes eNB timing over GNSS timing.
  • ii) In case of an In-coverage UE, if the eNB is set to prioritize GNSS timing over eNB timing, the UE always transmits SLSS / PSBCH if it has GNSS timing with sufficient reliability.
  • LTE release 12/13 SLSS / PSBCH transmission mechanism is reused. In addition, if the UE has GNSS timing with sufficient reliability, the UE always transmits SLSS / PSBCH.
  • one synchronization resource is configured for in-coverage UE and two synchronization resources are configured for out-coverage UE.
  • V2V when the UE selects GNSS as the timing reference, one additional synchronization resource may be configured for the incovery UE.
  • GNSS can be considered as a very wide cell, but since GNSS cannot configure synchronous resources, eNB can configure SLSS resources instead of GNSS.
  • Timing references should be discussed when the eNB configures additional synchronization resources.
  • LTE Release 12/13 D2D all timing offsets are configured for SFN 0. If the eNB has GNSS reception capability, the SFN is aligned with the DFN, so the eNB can configure additional synchronization resources for SFN 0. If the eNB does not have GNSS reception capability, SLSS timing mismatch occurs between cells. Since the synchronization resource for SLSS based GNSS is for the GNSS cell, the reference timing should be relative to DFN 0. This may be advantageous to have a common SLSS transmission timing, especially in an asynchronous scenario.
  • the eNB configures the SLSS resource for GNSS timing for SFN 0.
  • asynchronous network timing mismatches occur between cells.
  • two synchronization resources can be configured. One is for eNB-based SLSS / PSBCH transmission and the other is for GNSS-based SLSS / PSBCH transmission.
  • the synchronization resource is configured for DFN 0.
  • two resources may be configured for DFN 0.
  • One resource may be configured for SLSS transmission for a UE directly synchronized to GNSS for GNSS based synchronization, and another resource may be configured for SLSS transmission for a UE indirectly synchronized to GNSS. If the UE does not select GNSS as the timing reference, if the UE selects another UE as the synchronization reference, one of two resources is used for SLSS transmission and the other is used for SLSS tracking.
  • two synchronization resources for GNSS may be configured by the network in the in coverage in a manner different from the above. This is one for the terminal that directly receives the GNSS, and the other is for the SLSS transmission of the terminal in synchronization with the terminal receiving the GNSS. This method is to allow GNSS relaying in the network to transmit and receive more stable GNSS-based timing.
  • one or two separate SLSS resources for GNSS may be configured. This is to allocate additional resources ahead of time in order to prevent resource conflicts with independent synchronization sources.
  • the network when configuring a resource pool, the network can configure by setting which synchronization source the pool refers to. That is, the synchronization source may be set for each resource pool.
  • the synchronization reference of the specific resource pool may be GNSS. If GNSS is a reference, the corresponding resource pool bitmap can be interpreted based on DFN 0.
  • subframes may partially overlap.
  • the network may partially overlap a subframe to be used for sidelinks with a D (downlink) or S (special) subframe among cellular subframes while configuring the DFN.
  • the subframe overlapping with the corresponding subframe is preferably excluded from the D2D resource pool.
  • whether or not to be excluded from the sidelink subframe may vary depending on how much overlap is present. The following method may be considered.
  • a part of cellular subframes that cannot be used for sidelinks overlap in part, all of the subframes are excluded from sidelink transmission.
  • this method for example, if the DL of cellular timing overlaps two UL subframes of the DFN standard, both UL SFs are excluded from the sidelink subframe.
  • a threshold value for the degree of overlap may be set differently depending on whether overlapping the front or the rear in the DFN standard subframe. For example, in the case where the sidelink subframe overlaps later, an area corresponding to the symbol may overlap with the cellular subframe since the sidelink transmission subframe does not use the last symbol. However, when the sidelink transmitting terminal affects the cellular subframe due to Tx / Rx switching, the corresponding regions may be configured not to overlap.
  • the length of the OFDM symbol length excluding the Tx Rx switching region may continue to use the corresponding sidelink subframe even if the sidelink subframe overlaps with the side link subframe.
  • the UE may acquire the subframe number / boundary / SFN boundary of the base station in the cell and obtain the DFN based on the GNSS timing.
  • the UE recognizes the difference between the two and can be regarded as a subframe in which D and S cannot be used based on the SFN.
  • it may be regarded as a subframe in which the corresponding subframe cannot be used.
  • a resource pool bitmap may be applied except for a subframe in which a synchronization signal is transmitted.
  • the UE may recognize the difference between the SFN and the DFN differently according to the position of the UE.
  • the network may signal the magnitude of the timing offset of the SFN and the DFN as a physical layer or higher layer signal.
  • the SFN may be based on a transmission time of the base station or may be determined as an average SFN boundary of the terminal in the cell.
  • the UE may determine how much overlap occurs between the DFN and SFN subframes by using signaling for the difference between the SFN and the DFN, and the terminal may exclude the location of the subframe to be excluded.
  • the terminal may signal the offset information of the SFN and the DFN using a physical layer or higher layer signal (for example, some fields of the PSBCH) so that such information may be delivered to the terminal outside the network coverage.
  • a terminal in a cell sets the timing of the base station as a synchronous reference, the terminals using the DFN outside the base station may not accurately know the pool information used by the base station terminals.
  • the UE can know the SFN boundary based on the DFN.
  • the TDD configuration in the cell can be used to determine which subframes are D, S and synchronization subframes. Can set resource pool bitmap
  • out-of-coverage terminals may have a specific TDD configuration set in advance.
  • the TDD configuration is a virtual cell, and a resource pool bitmap may be applied except for D and S.
  • FIG. This may be a UE that performs sidelink communication in a cell in a partial coverage situation.
  • a UE in a cell uses TDD, and the TDD configuration is aligned with a previously set TDD configuration, a virtual cell is present. It may be regarded as TDD used by a terminal in a nearby cell, and may be an operation for protecting D and S of the corresponding cell.
  • the corresponding out coverage UEs provide protection for partially overlapping D and S.
  • the out coverage UE In order to perform the sidelink subframe exclusion operation. That is, the out coverage UE expects the cellular terminal to be located nearby, and the subframes overlapping with D and S (at least) in advance by using a preset TDD configuration, a preset information, or offset information obtained from another UE It is to perform the operation to exclude in advance.
  • the out coverage terminal may signal the offset of the SFN and the DFN used to inform the terminal in the network coverage of a physical layer or a higher layer signal (eg, a reserved field of the PSBCH).
  • terminals in a cell can also accurately interpret the bitmap of the neighbor cell only by knowing how far the SFN of the neighbor cell is from the DFN.
  • the network may signal a difference between SFNs and DFNs by neighboring cells as a physical layer or higher layer signal, or a SFN difference between SFNs and neighboring cells of a serving cell as a physical layer or higher layer signal.
  • the TDD configuration and synchronization subframes of neighbor cells may also be signaled. Through this, it is possible to know how many sidelink subframes are excluded from the neighbor cell and to accurately apply a resource pool bitmap.
  • the network may configure the discovery UE to always prioritize a specific synchronization source. For example, when the difference between the SFN and the DFN occurs more than a certain time, the UE may determine a rule to prioritize the eNB timing than the GNSS.
  • Table 6 below describes the operation of the terminal when there are three synchronization resources.
  • UE synchronization state Resource 1 (" InC resource "or” 1st OoC resource ") Resource 2 ("2nd OoC resource") Resource 3 ("GNSS resource”)
  • UE is InC
  • sync to eNB SS from SS_net PSBCH R12 / 13 solution
  • UE is InC , sync to GNSS Reserved SLSS ID, PSBCH PSBCH used to protect cell-edge UEs.
  • PSBCH should be transmitted on the first resource to avoid interference with OoC GNSS UEs PSBCH.
  • UE synchronization state Resource 1 (" InC resource “or” 1st OoC resource ") Resource 2 ("2nd OoC resource") Resource 3 (" GNSS resource ”)
  • UE is InC
  • sync to eNB SS from SS_net PSBCH R12 / 13 solution
  • UE is InC , sync to GNSS Reserved SLSS ID, PSBCH PSBCH used to protect cell-edge UEs.
  • PSBCH should be transmitted on the first resource to avoid interference with OoC GNSS UEs PSBCH.
  • UE is OoC, synchronized to GNSS if incoverage UE ’s synchronization signal is successfully received.
  • the part corresponding to Resource 3 (“GNSS resource”) may or may not be transmitted. If it is not transmitted, since the transmitting terminal does not transmit two synchronization signals, the energy consumption will be reduced accordingly. In the case of transmission, since at least one sink is always transmitted, a stable synchronization signal can be transmitted to the receiving terminal.
  • the following method may be considered.
  • a synchronization signal may be transmitted from a synchronization resource (Resource 2).
  • This method can protect in-coverage sink resources and always receive a synchronization signal of an in-coverage UE.
  • the network can configure or preconfigure resources to be used.
  • a method in which UEs synchronized with a synchronization signal transmitted from synchronization resource 2 selects a sync transmission resource i) use of synchronization resource 1 (Resource 1) ii) use of synchronization resource 1/3 randomly iii) use a resource to be used in a network
  • synchronization resource 1 Resource 1
  • the terminal proposes a method of excluding all of the synchronization resource positions configured for the out coverage terminal from the V2V subframe. For example, even if the in-coverage terminal transmits a synchronization signal only in one synchronization resource, the V2V subframe indexing is not performed even in the synchronization resource configured for the out coverage UE. In this case, since the in coverage terminal and the out coverage terminal assume the same synchronization resource and perform subframe indexing, the above-mentioned problem disappears.
  • the network can configure two or three sidelink resources, and the agreement on synch source priority shown in Table 2 below must be satisfied regardless of the number of sidelink sink resources.
  • -P1 ' UE directly synchronized to eNB -P2': UE indirectly synchronized to eNB (ie, UE whose SyncRef is another UE directly synchronized to eNB) -P3 ': GNSS -P4': UE directly synchronized to GNSS- P5 ': UE indirectly synchronized to GNSS (ie, UE whose SyncRef is another UE directly synchronized to GNSS) -P4' and P5 'are differentiated at least when two sync resources are (pre) configured.
  • GNSS -P2 the following UE has the same priority: -UE directly synchronized to GNSS -UE directly synchronized to eNB -P3: the following UE has the same priority: -UE indirectly synchronized to GNSS (if RAN1 decides to differentiate between direct and indirect synchronization to GNSS) -UE indirectly synchronized to eNB -P4: the remaining UEs have the lowest priority.
  • GNSS -P2 the following UE has the same priority: -UE directly synchronized to GNSS -UE directly synchronized to eNB -P3: the following UE has the same priority: -UE indirectly synchronized to GNSS (if RAN1 decides to differentiate between direct and indirect synchronization to GNSS) -UE indirectly synchronized to eNB -P4: the remaining UEs have the lowest priority.
  • RAN1 decides to differentiate between direct and indirect synchronization to GNSS
  • eNB -P4 the remaining
  • -In-coverage indicator is used to differentiate direct GNSS and in-direct GNSS -UE directly and indirectly synchronized to GNSS set in-coverage indicator to 1 and 0 respectively.
  • -SLSS ID 168 is used to differentiate 1 hop sync. or more hops for GNSS based synchronization -FFS1 SLSS ID selection of “standalone UE”.
  • the sync resource for the in-coverage is one of the resource chosen from the out-of-coverage resources as D2D.-When three resources are included, the following behavior is used.
  • -For UE OoC sync to UE InC: -Resource 2: PSBCH (except DFN) and SLSSID from Sync Ref, InC bit 0.
  • Resource 1 is “InC resource” or “1st OoC resource”
  • Resource 2 and 3 are “2nd OoC resource” and “3rd OoC resource” respectively.
  • the standalone UE (the terminal which determines the synchronization signal timing by itself) is randomly selected among the SLSS IDs 168 to 335, P3 / P4 or P5 '/ P6' is distinguished. That is, when two resources are set, the standalone UE may consider a method of selecting one of the SLSS IDs ⁇ 168 ⁇ 335 ⁇ .
  • the UE When the UE sets GNSS as a synchronization reference, it transmits the SLSS ID 0 from resource 1 or 3. In this case, the synchronization signal relayed from resource 2 may be transmitted.
  • One of the SLSS ID oons is reserved for the synchronization signal relayed from the in coverage to distinguish the synchronization signal relayed from the incoverage and the synchronization signal relayed from the out coverage. The other proposes a method of reserve for synchronization signals relayed from out coverage.
  • SLSS ID 168 is reserved for a synchronization signal propagated from incoverage (and the initial synchronization is derived from GNSS) and SLSS ID 169 is a terminal synchronized with SLSS ID 0 propagated from out coverage (i.e. transmitted from sync resource 3).
  • the standalone UE proposes a method of selecting one of the SLSS IDs 170 to 335. Through this method, the direct / indirect GNSS UE and the standalone UE can be distinguished from each other, and the SLSS propagated from within the network coverage and the SLSS propagated out of the coverage can be distinguished from each other. Existing rel.
  • the DMRS of PSBCH is derived from SLSS ID. If the ID is the same but the PSBCH content is different (preconfigured or configured by the network), if the same SSRS / PSBCH is received from the same resource, the DMRS is the same. Decoding becomes impossible. To solve this problem, a terminal that synchronizes with SLSS ID 0 transmitted from synchronous resource 3 is transmitted from synchronous resource 2 using SLSS ID 169.
  • the SLSS ID set of standalone UEs is changed. If you have two, you can choose 168 ⁇ 335, and if you have three, you can choose 170 ⁇ 335.
  • different PLMNs are configured to perform sidelink transmission and reception on the same carrier
  • operators set different numbers of synchronization resources
  • ambiguity of SLSS ID sets selected by standalone UEs occurs. For example, operator A sets two sync resources to select from 168 to 335, and operator B sets three sync resources to select from 170 to 335. If a terminal selects 168 as a standalone terminal, this SLSS ID has a priority. The problem arises that cognitive application becomes obscure.
  • the standalone UE proposes a method of selecting a SLSS ID among SLSS IDs of the same set regardless of the number of resources. That is, even if two synchronization resources are set in the proposal, one of the SLSS IDs 170 to 335 is selected to eliminate ambiguity in Inter PLMN sidelink communication. In other words, even if two synchronization resources are set according to this proposal, the SLSS IDs 168 and 169 are reserved and not used.
  • the above descriptions are not limited only to direct communication between terminals, and may be used in uplink or downlink, where a base station or a relay node may use the proposed method.
  • examples of the proposed scheme described above may also be regarded as a kind of proposed schemes as they may be included as one of the implementation methods of the present invention.
  • the above-described proposed schemes may be independently implemented, some proposed schemes may be implemented in a combination (or merge) form.
  • Information on whether the proposed methods are applied is informed by the base station through a predefined signal (for example, a physical layer signal or a higher layer signal) to the terminal or received by the transmitting terminal. Rules may be defined to signal to the terminal or to request that the receiving terminal requests the transmitting terminal.
  • FIG. 11 is a diagram illustrating the configuration of a transmission point apparatus and a terminal apparatus according to an embodiment of the present invention.
  • the transmission point apparatus 10 may include a receiver 11, a transmitter 12, a processor 13, a memory 14, and a plurality of antennas 15. .
  • the plurality of antennas 15 refers to a transmission point apparatus that supports MIMO transmission and reception.
  • the reception device 11 may receive various signals, data, and information on the uplink from the terminal.
  • the transmitter 12 may transmit various signals, data, and information on downlink to the terminal.
  • the processor 13 may control the overall operation of the transmission point apparatus 10.
  • the processor 13 of the transmission point apparatus 10 according to an embodiment of the present invention may process matters necessary in the above-described embodiments.
  • the processor 13 of the transmission point apparatus 10 performs a function of processing the information received by the transmission point apparatus 10, information to be transmitted to the outside, and the memory 14 stores the calculated information and the like. It may be stored for a predetermined time and may be replaced by a component such as a buffer (not shown).
  • the terminal device 20 may include a receiver 21, a transmitter 22, a processor 23, a memory 24, and a plurality of antennas 25. have.
  • the plurality of antennas 25 refers to a terminal device that supports MIMO transmission and reception.
  • the receiving device 21 may receive various signals, data, and information on downlink from the base station.
  • the transmitter 22 may transmit various signals, data, and information on the uplink to the base station.
  • the processor 23 may control operations of the entire terminal device 20.
  • the processor 23 of the terminal device 20 may process matters necessary in the above-described embodiments.
  • the processor 23 of the terminal device 20 performs a function of processing the information received by the terminal device 20, information to be transmitted to the outside, etc., and the memory 24 stores the calculated information and the like for a predetermined time. And may be replaced by a component such as a buffer (not shown).
  • the description of the transmission point apparatus 10 may be equally applicable to a relay apparatus as a downlink transmission entity or an uplink reception entity, and the description of the terminal device 20 is a downlink. The same may be applied to a relay apparatus as a receiving subject or an uplink transmitting subject.
  • Embodiments of the present invention described above may be implemented through various means.
  • embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
  • a method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). It may be implemented by field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, and the like.
  • the method according to the embodiments of the present invention may be implemented in the form of an apparatus, procedure, or function for performing the above-described functions or operations.
  • the software code may be stored in a memory unit and driven by a processor.
  • the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.
  • FIG. 11 is a diagram illustrating the configuration of a transmission point apparatus and a terminal apparatus according to an embodiment of the present invention.
  • the transmission point apparatus 10 may include a receiver 11, a transmitter 12, a processor 13, a memory 14, and a plurality of antennas 15. .
  • the plurality of antennas 15 refers to a transmission point apparatus that supports MIMO transmission and reception.
  • the reception device 11 may receive various signals, data, and information on the uplink from the terminal.
  • the transmitter 12 may transmit various signals, data, and information on downlink to the terminal.
  • the processor 13 may control the overall operation of the transmission point apparatus 10.
  • the processor 13 of the transmission point apparatus 10 according to an embodiment of the present invention may process matters necessary in the above-described embodiments.
  • the processor 13 of the transmission point apparatus 10 performs a function of processing the information received by the transmission point apparatus 10, information to be transmitted to the outside, and the memory 14 stores the calculated information and the like. It may be stored for a predetermined time and may be replaced by a component such as a buffer (not shown).
  • the terminal device 20 may include a receiver 21, a transmitter 22, a processor 23, a memory 24, and a plurality of antennas 25. have.
  • the plurality of antennas 25 refers to a terminal device that supports MIMO transmission and reception.
  • the receiving device 21 may receive various signals, data, and information on downlink from the base station.
  • the transmitter 22 may transmit various signals, data, and information on the uplink to the base station.
  • the processor 23 may control operations of the entire terminal device 20.
  • the processor 23 of the terminal device 20 may process matters necessary in the above-described embodiments.
  • the processor 23 of the terminal device 20 performs a function of processing the information received by the terminal device 20, information to be transmitted to the outside, etc., and the memory 24 stores the calculated information and the like for a predetermined time. And may be replaced by a component such as a buffer (not shown).
  • the description of the transmission point apparatus 10 may be equally applicable to a relay apparatus as a downlink transmission entity or an uplink reception entity, and the description of the terminal device 20 is a downlink. The same may be applied to a relay apparatus as a receiving subject or an uplink transmitting subject.
  • Embodiments of the present invention described above may be implemented through various means.
  • embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
  • a method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). It may be implemented by field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, and the like.
  • the method according to the embodiments of the present invention may be implemented in the form of an apparatus, procedure, or function for performing the above-described functions or operations.
  • the software code may be stored in a memory unit and driven by a processor.
  • the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.
  • Embodiments of the present invention as described above may be applied to various mobile communication systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un mode de réalisation de la présente invention concerne un procédé de réception d'un signal de synchronisation de liaison latérale (SLSS, "sidelink synchronization signal") par un terminal dans un système de communication sans fil, comprenant les étapes consistant à : recevoir un canal de diffusion de liaison latérale physique (PSBCH, "physical sidelink broadcast channel") ; déterminer ce qui, entre des systèmes de satellites de navigation mondiale (GNSS, "global navigation satellite systems") ou un eNB, doit être une source de synchronisation selon des informations de priorité incluses dans le PSBCH ; et recevoir un SLSS associé à la source de synchronisation déterminée, le terminal déterminant que les informations de priorité sont valides uniquement lorsqu'un réseau mobile terrestre public (PLMN, "public land mobile network") associé aux informations de priorité correspond à un PLMN auquel le terminal appartient.
PCT/KR2017/010726 2016-09-27 2017-09-27 Procédé et dispositif de transmission et de réception de signal de synchronisation d'un terminal de communication dispositif à dispositif dans un système de communication sans fil WO2018062850A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020187021051A KR102063084B1 (ko) 2016-09-27 2017-09-27 무선 통신 시스템에서 장치 대 장치 통신 단말의 동기 신호 송수신 방법 및 장치
EP17856736.8A EP3522620A4 (fr) 2016-09-27 2017-09-27 Procédé et dispositif de transmission et de réception de signal de synchronisation d'un terminal de communication dispositif à dispositif dans un système de communication sans fil
US16/064,730 US10575269B2 (en) 2016-09-27 2017-09-27 Method and device for transmitting and receiving synchronization signal of device-to-device communication terminal in wireless communication system
CN201780059636.5A CN109804678B (zh) 2016-09-27 2017-09-27 在无线通信系统中发送和接收装置对装置通信终端的同步信号的方法和装置
US16/799,058 US11388687B2 (en) 2016-09-27 2020-02-24 Method and device for transmitting and receiving synchronization signal of device-to-device communication terminal in wireless communication system
US17/861,965 US11889442B2 (en) 2016-09-27 2022-07-11 Method and device for transmitting and receiving synchronization signal of device-to-device communication terminal in wireless communication system

Applications Claiming Priority (12)

Application Number Priority Date Filing Date Title
US201662400623P 2016-09-27 2016-09-27
US62/400,623 2016-09-27
US201662403050P 2016-09-30 2016-09-30
US62/403,050 2016-09-30
US201662407513P 2016-10-12 2016-10-12
US62/407,513 2016-10-12
US201662426219P 2016-11-23 2016-11-23
US62/426,219 2016-11-23
US201762458562P 2017-02-13 2017-02-13
US62/458,562 2017-02-13
US201762458590P 2017-02-14 2017-02-14
US62/458,590 2017-02-14

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/064,730 A-371-Of-International US10575269B2 (en) 2016-09-27 2017-09-27 Method and device for transmitting and receiving synchronization signal of device-to-device communication terminal in wireless communication system
US16/799,058 Continuation US11388687B2 (en) 2016-09-27 2020-02-24 Method and device for transmitting and receiving synchronization signal of device-to-device communication terminal in wireless communication system

Publications (1)

Publication Number Publication Date
WO2018062850A1 true WO2018062850A1 (fr) 2018-04-05

Family

ID=61763559

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/010726 WO2018062850A1 (fr) 2016-09-27 2017-09-27 Procédé et dispositif de transmission et de réception de signal de synchronisation d'un terminal de communication dispositif à dispositif dans un système de communication sans fil

Country Status (5)

Country Link
US (3) US10575269B2 (fr)
EP (1) EP3522620A4 (fr)
KR (1) KR102063084B1 (fr)
CN (1) CN109804678B (fr)
WO (1) WO2018062850A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109565648A (zh) * 2018-11-02 2019-04-02 北京小米移动软件有限公司 同步信号发送方法及装置
CN110958092A (zh) * 2018-09-26 2020-04-03 维沃移动通信有限公司 信号发送方法、接收方法及发送设备、接收设备
CN111294769A (zh) * 2019-01-11 2020-06-16 北京展讯高科通信技术有限公司 同步源信息的确定、指示方法及装置、存储介质、终端
WO2020175891A1 (fr) * 2019-02-25 2020-09-03 엘지전자 주식회사 Procédé et dispositif permettant de réaliser une synchronisation de liaison latérale dans un système de communication sans fil
WO2020258289A1 (fr) * 2019-06-28 2020-12-30 北京小米移动软件有限公司 Procédé d'envoi de données, procédé de réception de données, appareil et dispositif
CN112425217A (zh) * 2018-07-16 2021-02-26 Oppo广东移动通信有限公司 一种同步源优先级确定方法、设备和计算机存储介质
CN113424606A (zh) * 2019-02-14 2021-09-21 苹果公司 用于具有优化的接收器处理的增强型车辆到一切使用案例的nr侧链路同步信号的设计
EP3855773A4 (fr) * 2018-09-20 2021-09-22 Beijing Xiaomi Mobile Software Co., Ltd. Procédé et dispositif de synchronisation de véhicule-à-tout
CN114145053A (zh) * 2019-07-30 2022-03-04 高通股份有限公司 用于基于侧行链路同步信号优先化进行同步的技术
US20220132448A1 (en) * 2020-10-27 2022-04-28 Electronics And Telecommunications Research Institute Method and apparatus for synchronization in wireless communication system
CN114828164A (zh) * 2018-05-10 2022-07-29 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
JP2022552328A (ja) * 2019-11-07 2022-12-15 維沃移動通信有限公司 信号伝送の方法と通信機器

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11153837B2 (en) * 2015-07-02 2021-10-19 Qualcomm Incorporated Synchronization for wireless communication systems
CN109804678B (zh) * 2016-09-27 2021-09-21 Lg电子株式会社 在无线通信系统中发送和接收装置对装置通信终端的同步信号的方法和装置
KR102388049B1 (ko) * 2017-02-14 2022-04-19 삼성전자주식회사 무선 통신 시스템에서 통신을 수행하는 장치 및 이를 위한 방법
CN112332963A (zh) * 2017-04-27 2021-02-05 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
CN109392078B (zh) * 2017-08-11 2021-11-02 中兴通讯股份有限公司 信号检测、发送方法及装置、远端用户设备
WO2019066475A1 (fr) * 2017-09-28 2019-04-04 Samsung Electronics Co., Ltd. Procédé et équipement de sélection de source de référence de synchronisation pour communication de liaison latérale à porteuses multiples
WO2019080111A1 (fr) * 2017-10-27 2019-05-02 Oppo广东移动通信有限公司 Procédé et dispositif de radiocommunication
WO2019084734A1 (fr) * 2017-10-30 2019-05-09 Oppo广东移动通信有限公司 Procédé d'attribution de ressources, dispositif côté réseau et dispositif de terminal
WO2019125750A1 (fr) * 2017-12-18 2019-06-27 Kyocera Corporation Synchronisation de liaison descendante avancée pour une acquisition de signal de synchronisation commune
US11368929B2 (en) * 2017-12-18 2022-06-21 Kyocera Corporation Reduced system acquisition time for MTC using common synchronization channel
KR102604254B1 (ko) * 2018-08-10 2023-11-20 주식회사 아이티엘 Nr v2x 시스템을 위한 동기화 절차 수행 방법 및 그 장치
US11533695B2 (en) * 2018-08-10 2022-12-20 Apple Inc. Synchronization for sidelink based on prioritization of synchronization signals
JP7038837B2 (ja) * 2018-08-24 2022-03-18 株式会社Ｎｔｔドコモ 制御装置及び制御方法
US11463976B2 (en) 2018-09-28 2022-10-04 Lg Electronics Inc. Method for terminal, which supports sidelink, to transmit signals in wireless communication system, and terminal therefor
CN116961845A (zh) * 2018-09-28 2023-10-27 联发科技（新加坡）私人有限公司 侧链路同步的方法及其用户设备
KR102586632B1 (ko) * 2018-09-28 2023-10-11 주식회사 아이티엘 Nr v2x 시스템을 위한 harq 동작을 수행하는 방법 및 장치
WO2020204498A1 (fr) * 2019-03-29 2020-10-08 엘지전자 주식회사 Id de signal de synchronisation de liaison latérale
WO2020205990A1 (fr) * 2019-04-02 2020-10-08 Apple Inc. Systèmes et procédés de procédure améliorée de synchronisation nr-v2x
WO2020204442A1 (fr) * 2019-04-05 2020-10-08 엘지전자 주식회사 Proposition, relative à une erreur de temps de transmission, pour une communication de liaison latérale v2x
US11382098B2 (en) * 2019-06-14 2022-07-05 Qualcomm Incorporated Sidelink timing control
US11895694B2 (en) 2019-07-30 2024-02-06 Qualcomm Incorporated Time-division multiplexing of uplink communications during make-before-break handover
US11375464B2 (en) * 2019-08-15 2022-06-28 Qualcomm Incorporated Sidelink synchronization priority rules
CN114342428A (zh) * 2019-08-28 2022-04-12 Lg 电子株式会社 用于在nr v2x中执行同步的方法和装置
EP3996430A4 (fr) * 2019-08-28 2022-08-31 LG Electronics Inc. Procédé et dispositif de sélection de la référence de synchronisation dans nr v2x
CN110572231B (zh) * 2019-09-09 2023-06-06 北京百度网讯科技有限公司 时间同步方法、装置及设备
CN115190579A (zh) * 2019-11-09 2022-10-14 上海朗帛通信技术有限公司 一种被用于无线通信的方法和装置
US11641629B2 (en) * 2020-01-10 2023-05-02 Qualcomm Incorporated Sidelink synchronization assistance
CN113193930B (zh) * 2020-01-14 2024-07-02 维沃移动通信有限公司 信息处理方法及通信设备
CN113141594B (zh) * 2020-01-17 2022-10-14 大唐高鸿智联科技(重庆)有限公司 一种同步方法、装置及车联网v2x设备
US20210227480A1 (en) * 2020-01-21 2021-07-22 Qualcomm Incorporated Power-efficient sidelink synchronization signal transmission
CN111314852B (zh) * 2020-02-14 2021-08-03 惠州Tcl移动通信有限公司 数据传输方法、装置、存储介质及电子终端
KR20210106741A (ko) * 2020-02-21 2021-08-31 삼성전자주식회사 무선 통신 시스템에서 빔 정보 획득 방법 및 장치
US11770765B2 (en) * 2020-07-22 2023-09-26 Qualcomm Incorporated Radio base station sleep mode-beacon and wakeup
TWI783580B (zh) * 2020-08-03 2022-11-11 新加坡商聯發科技（新加坡）私人有限公司 側行鏈路同步之方法
CN112235215B (zh) * 2020-09-09 2022-09-13 鹏城实验室 一种无线信道探测方法、存储介质及终端设备
CN112367702B (zh) * 2020-10-27 2022-01-04 Tcl通讯（宁波）有限公司 同步方法、装置及存储介质
US11467850B2 (en) 2020-11-11 2022-10-11 Micron Technology, Inc. Computing device reboot
WO2022122161A1 (fr) * 2020-12-10 2022-06-16 Huawei Technologies Co., Ltd. Dispositif utilisateur et procédé de fonctionnement d'une communication de liaison latérale
US11991656B2 (en) * 2021-01-25 2024-05-21 Qualcomm Incorporated Synchronization signal selection across multiple transceiver nodes
CN115038061A (zh) * 2021-03-08 2022-09-09 华为技术有限公司 一种同步方法及设备
FI20215476A1 (en) * 2021-04-23 2022-03-30 Nokia Technologies Oy Selection of radio resources for direct communication between NTN terminals
CN116567569A (zh) * 2022-01-30 2023-08-08 中国移动通信有限公司研究院 一种直连链路定位同步方法、装置、通信设备和存储介质
WO2023212854A1 (fr) * 2022-05-05 2023-11-09 Qualcomm Incorporated Synchronisation basée sur la source pour des dispositifs sans fil
WO2023230947A1 (fr) * 2022-06-01 2023-12-07 Qualcomm Incorporated Techniques pour une sélection de paramètres de communication sur la base de signaux de synchronisation de liaison latérale

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014182342A1 (fr) * 2013-05-06 2014-11-13 Intel IP Corporation Signaux de synchronisation a priorites et mecanisme pour systemes de communication de dispositif a dispositif distribues
WO2016099888A1 (fr) * 2014-12-18 2016-06-23 Qualcomm Incorporated Synchronisation distribuée de dispositifs de l'internet de tout (ioe)

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015142090A1 (fr) * 2014-03-19 2015-09-24 엘지전자 주식회사 Procédé pour opération en dispositif à dispositif (d2d) exécutée par un terminal dans un système de communication sans fil et terminal utilisant le procédé
CN104935401B (zh) * 2014-03-21 2018-06-19 上海诺基亚贝尔股份有限公司 一种设备对设备通信中用于传输数据的方法和设备
KR102314442B1 (ko) * 2015-02-06 2021-10-19 삼성전자주식회사 D2d 네트워크에서 ue 디스커버리 방법 및 시스템
WO2016164510A1 (fr) * 2015-04-09 2016-10-13 Sharp Laboratories Of America, Inc. Procédé et appareil permettant de mettre en œuvre une couverture partielle et paquets de ressources de découverte de liaison latérale hors couverture pour des communications sans fil
US10383147B2 (en) * 2015-12-28 2019-08-13 Samsung Electronics Co., Ltd. Methods and apparatus for resource collision avoidance in vehicle to vehicle communication
CN106998575B (zh) * 2016-01-22 2020-09-29 株式会社Kt 用于执行v2x通信的用户设备的移动性的控制方法及其装置
WO2017165797A1 (fr) * 2016-03-25 2017-09-28 Sharp Laboratories Of America, Inc. Procédé et appareil de synchronisation pour communications v2x
KR102467752B1 (ko) * 2016-04-01 2022-11-16 주식회사 아이티엘 V2x 통신에서 동기화 방법 및 장치
CN109804678B (zh) * 2016-09-27 2021-09-21 Lg电子株式会社 在无线通信系统中发送和接收装置对装置通信终端的同步信号的方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014182342A1 (fr) * 2013-05-06 2014-11-13 Intel IP Corporation Signaux de synchronisation a priorites et mecanisme pour systemes de communication de dispositif a dispositif distribues
WO2016099888A1 (fr) * 2014-12-18 2016-06-23 Qualcomm Incorporated Synchronisation distribuée de dispositifs de l'internet de tout (ioe)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
12 August 2016, 3GPP DRAFT; R1-166168, - 20160821 - 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, article HUAWEI; HISILICON: "Timing alignment of different synchronization sources for V2V", XP051140088 *
21 August 2016, 3GPP DRAFT; R1-166200, - 20160821 - 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, article HUAWEI; HISILICON: "OOC synchronization priority and SLSS ID set definition", XP051142161 *
HUAWEI; HISILICON, 12 August 2016, 3GPP DRAFT; R1-166201, - 20160812 - 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, article "PSBCH contents and SLSS transmission procedure", XP051142162 *
See also references of EP3522620A4 *

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828164A (zh) * 2018-05-10 2022-07-29 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN112425217A (zh) * 2018-07-16 2021-02-26 Oppo广东移动通信有限公司 一种同步源优先级确定方法、设备和计算机存储介质
EP3823366A4 (fr) * 2018-07-16 2021-07-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de détermination de priorité de source de synchronisation, et support d'enregistrement informatique
EP3855773A4 (fr) * 2018-09-20 2021-09-22 Beijing Xiaomi Mobile Software Co., Ltd. Procédé et dispositif de synchronisation de véhicule-à-tout
US11917562B2 (en) 2018-09-20 2024-02-27 Beijing Xiaomi Mobile Software Co., Ltd. Vehicle-to-everything synchronization method and device
CN110958092A (zh) * 2018-09-26 2020-04-03 维沃移动通信有限公司 信号发送方法、接收方法及发送设备、接收设备
CN109565648A (zh) * 2018-11-02 2019-04-02 北京小米移动软件有限公司 同步信号发送方法及装置
CN111294769B (zh) * 2019-01-11 2022-08-09 北京紫光展锐通信技术有限公司 同步源信息的确定、指示方法及装置、存储介质、终端
CN111294769A (zh) * 2019-01-11 2020-06-16 北京展讯高科通信技术有限公司 同步源信息的确定、指示方法及装置、存储介质、终端
CN113424606A (zh) * 2019-02-14 2021-09-21 苹果公司 用于具有优化的接收器处理的增强型车辆到一切使用案例的nr侧链路同步信号的设计
WO2020175891A1 (fr) * 2019-02-25 2020-09-03 엘지전자 주식회사 Procédé et dispositif permettant de réaliser une synchronisation de liaison latérale dans un système de communication sans fil
WO2020258289A1 (fr) * 2019-06-28 2020-12-30 北京小米移动软件有限公司 Procédé d'envoi de données, procédé de réception de données, appareil et dispositif
CN114145053A (zh) * 2019-07-30 2022-03-04 高通股份有限公司 用于基于侧行链路同步信号优先化进行同步的技术
CN114145053B (zh) * 2019-07-30 2024-03-26 高通股份有限公司 用于基于侧行链路同步信号优先化进行同步的技术
JP2022552328A (ja) * 2019-11-07 2022-12-15 維沃移動通信有限公司 信号伝送の方法と通信機器
EP4057712A4 (fr) * 2019-11-07 2023-01-11 Vivo Mobile Communication Co., Ltd. Procédé de transmission de signal et dispositif de communication
JP7326603B2 (ja) 2019-11-07 2023-08-15 維沃移動通信有限公司 信号伝送の方法と通信機器
US20220132448A1 (en) * 2020-10-27 2022-04-28 Electronics And Telecommunications Research Institute Method and apparatus for synchronization in wireless communication system

Also Published As

Publication number Publication date
KR20180088735A (ko) 2018-08-06
US20190098589A1 (en) 2019-03-28
US11889442B2 (en) 2024-01-30
US11388687B2 (en) 2022-07-12
US10575269B2 (en) 2020-02-25
CN109804678A (zh) 2019-05-24
US20200196257A1 (en) 2020-06-18
US20220353833A1 (en) 2022-11-03
EP3522620A4 (fr) 2020-10-14
EP3522620A1 (fr) 2019-08-07
CN109804678B (zh) 2021-09-21
KR102063084B1 (ko) 2020-01-07

Similar Documents

Publication Publication Date Title
WO2018062850A1 (fr) Procédé et dispositif de transmission et de réception de signal de synchronisation d'un terminal de communication dispositif à dispositif dans un système de communication sans fil
WO2019098772A1 (fr) Procédé et appareil permettant de réaliser une communication de liaison latérale dans un système de communication sans fil
WO2017007285A1 (fr) Procédé et dispositif d'émission/réception de signal de synchronisation de terminal de communication de dispositif à dispositif dans un système de communication sans fil
WO2018143776A1 (fr) Procédé de surveillance de liaison sans fil par un terminal dans un système de communication sans fil et dispositif le prenant en charge
WO2018143771A1 (fr) Procédé d'émission et de réception de signaux entre un terminal et une station de base dans un système de communication sans fil, et appareil pour prendre en charge celui-ci
WO2020032740A1 (fr) Procédé d'émission/réception de signal dans un système de communication sans fil et dispositif correspondant
WO2019139298A1 (fr) Procédé de transmission et de réception de canal d'accès aléatoire sans fil, et dispositif associé
WO2019098769A1 (fr) Procédé d'émission et de réception de signal de référence et dispositif associé
WO2018231010A1 (fr) Procédé d'émission-réception de canal de liaison descendante et appareil associé
WO2019160266A1 (fr) Procédé de mesure de différence de rythme des trames et équipement utilisateur mettant en œuvre le procédé
WO2017213420A1 (fr) Procédé pour obtenir des informations relatives à un préfixe cyclique dans un système de communication sans fil et dispositif associé
WO2018143786A1 (fr) Procédé d'exécution d'une communication de liaison latérale dans un système de communications sans fil, et dispositif associé
WO2018128297A1 (fr) Procédé de notification de données de mesure, et terminal associé
WO2016036182A1 (fr) Procédé de mise en œuvre d'une communication entre dispositifs dans un système de communication sans fil, et dispositif associé
WO2018062937A1 (fr) Procédé de transmission et de réception de données dans un système de communication sans fil et appareil associé
WO2018231030A1 (fr) Procédés d'émission et de réception de canal physique de commande de liaison montante entre un terminal et une station de base dans un système de communication sans fil, et appareils pour sa prise en charge
WO2018030854A1 (fr) Procédé permettant à un terminal de transmettre des données à un autre terminal dans un système de communication sans fil
WO2018016921A1 (fr) Procédés destinés à la transmission et à la réception d'informations de commande de liaison descendante entre station de base et terminal dans un système de communication sans fil, et dispositifs destinés à prendre en charge lesdits procédés
WO2018062841A1 (fr) Procédé d'émission et de réception de signal entre un terminal et une station de base dans un système de communication sans fil, et appareil permettant de prendre en charge celui-ci
WO2018079969A1 (fr) Procédé de réalisation d'une gestion de faisceau dans un système de communication sans fil et appareil associé
WO2018147700A1 (fr) Procédé pour un terminal et une station de base, comprenant une pluralité de points d'émission et de réception (trp) pour émettre/recevoir des signaux dans un système de communications sans fil, et dispositif associé
WO2017043878A1 (fr) Procédé et appareil pour recevoir un canal physique de diffusion de liaison descendante dans un système d'accès radio qui prend en charge un internet des objets à bande étroite
WO2015163634A1 (fr) Procédé et équipement utilisateur pour réaliser une mesure
WO2019083344A1 (fr) Procédé de transmission d'informations de positionnement par un terminal dans un système de communication sans fil soutenant une liaison latérale, et dispositif a cet effet
WO2016021979A1 (fr) Procédé et appareil d'utilisateur de réception de signal de synchronisation et procédé et station de base de transmission de signal de synchronisation

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20187021051

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020187021051

Country of ref document: KR

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

Ref document number: 17856736

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017856736

Country of ref document: EP

Effective date: 20190429