CN114424650A

CN114424650A - Method and device for acquiring sidelink resources

Info

Publication number: CN114424650A
Application number: CN201980100596.3A
Authority: CN
Inventors: 彭文杰; 王君; 戴明增
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-09-30
Filing date: 2019-09-30
Publication date: 2022-04-29
Also published as: WO2021062704A1

Abstract

The application provides a method and a communication device for acquiring sidelink resources. The method comprises the following steps: the first terminal equipment receives first information from the second terminal equipment, wherein the first information is used for requesting SL resources; the first terminal equipment generates second information based on the first information, wherein the second information carries identification information of the second terminal equipment and is used for requesting the SL resources for the second terminal equipment; and the first terminal equipment sends the second information to the network equipment. The network device identifies that the SL resource requested by the second information is used for the second terminal device to transmit the service data according to the identification information carried in the received second information, so that the SL resource can be more accurately and reasonably allocated to the second terminal device.

Description

Method and device for acquiring sidelink resources

Technical Field

The present application relates to the field of wireless communications, and more particularly, to a method and apparatus for acquiring sidelink resources.

Background

Currently, under the Long Term Evolution (LTE) technology proposed by the 3rd generation partnership project (3 GPP), a vehicle-to-anything communication (V2X) vehicle networking technology is proposed. In addition, with the development of the future fifth generation (5G generation, 5G) system or New Radio (NR) technology in the 3GPP standards organization, the 5G NR V2X will be further developed.

In NR V2X, terminal devices may perform broadcast communication, unicast communication, and multicast communication on a Sidelink (SL). There is a method known in the art in which a terminal device (for example, referred to as terminal device #1) may request a network device to acquire an SL resource through another terminal device (for example, referred to as terminal device #2), and the network device cannot recognize whether the resource request information requests a resource for terminal device #1 or terminal device #2 during the process in which terminal device #2 forwards the resource request information from terminal device #1 to the network device. Therefore, the network device may not be able to accurately schedule the SL resource for the terminal device #2, resulting in low reliability of the terminal device #2 for transmitting the service data and poor service experience.

Disclosure of Invention

The application provides a method for obtaining SL resources, which aims to achieve the purpose that network equipment accurately schedules SL resources for second terminal equipment under the condition that the second terminal equipment requests the network equipment for the SL resources through first terminal equipment.

In a first aspect, a SL resource acquisition method is provided, where the method includes: the first terminal equipment receives first information from the second terminal equipment, wherein the first information is used for requesting SL resources; the first terminal device generates second information based on the first information, wherein the second information carries identification information of the second terminal device and is used for requesting the SL resource for the second terminal device; the first terminal device sends the second information to the network device.

Based on the above technical solution, the second information generated by the first terminal device based on the first information from the second terminal device carries the identification information of the second terminal device. After the first terminal device sends the second information to the network device, the network device can identify, according to the identification information of the second terminal device, that the SL resource requested by the second information is used for the second terminal device to transmit the service data, so that the SL resource can be more accurately and reasonably allocated to the second terminal device.

With reference to the first aspect, in some implementations of the first aspect, the identification information of the second terminal device includes third information used for identifying the second terminal device, or third information used for identifying the second terminal device and fourth information used for identifying a terminal device group to which the second terminal device belongs.

Based on the above technical solution, in different communication scenarios, the second information generated by the first terminal device based on the first information may carry different identification information of the second terminal device. Therefore, under different communication scenarios, the network device may also recognize that the SL resource requested by the second information is used for the second terminal device to transmit the service data, so that the SL resource may be more accurately and reasonably allocated to the second terminal device. For example, if the second terminal device requests the network device for the SL resource through the relay (the first terminal device), the identification information of the second terminal device carried by the second information generated by the first terminal device based on the first information may include third information for identifying the second terminal device, and the network device may identify the second terminal device based on the third information. For another example, when the first terminal device and the second terminal device belong to the same terminal device group, the identification information of the second terminal device may include third information for identifying the second terminal device and fourth information for identifying the terminal device group, and the network device may identify the second terminal device based on the third information and the fourth information.

With reference to the first aspect, in certain implementations of the first aspect, the third information includes one or more of: layer 2 (L2) identification of the second terminal device, intra-group identification of the second terminal device or an index.

With reference to the first aspect, in some implementations of the first aspect, the fourth information includes a group identification or an index of the terminal device group.

With reference to the first aspect, in certain implementations of the first aspect, the first information includes a first Buffer State Report (BSR), and the second information includes a second BSR generated based on the first BSR.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the first terminal device receives Downlink Control Information (DCI) from the network device, where the DCI includes first indication information and first Sidelink Control Information (SCI), the first indication information is used to indicate a first SL resource, and the first SL resource is used to transmit the first SCI; the first terminal device sends the first SCI to the second terminal device through the first SL resource, where the first SCI includes second indication information and a second SCI, the second indication information is used to indicate a second SL resource, the second SL resource is used to transmit the second SCI, the second SCI is used to indicate a third SL resource, and the third SL resource is used for the second terminal device to transmit service data.

Based on the above technical solution, the network device simultaneously schedules multiple SL resources according to the received second BSR, and completes sending the first SL resource of the first SCI to the second terminal device to the first terminal device and indicating the third SL resource for transmitting the service data to the second terminal device through the first terminal device in one step, thereby improving the efficiency of the second terminal device for obtaining the SL resources.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the first terminal equipment receives DCI from the network equipment, wherein the DCI is used for indicating SL resources; the first terminal equipment generates a second SCI according to the SL resource indicated by the DCI; the first terminal device sends a second SCI to the second terminal device, the second SCI is used for indicating a third SL resource, the third SL resource is used for the second terminal device to transmit service data, and the third SL resource is included in the SL resource indicated by the DCI.

With reference to the first aspect, in some implementations of the first aspect, the DCI further includes third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs.

Based on the above technical solution, in the case that there are multiple second terminal devices or multiple terminal device groups, the first terminal device may determine, through the third information and/or the fourth information included in the DCI, which second terminal device or which member terminal device in the terminal device group the SL resource scheduled by the network device is used for transmitting the service data.

With reference to the first aspect, in certain implementations of the first aspect, the first information includes a first business model, and the second information includes a second business model generated based on the first business model.

With reference to the first aspect, in certain implementations of the first aspect, the first traffic model further includes a first time offset parameter, where the first time offset parameter is a time offset of a time of arrival of traffic data of the second terminal device with respect to the predefined first time reference point.

With reference to the first aspect, in some implementations of the first aspect, before the first terminal device receives the first information from the second terminal device, the method further includes: the first terminal device sends a second time offset parameter to the second terminal device, where the second time offset parameter is a time offset of a subframe #0 of a Direct Frame Number (DFN) #0 with respect to a predefined first time reference point.

Based on the above technical scheme, the second terminal device determines the first time offset parameter according to the received second time offset parameter, and forwards the second service model containing the first time offset parameter to the network device through the first terminal device, so that the complexity of the network device side can be saved, and the existing Uu port reporting service model is reused.

With reference to the first aspect, in certain implementations of the first aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of traffic data of the second terminal device with respect to a predefined second time reference point; the second traffic model further comprises a first time offset parameter indicating a time offset of the arrival time of the traffic data of the second terminal device with respect to a predefined first time reference point, the method further comprising: the first terminal device determines the first time offset parameter according to the third time offset parameter.

Based on the above technical scheme, the first terminal device determines the first time offset parameter according to the received third time offset parameter, and forwards the second service model containing the first time offset parameter to the network device, so that the complexity of the network device side can be saved, and the existing Uu port reporting service model is reused.

With reference to the first aspect, in certain implementations of the first aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of traffic data of the second terminal device with respect to a predefined second time reference point, and the method further includes: the first terminal device sends a second time offset parameter to the network device, the second time offset parameter being a time offset of subframe #0 of the DFN #0 with respect to a predefined first time reference point.

With reference to the first aspect, in certain implementations of the first aspect, the first temporal reference point includes subframe #0 of a System Frame Number (SFN) # 0.

With reference to the first aspect, in certain implementations of the first aspect, the second time reference point includes a subframe #0 of the DFN #0 or a Global Navigation Satellite System (GNSS) absolute time point.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the first terminal device receives a sidelink configured grant (SL CG) configuration from the network device, where the SL CG further carries third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs; the first terminal device forwards the SL CG configuration to the second terminal device.

Based on the above technical solution, in the case that there are a plurality of second terminal devices or a plurality of terminal device groups, the first terminal device may determine, through the third information and/or the fourth information included in the SL CG configuration, which second terminal device the SL CG resource allocated by the network device is used for or which member terminal device in the terminal device group is used for transmitting the service data.

In a second aspect, a method for acquiring SL resources is provided, where the method includes: the first terminal device receives a third service model from the second terminal device, the third service model is used for requesting SL resources, the third service model comprises a time offset parameter, and the time offset parameter is used for determining the time offset of the arrival time of service data transmitted by the second terminal device relative to a predefined first time reference point; and the first terminal equipment forwards the third service model to network equipment.

Based on the above technical solution, by explicitly defining the time offset parameter carried in the third service model generated by the second terminal device, synchronization or alignment of the second terminal device and the network device in the time domain can be achieved, so that the network device effectively configures the SL CG allocated to the second terminal device by the first terminal device.

With reference to the second aspect, in some implementations of the second aspect, the time offset parameter is a first time offset parameter, and the first time offset parameter is a time offset of a time of arrival of the service data transmitted by the second terminal device with respect to a predefined first time reference point.

Based on the above technical scheme, the second terminal device determines the first time offset parameter according to the received second time offset parameter, and forwards the third service model containing the first time offset parameter to the network device through the first terminal device, so that the complexity of the network device side can be saved, and the existing Uu port reporting service model is reused.

With reference to the second aspect, in some implementations of the second aspect, the time offset parameter is a third time offset parameter, and the third time offset parameter is a time offset of a time of arrival of the service data of the second terminal device with respect to a predefined second time reference point; the method further comprises the following steps: the first terminal device sends the second time offset parameter to the network device, where the second time offset parameter is a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the second aspect, in certain implementations of the second aspect, the second time reference point includes subframe #0 of the DFN #0 or a GNSS-absolute time point.

With reference to the second aspect, in some implementations of the second aspect, before the first terminal device receives the third service model from the second terminal device, the method further includes: the first terminal device sends a second time offset parameter to the second terminal device, the second time offset parameter being a time offset of subframe #0 of the DFN #0 with respect to a predefined first time reference point.

With reference to the second aspect, in certain implementations of the second aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the first terminal device receiving the SL CG configuration from the network device; the first terminal device forwards the SL CG configuration to the second terminal device.

In a third aspect, a method for acquiring SL resources is provided, where the method includes: the first terminal device receives a third service model from the second terminal device, the third service model is used for requesting the SL resource, the first service model comprises a third time offset parameter, and the third time offset parameter is the time offset of the arrival time of the service data of the second terminal device relative to a predefined second time reference point; the first terminal device generates a fourth service model based on the first service model, the fourth service model includes a first time offset parameter, the first time offset parameter is determined by the third time offset parameter, and the first time offset parameter is a time offset of the arrival time of service data transmitted by the second terminal device relative to a predefined first time reference point; the first terminal device sends the fourth service model to the network device.

Based on the above technical solution, by explicitly defining the time offset parameter carried in the third service model generated by the second terminal device, synchronization or alignment of the second terminal device and the network device in the time domain can be achieved, so that the network device effectively configures the SL CG allocated to the second terminal device by the first terminal device. And the first terminal device determines the first time offset parameter according to the received third time offset parameter, and forwards the fourth service model containing the first time offset parameter to the network device, so that the complexity of the network device side can be saved, and the existing Uu port reporting service model is reused.

With reference to the third aspect, in certain implementations of the third aspect, the first time reference point includes subframe #0 of SFN #0, and the second time reference point includes subframe #0 of DFN #0 or a GNSS-absolute time point.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first terminal device receiving the SL CG configuration from the network device; the first terminal device forwards the SL CG configuration to the second terminal device.

In a fourth aspect, a communication method is provided, the method comprising: the method comprises the steps that a first terminal device determines that configuration of a second terminal device SL fails, wherein the second terminal device and the first terminal device are in the same terminal device group; the first terminal device sends third indication information to the network device, where the third indication information is used to indicate that the second terminal device SL configuration fails, or the third indication information is used to indicate that the terminal device group SL configuration fails.

Based on the above technical solution, if the configuration of the member terminal device SL in the terminal device group fails, the first terminal device may be triggered to execute Radio Resource Control (RRC) reestablishment. Or triggering the first terminal device to send third indication information indicating that the SL configuration of the member terminal device fails to the network device, so that the network device knows that the SL configuration has problems, and the network device optimizes and updates the SL configuration provided for the terminal device group.

With reference to the fourth aspect, in some implementations of the fourth aspect, the determining, by the first terminal device, that the configuration of the second terminal device SL fails includes: the first terminal equipment determines that the SL configuration of the second terminal equipment fails based on the received SL configuration failure indication from the second terminal equipment; or the first terminal device determines that the second terminal device SL configuration fails under the condition that the timer is overtime and still does not receive the SL configuration failure success indication from the second terminal device.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, if the third indication information is used to indicate that the configuration of the second terminal device SL fails, before the first terminal device determines that the configuration of the second terminal device SL fails, the method further includes: the first terminal device sends a radio resource control RRC reconfiguration complete message to the network device, where the RRC reconfiguration complete message is used to indicate that the first terminal device SL is successfully configured.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, if the third indication information is used to indicate that the configuration of the terminal device group SL fails, after the first terminal device determines that the configuration of the second terminal device SL fails, the method further includes: the first terminal device triggers RRC re-establishment.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, if the third indication information is used to indicate that the configuration of the second terminal device SL fails, the third indication information also carries identification information of the second terminal device.

Based on the above technical solution, the network device may identify which member terminal device SL configuration in the terminal device group is failed specifically according to the identification information of the second terminal device carried in the third indication information, so that the SL configuration provided for the terminal device group may be optimized and updated reasonably.

With reference to the fourth aspect, in some implementations of the fourth aspect, before the first terminal device sends the first indication information to the network device, the method further includes: the first terminal device sends group information of the terminal device group to the network device, the group information including one or more of: the group identifier of the terminal device group, the frequency information of the terminal device group, the L2 identifier of each terminal device in the terminal device group, and the group identifier or index of each terminal device in the terminal device group.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the first terminal equipment receives the measurement result from the second terminal equipment; the first terminal device sends the measurement result and the identification information of the second terminal device to the network device.

Based on the technical scheme, under the condition that the states and positions of the terminal devices in the terminal device group are different, the member terminal devices in the terminal device group are allowed to report the measurement result to the network device through the head terminal device in the terminal device group. Therefore, the network equipment optimizes and updates the SL resource pool configuration provided for each terminal equipment in the terminal equipment group according to the received measurement result.

With reference to the fourth aspect, in some implementations of the fourth aspect, the identification information of the second terminal device includes third information for identifying the second terminal device, or the third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the third information includes one or more of: the L2 identification of the second terminal device, the intra-group identification or index of the second terminal device.

With reference to the fourth aspect, in some implementations of the fourth aspect, the fourth information includes a group identification or an index of the terminal device group.

In a fifth aspect, a method for acquiring SL resources is provided, where the method includes: the network equipment receives second information from first terminal equipment, wherein the second information carries identification information of second terminal equipment, the second information is used for requesting SL resources for the second terminal equipment, and the second information is generated by the first terminal equipment based on first information from the second terminal equipment; the network equipment generates resource allocation information according to the second information; the network device sends the resource allocation information to the first terminal device.

Based on the above technical solution, the first terminal device generates the second information based on the first information from the second terminal device, and the second information carries the identification information of the second terminal device. After the first terminal device sends the second information to the network device, the network device can identify, according to the identification information of the second terminal device, that the SL resource requested by the second information is used for the second terminal device to transmit the service data, so that the SL resource can be more accurately and reasonably allocated to the second terminal device.

With reference to the fifth aspect, in some implementations of the fifth aspect, the identification information includes third information for identifying the second terminal device, or third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.

Based on the above technical solution, in different communication scenarios, the second information generated by the first terminal device based on the first information may carry different identification information of the second terminal device. Therefore, under different communication scenarios, the network device may identify that the SL resource requested by the second information is used for the second terminal device to transmit the service data, so that the SL resource may be more accurately and reasonably allocated to the second terminal device. For example, if the second terminal device requests the network device for the SL resource through the relay (the first terminal device), the identification information of the second terminal device carried by the second information generated by the first terminal device based on the first information may include third information for identifying the second terminal device, and the network device may identify the second terminal device based on the third information. For another example, when the first terminal device and the second terminal device belong to the same terminal device group, the identification information of the second terminal device may include third information for identifying the second terminal device and fourth information for identifying the terminal device group, and the network device may identify the second terminal device based on the third information and the fourth information.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the third information includes one or more of: the L2 identification of the second terminal device, the intra-group identification or index of the second terminal device.

With reference to the fifth aspect, in some implementations of the fifth aspect, the fourth information includes a group identification or an index of the terminal device group.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the first information includes a first BSR, and the second information includes a second BSR generated based on the first BSR.

With reference to the fifth aspect, in some implementations of the fifth aspect, the resource allocation information is DCI, where the DCI includes first indication information and a first SCI, the first indication information is used to indicate a first SL resource, the first SL resource is used to transmit the first SCI, the first SCI includes second indication information and a second SCI, the second indication information is used to indicate a second SL resource, the second SL resource is used to transmit the second SCI, the second SCI is used to indicate a third SL resource, and the third SL resource is used for the second terminal device to transmit service data.

With reference to the fifth aspect, in some implementations of the fifth aspect, the resource allocation information is DCI, where the DCI is used to indicate SL resources, the SL resources include a third SL resource, and the third SL resource is used for the second terminal device to transmit service data.

With reference to the fifth aspect, in some implementations of the fifth aspect, the DCI further includes third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the fifth aspect, in some implementations of the fifth aspect, the first information includes a first business model, and the second information includes a second business model generated based on the first business model.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the first traffic model further includes a first time offset parameter, which is a time offset of the arrival time of the traffic data of the second terminal device with respect to a predefined first time reference point.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of traffic data of the second terminal device with respect to a predefined second time reference point; the second traffic model further comprises a first time offset parameter for indicating a time offset of the time of arrival of traffic data of the second terminal device with respect to a predefined first time reference point, the third time offset parameter being determined in dependence of the first time offset parameter.

With reference to the fifth aspect, in some implementations of the fifth aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of traffic data of the second terminal device with respect to a predefined second time reference point, and the method further includes: the network device receives a second time offset parameter from the first terminal device, the second time offset parameter being a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the second point in time reference comprises subframe #0 of the DFN #0 or a GNSS-absolute time point.

With reference to the fifth aspect, in some implementations of the fifth aspect, the resource allocation information is configured by an SL CG, and the SL CG further carries third information used for identifying the second terminal device and/or fourth information used for identifying a terminal device group to which the second terminal device belongs.

In a sixth aspect, a method for acquiring SL resources is provided, the method comprising: the network equipment receives a third service model forwarded by the first terminal equipment and coming from the second terminal equipment, wherein the third service model is used for requesting SL resources and comprises a time offset parameter which is used for determining the time offset of the arrival time of service data transmitted by the second terminal equipment relative to a predefined first time reference point; the network equipment generates resource allocation information according to the third service model; the network device sends resource allocation information to the first terminal device.

With reference to the sixth aspect, in some implementations of the sixth aspect, the time offset parameter is a first time offset parameter, and the first time offset parameter is a time offset of a time of arrival of the traffic data transmitted by the second terminal device with respect to a predefined first time reference point.

With reference to the sixth aspect, in some implementations of the sixth aspect, the time offset parameter is a third time offset parameter, and the third time offset parameter is a time offset of a time of arrival of the service data of the second terminal device with respect to a predefined second time reference point; the method further comprises the following steps: the network device receives a second time offset parameter from the first terminal device, the second time offset parameter being a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the second point in time reference comprises subframe #0 of DFN #0 or a GNSS-absolute point in time.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the resource allocation information is configured for SL CG.

In a seventh aspect, a method for acquiring SL resources is provided, where the method includes: generating a third service model by the second terminal device, wherein the third service model is used for requesting to acquire the SL resource and comprises a time offset parameter, and the time offset parameter is used for determining the time offset of the arrival time of the service data transmitted by the second terminal device relative to a predefined first time reference point; the second terminal device sends the third service model to the first terminal device.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the time offset parameter is a first time offset parameter, and the first time offset parameter is a time offset of the arrival time of the service data transmitted by the second terminal device with respect to a predefined first time reference point.

With reference to the seventh aspect, in some implementations of the seventh aspect, the time offset parameter is a third time offset parameter, and the third time offset parameter is a time offset of a time of arrival of the traffic data of the second terminal device with respect to a predefined second time reference point

With reference to the seventh aspect, in some implementations of the seventh aspect, the second time reference point includes subframe #0 of DFN #0 or an absolute time point of GNSS.

With reference to the seventh aspect, in some implementations of the seventh aspect, before the second terminal device sends the third traffic model to the first terminal device, the method further includes: the second terminal device receives a second time offset parameter from the first terminal device, the second time offset parameter being a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the method further includes: the second terminal device receives the SL CG configuration from the first terminal device.

In an eighth aspect, a method for acquiring SL resources is provided, the method comprising: generating, by the second terminal device, a third service model, where the third service model is used for requesting SL resources, and the third service model includes a third time offset parameter, where the third time offset parameter is a time offset of arrival time of service data of the second terminal device relative to a predefined second time reference point; the second terminal device sends the third service model to the first terminal device.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the second time reference point includes subframe #0 of DFN #0 or a GNSS-absolute time point.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the method further includes: the second terminal device receives the SL CG configuration forwarded by the first terminal device.

A ninth aspect provides a communication device for acquiring SL resources, the communication device comprising a processing unit and a transceiving unit; the receiving and sending unit is used for receiving first information from a second terminal device, and the first information is used for requesting SL resources; the processing unit is configured to generate second information based on the first information, where the second information carries identification information of the second terminal device, and is used to request the SL resource for the second terminal device; the transceiver unit is further configured to send the second information to the network device.

With reference to the ninth aspect, in some implementations of the ninth aspect, the identification information of the second terminal device includes third information for identifying the second terminal device, or third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the third information includes one or more of: the L2 identification of the second terminal device, the intra-group identification or index of the second terminal device.

With reference to the ninth aspect, in some implementations of the ninth aspect, the fourth information includes a group identification or an index of the terminal device group.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the first information includes a first BSR, and the second information includes a second BSR generated based on the first BSR.

With reference to the ninth aspect, in some implementations of the ninth aspect, the transceiving unit is further configured to receive DCI from the network device, where the DCI includes first indication information and a first SCI, the first indication information is used to indicate a first SL resource, and the first SL resource is used to transmit the first SCI; the transceiving unit sends the first SCI to the second terminal device through the first SL resource, where the first SCI includes second indication information and a second SCI, the second indication information is used to indicate a second SL resource, the second SL resource is used to transmit the second SCI, the second SCI is used to indicate a third SL resource, and the third SL resource is used for the second terminal device to transmit service data.

With reference to the ninth aspect, in some implementations of the ninth aspect, the transceiving unit is further configured to receive DCI from the network device, where the DCI is used to indicate SL resources; the processing unit is further configured to generate a second SCI according to the SL resource indicated by the DCI; the transceiving unit is further configured to send a second SCI to the second terminal device, where the second SCI is used to indicate a third SL resource, the third SL resource is used for the second terminal device to transmit service data, and the third SL resource is included in the SL resource indicated by the DCI.

With reference to the ninth aspect, in some implementations of the ninth aspect, the DCI further includes third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the ninth aspect, in some implementations of the ninth aspect, the first information includes a first business model, and the second information includes a second business model generated based on the first business model.

With reference to the ninth aspect, in some implementations of the ninth aspect, the first traffic model further includes a first time offset parameter, which is a time offset of the arrival time of the traffic data of the second terminal device with respect to the predefined first time reference point.

With reference to the ninth aspect, in some implementations of the ninth aspect, before the transceiving unit receives the first information from the second terminal device, the transceiving unit is further configured to transmit a second time offset parameter to the second terminal device, where the second time offset parameter is a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the ninth aspect, in some implementations of the ninth aspect, the first service model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of the service data of the second terminal device with respect to a predefined second time reference point; the second traffic model further comprises a first time offset parameter for indicating a time offset of the time of arrival of traffic data of the second terminal device with respect to a predefined first time reference point, the processing unit being further configured to determine the first time offset parameter from the third time offset parameter.

With reference to the ninth aspect, in some implementations of the ninth aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of the traffic data of the second terminal device relative to a predefined second time reference point, and the transceiver unit is further configured to transmit a second time offset parameter to the network device, where the second time offset parameter is a time offset of the subframe #0 of the DFN #0 relative to the predefined first time reference point.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the first temporal reference point includes subframe #0 of the system frame number SFN # 0.

With reference to the ninth aspect, in some implementations of the ninth aspect, the second time reference point includes subframe #0 of the DFN #0 or a GNSS-absolute time point.

With reference to the ninth aspect, in some implementations of the ninth aspect, the transceiver unit is further configured to receive an SL CG configuration from the network device, where the SL CG further carries third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs; the transceiver unit is further configured to forward the SL CG configuration to the second terminal device.

A tenth aspect provides a communication apparatus for acquiring SL resources, the communication apparatus comprising a transceiving unit; the transceiving unit is configured to receive a third traffic model from a second terminal device, where the third traffic model is used to request SL resources, and the third traffic model includes a time offset parameter, where the time offset parameter is used to determine a time offset of arrival time of traffic data transmitted by the second terminal device with respect to a predefined first time reference point; the transceiving unit is further configured to forward the third service model to a network device.

With reference to the tenth aspect, in some implementations of the tenth aspect, the time offset parameter is a first time offset parameter, and the first time offset parameter is a time offset of the arrival time of the service data transmitted by the second terminal device relative to a predefined first time reference point.

With reference to the tenth aspect, in some implementations of the tenth aspect, the time offset parameter is a third time offset parameter, and the third time offset parameter is a time offset of a time of arrival of the service data of the second terminal device with respect to a predefined second time reference point; the transceiver unit is further configured to transmit the second time offset parameter to the network device, where the second time offset parameter is a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the second time reference point includes subframe #0 of the DFN #0 or a GNSS-absolute time point.

With reference to the tenth aspect, in some implementations of the tenth aspect, before the transceiver unit is configured to receive the third traffic model from the second terminal device, the transceiver unit is further configured to transmit a second time offset parameter to the second terminal device, where the second time offset parameter is a time offset of subframe #0 of the DFN #0 with respect to a predefined first time reference point.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the transceiving unit is further configured to receive an SL CG configuration from the network device; the transceiver unit is further configured to forward the SL CG configuration to the second terminal device.

In an eleventh aspect, a communication device for acquiring SL resources is provided, the communication device comprising a processing unit and a transceiving unit; the transceiving unit is configured to receive a third service model from a second terminal device, where the third service model is used to request SL resources, and the first service model includes a third time offset parameter, where the third time offset parameter is a time offset of arrival time of service data of the second terminal device relative to a predefined second time reference point; the processing unit is configured to generate a fourth traffic model based on the first traffic model, where the fourth traffic model includes a first time offset parameter, the first time offset parameter is determined by the third time offset parameter, and the first time offset parameter is a time offset of an arrival time of traffic data transmitted by the second terminal device with respect to a predefined first time reference point; the transceiving unit is further configured to send the fourth service model to a network device.

With reference to the eleventh aspect, in certain implementations of the eleventh aspect, the first time reference point includes subframe #0 of SFN #0, and the second time reference point includes subframe #0 of DFN #0 or a GNSS-absolute time point.

With reference to the eleventh aspect, in certain implementations of the eleventh aspect, the transceiving unit is further configured to receive a SL CG configuration from the network device; the transceiver unit is further configured to forward the SL CG configuration to the second terminal device.

A twelfth aspect provides a communication device, comprising a processing unit and a transceiving unit; the processing unit is configured to determine that a configuration of a second terminal device SL fails, where the second terminal device and the first terminal device are in the same terminal device group; the transceiver unit sends third indication information to the network device, where the third indication information is used to indicate that the configuration of the second terminal device SL fails, or the third indication information is used to indicate that the configuration of the terminal device group SL fails.

With reference to the twelfth aspect, in some implementations of the twelfth aspect, the processing unit is configured to determine that the configuration of the second terminal device SL fails, and the determining includes: the transceiver unit is configured to determine that the second terminal device SL configuration fails based on the received SL configuration failure indication from the second terminal device; or the transceiver unit is configured to determine that the second terminal device SL configuration fails when the timer expires and the SL configuration failure success indication from the second terminal device is not received.

With reference to the twelfth aspect, in some implementation manners of the twelfth aspect, if the third indication information is used to indicate that the configuration of the second terminal device SL fails, before the processing unit is configured to determine that the configuration of the second terminal device SL fails, the transceiver unit is further configured to send an RRC reconfiguration complete message to the network device, where the RRC reconfiguration complete message is used to indicate that the configuration of the first terminal device SL succeeds.

With reference to the twelfth aspect, in some implementation manners of the twelfth aspect, if the third indication information is used to indicate that the configuration of the terminal device group SL fails, after the processing unit is configured to determine that the configuration of the second terminal device SL fails, the processing unit is further configured to trigger RRC reestablishment.

With reference to the twelfth aspect, in some implementation manners of the twelfth aspect, if the third indication information is used to indicate that the configuration of the second terminal device SL fails, the third indication information also carries identification information of the second terminal device.

With reference to the twelfth aspect, in some implementations of the twelfth aspect, before the transceiving unit is configured to send the first indication information to the network device, the transceiving unit is further configured to send group information of the terminal device group to the network device, where the group information includes one or more of: the group identifier of the terminal device group, the frequency information of the terminal device group, the L2 identifier of each terminal device in the terminal device group, and the group identifier or index of each terminal device in the terminal device group.

With reference to the twelfth aspect, in some implementations of the twelfth aspect, the transceiver unit is further configured to receive a measurement result from the second terminal device; the transceiver unit is further configured to send the measurement result and the identification information of the second terminal device to the network device.

With reference to the twelfth aspect, in some implementations of the twelfth aspect, the identification information of the second terminal device includes third information for identifying the second terminal device, or the third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the twelfth aspect, in certain implementations of the twelfth aspect, the third information includes one or more of: the L2 identification of the second terminal device, the intra-group identification or index of the second terminal device.

With reference to the twelfth aspect, in some implementations of the twelfth aspect, the fourth information includes a group identifier or an index of the terminal device group.

In a thirteenth aspect, a communication device for acquiring SL resources is provided, the communication device comprising a processing unit and a transceiving unit; the receiving and sending unit is configured to receive second information from a first terminal device, where the second information carries identification information of a second terminal device, the second information is used to request SL resources for the second terminal device, and the second information is generated by the first terminal device based on first information from the second terminal device; the processing unit is used for generating resource allocation information according to the second information; the transceiver unit is further configured to send the resource allocation information to the first terminal device.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the identification information includes third information for identifying the second terminal device, or third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the third information includes one or more of: the L2 identification of the second terminal device, the intra-group identification or index of the second terminal device.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the fourth information includes a group identification or index of the group of terminal devices.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the first information includes a first BSR, and the second information includes a second BSR generated based on the first BSR.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the resource allocation information is DCI, where the DCI includes first indication information and a first SCI, the first indication information is used to indicate a first SL resource, the first SL resource is used to transmit the first SCI, the first SCI includes second indication information and a second SCI, the second indication information is used to indicate a second SL resource, the second SL resource is used to transmit the second SCI, the second SCI is used to indicate a third SL resource, and the third SL resource is used for the second terminal device to transmit service data.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the resource allocation information is DCI, and the DCI is used to indicate SL resources, where the SL resources include a third SL resource, and the third SL resource is used for the second terminal device to transmit traffic data.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the DCI further includes third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the first information includes a first business model, and the second information includes a second business model generated based on the first business model.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the first traffic model further includes a first time offset parameter, which is a time offset of the arrival time of the traffic data of the second terminal device with respect to a predefined first time reference point.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of the arrival time of the traffic data of the second terminal device with respect to a predefined second time reference point; the second traffic model further comprises a first time offset parameter for indicating a time offset of the time of arrival of traffic data of the second terminal device with respect to a predefined first time reference point, the third time offset parameter being determined in dependence of the first time offset parameter.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the first traffic model further includes a third time offset parameter, where the third time offset parameter is a time offset of a time of arrival of traffic data of the second terminal device with respect to a predefined second time reference point, and the transceiver unit is further configured to receive a second time offset parameter from the first terminal device, where the second time offset parameter is a time offset of subframe #0 of DFN #0 with respect to the predefined first time reference point.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the thirteenth aspect, in certain implementations of the thirteenth aspect, the second time reference point includes subframe #0 of the DFN #0 or a GNSS-absolute time point.

With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the resource allocation information is configured by an SL CG, and the SL CG further carries third information used for identifying the second terminal device and/or fourth information used for identifying a terminal device group to which the second terminal device belongs.

In a fourteenth aspect, a communication device for acquiring SL resources is provided, the communication device comprising a processing unit and a transceiving unit; the receiving and sending unit is configured to receive a third service model forwarded by the first terminal device from the second terminal device, where the third service model is used to request an SL resource, and the third service model includes a time offset parameter, and the time offset parameter is used to determine a time offset of arrival time of service data transmitted by the second terminal device with respect to a predefined first time reference point; the processing unit is further configured to generate resource allocation information according to the third service model; the transceiver unit is further configured to send resource allocation information to the first terminal device.

With reference to the fourteenth aspect, in some implementations of the fourteenth aspect, the time offset parameter is a first time offset parameter, and the first time offset parameter is a time offset of a time of arrival of the traffic data transmitted by the second terminal device with respect to a predefined first time reference point.

With reference to the fourteenth aspect, in some implementations of the fourteenth aspect, the time offset parameter is a third time offset parameter, and the third time offset parameter is a time offset of a time of arrival of the service data of the second terminal device with respect to a predefined second time reference point; the transceiver unit is further configured to receive a second time offset parameter from the first terminal device, where the second time offset parameter is a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the fourteenth aspect, in some implementations of the fourteenth aspect, the second time reference point includes subframe #0 of DFN #0 or an absolute time point of GNSS.

With reference to the fourteenth aspect, in certain implementations of the fourteenth aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the fourteenth aspect, in some implementations of the fourteenth aspect, the resource allocation information is configured for SL CG.

In a fifteenth aspect, a communication device for acquiring SL resources is provided, the communication device comprising a processing unit and a transceiving unit; the processing unit is configured to generate a third service model, where the third service model is used to request to acquire an SL resource, and the third service model includes a time offset parameter, where the time offset parameter is used to determine a time offset of arrival time of service data transmitted by the second terminal device with respect to a predefined first time reference point; the transceiving unit is configured to send the third service model to the first terminal device.

With reference to the fifteenth aspect, in certain implementations of the fifteenth aspect, the time offset parameter is a first time offset parameter, and the first time offset parameter is a time offset of the arrival time of the traffic data transmitted by the second terminal device with respect to a predefined first time reference point.

With reference to the fifteenth aspect, in certain implementations of the fifteenth aspect, the time offset parameter is a third time offset parameter, and the third time offset parameter is a time offset of the arrival time of the traffic data of the second terminal device relative to a predefined second time reference point

With reference to the fifteenth aspect, in certain implementations of the fifteenth aspect, the second point of time reference comprises subframe #0 of DFN #0 or a GNSS-absolute time point.

With reference to the fifteenth aspect, in some implementations of the fifteenth aspect, before the transceiver unit is configured to transmit the third traffic model to the first terminal device, the transceiver unit is further configured to receive a second time offset parameter from the first terminal device, where the second time offset parameter is a time offset of subframe #0 of DFN #0 with respect to a predefined first time reference point.

With reference to the fifteenth aspect, in certain implementations of the fifteenth aspect, the first time reference point includes subframe #0 of SFN # 0.

With reference to the fifteenth aspect, in certain implementations of the fifteenth aspect, the transceiver unit is further configured to receive the SL CG configuration from the first terminal device.

In a sixteenth aspect, a communication device for acquiring SL resources is provided, the communication device comprising a processing unit and a transceiving unit; the processing unit is configured to generate a third service model, where the third service model is used to request SL resources, and the third service model includes a third time offset parameter, where the third time offset parameter is a time offset of arrival time of service data of the second terminal device relative to a predefined second time reference point; the transceiving unit is configured to send the third service model to the first terminal device.

With reference to the sixteenth aspect, in certain implementations of the sixteenth aspect, the second point of time reference comprises subframe #0 of DFN #0 or a GNSS-absolute time point.

With reference to the sixteenth aspect, in some implementations of the sixteenth aspect, the transceiver unit is further configured to receive the SL CG configuration forwarded by the first terminal device.

In a seventeenth aspect, a communication apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute instructions or data in the memory to implement the method of any of the possible implementations of the first to fourth aspects and the first to fourth aspects. Wherein the communication device further comprises a memory. Wherein the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a first terminal device. When the communication device is a first terminal device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip or a system of chips configured in the first terminal equipment. When the communication device is a chip or a system of chips configured in a terminal equipment, the communication interface may be an input/output interface.

Wherein the transceiver may be a transceiver circuit. Wherein the input/output interface may be an input/output circuit.

In an eighteenth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute instructions or data in the memory to implement the method of any one of the possible implementations of the fifth to sixth aspects and of the fifth to sixth aspects. Wherein the communication device further comprises a memory. Wherein the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip or a system of chips configured in the network device. When the communication device is a chip or a system of chips configured in a network device, the communication interface may be an input/output interface.

In a nineteenth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is configured to execute instructions or data in the memory to implement the method in any possible implementation manner of the seventh to eighth aspects and the seventh to eighth aspects. Wherein the communication device further comprises a memory. Wherein the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a second terminal device. When the communication device is a second terminal device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip or a system of chips configured in the second terminal equipment. When the communication device is a chip or a system of chips configured in a terminal equipment, the communication interface may be an input/output interface.

In a twentieth aspect, there is provided a processor comprising: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal through the input circuit and send a signal through the output circuit, so that the processor performs the method in any possible implementation manner of the first to eighth aspects and the first to eighth aspects.

In a specific implementation process, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.

In a twenty-first aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal through the receiver and transmit a signal through the transmitter to perform the method of any one of the possible implementations of the first to eighth aspects and the first to eighth aspects.

The number of the processors is one or more, and the number of the memories is one or more.

Wherein the memory may be integrated with the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It will be appreciated that the associated data interaction process, for example, sending the indication information, may be a process of outputting the indication information from the processor, and receiving the capability information may be a process of receiving the input capability information from the processor. In particular, data output by the processor may be output to a transmitter and input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.

The processing device in the twenty-first aspect may be one or more chips, or may be a system of chips. The processor in the processing device may be implemented by hardware or may be implemented by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.

In a twenty-second aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes the method of any one of the possible implementations of the first to eighth aspects and the first to eighth aspects described above to be performed.

A twenty-third aspect provides a computer-readable storage medium storing a computer program (which may also be referred to as code or instructions) which, when run on a computer, causes the computer to perform the method of any one of the possible implementations of the first to eighth aspects and the first to eighth aspects.

A twenty-fourth aspect provides a communication system comprising: the aforementioned network device, and/or the aforementioned first terminal device and second terminal device.

Drawings

Fig. 1 is a schematic diagram of a communication system of a method provided in an embodiment of the present application.

Fig. 2 is a schematic flowchart of a method for acquiring SL resources according to an embodiment of the present application.

Fig. 3 is a schematic flowchart of a method for acquiring SL resources according to another embodiment of the present application.

Fig. 4 is a schematic diagram of a first BSR provided in an embodiment of the present application.

Fig. 5 is a schematic diagram of a second BSR provided in an embodiment of the present application.

Fig. 6 is a schematic diagram of a time offset parameter provided in an embodiment of the present application.

Fig. 7 is a schematic flowchart of a method for acquiring SL resources according to another embodiment of the present application.

Fig. 8 is a schematic flowchart of a communication method provided in an embodiment of the present application.

Fig. 9 is a schematic diagram of an SL communication environment of each terminal device in a terminal device group according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication device provided in an embodiment of the present application.

Fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Fig. 12 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Universal Mobile Telecommunications System (UMTS), a universal microwave access (WiMAX) communication system, a future fifth generation (5th generation, 5G) mobile communication system, or a new radio access technology (NR). The 5G mobile communication system may include a non-independent Network (NSA) and/or an independent network (SA), among others.

The technical scheme provided by the application can also be applied to Machine Type Communication (MTC), Long Term Evolution-machine (LTE-M) communication between machines, device to device (D2D) network, machine to machine (M2M) network, internet of things (IoT) network, or other networks. The IoT network may comprise, for example, a car networking network. The communication modes in the car networking system are collectively referred to as car-to-other devices (V2X, X may represent anything), for example, the V2X may include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) or vehicle to network (V2N) communication, etc.

The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system and the like. This is not limited in this application.

In the embodiment of the present application, the network device may be any device having a wireless transceiving function. Such devices include, but are not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (e.g., home evolved Node B or home Node B, HNB), baseband unit (BBU), Access Point (AP) in wireless fidelity (WiFi) system, wireless relay Node, wireless backhaul Node, Transmission Point (TP) or Transmission and Reception Point (TRP), etc., and may also be 5G, such as NR, gbb in the system, or transmission point (TRP or TP), one or a group of base stations in the 5G system may also include multiple antennas, or panels, and may also be configured as network panels or NB, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include an Active Antenna Unit (AAU). The CU implements part of the function of the gNB, and the DU implements part of the function of the gNB, for example, the CU is responsible for processing non-real-time protocols and services, and implementing functions of a Radio Resource Control (RRC) layer and a packet data convergence layer (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing and active antenna related functions. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or by the DU + AAU under this architecture. It is to be understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this embodiment of the present application.

In this embodiment, the terminal device may be referred to as a User Equipment (UE), a terminal (terminal), a Mobile Station (MS), a mobile terminal (mobile terminal), and the like; the terminal device may also communicate with one or more core networks via a Radio Access Network (RAN). The terminal device can also be called an access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capability, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a vehicle with communication capability, a wearable device, a terminal device in a future 5G network, and so on. The embodiment of the present application does not limit this.

Fig. 1 is a schematic diagram of a communication system suitable for use in the method provided by the embodiments of the present application.

As shown in fig. 1, the communication system 100 may include at least one network device, such as the network device 111 shown in fig. 1, and the communication system 100 includes at least two terminal devices, such as the terminal device 121 and the terminal device 122 shown in fig. 1. The wireless direct communication link formed between terminal device 121 and terminal device 122 may be referred to as SL. For example, network device 111 may schedule for end device 121 and/or end device 122 SL resources required for communication transmissions at SL that may be used for unicast, multicast, and broadcast type traffic data transmissions for end device 121 and/or end device 122. As another example, network device 111 may schedule SL resources for end device 122 via end device 121, which may be used for transmission of unicast, multicast, and broadcast type traffic data for end device 122.

It should be understood that the drawings are only schematic and show the SL link between two terminal devices, but this should not limit the present application in any way. In the communication system, a larger number of terminal devices may be included, and communication links between terminal devices may be referred to as SL links. The network device may also schedule SL resources for more terminal devices, so as to be used for transmission of service data of the terminal devices, such as unicast and multicast.

The end devices may communicate unicast, multicast, and broadcast over the SL. For example, in fig. 1, the terminal device 121 transmits data to the terminal device 122 in a unicast manner, and in this case, only the terminal device 122 can receive the data transmitted by the terminal device 121. For example, in fig. 1, the terminal device 121 transmits data in a multicast manner, and when the terminal device 122 and the terminal device 121 belong to the same terminal device group, the terminal device 122 may receive the data transmitted by the terminal device 121. It should be understood that although only two

end devices

121 and 122 are shown in fig. 1, in a multicast scenario, more end devices may be included in a group of end devices. That is, the data transmitted by terminal device 121 may be received by more terminal devices within the group of terminal devices, including terminal device 122. Although not shown in the drawings, this should not be construed as limiting the present application in any way.

The communication process between terminal device 122 and network device 111 is implemented by terminal device 121. For example, terminal device 121 may act as a relay station for terminal device 122 to request SL resources from network device 111 and for network device 111 to schedule SL resources for terminal device 122.

It should be understood that, for convenience of understanding only, the terminal device 121, the terminal device 122, and the network device 111 are schematically illustrated in fig. 1, but this should not limit the present application in any way, and a greater number of network devices may also be present in the communication system, and a greater or lesser number of terminal devices may also be included, which is not limited in this embodiment of the present application.

There are many ways for the terminal device to acquire the SL resource.

For example, the terminal device sends a Buffer Status Report (BSR) to the network device, the network device provides SL resource scheduling to the terminal device based on the BSR, and the terminal device uses the SL resource to complete sending of current data. For another example, the terminal device sends a service model to the network device, the network device provides a periodic SL Configuration Grant (CG) resource to the terminal device based on the service model, and after receiving the SL CG resource, the terminal device can directly use the SL CG resource to transmit service data without requesting scheduling or configuration of the network device.

However, in some scenarios, if a terminal device (e.g., the terminal device 122 in fig. 1) requests a network device to acquire an SL resource through another terminal device (e.g., the terminal device 121 in fig. 1), the network device may not be able to distinguish from which terminal device the request is from, and thus cannot accurately schedule the SL resource. For example, in a multicast scenario, terminal device 122 may send a BSR to a network device through terminal device 121 belonging to the same terminal device group to request to acquire SL resources. Terminal device 122 first sends a BSR to terminal device 121, and then terminal device 121 forwards the BSR to the network device. In this process, the BSR sent by the terminal device 122 to the terminal device 121 carries destination identification information, which may be, for example, a group identifier. However, terminal device 121 does not know the SL service of terminal device 122 that is not related to terminal device 121, and therefore terminal device 121 cannot understand the destination identification information in the BSR from terminal device 122. Further, the terminal device 121 forwards the BSR to the network device, and the network device cannot identify whether the BSR is generated by the terminal device 121 or the terminal device 122. Therefore, the network device cannot accurately schedule the SL resource for the terminal device 122, which results in low reliability of the second terminal device for transmitting the service data and poor service experience.

When the second terminal device requests the network device for the SL CG resource configuration through the first terminal device, the states of the second terminal device and the first terminal device, and the connected network devices may be different, and accordingly, configurations related to synchronization with the network device may also be different. In view of this, the present application provides a method for acquiring SL resources, so that a network device accurately schedules resources for a terminal device, in order to improve transmission reliability.

The method provided by the embodiment of the application will be described in detail below with reference to the accompanying drawings.

To facilitate understanding of the embodiments of the present application, the following description is made before describing the embodiments of the present application.

First, in the embodiments of the present application, "for indicating" may include for direct indication and for indirect indication, and may also include explicit indication and implicit indication. If the information indicated by a certain piece of information is referred to as information to be indicated, in a specific implementation process, there are many ways of indicating the information to be indicated, for example, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein an association relationship exists between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other part of the information to be indicated is known or predetermined. For example, indication of information to be indicated can also be implemented by means of pre-agreed (e.g., protocol specification) whether a certain cell exists, thereby reducing the indication overhead to some extent.

Second, in the embodiments shown below, the first, second and various numerical numbers are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. For example, different time offset parameters, different information, etc. are distinguished.

Third, in the embodiments of the present application, the predefinition may be, for example, protocol predefinition, or human predefinition. "predefining" may be implemented by pre-saving corresponding codes, tables or other manners that may be used to indicate related information in devices (e.g., including terminal devices and network devices), and the specific implementation manner of the present application is not limited thereto. Wherein "saving" may refer to saving in one or more memories. The one or more memories may be separate devices or may be integrated in the encoder or decoder, the processor, or the communication device. The one or more memories may also be provided as a portion of a stand-alone device, a portion of which is integrated into a decoder, a processor, or a communication device. The type of memory may be any form of storage medium and is not intended to be limiting of the present application.

Fourth, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the communication field, and may include, for example, an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in the present application.

Fifth, "at least one" means one or more, "a plurality" means two or more. "and/or" describes an association relationship of associated objects, meaning that there may be three relationships, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, and c, may represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b and c. Wherein a, b and c may be single or plural respectively.

Sixthly, in the embodiment of the present application, the descriptions of "when … …", "in … …", "if" and "if" all refer to that a device (e.g., a terminal device or a network device) performs corresponding processing under a certain objective condition, and do not limit the time, and do not require a certain judgment action when the device (e.g., the terminal device or the network device) is implemented, and do not mean that there are other limitations.

Seventhly, the following describes in detail various embodiments with reference to various flowcharts, but it should be understood that the flowcharts and their corresponding embodiments are only illustrative for the convenience of understanding, and should not limit the present application in any way. It is not necessary that each step in the flowcharts be performed, and some steps may be skipped, for example. In addition, the execution sequence of each step is not fixed or limited to that shown in the figures, and the execution sequence of each step should be determined by the function and the inherent logic of each step.

The following embodiments take the interaction between the network device, the first terminal device, and the second terminal device as an example, and describe the method provided by the embodiments in detail. This should not be construed as limiting the application in any way. For example, the terminal devices shown in the following embodiments may be replaced with components (such as a chip, a chip system, a circuit, or the like) configured in a terminal device (such as a first terminal device or a second terminal device). The network devices shown in the following embodiments may also be replaced with components (such as chips, systems of chips, circuits, etc.) configured in the network devices.

The embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as the communication can be performed according to the method provided by the embodiments of the present application by running the program recorded with the code of the method provided by the embodiments of the present application, for example, the execution subject of the method provided by the embodiments of the present application may be a terminal device or a network device, or a functional module capable of calling the program and executing the program in the terminal device or the network device.

Fig. 2 shows a schematic flowchart of a method for acquiring SL resources according to an embodiment of the present application. As shown in fig. 2, the method 200 may include steps 210 through 230, each of which is described in detail below.

In step 210, the second terminal device sends the first information to the first terminal device.

The embodiment of the present application does not specifically limit the relationship between the first terminal device and the second terminal device. For example, the first terminal device and the second terminal device may belong to the same terminal device group, or the first terminal device and the second terminal device may not belong to the same terminal device group.

The terminal device group may be a real terminal device group, such as a terminal device group in a multicast scenario, and a member terminal device in the group may request an SL resource from a network device through a head terminal device (or called an anchor terminal device); or a virtual terminal device group, for example, a plurality of terminal devices request SL resources from the network device through a relay (relay), and the plurality of terminal devices and the relay may form a terminal device group. The specific form of the terminal device group is not limited in the present application. In one implementation, all the second terminal devices that request SL resources from the network device through the first terminal device may be considered to belong to the same terminal device group as the first terminal device.

It can be understood that, if the terminal device group is a terminal device group in a multicast scenario, the first terminal device may be a head terminal device in the terminal device group, and the second terminal device may be a member terminal device in the terminal device group. The terminal device group may comprise at least two terminal devices, such as the first terminal device and the second terminal device as described above. The terminal device group may further include other terminal devices than the first terminal device and the second terminal device. This is not limited in this application. The creation of the terminal device group may be triggered by an Application (APP) or an Access Stratum (AS), and the triggering condition for creating the terminal device group is not specifically limited in the embodiment of the present application.

In addition, the determining method of the head terminal device in the terminal device group is not specifically limited in the embodiment of the present application. For example, the head terminal device in the terminal device group may be an initiator for establishing the terminal device group, or may be a terminal device having a capability of being the head terminal device in the terminal device group, or may be a terminal device preset by a user, or may be a terminal device selected by an application layer, and so on. For the sake of brevity, this is not necessarily an illustration.

The second terminal device may transmit the resource request information to the first terminal device in order to obtain the SL resource for transmitting the service data. For convenience of understanding and distinction, in the embodiment of the present application, resource request information sent by the second terminal device to the first terminal device is denoted as first information.

The embodiment of the present application does not specifically limit the form of the first information. As one example, the first information may be a BSR;

as another example, the first information may be a business model, and the above two different implementations will be described in detail later in conjunction with specific embodiments, which will not be described in detail here.

When the first terminal device receives the first information from the second terminal device, the first terminal device needs to identify the second terminal device. The identification method in the embodiment of the present application is not specifically limited, and may be, for example:

the first method is as follows: the second terminal device sends the first information to the first terminal device by taking the self-allocated L2 identifier as a source identifier, wherein the source identifier is used for communicating with the first terminal device, and the first terminal device identifies the second terminal device through the source identifier.

For example, if the first terminal device and the second terminal device belong to the same terminal device group, the second terminal device may send the first information to the first terminal device by using the group identifier of the terminal device group as the destination identifier and using the L2 identifier allocated to the terminal device group by the second terminal device as the source identifier. The first terminal device identifies which terminal device group is identified by the destination identifier, and identifies which member terminal device in the terminal device group is identified by the source identifier.

For another example, when the first terminal device and the second terminal device communicate via a unicast connection, the second terminal device transmits the first information to the first terminal device with the L2 id allocated to the unicast connection by the first terminal device as the destination id and the L2 id allocated to the unicast connection by the second terminal device as the source id. The first terminal device identifies which terminal device is by means of the destination identifier and/or the source identifier.

The second method comprises the following steps: the first terminal device allocates a SL resource for sending the first information to the first terminal device in advance, and the first terminal device can identify the second terminal device through the SL resource.

For example, the SL resource for transmitting the first information may be pre-allocated, and the SL resource may be, for example, a resource in a physical sidelink shared channel (PSCCH) or a Physical Sidelink Control Channel (PSCCH). Since the first terminal device allocates the SL resource to the second terminal device in advance, the first terminal device can identify the second terminal device that sent the first information when receiving the first information on the SL resource.

It should be understood that the above listed SL resources for transmitting the first information are only examples, and should not limit the present application in any way. The SL resource for transmitting the first information is not limited in the present application.

The method for sending the first information to the first terminal device by the second terminal device is not particularly limited in this embodiment of the application, and for example, the first information may be sent by a multicast method or may be sent by a unicast method.

Before step 210, the network device may provide SL configuration for one or more terminal devices including the first terminal device and the second terminal device, and the method for providing SL configuration is not specifically limited in this embodiment of the present application. The following steps 310 to 350 of the method 300 describe the specific process of SL configuration in detail, and for brevity, the detailed description is omitted here.

In step 220, the first terminal device generates second information based on the first information.

In order to distinguish from the first information described above, in the embodiment of the present application, resource request information generated by the first terminal device based on the first information is denoted as second information. The form of the second information may be the same as or different from the form of the first information. The embodiment of the present application does not limit this.

As an example, the first information may be a BSR, and may also be carried in one cell of the BSR, and this embodiment of the application only takes the first information as the first BSR as an example for description. The first terminal device generates a BSR to be sent to the network device based on the received BSR. For convenience of differentiation and description, in the embodiment of the present application, a BSR received by a first terminal device from a second terminal device is denoted as a first BSR, and a BSR to be sent to a network device, which is generated by the first terminal device based on the first BSR, is denoted as a second BSR. Such implementations are described in detail below with reference to specific embodiments, which are not explicitly described herein.

As another example, the first information may be a business model, or may be carried in the business model, and this embodiment of the application only takes the first information as the first business model as an example for description. The first terminal device generates a service model to be sent to the network device based on the received service model. For convenience of distinction and explanation, in the embodiment of the present application, a service model received by a first terminal device from a second terminal device is denoted as a first service model, and a service model to be sent to a network device, generated by the first terminal device based on the first service model, is denoted as a second service model. Such implementations are described in detail below with reference to specific embodiments, which are not explicitly described herein.

In this embodiment of the application, the second information generated by the first terminal device based on the first information may carry the identification information of the second terminal device.

For example, when the first terminal device and the second terminal device belong to the same terminal device group, the identification information of the second terminal device carried by the second information generated by the first terminal device based on the first information is used for identifying the second terminal device in the terminal device group.

The embodiment of the present application does not specifically limit the form of the identification information of the second terminal device. For example, the identification information of the second terminal device, which is carried by the second information generated by the first terminal device based on the first information, may include third information for identifying the second terminal device, where the first terminal device may be a relay device, and the second terminal device requests the network device for the SL resource through the first terminal device. For another example, the identification information of the second terminal device carried by the second information generated by the first terminal device based on the first information may include third information used for identifying the second terminal device and fourth information used for identifying the terminal device group, where the first terminal device and the second terminal device belong to the same terminal device group, and the second terminal device requests the network device for the SL resource through the first terminal device.

Wherein, the third information may include, for example, one or more of the following: the L2 identification of the second terminal device, the intra-group identification of the second terminal device, or an index. The fourth information may include, for example, one or more of: group identification or index of the group of terminal devices.

The group identifier or index of the second terminal device may be, for example, allocated by the first terminal device, or allocated by the network device, or may be obtained by arranging the information of the member terminal devices in the terminal device group reported to the network device by the first terminal device. The embodiment of the present application does not specifically limit the allocation manner of the identifier or index in the group of the second terminal device.

It should be understood that fig. 2 shows the case where a first terminal device interacts with one second terminal device for ease of understanding only. In fact, the number of second terminal devices is not limited to one. The first terminal device may communicate with one or more second terminal devices, receive first information from the one or more second terminal devices, and generate one or more second information based on the received one or more first information.

In one implementation, the first terminal device may generate one second information based on each first information to correspond to one second terminal device. In another implementation manner, the first terminal device may also generate a second message based on the plurality of first messages, and carry and send the identification information of each second terminal device in the plurality of first messages to the network device through the second message. The application does not limit the corresponding relationship between the number of the first information and the number of the second information. In other words, the present application does not limit the correspondence between the number of the second terminal devices and the number of the second information. For convenience of understanding and explanation, the method for acquiring the SL resource is described by taking one second terminal device as an example, and the number of the second terminal devices should not be limited at all.

It should be noted that, in the embodiment of the present application, a specific implementation manner of the first terminal device generating the second information based on the first information is not limited. For example, the first terminal device may generate a new piece of information, i.e., the second information, according to the received first information. For another example, the first terminal device may also modify or add a part of the cells according to the received first information to generate the second information. For example, after receiving a plurality of pieces of first information, the first terminal device may combine the identification information of a plurality of second terminal devices in the plurality of pieces of first information into one piece of second information, or after receiving the first information, the first terminal device adds an indication field of the identification information to the first information, so as to add the identification of the second terminal device to the first information, thereby obtaining the second information. For another example, the first terminal device may even directly forward the received first information to the network device, in which case the first information and the second information are the same information, and the generating step of step 220 may be omitted.

In step 230, the first terminal device sends the second information to the network device. Correspondingly, the network device receives the second information from the first terminal device.

The resource used by the first terminal device to send the second information to the network device may be, for example, a resource dynamically scheduled by the network device, or an authorized resource preconfigured by the network device, which is not limited in this application. As mentioned above, the second information may be BSR or traffic model. In this case, the first terminal device may transmit the second information through a resource for transmitting a BSR or a traffic model. For the way of acquiring the resource for the terminal device to send the BSR and the traffic model to the network device, reference may be made to the prior art, and for the sake of brevity, detailed description is not provided here.

After receiving the second information from the first terminal device, the network device may allocate SL resources to the second terminal device based on the second information.

For example, the network device may generate and transmit resource allocation information to the first terminal device, the resource allocation information including indication information indicating SL resources allocated to the second terminal device.

The SL resource indicated by the resource allocation information may be allocated to the second terminal device, or may be allocated to the first terminal device and the second terminal device. The resource allocation information may be one piece of information or multiple pieces of information, for example, the resource allocation information may include indication information of SL resources for indicating that the first terminal device sends Sidelink Control Information (SCI) to the second terminal device and SCI sent by the first terminal device to the second terminal device, or the resource allocation information only includes SCI sent by the first terminal device to the second terminal device.

For another example, the resource allocation information may further include indication information indicating SL resources including the SL resources allocated to the second terminal device.

In the embodiment of the application, the first terminal device generates second information based on first information from the second terminal device, and the second information carries identification information of the second terminal device. After the first terminal device sends the second information to the network device, the network device can identify, according to the identification information of the second terminal device, that the SL resource requested by the second information is used for the second terminal device to transmit the service data, so that the SL resource can be more accurately and reasonably allocated to the second terminal device. Under the condition that a plurality of terminal devices request the SL resources, different SL resources can be allocated to different terminal devices in different groups, and further, under the multicast scene, different SL resources can be allocated to different member terminal devices in the terminal device group, so that resource conflict is avoided, and the reliability of communication is improved. For a better understanding of the method provided by the present application, the method is further described below with reference to various embodiments and the accompanying drawings.

It should be understood that in the embodiments shown below, for convenience of understanding and explanation, the method for acquiring the SL resource is described in detail by taking a scenario of multicast communication as an example. The first terminal device and the second terminal device may be, for example, terminal devices belonging to the same terminal device group, the first terminal device being a head terminal device in the terminal device group, and the second terminal device being a member terminal device in the terminal device group. This should not be construed as limiting the application in any way. The method provided by the application is also applicable to other scenes of V2X, such as scenes of broadcast communication and unicast communication. That is, the first terminal device and the second terminal device do not necessarily belong to the same terminal device group.

Fig. 3 is a schematic flowchart of a method for acquiring SL resources according to another embodiment of the present application. The embodiment shown in fig. 3 describes in more detail an example where the first information referred to in step 210 is the first BSR.

As shown in fig. 3, the method 300 may include steps 310 through 390, each of which is described in detail below.

In step 310, the first terminal device and the second terminal device complete the establishment of the terminal device group.

AS described above, the establishment of the terminal device group may be triggered by APP or AS, which is not specifically limited in this embodiment of the application.

In the process of establishing the terminal device group, the head terminal device needs to be determined, and as described above, there may be multiple ways of determining the head terminal device, which is not specifically limited in this embodiment of the present application.

In the process of establishing the terminal equipment group or after the establishment of the terminal equipment group is completed, the head terminal equipment can acquire the information of the member terminal equipment in the terminal equipment group. For example, the information about the terminal devices as members of the terminal device group may include the number of terminal devices as members of the terminal device group, or the L2 identifier assigned by each terminal device in the terminal device group to the communication in the terminal device group.

The L2 identifier may be used as a source identifier of each terminal device in the terminal device group when transmitting service data in the group.

As an example, step 310 may be a new member terminal device joining an already existing group of terminal devices.

In step 320, the first terminal device sends information of the terminal device group to the network device.

The embodiment of the present application does not specifically limit the form of the information of the terminal device group. For example, if a multicast communication, the information for the group of end devices may include one or more of: the group identifier of the terminal device group, the frequency information of the terminal device group, the L2 identifier or the group identifier or index of each terminal device in the terminal device group, and the quality of service (QoS) requirement corresponding to the terminal device group. If the multicast communication scenario is not the multicast communication scenario, that is, the first terminal device communicates with each terminal device in the terminal device group in a unicast manner, the information of the terminal device group may include one or more of the following items: the L2 identifier or the intra-group identifier or the index of each terminal device in the terminal device group, and the QoS requirement corresponding to the unicast connection between each terminal device and the first terminal device may be L2 identifiers of each terminal device in this scenario, where the L2 identifiers are respectively allocated by each terminal device for the unicast connection between each terminal device and the first terminal device.

In step 330, the network device sends the SL configuration to the first terminal device, where the SL configuration is used to provide the SL configuration for each terminal device in the terminal device group.

The embodiment of the present application does not specifically limit the specific content of the SL configuration. For example, the SL configuration may include one or more of the following configurations: SL resource pool configuration, SL Radio Bearer (RB) configuration, logical channel group configuration, and measurement configuration.

The SL configuration provided by the network device for the terminal device group may include a dedicated configuration provided for each terminal device in the terminal device group, or may include a group configuration applicable to each terminal device in the terminal device group, which is not specifically limited in this embodiment of the present application.

Thus, the SL configuration provided by the network device for each terminal device in the terminal device group may include: a dedicated configuration provided for each terminal device in the group of terminal devices and/or a group configuration to which each terminal device in the group of terminal devices is adapted.

The embodiment of the present application is exemplified by an SL resource pool configuration.

After receiving the information of the terminal device group sent by the first terminal device, the network device provides SL resource pool configuration for each terminal device of the terminal device group. As described above, the network device may configure one SL resource pool for each terminal device in the terminal device group, or configure one SL resource pool for a plurality of terminal devices in the terminal device group, which is not specifically limited in this embodiment of the present application.

As an example, the SL resource pool may include a transmit resource pool for the terminal device to transmit data and/or a receive resource pool for the second terminal device to receive data.

In this embodiment, the synchronization source of the SL resource pool is not specifically limited, for example, the SL resource pool uses the first terminal device as the synchronization source. In this case, in order to achieve the purpose that the network device accurately schedules the SL resource for the second terminal device, the network device may receive the difference between the SFN and the DFN sent from the first terminal device.

Here, the difference between the SFN and the DFN may be a time difference, a timing difference or a time offset (timing offset) of the SFN and the DFN having the same frame number or subframe number on the same time axis, or a difference of time lengths of the SFN and the DFN having the same frame number or subframe number from the same time reference point (e.g., a certain absolute time point). The embodiment of the present application does not limit this.

Wherein the DFN is a DFN used by the first terminal device for broadcasting. Illustratively, the DFN information may be included in a sidelink master information block (SL-MIB) broadcast by the first terminal device.

The difference between the SFN and DFN may include one or more of: the difference between the SFN frame boundary and the DFN frame boundary, and the difference between the SFN subframe boundary and the DFN subframe boundary are not limited in this embodiment.

The difference between the SFN frame boundary and the DFN frame boundary can be understood as a time difference, a timing difference or a time offset between the SFN frame boundary and the DFN frame boundary on the same time axis, or a time length difference between the SFN frame boundary and the DFN frame boundary from the same time reference point (e.g. an absolute time point).

Similarly, the difference between the SFN subframe boundary and the DFN subframe boundary can be understood as a time difference, a timing difference or a time offset between the SFN subframe boundary and the DFN subframe boundary on the same time axis, or a time length difference between the SFN subframe boundary and the DFN subframe boundary from the same time reference point (e.g. an absolute time point).

For another example, the SL resource pool is a Global Navigation Satellite System (GNSS) synchronization source.

In step 340, after receiving the SL configuration sent by the network device, the first terminal device sends the SL configuration to the second terminal device.

The embodiment of the present application does not specifically limit the specific manner in which the first terminal device sends the SL configuration to the second terminal device.

As an example, the first end device may send the SL configuration to the second end device in a multicast manner, or may send the SL configuration through a unicast connection established with the second end device.

For example, the first end device sends the SL configuration to the second end device in a multicast manner. In this case, the SL configuration may include one or more of: the group configuration applicable to all the member terminal devices in the terminal device group, the L2 identifier of each terminal device in the terminal device group, the dedicated configuration configured for each terminal device, the group identifier or index of each terminal device in the terminal device group, and the dedicated configuration configured for each terminal device.

The first terminal device may send the SL configuration to the second terminal device through a Signaling Radio Bearer (SRB) of the terminal device group, or the first terminal device sends the SL configuration to the second terminal device through a user plane.

For another example, the first terminal device sends the SL configuration via a unicast connection established with the second terminal device, and the SL configuration may include a dedicated configuration of the second terminal device and/or a group configuration applicable to each terminal device in the terminal device group.

After receiving the SL configuration, the second terminal device sends information indicating success or failure of the SL configuration to the first terminal device, which will be described in detail later with reference to specific embodiments, and details of this implementation are not described here.

In step 350, the network device stores information of each terminal device within the terminal device group.

Steps 310 to 350 described above are one example of the network device providing the SL configuration for the first terminal device and the second terminal device. The network device may also provide the SL configuration for the first terminal device and the second terminal device before the second terminal device requests resource scheduling to the network device through the first terminal device.

It should be understood that, in this embodiment of the present application, the first terminal device and the second terminal device belong to the same terminal device group, the first terminal device is a head terminal device in the terminal device group, and the second terminal device is a member terminal device in the terminal device group. The SL configuration acquisition and SL resource acquisition of the member terminal equipment in the terminal equipment group aiming at the terminal equipment group are both acquired from the network equipment connected with the head terminal equipment through the head terminal equipment in the terminal equipment group. Even if the member terminal devices in the terminal device group are in a connected state, in a multicast communication scenario, the member terminal devices in the terminal device group do not need to report the information of the terminal device group to the network device connected with the member terminal devices.

When the member terminal devices in the terminal device group transmit the service data in the terminal device group, the member terminal devices may send first information to the head terminal device to request SL resource scheduling.

As shown in fig. 3, in steps 360 to 390, taking the first information as the first BSR as an example, the flow of requesting SL resources by the member terminal devices in the terminal device group is described in detail.

In step 360, the second terminal device sends a first BSR to the first terminal device.

The first BSR includes a Logical Channel Group (LCG) Identifier (ID) and a cache size corresponding to the LCG. Fig. 4 illustrates an example of the first BSR, as shown in fig. 4, the first BSR includes LCG ID1 and corresponding buffer size 1, LCG ID2 and corresponding buffer size 2 … …, LCG IDN and corresponding buffer size N, octets (Oct )1, Oct2 … … OctN in the figure respectively indicate that 8 bits (bits) form one byte (type), and N is a positive integer greater than or equal to 1.

When the second terminal device sends the first BSR to the first terminal device, the first terminal device needs to identify the second terminal device. The identification method in the embodiment of the present application is not specifically limited, and may be, for example:

the first method is as follows: the first terminal device may identify the second terminal device based on the source identity and/or the destination identity in the first BSR.

For example, in a multicast scenario, the second terminal device sends the first BSR to the first terminal device with the group identifier of the terminal device group as a destination identifier and the L2 identifier allocated to the member terminal device as a terminal device group as a source identifier. The first terminal equipment identifies which member terminal equipment in the terminal equipment group the second terminal equipment is through the source identification.

For another example, the second terminal device sends the first BSR to the first terminal device in a unicast manner, and in this case, the second terminal device sends the first BSR to the first terminal device with the L2 id allocated by the first terminal device for the unicast connection between the first terminal device and the second terminal device as the destination id and with the L2 id allocated by the second terminal device for the unicast connection as the source id. The first terminal equipment identifies which member terminal equipment the second terminal equipment is through the destination identification and/or the source identification.

The second method comprises the following steps: the first terminal device allocates a SL resource for sending the first BSR to the second terminal device in advance, and the first terminal device can identify the second terminal device through the SL resource.

For example, SL resources for transmission of BSRs may be pre-allocated, which may be resources in the psch or PSCCH, for example. Since the first terminal device allocates the SL resource to the second terminal device in advance, the first terminal device may identify the second terminal device that sends the first BSR when receiving the first BSR on the SL resource.

For another example, the first terminal allocates an SL resource for sending a first Scheduling Request (SR) to the second terminal in advance, and the first terminal device identifies the second device terminal through the SL resource, and then allocates an SL resource for sending the first BSR to the second terminal, and further identifies the second terminal device through the SL resource of the first BSR.

It should be understood that the above listed SL resources for transmission of BSR are only examples, and should not limit the present application in any way. The application does not limit the SL resource for transmitting the BSR.

The embodiment of the present application does not specifically limit the manner in which the second terminal device sends the first BSR to the first terminal device, and for example, the first BSR may be sent in a unicast manner or in a multicast manner.

In step 370, the first terminal device generates a second BSR based on the first BSR, and transmits the second BSR to the network device.

In this embodiment of the present application, the second BSR generated by the first terminal device based on the first BSR may include at least identification information of the second terminal device, an LCG ID included in the first BSR, and a cache size corresponding to the LCG. Fig. 5 illustrates an example of the second BSR, as shown in fig. 5, the second BSR includes an LCG ID1 and a corresponding buffer size 1, an LCG ID2 and a corresponding buffer size 2 … …, an LCG IDN and a corresponding buffer size N, octets (Oct )1 and Oct2 … … OctN in the figure respectively indicate that 8 bits (bits) form one byte (type), N is a positive integer greater than or equal to 1, and Destination (DST) indication information and UE indication information in the figure are identification information of the second terminal device.

The embodiment of the present application does not specifically limit the form of the identification information of the second terminal device. For example, the identification information of the second terminal device may include third information for identifying the second terminal device and fourth information for identifying the group of terminal devices.

Wherein the third information may include one or more of: the L2 identification of the second terminal device, the intra-group identification of the second terminal device, or an index. The fourth information may include one or more of: group identification or index of the group of terminal devices.

In an implementation manner, the first BSR may carry identification information of the second terminal device, and the second terminal device sends the first BSR to the first terminal device. In this case, the first terminal device does not need to perform additional processing on the received first BSR, and the first terminal device exists as a relay station and forwards the received first BSR to the network device.

In another implementation, the first terminal device may generate one second BSR based on each first BSR to correspond to one second terminal device. In this case, the first terminal device may add the identification information of the second terminal device to the first BSR to obtain the second BSR.

In another implementation, the first terminal device may also generate a second BSR based on the multiple first BSRs, and send the information carried by the multiple first BSRs to the network device through the second BSR. The corresponding relationship between the number of the first BSR and the number of the second BSR is not limited in the present application.

In step 380, the network device transmits resource allocation information to the first terminal device (# 1).

In step 390, the first terminal device transmits the corresponding resource allocation information to the second terminal device (# 2).

In one implementation, the resource allocation information (#1) transmitted by the network device to the first terminal device is Downlink Control Information (DCI).

As an example, a first terminal device receives DCI from a network device, the DCI including first indication information and a first SCI, the first indication information indicating a first SL resource for the first terminal device to transmit the first SCI.

Further, the first terminal device sends the first SCI to the second terminal device through the first SL resource, where the first SCI includes second indication information and a second SCI, the second indication information is used to indicate a second SL resource, the second SL resource is used for the second terminal device to transmit the second SCI, the second SCI is used to indicate a third SL resource, and the third SL resource is used for the second terminal device to transmit service data.

As another example, a first terminal device receives DCI from a network device, the DCI including a second SCI indicating a third SL resource for a second terminal device to transmit traffic data.

Further, after receiving the second SCI from the network device, the first terminal device requests the network device for the first SL resource for sending the first SCI and the second SL resource for transmitting the second SCI.

As another example, the first terminal device receives DCI from the network device indicating SL resources.

Further, the first terminal device generates a second SCI according to the SL resource indicated by the DCI.

Further, the first terminal device sends the second SCI to the second terminal device, the second SCI is used for indicating a third SL resource, the third SL resource is used for the second terminal device to transmit traffic data, and the third SL resource is included in the SL resource indicated by the DCI.

Several possible implementations of the network device indicating the SL resources for the first terminal device via the DCI are listed above. It should be understood that these implementations are merely examples, and should not be construed as limiting this application in any way.

Likewise, several possible implementations of the first terminal device indicating SL resources to the second terminal device via the SCI are listed above. It should be understood that these implementations are merely examples, and should not be construed as limiting this application in any way.

The DCI may further include third information for identifying the second terminal device and/or fourth information for identifying the terminal device group. For example, if there are a plurality of member terminal devices in the terminal device group, the DCI also includes third information. For another example, if the first terminal device is a head terminal device of a plurality of different terminal device groups, and each terminal device group has only one member terminal device, the DCI further includes the fourth information. For another example, if the first terminal device is a head terminal device of a plurality of different terminal device groups, and each terminal device group has a plurality of member terminal devices, the DCI further includes third information and fourth information.

In the embodiment of the present application, the second terminal device obtains the configuration of the SL resource pool from the network device through the first terminal device, and sets a uniform synchronization source when configuring the SL resource pool, thereby implementing synchronization between the network device and the second terminal device.

Based on the above technical solution, the second terminal device sends the first BSR to the first terminal device to obtain the SL resource, the first terminal device generates the second BSR based on the first BSR, and the second BSR carries the identification information of the second terminal device, after the first terminal device sends the second BSR to the network device, the network device can identify, according to the identification information of the second terminal device, that the SL resource requested by the second BSR is used for the second terminal device to transmit service data. Therefore, the network device can schedule the SL resources for the second terminal device from the SL resource pool configured for the second terminal device in advance, so that the network device can accurately schedule the SL resources for the second terminal device, and the reliability of the second terminal device for transmitting the service data is improved.

In addition, for a scenario in which the second terminal device is outside the coverage of the network device, the second terminal device may also obtain SL resource scheduling from the network device through the first terminal device, thereby implementing enhancement of the coverage of the network device.

Furthermore, when the first terminal device and the second terminal device belong to the same terminal device group, the unified management of the network device on the member terminal devices in the terminal device group is realized, and the reliability of multicast communication is improved.

Fig. 7 is a schematic flowchart of a method for acquiring SL resources according to another embodiment of the present application. The embodiment shown in FIG. 7 describes in more detail an example of the first business model as the first information mentioned in step 210.

As shown in fig. 7, the method 700 may include steps 710-750, each of which is described in detail below.

In step 710, the network device configures SL configurations for the first terminal device and the second terminal device.

In this embodiment, the method for configuring SL configurations for the first terminal device and the second terminal device by the network device in step 710 is the same as the method described in step 310 to step 350 in fig. 3, and is not described again here.

In step 720, the second terminal device sends the first traffic model to the first terminal device.

In step 730, the first terminal device generates a second service model based on the first service model, and sends the second service model to the network device.

The first service model and the second service model are used for reporting information such as the period and the data size of service data transmitted by the second terminal equipment in the terminal equipment group.

The second terminal device may send the first traffic model including different time offset parameters to the first terminal device, and the second traffic model generated by the first terminal device based on the different first traffic model may also include different time offset parameters. Wherein different time offset parameters are defined based on different predefined time reference points.

For ease of understanding, the time offset parameters and the predefined time reference points are described in detail below in conjunction with FIG. 6.

As shown in fig. 6, the predefined first time reference point may be a time boundary of the network device, for example, SFN #0 sf #0 in the figure. The predefined second time reference point may be a time boundary of the first terminal device, for example, DFN #0 sf #0 shown in the figure, or an absolute time point of the predefined GNSS. The first time offset parameter may be a time offset of the time of arrival of the traffic data of the second terminal device with respect to a predefined first time reference point. The second time offset parameter may be a time offset of DFN #0 sf #0 with respect to a predefined first time reference point, and the third time offset parameter may be a time offset of a time of arrival of traffic data of the second terminal device with respect to a predefined second time reference point. Examples of the first time offset parameter, the second time offset parameter and the third time offset parameter are given in fig. 6.

The first time reference point may further include an arbitrarily-numbered SFN or an arbitrarily-numbered subframe of the arbitrarily-numbered SFN. The second time reference point may also include an arbitrarily-numbered DFN, or an arbitrarily-numbered subframe of the arbitrarily-numbered DFN.

The second time offset parameter may be a difference between the DFN and the SFN. The description of the difference between the DFN and the SFN may refer to the description above in step 330 of method 300 and will not be repeated here for the sake of brevity.

In one implementation, the first traffic model sent by the second terminal device to the first terminal device may further include a first time offset parameter. When the second terminal device determines the first time offset parameter, the second time offset parameter may be acquired from the first terminal device in advance.

In this case, the first terminal device does not perform additional processing on the first time offset parameter in the received first service model, that is, the time offset parameter included in the second service model generated by the first terminal device based on the first service model is the first time offset parameter. The first terminal device then sends the second traffic model to the network device.

In another implementation, the first traffic model sent by the second terminal device to the first terminal device may further include a third time offset parameter.

If the third time offset parameter included in the first service model is a time offset of the arrival time of the service data of the second terminal device relative to an absolute time point of the GNSS. In this case, the first terminal device does not perform additional processing on the received third time offset parameter in the first service model, that is, the time offset parameter included in the second service model generated by the first terminal device based on the first service model is the third time offset parameter. The first terminal device then sends the second traffic model to the network device.

If the third time offset parameter included in the first service model is a time offset of the time of arrival of the service data to be transmitted by the second terminal device relative to the DFN #0 sf # 0. In this case, the first terminal device may process the received third time offset parameter in the first traffic model in at least two manners:

the first method is as follows: the first terminal device determines the first time offset parameter based on the third time offset parameter in the received first traffic model, i.e. the second traffic model generated by the first terminal device based on the received first traffic model includes the first time offset parameter. The first terminal device then sends the second traffic model to the network device.

The second method comprises the following steps: the first terminal device does not perform additional processing on the third time offset parameter in the received first service model, that is, the second service model generated by the first terminal device based on the received first service model includes the third time offset parameter. The first terminal device then sends the second traffic model to the network device. In this case, the first terminal device may transmit the second time offset parameter to the network device.

The first terminal device may send the second time offset parameter to the network device before forwarding the first service model to the network device, may also send the second time offset parameter to the network device after forwarding the first service model to the network device, and may also send the second time offset parameter to the network device while forwarding the first service model to the network device.

When the first terminal device receives the first service model, the second terminal device may be identified according to the source identifier and/or the destination identifier carried in the first service model.

For example, in a multicast scenario, the second terminal device sends the first service model to the first terminal device with the group identifier of the terminal device group as a destination identifier and the L2 identifier allocated to the member terminal device as the terminal device group as a source identifier. The first terminal equipment identifies which member terminal equipment in the terminal equipment group the second terminal equipment is through the source identification.

For another example, the second terminal device sends the first traffic model to the first terminal device in a unicast manner, and in this case, the second terminal device sends the first traffic model to the first terminal device with the L2 id allocated by the first terminal device for the unicast connection between the first terminal device and the second terminal device as the destination id and with the L2 id allocated by the second terminal device for the unicast connection as the source id. The first terminal equipment identifies which member terminal equipment the second terminal equipment is through the destination identification and/or the source identification.

The method for sending the first service model to the first terminal device by the second terminal device is not particularly limited in the embodiment of the present application, and for example, the first service model may be sent in a unicast manner, or may be sent in a multicast manner when the first terminal device and the second terminal device belong to the same terminal device group. Alternatively, the transmission may be carried by a control plane or a user plane.

In an implementation manner, the second service model generated by the first terminal device based on the received first service model may further include identification information of the second terminal device, and a form of the identification information of the second terminal device is not specifically limited in this embodiment of the application. For example, the identification information of the second terminal device may include third information for identifying the second terminal device and fourth information for identifying the group of terminal devices.

The group identifier or index of the second terminal device may be, for example, allocated by the first terminal device, or allocated by the network device, or may be obtained by arranging the information of the member terminal devices in the terminal device group reported to the network device by the first terminal device. In the embodiment of the present application, the allocation manner of the identifier or index in the group of the second terminal device is not specifically limited

In one implementation, the first terminal device may generate one second service model based on each first service model to correspond to one second terminal device.

In another implementation manner, the first terminal device may also generate a second service model based on the plurality of first service models, and carry and send information of the plurality of first service models, such as the first time offset parameter, to the network device through the second service model. The application does not limit the corresponding relationship between the number of the first business models and the number of the second business models.

In step 740, the network device sends the SL CG configuration to the first terminal device.

In step 750, the first terminal device sends the corresponding SL CG configuration to the second terminal device.

As described above, the first terminal device may or may not perform additional processing on the received time offset parameter in the first traffic model. Thus, the second traffic model transmitted by the first terminal device to the network device may comprise different time offset parameters. Thus, the SL CG configuration sent by the network device to the first terminal device based on the second traffic model is time-referenced to a different predefined point of time reference.

In one implementation, the second traffic model includes a first time offset parameter, and the network device uses a predefined first time reference point as a time reference according to the SL CG configuration determined by the second traffic model.

Further, after receiving the SL CG configuration, the first terminal device converts the SL CG configuration into an SL CG configuration with a predefined second time reference point as a time reference according to the second time offset parameter. The first terminal device then sends the SL CG configuration, time-referenced to a predefined second point of time reference, to the second terminal device. And after receiving the configuration of the SL CG, the second terminal equipment transmits service data by using the SL CG resource.

Or the first terminal equipment does not perform additional processing on the received SL CG configuration and directly sends the SL CG configuration to the second terminal equipment. In this case, the second terminal device determines the SL CG resource in combination with the SL CG configuration and the second time offset parameter. And the second time offset parameter is informed to the second terminal equipment by the first terminal equipment.

In another implementation, the second service model includes a third time offset parameter, and the network device uses a predefined second time reference point as a time reference according to the SL CG configuration determined by the second service model and the previously received second time offset parameter. In this case, the first terminal device sends the received SL CG configuration directly to the second terminal device without additional processing.

It should be understood that step 750 shown in fig. 7 only shows an example that the first terminal device directly transmits the received SL CG configuration from the network device to the second terminal device without additional processing, and should not constitute any limitation to the embodiment of the present application.

In an implementation manner, the SL CG configuration sent by the network device to the first terminal device may further carry third information for identifying the second terminal device and/or fourth information for identifying the terminal device group, for example, if there are multiple member terminal devices in the terminal device group, the SL CG configuration may further carry the third information, and for example, if the first terminal device is a head terminal device of multiple different terminal device groups and each terminal device group has only one member terminal device, the SL CG configuration may further carry the fourth information, and for example, if the first terminal device is a head terminal device of multiple different terminal device groups and each terminal device group has multiple CG member terminal devices, the SL configuration may further carry the third information and the fourth information.

In this embodiment of the present application, the second terminal device carries the time offset parameter (such as the first time offset parameter or the third time offset parameter described above) in the service model reported to the network device, so that the network device can allocate a corresponding SL CG resource to the second terminal device according to the reported time offset parameter, thereby synchronizing or aligning the network device and the second terminal device in the time domain. Even if the second terminal device is out of the coverage of the network device, the resource offset still does not occur, which is beneficial to improving the reliability of the second terminal device for transmitting the service data.

Meanwhile, the first terminal equipment determines the first time offset parameter according to the second time offset parameter, the service model of the second terminal equipment reported by the existing Uu port can be reused, and the complexity of network equipment can be saved.

Fig. 8 is a schematic flowchart of a method for configuring SL configuration according to an embodiment of the present application, and the embodiment shown in fig. 8 describes in more detail an implementation manner in which after receiving the SL configuration, the second terminal device mentioned in step 340 in fig. 3 sends an indication that the configuration is successful or failed to the first terminal device.

In step 810, the network device sends an RRC message to the first terminal device.

The RRC message includes SL configuration information configured by the network device for each terminal device in the terminal device group, and the embodiment of the present application does not limit specific contents of the SL configuration. For example, the SL configuration may include one or more of: SL resource pool configuration, SL bearer configuration, logical channel group configuration and measurement configuration.

The SL configuration provided by the network device for the terminal device group may include a dedicated configuration provided for each terminal device in the terminal device group, a group configuration applicable to each terminal device in the terminal device group, or a combination of the dedicated configuration and the group configuration. The embodiment of the present application does not limit this.

In step 820, the first terminal device parses the received RRC message.

In step 830, the first terminal device sends the parsed SL configuration provided by the network device for the second terminal device to the second terminal device.

As described above, the first terminal device may send the SL configuration to the second terminal device in a unicast manner, in this case, the first terminal device needs to filter the SL configuration received from the network device, and send the SL configuration applicable to the second terminal device only to the second terminal device, where the SL configuration may include a dedicated configuration of the second terminal device and a group configuration applicable to each terminal device in the terminal device group.

The embodiment of the present application does not limit the specific manner in which the first terminal device filters the received SL configuration. For example, the dedicated configuration received by the first terminal device from the network device may carry the L2 identifier of the second terminal device, or may also carry the intra-group identifier or index of the second terminal device. The first terminal device may determine to which member terminal device of the group of terminal devices the dedicated configuration applies based on the L2 identity or the intra-group identity or index.

As described above, the first end device may send the SL configuration to the second end device in a multicast manner. In this case, the message sent by the first terminal device to the second terminal device includes the SL configuration configured by the network device for all the member terminal devices in the terminal device group. After receiving the message sent by the first terminal device, the second terminal device may only execute the SL configuration applicable to the second terminal device, where the SL configuration may include a dedicated configuration of the second terminal device and/or a group configuration applicable to each terminal device in the terminal device group. SL configurations received by the second terminal device and not applicable to the second terminal device may or may not be reserved, which is not limited in this embodiment of the present application.

In step 840, the second terminal device sends an SL configuration success or failure indication to the first terminal device.

In one implementation, after receiving the SL configuration sent by the first terminal device, the second terminal device may send an SL configuration success indication to the first terminal device if the SL configuration can be completed. The SL configuration completion indication may be carried in an existing signaling or may be an additional signaling. This is not a limitation of the present application.

Taking the measurement configuration as an example, if the second terminal device can complete the measurement configuration, the second terminal device sends a measurement configuration success indication to the first terminal device.

Further, the manner in which the second end device sends the SL configuration success indication to the first end device may be sending in a multicast manner or sending in a unicast manner. For example, if the second end device sends the SL configuration success indication in a multicast manner, the other member end devices in the end device group may receive the SL configuration completion indication in addition to the first end device, and the other member end devices do not need to perform additional processing on the received SL configuration success indication. For another example, the second terminal device sends the SL configuration success indication to the first terminal device in a unicast manner.

In another implementation manner, after receiving the SL configuration sent by the first terminal device, if the SL configuration cannot be executed, the second terminal device sends an SL configuration failure indication to the first terminal device. The SL configuration failure indication may be carried in an existing signaling or may be an additional signaling. This is not a limitation of the present application.

Taking the measurement configuration as an example, if the second terminal device cannot execute the measurement configuration, the second terminal device sends a measurement configuration failure indication to the first terminal device.

In step 850, the first terminal device sends a SL configuration success indication or a SL configuration failure indication to the network device.

In response to the SL configuration information in the RRC message in step 810, the first network device may send a SL configuration success indication or a SL configuration failure indication. In one implementation, after the first terminal device receives the SL configuration success indication sent by all the member terminal devices in the terminal device group, the first terminal device may send information to the network device, indicating that the SL configuration of the terminal device group is successful. In one possible design, the SL configuration success indication may be an RRC reconfiguration complete message or an information element carried in the RRC reconfiguration complete message. This is not a limitation of the present application.

In another implementation manner, in a case where the first terminal device confirms that the SL configuration of the second terminal device fails, third indication information indicating that the SL configuration of the terminal device group fails is sent to the network device. In this case, the first terminal device recognizes that the SL configuration of the network device has failed. The method may further comprise: the first terminal device triggers RRC re-establishment.

The embodiment of the present application does not limit the manner in which the first terminal device confirms that the configuration of the second terminal device SL fails, for example, when the first terminal device receives an SL configuration failure instruction from the second terminal device, it confirms that the configuration of the second terminal device SL fails. Or, the first terminal device confirms that the SL configuration of the second terminal device fails when the preset timer is overtime and the SL configuration success indication of the second terminal device is not received.

In another implementation manner, if the first terminal device is capable of performing the SL configuration provided for the first terminal device in the RRC message sent by the network device to the first terminal device in step 810, an RRC reconfiguration complete message is sent to the network device to indicate that the configuration of the first terminal device is successful. And subsequently, if the configuration failure of the second terminal equipment SL is confirmed, third indication information for indicating the configuration failure of the second terminal equipment SL is sent to the network equipment.

Further, the third indication information indicating that the configuration of the second terminal device SL fails may also be sent to the network device by the first terminal device, where the third indication information may also carry the identifier information of the second terminal device described above.

For example, if the member terminal devices in the terminal device group can complete the measurement configuration, the member terminal devices will perform measurement to obtain the measurement result. Taking Channel Busy Rate (CBR) measurement as an example, when a measurement event is satisfied or a measurement period is reached, the member terminal device sends a CBR measurement result to the head terminal device. The method for the member terminal device to send the CBR measurement result is the same as the method for the member terminal device to send information to the head terminal device, which is not described herein again.

Further, after receiving the CBR measurement result of the member terminal device, the head terminal device sends the CBR measurement result to the network device. The CBR measurement result sent by the head terminal device to the network device may also carry the aforementioned identification information of the second terminal device.

As the positions of the terminal devices in the terminal device group may be different and the SL communication environments may also be different, the CBR measurement results that can be obtained by different terminal devices in the terminal device group may also be different, as shown in fig. 9, the positions of two member terminal devices in the terminal device group #1 are different from the positions of two member terminal devices in the terminal device group #2, and therefore the CBR measurement results reported to the network device by the member terminal devices in the terminal device group are different. As shown in fig. 9, the CBR measurement result obtained by the terminal device group #1 corresponding to the Resource Pool (RP) #1 in the figure is CBR 0.1, the CBR measurement result obtained by the terminal device group #1 corresponding to the RP #2 is CBR 0.9, the CBR measurement result obtained by the terminal device group #2 corresponding to the RP #1 in the figure is CBR 0.9, and the CBR measurement result obtained by the terminal device group #1 corresponding to the RP #2 is CBR 0.1. In this case, the network device receives the CBR measurement result of the member terminal device sent to the head terminal device, and may optimize the SL resource pool configuration generated for each terminal device in the terminal device group according to the CBR measurement result.

In this embodiment of the present application, the second terminal device may send SL configuration failure indication information to the first terminal device, and further, the first terminal device may also send third indication information indicating that the SL configuration of the second terminal device fails to the network device, or send third indication information indicating that the SL configuration of the terminal device group fails. And if the first terminal device sends third indication information indicating that the configuration of the terminal device group SL fails to the network device, the first terminal device triggers RRC reestablishment. Further, the third indication information indicating that the configuration of the second terminal device SL fails, which is sent to the network device by the first terminal device, may also carry identification information of the second terminal device. Therefore, the network device can optimize the SL configuration generated for each terminal device in the terminal device group according to the received SL configuration failure indication information.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 9. Hereinafter, the apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 10 to 12.

Fig. 10 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown in fig. 10, the communication device 1000 may include a processing unit 1100 and a transceiving unit 1200.

In one possible design, the communication apparatus 1000 may correspond to the first terminal device in the above method embodiment, and may be the first terminal device, or a component (such as a chip or a chip system) configured in the first terminal device, for example.

It should be understood that the communication apparatus 1000 may correspond to the first terminal device in the methods 200, 300, 700, 800 according to the embodiments of the present application, and the communication apparatus 1000 may include means for performing the methods performed by the first terminal device in the methods 200 in fig. 2, 300 in fig. 3, 700 in fig. 7, 800 in fig. 8. Also, the units in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2, the method 300 in fig. 3, the method 700 in fig. 7, and the method 800 in fig. 8.

When the communication device 1000 is used to execute the method 200 in fig. 2, the processing unit 1100 may be used to execute step 220 in the method 200, and the transceiver unit 1200 may be used to execute step 210 and step 230 in the method 200. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is used to execute the method 300 in fig. 3, the processing unit 1100 may be configured to execute the steps 310, 340, 370, and 390 in the method 300, and the transceiver unit 1200 may be configured to execute the steps 320 to 340, and the steps 360 to 390 in the method 300. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 700 in fig. 7, the processing unit 1100 may be configured to perform the steps 730 and 750 in the method 700, and the transceiver unit 1200 may be configured to perform the steps 720, 740, and 750 in the method 700. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 800 in fig. 8, the processing unit 1100 may be configured to perform the steps 820 and 850 in the method 800, and the transceiver unit 1200 may be configured to perform the steps 810, 830, 840 and 850 in the method 800. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

It should also be understood that when the communication apparatus 1000 is a first terminal device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by a transceiver, for example, may correspond to the transceiver 2020 in the terminal device 2000 shown in fig. 11, and the processing unit 1100 in the communication apparatus 1000 may be implemented by at least one processor, for example, may correspond to the processor 2010 in the first terminal device 2000 shown in fig. 11.

It should also be understood that, when the communication apparatus 1000 is a chip or a chip system configured in the first terminal device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by an input/output interface, and the processing unit 1100 in the communication apparatus 1000 may be implemented by a processor, a microprocessor, an integrated circuit, or the like integrated on the chip or the chip system.

In another possible design, the communication apparatus 1000 may correspond to the network device in the above method embodiment, and may be, for example, a network device or a component (e.g., a chip or a system-on-chip) configured in a network device.

It should be understood that the communication apparatus 1000 may correspond to the network device in the method 200, the method 300, the method 700, and the method 800 according to the embodiments of the present application, and the communication apparatus 1000 may include a unit for performing the method performed by the network device in the method 200 in fig. 2, the method 300 in fig. 3, the method 700 in fig. 7, and the method 800 in fig. 8. Also, the units in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2, the method 300 in fig. 3, the method 700 in fig. 7, and the method 800 in fig. 8.

When the communication device 1000 is used to execute the method 200 in fig. 2, the processing unit 1100 may be used to execute step 230 in the method 200, and the transceiver unit 1200 may be used to execute step 230 in the method 200. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 300 in fig. 3, the processing unit 1100 may be configured to perform the steps 330, 350, and 380 in the method 300, and the transceiver unit 1200 may be configured to perform the steps 320, 330, 370, and 380 in the method 300. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 700 in fig. 7, the processing unit 1100 may be configured to perform the steps 710 and 740 in the method 700, and the transceiver unit 1200 may be configured to perform the steps 730 and 740 in the method 700. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 800 in fig. 8, the processing unit 1100 may be configured to perform step 810 in the method 800, and the transceiver unit 1200 may be configured to perform step 810 and step 850 in the method 800. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

It should also be understood that when the communication apparatus 1000 is a network device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by a transceiver, for example, may correspond to the transceiver 3200 in the network device 3000 shown in fig. 12, and the processing unit 1100 in the communication apparatus 1000 may be implemented by at least one processor, for example, may correspond to the processor 3100 in the network device 3000 shown in fig. 12.

It should also be understood that, when the communication device 1000 is a chip or a system of chips configured in a network device, the transceiver unit 1200 in the communication device 1000 may be implemented by an input/output interface, and the processing unit 1100 in the communication device 1000 may be implemented by a processor, a microprocessor, an integrated circuit, or the like integrated on the chip or the system of chips.

In one possible design, the communication apparatus 1000 may correspond to the second terminal device in the above method embodiment, and may be, for example, the second terminal device or a component (such as a chip or a chip system) configured in the second terminal device.

It should be understood that the communication apparatus 1000 may correspond to the second terminal device in the methods 200, 300, 700, 800 according to the embodiments of the present application, and the communication apparatus 1000 may include means for performing the methods performed by the second terminal device in the methods 200 in fig. 2, 300 in fig. 3, 700 in fig. 7, 800 in fig. 8. Also, the units in the communication device 1000 and the other operations and/or functions described above are respectively for implementing the corresponding flows of the method 200 in fig. 2, the method 300 in fig. 3, the method 700 in fig. 7, and the method 800 in fig. 8.

When the communication device 1000 is used to execute the method 200 in fig. 2, the processing unit 1100 may be used to execute step 210 in the method 200, and the transceiver unit 1200 may be used to execute step 210 in the method 200. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 300 in fig. 3, the processing unit 1100 may be configured to perform step 310 in the method 300, and the transceiver unit 1200 may be configured to perform step 340, step 360, and step 390 in the method 300. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 700 in fig. 7, the processing unit 1100 may be configured to perform the steps 720 and 750 in the method 700, and the transceiver unit 1200 may be configured to perform the steps 720 and 750 in the method 700. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

When the communication device 1000 is configured to perform the method 800 in fig. 8, the processing unit 1100 is configured to perform step 840 in the method 800, and the transceiver unit 1200 is configured to perform step 830 and step 840 in the method 800. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

It should also be understood that when the communication apparatus 1000 is a second terminal device, the transceiver unit 1200 in the communication apparatus 1000 may be implemented by a transceiver, for example, may correspond to the transceiver 2020 in the second terminal device 2000 shown in fig. 11, and the processing unit 1100 in the communication apparatus 1000 may be implemented by at least one processor, for example, may correspond to the processor 2010 in the second terminal device 2000 shown in fig. 11.

It should also be understood that, when the communication device 1000 is a chip or a chip system configured in a terminal device, the transceiver unit 1200 in the communication device 1000 may be implemented by an input/output interface, and the processing unit 1100 in the communication device 1000 may be implemented by a processor, a microprocessor, an integrated circuit, or the like integrated on the chip or the chip system.

Fig. 11 is a schematic structural diagram of a terminal device 2000 according to an embodiment of the present application. The terminal device 2000 can be applied to the system shown in fig. 1, and performs the functions of the first terminal device or the second terminal device in the above method embodiment. As shown, the terminal device 2000 includes a processor 2010 and a transceiver 2020. Optionally, the terminal device 2000 further comprises a memory 2030. The processor 2010, the transceiver 2002 and the memory 2030 may be in communication with each other via the interconnection path to transfer control and/or data signals, the memory 2030 may be used for storing a computer program, and the processor 2010 may be used for retrieving and executing the computer program from the memory 2030 to control the transceiver 2020 to transmit and receive signals. Optionally, the terminal device 2000 may further include an antenna 2040, configured to transmit uplink data or uplink control signaling output by the transceiver 2020 by using a wireless signal.

The processor 2010 and the memory 2030 may be combined into a processing device, and the processor 2010 is configured to execute the program codes stored in the memory 2030 to achieve the above functions. In particular, the memory 2030 may be integrated with the processor 2010 or may be separate from the processor 2010. The processor 2010 may correspond to the processing unit 1100 of fig. 7.

The transceiver 2020 may correspond to the transceiver 1200 in fig. 10, and may also be referred to as a transceiver. The transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Wherein the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the terminal device 2000 shown in fig. 11 is capable of implementing the various processes involving the first terminal device in the method embodiments shown in fig. 2, 3, 7 and 8. The operations and/or functions of the modules in the terminal device 2000 are respectively to implement the corresponding flows in the above-described method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

The processor 2010 may be configured to perform the actions implemented inside the first terminal device, such as generating the second information, and the like, described in the foregoing method embodiments. The transceiver 2020 may be configured to perform the actions of the first terminal device transmitting to or receiving from the network device, such as transmitting the second information and the third indication information, receiving the resource allocation information, and the like, described in the foregoing method embodiments. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

It should also be understood that terminal device 2000 shown in fig. 11 is capable of implementing various processes involving the second terminal device in the method embodiments shown in fig. 2, 3, 7, and 8. The operations and/or functions of the modules in the terminal device 2000 are respectively to implement the corresponding flows in the above-described method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

The processor 2010 may be configured to perform the actions internally implemented by the second terminal device, such as generating the first information, and the like, described in the foregoing method embodiments. The transceiver 2020 may be configured to perform the actions of the first terminal device transmitting to or receiving from the network device, such as transmitting the first information, the SL configuration failure indication and the SL configuration success indication, receiving the resource allocation information, and the like, described in the foregoing method embodiments. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The terminal device 2000 may further include a power supply 2050, which is used for supplying power to various devices or circuits in the terminal device.

In addition, in order to further improve the functions of the terminal device, the terminal device 2000 may further include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, a sensor 2100, and the like, and the audio circuit may further include a speaker 2082, a microphone 2084, and the like.

Fig. 12 is a schematic structural diagram of a network device provided in the embodiment of the present application, which may be a schematic structural diagram of a base station, for example. The base station 3000 can be applied to the system shown in fig. 1, and performs the functions of the network device in the above method embodiment. As shown, the base station 3000 may include one or more radio frequency units, such as a Remote Radio Unit (RRU) 3100 and one or more baseband units (BBUs) (which may also be referred to as Distributed Units (DUs)) 3200. The RRU 3100 may be referred to as a transceiver unit or a part of a transceiver unit, and corresponds to the transceiver unit 1100 in fig. 10. Alternatively, the transceiving unit 3100 may also be referred to as a transceiver, transceiving circuit, or transceiver, etc., which may comprise at least one antenna 3101 and a radio frequency unit 3102. Alternatively, the transceiving unit 3100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit). The RRU 3100 part is mainly used for transceiving and converting radio frequency signals and baseband signals, for example, for sending SL configuration information and resource allocation information to a first terminal device, and receiving second information. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The BBU 3200 section is mainly used for performing baseband processing, controlling a base station, and the like. The RRU 3100 and the BBU 3200 may be physically disposed together or may be physically disposed separately, i.e. distributed base stations.

The BBU 3200, which is a control center of the base station and may also be referred to as a processing unit, may correspond to the processing unit 1200 in fig. 10, and may be used to complete baseband processing functions, such as channel coding, multiplexing, modulating, spreading, and the like. For example, the BBU (processing unit) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiment, for example, to generate the foregoing resource allocation information. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

In an example, the BBU 3200 may be formed by one or more boards, and the boards may collectively support a radio access network of a single access system (e.g., an LTE network), or may respectively support radio access networks of different access systems (e.g., an LTE network, a 5G network, or other networks). The BBU 3200 also includes a memory 3201 and a processor 3202. The memory 3201 is used to store necessary instructions and data. The processor 3202 is used for controlling the base station to perform necessary actions, for example, for controlling the base station to execute the operation flow related to the network device in the above method embodiment. The memory 3201 and processor 3202 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be understood that the base station 3000 shown in fig. 12 can implement the processes involving the network device in the method embodiments shown in fig. 2, 3, 7, and 8. The operations and/or functions of the respective modules in the base station 3000 are respectively for implementing the corresponding flows in the above-described method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

BBU 3200 as described above may be used to perform actions described in previous method embodiments as being implemented internally by a network device, while RRU 3100 may be used to perform actions described in previous method embodiments as being sent by or received from a network device to a first terminal device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

It should be understood that the base station 3000 shown in fig. 12 is only one possible form of network device, and should not limit the present application in any way. The method provided by the application can be applied to network equipment in other forms. For example, including AAUs, and may also include CUs and/or DUs, or including BBUs and Adaptive Radio Units (ARUs), or BBUs; the network device may also be a Customer Premise Equipment (CPE) or other forms, and the present application is not limited to a specific form of the network device.

Wherein the CU and/or DU may be adapted to perform the actions described in the previous method embodiments as implemented internally by the network device, and the AAU may be adapted to perform the actions described in the previous method embodiments as sent to or received from the first terminal device by the network device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is configured to perform the method of any of the above method embodiments.

It is to be understood that the processing means described above may be one or more chips. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the methods performed by the first terminal device, the second terminal device and the network device, respectively, in the embodiments shown in fig. 2, 3, 7 and 8.

According to the method provided by the embodiment of the present application, a computer-readable medium is further provided, and the computer-readable medium stores a program code, and when the program code runs on a computer, the computer is caused to execute the methods respectively executed by the first terminal device, the second terminal device and the network device in the embodiments shown in fig. 2, fig. 3, fig. 7 and fig. 8.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more first terminal devices, one or more second terminal devices, and one or more network devices.

The network device in the foregoing device embodiments completely corresponds to the terminal device and the network device or the terminal device in the method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the communication unit (transceiver) executes the steps of receiving or transmitting in the method embodiments, and other steps besides transmitting and receiving may be executed by the processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

In the above embodiments, the functions of the functional units may be fully or partially implemented by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). The procedures or functions described in accordance with the embodiments of the present application are generated in whole or in part when the computer program instructions (programs) are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for acquiring a sidelink SL resource is characterized by comprising the following steps:

a first terminal device receives first information from a second terminal device, wherein the first information is used for requesting SL resources;

the first terminal equipment generates second information based on the first information, wherein the second information carries identification information of the second terminal equipment and is used for requesting the SL resources for the second terminal equipment;

and the first terminal equipment sends the second information to network equipment.
The method according to claim 1, wherein the identification information of the second terminal device includes third information for identifying the second terminal device, or third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.
The method of claim 2, wherein the third information comprises one or more of: a layer 2 identifier of the second terminal device, an intra-group identifier or an index of the second terminal device.
A method according to claim 2 or 3, wherein the fourth information comprises a group identity or an index of the group of terminal devices.
The method of any one of claims 1-4, wherein the first information comprises a first Buffer Status Report (BSR), and the second information comprises a second BSR generated based on the first BSR.
The method of claim 5, wherein the method further comprises:

the first terminal equipment receives Downlink Control Information (DCI) from the network equipment, wherein the DCI comprises first indication information and first Sidelink Control Information (SCI), the first indication information is used for indicating a first SL resource, and the first SL resource is used for transmitting the first SCI;

the first terminal device sends the first SCI to the second terminal device through the first SL resource, the first SCI includes second indication information and a second SCI, the second indication information is used for indicating a second SL resource, the second SL resource is used for transmitting the second SCI, the second SCI is used for indicating a third SL resource, and the third SL resource is used for transmitting service data by the second terminal device.
The method of claim 5, wherein the method further comprises:

the first terminal equipment receives DCI from the network equipment, wherein the DCI is used for indicating SL resources;

the first terminal equipment generates a second SCI according to the SL resource indicated by the DCI;

and the first terminal equipment sends a second SCI to the second terminal equipment, wherein the second SCI is used for indicating a third SL resource, the third SL resource is used for the second terminal equipment to transmit service data, and the third SL resource is contained in the SL resource indicated by the DCI.
The method of claim 6 or 7, wherein the DCI further comprises third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs.
The method of any of claims 1-4, wherein the first information comprises a first business model and the second information comprises a second business model generated based on the first business model.
The method of claim 9, wherein the first traffic model further comprises a first time offset parameter, the first time offset parameter being a time offset of a time of arrival of traffic data of the second terminal device relative to the predefined first time reference point.
The method of claim 10, wherein prior to the first terminal device receiving the first information from the second terminal device, the method further comprises:

the first terminal device sends a second time offset parameter to the second terminal device, where the second time offset parameter is a time offset of a subframe #0 of a direct connection frame number DFN #0 with respect to a predefined first time reference point.
The method of claim 9, wherein the first traffic model further comprises a third time offset parameter, the third time offset parameter being a time offset of a time of arrival of traffic data of the second terminal device relative to a predefined second time reference point; the second traffic model further comprises a first time offset parameter being a time offset of the arrival time of traffic data of the second terminal device with respect to a predefined first time reference point,

the method further comprises the following steps:

and the first terminal equipment determines the first time offset parameter according to the third time offset parameter.
The method of claim 9, wherein the first traffic model further comprises a third time offset parameter, the third time offset parameter being a time offset of a time of arrival of traffic data of the second terminal device relative to a predefined second time reference point,

the method further comprises the following steps:

the first terminal device sends the second time offset parameter to the network device, where the second time offset parameter is a time offset of subframe #0 of the DFN #0 with respect to a predefined first time reference point.
The method of any of claims 10-13, wherein the first time reference point comprises subframe #0 of a system frame number SFN # 0.
The method of claim 12 or 13, wherein the second time reference point comprises subframe #0 of the DFN #0 or a global navigation satellite system GNSS-absolute time point.
The method of any one of claims 9-15, further comprising:

the first terminal equipment receives configuration of a side link configuration authorization (SL CG) from the network equipment, wherein the SL CG also carries third information used for identifying the second terminal equipment and/or fourth information used for identifying a terminal equipment group to which the second terminal equipment belongs;

the first terminal device forwards the SL CG configuration to the second terminal device.
A method for acquiring a sidelink SL resource is characterized by comprising the following steps:

the network equipment receives second information from first terminal equipment, wherein the second information carries identification information of second terminal equipment, the second information is used for requesting SL resources for the second terminal equipment, and the second information is generated by the first terminal equipment based on first information from the second terminal equipment;

and the network equipment sends resource allocation information to the first terminal equipment according to the second information.
The method according to claim 17, wherein the identification information includes third information for identifying the second terminal device, or third information for identifying the second terminal device and fourth information for identifying a terminal device group to which the second terminal device belongs.
The method of claim 18, wherein the third information comprises one or more of: a layer 2 identifier of the second terminal device, an intra-group identifier or an index of the second terminal device.
The method according to claim 18 or 19, characterized in that the fourth information comprises a group identification or an index of the group of terminal devices.
The method of any one of claims 17-20, wherein the first information comprises a first Buffer Status Report (BSR), and the second information comprises a second BSR generated based on the first BSR.
The method of claim 21, wherein the resource allocation information is downlink control information DCI, the DCI includes first indication information and first sidelink control information SCI, the first indication information is used for indicating a first SL resource, the first SL resource is used for transmitting the first SCI, the first SCI includes second indication information and a second SCI, the second indication information is used for indicating a second SL resource, the second SL resource is used for transmitting the second SCI, the second SCI is used for indicating a third SL resource, and the third SL resource is used for transmitting traffic data by the second terminal device.
The method of claim 21, wherein the resource allocation information is DCI, the DCI is configured to indicate SL resources, the SL resources include a third SL resource, and the third SL resource is used for the second terminal device to transmit traffic data.
The method of claim 22 or 23, wherein the DCI further comprises third information for identifying the second terminal device and/or fourth information for identifying a terminal device group to which the second terminal device belongs.
The method of any of claims 17-20, wherein the first information comprises a first business model and the second information comprises a second business model generated based on the first business model.
The method of claim 25, wherein the first traffic model further comprises a first time offset parameter, the first time offset parameter being a time offset of a time of arrival of traffic data of the second terminal device relative to a predefined first time reference point.
The method of claim 25, wherein the first traffic model further comprises a third time offset parameter, the third time offset parameter being a time offset of the time of arrival of traffic data of the second terminal device relative to a predefined second time reference point; the second traffic model further comprises a first time offset parameter, the first time offset parameter being a time offset of the time of arrival of traffic data of the second terminal device with respect to a predefined first time reference point, the third time offset parameter being determined in accordance with the first time offset parameter.
The method of claim 25, wherein the first traffic model further comprises a third time offset parameter, the third time offset parameter being a time offset of a time of arrival of traffic data of the second terminal device relative to a predefined second time reference point,

the method further comprises the following steps:

the network device receives a second time offset parameter from the first terminal device, where the second time offset parameter is a time offset of subframe #0 of a direct connection frame number DFN #0 with respect to a predefined first time reference point.
The method of any of claims 24-28, wherein the first time reference point comprises subframe #0 of a system frame number SFN # 0.
The method of claim 27 or 28, wherein the second time reference point comprises subframe #0 of the DFN #0 or a global navigation satellite system GNSS-absolute time point.
The method according to any of claims 25-30, wherein the resource allocation information is a sidelink configuration grant, SL CG, configuration, the SL CG further carrying third information identifying the second terminal device and/or fourth information identifying a group of terminal devices to which the second terminal device belongs.
A communication apparatus, characterized in that it comprises means for implementing the method according to any of claims 1-16.
A communication apparatus, characterized in that it comprises means for implementing the method according to any of claims 17-31.
A communications apparatus, comprising:

a processor to execute computer instructions stored in the memory to cause the apparatus to perform: the method of any one of claims 1-16.
A communications apparatus, comprising:

a processor to execute computer instructions stored in the memory to cause the apparatus to perform: the method of any one of claims 17-31.
A communication system, comprising: communication apparatus according to claims 32 and 33, or according to claims 34 and 35.
A computer-readable storage medium, having stored thereon a computer program which, when executed, causes the method of any of claims 1-31 to be performed.