WO2018125287A1 - Terminal de communication et procédé d'initiation de communication - Google Patents

Terminal de communication et procédé d'initiation de communication Download PDF

Info

Publication number
WO2018125287A1
WO2018125287A1 PCT/US2017/039851 US2017039851W WO2018125287A1 WO 2018125287 A1 WO2018125287 A1 WO 2018125287A1 US 2017039851 W US2017039851 W US 2017039851W WO 2018125287 A1 WO2018125287 A1 WO 2018125287A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication terminal
communication
synchronization
frequency
bandwidth
Prior art date
Application number
PCT/US2017/039851
Other languages
English (en)
Inventor
Biljana Badic
Stefania Sesia
Thomas Luetzenkirchen
Alexey Khoryaev
Christian Drewes
Huaning Niu
Birgit Breining
Alexandre Stojanovski
Markus Dominik MUECK
Original Assignee
Intel IP Corporation
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
Priority claimed from PCT/IB2016/001995 external-priority patent/WO2018122571A1/fr
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018125287A1 publication Critical patent/WO2018125287A1/fr

Links

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
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • Exemplary implementations described herein generally relate to communication terminals and methods for initiating a communication.
  • a cellular mobile communication system may allow direct communication between mobile communication devices which bypasses the cellular mobile communication system's base stations (i.e. device-to-device communication).
  • direct communication may impact regular operation of the mobile communication system, i.e. communication via its base stations or it is not possible due to a lack of communication resources, e.g. when the cellular mobile communication system is heavily loaded or communication terminals are too far apart as direct communication was designed for short range. Accordingly, approaches are desirable which allow a usage of direct communication in a wide range of scenarios, including unlicensed bands and narrow bandwidth.
  • Figure 1 shows a communication system, e.g. an LTE (Long Term Evolution)
  • LTE Long Term Evolution
  • Figure 2 shows a communication arrangement illustrating D2D (device-to-device)
  • FIG. 3 shows a table summarizing the main regulatory requirements.
  • Figure 4 shows a communication arrangement illustrating DNB-U communication.
  • Figure 5 illustrates the functionality of a DNB-U Synch device.
  • Figure 6 shows a communication arrangement
  • Figure 7 shows a message flow diagram illustrating a message flow according to 3GPP
  • Figure 8 shows a message flow diagram illustrating an example of a two-stage
  • Figure 9 shows a signal diagram illustrating a frequency hopping pattern for
  • Figure 10 illustrates a synchronization procedure
  • Figure 11 illustrates a synchronization procedure according to a first option.
  • Figure 12 illustrates a synchronization procedure according to a second option.
  • Figure 13 illustrates a synchronization procedure according to a first option for another use case.
  • Figure 14 illustrates a synchronization procedure according to a second option for another use case.
  • Figure 15 shows a signal diagram illustrating a first example of a synchronization
  • Figure 16 shows a signal diagram illustrating a second example of a synchronization framework.
  • Figure 17 shows an NPSS sequence in NB-IOT.
  • Figure 18 shows a U-NPSS structure according to a first example.
  • Figure 19 shows an NSSS sequence in NB-IOT.
  • Figure 20 shows a U-NPSS structure according to a second example.
  • Figure 21 shows diagrams each showing time to acquire 90% probability of detection depending on SNR illustrating the performance that can be achieved by the U-
  • Figure 22 shows the synchronization sequence of in a legacy D2D system.
  • Figure 23 shows a mapping of a U-NPSS sequence into a signal PRB design.
  • Figure 24 illustrates a second example for U-NSSS design.
  • Figure 25 illustrates a third example for U-NSSS design.
  • Figure 26 shows a mapping of a U-NPSS sequence into time and frequency.
  • Figure 27 shows a diagram illustrating a two stage approach for synchronization
  • Figure 28 shows a diagram illustrating a three stage approach for synchronization, discovery and communication.
  • Figure 29 shows a communication terminal.
  • Figure 30 shows a flow diagram illustrating a method for initiating a communication.
  • Figure 1 shows a communication system 100, e.g. an LTE (Long Term Evolution) communication system as specified by 3GPP (Third Generation Partnership Project).
  • LTE Long Term Evolution
  • 3GPP Third Generation Partnership Project
  • the communication system 100 includes a radio access network (e.g. an E-UTRAN, Evolved UMTS (Universal Mobile Communications System) Terrestrial Radio Access Network according to LTE) 101 and a core network (e.g. an EPC, Evolved Packet Core, according LTE) 102.
  • the radio access network 101 may include base (transceiver) stations (e.g. eNodeBs, eNBs, according to LTE) 103. Each base station 103 provides radio coverage for one or more mobile radio cells 104 of the radio access network 101.
  • a mobile terminal (also referred to as UE, user equipment, or MS, mobile station) 105 located in one of the mobile radio cells 104 (in this example the leftmost radio cell 104) may communicate with the core network 102 and with other mobile terminals 105 via the base station providing coverage in (in other words operating) the mobile radio cell.
  • UE user equipment
  • MS mobile station
  • Control and user data are transmitted between a base station 103 and a mobile terminal 105 located in the mobile radio cell 104 operated by the base station 103 over the air interface 106 on the basis of a multiple access method.
  • the base stations 103 are interconnected with each other by means of a first interface 107, e.g. an X2 interface.
  • the base stations 103 are also connected by means of a second interface 108, e.g. an SI interface, to the core network, e.g. to an MME (Mobility Management Entity) 109, and a Serving Gateway (S-GW) 110.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • the MME 109 is responsible for controlling the mobility of mobile terminals located in the coverage area of E- UTRAN
  • S-GW 110 is responsible for handling the transmission of user data between mobile terminals 105 and core network 102.
  • D2D Device to Device
  • Figure 2 shows a communication arrangement 200 illustrating D2D (device-to- device) communication.
  • first mobile devices (UEs) 201 located in a coverage area 202 of an E-UTRAN are served by a base station 203 and perform uplink (UL) and downlink (DL) communication with the base station 203.
  • D2D device-to-device communication
  • a third mobile device 205 located in the coverage area 202 uses both direct communication with one of the second mobile devices 204 and also communicates with the base station 203.
  • Fourth mobile devices 206 are located outside of the coverage area 202 and use direct communication to communicate with each other.
  • D2D ProSe has been optimized for proximity scenarios targeting a maximum coupling loss of ⁇ 130dB.
  • D2D ProSe is mainly based on LTE radio access technology where the uplink spectrum and the uplink waveform is used for direct communication between the mobile devices such that D2D operates in the operator licensed spectrum.
  • D2D allows direct communication between mobile devices in scenarios where the devices are within the network coverage or outside the network coverage
  • certain specific use cases might not be optimally covered.
  • the D2D feature may not optimally cover cases when the range to be covered is sufficiently large, e.g. 2km.
  • one use case could be when a set of users are skiing in different sectors of a ski resort and would like to communicate either via voice or text messages.
  • Another example could be when users are in a highly dense environment (such as a stadium) and due to high load the network is congested. Users then might still want to communicate in a direct manner. However, in this particular scenario the operator frequency (i.e. the licensed spectrum) might be congested that there are no radio resources for D2D and hence no D2D communication (at least for normal communications - this might not be the case for public safety type of communications) between mobile devices would be possible according to D2D.
  • the operator frequency i.e. the licensed spectrum
  • Typical unlicensed bands which may be used for direct communication are the ISM band, e.g. at 900MHz in US and 800 MHz band in Europe or e.g. 800-900MHz or 2.4GHz.
  • shared bands such as TVWS (Television White Space) bands, Licensed Shared Access bands (currently defined for 2.3-2.4 GHz but may be applied to other bands as well) and Spectrum Access System bands (currently defined for 3.55-3.7 GHz but may be applied to other bands as well) may be used.
  • Figure 3 shows a table 300 summarizing the main regulatory requirements. It can be seen from table 300 that it is not possible to deploy a wide bandwidth in those frequency bands. The bandwidths span between 250 kHz and 500 kHz. Hence, D2D as typically operated in LTE band is not suitable to operate in the unlicensed spectrum.
  • 3GPP has introduced narrow bandwidth based cellular technologies specifically to serve Internet of Things (IoT)-related use cases.
  • IoT Internet of Things
  • the following cellular technologies recently standardized in 3GPP are meant to operate in licensed spectrum:
  • Cat NBl and Cat Ml are developed to maximize the coverage level (e.g. thanks to repetitions) for delay tolerant applications.
  • EDGE Enhanced Data Rates for GSM Evolution
  • D2D ProSE is complex and does not support unlicensed bands and has short range (up to 1km)
  • NB-IOT 3GPP precludes the support of voice and does not support unlicensed spectrum
  • LAA Liense Assisted access
  • MuLTEfire do not support direct communication.
  • DNB-U Direct NarrowBand communication in Unlicensed Spectrum
  • the DNB-U is for example a narrowband low-rate data transmission, e.g. with at least 2km range.
  • LTE narrowband PHY physical layer
  • LTE narrowband PHY physical layer
  • FIG. 4 shows a communication arrangement 400 illustrating DNB-U communication.
  • first mobile devices (UEs) 401 located in a coverage area 402 of an E-UTRAN are served by a base station 403 and perform uplink (UL) and downlink (DL) communication with the base station 403.
  • a second mobile device 404 which is also located in the coverage area 402, uses direct communication (D2D) in licensed band, i.e. in the band of the E-UTRAN to communicate with a third mobile device 405 located in the coverage area 402 which uses both direct communication with the second mobile devices 404 and also communicates with the base station 403.
  • D2D direct communication
  • Fourth mobile devices 406 are also located within the coverage area 402 and are moved, e.g. due to high load of the E-UTRAN, to unlicensed spectrum (as illustrated by arrow 407) and use DNB-U for communicating with each other.
  • Fifth mobile devices 408 are located outside of the coverage area 402 and use DNB-U to communicate with each other.
  • DNB-U functionality is implemented in a mobile device rendering it capable of enabling a direct communication in unlicensed bands in case of out-of-coverage, in-coverage and partial coverage and/or a highly loaded cellular network.
  • the mobile device e.g. a UE
  • the mobile device may determine to be out-of-coverage based on that its LTE modem does not detect any PLMN (Public Land Mobile Network) during frequency scan, or based on that it detects a radio link failure.
  • PLMN Public Land Mobile Network
  • the mobile device may determine to be out-of-coverage based on that its LTE modem does not detect any PLMN (Public Land Mobile Network) during frequency scan, or based on that it detects a radio link failure.
  • PLMN Public Land Mobile Network
  • the mobile device e.g. UE
  • the mobile device may be in a cellular network coverage area but it cannot access the cellular network. This can happen if
  • SIB1, SIB2 and SIB14 are SIB1, SIB2 and SIB14.
  • the device detects a roaming cellular network but its user has disabled mobile data during roaming
  • the mobile device is in a cellular network coverage area but the cellular network is congested.
  • the mobile device can detect this situation based on any of the following:
  • Blocks scheduled to UEs in the cellular network) in a radio cell in which it is located or based on any other condition
  • the detection is not limited to the above and the mobile device may use the various detection approaches in any combination.
  • the mobile device may
  • a mobile device may act as DNB-U Synch device as it is described in the following with reference to figure 5.
  • Figure 5 illustrates the functionality of a DNB-U Synch device 500.
  • the DNB-U Sync device 500 is a mobile device which is responsible for at least delivering discovery signals 502 to allow other devices 501 to synchronize and providing a direct link cell identity (D-ID) 503. How long and on which frequency it sends the discovery signals 502 depends on the used approach and is explained in further below.
  • D-ID direct link cell identity
  • the discovery signals 502 may be used for discovery and for example as well as for time and/or frequency synchronization. Alternatively, the discovery signal 502 are only for discovery of communication tiers and synchronization is done based on subsequently transmitted specific synchronization training sequences.
  • the DNB-U Sync device 500 may also share information 504 about which mobile devices are within his coverage (within some km).
  • the DNB-U Sync device 500 may share this information via multicast communication (open at least within certain groups; the forming of groups of mobile devices is described further below).
  • DNB-U Synch devices In a specific location many mobile devices can temporarily operate as DNB-U Sync devices. As such, many mobile devices may send discovery signals 502 in order to be discoverable by other devices in a specific range (details of which are given further below). In the following, an approach is described for a mobile device to choose which DNB-U Synch device to synchronize to.
  • a set of "groups" may be configured in each mobile device.
  • the groups may be either predefined by the cellular network (e.g. groups corresponding to public security) or they are defined by the users when communication with the cellular network is available (e.g. a communication with a server or cloud), e.g. in order to generate an additional group or introduce additional mobile devices into a specific group a mobile device accesses a cloud or server.
  • Each group is associated with a specific priority and this for example can be changed manually by the mobile device's user up to a certain extent (e.g. public security has always highest priority and cannot be modified).
  • a hierarchy of groups i.e., terminals of a lower hierarchy group may only access their own group (type) while terminals of a higher hierarchy group may access to more groups.
  • priority groups are (in order of descending priority)
  • Priority Group 2 mobile devices with best reception quality (e.g. highest RSRP
  • Private priority group 3 preferred set of devices (from list of contacts, friends)
  • a mobile device only initiates direct communication with another mobile device of a communication group if there is no mobile device of a priority group with a higher priority with which the mobile device is to communicate.
  • a mobile device may define further priority groups and any order of the above mentioned priority groups can be considered (e.g. up to a certain extent). Many private priority groups can be created, and the priority associated to this can be manually changed according to the needs.
  • private groups can correspond to one or more devices which would cover unicast and multicast communications.
  • a reselection may take place if the e.g. a timer associated to the DNB-U Sync device expires, if the DNB-U Sync device does not have any active communication, if it becomes out of coverage (RSRP of the DNB-U synch device is lower than a certain threshold), or if another DNB-U sync device appears that belongs to a higher priority group than the current one.
  • a timer associated to the DNB-U Sync device expires, if the DNB-U Sync device does not have any active communication, if it becomes out of coverage (RSRP of the DNB-U synch device is lower than a certain threshold), or if another DNB-U sync device appears that belongs to a higher priority group than the current one.
  • the mobile device may become discoverable for other mobile devices supporting DNB-U in a certain range and the mobile device may try to discover other mobile devices which might be communicating already.
  • the user can (manually or
  • the above mentioned location for the synchronization signal (middle chunk) is only provided as example and other locations may be used. However, in order to simplify the implementation a specific location may be
  • the DNB-U Sync min set is the minimum set of information the DNB-U Sync device 500 sends in order for other mobile devices to synchronize.
  • the DNB-U Sync min set for example includes at least a DNBU-Primary Synchronization Sequence, a DNBU- Secondary Synchronization Sequence, and may include other information such as user ID, priority group related information, reference signals and possibly any other broadcast information. Broadcast information may include also additional services the particular device can offer like e.g. printing capability, internet access, or relay functionality.
  • D e.g. in milliseconds
  • the corresponding configuration may be predefined.
  • DNB-U Discovery Frequencies in the following an approach based on a Primary DNB-U Sync Frequency (Fp) and one or more Secondary DNB-U Sync Frequencies FQ,
  • a first possibility is the configuration of a single Secondary DNB-U Sync frequency.
  • a multitude of secondary DNB-U Sync frequencies can be configured.
  • Both the Primary DNB-U Sync frequency and the Secondary DNB-U Sync frequency are frequencies that a mobile device may use in order to transmit/receive synchronization signals to make itself discoverable and to discover the presence of other mobile devices.
  • the mobile device may also use those two (or more) frequencies in different conditions.
  • two exemplary approaches for the discovery of other mobile devices and becoming discoverable are given.
  • the DNB-U Sync device 500 does not send periodic discovery/synchronization signals but stops transmitting if there is not an active communication or if no mobile device enters the proximity of the DNB-U Sync device 500 for a maximum duration (e.g. until a timer expires).
  • the case is considered that when a first mobile device activates DNB- U in a location where no other mobile devices are communicating or sending synchronization signals. After enabling DNB-U, the first mobile device senses the spectrum (listens for the frequency where synchronization signals should be sent, e.g. FA, F b and possibly further frequencies) by applying an equivalent of a Listen Before Talk protocol to detect whether other mobile devices are already transmitting synchronization signals or whether other
  • the mobile device A starts sending the DNB-U Sync min set within a certain DNB-U sync window on frequency FA.
  • the DNB-U sync window may be predefined and less than the Dwell Time (according to respective regulatory requirements) and less than the duty cycle (according to respective regulatory requirements).
  • the design of the synchronization sequence may for example be chosen to achieve at least approximately 2km range in typical use cases.
  • a second mobile device located in the vicinity after sensing the frequency F A can synchronize with the first mobile device which becomes a DNB-U Sync device. After this synchronization procedure the first mobile device and the second mobile device can
  • the DNB-U Sync device keeps sending the DNB-U Sync min set periodically to allow other mobile devices to synchronize, however in order to free frequency FA for other mobile devices, the first mobile device may use a the secondary frequency F B to keep sending synchronization signals.
  • the first mobile device maintains this for a maximum timing T max after the end of the direct communication which takes place according to a specific frequency hopping pattern whenever it is needed (e.g. in 900MHz frequency band).
  • T max elapses the DNB-U Sync device stops sending the DNB-U min set and enters sleep mode.
  • the first mobile device may not be capable to detect the presence of later (synchronization) signals from other mobile devices unless it wakes up periodically to scan the specific frequency where synchronization signals should be sent (F A and F B etc). Several options can be considered.
  • a mobile device wakes up with a certain periodicity and it tries to detect the presence of synchronization signals.
  • the mobile device has a particular architecture such that only specific components of the mobile device are waked up to detect the presence of synchronization signals to limit power consumptions.
  • the mobile device is equipped with a specific wake up receiver which could detect the presence of synchronization signals and in response wake up the mobile device's (regular) receiver.
  • This wake up receiver could e.g. detect the level of energy and the presence of a specific signature characteristic of the synchronization signal design.
  • the wake up receiver would be capable of waking up the mobile device's receiver only when needed and hence it would allow for battery consumption reduction.
  • a mobile device keeps sending periodic discovery (i.e. synchronization) signals by adapting the periodicity to reduce battery consumption if there is not an active communication or if no other mobile device enters the proximity region for a maximum timer.
  • periodic discovery i.e. synchronization
  • a first mobile device if a first mobile device enables DNB-U in a location where there are no other mobile devices it senses the spectrum (e.g. according to a Listen Before Talk procedure). Whenever possible the first mobile device starts the transmission of the DNB-U Sync min set with a certain Sync window and a certain periodicity.
  • the conditions on the parameters needs to be respected as above.
  • a second mobile device When a second mobile device enters the direct communication network (i.e. the area in which the first mobile device transmits the discovery signals), after sensing the direct communication network, it is able to synchronize to the first mobile device (acting as the master device of the direct communication network).
  • each mobile device for example only acts as sync device for a limited amount of time (e.g. until a corresponding timer in the mobile device has expired).
  • FIG. 6 shows a communication arrangement 600.
  • the communication arrangement 600 includes seven mobile devices 601 to 607 (referred to as devices A, B, C, M, N, X and Y).
  • the first mobile device 601 acts as DNB-U Sync device and the mobile devices B, C, X, and Y are synchronized to the DNB-U Sync device A.
  • device B wants to communicate with device C which are within the (direct communication) coverage area of the DNB-U Sync device A.
  • Device B may be aware of the reachability of device C because the DNB-U Sync device A has shared information (in a specific group) about which users are active (e.g. synchronized) within its coverage area 608.
  • device Y may want to communicate with other devices which are not known in the list of the devices synchronized to device A (not in coverage 608 of device A), such as device M and device N.
  • devices which are not known in the list of the devices synchronized to device A (not in coverage 608 of device A), such as device M and device N.
  • device M and device N For example, on radio layer, only mobile devices with unicast direct links are known to the sync device A.
  • Device X and Y are not known to device A as long as they are only listening to multi-cast data sent by device A.
  • a single arrow indicates a multi-cast connection and a double arrow line indicates a unicast connection.
  • any DNB-U device can become a Sync device.
  • communication links may be provided between the mobile devices 601 to 607 using different sync devices.
  • first links 609 are provided using device A as sync device
  • second links 610 are provided using device B as sync device
  • third links 611 are provided using device Y as sync device.
  • a DNB-U Sync device can serve either as the only synchronization source for all mobile devices in its coverage or a multitude of Sync devices can be present.
  • a synchronization timer allows that any communication between, for example, devices B and A and between the devices C and A is completed before devices B and C start their own synchronization procedure according one of the following ways:
  • the DNB-U Sync device A knows the coarse location of other mobile devices (sector based) and informs device B and device C to establish a direct communication. In this case the devices B and C release the synchronization to device A and device B (or C) starts sending DNB-U min set after listening for clean spectrum.
  • the Sync device (Device A) does not have (coarse) positioning information, it asks devices B and C to start a direct communication. In case devices B and C are not in coverage range the synchronization procedure fails and devices B and C are not able to communicate because of out of coverage.
  • the sync DNB-U device A acts as a relay of information and thus extends the coverage if the device to which the information is to be transmitted intended is within the coverage range 608 of device 8. However, this mode of operation leads to an increased power consumption in the sync device A.
  • each device is capable of supporting dual connectivity when it has activated DNB-U.
  • dual connectivity of a mobile device including one connection to a sync device and connection towards another mobile device with which the mobile device wants to communicate is possible.
  • this approach leads to an increased battery consumption in the mobile device.
  • Discovery Use Case 1 A UE out of cellular coverage would like to get alerted as soon as a specific UE or at least one member of a specific group is within proximity.
  • Discovery Use Case 2 A UE out of cellular coverage would like to discover other UEs within proximity e.g. for the purpose of a subsequent private direct communication.
  • ProSe Direct Discovery can be "open” or "restricted". Open is the case where there is no explicit permission needed from the UE being discovered, whereas restricted discovery only takes place with explicit permission from the UE that is being discovered.
  • ProSe defines two Models of discovery:
  • Announcing UE The UE announces certain information that could be used by UEs in proximity that have permission to discover.
  • Monitoring UE The UE that monitors certain information of interest in proximity of announcing UEs.
  • Discoverer UE The UE transmits a request containing certain information about what it is interested to discover.
  • ProSe Public Safety always uses restricted discovery. In ProSe Public Safety
  • Relay Discovery is supported via relay (a UE) that is connected to E-UTRAN and Group Member Discovery is defined within a group of UEs (Discovery Group ID). ProSe Public Safety Discovery messages are protected. Each ProSe-enabled Public Safety UE needs to obtain the security parameters from the ProSe Key Management Function before participating in ProSe direct discovery for public safety as shown in Figure 7.
  • Figure 7 shows a message flow diagram 700 illustrating a message flow according to 3GPP ProSe Discovery.
  • the message flow takes place between a UE 701, a ProSe Function (or multiple ProSe Function(s)) 702 and a PKMF (ProSe Key Management Function) 703. [0080] In 704, the UE 701 is configured.
  • the UE 701 gets provisioned discovery parameters plus a PKMF address.
  • the UE 701 requests a key from the PKMF 703.
  • the PKMF 703 checks the UE's authorization.
  • the PKMF 703 sends a key response to the UE 701.
  • the PKMF 703 sends a MIKEY (Multimedia Internet Keying) message to the PKMF 703
  • the UE 701 sends a MIKEY verification message to the PKMF 703.
  • the UE 701 is ready to send and receive a discovery message.
  • PKMF Management Function
  • PSDK Public Safety Discovery Key
  • DUCK Disovery User Confidentiality Key
  • ProSe Public Safety Group Member Discovery assumes several parameters preconfigured in the UE like:
  • a two stage discovery procedure and dynamic group creation for a device to device type of communication in out-of-coverage areas is introduced.
  • the first stage of the discovery only the minimum information is shared between two mobile terminals (e.g. UEs) to start communication without the sharing user ID.
  • mutual authentication of the two mobile terminals is carried out including User ID and (e.g. all) group related credentials necessary for the group communication.
  • This two-stage discovery approach enables discovery of any type of devices and it is not limited to public safety communication only and it protects confidentially of users participating in the discovery procedure.
  • 3GPP ProSe defines discovery for in-coverage and out-of- coverage public safety only (no discovery procedure is defined for out-of-coverage consumer use cases in 3GPP ProSe).
  • Figure 8 shows a message flow diagram 800 illustrating an example of a two-stage discovery procedure in out-of-coverage scenario for a general consumer.
  • the message flow takes place between a first UE (UE A) 801 and a second UE (UE B) 802.
  • the UEs 801, 802 perform a basic discovery using an anonymized short form of the User ID. This may be seen as the first stage of the discovery procedure.
  • the UEs 801, 802 perform authentication based on identity based cryptography or digital certificates.
  • the UEs 801, 802 exchange group credentials.804 and 805 can be seen as the second stage of the discovery procedure. [0099] In 806, the UEs 801, 802 switch to group communication.
  • the UE is configured with basic parameters to enable secure discovery. Parameters such as private keys, associated certificates or root certificate that may be needed for contacting other UEs in the same scenario are for example preconfigured in the UE and exchanged in this first stage. If Identity Based Cryptography is used for mutual authentication when UEs are out of network coverage, the UE is provisioned with a user identity and the following set of parameters defined by the IETF (Internet Engineering Task Force), for example:
  • a precondition is that a pre-affiliation of the UE's user is known (e.g. a set of communication terminals with which the user has previously communicated) which can be for example determined based for example on the contact list in the address book. Based on this user pre-affiliation, the UE may dynamically create a group (or multiple groups) when the UE is out of coverage. For example, two types of group organization can be supported:
  • Group Type A Distributed group with no leader, everybody can pull in (e.g. invite) a new group member
  • Group Type B Controlled group with a group administrator
  • Group Type A For Group Type A, in 801, a basic discovery using hashed User IDs (e.g. SIP URI, telephone number, app-layer identifier in the user@realm format, etc.) or the last 4 digits MSISDN/User ID is performed.
  • Each UE 801, 802 may start a discovery procedure by announcing e.g. a hashed value of its User ID and its DNB-U 2 ID or the last 4 digits of its MSISDN/User ID and its DNB-U 2 ID.
  • UE A the first UE 801 starts the discovery procedure.
  • the second UE (UE B) 802 receives the announcement of the first UE 801 and determines whether the hashed code matches the hashed value of UE A's User ID that is stored in UE B's address book or that the advertised last 4 digits matches the last 4 digits of UE A's MSISDN/User ID that is stored in UE B's address book. Based on this, UE B initiates a 1-to-l Direct Communication with UE A. As part of the secure 1-to-l link establishment the two UEs 801, 802 authenticate mutually by using Identity Based
  • Group Credential Exchanges are performed.
  • one of the two UEs 801, 802 creates a new group, which implies creation of group information such as Group ID, Group IP multicast address, Group Key and group security credential.
  • a UE that creates the group delivers the group parameters to another UE.
  • one of the UEs may already be member of a group, in which case it simply provides the group parameters of the existing group to the other UE (with which a group should be formed).
  • the UE that was provided with the group parameters stores those data for future direct group communication.
  • the UEs 801, 802 switch to group communication: At any point the two UEs may release the 1-to-l link and switch to direct group communication using the group information.
  • Group Type B i.e. group with a group administrator
  • the discovery procedure for Group Type A as described above can be followed, but for example with the following changes: • UEs configure search for the hashed User ID or the last 4 digits of the MSIDN of the group admin only.
  • Model A (Announcing / Monitoring) or Model B (Discoverer/ Discoveree)
  • the Solicitation message includes two hashed identities: a hashed value of Discoverer's User ID and for a hashed value of the Target's User ID (i.e. in this case the hashed value of group administrator's User ID).
  • the group administrator's UE determines that it can accept the request (e.g. because the hashed value of Discoverer's User ID matches an entry in his address book) and sends a Response message to the other UE.
  • the other UE can initiate establishment of 1-to-l link, during which the two UEs (administrator's UE and other UE) mutually authenticate.
  • the last 4 digits of the MSIDN can be included in Solicitation message.
  • the discovery procedure described above enables a dynamical group principle, i.e. one user is not restricted to a static one group only.
  • a discovery flow for a distributed group may for example be as follows:
  • this can be done over the Discovery plane (D-plane) or the Communication plane (C-plane). If done via C-plane, there is a need to define a DNB-U L2 ID that is understood by everyone as broadcast identifier (in contrast, the D-plane does not use any addresses, so everything sent in the D-plane is broadcast).
  • D-plane Discovery plane
  • C-plane Communication plane
  • the two users having performed the mutual authentication decide to create a group using app-layer means (e.g. similar to creating a chat room in an instant message service). Black-list users may be blocked automatically. Some users might be added automatically with no choice of not being added, e.g. family members.
  • the creation of a group implies creation of: Group ID, multicast DNB-U L2 (layer 2) ID, multicast IP address and associated group security credential.
  • the two users can stop their 1-to-l communication and instead continue to communicate with each other using DNB-U group communication.
  • Both UEs may in parallel continue to advertise their hash key to attract additional users g)
  • an additional user e.g. a user C
  • detects either of the other two users one of e.g. users A and B
  • it establishes a 1-to-l link with user A or user B
  • user A or user B can pull user C inside the group by simply providing the group parameters (Group ID, L2 ID, IP address, security credential) to user C's UE.
  • a black-list may be synchronized between the users to avoid undesired users in the group, e.g. if user A blacklisted user C and user B wants to add user C or user C blacklisted user A and user B wants to add user C.
  • the UE of user C can release the 1-to-l link and join the group using DNB-U group communication.
  • One of the first procedure that a UE has to perform in order to connect to a DNB-U network is the synchronization.
  • Synchronization Use Case 1 A given UE enables the DNB-U feature and wants to transmit data to a group and it does not receive any synchronization timing.
  • Synchronization Use Case 2 A given UE enables the DNB-U feature and wants to transmit data to a group and it does receive at least one synchronization signal after scanning a set of anchor frequency/frequencies.
  • Synchronization Use Case 3 A given UE enables the DNB-U feature and it does receive multiple synchronization signals after scanning a set of anchor frequencies.
  • D2D the following synchronization procedure is considered according to 3GPP: In case of out of coverage a UE first needs to listen to a predefined frequency where synchronization sequences are transmitted in D2D. In order to perform this search the UE tries to cross-correlate a received sequence with a set of known Secondary Sidelink Synchronization Sequences (SLSS) which depend on a SideLink ID (SLSS ID).
  • SLSS Secondary Sidelink Synchronization Sequences
  • the SLSS ID is in the range from 0 to 335 and is divided into two sets:
  • the device When the device (i.e. the UE) finds a synchronization source it gets its timing and frequency and is then able to demodulate the Master Information Block (MIB) sent by the synchronization source.
  • MIB Master Information Block
  • the device uses a Sidelink Reference Signal Received Power (S-RSRP) applying L3 (layer 3) filtering with preconfigured filter coefficients.
  • S-RSRP is measured on Demodulation Reference Signals (DMRS) which are embedded in the synchronization subframe.
  • DMRS Demodulation Reference Signals
  • the possible synchronization sources for a UE are those for which the S-RSRP is above a certain preconfigured threshold and the UE selects them according to a priority (first those who are in coverage, then those who are linked to a UE which is in coverage and then the rest).
  • the UE transmits itself the synchronization sequences (same primary and secondary synchronization sequences with potentially a difference SLSS ID and a different content for the MIB - the UE may use different subframes to transmit synchronization sequences compared to the synchronization source).
  • the UE In case the UE has not found any synchronization source with S-RSRP above the predefined threshold it starts transmitting its own synchronization sequences and MIB in a preconfigured subframe.
  • the synchronization source selection is based on the S-RSRP based on the DM-RS.
  • a frequency hopping framework is described considering regional regulatory requirements in the unlicensed spectrum.
  • a single UE is elected as the synchronization source.
  • the UE can decide to stop being a synchronization source (manually or automatically in a semi static manner or in a dynamic manner).
  • Another UE synchronized to the synchronization source uses the rx (receive) timing and frequency to transmit its data to one or more UEs assuming that the one or more UEs are synchronized to the same user.
  • Option 2 Single synchronization source and multiple secondary synchronization source a. According to certain rules a single UE is elected as synchronization source.
  • the UE can decide to stop being a synchronization source (manually (e.g. based on user input) or automatically in a semi static manner or in a dynamic manner).
  • Another UE synchronized to the synchronization source uses the rx (receive) timing and frequency to transmit its data and sends synchronization units as well according to certain rules. The rules to choose whether the synchronization signals have to be transmitted is different and the subframes where to transmit the synchronization sequences are different from option 1.
  • Option 1 can be seen to be simpler as it creates less interference but it has the drawback that at the cell boundaries the direct communication with neighbor users might be limited as UEs are synchronized to different synch sources.
  • Option 2 can be seen to be similar to the D2D procedure but it is optimized in order to take into account specific problems related to large amount of cell reselection and ping pong effect and to limit the propagation of the time and frequency error that has to be handled by the device in order to properly synchronize.
  • Synchronization Unit (SU) which consists of certain amount of repetitions of
  • U-PBCH Unlicensed Physical Broadcast Channel
  • Synchronization Burst contains also some OFDM symbols for reference symbols.
  • the frequency hopping could be very rapid (as shown in figure 9) or very slow depending on the regional regulations.
  • Figure 9 shows a signal diagram 900 illustrating a frequency hopping pattern for synchronization signal transmission.
  • a set of frequencies N is defined to be used for synchronization: for example if fn, ---f
  • the hopping pattern could be • At time n, select frequency f
  • a new frequency following the frequency hopping pattern is selected every e.g. 10ms in case a rapid frequency hopping pattern is required or e.g. some minutes in case a slow frequency hopping pattern is required.
  • Synchronization Use Case 1 A given UE enables DNB-U feature and wants to transmit data to a group and it does not receive any synchronization timing
  • Figure 10 illustrates a synchronization procedure
  • a communication arrangement having four UEs 1001, 1002, 1003, 1004 (denoted as UEA to UEQ) is shown in figure 10 wherein a left-hand side representation of the
  • the communication arrangement illustrates the first stage of the synchronization procedure and the right-hand side representation of the communication arrangement illustrates the second stage of the synchronization procedure.
  • a UE scans the N anchor frequencies to try to synchronize: • For example, the device UE ⁇ 1001 scans each of the N frequencies for a time T svnc hf for each frequency (total time to search T svnc hf*N + T rnc j)
  • T rnc j is a UE specific timer that each UE would select randomly within a certain range ⁇ ° / T rndmax) which would limit collision.
  • UE ⁇ selects a predefined frequency to start transmitting the synchronization sequences or it will select randomly the frequency belonging to the set of allowed frequencies for synchronization autonomously based on e.g. the frequency for which the lowest received power level is detected.
  • Synchronization sequences are sent for a certain period before data transmission start (for a period p re . S y nc h) at least until UE ⁇ needs to transmit data (for a period ⁇ 3 3 ⁇ 4- 3 ) plus a preconfigured timer ⁇ 3( ⁇ that is used to limit cell reselections.
  • the timer ⁇ 3( ⁇ is defined and take a preconfigured set of values that the UE can select autonomously ( ⁇ includes at least the value 0ms)
  • the device has the possibility to further extend the timer according to a certain principle or stop transmitting synchronization sequence.
  • the principle based on which the device keeps transmitting synchronization sequences could be based on battery status, whether active communication is ongoing, based on the amount of users in the group, RSRP level of the LTE network or any combination of the above. If a device does not want to transmit data it does not send synchronization sequences. This may be important to ensure that battery of elected synchronization source is not drained.
  • the following metrics can be used to determine whether a device scanning the frequencies can decide to stop scanning and start stage 2.
  • Synchronization Use Case 2 A given UE enables DNB-U feature and wants to transmit data to a group and it does receive at least one synchronization signal after scanning the set of anchor frequency/frequencies.
  • Figure 11 illustrates a synchronization procedure according to a first option for Use Case 2.
  • a communication arrangement having eight UEs 1101-1108 (denoted as UE ⁇ to UE
  • a UE starts transmitting using the DL timing acquired via synchronization to the available Synch (synchronization) source (UE ⁇ and UEp_ in this example).
  • a drawback is that UEs synchronized to different Sync sources (i.e. Sync devices) are not able to communicate with each other even in near proximity as indicated by the cross 1109 in figure 11: UEp is not able to communicate to UEr Eventually communication will be possible when
  • UEQ (or UEp) becomes a Synch source.
  • Figure 12 illustrates a synchronization procedure according to a second option for Use Case 2.
  • a communication arrangement having four UEs 1201-1204 (denoted as UE ⁇ to UEp) is shown in figure 12.
  • UEp is synchronized to UE ⁇ . If UEp wants to transmit data it will start propagating UE ⁇ timing via the transmission of its synchronization sequences if certain conditions are respected, i.e. UEp becomes a secondary Synch source.
  • the conditions could be linked to the RSRP level of the received synchronization burst, i.e. at low RSRP time propagation is needed (cell edge conditions) at high RSRP one could assume that devices in the proximity could also receive the synchronization burst from UE .
  • UEp reuses the same frequencies and the same synchronization burst content, but the Cell ID used for the U-NSSS is different and the content of the Master Information Block carried by the U-PBCH is different compared to UE ⁇ (as it would carry information related to subframe and frame where the U-PBCH starts). It selects a subframe to transmit the synchronization sequences depending on offsets.
  • a preconfigured offset for example depends on the periodicity at which the synchronization burst is set, e.g.
  • Synchronization sequences are sent according to the same principle as defined for Use Case 1. UE ⁇ and ⁇ will not recognize two different synchronization sources but only one after detection of U-NSSS and MIB.
  • Synchronization Use Case 3 A given UE enables the DNB-U feature and it does receive multiple synchronization signal after scanning the set of anchor frequencies
  • Figure 13 illustrates a synchronization procedure according to a first option for Use Case 3.
  • a communication arrangement having eight UEs 1301-1308 (denoted as UE ⁇ to UE
  • UEp detects the presence of multiple synchronization sources and it decides whether to synchronize to UEp timing or if it keeps synchronization with UEp_.
  • Decision metrics can be RSRP, frame number, priority, etc.
  • Figure 14 illustrates a synchronization procedure according to a second option for Use Case 3.
  • a communication arrangement having eight UEs 1401-1408 (denoted as UE ⁇ to UE
  • UEp starts propagating the UEp_ timing.
  • UEp detects the presence of multiple synchronization sources and decides whether to synchronize to UEp timing or if it keeps synchronization with UE .
  • Decision metrics can be RSRP, frame number, hop number limitation (via MIB or via cell ID), priority, etc. After deciding which synchronization source to follow it will start propagating the chosen timing. Eventually a single timing could be established.
  • the 3GPP ProSe D2D synchronization procedure is defined for licensed band only, i.e. even if a UE is out of coverage it means that it is not under the coverage of the cell but still operating in licensed band. As such this procedure cannot be directly applied to unlicensed spectrum.
  • the synchronization sequences are located in a specific symbol and there is no need for frequency hopping mechanisms. In the unlicensed spectrum there is the need to have a more or less dynamic frequency hopping pattern.
  • a UE may listen to the spectrum to detect the presence of synchronization sources and then decide whether to become a synchronization source itself.
  • Different metrics may be used to decide whether to become a synchronization source. This may include timers that are used to indicate how long a device is going to be a synchronization source (plus possible extensions).
  • the above-mentioned modification of the MIB content allows informing the other users about the expiration of the timer. This allows reducing the power consumption of a UE which becomes a synchronization source.
  • a timing propagation may be used to create a large synchronization area as one option. It is not required to differentiate between out of coverage and in coverage UEs to handle priority. It should be noted that in 3GPP D2D the synchronization source selection is based on the S-RSRP based on the DM-RS. This is typically undesirable for the D2D synchronization in unlicensed band because it would potentially introduce a ping pong effect. The choice to always re-transmit synchronization sequences might introduce too much interference and potentially also a large amount of cell reselection.
  • LP-WAN low-power wide area networking
  • NarrowBand-IOT which is a new non backward compatible radio access technology which is specifically optimized in order to satisfy the requirements required for typical IoT solutions.
  • Licensed spectrum is in general used in order to deploy services which requires a certain QoS, especially in terms of latency.
  • IoT can be considered to be a delay tolerant service.
  • the requirement is that the latency should be below 10s compared to approximately hundreds of milliseconds in case of normal LTE services.
  • Operators might hence reserve the licensed spectrum to deploy normal mobile broadband type of service and might need to use unlicensed spectrum for delay tolerant services such as IoT.
  • a design of synchronization sequences is described to operate in the case of unlicensed spectrum below lGHz with the constraint of 200KHz bandwidth.
  • a synchronization signal structure for NB-IOT is provided which is designed to support compatibility with in-band deployments where legacy LTE signals are present. This means that many resources are not completely exploited for standalone only type of deployment in order to improve the time and frequency acquisition timing or reduce the complexity.
  • considering the use of these synchronization sequences in a direct link type of connection robustness with respect to large frequency errors and timing errors has to be considered.
  • Cell ID handling A way to inform the users synchronizing to a device whether this user is the synchronization source or the n-th secondary synchronization source is given. Two options are described in order to carry the Cell ID information.
  • Synchronization Unit contains at least the following:
  • U-PBCH Unlicensed -Physical Broadcast Channel information (which might include in the same subframe some symbols for reference signals).
  • a certain periodicity P for the Synchronization Unit (SU) of length W (e.g. in milliseconds) is introduced.
  • Each SU is composed by a certain amount of instances (time units) of the primary synchronization sequence, secondary synchronization sequences and broadcast channel (which includes also some symbols of reference signals in order to have coherent demodulation).
  • the number of instances of the above mentioned channel is a design parameter and may be chosen depending on the regulatory constraints (in order for example to fulfill 10% duty cycle in Europe in a specific band or 400ms maximum dwell time in USA etc.).
  • Two examples of the framework are shown in figures 15 and 16 depending on the relative position of the channels in time domain.
  • Figure 15 shows a signal diagram 1500 illustrating a first example of a
  • a synchronization unit 1501 with a length of W milliseconds is periodically transmitted with a periodicity P.
  • the synchronization unit 1501 includes multiple blocks 1502, wherein each block includes N
  • Each channel i.e. the transmission of each of U-NSSS, U-NPSS and U-PBCH, occupies all the frequency resources.
  • Figure 16 shows a signal diagram 1600 illustrating a second example of a synchronization framework.
  • the second example illustrated in figure 16 is similar to the first example illustrated in figure 15, except that in the blocks 1602 of the synchronization unit 1601 U-NPSS is transmitted before U-NSSS.
  • Table 1 gives examples of the choice of N
  • table 1 could be applicable in USA when a maximum on time for a particular frequency chunk is possible.
  • NU-NPBCH 1, NU-NSSS: 1, NU-NPSS: 1, W: 1 SU, P: 80ms
  • a certain amount of time units may be reserved in order to do carrier sensing at the beginning of the SU window as illustrated in figure 15 and 16.
  • Figure 17 shows an NPSS sequence 1700 in NB-IOT.
  • the NPSS sequence is defined as a length 11 sequence repeated over 11 OFDM symbols (indicated from left to right in a communication resource block 1701, wherein each OFDM symbol corresponds to a column of the resource block 1701) with a particular cover code that is used in order to have better frequency error estimation.
  • Each square of the communication resource block 1701 (and similarly of the other communication resource blocks shown in the following figures) corresponds to a resource element such that each column of resource elements corresponds to an OFDM symbol.
  • FIG. 18 shows a U-NPSS structure 1800 according to a first example (which can be seen as an extension with respect to figure 17).
  • the U-NPSS structure 1800 includes 14 OFDM symbols numbered from 0 to 13 illustrated in the form of a communication resource block 1801. The first three OFDM symbols (the first three columns of the communication resource block 1801) are filled with NPSS sequences.
  • An extension of the cover code is provided. Any type of cover code can be used as it can be shown that performance is not sensitive to the specific cover code. In this example a specific cover code is used as shown in figure 18 but this can be generalized to any cover code.
  • a receiver algorithm based on sliding autocorrelation can be used with coherent or noncoherent combining. Coherent combining achieves better performance. Coherent weighted combining can be used by deriving coefficients with the following formula:
  • Figure 19 shows an NSSS sequence 1900 in NB-IOT (according to 3GPP Rel-13). Similarly to figure 19, the NSSS sequence 1900 is illustrated as a communication resource block 1901.
  • the U-NPSS sequence exploits the extra symbols available in the subframe normally used by NSSS in order to increase the amount of repetitions. This is shown in figure 20 (normal cyclic prefix (CP)).
  • CP normal cyclic prefix
  • Figure 20 shows a U-NPSS structure 2000 according to a second example.
  • the indicated subframe shown as communication resource block 2001, is the one normally used by NSSS.
  • Figure 20 shows which subframes are used by U-NSSS and which one by U-NPSS.
  • FIG. 21 shows diagrams 2101, 2102, each showing time to acquire 90% probability of detection depending on SNR illustrating the performance that can be achieved by the U-NPSS of the first example.
  • Each diagram 2101, 2102 shows four curves, wherein the lowest curve corresponds to usage of the NPSS (legacy design) with 4 lags, the second to lowest curve to the usage of NPSS (legacy design) with 6 lags, the third to lowest curve to the usage of U-NPSS according to the first example with 4 lags and the top curve to top curve to the usage of U-NPSS according to the first example with 6 lags, wherein the left diagram 2101 shows the performance for coherent combining and the right diagram 2102 shows the performance for incoherent combining.
  • Figure 22 shows the synchronization sequence of in a legacy D2D system.
  • Time increases from left to right along a time axis 2201 and frequency increases from bottom to top along a frequency axis 2202.
  • a U-NPSS structure As a third example for a U-NPSS structure the following can be considered: Use of a length-48, or length-60 (wherein length is given in REs (resource elements)) Zadoff-Chu sequence (length 49, 61 in case of extended CP, and 61 or 85 for normal CP rather than length 63 in D2D system) repeated at least twice in a subframe. This scheme allows for larger reliability than shorter sequences (length-11 sequence). However, sliding autocorrelation receivers cannot be used (only cross-correlation -similar to legacy LTE can be used).
  • Figure 23 shows a mapping of a U-NPSS sequence into a signal PRB (physical resource block) design according to the third example into time and frequency for length 61 (left diagram 2301) and length 49 (right diagram 2302). The mapping is to be considered first in frequency and then in time. Other mappings could be also considered. Again, each square represents a resource element and each column of squares an OFDM symbol. [00212] In figure 23 the possibility to map DM-RS (demodulation reference signal) into the last two symbols is also shown in the right diagram 2302. This could be particularly beneficial when N-PBCH is located after the U-NPSS. Each repetition could be scrambled in a different way to limit the crosscorrelation between the sequences.
  • PRB physical resource block
  • U-NSSS design As first example of the U-NSSS design, the same design for U-NSSS as for legacy NSSS may be kept and the first three symbols may be used for symbols for U-NPSS sequences or alternatively use U-NPSS (see figure 20).
  • Figure 24 illustrates a second example for U-NSSS design 2400.
  • a long sequence may be defined for U-NSSS (normal cyclic prefix CP).
  • the U-NSSS sequence is designed according to a length-167 ZC sequence
  • Figure 25 illustrates a third example for U-NSSS design (normal CP) 2500, again in the form of a communication resource block 2501.
  • the length-35 ZC sequence is used to convey information about the V parameter, where q is encoded in 32 size Hadamard scrambling sequence: nun'(n'+ ⁇ )
  • d ⁇ n) bbq (m)e 35 where u is a root different from the roots that could be used by the length 131 sequence and bbq(m) corresponds to the one Hadamard sequence of size 32.
  • u is a root different from the roots that could be used by the length 131 sequence and bbq(m) corresponds to the one Hadamard sequence of size 32.
  • Hadamard sequences are used. Any four length 32 Hadamard sequences could be considered.
  • the length-35 ZC sequence carries information about parameter and this is encoded via the use of different roots ' ⁇ ': nhn' ⁇ n'+ ⁇ )
  • the possible roots that could be used without colliding with the length 131 sequence are 0, 1, 2, 129 and 130. Any combination of four roots among those values may be considered. It can be shown via simulations that depending on different residual frequency offset after U-NPSS detection, target SNR and target complexity different methods for U-NSSS might be more beneficial.
  • the U-NSSS is extended from the D2D design (similar to legacy LTE design) as an interleaved concatenation of two length-N/2 binary sequences without DFT (Discrete Fourier Transform) precoding (same sequences as for LTE) scrambled via a binary sequence that depends on the Side Link ID.
  • Figure 26 shows a mapping of a U-NPSS sequence according to the fourth example into time and frequency for length 60 (left diagram 2601) and length 48 (right diagram 2602). The mapping is to be considered first in frequency and then in time. As in figure 22, each square represents a resource element and each column of squares an OFDM symbol.
  • Each repetition may be scrambled in a different way to limit the cross-correlation between the sequences.
  • Spare symbols can be used for reference signals which are particularly useful if U-NSSS is located before the U-PBCH.
  • a subcarrier spacing of 15KHz may be considered as in legacy LTE to avoid high sensitivity to frequency error.
  • the cell ID is determined depending on the number of synchronization propagation hops. As described above synchronization propagation hops may be used: a device (UE) could be the synchronization source or it can be a secondary synchronization source (i.e. it is propagating the timing of another user).
  • a device UE
  • a secondary synchronization source i.e. it is propagating the timing of another user.
  • synchronization sources and forwards it (which is referred to as a hop).
  • a hop In case the device is a (primary) synchronization source it selects a cell ID in the range
  • M corresponds to the maximum cell ID (e.g. 336 or 504), K is the amount of hops that are allowed and n is the range index.
  • the U-NSSS sequence design carries only information about a single range.
  • FCC FCC introduces specific regulations that have to be followed depending on which type of device the system complies with. Following options are possible:
  • the systems with less than 250 KHz 20dB bandwidth will have to hop over 50 channels and can transmit with up to 36dBm eirp (equivalent isotropic radiated power) including the antenna gain (up to 30dB maximum output power).
  • the dwell time in this case is 400ms/20s and all the frequencies have to be used in average the same amount of time,
  • 500KHz will have to hop over more than 25 channels and can transmit with up to 30dBm eirp including the antenna gain (up to 24dB maximum output power).
  • the dwell time in this case is 400ms/10s and all the frequencies have to be used in average the same amount of time.
  • DTS Digital Modulations
  • PSD Power Spectral Density
  • Hybrid type of system where the device has to comply with the power density standard of 8 dBm in any 3 kHz band when the frequency hopping function is turned off. The transmission also must comply with a 0.4 second/channel maximum dwell time when the hopping function is turned on. There is no requirement for this type of hybrid system to comply with the 500 kHz minimum bandwidth normally associated with a DTS transmission; and, there is no minimum number of hopping channels associated with this type of hybrid system.
  • synchronization long is the dwell time requirement. This requires the synchronization procedure to hop over different frequencies in order to be able to transmit for a longer time.
  • the handling of the frequency hopping would require either a long period to sense the network to be able to synchronize or higher complexity in the device in order to support the possibility to receive the signal over a larger bandwidth (e.g. 5 times the narrowband over which the system is based) and then down-convert in a different manner each 180KHz chunk in order to process the different portion of the synchronization signal transmission.
  • N phases where N could for example be 2 or 3
  • Each phase is characterized by different type of transmission.
  • the synchronization phase is based on the use of a wide channel bandwidth (more than one physical resource block (PRB)) satisfying the regulation for digital modulation (as per FCC).
  • the communication is based on the use of a narrowband scheme that follows the frequency hopping regulation (as per FCC).
  • the discovery phase can be either associated to the communication phase and multiplexed with the communication phase or can be considered as an independent phase and based on a wide channel bandwidth (more than one PRB) satisfying the regulation for digital modulation.
  • synchronization sequences are provided in order to adapt to a wider bandwidth.
  • the current design for NB-IOT is not optimized to exploit all the available degree of freedom in the system and the current design for D2D is not optimized to a small bandwidth and in particular neither the NB-IOT nor the D2D technology are adapted to the FCC regulatory requirements. While the above approaches can be seen to focus on the use of a narrowband system (1 PRB) and aiming at satisfying the frequency hopping regulation, the approach described in the following addresses a system design that satisfies regulations of a hybrid system and that exploits the benefit of both digital modulation and frequency hopping (as per FCC).
  • Figure 27 shows a diagram 2700 illustrating a two stage approach for
  • the first state corresponds to a synchronization phase 2701 while a second state corresponds to the discovery and communication phase 2702.
  • the synchronization procedures and synch source may for example work as described above.
  • the device enters the synchronization phase 2701
  • the device enters into synchronization phase (Synch or SYNCH_PHASE).
  • This phase has a maximum duration T_SYNCH.
  • synchronization sequences are sent by the synchronization device or it transmits itself synchronization sequence. It operates as a digital modulation system and it transmits synchronization sequences and broadcast channel mapped into a bandwidth of width B.
  • the bandwidth B is for example larger than 500KHz.
  • the device may transmit synchronization sequences U-NPSS and U-NSSS as described above: for example, U-NPSS as a length 35 ZC sequence that spans 35 subcarriers potentially excluding the DC subcarrier. It repeats the sequence over the at least 14 symbols available in 1 subframe. To generalize the U-NSSS 3 extra symbols in the U-NSSS subframe could also be used for the U-NPSS.
  • U-NSSS design can be extended according to different methodologies:
  • a 501 ZC long sequence mapped first in frequency and then in time, spanning 3 PRBs in frequency and 14 symbols in time domain.
  • PBCH is mapped into 3 PRBs also, split into blocks and each repeated RLPBCH times.
  • the synchronization device transmits in a continuous manner in a specified frequency the following set of signals:
  • Pp, Ps and ⁇ may be different depending on the amount of repetitions needed in order to achieve a target SNR of e.g.-19dB.
  • the synchronization device exits the synchronization phase at the end of the transmission of the predefined amount of U-NPSS, U-NSSS and U-NPBCH repetitions.
  • a device (UE) listening for the spectrum to detect a synchronization source i.e. a synchronization device
  • the device If after X seconds the device does not detect any synchronization source already present it continues the synchronization phase and becomes a synchronization source by operating as sync device as described above.
  • synchronization source it exits the synchronization phase and enters into the discovery and communication phase 2702 when the timer related to the synchronization phase has expired.
  • discovery and communication may be operating in the same way and hence the device could be able to multiplex communication signals with discovery signals.
  • the device operates according to a frequency hopping pattern and it operates in a narrowband
  • transmission method with a bandwidth that spans from single tone (e.g. for discovery signal or for user data) to single PRB transmission (multi-tone transmission for communication).
  • single tone e.g. for discovery signal or for user data
  • single PRB transmission multi-tone transmission for communication
  • the device sends pilot signals (based on DM-RS) together with the transmission burst in order to allow compensation of the frequency and time misalignment.
  • Figure 28 shows a diagram illustrating a three stage approach for synchronization, discovery and communication.
  • the first state corresponds to a synchronization phase 2801
  • the second state corresponds to a discovery phase 2802
  • the third state corresponds to a communication phase 2803.
  • the synchronization phase 2801 may be similar to the synchronization phase 2701 of figure 27.
  • a device When a device exits the synchronization phase 2801 the device enters into a discovery phase (DISCOVERY_PHASE) 2802 with a maximum duration T_DISC.
  • the discovery phase 2802 is based on the use of a digital modulation and hence a discovery signal is transmitted in a similar manner as the synchronization signal.
  • the discovery signal is periodically transmitted with a duty cycle of Y seconds within the synchronization duty cycle, creating a regular pattern as illustrated in figure 28.
  • a communication terminal is provided as illustrated in figure 29.
  • Figure 29 shows a communication terminal 2900.
  • the communication terminal 2900 includes a transceiver 2901 configured to support radio communication with a cellular radio communication network via a first frequency band (e.g. via a first carrier frequency) using a first bandwidth and a controller 2902 configured to control the transceiver 2901 to (e.g. directly) communicate with another communication terminal via a second frequency band (e.g. via a second carrier frequency) using a second bandwidth, wherein the second frequency band is located in a spectrum which is license free.
  • a communication terminal uses direct communication (in other words direct device-to-device communication, i.e. bypassing a cellular radio network radio access network, e.g.
  • the direct device-to-device communication may be a communication without central resource allocation) in a different frequency band e.g. in the case that communication via a cellular mobile communication network, i.e. via the radio access network of a cellular mobile communication network, is not possible, e.g. due to high load of the radio access network or due to the communication terminal not being in a coverage region of the radio access network.
  • the direct communication may be entirely proprietary or may be implemented as a variation of any of the below mentioned radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third
  • GSM Global System for Mobile Communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • 3GPP Third Generation Partnership Project
  • W-CDMA High Speed Packet Access
  • HSPA High- Speed Downlink Packet Access
  • HSDPA High-Speed Uplink Packet Access
  • HSPA+ Universal Mobile Telecommunications System-Time- Division Duplex
  • UMTS-TDD Time Division-Code Division Multiple Access
  • TD-CDMA Time Division-Synchronous Code Division Multiple Access
  • 3rd Generation Partnership Project Release 8 Pre-4th Generation
  • 3GPP Rel. 8 Pre-4G
  • 3GPP Rel. 9 3rd Generation Partnership Project Release 9
  • 3GPP Rel. 10 3rd Generation Partnership Project Release 10) , 3GPP Rel.
  • 3GPP Rel. 12 3rd Generation Partnership Project Release 12
  • 3GPP Rel. 13 3rd Generation Partnership Project Release 13
  • 3GPP Rel. 14 3rd Generation Partnership Project Release 14
  • 3GPP Rel. 15 3rd Generation Partnership Project Release 15
  • 3GPP Rel. 16 3rd Generation Partnership Project Release 16
  • 3GPP Rel. 17 3rd Generation Partnership Project Release 17
  • V2V Vehicle-to-Vehicle
  • V2X Vehicle-to-X
  • DSRC Dedicated Short Range Communications
  • the direct communication mode may be implemented as i) a fully proprietary mode or ii) as a modification of an existing (standardized) RAT, for example by introducing new signaling mechanisms on the MAC layer.
  • the (de)activation of the direct communication may be done by (de)activating the modification (e.g., MAC signaling) when the concerned direct communicatoin transmission starts (ends).
  • the direct communication may be narrowband communication i.e. may be performed in a narrowband (e.g. at 180KHz or 1.4MHz). It may for example be based on on a contention based radio access protocol, e.g. Carrier Sense Multiple Access/Collision Avoidance (CSMA/CA).
  • CSMA/CA Carrier Sense Multiple Access/Collision Avoidance
  • the communication terminal may further include a transmitter configured to transmit a discovery signal to make the presence of the communication terminal detectable by the other communication terminal.
  • the communicatoin terminal may also include a receiver configured to receive a discovery signal to detect the presence of the other communication terminal.
  • the components of the communication terminal may for example be implemented by one or more circuits.
  • a “circuit” may be understood as any kind of a logic implementing entity, which may be special purpose circuitry or a processor executing software stored in a memory, firmware, or any combination thereof.
  • a “circuit” may be a hard-wired logic circuit or a programmable logic circuit such as a programmable processor, e.g. a microprocessor.
  • a “circuit” may also be a processor executing software, e.g. any kind of computer program. Any other kind of implementation of the respective functions which will be described in more detail below may also be understood as a "circuit".
  • the communication terminal may for example carry out a method as illustrated in figure 30.
  • Figure 30 shows a flow diagram 3000 illustrating a method for initiating a communication, for example carried out by a communication terminal.
  • the communication terminal (e.g. directly) communicates, by means of a transceiver supporting radio communication with a cellular radio communication network via a first frequency band using a first bandwidth, with another communication terminal via a second frequency band using a second bandwidth, wherein the second frequency band is located in a spectrum which is license free.
  • Example 1 is a communication terminal as illustrated in figure 29.
  • Example 2 the subject-matter of Example 1 may optionally include the second bandwidth being equal or smaller than the first bandwidth.
  • Example 3 the subject-matter of Example 1 or 2 may optionally include the first frequency band being one of the licensed bands used for GSM, GPRS, UTRA, EUTRA and the communication with the other communication terminal operating in a non-licensed band.
  • Example 4 the subject-matter of any one of Examples 1 to 3 may optionally include the controller being configured to control the transceiver to communicate with the other communication terminal by means of a direct communication via the second frequency band using the second bandwidth.
  • Example 5 the subject-matter of any one of Examples 1 to 4 may optionally include the transceiver being configured to operate the direct communication in a narrowband.
  • Example 6 the subject-matter of any one of Examples 1 to 5 may optionally include the controller being configured to control the transceiver to directly communicate with the other communication terminal if communication with the cellular radio communication network is not available.
  • Example 7 the subject-matter of any one of Examples 1 to 6 may optionally include the controller being configured to control the transceiver to directly communicate with the other communication terminal based on at least one of an availability of radio resources for communicating with the cellular mobile communication network, a load of the cellular mobile communication network and whether the communication terminal is in a coverage area of the cellular mobile communication network.
  • Example 8 the subject-matter of any one of Examples 1 to 7 may optionally include the controller being configured to control the transceiver to directly communicate with the other communication terminal if a load of the cellular mobile communication network is above a predetermined threshold.
  • Example 9 the subject-matter of any one of Examples 1 to 8 may optionally include the controller of the communication terminal being configured to select the other communication terminal from a plurality of other communication terminals.
  • Example 10 the subject-matter of Example 9 may optionally include the controller being configured to select the other communication terminal from a plurality of other communication terminals being in direct-to-direct communication range of the communication terminal.
  • Example 11 the subject-matter of Example 9 or 10 may optionally include the controller being configured to group the plurality of other communication terminals and to select the other communication terminal based on priorities associated with the groups.
  • Example 12 the subject-matter of Example 11 may optionally include the controller being configured to select the other communication terminal based on that the other subject-matter of the plurality of other communication terminals has the highest priority among the plurality of other communication terminals.
  • Example 13 the subject-matter of any one of Examples 1 to 12 may optionally include the controller being configured to initiate the direct communication based on whether a user input indicates a request to initiate direct communication.
  • Example 14 the subject-matter of any one of Examples 1 to 13, further comprising a transmitter configured to transmit information about further communication terminals which are in the communication terminal's range for direct communication to the other communication terminal.
  • Example 15 the subject-matter of any one of Examples 1 to 14 may optionally include the transceiver being configured to transmit a synchronization signal to a least the other communication terminal for the purpose of synchronization in at least a single frequency for a given period of time and changing frequency with a specific duty cycle.
  • Example 16 the subject-matter of Example 15 may optionally include
  • synchronizing with the other communication terminal comprising synchronizing at least one of a transmission frequency and a transmission timing with the other communication terminal.
  • Example 17 the subject-matter of Example 14 or 15 may optionally include the transceiver being configured to transmit the synchronization signal after detecting no other synchronization sources present during a plurality of predetermined times portion of which are indicated in master information.
  • Example 18 the subject-matter of Example 14 or 15 may optionally include the transmitter being configured to transmit the synchronization signal based on forwarding a synchronization signal received from a third communication terminal whenever it needs to communicate under specific conditions related to the received power, number of hops already used, battery status etc.
  • Example 19 the subject-matter of Example 14 or 15 may optionally include the transmitter being explicitly not allowed to transmit the synchronization signal based on forwarding a synchronization signal received from a third communication terminal.
  • Example 20 the subject-matter of any one of Examples 15 to 19 may optionally include the transmitting the synchronization signal comprising a periodic transmission of a synchronization unit.
  • Example 21 the subject-matter of Example 20 may optionally include the transmission of a synchronization unit comprising the transmission of one or more
  • Example 22 the subject-matter of Example 21 may optionally include each synchronization block comprising one or more times a primary synchronization sequence, one or more times a secondary synchronization sequence and one or more times broadcast channel master information.
  • Example 23 the subject-matter of any one of Examples 15 to 22 may optionally include the synchronization signal indicating whether the communication terminal is a synchronization source or transmits the synchronization signal based on forwarding a synchronization signal received from a third communication terminal.
  • Example 24 the subject-matter of any one of Examples 1 to 23 may optionally include the controller being configured to control the transceiver to initiate communication with the other communication terminal by means of a two-stage discovery procedure.
  • Example 25 the subject-matter of Example 24 may optionally include the two- stage discovery procedure comprising a first stage including an exchange of an anonymized version of an identification of the communication terminal with the other communication terminal.
  • Example 26 the subject-matter of Example 25 may optionally include the anonymized version of the identification of the communication terminal being a shortened form of an identification of the communication terminal which misses a part of the identification of the communication terminal.
  • Example 27 the subject-matter of Example 25 or 26 may optionally include the two-stage discovery procedure comprising a second stage after the first stage comprising an authentication and a group credential exchange with the other communication terminal.
  • Example 28 the subject-matter of any one of Examples 1 to 27 may optionally include the communication terminal being configured to transmit a synchronization signal during a first time period based on a first bandwidth ((in a continuous manner) based on the use of at least 3 PRBs (504KHz)) and to perform discovery of communication devices or communication with the other communication device during a second time period based on a second bandwidth narrower than the first bandwidth (with frequency hopping scheme on a single frequency) based on a narrow bandwidth (e.g. smaller than 504KHz).
  • a first bandwidth ((in a continuous manner) based on the use of at least 3 PRBs (504KHz))
  • discovery of communication devices or communication with the other communication device during a second time period based on a second bandwidth narrower than the first bandwidth (with frequency hopping scheme on a single frequency) based on a narrow bandwidth (e.g. smaller than 504KHz).
  • Example 29 the subject-matter of any one of Examples 1 to 28 may optionally include the communication terminal being configured to transmit a synchronization signal during a first time period ((in a continuous manner on a single frequency) based on the use of at least 3 PRBs (504KHz)) based on a first bandwidth, to perform discovery of communication devices during a second time period ((in a continuous manner on a single frequency) based on the use of at least 3 PRBs (504KHz)) based on a second bandwidth and to perform
  • Example 30 the subject-matter of Example 29 may optionally include the first time period and the second time period being periodically scheduled with a given duty cycle.
  • Example 31 is a method for initiating a communication as illustrated in figure 30.
  • Example 32 the subject-matter of Example 31 may optionally include the second bandwidth being equal or smaller than the first bandwidth.
  • Example 33 the subject-matter of Example 31 or 32 may optionally include the first frequency band being one of the licensed bands used for GSM, GPRS, UTRA, EUTRA and the communication with the other communication terminal operating in a non-licensed band.
  • Example 34 the subject-matter of any one of Examples 31 to 33 may optionally include controlling the transceiver to communicate with the other communication terminal by means of a direct communication via the second frequency band using the second bandwidth.
  • Example 35 the subject-matter of any one of Examples 31 to 34 may optionally include the transceiver operating the direct communication in a narrowband.
  • Example 36 the subject-matter of any one of Examples 31 to 35 may optionally include controlling the transceiver to directly communicate with the other communication terminal if communication with the cellular radio communication network is not available.
  • Example 37 the subject-matter of any one of Examples 31 to 36 may optionally include controlling the transceiver to directly communicate with the other communication terminal based on at least one of an availability of radio resources for communicating with the cellular mobile communication network, a load of the cellular mobile communication network and whether the communication terminal is in a coverage area of the cellular mobile communication network.
  • Example 38 the subject-matter of any one of Examples 31 to 37 may optionally include controlling the transceiver to directly communicate with the other communication terminal if a load of the cellular mobile communication network is above a predetermined threshold.
  • Example 39 the subject-matter of any one of Examples 31 to 38 may optionally include selecting the other communication terminal from a plurality of other communication terminals.
  • Example 40 the subject-matter of Example 39 may optionally include selecting the other communication terminal from a plurality of other communication terminals being in direct-to-direct communication range of the communication terminal.
  • Example 41 the subject-matter of Example 39 or 40 may optionally include grouping the plurality of other communication terminals and selecting the other communication terminal based on priorities associated with the groups.
  • Example 42 the subject-matter of Example 41 may optionally include selecting the other communication terminal based on that the other subject-matter of the plurality of other communication terminals has the highest priority among the plurality of other communication terminals.
  • Example 43 the subject-matter of any one of Examples 31 to 42 may optionally include initiating the direct communication based on whether a user input indicates a request to initiate direct communication.
  • Example 44 the subject-matter of any one of Examples 31 to 43 may optionally include transmitting information about further communication terminals which are in the communication terminal's range for direct communication to the other communication terminal.
  • Example 45 the subject-matter of any one of Examples 31 to 44 may optionally include transmitting a synchronization signal to a least the other communication terminal for the purpose of synchronization in at least a single frequency for a given period of time and changing frequency with a specific duty cycle.
  • Example 46 the subject-matter of Example 45 may optionally include
  • synchronizing with the other communication terminal comprising synchronizing at least one of a transmission frequency and a transmission timing with the other communication terminal.
  • Example 47 the subject-matter of Example 44 or 45 may optionally include transmitting the synchronization signal after detecting no other synchronization sources present during a plurality of predetermined times portion of which are indicated in master information.
  • Example 48 the subject-matter of Example 44 or 45 may optionally include transmitting the synchronization signal based on forwarding a synchronization signal received from a third communication terminal whenever it needs to communicate under specific conditions related to the received power, number of hops already used, battery status etc.
  • Example 49 the subject-matter of Example 44 or 45 may optionally include explicitly not being allowed to transmit the synchronization signal based on forwarding a synchronization signal received from a third communication terminal.
  • Example 50 the subject-matter of any one of Examples 45 to 49 may optionally include the transmitting the synchronization signal comprising a periodic transmission of a synchronization unit.
  • Example 51 the subject-matter of Example 50 may optionally include the transmission of a synchronization unit comprising the transmission of one or more
  • Example 52 the subject-matter of Example 51 may optionally include each synchronization block comprising one or more times a primary synchronization sequence, one or more times a secondary synchronization sequence and one or more times broadcast channel master information.
  • Example 53 the subject-matter of any one of Examples 45 to 52 may optionally include the synchronization signal indicating whether the communication terminal is a synchronization source or transmits the synchronization signal based on forwarding a synchronization signal received from a third communication terminal.
  • Example 54 the subject-matter of any one of Examples 31 to 53 may optionally include controlling the transceiver to initiate communication with the other communication terminal by means of a two-stage discovery procedure.
  • Example 55 the subject-matter of Example 54 may optionally include the two- stage discovery procedure comprising a first stage including an exchange of an anonymized version of an identification of the communication terminal with the other communication terminal.
  • Example 56 the subject-matter of Example 55 may optionally include the anonymized version of the identification of the communication terminal being a shortened form of an identification of the communication terminal which misses a part of the identification of the communication terminal.
  • Example 57 the subject-matter of Example 55 or 56 may optionally include the two-stage discovery procedure comprising a second stage after the first stage comprising an authentication and a group credential exchange with the other communication terminal.
  • Example 58 the subject-matter of any one of Examples 31 to 57 may optionally include transmitting a synchronization signal during a first time period based on a first bandwidth ((in a continuous manner) based on the use of at least 3 PRBs (504KHz)) and performing discovery of communication devices or communication with the other
  • a communication device during a second time period based on a second bandwidth narrower than the first bandwidth (with frequency hopping scheme on a single frequency) based on a narrow bandwidth (e.g. smaller than 504KHz).
  • Example 59 the subject-matter of any one of Examples 31 to 58 may optionally include transmitting a synchronization signal during a first time period ((in a continuous manner on a single frequency) based on the use of at least 3 PRBs (504KHz)) based on a first bandwidth, to perform discovery of communication devices during a second time period ((in a continuous manner on a single frequency) based on the use of at least 3 PRBs (504KHz)) based on a second bandwidth and performing communication with the other communication device during a third time period based on a third bandwidth narrower than the first bandwidth and the second bandwidth (with frequency hopping scheme) based on a narrow bandwidth (e.g. smaller than 504KHz).
  • a synchronization signal during a first time period ((in a continuous manner on a single frequency) based on the use of at least 3 PRBs (504KHz)) based on a first bandwidth
  • to perform discovery of communication devices during a second time period ((in a continuous manner
  • Example 60 the subject-matter of Example 59 may optionally include the first time period and the second time period being periodically scheduled with a given duty cycle.
  • a mobile communication device comprising a transceiver configured to, in response to communication via a cellular
  • a mobile communication device which i) first has a classical connection (between mobile communication device and cellular network infrastructure) based on a standardized RAT, then ii) it switches to a proprietary device to device mode if communication resources are not available or are limited (wherein the device to device mode fully proprietary or modification of a standardized RAT), then iii) the mobile communication device exchanges data using the device to device connection, then iv) the mobile communication device switches back to the classical connection (to the cellular network infrastructure) once the communication resources become available again.
  • the device to device (e.g. proprietary) connection can be established in parallel to the classical connection.
  • a mobile communication device in a standalone manner uses an unlicensed band to communicate with other devices based on a narrowband communication and exchanges data with the other device. For example, this mobile
  • communication device is a classical device capable of supporting a connection to a cellular radio network infrastructure based on a standard RAT and supports switching from the standardized RAT to a proprietary RAT depending on resource availability, traffic load, quality of the connections (RSRP for example) and alternatively there is the possibility to support this via a dual connection capability.
  • RSRP quality of the connections
  • a communication terminal (and a corresponding method for initiating a communication) comprising a detector configured to detect whether communication in a first frequency band via a cellular mobile communication network is available and a controller configured to initiate, based on whether communication via the cellular mobile communication network is available, direct communication with another communication terminal in a second frequency band different from the first frequency band.
  • the controller may for example be configured to check whether direct
  • communication with the other communication terminal is allowed and is configured to initiate the direct communication based on whether direct communication with the other
  • the controller is configured to check whether direct communication with the other communication terminal is allowed based on an authorization of the other communication terminal.
  • the detector may be configured to perform an authorization procedure with other communication terminal and initiate direct communication with the other communication terminal if the authorization procedure successfully authorizes the other communication terminal.
  • the controller may be configured to check whether direct communication with the other communication terminal is allowed based on a manufacturer identification of other communication terminal.
  • a mobile communication device capable of communicating at least with other devices in a narrowband manner operating in the unlicensed spectrum
  • the device is also capable of communicate to the network based on a standardized rat.
  • the device is capable of switching to the direct narrowband communication when e.g. resources are not available or radio conditions become poor and of switching back to the standardized RAT method when e.g. radio conditions are above a certain threshold.
  • the device may be capable of establishing always a dual communications and choose in a dynamic manner the best technology to communicate.

Landscapes

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

Abstract

L'invention concerne un terminal de communication comprenant un émetteur-récepteur configuré pour prendre en charge une synchronisation, une découverte et une communication radio au moyen d'un réseau de radiocommunication cellulaire par l'intermédiaire d'une première bande de fréquences utilisant une première bande passante et un dispositif de commande conçu pour commander l'émetteur-récepteur de sorte à communiquer directement avec un autre terminal de communication par l'intermédiaire d'une seconde bande de fréquences utilisant une seconde bande passante, la seconde bande de fréquences étant située dans un spectre sans licence.
PCT/US2017/039851 2016-12-28 2017-06-29 Terminal de communication et procédé d'initiation de communication WO2018125287A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
PCT/IB2016/001995 WO2018122571A1 (fr) 2016-12-28 2016-12-28 Terminal de communication et procédé d'amorce d'une communication
IBPCT/IB2016/001995 2016-12-28
USPCT/US2017/025266 2017-03-31
US2017025266 2017-03-31

Publications (1)

Publication Number Publication Date
WO2018125287A1 true WO2018125287A1 (fr) 2018-07-05

Family

ID=62710688

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/039851 WO2018125287A1 (fr) 2016-12-28 2017-06-29 Terminal de communication et procédé d'initiation de communication

Country Status (1)

Country Link
WO (1) WO2018125287A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108650688A (zh) * 2018-08-22 2018-10-12 苏州凌犀物联网技术有限公司 一种扫频测试的方法及Lora网关
CN108650686A (zh) * 2018-08-22 2018-10-12 苏州凌犀物联网技术有限公司 一种扫频的Ping-Pong测试方法、终端及服务器
CN108965063A (zh) * 2018-08-22 2018-12-07 苏州凌犀物联网技术有限公司 一种扫频测试的异常处理方法、网关及服务器
CN109039820A (zh) * 2018-08-22 2018-12-18 苏州凌犀物联网技术有限公司 一种Lora扫频测试方法、终端及服务器
CN109275180A (zh) * 2018-09-30 2019-01-25 上海移芯通信科技有限公司 一种窄带物联网系统中的功耗优化方法及终端
WO2020211684A1 (fr) * 2019-04-18 2020-10-22 Oppo广东移动通信有限公司 Procédé de transmission de message et dispositif correspondant
WO2023142090A1 (fr) * 2022-01-29 2023-08-03 北京小米移动软件有限公司 Procédé et appareil de transmission d'informations, dispositif de communication et support de stockage

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015021345A2 (fr) * 2013-08-09 2015-02-12 Alcatel-Lucent Usa Inc. Procédures de découverte de dispositif à dispositif (d2d) en deux étapes
US20150085789A1 (en) * 2013-09-25 2015-03-26 Qualcomm Incorporated Time coordination to improve throughput for d2d broadcast
US20150249937A1 (en) * 2012-09-28 2015-09-03 Telefonaktiebolaget L M Ericsson (Publ) Method for d2d radiocommunication
US20160174179A1 (en) * 2014-12-10 2016-06-16 Lg Electronics Inc. Method of selecting synchronization source in wireless communication system and apparatus therefor
WO2016203290A1 (fr) * 2015-06-15 2016-12-22 Telefonaktiebolaget Lm Ericsson (Publ) Format de bloc de synchronisation variable

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150249937A1 (en) * 2012-09-28 2015-09-03 Telefonaktiebolaget L M Ericsson (Publ) Method for d2d radiocommunication
WO2015021345A2 (fr) * 2013-08-09 2015-02-12 Alcatel-Lucent Usa Inc. Procédures de découverte de dispositif à dispositif (d2d) en deux étapes
US20150085789A1 (en) * 2013-09-25 2015-03-26 Qualcomm Incorporated Time coordination to improve throughput for d2d broadcast
US20160174179A1 (en) * 2014-12-10 2016-06-16 Lg Electronics Inc. Method of selecting synchronization source in wireless communication system and apparatus therefor
WO2016203290A1 (fr) * 2015-06-15 2016-12-22 Telefonaktiebolaget Lm Ericsson (Publ) Format de bloc de synchronisation variable

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108650688A (zh) * 2018-08-22 2018-10-12 苏州凌犀物联网技术有限公司 一种扫频测试的方法及Lora网关
CN108650686A (zh) * 2018-08-22 2018-10-12 苏州凌犀物联网技术有限公司 一种扫频的Ping-Pong测试方法、终端及服务器
CN108965063A (zh) * 2018-08-22 2018-12-07 苏州凌犀物联网技术有限公司 一种扫频测试的异常处理方法、网关及服务器
CN109039820A (zh) * 2018-08-22 2018-12-18 苏州凌犀物联网技术有限公司 一种Lora扫频测试方法、终端及服务器
CN108650688B (zh) * 2018-08-22 2022-08-16 苏州凌犀物联网技术有限公司 一种扫频测试的方法及Lora网关
CN109275180A (zh) * 2018-09-30 2019-01-25 上海移芯通信科技有限公司 一种窄带物联网系统中的功耗优化方法及终端
CN109275180B (zh) * 2018-09-30 2019-12-10 上海移芯通信科技有限公司 一种窄带物联网系统中的功耗优化方法及终端
WO2020211684A1 (fr) * 2019-04-18 2020-10-22 Oppo广东移动通信有限公司 Procédé de transmission de message et dispositif correspondant
EP3955645A4 (fr) * 2019-04-18 2022-06-08 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de transmission de message et dispositif correspondant
US11750697B2 (en) 2019-04-18 2023-09-05 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Message transmission method and related devices
WO2023142090A1 (fr) * 2022-01-29 2023-08-03 北京小米移动软件有限公司 Procédé et appareil de transmission d'informations, dispositif de communication et support de stockage

Similar Documents

Publication Publication Date Title
US12096335B2 (en) Method and apparatus for performing device-to-device discovery
WO2018125287A1 (fr) Terminal de communication et procédé d'initiation de communication
CN110708153B (zh) 在未许可射频频谱上的无线通信
Mumtaz et al. Smart Direct-LTE communication: An energy saving perspective
CN104349421B (zh) 设备发现方法和用户设备、网络侧设备
CN103997788B (zh) 用于设备到设备通信的设备发现方法及用户设备、网络侧设备
US20140099950A1 (en) Method and user equipment for peer-to-peer communication
US11197303B2 (en) Direct link synchronization signal block transmission
KR20200052890A (ko) 뉴 라디오에서 전력 트랜지션들을 핸들링하기 위한 방법들 및 장치들
US11265875B2 (en) Techniques for resource block allocation in wireless communications
CN112689962A (zh) 用于无线通信的半双工技术
KR101652929B1 (ko) 무선통신 시스템의 동기신호 송수신 방법 및 장치
CN111527721A (zh) 用于sps指派的业务的dmrs设计
US11133970B2 (en) Techniques for supporting multiple waveforms in wireless communications
EP4322627A1 (fr) Signal de réveil prenant en charge la mesure et le suivi de rrm
CN115885488A (zh) 用于无线通信中的群共用参考信号触发技术
CN115398844A (zh) 用于在无线通信中传送控制信道的重复的技术
KR20220002924A (ko) 무선 통신들에서 랜덤 액세스 프리앰블들 및 페이로드 포맷들을 선택하기 위한 기법들
WO2018122571A1 (fr) Terminal de communication et procédé d'amorce d'une communication
WO2024033039A1 (fr) Signal de réveil prenant en charge une mesure et un suivi rrm
EP4211857A2 (fr) Techniques de fourniture de signaux de référence de démodulation dédiés à des fins de répétitions de transmission
WO2024033064A1 (fr) Structure de signal de réveil en deux parties
CN118575550A (zh) 用于多侧行链路信道占用时间共享的方法和装置

Legal Events

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

Ref document number: 17885638

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17885638

Country of ref document: EP

Kind code of ref document: A1