Patent Application
20230309001
The present invention pertains in general to wireless communication and in particular to methods and apparatuses for managing device-to-device communications in a wireless network.
Device-to-device (D2D) communication, for example side link (SL) communication, can enable UEs to directly communicate with each other. D2D communications can be performed with or without assistance of a base station, which can potentially improve latency and battery life of the UE.
However, current D2D communication protocols have technical problems in certain situations. For example, an end node (EN) cannot establish D2D communication if the EN and gateway (GW) are using different cellular serving cells that are not synchronized. Another example would be that D2D data transmission rate can be very low, for example in the case of data transmission with polite spectrum access (PSA), as PSA requires a transmitter to remain off after a transmission and this results in unacceptable transmission gaps.
Therefore there is a need for a method and apparatus for managing device-to-device communications in a wireless network, that is not subject to one or more limitations of the prior art.
This background information is provided to reveal information believed by the applicant to be of possible relevance to the present invention. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present invention.
An object of embodiments of the present invention is to provide a method and apparatus for managing device-to-device communications in a wireless network. In accordance with embodiments, there is provided a method for supporting device-to-device (D2D) communication in a wireless network, in accordance with embodiments of the present disclosure. The method is performed between a first D2D device (D1) and a second D2D device (D2). The method includes during a period where the D1 and the D2 are available for active D2D communications therebetween and when the D2 identifies a need for a second communication with at least one of a base station or a different D2D device, transmitting, by the D2, a D2D communication not available message (DNAM) to the D1. The DNAM indicates that one or more of the D1 and the D2 are unavailable for active D2D communications therebetween. Upon receipt of the DNAM by the D1, transitioning, by the D1, to a listening mode for receiving at least a D2D communication available message (DAM) from the D2. The DAM indicates that the D1 and the D2 are available for active D2D communications therebetween and the D2 is capable of performing both the D2D communication and cellular communication non-simultaneously.
In some embodiments, during the listening mode, upon the D2 identifying a need for a third communication, transmitting by the D2, a second DNAM. In some embodiments, one or more of the DNAM and the second DNAM are transmitted to one or more of a plurality of devices, wherein the plurality of devices includes at least the D1. In some embodiments, transitioning to the listening mode includes transitioning, by the D1, to a power saving mode, wherein the D1 sleeps for at least one sleep period upon transition to the power saving mode. In some embodiments a duration of the sleep period is specified in one or more of the DNAM and the second DNAM. In some embodiments, upon expiry of the sleep period, the D1 listens for one or more of the second DNAM or the DAM for a receive mode period. In some embodiments, upon non-receipt of the DAM or the second DNAM before expiry of the receive mode period, transitioning, by the D1, to a short power saving mode, wherein the D1 sleeps for a short sleep period during the short power saving mode. Upon expiry of the short sleep period, listening, by the D1, for one or more of the DAM and the second DNAM during a short wake up period.
In some embodiments, the DNAM or the second DNAM indicates whether one or more of the second communication or the third communication has a known duration. In some embodiments, the third communication is one or more of an extension of the second communication, a new D2D communication and a new cellular communication.
In some embodiments, transitioning to the listening mode includes transitioning, by the D1, to a short power saving mode, wherein the D1 sleeps for a short sleep period during the short power saving mode and upon expiry of the short sleep period, listening, by the D1, for the DAM or the second DNAM during a short wake up period. In some embodiments, the short sleep period has a duration, the duration is one or more of: a preconfigured period, a period signalled by the D2 and a period calculated based on a known formula. In some embodiments, the short sleep period is signalled by the D2 within the DNAM. In some embodiments, upon the D1 receiving the DAM, transmitting, by the D1, a message to the D2.
In accordance with embodiments, there is provided a method for supporting device-to-device (D2D) communication in a wireless network. The method is performed between two D2D devices (i.e., D1 and D2). D2D devices can be one or more of an end node (EN), a gateway (GW) and/or a mesh node. The method includes upon synchronization of the D1 and the D2, establishing a D2D connection between the D1 and the D2 using a D2D connection request (CRQ) and a D2D connection response (CRS). The method further includes transitioning to a D2D connected mode and performing data transmission between the D1 and the D2. The method further includes exiting from the D2D connected mode upon one or more of receipt of a D2D connection release request and expiry of an inactivity timer. Each of the D1 and the D2 is capable of performing both the D2D communication and cellular communication.
In some embodiments, D1 can be an end node and D2 can be a gateway. The method includes upon synchronization of the EN and the GW, establishing a D2D connection between the EN and the GW using a D2D connection request (CRQ) and a D2D connection response (CRS). The method further includes transitioning to a D2D connected mode and performing data transmission between the EN and the GW. The method further includes exiting from the D2D connected mode upon one or more of receipt of a D2D connection release request and expiry of an inactivity timer. Each of the EN and the GW is capable of performing both the D2D communication and cellular communication.
In some embodiments, establishing the D2D connection includes transmitting the D2D CRQ and receiving the D2D CRS with acceptance prior to transitioning to the D2D connected mode.
In some embodiments, the GW and the EN are engaged with two asynchronous cellular serving cells and the method further includes synchronizing the EN and the GW, wherein synchronizing includes detecting, by the EN, surrounding base transceiver stations (BTSs) e.g., synchronization signals from the surrounding BTSs) and discovering, by the EN, the GW attached to one of the detected BTSs. In some embodiments, synchronizing further includes prioritizing, by the EN, the detected BTSs based on one or more of a pre-configured list of prioritized public land mobile networks (PLMNs) and a quality of signal detection.
In some embodiments, the method further includes the EN synchronizing with the GW using cellular synchronization signals. In some embodiments, the EN identifies the GW using a D2D synchronization signal transmitted by the GW. In some embodiments, the GW transmits the D2D synchronization signal every Nth reception occasion (RO), wherein the N is indicative of one or more of a timing accuracy requirement of the RO and a timing accuracy capability of the EN. In some embodiments, the EN identifies the GW via the CRQ when the CRQ is transmitted using the discovery ID of the GW.
In some embodiments, the GW identifies an imminent upcoming cellular activity during the D2D connected mode and the method further includes terminating the D2D connection between the EN and the GW using an immediate release request (RRQ IR) and re-establishing the D2D connection between the EN and the GW.
In some embodiments, the imminent upcoming cellular activity has a known duration and the method further includes transmitting, from the GW to the EN, a D2D immediate release request including an indication of the known duration of the cellular activity and upon receiving the D2D immediate release request, transitioning, by the EN, to a sleep mode for the known duration. The method further includes upon completion of the known duration, transitioning, by the EN, to a wake up mode and transmitting, from the GW to the EN upon completion of the cellular activity and during the EN wake up mode, the D2D CRQ to re-establish the D2D connection within a connection request time period.
In some embodiments, the method further includes transmitting, from the GW to the EN, a D2D immediate release request with the field indicating that the imminent upcoming cellular activity has an unknown duration and upon receiving the D2D immediate release request, transitioning, by the EN, to a short D2D discontinuous reception (DRX) mode for a short D2D DRX cycle and to a wake up mode for a short D2D reception opportunity (RO) duration. The method further includes repeating the transitions if the cellular activity is incomplete during the short D2D RO duration and upon completion of the cellular activity, transmitting, from the GW to the EN, the CRQ to re-establish the D2D connection during the wake up mode.
In some embodiments, the cellular activity includes cellular connected mode discontinuous reception (jC-DRX). In some embodiments the EN transmits the D2D CRQ to the GW while the GW is performing a cellular activity, wherein establishing the D2D connection includes upon completion of the cellular activity, transmitting, from the GW to the EN, a D2D available message (DAM). Establishing the D2D connection further includes upon receipt of the DAM, transmitting, from the EN to the GW, the D2D CRQ and upon receipt of a D2D CRS with acceptance, transitioning to the D2D connected mode. In some embodiments, the transmission of the DAM is delayed for a period of time up to an available transmission time for the DAM. In some embodiments, the D2D communication is performed using a single radio and a single antenna.
In some embodiments, the data transmission is performed using one or more sub-bands in compliance with one or more spectrum transmission rules including a maximum percent transmission time and a minimum off time after transmission for each sub-band. In some embodiments, the number of the sub-bands and bandwidth of each sub-band are determined based on one or more of: the spectrum transmission rules, EN power consumption, short term sustained required data rates, long term sustained required data rates, average signal-to-noise ratio (SNR), scheduling efficiency, device cost device, duplexing protocol and capacity. In some embodiments, the spectrum transmission rules further include data transmission being performed after a clear channel assessment (CCA), the CCA configured for a bandwidth smaller than the sub-band. In some embodiments, data transmission is suspended within the CCA configured bandwidth upon failure of the CCA. In some embodiments, the configured bandwidth of the CCA is configured based on one or more of the spectrum transmission rules, bandwidth of each sub-band, short term data rates, long term data rates, average signal-to-noise ratio (SNR) and scheduling efficiency. In some embodiments, the data transmission is performed using one or more sub-bands in two D2D communication modes including polite spectrum access (PSA) mode and non-PSA mode.
In accordance with embodiments, there is provided a method for supporting device-to-device (D2D) communication in a wireless network. The method is performed between a first end node (EN1) and a second end node (EN2). Upon synchronization of the EN1 and the EN2, the method includes establishing a D2D connection between the EN1 and the EN2 using a D2D connection request (CRQ) and a D2D connection response (CRS). The method further includes transitioning to a D2D connected mode and performing data transmission between the EN1 and the EN2. The method additionally includes exiting from the D2D connected mode upon one or more of receipt of a D2D connection release request and expiry of an inactivity timer. Each of the EN1 and the EN2 is capable of performing both the D2D communication and a cellular communication.
In some embodiments, the EN2 is a mesh node.
In accordance with embodiments, there is provided a method for supporting device-to-device (D2D) communication in a wireless network. The method is performed between an end node (EN) and a gateway (GW). Upon synchronization of the EN and the GW, the method includes establishing a D2D connection between the EN and the GW using a D2D connection request (CRQ) and a D2D connection response (CRS). The method further includes transitioning to a D2D connected mode and performing data transmission between the EN and the GW. The method additionally includes exiting from the D2D connected mode upon one or more of receipt of a D2D connection release request and expiry of an inactivity timer. Each of the EN and the GW is capable of performing both the D2D communication and cellular communication.
In accordance with embodiments, there is provided an apparatus including a network interface for receiving data from and transmitting data to network devices connected to the wireless network, a processor and a machine readable memory storing machine executable instructions. The machine executable instructions, when executed by the processor configure the apparatus to perform one or more of the methods defined above.
Embodiments have been described above in conjunctions with aspects of the present invention upon which they can be implemented. Those skilled in the art will appreciate that embodiments may be implemented in conjunction with the aspect with which they are described, but may also be implemented with other embodiments of that aspect. When embodiments are mutually exclusive, or are otherwise incompatible with each other, it will be apparent to those skilled in the art. Some embodiments may be described in relation to one aspect, but may also be applicable to other aspects, as will be apparent to those of skill in the art.
Further features and advantages of the present invention will become apparent from the following detailed description, taken in combination with the appended drawings, in which:
It will be noted that throughout the appended drawings, like features are identified by like reference numerals.
In the present disclosure, it will be readily understood that communication between wireless devices can be enabled in multiple ways, and it can be defined as device to device (D2D) communications.
In the present disclosure, the terms “D2D” and “D2D communication” refer to any type of D2D communication such as sidelink (SL), wireless smart utility network (Wi-SUN™), digital enhanced cordless telecommunication (DECT™) 2020, Zigbee™ Wise™, etc. Said communication technologies are just examples and should not be construed as limiting in any way. It will be also understood that “Forte™”, “Forte SideLink (SL)” and “Forte PSA” are further examples of non-limiting examples of D2D communications or protocols.
In the present disclosure, the terms “cellular” and “cellular communication” refer to any type of cellular communication, for example but not limited to orthogonal frequency-division multiplexing (OFDM) based cellular, and long term evolution (LTE) and new radio (NR).
In the present disclosure, the terms “modulation” and “modulation and coding scheme (MCS)” refer to any known modulation technique, for example but not limited to quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64QAM, Gaussian minimum-shift keying (GMSK), Adaptive modulation and the like or any combination thereof.
In the present disclosure, the term base station, base transceiver station (BTS) can be interchangeably used to define a base station of a cellular communication network and can include a NodeB, evolved NodeB (eNB), next generation NodeB (gNB) or other base station configuration as would be readily understood.
In the present disclosure, it will be readily understood that any features and embodiments thereof illustrated in the instant application are intended to be applicable to any D2D communications and protocols, including for example Forte. It will be further understood that while some of the discussion below relates to a certain D2D communication, for example SL communication, it would be readily understood that corresponding or similar steps and procedures illustrated in the present disclosure would be generally applicable to any types of D2D communication protocols, such as Forte protocol.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.
The present disclosure provides a method and apparatus for supporting device-to-device (D2D) communication in a wireless network. The D2D devices can be one or more of an end node (EN), a gateway (GW) and/or a mesh node. A GW can be a device which is connected to ENs and/or mesh nodes via a D2D protocol and can also connected to the cloud via cellular communication. The GW may aggregate and distribute traffic to and from the connected ENs and mesh nodes. The GW can also act as a data source or a data sink. A mesh node can be a device which is connected to ENs and other mesh nodes via a D2D protocol and may also be connected to a GW via D2D protocol. The mesh node may aggregate and distribute traffic to and from the connected ENs and other mesh nodes which not connected to a GW. The mesh node can also act as a data source or a data sink. An EN can be a device which is connected to one or more of a mesh nodes and/or GWs. The EN may act as a data source or data sink. One aspect of the present disclosure relates to a feature that a single D2D device (e.g. end node (EN), gateway (GW), user equipment (UE), a mesh node etc.) is able to perform both cellular communication and D2D communication (e.g. Forte). It should be readily understood that the procedures and methods disclosed herein can be carried out between any two D2D devices D1 and D2 (i.e., D1 and D2 can be any of EN, GW and/or mesh node). Even if some procedures and figures are explained using an EN and a GW, they are simply examples which can be more generally applied to any combination of D2D devices. According to embodiments, a D2D connection between an end node (EN) and a gateway (GW) is established using a D2D connection request (CRQ) and a D2D connection response (CRS). Upon transitioning to a D2D connected mode, the EN and GW can perform data transmission. When the data transmission is completed or when certain situations occur, as disclosed elsewhere herein, the EN and GW can exit from the D2D connected mode via a D2D connection release request or the exit from D2D connected mode can occur upon expiry of an inactivity timer. According to embodiments, the D2D connection procedures disclosed herein can also be applied for D2D connection between two end nodes and/or between one end node and a mesh node. According to embodiments, the D2D connection procedures can be performed using a single radio and/or a single antenna.
Forte SideLink
When an end node (EN) requires synchronization with a gateway (GW), one way to achieve synchronization is to prompt the GW to send a D2D synchronization signal (e.g. a Forte SL synchronization (F-SS)) to the EN. Another way to achieve synchronization is for the ENs and GWs to be synchronized using cellular synchronization signals. Before a GW or EN sends a D2D connection request (CRQ) signal (e.g. a Forte CRQ), the GW or EN will need to synchronize with the other party with which D2D communication is desired.
In wireless communication, the physical layer of the control channel is often different from the physical layer of the data channel. Some non-limiting examples of the physical layer control channel include physical downlink control channel (PDCCH) for LTE and machine type communication (MTC) and a PDCCH (MPDCCH) for LTE-MTC (LTE-M).
A control message which can be transmitted on the control channel often needs to include information associated with one or more of the following fields:
As a non-limiting example, a D2D connected mode procedure can be defined based on the following sequence of steps. First, an EN and a GW perform synchronization, wherein the EN and GW attempt to synchronize their timing with each other. Upon synchronization, the EN may send a D2D connection request (CRQ) to the GW. In response to the D2D CRQ received from the EN, the GW sends an acceptance in the D2D connection response (e.g. Forte CRS). The GW can subsequently enter D2D connected mode (e.g. Forte connected mode). The EN enters the D2D connected mode (e.g. Forte connected mode) after it sends the D2D connection request (e.g. Forte CRQ) and receives the D2D connection request accept response (e.g. Forte CRS accept) from the GW.
During D2D connected mode, the EN and the GW adhere to a fixed scheduling mode, wherein the EN and GW know exactly when they are permitted to transmit data to each other. For example, this may be provided by a time division duplex (TDD) frame pattern that is fixed with a certain time period.
The EN and GW can exit from the D2D connected mode (e.g. Forte connected mode) when one or more of the following occurs: 1) both the EN and the GW send a D2D release request (e.g. a Forte RRQ); 2) after an inactivity timer (e.g. T_INACTIVITY in Forte) expires; and 3) after the EN and/or GW send the D2D connection response reject (e.g. Forte CRS reject) to each other.
At subframe (SF) #0, the GW sends D2D synchronization signals—one or more of D2D primary synchronization signals (DPSS), D2D secondary synchronization signals (DSSS) and D2D master information block (DMIB). It should be noted that DPSS, DSSS and DMIB are non-limiting examples of D2D synchronization signals. In this example, the three synchronization signals DPSS, DSSS and DMIB are transmitted when mod(SFN,10)=0.
At SF #5, the GW sends DPSS and DSSS for D2D synchronization. In this example, the two synchronization signals DPSS and DSSS are transmitted when mod(SFN,10)=5.
At SF #1, the EN sends the CRQ to the GW. Specifically, the EN sends the control indication for D2D (CID) connection request to the GW during the time period that the GW can receive the D2D signals. This time period can be referred to as the GW's reception opportunity (GW RO). In this case, the GW RO would be SF #1 to SF #4.
At SF #6, the GW, in response to the CRQ, sends the connection response (CRS) to the EN. Specifically, the GW sends the CID connection response to the EN. The CRS or the CID connection response includes an acceptance of the CRQ that the GW received from the EN in SF #1.
From SF #11 to SF #14, four grants (i.e. G1, G2, G3, G4) for four TB transmissions are transmitted to the GW. The fifth grant (i.e. G5) for the last TB transmission is transmitted to the GW at SF #21. Each grant sent to the GW may include MCS (modulation and coding schemes), resources or both.
When the grant for each TB transmission is transmitted, data (e.g. TB) is transmitted to the GW by the EN. For example, the first two TB transmissions (i.e. D1, D2) is done at SF #13 and SF #14, as the grants (i.e. G1, G2) for the TB transmissions are transmitted at SF #11 and SF #12, respectively. The remaining TB transmissions (i.e. D3, D4, D5) are similarly transmitted at SF #21 to SF #23.
Upon successful TB transmission, the GW sends, to the EN, an acknowledgement for each TB transmission. Specifically, the acknowledgements (i.e. A1, A2) for the first two TB transmissions are transmitted at SF #18 and SF #19. The remaining acknowledgments (i.e. A3, A4, A5) are similarly transmitted at SF #26 to SF #28.
When all TB transmissions are completed and acknowledged, the release request (RRQ) is transmitted from the EN to the GW at SF #31, and vice versa (i.e. from the GW to the EN) at SF #37. Upon transmission of the RRQ, the EN and GW exit from the connection mode.
There exists a Long D2D discontinuous reception (LG_DDRX) mode. In this mode, the D2D device sleeps for a certain period of time (e.g. LG_DDRX in SF) and then the D2D device wakes up for a period of time (e.g. the reception opportunity (RO)) for data reception. The LG_DDRX RO can be defined by Equation 1 below, which is based on the ID of the D2D device (e.g. Forte RNTI). For example, the RO can be defined as the one or more system frame numbers that satisfy Equation 1.
mod(FRAME_NUM,LG_DDRX)=HASH(RNTI)+ForteOffset (5)
where ForteOffset can be preconfigured and the HASH equation is specified or known.
If an EN and a GW are connected to the same cellular serving cell (e.g., the same BTS), the EN and GW can be synchronized (e.g. with up to 2 cyclic prefix (CP)) and therefore can establish a D2D connection therebetween (e.g. a Forte SL connection). However, if the EN and the GW are connected to different cellular serving cells (i.e. not engaged with the same cellular serving cells) and those cells are asynchronous (i.e. not synchronized), the EN cannot establish a D2D connection with the GW due to this lack of synchronization.
Some of the solutions that may be able to resolve the above issue are explained below. For example, the EN can obtain a timing offset between the serving cells from a D2D wireless network server (e.g. a Forte self-organizing network (SON) server), assuming that the timing offset is fixed. To obtain the timing offset, the EN establishes a cellular connection with the D2D wireless network server (e.g. Forte SON server). In order to contact the D2D wireless network server, the EN must be attached to the cellular network. However, merely using the cellular synchronization signal would not be sufficient to attach to the network since a cellular subscription is needed for that, which may not be always desirable. In another example, the GW sends out D2D synchronization signals (e.g. Forte SL synchronization (F-SS)). The EN can synchronize using the D2D synchronization signals transmitted by the GW. However, transmitting (e.g. broadcasting) D2D synchronization signals (e.g. Forte SL synchronization (F-SS)) has an impact on the battery power and system resources.
Various embodiments of the present disclosure provide a way of resolving the above issues. According to embodiments, the EN performs a deep search for all surrounding base transceiver stations (BTS) in all networks including all public land mobile networks (PLMNs). Put another way, the EN attempts to decode cellular synchronization signals from all possible BTSs. The longer correlation times, the higher the maximum coupling loss (MCL) that can result when cellular synchronization signals are decoded. Generally speaking, the higher MCL, the farther away the synchronization signals are being transmitted, namely the distance between the EN and that particular BTS is greater. The cellular synchronization signals that are decoded may include one or more of primary synchronization signal (PSS), secondary synchronization signal (SSS), master information block (MIB) and system information block (SIB).
The EN may receive cellular synchronization signals from multiple BTSs. As most cellular BTSs are synchronized within a few milliseconds (ms), the EN may not need to decode either the MIB in order to obtain the subframe number (SFN) or the SIB in order to obtain the hyper-frame. The EN can be synchronized with the BTS using the received cellular synchronization signals.
The EN can optionally prioritize the list of detected BTSs based on one or more of a pre-configured list of prioritized PLMNs or the quality of signal detection, which is indicative of the distance to the BTSs. For each detected BTS, the EN can attempt to discover a GW using that BTS's timing. In order to discover a GW, the EN, for example, may send out a D2D CRQ message. If the GW is attached to a particular BTS, the timing of the GW and the attached BTS will match. Provided that the EN can be synchronized with the BTS, the GW and the EN would then be synchronized through the attached BTS. Therefore, the GW with timing that matches the timing of the BTS (e.g. GW attached to the BTS) can receive the connection request from the EN and respond with a connection response message to the EN.
However, after a certain number of unsuccessful attempts, the EN can decide that there is no GW in range. The number of (unsuccessful) attempts to be made can be predetermined or dynamically configured. Upon the determination that no GW is in range, the EN can contact the D2D wireless network server (e.g. the Forte SON server) to obtain one or more of additional information (e.g. surrounding GWs, Offsets etc.) and receive instructions (e.g. to become a GW itself).
In the above embodiment, a cellular subscription is not frequently required in order to reach the D2D wireless network server, and thus costs associated therewith can be reduced.
Identifying GW using Cellular Synchronization Signal
The EN is usually aware of the ID of the GW before it makes a connection request (CRQ). For example, in Forte SL, the EN identifies the GW using the RNTI (i.e., GW ID) before sending a Forte CRQ. If the EN uses the cellular synchronization signal to synchronize with the GW without using the GW's D2D synchronization signal (e.g. F-SS) which normally carries the ID of the GW, the ID of the GW is unknown to the EN. Therefore, it is desired for the EN to be able to identify the ID of the GW (e.g. in Forte SL, RNTI of the GW) when the EN uses cellular synchronization signals.
According to embodiments, when the EN uses cellular synchronization signals, the EN can identify the ID of the GW using the D2D synchronization signals which may be infrequently transmitted by the GW to advertise the GW ID. In other words, the GW sends D2D synchronization signals (e.g. F-SS in Forte) in order to advertise its ID (e.g. RNTI in Forte) infrequently.
Specifically, the GW sends D2D synchronization signals with the GW ID every Nth reception occasion (RO). The Nth RO can be determined based on for example, LG_DDRX and/or GW ID. The selection of N for the Nth RO may also depend on one or more of the timing accuracy requirements of the RO and the timing accuracy capability of the EN. In some embodiments, alternately or additionally, the GW can, at selected times send D2D synchronization signals (which may contain the GW ID) based on one or more of the ID of the cellular BTS with which the GW (and the EN) is synchronizing, the ID of the GW, and the preconfigured D2D synchronization period. For example, the preconfigured D2D synchronization period can be X numbers of frames or N ROs.
Even if N=1, where the GW sends the D2D synchronization signal before every D2D RO, and the LG-DDRX is very long (for example in the range of 10 minutes), it can take a very long period of time for the EN to acquire the GW ID, since the EN has to decode many D2D channels for a very long time which consumes a lot of power. For example, if there are 10 D2D channels to search and LG-FDRX is 10 minutes, it could take up to 10×10=100 minutes to find the D2D synchronization signal. If the GW instead sends a D2D synchronization signal based on the cellular BTS ID and the D2D channel (not on the RO), since the EN also knows the BTS ID and D2D channel, it will know when the GW will send the D2D sync and not spend time looking for D2D sync at the wrong time. The 10 ms frame number when the GW is to send D2D sync and the EN is to search for D2D Sync is when the follow equality holds:
In the above embodiment, when more than one GW is synchronized to the same cell ID, they would be required to send D2D sync within the same SFN or frame number. Given a SFN is only 10 ms, there is a high chance of collision. To solve this a SEARCH_TIME can be introduced to reduce collisions of co-located GW D2D synchronization signals. The GW may autonomously decide which SFN within the SEARCH_TIME to send the D2D SYNC (i.e. the D2D_SYNC_LOCATION) or the SON controller may assign the location to ensure no collisions. The frame number (e.g., HSFN and SFN) for the EN to start to search for the SYNC is when:
The FRAME_NUM for the GW to send D2D sync is when:
With respect to the procedures performed at the EN, the EN can use the cellular synchronization signal to synchronize with the GW. The EN may not use the D2D synchronization signal that is transmitted infrequently for synchronization, at least in part due to the long synchronization process which can result in poor battery life and poor connection time. The EN can determine the approximate time that the GW will send the D2D synchronization signal based on the cellular BTS ID and the preconfigured D2D synchronization period. As such the EN may sleep and subsequently wake prior to the determined approximate time that the GW is to send the D2D synchronization signal. When the EN wakes up, the EN can search for the D2D synchronization signal at least for the (preconfigured) SEARCH_TIME. In some embodiments, when the EN detects multiple cellular synchronization signals and the EN can perform the above operations in parallel.
In some embodiments, the GW can send a shorter D2D synchronization signal when synchronization is not needed (i.e., when sync is done using other methods (e.g., using cellular sync signals) and when EN is not dependent on D2D sync signal for synchronizing with the GW) and the GW ID (e.g. GW RNTI) can be determined based at least in part on the cellular subframe on which the discovered D2D synchronization signal is decoded.
EN may be able to identify the ID of the GW (e.g. in Forte SL, RNTI of the GW) when the EN uses a cellular synchronization signal. According to embodiments, when the EN uses cellular synchronization signal, the EN can identify the ID of the GW through the CRQ connection requests on the discovery ID (e.g. D-RNTI).
In some embodiments, the GW listens for connection request using a discovery ID (e.g. D-RNTI) on a reception opportunity (RO), denoted as a discovery RO, in addition to the RO determined from the LG-DDRX. The time period of the discover RO is denoted as DISC_LG_DDRX. The DISC_LG_DDRX is typically much longer than the LG_DDRX in order not to use too much power. Although the longer DISC_LG_DDRX extends the time for discovery, this extended period of time may generally be acceptable as discovery occurs infrequently.
According to embodiments, without discovering the GW, the EN can determine one of more of the followings.
Mod(FRAME_NUM,DISC_LG_DDRX)=D-RNTI
It should be noted that using the discovery ID based on the GW's service cellular information may identify more than one GW responding to the CRQ. The multiple responses will occur when more than one GW is using the same cell for sync and thus will have the same discovery RO location. In such cases, the EN can attempt to discover the GW for each CRS that is decoded. As such, in various embodiments, the GW can randomize the CRS in both time and frequency, to avoid collisions.
Upon determining the discovery ID and the discovery period, the EN can determine the discovery RO on which the EN is to send the Connection requests CRQs, based on the discovery ID and discovery period determined in addition to the long discontinuous reception (DRX) rules.
The following is an example of the procedures performed at the EN.
Since the network devices (e.g. GW and/or EN and/or mesh node) are capable of performing both cellular and D2D communication, in some instances there can be collisions for example when one type of communication (e.g. D2D communication) occurs with respect to a device (e.g. GW) while that device is performing the other type of communication (e.g. cellular activity).
If a GW needs to perform some cellular activity while it is engaged in active D2D communications (e.g. Forte connected mode) with an EN, the D2D connection needs to be terminated in order to proceed with the cellular activity. However, it takes a long time to re-establish (or re-connect) the D2D communication after the cellular activity has completed. This re-connection time can take a long period because either the EN can be going into exponential back-off or the GW may have a long LG_DDRX cycle.
Some cellular activities have an approximately known duration and some cellular activities do not. Some non-limiting examples of cellular activities with known and unknown durations are provided below. It should be noted that the numbers in the brackets are merely examples of the approximate time duration needed to perform each activity.
According to embodiments, when the GW identifies or determines that there is an imminently upcoming cellular activity and the duration of that activity is approximately known, the GW terminates the D2D connection with the EN by transmitting an immediate release request (e.g. RRQ IR) to the engaged EN. In various embodiments, the immediate release request includes a field containing the time duration required to complete the cellular activity (e.g. T_BUSY). The time duration required to complete the cellular activity may be determined by the GW. In some embodiments, the time duration required to complete the cellular activity may be set slightly longer than the actual time duration needed for the cellular activity (e.g. the time duration, the GW knows for certain, that the activity can be completed).
Upon reception of the immediate release request (e.g. RRQ IR) with the time duration required to complete the cellular activity (e.g. T_BUSY), the EN sleeps for the received time duration required to complete the cellular activity (e.g. T_BUSY). After the time duration required to complete the cellular activity (e.g. T_BUSY), the EN wakes up and listens for a connection request for a pre-determined period (e.g., T_AVAIL). The pre-determined period for which the EN will listen for a connection request can be pre-configured or dynamically signaled. For example, the time period for a connection request (e.g. T_AVAIL) is included in the RRQ IR or dynamically signalled. The GW can re-initiate the connection after the time duration required to complete the cellular activity (e.g. T_BUSY) but within the time period for a connection request (e.g. T_AVAIL) by sending a connection request signal (e.g. CRQ) to the EN. It should be noted that the RRQ IR and the CRQ are control plane messages (for example a CID).
According to embodiments, when the GW identifies or determines that there is an imminently upcoming cellular activity but the duration of that activity is unknown, the GW terminates the D2D connection with the EN by transmitting an immediate release request (e.g. RRQ IR) to the engaged EN. In various embodiments, the immediate release request includes a field informing the EN of the imminently upcoming cellular activity that will be performed for an unknown duration (e.g. cellular activity unknown duration (CAUD)). Upon reception of the immediate release request (e.g. RRQ IR) with the field indicating the unknown duration cellular activity (e.g. CAUD), the EN enters into a short D2D DRX mode. In the short D2D DRX mode, the EN sleeps for a short D2D DRX cycle (i.e. SH_DDRX in SFs) and wakes up (e.g. transfers to wake up mode) for a short D2D RO duration. The short D2D DRX RO can be determined, for example in a similar manner to that of the long DRX mode. For example, the short D2D DRX RO is associated with the system frame number(s) as defined below, where the RNTI and SH_DDRX can be those associated with the EN or the GW.
mod(FRAME_NUM,SH_DDRX)=HASH(RNTI)+ForteOffset
where ForteOffset is preconfigured and the HASH equation is specified or known.
In various embodiments, the short D2D DRX cycle (i.e. SH_DDRX) can be associated with the EN, the GW or both, unless there is a specific indication that the SH_DDRX is to be associated with only one of the EN or the GW. The SH_DDRX can be pre-configured or signaled by the GW, for example within the RRQ IR. When the GW is ready to re-initiate the D2D connection, the GW sends a connection request signal (e.g. CRQ) to the EN during the short D2D DRX RO associated with the EN.
It should be noted that the SH_DDRX, which is typically 100˜500 ms, can be used instead of the LG_DDRX, which is typically 80 seconds ˜10 minutes, as the SH_DDRX can provide more opportunities for the GW to send the connection request signal (e.g. CRQ) with a smaller delay. In various embodiments, long D2D DRX mode can be used by the EN as this mode is the most power efficient. The EN transitions from long DRX mode to short D2D DRX mode when the EN is in D2D connected state. The EN is typically in a short DRX state (e.g. associated with short DRX mode) when the GW is in active cellular communication. Short D2D DRX mode can be used as per the methods and embodiments illustrated in the present disclosure. If long D2D DRX mode is used instead of short D2D DRX mode, there will be fewer opportunities for the GW to send the connection request signal (e.g. CRQ) and thus there will be more delay.
It should be further noted that simply shortening the value of LG_DDRX parameter to match the SH_DDRX parameter will proportionally increase the power consumption. For example, if the LG_DDRX is set to 100 milliseconds instead of 10 seconds, the power consumption of the LG DRX mode will increase by approximately 100 times (i.e. 10000/100). As many IoT (internet of things) applications transmit data infrequently, the EN would be in the Long DRX state most of the time (e.g. 99% of the time) and thus power optimization of the long DRX can be important.
According to embodiments, the procedures illustrated above (e.g. procedures in
Referring to
When the GW 501 identifies or determines that there is an (imminent) upcoming cellular activity for a known duration, T_BUSY, the GW 501 transmits an immediate release request (RRQ IR) to the engaged EN 502 to inform the EN of an imminently upcoming cellular activity that will be performed for the time period of T_BUSY. While the cellular activity is performed for T_BUSY, the GW 501 will be released from the D2D connected mode and the C-DRX is in an on state 540. Once the cellular activity of known duration is complete and after the time duration of T_BUSY, the GW 501 will return to the D2D connected mode 550 and the C-DRX is in an off state 560.
According to embodiments, in the case where the GW goes from cellular C-DRX back to cellular active (e.g. when the GW has data to send to the eNB or when the eNB has data to send to the GW), there is an additional EN procedure to be followed.
Referring to
According to some embodiments, the D2D connected mode may collide with a positive page (e.g. device terminated cellular data (e.g. mobile terminated (MT) cellular data)) that uses both short and long solutions. When the approximate time needed to decode the page message is known but the page is positive, the GW transitions to the RRC connected mode where the time to service is unknown. This situation can be supported by first transmitting immediate release request with the time duration required to complete the cellular activity (e.g. RRQ_IR with T_BUSY). If the GW is required to transition to the connected mode, the GW will send an immediate release request with a cellular activity of unknown duration (e.g. RRQ_IR with CAUD). An example of a cellular page procedure where a positive page is decoded and the GW needs to go to cell connected mode is illustrated in
When an EN wants to engage in active D2D communications (e.g., EN was not in D2D connected mode before and wishes to establish D2D connection with the GW now) while the GW is performing a cellular activity, the EN will not receive a response to its connection requests and therefore will go into exponential back-off which may result in multiple sequential access failures. These sequential failures can cause problems including one or more of wasted spectral resources, delayed transmission time, and the like. Therefore, optimization of the connection access method can be necessary. An example case where multiple sequential access failures occur due to the exponential back-off of the EN is illustrated in
In order to solve the issue of multiple sequential access failures, in various embodiments, the EN continues decoding for a longer period of time when the duration of the cellular activity is short. This decoding period may be longer than the time that would normally be taken for transmission of a connection response (CRS) (e.g. 10 ms). In some embodiments, the decoding period may be extended by the CRS timeout (CRS_TO) period. During the CRS_TO period, the EN will be searching for a CRS, a D2D available message (DAM) or both. The DAM can be sent by the GW after the cellular activity is complete. In some embodiments, the DAM is a control plane message (e.g. CID) that is broadcasted by the GW and is decodable by any EN. In such cases, the destination ID of the DAM may be a broadcast ID or GW ID. Upon receipt of the DAM, the EN transmits the CRQ to the GW. In order to avoid collision, the EN may randomly delay transmission of the CRQ until after reception of DAM. The transmission of the CRQ may be delayed up to the available time for DAM transmission (DAM_AVAIL), wherein DAM_AVAIL may be predetermined or dynamically signalled.
The delayed transmission of the CRQ illustrated above (e.g. procedure illustrated in
The following procedure is performed when the GW is in active connected mode for a longer period of time, for example longer than the CRS_TO. According to some embodiments, the short DRX used by the EN is based on the GW's ID (e.g. GW RNTI) and the period is based on the GW's short D2D DRX cycle (e.g. GW's SH_DDRX) and the RO is based on the GW's ID (e.g. GW RNTI). The GW's SH_DDRX can be pre-configured or signaled (for example dynamically) to the EN during an earlier D2D communication. The DAM is sent, by the GW during GW RO based on the GW's ID and SH_DDRX, after the cellular activity is complete. In some embodiments, the DAM is a control plane message (e.g. CID) that is broadcasted by the GW and is decodable by any EN. In such cases, the destination ID of the DAM may be a broadcast ID or GW ID. Upon receipt of the DAM, the EN transmits the CRQ to the GW. In order to avoid collisions, the EN may randomly delay transmission of the CRQ after reception of DAM. The transmission of the CRQ may be delayed up to the available time for DAM transmission (DAM_AVAIL). The remaining steps are substantially similar as those in the procedure where the GW is engaged with a short cellular activity, as illustrated above.
After the CRS_TO 1060, the EN 1002 sleeps for the GW's 1001 short D2D DRX cycle, the SH_DDRX 1070a. The EN 1002 wakes up during the GW's 1001 RO 1080a. As the cellular activity 1050 is not completed during the RO 1080a and since the GW has not sent DAM, the EN 1002 sleeps again for the SH_DDRX 1070b. When the EN 1002 wakes up again, at this time the cellular activity 1050 is complete. As such, the GW 1001 can send (e.g. directly transmit or broadcast) the DAM 1020 to the EN 1002 during the RO 1080b. Upon receipt of the DAM 1020, the EN 1002 transmits the CRQ 1010b to the GW 1001. Put another way, the transmission of the CRQ 1010b is delayed until the EN 1002 receives the DAM 1020. While the transmission of the CRQ 1010b can be further delayed (e.g. transmission is randomly backed off), the CRQ 1010b is sent within the DAM_AVAIL 1040. Upon receipt of the CRQ 1010b, the GW 1001 sends the CRS 1030 to the EN 1002.
An alternative example of the delayed transmission of a CRS when the GW is engaged with a long cellular activity is illustrated in
According to embodiments, an alternate way of suspending D2D activity during cellular activity is by changing the way the D2D time resources are allocated during cellular activity. In most D2D protocols, time slots for transmission between a GW and an EN are assigned in a fixed scheduling pattern. For example, a time slot is assigned for transmission from a GW to an EN and a different time slot is assigned after a beacon for transmission from the EN to the GW. For example, time slots for transmission between a GW and an EN are assigned in a time division duplex (TDD) pattern. However, such rigid time resource allocation is not applicable while the GW is performing cellular activity, as the time slots or subframes, which are available for D2D transmission (e.g. switch subframes and decoding subframes), are dynamic. To resolve this problem, according to embodiments, the GW allocates resources dynamically to the EN. Dynamic resource allocation is possible because the GW determines when time resources can be allocated for D2D communications. In various embodiments, the GW transmits control plane messages to the EN in order to indicate which scheduling mode EN should be in (e.g. dynamic scheduling mode (DSM) or fixed scheduling mode (FSM)), as illustrated in
In LTE-M (or NB-10T (narrowband internet of things)), D2D traffic can be transmitted at least during “switch” subframes. In other words, a switch SF is a SF used to allow a half duplex frequency division duplex (HD-FDD) radio to switch from uplink (UL) to downlink (DL) or from DL to UL (e.g. switching between acting as a transmitter and a receiver). The GW can predict when a switch SF is present by examining the cellular grants that it receives. In LTE-M (and NB-IOT), there are predetermined delays between grants, data and acknowledgments (ACKs).
The procedure is similar to a case when UL traffic is sent using cellular communications, as illustrated in
For NB-IoT, switching times and scheduling delays are longer than those of LTE-M. Therefore, the HD-FDD radio switches slower than in LTE-M.
Those skilled in the art would readily understand that the above LTE-M techniques for determining when future resources are available for D2D transmission are applicable to other cellular protocols such as narrow band IOT (NB-IOT), LTE or new radio (NR).
If a D2D EN attempts to connect with a GW during GW RO when the GW is in an active D2D communication with another EN, this connection request will fail and the EN will execute exponential back-off which may result in multiple sequential access failures.
Upon decoding the DNAM 1625 that the EN 1603 receives in response to the CRQ 1615, the EN 1603 goes into short D2D DRX mode and sleeps for short D2D DRX cycle, the SH_DDRX 1620a. The EN 1603 wakes up during the short D2D RO 1630a and waits for the CRQ 1635 to be receive from the GW 1602. However, as the GW 1602 is still in D2D connected mode (e.g. the GW 1602 is still actively communicating with the EN 1601), the EN 1603 does not receive the CRQ 1635 during this time period and sleeps again for the SH_DDRX 1620b. When the EN 1603 wakes up again during the short D2D RO 1630b, the active communication between the EN 1601 and the GW 1602 is completed, and therefore the EN 1603 receives the CRQ 1635 from the GW 1602. In response, the EN 1603 transmits the CRS 1645 to the GW 1602.
While not specifically illustrated in
The following illustrates an example set of procedures for resolving collision issues, for example when one type of communication (e.g. cellular activity) occurs to a device (e.g. GW) while that device is performing the other type of communication (e.g. D2D communication between the GW and EN), in accordance with embodiments of the present disclosure.
According to embodiments, the actions of the GW can be determined based on whether the GW is in D2D connected mode with an EN and whether the duration of the GW's cellular activity is known. If the GW is in D2D connected mode with an EN (e.g. Forte connected mode) and GW has to transition to cellular active mode where the duration of the GW's cellular activity is known, the GW can send a D2D immediate release request (RRQ_IR) with the time duration (or approximation thereof) required to complete the GW's cellular activity (T_BUSY). The time duration required to complete the cellular activity may be determined by the GW. In order to improve reliability, in some embodiments, the GW sends more than one D2D RRQ_IR. After transmitting the RRQ_IR, the GW, with regards to the D2D communication, waits for the T_BUSY to expire. If the cellular activity is complete after T_BUSY, the GW sends a D2D connection request (CRQ) to the previously connected EN to re-initiate the D2D connected mode (e.g. Forte connected mode). If the cellular activity is not complete after T_BUSY, the above procedure may be repeated (e.g. start with sending an RRQ_IR).
If the GW is in D2D connected mode with an EN (e.g. Forte connected mode) and GW has to transition to cellular active mode where the duration of the GW's cellular activity is not known, the GW sends a D2D immediate release request (RRQ_IR) with the data indicative of an imminently upcoming cellular activity with an unknown duration (e.g. CAUD). In some embodiments, the RRQ_IR optionally further contains the data indicative of the short D2D DRX cycle (e.g. SH_DDRX). After transmitting the RRQ_IR, the GW, with regards to the D2D communication, waits for completion of the cellular activity. When the cellular activity is complete, the GW sends a D2D connection request (e.g. Forte CRQ) to previously connected EN at short D2D DRX RO (e.g. short Forte DRX) in order to re-initiate the D2D connection with the EN.
If the GW is not in D2D connected mode with an EN (e.g. Forte idle mode or Forte long DRX) and the GW is engaged in cellular activity, there will not be a D2D reception opportunity (e.g. Forte RO) due to the GW's cellular activity, which would result in collisions with D2D reception opportunity. In this case, the GW will wait for the cellular activity to be completed. If the duration of the cellular activity is shorter than the CRS timeout (CRS_TO), the GW will send a D2D available message (DAM) immediately after the cellular activity is completed. If the duration of the cellular activity is equal to or longer than the CRS_TO, then the GW will send a DAM during the first RO of the short DRX, after the cellular activity is completed.
According to embodiments, the actions of the EN would be determined based on whether the EN is in D2D connected mode with the GW and whether the EN receives the known duration of the GW's cellular activity. If the EN is in D2D connected mode with the GW and receives a D2D immediate release request (RRQ_IR) (e.g. Forte RRQ-IR) with the time duration (or approximation thereof) required to complete the GW's cellular activity (T_BUSY), the EN immediately exits from the D2D connected mode (e.g. Forte connected mode). Then, the EN goes to sleep for T_BUSY. After T_BUSY, the EN wakes up and listens for a D2D connection request for a pre-determined period (T_AVAIL). T_AVAIL may be included in the RRQ_IR or dynamically signalled. If the D2D connection request (e.g. Forte CRQ) is received within the T_AVAIL, then the EN sends a D2D connection response with an acceptance of the connection request (e.g. Forte CRS with accept) to re-establish the D2D connected mode (e.g. Forte connected mode). If the D2D connection request (e.g. Forte CRQ) is not received within the T_AVAIL and a D2D available message (DAM) is received, the EN may randomly back off the procedure up to the available time for DAM transmission (DAM_AVAIL). Put another way, the EN may randomly delay transmission of a D2D connection request (e.g. Forte CRQ) up to DAM_AVAIL in order to re-establish the D2D connected mode (e.g. Forte connected mode). If the D2D connection request (e.g. Forte CRQ) is not received within the T_AVAIL and a D2D available message (DAM) is not received, but a D2D immediate release (e.g. Forte RRQ-IR) is received, then the EN can re-start the procedure with an assumption that the EN is in the D2D connected mode (e.g. Forte connected mode). In other words, the EN re-starts the process. If nothing is received within the T_AVAIL (e.g. the D2D connection request (e.g. Forte CRQ), a D2D available message (DAM) and a D2D immediate release (e.g. Forte RRQ-IR) are not received, the EN enters into a short D2D DRX mode (e.g. short Forte DRX). Upon the short D2D DRX timeout (e.g. short Forte DRX timeout), the EN re-initiates connection access procedures, as illustrated above or elsewhere in the present disclosure.
According to embodiments, if the EN is in D2D connected mode with the GW and receives the RRQ_IR with the data indicative of an imminently upcoming cellular activity with an unknown duration (CAUD) instead of the RRQ_IR with T_BUSY, the EN enters into a short D2D DRX mode (e.g. short Forte DRX). Upon the short D2D DRX timeout (e.g. short Forte DRX timeout), the EN re-initiates connection access procedures, as illustrated above or elsewhere in the present disclosure.
According to embodiments, during the GW's D2D reception opportunity (e.g. Forte RO), if the D2D connected EN is configured by higher layers (e.g. components in higher layers), the EN will not transmit to the GW during the GW's Long DRX D2D RO.
It may be noted that the short D2D DRX timeout (e.g. short Forte DRX timeout) can a predetermined time period (e.g. preconfigured and/or dynamically signaled). When the EN enters into a short D2D DRX mode, this timeout period can be activated. After the expiry of this timeout period, the EN can go into one or both of exponential back-off and re-initiate connection access procedures, as illustrated above or elsewhere in the present disclosure.
According to embodiments, the GW is able to transmit a release request (RRQ) and transition to the active cellular connected mode before cellular operation is started. The procedures illustrated above with a known cellular activity duration would not cause the GW to delay the cellular activities, as the duration of the cellular activity, tracking area update (TAU) and system information block (SIB) are known in advance. For device terminated data (e.g. response to a positive page message), the device (e.g. GW etc.) can initiate a RRC connection in a timely manner. However, there is no strict cellular requirement (e.g. <100 ms). For device originated data, there is no defined cellular timing requirement however latency can result if there is a delay in the transmission of a RRQ and transition from the D2D connected mode to the active cellular connected mode. In various embodiments, hard timing requirement for transmission of RRQ and transition from the D2D connected mode to the active cellular connected mode is typically not required. However, generally it can be considered that a time period of <100 ms may be desired.
It is understood that the 863-870 MHz unlicensed frequency range is an important band for use of D2D, as it is unlicensed and is a relatively low frequency band compared to other unlicensed bands (e.g. 2.5 GHz). These frequency ranges (e.g. 863-870 MHz) are also within the cellular bands. Therefore, most IoT cellular modules can support these frequency ranges without any additional hardware (e.g. low-noise amplifier (LNA)/power amplifier (PA)). However, for example in Europe, the use of this frequency range (863-870 MHz) is tightly regulated. Regulation items includes device category, start and end frequency of bands defined within the 863-870 MHz frequency range, signal bandwidth, transmit power, duty cycle and spectrum access.
For example, pursuant to the duty cycle regulations, the cumulated sum of air transmission time of a device during an observation period (for example listening period or the ON period of the device) may be restricted to e.g., one hour within a specific frequency band. Duty cycle restrictions can be relaxed in the case of polite spectrum access (PSA). PSA is a technique to access spectrum and mitigate interference by employing a clear channel assessment (CCA). PSA encompasses a listen before transmit (LBT) mechanism to which a device applies a clear channel assessment (CCA) before transmission. The CCA is a mechanism for determining whether the band is idle or not. To be considered “idle”, the signal strength within the frequency band needs to be below a threshold for a certain period of time.
In light of the duty restrictions, there are problems when transmitting data via unlicensed frequency bands. In the case of transmission without PSA, the duty cycle restrictions apply to an entire band defined in the frequency range of 863-870 MHz. For example, Band 47 spans from 865 MHz to 868 MHz and is subject to a 1% duty cycle. If a system uses, for example, two 200 KHz signals within the ranges from 865.0 MHz to 865.2 MHz and from 866.0 to 866.2 MHz, the 1% duty cycle restriction applies to the aggregated traffic over those two frequency ranges. This can limit the overall traffic that can be migrated in the band.
Moreover, the PSA illustrated in the European norm ETSI EN 300 220-1, hereinafter referred to as ETSI document, has a minimum off-time parameter that requires a transmitter to remain off after a transmission on the same operating frequency for 100 milliseconds. This can lead to unacceptable transmission gaps for devices. For example, if a D2D side link (SL) protocol operates in active cellular transmission, the devices can use only intermittent transmission opportunities for D2D SL communication. The transmission opportunities can be scarce and typically less than 100 milliseconds apart.
Other technologies operated in the 863-870 MHz frequency range in Europe such as SigFox™ and LoRa™ assume that traffic can be accommodated under the duty cycle restrictions. For example, Band 54, which permits a 10% duty cycle, is used for downlink (DL) transmission and Band 48, which permits a 1% duty cycle, is used for uplink transmission. This can account for the traffic imbalance among individual uplink and downlink transmitters in a star network architecture. However, Band 54 is only 250 kHz wide, and therefore data transmission is significantly limited. Moreover, it is predicted that the duty cycle restrictions will become further stringent due to higher traffic demands by applications (e.g. mobile applications).
According to the ETSI document, the PSA permits a maximum duty cycle of 2.78% per 200 kHz. A frequency agile system using multiple 200 kHz portions of the frequency spectrum can increase the aggregate duty cycle, for example to 41.6% in a 3 MHz band. However, there is no solution of how to accommodate primary sub-bands and secondary sub-bands with different signal bandwidths associated with different data rate demands. Primary sub-bands may include additional information (e.g., one or more of D2D sync signals, spectrum configuration, configuration of secondary sub-bands, control information and data) and such additional information may not be present in the secondary sub-bands.
PSA with Dynamic Bandwidth
Division of the frequency band into smaller sub-bands is a method for increasing the duty cycle (=number of sub-bands×2.78%). However, while many factors can affect the size and the number of the sub-bands, it is unclear how to determine the optimal size and the number of the sub-bands. It is also unclear how these sub-bands can operate within a device that supports both D2D communication and cellular communications.
According to embodiments, the polite spectrum access (PSA) is utilized with network-wide synchronized frequency agility that is adjusted to the requirements of primary and secondary sub-bands. The minimum granularity is a bandwidth B, the bandwidth used to define the duty cycle for PSA. For example, in accordance with the European standard provided in the ETSI document, the bandwidth B may be 200 kHz. The successive transmissions from the same device may respect the required off-time, Toff. For example, in accordance with the European standard provided in the ETSI document, Toff may be 100 milliseconds.
In various embodiments, the transmitting device switches between operating bands and transmitting signals in different bandwidths in order to achieve the desired data rates (short-term target) and maximize the effective duty cycle (long-term target).
In some embodiments, the bandwidths of the secondary sub-bands 1720, 1730 and 1740 are same as illustrated in
Further referring to
Each of TABLE 1 and TABLE 2 provide example relative peaks and sustained data rates for the three bandwidth options for data signals illustrated in
Referring to TABLE 1 and TABLE 2 presented above, the BW reduction factor at a given signal-to-noise ratio (SNR) can be calculated using the formula of
In TABLE 1 and TABLE 2, the BW reduction factor can be determined, using the 6PRB band as a reference, as follows:
Regarding the scheduling efficiency, in the high SNR case, the scheduling efficiency was calculated with an assumption that 1 PRB is needed to schedule a data packet. In the low SNR case, the scheduling efficiency was calculated with an assumption that 2 slots are needed to schedule a data packet and 16 repeats are needed for the data packet. As a result, an efficiency of 89% (i.e. 16/18) is obtained for all low SNR cases.
Regarding the peak activity per band, the peak activity per band can be defined as the ratio of activity per band defined by a percentage (%).
Regarding the peak rate, the relative peak data rate covers all bands. However, it does not necessarily adhere to the regulatory limitation (i.e. 2.8% per band). The peak rate can be determined using the following equation:
Peak rate=(Number of bands)×(BW reduction factor)×(Scheduling efficiency)×(Peak activity per band)
Regarding the sustained activity per band, the sustained activity per band can be 2.8% per band pursuant to the regulatory requirements.
Regarding the sustained activity, the sustained activity is defined as a percentage (%) indicative of the time of activity in total. The sustained activity can be calculated as 2.8%×(number of bands).
Regarding the sustained rate, the sustained relative data rate covers all bands and adheres to the regulatory limitation (i.e. 2.8% per band). The sustained rate can be determined using the following equation:
Sustained rate=(Number of bands)×(BW reduction factor)×(Scheduling efficiency)×(Peak activity per band)
Further referring to TABLE 1 and TABLE 2 presented above, it is observed that the peak data is better for the 3PRB bands than for the 1 PRB band. However, the sustain rate is better for the 1PRB bands than for the 3 PRB bands. Specifically, in the high SNR case, the peak data is significantly better for the 3PRB bands than for the 1 PRB bands, and the sustain rate is slightly better for the 1PRB bands than for the 3 PRB bands. On the other hand, in the low SNR case, the peak data is slightly better for the 3PRB bands than for the 1 PRB bands, and the sustain rate is significantly better for the 1PRB bands than for the 3 PRB bands. This comparison signifies that one bandwidth is not optimal for all SNR ranges, peak rate requirements or sustained data rate requirement. Therefore, configuration is needed.
In various embodiments, based on the numerical results provided in TABLE 1 and TABLE 2, the optimal configuration can be determined by considering one or more of the followings.
the data rate gain due to BW would depend on the SNR experienced in the link. Scheduling efficiency: Scheduling efficiency affects all rate figures. In general, as the amount of spectrum decreases, the scheduling efficiency goes down as scheduling overhead is generally constant.
As stated above, provided that a device is capable of performing both D2D and cellular transmissions with a single radio, D2D transmission can be bound by spectrum transmission rules (i.e. regulatory rules) which at least include the maximum percent transmission time per frequency range and the minimum off-time after transmission per frequency range.
For effective D2D data transmission (e.g. potential optimal performance) pursuant to the spectrum transmission rules, in various embodiments, the bandwidth of the signaling sub-band (e.g., primary sub-band) is pre-configured, and signaling includes at least synchronization information (e.g. D2D PSS, SSS, PBCH), configuration of other sub-bands, and configuration of duplexing protocol (e.g. TDD). The configuration of other sub-bands (e.g., secondary sub-bands) includes configuring at least one or more of: number of sub-bands, bandwidth (of the sub-bands), time (for example, hopping pattern), and location within the spectrum.
According to embodiments, the configuration of the number of sub-bands and bandwidth of the sub-bands can consider one or more of the followings:
The polite spectrum access (PSA) implies performance of the clear channel assessment (CCA). The CCA needs to be performed on the bandwidth B in accordance with the applicable PSA mechanism (e.g. B=200 kHz). Whenever there is a narrow band interferer (e.g. 100 kHz) within the D2D transmission bandwidth (e.g. 1 MHz), the CCA will fail and the D2D transmission will be suspended. This can be considered to be an inefficient use of spectrum.
According to embodiments, the bandwidth used for the CCA does not need to be equal to the bandwidth of the D2D transmission signal. If the transmission bandwidth is larger than bandwidth B (i.e. 200 kHz), for example as illustrated in
In various embodiments, the optimal configuration can be determined considering one or more of the followings.
As stated above, provided that a device is capable of performing both D2D and cellular transmissions with a single radio, D2D transmission is bound by spectrum transmission rules (i.e. regulatory rules). The transmission rules at least include the maximum percent transmission time per frequency range, the minimum off-time after transmission per frequency range, and the limitation that devices can transmit only after the clear channel assessment (CCA) is successfully performed.
For more effective D2D data transmission (e.g. optimal performance) pursuant to the spectrum transmission rules, in various embodiments, the CCA bandwidth is configured as a sub-band of the maximum D2D transmission bandwidth. As such, the CCA bandwidth is configured to be smaller than the maximum D2D transmission bandwidth. Therefore, multiple CCA sub-bands are processed to cover the maximum D2D transmission bandwidth. In various embodiments, D2D transmission is suspended only for those sub-band frequency ranges where the CCA was not successful. The CCA bandwidth can be optimized in consideration of at least one of more of: spectrum transmission rules, the bandwidth of the signaling sub-band (e.g. bandwidth of each sub-band), data rates required in short and long terms, average signal-to-noise ratio (SNR), and scheduling efficiency.
When a cellular modem device is in active transmission mode, there are only small sporadic gaps (e.g. 1 millisecond) that can be used for D2D transmission. With the PSA off-time requirement (e.g. Toff), the D2D transmission would be suspended after a short transmission for a longer period of time. For example, the D2D transmission is suspended for 100 milliseconds after transmitting only a very small amount of data for 1 millisecond. This can result in a very low D2D data rate.
According to embodiments, the D2D transmission is performed by dividing a physical device into two logical D2D devices. The two logical D2D devices are the device-NPSA (for Non-PSA operation) and the device-PSA (for PSA operation). The two logical D2D devices are time multiplexed based on certain factors.
In some embodiments, the device-PSA is used for D2D transmission when the cellular modem device is in idle mode (i.e. not actively transmitting), in order to make use of the increased duty cycle allowed by PSA. The device-NPSA is used for D2D transmissions when the cellular modem device is in active cellular transmission mode as such usage can avoid the issue of the regulatory off-time imposed by PSA. The device-PSA can be also used to solve other problems illustrated above or elsewhere in the present disclosure.
In some embodiments, if the device-NPSA and the device-PSA operate in the same band (within one band) (e.g. Band 47), the two logical D2D devices may use non-overlapping frequency ranges or overlapping frequencies. If the device-NPSA and the device-PSA operate in different bands (across the bands) (e.g. in Bands 47 and 84), the frequency ranges for these bands are non-overlapping.
As stated above, provided that a device is capable of performing both D2D and cellular transmissions with a single radio, D2D transmission is bound by spectrum transmission rules (i.e. regulatory rules). The spectrum transmission rules at least include two D2D modes. One of the two D2D modes is the PSA mode. In the PSA mode, the spectrum transmission rules at least include the maximum percent transmission time per frequency range, the minimum off-time after transmission per frequency range, and the limitation that devices can transmit only after the clear channel assessment (CCA) is successfully performed. The other mode is the non-PSA mode. In the non-PSA mode, a maximum transmission duty cycle is applied.
In various embodiments, the device can operate in both D2D modes (i.e. PSA and non-PSA modes). In some embodiments, the device alternately operates in the two D2D modes. The two D2D modes may use the same or different regulated bands. The D2D operating mode may be determined based at least on one or more of: the cellular operation mode, spectrum transmission rules, data rates required in short and long terms, and average signal-to-noise ratio (SNR). Regarding the cellular operation mode, the device may operate in PSA mode if the cellular modem device is in idle mode, and operate in non-PSA mode if the cellular modem device is in active cellular transmission mode.
According to embodiments, the polite spectrum access (PSA) is utilized with dynamic bandwidth. This can increase D2D duty cycle for example from 2.78% up to 33.6% (i.e. 2.78%×12) using 12 sub-bands of 1 PRB.
According to embodiments, the CCA can be performed at sub-bands smaller than the transmission bandwidth, and this can improve spectral efficiency. For example, with a 100 kHz interferer operation at 50%, a D2D transmission BW of 6PRB and CCA BW of 1PRB, spectrum utilization is improved from 50% to 91.7% (i.e. 50+5/6×50).
According to embodiments, using the hybrid transmission with and without PSA illustrated above, the resulting duty cycle can be increased from 1% as shown using the following assumptions:
According to embodiments, using the hybrid transmission mode with and without PSA illustrated above, the maximum duty cycle can be calculated as a combination of NPSA used 5% of the time and PSA used 95% of the time. When operation in PSA, the resulting D2D transmission duty cycle would be 8.34% (3×2.78%). When operating in the NPSA mode, the long term duty cycle is 0.5% (5%×1SF/10SF) which is less than 1% thus the regulatory limit of 1% does not need to be applied. The resulting maximum aggregated duty cycle for the hybrid transmission mode is 95%*8.34%+5%*0.5%=7.923+0.025=7.948%.
As will be readily understood by the worker skilled in the art, the figures and the accompanying detailed description are for illustrative purposes. It will be readily understood that for example if a figure identifies a gateway (GW) or an end node (EN), either of these network devices may be envisioned as another configuration of a network device, for example a mesh node or other configuration. It will also be readily understood that, for example, if a figure illustrates cellular activity when a gateway drops a D2D communication, this is to be considered merely as an example. The communication that is dropped may equally be considered to be a cellular communication or a second D2D communication or other type of wireless communication as would be readily understood. It my be further envisioned that another D2D communication or other wireless communication type may be enabled when a gateway drops a D2D communication.
In some embodiments, establishing the D2D connection includes transmitting the D2D CRQ and receiving the D2D CRS with acceptance prior to transitioning to the D2D connected mode.
In some embodiments, when the GW and the EN are engaged with two asynchronous cellular serving cells, the method further includes synchronizing the EN and the GW. Synchronizing includes detecting, by the EN, surrounding base transceiver stations (BTSs) and discovering, by the EN, the GW attached to one of the detected BTSs. In some embodiments, synchronizing further includes prioritizing, by the EN, the detected BTSs based on one or more of a pre-configured list of prioritized public land mobile networks (PLMNs) and a quality of signal detection.
In some embodiments, the EN synchronizes with the GW using a cellular synchronization signal. In some embodiments, the EN identifies the GW using a D2D synchronization signal transmitted by the GW. In some embodiments, the GW transmits the D2D synchronization signal every Nth reception occasion (RO), wherein the N is indicative of one or more of a timing accuracy requirement of the RO and a timing accuracy capability of the EN.
In some embodiments, the GW identifies an imminent upcoming cellular activity during the D2D connected mode. The method further includes terminating the D2D connection between the EN and the GW using an immediate release request (RRQ IR) and re-establishing the D2D connection between the EN and the GW.
In some embodiments, the imminent upcoming cellular activity has a known duration. The method further includes transmitting, from the GW to the EN, a D2D immediate release request including an indication of the known duration of the cellular activity and upon receiving the D2D immediate release request, transitioning, by the EN, to a sleep mode for the known duration. Upon completion of the cellular activity, the method further includes transitioning, by the EN, to a wake up mode and transmitting, from the GW to the EN, the D2D CRQ to re-establish the D2D connection within a connection request time period.
In some embodiments, the method further includes transmitting, from the GW to the EN, a D2D immediate release request with the field indicating that the imminent upcoming cellular activity has an unknown duration. Upon receiving the D2D immediate release request, the method further includes transitioning, by the EN, to a short D2D discontinuous reception (DRX) mode for a short D2D DRX cycle and to a wake up mode for a short D2D reception opportunity (RO) duration. The method further includes repeating the transitions if the cellular activity is not complete during the short D2D RO duration. Upon completion of the cellular activity, the method further includes transmitting, from the GW to the EN, the CRQ to re-establish the D2D connection during the wake up mode.
In some embodiments, during the listening mode, upon the D2 identifying a need for a third communication, transmitting by the D2, a second DNAM. In some embodiments, one or more of the DNAM and the second DNAM are transmitted to one or more of a plurality of devices, wherein the plurality of devices includes at least the D1. In some embodiments, transitioning to the listening mode includes transitioning, by the D1, to a power saving mode, wherein the D1 sleeps for at least one sleep period upon transition to the power saving mode. In some embodiments a duration of the sleep period is specified in one or more of the DNAM and the second DNAM. In some embodiments, upon expiry of the sleep period, the D1 listens for one or more of the second DNAM or the DAM for a receive mode period. In some embodiments, upon non-receipt of the DAM or the second DNAM before expiry of the receive mode period, transitioning, by the D1, to a short power saving mode, wherein the D1 sleeps for a short sleep period during the short power saving mode. Upon expiry of the short sleep period, listening, by the D1, for one or more of the DAM and the second DNAM during a short wake up period.
In some embodiments, one or more of the DNAM and the second DNAM indicate whether one or more of the second communication or the third communication has a known duration.
In some embodiments, transitioning to the listening mode includes transitioning, by the D1, to a short power saving mode, wherein the D1 sleeps for a short sleep period during the short power saving mode and upon expiry of the short sleep period, listening, by the D1, for the DAM or the second DNAM during a short wake up period. In some embodiments, the short sleep period has a duration, the duration is one or more of: a preconfigured period, a period signalled by the D2 and a period calculated based on a known formula. In some embodiments, the short sleep period is signalled by the D2 within the DNAM. In some embodiments, upon the D1 receiving the DAM, transmitting, by the D1, a message to the D2.
As shown, the device includes a processor 2110, memory 2120, non-transitory mass storage 2130, I/O interface 2140, network interface 2150, and a transceiver 2160, all of which are communicatively coupled via bi-directional bus 2170. According to certain embodiments, any or all of the depicted elements may be utilized, or only a subset of the elements. Further, the device 2100 may contain multiple instances of certain elements, such as multiple processors, memories, or transceivers. Also, elements of the hardware device may be directly coupled to other elements without the bi-directional bus.
The memory 2120 may include any type of non-transitory memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), any combination of such, or the like. The mass storage element 2130 may include any type of non-transitory storage device, such as a solid state drive, hard disk drive, a magnetic disk drive, an optical disk drive, USB drive, or any computer program product configured to store data and machine executable program code. According to certain embodiments, the memory 2120 or mass storage 2130 may have recorded thereon statements and instructions executable by the processor 2110 for performing any of the aforementioned method steps described above.
It will be appreciated that, although specific embodiments of the technology have been described herein for purposes of illustration, various modifications may be made without departing from the scope of the technology. The specification and drawings are, accordingly, to be regarded simply as an illustration of the invention as defined by the appended claims, and are contemplated to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present invention. In particular, it is within the scope of the technology to provide a computer program product or program element, or a program storage or memory device such as a magnetic or optical wire, tape or disc, or the like, for storing signals readable by a machine, for controlling the operation of a computer according to the method of the technology and/or to structure some or all of its components in accordance with the system of the technology.
Acts associated with the method described herein can be implemented as coded instructions in a computer program product. In other words, the computer program product is a computer-readable medium upon which software code is recorded to execute the method when the computer program product is loaded into memory and executed on the microprocessor of the wireless communication device.
Acts associated with the method described herein can be implemented as coded instructions in plural computer program products. For example, a first portion of the method may be performed using one computing device, and a second portion of the method may be performed using another computing device, server, or the like. In this case, each computer program product is a computer-readable medium upon which software code is recorded to execute appropriate portions of the method when a computer program product is loaded into memory and executed on the microprocessor of a computing device.
Further, each step of the method may be executed on any computing device, such as a personal computer, server, PDA, or the like and pursuant to one or more, or a part of one or more, program elements, modules or objects generated from any programming language, such as C++, Java, or the like. In addition, each step, or a file or object or the like implementing each said step, may be executed by special purpose hardware or a circuit module designed for that purpose.
It is obvious that the foregoing embodiments of the invention are examples and can be varied in many ways. Such present or future variations are not to be regarded as a departure from the spirit and scope of the invention, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.
This application claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 63/218,658 entitled “Method and Apparatus for Managing Device to Device Communications in a Wireless Network” filed Jul. 6, 2021 and U.S. Provisional Patent Application Ser. No. 63/235,573 entitled “Method and Apparatus for Managing Device to Device Communication” filed Aug. 20, 2021, the contents of which are hereby incorporated by reference in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CA2022/051060 | 7/5/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63235573 | Aug 2021 | US | |
| 63218658 | Jul 2021 | US |
