CN111385891A

CN111385891A - Configuration method, equipment and system

Info

Publication number: CN111385891A
Application number: CN201811644891.9A
Authority: CN
Inventors: 徐海博; 肖潇; 王键
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-12-29
Filing date: 2018-12-29
Publication date: 2020-07-07
Anticipated expiration: 2038-12-29
Also published as: WO2020135625A1; CN111385891B

Abstract

The embodiment of the application provides a configuration method, a device and a system, which can be configured to be used for relevant configuration of an SR (scheduling request) used when the SR for the sidelink data transmission of the PC5 port is sent by a Uu port of an NR (noise reduction) system. The method comprises the following steps: the terminal equipment sends a first message to the network equipment, wherein the first message comprises a first identifier; the terminal device receives a second message from the network device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

Description

Configuration method, equipment and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a configuration method, device, and system.

Background

In a Long Term Evolution (LTE) system or a New Radio (NR) system, a communication interface between a terminal device and a base station is called a Uu port. A link on the Uu port where a terminal device transmits data to a base station is called an Uplink (UL), and a link where a terminal device receives data transmitted by a base station is called a Downlink (DL). Further, the terminal device and the communication interface between the terminal devices are referred to as PC5 ports. The link between the terminal device on the PC5 port and the terminal device for transmitting data is called Sidelink (SL). The PC5 port is generally used in a vehicle to outside communication (V2X), a device-to-device communication (D2D), and other scenarios where direct communication between devices is possible.

As shown in fig. 1a, for the communication over Uu port, for example, when the terminal device has uplink data to transmit but no uplink grant (UL grant) is available, the terminal device needs to trigger a Scheduling Request (SR) and request the uplink grant from the base station by transmitting the SR. After receiving the uplink grant, the terminal device 1 may send a Buffer Status Report (BSR) to the base station through the uplink grant, so that the base station further allocates an UL grant to the terminal device according to the UL BSR, so that the terminal device sends UL data on the corresponding UL grant.

As shown in fig. 1b, for communication of PC5 port, if the base station configures the terminal device 1 with a resource allocation manner based on base station scheduling, when the terminal device 1 has a sidelink data to be transmitted but has no available sidelink grant (SLgrant), the terminal device also needs to trigger SR and request uplink grant from the base station by transmitting SR. After receiving the uplink grant, the terminal device may send the SL BSR to the base station through the uplink grant, so that the base station further allocates the SL grant to the terminal device 1 according to the SLBSR, so that the terminal device 1 continues to send SL data on the corresponding SL grant.

As can be seen from the flow shown in fig. 1a and the flow shown in fig. 1b, whether uplink data transmission on the Uu port or sidelink data transmission on the PC5 port, an SR needs to be sent through the Uu port to request a corresponding link grant from the base station. The terminal device may send the SR through a dedicated SR resource on a Physical Uplink Control Channel (PUCCH) configured for the terminal device by the base station.

In the related art, there are SR-related configurations used when an SR for uplink data transmission of the Uu port is transmitted at the Uu port of the LTE system, and SR-related configurations used when an SR for sidelink data transmission of the PC5 port is transmitted at the Uu port, and SR-related configurations used when an SR for uplink data transmission of the Uu port is transmitted at the NR system, but there is no solution at present how to configure the SR-related configurations used when an SR for sidelink data transmission of the PC5 port is transmitted at the Uu port of the NR system.

Disclosure of Invention

The embodiment of the application provides a configuration method, a device and a system, which can be configured to be used for relevant configuration of an SR (scheduling request) used when the SR for the sidelink data transmission of the PC5 port is sent by a Uu port of an NR (noise reduction) system.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, a configuration method is provided, including: the terminal equipment sends a first message to the network equipment, wherein the first message comprises a first identifier; the terminal device receives a second message from the network device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier. Furthermore, if the logical channel associated with the second identifier triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device for the SR may be the SR configuration corresponding to the SR identifier mapped by the second identifier; the SR resource configuration used by the terminal device for the SR may be one or more SR resource configurations associated with the SR configuration. That is to say, the terminal device may determine, according to the second identifier and the SR identifier mapped by the second identifier, an SR configuration and an SR resource configuration used when sending an SR for sidelink data transmission of the PC5 port at the Uu port of the NR system, so that the SR may be sent at the Uu port of the NR system according to the determined SR configuration and SR resource configuration.

With reference to the first aspect, in one possible design, the first message further includes quality of service QoS information corresponding to the first identifier. The QoS information may be used to determine the scheduling request SR identity to which the second identity is mapped.

With reference to the first aspect or a possible design of the first aspect, in a possible design, if the first identifier and the second identifier have a mapping relationship, the second message further includes or indicates the mapping relationship between the first identifier and the second identifier. Furthermore, the terminal device can acquire the mapping relationship between the first identifier and the second identifier.

With reference to the first aspect or a possible design of the first aspect, in one possible design, the first message further includes destination information, wherein the first identifier is associated with the destination information. The destination information is used for the network device to distinguish a destination to which the first identifier belongs, so that one or more of the SR configuration and the SR resource configuration related to the SR configuration are configured for the terminal device according to the destination information and the first identifier.

With reference to the first aspect or a possible design of the first aspect, in one possible design, the second message further includes the destination information, wherein the second identifier is associated with the destination information, and the SR identifier mapped by the second identifier is associated with the destination information. The destination information is used for the terminal device to distinguish a destination to which the SR identifier mapped by the second identifier belongs, so as to determine, according to the destination information and the SR identifier mapped by the second identifier, an SR configuration used for SR transmission and one or more SR resource configurations associated with the SR configuration.

With reference to the first aspect or a possible design of the first aspect, in one possible design, the first message further includes source information and destination information, where the first identifier is associated with the source information and the first identifier is associated with the destination information. The source information and the destination information are used for the network device to distinguish the combination of the source and the destination to which the first identifier belongs, so that one or more of the SR configuration and the SR resource configuration related to the SR configuration are configured for the terminal device according to the combination of the source information and the destination information and the first identifier.

With reference to the first aspect or a possible design of the first aspect, in one possible design, the second message further includes the source information and the destination information, where the second identifier is associated with the source information and the second identifier is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information. The source information and the destination information are used for the terminal device to distinguish a combination of a source and a destination to which the SR identifier mapped by the second identifier belongs, so that the SR configuration for SR transmission and one or more SR resource configurations associated with the SR configuration are determined according to the combination of the source information and the destination information and the SR identifier mapped by the second identifier.

With reference to the first aspect or the possible design of the first aspect, in a possible design, the second message further includes one or more of an SR configuration corresponding to the SR identification and an SR resource configuration associated with the SR configuration; the SR configuration comprises the SR identifier, an SR prohibition counter and the maximum SR transmission times; the SR resource configuration includes an SR resource identifier, a period and an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify a configuration of a scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

For example, if the network device has previously sent the SR configuration corresponding to the SR identifier mapped by the second identifier included in the second message to the terminal device, but needs to associate a new SR resource configuration with the SR configuration corresponding to the SR identifier, the second message also needs to include one or more SR resource configurations associated with the SR configuration corresponding to the SR identifier.

Or, for example, if the network device does not configure, for the terminal device, the SR configuration corresponding to the SR identifier mapped by the second identifier included in the second message and the SR resource configuration associated with the SR configuration before that, the second message further needs to include the SR configuration corresponding to the SR identifier and one or more SR resource configurations associated with the SR configuration.

In combination with the first aspect or a possible design of the first aspect, in one possible design, the first identifier is an identifier of a QoS flow.

In this case, the second identifier is an identifier of a logical channel group to which a logical channel of a sidelink radio bearer mapped by the QoS flow belongs; or, the second identifier is an identifier of the QoS flow; or, the second identifier is an identifier of a sidelink radio bearer to which the QoS flow is mapped; alternatively, the second identifier is an identifier of a logical channel of a sidelink radio bearer to which the QoS flow is mapped.

In this case, if a logical channel of a sidelink radio bearer mapped by the QoS flow triggers a sidelink buffer status report SL BSR and triggers a first SR, the terminal device configures, for the first SR, a first SR configuration corresponding to the SR identifier mapped by the second identifier; the terminal device is used for configuring the first SR resource configuration of the first SR into one or more SR resource configurations related to the first SR configuration.

In combination with the first aspect or a possible design of the first aspect, in one possible design, the first identifier is a QoS index used to indicate QoS information.

In this case, the second identifier is an identifier of a logical channel group to which a logical channel of the sidelink radio bearer mapped by the QoS index belongs; or, the second identifier is the QoS index for indicating the QoS information corresponding to the first identifier; or, the second identifier is an identifier of a sidelink radio bearer mapped by the QoS index; alternatively, the second identifier is an identifier of a logical channel of a sidelink radio bearer to which the QoS index is mapped.

In this case, if the logical channel of the sidelink radio bearer mapped by the QoS index triggers a sidelink buffer status report SL BSR and triggers a second SR, the terminal device configures, for the second SR, a second SR configuration corresponding to the SR identifier mapped by the second identifier; the terminal device is configured to configure the second SR resource configuration for the second SR as one or more SR resource configurations associated with the second SR configuration.

With reference to the first aspect or a possible design of the first aspect, in a possible design, the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel of the sidelink radio bearer, and the second identifier is the same as the first identifier.

In this case, if the logical channel of the sidelink radio bearer triggers the SL BSR and triggers the third SR, the terminal device configures, as the SR configuration corresponding to the SR identifier mapped by the second identifier, the third SR configuration used by the third SR; the terminal device uses the SR resource configuration of the third SR as one or more SR resource configurations associated with the third SR configuration.

In a second aspect, a configuration method is provided, including: the network equipment receives a first message from the terminal equipment, wherein the first message comprises a first identifier; the network device sends a second message to the terminal device, where the second message includes a second identifier and a SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier. The technical effects of the second aspect can refer to the first aspect, and are not described herein again.

With reference to the second aspect, in one possible design, the first message further includes quality of service QoS information corresponding to the first identifier. The QoS information may be used to determine the scheduling request SR identity to which the second identity is mapped.

With reference to the second aspect or a possible design of the second aspect, in a possible design, if the first identifier and the second identifier have a mapping relationship, the second message further includes or indicates the mapping relationship between the first identifier and the second identifier. Furthermore, the terminal device can acquire the mapping relationship between the first identifier and the second identifier.

In combination with the second aspect or possible designs of the second aspect, in one possible design, the first message further includes destination information, wherein the first identifier is associated with the destination information. The destination information is used for the network device to distinguish a destination to which the first identifier belongs, so that one or more of the SR configuration and the SR resource configuration related to the SR configuration are configured for the terminal device according to the destination information and the first identifier.

In combination with the second aspect or a possible design of the second aspect, in one possible design, the second message further includes the destination information, wherein the second identifier is associated with the destination information, and the SR identifier mapped by the second identifier is associated with the destination information. The destination information is used for the terminal device to distinguish a destination to which the SR identifier mapped by the second identifier belongs, so as to determine, according to the destination information and the SR identifier mapped by the second identifier, an SR configuration used for SR transmission and one or more SR resource configurations associated with the SR configuration.

In combination with the second aspect or a possible design of the second aspect, in one possible design, the first message further includes source information and destination information, wherein the first identifier is associated with the source information and the first identifier is associated with the destination information. The source information and the destination information are used for the network device to distinguish the combination of the source and the destination to which the first identifier belongs, so that one or more of the SR configuration and the SR resource configuration related to the SR configuration are configured for the terminal device according to the combination of the source information and the destination information and the first identifier.

In combination with the second aspect or a possible design of the second aspect, in one possible design, the second message further includes the source information and the destination information, wherein the second identifier is associated with the source information and the second identifier is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information. The source information and the destination information are used for the terminal device to distinguish a combination of a source and a destination to which the SR identifier mapped by the second identifier belongs, so that the SR configuration for SR transmission and one or more SR resource configurations associated with the SR configuration are determined according to the combination of the source information and the destination information and the SR identifier mapped by the second identifier.

With reference to the second aspect or a possible design of the second aspect, in a possible design, the second message further includes one or more of an SR configuration corresponding to the SR identification and an SR resource configuration associated with the SR configuration; the SR configuration comprises the SR identifier, an SR prohibition counter and the maximum SR transmission times; the SR resource configuration includes an SR resource identifier, a period and an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify a configuration of a scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

In combination with the second aspect or a possible design of the second aspect, in one possible design, the first identifier is an identifier of a QoS flow.

In combination with the second aspect or a possible design of the second aspect, in one possible design, the first identifier is a QoS index used to indicate QoS information.

In a possible design, with reference to the first aspect or the second aspect, the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel of the sidelink radio bearer, and the second identifier is the same as the first identifier.

In a third aspect, a configuration method is provided, including: the terminal equipment sends a first message to the network equipment, wherein the first message is used for requesting side link resources; the terminal device receives a second message from the network device, where the second message includes a scheduling request SR identifier, the SR identifier corresponds to one SR configuration, and the SR configuration is associated with one or more SR resource configurations. The SR identifier is an SR identifier common to all V2X services transmitted through the PC5 interface, or the SR identifier is an SR identifier common to all V2X services or service packets transmitted through the PC5 interface and adopting a resource allocation method based on network device scheduling. Furthermore, if the terminal device triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device for the SR may be the SR configuration corresponding to the SR identifier; the SR resource configuration used by the terminal device for the SR may be one or more SR resource configurations associated with the SR configuration. That is, the terminal device may determine, according to the SR flag, an SR configuration and an SR resource configuration used when transmitting an SR for sidelink data transmission of the PC5 port at the Uu port of the NR system, so that the SR may be transmitted at the Uu port of the NR system according to the determined SR configuration and SR resource configuration.

In a fourth aspect, a configuration method is provided, including: the network equipment receives a first message from the terminal equipment, wherein the first message is used for requesting the side link resource; the network device sends a second message to the terminal device, where the second message includes a scheduling request SR identifier, the SR identifier corresponds to one SR configuration, and the SR configuration is associated with one or more SR resource configurations. The SR identifier is an SR identifier common to all V2X services transmitted through the PC5 interface, or the SR identifier is an SR identifier common to all V2X services or service packets transmitted through the PC5 interface and adopting a resource allocation method based on network device scheduling. For technical effects of the fourth aspect, reference may be made to the third aspect, which is not described herein again.

In a fifth aspect, a terminal device is provided, where the terminal device includes a receiving module and a sending module, and the sending module is configured to send a first message to a network device, where the first message includes a first identifier; a receiving module, configured to receive a second message from the network device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier. Furthermore, if the logical channel associated with the second identifier triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device for the SR may be the SR configuration corresponding to the SR identifier mapped by the second identifier; the SR resource configuration used by the terminal device for the SR may be one or more SR resource configurations associated with the SR configuration.

With reference to the fifth aspect, in one possible design, the first message further includes quality of service QoS information corresponding to the first identifier.

With reference to the fifth aspect or the possible design of the fifth aspect, in a possible design, if the first identifier and the second identifier have a mapping relationship, the second message further includes or indicates the mapping relationship between the first identifier and the second identifier.

In combination with the fifth aspect or possible designs of the fifth aspect, in one possible design, the first message further includes destination information, wherein the first identifier is associated with the destination information.

With reference to the fifth aspect or possible designs of the fifth aspect, in one possible design, the second message further includes the destination information, wherein the second identifier is associated with the destination information, and the SR identifier mapped by the second identifier is associated with the destination information.

In combination with the fifth aspect or possible designs of the fifth aspect, in one possible design, the first message further includes source information and destination information, wherein the first identifier is associated with the source information and the first identifier is associated with the destination information.

In combination with the fifth aspect or possible designs of the fifth aspect, in one possible design, the second message further includes the source information and the destination information, wherein the second identifier is associated with the source information and the second identifier is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information.

With reference to the fifth aspect or the possible design of the fifth aspect, in a possible design, the second message further includes one or more of an SR configuration corresponding to the SR identification and an SR resource configuration associated with the SR configuration; the SR configuration comprises the SR identifier, an SR prohibition counter and the maximum SR transmission times; the SR resource configuration includes an SR resource identifier, a period and an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify a configuration of a scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

In combination with the fifth aspect or possible designs of the fifth aspect, in one possible design, the first identifier is an identifier of a QoS flow.

In combination with the fifth aspect or possible designs of the fifth aspect, in one possible design, the first identifier is a QoS index used to indicate QoS information.

With reference to the fifth aspect or a possible design of the fifth aspect, in a possible design, the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel of the sidelink radio bearer, and the second identifier is the same as the first identifier.

For technical effects of any one of the possible designs of the fifth aspect or the fifth aspect, reference may be made to the technical effects of any one of the possible designs of the first aspect or the first aspect, which are not described herein again.

In a sixth aspect, a network device is provided, which includes a receiving module and a sending module; a receiving module, configured to receive a first message from a terminal device, where the first message includes a first identifier; a sending module, configured to send a second message to the terminal device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

With reference to the sixth aspect, in one possible design, the first message further includes quality of service QoS information corresponding to the first identifier.

With reference to the sixth aspect or the possible design of the sixth aspect, in a possible design, if the first identifier and the second identifier have a mapping relationship, the second message further includes or indicates the mapping relationship between the first identifier and the second identifier.

With reference to the sixth aspect or the possible designs of the sixth aspect, in one possible design, the first message further includes destination information, wherein the first identifier is associated with the destination information.

With reference to the sixth aspect or the possible design of the sixth aspect, in one possible design, the second message further includes the destination information, where the second identifier is associated with the destination information, and the SR identifier mapped by the second identifier is associated with the destination information.

With reference to the sixth aspect or the possible designs of the sixth aspect, in one possible design, the first message further includes source information and destination information, wherein the first identifier is associated with the source information and the first identifier is associated with the destination information.

With reference to the sixth aspect or the possible designs of the sixth aspect, in one possible design, the second message further includes the source information and the destination information, where the second identifier is associated with the source information and the second identifier is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information.

With reference to the sixth aspect or the possible design of the sixth aspect, in a possible design, the second message further includes one or more of an SR configuration corresponding to the SR identification and an SR resource configuration associated with the SR configuration; the SR configuration comprises the SR identifier, an SR prohibition counter and the maximum SR transmission times; the SR resource configuration includes an SR resource identifier, a period and an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify a configuration of a scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

In combination with the sixth aspect or the possible designs of the sixth aspect, in one possible design, the first identifier is an identifier of a QoS flow.

With reference to the sixth aspect or the possible designs of the sixth aspect, in one possible design, the first identifier is a QoS index used to indicate QoS information.

In a possible design, with reference to the fifth aspect or the sixth aspect, the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel of the sidelink radio bearer, and the second identifier is the same as the first identifier.

For technical effects of any one of the possible designs of the sixth aspect or the sixth aspect, reference may be made to the technical effects of any one of the possible designs of the second aspect or the second aspect, which are not described herein again.

In a seventh aspect, a terminal device is provided, where the terminal device includes a receiving module and a sending module; a sending module, configured to send a first message to a network device, where the first message is used to request a sidelink resource; a receiving module, configured to receive a second message from the network device, where the second message includes a scheduling request SR identifier, and the SR identifier corresponds to an SR configuration, where the SR configuration is associated with one or more SR resource configurations. The SR identifier is an SR identifier common to all V2X services transmitted through the PC5 interface, or the SR identifier is an SR identifier common to all V2X services or service packets transmitted through the PC5 interface and adopting a resource allocation method based on network device scheduling. Furthermore, if the terminal device triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device for the SR may be the SR configuration corresponding to the SR identifier; the SR resource configuration used by the terminal device for the SR may be one or more SR resource configurations associated with the SR configuration.

For technical effects of the seventh aspect, reference may be made to the technical effects of the third aspect, which is not described herein again.

In an eighth aspect, a network device is provided, where the network device includes a receiving module and a sending module, the receiving module is configured to receive a first message from a terminal device, where the first message is used to request a sidelink resource; a sending module, configured to send a second message to the terminal device, where the second message includes a scheduling request SR identifier, and the SR identifier corresponds to one SR configuration, and the SR configuration is associated with one or more SR resource configurations. The SR identifier is an SR identifier common to all V2X services transmitted through the PC5 interface, or the SR identifier is an SR identifier common to all V2X services or service packets transmitted through the PC5 interface and adopting a resource allocation method based on network device scheduling.

The technical effect of the eighth aspect can refer to the technical effect of the fourth aspect, and is not described herein again.

In a ninth aspect, a terminal device is provided, where the terminal device includes a processor and a communication interface, and the processor is communicatively connected through the communication interface, where the processor sends a first message to a network device through the communication interface, where the first message includes a first identifier; the processor receives a second message from the network device through the communication interface, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier. Furthermore, if the logical channel associated with the second identifier triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device for the SR may be the SR configuration corresponding to the SR identifier mapped by the second identifier; the SR resource configuration used by the terminal device for the SR may be one or more SR resource configurations associated with the SR configuration.

With reference to the ninth aspect, in a possible design, the first message further includes quality of service QoS information corresponding to the first identifier.

With reference to the ninth aspect or a possible design of the ninth aspect, in a possible design, if the first identifier and the second identifier have a mapping relationship, the second message further includes or indicates the mapping relationship between the first identifier and the second identifier.

In combination with the ninth aspect or possible designs of the ninth aspect, in one possible design, the first message further includes destination information, wherein the first identification is associated with the destination information.

In combination with the ninth aspect or a possible design of the ninth aspect, in one possible design, the second message further includes the destination information, wherein the second identifier is associated with the destination information, and the SR identifier mapped by the second identifier is associated with the destination information.

In combination with the possible design of the ninth aspect or the ninth aspect, in one possible design, the first message further includes source information and destination information, wherein the first identifier is associated with the source information and the first identifier is associated with the destination information.

In a possible design, in combination with the possible design of the ninth aspect or the ninth aspect, the second message further includes the source information and the destination information, wherein the second identifier is associated with the source information and the second identifier is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information.

With reference to the ninth aspect or the possible design of the ninth aspect, in a possible design, the second message further includes one or more of an SR configuration corresponding to the SR identification and an SR resource configuration associated with the SR configuration; the SR configuration comprises the SR identifier, an SR prohibition counter and the maximum SR transmission times; the SR resource configuration includes an SR resource identifier, a period and an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify a configuration of a scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

In combination with the ninth aspect or a possible design of the ninth aspect, in one possible design, the first identifier is an identifier of a QoS flow.

In combination with the ninth aspect or a possible design of the ninth aspect, in one possible design, the first identifier is a QoS index used to indicate QoS information.

With reference to the ninth aspect or a possible design of the ninth aspect, in a possible design, the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel of the sidelink radio bearer, and the second identifier is the same as the first identifier.

For technical effects of any one of the possible designs of the ninth aspect or the ninth aspect, reference may be made to the technical effects of any one of the possible designs of the first aspect or the first aspect, which are not described herein again.

In a tenth aspect, a network device is provided, which includes a processor and a communication interface, where the processor is connected to communicate through the communication interface, and the processor receives a first message from a terminal device through the communication interface, where the first message includes a first identifier; the processor sends a second message to the terminal device through the communication interface, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

With reference to the tenth aspect, in one possible design, the first message further includes quality of service QoS information corresponding to the first identifier.

With reference to the tenth aspect or the possible design of the tenth aspect, in a possible design, if the first identifier and the second identifier have a mapping relationship, the second message further includes or indicates the mapping relationship between the first identifier and the second identifier.

In combination with the tenth aspect or possible designs of the tenth aspect, in one possible design, the first message further includes destination information, wherein the first identifier is associated with the destination information.

In combination with the tenth aspect or possible designs of the tenth aspect, in one possible design, the second message further includes the destination information, wherein the second identifier is associated with the destination information, and the SR identifier mapped by the second identifier is associated with the destination information.

In combination with the possible design of the tenth aspect or the tenth aspect, in one possible design, the first message further includes source information and destination information, wherein the first identifier is associated with the source information and the first identifier is associated with the destination information.

In combination with the tenth aspect or possible designs of the tenth aspect, in one possible design, the second message further includes the source information and the destination information, wherein the second identifier is associated with the source information and the second identifier is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information.

With reference to the tenth aspect or the possible design of the tenth aspect, in a possible design, the second message further includes one or more of an SR configuration corresponding to the SR identification and an SR resource configuration associated with the SR configuration; the SR configuration comprises the SR identifier, an SR prohibition counter and the maximum SR transmission times; the SR resource configuration includes an SR resource identifier, a period and an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify a configuration of a scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

In combination with the tenth aspect or the tenth aspect, in a possible design, the first identifier is an identifier of a QoS flow.

In combination with the tenth aspect or possible designs of the tenth aspect, in one possible design, the first identifier is a QoS index used to indicate QoS information.

In a possible design, with reference to the ninth aspect or the tenth aspect, the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel of the sidelink radio bearer, and the second identifier is the same as the first identifier.

For technical effects of any one of the possible designs of the tenth aspect or the tenth aspect, reference may be made to the technical effects of any one of the possible designs of the second aspect or the second aspect, which are not described herein again.

In an eleventh aspect, a terminal device is provided, where the terminal device includes a processor and a communication interface, and the processor is communicatively connected to the communication interface, where the processor sends a first message to a network device through the communication interface, where the first message is used to request a sidelink resource; the processor receives a second message from the network device through the communication interface, where the second message includes a scheduling request, SR, identifier, and the SR identifier corresponds to an SR configuration associated with one or more SR resource configurations. The SR identifier is an SR identifier common to all V2X services transmitted through the PC5 interface, or the SR identifier is an SR identifier common to all V2X services or service packets transmitted through the PC5 interface and adopting a resource allocation method based on network device scheduling. Furthermore, if the terminal device triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device for the SR may be the SR configuration corresponding to the SR identifier; the SR resource configuration used by the terminal device for the SR may be one or more SR resource configurations associated with the SR configuration.

For technical effects of the eleventh aspect, reference may be made to the technical effects of the third aspect, which are not described herein again.

In a twelfth aspect, a network device is provided, which includes a processor and a communication interface, the processor is connected to communicate through the communication interface, wherein the processor receives a first message from a terminal device through the communication interface, and the first message is used for requesting a sidelink resource; and the processor sends a second message to the terminal equipment through the communication interface, wherein the second message comprises a Scheduling Request (SR) identifier, the SR identifier corresponds to one SR configuration, and the SR configuration is associated with one or more SR resource configurations. The SR identifier is an SR identifier common to all V2X services transmitted through the PC5 interface, or the SR identifier is an SR identifier common to all V2X services or service packets transmitted through the PC5 interface and adopting a resource allocation method based on network device scheduling.

The technical effect of the twelfth aspect can refer to the technical effect of the fourth aspect, and is not described herein again.

In a thirteenth aspect, there is provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the first aspect described above.

In a fourteenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the first aspect described above.

In a fifteenth aspect, there is provided a communication device (which may be a chip or a system of chips, for example) comprising a processor for implementing the functionality referred to in the first aspect above. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, the communication device may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the design manners in the thirteenth aspect to the fifteenth aspect, reference may be made to the technical effects brought by different design manners in the first aspect, and details are not described herein.

In a sixteenth aspect, a computer-readable storage medium is provided, having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the second aspect described above.

In a seventeenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, causes the computer to perform the method of the second aspect described above.

In an eighteenth aspect, there is provided a communication device (which may be a chip or a system of chips, for example) comprising a processor for implementing the functionality referred to in the second aspect above. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, the communication device may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the design manners in the sixteenth aspect to the eighteenth aspect, reference may be made to the technical effects brought by different design manners in the second aspect, and details are not repeated here.

In a nineteenth aspect, there is provided a computer readable storage medium having stored therein instructions which, when run on a computer, cause the computer to perform the method of the third aspect described above.

In a twentieth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the third aspect described above.

In a twenty-first aspect, there is provided a communication device (which may be a chip or a system of chips, for example) comprising a processor for implementing the functionality referred to in the above third aspect. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, the communication device may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the design manners in the nineteenth aspect to the twenty-first aspect, reference may be made to technical effects brought by different design manners in the third aspect, and details are not repeated here.

In a twenty-second aspect, there is provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the above-mentioned fourth aspect.

In a twenty-third aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the fourth aspect described above.

A twenty-fourth aspect provides a communication device (which may be a chip or a system-of-chips, for example) comprising a processor for implementing the functions referred to in the fourth aspect above. In one possible design, the communication device further includes a memory for storing necessary program instructions and data. When the communication device is a chip system, the communication device may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any one of the twenty-second to twenty-fourth aspects, reference may be made to technical effects brought by different design manners in the above-mentioned fourth aspect, and details are not described here.

A twenty-fifth aspect provides a communication system, where the communication system includes the terminal device of the above-mentioned fifth aspect and the network device of the above-mentioned sixth aspect, or the communication system includes the terminal device of the above-mentioned ninth aspect and the network device of the above-mentioned tenth aspect.

A twenty-sixth aspect provides a communication system, where the communication system includes the terminal device of the seventh aspect and the network device of the eighth aspect, or the communication system includes the terminal device of the eleventh aspect and the network device of the twelfth aspect.

Drawings

Fig. 1a is a schematic diagram illustrating a conventional Uu port communication scheduling;

FIG. 1b is a schematic diagram of a conventional PC5 port communication scheduling;

fig. 1c is a schematic diagram of a relevant configuration of an SR used when an NR system according to an embodiment of the present application transmits an SR for sidelink data transmission of a PC5 port through a Uu port;

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

fig. 3 is a schematic structural diagram of a terminal device and a network device provided in an embodiment of the present application;

fig. 4 is another schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 5 is a first flowchart illustrating a configuration method according to an embodiment of the present application;

fig. 6 is a second flowchart illustrating a configuration method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

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

Detailed Description

To facilitate understanding of the schemes in the embodiments of the present application, a brief introduction or definition of the related art is first given as follows:

first, SR-related configuration

In the embodiment of the present application, relevant configurations of the SR used when the SR for the sidelink data transmission of the PC5 port is sent by the Uu port of the NR system include SR configuration (scheduling request configuration) and SR resource configuration (scheduling request resource configuration).

Wherein the SR configuration is contained in a MAC configuration of the cell group configuration (MAC-CellGroupConfig). Each MAC entity has a MAC configuration. Each MAC configuration may contain up to 8 SR configurations. The SR configuration comprises:

an SR identification (SR ID) for identifying or corresponding to one SR configuration;

an SR inhibit counter (SR inhibit timer) for controlling a time interval of SR transmission;

SR transmission maximum number (SR trans Max) for controlling the maximum number of SR transmissions.

Wherein the SR resource configuration is included in a PUCCH configuration (PUCCH-config). A PUCCH configuration may include 8 SR resource configurations at most. The concept of bandwidth part (BWP) is introduced on the Uu port of NR systems. A maximum of 4 BWPs can be configured on each serving cell of the terminal device. Each BWP on the serving Cell where PUCCH can be configured, i.e. the PUCCH Cell of the terminal device (including PCell/PSCell and PUCCH SCell), has an independent PUCCH configuration and thus also an independent SR resource configuration. The SR resource configuration comprises:

an SR resource identifier (SR resource ID) for identifying a configuration of an SR resource;

period and offset (periodicity and offset) for determining the time domain resource location of the SR;

and a physical uplink control channel resource (PUCCH resource ID) for determining a frequency domain resource location of the SR.

As shown in fig. 1c, each SR configuration under each MAC entity of the terminal device corresponds to one or more uplink logical channels, and each uplink logical channel is mapped to 0 or 1 SR configuration. One SR configuration contains or is associated with a set of SR resource configurations (also referred to as PUCCH SR resource sets) for different BWPs and serving cells. When one MAC entity of the terminal equipment triggers the UL BSR and further triggers the SR, the terminal equipment determines the corresponding SR configuration and SR resource configuration according to the logic channel triggering the UL BSR. If the logical channel triggering the UL BSR configures SR configuration and associated SR resource configuration, that is, the terminal device has an effective dedicated SR resource for transmitting SR for the logical channel triggering the UL BSR, the terminal device sends SR through the dedicated SR resource. If the terminal device has multiple effective dedicated SR resources that coincide in time for the logical channel triggering the UL BSR, which dedicated SR resource is selected to transmit the SR is determined by the terminal device.

Second, QoS information

The QoS information in the embodiments of the present application includes, but is not limited to, one or more of the following parameters: priority, maximum end-to-end delay, reliability, transmission rate, data rate, load, and minimum required communication range, which are described herein in a unified manner and will not be described in detail below.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Where in the description of the present application, "/" indicates a relationship where the objects associated before and after are an "or", unless otherwise stated, for example, a/B may indicate a or B; in the present application, "and/or" is only an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. Also, in the description of the present application, "a plurality" means two or more than two unless otherwise specified. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

The technical scheme of the embodiment of the application can be applied to various communication systems. For example: orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. The term "system" may be used interchangeably with "network". The OFDMA system may implement wireless technologies such as evolved universal radio terrestrial access (E-UTRA), Ultra Mobile Broadband (UMB), and the like. E-UTRA is an evolved version of the Universal Mobile Telecommunications System (UMTS). The third generation partnership project (3rd generation partnership project, 3GPP) is using a new version of E-UTRA in Long Term Evolution (LTE) and various versions based on LTE evolution. The 5G communication system is a next generation communication system under study, and may also be referred to as an NR system. The 5G communication system includes a non-independent Network (NSA) 5G mobile communication system, an independent network (SA) 5G mobile communication system, or an NSA 5G mobile communication system and an SA 5G mobile communication system. In addition, the communication system can also be applied to future-oriented communication technologies, and the technical solutions provided by the embodiments of the present application are all applied. The above-mentioned communication system applicable to the present application is only an example, and the communication system applicable to the present application is not limited thereto, and is herein collectively described, and will not be described again.

Fig. 2 shows a communication system 20 according to an embodiment of the present application. The communication system 20 includes a network device 30 and one or more terminal devices 40 connected to the network device 30. Wherein different terminal devices 40 can communicate with each other.

Taking an example of interaction between the network device 30 shown in fig. 2 and any terminal device 40, in this embodiment of the present application, in order to configure an SR configuration and an SR resource configuration used when the Uu port of the NR system transmits an SR for sidelink data transmission of the PC5 port, the terminal device 40 transmits a first message to the network device 30, where the first message includes a first identifier. After receiving the first message from the terminal device 40, the network device 30 sends a second message to the terminal device 40, where the second message includes a second identifier and an SR identifier mapped by the second identifier, where the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier. Further, after the terminal device 40 receives the second message from the network device 30, if the logical channel associated with the second identifier triggers the SL BSR and triggers the SR, the SR configuration used by the terminal device 40 for the SR is configured as the SR configuration corresponding to the SR identifier mapped by the second identifier; the SR resource configuration used by the terminal device 40 for the SR is one or more SR resource configurations associated with the SR configuration. That is, the terminal device 40 may determine, according to the second identifier and the SR identifier mapped by the second identifier, an SR configuration and an SR resource configuration used when transmitting an SR for sidelink data transmission of the PC5 port at the Uu port of the NR system, so that the SR may be transmitted at the Uu port of the NR system according to the determined SR configuration and SR resource configuration. For a related description of the SR configuration and the SR resource configuration, reference may be made to the brief introduction of the detailed description, which is not repeated herein. The detailed description of the above scheme will refer to the following method embodiment, which is not repeated herein.

Optionally, the network device 30 in this embodiment is a device that accesses the terminal device 40 to a wireless network, and may be an evolved NodeB (eNB) or eNodeB in Long Term Evolution (LTE); or a base station in a fifth generation (5th generation, 5G) network or a Public Land Mobile Network (PLMN) for future evolution, a broadband network service gateway (BNG), a convergence switch or a non-third generation partnership project (3 GPP) access device, and the like, which is not specifically limited in this embodiment of the present application. Optionally, the base station in the embodiment of the present application may include various forms of base stations, for example: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like, which are not specifically limited in this embodiment of the present application.

Optionally, the terminal device 40 in the embodiment of the present application may be a device for implementing a wireless communication function, such as a terminal or a chip that can be used in the terminal. The terminal may be a User Equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a distant station, a remote terminal, a mobile device, a wireless communication device, a terminal agent or a terminal device, etc. in a 5G network or a PLMN which is evolved in the future. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, or a wearable device, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and the like. The terminal may be mobile or stationary.

Optionally, the network device 30 and the terminal device 40 in this embodiment may also be referred to as a communication apparatus, which may be a general device or a special device, and this is not specifically limited in this embodiment.

Optionally, as shown in fig. 3, a schematic structural diagram of the network device 30 and the terminal device 40 provided in the embodiment of the present application is shown.

The terminal device 40 includes at least one processor (exemplarily illustrated in fig. 3 by including one processor 401) and at least one transceiver (exemplarily illustrated in fig. 3 by including one transceiver 403). Optionally, the terminal device 40 may further include at least one memory (exemplarily illustrated in fig. 3 by including one memory 402), at least one output device (exemplarily illustrated in fig. 3 by including one output device 404), and at least one input device (exemplarily illustrated in fig. 3 by including one input device 405).

The processor 401, the memory 402 and the transceiver 403 are connected by a communication line. The communication link may include a path for transmitting information between the aforementioned components.

The processor 401 may be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure. In a specific implementation, the processor 401 may also include multiple CPUs as an embodiment, and the processor 401 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, or processing cores that process data (e.g., computer program instructions).

The memory 402 may be a device having a storage function. Such as, but not limited to, read-only memory (ROM) or other types of static storage devices that may store static information and instructions, Random Access Memory (RAM) or other types of dynamic storage devices that may store information and instructions, electrically erasable programmable read-only memory (EEPROM), compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 402 may be separate and coupled to the processor 401 via a communication link. The memory 402 may also be integrated with the processor 401.

The memory 402 is used for storing computer-executable instructions for executing the present application, and is controlled by the processor 401 to execute. In particular, the processor 401 is configured to execute computer-executable instructions stored in the memory 402, so as to implement the method for adjusting power described in the embodiment of the present application. Optionally, the computer execution instruction in the embodiment of the present application may also be referred to as an application program code or a computer program code, which is not specifically limited in the embodiment of the present application.

The transceiver 403 may use any transceiver or other device for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), or the like. The transceiver 403 includes a transmitter Tx and a receiver Rx.

An output device 404 is in communication with the processor 401 and may display information in a variety of ways. For example, the output device 404 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like.

The input device 405 is in communication with the processor 401 and may accept user input in a variety of ways. For example, the input device 405 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

Network device 30 includes at least one processor (illustrated in fig. 3 as including one processor 301), at least one transceiver (illustrated in fig. 3 as including one transceiver 303), and at least one network interface (illustrated in fig. 3 as including one network interface 304). Optionally, the network device 30 may further include at least one memory (exemplarily illustrated in fig. 3 by including one memory 302). The processor 301, the memory 302, the transceiver 303, and the network interface 304 are connected via a communication line. The network interface 304 is configured to connect with a core network device through a link (e.g., an S1 interface), or connect with a network interface of another network device (not shown in fig. 3) through a wired or wireless link (e.g., an X2 interface), which is not specifically limited in this embodiment of the present application. In addition, the description of the processor 301, the memory 302 and the transceiver 303 may refer to the description of the processor 401, the memory 402 and the transceiver 403 in the terminal device 40, and will not be repeated herein.

In conjunction with the schematic structural diagram of the terminal device 40 shown in fig. 3, fig. 4 is a specific structural form of the terminal device 40 provided in the embodiment of the present application.

Wherein, in some embodiments, the functions of the processor 401 in fig. 3 may be implemented by the processor 110 in fig. 4.

In some embodiments, the functions of the transceiver 403 in fig. 3 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, and the like in fig. 4.

Wherein the antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal equipment 40 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied on the terminal device 40. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the terminal device 40, including Wireless Local Area Networks (WLANs), such as Wi-Fi networks, Bluetooth (BT), Global Navigation Satellite Systems (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves. When the terminal device 40 is a first device, the wireless communication module 160 may provide a solution for NFC wireless communication applied on the terminal device 40, meaning that the first device includes an NFC chip. The NFC chip can improve the NFC wireless communication function. When the terminal device 40 is a second device, the wireless communication module 160 may provide a solution for NFC wireless communication applied on the terminal device 40, that is, the first device includes an electronic tag (e.g., a Radio Frequency Identification (RFID) tag). The NFC chip of the other device is close to the electronic tag to perform NFC wireless communication with the second device.

In some embodiments, antenna 1 of terminal device 40 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that terminal device 40 can communicate with networks and other devices via wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou satellite navigation system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

In some embodiments, the functions of the memory 402 in fig. 3 may be implemented by the internal memory 121 in fig. 4 or an external memory (e.g., a Micro SD card) or the like connected to the external memory interface 120.

In some embodiments, the functionality of output device 404 in FIG. 3 may be implemented by display screen 194 in FIG. 4. The display screen 194 is used to display images, videos, and the like. The display screen 194 includes a display panel. The display panel may be an LCD, an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (flex), miniature, Micro led, Micro-o led, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, terminal device 40 may include 1 or N display screens 194, with N being a positive integer greater than 1.

In some embodiments, the functionality of the input device 405 of fig. 3 may be implemented by a mouse, a keyboard, a touch screen device, or the sensor module 180 of fig. 4. Illustratively, as shown in fig. 4, the sensor module 180 may include, for example, one or more of a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, and a bone conduction sensor 180M, which is not particularly limited in this embodiment of the present application.

In some embodiments, as shown in fig. 4, the terminal device 40 may further include one or more of an audio module 170, a camera 193, an indicator 192, a motor 191, a key 190, a SIM card interface 195, a USB interface 130, a charging management module 140, a power management module 141, and a battery 142, wherein the audio module 170 may be connected to a speaker 170A (also referred to as a "speaker"), a receiver 170B (also referred to as a "receiver"), a microphone 170C (also referred to as a "microphone", "microphone"), or an earphone interface 170D, which is not particularly limited in this embodiment.

It is to be understood that the structure shown in fig. 4 does not constitute a specific limitation to the terminal device 40. For example, in other embodiments of the present application, terminal device 40 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

With reference to fig. 1 to 4, the network device 30 shown in fig. 2 interacts with any terminal device 40, where the terminal device 40 is a terminal in an NR system, and the network device 30 is a base station in the NR system.

For example, as shown in fig. 1b, for communication of PC5 port, if the base station configures a resource allocation manner based on base station scheduling for terminal device 1, when terminal device 1 has SL data to send but has no available SL grant, the terminal device needs to trigger SR and request UL grant from the base station by sending SR. After receiving the UL grant, the terminal device 1 may send the SL BSR to the base station through the UL grant, so that the base station further allocates the SL grant to the terminal device 1 according to the SL BSR, so that the terminal device 1 sends SL data on the corresponding SL grant. However, there is no relevant solution as to how to configure the relevant configuration of the SR used when transmitting the SR for the sidelink data transmission of the PC5 port at the Uu port of the NR system. Based on this, the embodiments of the present application provide the following two configuration methods. The following terminal devices may correspond to the terminal device 1, and are described in a unified manner herein, and will not be described in detail below.

It should be noted that, in the following embodiments of the present application, names of messages between network elements or names of parameters in messages are only an example, and other names may also be used in a specific implementation, which is not specifically limited in this embodiment of the present application.

As shown in fig. 5, a configuration method provided for the embodiment of the present application includes the following steps:

s501, the terminal device sends a first message to the base station. Accordingly, the base station receives a first message from the terminal device. Wherein the first message includes a first identification.

Illustratively, the first message may be, for example, a sidelink UE information (sidelink UE information) message.

Optionally, the QoS information corresponding to the first identifier may also be included in the first message. For the description of the QoS information, reference may be made to the brief introduction of the detailed description, and details are not repeated here.

In a possible implementation manner, destination information of the V2X service may also be included in the first message. The destination information is associated with the first identifier. The destination information is used for the base station to distinguish a destination to which the first identifier belongs, so that one or more of the SR configuration and the SR resource configuration related to the SR configuration are configured for the terminal device according to the destination information and the first identifier.

For example, the destination information in this embodiment may be, for example, a layer two destination identifier (destination L2 ID) or an index value of a layer two destination identifier mapping, which is not specifically limited in this embodiment.

It should be noted that, in the embodiment of the present application, association may also be described as mapping, corresponding or binding, that is, in the embodiment of the present application, association, mapping, corresponding or binding may be understood as different expressions with the same meaning, which are described in a unified manner herein and are not described in detail below.

Or, in another possible implementation manner, the source information and the destination information of the V2X service may also be included in the first message. The source information is associated with the first identifier and the destination information is associated with the first identifier. The source information and the destination information are used for the base station to distinguish the combination of the source and the destination to which the first identifier belongs, so that one or more of the SR configuration and the SR resource configuration related to the SR configuration are configured for the terminal equipment according to the combination of the source information and the destination information and the first identifier.

For example, the source information in this embodiment may be, for example, a source L2 ID or an index value of a source L2 ID mapping, which is not specifically limited in this embodiment.

Optionally, the first message may further include indication information, where the indication information is used to indicate whether the transmission mode corresponding to each QoS stream or each QoS identifier is unicast transmission, multicast transmission, or broadcast transmission.

S502, the base station sends a second message to the terminal equipment. Accordingly, the terminal device receives the second message from the base station. The second message includes a second identifier and an SR identifier mapped by the second identifier, where the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or the first identifier and the second identifier have a mapping relationship.

Illustratively, the second message may be, for example, a Radio Resource Control (RRC) reconfiguration message.

Optionally, in this embodiment of the application, if the first message includes the destination information of the V2X service, the second message may further include the destination information of the V2X service. The destination information is associated with the second identifier, and the destination information is associated with the SR identifier mapped by the second identifier. The destination information is used for the terminal device to distinguish a destination to which the SR identifier mapped by the second identifier belongs, so as to determine, according to the destination information and the SR identifier mapped by the second identifier, an SR configuration used for SR transmission and one or more SR resource configurations associated with the SR configuration.

Or, optionally, in this embodiment of the application, if the first message includes the source information and the destination information of the V2X service, the second message may further include the source information and the destination information of the V2X service. The source information is associated with the second identifier, the source information is associated with the SR identifier mapped by the second identifier, the destination information is associated with the second identifier, and the destination information is associated with the SR identifier mapped by the second identifier. The source information and the destination information are used for the terminal device to distinguish a combination of a source and a destination to which the SR identifier mapped by the second identifier belongs, so that the SR configuration for SR transmission and one or more SR resource configurations associated with the SR configuration are determined according to the combination of the source information and the destination information and the SR identifier mapped by the second identifier.

The above-described arrangement will be described in detail in several different cases.

The first condition is as follows: the first identity is an identity of a QoS flow.

Taking the V2X service AS an example, when a terminal device has a V2X service to be transmitted, an upper layer (application layer, or V2X layer) of the terminal device maps the V2X service to one or more QoS flows, and notifies an Access Stratum (AS) layer of an identifier of each QoS flow and QoS information corresponding to the QoS flow. When the upper layer of the terminal device delivers the V2X service packet to the AS, the upper layer informs the AS layer of the identification of the QoS flow to which the V2X service packet belongs.

Optionally, when the upper layer of the terminal device submits the V2X service packet to the AS, the upper layer simultaneously informs the AS layer that the transmission mode adopted by the V2X service packet is unicast transmission, multicast transmission or broadcast transmission; or when the upper layer of the terminal device notifies the AS layer of the identifier of each QoS flow and the QoS information corresponding to the QoS flow, the AS layer is simultaneously notified that the transmission mode adopted by the V2X service packet on the QoS flow is unicast transmission, multicast transmission or broadcast transmission.

Optionally, the upper layer may inform the AS layer of the transmission mode used by the V2X service packet in an explicit manner, or may inform the AS layer of the transmission mode used by the V2X service packet in an implicit manner, that is, if a service packet is delivered to the AS layer, the upper layer informs the AS layer of the identifier of the QoS stream to which the service packet belongs, that is, the transmission mode of the service packet is unicast transmission; on the contrary, if a service packet is delivered to the AS layer, the upper layer informs the AS layer of the QoS information of the service packet, which means that the transmission mode of the service packet is multicast transmission or broadcast transmission. The description applies to all embodiments of the present application, which are described herein in a unified manner and will not be described in detail below.

Optionally, when the upper layer of the terminal device submits the V2X service packet to the AS, the AS layer is simultaneously informed of the layer two source identifier of the V2X service packet. Or, optionally, when the upper layer of the terminal device delivers the V2X service packet to the AS, the upper layer informs the AS layer of the layer two source identifier and the layer two destination identifier of the V2X service packet at the same time.

Further, the AS layer of the terminal device triggers the first message and requests the base station for resources for V2X sidelink communication through the first message. The first message includes a first identifier, which is an identifier of each QoS flow mapped by the V2X service to be transmitted by the terminal device. Optionally, the first message may further include QoS information corresponding to the identifier of each QoS flow. Optionally, the first message may further include destination information of the V2X service; or, optionally, the first message may further include source information and destination information of the V2X service, and the above step S501 may be referred to for related description, which is not described herein again.

Optionally, the first message further includes indication information, where the indication information is used to indicate whether the transmission mode of the V2X service packet corresponding to each QoS flow or the identifier of each QoS flow is unicast transmission, multicast transmission, or broadcast transmission.

Taking any one of one or more QoS flows mapped by the V2X service to be transmitted by the terminal device as an example, after the base station receives the first message from the terminal device, the following different processing mechanisms are used.

Sub-case a: the second identification is an identification of a logical channel group.

After receiving the first message from the terminal device, the base station determines a logical channel group mapped by a QoS flow corresponding to an identifier of a certain QoS flow in the first message, and determines a configuration related to an SR mapped by the logical channel group according to QoS information corresponding to the identifier of the QoS flow. Further, the base station sends a second message to the terminal device, where the second message includes an identifier of the logical channel group to which the QoS flow is mapped and an SR identifier to which the identifier of the logical channel group is mapped.

Optionally, the second message may further include a mapping relationship between the identifier of the QoS flow and the identifier of the corresponding logical channel group, or in other words, the second message may further include an identifier of the QoS flow having a mapping relationship with the identifier of the logical channel group.

Illustratively, the base station configures the configuration of the logical channel group for the terminal device. Wherein the configuration of the logical channel group at least includes an identifier of the QoS flow mapped to the logical channel group and an identifier of the SR mapped by the logical channel group. Optionally, the configuration of the logical channel group further includes an identifier of the logical channel group.

Or, for example, the base station configures, for the terminal device, the identifier of the logical channel group mapped by the identifier of the QoS flow, and configures, for the terminal device, the configuration of the logical channel group; the configuration of the logical channel group at least comprises the identifier of the SR mapped by the logical channel group; optionally, the configuration of the logical channel group further includes an identifier of the logical channel group.

Optionally, in this embodiment of the present application, different QoS flows may correspond to the same or different logical channel groups, and SR identifiers mapped by identifiers of different logical channel groups may be the same or different. For example, the mapping relationship between the QoS flow identifier, the logical channel group identifier, and the SR identifier may be as shown in table one.

Watch 1

It should be noted that the table is only an exemplary table storage form, and other table storage forms or non-table storage forms may also exist. For example, as shown in table two, the identifier of each QoS flow is stored in one-to-one correspondence with the identifier of each logical channel group and the SR identifier, and the storage form of the correspondence is not specifically limited in the embodiment of the present application. The description applies to all embodiments of the present application, which are described herein in a unified manner and will not be described in detail below.

Watch two

Identification of QoS flows	Identification of logical channel groups	SR identification
			Identification of QoS flows 1	Identification of logical channel groups 1	SR identification 1
Identification of QoS flows 2	Identification of logical channel groups 1	SR identification 1
			Identification of QoS flows 3	Identification of logical channel groups 2	SR identification 2
Identification of QoS flows 4	Identification of logical channel groups 3	SR identification 2

Optionally, in this embodiment of the application, before step S501, the base station may have sent the SR configuration corresponding to the SR identifier to the terminal device, or the base station may have sent the SR configuration corresponding to the SR identifier and the SR resource configuration associated with the SR configuration to the terminal device, which is not specifically limited in this embodiment of the application. The description applies to the embodiments of the present application and the following embodiments, which are described herein in a unified manner and will not be repeated herein.

Optionally, in this embodiment of the application, if the base station has sent, to the terminal device, the SR configuration corresponding to the SR identifier mapped to the identifier of the logical channel group included in the second message before, but for the logical channel group mapped to the SR identifier, it is necessary to associate a new SR resource configuration with the SR configuration corresponding to the SR identifier, and then the second message further needs to include one or more SR resource configurations associated with the SR configuration corresponding to the SR identifier. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

Or, optionally, in this embodiment of the application, if the base station does not configure, for the terminal device, the SR configuration corresponding to the SR identifier mapped by the logical channel group and the SR resource configuration associated with the SR configuration included in the second message before, the second message further needs to include the SR configuration corresponding to the SR identifier and one or more SR resource configurations associated with the SR configuration. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

Optionally, in this embodiment of the application, if the first message includes the destination information of the V2X service, the second message may further include the destination information of the V2X service. Or, optionally, in this embodiment of the application, if the first message includes the source information and the destination information of the V2X service, the second message may further include the source information and the destination information of the V2X service, and the related description may refer to the step S502, which is not described herein again.

And after receiving the second message from the base station, the terminal equipment establishes the side-link radio bearer mapped by the QoS flow. Exemplary may include: a Packet Data Convergence Protocol (PDCP) entity of the sidelink radio bearer is established, a Radio Link Control (RLC) entity of the sidelink radio bearer is established, and a logical channel of the sidelink radio bearer is configured. The mapping relationship between the QoS flow and the sidelink radio bearer may be one-to-one mapping or many-to-one mapping.

In this embodiment of the present application, the identifier (SL DRB ID) of the sidelink radio bearer and the identifier (local channel ID) of the logical channel of the sidelink radio bearer are determined by the terminal device itself.

Further, the terminal device may configure, according to the mapping relationship between the identifier of the QoS flow and the identifier of the logical channel group included in the second message, the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs as the logical channel group corresponding to the QoS flow.

Further, the terminal device may determine, according to the SR identifier mapped to the identifier of the logical channel group included in the second message, that the SR identifier mapped to the logical channel of the sidelink radio bearer mapped to the QoS flow is the SR identifier mapped to the identifier of the logical channel group.

If the logical channel of the sidelink radio bearer mapped by the QoS flow triggers the SL BSR and triggers the first SR, the first SR configuration used by the terminal device for the first SR is the SR configuration corresponding to the SR identifier mapped by the identifier of the logical channel group; the terminal equipment is used for configuring the first SR resource configuration of the first SR into one or more SR resource configurations related to the first SR configuration.

Optionally, the embodiment of the present application may be only applicable to the V2X service whose transmission mode is unicast transmission, or may be applicable to all V2X services, that is, the V2X service whose transmission mode is unicast transmission, multicast transmission, and broadcast transmission.

Sub-case b: the second identification is an identification of a QoS flow.

After receiving the first message from the terminal device, the base station determines the configuration related to the SR mapped by a certain QoS flow according to the QoS information corresponding to the identifier of the QoS flow in the first message. And further, the base station sends a second message to the terminal equipment, wherein the second message comprises the identification of the QoS flow and the SR identification mapped by the identification of the QoS flow.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group corresponding to the QoS flow, and include, in the second message, a mapping relationship between an identifier of the QoS flow and an identifier of the corresponding logical channel group, or in other words, the second message may further include an identifier of a logical channel group having a mapping relationship with the identifier of the QoS flow.

Illustratively, the base station configures the configuration of the QoS flow for the terminal device. The configuration of the QoS flow at least includes an identifier of an SR mapped by the QoS flow and an identifier of a logical channel group corresponding to the QoS flow. Optionally, the configuration of the QoS flow further includes an identifier of the QoS flow.

Or, for example, the base station configures, for the terminal device, the identifier of the QoS flow mapped to the identifier of the logical channel group, and configures, for the terminal device, the configuration of the QoS flow; the configuration of the QoS flow at least comprises the identification of the SR mapped by the QoS flow; optionally, the configuration of the QoS flow further includes an identifier of the QoS flow.

Optionally, in this embodiment of the application, if the base station has sent, to the terminal device, the SR configuration corresponding to the SR identifier mapped to the identifier of the QoS flow included in the second message before, but for the QoS flow mapped to the SR identifier, it is necessary to associate a new SR resource configuration with the SR configuration corresponding to the SR identifier, and then the second message further needs to include one or more SR resource configurations associated with the SR configuration corresponding to the SR identifier. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

Or, optionally, in this embodiment of the application, if the base station does not configure, for the terminal device, the SR configuration corresponding to the SR identifier mapped by the identifier of the QoS flow included in the second message and the SR resource configuration associated with the SR configuration before that, the second message further needs to include the SR configuration corresponding to the SR identifier and one or more SR resource configurations associated with the SR configuration. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

After receiving the second message from the base station, the terminal device establishes the sidelink radio bearer mapped by the QoS flow, and the related description may refer to the sub-case a described above, which is not described herein again.

Further, if the second message includes the mapping relationship between the identifier of the QoS flow and the identifier of the logical channel group, the terminal device may configure, according to the mapping relationship between the identifier of the QoS flow and the identifier of the logical channel group, the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs as the logical channel group corresponding to the identifier of the QoS flow.

Further, the terminal device may determine, according to the SR identifier mapped to the identifier of the QoS flow included in the second message, that the SR identifier mapped to the logical channel of the sidelink radio bearer mapped to the QoS flow is the SR identifier mapped to the identifier of the QoS flow.

If the logical channel of the sidelink radio bearer mapped by the QoS flow triggers the SL BSR and triggers the first SR, the first SR configuration used by the terminal device for the first SR is the SR configuration corresponding to the SR identifier mapped by the identifier of the QoS flow; the terminal equipment is used for configuring the first SR resource configuration of the first SR into one or more SR resource configurations related to the first SR configuration.

Sub-case c: the second identification is an identification of a sidelink radio bearer.

After receiving the first message from the terminal device, the base station determines a sidelink radio bearer mapped by a QoS flow corresponding to an identifier of a certain QoS flow in the first message, and allocates an identifier for the sidelink radio bearer. Further, the base station determines the configuration related to the SR mapped by the sidelink radio bearer according to the QoS information corresponding to the identifier of the QoS flow. Further, the base station sends a second message to the terminal device, where the second message includes the identifier of the sidelink radio bearer mapped by the QoS flow and the SR identifier mapped by the identifier of the sidelink radio bearer mapped by the QoS flow.

Optionally, the second message may further include a mapping relationship between the identification of the QoS flow and the identification of the sidelink radio bearer to which the QoS flow is mapped, or in other words, the second message may further include an identification of the QoS flow to which the identification of the sidelink radio bearer to which the QoS flow is mapped has a mapping relationship.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer to which the QoS flow is mapped. Wherein, the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: an identification of the QoS flow mapped to the sidelink radio bearer and an identification of the SR mapped by the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of a sidelink radio bearer mapped by the identifier of the QoS flow, and configures, for the terminal device, a configuration of a sidelink radio bearer mapped by the QoS flow; the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: the identity of the SR mapped by the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group corresponding to the sidelink radio bearer mapped by the QoS flow, and include, in the second message, a mapping relationship between an identifier of the sidelink radio bearer mapped by the QoS flow and an identifier of the logical channel group, or, in other words, the second message may further include an identifier of the logical channel group having a mapping relationship with the identifier of the sidelink radio bearer mapped by the QoS flow.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer to which the QoS flow is mapped. Wherein, the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: an identifier of the QoS flow mapped to the sidelink radio bearer, an identifier of the SR mapped to the sidelink radio bearer, and an identifier of a logical channel group corresponding to the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of a sidelink radio bearer mapped by the identifier of the QoS flow, and configures, for the terminal device, a configuration of a sidelink radio bearer mapped by the QoS flow; the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: the identifier of the SR mapped by the sidelink radio bearer, and the identifier of the logical channel group corresponding to the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Optionally, in this embodiment of the application, if the base station has sent, to the terminal device, the SR configuration corresponding to the SR identifier mapped to the identifier of the sidelink radio bearer included in the second message before, but for the sidelink radio bearer mapped to the SR identifier, it is necessary to associate a new SR resource configuration with the SR configuration corresponding to the SR identifier, and then the second message further needs to include one or more SR resource configurations associated with the SR configuration corresponding to the SR identifier. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

Or, optionally, in this embodiment of the application, if the base station does not configure, for the terminal device, the SR configuration corresponding to the SR identifier mapped by the identifier of the sidelink radio bearer included in the second message and the SR resource configuration associated with the SR configuration before, the second message further needs to include the SR configuration corresponding to the SR identifier and one or more SR resource configurations associated with the SR configuration. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

In this embodiment of the present application, the identifier (SL DRB ID) of the sidelink radio bearer mapped by the QoS flow is the identifier of the sidelink radio bearer mapped by the QoS flow included in the second message, and the identifier (local channel ID) of the logical channel of the sidelink radio bearer mapped by the QoS flow is determined by the terminal device itself.

Further, if the second message includes the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS flow and the identifier of the logical channel group, the terminal device may configure, according to the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS flow and the identifier of the logical channel group, the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs as the logical channel group corresponding to the identifier of the sidelink radio bearer mapped by the QoS flow.

Further, the terminal device may determine, according to the SR identifier mapped to the identifier of the sidelink radio bearer mapped to the QoS flow included in the second message, that the SR identifier mapped to the logical channel of the sidelink radio bearer mapped to the QoS flow is the SR identifier mapped to the identifier of the sidelink radio bearer mapped to the QoS flow.

If the logical channel of the sidelink radio bearer mapped by the QoS flow triggers the SL BSR and triggers the first SR, the first SR configuration used by the terminal device for the first SR is the SR configuration corresponding to the SR identifier mapped by the identifier of the sidelink radio bearer mapped by the QoS flow; the terminal equipment is used for configuring the first SR resource configuration of the first SR into one or more SR resource configurations related to the first SR configuration.

Sub-case d: the second identification is an identification of a logical channel.

After receiving the first message from the terminal device, the base station determines a sidelink radio bearer mapped by a QoS flow corresponding to an identifier of a certain QoS flow in the first message, allocates an identifier to the sidelink radio bearer, and configures an identifier of a logical channel of the sidelink radio bearer. Further, the base station determines the configuration related to the SR mapped by the logical channel of the sidelink radio bearer according to the QoS information corresponding to the identifier of the QoS flow. Further, the base station sends a second message to the terminal device, where the second message includes an identifier of a logical channel of a sidelink radio bearer mapped by the QoS flow and an SR identifier mapped by the identifier of the logical channel of the sidelink radio bearer mapped by the QoS flow.

Optionally, the second message may further include an identification of the sidelink radio bearer to which the QoS flow is mapped.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer to which the QoS flow is mapped. Wherein, the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: an identity of the QoS flow mapped to the sidelink radio bearer, an identity of a logical channel of the sidelink radio bearer, and a configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of the SR mapped by the logical channel of the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of a sidelink radio bearer mapped by the identifier of the QoS flow, and configures, for the terminal device, a configuration of a sidelink radio bearer mapped by the QoS flow; the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: the identification of the logical channel of the sidelink radio bearer and the configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of the SR mapped by the logical channel of the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group to which a logical channel of a sidelink radio bearer mapped by the QoS flow belongs, and include, in the second message, a mapping relationship between an identifier of the sidelink radio bearer mapped by the QoS flow and an identifier of the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs, or, in other words, the second message may further include an identifier of the logical channel group having a mapping relationship with the identifier of the sidelink radio bearer mapped by the QoS flow.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer to which the QoS flow is mapped. Wherein, the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: an identity of the QoS flow mapped to the sidelink radio bearer, an identity of a logical channel of the sidelink radio bearer, and a configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of an SR mapped by the logical channel of the sidelink radio bearer and an identifier of a logical channel group to which the logical channel of the sidelink radio bearer belongs. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of a sidelink radio bearer mapped by the identifier of the QoS flow, and configures, for the terminal device, a configuration of a sidelink radio bearer mapped by the QoS flow; the configuration of the sidelink radio bearer mapped by the QoS flow at least includes: the identification of the logical channel of the sidelink radio bearer and the configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of an SR mapped by the logical channel of the sidelink radio bearer and an identifier of a logical channel group to which the logical channel of the sidelink radio bearer belongs. Optionally, the configuration of the sidelink radio bearer mapped by the QoS flow may further include an identifier of the sidelink radio bearer.

Optionally, in this embodiment of the application, if the base station has previously sent, to the terminal device, the SR configuration corresponding to the SR identifier mapped to the identifier of the sidelink radio bearer included in the second message, but for the logical channel of the sidelink radio bearer mapped to the SR identifier, it is necessary to associate a new SR resource configuration with the SR configuration corresponding to the SR identifier, and then the second message further needs to include one or more SR resource configurations associated with the SR configuration corresponding to the SR identifier. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

Optionally, in this embodiment of the application, if the first message includes the destination information of the V2X service, the second message may further include the destination information of the V2X service. Or, optionally, if the first message includes the source information and the destination information of the V2X service, the second message may further include the source information and the destination information of the V2X service, and the relevant description may refer to the step S502, which is not described herein again.

In this embodiment of the present application, the identifier (SL DRB ID) of the sidelink radio bearer mapped by the QoS flow is the identifier of the sidelink radio bearer mapped by the QoS flow included in the second message. The identifier (Logical channel ID) of the Logical channel of the sidelink radio bearer mapped by the QoS flow is the identifier of the Logical channel of the sidelink radio bearer mapped by the QoS flow included in the second message.

Further, if the second message includes a mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS flow and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs, the terminal device may configure the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs as the logical channel group corresponding to the identifier of the sidelink radio bearer mapped by the QoS flow according to the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS flow and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS flow belongs.

If the logical channel of the sidelink radio bearer mapped by the QoS flow triggers the SL BSR and triggers the first SR, the first SR configuration used by the terminal device for the first SR is an SR configuration corresponding to the SR identifier mapped by the identifier of the logical channel of the sidelink radio bearer mapped by the QoS flow; the terminal equipment is used for configuring the first SR resource configuration of the first SR into one or more SR resource configurations related to the first SR configuration.

Case two: the first identifier is a QoS index for indicating QoS information.

Taking the V2X service AS an example, when an upper layer (application layer, or V2X layer) of the terminal device delivers a V2X service packet to the AS, the QoS index of the QoS information of the V2X service or the V2X service packet to be transmitted by the AS layer is informed. The QoS index may be, for example, a 5G QoS identifier (5G QoS identifier, 5QI), a V2X/vehicle to vehicle (V2V) QoS identifier (V2X/V2V QoS identifier, VQI), a QoS Class Identifier (QCI), or other form of index value. Wherein each QoS index value corresponds to a set of QoS information.

Optionally, when the upper layer of the terminal device submits the V2X service packet to the AS, the upper layer simultaneously informs the AS layer that the transmission mode adopted by the V2X service packet is unicast transmission, multicast transmission or broadcast transmission. Or when the upper layer of the terminal device notifies the AS layer of the QoS information indicated by the QoS index and the QoS index, the AS layer is simultaneously notified that the transmission mode adopted by the V2X service packet corresponding to the QoS index is unicast transmission, multicast transmission or broadcast transmission.

Further, the AS layer of the terminal device triggers the first message and requests the base station for resources for V2X sidelink communication through the first message. The first message comprises a first identifier, and the first identifier is a QoS index of QoS information of V2X service or V2X service packet to be transmitted by the terminal device. Optionally, the first message may further include QoS information corresponding to the QoS index. Optionally, the first message may further include destination information of the V2X service; or, optionally, the first message may further include source information and destination information of the V2X service, and the above step S501 may be referred to for related description, which is not described herein again.

Optionally, the first message may further include indication information, where the indication information is used to indicate whether the transmission mode of the V2X service packet corresponding to the QoS index is unicast transmission, multicast transmission, or broadcast transmission.

After receiving the first message from the terminal device, the base station corresponds to several different processing mechanisms described below.

Sub-case e: the second identification is an identification of a logical channel group.

After receiving the first message from the terminal device, the base station determines a logical channel group mapped by the QoS index in the first message, and determines a configuration related to an SR mapped by the logical channel group according to QoS information corresponding to or indicated by the QoS index. Further, the base station sends a second message to the terminal device, where the second message includes an identifier of the logical channel group to which the QoS index is mapped and an SR identifier to which the identifier of the logical channel group is mapped.

Optionally, the second message may further include a mapping relationship between the QoS index and the identifier of the corresponding logical channel group, or in other words, the second message may further include the QoS index that has a mapping relationship with the identifier of the logical channel group.

Illustratively, the base station configures the configuration of the logical channel group for the terminal device. Wherein the configuration of the logical channel group at least includes the QoS index mapped to the logical channel group and an identification of the SR mapped by the logical channel group. Optionally, the configuration of the logical channel group further includes an identifier of the logical channel group.

Or, for example, the base station configures, for the terminal device, the identifier of the logical channel group to which the identifier of the QoS index is mapped, and configures, for the terminal device, the configuration of the logical channel group; the configuration of the logical channel group at least comprises the identifier of the SR mapped by the logical channel group; optionally, the configuration of the logical channel group further includes an identifier of the logical channel group.

Optionally, in this embodiment of the present application, different QoS indexes may correspond to the same or different logical channel groups, and SR identifiers mapped by identifiers of different logical channel groups may be the same or different. For example, the mapping relationship between the QoS index, the identification of the logical channel group, and the SR identification may be as shown in table three.

Watch III

Or, optionally, in this embodiment of the application, if the base station does not configure, for the terminal device, the SR configuration corresponding to the SR identifier mapped by the identifier of the logical channel group included in the second message and the SR resource configuration associated with the SR configuration before, the second message further needs to include the SR configuration corresponding to the SR identifier and one or more SR resource configurations associated with the SR configuration. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

And after receiving the second message from the base station, the terminal equipment establishes the side-link radio bearer mapped by the QoS index. For the related description, reference may be made to the description of establishing the sidelink radio bearer mapped by the QoS flow in the sub-scenario a, which is not described herein again. The mapping relationship between the QoS index and the sidelink radio bearer may be one-to-one mapping or many-to-one mapping.

Further, the terminal device may configure, according to the mapping relationship between the QoS index and the identifier of the logical channel group included in the second message, the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs as the logical channel group corresponding to the QoS index.

Further, the terminal device may determine, according to the SR identifier mapped to the identifier of the logical channel group included in the second message, that the SR identifier mapped to the logical channel of the sidelink radio bearer mapped to the QoS index is the SR identifier mapped to the identifier of the logical channel group.

If the logical channel of the sidelink radio bearer mapped by the QoS index triggers the SL BSR and triggers the second SR, the second SR configuration used by the terminal device for the second SR is the SR configuration corresponding to the SR identifier mapped by the identifier of the logical channel group; the terminal device is used for configuring the second SR resource configuration of the second SR into one or more SR resource configurations related to the second SR configuration.

Sub-case f: the second identification is a QoS index for indicating QoS information.

After receiving the first message from the terminal device, the base station determines the configuration related to the SR mapped by the QoS index according to the QoS information corresponding to or indicated by the QoS index in the first message. And further, the base station sends a second message to the terminal equipment, wherein the second message comprises the QoS index and the SR identifier mapped by the QoS index.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group corresponding to the QoS index, and include a mapping relationship between the QoS index and an identifier of the corresponding logical channel group in the second message, or in other words, the second message may further include an identifier of a logical channel group having a mapping relationship with the QoS index.

Illustratively, the base station configures the configuration of the QoS index for the terminal device. The configuration of the QoS index at least includes an identifier of the SR mapped by the QoS index and an identifier of a logical channel group corresponding to the QoS index. Optionally, the configuration of the QoS index further includes the QoS index.

Or, for example, the base station configures, for the terminal device, the identifier of the logical channel group mapped by the QoS index, and configures, for the terminal device, the configuration of the QoS index; the configuration of the QoS index at least comprises the identification of the SR mapped by the QoS index; optionally, the configuration of the QoS index further includes the QoS index.

Optionally, in this embodiment of the application, if the base station has sent, to the terminal device, the SR configuration corresponding to the SR identifier mapped by the QoS index included in the second message before, but for the QoS index mapped by the SR identifier, it is necessary to associate a new SR resource configuration with the SR configuration corresponding to the SR identifier, and then the second message further needs to include one or more SR resource configurations associated with the SR configuration corresponding to the SR identifier. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

Or, optionally, in this embodiment of the application, if the base station does not configure, for the terminal device, the SR configuration corresponding to the SR identification mapped by the QoS index included in the second message and the SR resource configuration associated with the SR configuration before that, the second message further needs to include the SR configuration corresponding to the SR identification and one or more SR resource configurations associated with the SR configuration. The one or more SR resource configurations are included in a PUCCH configuration in an uplink BWP of a Uu port configured by the base station for the terminal device.

And after receiving the second message from the base station, the terminal equipment establishes the side-link radio bearer mapped by the QoS index. For the related description, reference may be made to the above sub-case e, which is not described herein again.

Further, if the second message includes the mapping relationship between the QoS index and the identifier of the logical channel group, the terminal device may configure, according to the mapping relationship between the QoS index and the identifier of the logical channel group, the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs as the logical channel group corresponding to the QoS index.

Further, the terminal device may determine, according to the SR identifier mapped by the QoS index included in the second message, that the SR identifier mapped by the logical channel of the sidelink radio bearer mapped by the QoS index is the SR identifier mapped by the QoS index.

If the logical channel of the sidelink radio bearer mapped by the QoS index triggers the SL BSR and triggers the second SR, the second SR configuration used by the terminal device for the second SR is configured to the SR configuration corresponding to the SR identifier mapped by the QoS index; the terminal device is used for configuring the second SR resource configuration of the second SR into one or more SR resource configurations related to the second SR configuration.

Sub-case g: the second identification is an identification of a sidelink radio bearer.

After receiving the first message from the terminal equipment, the base station determines a sidelink radio bearer mapped by the QoS index in the first message, and allocates an identifier for the sidelink radio bearer. Further, the base station determines the SR-related configuration mapped by the sidelink radio bearer according to the QoS information corresponding to or indicated by the QoS index. Furthermore, the base station sends a second message to the terminal device, wherein the second message comprises the identifier of the sidelink radio bearer mapped by the QoS index and the SR identifier mapped by the identifier of the sidelink radio bearer mapped by the QoS index.

Optionally, the second message may further include a mapping relationship between the QoS index and the identification of the sidelink radio bearer to which the QoS index is mapped, or in other words, the second message may further include a QoS index that has a mapping relationship with the identification of the sidelink radio bearer to which the QoS index is mapped.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer mapped by the QoS index. Wherein, the configuration of the sidelink radio bearer mapped by the QoS index at least includes: a QoS index mapped to the sidelink radio bearer and an identification of the SR mapped by the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of the sidelink radio bearer mapped by the QoS index, and configures, for the terminal device, a configuration of the sidelink radio bearer mapped by the QoS index; the configuration of the sidelink radio bearer mapped by the QoS index at least includes: the identity of the SR mapped by the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group corresponding to the sidelink radio bearer mapped by the QoS index, and include, in the second message, a mapping relationship between an identifier of the sidelink radio bearer mapped by the QoS index and an identifier of the logical channel group, or, in other words, the second message may further include an identifier of the logical channel group having a mapping relationship with the identifier of the sidelink radio bearer mapped by the QoS index.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer mapped by the QoS index. Wherein, the configuration of the sidelink radio bearer mapped by the QoS index at least includes: a QoS index mapped to the sidelink radio bearer, an identification of the SR mapped by the sidelink radio bearer, and an identification of a logical channel group to which the sidelink radio bearer corresponds. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of the sidelink radio bearer mapped by the QoS index, and configures, for the terminal device, a configuration of the sidelink radio bearer mapped by the QoS index; the configuration of the sidelink radio bearer mapped by the QoS index at least includes: the identifier of the SR mapped by the sidelink radio bearer, and the identifier of the logical channel group corresponding to the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

In this embodiment of the present application, the identifier (SL DRBID) of the sidelink radio bearer mapped by the QoS index is the identifier of the sidelink radio bearer mapped by the QoS index included in the second message, and the identifier (local channel ID) of the logical channel of the sidelink radio bearer mapped by the QoS index is determined by the terminal device itself.

If the second message includes the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS index and the identifier of the logical channel group, the terminal device may configure, according to the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS index and the identifier of the logical channel group, the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs as the logical channel group corresponding to the sidelink radio bearer mapped by the QoS index.

Further, the terminal device may determine, according to the SR identifier mapped by the identifier of the sidelink radio bearer mapped by the QoS index included in the second message, that the SR identifier mapped by the logical channel of the sidelink radio bearer mapped by the QoS index is the SR identifier mapped by the sidelink radio bearer mapped by the QoS index.

If the logical channel of the sidelink radio bearer mapped by the QoS index triggers the SL BSR and triggers the second SR, the second SR configuration used by the terminal device for the second SR is the SR configuration corresponding to the SR identifier mapped by the identifier of the sidelink radio bearer mapped by the QoS index; the terminal device is used for configuring the second SR resource configuration of the second SR into one or more SR resource configurations related to the second SR configuration.

Sub-case h: the second identification is an identification of a logical channel of the sidelink radio bearer.

After receiving the first message from the terminal device, the base station determines a sidelink radio bearer mapped by the QoS index in the first message, allocates an identifier for the sidelink radio bearer, and configures an identifier of a logical channel of the sidelink radio bearer. Further, the base station determines the SR-related configuration mapped by the logical channel of the sidelink radio bearer according to the QoS information corresponding to or indicated by the QoS index. Further, the base station sends a second message to the terminal device, where the second message includes an identifier of a logical channel of the sidelink radio bearer mapped by the QoS index and an SR identifier mapped by the identifier of the logical channel of the sidelink radio bearer mapped by the QoS index.

Optionally, the second message may further include an identification of the sidelink radio bearer to which the QoS index is mapped.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer mapped by the QoS index. Wherein, the configuration of the sidelink radio bearer mapped by the QoS index at least includes: a QoS index mapped to the sidelink radio bearer, an identity of a logical channel of the sidelink radio bearer, and a configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of the SR mapped by the logical channel of the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of a sidelink radio bearer mapped by the identifier of the QoS index, and configures, for the terminal device, a configuration of a sidelink radio bearer mapped by the QoS index; the configuration of the sidelink radio bearer mapped by the QoS index at least includes: the identification of the logical channel of the sidelink radio bearer and the configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of the SR mapped by the logical channel of the sidelink radio bearer. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group to which a logical channel of the sidelink radio bearer mapped by the QoS index belongs, and include, in the second message, an identifier of the sidelink radio bearer mapped by the QoS index and a mapping relationship between the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs, or, in other words, the second message may further include an identifier of the logical channel group having a mapping relationship with the identifier of the sidelink radio bearer mapped by the QoS index.

Illustratively, the base station configures the terminal device with the configuration of the sidelink radio bearer mapped by the QoS index. Wherein, the configuration of the sidelink radio bearer mapped by the QoS index at least includes: a QoS index mapped to the sidelink radio bearer, an identity of a logical channel of the sidelink radio bearer, and a configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of an SR mapped by the logical channel of the sidelink radio bearer and an identifier of a logical channel group to which the logical channel of the sidelink radio bearer belongs. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

Or, for example, the base station configures, for the terminal device, an identifier of the sidelink radio bearer mapped by the QoS index, and configures, for the terminal device, a configuration of the sidelink radio bearer mapped by the QoS index; the configuration of the sidelink radio bearer mapped by the QoS index at least includes: the identification of the logical channel of the sidelink radio bearer and the configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of an SR mapped by the logical channel of the sidelink radio bearer and an identifier of a logical channel group to which the logical channel of the sidelink radio bearer belongs. Optionally, the configuration of the sidelink radio bearer mapped by the QoS index may further include an identifier of the sidelink radio bearer.

After receiving the second message from the base station, the terminal device establishes the sidelink radio bearer mapped by the QoS index, and the related description may refer to the sub-case e described above, which is not described herein again.

In this embodiment of the present application, the identifier (SL DRBID) of the sidelink radio bearer mapped by the QoS index is an identifier of the sidelink radio bearer mapped by the QoS index included in the second message. The identifier (Logical channel ID) of the Logical channel of the sidelink radio bearer mapped by the QoS index is the identifier of the Logical channel of the sidelink radio bearer mapped by the QoS index included in the second message.

Further, if the second message includes the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS index and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs, the terminal device may configure the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs as the logical channel group corresponding to the identifier of the sidelink radio bearer mapped by the QoS index according to the mapping relationship between the identifier of the sidelink radio bearer mapped by the QoS index and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer mapped by the QoS index belongs.

If the logical channel of the sidelink radio bearer mapped by the QoS index triggers the SL BSR and triggers the second SR, the second SR configuration used by the terminal device for the second SR is configured to be an SR configuration corresponding to the SR identifier mapped by the identifier of the logical channel of the sidelink radio bearer mapped by the QoS index; the terminal device is used for configuring the second SR resource configuration of the second SR into one or more SR resource configurations related to the second SR configuration.

Case three: the first identifier is an identifier of a sidelink radio bearer or an identifier of a logical channel, and the second identifier is the same as the first identifier.

Taking the V2X service as an example, when a terminal device has a V2X service to transmit, an upper layer (application layer, or V2X layer) of the terminal device has two processing modes for the V2X service.

One possible way of processing is: the upper layer of the terminal equipment maps the V2X service to one or more QoS flows and informs the AS layer of the identification of each QoS flow and the QoS information corresponding to the QoS flow. When the upper layer of the terminal device delivers the V2X service packet to the AS, the upper layer informs the AS layer of the identification of the QoS flow to which the V2X service packet belongs.

Another possible processing method is: the upper layers of the terminal device do not map V2X traffic to one or more QoS flows. When the upper layer of the terminal device delivers the V2X service packet to the AS, the AS layer is informed of the QoS index of the QoS information of the V2X service or V2X service packet to be transmitted by the terminal device. For the description of the QoS index, reference may be made to the above case two, which is not described herein again.

Optionally, when the upper layer of the terminal device submits the V2X service packet to the AS, the upper layer simultaneously informs the AS layer that the transmission mode adopted by the V2X service packet is unicast transmission, multicast transmission or broadcast transmission.

If the upper layer of the terminal device adopts the first possible processing manner, the AS layer of the terminal device may determine, according to the identifier of the QoS flow to which the V2X service packet submitted by the upper layer belongs, the identifier of the sidelink radio bearer mapped by the QoS flow or the identifier of the logical channel of the sidelink radio bearer mapped by the QoS flow, in combination with the QoS information corresponding to the QoS flow. I.e. the AS layer of the terminal device may perform the mapping of QoS flows to sidelink radio bearers.

Or, if the second possible processing manner is adopted by the upper layer of the terminal device, the AS layer of the terminal device may determine, according to the QoS index of the QoS information of the V2X service or the V2X service packet submitted by the upper layer, the identifier of the sidelink radio bearer mapped by the V2X service packet or the identifier of the logical channel of the sidelink radio bearer mapped by the V2X service packet, in combination with the QoS information indicated by the QoS index. I.e., the AS layer of the terminal device may perform mapping of the V2X traffic packets to the sidelink radio bearer.

The following is a description in two sub-cases.

Sub-case i: the first identity is an identity of a sidelink radio bearer.

The AS layer of the terminal equipment triggers the first message and requests the base station for the resources for V2X sidelink communication through the first message. The first message contains a first identifier, and the first identifier is an identifier of a sidelink radio bearer mapped by the V2X service to be transmitted by the terminal equipment. Optionally, the first message may further include QoS information corresponding to the sidelink radio bearer. Optionally, the first message may further include destination information of the V2X service; or, optionally, the first message may further include source information and destination information of the V2X service, and the above step S501 may be referred to for related description, which is not described herein again.

Optionally, the first message may further include indication information, where the indication information is used to indicate whether the transmission mode of the V2X service packet corresponding to the identifier of the sidelink radio bearer is unicast transmission, multicast transmission, or broadcast transmission.

After receiving the first message from the terminal device, the base station determines the SR-related configuration mapped by the sidelink radio bearer corresponding to the sidelink radio bearer identifier in the first message. And further, the base station sends a second message to the terminal device, wherein the second message comprises the identifier of the sidelink radio bearer and the SR identifier mapped by the identifier of the sidelink radio bearer.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group corresponding to the sidelink radio bearer, and include, in the second message, a mapping relationship between an identifier of the sidelink radio bearer and an identifier of the corresponding logical channel group, or, in other words, the second message may further include an identifier of a logical channel group having a mapping relationship with the identifier of the sidelink radio bearer.

Illustratively, the base station configures the configuration of the sidelink radio bearer for the terminal device. Wherein the configuration of the sidelink radio bearer at least comprises: the identifier of the SR mapped by the sidelink radio bearer, and the identifier of the logical channel group corresponding to the sidelink radio bearer. Optionally, the configuration of the sidelink rb may further include an identifier of the sidelink rb.

Or, for example, the base station configures, for the terminal device, the identifier of the sidelink radio bearer mapped to the identifier of the logical channel group, and configures, for the terminal device, the configuration of the sidelink radio bearer; the configuration of the sidelink radio bearer at least comprises: the identity of the SR mapped by the sidelink radio bearer. Optionally, the configuration of the sidelink rb may further include an identifier of the sidelink rb.

After receiving the second message from the base station, the terminal device establishes the sidelink radio bearer, and the related description may refer to the description of establishing the sidelink radio bearer mapped by the QoS flow in the sub-case a, which is not described herein again.

In this embodiment of the present application, the identifier (SL DRB ID) of the sidelink radio bearer is an identifier of the sidelink radio bearer included in the second message, and the identifier (logical ID) of the logical channel of the sidelink radio bearer is determined by the terminal device itself.

Further, if the second message includes the mapping relationship between the identifier of the sidelink radio bearer and the identifier of the logical channel group, the terminal device may configure, according to the mapping relationship between the identifier of the sidelink radio bearer and the identifier of the logical channel group, the logical channel group to which the logical channel of the sidelink radio bearer belongs as the logical channel group corresponding to the identifier of the sidelink radio bearer.

Further, the terminal device may determine, according to the SR identifier mapped to the identifier of the sidelink radio bearer included in the second message, that the SR identifier mapped to the logical channel of the sidelink radio bearer is the SR identifier mapped to the identifier of the sidelink radio bearer.

If the logic channel of the sidelink radio bearer triggers the SL BSR and triggers the third SR, the third SR configuration used by the terminal device for the third SR is the SR configuration corresponding to the SR identifier mapped by the identifier of the sidelink radio bearer; the SR resource configuration used by the terminal device for the third SR is one or more SR resource configurations associated with the third SR configuration.

Optionally, the embodiment of the present application may be applicable to all V2X services, that is, V2X services including unicast transmission, multicast transmission and broadcast transmission.

Sub-case j: the first identity is an identity of a logical channel.

The AS layer of the terminal equipment triggers the first message and requests the base station for the resources for V2X sidelink communication through the first message. The first message comprises a first identifier, and the first identifier is an identifier of a logical channel of a sidelink radio bearer mapped by the V2X service to be transmitted by the terminal equipment. Optionally, the first message may further include QoS information corresponding to an identification of a logical channel of the sidelink radio bearer. Optionally, the first message may further include destination information of the V2X service; or, optionally, the first message may further include source information and destination information of the V2X service, and the above step S501 may be referred to for related description, which is not described herein again.

Optionally, the first message may further include indication information, where the indication information is used to indicate whether the transmission mode of the V2X service packet corresponding to the identifier of the logical channel of the sidelink radio bearer is unicast transmission, multicast transmission, or broadcast transmission.

After receiving the first message from the terminal device, the base station determines the SR-related configuration mapped by the logical channel corresponding to the logical channel identifier of the sidelink radio bearer in the first message. And further, the base station sends a second message to the terminal device, wherein the second message comprises the identifier of the logical channel of the sidelink radio bearer and the SR identifier mapped by the identifier of the logical channel of the sidelink radio bearer.

Optionally, after receiving the first message from the terminal device, the base station may further determine a logical channel group to which a logical channel corresponding to the identifier of the logical channel of the sidelink radio bearer belongs in the first message, and include, in the second message, a mapping relationship between the identifier of the sidelink radio bearer and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer belongs, or, in other words, the second message may further include an identifier of the logical channel group having a mapping relationship with the identifier of the sidelink radio bearer.

Illustratively, the base station configures the configuration of the sidelink radio bearer for the terminal device. Wherein the configuration of the sidelink radio bearer at least comprises: the identification of the logical channel of the sidelink radio bearer and the configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of an SR mapped by the logical channel of the sidelink radio bearer and an identifier of a logical channel group to which the logical channel of the sidelink radio bearer belongs. Optionally, the configuration of the sidelink rb may further include an identifier of the sidelink rb.

Or, for example, the base station configures, for the terminal device, an identifier of the sidelink radio bearer mapped to the identifier of the logical channel group, and configures, for the terminal device, a configuration of the sidelink radio bearer; the configuration of the sidelink radio bearer at least comprises: the identification of the logical channel of the sidelink radio bearer and the configuration of the logical channel of the sidelink radio bearer; the configuration of the logical channel of the sidelink radio bearer includes an identifier of the SR mapped by the logical channel of the sidelink radio bearer. Optionally, the configuration of the sidelink rb may further include an identifier of the sidelink rb.

After receiving the second message from the base station, the terminal device establishes the sidelink radio bearer, and the related description may refer to the sub-case i described above, which is not described herein again.

In this embodiment of the present application, the identifier (logical ID) of the sidelink radio bearer is an identifier of the logical channel of the sidelink radio bearer included in the second message, and the identifier (SL DRB ID) of the sidelink radio bearer is determined by the terminal device itself.

Further, if the second message includes the mapping relationship between the identifier of the sidelink radio bearer and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer belongs, the terminal device may configure the logical channel group to which the logical channel of the sidelink radio bearer belongs as the logical channel group corresponding to the identifier of the sidelink radio bearer according to the mapping relationship between the identifier of the sidelink radio bearer and the identifier of the logical channel group to which the logical channel of the sidelink radio bearer belongs.

If the logical channel of the sidelink radio bearer triggers the SL BSR and triggers the third SR, the third SR configuration used by the terminal device for the third SR is an SR configuration corresponding to the SR identifier mapped by the identifier of the logical channel of the sidelink radio bearer; the SR resource configuration used by the terminal device for the third SR is one or more SR resource configurations associated with the third SR configuration.

Based on the configuration method provided by the embodiment of the present application, the configuration of the SR configuration and the SR resource configuration used when the Uu port of the NR system transmits the SR for the sidelink data transmission of the PC5 port can be realized.

The processor 301 in the network device 30 shown in fig. 3 may call the application code stored in the memory 302 to instruct the network device to perform the actions of the base station in the above steps S501 to S502, and the processor 401 in the terminal device 40 shown in fig. 3 may call the application code stored in the memory 402 to instruct the network device to perform the actions of the terminal device in the above steps S501 to S502, which is not limited in this embodiment.

Optionally, in the foregoing embodiment, the configuration related to the SR for the V2X service may be the same as or different from the configuration related to the SR for uplink data transmission of the Uu port of the terminal device.

Alternatively, the above embodiments may be used in combination. For example, for a unicast transmission V2X service or V2X service packet, the method described in the embodiment corresponding to the case 1 may be adopted, and for a multicast transmission or broadcast transmission V2X service or V2X service packet, the method described in the implementation corresponding to the case 2 may be adopted, which is described herein in a unified manner, but this is not specifically limited in the embodiment of the present application.

Optionally, in this embodiment of the application, for all V2X services, no matter what way the service is transmitted (broadcast way, multicast way, or unicast way), no matter whether the service is transmitted through the sidelink of the PC5 port of the LTE system or the sidelink of the PC5 port of the NR system, the base station configures only one set of SR-related configuration for one MAC entity of the terminal device. In this case, as shown in fig. 6, another configuration method provided in the embodiment of the present application includes the following steps:

s601, the terminal equipment sends a first message to the base station. Accordingly, the base station receives a first message from the terminal device.

Specifically, if the terminal device is interested in V2X service transmission, the terminal device requests the base station for resources for V2X sidelink communication through the first message.

S602, the base station sends a second message to the terminal equipment. Accordingly, the terminal device receives the second message from the base station.

Specifically, after receiving the first message from the terminal device, the base station sends a second message to the terminal device, where the second message includes the V2X-related configuration. The related configuration of V2X further includes an SR identifier common to all V2X services configured by the base station for the terminal device and transmitted via the PC5 interface, or the related configuration of V2X further includes an SR identifier common to all V2X services or service packets configured by the base station for the terminal device and transmitted via the PC5 interface and using a resource allocation manner based on base station scheduling.

Optionally, in this embodiment of the present application, the configuration related to the SR common to all V2X services may be the same as or different from the configuration related to the SR of the terminal device for uplink data transmission of the Uu port.

Illustratively, the second message may be, for example, an RRC reconfiguration (RRC reconfiguration) message.

When the terminal device triggers the SL BSR and triggers the fourth SR, the terminal device configures the fourth SR configuration for the fourth SR as the SR configuration corresponding to the SR identifier; the terminal device is configured to configure a fourth SR resource configuration of the fourth SR as one or more SR resource configurations associated with the fourth SR configuration.

The processor 301 in the network device 30 shown in fig. 3 may call the application code stored in the memory 302 to instruct the network device to perform the actions of the base station in the above steps S601 to S602, and the processor 401 in the terminal device 40 shown in fig. 3 may call the application code stored in the memory 402 to instruct the network device to perform the actions of the terminal device in the above steps S501 to S502, which is not limited in this embodiment.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. Correspondingly, the embodiment of the application also provides a communication device, and the communication device is used for realizing the various methods. The communication device may be the terminal device in the above method embodiment, or a device including the above terminal device, or a component that can be used for the terminal device; alternatively, the communication device may be the access network device in the above method embodiment, or a device including the above access network device, or a component that can be used for the access network device. It is to be understood that the communication device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the communication apparatus may be divided into functional modules according to the method embodiments, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

For example, the communication device is taken as the terminal device in the above method embodiment. Fig. 7 shows a schematic structural diagram of a terminal device 70. The terminal device 70 includes a receiving module 701 and a transmitting module 702. The receiving module 701, which may also be referred to as a receiving unit, is used to implement a receiving function, and may be, for example, a receiving circuit, a receiver, or a communication interface. The sending module 702, which may also be referred to as a sending unit, is used to implement a sending function, and may be, for example, a sending circuit, a sender, or a communication interface.

The sending module 702 is configured to send a first message to a network device, where the first message includes a first identifier. A receiving module 701, configured to receive a second message from a network device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the present embodiment, the terminal device 70 is presented in a form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, those skilled in the art will appreciate that the terminal device 70 may take the form of the terminal device 40 shown in fig. 3.

For example, the processor 401 in the terminal device 40 shown in fig. 3 may execute the instructions by calling a computer stored in the memory 402, so that the terminal device 40 executes the configuration method in the above-described method embodiment.

Specifically, the functions/implementation procedures of the receiving module 701 and the sending module 702 in fig. 7 may be implemented by the processor 401 in the terminal device 40 shown in fig. 4 calling the computer execution instructions stored in the memory 402. Alternatively, the functions/implementation procedures of the receiving module 701 and the transmitting module 702 in fig. 7 may be implemented by the transceiver 403 in the terminal device 40 shown in fig. 4.

Since the terminal device 70 provided in this embodiment can execute the configuration method, the technical effects obtained by the terminal device 70 can refer to the method embodiments, and are not described herein again.

Or, for example, the communication device is taken as the network device in the above method embodiment. Fig. 8 shows a schematic structural diagram of a network device 80. The network device 80 includes a receiving module 801 and a transmitting module 802. The receiving module 801, which may also be referred to as a receiving unit, is used to implement a receiving function, and may be, for example, a receiving circuit, a receiver, or a communication interface. The transmitting module 802, which may also be referred to as a transmitting unit, is used to implement a transmitting function, and may be, for example, a transmitting circuit, a transmitter, or a communication interface.

The receiving module 801 is configured to receive a first message from a terminal device, where the first message includes a first identifier. A sending module 802, configured to send a second message to the terminal device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to one SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

In the present embodiment, the network device 80 is presented in the form of dividing each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that provides the described functionality. In a simple embodiment, those skilled in the art will appreciate that the network device 80 may take the form of the network device 30 shown in FIG. 3.

For example, the processor 301 in the network device 30 shown in fig. 3 may execute the instructions by calling a computer stored in the memory 302, so that the network device 30 executes the configuration method in the above method embodiment.

Specifically, the functions/implementation procedures of the receiving module 801 and the sending module 802 in fig. 8 can be implemented by the processor 301 in the network device 30 shown in fig. 4 calling the computer execution instructions stored in the memory 302. Alternatively, the functions/implementation procedures of the receiving module 801 and the transmitting module 802 in fig. 8 may be implemented by the transceiver 303 in the network device 30 shown in fig. 4.

Since the network device 80 provided in this embodiment can execute the configuration method, the technical effects obtained by the method can refer to the method embodiments, and are not described herein again.

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

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of configuration, the method comprising:

the method comprises the steps that terminal equipment sends a first message to network equipment, wherein the first message comprises a first identifier;

the terminal device receives a second message from the network device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

2. A method of configuration, the method comprising:

the method comprises the steps that network equipment receives a first message from terminal equipment, wherein the first message comprises a first identifier;

the network device sends a second message to the terminal device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to one SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

3. A communication apparatus, characterized in that the communication apparatus comprises: a transmitting module and a receiving module;

the sending module is configured to send a first message to a network device, where the first message includes a first identifier;

the receiving module is configured to receive a second message from the network device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

4. A communication apparatus, characterized in that the communication apparatus comprises: the device comprises a receiving module and a sending module;

the receiving module is used for receiving a first message from the terminal equipment, wherein the first message comprises a first identifier;

the sending module is configured to send a second message to the terminal device, where the second message includes a second identifier and a scheduling request SR identifier mapped by the second identifier, the SR identifier corresponds to an SR configuration, the SR configuration is associated with one or more SR resource configurations, and the first identifier is the same as the second identifier, or there is a mapping relationship between the first identifier and the second identifier.

5. The method or communications device according to any of claims 1-4, wherein the first message further comprises quality of service, QoS, information corresponding to the first identity.

6. The method or communications device according to any one of claims 1 to 5, wherein if there is a mapping relationship between the first identifier and the second identifier, the second message further includes or indicates a mapping relationship between the first identifier and the second identifier.

7. The method or communications device according to any one of claims 1-6, wherein the first message further comprises destination information, wherein the first identifier is associated with the destination information;

the second message further comprises the destination information, wherein the second identity is associated with the destination information and the SR identity mapped by the second identity is associated with the destination information.

8. The method or communications device according to any one of claims 1-6, wherein the first message further comprises source information and destination information, wherein the first identifier is associated with the source information and the first identifier is associated with the destination information;

the second message further includes the source information and the destination information, wherein the second identification is associated with the source information and the second identification is associated with the destination information; the SR identification mapped by the second identification is associated with the source information, and the SR identification mapped by the second identification is associated with the destination information.

9. The method or communications apparatus according to any one of claims 1-8, wherein the second message further includes one or more of an SR configuration to which the SR identification corresponds and an SR resource configuration with which the SR configuration is associated; the SR configuration comprises the SR identifier, an SR prohibition counter and the SR transmission maximum number; the SR resource configuration includes an SR resource identifier, a period, an offset, and a physical uplink control channel resource, where the SR prohibit counter is used to control a time interval of SR transmission, the maximum number of SR transmission is used to control the maximum number of SR transmission, the SR resource identifier is used to identify configuration of one scheduling request resource, the period and the offset are used to determine a time domain resource location of an SR, and the physical uplink control channel resource is used to determine a frequency domain resource location of the SR.

10. The method or communications device according to any of claims 1-9, wherein the first identity is an identity of a QoS flow.

11. The method or communication apparatus according to claim 10, wherein the second identifier is an identifier of a logical channel group to which a logical channel of a sidelink radio bearer to which the QoS flow is mapped belongs; or, the second identifier is an identifier of the QoS flow; or, the second identifier is an identifier of a sidelink radio bearer to which the QoS flow is mapped; or, the second identifier is an identifier of a logical channel of a sidelink radio bearer to which the QoS flow is mapped.

12. The method or the communications apparatus according to claim 11, wherein if a logical channel of a sidelink radio bearer mapped by the QoS flow triggers a sidelink buffer status report (SL BSR) and triggers a first SR, the terminal device configures, as an SR configuration corresponding to an SR identifier mapped by the second identifier, the first SR configuration used by the first SR; the terminal equipment is used for configuring the first SR resource configuration of the first SR into one or more SR resource configurations related to the first SR configuration.

13. The method or communications device of any of claims 1-9, wherein said first identifier is a QoS index indicating QoS information.

14. The method or communication apparatus according to claim 13, wherein the second identifier is an identifier of a logical channel group to which a logical channel of a sidelink radio bearer mapped by the QoS index belongs; or, the second identifier is the QoS index for indicating the QoS information corresponding to the first identifier; or, the second identifier is an identifier of a sidelink radio bearer mapped by the QoS index; or, the second identifier is an identifier of a logical channel of a sidelink radio bearer mapped by the QoS index.

15. The method or the communications apparatus according to claim 14, wherein if a logical channel of a sidelink radio bearer mapped by the QoS index triggers a sidelink buffer status report (SL BSR) and triggers a second SR, the terminal device configures, as the SR configuration corresponding to the SR identifier mapped by the second identifier, the second SR configuration for the second SR; the terminal equipment is used for configuring the second SR resource configuration of the second SR into one or more SR resource configurations related to the second SR configuration.

16. The method or communications device according to any one of claims 1 to 9, wherein the first identity is an identity of a sidelink radio bearer or an identity of a logical channel of the sidelink radio bearer, and wherein the second identity is the same as the first identity.

17. The method or the communication apparatus according to claim 16, wherein if a logical channel of the sidelink radio bearer triggers a SL BSR and triggers a third SR, the terminal device configures, for the third SR, an SR configuration corresponding to the SR identifier mapped by the second identifier; the terminal device uses the SR resource configuration of the third SR as one or more SR resource configurations associated with the third SR configuration.

18. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1, 2 or 5-17.