Patent Description:
Embodiments of the present disclosure relate to the communications field, and in particular, to a sidelink (SideLink, SL for short, or translated into a side link, a lateral link, or an edge link) transmission method and device.

A Long Term Evolution (Long Term Evolution, LTE) system supports SL transmission, that is, data transmission can be directly performed between terminal devices over a wireless air interface. In the LTE system, a terminal device works in only one resource allocation mode. In a new radio (New Radio, NR) system, because more diversified QoS services need to be supported, the foregoing resource allocation mode probably cannot meet a data transmission QoS requirement. "Enhancements of Uu link to control sidelink"; R1-<NUM> discloses that "RAN2 will support the case a UE can be configured to perform both mode-<NUM> and mode-<NUM> at the same time assuming RANI does not have concern on it. RAN2 has agreed that a connected UE can perform mode-<NUM> and mode-<NUM> simultaneously. If a UE can perform mode-<NUM> and mode-<NUM> simultaneously, the resource for the two modes should be separated in time. Moreover, as discussed above, the broadcast transmission needs multiple slots for beam sweeping, while the unicast transmission may only require one shot transmission. In order to assign the proper sidelink resource for different kinds of transmission, the BSR should indicate not only the buffer size but also the transmission type of the data. If more than one unicast (or groupcast) links are supported in a UE, the BSR report from that UE should also indicate which link the data belongs to. Otherwise, the network may not be able to schedule a suitable beam for transmission and reception. BSR for sidelink should be enhanced to indicate the transmission type and destination".

Embodiments of the present disclosure provide an SL transmission method and a device, to resolve a problem that it is difficult to meet a data transmission QoS requirement in a single resource allocation mode.

According to a first aspect, an SL transmission method is provided, which is defined in claim <NUM>.

According to a second aspect, a terminal device is provided, which is defined in claim <NUM>. The terminal device includes a configuration module, configured to perform configuration based on first configuration information, so that the terminal device simultaneously works in both a Mode <NUM> and a Mode <NUM>.

According to a third aspect, a computer-readable storage medium is provided, which is defined in claim <NUM>.

It is to be understood that both the forgoing general description and the following detailed description are exemplary only, and are not restrictive of the present disclosure.

The accompanying drawings illustrated herein are provided to further understand this application and form a part of this application. The exemplary embodiments of this application and the descriptions thereof are used to explain this application and do not constitute an improper limitation on this application. In the accompanying drawings:.

To make the objectives, technical solutions, and advantages of this application clearer, the following clearly and completely describes the technical solutions of this application with reference to the specific embodiments of this application and the corresponding accompanying drawings Apparently, the described embodiments are merely some rather than all of the embodiments of this application.

It should be understood that the technical solutions in the embodiments of the present disclosure may be applied to various communications systems, such as Global System for Mobile Communications (Global System of Mobile communication, GSM), a Code Division Multiple Access (Code Division Multiple Access, CDMA) system, a Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, a general packet radio service (General Packet Radio Service, GPRS) system, a Long Term Evolution (Long Term Evolution, LTE) system, an LTE frequency division duplex (Frequency Division Duplex, FDD) system, an LTE time division duplex (Time Division Duplex, TDD) system, a universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS) or a worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, WiMAX) communications system, a <NUM> system, a new radio (New Radio, NR) system, or a subsequent evolved communications system.

In some embodiments of the present disclosure, a terminal device may include but is not limited to a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile telephone (Mobile Telephone), user equipment (User Equipment, UE), a handset (handset), portable equipment (portable equipment), a vehicle (vehicle), and the like. The terminal device may communicate with one or more core networks by using a radio access network (Radio Access Network, RAN). For example, the terminal device may be a mobile telephone (or referred to as a "cellular" telephone), or a computer having a wireless communication function; or the terminal device may be a portable, pocket-sized, handheld, computer built-in, or in-vehicle mobile apparatus.

In some embodiments of the present disclosure, a network device is an apparatus that is deployed in a radio access network and that is used to provide a wireless communication function for a terminal device. The network device may be a base station, and the base station may include various forms such as a macro base station, a micro base station, a relay station, or an access point. In systems that use different radio access technologies, devices that have a base station function may have different names. For example, in an LTE network, the network device is referred to as an evolved NodeB (Evolved NodeB, eNB or eNodeB), and in a 3rd Generation (3rd Generation, <NUM>) network, the network device is referred to as a NodeB (NodeB) or a network device in the subsequent evolved communications system. However, the terms do not constitute a limitation.

As shown in <FIG>, an embodiment of the present disclosure provides an SL transmission method <NUM>. The method may be performed by a terminal device, and includes the following steps.

S102: Perform configuration based on first configuration information, so that the terminal device simultaneously works in both a Mode <NUM> and a Mode <NUM>.

Optionally, the foregoing first configuration information may be obtained in at least one of the following three manners:.

If the foregoing first configuration information is sent through the network device broadcast message or the dedicated RRC signaling of network device, before step S102, the terminal device may further receive the first configuration information.

The Mode <NUM> mentioned in the embodiments of the present disclosure is a network device scheduling mode. For the Mode <NUM>, the terminal device may obtain a sidelink control channel (Physical Sidelink Control Channel, PSCCH) resource pool configuration and an associated sidelink shared channel (Physical Sidelink Shared Channel, PSSCH) resource pool configuration of the Mode <NUM> by receiving system broadcast signaling and the like sent by the network device. When the terminal device has to-be-transmitted data, the terminal device requests a dedicated Mode <NUM> communication resource from the network device through a buffer status report (Buffer Status Report, BSR).

The Mode <NUM> mentioned in the embodiments of the present disclosure is a terminal device autonomous mode. For the Mode <NUM>, the terminal device obtains a PSCCH resource pool configuration and an associated PSSCH resource pool configuration of the Mode <NUM> by receiving network device system broadcast signaling, or obtains a PSCCH resource pool configuration and an associated PSSCH resource pool configuration of the Mode <NUM> through the dedicated RRC signaling of network device, or determines a PSCCH resource pool configuration and an associated PSSCH resource pool configuration of the Mode <NUM> through preconfiguration information. In each PSCCH period, the terminal device randomly selects sending resources of a PSCCH and an associated PSSCH.

According to the SL transmission method provided in some embodiments of the present disclosure, the terminal device may perform related configuration based on configuration information, so that the terminal device can work in both the Mode <NUM> and the Mode <NUM> during SL transmission. The terminal device has diversified resource allocation modes, so that resource utilization efficiency of SL transmission can be improved, and different QoS requirements can be met.

For the foregoing improving resource utilization efficiency of SL transmission, in the related art, the terminal device supports only one single resource allocation mode, and cannot fully use communications resources. Especially, in an SL communication scenario, when a large amount of service data or service data of many types needs to be transmitted, the foregoing disadvantage is more obvious.

According to the SL transmission method provided in some embodiments of the present disclosure, after performing configuration based on configuration information, the terminal device can work in both the Mode <NUM> and the Mode <NUM>, to make full use of SL resources. In addition, a correspondence between a service and the Mode <NUM> or the Mode <NUM> may be determined based on a quality of service QoS or a service type of the service, to meet different QoS requirements.

The first configuration information may be used to instruct the terminal device to perform related configuration of working in the Mode <NUM> and the Mode <NUM>. Optionally, based on the foregoing embodiment, the first configuration information may include at least one of the following five types:.

In the implementation of (<NUM>) or (<NUM>), in a case that the terminal device simultaneously works in both the Mode <NUM> and the Mode <NUM>, a logical channel or a logical channel group corresponding to the Mode <NUM> may further be distinguished from a logical channel or a logical channel group corresponding to the Mode <NUM>. (<NUM>) Mapping relationship between a mode type and a sidelink radio bearer identifier (SideLink Radio Bearer Identity, SLRB ID): The mode type herein includes at least one of the Mode <NUM> and the Mode <NUM>. Specifically, the mapping relationship between a mode type and an SLRB ID may be the following three cases: a mapping relationship between the Mode <NUM> and an SLRB ID; or a mapping relationship between the Mode <NUM> and an SLRB ID; or a mapping relationship between the Mode <NUM> and an SLRB ID and a mapping relationship between the Mode <NUM> and an SLRB ID.

In this implementation, the mapping relationship between a mode type and an SLRB ID is established. In a case that the terminal device simultaneously works in both the Mode <NUM> and the Mode <NUM>, a correspondence between a service and the Mode <NUM> or the Mode <NUM> may be determined based on at least one of a quality of service QoS and a service type of the service, that is, different types of service data can be sent in different resource allocation modes (that is, the Mode <NUM> or the Mode <NUM>) in this implementation. (<NUM>) Mapping relationship between a mode type and a destination identifier (Destination ID): The mode type herein includes at least one of the Mode <NUM> and the Mode <NUM>. Specifically, the mapping relationship between a mode type and a destination ID may be the following three cases: a mapping relationship between the Mode <NUM> and a destination ID; or a mapping relationship between the Mode <NUM> and a destination ID; or a mapping relationship between the Mode <NUM> and a destination ID and a mapping relationship between the Mode <NUM> and a destination ID.

In this implementation, the mapping relationship between a mode type and a destination ID is established, and a correspondence between a service and the Mode <NUM> or the Mode <NUM> may be determined based on at least one of a quality of service QoS and a service type of the service, that is, different types of service data can be sent in different resource allocation modes (that is, the Mode <NUM> or the Mode <NUM>) in this implementation.

Based on the foregoing plurality of embodiments, in a case that the terminal device simultaneously works in both the Mode <NUM> and the Mode <NUM>:.

Optionally, as shown in <FIG>, for terminal devices (UE1 and UE2) that perform SL communication, the Mode <NUM> and the Mode <NUM> may share a Media Access Control MAC entity.

Further, optionally, as shown in <FIG> and <FIG>, for terminal devices (UE1 and UE2) that perform SL communication, the Mode <NUM> and the Mode <NUM> may correspond to different MAC entities.

In the embodiments shown in <FIG>, the first configuration information may further include a mapping relationship between a mode type and an SLRB ID.

The following separately describes two cases in which the Mode <NUM> and the Mode <NUM> share a MAC entity, and the Mode <NUM> and the Mode <NUM> correspond to different MAC entities.

In the embodiments shown in <FIG>, terminal devices (for example, UE1 and UE2) that perform SL communication may separately create a MAC entity, and when both a mode <NUM> and a mode <NUM> of the UE1 and the UE2 work, one MAC entity is shared. That is, in <FIG>, when both the mode <NUM> and the mode <NUM> of the UE1 work, a MAC1 is shared, and when both the mode <NUM> and the mode <NUM> of the UE2 work, a MAC2 is shared.

The foregoing is merely described by using SL communication between the UE1 and the UE2 as an example. As shown in <FIG>, for SL communication between the UE1 and UE3, SL communication between the UE1 and UE4, and the like, the content described in each corresponding embodiment of the present disclosure is also applicable, and is not described again herein.

In a case that the Mode <NUM> and the Mode <NUM> share a MAC entity, the performing configuration based on first configuration information in step S102 in the foregoing several embodiments may further include: defining that the MAC entity shared by the Mode <NUM> and the Mode <NUM> performs at least one of the following behaviors:.

In this implementation, the first configuration information may include a mapping relationship between a mode type and an SL logical channel identifier.

(<NUM>) If there is buffer data in at least one of currently configured SL logical channels (which may be all SL logical channels), an SL BSR is triggered in a case that an SL logical channel on which data arrives (which may be one or more of the currently configured SL logical channels) has a higher logical channel priority and the SL logical channel on which data arrives corresponds to the Mode <NUM>.

"An SL logical channel on which data arrives has a higher logical channel priority" mentioned in this implementation means that a priority of an SL logical channel on which data arrives currently is higher than a priority of an SL logical channel in which there is buffer data in the currently configured SL logical channels.

(<NUM>) If a retransmission SL BSR timer expires, an SL BSR is triggered in a case that there is buffer data in at least one of currently configured SL logical channels (which may be all SL logical channels), and an SL logical channel corresponding to the retransmission SLBSR timer corresponds to the Mode <NUM>.

In the foregoing plurality of implementations, when an SL BSR trigger condition is met, an SL BSR can be triggered in a timely manner, to request, from the network device in a timely manner, resources required for transmission in the Mode <NUM>, thereby improving communication efficiency.

In addition, an SL BSR is triggered only in a case that buffer data arrives on a logical channel corresponding to the Mode <NUM>, and the SL BSR is not triggered in a case that buffer data arrives on a logical channel corresponding to the Mode <NUM>.

Optionally, in a case that the Mode <NUM> and the Mode <NUM> share a MAC entity, the performing configuration based on first configuration information in step S <NUM> in the foregoing several embodiments may further include: defining that the MAC entity shared by the Mode <NUM> and the Mode <NUM> performs the following behavior:.

In the foregoing implementation, buffer data in an SL logical channel corresponding to the Mode <NUM> can be ignored, and only buffer data in an SL logical channel corresponding to the Mode <NUM> is calculated into the SLBSR, so that the Mode <NUM> and the Mode <NUM> can independently work without affecting each other.

In a case that the Mode <NUM> and the Mode <NUM> share a MAC entity, optionally, the terminal device may further perform flexible switching between resource allocation modes. Specifically, the terminal device may perform configuration based on second configuration information, so that the terminal device works only in the Mode <NUM> or the Mode <NUM>, that is, cancels working in both the Mode <NUM> and the Mode <NUM>.

The second configuration information may be obtained in at least one of the following manners:.

Optionally, the performing configuration based on second configuration information may include: defining that the MAC entity shared by the Mode <NUM> and the Mode <NUM> performs at least one of the following behaviors:.

In the foregoing plurality of implementations, after the terminal device switches from working in both the Mode <NUM> and the Mode <NUM> to working in the Mode <NUM> or the Mode <NUM>, and especially enters the Mode <NUM>, the terminal device may cancel or stop a previous related configuration in a timely manner, and further may perform reconfiguration when working in the Mode <NUM> or the Mode <NUM>, to avoid configuration impact caused by resource allocation mode switching, thereby improving communication effectiveness.

As shown in <FIG> and <FIG>, for terminal devices (UE1 and UE2) that perform SL communication, the Mode <NUM> and the Mode <NUM> may correspond to different MAC entities. In this embodiment, a pair of terminal devices (UE1 and UE2) that perform SL communication may separately create a pair of MAC entities. Referring to <FIG>, a mode <NUM> of the UE1 works at a MAC <NUM>, and a mode <NUM> works at a MAC <NUM>; and a mode <NUM> of the UE2 works at a MAC <NUM>, and a mode <NUM> works at a MAC <NUM>.

In a case that the Mode <NUM> and the Mode <NUM> correspond to different MAC entities, the performing configuration based on first configuration information in step S <NUM> in the foregoing several embodiments may further include: obtaining, based on the first configuration information, maximum transmit power P_max; maximum transmit power P_max1 of a MAC entity corresponding to the Mode <NUM>; and maximum transmit power P_max2 of a MAC entity corresponding to the Mode <NUM>.

In this way, the performing configuration based on first configuration information in step S102 in the foregoing several embodiments may further include: if the P_max is greater than a sum of the P_max1 and the P_max2, defining that the MAC entity corresponding to the Mode <NUM> and the MAC entity corresponding to Mode <NUM> perform one of the following four behaviors.

The remaining power herein may be obtained by using a difference between the P_max and the P_max1 and a difference between the P_max and the P_max2.

(<NUM>) Remaining power is allocated to the MAC entity corresponding to the Mode <NUM> and the MAC entity corresponding to the Mode <NUM> based on a first preset proportion.

In this implementation, the first preset proportion may be prestored. Specifically, for example, the first preset proportion may be <NUM>:<NUM> or <NUM>:<NUM>.

(<NUM>) Remaining power is allocated to the MAC entity corresponding to the Mode <NUM> or the MAC entity corresponding to the Mode <NUM> based on a size relationship between a priority of to-be-transmitted data and a first preset threshold.

Specifically, for example, if the priority of the to-be-transmitted data is greater than or equal to the first preset threshold, the remaining power is allocated to the MAC entity corresponding to the Mode <NUM>. If the priority of the to-be-transmitted data is less than the first preset threshold, the remaining power is allocated to the MAC entity corresponding to the Mode <NUM>.

In this implementation, optionally, the to-be-transmitted data may be transmitted by using the MAC entity to which the remaining power is allocated.

(<NUM>) Remaining power is allocated to the MAC entity corresponding to the Mode <NUM> or the MAC entity corresponding to the Mode <NUM> based on a size relationship between a priority P<NUM> of to-be-transmitted data corresponding to the Mode <NUM> and a priority P<NUM> of to-be-transmitted data corresponding to the Mode <NUM>.

Specifically, for example, if P<NUM> is greater than or equal to P<NUM>, the remaining power is allocated to the MAC entity corresponding to the mode <NUM>. If P<NUM> is less than P<NUM>, the remaining power is allocated to the MAC entity corresponding to the mode <NUM>.

Optionally, if the P_max is less than a sum of the P_max <NUM> and the P_max2, it is defined that a MAC entity corresponding to the Mode <NUM> and a MAC entity corresponding to the Mode <NUM> perform one of the following four behaviors:.

Optionally, the P_max1 or the P_max2 may be further reduced based on a value P obtained by subtracting the P_max from the sum of the P_max1 and the P_max2.

The power value reduced for the P_max1 or the P_max2 may be equal to the foregoing obtained value P, or may be greater than the foregoing obtained value P.

(<NUM>) The P_max1 and the P_max2 are reduced based on a second preset proportion.

In this implementation, the second preset proportion may be prestored. Specifically, for example, the second preset proportion may be <NUM>:<NUM> or <NUM>:<NUM>.

The total power value reduced for the P_max1 or the P_max2 may be equal to the foregoing obtained value P, or may be greater than the foregoing obtained value P.

(<NUM>) The P_max1 or the P_max2 is reduced based on a size relationship between a priority of to-be-transmitted data and a second preset threshold.

Specifically, for example, if the priority of the to-be-transmitted data is greater than or equal to the second preset threshold, the P_max2 is reduced; or if the priority of the to-be-transmitted data is less than the second preset threshold, the P_max1 is reduced.

In this implementation, the to-be-transmitted data may be specifically transmitted by using a MAC entity for which power is not reduced.

(<NUM>) The P_max1 or the P_max2 is reduced based on a size relationship between a priority P<NUM> of to-be-transmitted data corresponding to the Mode <NUM> and a priority P<NUM> of to-be-transmitted data corresponding to the Mode <NUM>.

Specifically, for example, if P<NUM> is greater than or equal to P<NUM>, the P_max2 is reduced; or if P<NUM> is less than P<NUM>, the P_max1 is reduced.

For the foregoing several embodiments, optionally, the performing configuration based on first configuration information in step S102 may include: if a first resource corresponding to the Mode <NUM> conflicts with a second resource corresponding to the Mode <NUM>, selecting a resource according to at least one of the following rules:.

Specifically, for example, if the priority of the to-be-transmitted data is greater than or equal to the third preset threshold, the first resource is used; or if the priority of the to-be-transmitted data is less than the third preset threshold, the second resource is used.

In this implementation, the to-be-transmitted data may be specifically transmitted by using a resource selected after a resource conflict occurs.

(<NUM>) It is determined, based on a size relationship between a priority P<NUM> of to-be-transmitted data corresponding to the Mode <NUM> and a priority P<NUM> of to-be-transmitted data corresponding to the Mode <NUM>, to use the first resource or the second resource.

Specifically, for example, if P<NUM> is greater than or equal to P<NUM>, the first resource is used; or if P<NUM> is less than P<NUM>, the second resource is used.

For the foregoing several embodiments, optionally, the performing configuration based on first configuration information in step S102 may further include: defining that the terminal device performs at least one of the following behaviors:.

The SL transmission method according to some embodiments of the present disclosure is described above in detail with reference to <FIG>. An SL transmission method according to another embodiment of the present disclosure is described in detail below with reference to <FIG>. It may be understood that interaction between a network device and a terminal device described on the network device side is the same as that described on the terminal device side in the method shown in <FIG>. To avoid repetition, related descriptions are appropriately omitted.

<FIG> is a schematic flowchart of implementing an SL transmission method according to some embodiments of the present disclosure, and the method may be applied to a network device side. As shown in <FIG>, the method <NUM> includes the following step.

S502: Send first configuration information, where the first configuration information is used to instruct a terminal device to configure a resource allocation mode, and the resource allocation mode includes a Mode <NUM> and a Mode <NUM>.

The SL transmission method according to some embodiments of the present disclosure is described above in detail with reference to <FIG>. A terminal device according to some embodiments of the present disclosure is described in detail below with reference to <FIG>.

<FIG> is a schematic structural diagram of a terminal device according to some embodiments of the present disclosure. As shown in <FIG>, a terminal device <NUM> includes:
a configuration module <NUM>, configured to perform configuration based on first configuration information, so that the terminal device simultaneously works in both a Mode <NUM> and a Mode <NUM>.

In some embodiments of the present disclosure, the terminal device may perform related configuration based on configuration information, so that the terminal device can work in both the Mode <NUM> and the Mode <NUM> during SL transmission. The terminal device has diversified resource allocation modes, so that resource utilization efficiency of SL transmission can be improved, and different QoS requirements can be met.

Optionally, in an embodiment, the first configuration information includes at least one of the following:.

According to the present disclosure, the Mode <NUM> and the Mode <NUM> share a MAC entity, and the configuration module <NUM> is specifically configured to:
define that the MAC entity performs at least one of the following behaviors:.

Optionally, in an embodiment, the Mode <NUM> and the Mode <NUM> share a MAC entity, and the configuration module <NUM> may be specifically configured to:
define that the shared MAC entity performs the following behavior:.

Optionally, in an embodiment, the configuration module <NUM> may be further configured to:
perform configuration based on second configuration information, so that the terminal device works in the Mode <NUM> or the Mode <NUM>.

Optionally, in an embodiment, the Mode <NUM> and the Mode <NUM> share a MAC entity, and the configuration module <NUM> may be specifically configured to:
define that the MAC entity performs at least one of the following behaviors:.

Optionally, in an embodiment, the Mode <NUM> and the Mode <NUM> correspond to different MAC entities, and the configuration module <NUM> may be configured to:.

Optionally, in an embodiment, the Mode <NUM> and the Mode <NUM> correspond to different MAC entities, and the configuration module <NUM> may be configured to:
if the P_max is greater than a sum of the P_max1 and the P_max2, define that a MAC entity corresponding to the Mode <NUM> and a MAC entity corresponding to the Mode <NUM> perform one of the following four behaviors:.

Optionally, in an embodiment, the Mode <NUM> and the Mode <NUM> correspond to different MAC entities, and the configuration module <NUM> may be configured to: if the P_max is less than a sum of the P_max1 and the P_max2, define that a MAC entity corresponding to the Mode <NUM> and a MAC entity corresponding to the Mode <NUM> perform one of the following four behaviors:.

Optionally, in an embodiment, the configuration module <NUM> may be specifically configured to:
if a first resource corresponding to the Mode <NUM> conflicts with a second resource corresponding to the Mode <NUM>, select a resource according to at least one of the following rules:.

Optionally, in an embodiment, the configuration module <NUM> may be specifically configured to:
define that the terminal device <NUM> performs at least one of the following:.

Optionally, in an embodiment, the first configuration information is obtained in at least one of the following manners:.

For the terminal device <NUM> according to some embodiments of the present disclosure, reference may be made to the corresponding procedure of the method <NUM> according to some embodiments of the present disclosure, and the units/modules in the terminal device <NUM> and the foregoing operations and/or functions are respectively for implementing the corresponding procedures of the method <NUM>. For brevity, details are not described herein again.

<FIG> is a schematic structural diagram of a network device according to some embodiments of the present disclosure. As shown in <FIG>, a network device <NUM> includes:
a sending module <NUM>, configured to send first configuration information, where the first configuration information is used to instruct a terminal device to configure a resource allocation mode, and the resource allocation mode includes a Mode <NUM> and a Mode <NUM>.

The network device <NUM> according to some embodiments of the present disclosure may be corresponding to the procedure of the method <NUM> in some embodiments of the present disclosure, and the units/modules in the network device <NUM> and the foregoing operations and/or functions are respectively for implementing the corresponding procedures of the method <NUM>. For brevity, details are not described herein again.

<FIG> is a block diagram of a terminal device according to another embodiment of the present disclosure. As shown in <FIG>, a terminal device <NUM> includes: at least one processor <NUM>, a memory <NUM>, at least one network interface <NUM>, and a user interface <NUM>. All components of the terminal device <NUM> are coupled together by using the bus system <NUM>. It can be understood that the bus system <NUM> is configured to implement connection and communication between these components. In addition to a data bus, the bus system <NUM> may include a power bus, a control bus, and a status signal bus. However, for clear description, various buses are marked as the bus system <NUM> in <FIG>.

The user interface <NUM> may include a display, a keyboard, or a clicking device (for example, a mouse, a trackball (trackball)), a touch panel, or a touchscreen.

It may be understood that the memory <NUM> in some embodiments of the present disclosure may be a volatile memory or a nonvolatile memory, or may include both a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), used as an external cache. Through example but not limitative description, many forms of RAMs may be used, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (Synchlink DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DRRAM). The memory <NUM> in the system and the method described in some embodiments of the present disclosure is intended to include, but is not limited to, these memories and memories of any other proper type.

In some implementations, the memory <NUM> stores the following element: an executable module or a data structure, a subset thereof, or an extended set thereof: an operating system <NUM> and an application <NUM>.

The operating system <NUM> includes various system programs, such as a framework layer, a core library layer, and a driver layer, and is configured to implement various basic services and process hardware-based tasks. The application <NUM> includes various applications, for example, a media player (Media Player) and a browser (Browser), and is configured to implement various application services. A program for implementing the method in some embodiments of the present disclosure may be included in the application <NUM>.

In some embodiments of the present disclosure, the terminal device <NUM> further includes a program that is stored in the memory <NUM> and executable on the processor <NUM>, and when the processor <NUM> executes the program, the following steps of the method <NUM> are implemented.

The methods disclosed in some embodiments of the present disclosure may be applied to the processor <NUM> or implemented by the processor <NUM>. The processor <NUM> may be an integrated circuit chip having a signal processing capability. During implementation, each step of the foregoing method may be completed by using an integrated logic circuit of hardware in the processor <NUM> or an instruction in a form of software. The foregoing processor <NUM> may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic component, a discrete gate or a transistor logic component, or a discrete hardware component. The processor <NUM> may implement or execute the methods, steps, and logic block diagrams disclosed in some embodiments of the present disclosure. The general-purpose processor may be a microprocessor or may be any conventional processor or the like. The steps of the method disclosed in some embodiments of the present disclosure may be directly performed by a hardware decoding processor or by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature computer-readable storage medium in this field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, or a register. The computer-readable storage medium is located in the memory <NUM>, and the processor <NUM> reads information in the memory <NUM> and completes the steps in the foregoing method in combination with hardware of the processor <NUM>. Specifically, the computer-readable storage medium stores a computer program, and when the computer program is executed by the processor <NUM>, the steps of the foregoing embodiment of method <NUM> are performed.

It can be understood that those embodiments described in some embodiments of the present disclosure can be implemented with hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, a processing unit may be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP Device, DSPD), programmable logic devices (Programmable Logic Device, PLD), field-programmable gate arrays (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors, or other electronic units or a combination thereof used to perform the functions in this application.

For implementation with software, the technology described in some embodiments of the present disclosure may be implemented by executing functional modules (for example, a process and a function) described in some embodiments of the present disclosure. Software codes can be stored in the memory and executed by the processor. The memory may be implemented in the processor or outside the processor.

The terminal device <NUM> can implement each process implemented by the terminal device in the foregoing embodiments. To avoid repetition, details are not described herein again.

Referring to <FIG> is a structural diagram of a network device applied to some embodiments of the present disclosure, and the network device can implement details of the method embodiment <NUM> and achieve a same effect. As shown in <FIG>, a network device <NUM> includes a processor <NUM>, a transceiver <NUM>, a memory <NUM>, and a bus interface.

In some embodiments of the present disclosure, the network device <NUM> further includes a program that is stored in the memory <NUM> and executable on the processor <NUM>, and when the processor <NUM> executes the program, the steps of the method <NUM> are implemented.

In <FIG>, a bus architecture may include any quantity of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor <NUM> and a memory represented by the memory <NUM> are interconnected. The bus architecture may further link various other circuits such as a peripheral device, a voltage regulator, and a power management circuit. These are well known in the art, and therefore are not further described in this specification. The bus interface provides an interface. The transceiver <NUM> may be a plurality of components. To be specific, the transceiver <NUM> includes a transmitter and a receiver, and provides a unit configured to communicate with various other apparatuses on a transmission medium.

The processor <NUM> is responsible for managing the bus architecture and common processing, and the memory <NUM> may store data used when the processor <NUM> performs an operation.

Some embodiments of the present disclosure further provide a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when a processor executes the computer program, the processes of the method embodiment <NUM> and the method embodiment <NUM> are implemented and a same technical effect can be achieved. To avoid repetition, details are not described herein again. The computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, or an optical disc.

It should be noted that, in this specification, the terms "include", "comprise", or their any other variant is intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements which are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. An element limited by "includes a. " does not, without more constraints, preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

Based on the descriptions of the foregoing implementations, a person skilled in the art may clearly understand that the method in the foregoing embodiment may be implemented by software in addition to a necessary universal hardware platform or by hardware only. In most circumstances, the former is a preferred implementation. Based on such an understanding, the technical solutions of the present disclosure essentially or the part contributing to the prior art may be implemented in a form of a software product. The computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the methods described in the embodiments of the present disclosure.

Claim 1:
A sidelink, SL, transmission method, performed by a terminal device and comprising:
performing (S102) configuration based on first configuration information, so that the terminal device simultaneously works in both a network device scheduling mode, Mode <NUM>, and a terminal device autonomous mode, Mode <NUM>; characterized in that
in a case that the Mode <NUM> and the Mode <NUM> share the MAC entity, the performing (S102) configuration based on first configuration information comprises:
defining that the MAC entity performs at least one of following behaviors:
if there is no buffer data in currently configured SL logical channels, triggering a sidelink buffer status report, SL BSR, in a case that an SL logical channel on which data arrives corresponds to the Mode <NUM>;
if there is buffer data in at least one of currently configured SL logical channels, triggering an SL BSR in a case that an SL logical channel on which data arrives has a higher logical channel priority and the SL logical channel on which data arrives corresponds to the Mode <NUM>; and
if a retransmission SL BSR timer expires, triggering an SL BSR in a case that there is buffer data in at least one of currently configured SL logical channels, and an SL logical channel corresponding to the retransmission SL BSR timer corresponds to the Mode <NUM>.