CN112586073A

CN112586073A - Scheduling request processing method, terminal equipment and storage medium

Info

Publication number: CN112586073A
Application number: CN201980054875.0A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-01-31
Filing date: 2019-01-31
Publication date: 2021-03-30
Anticipated expiration: 2039-01-31
Also published as: CN112586073B; WO2020155069A1

Abstract

The invention discloses a scheduling request processing method, which comprises the following steps: a Media Access Control (MAC) entity of the terminal equipment triggers a random access process corresponding to a second Scheduling Request (SR) and/or cancels the second SR; and/or the MAC entity sends first indication information to a physical layer, where the first indication information is used to indicate transmission information of a physical channel, or the first indication information is used to indicate transmission information of Uplink Control Information (UCI). The invention also discloses a terminal device and a storage medium.

Description

Scheduling request processing method, terminal equipment and storage medium

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a scheduling request processing method, a terminal device, and a storage medium.

Background

In a New Radio (NR) system, three application scenarios are divided based on service requirements, which are Enhanced Mobile bandwidth (eMBB), Massive Machine Type Communication (MMTC), and Ultra Reliable and Low Latency Communication (URLLC). When the eMBB service and the URLLC service coexist, Uplink Control Information (UCI) of the two types of services may overlap in the time domain, UCI of the two types of services may overlap with a physical channel in the time domain, UCI of the two types of services may overlap with data in the time domain, or a Control channel of the two types of services may overlap with a data channel in the time domain. In the related art, when the UCI of two types of services overlap in the time domain, or the UCI of two types of services overlaps with the physical channel in the time domain, the network device cannot timely know that the URLLC Service needs to be transmitted, which results in scheduling delay and a Quality of Service (QoS) requirement of the URLLC Service being unable to be satisfied.

Disclosure of Invention

In order to solve the foregoing technical problems, embodiments of the present invention provide a scheduling request processing method, a terminal device, and a storage medium, which can avoid scheduling delay and meet QoS requirements of URLLC services when UCI of two types of services overlap in a time domain, UCI of two types of services overlap with a physical channel in a time domain, UCI of two types of services overlap with data in a time domain, or control channels of two types of services overlap with a data channel in a time domain.

In a first aspect, an embodiment of the present invention provides a method for processing a scheduling request, where the method includes: a Media Access Control (MAC) entity of the terminal device triggers a random Access procedure corresponding to a second Scheduling Request (SR), and/or cancels the second SR; and/or the MAC entity sends first indication information to a physical layer, wherein the first indication information is used for indicating the transmission information of a physical channel corresponding to the random access process.

In a second aspect, an embodiment of the present invention provides a terminal device, where the terminal device includes a processing unit and/or a transceiver unit;

the processing unit is configured to trigger a random access procedure corresponding to a second SR, and/or cancel the second SR;

the transceiver unit is configured to transmit first indication information, where the first indication information is used to indicate transmission information of a physical channel corresponding to the random access procedure.

In a third aspect, an embodiment of the present invention provides a terminal device, including a processor and a memory, where the memory is used for storing a computer program that can be executed on the processor, and the processor is configured to execute the steps of the scheduling request processing method executed by the terminal device when the processor executes the computer program.

In a fourth aspect, an embodiment of the present invention provides a storage medium storing an executable program, where the executable program, when executed by a processor, implements a scheduling request processing method performed by the terminal device.

In the scheduling request processing method provided by the embodiment of the present invention, an MAC entity of a terminal device triggers a random access procedure corresponding to a second SR, and/or cancels the second SR; and/or the MAC entity sends first indication information to a physical layer, wherein the first indication information is used for indicating the transmission information or UCI of a physical channel. Since the transmission information of the physical channel includes at least one of the priority, preemption information, corresponding service information, data information, and logical channel information of the physical channel transmission, when the physical channel corresponding to the random access process triggered by the second SR conflicts with other channels, the physical layer can determine how to send the physical channel, UCI, and preferentially send the physical channel or other channels; therefore, the network equipment can timely know that the service (such as URLLC) with high priority needs to be transmitted, and the problems that the scheduling delay is delayed and the QoS of the service (such as URLLC) with high priority cannot be met are solved. In addition, when the SR is cancelled, the embodiments of the present invention enable the network device to timely know that a service with a high priority (such as URLLC) needs to be transmitted by performing differentiated processing on the SRs, that is, not cancelling all the SRs, thereby avoiding scheduling delay and the problem that the QoS of the service with a high priority (such as URLLC) cannot be satisfied.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention;

fig. 2 is a schematic view of an alternative processing flow of a scheduling request processing method according to an embodiment of the present invention;

fig. 3 is a schematic view of another alternative processing flow of a scheduling request processing method according to an embodiment of the present invention;

fig. 4 is a schematic diagram of an alternative composition structure of a terminal device according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a hardware component structure of an electronic device according to an embodiment of the present invention.

Detailed Description

So that the manner in which the features and technical contents of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the present invention will be rendered by reference to the appended drawings, which are included for purposes of illustration and not limitation.

Before describing the embodiment of the present invention in detail, first, a scenario that when the eMBB service and the URLLC service coexist and UCI of the two types of services and a physical channel overlap in a time domain in the related art is briefly described. In the related art, if an effective transmission resource is not configured for an SR triggered by an eMB service, or the transmission frequency of the SR reaches the maximum value, triggering the PRACH corresponding to the eMB service; if the PRACH conflicts or partially conflicts with the SR triggered by the URLLC service in the time domain, and the physical layer of the terminal device does not know the priority of the triggered PRACH and the priority of the PUCCH corresponding to the SR triggered by the URLLC service, or the physical layer does not know the service information of the channel transmission corresponding to the trigger, the terminal device selects one to transmit according to the implementation.

In order to solve the above problem, the present invention provides a scheduling request processing method, and the scheduling request processing method according to the embodiment of the present application may be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

As shown in fig. 2, an optional processing flow of the scheduling request processing method provided in the embodiment of the present invention includes the following steps:

step S201, the MAC entity of the terminal equipment triggers the random access process corresponding to the second SR and/or cancels the second SR; and/or the MAC entity sends first indication information to a physical layer, wherein the first indication information is used for indicating transmission information of a physical channel, or the first indication information is used for indicating transmission information of UCI.

In some embodiments, the MAC entity triggers a random access procedure corresponding to a second SR, and/or cancels the second SR.

In other embodiments, the MAC entity sends first indication information to the physical layer, where the first indication information is used to indicate transmission information of the physical channel.

In still other embodiments, the MAC entity triggers a random access procedure corresponding to a second SR, and/or cancels the second SR; and the MAC entity sends first indication information to a physical layer, wherein the first indication information is used for indicating transmission information of a physical channel.

Optionally, the physical channel may be a physical channel corresponding to the random access procedure, may also be a PUSCH channel, and may also be a PUCCH channel.

Here, the transmission information of the physical channel includes at least one of: the priority of the physical channel transmission, preemption information, corresponding service information, data information, and logical channel information. Optionally, the transmission information of the physical channel includes at least one of: and when the physical channel conflicts with other channels, the transmission priority of the physical channel, the preemption information, the corresponding service information, the data information and the logical channel information. Further, the transmission information of the physical channel may be used to indicate/determine the priority, preemption information, corresponding service information, data information, and logical channel information of the transmission of the physical channel when the physical channel collides with another channel. Wherein the logical channel information comprises at least one of: identification of logical channels and priority of logical channels. Wherein the service information includes at least one of: an identification of the service and a priority of the service. The Physical channels corresponding to the Random Access procedure include a Physical Random Access Channel (PRACH) and a transport Channel of Msg 3.

Optionally, the UCI includes at least one of: uplink SR, downlink hybrid automatic repeat request acknowledgement (HARQ-ACK) information, and CSI-RS information.

The method is applicable to a scenario in which the MAC entity sends the first indication information to the physical layer, when the number of SR transmissions reaches a maximum value, or when the SR is not configured with an effective transmission resource, or when the SR is configured with an effective transmission resource, or when the MAC entity indicates physical layer transmission or generation (generation) transmission, or when a Hybrid Automatic Repeat Request (HARQ) entity requests transmission, or when transmission information is obtained from the HARQ, or when the terminal device performs grant (Grand) transmission. Wherein the SR may be at least one of: a first SR and a second SR. It can be understood that, when the number of SR transmissions reaches a maximum value, the MAC entity sends the first indication information to a physical layer; or, when the SR, such as the second SR and/or the first SR, does not configure a valid transmission resource, the MAC entity sends the first indication information to the physical layer. Or, when the MAC entity indicates a physical layer transmission or generates a transmission, the MAC entity sends the first indication information to the physical layer; or, when a hybrid automatic repeat request HARQ entity requests transmission, the MAC entity or a functional entity (e.g., a HARQ entity) of the MAC entity sends the first indication information to a physical layer; or, when acquiring transmission information from HARQ, the MAC entity or its functional entity (e.g., HARQ entity) sends the first indication information to a physical layer; or, when the terminal device performs Grand transmission, the MAC entity sends the first indication information to a physical layer. The first indication information is used to indicate related information of uplink grant transmission by the physical layer, such as: whether the uplink grant can be transmitted or whether the uplink grant is transmitted preferentially, whether the uplink grant is preempted or the transmission of other physical channels is preempted, or how to transmit the uplink grant, or priority information of the uplink grant, or service/logical channel/MAC CE priority information corresponding to the uplink grant, or service/logical channel/MAC CE identification information corresponding to the uplink grant, and the like.

Here, the first indication information includes at least one of: preemption (Pre-election) indication, priority information, service priority information, and logical channel information. Wherein the priority information at least comprises a priority and/or a priority level and/or a priority identification and/or a priority indication; the service information at least comprises: a service type and/or a service identification; the service priority information at least comprises a service priority level and/or a service identifier and/or a service priority; the logical channel information comprises at least a logical channel priority and/or a logical channel identification. Optionally, the first indication information is further used for indicating transmission information of data and/or transmission information of a service.

The method is suitable for a scenario that the MAC entity triggers a random access process corresponding to the second SR and/or cancels the second SR, and the method is suitable for a scenario that the MAC entity does not configure effective transmission resources for the second SR, or the transmission times of the SRs reach the maximum value. It can be understood that, when the MAC entity does not configure a valid transmission resource for the second SR, or the transmission number of the SRs reaches a maximum value, the MAC entity triggers a random access procedure corresponding to the second SR. Or, when the MAC entity does not configure a valid transmission resource for the second SR, or the number of SR transmissions reaches a maximum value, the MAC entity cancels the second SR. Or, when the MAC entity does not configure an effective transmission resource for the second SR, or the transmission frequency of the SR reaches a maximum value, the MAC entity triggers a random access procedure corresponding to the second SR, and cancels the second SR.

In an optional embodiment, when the MAC entity does not configure a valid transmission resource for the second SR, and the physical channel triggered by the second SR overlaps with the resource of the first SR; or when the transmission times of the SRs reach a maximum value and the physical channel triggered by the second SR overlaps with the resource of the first SR, the MAC entity performs the following operations: the MAC entity cancels the physical channel, or the MAC entity cancels the random access procedure triggered by the second SR, or the MAC entity does not trigger the random access procedure corresponding to the second SR, or the MAC entity delays the random access procedure triggered by the second SR, or the MAC entity delays the physical channel. Optionally, the resource of the first SR may be a PUCCH resource, or a PUSCH resource carrying a BSR MAC CE corresponding to the first SR, or a PUSCH resource of a piggyback first SR, or a random access channel corresponding to the first SR, such as a PRACH, which carries a PUSCH of Msg 3. Optionally, the physical channel triggered by the second SR may be a PUCCH resource, or a PUSCH resource of a piggyback second SR, or a PUSCH resource carrying a BSR MAC CE corresponding to the second SR, or a random access channel corresponding to the second SR, such as a PRACH, carrying a PUSCH of Msg 3.

In another alternative embodiment, when the MAC entity does not configure a valid transmission resource for the second SR and the first SR exists; or when the transmission times of the SRs reach the maximum value and the first SR exists, the MAC entity delays triggering the random access process corresponding to the second SR. Optionally, the MAC entity triggers a random access procedure corresponding to the second SR after the resource corresponding to the first SR.

In yet another alternative embodiment, when the number of transmissions of an SR reaches a maximum value and the first condition is satisfied, the MAC entity cancels all SRs to be transmitted except the first SR.

Here, the first condition includes at least one of: the SR is triggered by a first service; the SR is triggered by a logical channel or a logical channel group carrying and/or corresponding to the first service; SR is triggered by logical channels with high priority identification; SR is triggered by a first type of logical channel; SR is not triggered by the second service; there is a first SR. Accordingly, the factor for judging that the first condition is satisfied includes at least one of: corresponding service identification or service priority; a service identifier or service priority to be transmitted; a corresponding logical channel identifier or logical channel priority; a corresponding logical channel group identity or logical channel group priority; a logical channel identifier or a logical channel priority to be transmitted; a logical channel group identifier or a logical channel group priority to be transmitted; whether the first SR is present. It can be understood that if the service meeting the corresponding service identifier or service priority or meeting the SR is triggered by the service of the corresponding specific service identifier or service priority, it is considered that the first condition is met; or the service meeting the specific service identifier or service priority to be transmitted or the service meeting the SR triggered by the specific service identifier or service priority to be transmitted is considered to meet the first condition; or the logical channel meeting the corresponding logical channel identifier or logical channel priority or meeting the SR is triggered by the logical channel corresponding to the specific logical channel identifier or logical channel priority, and then the first condition is considered to be met; or the logical channel group meeting the corresponding logical channel group identifier or logical channel group priority or meeting the SR is triggered by the logical channel group corresponding to the specific logical channel group identifier or logical channel group priority, it is considered that the first condition is met; or the logic channel meeting the logic channel identifier or the logic channel priority to be transmitted or the SR is triggered by the corresponding specific logic channel identifier or the logic channel priority to be transmitted, and then the first condition is considered to be met; or the requirement of meeting the logical channel group identifier to be transmitted or the logical channel group priority or the requirement of meeting the SR is triggered by the corresponding specific logical channel group identifier to be transmitted or the logical channel group priority logical channel group, and then the first condition is considered to be met; or whether there is a match with or a first SR, the first condition is considered to be satisfied.

In an embodiment of the present invention, the first SR includes at least one of: SR triggered by the first service; SR triggered by logical channel or logical channel group for carrying and/or corresponding to specific service; a logical channel triggered SR with a high priority identification; a first type logical channel triggered SR; a non-second traffic triggered SR.

Wherein, the first service is a specific service; optionally, the specific service includes at least one of: traffic with a particular value, traffic with a particular range identification, and traffic with a particular priority. Optionally, the SR triggered by the logical channel or the logical channel group carrying and/or corresponding to the specific service is: a logical channel, or logical channel group triggered SR carrying and/or corresponding to the first service. Optionally, the first type of logical channel comprises at least one of: logical channels corresponding to logical channel identifications having a specific value, logical channels corresponding to logical channel identifications having a specific range, logical channels corresponding to logical channel priorities having a specific value, and logical channels corresponding to logical channel priorities having a specific range. Optionally, the second service is an eMBB service, and the first service includes at least one of: URLLC traffic, Time Sensitive Network (TSN) traffic, and Vehicle to other device (V2X) traffic.

In an embodiment of the present invention, the second SR includes at least one of: a service triggered SR having a first priority, a logical channel or logical new channel group triggered SR having the first priority, and an SR other than the first SR. Optionally, the second SR is an SR other than the first SR among all triggered SRs. Optionally, the SRs other than the first SR include a second SR, or the SRs other than the first SR include a second SR and a third SR different from both the first SR and the second SR. Optionally, the first priority service is a low priority service, and the first priority service is an eMBB service; the logical channel of the first priority is a logical channel of a low priority, and the logical channel of the first priority is a logical channel corresponding to an eMBB service. It may be understood that the second SR is an eMBB service triggered SR, and the second SR is a low-priority logical channel triggered SR.

In particular implementations, the method further includes: the MAC entity triggers a random access process corresponding to the first SR, and/or cancels the first SR, and/or the MAC entity sends first indication information to a physical layer.

The above description is made correspondingly for the case that the second SR is not configured with valid transmission resources; for a scenario in which a second SR is configured with available transmission resources or the MAC entity instructs a physical layer to send an SR, the method further includes: and the MAC entity sends the first indication information to the physical layer.

When the second SR configures an effective transmission resource, when the MAC entity has an SR transmission opportunity on the effective resource configured for the SR, and a second SR transmission time prohibit timer (SR-prohibit timer) does not operate, and the second SR transmitted resource does not overlap with the measurement gap, and the second SR transmitted resource does not overlap with an uplink SCHeduling (UL-SCH) resource, if the value of the SR timer is smaller than the value of the prohibit timer, that is, SR _ COUNTER < SR-max, the value of R _ COUNTER is added by 1, the MAC entity instructs the physical layer to transmit the second SR on the effective resource corresponding to the second SR, starts SR-prohibit timer, and the MAC entity transmits first indication information to the physical layer. If the value of the SR timer is larger than the value of the prohibition timer, namely SR _ COUNTER > SR-TransMax, the MAC entity informs the RRC to release PUCCH for each serving cell, informs the RRC to release channel Sounding Reference signals (Sounding Reference Signal, SRS) for each serving cell, clears all configured downlink resource allocation and uplink resource authorization, triggers a random access process on the cell, cancels all SRs to be transmitted, and sends first indication information to the physical layer.

It should be noted that the random access procedure according to the embodiment of the present invention is a random access procedure in a primary and secondary cell (PSCell).

Before performing step S201, the method further includes:

step S200, the MAC entity receives second indication information sent by a network device or the physical layer, where the second indication information is used to indicate at least one of the following: the MAC entity sends first indication information, the related information of the physical channel, the related information of the UCI sent by the MAC entity, the related processing information of the SR, and/or the related processing information of data, the related processing information of service and the related processing information of the logical channel.

Optionally, the first indication information and/or the information related to the physical channel and/or the UCI includes at least one of: the priority of the physical channel transmission, preemption information, corresponding service information, data information, and logical channel information. Optionally, the information related to the physical channel and/or UCI includes at least one of: and when the physical channel conflicts with other channels, the transmission priority of the physical channel, the preemption information, the corresponding service information, the data information and the logical channel information. Further, the transmission information of the physical channel and/or the UCI may be used to indicate/determine the priority, preemption information, corresponding service information, data information, and logical channel information of the physical channel transmission when the physical channel collides with another channel.

Optionally, the first indication information and/or the data and/or traffic and/or logical channel and/or SR related processing information includes at least one of: priority of transmission, preemption information, corresponding service information, data information, and logical channel information. Optionally, the processing information related to the data and/or traffic and/or logical channel and/or SR includes at least one of the following: and when the object conflicts with other channels/UCI/data/grant, the transmission priority, the preemption information, the corresponding service information, the data information and the logic channel information. Further, the processing information related to the data and/or traffic and/or logical channel and/or SR may be used to indicate/determine the priority of the object transmission, preemption information, corresponding traffic information, data information, and logical channel information when the object collides with other channels/UCI/data/grant.

Wherein the logical channel information comprises at least one of: identification of logical channels and priority of logical channels. Wherein the service information includes at least one of: an identification of the service and a priority of the service.

The related information of the SR comprises at least one of the following: whether the MAC entity triggers a random access process corresponding to the second SR and/or cancels the second SR.

Another optional processing flow of the scheduling request processing method provided in the embodiment of the present invention, as shown in fig. 3, includes the following steps:

step S301, the network device configures SR parameters and SR resources for different logical channels or different services, and notifies the terminal device of the SR parameters and SR resources.

Optionally, the SR parameter is at least one of: SR ID, Scheduling Request Id, SR configuration ID.

Step S302, the terminal equipment determines at least one of the following information according to the indication of the network equipment: corresponding logical channels, service SR, SR resources, corresponding relation between SR and SR resources, and corresponding SR and SR resources.

In step S303, when the second SR does not configure a valid PUCCH resource or reaches the maximum SR transmission frequency, the MAC entity of the terminal device performs the following operations.

Optionally, the MAC processes the first SR and/or the second SR, respectively.

A. When the second SR does not configure a valid PUCCH resource, the MAC entity performs any one of the following operations:

1) and the MAC entity triggers a random access process corresponding to the second SR.

2) The MAC entity cancels the second SR.

3) And the MAC entity triggers a random access process corresponding to the second SR and cancels the second SR.

4) When a first SR exists and a physical channel triggered by a second SR overlaps with a resource of the first SR, a MAC entity cancels the physical channel, or the MAC entity cancels a random access procedure triggered by the second SR, or the MAC entity does not trigger a random access procedure corresponding to the second SR, or the MAC entity delays triggering the random access procedure triggered by the second SR, or the MAC entity delays the random access procedure triggered by the second SR.

5) And when the first SR exists, the MAC entity delays to trigger the random access process corresponding to the second SR or triggers the random access process corresponding to the second SR at a time after the PUCCH resource corresponding to the first SR. .

B. When the SR maximum transmission times is reached, the MAC entity executes any one of the following operations:

2) The MAC entity cancels all SRs to be transmitted except the first SR.

3) The MAC entity triggers a random access process corresponding to the second SR and cancels all the SRs to be transmitted except the first SR. In the related art, when the maximum number of SR transmissions is reached, the MAC entity cancels all SRs to be transmitted. For R16, it supports to distinguish SR triggered by low priority service (e.g. eMBB) from SR triggered by high priority service (e.g. URLLC); at this time, if the SR triggered by the eMBB service reaches the maximum retransmission times, the SR triggered by the URLLC service is still cancelled, which may cause the network to fail to know in time that the URLLC service needs to be transmitted, resulting in scheduling delay and a problem that the QoS of the URLLC service cannot be satisfied; the embodiment of the invention can still not cancel the retransmission of the first SR (SR corresponding to the URLLC service) when the SR reaches the maximum retransmission times by carrying out differential processing on the SRs, so that the network equipment can timely know that the URLLC service needs to be transmitted, and the problems of scheduling delay and unsatisfiable QoS of the URLLC service are avoided.

Optionally, when the second SR is not configured with a valid PUCCH resource or reaches the SR maximum transmission number or is configured with a valid PUCCH resource or is less than the SR maximum transmission number, the MAC entity of the terminal device performs the following operations:

C. the MAC entity of the terminal equipment also sends first indication information to the physical layer, wherein the first indication information is used for indicating the transmission information of the physical channel.

Optionally, when the first SR is not configured with a valid PUCCH resource or reaches the SR maximum transmission number or is configured with a valid PUCCH resource or is less than the SR maximum transmission number, the MAC entity of the terminal device performs the following operations:

the MAC entity of the terminal equipment also sends first indication information to the physical layer, wherein the first indication information is used for indicating the transmission information of the physical channel or the transmission information of the UCI.

Because the transmission information of the physical channel comprises at least one item of priority, preemption information, corresponding service information, data information and logic channel information of physical channel transmission, when the physical channel corresponding to the random access process triggered by the second SR conflicts with other channels, the physical layer can determine whether to preferentially send the physical channel or other channels; when the other channels transmit the logic channels corresponding to the services with high priority, if the logic channels corresponding to the URLLC services, the logic channels corresponding to the URLLC services are transmitted preferentially; and the physical channel corresponding to the random access procedure triggered by the second SR is either cancelled or transmitted after the transmission of the logical channel corresponding to the URLLC service. According to the embodiment of the invention, the physical layer can send the corresponding channel and UCI according to the priority indicated by the first indication information and preferentially send the physical channel or other channels according to the priority indicated by the first indication information; therefore, the network equipment can timely know that the service (such as URLLC) with high priority needs to be transmitted, and avoid scheduling delay and the problem that the QoS of the service (such as URLLC) with high priority cannot be met.

It should be noted that, in the embodiment of the present invention, descriptions for the first SR, the second SR, and the first indication information are the same as those of the above embodiment, and are not repeated herein; the operation C may be performed separately, that is, when the operation C is performed, the operation a and the operation B are not performed; operation C may also be combined with operations a, B, i.e., performing operation a and operation C, or performing operation B and operation C, or performing operation a, operation B, and operation C.

Optionally, when the MAC entity indicates a physical layer transmission or generates a transmission, the MAC entity sends the first indication information to the physical layer; or, when a hybrid automatic repeat request HARQ entity requests transmission, the MAC entity or its functional entity (e.g., HARQ entity) sends the first indication information to a physical layer; or, when transmission information is acquired from a hybrid automatic repeat request HARQ, the MAC entity or a functional entity (e.g., a HARQ entity) thereof sends the first indication information to a physical layer; or, when the terminal device performs Grand transmission, the MAC entity sends the first indication information to a physical layer. The first indication information is used to indicate related information of uplink grant transmission by the physical layer, such as: whether the uplink grant can be transmitted or whether the uplink grant is transmitted preferentially, whether the uplink grant is preempted or the transmission of other physical channels is preempted, or how to transmit the uplink grant, or priority information of the uplink grant, or service/logical channel/MAC CE priority information corresponding to the uplink grant, or service/logical channel/MAC CE identification information corresponding to the uplink grant, and the like.

Optionally, the MAC entity sends the first indication information to the physical layer according to a network indication or a physical layer indication, or after receiving the network indication or the physical layer indication. For example, when a hybrid automatic repeat request HARQ entity requests transmission after receiving a network indication or a physical layer indication, the MAC entity or a functional entity thereof (e.g., a HARQ entity) sends the first indication information to a physical layer. Also, for example, after receiving a network indication or a physical layer indication, the MAC entity performs an operation for the first SR, the second SR, and the first indication information.

The following describes a processing procedure of the scheduling request processing method according to the embodiment of the present invention based on different scenarios.

Scene 1

As long as there is a pending SR, the following operations are performed on each pending SR MAC entity:

1> if the MAC entity does not have a valid PUCCH resource configured for this pending SR:

2> trigger the random access procedure on the SpCell, cancelling this pending SR;

2> indicates physical layer first indication information.

1> otherwise, SR configuration for this pending SR:

2> when the MAC entity has one SR transmission opportunity on the valid PUCCH resource configured for SR; and is

2> if SR-ProhibitTimer is not running at this SR transmission time SR; and is

2> if the PUCCH resources for SR transmission do not overlap with the measurement gap; and is

2> if the PUCCH resource for SR transmission does not overlap with the UL-SCH resource:

3> if SR _ COUNTER < SR-TransMax:

4> SR _ COUNTER plus 1;

4> indicate to the physical layer to send this SR on the valid PUCCH resource corresponding to this SR;

4> turn sr-ProhibitTimer on.

4> indicates physical layer first indication information.

3> otherwise:

4> inform RRC to release PUCCH for each serving cell;

4> inform RRC to release SRS for each serving cell;

4> emptying all configured downlink resource allocation and uplink resource grants;

4> trigger the random access process on the SpCell, cancelling all pending SRs;

4> indicates physical layer first indication information.

The first indication information includes, but is not limited to, at least one of:

-Pre-indication;

-priority information, such as priority, priority level, priority indication, priority identification, etc.;

-corresponding service type information, such as identity, type, etc.;

-corresponding traffic priority information, such as identification, priority level, priority indication, etc.;

logical channel information such as priority, identity, etc.

In the embodiment of the present invention, the indicating the first indication information of the physical layer is optional, that is, the first indication information of the physical layer may be indicated, or the first indication information of the physical layer may not be indicated.

Scene 2

2> trigger random access procedure on SpCell;

2> if the pending SR is the second SR, and the available PRACH resources of the triggered random access procedure overlap with the PUCCH resources triggered by the first SR:

3> cancel triggered random access procedure on SpCell.

·2>else：

3> cancel this pending SR.

2> indicates physical layer first indication information.

1> otherwise, SR configuration for this pending SR:

2> if SR-ProhibitTimer is not running at this SR transmission time SR; and is

3> if SR _ COUNTER < SR-TransMax:

4> SR _ COUNTER plus 1;

4> turn sr-ProhibitTimer on.

4> indicates physical layer first indication information.

3> otherwise:

4> inform RRC to release PUCCH for each serving cell;

4> inform RRC to release SRS for each serving cell;

4> trigger the random access process on the SpCell, cancelling all pending SRs;

4> indicates physical layer first indication information.

-Pre-indication;

-priority information, such as priority, priority identification, priority level, priority indication, etc.;

-corresponding service type information, such as identity, type, etc.;

-corresponding traffic priority information, such as identification, priority identification, priority class, priority indication, etc.;

logical channel information such as priority, identity, etc.

Scene three

3> cancel triggered random access procedure on SpCell.

2> indicates physical layer first indication information.

1> otherwise, SR configuration for this pending SR:

2> if SR-ProhibitTimer is not running at this SR transmission time SR; and is

3> if SR _ COUNTER < SR-TransMax:

4> SR _ COUNTER plus 1;

4> turn sr-ProhibitTimer on.

4> indicates physical layer first indication information.

3> otherwise:

4> inform RRC to release PUCCH for each serving cell;

4> inform RRC to release SRS for each serving cell;

4> trigger the random access process on the SpCell, cancelling all pending SRs;

4> indicates physical layer first indication information.

-Pre-indication;

-corresponding service type information, such as identity, type, etc.;

logical channel information such as priority, identity, etc.

Scene four

And when no effective PUCCH resource is configured for the second SR, if the first SR exists, deferring the trigger random access process corresponding to the second SR, or triggering the random access process corresponding to the second SR at a time after the PUCCH resource corresponding to the first SR.

Optionally, the MAC indicates the first indication information to the physical layer.

An alternative procedure is as follows:

as long as there is a pending SR, the MAC entity will do the following operations:

1> if there is a first SR, for each pending SR:

2> the MAC entity has no valid PUCCH resources configured for this pending SR:

3> if SR is the first SR:

4, triggering a random access process on the SpCell, and canceling the pending SR;

3> otherwise:

4> triggering the random access process on the SpCell after the PUCCH resource position corresponding to the first SR,

cancel this pending SR;

2> otherwise, SR configuration for this pending SR:

3> when the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for the SR; and is

3> if the SR transmission time SR-ProhibitTimer is not running; and is

3> if the PUCCH resource transmitted by the SR does not overlap with the measurement gap; and is

3> if the PUCCH resource and UL-SCH resource of SR transmission do not overlap:

4> if SR _ COUNTER < SR-TransMax:

5> SR _ COUNTER plus 1;

5> indicates the physical layer to transmit the SR on the valid PUCCH resource corresponding to the SR;

5> turn on sr-ProhibitTimer.

4> otherwise:

5> informing the RRC to release the PUCCH for each serving cell;

5> informing the RRC to release the SRS for each serving cell;

5, emptying all configured downlink resource allocation and uplink resource authorization;

and 5> triggering a random access process on the SpCell and canceling all pending SRs.

1> otherwise, for each pending SR:

2> the MAC entity has no valid PUCCH resources configured for this pending SR:

3> triggering a random access process on the SpCell, and canceling the pending SR;

2> otherwise, SR configuration for this pending SR:

3> when the MAC entity has one SR transmission opportunity on the effective PUCCH resource configured for SR; and is

3> if the SR transmission time SR-ProhibitTimer is not running; and is

3> if the PUCCH resource and UL-SCH resource of SR transmission do not overlap:

4> if SR _ COUNTER < SR-TransMax:

5> SR _ COUNTER plus 1;

5> turn on sr-ProhibitTimer.

4> otherwise:

5> informing the RRC to release the PUCCH for each serving cell;

5> informing the RRC to release the SRS for each serving cell;

Another alternative process is as follows:

1> if there is a first SR present,

2> first SR for each pending:

3> no valid PUCCH resource configured for this pending SR by the MAC entity:

3> otherwise, the SR configuration corresponding to the pending SR:

4> when the MAC entity has one SR transmission opportunity on the effective PUCCH resource configured for SR; and is

4> if the SR transmission time SR-ProhibitTimer is not running; and is

4> if the PUCCH resource transmitted by the SR does not overlap with the measurement gap; and is

4> if the PUCCH resource and UL-SCH resource of SR transmission do not overlap:

5> if SR _ COUNTER < SR-TransMax:

6> SR _ COUNTER plus 1;

6> indicates the physical layer to transmit the SR on the valid PUCCH resource corresponding to the SR;

6> turn sr-ProhibitTimer on.

5> otherwise:

6> informing RRC to release PUCCH for each serving cell;

6> informing the RRC to release the SRS for each serving cell;

6, emptying all configured downlink resource allocation and uplink resource authorization;

6> trigger the random access process on the SpCell, and cancel all pending SRs.

2> for other pending SR:

3> no valid PUCCH resource configured for this pending SR by the MAC entity:

cancel this pending SR;

3> otherwise, the SR configuration corresponding to the pending SR:

4> if the SR transmission time SR-ProhibitTimer is not running; and is

4> if the PUCCH resource and UL-SCH resource of SR transmission do not overlap:

5> if SR _ COUNTER < SR-TransMax:

6> SR _ COUNTER plus 1;

6> turn sr-ProhibitTimer on.

5> otherwise:

6> informing RRC to release PUCCH for each serving cell;

6> informing the RRC to release the SRS for each serving cell;

6> trigger the random access process on the SpCell, and cancel all pending SRs.

1> otherwise, for each pending SR:

2> the MAC entity has no valid PUCCH resources configured for this pending SR:

2> otherwise, SR configuration for this pending SR:

3> when the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for SR

When the current is over; and is

3> if the SR transmission time SR-ProhibitTimer is not running; and is

3> if the PUCCH resource and UL-SCH resource of SR transmission do not overlap:

4> if SR _ COUNTER < SR-TransMax:

5> SR _ COUNTER plus 1;

5> turn on sr-ProhibitTimer.

4> otherwise:

5> informing the RRC to release the PUCCH for each serving cell;

5> informing the RRC to release the SRS for each serving cell;

Scene five

2> triggering a random access process on the SpCell, and canceling the pending SR;

1> otherwise, SR configuration for this pending SR:

2> when the MAC entity has one SR transmission opportunity on the effective PUCCH resource configured for SR; and is

2> if the SR transmission time SR-ProhibitTimer is not running; and is

2> if the PUCCH resources transmitted by the SR do not overlap with the measurement gap; and is

2> if the PUCCH resource and UL-SCH resource of SR transmission do not overlap:

3> if SR _ COUNTER < SR-TransMax:

4> SR _ COUNTER plus 1;

4> indicates the physical layer to transmit the SR on the valid PUCCH resource corresponding to the SR;

4> indicates physical layer first indication information;

4> turn on sr-ProhibitTimer.

3> otherwise:

4> informing the RRC to release the PUCCH for each serving cell;

4> informing the RRC to release the SRS for each serving cell;

4, emptying all configured downlink resource allocation and uplink resource authorization;

4> triggering a random access process on the SpCell;

4, if the first condition is met, all pending SRs are cancelled, otherwise all pending SRs except the first SR are cancelled;

4> indicates physical layer first indication information.

In order to implement the foregoing scheduling request processing method, an embodiment of the present invention provides a terminal device, where the terminal device has a structure as shown in fig. 4, where the terminal device 400 includes: a processing unit 401, and/or a transceiving unit 402;

the processing unit 401 is configured to trigger a random access procedure corresponding to a second SR, and/or cancel the second SR;

the transceiving unit 402 is configured to send first indication information, where the first indication information is used to indicate transmission information of a physical channel, or the first indication information is used to indicate transmission information of UCI.

In some embodiments, the transmission information of the physical channel comprises at least one of:

the priority of the physical channel transmission, preemption information, corresponding service information, data information, and logical channel information.

In some embodiments, the transmission information of the physical channel is used to indicate or determine the priority, preemption information, corresponding traffic information, data information, and logical channel information of the transmission of the physical channel when the physical channel collides with another channel.

In some embodiments, when the number of transmission times of the SR reaches a maximum value and a first condition is satisfied, the processing unit is configured to cancel all SRs to be transmitted except the first SR.

In some embodiments, when the number of SR transmissions reaches a maximum value, the transceiver 402 is configured to transmit the first indication information.

In some embodiments, when the second SR is not configured with valid transmission resources, the processing unit 401 is configured to trigger a random access procedure corresponding to the second SR, and/or cancel the second SR;

the transceiving unit 402 is configured to transmit the first indication information.

In some embodiments, when the processing unit 401 indicates physical layer transmission or generation transmission, or when a HARQ entity requests transmission, or obtains transmission information from a HARQ, or when the terminal device performs Grand transmission, the transceiving unit 402 is configured to send the first indication information.

In some embodiments, when the physical channel overlaps with the resource of the first SR, the processing unit is configured to cancel the physical channel, or cancel the random access procedure triggered by the second SR, or not trigger the random access procedure corresponding to the second SR, or delay triggering the random access procedure triggered by the second SR, or delay triggering the physical channel by the MAC entity.

In some embodiments, when the first SR exists, the processing unit 401 is configured to delay triggering of the random access procedure corresponding to the second SR.

In some embodiments, the processing unit 401 is configured to trigger a random access procedure corresponding to the second SR after the resource corresponding to the first SR.

In some embodiments, the first condition comprises at least one of:

the SR is triggered by a first service;

the SR is triggered by a logical channel or a logical channel group carrying and/or corresponding to the first service;

SR is triggered by logical channels with high priority identification;

SR is triggered by a first type of logical channel;

SR is not triggered by the second service;

there is a first SR.

In some embodiments, the first traffic comprises at least one of:

traffic with a specific value, traffic with a specific range identification, and traffic with a specific priority.

In some embodiments, the first type of logical channel comprises at least one of:

logical channels having logical channel identifications of a specific value or a specific range, and logical channels having logical channel priorities of a specific value or a specific range.

In some embodiments, determining that the first condition is satisfied includes at least one of:

corresponding service identification or service priority;

a service identifier or service priority to be transmitted;

a corresponding logical channel identifier or logical channel priority;

a corresponding logical channel group identity or logical channel group priority;

a logical channel identifier or a logical channel priority to be transmitted;

a logical channel group identifier or a logical channel group priority to be transmitted;

whether the first SR is present.

In some embodiments, the second SR comprises at least one of:

a service triggered SR having a first priority;

a logical channel or logical new group of channels with a first priority triggers an SR.

In some embodiments, the first SR comprises at least one of:

SR triggered by the first service;

SR triggered by logical channel or logical channel group for carrying and/or corresponding to specific service;

a logical channel triggered SR with a high priority identification;

a first type logical channel triggered SR;

a non-second service triggered SR;

an SR other than the first SR.

In some embodiments, the first traffic comprises at least one of: URLLC traffic, TSN traffic, and V2X traffic.

In some embodiments, the first indication information comprises at least one of a Pre-preemption indication; priority information; service information; service priority information; logical channel information.

In some embodiments, the first indication information is further used for indicating transmission information of data and/or transmission information of traffic.

In some embodiments, the transceiving unit 402 is further configured to receive second indication information sent by a network device or the physical layer, where the second indication information is used to indicate that the MAC entity sends information related to the physical channel and/or processing information related to the SR.

In some embodiments, when the second SR configures a valid transmission resource or the MAC entity instructs a physical layer to transmit an SR, the transceiver 402 is further configured to transmit the first indication information.

In some embodiments, the processing unit 401 is further configured to trigger a random access procedure corresponding to the first SR, and/or cancel the first SR.

In some embodiments, the physical channel comprises at least one of: PRACH, Msg3, PUSCH, and PUCCH.

In specific implementation, the processing unit 401 and the transceiver unit 402 are structural units of a MAC entity of a terminal device.

The embodiment of the present invention further provides a terminal device, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the scheduling request processing method executed by the terminal device when running the computer program.

Fig. 5 is a schematic diagram of a hardware configuration of an electronic device (terminal device) according to an embodiment of the present invention, where the electronic device 1000 includes: at least one processor 1001, memory 1002, and at least one network interface 1004. The various components in the electronic device 1000 are coupled together by a bus system 1005. It is understood that bus system 1005 is used to enable communications among the components connected. The bus system 1005 includes a power bus, a control bus, and a status signal bus, in addition to a data bus. But for the sake of clarity the various busses are labeled in figure 5 as the bus system 1005.

It will be appreciated that the memory 1002 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. The non-volatile Memory may be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic random access Memory (FRAM), Flash Memory (Flash Memory), magnetic surface Memory, optical Disc, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 1002 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory 1002 in embodiments of the present invention is used to store various types of data in support of the operation of the electronic device 1000. Examples of such data include: any computer program for operating on the electronic device 1000, such as the application program 10022. The program implementing the method according to the embodiment of the present invention may be included in the application program 10022.

The method disclosed by the embodiment of the invention can be applied to the processor 1001 or can be implemented by the processor 1001. The processor 1001 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1001. The Processor 1001 may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 1001 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed by the embodiment of the invention can be directly implemented by a hardware decoding processor, or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 1002 and the processor 1001 reads the information from the memory 1002 and performs the steps of the method described above in conjunction with its hardware.

In an exemplary embodiment, the electronic Device 1000 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic components for performing the foregoing methods.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

In the above embodiments of the present invention, "/" means "or"; A/B represents A or B.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.

Claims

A method of scheduling request processing, the method comprising:

a Media Access Control (MAC) entity of the terminal equipment triggers a random access process corresponding to a second Scheduling Request (SR) and/or cancels the second SR;

and/or the MAC entity sends first indication information to a physical layer, where the first indication information is used to indicate transmission information of a physical channel, or the first indication information is used to indicate transmission information of uplink control information UCI.
The method of claim 1, wherein the transmission information of the physical channel comprises at least one of:

the priority of the physical channel transmission, preemption information, corresponding service information, data information, and logical channel information.
The method of claim 2, wherein the transmission information of the physical channel is used to indicate or determine the priority, preemption information, corresponding traffic information, data information, and logical channel information for the physical channel transmission when the physical channel collides with other channels.
The method according to any one of claims 1 to 3, wherein the number of transmissions of the SR reaches a maximum value, and when a first condition is satisfied, the MAC entity cancels all SRs to be transmitted except the first SR.
The method according to any one of claims 1 to 3, wherein the MAC entity transmits the first indication information to a physical layer when the number of transmissions of the SR reaches a maximum value.
The method according to any one of claims 1 to 3, wherein when the second SR is not configured with valid transmission resources, the MAC entity triggers a random access procedure corresponding to the second SR, and/or cancels the second SR, and/or sends the first indication information to a physical layer.
The method according to any of claims 1 to 3, wherein when the MAC entity indicates physical layer transmission or generates generic transmission, or when a hybrid automatic repeat request (HARQ) entity requests transmission, or when transmission information is obtained from HARQ, or when the terminal equipment performs grant Grand transmission,

and the MAC entity sends the first indication information to a physical layer.
The method according to any of claims 1 to 7, wherein, when the physical channel overlaps with resources of the first SR,

the MAC entity cancels the physical channel;

or the MAC entity cancels the random access process triggered by the second SR;

or the MAC entity does not trigger the random access procedure corresponding to the second SR;

or the MAC entity delays a random access procedure triggering the second SR;

or the MAC entity delays the random access procedure triggered by the second SR;

or the MAC entity delays triggering the physical channel.
The method according to any of claims 1 to 8, wherein the MAC entity delays triggering of a random access procedure corresponding to the second SR when the first SR is present.
The method of claim 9, wherein the MAC entity triggers a random access procedure for the second SR after the resource for the first SR.
The method of claim 4, wherein the first condition comprises at least one of:

the SR is triggered by a first service;

the SR is triggered by a logical channel or a logical channel group carrying and/or corresponding to the first service;

SR is triggered by logical channels with high priority identification;

SR is triggered by a first type of logical channel;

SR is not triggered by the second service;

there is a first SR.
The method of claim 11, wherein the first traffic comprises at least one of:

traffic with a specific value, traffic with a specific range identification, and traffic with a specific priority.
The method according to claim 11 or 12, wherein the first type of logical channel comprises at least one of:

logical channels having logical channel identifications of a specific value or a specific range, and logical channels having logical channel priorities of a specific value or a specific range.
The method according to any one of claims 4, 11 to 13, wherein determining that the first condition is satisfied includes at least one of:

corresponding service identification or service priority;

a service identifier or service priority to be transmitted;

a corresponding logical channel identifier or logical channel priority;

a corresponding logical channel group identity or logical channel group priority;

a logical channel identifier or a logical channel priority to be transmitted;

a logical channel group identifier or a logical channel group priority to be transmitted;

whether the first SR is present.
The method of any of claims 1 to 14, wherein the second SR comprises at least one of:

a service triggered SR having a first priority;

a logical channel or logical new channel group triggered SR having a first priority;

an SR other than the first SR.
The method of any of claims 1 to 15, wherein the first SR comprises at least one of:

SR triggered by the first service;

SR triggered by logical channel or logical channel group for carrying and/or corresponding to specific service;

a logical channel triggered SR with a high priority identification;

a first type logical channel triggered SR;

a non-second traffic triggered SR.
The method according to any of claims 10 to 13, 16, wherein the first traffic comprises at least one of:

ultra-reliable low-latency communication URLLC traffic, time-sensitive network TSN traffic, and vehicle-to-other device V2X traffic.
The method of any of claims 1 to 17, wherein the first indication information comprises at least one of:

preempting the Pre-indication;

priority information;

service information;

service priority information;

logical channel information.
The method according to any one of claims 1 to 18, wherein the first indication information is further used for indicating transmission information of data and/or transmission information of traffic.
The method of any one of claims 1 to 19, wherein the method further comprises:

the MAC entity receives second indication information sent by a network device or the physical layer, where the second indication information is used to indicate at least one of the following:

the MAC entity sends the first indication information;

the related information of the physical channel and/or the related information of the UCI;

processing information related to the SR;

processing information related to the data;

and processing information related to the service.
The method of any one of claims 1 to 20, wherein the method further comprises:

and when the second SR configures effective transmission resources or the MAC entity indicates a physical layer to send the SR, the MAC entity sends the first indication information to the physical layer.
The method of any one of claims 1 to 21, wherein the method further comprises:

and the MAC entity triggers a random access process corresponding to the first SR and/or cancels the first SR.
The method of any of claims 1 to 22, wherein the physical channel comprises at least one of:

a physical random access channel PRACH, a transport channel of Msg3, a physical uplink shared channel PUSCH, and a physical uplink control channel PUCCH.
A terminal device, the terminal device comprising: a processing unit and/or a transceiver unit;

the processing unit is configured to trigger a random access procedure corresponding to a second Scheduling Request (SR), and/or cancel the second SR;

the transceiver unit is configured to send first indication information, where the first indication information is used to indicate transmission information of a physical channel, or the first indication information is used to indicate transmission information of uplink control information UCI.
The terminal device of claim 24, wherein the transmission information of the physical channel comprises at least one of:

the priority of the physical channel transmission, preemption information, corresponding service information, data information, and logical channel information.
The terminal device of claim 25, wherein the transmission information of the physical channel is used to indicate or determine the priority, preemption information, corresponding traffic information, data information, and logical channel information for transmission of the physical channel when the physical channel collides with another channel.
The terminal device according to claims 24 to 26, wherein when the number of transmissions of the SR reaches a maximum value and a first condition is satisfied, the processing unit is configured to cancel all SRs to be transmitted except the first SR.
The terminal device according to claims 24 to 26, wherein when the number of SR transmissions reaches a maximum value, the transceiver unit is configured to transmit the first indication information.
The terminal device of claims 24 to 26, wherein, when the second SR is not configured with valid transmission resources,

the processing unit is configured to trigger a random access procedure corresponding to the second SR, and/or cancel the second SR;

the transceiver unit is configured to transmit the first indication information.
The terminal device according to claims 24 to 26, wherein the processing unit instructs physical layer transmission or generation of generic transmission, or hybrid automatic repeat request HARQ entity to request transmission, or obtains transmission information from HARQ, or the terminal device performs grant Grand transmission,

the transceiver unit is configured to transmit the first indication information.
The terminal device according to any of claims 24 to 30, wherein, when the physical channel overlaps with the resource of the first SR, the processing unit is configured to cancel the physical channel;

or canceling the random access process triggered by the second SR;

or not triggering the random access process corresponding to the second SR;

or delaying a random access procedure triggering the second SR trigger;

or delaying the random access procedure triggered by the second SR;

or the MAC entity delays triggering the physical channel.
The terminal device according to any one of claims 24 to 31, wherein, in the presence of the first SR, the processing unit is configured to delay triggering of a random access procedure corresponding to the second SR.
The terminal device of claim 32, wherein the processing unit is configured to trigger a random access procedure corresponding to the second SR after the resource corresponding to the first SR.
The terminal device of claim 27, wherein the first condition comprises at least one of:

the SR is triggered by a first service;

the SR is triggered by a logical channel or a logical channel group carrying and/or corresponding to the first service;

SR is triggered by logical channels with high priority identification;

SR is triggered by a first type of logical channel;

SR is not triggered by the second service;

there is a first SR.
The terminal device of claim 34, wherein the first traffic comprises at least one of:

traffic with a specific value, traffic with a specific range identification, and traffic with a specific priority.
The terminal device of claim 34 or 35, wherein the first type of logical channel comprises at least one of:

logical channels having logical channel identifications of a specific value or a specific range, and logical channels having logical channel priorities of a specific value or a specific range.
The terminal device of any of claims 27 and 34 to 36, wherein the factor determining that the first condition is met comprises at least one of:

corresponding service identification or service priority;

a service identifier or service priority to be transmitted;

a corresponding logical channel identifier or logical channel priority;

a corresponding logical channel group identity or logical channel group priority;

a logical channel identifier or a logical channel priority to be transmitted;

a logical channel group identifier or a logical channel group priority to be transmitted;

whether the first SR is present.
The terminal device of any of claims 24 to 37, wherein the second SR comprises at least one of:

a service triggered SR having a first priority;

a logical channel or logical new channel group triggered SR having a first priority;

an SR other than the first SR.
The terminal device of any of claims 24 to 38, wherein the first SR comprises at least one of:

SR triggered by the first service;

SR triggered by logical channel or logical channel group for carrying and/or corresponding to specific service;

a logical channel triggered SR with a high priority identification;

a first type logical channel triggered SR;

a non-second traffic triggered SR.
The terminal device of any one of claims 33 to 36, 39, wherein the first traffic comprises at least one of:

ultra-reliable low-latency communication URLLC traffic, time-sensitive network TSN traffic, and vehicle-to-other device V2X traffic.
The terminal device of any one of claims 24 to 40, wherein the first indication information comprises at least one of:

preempting the Pre-indication;

priority information;

service information;

service priority information;

logical channel information.
The terminal device according to any one of claims 24 to 41, wherein the first indication information is further used for indicating transmission information of data and/or transmission information of traffic.
The terminal device according to any one of claims 24 to 42, wherein the transceiver unit is further configured to receive second indication information sent by a network device or the physical layer, where the second indication information indicates at least one of the following:

the MAC entity sends the first indication information;

information about the physical channel;

information related to the UCI;

processing information related to the SR;

processing information related to the data;

and processing information related to the service.
The terminal device according to any of claims 24 to 43, wherein when a second SR configuration is valid for a transmission resource or the MAC entity indicates a physical layer to transmit SR,

the transceiver unit is further configured to transmit the first indication information.
The terminal device according to any of claims 24 to 44, wherein the processing unit is further configured to trigger a random access procedure corresponding to the first SR, and/or cancel the first SR.
The terminal device of any of claims 24 to 45, wherein the physical channel comprises at least one of:

a physical random access channel PRACH, a transport channel of Msg3, a physical uplink shared channel PUSCH, and a physical uplink control channel PUCCH.
A terminal device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is configured to perform the steps of the method for processing scheduling request of any of claims 1 to 23 when running the computer program.
A storage medium storing an executable program which, when executed by a processor, implements the scheduling request processing method of any one of claims 1 to 23.