WO2018172857A1

WO2018172857A1 - Communication method, network device and terminal device

Info

Publication number: WO2018172857A1
Application number: PCT/IB2018/000407
Authority: WO
Inventors: Haijing LIU; He Wang
Original assignee: Alcatel Lucent
Priority date: 2017-03-24
Filing date: 2018-03-22
Publication date: 2018-09-27
Also published as: CN108632743B; CN108632743A

Abstract

The present disclosure relates to a communication method, network device and terminal device. For example, a sidelink semi-persistent scheduling (SL SPS) parameter is configured based on positions of a first terminal device and a second terminal device with respect to coverage of the network device, the first terminal device acting as a relay device between the network device and the second terminal device. Downlink control information (DCI) is scrambled with uplink or downlink sidelink semi-persistent scheduling-radio network temporary identity (SPS SL-RNTI) in the SL SPS parameter. The DCI is sent to at least one of the first and second terminal devices to indicate an activation of SL SPS and sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

Description

COMMUNICATION METHOD, NETWORK DEVICE

AND TERMINAL DEVICE

FIELD

[0001] Embodiments of the present disclosure generally relate to wireless communication technologies, and more particularly, to a communication method, a network device and a terminal device.

BACKGROUND

[0002] One of the requirements of the relay solution in further enhanced device-to-device (feD2D) is Quality of Service (QoS). That is, the relay solution shall allow for various QoS configurations to meet requirements of different services and traffic types. The level of QoS while using indirect 3GPP connection based on PC5 should be comparable to that achieved while using direct 3GPP connection for the same device. The sidelink enhancements should be studied in feD2D, including necessary enhancements for QoS, more efficient, reliable, and/or low complexity/cost as well as low energy-consumption sidelink. [0003] It is mentioned that the semi-persistent scheduling (SPS) in V2V/V2X would fit very well e.g. Voice over Internet Protocol (VoIP) services of remote terminal devices, which makes it a good candidate for QoS related enhancements in terminal device to network device relaying solutions.

[0004] Further, evolved proximity service (ProSe) remote terminal devices (e.g. wearable devices), the power efficiency of remote terminal devices is an unnegligible issue in feD2D.

SUMMARY

[0005] Generally the embodiments of the present disclosure propose a communication method implemented at a network device as well as the corresponding communication device, and a communication method implemented at a terminal device as well as the corresponding terminal device.

[0006] In a first aspect, the embodiments of the present disclosure provide a communication method implemented at a network device, the method comprising: configuring a sidelink semi-persistent scheduling (SL SPS) parameter based on positions of a first terminal device and a second terminal device with respect to a coverage of the network device, the first terminal device acting as a relay device between the network device and the second terminal device; scrambling downlink control information (DCI) with a sidelink semi-persistent scheduling-radio network temporary identity (SPS SL-RNTI) of uplink or downlink in the SL SPS parameter; and sending the DCI to at least one of the first and second terminal devices to indicate an activation of SL SPS and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

[0007] In a second aspect, the embodiments of the present disclosure provide a communication method implemented at a terminal device, the terminal device acting as a relay device between a network device and a further terminal device different from the terminal device, the method comprising: receiving downlink control information (DCI) from the network device; determining an activation of SL SPS and an allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit SL SPS data; and communicating with the further terminal device based on an obtained indication of the activation of SL SPS and the allocated sidelink resource. [0008] In a third aspect, the embodiments of the present disclosure provide a network device, comprising: a controller configured to configure a sidelink semi-persistent scheduling (SL SPS) parameter based on positions of a first terminal device and a second terminal device with respect to a coverage of the network device, the first terminal device acting as a relay device between the network device and the second terminal device; scramble downlink control information (DCI) with sidelink semi-persistent scheduling-radio network temporary identity (SPS SL-RNTI) of uplink or downlink in the SL SPS parameter; and a transceiver coupled to the controller and configured to send the DCI to at least one of the first and second terminal devices to indicate an activation of SL SPS and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data. [0009] In a fourth aspect, the embodiments of the present disclosure provide a terminal device, the terminal device acting as a relay device between a network device and a further terminal device different from the terminal device, comprising: a transceiver configured to receive downlink control information (DCI) from the network device; and a controller coupled to the transceiver and configured to determine an activation of SL SPS and an allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit SL SPS data; the transceiver being further configured to communicate with the further terminal device based on an obtained indication of the activation of SL SPS and the allocated sidelink resource. [0010] As will be understood from the following description, the less scheduling and assignment (SA-less) sidelink (SL TX and SL RX) semi-persistent scheduling (SL SPS) scheme_ for feD2D as proposed in the present disclosure can improve the power efficiency of remote and relay terminal devices by reducing the SA transmission in SL SPS. [0011] It should be appreciated contents as described in the SUMMARY portion are not intended to limit key or important features of the embodiments of the present disclosure or used to limit the scope of the present disclosure. Other features of the present disclosure will become easier to understand from the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above and other features, advantages and aspects of various embodiments of the present disclosure will become apparent from the following detailed illustration, when taken in conjunction with the accompanying drawings in which the same or similar reference numerals denote the same or similar elements, wherein:

[0013] Fig. 1 shows an example communication network in which the embodiments of the present disclosure are implemented;

[0014] Fig. 2 shows a flowchart of an example communication method 200 according to some embodiments of the present disclosure;

[0015] Fig. 3 shows a flowchart of an example communication method 300 according to some embodiments of the present disclosure; [0016] Fig. 4 shows a schematic view of communication implemented based on SL SPS in V2V according to the prior art;

[0017] Fig. 5 shows a schematic view of communication implemented based on SL SPS according to some embodiments of the present disclosure;

[0018] Fig. 6 shows a schematic view of communication implemented based on SL SPS according to some embodiments of the present disclosure;

[0019] Fig. 7 shows a schematic view of communication implemented based on SL SPS according to some embodiments of the present disclosure;

[0020] Fig. 8 shows a schematic view of communication implemented based on SL SPS according to some embodiments of the present disclosure; [0021] Fig. 9 shows a block diagram of an apparatus according to some embodiments of the present disclosure;

[0022] Fig. 10 shows a block diagram of an apparatus according to some embodiments of the present disclosure;

[0023] Fig. 11 shows a flowchart of an example communication method 1100 according to some embodiments of the present disclosure;

[0024] Fig. 12 shows a flowchart of an example communication method 1200 according to some embodiments of the present disclosure; and

[0025] Fig. 13 shows a block diagram of a device according to some embodiments of the present disclosure. [0026] Throughout the figures, the same or similar reference numerals denote the same or similar elements.

DETAILED DESCRIPTION OF EMBODIMENTS

[0027] Embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings, in which some embodiments of the present disclosure have been illustrated. However, the present disclosure can be implemented in various manners, and thus should not be construed to be limited to the embodiments disclosed herein. On the contrary, those embodiments are provided for the thorough and complete understanding of the present disclosure. It should be understood that the accompanying drawings and embodiments of the present disclosure are merely for the illustration purpose, rather than limiting the protection scope of the present disclosure.

[0028] The term "network device" used here refers to other entity or node with specific functionality in a base station or communication network. The "base station (BS)" may represent a node B (NodeB or NB), an Evolved Node B (eNodeB or eNB), a remote radio unit (RRU), a radio-frequency head (RH), a remote radio head (RRH), a repeater, or a low power node such as a Picocell, a Femto cell and the like. In the context of the present disclosure, the terms "network device" and "base station" may be used interchangeably, and generally, the eNB is taken as an example of the network device, for the sake of discussion.

[0029] The term "terminal device" or "terminal device" (UE) used here refers to any terminal device that can perform wireless communication with the network device or one another. As an example, the terminal device may comprise a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS), a mobile station (MS) or an access terminal (AT), and the above on-board devices. In the context of the present disclosure, the term "terminal device" might mainly take a vehicle as an example of the network device for the sake of discussion. It will be appreciated this is merely exemplary and not limiting.

[0030] The terms "comprise", "include" and their variants used here are to be read as open terms that mean "include, but is not limited to". The term "based on" is to be read as "based at least in part on". The term "one embodiment" is to be read as "at least one embodiment"; the term "another embodiment" is to be read as "at least one other embodiment". Definitions of other terms will be presented in description below.

[0031] In legacy V2V/V2X, for mode 3 in V2V/V2X, SL SPS from the network device is supported. SL SPS means that the network device allocates and periodically allocates a set of occurring resource for SL SA and data transmission. Fig. 4 shows a schematic view of transmission of mode 3 SPS mechanism in V2V according to the prior art. First of all, a DCI is scrambled with SPS SL-RNTI for V2V PC5. Then, as shown in Fig. 4, a network device 110 sends 410 the scrambled DCI to a terminal device 416 acting as a transmitter, to activate the SPS over PC5. The resources for SPS transmission (including SA and data) in time and frequency domain are indicated in the DCI. After receiving the DCI, the terminal device 416 acting as a transmitter periodically transmits SA and associated data to a terminal device 418 acting as a receiver. For example, in Fig. 4, after receiving the DCI, the terminal device 416 acting as a transmitter transmits 412 SA and associated data to the terminal device acting as a receiver in the next period to the period when the DCI is received, and the terminal device 416 acting as a transmitter transmits 414 SA and associated data to the terminal device acting as a receiver in the further next period.

[0032] Thus, it can be observed that for the SL SPS in V2V/V2X mode 3, the indication of SPS activation is only sent to the terminal device acting as a transmitter. The SA part is transmitted along with the data part in the SL SPS transmission. This is reasonable to V2V because the V2V transmission based on PC5 is multicast in essence, due to the uncertainty of a vehicle or other object acting as a receiver. If the SA is not obtained, then newly joined terminal devices cannot successfully decode the data channel. Further, the SA can also be used for the collision sensing of V2V terminal devices. [0033] However, in terminal device to network device relaying in feD2D, the data transmission is usually unicast. That is, the network device already learns an object acting as a receiver. Hence, the above SL SPS for V2V mode 3 cannot be adopted in feD2D directly

[0034] Therefore, there is a need for a solution for effectively improving and enhancing the above SL SPS for V2V/V2X mode 3. The SL SPS is made applicable to feD2D, and the power efficiency of remote terminal devices and relay terminal devices can be improved. [0035] To at least partially solve these and other potential problems, according to the embodiments of the present disclosure, sidelink semi-persistent scheduling (SL SPS) parameters are configured based on positions of a first terminal device and a second terminal device with respect to the coverage of a network device. First of all, downlink control information (DCI) is scrambled with sidelink semi-persistent scheduling-radio network temporary identity (SPS SL-RNTI) of uplink or downlink in the SL SPS parameters. Then, the DCI is sent to at least one of the first and second terminal devices to indicate an activation of SL SPS and sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

[0036] In this way, by means of the proposed scheduling assigning-less (SA-less) sidelink transmit (SL TX) and sidelink receive (SL RX) scheme for feD2D, the power efficiency of remote and relay terminal devices can be improved by reducing the SA transmission in SL SPS.

[0037] Fig. 1 shows an example communication network 100 in which the embodiments of the present disclosure may be implemented. The communication network 100 comprises a network device 110 and terminal devices, namely a first terminal device 120 and second terminal devices 130 and 140. The network device 110 can communicate with the first terminal device 120 and the second terminal device 130 or 140. Accordingly, the first terminal device 120 and the second terminal device 130 or 140 can communicate with each other. It should be understood the number of network device and the number of terminal devices as shown in Fig. 1 are merely for the illustration purpose, without suggesting any limitation. The communication network 100 may include any appropriate number of network devices and/or terminal devices.

[0038] As depicted, in this example, the first terminal device 120 is nearer to the network device 110, while the second terminal devices 130 and 140 are further from the network device 110. The second terminal device 130 is within the coverage of the network device 110 and the second terminal device 140 is out of the coverage of the network device 110. It should be understood this is merely illustrative rather than limiting. The second terminal devices 130 and 140 as well as the first terminal device 120 may be located in any position either near or far from the network device 110. For example, in the scenario of one embodiment of the present disclosure, the second terminal device 130 and the first terminal device 120, both of which are within the coverage of the network device 110, are almost equally distant to the network device 110 as they are carried together by a carrier (e.g. user). In the scenario of another embodiment of the present disclosure, for example, the second terminal device 140 and the first terminal device 120 are at the edge of the coverage of the network device 110, and the second terminal device 140 goes beyond the coverage of the network device 110 for some reason. [0039] According to one embodiment of the present disclosure, the network device 110 may configure some SL SPS parameters based on a positional relationship between the first terminal device 120 and the second terminal device 130 or 140. After configuring the parameters, the network device 110 scrambles DCI using SPS SL-RNTI in the SL SPS parameters and sends the scrambled DCI to at least one of the first and second terminal devices. If the second terminal device, e.g. the second terminal device 130, is within the coverage of the network device 110, then the network device 110 sends the scrambled DCI to the first terminal device 120 and the second terminal device 130, so that the first terminal device 120 and the second terminal device 130 indicate an activation of SL SPS and sidelink resource in time and frequency domain. If the second terminal device, e.g. the second terminal device 140, is out of the coverage of the network device 110, then the network device 110 sends the scrambled DCI to the first terminal device 120 only, so that the first terminal device 120 indicates an activation of SL SPS and sidelink resource in time and frequency domain. It should be understood that SPS SL-RNTI in the SL SPS parameters can be configured for the uplink and also can be configured for the downlink. [0040] Communication in the network 100 may be implemented according to any appropriate communication protocol, including without limitation to, the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G) and other cellular communication protocol, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and/or any other protocols that are currently known or to be developed later. Furthermore, the communication utilizes any appropriate wireless communication technology, including without limitation to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), and/or any other technology that is currently known or to be developed in future.

[0041] With reference to Figs. 2, 3 and 5 to 8, principles and specific embodiments of the present disclosure will be illustrated in detail. First with reference to Fig. 2, this figure shows a flowchart of an example communication method 200 according to some embodiments of the present disclosure. It will be appreciated the method 200 may be implemented at, for example, the network device 110 as shown in Fig. 1. For the sake of description, the method 200 will be described below in conjunction with Fig. 1. [0042] In one embodiment of the present disclosure, at 210, the network device 110 configures an SL SPS parameter based on positions of a first terminal device (the first terminal device 120 in Fig. 1) and a second terminal device (the second terminal device 130 or 140 in Fig. 1) with respect to the coverage of the network device 110. Here, the SL SPS parameter may comprise SPS SL-RNTI and SL SPS time interval. At 220, if the first and second terminal devices are both within the coverage, then at 230, it is determined whether SPS SL-RNTI in the SL SPS parameter is used for the downlink or the uplink. If SPS SL-RNTI is used for the downlink, then at 232, DCI that is scrambled with the SPS SL-RNTI of downlink is sent to the first and second terminal devices, so that at 236, SL RX SPS of the first terminal device is activated. In the meantime, SL RX SPS of the second terminal device is activated.

[0043] If SPS SL-RNTI is used for the uplink, then at 234, DCI that is scrambled with the SPS SL-RNTI of uplink is sent to the first and second terminal devices, so that at 238, SL RX SPS of the first terminal device is activated. In the meantime, SL TX SPS of the second terminal device is activated. [0044] Returning to 220, if not both the first and second terminal devices are within the coverage, then it is determined whether the second terminal device is out of the coverage. If the second terminal device is out of the coverage, then at 250, it is determined whether SPS SL-RNTI in the SL SPS parameter is used for the downlink or the uplink. If SPS SL-RNTI is used for the downlink, then at 252, DCI that is scrambled with the SPS SL-RNTI of downlink is sent to the first terminal device, so that SL TX SPS of the first terminal device is activated at 256.

[0045] If SPS SL-RNTI is used for the uplink, then at 254, DCI that is scrambled with the SPS SL-RNTI of uplink is sent to the first terminal device, so that SL RX SPS of the first terminal device is activated at 258.

[0046] Reference is now made to Fig. 3 which shows a flowchart of an example communication method 300 according to some embodiments of the present disclosure. It will be appreciated the method 300 may be implemented at, for example, the first terminal device 120 as shown in Fig. 1. For the sake of description, the method 300 will be described below in conjunction with Fig. 1.

[0047] In one embodiment of the present disclosure, at 310, a first terminal device (e.g. the first terminal device 120 in Fig. 1) receive DCI from the network device 110. Next at 320, it is determined whether a second terminal device that is to communicate with the first terminal device is also within the coverage of the network device 110 or not. It should be understood the first terminal device can learn from the network device whether the second terminal device is within the coverage, or can learn from its own channel estimation parameter whether the second terminal device is within the coverage. Therefore, the determining procedure is not detailed here.

[0048] At 320, if it is determined the second terminal device is also within the coverage of the network device 110, then at 330, it is determined whether SPS SL-RNTI in a SL SPS parameter is used for the downlink or the uplink by descrambling the DCI. If SPS SL-RNTI is used for the downlink, then at 332 an indication of an activation of SL TX SPS is obtained. At the same time, since the second terminal device has obtained an indication of an activation of SL RX SPS, the first terminal device can communicate with the second terminal device. The DCI further indicates sidelink resource allocated in time and frequency domain. Therefore, at 336 the first terminal device can only send SPS data to the second terminal device in the second available period after the first available period in the allocated sidelink resource. That is, since the second terminal device also obtains SA information by receiving the DCI, the first terminal device no longer needs to send SA information to the second terminal device but only sends SPS data. It should be understood that unless an indication of a release is received from the network device, the first terminal device can send only the SPS data to the second terminal device in each available period since the second available period after the first available period of the allocated sidelink resource. It is noteworthy the first available period is used for receiving an indication of activation.

[0049] If SPS SL-RNTI is used for the uplink, then at 334 an indication of an activation of SL RX SPS is obtained. At the same time, since the second terminal device has obtained an indication of an activation of SL TX SPS, the first terminal device can communicate with the second terminal device. The DCI further indicates sidelink resource allocated in time and frequency domain. Therefore, at 338, the first terminal device can receive the SPS data from the second terminal device in the second available period after the first available period in the allocated sidelink resource. That is, since the second terminal device also obtains SA information by receiving the DCI, the second terminal device may receive the SPS data from the second terminal device without sending SA information to the first terminal device any longer. It should be understood that unless an indication of a release is received from the network device, the first terminal device can receive the SPS data from the second terminal device in each available period since the second available period after the first available period of the allocated sidelink resource. It is noteworthy the first available period is used for receiving an indication of activation.

[0050] Returning to 320, if it is determined the second terminal device is not within the coverage of the network device 110, then the flow proceeds to 340 where it is determined whether the second terminal device is out of the coverage of the network device 110. At 350, it is determined whether SPS SL-RNTI in the SL SPS parameter is used for the downlink or the uplink by descrambling the DCI. If SPS SL-RNTI is used for the downlink, then at 352 an indication of an activation of SL TX SPS is obtained. The DCI further indicates sidelink resource allocated in time and frequency domain. Since the second terminal device is out of the coverage, that is, the second terminal device cannot obtain the DCI from the network device, at 356, the first terminal device can send SPS data and SL SPS scheduling information to the second terminal device in the second available period after the first available period in the allocated sidelink resource to activate SL RX SPS of the second terminal device. At the same time, the second terminal device also obtains SA information. Therefore, unless an indication of a release is received from the network device, the first terminal device can send only the SPS data to the second terminal device in each available period after the second available period. It is noteworthy the first available period is used for receiving an indication of activation. [0051] If SPS SL-RNTI is used for the uplink, then at 354 an indication of an activation of SL RX SPS is obtained. The DCI further indicates sidelink resource allocated in time and frequency domain. Since the second terminal device is out of the coverage, that is, the second terminal device cannot obtain the DCI from the network device, at 358, the first terminal device can send SL SPS scheduling information to the second terminal device in the second available period after the first available period in the allocated sidelink resource to activate SL TX SPS of the second terminal device. Since the second terminal device has obtained SL TX SPS scheduling information at 358, unless an indication of a release is received from the network device, the second terminal device can send only the SPS data to the first terminal device in each available period after the second available period. Since the first terminal device has obtained SL RX SPS scheduling information from the DCI, at 360 the first terminal device may receive the SPS data from the second terminal device in each available period after the second available period. It is noted that the first available period is used for receiving an indication of the activation.

[0052] It should be understood from the method 200 and the method 300 that since the concept of SL RX SPS is introduced to feD2D, new definition is given to SPS SL-RNTI. By sending to the first terminal device DCI that is scrambled with newly defined SPS SL-RNTI, the first terminal device can obtained SA information directly or indirectly. In a feD2D scenario, once SA information is obtained, unless an indication of release of the link is received, the first terminal device does not have to transmit SA in each available period but only transmits data. In this manner, the power for transmitting SA information can be reduced significantly, and the overall efficiency of the communication architecture can be improved further. [0053] Figs. 5 to 8 each shows a schematic view of communication implemented based on SL SPS according to the embodiments of the present disclosure. For the sake of convenience, Figs. 5 to 8 will be described in conjunction with Fig. 1. Fig. 5 shows the situation of SL SPS used for the downlink, wherein both the first terminal device 120 and the second terminal device 130 are within the coverage. The network device 110 configures parameters for the first terminal device 120 and the second terminal device 130, such as the SPS SL-RNTI of the downlink and SL SPS time interval. The network device 110 sends 510 to the first terminal device 120 DCI that is scrambled with the SPS SL-RNTI of the downlink and meanwhile (in the same available period, e.g. the first available period in Fig. 5) sends 512 to the second terminal device 130 DCI that is scrambled with the SPS SL-RNTI of the downlink. The DCI comprises an indication of SL resource and activation of SL TX SPS of the first terminal device 120 and SL RX SPS of the second terminal device 130. In the second available period in the allocated SL SPS resource, the first terminal device 120 can send 514 only the SPS data to the second terminal device 130 without transmitting SA information any longer. Where no indication of a release is received from the network device 110, the first terminal device 120 can continue transmitting 516 only the SPS data to the second terminal device 130 in the third available period in the allocated SL SPS resource. The procedure is also applicable to release SL SPS in the present scenario. In addition, timer-based automatic release may also be considered.

[0054] Fig. 6 shows the situation of SL SPS used for the uplink, wherein both the first terminal device 120 and the second terminal device 130 are within the coverage. The network device 110 configures parameters for the first terminal device 120 and the second terminal device 130, such as the SPS SL-RNTI of the uplink and SL SPS time interval. The network device 110 sends 610 to the first terminal device 120 DCI that is scrambled with the SPS SL-RNTI of the uplink and meanwhile (in the same available period, e.g. the first available period in Fig. 6) sends 612 to the second terminal device 130 DCI that is scrambled with the SPS SL-RNTI of the uplink. The DCI comprises an indication of SL resource and activation of SL RX SPS of the first terminal device 120 and SL TX SPS of the second terminal device 130. In the second available period on the allocated SL SPS resource, the first terminal device 120 can receive 614 SPS data transmitted from the second terminal device 130. Where no indication of a release is received from the network device 110, the first terminal device 120 can continue receiving 616 SPS data transmitted from the second terminal device 130 in the third available period in the allocated SL SPS resource. The procedure is also applicable to release SL SPS in the present scenario. In addition, timer-based automatic release may also be considered.

[0055] Fig. 7 shows the situation of SL SPS used for the downlink, wherein the first terminal device 120 is within the coverage and the second terminal device 140 is out of coverage. The network device 110 configures parameters for the first terminal device 120, such as the SPS SL-RNTI of the downlink and SL SPS time interval. The network device 110 sends 710 to the first terminal device 120 DCI that is scrambled with the SPS SL-RNTI of the downlink. The DCI comprises an indication of SL resource and activation of SL TX SPS of the first terminal device 120. In the second available period on the allocated SL SPS resource, the first terminal device 120 can transmit 712 SL SPS scheduling information and SPS data to the second terminal device 140 to send an indication of an activation of SL RX SPS and sidelink resource to the second terminal device 140. Later, the first terminal device 120 can continue transmitting 715 only the SPS data to the second terminal device 130 in the third available period in the allocated SL SPS resource. Where no indication of a release is received from the network device 110, the first terminal device 120 can continue transmitting only the SPS data to the second terminal device 140 in each available period since the third available period in the allocated SL SPS resource. The procedure is also applicable to release SL SPS in the present scenario. In addition, timer-based automatic release may also be considered.

[0056] Fig. 8 shows the situation of SL SPS used for the uplink, wherein the first terminal device 120 is within the coverage and the second terminal device 140 is out of coverage. The network device 110 configures parameters for the first terminal device 120, such as the SPS SL-RNTI of the uplink and SL SPS time interval. The network device 110 sends 810 to the first terminal device 120 DCI that is scrambled with the SPS SL-RNTI of the uplink. The DCI comprises an indication of SL resource and activation SL RX SPS of the first terminal device 120. In the second available period in the allocated SL SPS resource, the first terminal device 120 can transmit 812 SL SPS scheduling information to the second terminal device 140 to send an indication of SL RX SPS activation and sidelink resource to the second terminal device 140. Once SL TX SPS of the second terminal device 140 is activated, the first terminal device 120 can receive 814 SPS data from the second terminal device 140 in the third available period. Later, the first terminal device 120 can receive 816 SPS data from the second terminal device 140 in the fourth available period in the allocated SL SPS resource. Where no indication of a release is received from the network device 110, the first terminal device 120 can receive the SPS data from the second terminal device 140 in each available period since the third available period in the allocated SL SPS resource. The procedure is also applicable to release SL SPS in the present scenario. In addition, timer-based automatic release may also be considered.

[0057] Fig. 9 shows a block diagram of an apparatus according to some embodiments of the present disclosure. It will be appreciated an apparatus 900 may be implemented at the network device 110 side shown in Fig. 1. As depicted in Fig. 9, the apparatus 900 (e.g. the network device 110) comprises: a first configuring unit 910 configured to configure an SL SPS parameter based on positions of a first terminal device (the first terminal device 120 in Fig. 1) and a second terminal device (the second terminal device 130 or 140 in Fig. 1) with respect to a coverage of a network device, the first terminal device acting as a relay device between the network device 110 and the second terminal device; a scrambling unit 920 configured to scramble DCI with sidelink SPS SL-RNTI of uplink or downlink in the SL SPS parameter; and a first sending unit 930 configured to send the DCI to at least one of the first and second terminal devices to indicate an activation of SL SPS and sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

[0058] In some embodiments, the first configuring unit 910 further comprises a second configuring unit configured to: configure an SL SPS time interval and SPS SL-RNTI for the first and second terminal devices.

[0059] In some embodiments, the first sending unit 930 further comprises a second sending unit configured to: if the first and second terminal devices are both within the coverage, activate SL TX SPS of the first terminal device and SL RX SPS of the second terminal device.

[0060] In some embodiments, the first sending unit 930 further comprises a third sending unit configured to: if the first and second terminal devices are both within the coverage, activate SL RX SPS of the first terminal device and SL TX SPS of the second terminal device.

[0061] In some embodiments, the first sending unit 930 further comprises a fourth sending unit configured to: if the first terminal device is within the coverage and the second terminal device is out of the coverage, activate SL TX SPS of the first terminal device. [0062] In some embodiments, the first sending unit 930 further comprises a fifth sending unit configured to: if the first terminal device is within the coverage and the second terminal device is out of the coverage, activate SL RX SPS of the first terminal device.

[0063] In some embodiments, the apparatus 900 (e.g. the network device 110) further comprises a sixth sending unit configured to: send the DCI to at least one of the first and second terminal devices to indicate A release of SL SPS and the sidelink resource, the sidelink resource being at least partially used to transmit the SL SPS data.

[0064] Fig. 10 shows a block diagram of an apparatus 1000 according to some embodiments of the present disclosure. It will be appreciated the apparatus 1000 may be implemented at the first terminal device 120 side shown in Fig. 1. As depicted in Fig. 10, the apparatus 1000 acts as a first terminal device (e.g. the first terminal device 120) between the network device 110 and the second terminal device 130 or 140 , the apparatus 1000 comprising: a first receiving unit 1010 configured to receive downlink control information DCI from the network device; a first determining unit 1020 configured to determine an activation of SL SPS and an allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit the SL SPS data; and a first communicating unit 1030 configured to communicate with the second terminal device 130 or 140 based on an obtained indication of the an activation of SL SPS and the allocated sidelink resource. [0065] In some embodiments, the first communicating unit 1030 further comprises a second communication unit configured to: if the apparatus 1000 and the second terminal device 130 are both within the coverage of the network device, in response to obtaining an indication of an activation of SL TX SPS, transmit only the SPS data to the second terminal device 130 in the second available period after the first available period on the allocated sidelink resource, the indication of the activation being received within the first available period.

[0066] In some embodiments, the first communication unit 1030 further comprises a third communication unit configured to: if both the apparatus 1000 and the second terminal device 130 are within the coverage, in response to obtaining an indication of an activation of SL RX SPS, receive the SPS data from the second terminal device 130 in the second available period after the first available period on the allocated sidelink resource, the indication of the activation being received within the first available period.

[0067] In some embodiments, the first communicating unit 1030 further comprises a fourth communication unit configured to: if the apparatus 1000 is within the coverage and the second terminal device 130 is out of the coverage, in response to obtaining an indication of an activation of SL TX SPS, transmit the SPS data and SL SPS scheduling information to the second terminal device 130 in the second available period after the first available period on the allocated sidelink resource, the SL SPS scheduling information being used to indicate SL RX SPS activation and sidelink resource, the indication of the activation being received within the first available period, the sidelink resource being at least partially used to transmit SL SPS data.

[0068] In some embodiments, the first communication unit 1030 further comprises a fifth communication unit configured to: if the apparatus 1000 is within the coverage and the second terminal device 130 is out of the coverage, in response to obtaining an indication of an activation of SL RX SPS, transmit only SL SPS scheduling information to the second terminal device 130 in the second available period after the first available period on the allocated sidelink resource, the SL SPS scheduling information being used to indicate SL TX SPS activation and sidelink resource, the indication of the activation being received within the first available period, the sidelink resource being at least partially used to transmit SL SPS data; and receive the SPS data from the second terminal device 140 in the third available period.

[0069] In some embodiments, the apparatus 1000 further comprises a second determining unit configured to: determine A release of SL SPS from the DCI and allocated sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

[0070] It will be appreciated each unit of the apparatus 900 and the apparatus 1000 corresponds to each step of the methods 200 and 300 described with reference to Figs. 1 to 3. Therefore, operations and features described above with reference to Figs. 1 to 3 are also applicable to the apparatus 900, the apparatus 1000 as well as units included in them, and meanwhile have the same effect, details of which are ignored here.

[0071] The units included in the apparatus 900 and/or the apparatus 1000 may be implemented in various manners, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium. In addition to or instead of machine-executable instructions, parts or all of the units may be implemented, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application- specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

[0072] The units shown in Figs. 9 and 10 may be implemented, partially or entirely, as hardware modules, software modules, firmware modules or any combination thereof. In particular, in some embodiments, the flows, methods or processes described above may be implemented by hardware in a base station or terminal device. For example, the base station or terminal device may implement the methods 200 and 300 by means of its transmitter, receiver, transceiver and/or processor.

[0073] Fig. 11 shows a flowchart of an example communication method 1100 according to some embodiments of the present disclosure. It will be appreciated the method 1100 may be implemented at, for example, the network device 110 as shown in Fig. 1. For the sake of description, the method 1100 will be described in conjunction with Fig. 1.

[0074] At 1110, an SL SPS parameter is configured based on positions of the first terminal device 120 and the second terminal device 130 or 140 with respect to coverage of a network device, the first terminal device 120 acting as a relay device between the network device 110 and the second terminal device 130 or 140. At 1120, DCI is scrambled with the SPS SL-RNTI of uplink or downlink in the SL SPS parameter. At 1130 the DCI is transmitted to at least one of the first terminal device 120 and the second terminal device 130 or 140, to indicate an activation of SL SPS and sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

[0075] Fig. 12 shows a flowchart of an example communication method 1200 according to some embodiments of the present disclosure. It will be appreciated the method 1200 may be implemented at, for example, the first terminal device 120 as shown in Fig. 1. For the sake of description, the method 1200 will be described in conjunction with Fig. 1.

[0076] At 1210, the first terminal device 120 receives DCI from a network device. At 1220, an activation of SL SPS and the allocated sidelink resource are determined from the DCI, the sidelink resource being at least partially used to transmit SL SPS data. At 1230, the first terminal device 120 communicates with the second terminal device 130 or 140 based on an obtained indication of the activation of SL SPS and the allocated sidelink resource.

[0077] It will be appreciated each operation of the methods 1100 and 1200 corresponds to each step of the methods 200 and 300 described with reference to Figs. 1 to 3 and/or each unit of the apparatuses 900 and 1000 described with reference to Figs. 9 and 10. Therefore, operations described with reference to Figs. 1 to 3 as well as units and features of the apparatuses 900 and 1000 described with reference to Figs. 9 and 10 are also applicable to each operation of the methods 1100 and 1200, and meanwhile have the same effect, details of which are ignored here.

[0078] Fig. 13 shows a block diagram of a device 1300 which is applicable to implement the embodiments of the present disclosure. The device 1300 may be used for implementing a network device, e.g. the network device 110 shown in Fig. 1, and/or may be used for implementing a terminal device, e.g. the first terminal device 120 shown in Fig. 1.

[0079] As depicted, the device 1300 comprises a controller 1310. The controller 1310 controls operations and functions of the device 1300. For example, in some embodiments, the controller 1310 may execute various operations by means of instructions 1330 stored in a memory 1320 coupled to the controller 1310. The memory 1320 may be of any appropriate type that is applicable to a local technical environment, and may be implemented using any appropriate data storage techniques, including without limitation to, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems. Though only one memory unit is shown in Fig. 13, there may be a plurality of physically different memory units in the device 1300.

[0080] The controller 1310 may be of any appropriate type that is applicable to a local technical environment, and may include without limitation to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), as well as one or more processors in a processor based multi-core processor architecture. The device 1300 may also comprise multiple controllers 1310. The controller 1310 is coupled to a transceiver 1340 that may affect information receiving and transmitting by means of one or more antennas 1350 and/or other component. Note the transceiver 1340 may be a single device or may comprise separate devices for sending and receiving respectively.

[0081] When the device 1300 acts as the network device 110, the controller 1310 and the transceiver 1340 may operate in cooperation to implement the methods 200 and 1100 described with reference to Figs. 2 and 11 respectively. When the device 1300 acts as the first terminal device 120, the controller 1310 and the transceiver 1340 may operate in cooperation under the control of the instructions 1330 in the memory 1320, to implement the methods 300 and 1200 described with reference to Figs. 3 and 12 respectively. For example, the transceiver 1340 may affect data/information receiving and/or transmitting, while the controller 1310 executes or triggers data processing, computing and/or other operation. All features described with reference to Figs. 2, 3, 11 and 12 are applicable to the device 1300, details of which are ignored here.

[0082] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0083] For example, embodiments of the present disclosure can be described in the general context of machine-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0084] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0085] In the context of this disclosure, a machine readable medium may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0086] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0087] Although the subject matter has been described in a language that is specific to structural features and/or method actions, it is to be understood the subject matter defined in the appended claims is not limited to the specific features or actions described above. On the contrary, the above-described specific features and actions are disclosed as an example of implementing the claims.

Claims

I/We Claim:

1. A communication method implemented at a network device, the method comprising:

configuring a sidelink semi-persistent scheduling (SL SPS) parameter based on positions of a first terminal device and a second terminal device with respect to a coverage of the network device, the first terminal device acting as a relay device between the network device and the second terminal device;

scrambling downlink control information (DCI) with a sidelink semi-persistent scheduling-radio network temporary identity (SPS SL-RNTI) of uplink or downlink in the SL SPS parameter; and

sending the DCI to at least one of the first and second terminal devices to indicate an activation of SL SPS and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

2. The method according to Claim 1, wherein configuring the SL SPS parameter at least comprises:

configuring an SL SPS time interval and the SPS SL-RNTI for the first and second terminal devices.

3. The method according to Claim 1, wherein sending the DCI comprises:

if the first and second terminal devices are both within the coverage, activating sidelink transmit semi-persistent scheduling (SL TX SPS) of the first terminal device and sidelink receive semi-persistent scheduling (SL RX SPS) of the second terminal device.

4. The method according to Claim 1, wherein sending the DCI comprises:

if the first and second terminal devices are both within the coverage, activating sidelink receive semi-persistent scheduling (SL RX SPS) of the first terminal device and sidelink transmit semi-persistent scheduling (SL TX SPS) of the second terminal device.

5. The method according to Claim 1, wherein sending the DCI comprises:

if the first terminal device is within the coverage and the second terminal device is out of the coverage, activating sidelink transmit semi-persistent scheduling (SL TX SPS) of the first terminal device.

6. The method according to Claim 1, wherein sending the DCI comprises: if the first terminal device is within the coverage and the second terminal device is out of the coverage, activating sidelink receive semi-persistent scheduling (SL RX SPS) of the first terminal device.

7. The method according to Claim 1, further comprising:

sending the DCI to at least one of the first and second terminal devices to indicate a release of SL SPS and the sidelink resource, the sidelink resource being at least partially used to transmit the SL SPS data.

8. A communication method implemented at a terminal device, the terminal device acting as a relay device between a network device and a further terminal device different from the terminal device, the method comprising:

receiving downlink control information (DCI) from the network device;

determining an activation of SL SPS and an allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit SL SPS data; and

communicating with the further terminal device based on an obtained indication of the activation of SL SPS and the allocated sidelink resource.

9. The method according to Claim 8, wherein communicating with the further terminal device comprises:

if the terminal device and the further terminal device are both within a coverage of the network device, in response to obtaining an indication of an activation of sidelink transmit semi-persistent scheduling (SL TX SPS), transmitting only the SPS data to the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period.

10. The method according to Claim 8, wherein communicating with the further terminal device comprises:

if the terminal device and the further terminal device are both within a coverage, in response to obtaining an indication of an activation of sidelink receive semi-persistent scheduling (SL RX SPS), receiving the SPS data from the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period.

11. The method according to Claim 8, wherein communicating with the further terminal device comprises:

if the terminal device is within the coverage and the further terminal device is out of the coverage, in response to obtaining an indication of an activation of sidelink transmit semi-persistent scheduling (SL TX SPS), transmitting the SPS data and SL SPS scheduling information to the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period, the SL SPS scheduling information being used to indicate an activation of sidelink receive semi-persistent scheduling (SL RX SPS) and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

12. The method according to Claim 8, wherein communicating with the further terminal device comprises:

if the terminal device is within the coverage and the further terminal device is out of the coverage, in response to obtaining an indication of an activation of sidelink receive semi-persistent scheduling (SL RX SPS), transmitting only SL SPS scheduling information to the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period, the SL SPS scheduling information being used to indicate an activation of sidelink transmit semi-persistent scheduling (SL TX SPS) and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data; and

receiving the SPS data from the further terminal device in a third available period after the second available period.

13. The method according to Claim 8, further comprising:

determining a release of SL SPS and the allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit the SL SPS data.

14. A network device, comprising:

a controller configured to:

configure a sidelink semi-persistent scheduling (SL SPS) parameter based on positions of a first terminal device and a second terminal device with respect to a coverage of the network device, the first terminal device acting as a relay device between the network device and the second terminal device;

scramble downlink control information (DCI) with sidelink semi-persistent scheduling-radio network temporary identity (SPS SL-RNTI) of uplink or downlink in the SL SPS parameter; and

a transceiver coupled to the controller and configured to:

send the DCI to at least one of the first and second terminal devices to indicate an activation of SL SPS and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

15. The device according to Claim 14, wherein the controller is configured to:

configure an SL SPS time interval and SPS SL-RNTI for the first and second terminal devices.

16. The device according to Claim 14, wherein the transceiver is configured to:

if the first and second terminal devices are both within the coverage, activate sidelink transmit semi-persistent scheduling (SL TX SPS) of the first terminal device and sidelink receive semi-persistent scheduling (SL RX SPS) of the second terminal device.

17. The device according to Claim 14, wherein the transceiver is configured to:

if the first and second terminal devices are both within the coverage, activate sidelink receive semi-persistent scheduling (SL RX SPS) of the first terminal device and sidelink transmit semi-persistent scheduling (SL TX SPS) of the second terminal device.

18. The device according to Claim 14, wherein the transceiver is configured to:

if the first terminal device is within the coverage and the second terminal device is out of the coverage, activate sidelink transmit semi-persistent scheduling (SL TX SPS) of the first terminal device.

19. The device according to Claim 14, wherein the transceiver is configured to:

if the first terminal device is within the coverage and the second terminal device is out of the coverage, activate sidelink receive semi-persistent scheduling (SL RX SPS) of the first terminal device.

20. The device according to Claim 14, wherein the transceiver is further configured to: send the DCI to at least one of the first and second terminal devices to indicate a release of SL SPS and the sidelink resource, the sidelink resource being at least partially used to transmit the SL SPS data.

21. A terminal device, the terminal device acting as a relay device between a network device and a further terminal device different from the terminal device, the terminal device comprising:

a transceiver configured to receive downlink control information (DCI) from the network device; and

a controller coupled to the transceiver and configured to determine an activation of SL SPS and an allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit SL SPS data;

the transceiver being further configured to communicate with the further terminal device based on an obtained indication of the activation of SL SPS and the allocated sidelink resource.

22. The device according to Claim 21, wherein the transceiver is further configured to: if the terminal device and the further terminal device are both in a coverage of the network device, in response to obtaining an indication of an activation of sidelink transmit semi-persistent scheduling (SL TX SPS), transmitt only the SPS data to the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period.

23. The device according to Claim 21, wherein the transceiver is further configured to: if both the terminal device and the further terminal device are within the coverage, in response to obtaining an indication of an activation of sidelink receive semi-persistent scheduling (SL RX SPS), receive the SPS data from the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period.

24. The device according to Claim 21, wherein the transceiver is further configured to: if the terminal device is within the coverage and the further terminal device is out of the coverage, in response to obtaining an indication of an activation of sidelink transmit semi-persistent scheduling (SL TX SPS), transmit the SPS data and SL SPS scheduling information to the further terminal device in a second available period after a first available period in the allocated sidelink resource, the indication of the activation being received within the first available period, the SL SPS scheduling information being used to indicate an activation of sidelink receive semi-persistent scheduling (SL RX SPS) and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data.

25. The device according to Claim 21, wherein the transceiver is further configured to: if the terminal device is within the coverage and the further terminal device is out of the coverage, in response to obtaining an indication of sidelink receive semi-persistent scheduling (SL RX SPS) activation, transmit only SL SPS scheduling information to the further terminal device in a second available period after a first available period on the allocated sidelink resource, the indication of the activation being received within the first available period, the SL SPS scheduling information being used to indicate an activation of sidelink transmit semi-persistent scheduling (SL TX SPS) and a sidelink resource, the sidelink resource being at least partially used to transmit SL SPS data; and

receive the SPS data from the further terminal device in a third available period after the second available period.

26. The device according to Claim 21, wherein the controller is further configured to: determine a release of SL SPS and the allocated sidelink resource from the DCI, the sidelink resource being at least partially used to transmit the SL SPS data.