WO2021232379A1

WO2021232379A1 - Scheduling request processing method, apparatus, and system

Info

Publication number: WO2021232379A1
Application number: PCT/CN2020/091667
Authority: WO
Inventors: 李国荣; 贾美艺; 张磊; 王昕�
Original assignee: 富士通株式会社; 李国荣; 贾美艺; 张磊; 王昕�
Priority date: 2020-05-21
Filing date: 2020-05-21
Publication date: 2021-11-25

Abstract

The embodiments of the present application provide a scheduling request (SR) processing method, an apparatus and a system. The SR processing method comprises: a terminal device receiving an SR configuration related to a sidelink channel state information (SL CSI) reporting, sent by a network device, and the terminal device performing one of the following operations: with regard to the SR configuration related to the SL CSI reporting, an SR prohibit timer is not expected to be configured; with regard to the SR configuration related to the SL CSI reporting, the SR prohibit timer is not applied; and with regard to the SR configuration related to the SL CSI reporting, the SR prohibit timer having a value of 0 is applied. According to the embodiments of the present application, the allocation of resources to a sidelink by a network can be accelerated, and resource consumption can be reduced.

Description

Method, device and system for processing scheduling request

Technical field

The embodiments of the application relate to the field of communication technology.

Background technique

Sidelink communication (sidelink communication) can be applied to automotive communication services, etc. Vehicle communication business is represented by V2X (Vehicle-to-Everything) business, which can include multiple types: V2V (Vehicle-to-Vehicle, vehicle-to-vehicle communication), V2I (Vehicle-to-Infrastructure, vehicle-to-infrastructure) Facilities communication) and V2P (Vehicle-to-Pedestrian, vehicle-to-person communication). Automobile communication service is a communication mode in which terminal devices can directly communicate with each other through the PC5 interface. In Long Term Evolution (LTE) or New Radio (NR), terminal devices support this communication mode when they are within or outside the coverage of network equipment.

There are two resource allocation methods in side link communication, namely mode 1 (mode-1) and mode 2 (mode-2). Among them, mode-1 refers to the resource allocation method for network equipment scheduling side link resources, and mode-2 refers to the resource allocation method for terminal equipment to independently select resources.

When the terminal device is in mode-1, if the terminal device has a sidelink channel state information report (Sidelink CSI report or Sidelink CSI report or SL CSI report or SL CSI report) is triggered and there is currently no sidelink resource available for new transmission, Then the terminal device will trigger a scheduling request (scheduling request, SR). Once an SR is triggered, the SR remains in the pending state until cancelled, and the terminal device expects to use the SR configuration corresponding to the SL CSI reporting to send the SR.

It should be noted that the above introduction to the technical background is only for the convenience of a clear and complete description of the technical solutions of the present application, and to facilitate the understanding of those skilled in the art. It should not be considered that the above technical solutions are well-known to those skilled in the art just because these solutions are described in the background art part of this application.

Summary of the invention

The inventor found that according to the prior art, when a terminal device triggers SL CSI reporting for more than one destination address (destination), if there is no side link shared channel (SL-SCH) resource for new transmission, the terminal device will Trigger more than one SR using one SR configuration (scheduling request configuration). Take Figure 1 as an example for illustration.

Fig. 1 is a schematic diagram of an example of a side link communication scenario. In Fig. 1, UE3 has unicast services with UE1 and UE2, or respectively establishes PC5-RRC (radio resource control) connections. UE3 is triggered by UE1 and UE2 to report SL CSI. For example, UE1 and UE2 respectively send SCI (sidelink control information) to UE3 to trigger UE3 to report SL CSI. When the MAC (Media Access Control) entity of UE3 receives these 2 SCIs, it triggers 2 SL CSI reporting, respectively for UE1 and UE2. If there is no SL-SCH for new transmission, it will trigger 2 SRs (such as SR1). And SR2), these two SRs use the same SR configuration.

On the one hand, the inventor found that according to the current MAC specification, for an SR configuration, if SR1 is instructed to be sent to the physical layer, it will not receive an LBT (Listen Before Talk) failure indication (failure indication). In this case, the SR_COUNTER (scheduling request counter) corresponding to the SR configuration is incremented by 1, and the sr-ProhibitTimer (scheduling request prohibition timer) is started. Then for pending SR2, because SR2 uses the same SR configuration as SR1, SR2 will be instructed to send to the physical layer only when sr-ProhibitTimer is not running (running). Therefore, for UE3, the SL CSI reporting for UE2 will be delayed to be sent, that is, it will not be sent until the sr-ProhibitTimer expires. At this time, the delay requirement of SL CSI reporting configured by UE2 to UE3 (a value from 3ms to 20ms) may be exceeded.

On the other hand, the inventor found that in the current MAC specification, there is the following description: when an SR is triggered and there is no other pending SR under the same SR configuration, the SR_COUNTER of the corresponding SR configuration will be set to 0. . Therefore, if the terminal device has more than one destination address (destination) corresponding to the SL CSI reporting is triggered, because only when all the SL CSI reporting are sent, that is, all the SR triggered by the SL CSI reporting are cancelled, the SR The SR_COUNTER of the configuration will be set to 0. Therefore, the SR_COUNTER of the SR configuration corresponding to SL CSI reporting may reach the maximum number more easily. At this time, the random access process will be triggered, and the random access process may not be able to notify the network equipment terminal. The device is requesting side link resources for SL CSI reporting, so it does not want to trigger the random access process too early.

In order to solve at least one of the above-mentioned problems or other similar problems, embodiments of the present application provide a method, device, and system for processing a scheduling request.

According to an aspect of the embodiments of the present application, there is provided an apparatus for processing a scheduling request, wherein the apparatus includes:

A receiving unit, which receives the SR configuration related to the side link channel state information (SL CSI) report (reporting or report) sent by the network device;

Processing unit, which performs one of the following operations:

For the SR configuration related to the SL CSI report, it is not expected that the SR prohibit timer is configured;

For the SR configuration related to the SL CSI report, the SR prohibit timer is not applied;

For the SR configuration related to the SL CSI reporting, an SR prohibition timer with a value of 0 is applied.

According to another aspect of the embodiments of the present application, there is provided an apparatus for processing a scheduling request, wherein the apparatus includes:

An indication unit, which instructs the physical layer at the MAC layer of the terminal device to send an SR on an effective physical uplink control channel (PUCCH) resource used for scheduling request (SR) transmission, and the SR is triggered by SLCSI reporting;

The processing unit does not start the SR prohibit timer.

The setting unit sets the value of the scheduling request counter in the SR configuration according to the destination address reported by the SL CSI.

The determining unit, which determines the destination address information and/or delay information related to the SL CSI report;

A sending unit, which sends the destination address information and/or time delay information related to the SL CSI report to the network device.

According to another aspect of the embodiments of the present application, there is provided a configuration device, wherein the device includes:

The receiving unit, which receives the SL CSI reporting delay requirements sent by the terminal equipment;

The configuration unit configures uplink resources for the SR related to the SL CSI reporting, and the uplink resources corresponding to the SR triggered by the SL CSI reporting meet the delay requirements of the SL CSI reporting.

One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, it can speed up the reception of SR triggered by SL CSI reporting by network equipment, or reduce the random access process triggered by the maximum number of SRs triggered by SL CSI reporting. It is conducive to network equipment to allocate side link resources to terminal equipment as soon as possible, to meet the delay requirements of SL CSI reporting, and to reduce resource overhead.

With reference to the following description and drawings, specific implementations of the present application are disclosed in detail, and the ways in which the principles of the present application can be adopted are indicated. It should be understood that the scope of the embodiments of the present application is not limited thereby. Within the spirit and scope of the terms of the appended claims, the implementation of the present application includes many changes, modifications and equivalents.

Features described and/or shown for one embodiment can be used in one or more other embodiments in the same or similar manner, combined with features in other embodiments, or substituted for features in other embodiments .

It should be emphasized that the term "comprising/comprising" when used herein refers to the existence of a feature, a whole, a step or a component, but does not exclude the existence or addition of one or more other features, a whole, a step or a component.

Description of the drawings

The elements and features described in one drawing or one embodiment of the embodiment of the present application may be combined with the elements and features shown in one or more other drawings or embodiments. In addition, in the drawings, similar reference numerals indicate corresponding parts in several drawings, and may be used to indicate corresponding parts used in more than one embodiment.

Figure 1 is a schematic diagram of an example of a side link communication scenario;

Figure 2 is a schematic diagram of the control plane protocol stack;

FIG. 3 is a schematic diagram of a method for processing a scheduling request according to an embodiment of the present application;

FIG. 4 is another schematic diagram of a method for processing a scheduling request according to an embodiment of the present application;

Figure 5 is a schematic diagram of information exchange between UE1, UE2, UE3 and the network side;

FIG. 6 is another schematic diagram of the method for processing a scheduling request according to an embodiment of the present application;

FIG. 7 is another schematic diagram of a method for processing a scheduling request according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a configuration method of an embodiment of the present application;

FIG. 9 is a schematic diagram of an apparatus for processing a scheduling request according to an embodiment of the present application;

FIG. 10 is another schematic diagram of the device for processing a scheduling request according to an embodiment of the present application;

FIG. 11 is still another schematic diagram of the scheduling request processing apparatus according to an embodiment of the present application;

FIG. 12 is another schematic diagram of the apparatus for processing a scheduling request according to an embodiment of the present application;

FIG. 13 is a schematic diagram of a configuration device of an embodiment of the present application;

FIG. 14 is a schematic diagram of a communication system according to an embodiment of the present application;

FIG. 15 is a schematic diagram of a terminal device according to an embodiment of the present application;

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

Detailed ways

With reference to the drawings, the foregoing and other features of this application will become apparent through the following description. In the specification and drawings, specific implementations of the application are specifically disclosed, which indicate some implementations in which the principles of the application can be adopted. It should be understood that the application is not limited to the described implementations. On the contrary, the present application is not limited to the described implementations. The application includes all modifications, variations and equivalents falling within the scope of the appended claims.

In the embodiments of this application, the terms "first", "second", etc. are used to distinguish different elements from the terms, but they do not indicate the spatial arrangement or chronological order of these elements. These elements should not be used by these terms. Limited. The term "and/or" includes any and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having" and the like refer to the existence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

In the embodiments of this application, the singular forms "a", "the", etc. include plural forms, which should be broadly understood as "a" or "a type" rather than being limited to the meaning of "a"; in addition, the term "so" "Said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "based on" should be understood as "based at least in part on...", and the term "based on" should be understood as "based at least in part on...", unless the context clearly dictates otherwise.

In the embodiments of this application, the term "communication network" or "wireless communication network" can refer to a network that meets any of the following communication standards, such as Long Term Evolution (LTE), and Enhanced Long Term Evolution (LTE-A, LTE-A). Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.

In addition, the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G , New Radio (NR, New Radio), etc., and/or other currently known or future communication protocols.

In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.

Among them, the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay), or low-power node (such as femeto, pico, etc.). And the term "base station" can include some or all of their functions, and each base station can provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and/or its coverage area, depending on the context in which the term is used.

In the embodiments of the present application, the term "User Equipment" (UE, User Equipment) or "Terminal Equipment" (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services. The terminal device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc.

Among them, terminal devices may include but are not limited to the following devices: cellular phones (Cellular Phone), personal digital assistants (PDAs, Personal Digital Assistant), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, Cordless phones, smart phones, smart watches, digital cameras, etc.

For another example, in scenarios such as the Internet of Things (IoT), a terminal device may also be a machine or device that performs monitoring or measurement. For example, it may include, but is not limited to: Machine Type Communication (MTC) terminals, In-vehicle communication terminals, device to device (D2D, Device to Device) terminals, machine to machine (M2M, Machine to Machine) terminals, etc.

In addition, the term "network side" or "network device side" refers to a side of the network, which may be a certain base station, and may also include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to a side of a user or a terminal, which may be a certain UE, and may also include one or more terminal devices as described above. Unless otherwise specified in this article, "equipment" can refer to network equipment or terminal equipment.

At present, 3GPP has the following conclusions on the SR triggered by SL CSI reporting:

Regardless of which destination the terminal device needs to report the Sidelink CSI to, the network device can configure an SR configuration ID associated with the Sidelink CSI reporting for all unicast links of the terminal device. When the Sidelink CSI reporting of any destination triggers an SR, the terminal device shall use the SR configuration indicated by the associated SR configuration ID to send the SR.

Working hypothesis: When SL grant(s) can accommodate the Sidelink CSI reporting of a destination that has been triggered but not cancelled, the pending SR triggered by the Sidelink CSI reporting needs to be cancelled, and the corresponding sr-ProhibitTimer needs to be stopped .

In the current MAC specification, as long as at least one SR is in the pending state, for each pending SR, if the pending SR has a configured valid PUCCH resource, the terminal device performs the following operations on the SR configuration corresponding to the pending SR:

When the MAC entity has an SR transmission occasion on the effective PUCCH resource configured for the SR, and if the sr-ProhibitTimer is not running at the time when the SR is sent, and if the PUCCH resource of the SR transmission opportunity is not the same The measurement gap overlaps. If SR transmission takes precedence over other overlapping uplink transmissions (if any), then:

If the number of times the SR is sent (SR_COUNTER) is less than the maximum value (sr-TransMax), the physical layer is instructed to notify the SR on a valid PUCCH resource for the SR. If the LBT failure indication is not received from the lower layer, SR_COUNTER is increased by one, and sr-ProhibitTimer is started.

Figure 2 is a schematic diagram of the control plane protocol stack. Figure 2 shows the protocol stack between the UE and the network side. The RRC protocol provides system information broadcasting, paging, establishment and maintenance and release of RRC connections, security, and radio bearer establishment. Configuration maintenance and release, mobility, QoS (Quality of Service) management, measurement and other functions. The MAC layer provides functions such as mapping between logical channels and transmission channels, scheduling information reporting, data multiplexing and demultiplexing, and priority processing.

The RRC layer of the UE receives RRC messages sent by the network (gNB), such as RRC reconfiguration (reconfiguration) messages, RRC resume (resume) messages, etc., according to the content of the message to PDCP (Packet Data Convergence Protocol), RLC (Radio Link Channel control), MAC (Media Access Control) and PHY (Physical) are configured accordingly.

The various implementations of the embodiments of the present application will be described below with reference to the accompanying drawings.

Embodiments of the first aspect

The embodiment of the present application provides a method for processing a scheduling request, which is described from the terminal device side.

Fig. 3 is a schematic diagram of a method for processing a scheduling request according to an embodiment of the present application. As shown in Fig. 3, the method includes:

301: The terminal device receives the SR configuration (SR configuration) related to the side link channel state information (SL CSI) report (reporting or report) sent by the network device;

302: The terminal device performs one of the following operations: configures the SR related to the SL CSI report, and does not expect the SR prohibit timer (sr-ProhibitTimer) to be configured; and performs one of the following operations on the SR related to the SL CSI report The configuration does not apply the SR prohibition timer; for the SR configuration related to the SL CSI reporting, the SR prohibition timer with a value of 0 is applied.

According to the embodiment of this application, when the terminal device receives the SR configuration related to SL CSI reporting, the terminal device does not expect sr-ProhibitTimer, or the terminal device does not apply sr-ProhibitTimer, or the terminal device applies sr with a value of 0 -ProhibitTimer, as a result, the sending of SR is no longer limited to sr-ProhibitTimer, which can accelerate the network side to receive the SR triggered by the SL CSI report, which is beneficial to the network side to allocate side link resources as soon as possible to meet the delay requirements of the SL CSI report .

It is worth noting that Figure 3 above only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the order of execution among various operations can be appropriately adjusted, and some other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of FIG. 3 above.

In the embodiment of the present application, the SR configuration related to the SL CSI report may be 0 or 1 SR configuration to which the SL CSI report is mapped. The agreement can be expressed as "SR configuration of the SL CSI reporting" or "SR configuration corresponding to the SL CSI reporting" or "SR configuration associated with the SL CSI reporting", etc.

In this embodiment of the application, the SR configuration related to the SL CSI report may include a set of PUCCH resources, and the set of PUCCH resources may be on one or more bandwidth parts (Bandwidth Part, BWP), but this application does not Limited to this.

In the embodiment of the present application, the SR configuration of the SL CSI report triggered by the terminal device is considered to be the SR configuration corresponding to the SR triggered by the SL CSI report of the terminal device. That is, when the terminal device triggers an SR due to an SL CSI report, it uses the PUCCH resources included in the SR configuration related to the SL CSI report to send the SR. In the embodiment of the present application, unless otherwise specified, the SR triggered by the SL CSI report may be an SR triggered by the SL CSI report being triggered or waiting to be sent.

In some embodiments, for the SR configuration related to the SL CSI report, the field of the SR prohibit timer does not appear. For example, in the SR configuration related to SL CSI reporting configured by the network device, there is no sr-ProhibitTimer field. From the perspective of the terminal device, the terminal device does not expect sr-ProhibitTimer to be configured, or the terminal device does not use sr-ProhibitTimer, or the terminal device uses sr-ProhibitTimer with a value of 0.

In some embodiments, the SR configuration related to the above-mentioned SL CSI report is configured by the network device through RRC signaling.

An example of the RRC signaling is given below.

In the above example, the network device configures its related SR configuration for SL CSI reporting through RRC signaling.

In some embodiments, the network device may also configure the scheduling request prohibition timer (sr-ProhibitTimer) and the maximum number of scheduling request transmissions (sr-TransMax) through RRC signaling. The sr-ProhibitTimer and the sr-TransMax can be configured for each SR configuration. In addition, the start, stop, or timeout operation of the sr-ProhibitTimer by the terminal device is also performed according to each SR configuration, but the application is not limited to this. For example, the configuration of these two parameters can be expressed in the following form:

In some embodiments, after receiving the SR configuration related to SL CSI reporting, the terminal device does not expect (do not expect) sr-ProhibitTimer to be configured or does not apply sr-ProhibitTimer to the SR configuration related to SL CSI reporting. ProhibitTimer, or use sr-ProhibitTimer with a value of zero. As a result, the terminal device can be freed from the restriction of sr-ProhibitTimer to send SR, which speeds up the network device's receipt of the SR triggered by the SL CSI report, which is beneficial to the network to allocate side link resources as soon as possible to meet the delay requirements of the SL CSI report.

In some embodiments, sr-ProhibitTimer is not expected to be configured, or sr-ProhibitTimer is not applied, or sr-ProhibitTimer with a value of zero is applied, which is reflected in the operation of the terminal device on sr-ProhibitTimer. (The SR part of 321 of the current MAC protocol) is modified similar to the following.

In some embodiments, the sr-ProhibitTimer field does not appear, which is reflected in the configuration of the network device. The configuration for the sr-ProhibitTimer (the field description of the sr-ProhibitTimer in 331 of the current RRC protocol) can be similar to the following Revise.

In some embodiments, the SR configuration related to the above-mentioned SL CSI reporting includes an SR identifier (schedulingRequestId). For example, the SR identifier may correspond to a set of PUCCH resources, and the set of PUCCH resources may be used by the terminal device to send the SR triggered by the SL CSI report.

For example, the network device can also configure the "schedulingRequestId" to be included in the "SchedulingRequestToAddMod" structure.

An example of the "SchedulingRequestToAddMod" structure is given below.

In some embodiments, for the SR configuration related to the above-mentioned SL CSI reporting, the field of the sr-ProhibitTimer corresponding to the SR identifier does not appear.

Still taking the aforementioned "SchedulingRequestToAddMod" structure as an example, the aforementioned structure includes "schedulingRequestId" and "sr-ProhibitTimer". In some embodiments, the aforementioned structure does not include the "sr-ProhibitTimer" domain, that is, , The "schedulingRequestId" corresponding to the SL CSI report, the "sr-ProhibitTimer" field corresponding to the "schedulingRequestId" does not appear. Therefore, the terminal device can send SR without being restricted by sr-ProhibitTimer, which speeds up the network device receiving the SR triggered by the SL CSI report, which is beneficial to the network to allocate side link resources as soon as possible to meet the delay requirements of the SL CSI report. .

In some embodiments, the terminal device may also send the aforementioned SL CSI reporting delay requirement to the network device. Therefore, the PUCCH resource corresponding to the SR configuration configured by the network device can meet the SL CSI reporting delay requirement. The related content of the delay requirement will be described in the following embodiments.

Fig. 4 is another schematic diagram of a method for processing a scheduling request according to an embodiment of the present application. As shown in Fig. 4, the method includes:

401: The MAC layer of the terminal device instructs the physical layer to send an SR on an effective physical uplink control channel (PUCCH) resource used for scheduling request (SR) transmission, and the SR is triggered by the SL CSI report;

402: The terminal device does not start the SR prohibition timer.

According to this embodiment of the application, when the conditions for sending SR are met, the MAC layer of the terminal device instructs the physical layer to send the SR on the effective PUCCH resources used for SR transmission. If the SR is triggered by the SL CSI report, the terminal The device does not start sr-ProhibitTimer. Therefore, the terminal device is not limited to the sr-ProhibitTimer, which can accelerate the network side to receive the SR triggered by the SL CSI report, which is beneficial to the network side to allocate side link resources as soon as possible to meet the delay requirements of the SL CSI report.

It is worth noting that Figure 4 above only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the order of execution among various operations can be appropriately adjusted, and some other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the foregoing content, and are not limited to the description of the foregoing FIG. 4.

In some embodiments, the effective PUCCH resource used for the SR refers to the PUCCH resource on the BWP activated at the moment the SR is sent, where the PUCCH resource may be a set of PUCCH resources included in the SR configuration (SR configuration) of the SR PUCCH resources in. For the SR triggered by the SL CSI report, according to the previous description, the effective PUCCH resource used for the SR may be a set of PUCCH resources included in the SR configuration related to the SL CSI report on the BWP that is activated at the moment the SR is sent One or more than one PUCCH resource.

In some embodiments, in 401, the condition for sending the SR may include: the MAC layer has an SR transmission opportunity (SR transmission) on the above-mentioned effective PUCCH resource and the above-mentioned effective PUCCH resource does not overlap with a measurement gap.

In some embodiments, in 401, the condition for sending the SR may include: the number of times the SR is sent is less than the configured maximum number of times (sr-TransMax).

In some embodiments, in 401, the condition for sending the SR may include: the MAC layer of the terminal device does not receive an LBT failure indication (LBT failure indication) from the physical layer.

In some embodiments, the above-mentioned effective PUCCH resources do not overlap with uplink shared channel (UL-SCH) resources, and the above-mentioned effective PUCCH resources do not overlap with SL-SCH resources.

In some embodiments, the above-mentioned effective PUCCH resource overlaps with the UL-SCH resource, and the priority of the SL CSI report that triggers the above-mentioned SR is higher than the priority of the uplink grant (grant) of the above-mentioned UL-SCH resource, and the uplink grant has not The priority is de-prioritized. Therefore, the SR triggered by the higher priority SL CSI report can be instructed to be sent to the physical layer, which is beneficial to the network equipment to allocate side link resources for the transmission of the SL CSI report earlier. Meet the delay requirements of SL CSI reporting.

In some embodiments, the above-mentioned effective PUCCH resource overlaps with the SL-SCH resource, and the MAC layer of the terminal device cannot perform the transmission of the above-mentioned SR and the above-mentioned SL-SCH resource at the same time, and the priority of the SL CSI report that triggers the above-mentioned SR is higher than the above-mentioned The priority of the media access control protocol data unit (MAC PDU) included in the SL-SCH resource.

In the embodiment of this application, in 402, the terminal device does not start the SR prohibition timer, which is reflected in the description of the current MAC specification. It can be that if the above SR is not triggered by the SL CSI report, for example, the SR is in the buffer state. The sr-ProhibitTimer is started if the Buffer Status Report (BSR) is triggered or is triggered by the logical channel, or by the continuous LBT failure, or by the beam failure recovery of the secondary cell, or if the above SR is not related to the above SL CSI report, for example If the configuration of the SR is the SR configuration of the logical channel that triggers the BSR (the BSR triggers the SR) or the SR configuration corresponding to the continuous LBT failure triggering or the SR configuration corresponding to the beam failure recovery of the secondary cell, then the sr-ProhibitTimer is started; It may be that if the above SR is triggered by the above SL and CSI reporting, the sr-ProhibitTimer is not started or a value of 0 is applied to the sr-ProhibitTimer.

An example of the modification to the MAC specification is given below.

Another example of the modification to the MAC specification is given below.

For the content omitted in the above two examples, reference may be made to the above embodiment or the existing MAC specification, and the description is omitted here.

In some embodiments, the terminal device may also send the aforementioned SL CSI reporting delay requirement to the network device. Therefore, the PUCCH resource (set) corresponding to the SR configuration related to CSI reporting sent by the network device can meet the SL CSI reporting requirements. Delay requirements.

Fig. 5 is a schematic diagram of information exchange between UE1, UE2, UE3 and the network side (eNB or gNB, eNB/gNB for short) in the scenario of Fig. 1. As shown in Fig. 5, the process includes:

501: UE1 and UE2 respectively perform side link communication with UE3 (terminal equipment in this embodiment of the application), such as unicast communication. UE1 and UE2 respectively send RRC reconfiguration side link (RRCReconfiguration Sidelink) messages to UE3. It can include the delay requirement for SL CSI reporting. For example, the delay requirement for SL CSI reporting by UE1 is 6ms, and the delay requirement for SL CSI reporting by UE2 is 3ms;

502: UE3 sends SL CSI reporting related delay information to the network side. For example, the SL CSI reporting delay message to UE1 is 6 ms, and the SL CSI reporting delay information to UE2 is 3 ms;

503: The network side sends the SR configuration related to SL CSI reporting to UE3 according to the information reported by UE3 in 502, including the configuration of a set of PUCCH resources, for example, the configured PUCCH resources (interval or period) meet the requirements of SL CSI reporting In addition, the network side can also be configured with sr-ProhibitTimer, as described above, and the description is omitted here;

504: UE1 and UE2 respectively send SCI that triggers SL and CSI reporting;

505: UE3 receives the SCI sent by UE1 and UE2 to trigger the SL CSI report. Since there is no side link resource available for new transmission, it triggers SR1 and SR2 respectively. SR1 and SR2 use the same SR configuration (referred to as SR configuration A);

506: UE3 sends SR1 on the effective PUCCH resource configured by the SR related to SL CSI reporting, and does not run sr-ProhibitTimer (sr-ProhibitTimer is not expected to be configured or sr-ProhibitTimer or sr-ProhibitTimer is set to 0 (corresponding figure) 3) or not start the sr-ProhibitTimer (corresponding to the operation of 402 in Figure 4)), and send SR2 on the effective PUCCH resource configured by the SR;

507: The network side sends a sidelink grant (sidelink grant) to UE3;

508: UE3 uses the side link resources allocated by the network side to send the SL CSI report to UE1 and the SL CSI report to UE2.

It should be noted that Figure 5 above only schematically illustrates an embodiment of the present application, but the present application is not limited thereto. For example, the order of execution between various operations can be appropriately adjusted. In addition, other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the above-mentioned drawings. 4 records. For example, the above operations 501 and 502 are optional. Without operations 501 and/or 502, in operation 503, the network side directly performs the SL CSI reporting corresponding SR configuration PUCCH resource configuration, and no longer Refer to the information reported in operation 502. For another example, this application does not limit the position of the operation of "sr-ProhibitTimer is not expected to be configured or sr-ProhibitTimer is not applied or sr-ProhibitTimer is set to 0 or sr-ProhibitTimer is not started" in the above process. Before operation 506 of SR1, it may also precede operation 506 for SR2 as shown in FIG. 5. For another example, the operations 504 to 506 for SR1 may also precede the operations 504 to 506 for SR2, and so on.

The above embodiments only exemplify the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may also be made on the basis of the above various embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be combined.

It can be seen from the above embodiment that when the SL CSI report triggers SR, it can be accelerated by not expecting sr-ProhibitTimer to be configured or not applying sr-ProhibitTimer or applying sr-ProhibitTimer with a value of 0 or not starting sr-ProhibitTimer The network receives the SR triggered by the SL CSI report, which helps the network allocate side link resources as soon as possible to meet the delay requirements of the SL CSI report.

Embodiment of the second aspect

FIG. 6 is a schematic diagram of a method for processing a scheduling request according to an embodiment of the present application. As shown in FIG. 6, the method includes:

601: The terminal device receives the SR configuration related to the side link channel state information (SL CSI) report (reporting or report) sent by the network device;

602: The terminal device sets the value of the scheduling request counter (SR_COUNTER) in the SR configuration according to the destination address reported by the SL CSI.

According to the embodiment of the present application, when the terminal device receives the SR configuration related to the SL CSI report, the terminal device sets the value of SR_COUNTER in the SR configuration according to the destination address of the SL CSI report, thereby reducing The random access process triggered by the sending of the SR triggered by the SL CSI report reaches the maximum number of times, which is helpful for the network side to know that the terminal device has the SL CSI report to be sent and allocate side link resources for it, and reduce the random access generated Resource overhead.

In this embodiment of the application, the destination address of the SL CSI report may be the destination address of the terminal device that sends the SCI that triggers the SL CSI report to the terminal device, such as the destination L2 ID or source of the terminal device. L2 ID) or layer one identification (destination L1 ID or source L1 ID) or source layer two identification and destination layer two identification pair (source L2 ID and destination L2 ID pair), etc.

In the embodiment of the present application, the relevant content of the SR configuration related to the SL CSI report has been described in the embodiment of the first aspect, and the content is merged here, and the description will not be repeated here.

In some embodiments, the terminal device triggers an SR. The SR is triggered because the above-mentioned SL CSI report is triggered, and there is no other SR with the same SR configuration corresponding to the SR and in the pending state or no other SR with the SR. For other SRs that correspond to the same destination address reported by the SL CSI and are in the pending state, the terminal device sets the value of the scheduling request counter to 0.

In other words, if an SR is triggered and corresponds to the same SR configuration or to the same SL CSI report destination address (if the SR is triggered by the SL CSI report), and no other SR is in the pending state, the MAC entity sets the SR The configured SR_COUNTER is 0.

In the MAC specification, the above content can be described as the following form.

The following still takes the scenario shown in FIG. 1 as an example for description.

For example, in UE3, SR1 is triggered for the SL CSI report of UE1. At this time, no other SR is in the pending state for the same SR configuration or the destination address reported to the same SL CSI, so the SR_COUNTER of the SR configuration is set to 0. Then, for the SL CSI reporting of UE2, SR2 is triggered, and the SR configured for the same SR is in the pending state (SR1 is in the pending state), but no other SR is in the pending state for the destination address reported by the same SL CSI, so the SR configured SR_COUNTER is set to 0 again.

As a result, the problem caused by the SR_COUNTER reaching the maximum number of times too quickly is avoided.

In some embodiments, if the SR triggered by the SL CSI reporting of different destination addresses triggers the notification of the SR from the MAC layer to the physical layer of the terminal device, the terminal device increases the value of the scheduling request counter by one time.

That is to say, if more than one SR triggered by the SL CSI reporting of different destination addresses triggers the notification of the SR from the MAC layer to the physical layer, the SR_COUNTER configured by the relevant SR is only increased once.

In the MAC specification, the above content can be described in the form of notes, such as the following form.

For example, in UE3, SR1 triggered by the SL CSI report of UE1 and SR2 triggered by the SL CSI report of UE2 are both instructed by the MAC layer to be sent to the physical layer, but because SR1 and SR2 are triggered by the SL CSI report of different destination addresses, Therefore, the SR_COUNTER configured by the SR is only increased once.

In some embodiments, if the destination address reported by the SL CSI has not changed, the terminal device increases the value of the aforementioned scheduling request counter by 1.

That is, when the destination address of the SL CSI report changes, the SR_COUNTER of the SR configuration corresponding to the SL CSI report does not increase by 1 (or remains unchanged).

For the content omitted in the above example, reference may be made to the above embodiment or the existing MAC specification, and the description is omitted here.

For example, in UE3, for the SR1 reported by the SL CSI of UE1, instruct the physical layer to send the SR (SR1) and add 1 to SR_COUNTER, and then, for the SR2 reported by the SL CSI of UE2, instruct the physical layer to send the SR (SR2) Since the destination address reported by SL CSI is changed from UE1 to UE2, SR_COUNTER is no longer increased by 1.

In some embodiments, the terminal device uses the product of the number of the aforementioned destination addresses and the sr-TransMax in the aforementioned SR configuration as the maximum number of dispatch requests sent for comparison with the value of the aforementioned dispatch request counter.

In other words, the terminal device multiplies the sr-TransMax corresponding to the SR configuration corresponding to the SL CSI reported by the network side by the number of destination addresses reported by the SL CSI that triggers the SR, and if the SR_COUNTER is less than this value, the physical layer is instructed to send the SR .

In some embodiments, the MAC layer of the terminal device may instruct the physical layer to send the SR when the value of SR_COUNTER is less than the maximum number of times the scheduling request is sent. Thus, the transmission of SR is guaranteed.

It can be seen from the above embodiment that when the terminal device receives the SR configuration related to the SL CSI report, the terminal device sets the value of SR_COUNTER in the SR configuration according to the destination address of the SL CSI report, thereby reducing The random access process triggered by the sending of the SR triggered by the SL CSI report reaches the maximum number of times, which helps the network side know that the terminal device has an SL CSI report to send and allocate side link resources for it, and reduces the resources generated by random access Overhead.

Embodiments of the third aspect

FIG. 7 is a schematic diagram of a method for processing a scheduling request according to an embodiment of the present application. As shown in FIG. 7, the method includes:

701: The terminal device determines destination information and/or latency information (latency bound) related to SL CSI reporting;

702: The terminal device sends the destination address information and/or delay information related to the SL CSI report to the network device.

According to the embodiment of the present application, the terminal device sends the destination address information and/or delay information related to the SL CSI report to the network device. Therefore, the network side can, according to the destination address information and/or delay information reported by the terminal device, Configuring the PUCCH resource or the value of sr-ProhibitTimer that meets the delay requirements of SL CSI reporting is beneficial to meet the transmission delay requirements of SL CSI reporting.

In the embodiment of the present application, in 702, the terminal device may send the above-mentioned destination address information and/or delay information related to the SL CSI report to the network device through RRC signaling (also referred to as RRC message). The application is not limited to this. The foregoing RRC message is, for example, sidelink UE Information (Sidelink UE Information) or UE Assistant Information (UE Assistant Information), etc. The present application is not limited to this.

In some embodiments, the terminal device sends one or more destination address information related to the above-mentioned SL CSI report and delay information corresponding to each destination address information to the network side. Taking the scenario shown in Figure 1 as an example, UE3 can send the addresses of UE1 and UE2 and the delay information (6ms) corresponding to UE1 and the delay information (3ms) corresponding to UE2 to the network side, so that the network side can understand each The delay requirement of the destination address is to allocate PUCCH resources for SR transmission or configure parameters (such as sr-ProhibitTimer) according to the learned information.

In some embodiments, the terminal device sends one or more destination address information related to the above-mentioned SL CSI report and a delay information applied to the one or more destination address information to the network side. Taking the scenario shown in Figure 1 as an example, UE3 can send the addresses of UE1 and UE2 and a delay information (for example, 3ms) to the network side. In this way, the network side can understand the minimum delay requirements of each destination address. The information is allocated for PUCCH resources sent by SR or for configuration of parameters (such as sr-ProhibitTimer). The foregoing is only an example, the above-mentioned delay information sent may not be the minimum value in the delay requirement, and may also be determined according to other strategies.

In some embodiments, the terminal device only sends one or more destination address information related to the above-mentioned SL CSI report to the network side. That is, the time delay information is not reported. In this way, the network device can understand each destination address, allocate PUCCH resources for SR transmission or configure parameters (such as sr-ProhibitTimer) according to the learned information.

In some embodiments, the terminal device only sends one or more delay information corresponding to one or more destination address information related to the above-mentioned SL CSI report to the network side, that is, it does not report the destination address, but only reports Delay information, the delay information can be the minimum or average value of the delay required for SL CSI reporting of one or more than one destination address, so that the network device can understand the delay required for SL CSI reporting that triggers SR , According to the learned information, allocate PUCCH resources for SR transmission or configure parameters (such as sr-ProhibitTimer).

In some embodiments, the foregoing destination address information may be an address of a terminal device that has a unicast link with the foregoing terminal device. Taking the scenario shown in FIG. 1 as an example, UE1 and/or UE2 and UE3 have unicast links, and the destination address information may be the addresses of UE1 and/or UE2.

In some embodiments, the aforementioned destination address information may be the address of a terminal device that has established a PC5-RRC connection with the aforementioned terminal device. Taking the scenario shown in FIG. 1 as an example, UE1 and/or UE2 establishes a PC5-RRC connection with UE3, and the destination address information may be the addresses of UE1 and/or UE2.

In some embodiments, the foregoing destination address information may be the address of the terminal device that has sent the SL CSI reporting configuration to the foregoing terminal device. Here, the SL CSI reporting configuration includes, for example, the delay requirements of the SL CSI reporting (as shown in FIG. 5) and/or the SL CSI-RS time-frequency resource information and so on. Taking the scenario shown in FIG. 1 as an example, UE1 and/or UE2 sends SL CSI reporting configuration to UE3, and the destination address information may be the addresses of UE1 and/or UE2.

In some embodiments, the above destination address information may be the L1 ID of the terminal device that triggers the above SL CSI report, for example, the L1 ID of UE1 and/or the L1 ID of UE2 in the scenario shown in FIG. 1; or the above SL The L2 ID of the terminal device reported by the CSI, such as the L2 ID of UE1 and/or the L2 ID of UE2 in the scenario shown in FIG. 1; or the terminal device (source) and the terminal device that triggered the SLCSI report (destination) For example, the L2 ID pair of UE3’s L2 ID and UE1’s L2 ID in the scenario shown in Figure 1 and/or the L2 ID pair of UE3’s L2 ID and UE2’s L2 ID; or the above The PC5 unicast link ID of the PC5 unicast link between the terminal device and the terminal device that triggers the above-mentioned SL CSI report, such as the ID of the PC5 unicast link between UE3 and UE1 in the scenario shown in Figure 1 And/or the ID of the PC5 unicast link between UE3 and UE2.

In some embodiments, the above-mentioned delay information may be the delay information included in the SL CSI reporting configuration received by the terminal device from the terminal device (the opposite terminal device) that triggers the SL CSI report, or it may be a predefined delay. Information, this application is not limited to this. Here, the SL CSI reporting configuration includes, for example, the time delay requirement of SL CSI reporting (as shown in FIG. 5) or SL CSI-RS time-frequency resource information, etc. Taking the process shown in FIG. 5 as an example, the delay information may be 6ms and 3ms information received by UE3 (the terminal device of the present application) from UE1 and UE2 (the opposite terminal device).

In the above embodiment, the terminal device that triggers the SL CSI report, as described above, can also be a terminal device that has a unicast link with the above terminal device, or a terminal that has established a PC5-RRC connection with the above terminal device. The device may also be a terminal device that has sent the SL CSI reporting configuration to the above-mentioned terminal device, and it will not be repeated here.

It can be seen from the above embodiment that the terminal device sends the destination address information and/or delay information related to the SL CSI report to the network device. Therefore, the network side can, according to the destination address information and/or delay information reported by the terminal device, Configuring the PUCCH resource or the value of sr-ProhibitTimer that meets the delay requirements of SL CSI reporting is beneficial to meet the transmission delay requirements of SL CSI reporting.

Embodiment of the fourth aspect

The embodiment of the present application provides a configuration method, which is described from the network device side, wherein the same content as the embodiment of the first aspect to the third aspect will not be repeated.

FIG. 8 is a schematic diagram of a configuration method of an embodiment of the present application. As shown in FIG. 8, the method includes:

801: The network device receives the SL CSI report delay requirement sent by the terminal device;

802: The network device configures uplink resources for the SR related to the SL CSI report, and the uplink resource corresponding to the SR triggered by the SL CSI report meets the delay requirement of the SL CSI report.

In the embodiments of the present application, the above-mentioned delay requirements have been described in the embodiments of the first aspect, and the content is incorporated here, and will not be repeated here.

According to the embodiment of the present application, the network side can configure PUCCH resources that meet the delay requirements of the SL CSI reported by the terminal device according to the delay requirements of the SL CSI report, which is beneficial to meet the delay requirements of the SL CSI report.

It should be noted that Fig. 8 above only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the order of execution among various operations can be appropriately adjusted, and some other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of FIG. 8 above.

In some embodiments, the network device also sends an SR configuration to the terminal device, and the SR configuration includes the PUCCH resource configured or allocated by the network device for the terminal device for SR transmission, such as operation 503 in the example of FIG. 5. In some embodiments, the SR configuration does not include the configuration of the SR prohibit timer.

Since in the embodiment of the first aspect, the SR configuration and the configuration of the SR prohibit timer have been described in detail, their content is merged here, and will not be repeated here.

It can be seen from the foregoing embodiment that the network side can configure PUCCH resources that meet the delay requirements of each SL CSI reported by the terminal device according to the delay requirements of each SL CSI report, which is beneficial to meet the delay requirements of the SL CSI report.

Embodiments of the fifth aspect

The embodiment of the present application provides an apparatus for processing a scheduling request. The apparatus may be a terminal device, or may be some or some components or components configured in the terminal device. The terminal device is, for example, the terminal device described in the embodiment of the first aspect, which is similar to the embodiment of the first aspect. The same content will not be repeated.

Fig. 9 is a schematic diagram of a scheduling request processing device according to an embodiment of the present application. As shown in FIG. 9, the processing device 900 for the scheduling request includes:

The receiving unit 901 is configured to receive the SR configuration related to the side link channel state information (SL CSI) report (reporting or report) sent by the network device;

The processing unit 902 is configured to perform one of the following operations: configure the SR related to the SL CSI report without expecting the SR prohibit timer to be configured; and configure the SR related to the SL CSI report without Apply the SR prohibition timer; for the SR configuration related to the SL CSI reporting, use the SR prohibition timer with a value of 0.

In some embodiments, for the SR configuration related to the SL CSI report, the field of the SR prohibit timer does not appear.

In some embodiments, the SR configuration related to the SL CSI report includes an SR identifier.

In some embodiments, in the SR configuration related to the SL CSI report, the field of the SR prohibition timer corresponding to the SR identifier does not appear.

In some embodiments, as shown in FIG. 9, the device further includes:

The sending unit 903 sends the time delay request of the SL CSI report to the network device.

According to the embodiment of this application, when the terminal device receives the SR configuration related to SL CSI reporting, the terminal device does not expect sr-ProhibitTimer, or the terminal device does not apply sr-ProhibitTimer, or the terminal device applies sr with a value of 0 -ProhibitTimer, or the sr-ProhibitTimer field does not appear in the SR configuration. Therefore, the sending of SR is no longer limited to sr-ProhibitTimer, which can speed up the network side to receive the SR triggered by the SL CSI report, which is beneficial to the network side as soon as possible Allocate side link resources to meet the delay requirements of SL CSI reporting.

Fig. 10 is a schematic diagram of a scheduling request processing device according to an embodiment of the present application. As shown in FIG. 10, the device 1000 for processing a scheduling request includes:

Indication unit 1001, which instructs the physical layer at the MAC layer of the terminal device to send an SR on an effective physical uplink control channel (PUCCH) resource used for scheduling request (SR) transmission, where the SR is triggered by SLCSI reporting;

The processing unit 1002 does not start the SR prohibit timer.

In some embodiments, the MAC layer has an SR transmission opportunity (SR transmission occasion) on the effective PUCCH resource, and the effective PUCCH resource does not overlap with a measurement gap.

In some embodiments, the effective PUCCH resources do not overlap with UL-SCH resources, nor do they overlap with SL-SCH resources.

In some embodiments, the effective PUCCH resource overlaps the UL-SCH resource, and the priority of the SL CSI report that triggers the SR is higher than the priority of the uplink grant (grant) of the UL-SCH resource, wherein, The uplink grant has not been de-prioritized.

In some embodiments, the effective PUCCH resource overlaps with the SL-SCH resource and the MAC layer of the terminal device cannot perform the transmission of the SR and the SL-SCH resource at the same time, which triggers the SL CSI report of the SR The priority is higher than the priority of the MAC PDU included in the SL-SCH resource.

In some embodiments, the number of transmissions of the SR is less than the configured maximum number of transmissions (sr-TransMax).

In some embodiments, the MAC layer of the terminal device does not receive an LBT failure indication (Listen Before Talk (LBT) failure indication) from the physical layer.

In some embodiments, not starting the SR prohibition timer by the processing unit 1002 means: if the SR is not triggered by the SL CSI report, then the SR prohibition timer is started.

In some embodiments, the fact that the processing unit 1002 does not start the SR prohibition timer means that if the SR is not related to the SL CSI report, then the SR prohibition timer is started.

In some embodiments, the processing unit 1002 not starting the SR prohibition timer means that if the SR is triggered by the SL CSI report, then the SR prohibition timer is not started or the SR prohibition timer is applied. The value is 0.

In some embodiments, as shown in FIG. 10, the device further includes:

The sending unit 1003 sends the time delay request of the SL CSI report to the network device.

It is worth noting that the above only describes the components or modules related to the application, but the application is not limited thereto. The apparatus for processing a scheduling request in an embodiment of the present application may further include other components or modules, and for the specific content of these components or modules, reference may be made to related technologies.

In addition, for the sake of simplicity, FIGS. 9 and 10 only exemplarily show the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. . The foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.

It can be seen from the above embodiment that the terminal device is not limited to the sr-ProhibitTimer, which can accelerate the network side to receive the SR triggered by the SL CSI report, which is beneficial to the network side to allocate side link resources as soon as possible, and meets the delay requirement of the SL CSI report.

Embodiments of the sixth aspect

The embodiment of the present application provides an apparatus for processing a scheduling request. The device may be a terminal device, or some component or component configured in a terminal device. The terminal device is, for example, the terminal device described in the embodiment of the second aspect, which is similar to the embodiment of the second aspect. The same content will not be repeated.

FIG. 11 is a schematic diagram of an apparatus for processing a scheduling request according to an embodiment of the present application. As shown in FIG. 11, the device 1100 for processing a scheduling request includes:

The receiving unit 1101, which receives the SR configuration related to the side link channel state information (SL CSI) report (reporting or report) sent by the network device;

The setting unit 1102 sets the value of the scheduling request counter in the SR configuration according to the destination address reported by the SL CSI.

In some embodiments, the terminal device triggers an SR, the SR is triggered because the SL CSI report is triggered, and there is no other SR with the same SR configuration and pending state corresponding to the SR or no other SR. For other SRs that correspond to the same SL CSI reported destination address and are in the pending state with the SR, the setting unit 1102 sets the value of the scheduling request counter to 0.

In some embodiments, if the SR triggered by the SL CSI reporting of different destination addresses triggers the notification of the SR from the MAC layer to the physical layer of the terminal device, the setting unit 1102 sets the value of the scheduling request counter Increase 1 time.

In some embodiments, if the destination address reported by the SL CSI has not changed, the setting unit 1102 increases the value of the scheduling request counter by 1.

In some embodiments, the setting unit 1102 uses the product of the number of the destination address and the sr-TransMax in the SR configuration as the maximum number of dispatch request transmissions compared with the value of the dispatch request counter .

In some embodiments, as shown in FIG. 11, the apparatus 1100 for processing a scheduling request further includes:

The indicating unit 1103, which instructs the physical layer to send the scheduling request when the value of the scheduling request counter is less than the maximum number of times of sending the scheduling request.

In addition, for the sake of simplicity, FIG. 11 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.

Embodiments of the seventh aspect

The embodiment of the present application provides an apparatus for processing a scheduling request. The device may be a terminal device, or some component or component configured in a terminal device. The terminal device is, for example, the terminal device described in the embodiment of the third aspect, which is similar to the embodiment of the third aspect. The same content will not be repeated.

Fig. 12 is a schematic diagram of a scheduling request processing device according to an embodiment of the present application. As shown in FIG. 12, the device 1200 for processing a scheduling request includes:

The determining unit 1201 determines the destination address information and/or delay information related to SL CSI reporting;

The sending unit 1202 sends the destination address information and/or delay information related to the SL CSI report to the network device.

In some embodiments, the sending unit 1202 sends one or more destination address information related to the SL CSI report and delay information corresponding to each destination address information to the network device.

In some embodiments, the sending unit 1202 sends to the network device one or more destination address information related to the SL CSI report and a delay applied to the one or more destination address information information;

In some embodiments, the sending unit 1202 sends one or more destination address information related to the SL CSI report to the network device;

In some embodiments, the sending unit 1202 sends one or more delay information corresponding to one or more destination address information related to the SL CSI report to the network device.

In some embodiments, the destination address information includes at least one of the following:

The address of the terminal device that has a unicast link with the terminal device;

The address of the terminal device that has established a PC5-RRC connection with the terminal device;

The address of the terminal device configured for SL CSI reporting is sent to the terminal device.

In some embodiments, the destination address information includes one of the following:

Trigger the L1 ID of the terminal device reported by the SL CSI;

Trigger the L2 ID of the terminal device reported by the SL CSI;

A pair of the L2 ID of the terminal device (source) and the L2ID of the terminal device (destination) that triggers the SL CSI report;

The PC5 unicast link ID related to the terminal device and/or triggering the SL CSI report.

In some embodiments, the delay information includes one of the following:

The delay information included in the SL CSI report configuration received by the terminal device from the terminal device (the opposite terminal device) that triggered the SL CSI report;

Predefined delay information.

In some embodiments, the sending unit 1202 sends the destination address information and/or delay information related to the SL CSI report to the network device through a radio resource control (RRC) message.

In addition, for the sake of simplicity, FIG. 12 only exemplarily shows the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.

Embodiment of the eighth aspect

The embodiment of the present application provides a configuration device. The device may be, for example, a network device, or some component or component configured in a network device. The network device may be, for example, the network device described in the embodiment of the fourth aspect. The same content in the embodiment will not be repeated.

Fig. 13 is a schematic diagram of a configuration device of an embodiment of the present application. As shown in FIG. 13, the configuration device 1300 includes:

The receiving unit 1301, which receives the time delay requirement of the SL CSI report sent by the terminal device;

The configuration unit 1302 configures uplink resources for the SR related to the SL CSI reporting, and the uplink resources corresponding to the SR triggered by the SL CSI reporting meet the delay requirements of the SL CSI reporting.

In some embodiments, as shown in FIG. 13, the configuration apparatus 1300 further includes:

The sending unit 1303 sends an SR configuration to the terminal device, where the SR configuration includes uplink resources, and the SR configuration does not include the configuration of the SR prohibit timer.

It is worth noting that the above only describes the components or modules related to the application, but the application is not limited thereto. The configuration device of the embodiment of the present application may further include other components or modules, and for the specific content of these components or modules, reference may be made to related technologies.

In addition, for the sake of simplicity, FIG. 13 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.

Embodiment of the ninth aspect

An embodiment of the present application also provides a communication system. FIG. 14 is a schematic diagram of the communication system 1400. As shown in FIG. 14, the communication system 1400 includes a network device 1401 and a terminal device 1402. For simplicity, FIG. 14 uses only one terminal. The device and a network device are taken as an example for description, but the embodiment of the present application is not limited to this.

In the embodiment of the present application, the network device 1401 and the terminal device 1402 may perform existing service or service transmission that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), large-scale machine type communication (mMTC), high-reliability and low-latency communication (URLLC), and Internet of Vehicles (V2X) communication, and so on.

In the embodiment of the present application, the network device 1401 may be configured to implement the method described in the embodiment of the fourth aspect, and the content of the method described in the embodiment of the fourth aspect is merged here, and will not be repeated here.

In the embodiment of the present application, the terminal device 1402 may be configured to implement the method described in the embodiment of any aspect of the first aspect to the third aspect, the content of which is merged here, and will not be repeated here.

The embodiment of the present application also provides a terminal device. The terminal device may be, for example, a UE, but the present application is not limited to this, and may also be other devices.

FIG. 15 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 15, the terminal device 1500 may include a processor 1501 and a memory 1502; the memory 1502 stores data and programs, and is coupled to the processor 1501. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to implement telecommunication functions or other functions.

For example, the processor 1501 may be configured to execute a program to implement the scheduling request processing method as described in the embodiment of any one of the first aspect to the third aspect.

As shown in FIG. 15, the terminal device 1500 may further include: a communication module 1503, an input unit 1504, a display 1505, and a power supply 1506. Among them, the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the terminal device 1500 does not necessarily include all the components shown in FIG. 15 and the above-mentioned components are not necessary; in addition, the terminal device 1500 may also include components not shown in FIG. technology.

The embodiments of the present application also provide a network device. The network device may be, for example, a base station (eNB or gNB), but the present application is not limited to this, and may also be other network devices.

FIG. 16 is a schematic diagram of a structure of a network device according to an embodiment of the present application. As shown in FIG. 16, the network device 1600 may include: a processor (such as a central processing unit CPU) 1601 and a memory 1602; the memory 1602 is coupled to the processor 1601. The memory 1602 can store various data; in addition, it also stores information processing programs, which are executed under the control of the central processing unit 1601.

For example, the processor 1601 may be configured to execute a program to implement the configuration method described in the embodiment of the fourth aspect.

In addition, as shown in FIG. 16, the network device 1600 may further include: a transceiver 1603, an antenna 1604, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the network device 1600 does not necessarily include all the components shown in FIG. 16; in addition, the network device 1600 may also include components not shown in FIG. 16, which can refer to the prior art.

An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the scheduling request described in the embodiment of any one of the first aspect to the third aspect的处理方法。 Treatment methods.

An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the scheduling request processing method described in the embodiment of the fourth aspect.

An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the scheduling request processing method described in the embodiment of any aspect of the first aspect to the third aspect.

An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program causes a network device to execute the configuration method described in the embodiment of the fourth aspect.

The above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software. This application relates to such a computer-readable program, when the program is executed by a logic component, the logic component can realize the above-mentioned device or constituent component, or the logic component can realize the above-mentioned various methods Or steps. This application also relates to storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

The method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow or each hardware module. These software modules can respectively correspond to the steps shown in the figure. These hardware modules can be implemented by solidifying these software modules by using a field programmable gate array (FPGA), for example.

The software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art. A storage medium may be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be a component of the processor. The processor and the storage medium may be located in the ASIC. The software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a larger-capacity MEGA-SIM card or a large-capacity flash memory device, the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.

One or more of the functional blocks and/or one or more combinations of the functional blocks described in the drawings can be implemented as general-purpose processors, digital signal processors (DSPs) for performing the functions described in this application. ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof. One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, and multiple micro-processing Processor, one or more microprocessors in communication with the DSP, or any other such configuration.

The application is described above in conjunction with specific implementations, but it should be clear to those skilled in the art that these descriptions are all exemplary and do not limit the scope of protection of the application. Those skilled in the art can make various variations and modifications to the application according to the spirit and principle of the application, and these variations and modifications are also within the scope of the application.

Regarding the implementation including the above examples, the following supplementary notes are also disclosed:

1. A method for processing a scheduling request, wherein the method includes:

The terminal device receives the SR configuration related to side link channel state information (SL CSI) reporting (reporting or report) sent by the network device, and the terminal device performs one of the following operations:

2. The method according to appendix 1, wherein for the SR configuration related to the SL CSI report, the domain of the SR prohibition timer does not appear.

3. The method according to appendix 1, wherein the SR configuration related to the SL CSI report includes an SR identifier.

4. The method according to appendix 3, wherein in the SR configuration related to the SL CSI reporting, the SR prohibition timer field corresponding to the SR identifier does not appear.

5. A method for processing a scheduling request, wherein the method includes:

The MAC layer of the terminal device instructs the physical layer to send an SR on an effective physical uplink control channel (PUCCH) resource used for scheduling request (SR) transmission, and the SR is triggered by SL CSI reporting;

The terminal device does not start the SR prohibition timer.

6. The method according to appendix 5, wherein the MAC layer has an SR transmission opportunity on the effective PUCCH resource, and the effective PUCCH resource does not overlap with a measurement gap.

7. The method according to appendix 5, wherein the effective PUCCH resource satisfies one of the following conditions:

The effective PUCCH resources do not overlap with UL-SCH resources, nor do they overlap with SL-SCH resources;

The effective PUCCH resource overlaps the UL-SCH resource, and the priority of the SL CSI report that triggers the SR is higher than the priority of the uplink grant (grant) of the UL-SCH resource, wherein the uplink grant has not Reduced priority (de-prioritized);

The effective PUCCH resource overlaps with the SL-SCH resource, and the MAC layer of the terminal device cannot perform the transmission of the SR and the SL-SCH resource at the same time, and the SL CSI report that triggers the SR has a higher priority than the The priority of the MAC PDU included in the SL-SCH resource.

8. The method according to appendix 5, wherein the number of transmissions of the SR is less than the configured maximum number of transmissions (sr-TransMax).

9. The method according to appendix 5, wherein the MAC layer of the terminal device does not receive an LBT failure indication (Listen Before Talk (LBT) failure indication) from the physical layer.

10. The method according to appendix 5, wherein the terminal device does not start the SR prohibition timer, which includes one of the following:

If the SR is not triggered by the SL CSI report, start the SR prohibit timer;

If the SR has nothing to do with the SL CSI report, start the SR prohibit timer;

If the SR is triggered by the SL CSI report, the SR prohibition timer is not started or the value 0 is applied to the SR prohibition timer.

11. The method according to any one of appendix 1 to 10, wherein the method further comprises:

The terminal device sends the time delay request of the SL CSI report to the network device.

12. A method for processing a scheduling request, wherein the method includes:

The terminal device receives the SR configuration related to the side link channel state information (SL CSI) report (reporting or report) sent by the network device;

The terminal device sets the value of the scheduling request counter in the SR configuration according to the destination address reported by the SL CSI.

13. The method according to appendix 12, wherein the terminal device triggers an SR that is triggered because the SL CSI report is triggered, and does not have the same SR configuration corresponding to the SR and is in For other SRs in the pending state or other SRs that do not have the same SL CSI reported destination address corresponding to the SR and are in the pending state, the terminal device sets the value of the scheduling request counter to 0.

14. The method according to appendix 12, wherein if the SR triggered by the SL CSI reporting of different destination addresses triggers the notification of the SR from the MAC layer to the physical layer of the terminal device, the terminal device will The value of the scheduling request counter is increased by one time.

15. The method according to appendix 12, wherein, if the destination address reported by the SL CSI does not change, the terminal device increases the value of the scheduling request counter by 1.

16. The method according to appendix 12, wherein the terminal device compares the product of the number of the destination address and the sr-TransMax in the SR configuration as the value of the scheduling request counter The maximum number of dispatch requests sent.

16.1. The method according to Supplement 12, wherein, when the value of the scheduling request counter is less than the maximum number of scheduling request transmissions, the terminal device instructs the physical layer to send the scheduling request at the MAC layer.

17. A method for processing a scheduling request, wherein the method includes:

The terminal device determines the destination address information and/or delay information related to the SL CSI report;

The terminal device sends the destination address information and/or delay information related to the SL CSI report to the network device.

18. The method according to appendix 17, wherein the terminal device sending the destination address information and/or delay information related to the SL CSI report to the network device includes one of the following:

Sending, by the terminal device, one or more destination address information related to the SL CSI report and the delay information corresponding to each destination address information to the network device;

Sending, by the terminal device, one or more destination address information related to the SL CSI report and a delay information applied to the one or more destination address information to the network device;

Sending, by the terminal device, one or more destination address information related to the SL CSI report to the network device;

The terminal device sends to the network device one or more delay information corresponding to one or more destination address information related to the SL CSI report.

19. The method according to Supplement 17 or 18, wherein the destination address information includes at least one of the following:

20. The method according to Supplement 17 or 18, wherein the destination address information includes one of the following:

Trigger the L1 ID of the terminal device reported by the SL CSI;

Trigger the L2 ID of the terminal device reported by the SL CSI;

21. The method according to Supplement 17 or 18, wherein the delay information includes one of the following:

Predefined delay information.

22. The method according to Supplement 17, wherein:

The terminal device sends the destination address information and/or delay information related to the SL CSI report to the network device through a radio resource control (RRC) message.

23. A configuration method, wherein the method includes:

The network equipment receives the SL CSI reporting delay requirements sent by the terminal equipment;

The network device configures uplink resources for the SR related to the SL CSI report, and the uplink resource corresponding to the SR triggered by the SL CSI report meets the delay requirement of the SL CSI report.

24. The method according to Supplement 23, wherein the method further includes:

The network device sends an SR configuration to the terminal device, where the SR configuration includes uplink resources, and the SR configuration does not include the configuration of an SR prohibition timer.

25. A terminal device, wherein the terminal device includes a memory and a processor, the memory is stored with a computer program, and the processor is configured to execute the computer program to implement any item as described in Appendix 1-22 The method described.

26. A network device, wherein the terminal device includes a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to implement any one of items such as appendix 23-24 The method described.

27. A communication system, wherein the communication system includes: the terminal device described in appendix 25 and the network device described in appendix 26.

Claims

A processing device for scheduling requests, wherein the device includes:

A receiving unit, which receives the scheduling request configuration related to the side link channel state information report sent by the network device;

Processing unit, which performs one of the following operations:

For the scheduling request configuration related to the side link channel state information reporting, the scheduling request prohibition timer is not expected to be configured;

For the scheduling request configuration related to the side link channel state information reporting, the scheduling request prohibition timer is not applied;

For the scheduling request configuration related to the side link channel state information reporting, a scheduling request prohibition timer with a value of 0 is applied.
The apparatus according to claim 1, wherein for the scheduling request configuration related to the reporting of the side link channel state information, the domain of the scheduling request prohibition timer does not appear.
The apparatus according to claim 1, wherein the scheduling request configuration related to the side link channel state information report includes a scheduling request identifier.
The apparatus according to claim 3, wherein, in the scheduling request configuration related to the side link channel state information reporting, the domain of the scheduling request prohibition timer corresponding to the scheduling request identifier does not appear.
The device according to claim 1, wherein the device further comprises:

A sending unit, which sends the delay requirement for reporting the side link channel state information to the network device.
A processing device for scheduling requests, wherein the device includes:

An indication unit that instructs the physical layer at the media access control layer of the terminal device to send a scheduling request on an effective physical uplink control channel resource used for scheduling request transmission, and the scheduling request is triggered by side link channel state information reporting;

The processing unit does not start the scheduling request prohibition timer.
7. The apparatus according to claim 6, wherein the medium access control layer has a scheduling request transmission opportunity on the effective physical uplink control channel resource, and the effective physical uplink control channel resource does not overlap with a measurement gap.
The apparatus according to claim 6, wherein the effective physical uplink control channel resource does not overlap with the uplink shared channel resource, nor does it overlap with the side link shared channel resource.
The apparatus according to claim 6, wherein the effective physical uplink control channel resources overlap with uplink shared channel resources, and the side link channel state information reporting that triggers the scheduling request has a higher priority than the uplink The priority of the uplink grant of the link shared channel resource, wherein the priority of the uplink grant has not been lowered.
The apparatus according to claim 6, wherein the effective physical uplink control channel resources overlap with side link shared channel resources and the media access control layer of the terminal device cannot execute the scheduling request and the side link at the same time The priority of the side link channel state information reporting that triggers the scheduling request for the transmission of the shared channel resource is higher than the priority of the media access control protocol data unit included in the side link shared channel resource.
The apparatus according to claim 6, wherein the number of transmissions of the scheduling request is less than the configured maximum number of transmissions.
7. The apparatus according to claim 6, wherein the media access control layer of the terminal device does not receive a listen-before-speak failure indication from the physical layer.
7. The apparatus according to claim 6, wherein the processing unit does not start a scheduling request prohibition timer, and includes one of the following:

If the scheduling request is not triggered by the side link channel state information reporting, start the scheduling request prohibition timer;

If the scheduling request has nothing to do with the side link channel state information reporting, start a scheduling request prohibition timer;

If the scheduling request is triggered by the side link channel state information report, the scheduling request prohibition timer is not started or the value 0 is applied to the scheduling request prohibition timer.
The device according to claim 6, wherein the device further comprises:

A sending unit, which sends the delay requirement for reporting the side link channel state information to the network device.
A processing device for scheduling requests, wherein the device includes:

A receiving unit, which receives the scheduling request configuration related to the side link channel state information report sent by the network device;

The setting unit sets the value of the scheduling request counter in the scheduling request configuration according to the destination address reported by the side link channel state information.
The apparatus according to claim 15, wherein the terminal device triggers a scheduling request, and the scheduling request is triggered due to the triggering of the side link channel state information report, and is not corresponding to the scheduling request. If the scheduling request is configured for other scheduling requests in the pending state, or other scheduling requests that do not have the same side link channel state information reported as the destination address corresponding to the scheduling request and are in the pending state, the setting unit sets the scheduling request The value of the request counter is set to 0.
The apparatus according to claim 15, wherein if the scheduling request triggered by the reporting of side link channel state information of different destination addresses triggers the notification of the scheduling request from the media access control layer to the physical layer of the terminal device, the The setting unit increases the value of the scheduling request counter by one time.
The apparatus according to claim 15, wherein, if the destination address reported by the side link channel state information has not changed, the setting unit increases the value of the scheduling request counter by 1.
The apparatus according to claim 15, wherein the setting unit compares the product of the number of the destination addresses and the maximum number of dispatch requests in the scheduling request configuration as the value of the scheduling request counter The maximum number of dispatch requests sent.
The device according to claim 15, wherein the device further comprises:

The indicating unit, which instructs the physical layer to send the scheduling request when the value of the scheduling request counter is less than the maximum number of times of sending the scheduling request.