WO2020113869A1 - 一种处理调度请求的方法及装置、终端 - Google Patents

一种处理调度请求的方法及装置、终端 Download PDF

Info

Publication number
WO2020113869A1
WO2020113869A1 PCT/CN2019/080667 CN2019080667W WO2020113869A1 WO 2020113869 A1 WO2020113869 A1 WO 2020113869A1 CN 2019080667 W CN2019080667 W CN 2019080667W WO 2020113869 A1 WO2020113869 A1 WO 2020113869A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
service
priority
logical channel
uplink control
Prior art date
Application number
PCT/CN2019/080667
Other languages
English (en)
French (fr)
Inventor
徐婧
石聪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to SG11202105133XA priority Critical patent/SG11202105133XA/en
Priority to MX2021006207A priority patent/MX2021006207A/es
Priority to EP19892513.3A priority patent/EP3836470A4/en
Priority to CN201980054684.4A priority patent/CN112585902A/zh
Priority to KR1020217014948A priority patent/KR20210080454A/ko
Priority to AU2019393979A priority patent/AU2019393979B2/en
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CA3120719A priority patent/CA3120719A1/en
Priority to CN202110428474.6A priority patent/CN113133123B/zh
Priority to JP2021526368A priority patent/JP7213971B2/ja
Priority to BR112021010638-3A priority patent/BR112021010638A2/pt
Publication of WO2020113869A1 publication Critical patent/WO2020113869A1/zh
Priority to US17/196,973 priority patent/US20210195623A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • the embodiments of the present application relate to the technical field of mobile communications, and in particular to a method, device, and terminal for processing scheduling requests.
  • NR New Radio
  • IIoT Industry Internet of Things
  • URLLC Ultra Reliable Low Latency
  • URLLC Ultra Reliable Low Latency
  • the terminal will only select one SR for transmission at the same time. If the uplink physical control channel (PUCCH, Uplink Physical Control Channel) resources corresponding to the two SRs cannot be allocated by the network, the terminal will choose which SR to transmit. Problem, and this choice is based on the terminal implementation decision. If the terminal selects SR transmission with low QoS (Quality of Service) requirements, it will cause problems that high QoS requirements cannot be guaranteed, such as the problem that the delay of the URLLC service cannot be guaranteed.
  • PUCCH Uplink Physical Control Channel
  • HARQ-ACK Hybrid Automatic Repeat-request-ACK
  • CSI-RS Channel State Information-Reference Signals
  • UCI and uplink physical shared channel PUSCH, Uplink Physical Shared Shared Channel
  • inappropriate priority selection will also lead to high QoS requirements of the business can not meet the demand.
  • Embodiments of the present application provide a method, device, and terminal for processing scheduling requests.
  • the Media Access Control (MAC, Media Access Control) layer instructs the physical layer to send the first scheduling request.
  • MAC Media Access Control
  • the indicating unit is used to instruct the physical layer to send the first scheduling request through the MAC layer.
  • the terminal provided by the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the foregoing method for processing scheduling requests.
  • the chip provided in the embodiment of the present application is used to implement the foregoing method for processing a scheduling request.
  • the chip includes: a processor, for calling and running a computer program from the memory, so that the device installed with the chip executes the above method for processing a scheduling request.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables the computer to execute the foregoing method for processing a scheduling request.
  • the computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions cause the computer to execute the foregoing method for processing a scheduling request.
  • the computer program provided by the embodiment of the present application when it runs on a computer, causes the computer to execute the above method for processing a scheduling request.
  • the technical solution of the embodiment of the present application proposes a method for processing scheduling requests of multiple UCIs or UCIs and PUSCHs in a scenario where transmission resources overlap, ensuring high QoS requirements, such as high reliability and low latency URLLC services. Transmission ensures the transmission performance of the terminal.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for processing a scheduling request provided by an embodiment of this application;
  • FIG. 3 is a schematic structural composition diagram of an apparatus for processing a scheduling request provided by an embodiment of this application;
  • FIG. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • GSM Global System of Mobile
  • CDMA Code Division Multiple Access
  • WCDMA Broadband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • Universal Mobile Communication System Universal Mobile Telecommunication System
  • WiMAX Global Interoperability for Microwave Access
  • the 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 120 (or referred to as a communication terminal, terminal).
  • the network device 110 can provide communication coverage for a specific geographic area, and can communicate with terminals located within the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or a wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks or network devices in future public land mobile networks (Public Land Mobile Network, PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B
  • eNodeB evolved base station in an LTE system
  • CRAN Cloud Radio Access Network
  • the network equipment can be a mobile switching center, a relay station, an access point, an in-veh
  • the communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110.
  • terminals include, but are not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Lines (DSL), digital cables, and direct cable connections; And/or another data connection/network; and/or via wireless interfaces, such as for cellular networks, wireless local area networks (Wireless Local Area Network, WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device of another terminal configured to receive/transmit communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Lines
  • WLAN wireless local area networks
  • DVB-H networks Digital Video Broadband
  • satellite networks satellite networks
  • AM-FM A broadcast transmitter AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal configured to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal”, or “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communication Systems (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; can include radiotelephones, pagers, Internet/internal PDAs with networked access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palm-type receivers or others including radiotelephone transceivers Electronic device.
  • PCS Personal Communication Systems
  • GPS Global Positioning System
  • Terminal can refer to access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user Device.
  • Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital processing (Personal Digital Assistant (PDA), wireless communication Functional handheld devices, computing devices, or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminals in a 5G network, or terminals in a future evolved PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • terminal 120 may perform terminal direct connection (Device to Device, D2D) communication.
  • D2D Terminal Direct connection
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within the coverage area. Embodiments of the present application There is no restriction on this.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
  • network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal 120 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication
  • the device may further include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiments of the present application.
  • the embodiments of the present application can be applied to the scenario where the Uplink Control (Information, UCI) and UCI collide (collision), or to the scenario where the UCI and PUSCH transmission collide (conflict), and can also be applied to PUSCH and PUSCH transmission collision (collision) scenarios can also be applied to UCI and data transmission collision (collision) scenarios, UCI and MAC collision (collision) scenarios, can also be applied to UCI and physical random connection In the scenario of collision between Physical Random Access Channel (PRACH), it is used to choose which one, or which one has priority, or cancel which one. It should be noted that UCI can also be replaced with PUCCH.
  • UCI can also be replaced with PUCCH.
  • the information carried by UCI includes but is not limited to at least one of the following: HARQ-ACK/Negative Acknowledgement (NACK), HARQ feedback, channel state information reference signal (Channel State Information Reference, CSI-RS) , Scheduling Request (SR).
  • NACK HARQ-ACK/Negative Acknowledgement
  • CSI-RS Channel State Information Reference
  • SR Scheduling Request
  • MAC includes but is not limited to at least one of the following: Power Headroom Report (PHR) MAC, CE, Data Volume and Power Headroom Report (Data Volume and Power Headroom Report, DPR) MAC, CE, semi-static Scheduling (Semi-Persistent Scheduling, SPS) confirmation (MAC) CE, autonomous uplink (Autonomous Uplink, AUL) confirmation MAC, CE (sidelink) BSR MAC.
  • PHR Power Headroom Report
  • CE Data Volume and Power Headroom Report
  • DPR Data Volume and Power Headroom Report
  • CE semi-static Scheduling (Semi-Persistent Scheduling, SPS) confirmation
  • CE autonomous uplink (Autonomous Uplink, AUL) confirmation MAC
  • CE sidelink BSR MAC.
  • pending SR For SR, as long as there is a pending SR (referred to as pending SR), for each pending SR, the MAC entity will do the following operations:
  • the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for the SR, and the sr-ProhibitTimer (SR prohibit timer) is not running at the time corresponding to the SR transmission opportunity, and the SR transmission PUCCH resource and measurement gap (measurement Gap)
  • the SR transmission PUCCH resource and measurement gap Measurement Gap
  • RRC Radio Resource Control
  • FIG. 2 is a schematic flowchart of a method for processing a scheduling request according to an embodiment of the present application. As shown in FIG. 2, the method for processing a scheduling request includes the following steps:
  • Step 201 The MAC layer instructs the physical layer to send the first scheduling request.
  • the MAC layer may also be called a MAC entity
  • the physical (PHY) layer may also be called a physical entity.
  • the communication module of the terminal implements the MAC layer and the physical layer.
  • the terminal may be any device capable of communicating with the network, such as a mobile phone, a tablet computer, a palmtop computer, an in-vehicle terminal, a wearable device, and an industrial terminal.
  • the scheduling request is a way for the terminal to apply for resources from the network side for new data transmission.
  • the scheduling request belongs to the information of the physical layer.
  • the action of sending the scheduling request by the terminal does not require RB resources, and can be transmitted through the PUCCH.
  • the terminal needs to send scheduling requests multiple times to apply for RB resources.
  • the scheduling request is in a pending state, which means that the terminal is ready but has not yet sent the scheduling request to the network side.
  • the sr-ProhibitTimer timer is used to monitor the SR signal transmitted in the PUCCH.
  • the terminal can resend the SR until The maximum number of transmissions dsr-TransMax is reached.
  • the value of the sr-ProhibitTimer timer is configured by RRC and delivered to the terminal in the MAC-MainConfig cell. The introduction of sr-ProhibitTimer timer greatly reduces the load on PUCCH. Since there is the concept of the maximum number of times dsr-TransMax, then there must be a variable used to record the current number of SR transmissions. The protocol records this variable as SR_COUNTER. If an SR is triggered and no other SR is in the pending state, the terminal sets SR_COUNTER to 0.
  • the physical layer determines at least one of the following according to the first rule:
  • the physical layer determines which scheduling request to transmit and/or which UCI has high priority and/or which PUCCH has high priority and/or which UCI to transmit and/or which PUCCH resource to use and/or to transmit traffic channel data according to the first rule Control channel information.
  • the first rule includes at least one of the following:
  • the second message from the network is the second message from the network.
  • the MAC layer indicates the first information of the physical layer. For example, when the MAC layer instructs the physical layer to send a scheduling request, it also indicates the first information of the physical layer.
  • the first information includes at least one of the following information corresponding to the first scheduling request:
  • the first information includes at least one of the following information corresponding to the first scheduling request:
  • the service priority information may be displayed priority level information or implicit priority indication information (priority level is determined based on the priority indication information).
  • the logical channel and/or logical channel group priority information may be displayed priority level information or implicit priority indication information (the priority level is determined based on the priority indication information).
  • the first information may also be included in the HARQ information or the MAC layer instructs the physical layer to send grant and HARQ information while indicating to the physical layer.
  • the second information may be the same as or different from the content of the first information.
  • the second information includes but is not limited to at least one of the following: Pre-emption indication information, UCI priority information, traffic channel priority information, control channel priority information, service information that can be carried, and logical channel information that can be carried, Logical channel group information that can be carried, resource attribute information (such as PUSCH transmission duration information).
  • the MAC layer instructs the physical layer to send the first scheduling request, which has the following two categories:
  • Category 1 Scenarios where multiple UCI transmission resources overlap
  • the MAC layer instructs the physical layer to send the first scheduling request.
  • the MAC layer determines the first condition according to at least one of the following factors: the priority of the logical channel that triggers the scheduling request, the identifier of the logical channel that triggers the scheduling request, and the priority of the service that triggers the scheduling request ,
  • the service identifier that triggers the scheduling request the service identifier corresponding to UCI, the priority corresponding to UCI, the priority corresponding to the configured physical uplink shared channel (PUSCH grant), the priority of the logical channel to be transmitted, the logical channel identifier to be transmitted, and the Transmission service identification/priority, service/data/MAC/CE/logical channel identification/priority carried by PUSCH, second information from the network, trigger PRACH logical channel/service/priority/identification of data to be transmitted.
  • the service/logical channel/data refers to the service/logical channel/data with the highest priority or the highest priority level.
  • the MAC layer determines the first condition according to at least one of the following factors: the priority of the logical channel that triggers the scheduling request, the identifier of the logical channel that triggers the scheduling request, the priority of the service that triggers the scheduling request, and the trigger scheduling
  • the first condition includes at least one of the following:
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the second scheduling.
  • the requested logical channel and/or logical channel group priority, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is higher than the service priority corresponding to the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request And the second scheduling request is a pending scheduling request;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than that of the second
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority of the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the third scheduling
  • the requested logical channel and/or logical channel group priority, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority of the first scheduling request is higher than the service priority of the third scheduling request.
  • the first scheduling request is a pending scheduling request
  • the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request Is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than the third
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority corresponding to the third scheduling request Level, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is cancelled;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet
  • the first scheduling request is a scheduling request that does not indicate transmission by the physical layer after the last pending scheduling request is canceled;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet, and the service and/or logical channel and/or logical channel group that triggered the scheduling request corresponds to the first service;
  • the first scheduling request is a scheduling request that does not indicate transmission at the physical layer after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service
  • the physical layer was not instructed to transmit the scheduling request.
  • the first condition includes at least one of the following:
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the second scheduling.
  • the requested logical channel and/or logical channel group priority, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is higher than the service priority corresponding to the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request And the second scheduling request is a pending scheduling request;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than that of the second
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority of the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the third scheduling
  • the requested logical channel and/or logical channel group priority, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority of the first scheduling request is higher than the service priority of the third scheduling request.
  • the first scheduling request is a pending scheduling request
  • the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request Is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than the third
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority corresponding to the third scheduling request Level, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is cancelled;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet
  • the first scheduling request is a scheduling request that does not indicate transmission by the physical layer after the last pending scheduling request is canceled;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet, and the service and/or logical channel and/or logical channel group that triggered the scheduling request corresponds to the first service;
  • the first scheduling request is a scheduling request that does not indicate transmission at the physical layer after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service;
  • the first scheduling request is a scheduling request triggered after the MAC PDU is packaged
  • the first scheduling request is a scheduling request triggered after the MAC PDU is transmitted to the physical layer
  • the first scheduling request is a scheduling request triggered after MAC PDU transmission
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, and the length of the first uplink data channel resource is greater than or equal to the first threshold;
  • the LCP mapping restriction (LCP mapping restriction) configured for the logical channel that triggers the first scheduling request is not satisfied;
  • the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggered the first scheduling request
  • the attribute of the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggers the first scheduling request
  • the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggers the first scheduling request;
  • the attribute of the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggers the first scheduling request
  • the length of the first uplink data channel resource is greater than or equal to the second threshold
  • the uplink control channel resource of the first scheduling request/the first scheduling request and the first uplink data channel resource cannot be simultaneously transmitted
  • the uplink control channel resource of the first scheduling request/the first scheduling request cannot be multiplexed or piggybacked to the first uplink data channel resource
  • the service that triggers the first scheduling request is the first service
  • the logical channel triggering the first scheduling request corresponds to the first service
  • the logical channel that triggers the first scheduling request is the target logical channel
  • the priority of the logical channel that triggers the first scheduling request is higher than the priority of the logical channel and/or MAC CE carried by the PUSCH;
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel carried by the PUSCH and/or MAC CE;
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel corresponding to the PUSCH and/or MAC and CE;
  • the service that triggers the first scheduling request is the first service, and the first scheduling request is the scheduling request triggered after the MAC PDU group packet;
  • the service that triggers the first scheduling request is the first service, and the first scheduling request is the scheduling request triggered after the MAC PDU is transmitted to the physical layer;
  • the service that triggers the first scheduling request is the first service, and when the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, and the first uplink data channel resource
  • the length is greater than or equal to the first threshold
  • the service that triggers the first scheduling request is the first service, which does not satisfy the LCP mapping restriction (LCP mapping restriction) configured for the logical channel that triggers the first scheduling request.
  • LCP mapping restriction LCP mapping restriction
  • the first service in the above solution may be a highly reliable and/or low-latency service, an industrial Internet of Things service, a service with high QoS requirements, and so on.
  • resource overlap in the above solution may be all resource overlap or partial resource overlap.
  • the second scheduling request in the above scheme refers to other pending scheduling requests other than the first scheduling request
  • the third scheduling request in the above scheme refers to other than the first scheduling request
  • the MAC layer at least instructs the physical layer to send the first scheduling request, which can ensure that the network immediately obtains transmission resources and guarantees the service quality of service transmission.
  • the first condition reference may be made to the previous description, which will not be repeated here.
  • the first resource to be transmitted is determined according to at least one of the following factors: the priority of the logical channel that triggers the scheduling request, the identifier of the logical channel that triggers the scheduling request, the priority of the service that triggers the scheduling request, and the trigger scheduling Requested service identifier, service identifier corresponding to HARQ feedback, logical channel identifier corresponding to HARQ feedback, identifier corresponding to HARQ feedback, service priority corresponding to HARQ feedback, logical channel priority corresponding to HARQ feedback, priority corresponding to HARQ feedback , CSI-RS corresponding service identifier, CSI-RS corresponding logical channel identifier, CSI-RS corresponding identifier, CSI-RS corresponding service priority, CSI-RS corresponding logical channel priority, CSI-RS corresponding priority Level, the second information from the network, the service identifier corresponding to UCI, the priority corresponding to UCI, the first information, the priority/identity of the logical channel/service/
  • the physical layer or MAC layer determines the first resource to be transmitted according to at least one of the following factors: the priority of the logical channel that triggers the scheduling request, the identifier of the logical channel that triggers the scheduling request, and the priority of the service that triggers the scheduling request Level, the identifier of the service that triggered the scheduling request, the service identifier corresponding to HARQ feedback, the logical channel identifier corresponding to HARQ feedback, the identifier corresponding to HARQ feedback, the service priority corresponding to HARQ feedback, the logical channel priority corresponding to HARQ feedback, HARQ feedback Corresponding priority, service identifier corresponding to CSI-RS, logical channel identifier corresponding to CSI-RS, identifier corresponding to CSI-RS, service priority corresponding to CSI-RS, logical channel priority corresponding to CSI-RS, CSI-RS Priority corresponding to RS, second information from the network, service identifier corresponding to UCI, priority corresponding to UCI, first information from the
  • the first resource to be transmitted is determined according to at least one of the following factors: the time point at which the scheduling request is triggered, whether to group the MAC PDU, whether to send the MAC PDU to the physical layer, the grant attribute, and the service that triggers the scheduling request ,
  • the factors based on it may include the first information.
  • the MAC layer instructs the physical layer to send the first scheduling request, and at the same time indicates the first information.
  • the first scheduling request and the first HARQ-ACK resource overlap and cannot be multiplexed, and the physical layer determines which UCI to transmit according to the first rule.
  • the MAC layer instructs the physical layer to send the first scheduling request, and at the same time indicates the first information.
  • the first scheduling request and the first HARQ-ACK resource overlap and cannot be multiplexed, and the physical layer determines which UCI to transmit according to the first rule.
  • the MAC layer instructs the physical layer to send the first scheduling request.
  • the first scheduling request and the first CSI-RS resource overlap and cannot be multiplexed, and the physical layer determines which UCI to transmit according to the first rule.
  • the second category scenarios where the transmission resources of UCI and PUSCH overlap, or scenarios where the transmission resources of UCI and PRACH overlap.
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the logical channel corresponding to the first service triggers the first scheduling request
  • the priority of the first service is higher than the priority of the service transmitted by the first uplink data channel or the priority of the first service is higher than the MAC carried by the first uplink data channel, such as the cache status
  • the priority of the service corresponding to the report control unit (BSR MAC, CE, Buffer, Status, Report, Media, Access, Control, Control Element), and/or,
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the logical channel corresponding to the first service triggers the first scheduling request
  • the first service The priority of is the same as the priority of the service transmitted by the first uplink data channel or the priority of the first service is the priority of the service corresponding to the MAC carried by the first uplink data channel, such as BSR MAC and CE Same, then:
  • the MAC layer indicates to the physical layer to transmit the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer to preferentially transmit the first scheduling request or the uplink control channel resource corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer the service type corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer logical channel information corresponding to the first scheduling request; and/or,
  • the MAC layer indicates the first information to the physical layer.
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the logical channel corresponding to the first service triggers the first scheduling request
  • the priority of the first service is higher than that of the service transmitted by the first uplink data channel or the priority of the first service is higher than that of the BSR MAC carried by the first uplink data channel.
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, if the logical channel corresponding to the first service triggers the first scheduling request, and the first service Has the same priority as the service transmitted by the first uplink data channel or the first service has the same priority as the service corresponding to the BSR MAC carried by the first uplink data channel, and// or,
  • the first scheduling request is a scheduling request triggered after the MAC PDU is packaged, and/or,
  • the first scheduling request is a scheduling request triggered after the MAC PDU is transmitted to the physical layer, and/or,
  • the first scheduling request is a scheduling request triggered after MAC PDU transmission, and/or,
  • the uplink control channel resource that transmits the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, and the length of the first uplink data channel resource is greater than or equal to the first threshold, and/or,
  • the LCP mapping limit configured for the logical channel that triggered the first scheduling request is not satisfied, and/or,
  • the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggered the first scheduling request, and/or
  • the attribute of the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggered the first scheduling request, and/or
  • the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggered the first scheduling request, and/or,
  • the attribute of the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggers the first scheduling request, and/or,
  • the length of the first uplink data channel resource is greater than or equal to the second threshold, and/or,
  • the uplink control channel resource of the first scheduling request/the first scheduling request and the first uplink data channel resource cannot be simultaneously transmitted, and/or,
  • the uplink control channel resource of the first scheduling request/the first scheduling request cannot multiplex or piggyback to the first uplink data channel resource, and/or,
  • the service triggering the first scheduling request is the first service, and/or,
  • the logical channel that triggered the first scheduling request corresponds to the first service, and/or,
  • the logical channel that triggered the first scheduling request is the target logical channel, and/or,
  • the priority of the logical channel triggering the first scheduling request is higher than the priority of the logical channel and/or MAC CE carried by the PUSCH, and/or
  • the priority of the logical channel triggering the first scheduling request is higher than the priority of the logical channel and/or MAC CE carried by the PUSCH, and/or
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel carried by the PUSCH and/or MAC CE, and/or,
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel corresponding to the PUSCH and/or MAC and CE, then:
  • the MAC layer indicates to the physical layer to transmit the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer to preferentially transmit the first scheduling request or the uplink control channel resource corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer the service type corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer logical channel information corresponding to the first scheduling request; and/or,
  • the MAC layer sends third information to the physical layer according to the physical layer indication, where the third information is information sent by the physical layer to the MAC layer.
  • the first service in the above solution may be a highly reliable and/or low-latency service, an industrial Internet of Things service, a service with high QoS requirements, and so on.
  • the priority of services/logical channels/data carried on the first uplink data channel the first uplink data channel
  • the physical layer or MAC layer determines whether to transmit the first scheduling request or the first uplink data channel or PRACH according to at least one of the following: the priority of the first service, the priority of the first service Identifier, the priority of the logical channel carrying the first service, the identifier of the logical channel carrying the first service, the priority of the logical channel group carrying the first service, the logical channel carrying the first service Group ID, ID of the logical channel to be transmitted, priority of the logical channel to be transmitted, ID of the service to be transmitted, priority of the service to be transmitted, and priority of the service carried on the first uplink data channel , The identifier of the service carried on the first uplink data channel, the priority of the data carried on the first uplink data channel, the identifier of the data carried on the first uplink data channel, the first uplink data The priority of the logical channel carried on the channel, the identifier of the logical channel carried on the first uplink data channel, the priority of the MAC carried on the first uplink data channel, the bearer
  • the service identifier corresponding to the MAC carried on the first uplink data channel, the priority of the data corresponding to the MAC carried on the first uplink data channel, and the MAC corresponding to the MAC carried on the first uplink data channel The identification of the data triggers the priority of the logical channel of the first scheduling request, triggers the identification of the logical channel of the first scheduling request, triggers the priority of the service corresponding to the logical channel of the first scheduling request, triggers the The logical channel of the first scheduling request corresponds to the service identifier, triggers the priority of the data corresponding to the logical channel of the first scheduling request, triggers the identification of the data corresponding to the logical channel of the first scheduling request, and the first uplink data channel
  • the factors based on it may include the first information.
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the logical channel corresponding to the first service triggers the first scheduling request
  • the priority of the first service or the priority of the logical channel corresponding to the first service is higher than the priority of the service/data/logical channel transmitted by the first uplink data channel, or the first service Or the priority of the logical channel corresponding to the first service is higher than the priority of the MAC carried by the first uplink data channel or the priority of the service/data/logical channel corresponding to the MAC, and/or ,
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the logical channel corresponding to the first service triggers the first scheduling request
  • the priority of the logical channel corresponding to the first service is the same as the priority of the service/data/logical channel transmitted by the first uplink data channel, or the priority of the first service or the first
  • the priority of the logical channel corresponding to a service is the same as the priority of the MAC carried by the first uplink data channel or the priority of the service/data/logical channel corresponding to the MAC, then:
  • the MAC layer indicates to the physical layer to transmit the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer to preferentially transmit the first scheduling request or the uplink control channel resource corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer the service type corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer logical channel information corresponding to the first scheduling request; and/or,
  • the MAC layer indicates the first information to the physical layer.
  • service/data/logical channel refers to: service or data or logical channel.
  • the priority of the logical channel that triggered the first scheduling request, the priority/identity of the service/data corresponding to the logical channel that triggered the first scheduling request, and the service/logic carried on the first uplink data channel The channel/data identification, the second information from the network, the logical channel/service/priority/identification of the data to be transmitted that triggers PRACH, and the first information.
  • the priority of services/logical channels/data carried on the first uplink data channel the first uplink data channel
  • the physical layer or MAC layer determines whether to transmit the first scheduling request or the first uplink data channel or PRACH according to at least one of the following: the priority of the first service, the priority of the first service Identifier, the priority of the logical channel carrying the first service, the identifier of the logical channel carrying the first service, the priority of the logical channel group carrying the first service, the logical channel carrying the first service Group ID, ID of the logical channel to be transmitted, priority of the logical channel to be transmitted, ID of the service to be transmitted, priority of the service to be transmitted, and priority of the service carried on the first uplink data channel , The identifier of the service carried on the first uplink data channel, the priority of the data carried on the first uplink data channel, the identifier of the data carried on the first uplink data channel, the first uplink data The priority of the logical channel carried on the channel, the identifier of the logical channel carried on the first uplink data channel, the priority of the MAC carried on the first uplink data channel, the bearer
  • the service identifier corresponding to the MAC carried on the first uplink data channel, the priority of the data corresponding to the MAC carried on the first uplink data channel, and the MAC corresponding to the MAC carried on the first uplink data channel The identification of the data triggers the priority of the logical channel of the first scheduling request, triggers the identification of the logical channel of the first scheduling request, triggers the priority of the service corresponding to the logical channel of the first scheduling request, triggers the The logical channel of the first scheduling request corresponds to the service identifier, triggers the priority of the data corresponding to the logical channel of the first scheduling request, triggers the identification of the data corresponding to the logical channel of the first scheduling request, and the first uplink data channel
  • the factors based on it may include the first information.
  • MAC CE can be but not limited to BSR MAC MAC.
  • the above solution can also be applied to all UCI and PUSCH/PRACH conflict/overlap scenarios, such as HARQ feedback conflict with PUSCH, CSI-RS conflict with PUSCH, SR conflict with PRACH (such as URLLC service triggered SR and eMBB trigger SR PRACH conflict, URLLC service triggered SR and BFR triggered PRACH conflict), HARQ feedback conflict with PRACH.
  • HARQ feedback conflict with PUSCH CSI-RS conflict with PUSCH
  • SR conflict with PRACH such as URLLC service triggered SR and eMBB trigger SR PRACH conflict, URLLC service triggered SR and BFR triggered PRACH conflict
  • HARQ feedback conflict with PRACH such as URLLC service triggered SR and eMBB trigger SR PRACH conflict, URLLC service triggered SR and BFR triggered PRACH conflict
  • the first service includes at least one of the following: a highly reliable low-latency service, an industrial Internet of Things service, a vertical industry service, a car networking service, and a service in a time-sensitive network.
  • a highly reliable low-latency service e.g., a highly reliable low-latency service
  • an industrial Internet of Things service e.g., a vertical industry service
  • a car networking service e.g., a service in a time-sensitive network.
  • the first scheduling request in the above scheme belongs to UCI
  • the first uplink data channel is, for example, PUSCH.
  • pending SR As long as there is a pending SR (referred to as pending SR), for each pending SR, the MAC entity will do the following:
  • the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for the SR, and the sr-ProhibitTimer is not running at the time corresponding to this SR transmission opportunity, and the SR transmission PUCCH resource does not overlap with the measurement gap, and the SR transmission PUCCH resources and UL-SCH resources do not overlap, there are two cases as follows:
  • the first information includes but is not limited to at least one of the following:
  • pending Priority information corresponding to SR such as priority level, priority indication, etc.
  • pending SR As long as there is a pending SR (referred to as pending SR), the following operations are performed for each pending SR MAC entity:
  • the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for the SR, and the sr-ProhibitTimer is not running at the time corresponding to the SR transmission opportunity, and the SR transmission PUCCH resource does not overlap with the measurement gap, and the SR transmission PUCCH resources and UL-SCH resources do not overlap, and the first condition is met, there are two cases as follows:
  • the first condition includes but is not limited to at least one of the following:
  • the PUCCH resource input to this SR overlaps the PUCCH resource corresponding to other pending SRs, and the corresponding service priority of the pending SR is higher than that of other pending SRs;
  • the PUCCH resource transmitting this SR is overlapped with the PUCCH resource corresponding to other pending SR, and the pending SR corresponds to a service with high reliability and low latency;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other pending SRs, and the logical channel priority of the pending SR is not lower than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other pending SRs, and the corresponding service priority of the pending SR is not lower than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the logical channel priority of the pending SR is higher than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the corresponding service priority of the pending SR is higher than other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have been instructed to be transmitted by the physical layer, and the pending SR corresponds to a service with high reliability and low latency;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the logical channel priority of the pending SR is not lower than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the corresponding service priority of the pending SR is not lower than that of other pending SRs;
  • This SR is the first pending SR after the last pending SR cancel
  • pending SR As long as there is a pending SR (referred to as pending SR), the following operations are performed for each pending SR MAC entity:
  • the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for the SR, and the sr-ProhibitTimer is not running at the time corresponding to this SR transmission opportunity, and the SR transmission PUCCH resource does not overlap with the measurement gap, and the SR transmission PUCCH resources and UL-SCH resources do not overlap, there are two cases as follows:
  • the physical layer is instructed to send the SR on the effective PUCCH resource of the corresponding SR;
  • pending SR As long as there is a pending SR (referred to as pending SR), the following operations are performed for each pending SR MAC entity:
  • the MAC entity has an SR transmission opportunity on the effective PUCCH resource configured for the SR, and the sr-ProhibitTimer is not running at the time corresponding to this SR transmission opportunity, and the SR transmission PUCCH resource does not overlap with the measurement gap, and the SR transmission PUCCH resources and UL-SCH resources do not overlap, there are two cases as follows:
  • the physical layer is instructed to send the SR on the effective PUCCH resource of the corresponding SR;
  • the first condition includes but is not limited to at least one of the following:
  • the PUCCH resource transmitting this SR overlaps the PUCCH resource corresponding to other pending SRs, and the logical channel priority of the pending SR is higher than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other pending SRs, and the corresponding service priority of the pending SR is higher than that of other pending SRs;
  • the PUCCH resource transmitting this SR is overlapped with the PUCCH resource corresponding to other pending SR, and the pending SR corresponds to a service with high reliability and low latency;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other pending SRs, and the logical channel priority of the pending SR is not lower than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other pending SRs, and the corresponding service priority of the pending SR is not lower than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the corresponding service priority of the pending SR is higher than other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have been instructed to be transmitted by the physical layer, and the pending SR corresponds to a service with high reliability and low latency;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the logical channel priority of the pending SR is not lower than that of other pending SRs;
  • the PUCCH resource transmitting this SR overlaps with the PUCCH resource corresponding to other SRs that have indicated the physical layer transmission, and the corresponding service priority of the pending SR is not lower than that of other pending SRs;
  • This SR is the first pending SR after the last pending SR cancel
  • the physical layer determines which SR is transmitted, and/or, which UCI has a higher priority, and/or, which PUCCH has a higher priority, and/or, which UCI is transmitted, and/or, which PUCCH resource is used, and/or Or, transmission of traffic channel data is also control channel information.
  • the physical layer considers the SR that arrived later (that is, indicated later in time) The priority is higher, or the PUCCH resource corresponding to the later arriving SR has a higher priority.
  • the physical layer considers that the SR that arrives first (that is, the indication in front of time) has priority The level is higher, or the PUCCH resource corresponding to the SR that arrives first has a higher priority.
  • the physical layer determines which SR or SR/PUCCH resource to transmit based on the first information
  • the priority is high and/or which UCI and/or which PUCCH resource is used and/or traffic channel data or control channel information is transmitted.
  • the physical layer determines which SR to transmit, and/or which UCI has high priority and/or which PUCCH has high priority and/or which UCI to transmit and/or which PUCCH to use based on the first information
  • the resource and/or transmission traffic channel data is also control channel information.
  • the first information may be indicated by MAC and/or indicated by scheduling and/or obtained through RRC.
  • the physical layer determines which SR and/or SR/PUCCH has the highest priority and/or which UCI has the highest priority and/or which UCI and/or which PUCCH resource to use and/or transmits the traffic channel according to the default rules
  • the data is also control channel information.
  • the physical layer determines which SR and/or SR/PUCCH has the highest priority and/or which UCI has the highest priority and/or which UCI and/or which PUCCH resource to use based on the second information from the network Or transmission of traffic channel data or control channel information.
  • the second information may be the same as or different from the content of the first information.
  • the second information includes but is not limited to at least one of the following: Pre-emption indication information; UCI priority information, traffic channel priority information, control channel priority information, bearable service information, and bearable logical channel information, Logical channel group information that can be carried, resource attribute information (such as PUSCH transmission duration information).
  • the second information may be indicated by DCI, carried by MAC CE, and indicated by RRC signaling.
  • the physical layer determines which SR and/or SR/PUCCH has the highest priority and/or which UCI has the highest priority and/or which UCI to transmit and/or uses based on the second information and the first information Which PUCCH resource and/or transmission traffic channel data is still control channel information.
  • the physical layer determines which UCI has the highest priority based on the first information, and/or whether to transmit SR or HARQ-ACK, and/or which PUCCH to use for transmission.
  • the physical layer determines the priority of PUSCH and PUCCH according to the first information, and/or determines which channel of data to transmit.
  • application example four can be superimposed on any one of application example one, application example two, and application example three.
  • the PUCCH resources transmitting the SR overlap or partially overlap the UL-SCH resources
  • the priority of the first service is higher than that of the UL-SCH transmission
  • the priority of the service, or the priority of the first service is higher than the priority of the service corresponding to the BSR MAC carried by the UL-SCH; and/or,
  • the PUCCH resources transmitting the SR overlap or partially overlap the UL-SCH resources
  • the priority of the first service is the same as the service transmitted by the UL-SCH Have the same priority, or the priority of the first service is the same as the priority of the service corresponding to the BSR MAC carried by the UL-SCH; then:
  • the MAC entity indicates to the physical layer to transmit the SR, and/or to indicate to the physical layer to preferentially transmit the SR or PUCCH resources corresponding to the SR, and/or to indicate to the physical layer the service type corresponding to the SR, and And/or indicating to the physical layer the logical channel (group) information corresponding to the service corresponding to the SR.
  • the first service includes but is not limited to at least one of the following: high-reliability and low-latency services, industrial Internet of Things services, vertical industry services, Internet of Vehicles services, URLLC services, and services in time-sensitive networks.
  • FIG. 3 is a schematic structural composition diagram of an apparatus for processing scheduling requests according to an embodiment of the present application. As shown in FIG. 3, the apparatus includes:
  • the indicating unit 301 is configured to instruct the physical layer to send the first scheduling request through the MAC layer.
  • the device further includes:
  • the determining unit 302 is configured to determine at least one of the following according to the first rule through the physical layer:
  • the first rule includes at least one of the following:
  • the second message from the network is the second message from the network.
  • the indication unit 301 is further configured to indicate the first information of the physical layer through the MAC layer.
  • the first information includes at least one of the following information corresponding to the first scheduling request:
  • the first information includes at least one of the following information corresponding to the first scheduling request:
  • the indication unit 301 is configured to instruct the physical layer to send the first scheduling request through the MAC layer when the first condition is satisfied.
  • the determining unit 302 is configured to determine the first condition according to at least one of the following factors: the priority of the logical channel that triggers the scheduling request, the identifier of the logical channel that triggers the scheduling request, and trigger The priority of the scheduled request service, the identifier of the service that triggered the dispatch request, the service identifier corresponding to UCI, the priority corresponding to UCI, the priority corresponding to PUSCH grant, the priority of the logical channel to be transmitted, the logical channel identifier to be transmitted, the identifier to be transmitted Service identification/priority, service/data/MAC/CE/logical channel identification/priority carried by PUSCH, second information from the network, trigger PRACH logical channel/service/priority/identification of data to be transmitted.
  • the determining unit 302 is configured to determine the first resource to be transmitted according to at least one of the following factors: the priority of the logical channel that triggered the scheduling request, and the identifier of the logical channel that triggered the scheduling request, The priority of the service that triggered the scheduling request, the identifier of the service that triggered the scheduling request, the service identifier corresponding to the HARQ feedback, the logical channel identifier corresponding to the HARQ feedback, the identifier corresponding to the HARQ feedback, the service priority corresponding to the HARQ feedback, and the service priority corresponding to the HARQ feedback Logical channel priority, priority corresponding to HARQ feedback, service identifier corresponding to CSI-RS, logical channel identifier corresponding to CSI-RS, identifier corresponding to CSI-RS, service priority corresponding to CSI-RS, and service priority corresponding to CSI-RS Logical channel priority, priority corresponding to CSI-RS, second information from the network, service identifier corresponding to CSI-RS, second
  • the determining unit 302 is configured to determine the first resource to be transmitted according to at least one of the following factors: the time point at which the scheduling request is triggered, whether to group the MAC PDU, and whether to send the MAC PDU to Physical layer, grant attribute, service triggering scheduling request, logical channel triggering scheduling request, priority of logical channel triggering scheduling request, identification of logical channel triggering scheduling request, priority of service triggering scheduling request, triggering scheduling request Service identification, service identification corresponding to HARQ feedback, logical channel identification corresponding to HARQ feedback, identification corresponding to HARQ feedback, service priority corresponding to HARQ feedback, logical channel priority corresponding to HARQ feedback, priority corresponding to HARQ feedback, Service identifier corresponding to CSI-RS, logical channel identifier corresponding to CSI-RS, identifier corresponding to CSI-RS, service priority corresponding to CSI-RS, logical channel priority corresponding to CSI-RS, and priority corresponding to CSI-RS ,
  • the first condition includes at least one of the following:
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the second scheduling.
  • the requested logical channel and/or logical channel group priority, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is higher than the service priority corresponding to the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request And the second scheduling request is a pending scheduling request;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than that of the second
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority of the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the third scheduling
  • the requested logical channel and/or logical channel group priority, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority of the first scheduling request is higher than the service priority of the third scheduling request.
  • the first scheduling request is a pending scheduling request
  • the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request Is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than the third
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority corresponding to the third scheduling request Level, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is cancelled;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet
  • the first scheduling request is a scheduling request that does not indicate transmission by the physical layer after the last pending scheduling request is canceled;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet, and the service and/or logical channel and/or logical channel group that triggered the scheduling request corresponds to the first service;
  • the first scheduling request is a scheduling request that does not indicate transmission at the physical layer after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request correspond to the first service.
  • the first condition includes at least one of the following:
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the second scheduling.
  • the requested logical channel and/or logical channel group priority, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is higher than the service priority corresponding to the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request And the second scheduling request is a pending scheduling request;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than that of the second
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the second scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority of the second scheduling request ,
  • the first scheduling request and the second scheduling request are pending scheduling requests;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is higher than that of the third scheduling
  • the requested logical channel and/or logical channel group priority, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority of the first scheduling request is higher than the service priority of the third scheduling request.
  • the first scheduling request is a pending scheduling request
  • the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service type corresponding to the first scheduling request is a high-reliability and low-latency service, and the first scheduling request Is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the logical channel and/or logical channel group priority of the first scheduling request is not lower than the third
  • the logical channel and/or logical channel group priority of the scheduling request, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the uplink control channel resource transmitting the first scheduling request overlaps with the uplink control channel resource transmitting the third scheduling request, and the service priority corresponding to the first scheduling request is not lower than the service priority corresponding to the third scheduling request Level, the first scheduling request is a pending scheduling request, and the third scheduling request is a scheduling request that has indicated a physical layer transmission;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is cancelled;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet
  • the first scheduling request is a scheduling request that does not indicate transmission by the physical layer after the last pending scheduling request is canceled;
  • the first scheduling request is the first pending scheduling request after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service;
  • the first scheduling request is the first pending scheduling request triggered after the latest MAC PDU group packet, and the service and/or logical channel and/or logical channel group that triggered the scheduling request corresponds to the first service;
  • the first scheduling request is a scheduling request that does not indicate transmission at the physical layer after the last pending scheduling request is canceled, and the service and/or logical channel and/or logical channel group that triggers the scheduling request corresponds to the first service;
  • the first scheduling request is a scheduling request triggered after the MAC PDU is packaged
  • the first scheduling request is a scheduling request triggered after the MAC PDU is transmitted to the physical layer
  • the first scheduling request is a scheduling request triggered after MAC PDU transmission
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, and the length of the first uplink data channel resource is greater than or equal to the first threshold;
  • the LCP mapping limit configured for the logical channel that triggers the first scheduling request is not satisfied
  • the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggered the first scheduling request
  • the attribute of the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggers the first scheduling request
  • the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggers the first scheduling request;
  • the attribute of the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggers the first scheduling request
  • the length of the first uplink data channel resource is greater than or equal to the second threshold
  • the uplink control channel resource of the first scheduling request/the first scheduling request and the first uplink data channel resource cannot be simultaneously transmitted
  • the uplink control channel resource of the first scheduling request/the first scheduling request cannot multiplex or piggyback to the first uplink data channel resource
  • the service that triggers the first scheduling request is the first service
  • the logical channel triggering the first scheduling request corresponds to the first service
  • the logical channel that triggers the first scheduling request is the target logical channel
  • the priority of the logical channel that triggers the first scheduling request is higher than the priority of the logical channel and/or MAC CE carried by the PUSCH;
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel carried by the PUSCH and/or MAC CE;
  • the logical channel triggering the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel corresponding to the PUSCH and/or MAC and CE.
  • the first service in the above solution may be a highly reliable and/or low-latency service, an industrial Internet of Things service, a service requiring high QoS, and so on.
  • the indication unit 301 is configured to, when the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, if the first service corresponds The logical channel of triggers the first scheduling request, and the priority of the first service is higher than the priority of the service transmitted by the first uplink data channel or the priority of the first service is higher than the first The priority of the service corresponding to the BSR MAC and CE carried in the upstream data channel, and/or,
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the first service Has the same priority as the priority of the service transmitted by the first uplink data channel or the priority of the first service is the same as the priority of the service corresponding to the BSR MAC carried by the first uplink data channel, then:
  • the MAC layer indicates to the physical layer to transmit the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer to preferentially transmit the first scheduling request or the uplink control channel resource corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer the service type corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer logical channel information corresponding to the first scheduling request.
  • the indication unit 301 is configured to, when the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, if the first service corresponds The logical channel of triggers the first scheduling request, and the priority of the first service is higher than the priority of the service transmitted by the first uplink data channel or the priority of the first service is higher than the first The priority of the service corresponding to the BSR MAC and CE carried in the upstream data channel, and/or,
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, if the logical channel corresponding to the first service triggers the first scheduling request, and the first service Has the same priority as the service transmitted by the first uplink data channel or the first service has the same priority as the service corresponding to the BSR MAC carried by the first uplink data channel, and// or,
  • the first scheduling request is a scheduling request triggered after the MAC PDU is packaged, and/or,
  • the first scheduling request is a scheduling request triggered after the MAC PDU is transmitted to the physical layer, and/or,
  • the first scheduling request is a scheduling request triggered after MAC PDU transmission, and/or,
  • the uplink control channel resource that transmits the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, and the length of the first uplink data channel resource is greater than or equal to the first threshold, and/or,
  • the LCP mapping limit configured for the logical channel that triggered the first scheduling request is not satisfied, and/or,
  • the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggered the first scheduling request, and/or
  • the attribute of the first uplink data channel resource does not match the LCP mapping limit configured for the logical channel that triggered the first scheduling request, and/or
  • the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggered the first scheduling request, and/or,
  • the attribute of the first uplink data channel resource does not satisfy the LCP mapping limit configured for the logical channel that triggers the first scheduling request, and/or,
  • the length of the first uplink data channel resource is greater than or equal to the second threshold, and/or,
  • the uplink control channel resource of the first scheduling request/the first scheduling request and the first uplink data channel resource cannot be simultaneously transmitted, and/or,
  • the uplink control channel resource of the first scheduling request/the first scheduling request cannot multiplex or piggyback to the first uplink data channel resource, and/or,
  • the service triggering the first scheduling request is the first service, and/or,
  • the logical channel that triggered the first scheduling request corresponds to the first service, and/or,
  • the logical channel that triggered the first scheduling request is the target logical channel, and/or,
  • the priority of the logical channel triggering the first scheduling request is higher than the priority of the logical channel and/or MAC CE carried by the PUSCH, and/or
  • the priority of the logical channel triggering the first scheduling request is higher than the priority of the logical channel and/or MAC CE carried by the PUSCH, and/or
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel carried by the PUSCH and/or MAC CE, and/or,
  • the logical channel that triggers the first scheduling request is a logical channel corresponding to the first service, and the priority of the logical channel of the first service is higher than that of the logical channel corresponding to the PUSCH and/or MAC and CE, then:
  • the MAC layer indicates to the physical layer to transmit the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer to preferentially transmit the first scheduling request or the uplink control channel resource corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer the service type corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer logical channel information corresponding to the first scheduling request; and/or,
  • the MAC layer sends third information to the physical layer according to the physical layer indication, where the third information is information sent by the physical layer to the MAC layer.
  • the first service in the above solution may be a highly reliable and/or low-latency service, an industrial Internet of Things service, a service with high QoS requirements, and so on.
  • the determining unit 302 is configured to determine whether to transmit the first scheduling request or the first uplink data channel or PRACH according to at least one of the following: priority/identity of the first service , The priority/identity of the logical channel carrying the first service, the priority/identity of the logical channel group carrying the first service, the identity/priority of the logical channel/service to be transmitted, the first uplink
  • the priority of the service/logical channel/data carried on the data channel, the priority of the MAC/CE carried on the first uplink data channel or the priority/identity of the logical channel/service/data corresponding to the MAC triggers the said
  • the priority of the logical channel of the first scheduling request triggers the identification of the logical channel of the first scheduling request, the priority/identity of the service/data corresponding to the logical channel that triggers the first scheduling request, and the first uplink data
  • the indication unit 301 is configured to, when the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource, if the first service corresponds
  • the logical channel of triggers the first scheduling request and the priority of the first service or the priority of the logical channel corresponding to the first service is higher than the service/data/logical channel transmitted by the first uplink data channel Priority, or the priority of the first service or the priority of the logical channel corresponding to the first service is higher than the priority of the MAC carried by the first uplink data channel or the service/data corresponding to the MAC CE /Priority of logical channels, and/or,
  • the uplink control channel resource transmitting the first scheduling request overlaps or partially overlaps with the first uplink data channel resource
  • the logical channel corresponding to the first service triggers the first scheduling request
  • the priority of the logical channel corresponding to the first service is the same as the priority of the service/data/logical channel transmitted by the first uplink data channel, or the priority of the first service or the first
  • the priority of the logical channel corresponding to a service is the same as the priority of the MAC carried by the first uplink data channel or the priority of the service/data/logical channel corresponding to the MAC, then:
  • the MAC layer indicates to the physical layer to transmit the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer to preferentially transmit the first scheduling request or the uplink control channel resource corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer the service type corresponding to the first scheduling request; and/or,
  • the MAC layer indicates to the physical layer logical channel information corresponding to the first scheduling request; and/or,
  • the MAC layer indicates the first information to the physical layer.
  • the determining unit 302 is configured to determine whether to transmit the first scheduling request or the first uplink data channel or PRACH according to at least one of the following: priority/identity of the first service , The priority/identity of the logical channel carrying the first service, the priority/identity of the logical channel group carrying the first service, the identity/priority of the logical channel/service to be transmitted, the first uplink
  • the priority/identity of the service/logical channel/data carried on the data channel, the priority of the MAC/CE carried on the first uplink data channel or the priority/identity of the logical channel/service/data corresponding to the MAC trigger The priority of the logical channel of the first scheduling request triggers the identification of the logical channel of the first scheduling request, and the priority/identity of the service/data corresponding to the logical channel that triggers the first scheduling request, the first The service/logical channel/data identification carried on the uplink data channel, the second information from the network, the logical channel/service/priority/ident
  • the first service includes at least one of the following: a high-reliability and low-latency service, an industrial Internet of Things service, a vertical industry service, a car networking service, and a service in a time-sensitive network.
  • FIG. 4 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device may be any type of terminal.
  • the communication device 600 shown in FIG. 4 includes a processor 610, and the processor 610 may call and run a computer program from the memory to implement the method in the embodiments of the present application.
  • the communication device 600 may further include a memory 620.
  • the processor 610 can call and run a computer program from the memory 620 to implement the method in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of antennas may be one or more.
  • the communication device 600 may specifically be a network device according to an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. .
  • the communication device 600 may specifically be the mobile terminal/terminal of the embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application. This will not be repeated here.
  • FIG. 5 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in FIG. 5 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 700 may further include a memory 720.
  • the processor 710 can call and run a computer program from the memory 720 to implement the method in the embodiments of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the chip 700 may further include an input interface 730.
  • the processor 710 can control the input interface 730 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740.
  • the processor 710 can control the output interface 740 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal in the embodiments of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. Repeat.
  • chips mentioned in the embodiments of the present application may also be referred to as system-on-chips, system chips, chip systems, or system-on-chip chips.
  • FIG. 6 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 6, the communication system 900 includes a terminal 910 and a network device 920.
  • the terminal 910 may be used to implement the corresponding functions implemented by the terminal in the above method
  • the network device 920 may be used to implement the corresponding functions implemented by the network device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an existing programmable gate array (Field Programmable Gate Array, FPGA), or other available Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory.
  • the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically Erasable programmable read only memory (Electrically, EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous) DRAM (SDRAM), double data rate synchronous dynamic random access memory (double data) SDRAM (DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memories in the embodiments of the present application are intended to include but are not limited to these and any other suitable types of memories.
  • Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method of the embodiments of the present application. No longer.
  • the computer-readable storage medium may be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal in each method of the embodiments of the present application, in order to It is concise and will not be repeated here.
  • An embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. Repeat again.
  • the computer program product can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal in each method of the embodiments of the present application, for simplicity , Will not repeat them here.
  • An embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program runs on the computer, the computer is allowed to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. , Will not repeat them here.
  • the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application, and when the computer program runs on the computer, the computer is allowed to execute the corresponding implementations of the mobile terminal/terminal in each method of the embodiments of the present application For the sake of brevity, I will not repeat them here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a division of logical functions.
  • there may be other divisions for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

本申请实施例提供一种处理调度请求的方法及装置、终端，包括：终端的MAC层指示物理层发送第一调度请求。

Description

一种处理调度请求的方法及装置、终端 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种处理调度请求的方法及装置、终端。
背景技术
在新无线(NR，New Radio)工业物联网(IIoT，Industry Internet of Things)中，需要同时支持增强型移动宽带(eMBB，Enhance Mobile Broadband)业务和低时延高可靠通信(URLLC，Ultra Reliable Low Latency Communication)业务，其中，URLLC业务需要保证其高可靠低时延的要求。当两类业务共存时，会出现两类业务的上行控制信息(UCI，Uplink Control Information)在时域上重叠的情况和/或同类业务的UCI在时域上重叠的情况，例如URLLC业务触发的调度请求(SR，Scheduling Request)和eMBB业务触发的SR在时间上重叠的情况。对当前协议来说，终端同一时刻只会选择一个SR传输，若两个SR对应的上行物理控制信道(PUCCH，Uplink Physical Control Channel)资源不能由网络保证配开，就会导致终端选择哪个SR传输的问题，而这个选择是基于终端实现决定的。若终端选择了低服务质量(QoS，Quality of Service)需求的SR传输，就会造成高QoS需求不能保证的问题，如URLLC业务的时延不能保证的问题。另外，上行UCI不能复用时，会出现SR和混合自动重传请求-确认消息(HARQ-ACK，Hybrid Automatic Repeat request-ACK)，信道状态信息参考信号(CSI-RS，Channel State Information-Reference Signals)传输冲突的问题，或者，UCI和上行物理共享信道(PUSCH，Uplink Physical Shared Channel)冲突的问题，此时，不合适的优先级选择同样会导致高QoS需求的业务不能满足需求。
发明内容
本申请实施例提供一种处理调度请求的方法及装置、终端。
本申请实施例提供的处理调度请求的方法，包括：
媒体接入控制(MAC，Media Access Control)层指示物理层发送第一调度请求。
本申请实施例提供的处理调度请求的装置，包括：
指示单元，用于通过MAC层指示物理层发送第一调度请求。
本申请实施例提供的终端，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的处理调度请求的方法。
本申请实施例提供的芯片，用于实现上述的处理调度请求的方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的处理调度请求的方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的处理调度请求的方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的处理调度请求的方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的处理调度请求的方法。
本申请实施例的技术方案，提出了一种多个UCI或者UCI和PUSCH在传输资源重叠的场景下的调度请求的处理方法，保证了高QoS要求，如高可靠低时延的URLLC业务的有效传输，保证了终端的传输性能。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例提供的一种通信系统架构的示意性图；
图2为本申请实施例提供的处理调度请求的方法的流程示意图；
图3为本申请实施例提供的处理调度请求的装置的结构组成示意图；
图4是本申请实施例提供的一种通信设备示意性结构图；
图5是本申请实施例的芯片的示意性结构图；
图6是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
可选地，终端120之间可以进行终端直连(Device to Device，D2D)通信。
可选地，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端120，网络设备110和终端120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为便于理解本申请实施例的技术方案，以下对本申请实施例涉及到的相关技术进行说明。
需要说明的是，本申请实施例可以适用于上行控制信息(Uplink Control Information，UCI)与 UCI碰撞(冲突)的场景，也可以适用于UCI与PUSCH传输碰撞(冲突)的场景，也可以适用于PUSCH与PUSCH传输碰撞(冲突)的场景，也可以适用于UCI与数据传输碰撞(冲突)的场景，也可以适用于UCI与MAC CE碰撞(冲突)的场景，也可以适用于UCI与物理随机接入信道(Physical Random Access Channel，PRACH)冲突的场景，用于选择其中哪个，或者优先其中哪个，或者取消其中哪个。需要说明的是，UCI也可以用PUCCH替代。
可选地，UCI所承载的信息包括但不限于以下至少之一：HARQ-ACK/否定应答(Negative Acknowledgement，NACK)，HARQ反馈，信道状态信息参考信号(Channel State Information Reference Signal，CSI-RS)，调度请求(Scheduling Request，SR)。
可选地，MAC CE包括但不限于以下至少之一：功率余量报告(Power Headroom Report，PHR)MAC CE，数据量和功率净空报告(Data Volume and Power Headroom Report，DPR)MAC CE，半静态调度(Semi-Persistent Scheduling，SPS)确认(confirmation)MAC CE，自主上行链路(Autonomous Uplink，AUL)确认MAC CE，单边(sidelink)BSR MAC CE。
对SR来说，只要有一个待传输(pending)的SR(简称为pending SR)，对每个pending的SR，MAC实体都会做以下操作：
1)如果MAC实体没有为这个pending SR配置有效的PUCCH资源，则触发SpCell上的随机接入过程，取消这个pending SR。
2)如果MAC实体为这个pending SR配置有效的PUCCH资源，对对应这个pending SR的SR配置：
若MAC实体在为SR配置的有效PUCCH资源上有一个SR传输机会，且在这个SR传输机会对应的时间sr-ProhibitTimer(SR禁止定时器)没有运行，且SR传输的PUCCH资源与测量gap(测量间隙)没有重叠，且SR传输的PUCCH资源与UL-SCH资源没有重叠，则有如下两种情况：
情况一：若SR_COUNTER(SR计数器)<sr-TransMax(SR最大发送次数)，则执行如下操作：
SR_COUNTER加1；
指示物理层在对应SR的有效PUCCH资源上发送这个SR；
开启sr-ProhibitTimer；
情况二：若SR_COUNTER≥sr-TransMax，则执行如下操作：
通知无线资源控制(Radio Resource Control，RRC)为每个服务小区释放PUCCH；
通知RRC为每个服务小区释放SRS；
清空所有配置的下行资源分配和上行资源授权；
触发SpCell上的随机接入过程，取消所有的pending SR。
图2为本申请实施例提供的处理调度请求的方法的流程示意图，如图2所示，所述处理调度请求的方法包括以下步骤：
步骤201：MAC层指示物理层发送第一调度请求。
本申请实施例中，MAC层也可以称为MAC实体，物理(PHY)层也可以称为物理实体。
本申请实施例中，终端的通信模块实现所述MAC层和所述物理层。这里，终端可以是手机、平板电脑、掌上电脑、车载终端、可穿戴式设备、工业终端等任意能够与网络进行通信的设备。
需要说明的是，调度请求是终端向网侧申请资源用于新数据传输的一种方式。调度请求属于物理层的信息，终端发送调度请求这个动作的本身不需要RB资源，可以通过PUCCH传输。很多时候，终端为了得到上行RB资源，需要多次发送调度请求来申请RB资源。当终端触发了一个调度请求时，该调度请求就处于pending状态，意思就是终端准备但还没有向网侧发送该调度请求。关于sr-ProhibitTimer定时器：sr-ProhibitTimer定时器用于监视在PUCCH中传输的SR信号，当该定时器正在运行时，是不能发送SR的，一旦该定时器超时，终端就可以重新发送SR，直到达到最大发送次数dsr-TransMax。sr-ProhibitTimer定时器的值由RRC配置，在MAC-MainConfig信元中下发到终端。sr-ProhibitTimer定时器的引入，大大降低了PUCCH上的负载。既然有最大次数dsr-TransMax的概念，那么必然需要有一个变量用来记录当前SR的传输次数，协议把这个变量记为SR_COUNTER。如果一个SR被触发，同时没有其他的SR处于pending状态，那么终端会把SR_COUNTER设置为0。
在本申请的一种实施方式中，MAC层指示物理层发送第一调度请求后，所述物理层根据第一规则确定以下至少之一：
需要传输的调度请求；
上行控制信息的优先级；
上行控制信道的优先级。
这里，物理层根据第一规则确定传输哪个调度请求和/或哪个UCI优先级高和/或哪个PUCCH优先级高和/或传输哪个UCI和/或使用哪个PUCCH资源和/或传输业务信道数据还是控制信道信息。
上述方案中，所述第一规则包括以下至少之一：
第一信息；
优先处理所述MAC层最后指示的第一调度请求；
优先处理所述MAC层最先指示的第一调度请求；
来自网络的第二信息。
在本申请一种实施方式中，所述MAC层指示所述物理层第一信息。举个例子：所述MAC层指示物理层发送调度请求的同时，指示所述物理层第一信息。
上述方案中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
先占(Pre-emption)指示信息；
业务类型信息；
业务优先级信息；
逻辑信道信息；
逻辑信道优先级信息；
逻辑信道组信息；
逻辑信道组优先级信息；
第一业务指示信息。
上述方案中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
Pre-emption指示信息；
业务类型信息；
业务优先级信息；
逻辑信道信息；
逻辑信道优先级信息；
逻辑信道组信息；
逻辑信道组优先级信息；
第一业务指示信息；
优先级信息；
优先等级信息。
这里，业务优先级信息可以是显示的优先级等级信息，也可以是隐式的优先级指示信息(基于优先级指示信息确定优先级等级)。
这里，逻辑信道和/或逻辑信道组优先级信息可以是显示的优先级等级信息，也可以是隐式的优先级指示信息(基于优先级指示信息确定优先级等级)。
可选的，所述第一信息同样可以包含在HARQ信息中或者由MAC层指示物理层发送grant和HARQ信息的同时指示给物理层。
上述方案中，所述第二信息可以与所述第一信息内容相同或者不同。所述第二信息包括但不限于以下至少一项：Pre-emption指示信息，UCI优先级信息，业务信道优先级信息，控制信道优先级信息，可承载的业务信息，可承载的逻辑信道信息，可承载的逻辑信道组信息，资源属性信息(如PUSCH传输时长信息)。
本申请实施例中，所述MAC层指示物理层发送第一调度请求，具有以下两类：
第一类：多个UCI的传输资源重叠的场景
在满足第一条件的情况下，所述MAC层指示所述物理层发送所述第一调度请求。
本申请实施例中，所述MAC层根据以下因素至少之一确定所述第一条件：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，UCI对应的业务标识，UCI对应的优先级，配置的物理上行共享信道(PUSCH grant)对应的优先级，待传输逻辑信道优先级，待传输逻辑信道标识，待传输业务标识/优先级，PUSCH承载的业务/数据/MAC CE/逻辑信道的标识/优先级，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识。
可选地，对于上述方案中的“待传输逻辑信道优先级，待传输逻辑信道标识，待传输业务标识/优先级，PUSCH承载的业务/数据/MAC CE/逻辑信道的标识/优先级”其中的业务/逻辑信道/数据是指优先级或优先级等级最高的业务/逻辑信道/数据。
具体地，所述MAC层根据以下因素至少之一确定所述第一条件：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，上行控制信息UCI对应的业务标识，UCI对应的优先级，配置的物理上行共享信道PUSCH grant对应的优先级，待传输逻辑信道优先级，待传输逻辑信道标识，待传输业务标识，待传输业务优先级，PUSCH承载的业务的标识，PUSCH承载的业务的优先级，PUSCH承载的数据的标识，PUSCH承载的数据的优先级，PUSCH承载的MAC CE的标识，PUSCH承载的MAC CE的优先级，PUSCH承载的逻辑信道的标识，PUSCH承载的逻辑信道的优先级，来自网络的第二信息，触发PRACH的逻辑信道的优先级，触发PRACH的逻辑信道的标识，触发PRACH的业务的优先级，触发PRACH的业务的标识，触发PRACH的待传输数据的优先级，触发PRACH的待传输数据的标识。
在一实施方式中，所述第一条件包括以下至少之一：
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑 信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务
上次pending的调度请求被取消后没有指示物理层传输调度请求。
在另一实施方式中，所述第一条件包括以下至少之一：
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或 逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为MAC PDU组包后触发的调度请求；
所述第一调度请求为MAC PDU传输到物理层后触发的调度请求；
所述第一调度请求为MAC PDU传输后触发的调度请求；
传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值；
不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制(LCP mapping restriction)；
所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
所述第一上行数据信道资源的长度大于等于第二门限值；
所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输；
所述第一调度请求的上行控制信道资源/所述第一调度请求不能复用(multiplex)或捎带(piggyback)到第一上行数据信道资源；
触发所述第一调度请求的业务为第一业务；
触发所述第一调度请求的逻辑信道对应第一业务；
触发所述第一调度请求的逻辑信道为目标逻辑信道；
触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级；
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级；
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE对应的逻辑信道的优先级；
触发所述第一调度请求的业务为第一业务，所述第一调度请求为MAC PDU组包后触发的调度请求；
触发所述第一调度请求的业务为第一业务，所述第一调度请求为MAC PDU传输到物理层后触发的调度请求；
触发所述第一调度请求的业务为第一业务，传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于 第一门限值；
触发所述第一调度请求的业务为第一业务，不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制(LCP mapping restriction)。
上述方案中的第一业务可以为高可靠和/或低时延的业务，工业物联网业务，获知QoS要求高的业务等。
需要说明的是，上述方案中的资源重叠可以是全部资源重叠，也可以是部分资源重叠。
需要说明的是，上述方案中的第二调度请求是指除所述第一调度请求以外的其他pending的调度请求，上述方案中的第三调度请求是指除所述第一调度请求以外的其他已经指示物理层传输的调度请求。
需要说明的是，上述方案中的各种调度请求都属于UCI。
需要说明的是，在传统的通信网络中，通常不会出现至少在MAC PDU组包这个时间后触发的SR，并且该SR和传输该MAC PDU的PUSCH发生冲突的场景。现有协议，即使触发了SR，由于和PUSCH冲突，也不会发送。而在URLLC场景，这种场景常有发生，且不向物理层指示SR传输将造成网络不能及时获知URLLC业务需要传输的信息，导致该业务QoS等性能不能保证。此外，现有协议也没有对至少在MAC PDU组包这个时间后触发的、与传输该MAC PDU的PUSCH冲突的SR如何处理的说明。因此，本方案对此场景进行了完善。具体的，可以在第一条件满足时，所述MAC层至少指示物理层发送所述第一调度请求，可以保障网络即时获得传输资源，保证业务传输的服务质量。这里，第一条件可以参照之前的描述，此处不再赘述。
本申请实施例中，根据以下因素至少之一确定需要传输的第一资源：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：SR，PUSCH，CSI-RS，HARQ反馈，PRACH。
具体地，所述物理层或MAC层根据以下因素至少之一确定需要传输的第一资源：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道的优先级，触发PRACH的逻辑信道的标识，触发PRACH的业务的优先级，触发PRACH的业务的标识，触发PRACH的待传输数据的优先级，触发PRACH的待传输数据的标识；其中，所述第一资源为以下至少之一：SR，PUSCH，CSI-RS，HARQ反馈，PRACH。
本申请实施例中，根据以下因素至少之一确定需要传输的第一资源：触发调度请求的时间点，是否组包MAC PDU，是否将MAC PDU发送到物理层，grant属性，触发调度请求的业务，触发调度请求的逻辑信道，触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
需要说明的是，如果上述方案是MAC层作为判断主体，则其根据的因素可以包括所述第一信息。
此外，还有另一种UCI传输资源重叠的场景，以下举例说明。
例如，在满足第一条件的情况下，所述MAC层指示所述物理层发送所述第一调度请求，同时指示第一信息。所述第一调度请求和第一HARQ-ACK资源重叠且不能复用，物理层根据第一规则确定传输哪个UCI。
又例如，所述MAC层指示所述物理层发送所述第一调度请求，同时指示第一信息。所述第一调度请求和第一HARQ-ACK资源重叠且不能复用，物理层根据第一规则确定传输哪个UCI。
又例如，所述MAC层指示所述物理层发送所述第一调度请求。所述第一调度请求和第一CSI-RS资源重叠且不能复用，物理层根据第一规则确定传输哪个UCI。
第二类：UCI和PUSCH的传输资源重叠的场景，或者UCI和PRACH的传输资源重叠的场景。
在一实施方式中，在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的MAC CE，如缓存状态报告控制单元(BSR MAC CE，Buffer Status Report Media Access Control Control Element)对应的业务的优先级，和/或，
在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的MAC CE，如BSR MAC CE对应的业务的优先级相同，则：
所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
所述MAC层向所述物理层指示第一信息。
在另一实施方式中，在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级相同，和/或，
所述第一调度请求为MAC PDU组包后触发的调度请求，和/或，
所述第一调度请求为MAC PDU传输到物理层后触发的调度请求，和/或，
所述第一调度请求为MAC PDU传输后触发的调度请求，和/或，
传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值，和/或，
不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
所述第一上行数据信道资源的长度大于等于第二门限值，和/或，
所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输，和/或，
所述第一调度请求的上行控制信道资源/所述第一调度请求不能multiplex或piggyback到第一上行数据信道资源，和/或，
触发所述第一调度请求的业务为第一业务，和/或，
触发所述第一调度请求的逻辑信道对应第一业务，和/或，
触发所述第一调度请求的逻辑信道为目标逻辑信道，和/或，
触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE对应的逻辑信道的优先级，则：
所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
所述MAC层根据所述物理层指示，向所述物理层发送第三信息，其中，所述第三信息为所述物理层指示MAC层发送的信息。
上述方案中的第一业务可以为高可靠和/或低时延的业务，工业物联网业务，获知QoS要求高的业务等。
本申请实施例中，根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
可选地，对于上述方案中的“待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识”，以及“所述第一上行数据信道上承载的业务/逻辑信道/数据的标识”，其中的业务/逻辑信道/数据是指优先级或优先级等级最高的业务/逻辑信道/数据。
具体地，所述物理层或MAC层根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级，所述第一业务的标识，承载所述第一业务的逻辑信道的优先级，承载所述第一业务的逻辑信道的标识，承载所述第一业务的逻辑信道组的优先级，承载所述第一业务的逻辑信道组的标识，待传输的逻辑信道的标识，待传输的逻辑信道的优先级，待传输的业务的标识，待传输的业务的优先级，所述第一上行数据信道上承载的业务的优先级，所述第一上行数据信道上承载的业务的标识，所述第一上行数据信道上承载的数据的优先级，所述第一上行数据信道上承载的数据的标识，所述第一上行数据信道上承载的逻辑信道的优先级，所述第一上行数据信道上承载的逻辑信道的标识，所述第一上行数据信道上承载的MAC CE的优先级，所述第一上行数据信道上承载的MAC CE对应的逻辑信道的优先级，所述第一上行数据信道上承载的MAC CE对应的逻辑信道的标识，所述第一上行数据信道上承载的MAC CE对应的业务的优先级，所述第一上行数据信道上承载的MAC CE对应的业务的标识，所述第一上行数据信道上承载的MAC CE对应的数据的优先级，所述第一上行数据信道上承载的MAC CE对应的数据的标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务的优先级，触发所述第一调度请求的逻辑信道对应业务的标识，触发所述第一调度请求的逻辑信道对应数据的优先级，触发所述第一调度请求的逻辑信道对应数据的标识，所述第一上行数据信道上承载的业务的标识，所述第一上行数据信道上承载的逻辑信道的标识，所述第一上行数据信道上承载的数据的标识，来自网络的第二信息，第一信息，触发PRACH的逻辑信道的优先级，触发PRACH的逻辑信道的标识，触发PRACH的业务的优先级，触发PRACH的业务的标识，触发PRACH的待传输数据的优先级，触发PRACH的待传输数据的标识。
需要说明的是，如果是上述方案是物理层作为判断主体，则其根据的因素可以包括所述第一信息。
在另一实施方式中，在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道传输的业务/数据/逻辑信道的优先级，或者所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级，和/或，
在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级与所述第一上行数据信道传输的业务/数据/逻辑信道的优先级相同，或者所述第一业务的优先级或所述第一业务的对应的逻辑信道的优先级与所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级相同，则：
所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
所述MAC层向所述物理层指示第一信息。
上述方案中，业务/数据/逻辑信道，是指：业务或数据或逻辑信道。
本申请实施例中，根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数 据信道上承载的业务/逻辑信道/数据的优先级/标识，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
可选地，对于上述方案中的“待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识”，以及“所述第一上行数据信道上承载的业务/逻辑信道/数据的标识”，其中的业务/逻辑信道/数据是指优先级或优先级等级最高的业务/逻辑信道/数据。
具体地，所述物理层或MAC层根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级，所述第一业务的标识，承载所述第一业务的逻辑信道的优先级，承载所述第一业务的逻辑信道的标识，承载所述第一业务的逻辑信道组的优先级，承载所述第一业务的逻辑信道组的标识，待传输的逻辑信道的标识，待传输的逻辑信道的优先级，待传输的业务的标识，待传输的业务的优先级，所述第一上行数据信道上承载的业务的优先级，所述第一上行数据信道上承载的业务的标识，所述第一上行数据信道上承载的数据的优先级，所述第一上行数据信道上承载的数据的标识，所述第一上行数据信道上承载的逻辑信道的优先级，所述第一上行数据信道上承载的逻辑信道的标识，所述第一上行数据信道上承载的MAC CE的优先级，所述第一上行数据信道上承载的MAC CE对应的逻辑信道的优先级，所述第一上行数据信道上承载的MAC CE对应的逻辑信道的标识，所述第一上行数据信道上承载的MAC CE对应的业务的优先级，所述第一上行数据信道上承载的MAC CE对应的业务的标识，所述第一上行数据信道上承载的MAC CE对应的数据的优先级，所述第一上行数据信道上承载的MAC CE对应的数据的标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务的优先级，触发所述第一调度请求的逻辑信道对应业务的标识，触发所述第一调度请求的逻辑信道对应数据的优先级，触发所述第一调度请求的逻辑信道对应数据的标识，所述第一上行数据信道上承载的业务的标识，所述第一上行数据信道上承载的逻辑信道的标识，所述第一上行数据信道上承载的数据的标识，来自网络的第二信息，第一信息，触发PRACH的逻辑信道的优先级，触发PRACH的逻辑信道的标识，触发PRACH的业务的优先级，触发PRACH的业务的标识，触发PRACH的待传输数据的优先级，触发PRACH的待传输数据的标识。
需要说明的是，如果是上述方案是物理层作为判断主体，则其根据的因素可以包括所述第一信息。
上述方案中，MAC CE可以但不局限于是BSR MAC CE。
可选的，上述方案还可以适用于所有UCI与PUSCH/PRACH冲突/重叠的场景，如HARQ反馈与PUSCH冲突，CSI-RS与PUSCH冲突，SR与PRACH冲突(如URLLC业务触发的SR与eMBB触发的SR PRACH冲突，URLLC业务触发的SR与BFR触发的PRACH冲突)，HARQ反馈与PRACH冲突。
上述方案中，所述第一业务包括以下至少之一：高可靠低时延业务、工业物联网业务、垂直行业业务、车联网业务、时间敏感性网络中的业务。需要说明的是，上述方案中的第一调度请求属于UCI，第一上行数据信道例如是PUSCH。
以下结合具体应用示例对本申请实施例的技术方案做进一步解释说明。需要说明的是，以下应用示例中的MAC实体是指上述实施例中的MAC层。
应用示例一
只要有一个pending的SR(简称为pending SR)，对每个pending的SR，MAC实体都会做以下操作：
1)如果MAC实体没有为这个pending SR配置有效的PUCCH资源，则触发SpCell上的随机接入过程，取消这个pending SR。
2)如果MAC实体为这个pending SR配置有效的PUCCH资源，对对应这个pending SR的SR配置：
若MAC实体在为SR配置的有效PUCCH资源上有一个SR传输机会时，且在这个SR传输机会对应的时刻sr-ProhibitTimer没有运行，且SR传输的PUCCH资源与测量gap没有重叠，且SR传输的PUCCH资源与UL-SCH资源没有重叠，则有如下两种情况：
情况一：若SR_COUNTER<sr-TransMax，则执行如下操作：
SR_COUNTER加1；
指示物理层在对应SR的有效PUCCH资源上发送这个SR；
指示物理层第一信息；
开启sr-ProhibitTimer；
情况二：若SR_COUNTER≥sr-TransMax，则执行如下操作：
通知RRC为每个服务小区释放PUCCH；
通知RRC为每个服务小区释放SRS；
清空所有配置的下行资源分配和上行资源授权；
触发SpCell上的随机接入过程，取消所有的pending SR。
上述方案中，所述第一信息包括但不限于以下至少一项：
Pre-emption指示信息；
pending SR对应的优先级信息，如优先级等级，优先级指示等；
pending SR对应的业务类型信息；
逻辑信道优先级信息；
逻辑信道信息；
逻辑信道组优先级信息；
逻辑信道组信息；
第一业务指示信息。
应用示例二：
只要有一个pending的SR(简称为pending SR)，对每个pending的SR MAC实体都会做以下操作：
1)如果MAC实体没有为这个pending SR配置有效的PUCCH资源，则触发SpCell上的随机接入过程，取消这个pending SR。
2)如果MAC实体为这个pending SR配置有效的PUCCH资源，对对应这个pending SR的SR配置：
若MAC实体在为SR配置的有效PUCCH资源上有一个SR传输机会时，且在这个SR传输机会对应的时刻sr-ProhibitTimer没有运行，且SR传输的PUCCH资源与测量gap没有重叠，且SR传输的PUCCH资源与UL-SCH资源没有重叠，且满足第一条件，则有如下两种情况：
情况一：若SR_COUNTER<sr-TransMax，则执行如下操作：
SR_COUNTER加1；
指示物理层在对应SR的有效PUCCH资源上发送这个SR；
开启sr-ProhibitTimer；
情况二：若SR_COUNTER≥sr-TransMax，则执行如下操作：
通知RRC为每个服务小区释放PUCCH；
通知RRC为每个服务小区释放SRS；
清空所有配置的下行资源分配和上行资源授权；
触发SpCell上的随机接入过程，取消所有的pending SR。
上述方案中，所述第一条件包括但不限于以下至少一个：
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源重叠(overlap)，且该pending的SR的逻辑信道优先级高于其他pending的SR；
输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的对应高可靠低时延的业务；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的逻辑信道优先级不低于其他pending的SR；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级不低于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的逻辑信道优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的对应高可靠低时延的业务；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的的PUCCH资源overlap，且该pending的SR的逻辑信道优先级不低于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级不低于其他pending的SR；
此SR为上次pending SR cancel后第一个pending SR；
上次pending SR cancel后没有指示物理层传输的SR。
可选的，上述应用示例一，可叠加在应用示例二的方案中使用。
应用示例三：
只要有一个pending的SR(简称为pending SR)，对每个pending的SR MAC实体都会做以下操作：
1)如果MAC实体没有为这个pending SR配置有效的PUCCH资源，则触发SpCell上的随机接入过程，取消这个pending SR。
2)如果MAC实体为这个pending SR配置有效的PUCCH资源，对对应这个pending SR的SR配置：
若MAC实体在为SR配置的有效PUCCH资源上有一个SR传输机会时，且在这个SR传输机会对应的时刻sr-ProhibitTimer没有运行，且SR传输的PUCCH资源与测量gap没有重叠，且SR传输的PUCCH资源与UL-SCH资源没有重叠，则有如下两种情况：
情况一：若SR_COUNTER<sr-TransMax，则执行如下操作：
SR_COUNTER加1；
若满足第一条件，指示物理层在对应SR的有效PUCCH资源上发送这个SR；
开启sr-ProhibitTimer；
情况二：若SR_COUNTER≥sr-TransMax，则执行如下操作：
通知RRC为每个服务小区释放PUCCH；
通知RRC为每个服务小区释放SRS；
清空所有配置的下行资源分配和上行资源授权；
触发SpCell上的随机接入过程，取消所有的pending SR。
或者，
只要有一个pending的SR(简称为pending SR)，对每个pending的SR MAC实体都会做以下操作：
1)如果MAC实体没有为这个pending SR配置有效的PUCCH资源，则触发SpCell上的随机接入过程，取消这个pending SR。
2)如果MAC实体为这个pending SR配置有效的PUCCH资源，对对应这个pending SR的SR配置：
若MAC实体在为SR配置的有效PUCCH资源上有一个SR传输机会时，且在这个SR传输机会对应的时刻sr-ProhibitTimer没有运行，且SR传输的PUCCH资源与测量gap没有重叠，且SR传输的PUCCH资源与UL-SCH资源没有重叠，则有如下两种情况：
情况一：若SR_COUNTER<sr-TransMax，则执行如下操作：
SR_COUNTER加1；
若满足第一条件，指示物理层在对应SR的有效PUCCH资源上发送这个SR；
若满足第一条件，开启sr-ProhibitTimer。
需要说明的是，这里的“若满足第一条件”不局限于以上描述方式，这里的“若满足第一条件”可以作为以下任意一种或多种操作的前提条件：
SR_COUNTER加1；
指示物理层在对应SR的有效PUCCH资源上发送这个SR；
开启sr-ProhibitTimer。
情况二：若SR_COUNTER≥sr-TransMax，则执行如下操作：
通知RRC为每个服务小区释放PUCCH；
通知RRC为每个服务小区释放SRS；
清空所有配置的下行资源分配和上行资源授权；
触发SpCell上的随机接入过程，取消所有的pending SR。
上述方案中，所述第一条件包括但不限于以下至少一个：
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的逻辑信道优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的对应高可靠低时延的业务；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的逻辑信道优先级不低于其他pending的SR；
传输此SR的PUCCH资源与其他pending的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级不低于其他pending的SR；
若传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的逻辑信道优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级高于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该 pending的SR的对应高可靠低时延的业务；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的的PUCCH资源overlap，且该pending的SR的逻辑信道优先级不低于其他pending的SR；
传输此SR的PUCCH资源与其他已经指示物理层传输的SR对应的PUCCH资源overlap，且该pending的SR的对应的业务优先级不低于其他pending的SR；
此SR为上次pending SR cancel后第一个pending SR；
上次pending SR cancel后没有指示物理层传输的SR；
可选的，上述应用示例一，可叠加在应用示例三的方案中使用。
应用示例四：
物理层根据第一规则确定传输哪个SR，和/或，哪个UCI优先级高，和/或，哪个PUCCH优先级高，和/或，传输哪个UCI，和/或，使用哪个PUCCH资源，和/或，传输业务信道数据还是控制信道信息。
举个例子：若物理层收到多于一个来自MAC实体的SR的指示，且SR对应的PUCCH资源在时间上重叠或部分重叠，则物理层认为后到达(即时间上靠后指示)的SR优先级更高，或者后到达的SR对应的PUCCH资源优先级更高。
举个例子：若物理层收到多于一个来自MAC的SR的指示，且SR对应的PUCCH资源在时间上重叠或部分重叠，则物理层认为先到达(即时间上靠前指示)的SR优先级更高，或者先到达的SR对应的PUCCH资源优先级更高。
举个例子：若物理层收到多于一个来自MAC的SR的指示，且SR对应的PUCCH资源在时间上重叠或部分重叠，则物理层根据第一信息确定传输哪个SR或者哪个SR/PUCCH资源优先级高和/或传输哪个UCI和/或使用哪个PUCCH资源和/或传输业务信道数据还是控制信道信息。
举个例子：当UCI不能复用时，物理层根据第一信息确定传输哪个SR，和/或哪个UCI优先级高和/或哪个PUCCH优先级高和/或传输哪个UCI和/或使用哪个PUCCH资源和/或传输业务信道数据还是控制信道信息。所述第一信息可以为MAC指示的和/或调度指示的和/或通过RRC获得的。
举个例子：物理层根据默认规则确定传输哪个SR和/或哪个SR/PUCCH优先级高和/或哪个UCI优先级高和/或传输哪个UCI和/或使用哪个PUCCH资源和/或传输业务信道数据还是控制信道信息。
举个例子：物理层根据来自网络的第二信息确定传输哪个SR和/或哪个SR/PUCCH优先级高和/或哪个UCI优先级高和/或传输哪个UCI和/或使用哪个PUCCH资源和/或传输业务信道数据还是控制信道信息。所述第二信息可以与所述第一信息内容相同或者不同。所述第二信息包括但不限于以下至少一项：Pre-emption指示信息；UCI优先级信息，业务信道优先级信息，控制信道优先级信息，可承载的业务信息，可承载的逻辑信道信息，可承载的逻辑信道组信息，资源属性信息(如PUSCH传输时长信息)。所述第二信息可以由DCI指示，MAC CE承载，RRC信令指示。举个例子：物理层根据所述第二信息和所述第一信息确定传输哪个SR和/或哪个SR/PUCCH优先级高和/或哪个UCI优先级高和/或传输哪个UCI和/或使用哪个PUCCH资源和/或传输业务信道数据还是控制信道信息。
举个例子：当SR和HARQ-ACK重叠，且UCI不能复用时，物理层根据第一信息确定哪个UCI优先级高，和/或传输SR还是HARQ-ACK，和/或使用哪个PUCCH传输。
举个例子：当SR和PUSCH重叠，且UCI不能复用在PUSCH上时，物理层根据第一信息确定PUSCH和PUCCH的优先级，和/或确定传输哪个信道的数据。
可选的，应用示例四，可叠加在应用示例一，应用示例二，应用示例三的任何一个方案中使用。
应用示例五：
在传输SR的PUCCH资源与UL-SCH资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述SR，且所述第一业务的优先级高于所述UL-SCH传输的业务的优先级，或者，所述第一业务的优先级高于所述UL-SCH携带的BSR MAC CE对应的业务的优先级；和/或，
在传输SR的PUCCH资源与UL-SCH资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述SR，且所述第一业务的优先级与所述UL-SCH传输的业务的优先级相同，或者，所述第一业务的优先级与所述UL-SCH携带的BSR MAC CE对应的业务的优先级相同；则：
MAC实体向物理层指示传输所述SR，和/或，向物理层指示优先传输所述SR或所述SR对应的PUCCH资源，和/或，向物理层指示所述SR对应的业务类型，和/或，向物理层指示所述SR对应的业务对应的逻辑信道(组)信息。可选的，对此SR，SR_COUNTER加1，和/或开启sr-ProhibitTimer。
上述方案中，所述第一业务包括但不限于以下至少一种：高可靠低时延业务，工业物联网业务，垂直行业业务，车联网业务，URLLC业务，时间敏感性网络中的业务。
本领域技术人员应当理解，本申请实施例仅为可行性实施例的示例性说明，并不对其他的可行性实施例进行限制。
图3为本申请实施例提供的处理调度请求的装置的结构组成示意图，如图3所示，所述装置包括：
指示单元301，用于通过MAC层指示物理层发送第一调度请求。
在本申请一种实施方式中，所述装置还包括：
确定单元302，用于通过物理层根据第一规则确定以下至少之一：
需要传输的调度请求；
上行控制信息的优先级；
上行控制信道的优先级。
在本申请一种实施方式中，所述第一规则包括以下至少之一：
第一信息；
优先处理所述MAC层最后指示的第一调度请求；
优先处理所述MAC层最先指示的第一调度请求；
来自网络的第二信息。
在本申请一种实施方式中，所述指示单元301，还用于通过所述MAC层指示所述物理层第一信息。
在本申请一种实施方式中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
Pre-emption指示信息；
业务类型信息；
业务优先级信息；
逻辑信道信息；
逻辑信道优先级信息；
逻辑信道组信息；
逻辑信道组优先级信息；
第一业务指示信息。
在本申请一种实施方式中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
Pre-emption指示信息；
业务类型信息；
业务优先级信息；
逻辑信道信息；
逻辑信道优先级信息；
逻辑信道组信息；
逻辑信道组优先级信息；
第一业务指示信息；
优先级信息；
优先等级信息。
在本申请一种实施方式中，所述指示单元301，用于在满足第一条件的情况下，通过所述MAC层指示所述物理层发送所述第一调度请求。
在本申请一种实施方式中，所述确定单元302，用于根据以下因素至少之一确定所述第一条件：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，UCI对应的业务标识，UCI对应的优先级，PUSCH grant对应的优先级，待传输逻辑信道优先级，待传输逻辑信道标识，待传输业务标识/优先级，PUSCH承载的业务/数据/MAC CE/逻辑信道的标识/优先级，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识。
在本申请一种实施方式中，所述确定单元302，用于根据以下因素至少之一确定需要传输的第一资源：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
在本申请一种实施方式中，所述确定单元302，用于根据以下因素至少之一确定需要传输的第一资源：触发调度请求的时间点，是否组包MAC PDU，是否将MAC PDU发送到物理层，grant属性，触发调度请求的业务，触发调度请求的逻辑信道，触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务 标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
在本申请一种实施方式中，所述第一条件包括以下至少之一：
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务。
在本申请一种实施方式中，所述第一条件包括以下至少之一：
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
所述第一调度请求为MAC PDU组包后触发的调度请求；
所述第一调度请求为MAC PDU传输到物理层后触发的调度请求；
所述第一调度请求为MAC PDU传输后触发的调度请求；
传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值；
不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
所述第一上行数据信道资源的长度大于等于第二门限值；
所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输；
所述第一调度请求的上行控制信道资源/所述第一调度请求不能multiplex或piggyback到第一上行数据信道资源；
触发所述第一调度请求的业务为第一业务；
触发所述第一调度请求的逻辑信道对应第一业务；
触发所述第一调度请求的逻辑信道为目标逻辑信道；
触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级；
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级；
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE对应的逻辑信道的优先级。
上述方案中的第一业务可以为高可靠和/或低时延的业务，工业物联网业务，获知QoS要求高的 业务等。
在本申请一种实施方式中，所述指示单元301，用于在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级相同，则：
所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息。
在本申请一种实施方式中，所述指示单元301，用于在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级相同，和/或，
所述第一调度请求为MAC PDU组包后触发的调度请求，和/或，
所述第一调度请求为MAC PDU传输到物理层后触发的调度请求，和/或，
所述第一调度请求为MAC PDU传输后触发的调度请求，和/或，
传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值，和/或，
不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
所述第一上行数据信道资源的长度大于等于第二门限值，和/或，
所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输，和/或，
所述第一调度请求的上行控制信道资源/所述第一调度请求不能multiplex或piggyback到第一上行数据信道资源，和/或，
触发所述第一调度请求的业务为第一业务，和/或，
触发所述第一调度请求的逻辑信道对应第一业务，和/或，
触发所述第一调度请求的逻辑信道为目标逻辑信道，和/或，
触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE对应的逻辑信道的优先级，则：
所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
所述MAC层根据所述物理层指示，向所述物理层发送第三信息，其中，所述第三信息为所述物理层指示MAC层发送的信息。
上述方案中的第一业务可以为高可靠和/或低时延的业务，工业物联网业务，获知QoS要求高的业务等。
在本申请一种实施方式中，确定单元302，用于根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
在本申请一种实施方式中，所述指示单元301，用于在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道传输的业务/数据/逻辑信道的优先级，或者所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级，和/或，
在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级与所述第一上行数据信道传输的业务/数据/逻辑信道的优先级相同，或者所述第一业务的优先级或所述第一业务的对应的逻辑信道的优先级与所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级相同，则：
所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
所述MAC层向所述物理层指示第一信息。
在本申请一种实施方式中，确定单元302，用于根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级/标识，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
在本申请一种实施方式中，所述第一业务包括以下至少之一：高可靠低时延业务、工业物联网业务、垂直行业业务、车联网业务、时间敏感性网络中的业务。
本领域技术人员应当理解，本申请实施例的上述处理调度请求的装置的相关描述可以参照本申请实施例的处理调度请求的方法的相关描述进行理解。
图4是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以是任意类型的终端，图4所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图4所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图4所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
图5是本申请实施例的芯片的示意性结构图。图5所示的芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图5所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图6是本申请实施例提供的一种通信系统900的示意性框图。如图6所示，该通信系统900包括终端910和网络设备920。
其中，该终端910可以用于实现上述方法中由终端实现的相应的功能，以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (41)

  1. 一种处理调度请求的方法，应用于终端，所述方法包括：
    媒体接入控制MAC层指示物理层发送第一调度请求。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述物理层根据第一规则确定以下至少之一：
    需要传输的调度请求；
    上行控制信息的优先级；
    上行控制信道的优先级。
  3. 根据权利要求2所述的方法，其中，所述第一规则包括以下至少之一：
    第一信息；
    优先处理所述MAC层最后指示的第一调度请求；
    优先处理所述MAC层最先指示的第一调度请求；
    来自网络的第二信息。
  4. 根据权利要求1至3任一项所述的方法，其中，所述方法还包括：
    所述MAC层指示所述物理层第一信息。
  5. 根据权利要求3或4所述的方法，其中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
    先占Pre-emption指示信息；
    业务类型信息；
    业务优先级信息；
    逻辑信道信息；
    逻辑信道优先级信息；
    逻辑信道组信息；
    逻辑信道组优先级信息；
    第一业务指示信息。
  6. 根据权利要求3或4所述的方法，其中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
    先占Pre-emption指示信息；
    业务类型信息；
    业务优先级信息；
    逻辑信道信息；
    逻辑信道优先级信息；
    逻辑信道组信息；
    逻辑信道组优先级信息；
    第一业务指示信息；
    优先级信息；
    优先等级信息。
  7. 根据权利要求1至6任一项所述的方法，其中，所述MAC层指示物理层发送第一调度请求，包括：
    在满足第一条件的情况下，所述MAC层指示所述物理层发送所述第一调度请求。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    所述MAC层根据以下因素至少之一确定所述第一条件：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，上行控制信息UCI对应的业务标识，UCI对应的优先级，配置的物理上行共享信道PUSCH grant对应的优先级，待传输逻辑信道优先级，待传输逻辑信道标识，待传输业务标识/优先级，PUSCH承载的业务/数据/MAC CE/逻辑信道的标识/优先级，来自网络的第二信息，触发物理随机信道PRACH的逻辑信道/业务/待传输数据的优先级/标识。
  9. 根据权利要求7所述的方法，其中，所述方法还包括：
    根据以下因素至少之一确定需要传输的第一资源：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中， 所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
  10. 根据权利要求7所述的方法，其中，所述方法还包括：
    根据以下因素至少之一确定需要传输的第一资源：触发调度请求的时间点，是否组包MAC PDU，是否将MAC PDU发送到物理层，grant属性，触发调度请求的业务，触发调度请求的逻辑信道，触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
  11. 根据权利要求7至10任一项所述的方法，其中，所述第一条件包括以下至少之一：
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务。
  12. 根据权利要求7至10任一项所述的方法，其中，所述第一条件包括以下至少之一：
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或 逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为MAC PDU组包后触发的调度请求；
    所述第一调度请求为MAC PDU传输到物理层后触发的调度请求；
    所述第一调度请求为MAC PDU传输后触发的调度请求；
    传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值；
    不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
    所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
    所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
    所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
    所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
    所述第一上行数据信道资源的长度大于等于第二门限值；
    所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输；
    所述第一调度请求的上行控制信道资源/所述第一调度请求不能复用或捎带到第一上行数据信道 资源；
    触发所述第一调度请求的业务为第一业务；
    触发所述第一调度请求的逻辑信道对应第一业务；
    触发所述第一调度请求的逻辑信道为目标逻辑信道；
    触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级；
    触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级。
  13. 根据权利要求1至6任一项所述的方法，其中，所述MAC层指示物理层发送第一调度请求，包括：
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级相同，则：
    所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
    所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息。
  14. 根据权利要求1至6任一项所述的方法，其中，所述MAC层指示物理层发送第一调度请求，包括：
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级相同，和/或，
    所述第一调度请求为MAC PDU组包后触发的调度请求，和/或，
    所述第一调度请求为MAC PDU传输到物理层后触发的调度请求，和/或，
    所述第一调度请求为MAC PDU传输后触发的调度请求，和/或，
    传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值，和/或，
    不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
    所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
    所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
    所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
    所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
    所述第一上行数据信道资源的长度大于等于第二门限值，和/或，
    所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输，和/或，
    所述第一调度请求的上行控制信道资源/所述第一调度请求不能复用或捎带到第一上行数据信道资源，和/或，
    触发所述第一调度请求的业务为第一业务，和/或，
    触发所述第一调度请求的逻辑信道对应第一业务，和/或，
    触发所述第一调度请求的逻辑信道为目标逻辑信道，和/或，
    触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
    触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，则：
    所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
    所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
    所述MAC层根据所述物理层指示，向所述物理层发送第三信息，其中，所述第三信息为所述物理层指示MAC层发送的信息。
  15. 根据权利要求14所述的方法，其中，所述方法还包括：
    根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
  16. 根据权利要求1至6任一项所述的方法，其中，所述MAC层指示物理层发送第一调度请求，包括：
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道传输的业务/数据/逻辑信道的优先级，或者所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级，和/或，
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级与所述第一上行数据信道传输的业务/数据/逻辑信道的优先级相同，或者所述第一业务的优先级或所述第一业务的对应的逻辑信道的优先级与所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级相同，则：
    所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
    所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
    所述MAC层向所述物理层指示第一信息。
  17. 根据权利要求16所述的方法，其中，所述方法还包括：
    根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级/标识，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
  18. 根据权利要求13至17任一项所述的方法，其中，所述第一业务包括以下至少之一：高可靠低时延业务、工业物联网业务、垂直行业业务、车联网业务、时间敏感性网络中的业务。
  19. 一种处理调度请求的装置，所述装置包括：
    指示单元，用于通过MAC层指示物理层发送第一调度请求。
  20. 根据权利要求19所述的装置，其中，所述装置还包括：
    确定单元，用于通过物理层根据第一规则确定以下至少之一：
    需要传输的调度请求；
    上行控制信息的优先级；
    上行控制信道的优先级。
  21. 根据权利要求20所述的装置，其中，所述第一规则包括以下至少之一：
    第一信息；
    优先处理所述MAC层最后指示的第一调度请求；
    优先处理所述MAC层最先指示的第一调度请求；
    来自网络的第二信息。
  22. 根据权利要求19至21任一项所述的装置，其中，所述指示单元，还用于通过所述MAC层指示所述物理层第一信息。
  23. 根据权利要求21或22所述的装置，其中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
    Pre-emption指示信息；
    业务类型信息；
    业务优先级信息；
    逻辑信道信息；
    逻辑信道优先级信息；
    逻辑信道组信息；
    逻辑信道组优先级信息；
    第一业务指示信息。
  24. 根据权利要求21或22所述的装置，其中，所述第一信息包括所述第一调度请求对应的以下至少一种信息：
    先占Pre-emption指示信息；
    业务类型信息；
    业务优先级信息；
    逻辑信道信息；
    逻辑信道优先级信息；
    逻辑信道组信息；
    逻辑信道组优先级信息；
    第一业务指示信息；
    优先级信息；
    优先等级信息。
  25. 根据权利要求19至24任一项所述的装置，其中，所述指示单元，用于在满足第一条件的情况下，通过所述MAC层指示所述物理层发送所述第一调度请求。
  26. 根据权利要求25所述的装置，其中，所述装置还包括：
    确定单元，用于根据以下因素至少之一确定所述第一条件：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，UCI对应的业务标识，UCI对应的优先级，PUSCH grant对应的优先级，待传输逻辑信道优先级，待传输逻辑信道标识，待传输业务标识/优先级，PUSCH承载的业务/数据/MAC CE/逻辑信道的标识/优先级，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识。
  27. 根据权利要求25所述的装置，其中，所述装置还包括：
    确定单元，用于根据以下因素至少之一确定需要传输的第一资源：触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
  28. 根据权利要求25所述的装置，其中，所述装置还包括：
    确定单元，用于根据以下因素至少之一确定需要传输的第一资源：触发调度请求的时间点，是否组包MAC PDU，是否将MAC PDU发送到物理层，grant属性，触发调度请求的业务，触发调度请求的逻辑信道，触发调度请求的逻辑信道的优先级，触发调度请求的逻辑信道的标识，触发调度请求的业务的优先级，触发调度请求的业务的标识，HARQ反馈对应的业务标识，HARQ反馈对应的逻辑信道标识，HARQ反馈对应的标识，HARQ反馈对应的业务优先级，HARQ反馈对应的逻辑信道优先级，HARQ反馈对应的优先级，CSI-RS对应的业务标识，CSI-RS对应的逻辑信道标识，CSI-RS对应的标识，CSI-RS对应的业务优先级，CSI-RS对应的逻辑信道优先级，CSI-RS对应的优先级，来自网络的第二信息，UCI对应的业务标识，UCI对应的优先级，第一信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识；其中，所述第一资源为以下至少之一：调度请求SR，PUSCH，信道状态信息参考信号CSI-RS，混合自动重传请求HARQHARQ反馈，PRACH。
  29. 根据权利要求25至28任一项所述的装置，其中，所述第一条件包括以下至少之一：
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠， 且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务。
  30. 根据权利要求25至28任一项所述的装置，其中，所述第一条件包括以下至少之一：
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级高于所述第二调度请求对应的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第二调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第二调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第二调度请求的业务优先级，所述第一调度请求和所述第二调度请求为pending的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级高于所述第三调度请求的逻辑信道和/或 逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的业务优先级高于所述第三调度请求的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务类型为高可靠低时延业务，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求的逻辑信道和/或逻辑信道组优先级不低于所述第三调度请求的逻辑信道和/或逻辑信道组优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    传输所述第一调度请求的上行控制信道资源与传输第三调度请求的上行控制信道资源重叠，且所述第一调度请求对应的业务优先级不低于所述第三调度请求对应的业务优先级，所述第一调度请求为pending的调度请求，所述第三调度请求为已经指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求；
    所述第一调度请求为上次pending的调度请求被取消后的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为最近一次MAC PDU组包后触发的第一个pending的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为上次pending的调度请求被取消后没有指示物理层传输的调度请求，且触发所述调度请求的业务和/或逻辑信道和/或逻辑信道组对应第一业务；
    所述第一调度请求为MAC PDU组包后触发的调度请求；
    所述第一调度请求为MAC PDU传输到物理层后触发的调度请求；
    所述第一调度请求为MAC PDU传输后触发的调度请求；
    传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值；
    不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
    所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
    所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配；
    所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
    所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制；
    所述第一上行数据信道资源的长度大于等于第二门限值；
    所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输；
    所述第一调度请求的上行控制信道资源/所述第一调度请求不能复用或捎带到第一上行数据信道资源；
    触发所述第一调度请求的业务为第一业务；
    触发所述第一调度请求的逻辑信道对应第一业务；
    触发所述第一调度请求的逻辑信道为目标逻辑信道；
    触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级；
    触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级。
  31. 根据权利要求19至24任一项所述的装置，其中，所述指示单元，用于在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信 道携带的BSR MAC CE对应的业务的优先级相同，则：
    所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
    所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息。
  32. 根据权利要求19至24任一项所述的装置，其中，所述指示单元，用于在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级高于所述第一上行数据信道传输的业务的优先级或者所述第一业务的优先级高于所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级，和/或，
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级与所述第一上行数据信道传输的业务的优先级相同或者所述第一业务的优先级与所述第一上行数据信道携带的BSR MAC CE对应的业务的优先级相同，和/或，
    所述第一调度请求为MAC PDU组包后触发的调度请求，和/或，
    所述第一调度请求为MAC PDU传输到物理层后触发的调度请求，和/或，
    所述第一调度请求为MAC PDU传输后触发的调度请求，和/或，
    传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，且所述第一上行数据信道资源的长度大于等于第一门限值，和/或，
    不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
    所述第一上行数据信道资源与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
    所述第一上行数据信道资源的属性与为触发所述第一调度请求的逻辑信道配置的LCP映射限制不匹配，和/或，
    所述第一上行数据信道资源不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
    所述第一上行数据信道资源的属性不满足为触发所述第一调度请求的逻辑信道配置的LCP映射限制，和/或，
    所述第一上行数据信道资源的长度大于等于第二门限值，和/或，
    所述第一调度请求的上行控制信道资源/所述第一调度请求与第一上行数据信道资源不能同时传输，和/或，
    所述第一调度请求的上行控制信道资源/所述第一调度请求不能复用或捎带到第一上行数据信道资源，和/或，
    触发所述第一调度请求的业务为第一业务，和/或，
    触发所述第一调度请求的逻辑信道对应第一业务，和/或，
    触发所述第一调度请求的逻辑信道为目标逻辑信道，和/或，
    触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
    触发所述第一调度请求的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，和/或，
    触发所述第一调度请求的逻辑信道为对应第一业务的逻辑信道，第一业务的逻辑信道的优先级高于PUSCH承载的逻辑信道和/或MAC CE的优先级，则：
    所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
    所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
    所述MAC层根据所述物理层指示，向所述物理层发送第三信息，其中，所述第三信息为所述物理层指示MAC层发送的信息。
  33. 根据权利要求32所述的装置，其中，所述装置还包括：
    确定单元，用于根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的 第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
  34. 根据权利要求19至24任一项所述的装置，其中，所述指示单元，用于在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道传输的业务/数据/逻辑信道的优先级，或者所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级高于所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级，和/或，
    在传输所述第一调度请求的上行控制信道资源与第一上行数据信道资源重叠或者部分重叠的情况下，若第一业务对应的逻辑信道触发所述第一调度请求，且所述第一业务的优先级或所述第一业务对应的逻辑信道的优先级与所述第一上行数据信道传输的业务/数据/逻辑信道的优先级相同，或者所述第一业务的优先级或所述第一业务的对应的逻辑信道的优先级与所述第一上行数据信道携带的MAC CE的优先级或MAC CE对应的业务/数据/逻辑信道的优先级相同，则：
    所述MAC层向所述物理层指示传输所述第一调度请求；和/或，
    所述MAC层向所述物理层指示优先传输所述第一调度请求或所述第一调度请求对应的上行控制信道资源；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的业务类型；和/或，
    所述MAC层向所述物理层指示所述第一调度请求对应的逻辑信道信息；和/或，
    所述MAC层向所述物理层指示第一信息。
  35. 根据权利要求34所述的装置，其中，所述装置还包括：
    确定单元，用于根据以下至少之一确定传输所述第一调度请求还是传输所述第一上行数据信道或PRACH：所述第一业务的优先级/标识，承载所述第一业务的逻辑信道的优先级/标识，承载所述第一业务的逻辑信道组的优先级/标识，待传输的逻辑信道/业务的标识/优先级，所述第一上行数据信道上承载的业务/逻辑信道/数据的优先级/标识，所述第一上行数据信道上承载的MAC CE的优先级或MAC CE对应的逻辑信道/业务/数据的优先级/标识，触发所述第一调度请求的逻辑信道的优先级，触发所述第一调度请求的逻辑信道的标识，触发所述第一调度请求的逻辑信道对应业务/数据的优先级/标识，所述第一上行数据信道上承载的业务/逻辑信道/数据的标识，来自网络的第二信息，触发PRACH的逻辑信道/业务/待传输数据的优先级/标识，第一信息。
  36. 根据权利要求31至35任一项所述的装置，其中，所述第一业务包括以下至少之一：高可靠低时延业务、工业物联网业务、垂直行业业务、车联网业务、时间敏感性网络中的业务。
  37. 一种终端，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至18中任一项所述的方法。
  38. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至18中任一项所述的方法。
  39. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
  40. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至18中任一项所述的方法。
  41. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
PCT/CN2019/080667 2018-12-04 2019-03-29 一种处理调度请求的方法及装置、终端 WO2020113869A1 (zh)

Priority Applications (11)

Application Number Priority Date Filing Date Title
MX2021006207A MX2021006207A (es) 2018-12-04 2019-03-29 Metodo, aparato y terminal para procesar solicitud de programacion.
EP19892513.3A EP3836470A4 (en) 2018-12-04 2019-03-29 PROCESS, APPARATUS AND TERMINAL FOR PROCESSING A SCHEDULE REQUEST
CN201980054684.4A CN112585902A (zh) 2018-12-04 2019-03-29 一种处理调度请求的方法及装置、终端
KR1020217014948A KR20210080454A (ko) 2018-12-04 2019-03-29 스케줄링 요청을 처리하는 방법 및 장치, 단말
AU2019393979A AU2019393979B2 (en) 2018-12-04 2019-03-29 Method, apparatus and terminal for processing scheduling request
SG11202105133XA SG11202105133XA (en) 2018-12-04 2019-03-29 Method, apparatus and terminal for processing scheduling request
CA3120719A CA3120719A1 (en) 2018-12-04 2019-03-29 Method, apparatus and terminal for processing scheduling request
CN202110428474.6A CN113133123B (zh) 2018-12-04 2019-03-29 一种处理调度请求的方法及装置、终端
JP2021526368A JP7213971B2 (ja) 2018-12-04 2019-03-29 スケジューリング要求の処理方法及び装置、端末
BR112021010638-3A BR112021010638A2 (pt) 2018-12-04 2019-03-29 Método para processar uma solicitação de agendamento aplicada a um terminal, e dispositivo para processar uma solicitação de agendamento
US17/196,973 US20210195623A1 (en) 2018-12-04 2021-03-09 Method, apparatus and terminal for processing scheduling request

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CNPCT/CN2018/119219 2018-12-04
PCT/CN2018/119219 WO2020113433A1 (zh) 2018-12-04 2018-12-04 一种处理调度请求的方法及装置、终端
PCT/CN2019/072842 WO2020113801A1 (zh) 2018-12-04 2019-01-23 一种处理调度请求的方法及装置、终端
CNPCT/CN2019/072842 2019-01-23

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/196,973 Continuation US20210195623A1 (en) 2018-12-04 2021-03-09 Method, apparatus and terminal for processing scheduling request

Publications (1)

Publication Number Publication Date
WO2020113869A1 true WO2020113869A1 (zh) 2020-06-11

Family

ID=70973566

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/CN2018/119219 WO2020113433A1 (zh) 2018-12-04 2018-12-04 一种处理调度请求的方法及装置、终端
PCT/CN2019/072842 WO2020113801A1 (zh) 2018-12-04 2019-01-23 一种处理调度请求的方法及装置、终端
PCT/CN2019/080667 WO2020113869A1 (zh) 2018-12-04 2019-03-29 一种处理调度请求的方法及装置、终端

Family Applications Before (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/119219 WO2020113433A1 (zh) 2018-12-04 2018-12-04 一种处理调度请求的方法及装置、终端
PCT/CN2019/072842 WO2020113801A1 (zh) 2018-12-04 2019-01-23 一种处理调度请求的方法及装置、终端

Country Status (11)

Country Link
US (1) US20210195623A1 (zh)
EP (1) EP3836470A4 (zh)
JP (1) JP7213971B2 (zh)
KR (1) KR20210080454A (zh)
CN (2) CN112585902A (zh)
AU (1) AU2019393979B2 (zh)
BR (1) BR112021010638A2 (zh)
CA (1) CA3120719A1 (zh)
MX (1) MX2021006207A (zh)
SG (1) SG11202105133XA (zh)
WO (3) WO2020113433A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020220254A1 (en) * 2019-04-30 2020-11-05 Lenovo (Beijing) Limited Apparatus and method of pucch transmission and reception
WO2021022439A1 (en) * 2019-08-05 2021-02-11 Zte Corporation Systems and methods for determining feedback codebook
KR20210123934A (ko) * 2020-04-06 2021-10-14 삼성전자주식회사 Rar에의해 수신한 상향링크 자원을 고려한 단말 내 우선화를 위한 방법 및 장치
US11716753B2 (en) * 2021-01-26 2023-08-01 Qualcomm Incorporated Feedback methods for subband full duplex systems
EP4320779A1 (en) * 2021-04-06 2024-02-14 Apple Inc. Uci multiplexing with physical layer priority and lch based prioritization
CN118891942A (zh) * 2022-04-22 2024-11-01 中兴通讯股份有限公司 无线通信的传输块生成

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9680608B2 (en) * 2014-06-27 2017-06-13 Silicon Laboratories Inc. Communication protocol with reduced overhead
CN107078876A (zh) * 2014-10-16 2017-08-18 高通股份有限公司 利用统一的空中接口的无线通信
CN107534537A (zh) * 2015-03-09 2018-01-02 欧芬诺技术有限责任公司 载波聚合的调度请求

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101938851B (zh) * 2009-06-30 2014-08-13 中兴通讯股份有限公司 语音编码器速率自适应调整方法及系统
US9065545B2 (en) * 2012-03-12 2015-06-23 Blackberry Limited Handling scheduling request collisions with an ACK/NACK repetition signal
TWI612833B (zh) * 2014-09-17 2018-01-21 創新音速股份有限公司 在一無線通訊系統中請求資源的方法及裝置
WO2017209412A2 (ko) * 2016-06-02 2017-12-07 엘지전자 주식회사 무선 통신 시스템에서 스케줄링 요청을 전송하는 방법 및 장치
US9781744B1 (en) * 2016-08-11 2017-10-03 Futurewei Technologies, Inc. System and method for uplink data scheduling for grant free transmission
CN108811099B (zh) * 2017-05-03 2024-07-23 华为技术有限公司 上行传输资源的调度方法和设备
CN107071916A (zh) * 2017-05-05 2017-08-18 宇龙计算机通信科技(深圳)有限公司 一种资源调度方法及相关设备
US11160119B2 (en) * 2017-06-20 2021-10-26 Lg Electronic Inc. Method for requesting an uplink resource in a wireless communication system and a device therefor
JP6937202B2 (ja) * 2017-09-14 2021-09-22 シャープ株式会社 端末装置、基地局装置、および、通信方法
CN109587807B (zh) * 2017-09-29 2022-09-23 华为技术有限公司 确定调度请求的优先级的方法、终端设备和基站
JP2019140597A (ja) * 2018-02-14 2019-08-22 シャープ株式会社 端末装置、基地局装置、および、通信方法
US11382129B2 (en) * 2018-11-08 2022-07-05 Acer Incorporated Device and method for handling channel access procedure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9680608B2 (en) * 2014-06-27 2017-06-13 Silicon Laboratories Inc. Communication protocol with reduced overhead
CN107078876A (zh) * 2014-10-16 2017-08-18 高通股份有限公司 利用统一的空中接口的无线通信
CN107534537A (zh) * 2015-03-09 2018-01-02 欧芬诺技术有限责任公司 载波聚合的调度请求

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3836470A4 *
VIVO: "Interaction between MAC and PHY for Intra-UE Prioritization", 3GPP TSG-RAN WG2 MEETING #104 R2-1816942, 2 November 2018 (2018-11-02), XP051480881, DOI: 20190717094910X *

Also Published As

Publication number Publication date
AU2019393979B2 (en) 2022-08-11
WO2020113433A1 (zh) 2020-06-11
EP3836470A1 (en) 2021-06-16
SG11202105133XA (en) 2021-06-29
JP2022511412A (ja) 2022-01-31
EP3836470A4 (en) 2021-11-17
CN113133123B (zh) 2023-03-10
CN113133123A (zh) 2021-07-16
JP7213971B2 (ja) 2023-01-27
WO2020113801A1 (zh) 2020-06-11
CN112585902A (zh) 2021-03-30
US20210195623A1 (en) 2021-06-24
AU2019393979A1 (en) 2021-06-10
CA3120719A1 (en) 2020-06-11
KR20210080454A (ko) 2021-06-30
BR112021010638A2 (pt) 2021-09-28
MX2021006207A (es) 2021-08-11

Similar Documents

Publication Publication Date Title
WO2020113869A1 (zh) 一种处理调度请求的方法及装置、终端
US11678300B2 (en) Communication method, terminal device, and network device
WO2020140289A1 (zh) 资源分配的方法、终端设备和网络设备
WO2020133445A1 (zh) 无线通信方法、终端设备和网络设备
WO2020073623A1 (zh) 一种资源配置方法及装置、通信设备
WO2021026841A1 (zh) 调度请求传输的方法和设备
US20210400701A1 (en) Communication method, terminal device, and network device
WO2020211097A1 (zh) 一种信息处理方法、网络设备、终端设备
WO2020051919A1 (zh) 一种资源确定及配置方法、装置、终端、网络设备
WO2021087925A1 (zh) 配置取消传输资源指示信息的方法、网络设备和终端设备
WO2020107692A1 (zh) 一种无线通信方法和通信设备
WO2020061773A9 (zh) 一种反馈资源分配方法、终端设备及网络设备
WO2020107714A1 (zh) 一种无线通信方法和通信设备
CN112586073B (zh) 一种调度请求处理方法、终端设备及存储介质
WO2020056606A1 (zh) 确定上行控制信息传输资源个数的方法、装置及程序
WO2021088004A1 (zh) 一种信道处理方法及装置、终端设备
WO2021031011A1 (zh) 一种harq码本确定方法及装置、终端设备、网络设备
WO2020199004A1 (zh) 通信方法和终端设备
WO2020087289A1 (zh) 一种资源配置方法、网络设备及终端设备
WO2019242378A1 (zh) 确定信道接入类型的方法、终端设备及网络设备
RU2781381C1 (ru) Способ, устройство и терминал для обработки запроса на планирование
WO2023133902A1 (zh) 一种无线通信方法及装置、终端设备、网络设备
WO2021142636A1 (zh) 上行传输的方法和终端设备
WO2020133114A1 (zh) 一种harq进程确定方法和网络设备、终端
WO2020107147A1 (zh) 一种信息生成及指示方法、装置、终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19892513

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019892513

Country of ref document: EP

Effective date: 20210310

ENP Entry into the national phase

Ref document number: 2021526368

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20217014948

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3120719

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021010638

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2019393979

Country of ref document: AU

Date of ref document: 20190329

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112021010638

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210601