The present invention relates to sidelink relay operations in wireless communications, and more specifically to a mechanism for a Relay indication transmission procedure or a Sidelink User Equipment (UE) information transmission procedure related to a sidelink Relay operation.
Proximity-based Services (ProSe) or Device-to-Device (D2D) services, which will enable devices to communicate each other directly, will provide valuable service for both public safety and non-public safety purposes. The benefits of D2D include, but are not limited to, improving the spectrum efficiency and overall throughput, reducing terminal's power consumption and providing a new type of peer to peer services.
Typical D2D applications include, but are not limited to, public safety, network offloading, etc. Additionally, D2D communication is one of the key features of 3GPP Release 12. In 3GPP Release 12, D2D has standardized support for a subset of features including:
Additionally, D2D will continue its evolution in a 3GPP Release 13 time frame. As discussed in RP-150441, “Revised WI: Enhanced LTE Device to Device Proximity Services”, Qualcomm Inc., main targets for D2D service in 3GPP Release 13 include:
A further use of D2D is to provide a D2D relay in which an out of coverage UE (e.g., a remote UE) transmits and receives signals to/from an eNB through a relay UE. The procedure to decide which UE can act as a relay UE has not been determined in 3GPP. However a procedure based on eNB control is a reasonable solution and has been proposed in, such as, for example, in R2-152185, “Considerations on relay selection and reselection”, Fujitsu. Additionally, in R2-152468, “Considerations on Relay initiation”, HuaWei, it was proposed that two thresholds, RSRP ThreshHigh and ThreshLow could be broadcasted by eNB. If the RSRP of a particular relay UE candidate satisfies ThreshLow<RSRP<ThreshHigh, this UE relay candidate can act as a UE relay and has either Model A or Model B discovery solutions. Model A and Model B discovery solutions, defined in 3GPP TR 23.713 V1.1.0, “Study on extended architecture support for proximity-based services”, are copied here for reference:
The basic concept of the D2D relay is shown in
The above and other features, elements, characteristics, steps, and advantages of the present invention will become more apparent from the following detailed description of preferred embodiments of the present invention with reference to the attached drawings.
According to the present invention, there is provided a method performed by a user equipment (UE), the method comprising: receiving a Radio Resource Control (RRC) message including a first configuration for the UE to configure a sidelink relay operation; and broadcasting a master information block sidelink (MasterInformationBlock-SL) including a second configuration that indicates that the UE performs the sidelink relay operation.
According to the present invention, there is provided another method performed by an evolved NodeB (eNB), the method comprising: transmitting a Radio Resource Control (RRC) message including a first configuration for a user equipment (UE) to configure a sidelink relay operation, wherein the first configuration causes the UE broadcasting a master information block sidelink (MasterInformationBlock-SL) including a second configuration that indicates that the UE performs the sidelink relay operation.
Preferred embodiments of the present invention correspond to discovering efficient manners for providing a mechanism for a relay indication transmission procedure or a sidelink UE information transmission procedure related to a sidelink Relay operation. In accordance with these mechanisms and procedures, choosing which UE can act as a relay UE could be determined by an eNB, and one logical conclusion is that the relay UE being selected should not be a UE at the cell edge, since the quality of the radio link at the cell edge is typically not as good as the quality of the radio link located within the middle of the cell. On the other hand, a cell center UE is also not a preferred UE to be used as a relay UE because, under that scenario, a better solution would be to let the UE communicate with its serving eNB directly. Accordingly, an optimal position for locating a relay UE region in accordance with the aforementioned reasons is shown in
Although there has been some studying of the relay UE selection/reselection issue, the relay UE release procedure (i.e., a procedure which determines when and how to stop the relay function of a relay UE) which would result in ensuring that any remote UE camping on a relay UE would not be able to continue the camping for an unrestrained amount of time, has not attracted a lot of attention.
However, it has been discovered that a UE relay release mechanism is a necessity in some of the following user cases:
Details of preferred embodiments of a mechanism for a relay indication transmission procedure or Sidelink UE information transmission procedure related to a sidelink relay operation will now be described. The preferred embodiments of the present invention are able to ensure efficient performance of a sidelink relay operation. The preferred embodiments of the present invention may also be able to ensure that a UE relay is neither very close to the cell center nor at the cell edge through the use of, for example, two thresholds, RSRP ThreshHigh and ThreshLow which can be broadcasted by eNB. If the RSRP of a particular relay UE candidate satisfies ThreshLow<RSRP<ThreshHigh, this UE relay candidate can act as a UE. Together the higher threshold and lower threshold can be used to define a region where a relay UE locates. However, there is another issue to consider: how to determine the conditions to trigger UE relay release when radio conditions are deteriorated.
A method performed by a user equipment (UE) is described, The method includes receiving a Radio Resource Control (RRC) message including a first configuration (e.g., sl-RelayConfig) for the UE to configure a sidelink relay operation, and broadcasting a master information block sidelink (MasterInformationBlock-SL) including a second configuration (e.g., Relay-r13) that indicates that the UE performs the sidelink relay operation. The method may further include transmitting a RRC message including a relay release request related to whether the UE is releasing the relay operation in a cast that the UE is configured with the relay operation based on the configuration. The method may further include transmitting a RRC message including a relay request related to whether the UE is interested in establishing the relay operation.
A method performed by a evolved NodeB (eNB) is described. The method include transmitting a Radio Resource Control (RRC) message including a first configuration for a user equipment (UE) to configure a sidelink relay operation. The first configuration causes the UE broadcasting a master information block sidelink (MasterInformationBlock-SL) including a second configuration that indicates that the UE performs the sidelink relay operation. The method may further include receiving a RRC message including a relay release request related to whether the UE is releasing the relay operation in a cast that the UE is configured with the relay operation based on the configuration. The method may further include receiving a RRC message including a relay request related to whether the UE is interested in establishing the relay operation.
The proposed solution may be based on both thresholds and a timer. These thresholds may be either broadcasted to the whole cell or signaled to a particular relay UE through RRC signaling and a timer is used to avoid ping-pong issues so that the timer prevents the UE changing a behavior due to crossing thresholds in short times. In detail, one preferred embodiment of the present invention includes a situation in which a RRC_IDLE state UE asks to receive a connection to act as a relay when it finds it can be a relay based on thresholds. After that UE enters into RRC_CONNECTED states, where it will use both thresholds and timers to control its relay operation.
PC5 interface is an interface between UEs which is realized by sidelink. The sidelink may include ProSe Direct Discovery (e.g., sidelink direct discovery announcement) and/or ProSe Direct Communication (e.g., sidelink direct communication) between UEs (e.g. D2D). Sidelink may use uplink resources and physical channel structure similar to uplink transmissions. ProSe Direct Communication is a mode of communication whereby UEs can communicate with each other directly over the PC5 interface. ProSe Direct Discovery is defined as the procedure used by the UE supporting ProSe Direct Discovery to discover other UE(s) in its proximity, using EUTRA direct radio signals via PC5.
In order to perform synchronization for out of coverage operation UE(s) may act as a synchronization source by transmitting Sidelink Broadcast Control Channel (SBCCH) and a synchronization signal. SBCCH carries the most essential system information needed to receive other ProSe channels and signals. SBCCH along with a synchronization signal is transmitted with a fixed periodicity of 40 ms. When the UE is in network coverage, the contents of SBCCH are derived from the parameters signaled by the eNB. When the UE is out of coverage, if the UE selects another UE as a synchronization reference, then the content of SBCCH is derived from the received SBCCH; otherwise UE uses pre-configured parameters. SIB18 (SystemInformationBlockType18) provides the resource information for a synchronization signal and SBCCH transmission.
In order to perform synchronization UE(s) participating in announcing of discovery messages may act as a synchronization source by transmitting a synchronization signal based on the resource information for synchronization signals provided in SIB19.
There are three range classes. Upper layer authorization provides applicable range class of the UE. Maximum allowed transmission power for each range class is signaled in SIB19. UE uses the applicable maximum allowed transmission power corresponding to its authorized range class. This puts an upper limit on the determined transmit power based on open loop power control parameters. The eNB may provide a resource pool for UE autonomous resource selection based discovery message announcement in SIB 19 (SystemInforamtionBlockType19). UEs that are authorized for Prose Direct Discovery use these resources for announcing discovery message in RRC_IDLE. The eNB may indicate in SIB 19 that it supports ProSe Direct Discovery but does not provide resources for discovery message announcement. UEs need to enter RRC_CONNECTED in order to request resources for discovery message announcement.
A (Sidelink) Relay request may be transmitted to the eNB based on RSRP of the PCell. The Relay request may be related to whether the UE is interested in establishing a relay operation. The Relay request may, for example, be included in Sidelink UE information. Alternatively, the Relay request may be included in a Relay Indication. Differences between the implementations using the Relay request and the Sidelink UE information will be described below.
For one example, the upper layers may configure the UE to transmit a Relay request. The upper layers may initiate the RRC connection for the sidelink direct communication based on RSRP of the PCell and SIB18 and/or for the sidelink direct discovery based on RSRP of the PCell and SIB19. The procedure of transmission of sidelink UE information including a Relay request or the procedure of transmission of Relay Indication including a Relay request may be initiated following the RRC connection establishment procedure. For another example, the RRC may configure to transmit a Relay request. The upper layers initiate an RRC connection for sidelink direct communication based on SIB18 and/or for sidelink direct discovery announcement based on SIB19. The procedure of transmission of sidelink UE information including a Relay request or the procedure of transmission of Relay Indication including a Relay request may be initiated based on RSRP of the PCell and SIB18 and/or SIB19.
A (Sidelink) Relay Release request may be transmitted to the eNB based on RSRP of the PCell. The Relay Release request may be related to whether the UE is interested in or releasing the relay operation. The Relay Release request may be included in Sidelink UE information. Alternatively, the Relay Release request may be included in Relay Indication. For one example, the upper layers may configure the UE to transmit a Relay Release request. For another example, the procedure of transmission of sidelink UE information including a Relay Release request or the procedure of transmission of Relay Indication including a Relay Release request may be initiated based on RSRP of the PCell and SIB18 and/or SIB19.
Detailed conditions for transmission of Relay request or Relay Release request based on RSRP of the PCell preferably include the following examples. Regarding the settings of these thresholds and how to trigger the procedure, there are a few alternatives:
Next, specific details of preferred embodiments of signaling procedures of relay UEs will be discussed. As mentioned above, the eNB could update thresholds which are used by a particular relay UE or could instead broadcast new thresholds over the cell, which implies that some relay UEs may trigger the relay UE release procedure after obtaining new thresholds.
Below, the concrete implementation on how to realize the sidelink relay operation (e.g., Relay request/establish procedure, Relay release procedure) will be discussed. As shown in
In preferred embodiments of the present invention, a “relay UE release request” message could include an indicator, which shows that the corresponding UE does not want to be a relay UE anymore. In addition it could include further optional information such as specific details of the “reasons” which caused the UE to send “relay UE release” indicator. The reasons could be related to the performance load on the UE, for example. Inside the “relay UE release request confirmation” message, a confirmation on “relay UE release” preferably is provided. The message could further include optional/non-optional indicators such as indicators which inform relay UE to release any resource related to relay UE operation. For example, any transmission/reception resource/resource pools allocated for relay operation purpose could be released.
A “Relay UE release indication” message is preferably sent by eNB to a relay UE directly without any prior information from relay UE side. Similarly to “relay UE release request confirmation” message, the message has a “relay UE release” indicator and other optional/non-optional indicators to release the resource used for relay operation.
Signaling for Sidelink Relay operation (sidelink UE information basis) in accordance with preferred embodiments of the present invention will now be discussed. As shown in
The SidelinkUEInformation should be updated in order to send the relay release indication. One example implementation is described in Section 6.2.2 of 3GPP TS 36.331, Radio Resource Control (RRC) Protocol specification, v12.5.0, which states as follows:
SidelinkUEInformation Message
Signalling for Sidelink Relay operation (Relay Indication basis) in accordance with preferred embodiments of the present invention will now be discussed. As shown in
The UE shall submit the ‘RelayIndication’ message to lower layers for transmission.
The ‘RelayIndication’ should be updated in order to send the relay release indication. One example implementation is described below:
Signalling for Sidelink Relay reconfiguration in accordance with preferred embodiments of the present invention will now be discussed. As shown in
In the preferred embodiments of the present invention, the new IE introduced for relay operation (for example sl-RelayConfig) could include, for example, resource allocated for relay announcement signal transmission or resource for receiving signal from remote UE.
Signaling for Sidelink Relay UE status indication in accordance with preferred embodiments of the present invention will now be discussed. Besides the signaling between a relay UE and eNB designed in previous two sections, a relay UE could also indicate its relay status (Relay-r13) (whether the US is acting as a relay UE or not) through a MasterInformationBlock at the sidelink. This will help remote UE learn the current situation of relay UE. One example implementation based on section 5.10.7.4 of 3GPP TS 36.331, Radio Resource Control (RRC) Protocol specification, v12.5.0 is illustrated below:
The MasterinformationBlock-SL (section 6.5.2 of 3GPP TS 36.331, Radio Resource Control (RRC) Protocol specification, v12.5.0) should be updated and one example implementation is described below:
In the above, the sl-RelayConfig indicates configurations for sidelink relay operation, which is included in a part of a RRC connection reconfiguration message. Relay-r13 indicates whether the UE can act as a relay (sidelink relay), which is broadcasted in MasterinformationBlock-SL. In the other words, the Relay-r13 may indicate whether the UE performs the sidelink relay operation. For example, the “condition A” above may not exist. UE sets Relay-r13 just based on whether sl-RelayConfig is configured or not. Then, broadcasting information whether the UE can act as a relay is controlled by the eNB. In the other words, the eNB may provide Relay-r13 and the UE may just set a value received by the RRC connection reconfiguration message to the Relay-r13. For another example, the “condition A” above may be ThreshLow<RSRP<ThreshHigh. For yet another example, the “condition A” above may be an expiry of a timer, where the timer starts when either RSRP<ThreshLow or RSRP>ThreshHigh. For yet another example, the “condition A” above may be that the UE is releasing the relay operation. It may be that the UE has performed the Relay Release request transmitting operation.
UE 1104 can also include a housing that contains a transmitter 1172 and a receiver 1173 which are configured to allow transmission and reception of data. The transmitter 1172 and receiver 1173 can be combined into a transceiver 1171, for example. One or more antennas 1199a-n are preferably attached to or enclosed within the housing and electrically coupled to the transceiver 1171.
The various components of UE 1104 are preferably coupled together by a bus system 1177, which can include a power bus, a control signal bus, and a status signal bus, in addition to a data bus, for example. However, for the sake of clarity, the various buses are illustrated in
he functions described in this specification can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored as one or more computer-executable or processor-executable instructions on a computer-readable medium. The term “computer-readable medium” refers to any available tangible, non-transitory medium that can be accessed by a computer or a processor. By way of example, and not limitation, a computer-readable or processor-readable medium can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used in this specification, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray (registered trademark) disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. If implemented in hardware, the functions described in this specification can be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), an integrated circuit, etc.
Each of the methods disclosed in this specification includes one or more steps or actions that achieve the described method. The method steps and/or actions can be interchanged with one another and/or combined into a single step without departing from the scope of the present invention. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions can be modified without departing from the scope of the claims.
The term “processor” should be interpreted broadly to encompass a general purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a controller, a microcontroller, a state machine and so forth. Under some circumstances, a “processor” can refer to an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. The term “processor” can refer to a combination of processing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core or any other such configuration.
The term “memory” should be interpreted broadly to encompass any electronic component capable of storing electronic information. The term “memory” can include various types of processor-readable media such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable PROM (EEPROM), flash memory, magnetic or optical data storage, registers, etc. Memory is considered to be in electronic communication with a processor if the processor can read information from and/or write information to the memory. Memory can be integral with a processor and still be considered to be in electronic communication with the processor.
The terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement(s). For example, the terms “instructions” and “code” can refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” can be defined by or include a single computer-readable statement or many computer-readable statements.
It should be understood that the foregoing description is only illustrative of preferred embodiments of the present invention. Various alternatives and modifications can be devised by those skilled in the art without departing from the present invention. Accordingly, the present invention is intended to embrace all such alternatives, modifications, and variances that fall within the scope of the foregoing description.
With the preferred embodiments of the present invention described above, solutions for sidelink relay operations are provided. These solutions include mechanisms and procedures to perform the sidelink relay request/release procedure and the detailed implementation on how to realize sidelink relay procedure. The preferred embodiments provide various solutions to perform sidelink relay procedures. Preferred embodiments of the present invention and modifications thereof provide a mechanism to configure a relay operation, a mechanism to broadcast a relay indication by a Relay UE, and a mechanism to indicate an interest of a relay release or request from a Relay UE to an eNB.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/JP2016/002533 | 5/25/2016 | WO | 00 |
Number | Date | Country | |
---|---|---|---|
62198166 | Jul 2015 | US |