Wireless communication method and terminal device
By triggering a sidelink buffer status report and determining the need for a scheduling request based on specific information, terminal devices in communication systems can efficiently acquire sidelink resources, addressing the challenge of resource acquisition in sidelink transmission technology.
Patent Information
- Application Number
- JP2023168427
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-09-28
- Publication Date
- 2025-06-11
- Estimated Expiration
- 2039-04-04
AI Technical Summary
In communication systems supporting sidelink transmission technology, terminal devices face challenges in efficiently requesting and acquiring sidelink resources for data transmission.
The method involves a terminal device triggering a sidelink buffer status report (BSR) and determining, based on specific information, whether to trigger a scheduling request (SR) to request sidelink resources.
This approach ensures that terminal devices can effectively obtain the necessary sidelink resources to meet transmission requirements, enhancing the efficiency and reliability of sidelink communication.
Smart Images
Figure 0007691467000001 
Figure 0007691467000002 
Figure 0007691467000003
Abstract
Description
Technical Field
[0001] Embodiments of the present application relate to the field of communications, and more specifically, to wireless communication methods and terminal devices.
Background Art
[0002] In a cellular communication system, a terminal device may trigger a Buffer State Report (BSR) to request uplink resources from a network device. If there is no uplink grant (UL grant), the terminal device may trigger a Scheduling Request (SR) to request uplink resources from the network device.
[0003] Device-to-device communication is a sidelink transmission technology based on Device-to-Device (D2D) technology. The Internet of Vehicles (IoV) system is a system based on D2D technology. Different from the conventional cellular communication system that needs to transmit and receive data through a network device, in the IoV system, it is possible to adopt a direct communication method of terminal-to-terminal, so it has higher spectral efficiency and lower transmission delay time.
[0004] In a communication system supporting sidelink transmission technology, a terminal device needs sidelink resources to perform sidelink communication. Therefore, for the terminal device, how to request sidelink resources is a problem that needs to be solved urgently.
Summary of the Invention
[0005] An embodiment of the present application provides a wireless communication method and a terminal device. When the terminal device needs to perform side data transmission, it triggers a sidelink buffer status report (BSR), and further determines whether a scheduling request (SR) is triggered based on the first information, so as to request sidelink resources.
[0006] The first aspect provides a wireless communication method. The wireless communication method includes: a first terminal triggering a sidelink buffer status report (BSR) to request sidelink resources for first side data to be transmitted; and the first terminal determining, based on first information, whether a scheduling request (SR) for requesting the sidelink resources is triggered.
[0007] The second aspect provides a terminal device for executing the method in any of the above first aspects or possible implementation forms of the first aspect. Specifically, this terminal device includes a unit for executing the method in any of the above first aspects or possible implementation forms of the first aspect.
[0008] The third aspect provides a terminal device including a processor and a memory. The memory stores a computer program, and the processor calls and executes the computer program stored in the memory to execute the method in the above first aspect or various implementation forms thereof.
[0009] The fourth aspect provides a chip for implementing the method in the above first aspect or its implementation form. Specifically, this chip includes a processor that calls and executes a computer program from a memory to cause the device on which the chip is implemented to execute the method in the above first aspect or its implementation form.
[0010] The fifth aspect provides a computer-readable storage medium storing a computer program for causing a computer to execute the method in the above first aspect or its various implementation aspects.
[0011] A sixth aspect provides a computer program product including computer program instructions for causing a computer to execute the method in the above first aspect or various embodiments thereof.
[0012] A seventh aspect provides a computer program which, when executed on a computer, causes the computer to execute the method in the above first aspect or its implementation form.
[0013] According to the above technical solution, when the terminal device needs to transmit sidelink data, it can trigger the sidelink BSR, and further, based on the first information, it can determine whether the SR is triggered, which is advantageous for ensuring that the required sidelink resources can meet the actual transmission requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0014]
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
[0015] Hereinafter, the technical solution in the embodiments of the present application will be described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, not all of them. All other embodiments obtained by those skilled in the art without creative efforts based on the embodiments in the present application belong to the protection scope of the present application.
[0016] The technical solution of the embodiment of the present application may be applied to, for example, a vehicle Internet system that performs D2D communication based on Long Term Evolution (LTE), or a device-to-device (D2D) communication system such as a new radio vehicle-to-everything (NR-V2X) system. It should be understood that, different from the method in which communication data between terminals in a conventional LTE system is received or transmitted by a network device (for example, a base station), the vehicle Internet system adopts a direct communication method of terminal-to-terminal, and thus has higher spectral efficiency and lower transmission delay time.
[0017] Optionally, the communication system on which the vehicle Internet system is based may be a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), an LTE system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a 5G New Radio (NR) system, etc.
[0018] The terminal device in the embodiments of the present application may be a terminal device capable of realizing D2D communication. For example, the terminal device may be an in-vehicle terminal device, or may be a terminal device in a 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., but the embodiments of the present application are not limited thereto.
[0019] FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the wireless communication system in the embodiments of the present application may include a plurality of network devices, and each network device's coverage may include other numbers of terminal devices, and the embodiments of the present application are not limited thereto.
[0020] Optionally, the wireless communication system may further include other network entities such as a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a Packet Data Network Gateway (P-GW), or the wireless communication system may further include other network entities such as a Session Management Function (SMF), a Unified Data Management (UDM), and an Authentication Server Function (AUSF), and the embodiments of the present application are not limited thereto.
[0021] In the in-vehicle Internet system, the terminal device can communicate by adopting mode A and mode B.
[0022] Specifically, the terminal device 121 and the terminal device 122 can communicate in the D2D communication mode. When performing D2D communication, the terminal device 121 and the terminal device 122 communicate directly via a D2D link, that is, a side link (SL). Here, in mode A, the transmission resources of the terminal device are allocated by the base station, and the terminal device may transmit data on the SL based on the resources allocated by the base station. The base station may allocate single-transmission resources to the terminal device, or may allocate semi-static transmission resources to the terminal device. In mode B, the terminal device adopts a sensing and reservation transmission method, and the terminal device autonomously selects transmission resources on the SL resources. Specifically, the terminal device obtains a set of available transmission resources in the resource pool in a sensing manner, and the terminal device randomly selects one resource from the set of available transmission resources to perform data transmission.
[0023] It should be understood that the above mode A and mode B are only exemplary explanations of two types of transmission modes, and it is possible to define other transmission modes. For example, mode C and mode D are introduced into NR-V2X. Here, mode C indicates that the side link transmission resources of the terminal device are allocated by the base station, and mode D indicates that the side link transmission resources of the terminal device are selected by the terminal.
[0024] D2D communication can refer to Vehicle to Vehicle (simply referred to as "V2V") communication or communication from a vehicle to other devices (Vehicle to Everything, V2X: Vehicle to Vehicle / vehicle to infrastructure communication). In V2X communication, X can broadly refer to any device with wireless reception and transmission capabilities, such as, for example, a wireless device moving at a low speed, an in-vehicle device moving at a high speed, or a network control node with wireless transmission and reception capabilities, but is not limited thereto. Embodiments of the present invention are mainly applicable to scenarios of V2X communication, but may also be applicable to any other D2D communication scenario, and it should be understood that the embodiments of the present application do not limit this in any way.
[0025] In this specification, it should be understood that the terms "system" and "network" are often used interchangeably. Here, the so-called "and / or" refers to the relationship of simply explaining related objects, and there are three relationships such as A and / or B, which means there are three cases: the case of A alone, the case of both A and B, and the case of B alone. Also, " / " in the text generally indicates that the objects before and after are in an "or" relationship.
[0026] FIG. 2 is a schematic flowchart of a wireless communication method according to an embodiment of the present application. For example, this method is executed by terminal devices such as terminal device 121 and terminal device 122 in a vehicle's Internet system. As shown in FIG. 2, this method 200 includes the following steps.
[0027] In S210, the first terminal triggers a side link buffer status report BSR for requesting side link resources for the first sidelink data to be transmitted.
[0028] In S220, the first terminal determines whether a scheduling request SR for requesting the side link resources is triggered based on the first information.
[0029] Specifically, when the first terminal transmits side data to another terminal, such as the second terminal, it requires sidelink resources. If there are no sidelink resources, it is necessary to request sidelink resources from the network device. In this case, the terminal device may trigger a sidelink BSR, and the sidelink BSR may be used to request sidelink resources for the transmission of side data.
[0030] Optionally, in the embodiments of the present application, the first side data to be transmitted may be a logical channel that triggers the sidelink BSR, or a logical channel group (Logic Channel Group, LCG) that triggers the sidelink BSR.
[0031] That is, when it is necessary to transmit the data in the logical channel or the logical channel group to another terminal device, the first terminal may trigger a sidelink BSR.
[0032] In the embodiments of the present application, the first terminal triggers a sidelink BSR, and the sidelink BSR is in a pending state at this time. That is, it should be understood that the first terminal attempts to transmit the sidelink BSR to the network device but does not transmit it.
[0033] Optionally, the first side data may include data in a Data Radio Bearer (DRB) and / or data in a Signalling Radio Bearer (SRB).
[0034] Optionally, in some embodiments, the SRB may be used to bear sidelink Radio Resource Control (RRC) signalling and / or sidelink PC5 interface signalling (PC5 Signalling, PC5-S).
[0035] Optionally, in some embodiments, the QoS attribute of the SRB is set by a network device or preset.
[0036] Optionally, the QoS attribute of the SRB may include priority and, optionally, may further include other attributes such as time delay.
[0037] Optionally, in some embodiments, when the first terminal triggers a sidelink BSR, it can request sidelink resources by the SR by determining whether to trigger the SR based on the first information.
[0038] In the embodiments of the present application, if it is determined that the SR is triggered, it may not be necessary to transmit the sidelink BSR. After the first terminal transmits the SR to the network device, the network device may allocate sidelink resources to the first terminal. If the sidelink resources cannot meet the transmission requirements of sidelink data, for example, if the size of the sidelink resources is not sufficient to transmit the first sidelink data to be transmitted, the first terminal may further trigger the sidelink BSR and request sidelink resources from the network device via the sidelink BSR. It should be understood.
[0039] Optionally, in some embodiments, if the first terminal determines that the SR is not triggered, for example, if no uplink grant resource is set for the first terminal, the first terminal may further initiate a random access process and request an uplink grant resource from the network device.
[0040] Hereinafter, the triggering method of the SR will be described with reference to specific embodiments.
[0041] Optionally, as an embodiment, it is described as Embodiment 1, and the first information is Whether the first terminal has available sidelink resources for the first transmission and / or whether the available sidelink resources for the first transmission satisfy the transmission requirement of the first sidelink data may be included.
[0042] For example, if no available sidelink resources for the first transmission are configured for the first terminal, the first terminal may determine that SR is triggered and further send the SR to the network device.
[0043] Also, for example, if available sidelink resources for the first transmission are configured for the first terminal, the first terminal may determine that SR is not triggered.
[0044] Therefore, the first terminal may determine whether SR is triggered based on whether there are available sidelink resources for the first transmission (i.e., newly transmitted).
[0045] In some other embodiments, if available sidelink resources for the first transmission are configured for the first terminal, the first terminal may further determine whether SR is triggered based on whether the available sidelink resources satisfy the transmission requirement of the first sidelink data. In this way, it is advantageous to ensure that the required sidelink resources can satisfy the transmission requirement of the sidelink data.
[0046] For example, if available sidelink resources for the first transmission are configured for the first terminal, but the available sidelink resources cannot satisfy the transmission requirement of the first sidelink data to be transmitted, the first terminal may determine that SR is triggered and can further send the SR to the network device.
[0047] Or, when available sidelink resources for initial transmission are configured for the first terminal, but the available sidelink resources can satisfy the transmission requirement of the first sidelink data to be transmitted, the first terminal determines that SR is not triggered and can transmit the first sidelink data using the available sidelink resources.
[0048] By way of non-limiting example, the available sidelink resources being unable to satisfy the transmission requirement of the first sidelink data includes at least one of the following.
[0049] The available sidelink resources and the first sidelink data do not satisfy a first mapping relationship.
[0050] The available sidelink resources do not satisfy the time delay requirement of the first sidelink data.
[0051] The size of the available sidelink resources is not sufficient to transmit the first sidelink data.
[0052] Therefore, in the embodiments of the present application, when available link resources are configured for the first terminal, the first terminal can determine whether to satisfy the actual transmission requirement based on the attributes of the available link resources and determine whether SR is triggered. Thereby, when the available link resources do not satisfy the actual transmission requirement, SR is triggered and sidelink resources can be further requested by SR, which is advantageous for ensuring that the requested sidelink resources that can satisfy the actual transmission requirement are obtained.
[0053] In the embodiments of the present application, the situation where the available sidelink resources cannot meet the transmission requirements of the first sidelink data is only an example. The transmission requirements of the sidelink data may further include other parameters that affect the transmission performance, such as Quality-of-Service (QoS) requirements, priorities, reliability requirements, etc. It should be understood that the embodiments of the present application are not specifically limited thereto.
[0054] Optionally, in some embodiments, the first mapping relationship may be a mapping relationship between the sidelink data that triggers the sidelink BSR and the attributes of the sidelink resources.
[0055] For example, the first mapping relationship may be a relationship between the logical channel or logical channel group that triggers the sidelink BSR and the attributes of the sidelink resources.
[0056] That is, the sidelink data that triggers the sidelink BSR needs to correspond to sidelink resources with specific attributes. When the attributes of the available sidelink resources are different from the attributes of the sidelink resources mapped to the first sidelink data, the available sidelink resources and the first sidelink data do not satisfy the first mapping relationship. In this case, the first terminal may trigger an SR and can further request through the SR to meet the sidelink resources, which is advantageous for requesting sidelink resources with specific attributes that satisfy the first mapping relationship.
[0057] Optionally, in some embodiments, if a sidelink resource available for initial transmission is set for the first terminal, the first terminal may further refer to the current packetization status of the data and determine whether to trigger the SR. For example, if the packetization of the data is completed, that is, if the BSR cannot be packetized again into the data packet, in this case, the first terminal can trigger the SR. Specifically, it may transmit a (Physical Uplink Control Channel, PUCCH) to the network device, and the SR can be transmitted to the network device by the PUCCH.
[0058] Optionally, as another embodiment, described in Embodiment 2, the first information may also include at least one of the following.
[0059] Whether the first terminal has available Physical Uplink Control Channel (PUCCH) resources and / or information on SR collision data.
[0060] Optionally, the PUCCH resource is a PUCCH resource to which a logical channel or logical channel group corresponding to the first sidelink data is mapped.
[0061] The following relates to Embodiments 3 to 9 and describes specific implementation forms of Embodiment 2.
[0062] Embodiment 3: The first terminal determines whether to trigger the SR based on whether available PUCCH resources are set for the first terminal.
[0063] The SR may be transmitted by a PUCCH resource. In some specific embodiments, the first terminal determines whether the SR is triggered based on whether a PUCCH resource available to the first terminal is configured. For example, the first terminal may determine that the SR is triggered if a PUCCH resource is configured, or may determine that the SR is not triggered if no PUCCH resource is configured.
[0064] Embodiment 4: The first terminal may determine whether the SR is triggered based on information about collision data of the SR.
[0065] By way of example and not limitation, the information about the collision data of the SR includes whether there is uplink data to be transmitted that collides with the SR; the importance level of the uplink data that collides with the SR; the transmission requirement of the uplink data that collides with the SR; whether there is sidelink data to be transmitted that collides with the SR; and includes at least one of the transmission requirements of the sidelink data that collides with the SR.
[0066] Generally speaking, the first terminal may transmit only uplink data or sidelink data at the same time. Therefore, in the embodiments of the present application, the first terminal may determine whether the SR is triggered based on whether there is uplink data and / or sidelink data to be transmitted that collides with the SR at present, or when there is uplink data and / or sidelink data to be transmitted, the first terminal may further refer to the attributes of the uplink data and / or sidelink data to be transmitted to determine whether the SR is triggered.
[0067] Relating to Embodiments 5 to 9, specific implementation forms of Embodiment 4 are described.
[0068] Embodiment 5: The first terminal determines whether the SR is triggered based on whether there is uplink data to be transmitted that collides with the SR.
[0069] For example, when there is uplink data to be transmitted that collides with the SR, the first terminal may determine that the SR is not triggered, or when there is no uplink data to be transmitted that collides with the SR, the first terminal may determine that the SR is triggered.
[0070] Embodiment 6: The first terminal determines whether the SR is triggered based on the importance level of the uplink data to be transmitted that collides with the SR.
[0071] For example, when the importance level of the uplink data is lower than the importance level of the first sidelink data, the first terminal may determine that the SR is triggered, that is, the SR may be preferentially transmitted to request the sidelink resources of the first sidelink data. In this case, it may be considered that the importance level of the SR is higher than the importance level of the uplink data, or the priority of the SR is higher than the priority of the uplink data.
[0072] Also, for example, when the importance level of the uplink data is lower than a specific importance level threshold, the first terminal may determine that the SR is triggered, that is, the SR may be preferentially transmitted to request the sidelink resources of the first sidelink data.
[0073] It may be considered that the importance level of the uplink message in the random access process is high. In some specific embodiments, when the uplink data is not the uplink message in the random access process, the first terminal may determine that the SR is triggered.
[0074] Optionally, the uplink message in the random access process is Message 3 (MSG3) for requesting uplink resources in the random access process.
[0075] In Embodiment 7, the first terminal determines whether the SR is triggered based on a transmission request for uplink data to be transmitted that collides with the SR.
[0076] For example, if the transmission request for the uplink data is higher than the transmission request for the first side data, that is, if the uplink data needs to be transmitted preferentially, in this case, even if the priority of the SR is considered to be lower than the priority of the uplink data, the first terminal may determine that the SR is not triggered and may preferentially transmit the uplink data.
[0077] Or, if the transmission request for the uplink data is lower than the transmission request for the first side data, that is, if the first side data needs to be transmitted preferentially, in this case, even if the priority of the SR is considered to be higher than the priority of the uplink data, the first terminal may determine that the SR is triggered and may preferentially transmit the SR so as to request a side link resource for transmitting the first side data.
[0078] Also, for example, if the transmission request for the uplink data is lower than a threshold value of the transmission request, in this case, even if the priority of the SR is considered to be higher than the priority of the uplink data, the first terminal may determine that the SR is triggered and may preferentially transmit the SR so as to request a side link resource for transmitting the first side data.
[0079] Or, if the transmission request for the uplink data is higher than a threshold value of a specific transmission request, in this case, even if the priority of the SR is considered to be lower than the priority of the uplink data, the first terminal may determine that the SR is not triggered and may preferentially transmit the uplink data.
[0080] By way of example and not limitation, the transmission request may be a time delay request, a QoS request, a reliability request, etc., and correspondingly, the threshold value of the transmission request may be a threshold value of the time delay request, a threshold value of the QoS request, a threshold value of the reliability request, etc.
[0081] Optionally, in some embodiments, the fact that the transmission requirement of the uplink data is lower than that of the first side data means that the priority of the uplink data is lower than that of the first side data, the quality of service (QoS) requirement of the uplink data is lower than the QoS requirement of the first side data, the QoS requirement of the uplink data is a QoS requirement in a first set of QoS requirements, and at least one of the fact that the latency requirement of the uplink data is lower than the latency requirement of the first side data.
[0082] Optionally, the first set of QoS requirements may be preset or set by a network device.
[0083] For example, the network device may set one or more QoS requirements to form the first set of QoS requirements. Optionally, the QoS requirements in the first QoS set are lower than a threshold of a specific QoS requirement.
[0084] The QoS requirements in the first set of QoS requirements may be considered as low-priority QoS requirements. When the QoS requirement of the uplink data is a QoS requirement in the first set of QoS requirements, the first terminal may determine that the SR is triggered.
[0085] Optionally, in some embodiments, the fact that the latency requirement of the uplink data is lower than the latency requirement of the first side data includes that the uplink data does not include voice call data.
[0086] Therefore, when there is uplink data that collides with the SR, the first terminal may further refer to the transmission request of the uplink data to determine whether the SR is triggered. For example, when the transmission request of the uplink data is lower than the transmission request of the first side data, the SR may be preferentially transmitted so as to request side link resources for the first side data, or when the transmission request of the uplink data is higher than the transmission request of the first side data, the uplink data may be preferentially transmitted so as to satisfy the transmission request of the uplink data.
[0087] Embodiment 8: The first terminal determines whether the SR is triggered based on whether there is side data to be transmitted that collides with the SR.
[0088] For example, when there is side data to be transmitted that collides with the SR, the first terminal may determine that the SR is not triggered, or when there is no side data to be transmitted that collides with the SR, the first terminal may determine that the SR is triggered.
[0089] Embodiment 9: The first terminal determines whether the SR is triggered based on the transmission request of the second side data to be transmitted that collides with the SR.
[0090] For example, when the transmission request of the second side data is higher than the transmission request of the first side data, that is, when the second side data needs to be preferentially transmitted, in this case, it may be considered that the priority of the SR is lower than the priority of the second side data, and the first terminal may determine that the SR is not triggered and preferentially transmit the second side data.
[0091] Or, when the transmission requirement of the second side data is lower than that of the first side data, that is, when the first side data needs to be preferentially transmitted, in this case, it may be considered that the priority of the SR is higher than that of the second side data. The first terminal may determine that the SR is triggered and preferentially transmit the SR so as to request side link resources for the first side data.
[0092] Also, for example, when the transmission requirement of the second side data is lower than the transmission requirement threshold, in this case, it may be considered that the priority of the SR is higher than that of the second side data. The first terminal may determine that the SR is triggered and preferentially transmit the SR so as to request side link resources for the first side data.
[0093] Or, when the transmission requirement of the second side data is higher than a specific transmission requirement threshold, in this case, it may be considered that the priority of the SR is lower than that of the second side data. The first terminal may determine that the SR is not triggered and preferentially transmit the second side data so as to meet the transmission requirement of the second side data.
[0094] By way of example and not limitation, the transmission requirement may be a time delay requirement, a QoS requirement, a reliability requirement, etc. Correspondingly, the transmission requirement threshold may be a time delay requirement threshold, a QoS requirement threshold, a reliability requirement threshold, etc.
[0095] Optionally, in some embodiments, the fact that the transmission requirement of the second side data is lower than that of the first side data means that the priority of the second side data is lower than that of the first side data, the QoS requirement of the second side data is lower than that of the first side data, the time delay requirement of the second side data is lower than that of the first side data, The QoS requirement of the second side data includes at least one of the QoS requirements in the second QoS requirement set.
[0096] Optionally, the second QoS requirement set is preset or set by a network device.
[0097] For example, the network device may set one or more QoS requirements to form the second QoS requirement set. Optionally, the QoS requirement in the second QoS set is lower than a threshold of a specific QoS requirement.
[0098] The QoS requirement in the second QoS requirement set may be considered as a QoS requirement with a low priority. When the QoS requirement of the side data is a QoS requirement in the second QoS requirement set, the first terminal may determine to trigger the SR.
[0099] Therefore, when the first terminal has second side data that collides with the SR, the first terminal may further refer to the transmission requirement of the second side data to determine whether to trigger the SR. For example, when the transmission requirement of the second side data is lower than the transmission requirement of the first side data, the first terminal may preferentially transmit the SR to request side link resources for the first side data, or when the transmission requirement of the second side data is higher than the transmission requirement of the first side data, the first terminal may preferentially transmit the second side data to preferentially satisfy the transmission requirement of the second side data.
[0100] It should be understood that the above embodiments may be implemented individually or in combination, and the embodiments of the present application are not limited thereto. For example, when there is a PUCCH resource, the first terminal may further implement Embodiments 4 to 9. For example, when there is an available PUCCH resource, the first terminal may further determine whether the SR is triggered based on the information of the SR collision data. For example, the first terminal may refer to the importance level and transmission requirements of the uplink data that collides with the SR to determine whether the SR is triggered. For example, when the uplink data is an uplink message in the random access process, the first terminal may determine that the SR is triggered, or when the uplink data is not an uplink message in the random access process, the first terminal may further aggregate the transmission requirements of the uplink data to determine whether the SR is triggered. The embodiments of the present application do not limit such matters.
[0101] Note that the first information may only include the content included in the first information in Embodiment 1, may only include the content included in the first information in Embodiment 2, or may include both of the above. The embodiments of the present application are not limited thereto.
[0102] Therefore, according to the wireless communication method according to the embodiments of the present application, the first terminal may determine whether the SR is triggered based on information such as the status of available sidelink resources, the status of available PUCCH resources, and the status of data that collides with the SR, which is advantageous for ensuring that new sidelink resources are requested by the SR when the currently available sidelink resources do not meet the requirements.
[0103] As described above, the wireless communication method according to the embodiments of the present application has been described in detail from the perspective of the first terminal with reference to FIG. 2. Hereinafter, the embodiments of the apparatus of the present application will be described in detail with reference to FIGS. 3 to 5. The embodiments of the apparatus and the embodiments of the method correspond to each other, and for similar descriptions, reference may be made to the embodiments of the method.
[0104] FIG. 3 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 3, the device 400 includes a trigger module 410 for triggering a side link buffer status report BSR for requesting side link resources for the first side data to be transmitted, and a determination module 420 for determining that a scheduling request SR for requesting the side link resources is triggered based on the first information.
[0105] Optionally, in some embodiments, the first information includes whether the terminal device has available side link resources for the first transmission and / or whether the available side link resources for the first transmission satisfy the transmission request of the first side data.
[0106] Optionally, in some embodiments, the determination module 420 specifically is used to determine that the SR is triggered when at least one of the following conditions is satisfied: the terminal device does not have available side link resources for the first transmission; the terminal device has available side link resources for the first transmission and the available side link resources cannot satisfy the transmission request of the first side data; the terminal device has available side link resources for the first transmission and the packetization of the data has already been completed.
[0107] Optionally, in some embodiments, the fact that the available side link resources cannot satisfy the transmission request of the first side data means that the available side link resources and the first side data do not satisfy a first mapping relationship. including at least one of the fact that the available sidelink resources do not meet the time delay requirement of the first sidelink data.
[0108] Optionally, in some embodiments, the first mapping relationship is a mapping relationship between the sidelink data that triggers the sidelink BSR and the attributes of the sidelink resources.
[0109] Optionally, in some embodiments, the first information includes whether the terminal device has available physical uplink control channel PUCCH resources and / or information on the collision data of the SR.
[0110] Optionally, in some embodiments, the information on the collision data of the SR includes whether there is uplink data to be transmitted that collides with the SR; the importance level of the uplink data that collides with the SR; the transmission requirement of the uplink data that collides with the SR; includes whether there is sidelink data to be transmitted that collides with the SR; and at least one of the transmission requirements of the sidelink data that collides with the SR.
[0111] Optionally, in some embodiments, the determination module 420 specifically includes that the terminal device has available physical uplink control channel PUCCH resources, the terminal device does not have uplink data to be transmitted that collides with the SR, the terminal device has uplink data to be transmitted that collides with the SR and the importance level of the uplink data is lower than the importance level of the SR, the terminal device has uplink data to be transmitted that collides with the SR and the transmission requirement of the uplink data is lower than the transmission requirement of the first sidelink data, the terminal device does not have second sidelink data to be transmitted that collides with the SR. When at least one of the conditions that the terminal device has second side data to be transmitted that collides with the SR and that the transmission request for the second side data is lower than the transmission request for the first side data is satisfied, it is used to determine that the SR is triggered.
[0112] Optionally, in some embodiments, the fact that the importance level of the uplink data is lower than the importance level of the SR includes that the uplink data does not include uplink messages in the random access process.
[0113] Optionally, in some embodiments, the uplink message is Message 3 for requesting uplink resources in the random access process.
[0114] Optionally, in some embodiments, the fact that the transmission request for the uplink data is lower than the transmission request for the first side data includes that the priority of the uplink data is lower than the priority of the first side data, that the quality of service QoS requirement for the uplink data is lower than the QoS requirement for the first side data, that the QoS requirement for the uplink data is a QoS requirement in a first QoS requirement set, and that the time delay requirement for the uplink data is lower than the time delay requirement for the first side data.
[0115] Optionally, in some embodiments, the first QoS requirement set is preset or set by a network device.
[0116] Optionally, in some embodiments, the QoS requirement in the first QoS set is lower than a threshold of a specific QoS requirement.
[0117] Optionally, in some embodiments, the uplink data having a lower time delay requirement than the first side data includes that the uplink data does not include voice call data.
[0118] Optionally, in some embodiments, the transmission requirement of the second side data being lower than the transmission requirement of the first side data includes at least one of: the priority of the second side data being lower than the priority of the first side data; the QoS requirement of the second side data being lower than the QoS requirement of the first side data; the time delay requirement of the second side data being lower than the time delay requirement of the first side data; and the QoS requirement of the second side data being a QoS requirement in a second QoS requirement set.
[0119] Optionally, in some embodiments, the second QoS set is preset or set by a network device.
[0120] Optionally, in some embodiments, the QoS requirements in the second QoS set are lower than a threshold of specific QoS requirements.
[0121] Optionally, in some embodiments, the PUCCH resource is a PUCCH resource mapped to a logical channel or a logical channel group corresponding to the first side data.
[0122] Optionally, in some embodiments, the first side data for triggering the sidelink BSR includes at least one of the logical channel for triggering the sidelink BSR and the logical channel group for triggering the sidelink BSR.
[0123] Optionally, in some embodiments, the first side data includes data in a data radio bearer (DRB) and / or data in a signaling radio bearer (SRB).
[0124] Optionally, in some embodiments, the SRB is used to bear side link radio resource control (RRC) signaling and / or side link PC5 interface signaling (PC5-S).
[0125] Optionally, in some embodiments, the QoS attribute of the SRB is set by a network device or preset.
[0126] Optionally, the QoS attribute of the SRB may include a priority, and optionally may further include other attributes such as a time delay.
[0127] The terminal device 400 according to the embodiments of the present application can correspond to the first terminal in the method embodiments of the present application. It should be understood that the above and other operations and / or functions of each part of the terminal device 400 respectively implement the corresponding flow of the first terminal in the method 200 shown in FIG. 2, and for the sake of brevity, the description is omitted here.
[0128] FIG. 4 is a schematic configuration diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in FIG. 4 has a processor 610 that realizes the method in the embodiments of the present application by calling and executing a computer program from a memory.
[0129] Optionally, as shown in FIG. 4, the communication device 600 may further include a memory 620. Here, the processor 610 realizes the method in the embodiments of the present application by calling and executing a computer program from the memory 620.
[0130] Here, the memory 620 may be a separate component independent of the processor 610, or may be integrated into the processor 610.
[0131] Optionally, as shown in FIG. 4, the communication device 600 may further include a transceiver 630 that can control the processor 610 to communicate with other devices. Specifically, it can transmit information or data to other devices or receive information or data transmitted by other devices.
[0132] Here, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include one or more antennas.
[0133] Optionally, this communication device 600 may be the first terminal in the embodiments of the present application. The communication device 600 may also implement the corresponding flow implemented by the first terminal in various methods of the embodiments of the present application. For the sake of brevity, detailed descriptions are omitted here.
[0134] FIG. 5 is a schematic configuration diagram of a chip in the embodiments of the present application. The chip 700 shown in FIG. 5 includes a processor 710 that can execute the method in the embodiments of the present application by calling and executing a computer program from a memory.
[0135] Optionally, as shown in FIG. 5, the chip 700 may further include a memory 720. Here, the processor 710 can realize the method in the embodiments of the present application by calling and executing a computer program from the memory 720.
[0136] Here, the memory 720 may be a separate component independent of the processor 710, or may be integrated into the processor 710.
[0137] Optionally, this chip 700 may further include an input interface 730. Here, the processor 710 may control the input interface 730 to communicate with other devices or chips. Specifically, the processor 710 may obtain information or data transmitted by other devices or chips.
[0138] Optionally, this chip 700 may further include an output interface 740. Here, the processor 710 may control the output interface 740 to communicate with other devices or chips. Specifically, the processor 710 may output information or data to other devices or chips.
[0139] Optionally, this chip may be applied to the first terminal in the embodiments of the present application. This chip may implement the corresponding flows implemented by the first terminal in various methods of the embodiments of the present application. For the sake of brevity, the description is omitted here. It should be understood that the chip referred to in the embodiments of the present application may also be referred to as a system-level chip, a system-on-chip, a chip system, or a system-on-chip, etc.
[0140] It is understood that the processor of the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above-described method embodiment may be executed by the integrated logic circuit of the hardware in the processor or instructions in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an existing field programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor, and the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application can be embodied as directly as hardware decoding processor execution or as executed by a combination of hardware and software modules in the decoding processor. The software module can be set in a storage medium familiar to those skilled in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and executes the steps of the above-described method together with the hardware The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. Here, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM) used as an external cache. By way of example and not limitation, RAM is available in many forms such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM).The memory of the systems and methods described herein is intended to include these and any other suitable types of memory, but it should be noted that it is not limited thereto. The above memory is exemplary rather than limiting. For example, in the embodiments of the present application, the memory may be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synch link DRAM (SLDRAM), and direct rambus RAM (DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include these and any other suitable types of memory, but is not limited thereto.
[0141] The embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
[0142] Optionally, the computer-readable storage medium may be applied to the network devices in the embodiments of the present application. The computer program causes the computer to execute the corresponding flows implemented by the network devices in each method of the embodiments of the present application, and the description is omitted here for the sake of brevity.
[0143] Optionally, the computer-readable storage medium may be applied to the mobile terminals / terminal devices in the embodiments of the present application. The computer program causes the computer to execute the corresponding flows implemented by the mobile terminals / terminal devices in each method of the embodiments of the present application, and the description is omitted here for the sake of brevity.
[0144] Embodiments of the present application also provide a computer program product including computer program instructions.
[0145] Optionally, the computer program product may be applied to a network device in an embodiment of the present application. The computer program instructions cause a computer to execute corresponding flows implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, the description is omitted here.
[0146] Optionally, the computer program product may be applied to a mobile terminal / terminal device in an embodiment of the present application. The computer program instructions cause a computer to execute corresponding flows implemented by the mobile terminal / terminal device in each method of the embodiments of the present application. For the sake of brevity, the description is omitted here. Embodiments of the present application also provide a computer program.
[0147] Optionally, this computer program may be applied to a network device in an embodiment of the present application. When the computer program is executed on a computer, the computer program causes a computer to execute corresponding flows implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, the description is omitted here.
[0148] Optionally, this computer program may be applied to a mobile terminal / terminal device in an embodiment of the present application. When the computer program is executed on a computer, the computer program causes a computer to execute corresponding flows implemented by the mobile terminal / terminal device in each method of the embodiments of the present application. For the sake of brevity, the description is omitted here.
[0149] Those skilled in the art will recognize that the various example units and algorithm steps described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. These functions depend on whether they are executed by hardware or software according to the specific application examples and design constraints of the technical solution. Those skilled in the art may use different methods for each specific application to implement the described functions, but such implementations should not be considered as departing from the scope of this application.
[0150] For the sake of convenience and brevity of description, those skilled in the art may refer to the corresponding processes in the foregoing method embodiments for the specific operation processes of the systems, devices, and units described above, where the description thereof is omitted here.
[0151] In some of the embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the above-described device embodiments are merely illustrative. For example, the division of the above units is only a division of one logical function. In actual implementation, there may be other division methods. For example, a plurality of units or components may be combined, integrated into another system, or some features may be omitted or not executed. In other respects, the couplings or direct couplings or communication connections shown or discussed between each other may be indirect couplings or communication connections through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
[0152] The units described as the separation means may or may not be physically separated. The means for displaying as a unit may or may not be a physical unit, and may be in one place, or may be distributed in a plurality of network units. Also, the purpose of this embodiment can be implemented by selecting some or all of each part as needed.
[0153] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may physically exist separately, or two or more units may be integrated into one unit.
[0154] When the above function is realized in a software functional unit and sold or used as an independent product, it may be stored in a computer-readable recording medium. Based on such an understanding, the essence of the technical solution of the present application, the part that contributes to the prior art, or the part of the technical solution of the present application may be embodied in the form of a software product stored in a storage medium including a plurality of instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. Note that as the storage medium, various media capable of storing program codes such as USB disks, removable hard disks, ROMs, RAMs, magnetic disks, and optical disks can be used. As described above, specific embodiments of the present application have been described. However, the technical scope of the present application is not limited thereto. Of course, those having ordinary knowledge in the technical field to which the present application belongs can easily make changes and substitutions within the technical scope of the present application. Therefore, the protection scope of the present application should be defined by the scope of the patent claims.
Claims
1. The first terminal triggers a sidelink buffer status report BSR for requesting sidelink resources for first sidelink data to be transmitted, wherein the sidelink BSR is in a suspended state, and when the sidelink BSR is triggered, the first terminal determines, based on first information, whether a scheduling request SR for requesting the sidelink resources is to be triggered, wherein the first information includes whether there is uplink data to be transmitted that collides with the SR, and the priority of the uplink data that collides with the SR, triggering the SR for requesting the sidelink resources includes transmitting the SR preferentially over the uplink data to be transmitted, characterized in that it is a wireless communication method.
2. The wireless communication method further includes transmitting the SR to a network device characterized in that it is the wireless communication method according to claim 1.
3. The first information further includes whether the first terminal has available physical uplink control channel PUCCH resources, characterized in that it is the wireless communication method according to claim 1 or 2.
4. The first terminal determines, based on first information, whether a scheduling request SR for requesting the sidelink resources is to be triggered, which is when the first terminal does not have uplink data to be transmitted that collides with the SR, the first terminal determines that the SR is to be triggered, or when the first terminal has uplink data to be transmitted that collides with the SR and the priority of the uplink data is lower than the priority of the first sidelink data, the first terminal determines that the SR is to be triggered, characterized in that it is the wireless communication method according to claim 1.
5. A trigger module for triggering a sidelink buffer status report BSR for requesting sidelink resources for first sidelink data to be transmitted, wherein the sidelink BSR is in a suspended state, and a determination module for determining, based on first information, whether a scheduling request SR for requesting the sidelink resources is to be triggered when the sidelink BSR is triggered, wherein the first information Whether there is uplink data to be transmitted that collides with the SR, and the priority of the uplink data that collides with the SR, The triggering of the SR for requesting the sidelink resource includes that the SR is transmitted preferentially over the uplink data to be transmitted, A terminal device characterized by the above.
6. The determination module further, Is configured to transmit the SR to a network device, The terminal device according to claim 5, characterized in that.
7. The first information further, Whether the terminal device has available physical uplink control channel PUCCH resources, is included The terminal device according to claim 5 or 6, characterized in that.