RU2783980C2 - Communication method and related device - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: terminal device receives the first data and a quality of service (hereinafter – QoS) parameter corresponding to the first data, wherein QoS parameter contains at least one of information about reliability, about waiting time, about communication range, about data transmission speed, and about service type. The terminal device sends an identifier corresponding to QoS parameter to a network device. Sending of the identifier to the network device contains sending of a buffer state report (hereinafter – BSR) containing the identifier. BSR additionally contains the total data volume of all data, which is in the terminal device, and which corresponds to the identifier, or BSR additionally contains information about a destination address, corresponding to the first data and/or data volume of all data, which is in the terminal device, and which corresponds to both destination address information and the identifier.

EFFECT: provision by a network device of resource planning for a terminal device, satisfying requirements for quality of service of data transmission along a side communication line.

12 cl, 15 dwg, 11 tbl

Description

The technical field to which the invention belongs

The present invention relates to the field of terminal technology, in particular to a communication method and a corresponding device.

State of the art

V2X (vehicle - X) communication technology is the core technology of the intelligent transportation system. V2X includes vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle to pedestrian" (vehicle to pedestrian, V2P). The intelligent transportation system (ITS) aims to obtain various kinds of traffic information such as real-time road conditions, traffic information and pedestrian information through V2X communication, thereby improving traffic safety, improving transportation efficiency and providing a variety of streaming media services to users.

The Intelligent Transportation System has strict requirements for low latency and highly reliable communications. A 3rd generation partnership project (3GPP) is, for example, 2G, 3G, long term evolution (LTE) or 5G. 3GPP cellular technology has the advantages of low latency, high speed, wide coverage, large bandwidth and high reliability. Thus, at present, the introduction of an intelligent transport system using 3GPP cellular technology is becoming the main direction.

V2X communication may be implemented via side link communication. The communication link for realizing direct communication between end devices is called a side link (sidelink, SL). For example, as shown in FIG. 1, a channel for realizing direct communication between vehicle a and vehicle b is called a side link.

Sidelink communication includes a network device scheduling mode. The network device may be a base station or the like. The network device scheduling mode means that the terminal device sends request information to the network device, and the network device dynamically or semi-dynamically schedules a resource for V2X sidelink communication. However, in practice, it has been found that in the scheduling mode of the network device for sidelink communication, the resource scheduled by the network device for the terminal device cannot meet the quality of service requirements for sidelink data transmission.

The essence of the invention

Embodiments of the present application provide a communication method and a corresponding apparatus for meeting quality of service requirements for a network device. In this way, the network device can schedule a resource for the terminal device that satisfies the quality of service requirements for sidelink data transmission.

According to a first aspect, an embodiment of the present application provides a communication method. The method is applied in a terminal device, and the method includes: obtaining a first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, delay information, communication range information , data rate information and service type information; and sending the identifier to the network device, where the identifier corresponds to the QoS parameter. Optionally, the first data is data to be transmitted by the terminal on the sidelink.

It should be understood that by implementing the method described in the first aspect, the terminal device can send an identifier corresponding to the QoS parameter to the network device. Therefore, after receiving the ID, the network device can determine the corresponding QoS parameter based on the ID. Thus, by implementing the method described in the first aspect, the terminal device can provide the quality of service requirement for the network device. In addition, the QoS parameter is specified using an identifier instead of passing it directly, and this reduces the amount of overhead.

Optionally, the QoS parameter further includes data priority information.

In this implementation, the terminal may indicate to the network device at least two types of QoS parameters. Thus, it helps the network device to schedule resources for the terminal device that meet different quality of service requirements for sidelink data transmission.

Optionally, the identifier may be one of a logical channel group identifier, a QoS class identifier index (QCI index), and a flow identifier.

If necessary, different types of services can be distinguished by application identifiers carried at the application layer, or top layer identifiers delivered by the upper layer (above the access layer).

Optionally, the tag further receives a first message sent by the network device, where the first message includes a match between the identifier and the QoS parameter. After receiving the first message sent by the network device, the terminal device may retain the mapping included in the first message between the identifier and the QoS parameter. In other words, in this implementation, the mapping stored in the terminal device between the identifier and the QoS parameter is configured by the network device.

Optionally, the first message may be radio resource control (RRC) signaling.

If necessary, the correspondence stored in the terminal device between the identifier and the QoS parameter can be configured in advance. For example, the mapping between the identifier and the QoS parameter is specified in the protocol, and the device vendor may pre-configure the mapping between the identifier and the QoS parameter in the tag prior to delivery of the tag. Alternatively, when a terminal device accesses a network, the network device may pre-configure the mapping between the identifier and the QoS parameter in the terminal device.

If necessary, the correspondence between the identifier and the QoS parameter is pre-configured for the end device; and after the terminal device receives the first message that is sent by the network device and which includes the mapping between the identifier and the QoS parameter, the terminal replaces the previously configured mapping between the identifier and the QoS parameter with the mapping included in the first message between the identifier and the QoS parameter QoS. In other words, after receiving the first message sent by the network device, the terminal device may update the pre-configured mapping between the identifier and the QoS parameter to the mapping included in the first message between the identifier and the QoS parameter.

Optionally, the specific implementation of sending the identifier to the network device is: sending a buffer status report (BSR) to the network device, where the BSR includes the identifier, and the BSR further includes the total amount of data of all data that is in the terminal and corresponds to the identifier, or the BSR further includes information about the destination address corresponding to the first data and/or the data volume of all data that is in the terminal device and that corresponds to both the destination address information and the identifier. The data corresponding to the identifier is the data corresponding to the QoS parameter that corresponds to the identifier.

If necessary, the amount of data in the tag may include, but is not limited to, the amount of data in the buffer of the tag. The buffer may be a packet data convergence protocol (PDCP) buffer and/or a radio link control (RLC) buffer. The present application is not limited to this.

Since the BSR is sent dynamically, in this implementation, the terminal device may dynamically send, to the network device, the identifier and the total amount of data of all data corresponding to the identifier, or may dynamically send, to the network device, the identifier, the destination address information corresponding to the first data , and/or the data volume of all data that is in the terminal device and which corresponds to both the information about the destination address and the identifier. Thus, the network device can dynamically perform an operation associated with it based on the ID and total data size of all data corresponding to the ID, or based on the destination address information corresponding to the first data and/or data size of all data that is in the terminal device and match both the destination address information and the identifier.

If necessary, the terminal further receives scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and the terminal further transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

It should be understood that in this implementation, the network device may allocate a scheduling resource to a terminal device, and the terminal device may transmit the corresponding data using the allocated scheduling resource.

Optionally, the tag further receives a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier. After receiving the second message sent by the network device, the terminal device may store the mapping included in the second message between the subcarrier spacing and/or transmission time interval and the identifier. In other words, in this implementation, the correspondence stored in the tag between the subcarrier spacing and/or transmission time interval and the identifier is configured by the network device.

Optionally, the second message may be an RRC signaling.

If necessary, the correspondence stored in the terminal device between the subcarrier spacing and/or transmission time interval and the identifier can be configured in advance. For example, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the subcarrier spacing and/or transmission time interval and the identifier to the terminal prior to delivery of the terminal. Alternatively, when a terminal device accesses a network, the network device may pre-configure a mapping between subcarrier spacing and/or transmission time interval and an identifier in the terminal device.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is preconfigured for the terminal; and after the tag receives a second message that is sent by the network device and which includes the mapping between the subcarrier spacing and/or transmission timeslot and the identifier, the tag replaces the preconfigured mapping between the subcarrier spacing and/or transmission timeslot and the identifier to the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier. In other words, upon receiving the second message sent by the network device, the terminal may update the pre-configured mapping between the subcarrier spacing and/or transmission time interval and the identifier with the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier.

According to a second aspect, an embodiment of the present application provides a communication method. The method is applied in a terminal device, and the method includes: obtaining the first data and a QoS parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, latency information, communication range information, information about data rate and service type information; determining an identifier, where the identifier corresponds to a QoS parameter; receiving scheduling resource information sent by the network device, wherein the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and transmitting, on the sidelink using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the identifier corresponds to a subcarrier spacing and/or a transmission time interval.

By implementing the method described in the second aspect, the terminal device does not dynamically access the network device for the scheduling resource, and the network device can statically or semi-statically configure the resource set for the terminal device. Thus, the terminal can independently select an appropriate scheduling resource from a set of resources to transmit the corresponding data. A resource set may include, but is not limited to, a resource pool or a semi-statically scheduled resource.

Optionally, the QoS parameter further includes data priority information.

Optionally, the identifier may be one of a logical channel group identifier, a QoS class identifier index (QCI index), and a flow identifier.

If necessary, different types of services can be distinguished by application identifiers carried at the application layer, or top layer identifiers delivered by the upper layer (above the access layer).

Optionally, the tag further receives a first message sent by the network device, where the first message includes a match between the identifier and the QoS parameter.

Optionally, the first message may be radio resource control (RRC) signaling.

If necessary, the correspondence stored in the terminal device between the identifier and the QoS parameter can be configured in advance.

If necessary, the correspondence between the identifier and the QoS parameter is pre-configured for the end device; and after the terminal device receives the first message that is sent by the network device and which includes the mapping between the identifier and the QoS parameter, the terminal replaces the previously configured mapping between the identifier and the QoS parameter with the mapping included in the first message between the identifier and the QoS parameter QoS.

Optionally, the tag further receives a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

Optionally, the second message may be an RRC signaling.

If necessary, the correspondence stored in the terminal device between the subcarrier spacing and/or transmission time interval and the identifier can be configured in advance.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is preconfigured for the terminal; and after the tag receives a second message that is sent by the network device and which includes the mapping between the subcarrier spacing and/or transmission timeslot and the identifier, the tag replaces the preconfigured mapping between the subcarrier spacing and/or transmission timeslot and the identifier to the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier.

To obtain the beneficial effects of additional implementations of the second aspect, one should refer to the beneficial effects of the corresponding parts of the first aspect. The details are again not described here.

According to a third aspect, an embodiment of the present application provides a communication method. The method is applied in a terminal device, and the method includes: obtaining a first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, latency information, range information communication, data rate information and service type information; and sending the SR to the network device using the SR resource. Optionally, the SR corresponds to the identifier, and the identifier corresponds to the QoS parameter. If necessary, the SR resource corresponds to the QoS parameter.

It should be understood that by implementing the method described in the third aspect, the terminal device can determine, based on the QoS parameter, the SR resource to send the SR and send the SR on the determined scheduling request (SR) resource. Therefore, after discovering the SR on the SR resource, the network device can determine the QoS parameter based on the SR resource. Thus, by implementing the method described in the third aspect, the terminal device can meet the quality of service requirement for the network device. In addition, the QoS parameter is indicated using the SR resource instead of direct transmission, and this can reduce the amount of overhead.

Optionally, the QoS parameter further includes data priority information.

In this implementation, the terminal may indicate to the network device at least two types of QoS parameters. Thus, it helps the network device to schedule resources for the terminal device that satisfy the various quality of service requirements of sidelink data transmission.

Optionally, the identifier may be one of a logical channel group identifier, a QCI, and a flow identifier.

If necessary, different types of services can be distinguished by application identifiers carried at the application layer, or top layer identifiers delivered by the upper layer (above the access layer).

Optionally, the tag further receives a first message sent by the network device, where the first message includes a mapping between the identifier and the QoS parameter and a mapping between the SR resource and the identifier.

Optionally, the first message may be an RRC signaling.

If necessary, the mapping stored in the tag between the ID and the QoS parameter and the mapping stored in the tag between the SR resource and the ID can be configured in advance.

If necessary, the correspondence between the identifier and the QoS parameter and the correspondence between the SR resource and the identifier are preconfigured for the terminal device; and after the terminal device receives the first message that is sent by the network device and which includes the mapping between the identifier and the QoS parameter and the mapping between the SR resource and the identifier, the terminal replaces the preconfigured mapping between the identifier and the QoS parameter and the preconfigured mapping between the SR resource and the identifier against the correspondence included in the first message between the identifier and the QoS parameter and the correspondence included in the first message between the SR resource and the identifier.

Optionally, the terminal device may receive the first message sent by the network device, where the first message includes a mapping between the SR resource and the QoS parameter.

If necessary, the correspondence stored in the terminal device between the SR resource and the QoS parameter can be configured in advance.

If necessary, the mapping between the SR resource and the QoS parameter is pre-configured for the end device; and after the tag receives the first message that is sent by the network device and which includes the mapping between the SR resource and the QoS parameter, the tag replaces the preconfigured mapping between the SR resource and the QoS parameter with the mapping included in the first message between the resource SR and QoS parameter.

If necessary, the terminal further receives scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

It should be understood that in this implementation, the network device may allocate a scheduling resource to a terminal device, and the terminal device may transmit the corresponding data using the allocated scheduling resource.

Optionally, the tag further receives a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

Optionally, the second message may be an RRC signaling.

If necessary, the correspondence stored in the terminal device between the subcarrier spacing and/or transmission time interval and the identifier can be configured in advance.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is pre-configured for the terminal; and after the tag receives a second message that is sent by the network device and which includes the mapping between the subcarrier spacing and/or transmission timeslot and the identifier, the tag replaces the preconfigured mapping between the subcarrier spacing and/or transmission timeslot and the identifier to the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier.

Optionally, the SR resource is an SR resource that is in the set of SR resources corresponding to the identifier and that corresponds to the data amount of the first data.

In this implementation, the tag may provide a data volume of the first data to the network device.

If necessary, the data amount of the first data may include, but is not limited to, the data amount of the buffer corresponding to the first data.

Optionally, the SR resource used by the terminal to send the SR is the SR resource that is in the set of SR resources corresponding to the QoS parameter and which corresponds to the data amount of the first data. In this implementation, the tag may provide a data volume of the first data to the network device.

Optionally, the terminal device may receive a third message sent by the network device, where the third message includes a correspondence between the amount of data and the SR resource.

Optionally, the third message may be an RRC signaling.

If necessary, the correspondence stored in the terminal device between the amount of data and the resource SR can be configured in advance.

If necessary, the correspondence between the amount of data and the SR resource is pre-configured for the terminal device; and after the terminal device receives the third message that is sent by the network device and which includes the correspondence between the amount of data and the SR resource, the terminal device replaces the preconfigured correspondence between the amount of data and the SR resource with the correspondence included in the third message between the amount data and resource SR.

Optionally, the terminal device may receive a fourth message sent by the network device, where the fourth message includes a correspondence between the amount of data and the pilot sequence.

If necessary, the correspondence stored in the terminal device between the amount of data and the pilot sequence can be configured in advance.

If necessary, the correspondence between the amount of data and the pilot sequence is pre-configured for the terminal device; and upon receiving a fourth message sent by the network device that includes a data volume-to-pilot mapping, the terminal replaces the preconfigured data-to-pilot mapping with the data-to-pilot mapping included in the fourth message.

In this case, the terminal may send different pilots on the same SR to distinguish between data amounts. Thus, the network device can determine the amount of data by detecting the corresponding SR resource and detecting the pilot sequence.

According to a fourth aspect, an embodiment of the present application provides a communication method. The method is applied in a network device, and the method includes: receiving an identifier from a terminal device; and determining a QoS parameter, where the QoS parameter corresponds to the identifier, and the QoS parameter includes at least one of reliability information, latency information, communication distance information, data rate information, and service type information.

Optionally, the QoS parameter further includes data priority information.

Optionally, the identifier may be one of a logical channel group identifier, a QCI, and a flow identifier.

If necessary, different types of services can be distinguished by application identifiers carried at the application layer, or top layer identifiers delivered by the upper layer (above the access layer).

If necessary, the network device additionally sends a first message to the terminal device, where the first message includes the correspondence between the identifier and the QoS parameter.

Optionally, the first message may be an RRC signaling.

Optionally, the specific implementation of the network device receiving the identifier from the terminal is: receiving a buffer status report (BSR) from the terminal, where the BSR includes the identifier and the BSR further includes the total data size of all data that is in the terminal and that match the identifier, or the BSR further includes the destination address information corresponding to the first data and/or the data volume of all data that is in the tag and that matches both the destination address information and the identifier. The data corresponding to the identifier is the data corresponding to the QoS parameter that corresponds to the identifier.

If necessary, the amount of data in the tag may include, but is not limited to, the amount of data in the buffer of the tag. The buffer may be a packet data convergence protocol (PDCP) buffer and/or a radio link control (RLC) buffer. The present application is not limited to this.

If necessary, the network device further sends the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the network device further sends a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

For the beneficial effects of the fourth aspect, see the beneficial effects of the respective parts of the first aspect. The details are again not described here.

According to a fifth aspect, an embodiment of the present application provides a communication method. The method is applied in a network device and includes: discovering an SR on an SR resource; and determining a QoS parameter, where the QoS parameter includes at least one of reliability information, delay information, communication range information, data rate information, and service type information. Optionally, the QoS parameter corresponds to the identifier, and the identifier corresponds to the SR resource. If necessary, the QoS parameter corresponds to the SR resource.

Optionally, the QoS parameter further includes data priority information.

Optionally, the identifier may be one of a logical channel group identifier, a QCI, and a flow identifier.

If necessary, different types of services can be distinguished by application identifiers carried at the application layer, or top layer identifiers delivered by the upper layer (above the access layer).

Optionally, the network device further sends a first message to the terminal device, where the first message includes the correspondence between the identifier and the QoS parameter and the correspondence between the SR resource and the identifier.

Optionally, the first message may be an RRC signaling.

Optionally, the network device may send a first message to the terminal device, where the first message includes a mapping between the SR resource and the QoS parameter.

If necessary, the network device further sends the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the network device further sends a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

Optionally, the second message may be an RRC signaling.

If necessary, the network device further determines the amount of data, where the amount of data corresponds to the resource SR.

If necessary, the network device sends a third message to the terminal device, where the third message includes the correspondence between the amount of data and the resource SR.

If necessary, the network device further detects a pilot sequence on the SR resource and determines a data amount, where the data amount corresponds to the detected pilot sequence.

If necessary, the network device sends a fourth message to the terminal device, where the fourth message includes the correspondence between the amount of data and the pilot sequence.

For the beneficial effects of the fifth aspect, see the beneficial effects of the respective parts of the third aspect. The details are again not described here.

According to a sixth aspect, a terminal device is provided. The terminal device includes: a processing module configured to obtain the first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, latency information, range information communication, data rate information and service type information; and a communication module configured to send the identifier to the network device, where the identifier corresponds to the QoS parameter. Optionally, the first data is data to be transmitted by the terminal on the sidelink.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module is further configured to receive the first message sent by the network device, where the first message includes a correspondence between the identifier and the QoS parameter.

If necessary, the method for sending the communication module of the identifier to the network device is, in particular: sending a buffer status report (BSR) to the network device, where the BSR includes the identifier, and the BSR further includes the total amount of data of all data that is in tag and that match the identifier, or the BSR further includes destination address information corresponding to the first data and/or a data volume of all data that is in the tag and that matches both the destination address information and the identifier.

If necessary, the communication module is further configured to receive scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and the communication module is further configured to transmit, on the sidelink using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

If necessary, the communication module is further configured to receive a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the network device may further perform another possible implementation of the first aspect. The details are again not described here. Based on the same inventive concept, in order to provide the problem solving principle and benefits of the terminal device, one should refer to the problem solving principle and benefits of the first aspect or possible implementations of the first aspect. Repetitive parts are not described in detail again.

According to a seventh aspect, a terminal device is provided. The terminal device includes: a processing module configured to obtain the first data and a QoS parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, delay information, communication distance information, speed information transmitting data and information about the type of service, where the processing module is further configured to determine the identifier, where the identifier corresponds to the QoS parameter; and a communication module configured to receive scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval, the communication module is further configured to transmit on a sidelink using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the identifier corresponds to a subcarrier spacing and/or a transmission time interval.

Optionally, the QoS parameter further includes data priority information.

Optionally, the communication module further receives a first message sent by the network device, where the first message includes a match between the identifier and the QoS parameter.

If necessary, the communication module further receives a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the correspondence stored in the terminal device between the subcarrier spacing and/or transmission time interval and the identifier can be configured in advance.

If necessary, the terminal may further perform another possible implementation of the second aspect. The details are again not described here. Based on the same inventive concept, in order to provide the problem solving principle and benefits of the terminal device, one should refer to the problem solving principle and benefits of the second aspect or possible implementations of the second aspect. Repetitive parts are not described in detail again.

According to an eighth aspect, a terminal device is provided. The terminal device includes: a processing module configured to obtain the first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, latency information, range information communication, data rate information and service type information; and a communication module configured to send the SR to the network device using the SR resource. Optionally, the SR corresponds to the identifier, and the identifier corresponds to the QoS parameter. If necessary, the SR resource corresponds to the QoS parameter.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module is further configured to receive a first message sent by the network device, where the first message includes a match between the identifier and the QoS parameter and a match between the SR resource and the identifier.

Optionally, the terminal device may receive the first message sent by the network device, where the first message includes a mapping between the SR resource and the QoS parameter.

If necessary, the communication module is further configured to receive scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and the communication module is further configured to transmit, on the sidelink using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

If necessary, the communication module is further configured to receive a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

Optionally, the SR resource used by the communication module to send the SR is the SR resource that is in the set of SR resources corresponding to the ID and that corresponds to the data amount of the first data.

Optionally, the SR resource used by the communication module to send the SR is the SR resource that is in the SR resource set corresponding to the QoS parameter and that corresponds to the data amount of the first data.

If necessary, the communication module is further configured to receive a third message sent by the network device, where the third message includes a correspondence between the amount of data and the resource SR.

If necessary, the communication module is further configured to receive a fourth message sent by the network device, where the fourth message includes a correspondence between the amount of data and the pilot sequence. In this case, the communication module may send different pilot sequences on the same SR in order to distinguish between data amounts. Thus, the network device can determine the amount of data by detecting the corresponding SR resource and detecting the pilot sequence.

If necessary, the terminal may further perform another possible implementation of the third aspect. The details are again not described here. Based on the same inventive concept, in order to provide the problem solving principle and benefits of the terminal device, one should refer to the problem solving principle and benefits of the third aspect or possible implementations of the third aspect. The repeating steps are again not described in detail.

According to a ninth aspect, a network device is provided. The network device includes: a communication module configured to receive an identifier from a terminal device; and a processing unit configured to determine a QoS parameter, where the QoS parameter corresponds to the identifier, and the QoS parameter includes at least one of reliability information, latency information, communication distance information, data rate information, and information about service type.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module is further configured to send a first message to the terminal device, where the first message includes a correspondence between the identifier and the QoS parameter.

If necessary, the method for the communication module to receive the identifier from the terminal device is, in particular: receiving a buffer status report (BSR) from the terminal device, where the BSR includes the identifier, and the BSR further includes the total amount of data of all data that is in tag and that match the identifier, or the BSR further includes destination address information corresponding to the first data and/or a data volume of all data that is in the tag and that matches both the destination address information and the identifier.

If necessary, the communication module is further configured to send the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the communication module is further configured to send a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the terminal may further perform another possible implementation of the fourth aspect. The details are again not described here. Based on the same inventive concept, in order to provide the problem solving principle and benefits of the terminal device, one should refer to the problem solving principle and benefits of the fourth aspect or possible implementations of the fourth aspect. The repeating steps are again not described in detail.

According to a tenth aspect, a network device is provided. The network device includes: a communication module configured to locate an SR on the SR resource; and a processing unit configured to determine a QoS parameter, where the QoS parameter includes at least one of reliability information, latency information, communication distance information, data rate information, and service type information. Optionally, the QoS parameter corresponds to the identifier, and the identifier corresponds to the SR resource. If necessary, the QoS parameter corresponds to the SR resource.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module is further configured to send a first message to the terminal device, where the first message includes the correspondence between the identifier and the QoS parameter and the correspondence between the SR resource and the identifier.

If necessary, the communication module is further configured to send a first message to the terminal device, where the first message includes a correspondence between the SR resource and the QoS parameter.

If necessary, the communication module is further configured to send the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the communication module is further configured to send a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the processing module is further configured to determine the amount of data, where the amount of data corresponds to the resource SR.

If necessary, the communication module is further configured to send a third message to the terminal device, where the third message includes a correspondence between the amount of data and the resource SR.

If necessary, the processing module is further configured to detect a pilot sequence on the SR resource and determine the amount of data, where the amount of data corresponds to the detected pilot sequence.

If necessary, the communication module is further configured to send a fourth message to the terminal device, where the fourth message includes a correspondence between the amount of data and the pilot sequence.

If necessary, the terminal may further perform another possible implementation of the fifth aspect. The details are again not described here. Based on the same inventive concept, in order to provide the problem solving principle and benefits of the terminal device, one should refer to the problem solving principle and benefits of the fifth aspect or possible implementations of the fifth aspect. Repetitive parts are not described in detail again.

According to an eleventh aspect, a communication device is provided. The communication device includes: at least one processor and a communication interface. The communication interface is used by a communication device to exchange information with another communication device; and when the program instruction is executed in at least one processor, the method according to any one of the first to fifth aspects and further implementations of the first aspect to the fifth aspect is implemented in any of the following devices: a terminal device and a network device. In order to realize the problem solving and benefits of the communication device, reference should be made to the respective parts of the description and the benefits of the first aspect to the fifth aspect, and further implementations of the first aspect to the fifth aspect. The repeating steps are again not described in detail.

According to a twelfth aspect, a medium for storing computer programs is provided. The computer program carrier has a program instruction; and when the program instruction is executed directly or indirectly, the method according to any of the first to fifth aspects and further implementations of the first aspect to the fifth aspect is implemented in any of the following devices: a terminal device and a network device.

According to a thirteenth aspect, a chip system is provided. The chip system is applied to a communication device and includes at least one processor; and when the program instruction is executed in at least one processor, the method according to any of the first to fifth aspects and further implementations of the first aspect to the fifth aspect is implemented in any of the following devices: a terminal device and a network device.

According to a fourteenth aspect, a communication system is provided. The communication system includes the aforementioned communication device. For example, a communication system includes a terminal device and a network device. The terminal device performs the method described in the first aspect and additional implementations of the first aspect, and the network device performs the method described in the fourth aspect and additional implementations of the fourth aspect. Alternatively, the terminal device performs the method described in the third aspect and additional implementations of the third aspect, and the network device performs the method described in the fifth aspect and additional implementations of the fifth aspect.

Brief description of the drawings

Fig. 1 - schematic representation of the existing communication system;

fig. 2 is a schematic representation of a communication system according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a communication method according to an embodiment of the present application;

fig. 4 is a schematic block diagram of a BSR according to an embodiment of the present application;

fig. 5 is a schematic block diagram of a BSR according to an embodiment of the present application;

fig. 6 - fig. 9 are schematic flowcharts of communication methods according to embodiments of the present application.

fig. 10 and FIG. 11 are schematic block diagrams of terminal devices according to embodiments of the present application;

fig. 12 and FIG. 13 are schematic block diagrams of network devices according to embodiments of the present application;

fig. 14 is a schematic block diagram of a terminal device according to an embodiment of the present application; and

fig. 15 is a schematic block diagram of a network device according to an embodiment of the present application.

Detailed description of the invention

The following describes in detail specific embodiments of the present application with reference to the accompanying drawings.

Embodiments of the present application provide a communication method and a corresponding apparatus for fulfilling quality of service requirements for a network device. Thus, the network device can schedule a resource for the terminal device that satisfies the quality of service requirements of the sidelink data transmission.

In order to better understand the embodiments of the present application, the following describes a communication system in which the embodiments of the present application may be applied.

In FIG. 2 is a schematic representation of a communication system according to an embodiment of the present application. As shown in FIG. 2, the communication system includes a network device and at least one terminal device. In FIG. 2 uses an example in which the communication system includes terminal 1 and terminal 2.

The network device may be an evolved NodeB (evolved NodeB, eNB or eNodeB) in an LTE system, or a radio network controller in a cloud radio access network (CRAN), or may be an access network device in a 5G network, such as a gNB, or may be a small cell, a micro base station or a transmission reception point (TRP), or may be a relay station, an access point, an access network device in a future public land mobile network (PLMN) evolved, and the like.

The terminal may be an access terminal, a user equipment (UE), a user equipment, a subscriber station, a mobile station, a mobile console, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, user device, vehicle, or infrastructure. The access terminal can 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 portable with wireless communication function, computing device, other data processing device connected to a wireless modem, vehicle-mounted device, wearable device, IoT terminal device, virtual reality device, terminal device in the future 5G network, terminal device in the future advanced terrestrial a public land mobile network (PLMN), etc. Fig. 2 shows an example in which terminal 1 and terminal 2 are vehicles.

Terminal 1 sends data to terminal 2 via side link communication. Sidelink communication means that terminal device 1 directly sends data to terminal device 2, and data sent by terminal device 1 to terminal device 2 is not forwarded by the network device. As shown in FIG. 2, the channel for realizing direct communication between terminal device 1 and terminal device 2 is called a side link.

Sidelink communication includes a network device scheduling mode. The network device scheduling mode means that the terminal device sends request information to the network device, and the network device dynamically or semi-dynamically schedules a resource for V2X sidelink communication. For example, if the terminal device 1 needs to send data to the terminal device 2 on the side link, the terminal device 1 must send request information to the network device. Thus, the network device allocates a scheduling resource to the terminal device 1, which is used to send data to the terminal device 2 on the side link.

The communication method and associated apparatus provided in the present application are described in detail below.

In FIG. 3 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 3, the communication method includes the following steps 301 to 303.

301: The terminal receives the first data and the QoS parameter corresponding to the first data.

In this embodiment of the present application, for example, the terminal may be terminal 1 or terminal 2 shown in FIG. 2.

In this embodiment of the present application, the quality of service (QoS) parameter includes at least one of reliability information, latency information, communication range information, data rate information, and service type information.

For example, the QoS parameter includes one of reliability information, delay information, communication range information, data rate information, and service type information.

Alternatively, the QoS parameter includes any two of reliability information, delay information, communication distance information, data rate information, and service type information. For example, the QoS parameter includes reliability information and delay information; or the QoS parameter includes reliability information and communication range information; or the QoS parameter includes reliability information and data rate information; or the QoS parameter includes delay information and communication range information; or the QoS parameter includes delay information and data rate information; or the QoS parameter includes communication range information and data rate information.

Alternatively, the QoS parameter includes any three of reliability information, delay information, communication range information, data rate information, and service type information. For example, the QoS parameter includes reliability information, latency information, and communication distance information; or the QoS parameter includes delay information, communication distance information, and data rate information; or the QoS parameter includes communication range information, data rate information, and service type information.

Alternatively, the QoS parameter includes any four of reliability information, delay information, communication range information, data rate information, and service type information. For example, the QoS parameter includes reliability information, latency information, communication range information, and data rate information; or the QoS parameter includes delay information, communication range information, data rate information, and service type information.

Alternatively, the QoS parameter includes reliability information, latency information, communication range information, data rate information, and service type information.

Optionally, the QoS parameter further includes data priority information. In this implementation, the terminal may indicate to the network device at least two types of QoS parameters. Thus, it helps the network device to schedule resources for the terminal device that meet different quality of service requirements for sidelink data transmission.

Reliability information is used to indicate the reliability corresponding to the data. The data in the terminal device may have different reliability. The reliability associated with the data represents the requirement/level/limitation of the reliability of the data transmission. The transmission reliability may be, but is not limited to, end-to-end transmission reliability, air interface transmission reliability, and the like. For example, transmission reliability can be defined as a 1-bit error rate, namely as a 1-bit error rate; 1-symbol error rate, namely 1-symbol error rate; or 1-burst error rate, namely 1-burst error rate.

The delay information is used to indicate the delay corresponding to the data. The data in the terminal may have different latency requirements/limits. The delay may be, but is not limited to, end-to-end delay, air interface delay, delay budget, transmission timeslot, and the like.

The communication range information is used to indicate the communication range corresponding to the data. The data in the terminal device can have different transmission distances.

The bit rate information is used to indicate the bit rate corresponding to the data. The data in the terminal device can have different transmission rates.

A terminal may support many different service types, and different pieces of service type information are used to indicate different types of services. For example, the aforementioned different types of services may be services corresponding to different receiving sides and/or different transmitting sides. For example, the above-mentioned different types of services may be a V2V service, a V2P service, a V2I service, a V2N service, a pedestrian to vehicle (P2V) service, a pedestrian to pedestrian (P2P) service, and a "pedestrian to pedestrian" (P2P) service. pedestrian infrastructure" (pedestrian to infrastructure, P2I).

If necessary, the aforementioned different types of services can be distinguished by application identifiers carried at the application layer or upper layer identifiers delivered by the upper layer (above the access layer). For example, a collision warning service and an entertainment and multimedia service may have different top-level identifiers. For example, the top-level identifier may be an ITS application identifier (ITS-AID) or a provider service identifier (PSID).

The data priority information is used to indicate the priority corresponding to the data. The data in the target device can have different priorities. Typically, data with different priorities differs in the selection and allocation of resources at the access layer, and preferably, the transmission of data with a high priority should be guaranteed.

The QoS parameter may include, but is not limited to, an identifier, an index, or other information indicating or pointing to QoS. For example, the QoS parameter is reliability information, and the reliability information may be, but is not limited to, a reliability identifier, a reliability index, a reliability range, and a reliability value.

Optionally, the specific implementation in which the terminal device receives the first data and the quality of service (QoS) parameter corresponding to the first data is as follows: the access layer of the terminal device receives the first data and the QoS parameter of the quality of service corresponding to the first data that is sent by the upper layer ( which is a layer above the access layer and, for example, can be an application layer, a network transmission layer or an adaptation layer) of a terminal device. In this implementation, after generating the first data and the QoS parameter corresponding to the first data, the upper layer of the terminal device sends the first data and the QoS parameter corresponding to the first data to the access layer of the terminal device.

302: The end device sends an identifier to the network device.

The identifier corresponds to the QoS setting.

In this embodiment of the present application, the terminal device stores the correspondence between the identifier and the QoS parameter. After receiving the QoS parameter, the terminal device obtains, based on the correspondence between the ID and the QoS parameter, the ID corresponding to the QoS parameter and sends the ID corresponding to the QoS parameter to the network device.

For example, the terminal maintains the correspondence shown in Table 1 below. If the QoS parameter is Reliability Information 1, Latency Information 1, Communication Range Information 1, Data Rate Information 1, and Data Priority Information 1, after receiving the QoS parameter, the terminal device finds from the correspondence presented in table 1, the identifier 1 corresponding to the QoS parameter, and sends the identifier 1 to the network device.

Table 1

Identifier QoS setting ID 1 Reliability information 1, delay information 1, communication range information 1, data rate information 1 and data priority information 1 ID 2 Reliability information 2, delay information 2, communication range information 2, data rate information 2 and data priority information 2 ID 3 Reliability information 3, delay information 3, communication distance information 3, data rate information 3 and data priority information 3

As another example, the end device maintains the mapping shown in Table 2 below. Different QoS parameters can correspond to the same identifier. For example, the QoS parameter, namely reliability information 1, delay information 1, communication range information 1, data rate information 1, and data priority information 1, corresponds to identifier 1; and the QoS parameter, namely, reliability information 2, delay information 1, communication range information 1, data rate information 1, and data priority information 1, also correspond to identifier 1.

table 2

Identifier QoS setting ID 1 Reliability information 1, delay information 1, communication range information 1, data rate information 1 and data priority information 1 Reliability information 2, delay information 1, communication distance information 1, data rate information 1 and data priority information 1 ID 2 Reliability information 2, delay information 2, communication range information 2, data rate information 2 and data priority information 2 ID 3 Reliability information 3, delay information 3, communication distance information 3, data rate information 3 and data priority information 3

Optionally, the identifier may be one of a logical channel group identifier, a QCI, and a flow identifier.

Optionally, the network device may send a first message to the end device, where the first message includes a match between the identifier and the QoS parameter. The end device may receive the first message sent by the network device. After receiving the first message sent by the network device, the end device retains the mapping included in the first message between the identifier and the QoS parameter. In other words, in this implementation, the mapping stored in the terminal device between the identifier and the QoS parameter is configured by the network device.

Optionally, the first message may be an RRC signaling. The RRC signaling may be a system information block (SIB) or a dedicated RRC signaling.

If necessary, the correspondence, in the first message, between the identifier and the QoS parameter may be implicit or explicit.

For example, the correspondence, in the first message, between the identifier and the QoS parameter is implicit. The identifier may have a specific sequence, and the sequence may be specified in the protocol. In this case, the first message may not include the identifier. For example, the identifier is assumed to be a logical channel group identifier, and the QoS parameter includes delay information and data priority information. The first message includes {delay information 1, data priority information 1}, {delay information 2, data priority information 2} and {delay information 3, data priority information 3}. The protocol provides that the logical channel group identifiers are arranged in ascending order, so that the logical channel group identifier 1 is the logical channel group identifier 3, respectively, and sequentially correspond to the above elements.

As another example, one piece of information in a QoS parameter, such as data priority information, may be provided with a specific number or sequence. For example, the priority information may be a priority identifier, and priority identifiers 1 to 8, respectively, define priorities in descending order. When a plurality of QoS parameters correspond to the same identifier, for example, when identifier 1 corresponds to priority identifier 1, priority identifier 2, priority identifier 3 and priority identifier 4, i.e. identifier 1 corresponds to priority identifier 1 - priority identifier 4, the first message may include includes only priority ID 1 and priority ID 4. It is provided in the protocol that the priority identifier 1 and the priority identifier 4 which are included in the first message represent, respectively, an upper bound and a lower bound of the priority identifiers. In this case, the match can be considered implicit. It should be understood that the first message includes a correspondence between identifier 1 and priority identifiers 1-4. For example, if the QoS parameter corresponding to the first data is priority ID 3, it is determined that priority ID 3 corresponds to ID 1.

As another example, the correspondence, in the first message, between the identifier and the QoS parameter is explicit; and the identifier is assumed to be a logical channel group identifier and the QoS parameter includes delay information and data priority information. The first message includes {delay information 1, data priority information 1, logical channel group identifier 1}, {delay information 2, data priority information 2, logical channel group identifier 2} and {delay information 3, logical channel group 3 about data priority, logical channel group identifier 3}. In {delay information 1, data priority information 1, logical channel group ID 1}, the logical channel group ID 1 corresponds to delay information 1 and data priority information 1. In {delay information 2, data priority information 2, logical channel group ID 2}, the logical channel group ID 2 corresponds to delay information 2 and data priority information 2. In {delay information 3, data priority information 3, logical channel group ID 3}, the logical channel group ID 3 corresponds to delay information 3 and data priority information 3.

If necessary, the correspondence stored in the terminal device between the identifier and the QoS parameter can be configured in advance. For example, the correspondence between an identifier and a QoS parameter is specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the identifier and the QoS parameter in the tag before shipping the tag. Alternatively, when a terminal device accesses a network, the network device may pre-configure the mapping between the identifier and the QoS parameter in the terminal device.

If necessary, the correspondence between the identifier and the QoS parameter is pre-configured for the end device; and after the terminal device receives the first message that is sent by the network device and which includes the mapping between the identifier and the QoS parameter, the terminal replaces the previously configured mapping between the identifier and the QoS parameter with the mapping included in the first message between the identifier and the QoS parameter QoS. In other words, after receiving the first message sent by the network device, the terminal updates the pre-configured mapping between the identifier and the QoS parameter with the mapping included in the first message between the identifier and the QoS parameter.

Optionally, the specific implementation in which the tag sends the identifier to the network device is as follows: the tag sends a buffer status report (BSR) to the network device, where the BSR includes the identifier. If necessary, the BSR further includes the total data amount of all data that is in the terminal device and that corresponds to the identifier, or the BSR further includes information about the destination address corresponding to the first data, and/or the data volume of all data that is in the terminal device , which matches both the destination address information and the identifier. Accordingly, the specific implementation in which the network device receives the identifier from the terminal device is as follows: the network device receives the BSR from the terminal device. If necessary, the amount of data in the tag may include, but is not limited to, the amount of data in the buffer of the tag. The buffer may be a packet data convergence protocol (PDCP) buffer and/or a radio link control (RLC) buffer. The present application is not limited to this.

The data corresponding to the identifier is the data corresponding to the QoS parameter that corresponds to the identifier. When one identifier corresponds to a plurality of QoS parameters, the data corresponding to the identifier is data corresponding to the plurality of QoS parameters that correspond to the identifier. For example, both the first data and the second data correspond to the QoS parameter 1, and the QoS parameter 1 corresponds to the identifier 1. In this case, the identifier 1 corresponds to the first data and the second data. Thus, all data corresponding to ID 1 is the first data and the second data.

The destination address information corresponding to the first data is used to indicate the destination address or indicate the destination address to which the first data is to be sent. The destination address information may be, but is not limited to, a destination address identifier, a destination address index, and the like.

For example, the BSR includes an identifier and the total data size of all data that is in the terminal and that matches the identifier. As shown in FIG. 4, if the terminal has first data and second data, both the first data and second data correspond to identifier 1, and the total amount of data of the first data and second data is 2 M, the BSR includes identifier 1 and information used to indicate the total amount of data 2 M. It should be noted that the information used to indicate the total amount of data may be the identifier of the amount of data; and the data volume identifier may not accurately indicate 2 M, and may indicate a range of data volume, such as 2 M - 3 M.

As another example, the BSR includes the identifier, the destination address information corresponding to the first data, and the data size of all data that is in the terminal device and which corresponds to both the destination address information and the identifier. As shown in FIG. 5, all the first data, the second data and the third data correspond to the identifier 1, the destination address information corresponding to the first data is the destination address information 1, the destination address information corresponding to the second data is also the destination address information 1, and the information about the destination address corresponding to the third data is the destination address information 2. Thus, the BSR includes an identifier 1, destination address information 1, and information used to indicate the total amount of data 2 M of the first data and the second data.

Since the BSR is sent dynamically, in this implementation, the terminal device may dynamically send, to the network device, the identifier and the total amount of data of all data corresponding to the identifier, or may dynamically send, to the network device, the identifier, the destination address information corresponding to the first data , and/or the data size of all data that is in the terminal device and that matches both the destination address information and the identifier. Thus, the network device can dynamically perform an operation associated with it based on the ID and total data size of all data corresponding to the ID, or based on the destination address information corresponding to the first data and/or data size of all data that is in the terminal device and match both the destination address information and the identifier.

303: The network device determines the QoS parameter.

In particular, after receiving the identifier from the terminal device, the network device determines the QoS parameter. The QoS parameter corresponds to the identifier.

In particular, the network device stores the correspondence between the identifier and the QoS parameter. After receiving the identifier, the network device determines, based on the correspondence between the identifier and the QoS parameter, the QoS parameter corresponding to the identifier.

For example, the network device maintains the correspondence shown in Table 1 above. After receiving ID 1, the network device finds from the match shown in Table 1 the QoS parameter corresponding to ID 1. Thus, the QoS parameter determined by the network device is information 1 reliability information 1, delay information 1, communication range information 1, data rate information 1, and data priority information 1.

As another example, the network device maintains the mapping shown in Table 2 above. After receiving ID 1, the network device finds from the mapping shown in Table 2 the QoS parameter corresponding to ID 1. Thus, the network device determines that the terminal has at least one of QoS parameter data including reliability information 1, delay information 1, communication range information 1, data rate information 1 and data priority information 1, and QoS parameter data including reliability information 2, delay information 1, communication distance information 1, data rate information 1, and data priority information 1. In this case, the network device may not determine in detail whether the QoS parameter is reliability information 1, delay information 1, communication range information 1, data rate information 1, and data priority information of parameter 1, or whether the QoS parameter is reliability information 2, delay information 1, communication range information 1, data rate information 1 and data priority information 1, or the terminal has knowledge of both of the two above mentioned QoS parameters. However, in this case, the amount of overhead can be effectively reduced.

It should be understood that by implementing the method described in FIG. 3, the terminal device may send an identifier corresponding to the QoS parameter to the network device. Therefore, after receiving the ID, the network device can determine the corresponding QoS parameter based on the ID. Thus, by implementing the method described in FIG. 3, the terminal device can meet the quality of service requirements for the network device. In addition, the QoS parameter is specified using an identifier instead of being passed directly, and this reduces the amount of overhead.

In FIG. 6 is a schematic flowchart of another communication method according to an embodiment of the present application. As shown in FIG. 6, the communication method includes the following steps 601 to 605.

601: The terminal receives the first data and the QoS parameter corresponding to the first data.

In this embodiment of the present application, the QoS parameter includes at least one of reliability information, latency information, communication distance information, data rate information, and service type information.

The specific implementation and additional implementation 601 are the same as the specific implementation and additional implementation 301 in the above method embodiment. For details, refer to the relevant parts of the description of the above embodiment of the method. The details are again not described here.

602: The end device sends a BSR to the network device.

The BSR includes an identifier, and the identifier corresponds to the QoS parameter. Optionally, the BSR further includes the total data size of all data that is in the terminal and that matches the identifier, or the BSR further includes destination address information corresponding to the first data and/or the data size of all data that is in the terminal. device and which match both the destination address information and the identifier.

In particular, the end device stores the correspondence between the identifier and the QoS parameter. After receiving the QoS parameter, the terminal device obtains, based on the correspondence between the identifier and the QoS parameter, the identifier corresponding to the QoS parameter, adds the identifier corresponding to the QoS parameter to the BSR, and sends the BSR to the network device.

For the specific principle of obtaining an identifier corresponding to a QoS parameter by a terminal device, refer to the example corresponding to Table 1. Again, details are not described here.

Optionally, the identifier may be one of a logical channel group identifier, a QCI, and a flow identifier.

Regarding how to configure the correspondence in the terminal device between the identifier and the QoS parameter, one should refer to the relevant parts of the description of the above embodiment of the method. The details are again not described here.

For descriptions related to the BSR, refer in particular to the descriptions of the BSR in the above method embodiment. The details are again not described here.

603: The network device determines the QoS parameter.

The QoS parameter corresponds to the identifier.

Specifically, after receiving the BSR from the terminal device, the network device obtains the identifier from the BSR and determines, based on the correspondence between the identifier and the QoS parameter, the QoS parameter corresponding to the identifier.

For a specific implementation of the determination of the QoS parameter by the network device, see the respective descriptions 303 in the previous embodiment of the method. The details are again not described here.

604: The network device sends scheduling resource information to the end device.

In this embodiment of the present application, after determining the QoS parameter, the network device sends scheduling resource information to the terminal device. The scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

Optionally, the network device may allocate a scheduling resource based on the QoS parameter determined in step 603. Optionally, the network device maintains a mapping between the subcarrier spacing and/or transmission timeslot and the identifier, and the subcarrier spacing and/or transmission timeslot of the scheduling resource allocated by the network device. device that/which matches/corresponds to the identifier accepted by the network device. For example, the ID in the BSR received by the network device is ID 1, and ID 1 corresponds to the subcarrier spacing and/or transmission time interval of the scheduling resource allocated by the network device.

605: The terminal transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, the data corresponding to the identifier.

In the present embodiment of the present application, after receiving the scheduling resource information sent by the network device, the terminal transmits, on the side link, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier. The identifier corresponds to the subcarrier spacing and/or transmission time interval. The data corresponding to the identifier is the data corresponding to the QoS parameter that corresponds to the identifier.

In this embodiment of the present application, the terminal maintains a correspondence between the subcarrier spacing and/or transmission time interval and the identifier. After receiving the scheduling resource information sent by the network device, the terminal device may receive the subcarrier spacing and/or transmission time interval of the scheduling resource corresponding to the scheduling resource information and obtain, based on the correspondence between the subcarrier spacing and/or transmission time interval and the identifier, an identifier corresponding to the subcarrier spacing and/or transmission time interval. The terminal transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, the data corresponding to the identifier.

The correspondence between the subcarrier spacing and/or transmission time interval and the identifier may include many cases. The match can be one-to-one, one-to-many, many-to-one, or many-to-many. The present application is not limited to this.

It should be noted that data corresponding to a plurality of identifiers can be loaded into a scheduling resource. This is not limited in the present application as long as the subcarrier spacing and/or transmission time interval of the scheduling resource supports/supports data corresponding to a plurality of identifiers. In addition, since the size of the scheduling resource may be variable, and data corresponding to different identifiers may have certain priorities during data encapsulation, the number of QoS parameters whose data is transferred on the scheduling resource and the amount of data transferred are not limited in the present application.

For example, the terminal stores the correspondence shown in Table 3 below. detects, based on the match in Table 3 below, that subcarrier spacing 1 and/or transmission time slot 1 match/match ID 1. The terminal transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the one.

Table 3

Identifier Subcarrier spacing and/or transmission time interval ID 1 1 subcarrier spacing and/or 1 transmission time slot ID 2 2 subcarrier spacing and/or 2 transmission timeslot ID 3 1 subcarrier spacing and/or 3 transmission timeslot

Optionally, as shown in Table 4 below, one identifier may correspond to at least one subcarrier spacing and/or at least one transmission time interval. For example, an identifier of 1 corresponds to both a 1 subcarrier spacing and/or a 1 transmission timeslot and a 2 subcarrier spacing and/or a 1 transmission timeslot. The data corresponding to ID 1 may be loaded into a 1 subcarrier diversity scheduling resource and/or transmission time slot 1 or may be loaded into a 2 subcarrier diversity scheduling resource and/or transmission time slot 1.

Table 4

Identifier Subcarrier spacing and/or transmission time interval ID 1 1 subcarrier spacing and/or 1 transmission time slot 2 subcarrier spacing and/or 1 transmission time slot ID 2 2 subcarrier spacing and/or 2 transmission timeslot ID 3 3 subcarrier spacing and/or 3 transmission timeslot

Optionally, the network device may send a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier. Accordingly, the terminal may receive the second message. After receiving the second message sent by the network device, the terminal device may store the mapping included in the second message between the subcarrier spacing and/or transmission time interval and the identifier. In other words, in this implementation, the correspondence stored in the tag between the subcarrier spacing and/or transmission time interval and the identifier is configured by the network device.

If necessary, the correspondence stored in the terminal device between the subcarrier spacing and/or transmission time interval and the identifier can be configured in advance. For example, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the subcarrier spacing and/or transmission time interval and the identifier to the terminal prior to delivery of the terminal. Alternatively, when a terminal device accesses a network, the network device may pre-configure a mapping between subcarrier spacing and/or transmission time interval and an identifier in the terminal device.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is preconfigured for the terminal; and after the tag receives a second message that is sent by the network device and which includes the mapping between the subcarrier spacing and/or transmission timeslot and the identifier, the tag replaces the preconfigured mapping between the subcarrier spacing and/or transmission timeslot and the identifier to the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier. In other words, upon receiving the second message sent by the network device, the terminal may update the pre-configured mapping between the subcarrier spacing and/or transmission time interval and the identifier with the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier may be implicit or explicit.

For example, the match is implicit. The identifier may have a specific sequence, and the sequence may be specified in the protocol. In this case, the second message may not include the identifier. For example, the identifier is assumed to be a logical channel identifier. The first message includes {subcarrier slot 1, subcarrier slot 2}, {subcarrier slot 2, subcarrier slot 3}, and {subcarrier slot 3}. The protocol stipulates that the logical channel identifiers are arranged in ascending order, so that the logical channel identifier 1 is the logical channel identifier 3 respectively and sequentially correspond to the above elements.

As another example, the match in the second message is explicit; and the identifier is assumed to be a logical channel identifier. The first message includes {subcarrier slot 1, subcarrier slot 2, logical channel ID 1}, {subcarrier slot 2, subcarrier slot 3, logical channel ID 2}, and {subcarrier slot 3, logical channel ID 3}. At {Spacing 1 subcarrier, spacing 2 subcarriers, logical channel ID 1}, the logical channel ID 1 corresponds to a subcarrier interval of 1 and a subcarrier interval of 2, and it indicates that the data corresponding to the ID is allowed to load a resource whose subcarrier spacing is 1 or 2. The description of the other information included in the second message is the same as the description of {subcarrier spacing 1, subcarrier spacing 2, logical channel identifier 1}.

The subcarrier spacing is information used to indicate or refer to a subcarrier spacing, and may be, but is not limited to, an identifier, an index, or other information that indicates a subcarrier spacing.

A transmission time slot is information used to indicate or point to a transmission time slot, and may be, but is not limited to, an identifier, index, or other information that indicates a transmission time slot. If necessary, the transmission time interval may be the transmission time of the shared sidelink.

It should be understood that by implementing the method described in FIG. 6, the tag may dynamically request a scheduling resource from the network device, and the network device may dynamically allocate the scheduling resource to the tag. After receiving the scheduling resource information, the terminal may transmit, using the scheduling resource corresponding to the scheduling resource information, the corresponding data.

In FIG. 7 is a schematic flowchart of another communication method according to an embodiment of the present application. As shown in FIG. 7, the communication method includes the following steps 701 to 704.

701: The terminal receives the first data and the QoS parameter corresponding to the first data.

In this embodiment of the present application, the QoS parameter includes at least one of reliability information, delay information, communication range information, data rate information, and service type information.

The specific implementation and additional implementation 701 are identical to the specific implementation and additional implementation 301 in the above method embodiment. For details, refer to the relevant parts of the description of the above embodiment of the method. The details are again not described here.

702: The terminal determines the identifier.

The identifier corresponds to the QoS setting. In particular, the terminal maintains a correspondence between the identifier and the QoS parameter. After receiving the QoS parameter, the terminal determines, based on the correspondence between the identifier and the QoS parameter, the identifier corresponding to the QoS parameter.

703: The network device sends scheduling resource information to the end device.

The network device may configure scheduling resource information. The scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the network device may configure an appropriate scheduling resource based on the QoS parameter.

704: The terminal transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, the data corresponding to the identifier.

In the present embodiment of the present application, after receiving the scheduling resource information sent by the network device, the terminal transmits, on the side link, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier. The identifier corresponds to the subcarrier spacing and/or transmission time interval. The data corresponding to the identifier is the data corresponding to the QoS parameter that corresponds to the identifier.

Optionally, steps 701 and 702 may be performed after the tag receives the scheduling resource information sent by the network device, or may be performed before the tag receives the scheduling resource information sent by the network device. This is not limited to this embodiment of the present application.

For example, the network device can configure the scheduling resource 1 corresponding to the QoS option 1 and the scheduling resource 2 corresponding to the QoS option 2, and then send the scheduling resource information corresponding to the scheduling resource to the terminal device. 1 and scheduling resource information corresponding to the scheduling resource 2. The terminal stores a correspondence between the subcarrier spacing and the identifier. The correspondence is that 1 subcarrier spacing corresponds to identifier 1 and 2 subcarrier spacing corresponds to identifier 2. If the subcarrier spacing of scheduling resource 1 is a 1 subcarrier spacing and the subcarrier spacing of scheduling resource 2 is a 2 subcarrier spacing, after the scheduling resource information corresponding to scheduling resource 1 and scheduling resource information corresponding to scheduling resource 2, if the ID determined based on the QoS parameter of the first data is ID 1, the terminal selects, from scheduling resource 1 and scheduling resource 2, the resource 1 scheduling to send data corresponding to ID 1.

For a description of the method for configuring the correspondence in the terminal between the subcarrier spacing and/or transmission time interval and the identifier, see the corresponding description with reference to FIG. 6. Details are not described here again.

It should be understood that by implementing the method described in FIG. 7, the terminal device does not dynamically contact the network device for the scheduling resource, and the network device can configure the resource set for the terminal device. Thus, the terminal can independently select an appropriate scheduling resource from a set of resources to transmit the corresponding data. The network device may statically or semi-statically configure a resource set, and the resource set may include, but is not limited to, a resource pool or a semi-statically scheduled resource. The resource set includes several time-frequency resources.

In FIG. 8 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 8, the communication method includes the following steps 801 to 804.

801: The terminal receives the first data and the QoS parameter corresponding to the first data.

In this embodiment of the present application, the QoS parameter includes at least one of reliability information, latency information, communication distance information, data rate information, and service type information.

Optionally, the QoS parameter further includes data priority information. In this implementation, the terminal may indicate to the network device at least two types of QoS parameters. Thus, it helps the network device to schedule, for the terminal device, resources that meet different quality of service requirements for sidelink data transmission.

The specific implementation and optional implementation 801 are the same as the specific implementation and optional implementation 301 in the above method embodiment. For details, refer to the relevant parts of the description of the above embodiment of the method. The details are again not described here.

802: The end device sends an SR to the network device using the SR resource.

Optionally, the SR corresponds to the identifier, and the identifier corresponds to the QoS parameter.

In particular, the terminal stores the correspondence between the identifier and the QoS parameter, and the correspondence between the SR resource and the identifier. After determining the QoS parameter, the terminal may determine, based on the correspondence between the identifier and the QoS parameter, the identifier corresponding to the QoS parameter.

For correspondence between the identifier and the QoS parameter, in the embodiment described in FIG. 8, reference should be made to a description of the correspondence between the identifier and the QoS parameter in the embodiment described with reference to FIG. 3. Details are not described here again.

For example, the terminal keeps the correspondence shown in the previous table 1 and the correspondence shown in the following table 5. If the QoS parameter is reliability information 1, delay information 1, communication range information 1, data rate information 1 and information 1 about data priority, after receiving the QoS parameter, the terminal device finds from the correspondence presented in table 1, the identifier 1 corresponding to the QoS parameter. After the tag finds ID 1, the tag finds from the match shown in Table 5 the SR resource 1 corresponding to ID 1 and sends the SR using SR resource 1.

Table 5

Identifier SR resource ID 1 Resource 1SR ID 2 Resource 2 SR ID 3 Resource 2 SR

Optionally, the identifier may be one of a logical channel group identifier, a QCI, and a flow identifier.

Optionally, the network device may send a first message to the terminal device, where the first message includes the correspondence between the identifier and the QoS parameter and the correspondence between the SR resource and the identifier. The end device may receive the first message sent by the network device. After receiving the first message sent by the network device, the terminal may store the mapping included in the first message between the identifier and the QoS parameter and the mapping included in the first message between the SR resource and the identifier. In other words, in this implementation, the mapping held in the tag between the ID and the QoS parameter and the mapping stored in the tag between the SR resource and the ID are configured by the network device.

Optionally, the first message may be an RRC signaling. The RRC signaling may be a system information block (SIB) or a dedicated RRC signaling. If necessary, the correspondence between the identifier and the QoS parameter and the correspondence between the SR resource and the identifier may be sent using other RRC signaling.

If necessary, the mapping, in the first message, between the identifier and the QoS parameter and the mapping, in the first message, between the SR resource and the identifier may be implicit or explicit.

For example, the correspondence, in the first message, between the identifier and the QoS parameter is implicit. The identifier may have a specific sequence, and the sequence may be specified in the protocol. In this case, the first message may not include an identifier. For example, the identifier is assumed to be a logical channel group identifier, and the QoS parameter includes delay information and data priority information. The first message includes {delay information 1, data priority information 1}, {delay information 2, data priority information 2} and {delay information 3, data priority information 3}. The protocol provides that the logical channel group identifiers are arranged in ascending order, so that the logical channel group identifier 1 is the logical channel group identifier 3, respectively, and sequentially correspond to the above elements.

As another example, the correspondence, in the first message, between the identifier and the SR resource is implicit. The identifier may have a specific sequence, and the sequence may be specified in the protocol. In this case, the first message may not include the identifier. For example, the identifier is assumed to be a logical channel group identifier. The first message includes {SR resource 1}, {SR resource 2}, and {SR resource 3}. The protocol provides that the logical channel group IDs are arranged in ascending order, so that the logical channel group ID 1 is the logical channel group ID 3 respectively and sequentially correspond to the above elements.

As another example, the correspondence, in the first message, between the identifier and the QoS parameter is explicit; and the identifier is assumed to be a logical channel group identifier and the QoS parameter includes delay information and data priority information. The first message includes {delay information 1, data priority information 1, logical channel group identifier 1}, {delay information 2, data priority information 2, logical channel group identifier 2} and {delay information 3, logical channel group 3 about data priority, logical channel group identifier 3}. In {delay information 1, data priority information 1, logical channel group ID 1}, the logical channel group ID 1 corresponds to delay information 1 and data priority information 1. In {delay information 2, data priority information 2, logical channel group ID 2}, the logical channel group ID 2 corresponds to delay information 2 and data priority information 2. In {delay information 3, data priority information 3, logical channel group ID 3}, the logical channel group ID 3 corresponds to delay information 3 and data priority information 3.

As another example, the correspondence, in the first message, between the identifier and the SR resource is explicit; and the identifier is assumed to be a logical channel group identifier. The first message includes {SR resource 1, logical channel group identifier 1}, {SR resource 2, logical channel group identifier 2}, and {SR resource 3, logical channel group identifier 3}. In {SR resource 1, logical channel group ID 1}, logical channel group ID 1 corresponds to SR resource 1. In {SR resource 2, logical channel group ID 2}, logical channel group ID 2 corresponds to SR Resource 2. In {SR resource 3, logical channel group ID 3}, logical channel group ID 3 corresponds to SR resource 3.

If necessary, the mapping stored in the tag between the ID and the QoS parameter and the mapping stored in the tag between the SR resource and the ID can be configured in advance. For example, a mapping between an identifier and a QoS parameter, and a mapping between an SR and an identifier are specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the ID and the QoS parameter and the mapping between the SR and the ID in the tag prior to delivery of the tag. Alternatively, when a terminal device accesses a network, the network device may pre-configure the mapping between the identifier and the QoS parameter and the mapping between the SR resource and the identifier in the terminal device.

If necessary, the correspondence between the identifier and the QoS parameter and the correspondence between the SR resource and the identifier are preconfigured for the terminal device; and after the terminal device receives the first message that is sent by the network device and which includes the mapping between the identifier and the QoS parameter and the mapping between the SR resource and the identifier, the terminal replaces the preconfigured mapping between the identifier and the QoS parameter and the preconfigured mapping between the SR resource and the identifier against the correspondence included in the first message between the identifier and the QoS parameter and the correspondence included in the first message between the SR resource and the identifier. In other words, after receiving the first message sent by the network device, the terminal device can update the preconfigured mapping between the identifier and the QoS parameter and the preconfigured mapping between the SR resource and the identifier with the mapping included in the first message between the identifier and the QoS parameter and the mapping included in the first message, between the SR resource and the identifier.

If necessary, the SR resource corresponds to the QoS parameter.

In particular, the terminal stores a mapping between the SR resource and the QoS parameter. After determining the QoS parameter, the terminal may determine, based on the mapping between the SR resource and the QoS parameter, the SR resource corresponding to the QoS parameter.

For example, the end device maintains the correspondence shown in Table 6 below. The QoS parameter is the delay information. SR resource 1 corresponds to delay information 1, and SR resource 2 corresponds to delay information 2 and delay information 3. Upon learning that the QoS parameter is delay information 1, the terminal finds from the correspondence shown in Table 6 an SR resource 1 corresponding to delay information 1 and sends the SR using the SR resource 1.

Table 6

SR resource QoS setting Resource 1SR Information 1 about delay Resource 2 SR Delay information 2, delay information 3

Optionally, the network device may send a first message to the terminal device, where the first message includes a mapping between the SR resource and the QoS parameter. The end device may receive the first message sent by the network device. After receiving the first message sent by the network device, the terminal device may retain the mapping included in the first message between the SR resource and the QoS parameter. In other words, in this implementation, the mapping stored in the tag between the SR resource and the QoS parameter is configured by the network device.

Optionally, the first message including the mapping between the SR resource and the QoS parameter may be an RRC signaling. The RRC signaling may be SIB or dedicated RRC signaling.

The correspondence, in the first message, between the SR resource and the QoS parameter may be implicit or explicit if necessary.

If necessary, the correspondence stored in the terminal device between the SR resource and the QoS parameter can be configured in advance. For example, the mapping between an SR resource and a QoS parameter is specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the SR resource and the QoS parameter in the tag before shipping the tag. Alternatively, when the terminal accesses the network, the network device may pre-configure the mapping between the SR resource and the QoS parameter in the terminal.

If necessary, the mapping between the SR resource and the QoS parameter is pre-configured for the end device; and after the tag receives the first message that is sent by the network device and which includes the mapping between the SR resource and the QoS parameter, the tag replaces the preconfigured mapping between the SR resource and the QoS parameter with the mapping included in the first message between the resource SR and QoS parameter. In other words, after receiving the first message sent by the network device, the terminal device may update the pre-configured mapping between the SR resource and the QoS parameter with the mapping included in the first message between the SR resource and the QoS parameter.

Optionally, the SR resource used by the terminal to send the SR is the SR resource that is in the set of SR resources corresponding to the identifier and which corresponds to the data size of the first data. After detecting the SR on the SR resource, the network device determines the amount of data, where the amount of data corresponds to the SR resource. In this implementation, the tag may provide a data volume of the first data to the network device.

If necessary, the data amount of the first data may include, but is not limited to, the data amount of the buffer corresponding to the first data.

In other words, in this implementation, one identifier may correspond to multiple SRs. For example, ID 1 corresponds to SR resource 1 and SR resource 2. In this implementation, the terminal device and the network device have a correspondence between the amount of data and the resource SR.

For example, as shown in Table 7 below, a QoS parameter corresponds to an identifier, and one identifier may correspond to multiple SRs. As shown in Table 8 below, the amount of data corresponds to the resource SR. If the QoS parameter corresponding to the first data is delay information 1, the terminal determines, based on the correspondence in Table 7 below, that delay information 1 corresponds to identifier 1, and determines that identifier 1 corresponds to SR resource 1 and SR resource 2 . If the data size of the first data is greater than 2 M, the terminal determines from the SR resource 1 and the SR resource 2 based on the correspondence in Table 8 below that the SR resource 1 corresponds to a data size of more than 2 Mbytes. Thus, the terminal sends an SR using SR resource 1. Accordingly, after detecting the SR on the SR resource 1, the network device determines, based on the correspondence between the data amount and the SR resource, that the data amount corresponding to the SR resource 1 is greater than 2 M.

Table 7

QoS setting Identifier SR resource Information 1 about delay ID 1 Resource 1 SR, Resource 2 SR Delay information 2, delay information 3 ID 2 Resource 3 SR Delay information 4, delay information 5 ID 3 Resource 4 SR

Table 8

SR resource Data volume Resource 1SR More than 2 M Resource 2 SR Less than 2M Resource 3 SR More than 2 M Resource 4 SR Less than 2M

Optionally, the SR resource used by the terminal to send the SR is the SR resource that is in the set of SR resources corresponding to the QoS parameter and which corresponds to the data amount of the first data. After detecting the SR on the SR resource, the network device determines the amount of data, where the amount of data corresponds to the SR resource. In this implementation, the tag may provide a data volume of the first data to the network device.

For example, as shown in Table 9 below, one QoS parameter may correspond to multiple SRs. If the QoS parameter corresponding to the first data is delay information 1, the terminal determines based on the correspondence in Table 9 below that delay information 1 corresponds to SR resource 1 and SR resource 2. If the data amount of the first data is larger than 2 M, the terminal determines from the 1 SR resource and the 2 SR resource based on the correspondence in Table 10 below that the 1 SR resource corresponds to a data amount greater than 2 M. Thus, the terminal sends an SR using resource 1 SR. Accordingly, after detecting the SR on the SR resource 1, the network device determines, based on the correspondence between the data amount and the SR resource, that the data amount corresponding to the SR resource 1 is greater than 2 M.

Table 9

SR resource QoS setting Resource 1 SR,
resource 2 SR Information 1 about delay Resource 3 SR Delay information 2, delay information 3

Table 10

SR resource Data volume Resource 1SR More than 2 M Resource 2 SR Less than 2M Resource 3 SR More than 2 M

If necessary, the network device may send a third message to the terminal device, where the third message includes a correspondence between the amount of data and the resource SR. The match can be implicit or explicit. The terminal device may receive the third message sent by the network device. After receiving the third message sent by the network device, the terminal device may retain the mapping included in the third message between the amount of data and the SR resource. In other words, in this implementation, the correspondence stored in the tag between the amount of data and the resource SR is configured by the network device.

If necessary, the correspondence stored in the terminal device between the amount of data and the resource SR can be configured in advance. For example, the correspondence between the amount of data and the resource SR is specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the amount of data and the SR resource in the tag prior to delivery of the tag. Alternatively, when the terminal device accesses the network, the network device may pre-configure the mapping between the amount of data and the SR resource in the terminal device.

If necessary, the correspondence between the amount of data and the SR resource is pre-configured for the terminal device; and after the terminal device receives the third message that is sent by the network device and which includes the correspondence between the amount of data and the SR resource, the terminal device replaces the preconfigured correspondence between the amount of data and the SR resource with the correspondence included in the third message between the amount data and resource SR. In other words, after receiving the third message sent by the network device, the terminal device may update the pre-configured mapping between the amount of data and the SR resource to the correspondence included in the third message between the amount of data and the SR resource.

If necessary, the network device may send a fourth message to the terminal device, where the fourth message includes the correspondence between the amount of data and the pilot sequence. The match can be implicit or explicit. The terminal device may receive the fourth message sent by the network device. After receiving the fourth message sent by the network device, the terminal may store the correspondence included in the fourth message between the amount of data and the pilot sequence. In other words, in this implementation, the correspondence stored in the tag between the amount of data and the pilot sequence is configured by the network device.

If necessary, the correspondence stored in the terminal device between the amount of data and the pilot sequence can be configured in advance. For example, the correspondence between the amount of data and the pilot sequence is specified in the protocol. Alternatively, the device vendor may pre-configure the correspondence between the amount of data and the pilot sequence in the tag prior to delivery of the tag. Alternatively, when the terminal accesses the network, the network device may pre-configure the correspondence between the amount of data and the pilot sequence in the terminal.

If necessary, the correspondence between the amount of data and the pilot sequence is pre-configured for the terminal device; and upon receiving a fourth message sent by the network device that includes a data volume-to-pilot mapping, the terminal replaces the preconfigured data-to-pilot mapping with the data-to-pilot mapping included in the fourth message. In other words, after receiving the fourth message sent by the network device, the terminal device may update the preconfigured correspondence between the amount of data and the pilot sequence to the correspondence included in the fourth message between the amount of data and the pilot sequence.

In this case, the terminal may send different pilot sequences on the same SR resource to distinguish between data amounts. The network device determines the amount of data by detecting the corresponding SR resource and detecting the pilot sequence.

For example, the end device maintains the mapping shown in Table 11 below. The QoS parameter is the delay information. SR resource 1 corresponds to data volume 1 and pilot sequence 1, and SR resource 1 corresponds to data volume 2 and pilot sequence 2.

Table 11

SR resource Data volume Pilot sequence Resource 1SR Data volume 1 Pilot sequence 1 Resource 1SR Data volume 2 Pilot sequence 2

803 The network device discovers the SR on the SR resource.

Optionally, the network device further needs to detect a pilot sequence on the SR resource and determine an appropriate amount of data based on the detected pilot sequence.

804: The network device determines the QoS parameter.

Optionally, the QoS parameter corresponds to the identifier, and the identifier corresponds to the SR resource.

The network device stores the correspondence between the identifier and the QoS parameter, and the correspondence between the SR resource and the identifier. After discovering the SR on the SR resource, the network device determines, based on the correspondence between the SR resource and the identifier, an identifier corresponding to the SR resource, and then determines, based on the correspondence between the identifier and the QoS parameter, the QoS parameter corresponding to the identifier.

For example, the network device maintains the mapping shown in Table 1 above and the mapping shown in Table 3. After finding the SR on SR resource 1, the network device detects from the mapping shown in Table 3 that SR resource 1 corresponds to ID 1. Network device detects from the correspondence shown in Table 1 that the identifier 1 corresponds to reliability information 1, delay information 1, communication distance information 1, data rate information 1, and data priority information 1. Thus, the QoS parameter determined by the network device is reliability information 1, delay information 1, communication distance information 1, data rate information 1, and data priority information 1.

Alternatively, if necessary, there is a correspondence between the SR resource and the QoS parameter, and after detecting the SR on the SR resource, the network device determines, based on the correspondence between the SR resource and the QoS parameter, the QoS parameter corresponding to the identifier.

It should be understood that by implementing the method described in FIG. 8, the terminal may determine, based on the QoS parameter, the SR resource to send the SR, and send the SR on the determined SR resource. Therefore, after discovering the SR on the SR resource, the network device can determine the QoS parameter based on the SR resource. Thus, by implementing the method described in FIG. 8, the terminal device can fulfill the quality of service requirements for the network device. In addition, the QoS parameter is indicated using the SR resource instead of direct transmission, and this can reduce the amount of overhead.

In FIG. 9 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 9, the communication method includes the following steps 901 to 906.

901: The terminal receives the first data and the QoS parameter corresponding to the first data.

902: The end device sends an SR to the network device using the SR resource.

903 The network device discovers the SR on the SR resource.

904 The network device determines the QoS parameter.

The specific implementation and optional implementation of parts 901 to 904 are the same as the specific implementation and optional implementation of steps 801 to 804. Again, details are not described here.

905: The network device sends scheduling resource information to the end device.

In this embodiment of the present application, after determining the QoS parameter, the network device sends scheduling resource information to the terminal device. The scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the network device may allocate a scheduling resource based on the determined QoS parameter. If necessary, the network device maintains a correspondence between the subcarrier spacing and/or transmission time interval and the identifier, and the identifier determined by the network device based on the QoS parameter corresponds to the subcarrier spacing and/or transmission time interval of the scheduling resource allocated by the network device.

906: The terminal transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

In the present embodiment of the present application, after receiving the scheduling resource information sent by the network device, the terminal transmits, on the side link, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier. The identifier corresponds to the subcarrier spacing and/or transmission time interval. The data corresponding to the identifier is the data corresponding to the QoS parameter that corresponds to the identifier.

In this embodiment of the present application, the terminal maintains a correspondence between the subcarrier spacing and/or transmission time interval and the identifier. After receiving the scheduling resource information sent by the network device, the terminal may receive the subcarrier spacing and/or transmission time interval of the scheduling resource corresponding to the scheduling resource information and obtain, based on the correspondence between the subcarrier spacing and/or transmission time interval and the identifier, an identifier corresponding to the subcarrier spacing and/or transmission time interval. The terminal transmits, on the sidelink, using the scheduling resource corresponding to the scheduling resource information, the data corresponding to the identifier.

For example, the terminal retains the correspondence shown in Table 3 above. based on the match in the above table 3, finds that subcarrier slot 1 and/or transmission time slot 1 match/corresponds to ID 1. one.

As another example, the terminal further stores the mapping shown in Table 4 above. One identifier may correspond to at least one subcarrier spacing and/or at least one transmission time interval.

Optionally, the network device may send a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier. Accordingly, the terminal may receive the second message. After receiving the second message sent by the network device, the terminal device may store the mapping included in the second message between the subcarrier spacing and/or transmission time interval and the identifier. In other words, in this implementation, the correspondence stored in the tag between the subcarrier spacing and/or transmission time interval and the identifier is configured by the network device.

If necessary, the correspondence stored in the terminal device between the subcarrier spacing and/or transmission time interval and the identifier can be configured in advance. For example, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is specified in the protocol. Alternatively, the device vendor may pre-configure the mapping between the subcarrier spacing and/or transmission time interval and the identifier to the terminal prior to delivery of the terminal. Alternatively, when a terminal device accesses a network, the network device may pre-configure a mapping between subcarrier spacing and/or transmission time interval and an identifier in the terminal device.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier is preconfigured for the terminal; and after the tag receives a second message that is sent by the network device and which includes the mapping between the subcarrier spacing and/or transmission timeslot and the identifier, the tag replaces the preconfigured mapping between the subcarrier spacing and/or transmission timeslot and the identifier to the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier. In other words, upon receiving the second message sent by the network device, the terminal may update the pre-configured mapping between the subcarrier spacing and/or transmission time interval and the identifier with the correspondence included in the second message between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the correspondence between the subcarrier spacing and/or transmission time interval and the identifier may be implicit or explicit. For specific descriptions, see the corresponding embodiment in FIG. 6. Details are not described here again.

It should be understood that by implementing the method described in FIG. 9, the network device may allocate a scheduling resource to the terminal device, and the terminal device may transmit the corresponding data using the corresponding scheduling resource.

In embodiments of the present invention, the device may be divided into functional modules based on the above example methods. For example, each functional module may be obtained by splitting based on each respective function, or two or more functions may be integrated into one module. An integrated module may be implemented in hardware or may be implemented in a software function module. It should be noted that in the embodiments of the present invention, the division into modules is an example and is simply a division of logical functions. During actual implementation, another partitioning method may be used.

In FIG. 10 shows a terminal device according to an embodiment of the present invention. The terminal device includes a processing module 1001 and a communication module 1002.

The processing unit 1001 is configured to obtain the first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, delay information, communication distance information, data rate information and information about the type of service. The communication module 1002 is configured to send the identifier to the network device, where the identifier corresponds to the QoS parameter.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module 1002 is further configured to receive a first message sent by the network device, where the first message includes a match between the identifier and the QoS parameter.

Optionally, the method for sending, by the communication module 1002, an identifier to the network device is, in particular: sending a buffer status report (BSR) to the network device, where the BSR includes the identifier, and the BSR further includes a data amount of all data that located in the terminal device and which correspond to the identifier, or the BSR further includes information about the destination address corresponding to the first data and/or the data volume of all data that is located in the terminal device and which corresponds to the information about the destination address and the identifier.

If necessary, the communication module 1002 is further configured to receive scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and the communication module 1002 is further configured to transmit, on the sidelink using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

If necessary, the communication module 1002 is further configured to receive a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

In FIG. 11 shows a terminal device according to an embodiment of the present invention. The terminal device includes a processing module 1101 and a communication module 1102.

The processing unit 1101 is configured to obtain the first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, delay information, communication distance information, data rate information and information about the type of service. The communication module 1102 is configured to send the SR to the network device using the SR resource, where the SR resource corresponds to an identifier and the identifier corresponds to a QoS parameter.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module 1102 is further configured to receive a first message sent by the network device, where the first message includes a match between an identifier and a QoS parameter, and a match between an SR resource and an identifier.

If necessary, the communication module 1102 is further configured to receive scheduling resource information sent by the network device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and the communication module 1102 is further configured to transmit, on the sidelink using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier.

If necessary, the communication module 1102 is further configured to receive a second message sent by the network device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

Optionally, the SR resource is an SR resource that is in the set of SR resources corresponding to the identifier and that corresponds to the data amount of the first data.

In FIG. 12 shows a network device according to an embodiment of the present invention. The network device includes a processing module 1201 and a communication module 1202.

The communication module 1202 is configured to receive the identifier from the tag. The processing unit 1201 is configured to determine a QoS parameter, where the QoS parameter corresponds to an identifier, and the QoS parameter includes at least one of reliability information, latency information, communication range information, data rate information, and type information. services.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module 1202 is further configured to send a first message to the terminal device, where the first message includes a correspondence between the identifier and the QoS parameter.

Optionally, the method for receiving, by the communication module 1202, an identifier from the terminal device is, in particular: receiving a buffer status report (BSR) from the terminal device, where the BSR includes the identifier, and the BSR further includes the amount of data of all data that located in the terminal device and which correspond to the identifier, or the BSR further includes information about the destination address corresponding to the first data and/or the data volume of all data that is located in the terminal device and which corresponds to the information about the destination address and the identifier.

If necessary, the communication module 1202 is further configured to send the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the communication module 1202 is further configured to send a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

In FIG. 13 shows a network device according to an embodiment of the present invention. The network device includes a processing module 1301 and a communication module 1302.

The communication module 1302 is configured to discover the SR on the SR resource. The processing unit 1301 is configured to determine a QoS parameter, where the QoS parameter corresponds to an identifier, the identifier corresponds to an SR resource, and the QoS parameter includes at least one of reliability information, latency information, communication range information, transmission rate information data and information about the type of service.

Optionally, the QoS parameter further includes data priority information.

If necessary, the communication module 1302 is further configured to send a first message to the tag, where the first message includes the mapping between the identifier and the QoS parameter and the mapping between the SR resource and the identifier.

If necessary, the communication module 1302 is further configured to send the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

If necessary, the communication module 1302 is further configured to send a second message to the terminal device, where the second message includes a correspondence between the subcarrier spacing and/or transmission time interval and the identifier.

If necessary, the processing module 1301 is further configured to determine the amount of data, where the amount of data corresponds to the resource SR.

In FIG. 14 is a schematic block diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 14, terminal device 1400 includes a processor 1401, a memory 1402, and a communication interface 1403. The processor 1401, the memory 1402 and the communication interface 1403 are connected to each other.

The processor 1401 may be a central processing unit (CPU), a general purpose processor, a coprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, transistorized logic device, hardware component, or any combination thereof. Alternatively, processor 1401 may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor.

Communication interface 1403 is configured to communicate with another network element (eg, a network device).

The processor 1401 calls the program code stored in the memory 1402 to perform the steps performed by the terminal device in the above method embodiments.

In FIG. 15 is a schematic block diagram of a network device according to an embodiment of the present application. As shown in FIG. 15, the network device 1500 includes a processor 1501, a memory 1502, and a communication interface 1503. The processor 1501, the memory 1502 and the communication interface 1503 are connected to each other.

The processor 1501 may be a central processing unit (CPU), a general purpose processor, a coprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array, FPGA) or other programmable logic device, transistorized logic device, hardware component, or any combination thereof. Alternatively, processor 1501 may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor.

Communication interface 1503 is configured to communicate with another network element (eg, a terminal).

The processor 1501 calls the program code stored in the memory 1502 to perform the steps performed by the network device in the above method embodiments.

Based on the same concept of the invention, the problem solving principle of each device presented in the embodiments of the present application is similar to the principle of the method embodiment of the present application. Therefore, to implement the device, you should refer to the implementation of the method. For brevity, the details are again not described here.

It should be understood that when the embodiments of the present application are applied to a tag chip, the tag chip implements the function of the tag in the above method embodiments. The terminal device chip sends the first information to another module (eg, RF module or antenna) in the terminal device or receives the second information from another module in the network device. The first information is sent to the network device using another module in the terminal device, and the second information is sent by the network device to the terminal device. When the embodiments of the present application are applied to a network device chip, the network device chip implements the network device function in the above method embodiments. The network device chip receives first information from another module (eg, RF module or antenna) in the network device or sends second information to another module in the network device. The first information is sent by the terminal device to the network device, and the second information is sent to the terminal device. The first information and the second information in this document are not a specific type of information, and are simply used to indicate the communication mode between the chip and another module.

All or some of the above embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the instructions of a computer program are downloaded and executed on a computer, procedures or functions in accordance with embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a specialized computer, a computer network, or other programmable device. The computer instructions may be stored on a computer-readable storage medium or may be transmitted via a computer-readable storage medium. Computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (for example, coaxial cable, optical fiber, or digital subscriber line (DSL). DSL)) or wirelessly (for example, using infrared waves, radio waves, or microwaves) in a manner A computer-readable storage medium can be any usable storage medium accessible to a computer, or storage device, such as a server or data center, integrating one or more media used The media used can be a magnetic storage medium (such as a floppy disk, hard disk or magnetic tape), an optical storage medium (such as a DVD), a semiconductor storage medium (such as a Solid State Disk (SSD)) or the like.

In the above embodiments, the description of each embodiment has appropriate emphasis. For the part that is not described in detail in the embodiment, one should refer to the corresponding descriptions in other embodiments.

Finally, it should be noted that the foregoing embodiments are only intended to describe the technical solutions of the present application, and not to limit the present application. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they may still make changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some or all of their specifications, without leaving beyond the technical solutions of the embodiments of the present application.

Claims (26)

1. A communication method used in a terminal device, the method comprising: obtaining the first data and a quality of service (QoS) parameter corresponding to the first data, the QoS parameter comprising at least one of reliability information, latency information, communication range information, data rate information, and service type information; and sending the identifier to the network device, and the identifier corresponds to the QoS parameter, in which sending an identifier to a network device contains: sending a buffer status report (BSR) to the network device, wherein the BSR contains an identifier, and the BSR further contains the total amount of data of all data that is in the terminal device and that matches the identifier, or the BSR additionally contains information about the destination address corresponding to the first data and /or the data volume of all data that is in the terminal device and that matches both the destination address information and the identifier. 2. The method of claim 1, wherein the QoS parameter further comprises data priority information. 3. The method according to claim 1 or 2, in which the method further comprises: receiving a first message sent by the network device, the first message containing a match between the identifier and the QoS parameter. 4. The method of claim 1, wherein the method further comprises: receiving scheduling resource information sent by the network device, wherein the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and sidelink transmission using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, the subcarrier spacing and/or transmission time interval corresponding/corresponding to the identifier. 5. Terminal device, characterized in that it contains: a processing module configured to obtain the first data and a quality of service (QoS) parameter corresponding to the first data, where the QoS parameter includes at least one of reliability information, delay information, communication distance information, data rate information and information about the type of service; and a communication module configured to send the identifier to the network device, where the identifier corresponds to the QoS parameter, in which the communication module is configured to send a buffer status report (BSR) to the network device, where the BSR contains an identifier, and the BSR further contains the total amount of data of all data that is in the terminal device and that matches the identifier, or the BSR further contains information about the destination address corresponding to the first data, and/or the data volume of all data that is in the terminal device and that corresponds to both the destination address information and the identifier. 6. The terminal device according to claim 5, in which the QoS parameter additionally contains information about the priority of the data. 7. The terminal device of claim 5 or 6, wherein the communication module is further configured to receive a first message sent by the network device, the first message including a mapping between the identifier and the QoS parameter. 8. The tag according to claim 5, wherein the communication module is further configured to receive scheduling resource information sent by the network device, wherein the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval; and the communication module is further configured to transmit on the sidelink, using the scheduling resource corresponding to the scheduling resource information, data corresponding to the identifier, where the subcarrier spacing and/or transmission time interval corresponds/corresponds to the identifier. 9. Network device, containing: a communication module configured to receive the identifier from the terminal device; and a processing module configured to determine the quality of service, the QoS parameter, where the QoS parameter corresponds to the identifier, and the QoS parameter contains at least one of reliability information, delay information, communication distance information, data rate information, and type information services, in which the communication module is configured to receive a buffer status report (BSR) from the terminal device, where the BSR contains an identifier, and the BSR additionally contains the amount of data of all data that is in the terminal device that matches the identifier, or the BSR additionally contains information about the address destination corresponding to the first data, and/or the data volume of all data that is in the terminal device and that corresponds to both the information about the destination address and the identifier. 10. The network device of claim 9, wherein the QoS parameter further includes data priority information. 11. The network device according to claim 9 or 10, wherein the communication module is further configured to send a first message to the terminal device, where the first message contains a correspondence between the identifier and the QoS parameter. 12. The network device of claim 9, wherein the communication module is further configured to send the scheduling resource information to the terminal device, where the scheduling resource corresponding to the scheduling resource information has a subcarrier spacing and/or a transmission time interval.

Images