WO2021232384A1 - 计数器维护方法，调度请求接收方法以及装置 - Google Patents

计数器维护方法，调度请求接收方法以及装置 Download PDF

Info

Publication number
WO2021232384A1
WO2021232384A1 PCT/CN2020/091674 CN2020091674W WO2021232384A1 WO 2021232384 A1 WO2021232384 A1 WO 2021232384A1 CN 2020091674 W CN2020091674 W CN 2020091674W WO 2021232384 A1 WO2021232384 A1 WO 2021232384A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
counter
trigger event
type
trigger
Prior art date
Application number
PCT/CN2020/091674
Other languages
English (en)
French (fr)
Inventor
贾美艺
蒋琴艳
易粟
王昕�
Original Assignee
富士通株式会社
贾美艺
蒋琴艳
易粟
王昕�
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
Application filed by 富士通株式会社, 贾美艺, 蒋琴艳, 易粟, 王昕� filed Critical 富士通株式会社
Priority to PCT/CN2020/091674 priority Critical patent/WO2021232384A1/zh
Publication of WO2021232384A1 publication Critical patent/WO2021232384A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • the embodiments of the application relate to the field of communication technology.
  • Scheduling request is a way for terminal equipment to request resources from network equipment for new data transmission.
  • NR New Radio
  • the logical channel has a pending regular status buffer report (regular BSR). ) But when there is no uplink resource, SR can be triggered.
  • the network device Since the network device does not know when the terminal device will send the scheduling request, the network device will configure the SR configuration for the terminal device in advance.
  • the SR configuration includes the physical uplink control channel (PUCCH) resource set, and the terminal device uses the PUCCH resource in the SR configuration Send the SR, and the network device detects whether there is an SR to report on the resources in the allocated SR configuration.
  • PUCCH physical uplink control channel
  • Figure 2 is a schematic diagram of the maintenance of the SR_COUNTER.
  • the terminal device configures and maintains the SR
  • a variable SR_COUNTER counter when there is no other SR pending, the SR_COUNTER is set to 0, when the counter is greater than or equal to the maximum number of SR transmissions sr_TransMax, initiate a random access process and cancel all pending SRs, otherwise the higher layer can instruct
  • the lower layer sends the SR on a valid PUCCH resource of the SR, and the SR_COUNTER is incremented by 1.
  • New Radio (NR, New Radio) Rel-16 in addition to the SR triggered by the logical channel (that is, the SR for BSR), a new method of triggering SR is introduced, including beam failure recovery (BFR) in the secondary cell. Or when the LBT continues to fail, if there are no available uplink resources to send the medium access control layer control unit (MAC CE) indicating the occurrence of BFR in the secondary cell or the continuous LBT failure, the terminal device can trigger the SR, in other words , Newly introduced SR triggered by MAC CE.
  • the SR configuration corresponding to the SR triggered by the logical channel can be shared with the SR triggered by the BFR of the secondary cell, or shared with the SR triggered by the continuous LBT failure.
  • the device maintains an SR counter for one SR configuration, and when the SR triggered by the logical channel shares the SR configuration with the SR triggered by the BFR of the secondary cell or the SR triggered by the continuous LBT failure, the SR configuration corresponds to a maximum SR transmission value sr_TransMax, which will lead to premature or excessive Initiate the random access process late; in addition, when the terminal device triggers at least two types of SRs (corresponding to the same SR configuration), if only one SR maximum transmission value sr_TransMax is used, there is no guarantee that the at least two types of SRs are fair , The abuse of random access resources may occur.
  • embodiments of the present application provide a counter maintenance method, a dispatch request receiving method and an apparatus.
  • a counter maintenance device which is applied to terminal equipment, including:
  • a receiving unit configured to receive scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and scheduling request counter related information;
  • the maintenance unit is configured to maintain the first SR counter corresponding to the first type of trigger event and/or maintain the second SR counter corresponding to the second type of trigger event according to the related information of the scheduling request counter.
  • a counter maintenance device which is applied to terminal equipment, including:
  • a triggering unit which is used to trigger a first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a first type of trigger event;
  • the processing unit is configured to set the high-level layer of the terminal device to record the number of transmissions of the first scheduling request counter or the corresponding variable to 0 when the third scheduling request triggered by the triggering event of the first type is not suspended; or,
  • a canceling unit configured to cancel the suspended first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a trigger event of the first type
  • the processing unit is configured to set a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0 at the upper layer of the terminal device.
  • a counter maintenance device which is applied to terminal equipment, including:
  • a receiving unit configured to receive scheduling request related information sent by a network device, the scheduling request related information including at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event;
  • the maintenance unit is used to maintain the counter according to the indication information, and the counter is used to record the number of times the scheduling request is sent.
  • an apparatus for receiving a scheduling request which is applied to a network device, and includes:
  • a sending unit configured to send scheduling request related information to the terminal device, the scheduling request related information including at least resource information and related information of a scheduling request counter corresponding to a scheduling request trigger event;
  • the receiving unit is configured to receive the scheduling request sent by the terminal device on the resource indicated by the resource information.
  • the network devices respectively configure the relevant information of the SR counters corresponding to each type of trigger event, and the terminal device respectively maintains the SR counters corresponding to each type of trigger event, thereby avoiding early or late initiation In the random access process, the fairness of SR triggered by various trigger events is maintained, and the abuse of random access resources is avoided.
  • One of the beneficial effects of the embodiments of the present application is that when resetting the counter, the reset condition takes the SR trigger event into consideration, thereby preventing the terminal device from triggering the random access process prematurely, ensuring fairness, and avoiding random access.
  • the abuse of input resources is simple to implement and cost-saving.
  • the network device uses the indication information to indicate whether the condition of the terminal device to reset the counter considers the SR trigger event. Therefore, when the condition of the reset counter considers the SR trigger event, the terminal can be avoided
  • the device triggers the random access process prematurely to ensure fairness, avoid the abuse of random access resources, and is simple to implement and save costs.
  • Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • Figure 2 is a schematic diagram of SR counter maintenance
  • Fig. 3 and Fig. 4 are schematic diagrams of problems existing in the existing SR counter
  • Fig. 5 is a schematic diagram of a counter maintenance method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of resources configured by SR in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a method for receiving a scheduling request according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a counter maintenance method according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a counter maintenance method according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of resetting the counter of the embodiment of the present application.
  • FIG. 11 is a schematic diagram of a counter maintenance method according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a method for receiving a scheduling request according to an embodiment of the present application.
  • Figure 13 is a schematic diagram of a counter maintenance device according to an embodiment of the present application.
  • Figure 14 is a schematic diagram of a counter maintenance device according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a counter maintenance device according to an embodiment of the present application.
  • Figure 16 is a schematic diagram of a counter maintenance device according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of an apparatus for receiving a scheduling request according to an embodiment of the present application.
  • FIG. 18 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • Fig. 19 is a schematic diagram of a network device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the terms, but they do not indicate the spatial arrangement or chronological order of these elements. These elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having” and the like refer to the existence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” can refer to a network that meets any of the following communication standards, such as Long Term Evolution (LTE), and Enhanced Long Term Evolution (LTE-A, LTE-A). Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • LTE Long Term Evolution
  • LTE-A Enhanced Long Term Evolution
  • LTE-A LTE-A
  • Advanced Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G , New Radio (NR, New Radio), etc., and/or other currently known or future communication protocols.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G 3G
  • 5G New Radio
  • NR, New Radio New Radio
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay), or low-power node (such as femeto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femeto, pico, etc.
  • base station can include some or all of their functions, and each base station can provide communication coverage for a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” (UE, User Equipment) or “Terminal Equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • the terminal device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc.
  • terminal devices may include but are not limited to the following devices: cellular phones (Cellular Phone), personal digital assistants (PDAs, Personal Digital Assistant), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, Cordless phones, smart phones, smart watches, digital cameras, etc.
  • cellular phones Cellular Phone
  • PDAs personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • laptop computers Cordless phones
  • smart phones smart watches, digital cameras, etc.
  • a terminal device may also be a machine or device that performs monitoring or measurement.
  • it may include, but is not limited to: Machine Type Communication (MTC) terminals, In-vehicle communication terminals, device to device (D2D, Device to Device) terminals, machine to machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side or “network device side” refers to a side of the network, which may be a certain base station, and may also include one or more network devices as described above.
  • user side or “terminal side” or “terminal device side” refers to a side of a user or a terminal, which may be a certain UE, and may also include one or more terminal devices as described above.
  • equipment can refer to network equipment or terminal equipment.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a case where a terminal device and a network device are taken as an example.
  • the communication system 100 may include a network device 101 and terminal devices 102 and 103.
  • FIG. 1 only takes two terminal devices and one network device as an example for description, but the embodiment of the present application is not limited to this.
  • the network device 101 and the terminal devices 102 and 103 can perform existing services or future service delivery.
  • these services may include, but are not limited to: enhanced Mobile Broadband (eMBB), large-scale machine type communication (mMTC, massive Machine Type Communication), and high-reliability and low-latency communication (URLLC, Ultra-Reliable and Low). -Latency Communication), etc.
  • FIG. 1 shows that two terminal devices 102 and 103 are both within the coverage of the network device 101, but the application is not limited to this.
  • the two terminal devices 102 and 103 may not be within the coverage area of the network device 101, or one terminal device 102 is within the coverage area of the network device 101 and the other terminal device 103 is outside the coverage area of the network device 101.
  • the current terminal equipment maintains an SR counter for one SR configuration.
  • the SR configuration corresponds to the maximum number of SR transmissions sr_TransMax, which will appear too early Or the problem of initiating the random access process too late is described in detail below with reference to Figures 3-4.
  • the network device when the above-mentioned SR configuration is shared, if the network device only considers the SR triggered by one type of event, for example, consider the SR triggered by the logical channel to configure the maximum sending value of the SR, then when the two SRs are triggered, the terminal device sends The number of SRs will be less than expected, and random access can be triggered to obtain uplink authorization, that is, the random access process is initiated prematurely. This is unfair to other SR configurations corresponding to the SR, and will increase random access resources. use.
  • embodiments of the present application provide a scheduling request receiving method, counter maintenance, and device.
  • terminal equipment For SR triggered by various types of trigger events (for example, corresponding to the same SR configuration), terminal equipment maintains and triggers each type.
  • the maintenance of each SR counter corresponding to the event includes the following actions: setting the variable corresponding to the SR, incrementing the SR counter, resetting the SR counter, processing the SR counter reaching the maximum number of SR transmissions, and the network equipment can be configured to correspond to each type of trigger event.
  • the related information of the SR counter is described below in conjunction with the embodiments of the first to second aspects.
  • the embodiment of the present application provides a counter maintenance method, which is described from the terminal device side.
  • FIG. 5 is a schematic diagram of a counter maintenance method according to an embodiment of the present application. As shown in FIG. 5, the method includes:
  • a terminal device receives scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and scheduling request counter related information;
  • the terminal device maintains a first SR counter corresponding to the first type of trigger event and/or maintains a second SR counter corresponding to the second type of trigger event according to the related information of the scheduling request counter.
  • the terminal device separately maintains SR counters corresponding to each type of trigger event, so as to avoid initiating a random access process too early or too late, maintain fairness to each SR, and avoid the abuse of random access resources.
  • the scheduling request related information includes at least: resource information and scheduling request counter related information.
  • the resource information indicates which PUCCH resources the terminal device transmits on which PUCCH resources.
  • FIG. 6 is a schematic diagram of resources corresponding to each SR configuration. As shown in FIG. 5, the PUCCH resources are distributed on at least one BWP of at least one cell. The index of the resource is indicated by the schedulingRequestId field, and the specific resource indicated by the index is configured using the information element SchedulingRequestResourceConfig. For details, reference may be made to the prior art, which will not be repeated here.
  • the related information of the scheduling request counter includes the maximum transmission times of the scheduling request, for example, includes at least one parameter of the maximum transmission times of the scheduling request, and the maximum transmission times of the scheduling request corresponds or does not correspond to each type of trigger event.
  • the relevant information of the scheduling request counter includes a parameter of the maximum number of times of dispatching requests, and the parameter of the maximum number of times of dispatching requests is not configured for each type of trigger event, and the terminal device uses the maximum number of times of dispatching requests
  • the parameters maintain the SR counters corresponding to each type of trigger event.
  • the related information of the scheduling request counter includes a parameter of the maximum number of times of dispatching requests, and the parameter of the maximum number of times of dispatching requests is configured for each type of trigger event, that is, for each type of trigger event, a parameter is used to indicate the The maximum number of SR transmissions, in other words, this parameter is applicable to the SR counters corresponding to each type of trigger event, and the terminal device uses the one scheduling request maximum transmission times parameter to maintain the SR counters corresponding to each type of trigger event.
  • the related information of the scheduling request counter includes at least two parameters of the maximum number of times of dispatching requests, and the parameters of the maximum number of times of each scheduling request are configured for each type of trigger event, that is, for each type of trigger event, they are used respectively.
  • the respective parameters indicate the maximum transmission times of the SR, and the terminal device uses the parameters of the maximum transmission times of each scheduling request to maintain SR counters corresponding to various types of trigger events.
  • the above-mentioned trigger events include the first type of trigger event triggered by a logical channel and the second type of trigger event triggered by a non-logical channel. That is, for MAC CE triggering, it includes secondary cell BFR triggering and/or continuous LBT failure triggering, that is, for secondary cell BFR MAC CE triggering and/or for continuous LBT failure MAC CE triggering.
  • the sr_TransMax field when configuring a parameter of the maximum number of transmissions of a scheduling request, can be used to indicate, and when configuring at least two parameters of the maximum number of transmissions of a scheduling request, the sr_TransMax_BSR field and the sr_TransMax_MAC CE field can be used to indicate, or use
  • the sr_TransMax_BSR field, the sr_TransMax-LBT-SCell field and the sr_TransMax-BFR-SCell field indicate that they are not given as examples here.
  • the above parameter values can be configured as 4, 8, 18, 32, 64, etc., for example, with the first type of trigger
  • the maximum number of dispatch requests corresponding to the event and the maximum number of dispatch requests corresponding to the second type of trigger event can be configured to be the same or different, that is, the parameter values of sr_TransMax_BSR and sr_TransMax_MAC CE can be the same or different, and when the configuration parameter values are the same
  • a field sr_TransMax can also be used to indicate.
  • the maximum number of dispatch requests corresponding to the BFR trigger of the secondary cell and the maximum number of dispatch requests corresponding to the continuous LBT failure trigger are the same or different, namely sr_TransMax-LBT-SCell and sr_TransMax-BFR-
  • the parameter values of the SCell can be configured to be the same or different.
  • the configuration parameter values are the same, it is optional, and it can also be represented by a field sr_TransMax_MAC CE.
  • the network device may use radio resource control (RRC) signaling to send the scheduling request related information.
  • RRC radio resource control
  • the network device uses RRC signaling to configure logical channel parameters (represented by the information element LogicalChannelConfig) and MAC cell group parameters ( Using the information element MAC-CellGroupConfig), the network device can include the above-mentioned scheduling request related information in the logical channel parameters (represented by the information element LogicalChannelConfig) and MAC cell group parameters (using the information element MAC-CellGroupConfig) and send it to the terminal device.
  • RRC radio resource control
  • the trigger event of the first type triggers the first scheduling request
  • the trigger event of the second type triggers the second scheduling request (for example, the first SR and the second SR correspond to the same SR configuration), and a scheduling request is triggered, Until it is cancelled, it can be regarded as a pending state.
  • This scheduling request is a pending scheduling request; the terminal device maintains the SR counters corresponding to each type of trigger event, that is, maintenance and the first type of trigger event
  • the terminal device sets the first variable SR_COUNTER-1 to record the number of times the first SR is sent, and for the second type of trigger event triggered by the second SR, the terminal device sets the second variable SR_COUNTER-2 to record the number of times the second SR is sent.
  • the upper layer of the terminal device instructs the lower layer to send the first scheduling request, and the upper layer of the terminal device will correspond to the first scheduling request counter triggered by the first type of trigger event Or the corresponding variable plus 1;
  • the upper layer of the terminal device instructs the lower layer to send the second scheduling request, and the upper layer of the terminal device will correspond to the second scheduling request triggered by the second type of trigger event Add 1 to the second scheduling request counter or corresponding variable.
  • the upper layer will cancel the continuous LBT failure, which means that there is no need to send the SR triggered by the continuous LBT failure, or
  • the upper layer will cancel the persistent LBT failure, which means that there is no need to send the SR triggered by the persistent LBT failure.
  • the upper layer of the terminal device instructs the lower layer to send the first scheduling request, and when it does not receive the continuous LBT failure indication from the lower layer, or when it receives the continuous LBT failure indication from the lower layer and the continuous LBT failure recovery configuration information is not configured, it will The first scheduling request counter or the corresponding variable is incremented by 1; the upper layer of the terminal device instructs the lower layer to send the second scheduling request, and when it does not receive a continuous LBT failure indication from the lower layer, or when it receives a continuous LBT failure indication from the lower layer and does not When configuring the continuous LBT failure to recover the configuration information, add 1 to the second scheduling request counter or the corresponding variable.
  • the higher layer before the higher layer instructs the lower layer to send the scheduling request, it is also necessary to determine the relationship between the SR counter or the corresponding variable and the corresponding SR maximum transmission times (the SR maximum transmission times parameter and the corresponding configuration of various trigger events).
  • the higher layer can instruct the lower layer to send the first scheduling request; in the second scheduling request sending times timer or corresponding variable
  • the higher layer may instruct the lower layer to send the second scheduling request.
  • the higher layer before the higher layer instructs the lower layer to send the scheduling request, it is also necessary to determine the relationship between the SR counter or the corresponding variable and the maximum number of SR transmissions (that is, each trigger event corresponds to a parameter of the maximum number of SR transmissions).
  • the higher layer can instruct the lower layer to send the first scheduling request; when the second scheduling request sending times timer or the corresponding variable is less than the maximum sending times of the scheduling request, The higher layer may instruct the lower layer to send the second scheduling request.
  • the higher layer can instruct the lower layer to send the scheduling request.
  • it can also determine whether the higher layer instructs the lower layer to send the scheduling request in combination with other conditions.
  • the other conditions may be: overlapping uplink grants are de-prioritized uplink grants, etc.
  • the embodiment of the present application does not take this as a limitation.
  • the higher layer instructs the lower layer to send the first scheduling request or the second scheduling request, for example, the higher layer instructs the lower layer to send the first scheduling request on the first resource, and/or the higher layer instructs the lower layer to send the second scheduling request on the second resource Request, where the first resource and the second resource are both resources indicated by the first SR configuration.
  • the first scheduling request and the second scheduling request correspond to the same SR configuration, that is, the first SR configuration.
  • the action of adding 1 to the SR counter or the corresponding variable is described.
  • the first SR counter corresponding to the SR triggered by the logical channel when the first SR counter or the corresponding variable is less than sr-TransMax-BSR (or sr-TransMax), And it indicates that when the lower layer sends the SR triggered by the logical channel (sent on a valid PUCCH resource, such as the resource configured by the first scheduling request), if the LBT failure indication from the lower layer is not received, or if the LBT from the lower layer is received When failure indication and LBT failure recovery configuration is not configured, lbt-FailureRecoveryConfig, the first SR counter or corresponding variable corresponding to the SR triggered by the logical channel plus 1; the second SR corresponding to the SR triggered by the BFR of the secondary cell or the SR triggered by the continuous LBT failure Counter: When the second SR counter or the corresponding variable is less than sr-TransMax-BFR or
  • the first scheduling request counter or corresponding variable when the first scheduling request counter or corresponding variable is greater than or equal to the maximum number of dispatch requests corresponding to the first type of trigger event (the SR maximum number of transmission parameters are configured corresponding to various trigger events): 1 ) The upper layer of the terminal device cancels the first scheduling request, or, 2) cancels the first scheduling request and the second scheduling request, or, 3) the second scheduling request counter or the corresponding variable is 0, or greater than or equal to When the maximum sending times of the scheduling request corresponding to the second type of trigger event (the SR maximum sending times parameter is configured corresponding to each type of trigger event), cancel the first scheduling request and the second scheduling request; for example, in the second scheduling request counter Or when the corresponding variable is greater than or equal to the maximum sending times of the scheduling request corresponding to the second type of trigger event (the SR maximum sending times parameter is configured corresponding to each type of triggering event): 1) The upper layer of the terminal device cancels the second scheduling request, or , 2) Cancel the first scheduling request and the second scheduling request, 3) Or
  • the upper layer of the terminal device cancels the first scheduling request.
  • the scheduling request or, canceling the first scheduling request and the second scheduling request, or, when the second scheduling request counter or corresponding variable is 0 or greater than or equal to the maximum number of transmissions of the scheduling request (that is, one corresponding to each type of trigger event) SR maximum transmission times parameter) cancel the first scheduling request and the second scheduling request; for example, when the second scheduling request counter or corresponding variable is greater than or equal to the maximum transmission times of the scheduling request (that is, various trigger events correspond to the maximum transmission of a SR Times parameter), the upper layer of the terminal device cancels the second scheduling request, or cancels the first scheduling request and the second scheduling request, or, when the first scheduling request counter or the corresponding variable is 0 or greater than or equal to The first scheduling request and the second scheduling request are cancelled when the maximum number of sending times of the scheduling request (that is, various trigger events correspond to a parameter of the maximum number of sending SRs).
  • the higher layer in addition to canceling the corresponding SR, the higher layer will also initiate a random access procedure on the special cell.
  • the random access procedure refer to the prior art, which will not be repeated here.
  • the first SR counter of the first SR triggered by the logical channel when the first SR counter or the corresponding variable is greater than or equal to sr-TransMax-BSR (or sr-TransMax), the upper layer will initiate a random access procedure on the special cell and cancel all suspended SRs; or cancel the first suspended SRs corresponding to all logical channels; or the SR or continuous LBT triggered by the BFR of the secondary cell
  • the second SR counter or corresponding variable of the second SR triggered by failure is 0 or greater than or equal to sr-TransMax-BFR or sr-TransMax-LBT (or sr-TransMax)
  • the upper layer The random access procedure will be initiated on the special cell and all suspended SRs will be cancelled; for example, the second SR counter of the second SR triggered by the BFR or continuous LBT failure of the secondary cell
  • one SR counter (or corresponding variable) or at least two SR counters (or corresponding variables) corresponding to each trigger event is greater than Or equal to the maximum number of dispatch requests (corresponding or not corresponding to various trigger events)
  • the higher layer will cancel the corresponding SR (corresponding to a counter greater than or equal to the maximum number of dispatch requests) or cancel all pending SRs, and A random access procedure is initiated on the special cell.
  • the upper layer of the terminal device when no other third scheduling request triggered by the first type of triggering event is suspended, the upper layer of the terminal device sets the first scheduling request counter or the corresponding variable to 0; and/or, When no other fourth scheduling request triggered by the second type of triggering event is suspended, the upper layer of the terminal device sets the second scheduling request counter or the corresponding variable to 0.
  • the higher layer will set the logic
  • the first SR counter or corresponding variable corresponding to the first SR triggered by the channel is 0 (that is, the SR counter is reset); the BFR or continuous LBT failure of the secondary cell triggers the second SR, and there is no other secondary cell BFR or continuous LBT failure to trigger
  • the fourth SR is suspended (for example, the two use the same SR configuration)
  • the upper layer will set the second SR counter or the corresponding variable corresponding to the second SR triggered by the BFR of the secondary cell or the continuous LBT failure to 0 (ie reset The SR counter), in other words, if a type of trigger event triggers an SR, and (corresponding to the same SR configuration) no other SR triggered by the same type of trigger event is suspended, the higher layer will set the higher layer.
  • the higher layer is a MAC layer (for example, a MAC layer entity), and the lower layer is a physical layer, but this embodiment is not limited thereto.
  • Figure 5 above only schematically illustrates an embodiment of the present application, but the present application is not limited thereto.
  • the order of execution among various operations can be appropriately adjusted, and some other operations can be added or some operations can be reduced.
  • Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of FIG. 5 above.
  • the terminal device separately maintains SR counters corresponding to each type of trigger event, so as to avoid initiating a random access process too early or too late, maintain the fairness of each SR, and avoid the abuse of random access resources.
  • the embodiment of the present application provides a method for receiving a scheduling request, which is described from a network device.
  • FIG. 7 is a schematic diagram of a method for receiving a scheduling request according to an embodiment of the present application. As shown in FIG. 7, the method includes:
  • the network device sends scheduling request related information to a terminal device, where the scheduling request related information includes at least resource information and related information of a scheduling request counter corresponding to a scheduling request trigger event;
  • the network device receives a scheduling request sent by the terminal device on the resource indicated by the resource information.
  • the network device respectively configures the related information of the SR counter corresponding to each type of trigger event and sends it to the terminal device so that the terminal device can maintain the SR counter corresponding to each type of trigger event according to the related information. In this way, it is avoided that the random access process is initiated too early or too late, the fairness of each SR is maintained, and the abuse of random access resources is avoided.
  • Figure 7 above only schematically illustrates the embodiments of the present application, but the present application is not limited thereto.
  • the order of execution among various operations can be appropriately adjusted, and some other operations can be added or some operations can be reduced.
  • Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of FIG. 7 above.
  • the related information of the scheduling request counter corresponding to the scheduling request trigger event includes the maximum number of times of sending the scheduling request corresponding to the scheduling request trigger event.
  • the scheduling request related information please refer to the embodiment of the first aspect. , I won’t repeat it here.
  • the specific implementation manner of the scheduling request trigger event can refer to the embodiment of the first aspect, which will not be repeated here.
  • the network device may pre-configure and send at least one SR configuration to the terminal device.
  • Each SR configuration includes: a configuration index and at least one scheduling request maximum transmission times parameter.
  • the SR configuration may be represented by the information element SchedulingRequestConfig.
  • the configuration index schedulingRequestId can also indicate resource information, and can be configured using the information element SchedulingRequestResourceConfig.
  • the parameter of the maximum number of times of sending a scheduling request can be used for the maintenance and/or maintenance of the first SR counter corresponding to the first type of trigger event. Or maintenance of the second SR counter corresponding to the second type of trigger event.
  • an SR configuration when an SR configuration includes a parameter sr-TransMax for the maximum transmission times of a scheduling request, it corresponds to an SR configuration and configures a parameter for the maximum transmission times of a scheduling request.
  • This parameter is applicable to the first SR counter corresponding to the first type of trigger event.
  • the second SR counter corresponding to the second type of trigger event for example, corresponding to an SR configuration, configure the maximum number of dispatch requests parameter corresponding to the dispatch request trigger event, and one SR configuration contains two dispatch request maximum transmissions
  • the parameter sr-TransMax-BSR and sr-TransMax-MAC CE that is, the parameter sr-TransMax-BSR applies to the first SR counter corresponding to the first type of trigger event
  • the parameter sr-TransMax-MAC CE applies to the The second SR counter corresponding to the second type of trigger event; or when the parameter sr-TransMax-BSR, sr-TransMax-LBT-SCell and sr-TransMax-BFR-SCell is included in the maximum number of times of sending scheduling requests, that is, the parameter sr -TransMax-BSR applies to the first SR counter corresponding to the first type of trigger event, the parameter sr-TransMax-BFR-SCell applies to the second SR counter corresponding to
  • the related information of the scheduling request counter corresponding to the scheduling request trigger event can be directly carried in the RRC signaling.
  • the network device uses the RRC signaling to configure the logical channel parameters ( Using the information element LogicalChannelConfig to represent) and MAC cell group parameters (using the information element MAC-CellGroupConfig), the network device can include the relevant information of the scheduling request counter corresponding to the scheduling request trigger event in the logical channel parameters (using the information element LogicalChannelConfig to represent) and The MAC cell group parameters (using the information element MAC-CellGroupConfig) are sent to the terminal device.
  • the sr-TransMax-BSR field can be added to the LogicalChannelConfig to indicate the maximum number of transmissions of the scheduling request triggered by the logical channel, and the MAC-CellGroupConfig is added
  • the fields sr-TransMax-LBT-SCell and sr-TransMax-BFR-SCell indicate the maximum number of transmissions of scheduling requests triggered by continuous LBT failure and the maximum number of transmissions of scheduling requests triggered by the BFR of the secondary cell.
  • the network device may pre-configure and send at least one SR configuration to the terminal device.
  • Each SR configuration includes: a configuration index and a parameter of the maximum number of times of sending a scheduling request.
  • the parameter of the maximum number of times of sending a scheduling request may not be configured.
  • Modify the parameter attribute of the maximum number of dispatch requests to be sent from the indispensable mandate to optional and needs in some cases. For example, when various trigger events correspond to the same SR configuration, this parameter is the default absent (in other words, the terminal The device can use the maximum transmission times parameter indicated in the RRC signaling.
  • the terminal device uses the maximum transmission times parameter indicated in the RRC signaling, and ignores the scheduling request maximum transmission times parameter configured in the SR configuration.
  • the parameter value of the maximum sending times of the scheduling request can be configured as 4, 8, 18, 32, 64, etc., where the maximum sending times of the scheduling request corresponding to the first type of trigger event is the same as that of the second type of trigger.
  • the maximum sending times of scheduling requests corresponding to events can be configured to be the same or different, that is, the parameter values of sr_TransMax_BSR and sr_TransMax_MAC CE can be the same or different, where, when the configuration parameter values are the same, it is optional, and can also be represented by a field sr_TransMax.
  • the maximum number of dispatch requests corresponding to the BFR trigger of the secondary cell and the maximum number of dispatch requests corresponding to the continuous LBT failure trigger are the same or different, namely sr_TransMax-LBT-SCell and sr_TransMax-BFR-
  • the parameter values of the SCell can be configured to be the same or different.
  • the configuration parameter values are the same, it is optional, and it can also be represented by a field sr_TransMax_MAC CE.
  • the network device respectively configures the relevant information of the SR counter corresponding to each type of trigger event and sends it to the terminal device so that the terminal device can maintain the SR counter corresponding to each type of trigger event according to the relevant information, thereby Avoid initiating the random access process too early or too late, maintain the fairness of each SR, and avoid the abuse of random access resources.
  • embodiments of the present application also provide a scheduling request receiving method, a counter maintenance method, and a device.
  • the terminal equipment does not distinguish between Trigger event, maintain the same SR counter, but when resetting, the reset condition takes the SR trigger event into consideration. This prevents terminal equipment from triggering the random access process prematurely, ensuring fairness, and avoiding random access resources.
  • Abuse, simple implementation and cost saving, the following will be described in conjunction with the embodiments of the third to fifth aspects respectively.
  • the embodiment of the present application provides a counter maintenance method, which is described from the terminal device.
  • FIG. 8 is a schematic diagram of a counter maintenance method according to an embodiment of the present application. As shown in FIG. 8, the method includes:
  • the upper layer of the terminal device triggers a first scheduling request, where the first scheduling request is triggered by a trigger event of a first type,
  • the upper layer of the terminal device sets a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0.
  • the trigger event of the first type triggers a first SR
  • the first SR corresponds to the first SR configuration
  • the terminal device determines whether there are other SRs triggered by the trigger event of the first type corresponding to the first SR configuration.
  • the method may further include: (optionally, not shown), the terminal device uses the resource in the first scheduling request configuration to send the first scheduling request.
  • FIG. 9 is another schematic diagram of a counter maintenance method according to an embodiment of the present application. As shown in FIG. 9, the method includes:
  • the upper layer of the terminal device cancels the suspended first scheduling request, where the first scheduling request is triggered by a trigger event of the first type,
  • the upper layer of the terminal device sets a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0.
  • the upper layer of the terminal device triggers the first scheduling request, and the first scheduling request is in a suspended state. In the following cases, the upper layer will cancel the suspended SR:
  • the PDU When a MAC PDU is sent, the PDU includes a long or short BSR MAC CE.
  • the MAC CE includes the buffer status before the MAC PDU is assembled and until (and including) the last event that triggered the BSR. The higher layer will cancel the MAC PDU assembly All pending SRs triggered by BSR;
  • the upper layer will cancel all the suspended SRs triggered for the BSR.
  • the PDU When a MAC PDU is sent, the PDU includes a BFR (Beam Failure Recovery) MAC CE or Truncated BFR MAC CE.
  • the MAC CE includes the beam failure recovery information of the secondary cell, and the upper layer will Cancel all the suspended SRs triggered by the BFR of the secondary cell before the MAC PDU is assembled;
  • the MAC PDU When the MAC PDU is sent, the MAC PDU includes a persistent LBT failure MAC CE, which indicates the persistent LBT failure of the serving cell that triggered the SR, and the higher layer will cancel the suspended SR;
  • the upper layer will cancel the triggered uplink continuous LBT failure.
  • the upper layer of the terminal device sets a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0.
  • the first SR corresponds to the first SR configuration
  • the terminal device determines whether other SRs (fourth SR) triggered by the second type of triggering event are suspended corresponding to the first SR configuration.
  • the upper layer of the terminal device sets the counter or the corresponding variable that records the number of times the first scheduling request is sent to 0.
  • the counter maintenance methods in FIG. 8 and FIG. 9 can be executed individually or in combination, and the embodiment of the present application is not limited thereto.
  • the higher layer is a MAC layer (for example, a MAC layer entity), and the lower layer is a physical layer, but this embodiment is not limited thereto.
  • the first type of trigger event is a logical channel trigger
  • the second type of trigger event is a non-logical channel trigger
  • the first type of trigger event is a non-logical channel trigger
  • the second type of trigger event is a logical channel trigger.
  • logical channel triggering is also BSR triggering for status buffer report
  • non-logical channel triggering is also MAC CE triggering.
  • the non-logical channel triggering includes secondary cell BFR triggering and/or continuous LBT failure triggering.
  • the scheduling request triggered by the logical channel and the scheduling request triggered by the non-logical channel use the same scheduling request transmission times counter.
  • SR1 is the SR triggered by the logical channel
  • SR2 is the SR triggered by the BFR of the secondary cell.
  • the two share the SR configuration.
  • the largest of the SR configurations is The number of transmissions sr-TransMax is set to 4.
  • SR_COUNTER is set to 0.
  • the SR_COUNTER When SR2 is cancelled (optional, the same SR configuration is set by Different from when SR1 triggered by the logical channel triggered by the BFR of the secondary cell is suspended), the SR_COUNTER is set to 0, thus, the SR_COUNTER will not reach 4 too early, so that it can prevent the terminal equipment from triggering random access prematurely
  • the process requests uplink authorization to ensure fairness, avoid the abuse of random access resources, and is simple to implement and save costs.
  • the embodiment of the present application provides a counter maintenance method, which is described from the terminal device.
  • FIG. 11 is another schematic diagram of a counter maintenance method according to an embodiment of the present application. As shown in FIG. 11, the method includes:
  • the terminal device receives scheduling request related information sent by the network device, where the scheduling request related information includes at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event;
  • the terminal device maintains the counter according to the indication information, where the counter is used to record the number of times the scheduling request is sent.
  • the implementation of the resource information can refer to the embodiments of the first aspect and the second aspect, which will not be repeated here.
  • the indication information that the condition for resetting the counter is related or irrelevant to the scheduling request trigger event can be indicated by the newly added SR-trigger-relatedornot field. For example, 1 bit is used to indicate the indication information, and when the bit value is 1, the indication information is reset.
  • the condition of the counter is related to the triggering event of the scheduling request. When the bit value is 0, the condition indicating that the counter is reset is not related to the triggering event of the scheduling request, and vice versa.
  • the terminal device receives the scheduling request related information sent by the network device using RRC signaling.
  • the above-mentioned SR-trigger-relatedornot field may be added to the SR configuration, and the network device uses RRC signaling to send information for the terminal device.
  • Sending the configuration index of the SR the terminal device can determine the SR configuration it uses according to the index, and then determine the resource information indicated in the SR configuration and the indication information SR-trigger-relatedornot, and maintain the correspondence (with the SR configuration) according to the indication information.
  • SR-trigger-relatedornot field for example, it is also possible to add the above-mentioned SR-trigger-relatedornot field to the logical channel parameters (represented by the information element LogicalChannelConfig) and the MAC cell group parameters (using the information element MAC-CellGroupConfig), and the network device uses the RRC signal Command to send the configuration index for the terminal device to send the SR and the instruction information SR-trigger-relatedo-rnot, the terminal device can determine the SR configuration it uses according to the index, and maintain the corresponding (corresponding to the SR configuration) SR according to the instruction information Counter, no more examples here.
  • the terminal device when the indication information indicates that the condition for resetting the counter is related to the scheduling request trigger event, the terminal device considers the SR trigger event to maintain the counter, for example, resetting the counter using the method of the foregoing third aspect embodiment counter.
  • the terminal device uses the existing method to reset the counter, that is, regardless of the SR trigger event, an SR is triggered (corresponding to the first SR configuration)
  • SR_COUNTER is set to 0 when no other SR is suspended corresponding to the same first SR configuration.
  • the network device uses the indication information to indicate whether the condition for the terminal device to reset the counter considers the SR trigger event. Therefore, when the condition for resetting the counter considers the SR trigger event, the terminal device can prevent the terminal device from triggering the random prematurely.
  • the access process ensures fairness, avoids the abuse of random access resources, and is simple to implement and save costs.
  • the embodiment of the present application provides a method for receiving a scheduling request, which is described from a network device.
  • FIG. 12 is a schematic diagram of a method for receiving a scheduling request according to an embodiment of the present application. As shown in FIG. 12, the method includes:
  • the network device sends scheduling request related information to a terminal device, where the scheduling request related information includes at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event;
  • the network device receives a scheduling request sent by the terminal device on the resource indicated by the resource information.
  • the implementation manner of operation 1201 corresponds to 1101 in the embodiment of the fourth aspect.
  • the implementation manner of the indication information reference may be made to the embodiment of the fourth aspect, and the repetition will not be repeated.
  • the terminal device 1202 maintains the counter according to the indication information.
  • the counter is used to record the number of times the scheduling request is sent, and may send an SR to the network device on the resource indicated by the resource information, and the network device receives the For the scheduling request sent by the terminal device on the resource indicated by the resource information, reference may be made to the embodiment of the second aspect for details, which will not be repeated here.
  • the network device uses the indication information to indicate whether the condition for the terminal device to reset the counter considers the SR trigger event. Therefore, when the condition for resetting the counter considers the SR trigger event, the terminal device can prevent the terminal device from triggering the random prematurely.
  • the access process ensures fairness, avoids the abuse of random access resources, and is simple to implement and save costs.
  • the embodiment of the present application provides a counter maintenance device.
  • the device may be, for example, a terminal device (for example, the aforementioned terminal device), or may be some or some components or components configured in the terminal device, and the same content as the embodiment of the first aspect will not be repeated.
  • Fig. 13 is a schematic diagram of a counter maintenance device according to an embodiment of the present application. As shown in FIG. 13, the counter maintenance device 1300 includes:
  • the receiving unit 1301 is configured to receive scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and related information of a scheduling request counter;
  • the maintenance unit 1302 is configured to maintain the first SR counter corresponding to the first type of trigger event and/or maintain the second SR counter corresponding to the second type of trigger event according to the related information of the scheduling request counter.
  • the related information of the scheduling request counter includes the maximum number of times of sending the scheduling request.
  • the maximum number of times the scheduling request is sent corresponds to or does not correspond to the scheduling request trigger event.
  • the first type of trigger event is a logical channel trigger and the second type of trigger event is a non-logical channel trigger.
  • the non-logical channel trigger includes BFR trigger of the secondary cell and/or continuous LBT failure trigger.
  • the maximum number of dispatch requests corresponding to the trigger event of the first type and the maximum number of dispatch requests corresponding to the trigger event of the second type are the same or different.
  • the maximum number of dispatch requests corresponding to the BFR trigger of the secondary cell and the maximum number of dispatch requests corresponding to the continuous LBT failure trigger are the same or different.
  • the receiving unit 1301 receives the radio resource control signaling sent by the network device, and applies the scheduling request related information included in the radio resource control signaling.
  • the related information of the scheduling request counter includes at least one parameter of the maximum number of times the scheduling request is sent.
  • the device further includes:
  • An indication unit (optional, not shown), which is used to instruct the lower layer to send the first scheduling request or the second scheduling request from the upper layer of the terminal device; the first scheduling request is triggered by a trigger event of the first type; the first The second scheduling request is triggered by the second type of trigger event.
  • the maintenance unit 1302 is configured to increase the first scheduling request counter or the corresponding variable corresponding to the first scheduling request triggered by the first type of trigger event by 1, or to add 1 to the higher level of the terminal device.
  • the second scheduling request counter or corresponding variable corresponding to the second scheduling request triggered by the second type of triggering event is incremented by 1.
  • the maintenance unit 1302 when the continuous LBT failure indication from the lower layer is not received, or when the continuous LBT failure indication from the lower layer is received and the LBT failure recovery configuration information is not configured, the maintenance unit 1302 is used in the terminal device
  • the higher layer adds 1 to the first scheduling request counter or corresponding variable corresponding to the first scheduling request triggered by the trigger event of the first type, or adds the second scheduling request corresponding to the second scheduling request triggered by the trigger event of the second type. Request the counter or the corresponding variable to increase by 1.
  • the indicating unit instructs the lower layer to send the first scheduling request at the higher layer;
  • the instruction unit instructs the lower layer to send the second scheduling request at the higher layer.
  • the instructing unit when the first scheduling request transmission count timer is less than the maximum scheduling request transmission count, instructs the lower layer to send the first scheduling request at a higher level; when the second scheduling request transmission count timer is less than the scheduling request When the maximum number of transmissions is requested, the instruction unit instructs the lower layer to send the second scheduling request at the higher layer.
  • the maintenance unit 1302 cancels the first scheduling request at a higher level of the terminal device, Or, cancel the first scheduling request and the second scheduling request, or, when the second scheduling request counter or corresponding variable is 0, or greater than or equal to the maximum number of dispatch requests corresponding to the second type of trigger event, cancel the The first scheduling request and the second scheduling request.
  • the maintenance unit 1302 cancels the first scheduling request at a higher level of the terminal device, or cancels the first scheduling request And the second scheduling request, or when the second scheduling request counter or the corresponding variable is 0, or greater than or equal to the maximum number of times the scheduling request is sent, the first scheduling request and the second scheduling request are cancelled.
  • the device may further include:
  • An initiating unit (optional, not shown), which is used to initiate a random access procedure on a special cell at the upper layer of the terminal device.
  • the device may further include: (optional, not shown)
  • a triggering unit which is used to trigger a first scheduling request and/or a second scheduling request at a higher level of the terminal device, the first scheduling request being triggered by the first type of triggering event, and the second scheduling request being triggered by the second type Event triggered.
  • the maintenance unit 1302 sets the first scheduling request counter or the corresponding variable to 0 at a higher level of the terminal device when no other third scheduling requests triggered by the first type of triggering event are suspended; And/or, when no other fourth scheduling request triggered by the second type of triggering event is suspended, the maintenance unit 1302 sets the second scheduling request counter or the corresponding variable to 0 at the higher level of the terminal device.
  • the maintenance unit 1302 sets a first variable to record the number of times the first SR is sent, and sets a second variable to record the number of times the second SR is sent.
  • the foregoing first scheduling request, second scheduling request, third scheduling request, and fourth scheduling request may be configured corresponding to one scheduling request.
  • the higher layer is the MAC layer and the lower layer is the physical layer.
  • the counter maintenance device 1300 may also include other components or modules, and for the specific content of these components or modules, reference may be made to related technologies.
  • FIG. 13 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of this application does not limit this.
  • the terminal equipment maintains the SR counters corresponding to each type of trigger event, so as to avoid initiating the random access process too early or too late, maintain the fairness of the SR triggered by various trigger events, and avoid random access. Abuse of resources.
  • the embodiment of the present application provides a counter maintenance device.
  • the apparatus may be, for example, a terminal device (for example, the aforementioned terminal device), or may be some or some components or components configured in the terminal device, and the same content as the embodiment of the third aspect will not be repeated.
  • Fig. 14 is a schematic diagram of a counter maintenance device according to an embodiment of the present application. As shown in FIG. 14, the counter maintenance device 1400 includes:
  • a trigger unit 1401 which is used to trigger a first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a trigger event of the first type;
  • the processing unit 1402 is configured to, when the third scheduling request triggered by the trigger event of the first type is not suspended, the upper layer of the terminal device sets a counter or a corresponding variable that records the number of transmissions of the first scheduling request to 0.
  • the device may further include: (not shown, optional)
  • the sending unit is configured to use the resource in the first scheduling request configuration to send the first scheduling request.
  • Fig. 15 is a schematic diagram of a counter maintenance device according to an embodiment of the present application. As shown in Fig. 15, the counter maintenance device 5 includes:
  • the canceling unit 1501 is configured to cancel the suspended first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a first type of trigger event;
  • the processing unit 1502 is configured to set a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0 at the upper layer of the terminal device.
  • the canceling unit 1501 cancels the suspended first scheduling request at a higher level of the terminal device.
  • the processing unit 1502 sets a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0 at the higher level of the terminal device.
  • the higher layer is the MAC layer
  • the first type of trigger event is a logical channel trigger
  • the second type of trigger event is a non-logical channel trigger
  • the first type of trigger event is a non-logical channel trigger
  • the second type of trigger event is a non-logical channel trigger.
  • the trigger event is a logical channel trigger, where the non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • the scheduling request triggered by the logical channel and the scheduling request triggered by the non-logical channel use the same scheduling request transmission times counter.
  • the counter maintenance devices 1400-1500 may also include other components or modules. For the specific content of these components or modules, reference may be made to related technologies.
  • FIGS. 14-15 only exemplarily show the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.
  • the terminal device considers the SR trigger event to reset the counter, thereby avoiding the terminal device from triggering the random access process to request uplink authorization prematurely, ensuring fairness, avoiding the abuse of random access resources, and being simple to implement ,save costs.
  • the embodiment of the present application provides a counter maintenance device.
  • the apparatus may be, for example, a terminal device (for example, the aforementioned terminal device), or may be some or some parts or components configured in the terminal device, and the same content as the embodiment of the fourth aspect will not be repeated.
  • Fig. 16 is a schematic diagram of a counter maintenance device according to an embodiment of the present application. As shown in FIG. 16, the counter maintenance device 1600 includes:
  • the receiving unit 1601 is configured to receive scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event;
  • the maintenance unit 1602 is configured to maintain the counter according to the indication information, and the counter is used to record the number of times the scheduling request is sent.
  • the counter maintenance device 1600 may also include other components or modules. For the specific content of these components or modules, reference may be made to related technologies.
  • FIG. 16 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.
  • the network device uses the indication information to indicate whether the condition for the terminal device to reset the counter considers the SR trigger event. Therefore, when the condition for resetting the counter considers the SR trigger event, the terminal device can prevent the terminal device from triggering the random prematurely.
  • the access process ensures fairness, avoids the abuse of random access resources, and is simple to implement and save costs.
  • the embodiment of the present application provides an apparatus for receiving a scheduling request.
  • the device may be, for example, a network device (such as the aforementioned network device), or may be some or some components or components configured in the network device, and the same content as the embodiments of the second and fifth aspects will not be repeated.
  • Fig. 17 is a schematic diagram of a scheduling request receiving apparatus according to an embodiment of the present application. As shown in FIG. 17, the scheduling request receiving apparatus 1700 includes:
  • the sending unit 1701 is configured to send scheduling request related information to a terminal device, where the scheduling request related information includes at least resource information and related information of a scheduling request counter corresponding to a scheduling request trigger event;
  • the receiving unit 1702 is configured to receive a scheduling request sent by the terminal device on the resource indicated by the resource information.
  • the related information of the dispatch request counter corresponding to the dispatch request trigger event includes the maximum number of dispatch requests sent corresponding to the dispatch request trigger event, and/or the condition for resetting the counter is related to the dispatch request trigger event or not.
  • the scheduling request trigger event includes a first type trigger event triggered by a logical channel and a second type trigger event triggered by a non-logical channel.
  • the non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • the maximum number of dispatch requests corresponding to the trigger event of the first type and the maximum number of dispatch requests corresponding to the trigger event of the second type are the same or different.
  • the maximum number of dispatch requests corresponding to the BFR trigger of the secondary cell is the same or different from the maximum number of dispatch requests corresponding to the continuous LBT failure trigger.
  • the sending unit 1701 uses radio resource control signaling to send the scheduling request related information.
  • the related information of the scheduling request counter includes at least one parameter of the maximum number of times of dispatching requests, which is used to maintain the first SR counter corresponding to the first type of trigger event and/or to correspond to the second type of trigger event Maintenance of the second SR counter.
  • the scheduling request receiving apparatus 1700 may also include other components or modules, and for the specific content of these components or modules, reference may be made to related technologies.
  • FIG. 17 only exemplarily shows the connection relationship or signal direction between the various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the foregoing components or modules may be implemented by hardware facilities such as a processor, a memory, a transmitter, and a receiver; the implementation of this application does not limit this.
  • the network device uses the indication information to indicate whether the condition for the terminal device to reset the counter considers the SR trigger event. Therefore, when the condition for resetting the counter considers the SR trigger event, the terminal device can prevent the terminal device from triggering the random prematurely.
  • the access process ensures fairness, avoids the abuse of random access resources, and is simple to implement and save costs.
  • the network device respectively configures the relevant information of the SR counter corresponding to each type of trigger event and sends it to the terminal device so that the terminal device can maintain the SR counter corresponding to each type of trigger event according to the relevant information, thereby Avoid initiating the random access process too early or too late, maintain the fairness of SR triggered by various trigger events, and avoid the abuse of random access resources.
  • the embodiment of the present application also provides a communication system, which can be referred to FIG.
  • the communication system 100 may at least include:
  • a terminal device that receives information related to a scheduling request sent by a network device.
  • the related information of the scheduling request includes at least resource information and related information of a scheduling request counter; according to the related information of the scheduling request counter, maintains the first type of trigger event corresponding to the first type of trigger event.
  • the communication system 100 may at least include:
  • a terminal device that triggers a first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a trigger event of the first type; when the third scheduling request triggered by the trigger event of the first type is not suspended,
  • the upper layer of the terminal device sets the counter or the corresponding variable that records the number of transmissions of the first scheduling request to 0; or,
  • the communication system 100 may include at least:
  • a terminal device that receives information related to a scheduling request sent by a network device.
  • the related information of the scheduling request includes at least resource information and indication information that the condition for resetting the counter is related or not related to the triggering event of the scheduling request; maintaining the counter according to the indication information, This counter is used to record the number of times the scheduling request is sent.
  • the communication system 100 may at least include:
  • a network device that sends scheduling request related information to a terminal device, the scheduling request related information includes at least resource information and related information about a scheduling request counter corresponding to a scheduling request trigger event; receiving the terminal device to send information on the resource indicated by the resource information Scheduling request.
  • the embodiments of the present application also provide a terminal device, but the present application is not limited to this, and may also be other devices.
  • FIG. 18 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1800 may include a processor 1810 and a memory 1820; the memory 1820 stores data and programs, and is coupled to the processor 1810. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions.
  • the processor 1810 may be configured to execute a program to implement the counter maintenance method as described in the embodiment of the first aspect.
  • the processor 1810 may be configured to perform the following control: receive scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and scheduling request counter related information; and maintaining the scheduling request counter based on the scheduling request counter related information The first SR counter corresponding to the trigger event of the first type and/or the second SR counter corresponding to the trigger event of the second type are maintained.
  • the processor 1810 may be configured to execute a program to implement the counter maintenance method as described in the embodiment of the third aspect.
  • the processor 1810 may be configured to perform the following control: trigger a first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a trigger event of the first type; when it is not triggered by a trigger event of the first type
  • the higher layer of the terminal device sets the counter or the corresponding variable that records the number of times the first scheduling request is sent to 0; or the higher layer of the terminal device cancels the suspended first scheduling request, where the The first scheduling request is triggered by a trigger event of the first type; the upper layer of the terminal device sets a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0.
  • the processor 1810 may be configured to execute a program to implement the counter maintenance method as described in the embodiment of the fourth aspect.
  • the processor 1810 may be configured to perform the following control: receive scheduling request related information sent by a network device, the scheduling request related information including at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event ; Maintain the counter according to the instruction information, and the counter is used to record the number of times the scheduling request is sent.
  • the terminal device 1800 may further include: a communication module 1830, an input unit 1840, a display 1850, and a power supply 1860.
  • a communication module 1830 the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the terminal device 1800 does not necessarily include all the components shown in FIG. 18, and the above-mentioned components are not necessary; in addition, the terminal device 1800 may also include components not shown in FIG. There is technology.
  • the embodiments of the present application also provide a network device, which may be a base station, for example, but the present application is not limited to this, and may also be other network devices.
  • a network device which may be a base station, for example, but the present application is not limited to this, and may also be other network devices.
  • FIG. 19 is a schematic diagram of the structure of a network device according to an embodiment of the present application.
  • the network device 1900 may include: a processor 1910 (for example, a central processing unit CPU) and a memory 1920; the memory 1920 is coupled to the processor 1910.
  • the memory 1920 can store various data; in addition, it also stores an information processing program 1930, and the program 1930 is executed under the control of the processor 1910.
  • the processor 1910 may be configured to execute a program to implement the scheduling request receiving method as described in the embodiments of the second and fifth aspects.
  • the processor 1910 may be configured to perform the following control: send scheduling request related information to a terminal device, the scheduling request related information including at least resource information and related information about a scheduling request counter corresponding to a scheduling request trigger event; and receiving the terminal device The scheduling request sent on the resource indicated by the resource information.
  • the network device 1900 may further include: a transceiver 1940, an antenna 1950, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the network device 1900 does not necessarily include all the components shown in FIG. 19; in addition, the network device 1900 may also include components not shown in FIG. 19, and reference may be made to the prior art.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the counter maintenance method described in the first, third, and fourth embodiments.
  • An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables the terminal device to execute the counter maintenance method described in the first, third, and fourth embodiments.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the scheduling request receiving method described in the embodiments of the second and fifth aspects.
  • An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program causes a network device to execute the scheduling request receiving method described in the embodiments of the second and fifth aspects.
  • the above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software.
  • This application relates to such a computer-readable program, when the program is executed by a logic component, the logic component can realize the above-mentioned device or constituent component, or the logic component can realize the above-mentioned various methods Or steps.
  • This application also relates to storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow or each hardware module.
  • These software modules can respectively correspond to the steps shown in the figure.
  • These hardware modules can be implemented by solidifying these software modules by using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the drawings can be implemented as general-purpose processors, digital signal processors (DSPs) for performing the functions described in this application. ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof.
  • DSPs digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, and multiple micro-processing Processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • a method for receiving a scheduling request, which is applied to a network device, and the method includes:
  • the network device sends scheduling request related information to the terminal device, where the scheduling request related information includes at least resource information and related information of a scheduling request counter corresponding to a scheduling request trigger event;
  • the network device receives the scheduling request sent by the terminal device on the resource indicated by the resource information.
  • non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • the related information of the scheduling request counter corresponding to the triggering event of the scheduling request includes at least one parameter of the maximum transmission times of the scheduling request, which is used to compare with the first type Maintenance of the first SR counter corresponding to the trigger event and/or maintenance of the second SR counter corresponding to the second type of trigger event.
  • a counter maintenance method which is applied to a terminal device, and the method includes:
  • the terminal device receives scheduling request related information sent by the network device, where the scheduling request related information includes at least resource information and scheduling request counter related information;
  • the terminal device maintains the first SR counter corresponding to the first type of trigger event and/or maintains the second SR counter corresponding to the second type of trigger event according to the related information of the scheduling request counter.
  • non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • the upper layer of the terminal device instructs the lower layer to send the first scheduling request or the second scheduling request; the first scheduling request is triggered by a trigger event of the first type; the second scheduling request is triggered by a trigger event of the second type.
  • maintaining the first SR counter corresponding to the first type of trigger event and/or maintaining the second SR counter corresponding to the second type of trigger event comprises: a higher layer of the terminal device
  • the first scheduling request counter or corresponding variable corresponding to the first scheduling request triggered by the trigger event of the first type is incremented by 1, or the corresponding variable corresponding to the second scheduling request triggered by the triggering event of the second type is added to
  • the second scheduling request counter or corresponding variable is incremented by 1.
  • the terminal device does not receive a continuous LBT failure indication from a lower layer, or when it receives a continuous LBT failure indication from a lower layer and the LBT failure recovery configuration information is not configured, the terminal device
  • the upper layer of the first scheduling request counter or corresponding variable corresponding to the first scheduling request triggered by the trigger event of the first type is incremented by 1, or the second scheduling request triggered by the triggering event of the second type is increased by 1
  • the corresponding second scheduling request counter or corresponding variable is incremented by 1.
  • the higher layer instructs the lower layer to send the second scheduling request.
  • the higher layer instructs the lower layer to send the second scheduling request.
  • the higher layer of the terminal device cancels the first scheduling request, or,
  • the first scheduling request and the second scheduling request are cancelled.
  • the higher layer of the terminal device cancels the first scheduling request, or,
  • the first scheduling request and the second scheduling request are cancelled.
  • the upper layer of the terminal device initiates a random access procedure on the special cell.
  • the upper layer of the terminal device triggers a first scheduling request and/or a second scheduling request, the first scheduling request is triggered by a trigger event of the first type, and the second scheduling request is triggered by a trigger event of the second type .
  • the upper layer of the terminal device sets the first scheduling request counter or the corresponding variable to 0; and/or,
  • the upper layer of the terminal device sets the second scheduling request counter or the corresponding variable to 0.
  • the terminal device sets a first variable to record the number of times the first SR is sent, and sets a second variable to record the number of times the second SR is sent.
  • a counter maintenance method which is applied to a terminal device, and the method includes:
  • the upper layer of the terminal device triggers the first scheduling request, where the first scheduling request is triggered by a trigger event of the first type, and when the third scheduling request triggered by the trigger event of the first type is not suspended, the terminal device
  • the upper layer of the sets the counter or the corresponding variable that records the number of times the first scheduling request is sent to 0; or,
  • the upper layer of the terminal device cancels the suspended first scheduling request, where the first scheduling request is triggered by a trigger event of the first type, and the upper layer of the terminal device records a counter or corresponding variable of the number of times the first scheduling request is sent Set to 0.
  • the terminal device uses the resources in the first scheduling request configuration to send the first scheduling request.
  • non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • a counter maintenance method applied to a terminal device, the method comprising:
  • the terminal device receives the scheduling request related information sent by the network device, where the scheduling request related information includes at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event;
  • the terminal device maintains the counter according to the indication information, and the counter is used to record the number of times the scheduling request is sent.
  • An apparatus for receiving a scheduling request wherein, when applied to a network device, the apparatus includes:
  • a sending unit configured to send scheduling request related information to the terminal device, the scheduling request related information including at least resource information and related information of a scheduling request counter corresponding to a scheduling request trigger event;
  • the receiving unit is configured to receive the scheduling request sent by the terminal device on the resource indicated by the resource information.
  • the related information of the scheduling request counter corresponding to the scheduling request trigger event includes the maximum number of dispatch requests sent corresponding to the scheduling request trigger event, and/or the condition for resetting the counter Indication information related or not related to the triggering event of the dispatch request.
  • scheduling request trigger event includes a first type trigger event triggered by a logical channel and a second type trigger event triggered by a non-logical channel.
  • non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • the related information of the scheduling request counter corresponding to the triggering event of the scheduling request includes at least one parameter of the maximum number of times of sending a scheduling request, which is used to compare with the first type Maintenance of the first SR counter corresponding to the trigger event and/or maintenance of the second SR counter corresponding to the second type of trigger event.
  • a counter maintenance device wherein, applied to a terminal device, the device includes:
  • a receiving unit configured to receive scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and scheduling request counter related information;
  • the maintenance unit is configured to maintain the first SR counter corresponding to the first type of trigger event and/or maintain the second SR counter corresponding to the second type of trigger event according to the related information of the scheduling request counter.
  • non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • the indication unit is used to instruct the lower layer of the terminal device to send the first scheduling request or the second scheduling request; the first scheduling request is triggered by a trigger event of the first type; the second scheduling request is triggered by the second Triggered by the class trigger event.
  • the instructing unit instructs the lower layer to send the second scheduling request at the higher layer.
  • the instructing unit instructs the lower layer to send the second scheduling request at the higher layer.
  • the maintenance unit cancels the first scheduling request at the higher level of the terminal device, or,
  • the first scheduling request and the second scheduling request are cancelled.
  • the maintenance unit cancels the first scheduling request at the higher level of the terminal device, or,
  • the first scheduling request and the second scheduling request are cancelled.
  • the initiating unit is used to initiate a random access procedure on a special cell at the upper layer of the terminal device.
  • a triggering unit which is used to trigger a first scheduling request and/or a second scheduling request at a higher level of the terminal device, the first scheduling request is triggered by a trigger event of the first type, and the second scheduling request is triggered by The second type of trigger event is triggered.
  • the maintenance unit sets the second scheduling request counter or the corresponding variable to 0 at the upper layer of the terminal device.
  • a counter maintenance device wherein, applied to a terminal device, the device includes:
  • a triggering unit configured to trigger a first scheduling request at a higher level of the terminal device, where the first scheduling request is triggered by a trigger event of the first type
  • the processing unit is configured to set the recording first scheduling request counter or the corresponding variable to 0 when the third scheduling request triggered by the trigger event of the first type is not suspended, or include:
  • a canceling unit configured to cancel the suspended first scheduling request at a higher level of the terminal device, wherein the first scheduling request is triggered by a first type of trigger event
  • the processing unit is configured to set a counter or a corresponding variable that records the number of times the first scheduling request is sent to 0 at a higher level of the terminal device.
  • the sending unit is configured to use the resource in the first scheduling request configuration to send the first scheduling request.
  • non-logical channel trigger includes a secondary cell BFR trigger and/or a continuous LBT failure trigger.
  • a counter maintenance device applied to terminal equipment comprising:
  • a receiving unit configured to receive scheduling request related information sent by a network device, where the scheduling request related information includes at least resource information and indication information that the condition for resetting the counter is related or not related to the scheduling request trigger event;
  • the maintenance unit is configured to maintain the counter according to the indication information, and the counter is used to record the number of times the scheduling request is sent.
  • a terminal device comprising a memory and a processor, the memory storing a computer program, and the processor is configured to execute the computer program to implement the counter maintenance method as described in any one of appendix 9 to 39 .
  • a network device comprising a memory and a processor, the memory storing a computer program, and the processor is configured to execute the computer program to implement the scheduling request reception according to any one of appendix 1 to 8. method.
  • a communication system comprising at least: the terminal device described in Supplement 79.
  • a communication system comprising at least: the network equipment described in Supplement 80.

Landscapes

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

Abstract

本申请实施例提供一种计数器维护方法、调度请求接收方法以及装置，其中，该计数器维护方法包括：该终端设备接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；该终端设备根据该调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。

Description

计数器维护方法，调度请求接收方法以及装置 技术领域
本申请实施例涉及通信技术领域。
背景技术
调度请求(scheduling request，SR)是终端设备向网络设备请求资源用于新数据传输的一种方式，在新无线(NR，New Radio)中，逻辑信道有挂起的常规状态缓存报告(regular BSR)但没有上行资源时，可以触发SR。
由于网络设备不知道终端设备什么时候会发送调度请求，因此网络设备会预先为终端设备配置SR配置，该SR配置中包括物理上行控制信道(PUCCH)资源集，终端设备使用SR配置中的PUCCH资源发送SR，网络设备在已分配的SR配置中的资源上检测是否有SR上报。
对于NR SR过程，图2是该SR_COUNTER维护示意图，如图2所示，在触发SR后，该SR处于挂起(pending)状态，该SR即挂起的SR；终端设备针对该SR配置，维护一个变量SR_COUNTER计数器，在没有其他SR挂起时，该SR_COUNTER置为0，在该计数器大于或等于SR的最大发送次数sr_TransMax时，发起随机接入过程并取消所有挂起的SR，否则高层可以指示低层在SR的一个有效PUCCH资源上发送SR，SR_COUNTER加1。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在新无线(NR，New Radio)Rel-16中，除了逻辑信道触发的SR(即为了BSR的SR)外，引入了新的触发SR的方法，包括在发生了辅小区波束失败恢复(BFR)或者持续先听后说(LBT)失败时，如果没有可用的上行资源发送指示发生辅小区BFR或者持续LBT失败的媒体接入控制层控制单元(MAC CE)，终端设备可以触发SR，换句话说，新引入了由MAC CE触发的SR。另外，逻辑信道触发的SR对应的 SR配置可以共享给辅小区BFR触发的SR，或者共享给持续LBT失败触发的SR，即对于一个SR配置可能对应不同触发方法的SR，发明人发现，当前终端设备针对一个SR配置维护一个SR计数器，而在逻辑信道触发的SR与辅小区BFR或持续LBT失败触发的SR共享SR配置时，该SR配置对应一个SR最大发送值sr_TransMax，会导致过早或过晚发起随机接入过程；另外，在终端设备触发至少两种类型的SR(对应相同SR配置)时，如果只使用一个SR最大发送值sr_TransMax，则无法保证对该至少两种类型的SR都公平，可能出现随机接入资源的滥用现象。
针对上述问题的至少之一，本申请实施例提供一种计数器维护方法、调度请求接收方法及装置。
根据本申请实施例的一个方面，提供一种计数器维护装置，应用于终端设备，包括：
接收单元，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；
维护单元，其用于根据该调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
根据本申请实施例的一个方面，提供一种计数器维护装置，应用于终端设备，包括：
触发单元，其用于在终端设备的高层触发第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；
处理单元，其用于在没有由第一类触发事件触发的第三调度请求挂起时，该终端设备的高层将记录第一调度请求发送次数计数器或相应变量置为0；或者，
取消单元，其用于在终端设备的高层取消挂起的第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；
处理单元，其用于在该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
根据本申请实施例的一个方面，提供一种计数器维护装置，应用于终端设备，包括：
接收单元，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示 信息；
维护单元，其用于根据该指示信息维护该计数器，该计数器用于记录该调度请求的发送次数。
根据本申请实施例的一个方面，提供一种调度请求接收装置，应用于网络设备，包括：
发送单元，其用于向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；
接收单元，其用于接收该终端设备在该资源信息指示的资源上发送的调度请求。
本申请实施例的有益效果之一在于：网络设备分别配置与各个类型触发事件对应的SR计数器的相关信息，终端设备分别维护与各个类型触发事件对应的SR计数器，从而避免过早或过晚发起随机接入过程，保持对各类触发事件触发的SR的公平性，避免随机接入资源的滥用。
本申请实施例的有益效果之一在于：在重置计数器时，该重置的条件考虑该SR触发事件，由此，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本。
本申请实施例的有益效果之一在于：网络设备使用指示信息指示终端设备重置计数器的条件是否考虑SR触发事件，由此，在该重置计数器的条件考虑该SR触发事件时，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请实施例的通信系统的示意图；
图2是SR计数器维护的一示意图；
图3和图4是现有SR计数器存在问题示意图；
图5是本申请实施例的计数器维护方法的一示意图；
图6是本申请实施例SR配置的资源示意图；
图7是本申请实施例的调度请求接收方法的一示意图；
图8是本申请实施例的计数器维护方法的一示意图；
图9是本申请实施例的计数器维护方法的一示意图；
图10是本申请实施例的重置计数器的一示意图；
图11是本申请实施例的计数器维护方法的一示意图；
图12是本申请实施例的调度请求接收方法的一示意图；
图13是本申请实施例的计数器维护装置的一示意图；
图14是本申请实施例的计数器维护装置的一示意图；
图15是本申请实施例的计数器维护装置的一示意图；
图16是本申请实施例的计数器维护装置的一示意图；
图17是本申请实施例的调度请求接收装置的一示意图；
图18是本申请实施例的终端设备的示意图；
图19是本申请实施例的网络设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术 语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收 网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下，“设备”可以指网络设备，也可以指终端设备。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102、103。为简单起见，图1仅以两个终端设备和一个网络设备为例进行说明，但本申请实施例不限于此。
在本申请实施例中，网络设备101和终端设备102、103之间可以进行现有的业务或者未来可实施的业务发送。例如，这些业务可以包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
值得注意的是，图1示出了两个终端设备102、103均处于网络设备101的覆盖范围内，但本申请不限于此。两个终端设备102、103可以均不在网络设备101的覆盖范围内，或者一个终端设备102在网络设备101的覆盖范围之内而另一个终端设备103在网络设备101的覆盖范围之外。
当前终端设备针对一个SR配置维护一个SR计数器，在逻辑信道触发的SR与辅小区BFR或持续LBT失败触发的SR共享SR配置时，针对该SR配置对应一个SR最大发送次数sr_TransMax，会出现过早或过晚发起随机接入过程的问题，以下结合附图3-4详细说明，如图3所示，在上述SR配置共享时，如果网络设备考虑上述两类事件触发的SR，配置一个大的SR最大发送值，那么在仅触发了一个SR时，终端设备需要尝试比预期更多次数的SR发送，才能触发随机接入来获得上行授权，即过晚发起随机接入过程。如图4所示，在上述SR配置共享时，如果网络设备仅考虑一类事件触发的SR，例如考虑逻辑信道触发的SR配置SR最大发送值，那么在触发了两种SR时，终端设备发送SR的次数会比预期的少，就可以触发随机接入来获得上行授权，即过早发起随机接入过程，这对其他SR配置对应的SR是不公平的，同时会增加随机接入资源的使用。
针对上述问题的至少之一，本申请实施例提供一种调度请求接收方法，计数器维护及装置，针对各类型触发事件触发的SR(例如，对应相同SR配置)，终端设备分别维护与各个类型触发事件对应的各SR计数器，该维护包括以下动作：设置SR对应的变量，SR计数器加1，SR计数器重置，SR计数器达到SR最大发送次数的处理，网络设备可以分别配置与各个类型触发事件对应的SR计数器的相关信息，以下分别结合第一至第二方面的实施例进行说明。
第一方面的实施例
本申请实施例提供一种计数器维护方法，从终端设备侧进行说明。
图5是本申请实施例的计数器维护方法的一示意图，如图5所示，该方法包括：
501，终端设备接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；
502，终端设备根据该调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
在本申请实施例中，终端设备分别维护与各个类型触发事件对应的SR计数器，从而避免过早或过晚发起随机接入过程，保持对各个SR的公平性，避免随机接入资源的滥用。
在一些实施例中，该调度请求相关信息至少包括：资源信息和调度请求计数器的 相关信息。其中，该资源信息指示终端设备在哪些PUCCH资源上发送SR，图6是各SR配置对应的资源示意图，如图5所示，该PUCCH资源分布在至少一个小区的至少一个BWP上，该资源可以通过schedulingRequestId字段指示该资源的索引，该索引指示的具体资源使用信息元SchedulingRequestResourceConfig配置，具体可以参考现有技术，此处不再赘述。
在一些实施例中，该调度请求计数器的相关信息包括调度请求最大发送次数，例如包括至少一个调度请求最大发送次数的参数，该调度请求最大发送次数与各个类型触发事件对应或不对应。
例如，在该调度请求计数器的相关信息包括一个调度请求最大发送次数的参数，且该一个调度请求最大发送次数的参数并不是对应各个类型触发事件配置的，终端设备使用该一个调度请求最大发送次数的参数分别维护与各个类型触发事件对应的SR计数器。
例如，在该调度请求计数器的相关信息包括一个调度请求最大发送次数的参数，且该一个调度请求最大发送次数的参数对应各个类型触发事件配置的，即针对各个类型触发事件，使用一个参数表示该SR最大发送次数，换句话说，该一个参数适用于各个类型触发事件对应的SR计数器，终端设备使用该一个调度请求最大发送次数参数分别维护与各个类型触发事件对应的SR计数器。
例如，在该调度请求计数器的相关信息包括至少两个调度请求最大发送次数的参数，且各个调度请求最大发送次数的参数分别对应各个类型触发事件配置的，即针对各个类型触发事件，分别使用其各自的参数表示该SR最大发送次数，终端设备使用该各个调度请求最大发送次数的参数分别维护与各个类型触发事件对应的SR计数器。
在一些实施方式中，上述触发事件包括逻辑信道触发的第一类触发事件以及非逻辑信道触发的第二类触发事件，其中，逻辑信道触发也即为了状态缓存报告BSR触发，非逻辑信道触发也即为了MAC CE触发，其包括辅小区BFR触发和/或持续LBT失败触发，即为了辅小区BFR MAC CE触发和/或为了持续LBT失败MAC CE触发。
在一些实施方式中，在配置一个调度请求最大发送次数的参数时，可以使用sr_TransMax字段表示，在配置至少两个调度请求最大发送次数的参数时，可以使用sr_TransMax_BSR字段和sr_TransMax_MAC CE字段表示，或使用sr_TransMax_BSR 字段，sr_TransMax-LBT-SCell字段和sr_TransMax-BFR-SCell字段表示，此处不再一一举例，上述参数值可以配置为4,8,18,32,64等，例如，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数可以配置为相同或不同，即sr_TransMax_BSR和sr_TransMax_MAC CE的参数值可以相同或不同，其中，在配置参数值相同时，可选的，也可以使用一个字段sr_TransMax表示。例如，针对该第二类触发事件，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同，即sr_TransMax-LBT-SCell和sr_TransMax-BFR-SCell的参数值可以配置为相同或不同，其中，在配置参数值相同时，可选的，也可以使用一个字段sr_TransMax_MAC CE表示。
在一些实施例中，网络设备可以使用无线资源控制(RRC)信令发送该调度请求相关信息，例如，网络设备使用RRC信令配置逻辑信道参数(使用信息元LogicalChannelConfig表示)和MAC小区组参数(使用信息元MAC-CellGroupConfig)，网络设备可以将上述调度请求相关信息包含在逻辑信道参数(使用信息元LogicalChannelConfig表示)和MAC小区组参数(使用信息元MAC-CellGroupConfig)中发送给终端设备，具体可以参考第二方面的实施例。
在一些实施例中，第一类触发事件触发第一调度请求，第二类触发事件触发第二调度请求(例如，第一SR和第二SR对应相同SR配置)，在一个调度请求被触发，直到被取消之前，都可以看作是挂起(pending)状态，这个调度请求是一个挂起的调度请求；终端设备分别维护与各个类型触发事件对应的SR计数器，即维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器；该维护包括以下动作：设置SR对应的变量，SR计数器或相应变量加1，SR计数器重置，SR计数器或相应变量达到SR最大发送值的处理，以下分别说明。
针对设置SR对应的变量：
在一些实施例中，针对该第一类触发事件触发的第一SR，终端设备设置第一变量SR_COUNTER-1用来记录该第一SR的发送次数，针对该第二类触发事件触发的第二SR，终端设备设置第二变量SR_COUNTER-2用来记录该第二SR的发送次数。
针对SR计数器或相应变量加1的动作：
针对该挂起的第一调度请求，终端设备的高层指示低层发送该第一调度请求，该 终端设备的高层将与该第一类触发事件触发的该第一调度请求对应的第一调度请求计数器或相应变量加1；针对该挂起的第二调度请求，终端设备的高层指示低层发送该第二调度请求，该终端设备的高层将与该第二类触发事件触发的该第二调度请求对应的第二调度请求计数器或相应变量加1。
在一些实施例中，还需要确定是否收到来自低层的持续LBT失败指示，以及是否收到了来自低层的持续LBT失败指示且未配置LBT失败恢复配置信息；这是由于在一个MAC封装数据单元(PDU)被发送，且在未从低层收到持续LBT失败指示，且该PDU包括持续LBT失败的MAC CE时，高层会取消持续LBT失败，这意味着不需要发送持续LBT失败触发的SR，或者，在高层重配了LBT失败恢复配置信息时，高层会取消持续LBT失败，这意味着不需要发送持续LBT失败触发的SR。
例如，终端设备的高层指示低层发送该第一调度请求，在没有收到来自低层的持续LBT失败指示，或者在收到了来自低层的持续LBT失败指示且未配置持续LBT失败恢复配置信息时，将该第一调度请求计数器或相应变量加1；终端设备的高层指示低层发送该第二调度请求，在没有收到来自低层的持续LBT失败指示，或者在收到了来自低层的持续LBT失败指示且未配置持续LBT失败恢复配置信息时，将该第二调度请求计数器或相应变量加1。
在一些实施例中，在高层指示低层发送调度请求之前，还需要确定SR计数器或相应变量与其对应的SR最大发送次数(SR最大发送次数参数与各类触发事件对应配置)的关系，在该第一调度请求发送次数计时器或相应变量小于与第一类触发事件对应的调度请求最大发送次数时，高层可以指示低层发送该第一调度请求；在该第二调度请求发送次数计时器或相应变量小于与第二类触发事件对应的调度请求最大发送次数时，高层可以指示低层发送该第二调度请求。
在一些实施例中，在高层指示低层发送调度请求之前，还需要确定SR计数器或相应变量与SR最大发送次数(即各类触发事件对应一个SR最大发送次数参数)的关系，在该第一调度请求发送次数计时器或相应变量小于该调度请求最大发送次数时，高层可以指示低层发送该第一调度请求；在该第二调度请求发送次数计时器或相应变量小于该调度请求最大发送次数时，高层可以指示低层发送该第二调度请求。
需要说明的是，在至少满足“调度请求计数器或相应变量小于最大发送次数”这一条件时，高层可以指示低层发送调度请求，换句话说，还可以结合其他条件判断高 层是否指示低层发送调度请求，例如，该其他条件可以是：重叠的上行链路授权是去优先级的上行链路授权等，本申请实施例并不以此作为限制。
在一些实施例中，高层指示低层发送第一调度请求或第二调度请求，例如高层指示低层在第一资源上发送第一调度请求，和/或高层指示低层在第二资源上发送第二调度请求，其中第一资源和第二资源都是第一SR配置指示的资源，换句话说，该第一调度请求和第二调度请求对应相同的SR配置，即第一SR配置。
以上，说明了SR计数器或相应变量加1的动作，例如，逻辑信道触发的SR对应的第一SR计数器：当该第一SR计数器或相应变量小于sr-TransMax-BSR(或sr-TransMax)，且指示了低层发送该逻辑信道触发的SR(在有效的PUCCH资源上发送，例如第一调度请求配置的资源)时，如果没有收到来自低层的LBT失败指示，或者如果收到了来自低层的LBT失败指示且未配置LBT失败恢复配置时lbt-FailureRecoveryConfig，该逻辑信道触发的SR对应的第一SR计数器或相应变量加1；辅小区BFR触发的SR或持续LBT失败触发的SR对应的第二SR计数器：当该第二SR计数器或相应变量小于sr-TransMax-BFR或sr-TransMax-LBT(或sr-TransMax-MACCE或sr-TransMax)，且指示了低层发送该辅小区BFR触发的SR或持续LBT失败触发的SR(在有效的PUCCH资源上发送，同样是第一调度请求配置的资源)时，如果没有收到来自低层的LBT失败指示，或者如果收到了来自低层的LBT失败指示且未配置LBT失败恢复配置时lbt-FailureRecoveryConfig，该辅小区BFR触发的SR或持续LBT失败触发的SR对应的第二SR计数器或相应变量加1；换句话说，针对一类触发事件触发的SR，在有与该类触发事件不同的触发事件触发的SR挂起(例如，二者使用相同SR配置)，且高层指示低层在有效的PUCCH资源上发送该SR，终端设备将该一类触发事件触发的SR对应的SR计数器或相应变量加1。
针对SR计数器或相应变量达到SR最大发送次数的处理：
在一些实施例中，例如，在第一调度请求计数器或相应变量大于或等于与第一类触发事件对应的调度请求最大发送次数(SR最大发送次数参数与各类触发事件对应配置)时：1)该终端设备的高层取消该第一调度请求，或，2)取消该第一调度请求和该第二调度请求，或，3)在第二调度请求计数器或相应变量为0，或者大于或等于与第二类触发事件对应的调度请求最大发送次数(SR最大发送次数参数与各类触 发事件对应配置)时，取消该第一调度请求和该第二调度请求；例如，在第二调度请求计数器或相应变量大于或等于与第二类触发事件对应的调度请求最大发送次数(SR最大发送次数参数与各类触发事件对应配置)时：1)该终端设备的高层取消该第二调度请求，或，2)取消该第一调度请求和该第二调度请求，3)或，在第一调度请求计数器或相应变量为0，或者大于或等于与第一类触发事件对应的调度请求最大发送次数(SR最大发送次数参数与各类触发事件对应配置)时，取消该第一调度请求和该第二调度请求。
在一些实施例中，例如，在第一调度请求计数器或相应变量大于或等于调度请求最大发送次数(即各类触发事件对应一个SR最大发送次数参数)时，该终端设备的高层取消该第一调度请求，或，取消该第一调度请求和该第二调度请求，或，在第二调度请求计数器或相应变量为0或者大于或等于与该调度请求最大发送次数(即各类触发事件对应一个SR最大发送次数参数)时取消该第一调度请求和该第二调度请求；例如，在第二调度请求计数器或相应变量大于或等于调度请求最大发送次数(即各类触发事件对应一个SR最大发送次数参数)时，该终端设备的高层取消该第二调度请求，或，取消该第一调度请求和该第二调度请求，或，在第一调度请求计数器或相应变量为0或者大于或等于与该调度请求最大发送次数(即各类触发事件对应一个SR最大发送次数参数)时取消该第一调度请求和该第二调度请求。
在一些实施例中，除了取消对应的SR外，高层还会在特殊小区上发起随机接入过程，该随机接入过程可以参考现有技术，此处不再赘述。
以上，说明了SR计数器或相应变量达到最大发送次数的处理，例如，逻辑信道触发的第一SR的第一SR计数器，当该第一SR计数器或相应变量大于或等于sr-TransMax-BSR(或sr-TransMax)时，高层将会在特殊小区上发起随机接入过程并取消所有挂起的SR；或者取消所有逻辑信道对应的挂起的第一SRs；或者辅小区BFR触发的SR或持续LBT失败触发的第二SR(例如，二者使用相同SR配置)的第二SR计数器或相应变量为0或大于或等于sr-TransMax-BFR或sr-TransMax-LBT(或sr-TransMax)时，高层将会在特殊小区上发起随机接入过程并取消所有挂起的SR；例如，辅小区BFR或持续LBT失败触发的第二SR的第二SR计数器，当该第二SR计数器或相应变量大于或等于sr-TransMax-BFR或sr-TransMax-LBT(或sr-TransMax)时，高层将会在特殊小区上发起随机接入过程并取消所有挂起的SRs；或取消所有辅 小区BFR触发的或持续LBT失败触发的挂起的第二SR；或者逻辑信道触发的第一SR(例如，二者使用相同SR配置)对应的第一SR计数器或相应变量为0或大于或等于sr-TransMax-BSR(或sr-TransMax)时，高层将会在特殊小区上发起随机接入过程并取消所有挂起的SR。换句话说，针对各类触发事件触发的SR(挂起状态，使用相同SR配置)，在与各个触发事件对应的一个SR计数器(或相应变量)或至少两个SR计数器(或相应变量)大于或等于调度请求最大发送次数(可以与各类触发事件对应或不对应)，高层会取消对应(与大于或等于调度请求最大发送次数的计数器对应)的SR或取消所有挂起的SR，并在特殊小区上发起随机接入过程。
针对SR计数器重置的动作：
在一些实施例中，在没有由该第一类触发事件触发的其他第三调度请求挂起时，该终端设备的高层将该第一调度请求计数器或相应变量置为0；和/或，在没有由该第二类触发事件触发的其他第四调度请求挂起时，该终端设备的高层将该第二调度请求计数器或相应变量置为0。
以上，说明了SR计数器的重置，例如，逻辑信道触发了第一SR，且没有其他逻辑信道触发的第三SR(例如，二者使用相同SR配置)挂起时，高层将会设置该逻辑信道触发的第一SR对应的第一SR计数器或相应变量为0(即重置该SR计数器)；辅小区BFR或持续LBT失败触发了第二SR，且没有其他辅小区BFR或持续LBT失败触发的第四SR挂起(例如，二者使用相同SR配置)时，高层将会设置该辅小区BFR或持续LBT失败触发的第二SR对应的第二SR计数器或相应变量为0(即重置该SR计数器)，换句话说，如果一类触发事件触发了一个SR，且(对应相同的SR配置)没有其他相同类别触发事件触发的SR挂起时，高层将会设置该类触发事件触发的SR对应的SR计数器或相应变量为0(即重置该SR计数器)。
在一些实施例中，该高层是MAC层(例如MAC层实体)，该低层是物理层，但本实施例并不以此作为限制。
值得注意的是，以上附图5仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图5的记载。
由上述实施例可知，终端设备分别维护与各个类型触发事件对应的SR计数器， 从而避免过早或过晚发起随机接入过程，保持对各个SR的公平性，避免随机接入资源的滥用。
第二方面的实施例
本申请实施例提供一种调度请求接收方法，从网络设备进行说明。
图7是本申请实施例的调度请求接收方法的一示意图，如图7所示，该方法包括：
701，该网络设备向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；
702，该网络设备接收该终端设备在该资源信息指示的资源上发送的调度请求。
在本申请实施例中，网络设备分别配置与各个类型触发事件对应的SR计数器的相关信息，并发送给终端设备，以便终端设备可以根据该相关信息分别维护与各个类型触发事件对应的SR计数器，从而避免过早或过晚发起随机接入过程，保持对各个SR的公平性，避免随机接入资源的滥用。
值得注意的是，以上附图7仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图7的记载。
在一些实施例中，该与调度请求触发事件对应的调度请求计数器的相关信息包括与调度请求触发事件对应的调度请求最大发送次数，该调度请求相关信息的实施方式可以参考第一方面的实施例，此处不再赘述。
在一些实施例中，该调度请求触发事件的具体实施方式可以参考第一方面的实施例，此处不再赘述。
在一些实施例中，网络设备可以预配置并向终端设备发送至少一个SR配置，该每个SR配置包括：配置索引和至少一个调度请求最大发送次数参数，该SR配置可以使用信息元SchedulingRequestConfig表示，该配置索引schedulingRequestId还可以指示资源信息，可以使用信息元SchedulingRequestResourceConfig配置，具体可以参考现有技术，该调度请求最大发送次数参数可以用于与第一类触发事件对应的第一SR计数器的维护和/或与第二类触发事件对应的第二SR计数器的维护。例如，在一个SR配置包含一个调度请求最大发送次数参数sr-TransMax时，即对应一个SR配置， 配置一个调度请求最大发送次数参数，该参数适用于与第一类触发事件对应的第一SR计数器，也适用于与第二类触发事件对应的第二SR计数器；例如，对应一个SR配置，配置与调度请求触发事件对应的调度请求最大发送次数参数，在一个SR配置包含两个调度请求最大发送次数参数sr-TransMax-BSR和sr-TransMax-MAC CE时，即，该参数sr-TransMax-BSR适用于与第一类触发事件对应的第一SR计数器，参数sr-TransMax-MAC CE适用于与第二类触发事件对应的第二SR计数器；或包含三个调度请求最大发送次数参数sr-TransMax-BSR，sr-TransMax-LBT-SCell和sr-TransMax-BFR-SCell时，即，该参数sr-TransMax-BSR适用于与第一类触发事件对应的第一SR计数器，参数sr-TransMax-BFR-SCell适用于与辅小区BFR触发对应的第二SR计数器，参数sr-TransMax-LBT-SCell适用于与持续LBT失败触发对应的第三SR计数器；网络设备使用RRC信令发送用于终端设备发送SR的配置索引，终端设备根据该索引可以确定其使用的SR配置，进而确定该SR配置中指示的资源信息和调度请求最大发送次数参数，并使用调度请求最大发送次数参数分别维护与各类触发事件对应的SR计数器，例如，使用逻辑信道参数(使用信息元LogicalChannelConfig表示)和MAC小区组参数(使用信息元MAC-CellGroupConfig)承载上述配置索引。
在一些实施例中，与前述实施方式不同的是，可以将与调度请求触发事件对应的调度请求计数器的相关信息直接承载于RRC信令中，例如，网络设备使用RRC信令配置逻辑信道参数(使用信息元LogicalChannelConfig表示)和MAC小区组参数(使用信息元MAC-CellGroupConfig)，网络设备可以将与调度请求触发事件对应的调度请求计数器的相关信息包含在逻辑信道参数(使用信息元LogicalChannelConfig表示)和MAC小区组参数(使用信息元MAC-CellGroupConfig)中发送给终端设备，例如，可以在LogicalChannelConfig新增sr-TransMax-BSR字段指示与逻辑信道触发的调度请求的最大发送次数，在MAC-CellGroupConfig新增字段sr-TransMax-LBT-SCell、sr-TransMax-BFR-SCell指示持续LBT失败触发的调度请求的最大发送次数以及与辅小区BFR触发的调度请求的最大发送次数。在该实施例中，网络设备可以预配置并向终端设备发送至少一个SR配置，该每个SR配置包括：配置索引和调度请求最大发送次数参数，例如，可以不配置该调度请求最大发送次数参数，将调度请求最大发送次数参数属性由不可缺mandate修改为在某些情况下，可选optional，needS，例如各类触发事件对应相同SR配置时，该参数为缺省absent(换句话说，终端设备可以 使用RRC信令中指示的最大发送次数参数，因此，不需要在该SR配置中配置最大发送次数参数)，否则为mandate；例如，仍然可以配置该调度请求最大发送次数参数，但在RRC信令中新增加上述最大发送次数参数字段后，终端设备使用RRC信令中指示的最大发送次数参数，忽略SR配置中配置的调度请求最大发送次数参数。
在一些实施例中，上述调度请求的最大发送次数参数值可以配置为4,8,18,32,64等，其中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数可以配置为相同或不同，即sr_TransMax_BSR和sr_TransMax_MAC CE的参数值可以相同或不同，其中，在配置参数值相同时，可选的，也可以使用一个字段sr_TransMax表示。例如，针对该第二类触发事件，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同，即sr_TransMax-LBT-SCell和sr_TransMax-BFR-SCell的参数值可以配置为相同或不同，其中，在配置参数值相同时，可选的，也可以使用一个字段sr_TransMax_MAC CE表示。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，网络设备分别配置与各个类型触发事件对应的SR计数器的相关信息，并发送给终端设备，以便终端设备可以根据该相关信息分别维护与各个类型触发事件对应的SR计数器，从而避免过早或过晚发起随机接入过程，保持对各个SR的公平性，避免随机接入资源的滥用。
另外，针对前述问题的至少之一，本申请实施例还提供一种调度请求接收方法，计数器维护方法及装置，针对各类型触发事件触发的SR(例如，对应相同SR配置)，终端设备不区分触发事件，维护同一SR计数器，但在重置时，该重置的条件考虑该SR触发事件，由此，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本，以下分别结合第三至第五方面的实施例进行说明。
第三方面的实施例
本申请实施例提供一种计数器维护方法，从终端设备进行说明。
图8是本申请实施例的计数器维护方法的一示意图，如图8所示，该方法包括：
801，终端设备的高层触发第一调度请求，其中，该第一调度请求是由第一类触发事件触发的，
802，在没有由第一类触发事件触发的第三调度请求挂起时，该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，第一类触发事件触发第一SR，该第一SR对应第一SR配置，终端设备确定对应该第一SR配置是否有由该第一类触发事件触发的其他SR(第三SR)挂起，在没有由第一类触发事件触发的第三调度请求挂起时，该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，该方法还可以包括：(可选，未图示)，该终端设备使用第一调度请求配置中的资源发送该第一调度请求。
图9是本申请实施例的计数器维护方法的另一示意图，如图9所示，该方法包括：
901，终端设备的高层取消挂起的第一调度请求，其中，该第一调度请求是由第一类触发事件触发的，
902，该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，终端设备的高层触发第一调度请求，该第一调度请求处于挂起状态，在以下情况下，高层会取消挂起的SR：
对于逻辑信道触发的SR：
1)当MAC PDU发送时，该PDU包括长或短BSR MAC CE，该MAC CE包括该MAC PDU组装前、直到(并包括)触发BSR的最后的事件的缓存状态，高层会取消该MAC PDU组装前为了BSR触发的所有挂起的SR；
2)当上行授权能够容纳所有可用于传输的挂起的数据时，高层将会取消为了BSR触发的所有挂起的SR。
对于辅小区BFR触发的SR：
1)当MAC PDU发送时，该PDU包括一个BFR(Beam Failure Recovery，波束失败恢复)MAC CE或截短的(Truncated)BFR MAC CE，该MAC CE包括辅小区的波束失败恢复信息，高层将会取消该MAC PDU组装前该辅小区BFR触发的所有 挂起的SR；
2)当辅小区去激活时，高层将会取消该辅小区BFR触发的挂起的SR。
对于持续LBT失败触发的SR：
1)当MAC PDU发送时，该MAC PDU包括一个持续LBT失败MAC CE，该MAC CE指示触发SR的服务小区的持续LBT失败，高层将会取消该挂起的SR；
2)持续LBT失败被取消，高层将会取消挂起的SR。其中，满足如下条件，持续LBT失败会被取消：
a)当一个MAC PDU被发送，且未从低层收到持续LBT失败指示且该PDU包括持续LBT失败MAC CE，高层将会取消发送的LBT失败MAC CE里指示了持续LBT失败的辅小区里的持续LBT失败。
b)如果特殊小区里持续LBT失败被触发且未被取消，且特殊小区里的随机接入过程被认为成功完成，高层将会取消特殊小区里触发的持续LBT失败。
c)如果高层重配了一个服务小区的LBT失败恢复配置lbt-FailureRecoveryConfig，高层将会取消该服务小区里所有触发的持续LBT失败。
d)当MAC重置，如果存在，高层将会取消相应服务小区的触发的上行持续LBT失败。
e)当相应服务小区上由于收到部分带宽切换下行控制信息或RRC信令进行部分带宽切换时，高层将取消触发的上行持续LBT失败。
f)当SCell去激活时，高层将取消该SCell触发的所有上行持续LBT失败。
在一些实施例中，在该SR被取消时，该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，该第一SR对应第一SR配置，终端设备确定对应该第一SR配置是否有由第二类触发事件触发的其他SR(第四SR)挂起，在有由不同于第一类触发事件的第二类触发事件触发的SR(第四SR)挂起时，该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
上述图8和图9中的计数器维护方法可以单独执行，也可以结合执行，本申请实施例并不以此作为限制。
在一些实施例中，该高层是MAC层(例如MAC层实体)，该低层是物理层，但本实施例并不以此作为限制。
在一些实施例中，该第一类触发事件是逻辑信道触发，该第二类触发事件是非逻辑信道触发；或者该第一类触发事件是非逻辑信道触发，该第二类触发事件是逻辑信道触发，其中，逻辑信道触发也即为了状态缓存报告BSR触发，非逻辑信道触发也即为了MAC CE触发，该非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。该逻辑信道触发的调度请求和该非逻辑信道触发的调度请求使用相同的调度请求发送次数计数器。
以下结合附图10说明附图8-9中计数器维护方法，如图10所示，SR1是逻辑信道触发的SR，SR2是辅小区BFR触发的SR，二者共享SR配置，该SR配置中最大发送次数sr-TransMax配置为4，触发SR1后，该相同SR配置没有由逻辑信道触发的其他SR挂起，因此将SR_COUNTER置为0，在SR2取消时(可选的，该相同SR配置中由不同于辅小区BFR触发的逻辑信道触发的SR1挂起时)，将该SR_COUNTER置为0，由此，该SR_COUNTER不会过早的到达4，这样，可以避免终端设备过早的触发随机接入过程请求上行授权，保证公平性，避免了随机接入资源的滥用，且实现简单，节约成本。
第四方面的实施例
本申请实施例提供一种计数器维护方法，从终端设备进行说明。
图11是本申请实施例的计数器维护方法的另一示意图，如图11所示，该方法包括：
1101，该终端设备接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示信息；
1102，该终端设备根据该指示信息维护该计数器，该计数器用于记录该调度请求的发送次数。
在一些实施例中，资源信息的实施方式可以参考第一方面和第二方面的实施例，此处不再赘述。该重置计数器的条件与调度请求触发事件相关或不相关的指示信息可以通过新增SR-trigger-relatedornot字段表示，例如使用1比特表示该指示信息，在该比特值为1时，指示重置计数器的条件与调度请求触发事件相关，在该比特值为0时，指示重置计数器的条件与调度请求触发事件不相关，反之亦可。
在一些实施例中，终端设备接收网络设备使用RRC信令发送的该调度请求相关信息，例如可以在SR配置中新增上述SR-trigger-relatedornot字段，网络设备使用RRC信令发送用于终端设备发送SR的配置索引，终端设备根据该索引可以确定其使用的SR配置，进而确定该SR配置中指示的资源信息和指示信息SR-trigger-relatedornot，并根据该指示信息维护对应(与该SR配置对应)的SR计数器；例如，还可以在逻辑信道参数(使用信息元LogicalChannelConfig表示)和MAC小区组参数(使用信息元MAC-CellGroupConfig)中新增上述SR-trigger-relatedornot字段，网络设备使用RRC信令发送用于终端设备发送SR的配置索引以及指示信息SR-trigger-relatedo-rnot，终端设备根据该索引可以确定其使用的SR配置，根据该指示信息维护对应(与该SR配置对应)的SR计数器，此处不再一一举例。
在一些实施例中，在该指示信息指示重置计数器的条件与调度请求触发事件相关时，该终端设备考虑SR触发事件维护该计数器，例如，使用前述第三方面的实施例的方法重置该计数器。在该指示信息指示重置计数器的条件与调度请求触发事件不相关时，该终端设备使用现有的方法重置计数器，即不考虑SR触发事件，在触发了一个SR(对应第一SR配置)，且对应相同的第一SR配置没有其他SR挂起时，将该SR_COUNTER置为0。
需要说明的是，上述第三方面的实施例和第四方面的实施例可以单独执行，也可以结合执行，本申请实施例并不以此作为限制。
由上述实施例可知，网络设备使用指示信息指示终端设备重置计数器的条件是否考虑SR触发事件，由此，在该重置计数器的条件考虑该SR触发事件时，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本。
第五方面的实施例
本申请实施例提供一种调度请求接收方法，从网络设备进行说明。
图12是本申请实施例的调度请求接收方法的一示意图，如图12所示，该方法包括：
1201，该网络设备向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和重置计数器的条件与调度请求触发事件相关或不相关的指示信息；
1202，该网络设备接收该终端设备在该资源信息指示的资源上发送的调度请求。
在一些实施例中，操作1201的实施方式与第四方面实施例中的1101对应，该指示信息的实施方式可以参考第四方面的实施例，重复之处不再赘述。
在一些实施例中，终端设备1202根据该指示信息维护该计数器，该计数器用于记录该调度请求的发送次数，并可以在该资源信息指示的资源上向网络设备发送SR，该网络设备接收该终端设备在该资源信息指示的资源上发送的调度请求，具体可以参考第二方面的实施例，此处不再赘述。
由上述实施例可知，网络设备使用指示信息指示终端设备重置计数器的条件是否考虑SR触发事件，由此，在该重置计数器的条件考虑该SR触发事件时，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本。
第六方面的实施例
本申请实施例提供一种计数器维护装置。该装置例如可以是终端设备(例如前述的终端设备)，也可以是配置于终端设备的某个或某些部件或者组件，与第一方面的实施例相同的内容不再赘述。
图13是本申请实施例的计数器维护装置的一示意图。如图13所示，计数器维护装置1300包括：
接收单元1301，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；
维护单元1302，其用于根据该调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
在一些实施例中，该调度请求计数器的相关信息包括调度请求最大发送次数。
在一些实施例中，该调度请求最大发送次数与调度请求触发事件对应或不对应。
在一些实施例中，该第一类触发事件是逻辑信道触发的该第二类触发事件是非逻辑信道触发。其中，该非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
在一些实施例中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
在一些实施例中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT 失败触发对应的调度请求最大发送次数相同或不同。
在一些实施例中，该接收单元1301接收该网络设备发送的无线资源控制信令，并应用该无线资源控制信令包括的所述调度请求相关信息。
在一些实施例中，该调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数。
在一些实施例中，该装置还包括：
指示单元(可选，未图示)，其用于从该终端设备的高层指示低层发送第一调度请求或第二调度请求；该第一调度请求是由第一类触发事件触发的；该第二调度请求是由第二类触发事件触发的。
在一些实施例中，该维护单元1302用于在该终端设备的高层将与该第一类触发事件触发的该第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与该第二类触发事件触发的该第二调度请求对应的第二调度请求计数器或相应变量加1。
在一些实施例中，在没有收到来自低层的持续LBT失败指示，或者在收到了来自低层的持续LBT失败指示且未配置LBT失败恢复配置信息时，该维护单元1302用于在该终端设备的高层将与该第一类触发事件触发的该第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与该第二类触发事件触发的该第二调度请求对应的第二调度请求计数器或相应变量加1。
在一些实施例中，在该第一调度请求发送次数计时器小于与第一类触发事件对应的调度请求最大发送次数时，该指示单元在高层指示低层发送第一调度请求；在该第二调度请求发送次数计时器小于与第二类触发事件对应的调度请求最大发送次数时，该指示单元在高层指示低层发送第二调度请求。
在一些实施例中，在该第一调度请求发送次数计时器小于调度请求最大发送次数时，该指示单元在高层指示低层发送第一调度请求；在该第二调度请求发送次数计时器小于该调度请求最大发送次数时，该指示单元在高层指示低层发送第二调度请求。
在一些实施例中，在第一调度请求计数器或相应变量大于或等于与第一类触发事件对应的调度请求最大发送次数时，该维护单元1302在该终端设备的高层取消该第一调度请求，或，取消该第一调度请求和该第二调度请求，或，在第二调度请求计数器或相应变量为0，或者大于或等于与第二类触发事件对应的调度请求最大发送次数时，取消该第一调度请求和该第二调度请求。
在一些实施例中，在第一调度请求计数器或相应变量大于或等于调度请求最大发送次数时，该维护单元1302在该终端设备的高层取消该第一调度请求，或，取消该第一调度请求和该第二调度请求，或，在第二调度请求计数器或相应变量为0，或者大于或等于与该调度请求最大发送次数时，取消该第一调度请求和该第二调度请求。
在一些实施例中，该装置还可以包括：
发起单元(可选，未图示)，其用于在该终端设备的高层在特殊小区上发起随机接入过程。
在一些实施例中，该装置还可以包括：(可选，未图示)
触发单元，其用于在终端设备的高层触发第一调度请求和/或第二调度请求，该第一调度请求是由第一类触发事件触发的，该第二调度请求是由第二类触发事件触发的。
在一些实施例中，在没有由该第一类触发事件触发的其他第三调度请求挂起时，该维护单元1302在该终端设备的高层将该第一调度请求计数器或相应变量置为0；和/或，在没有由该第二类触发事件触发的其他第四调度请求挂起时，该维护单元1302在该终端设备的高层将该第二调度请求计数器或相应变量置为0。
在一些实施例中，该维护单元1302设置第一变量用于记录该第一SR的发送次数，设置第二变量用于记录该第二SR的发送次数。
在本申请实施例中，上述第一调度请求，第二调度请求，第三调度请求和第四调度请求可以对应一个调度请求配置。
在一些实施例中，该高层是MAC层，该低层是物理层。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。计数器维护装置1300还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图13中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实 现；本申请实施并不对此进行限制。
由上述实施例可知，终端设备分别维护与各个类型触发事件对应的SR计数器，从而避免过早或过晚发起随机接入过程，保持对各类触发事件触发的SR的公平性，避免随机接入资源的滥用。
第七方面的实施例
本申请实施例提供一种计数器维护装置。该装置例如可以是终端设备(例如前述的终端设备)，也可以是配置于终端设备的某个或某些部件或者组件，与第三方面的实施例相同的内容不再赘述。
图14是本申请实施例的计数器维护装置的一示意图。如图14所示，计数器维护装置1400包括：
触发单元1401，其用于在终端设备的高层触发第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；
处理单元1402，其用于在没有由第一类触发事件触发的第三调度请求挂起时，该终端设备的高层将记录第一调度请求发送次数计数器或相应变量置为0。
在一些实施例中，该装置还可以包括：(未图示，可选)
发送单元，其用于使用第一调度请求配置中的资源发送该第一调度请求。
图15是本申请实施例的计数器维护装置的一示意图。如图15所示，计数器维护装置5包括：
取消单元1501，其用于在终端设备的高层取消挂起的第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；
处理单元1502其用于在该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，该取消单元1501在终端设备的高层取消挂起的第一调度请求，在有由对应该第一调度请求配置的第二类触发事件触发的第四调度请求挂起时，该处理单元1502在该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，该高层是MAC层，该第一类触发事件是逻辑信道触发，该第二类触发事件是非逻辑信道触发；或者该第一类触发事件是非逻辑信道触发，该第二 类触发事件是逻辑信道触发，其中，非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。其中，该逻辑信道触发的调度请求和该非逻辑信道触发的调度请求使用相同的调度请求发送次数计数器。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。计数器维护装置1400-1500还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图14-15中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，终端设备考虑SR触发事件重置计数器，由此可以避免终端设备过早的触发随机接入过程请求上行授权，保证公平性，避免了随机接入资源的滥用，且实现简单，节约成本。
第八方面的实施例
本申请实施例提供一种计数器维护装置。该装置例如可以是终端设备(例如前述的终端设备)，也可以是配置于终端设备的某个或某些部件或者组件，与第四方面的实施例相同的内容不再赘述。
图16是本申请实施例的计数器维护装置的一示意图。如图16所示，计数器维护装置1600包括：
接收单元1601，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示信息；
维护单元1602，其用于根据该指示信息维护该计数器，该计数器用于记录该调度请求的发送次数。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可 以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。计数器维护装置1600还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图16中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，网络设备使用指示信息指示终端设备重置计数器的条件是否考虑SR触发事件，由此，在该重置计数器的条件考虑该SR触发事件时，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本。
第九方面的实施例
本申请实施例提供一种调度请求接收装置。该装置例如可以是网络设备(例如前述的网络设备)，也可以是配置于网络设备的某个或某些部件或者组件，与第二和第五方面的实施例相同的内容不再赘述。
图17是本申请实施例的调度请求接收装置的一示意图。如图17所示，调度请求接收装置1700包括：
发送单元1701，其用于向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；
接收单元1702，其用于接收该终端设备在该资源信息指示的资源上发送的调度请求。
在一些实施例中，该与调度请求触发事件对应的调度请求计数器的相关信息包括与调度请求触发事件对应的调度请求最大发送次数，和/或重置计数器的条件与调度请求触发事件相关或不相关的指示信息。
在一些实施例中，该调度请求触发事件包括逻辑信道触发的第一类触发事件以及非逻辑信道触发的第二类触发事件。
在一些实施例中，该非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
在一些实施例中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
在一些实施例中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同。
在一些实施例中，该发送单元1701使用无线资源控制信令发送该调度请求相关信息。
在一些实施例中，该调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数，用于与第一类触发事件对应的第一SR计数器的维护和/或与第二类触发事件对应的第二SR计数器的维护。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。调度请求接收装置1700还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图17中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，网络设备使用指示信息指示终端设备重置计数器的条件是否考虑SR触发事件，由此，在该重置计数器的条件考虑该SR触发事件时，可以避免终端设备过早触发随机接入过程，保证公平性，避免随机接入资源的滥用，且实现简单，节约成本。
由上述实施例可知，网络设备分别配置与各个类型触发事件对应的SR计数器的相关信息，并发送给终端设备，以便终端设备可以根据该相关信息分别维护与各个类型触发事件对应的SR计数器，从而避免过早或过晚发起随机接入过程，保持对各类触发事件触发的SR的公平性，避免随机接入资源的滥用。
第十方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第五方面的实施例相同的内容不再赘述。
在一些实施例中，通信系统100至少可以包括：
终端设备，其接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；根据该调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
在一些实施例中，通信系统100至少可以包括：
终端设备，其在终端设备的高层触发第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；在没有由第一类触发事件触发的第三调度请求挂起时，该终端设备的高层将记录第一调度请求发送次数计数器或相应变量置为0；或者，
在终端设备的高层取消挂起的第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；在该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
在一些实施例中，通信系统100至少可以包括：
终端设备，其接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示信息；根据该指示信息维护该计数器，该计数器用于记录该调度请求的发送次数。
在一些实施例中，通信系统100至少可以包括：
网络设备，其向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；接收该终端设备在该资源信息指示的资源上发送的调度请求。
本申请实施例还提供一种终端设备，但本申请不限于此，还可以是其他的设备。
图18是本申请实施例的终端设备的示意图。如图18所示，该终端设备1800可以包括处理器1810和存储器1820；存储器1820存储有数据和程序，并耦合到处理器1810。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
例如，处理器1810可以被配置为执行程序而实现如第一方面的实施例所述的计数器维护方法。例如处理器1810可以被配置为进行如下的控制：接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；根据该调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
例如，处理器1810可以被配置为执行程序而实现如第三方面的实施例所述的计数器维护方法。例如处理器1810可以被配置为进行如下的控制：在终端设备的高层触发第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；在没有由第一类触发事件触发的第三调度请求挂起时，在该终端设备的高层将记录第一调度请求发送次数计数器或相应变量置为0；或者，在终端设备的高层取消挂起的第一调度请求，其中，该第一调度请求是由第一类触发事件触发的；在该终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
例如，处理器1810可以被配置为执行程序而实现如第四方面的实施例所述的计数器维护方法。例如处理器1810可以被配置为进行如下的控制：接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示信息；根据该指示信息维护该计数器，该计数器用于记录该调度请求的发送次数。
如图18所示，该终端设备1800还可以包括：通信模块1830、输入单元1840、显示器1850、电源1860。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1800也并不是必须要包括图18中所示的所有部件，上述部件并不是必需的；此外，终端设备1800还可以包括图18中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种网络设备，例如可以是基站，但本申请不限于此，还可以是其他的网络设备。
图19是本申请实施例的网络设备的构成示意图。如图19所示，网络设备1900可以包括：处理器1910(例如中央处理器CPU)和存储器1920；存储器1920耦合到处理器1910。其中该存储器1920可存储各种数据；此外还存储信息处理的程序1930，并且在处理器1910的控制下执行该程序1930。
例如，处理器1910可以被配置为执行程序而实现如第二和第五方面的实施例所述的调度请求接收方法。例如处理器1910可以被配置为进行如下的控制：向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；接收该终端设备在该资源信息指示的资源上发送的调度请求。
此外，如图19所示，网络设备1900还可以包括：收发机1940和天线1950等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1900也并不是必须要包括图19中所示的所有部件；此外，网络设备1900还可以包括图19中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一，三，四方面的实施例所述的计数器维护方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得终端设备执行第一，三，四方面的实施例所述的计数器维护方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述程序使得所述网络设备执行第二，五方面的实施例所述的调度请求接收方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得网络设备执行第二，五方面的实施例所述的调度请求接收方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信 息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
1.一种调度请求接收方法，其中，应用于网络设备，所述方法包括：
所述网络设备向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；
所述网络设备接收所述终端设备在所述资源信息指示的资源上发送的调度请求。
2.根据附记1所述的方法，其中，所述与调度请求触发事件对应的调度请求计数器的相关信息包括与调度请求触发事件对应的调度请求最大发送次数，和/或重置计数器的条件与调度请求触发事件相关或不相关的指示信息。
3.根据附记1或2所述的方法，其中，所述调度请求触发事件包括逻辑信道触发的第一类触发事件以及非逻辑信道触发的第二类触发事件。
4.根据附记3所述的方法，其中，所述非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
5.根据附记3所述的方法，其中，与第一类触发事件对应的调度请求最大发送次 数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
6.根据附记4或5所述的方法，其中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同。
7.根据附记1至6任一项所述的方法，其中，所述网络设备使用无线资源控制信令发送所述调度请求相关信息。
8.根据附记1至7任一项所述的方法，其中，所述与调度请求触发事件对应的调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数，用于与第一类触发事件对应的第一SR计数器的维护和/或与第二类触发事件对应的第二SR计数器的维护。
9.一种计数器维护方法，其中，应用于终端设备，所述方法包括：
所述终端设备接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；
终端设备根据所述调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
10.根据附记9所述的方法，其中，所述调度请求计数器的相关信息包括调度请求最大发送次数。
11.根据附记10所述的方法，其中，所述调度请求最大发送次数与调度请求触发事件对应或不对应。
12.根据附记9至11任一项所述的方法，其中，所述第一类触发事件是逻辑信道触发的所述第二类触发事件是非逻辑信道触发。
13.根据附记12所述的方法，其中，所述非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
14.根据附记9至13任一项所述的方法，其中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
15.根据附记13或14所述的方法，其中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同。
16.根据附记9至15任一项所述的方法，其中，所述终端设备接收所述网络设备发送的无线资源控制信令，并应用所述无线资源控制信令包括的所述调度请求相关信息。
17.根据附记9至16任一项所述的方法，其中，所述调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数。
18.根据附记9至17任一项所述的方法，其中，所述方法还包括：
终端设备的高层指示低层发送第一调度请求或第二调度请求；所述第一调度请求是由第一类触发事件触发的；所述第二调度请求是由第二类触发事件触发的。
19.根据附记18所述的方法，其中，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器包括：所述终端设备的高层将与所述第一类触发事件触发的所述第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与所述第二类触发事件触发的所述第二调度请求对应的第二调度请求计数器或相应变量加1。
20.根据附记19所述的方法，其中，在没有收到来自低层的持续LBT失败指示，或者在收到了来自低层的持续LBT失败指示且未配置LBT失败恢复配置信息时，所述终端设备的高层将与所述第一类触发事件触发的所述第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与所述第二类触发事件触发的所述第二调度请求对应的第二调度请求计数器或相应变量加1。
21.根据附记18至20任一项所述的方法，其中，在所述第一调度请求发送次数计时器小于与第一类触发事件对应的调度请求最大发送次数时，高层指示低层发送第一调度请求；
在所述第二调度请求发送次数计时器小于与第二类触发事件对应的调度请求最大发送次数时，高层指示低层发送第二调度请求。
22.根据附记18至20任一项所述的方法，其中，在所述第一调度请求发送次数计时器小于调度请求最大发送次数时，高层指示低层发送第一调度请求；
在所述第二调度请求发送次数计时器小于所述调度请求最大发送次数时，高层指示低层发送第二调度请求。
23.根据附记19所述的方法，其中，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器包括：
在第一调度请求计数器或相应变量大于或等于与第一类触发事件对应的调度请求最大发送次数时，
所述终端设备的高层取消所述第一调度请求，或，
取消所述第一调度请求和所述第二调度请求，或，
在第二调度请求计数器或相应变量为0，或者大于或等于与第二类触发事件对应的调度请求最大发送次数时，取消所述第一调度请求和所述第二调度请求。
24.根据附记19所述的方法，其中，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器包括：
在第一调度请求计数器或相应变量大于或等于调度请求最大发送次数时，
所述终端设备的高层取消所述第一调度请求，或，
取消所述第一调度请求和所述第二调度请求，或，
在第二调度请求计数器或相应变量为0，或者大于或等于与所述调度请求最大发送次数时，取消所述第一调度请求和所述第二调度请求。
25.根据附记23或24所述的方法，其中，所述方法还包括：
所述终端设备的高层在特殊小区上发起随机接入过程。
26.根据附记9至17任一项所述的方法，其中，所述方法还包括：
所述终端设备的高层触发第一调度请求和/或第二调度请求，所述第一调度请求是由第一类触发事件触发的，所述第二调度请求是由第二类触发事件触发的。
27.根据附记26所述的方法，其中，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器包括：
在没有由所述第一类触发事件触发的其他第三调度请求挂起时，所述终端设备的高层将所述第一调度请求计数器或相应变量置为0；和/或，
在没有由所述第二类触发事件触发的其他第四调度请求挂起时，所述终端设备的高层将所述第二调度请求计数器或相应变量置为0。
28.根据附记9至17任一项所述的方法，其中，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器包括：
所述终端设备设置第一变量用于记录所述第一SR的发送次数，设置第二变量用于记录所述第二SR的发送次数。
29.根据附记18至28任一项所述的方法，其中，所述第一调度请求，第二调度请求，第三调度请求和第四调度请求对应一个调度请求配置。
30.根据附记18至29任一项所述的方法，其中，所述高层是MAC层，所述低层是物理层。
31.一种计数器维护方法，其中，应用于终端设备，所述方法包括：
终端设备的高层触发第一调度请求，其中，所述第一调度请求是由第一类触发事件触发的，在没有由第一类触发事件触发的第三调度请求挂起时，所述终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0；或者，
终端设备的高层取消挂起的第一调度请求，其中，所述第一调度请求是由第一类触发事件触发的，所述终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
32.根据附记31所述的方法，其中，所述方法还包括：
所述终端设备使用第一调度请求配置中的资源发送所述第一调度请求。
33.根据附记31所述的方法，其中，所述终端设备的高层取消挂起的第一调度请求，在有由对应所述第一调度请求配置的第二类触发事件触发的第四调度请求挂起时，所述终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
34.根据附记31至33任一项所述的方法，其中，所述高层是MAC层。
35.根据附记31至34任一项所述的方法，其中，所述第一类触发事件是逻辑信道触发或非逻辑信道触发。
36.根据附记33至35任一项所述的方法，其中，所述第二类触发事件是非逻辑信道触发或逻辑信道触发，所述第二类触发事件与所述第一类触发事件不同。
37.根据附记35或36所述的方法，其中，非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
38.根据附记35或36所述的方法，其中，所述逻辑信道触发的调度请求和所述非逻辑信道触发的调度请求使用相同的调度请求发送次数计数器。
39.一种计数器维护方法，应用于终端设备，所述方法包括：
所述终端设备接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示信息；
所述终端设备根据所述指示信息维护所述计数器，所述计数器用于记录所述调度请求的发送次数。
40.一种调度请求接收装置，其中，应用于网络设备，所述装置包括：
发送单元，其用于向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；
接收单元，其用于接收所述终端设备在所述资源信息指示的资源上发送的调度请求。
41.根据附记40所述的装置，其中，所述与调度请求触发事件对应的调度请求计数器的相关信息包括与调度请求触发事件对应的调度请求最大发送次数，和/或重置计数器的条件与调度请求触发事件相关或不相关的指示信息。
42.根据附记40或41所述的装置，其中，所述调度请求触发事件包括逻辑信道触发的第一类触发事件以及非逻辑信道触发的第二类触发事件。
43.根据附记42所述的装置，其中，所述非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
44.根据附记42所述的装置，其中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
45.根据附记43或44所述的装置，其中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同。
46.根据附记40至45任一项所述的装置，其中，所述发送单元使用无线资源控制信令发送所述调度请求相关信息。
47.根据附记40至46任一项所述的装置，其中，所述与调度请求触发事件对应的调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数，用于与第一类触发事件对应的第一SR计数器的维护和/或与第二类触发事件对应的第二SR计数器的维护。
48.一种计数器维护装置，其中，应用于终端设备，所述装置包括：
接收单元，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；
维护单元，其用于根据所述调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
49.根据附记9所述的装置，其中，所述调度请求计数器的相关信息包括调度请求最大发送次数。
50.根据附记10所述的装置，其中，所述调度请求最大发送次数与调度请求触发事件对应或不对应。
51.根据附记38至50任一项所述的装置，其中，所述第一类触发事件是逻辑信 道触发的所述第二类触发事件是非逻辑信道触发。
52.根据附记51所述的装置，其中，所述非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
53.根据附记48至52任一项所述的装置，其中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
54.根据附记52或53所述的装置，其中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同。
55.根据附记48至54任一项所述的装置，其中，所述接收单元接收所述网络设备发送的无线资源控制信令，并应用所述无线资源控制信令包括的所述调度请求相关信息。
56.根据附记48至55任一项所述的装置，其中，所述调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数。
57.根据附记48至56任一项所述的装置，其中，所述装置还包括：
指示单元，其用于在终端设备的高层指示低层发送第一调度请求或第二调度请求；所述第一调度请求是由第一类触发事件触发的；所述第二调度请求是由第二类触发事件触发的。
58.根据附记57所述的装置，其中，所述维护单元在所述终端设备的高层将与所述第一类触发事件触发的所述第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与所述第二类触发事件触发的所述第二调度请求对应的第二调度请求计数器或相应变量加1。
59.根据附记58所述的装置，其中，在没有收到来自低层的持续LBT失败指示，或者在收到了来自低层的持续LBT失败指示且未配置LBT失败恢复配置信息时，所述维护单元在所述终端设备的高层将与所述第一类触发事件触发的所述第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与所述第二类触发事件触发的所述第二调度请求对应的第二调度请求计数器或相应变量加1。
60.根据附记57至59任一项所述的装置，其中，在所述第一调度请求发送次数计时器小于与第一类触发事件对应的调度请求最大发送次数时，所述指示单元在高层指示低层发送第一调度请求；
在所述第二调度请求发送次数计时器小于与第二类触发事件对应的调度请求最 大发送次数时，所述指示单元在高层指示低层发送第二调度请求。
61.根据附记57至59任一项所述的装置，其中，在所述第一调度请求发送次数计时器小于调度请求最大发送次数时，所述指示单元在高层指示低层发送第一调度请求；
在所述第二调度请求发送次数计时器小于所述调度请求最大发送次数时，所述指示单元在高层指示低层发送第二调度请求。
62.根据附记58所述的装置，其中，在第一调度请求计数器或相应变量大于或等于与第一类触发事件对应的调度请求最大发送次数时，
所述维护单元在所述终端设备的高层取消所述第一调度请求，或，
取消所述第一调度请求和所述第二调度请求，或，
在第二调度请求计数器或相应变量为0，或者大于或等于与第二类触发事件对应的调度请求最大发送次数时，取消所述第一调度请求和所述第二调度请求。
63.根据附记58所述的装置，其中，在第一调度请求计数器或相应变量大于或等于调度请求最大发送次数时，
所述维护单元在所述终端设备的高层取消所述第一调度请求，或，
取消所述第一调度请求和所述第二调度请求，或，
在第二调度请求计数器或相应变量为0，或者大于或等于与所述调度请求最大发送次数时，取消所述第一调度请求和所述第二调度请求。
64.根据附记62或63所述的装置，其中，所述装置还包括：
发起单元，其用于在所述终端设备的高层在特殊小区上发起随机接入过程。
64.根据附记48至56任一项所述的装置，其中，所述装置还包括：
触发单元，其用于在所述终端设备的高层触发第一调度请求和/或第二调度请求，所述第一调度请求是由第一类触发事件触发的，所述第二调度请求是由第二类触发事件触发的。
66.根据附记65所述的装置，其中，在没有由所述第一类触发事件触发的其他第三调度请求挂起时，所述维护单元在所述终端设备的高层将所述第一调度请求计数器或相应变量置为0；和/或，
在没有由所述第二类触发事件触发的其他第四调度请求挂起时，所述维护单元在所述终端设备的高层将所述第二调度请求计数器或相应变量置为0。
67.根据附记48至56任一项所述的装置，其中，所述维护单元设置第一变量用于记录所述第一SR的发送次数，设置第二变量用于记录所述第二SR的发送次数。
68.根据附记57至67任一项所述的装置，其中，所述第一调度请求，第二调度请求，第三调度请求和第四调度请求对应一个调度请求配置。
69.根据附记57至68任一项所述的装置，其中，所述高层是MAC层，所述低层是物理层。
70.一种计数器维护装置，其中，应用于终端设备，所述装置包括：
触发单元，其用于在终端设备的高层触发第一调度请求，其中，所述第一调度请求是由第一类触发事件触发的；
处理单元，其用于在没有由第一类触发事件触发的第三调度请求挂起时，所述终端设备的高层将记录第一调度请求计数器或相应变量置为0；或者包括：
取消单元，其用于在终端设备的高层取消挂起的第一调度请求，其中，所述第一调度请求是由第一类触发事件触发的；
处理单元，其用于在所述终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
71.根据附记70所述的装置，其中，所述装置还包括：
发送单元，其用于使用第一调度请求配置中的资源发送所述第一调度请求。
72.根据附记70所述的装置，其中，所述取消单元在所述终端设备的高层取消挂起的第一调度请求，在有由对应所述第一调度请求配置的第二类触发事件触发的第四调度请求挂起时，所述处理单元在所述终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
73.根据附记70至72任一项所述的装置，其中，所述高层是MAC层。
74.根据附记70至73任一项所述的装置，其中，所述第一类触发事件是逻辑信道触发或非逻辑信道触发。
75.根据附记72至74任一项所述的装置，其中，所述第二类触发事件是非逻辑信道触发或逻辑信道触发，所述第二类触发事件与所述第一类触发事件不同。
76.根据附记74或75所述的装置，其中，非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
77.根据附记74或75所述的装置，其中，所述逻辑信道触发的调度请求和所述 非逻辑信道触发的调度请求使用相同的调度请求发送次数计数器。
78.一种计数器维护装置，应用于终端设备，所述装置包括：
接收单元，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息以及重置计数器的条件与调度请求触发事件相关或不相关的指示信息；
维护单元，其用于根据所述指示信息维护所述计数器，所述计数器用于记录所述调度请求的发送次数。
79.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记9至39任一项所述的计数器维护方法。
80.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至8任一项所述的调度请求接收方法。
81.一种通信系统，至少包括：附记79所述的终端设备。
82.一种通信系统，至少包括：附记80所述的网络设备。

Claims (20)

  1. 一种调度请求接收装置，其中，应用于网络设备，所述装置包括：
    发送单元，其用于向终端设备发送调度请求相关信息，该调度请求相关信息至少包括资源信息和与调度请求触发事件对应的调度请求计数器的相关信息；
    接收单元，其用于接收所述终端设备在所述资源信息指示的资源上发送的调度请求。
  2. 根据权利要求1所述的装置，其中，所述与调度请求触发事件对应的调度请求计数器的相关信息包括与调度请求触发事件对应的调度请求最大发送次数，和/或重置计数器的条件与调度请求触发事件相关或不相关的指示信息。
  3. 根据权利要求1所述的装置，其中，所述调度请求触发事件包括逻辑信道触发的第一类触发事件以及非逻辑信道触发的第二类触发事件。
  4. 根据权利要求3所述的装置，其中，所述非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
  5. 根据权利要求3所述的装置，其中，与第一类触发事件对应的调度请求最大发送次数和与第二类触发事件对应的调度请求最大发送次数相同或不同。
  6. 根据权利要求4所述的装置，其中，与辅小区BFR触发对应的调度请求最大发送次数和与持续LBT失败触发对应的调度请求最大发送次数相同或不同。
  7. 根据权利要求1所述的装置，其中，所述与调度请求触发事件对应的调度请求计数器的相关信息包括至少一个调度请求最大发送次数的参数，用于与第一类触发事件对应的第一SR计数器的维护和/或与第二类触发事件对应的第二SR计数器的维护。
  8. 一种计数器维护装置，其中，应用于终端设备，所述装置包括：
    接收单元，其用于接收网络设备发送的调度请求相关信息，该调度请求相关信息至少包括资源信息和调度请求计数器的相关信息；
    维护单元，其用于根据所述调度请求计数器的相关信息，维护与第一类触发事件对应的第一SR计数器和/或维护与第二类触发事件对应的第二SR计数器。
  9. 根据权利要求8所述的装置，其中，所述第一类触发事件是逻辑信道触发的所述第二类触发事件是非逻辑信道触发。
  10. 根据权利要求9所述的装置，其中，所述非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
  11. 根据权利要求8所述的装置，其中，所述装置还包括：
    指示单元，其用于从所述终端设备的高层指示低层发送第一调度请求或第二调度请求；所述第一调度请求是由第一类触发事件触发的；所述第二调度请求是由第二类触发事件触发的。
  12. 根据权利要求11所述的装置，其中，所述维护单元用于在所述终端设备的高层将与所述第一类触发事件触发的所述第一调度请求对应的第一调度请求计数器或相应变量加1，或者将与所述第二类触发事件触发的所述第二调度请求对应的第二调度请求计数器或相应变量加1。
  13. 根据权利要求11所述的装置，其中，在所述第一调度请求发送次数计时器小于调度请求最大发送次数时，所述指示单元在高层指示低层发送第一调度请求；
    在所述第二调度请求发送次数计时器小于所述调度请求最大发送次数时，所述指示单元在高层指示低层发送第二调度请求。
  14. 根据权利要求8所述的装置，其中，在第一调度请求计数器或相应变量大于或等于调度请求最大发送次数时，
    所述维护单元在所述终端设备的高层取消所述第一调度请求，或，取消所述第一调度请求和所述第二调度请求，或，在第二调度请求计数器或相应变量为0，或者大于或等于与所述调度请求最大发送次数时，取消所述第一调度请求和所述第二调度请求。
  15. 根据权利要求8所述的装置，其中，在没有由所述第一类触发事件触发的其他第三调度请求挂起时，所述维护单元在所述终端设备的高层将所述第一调度请求计数器或相应变量置为0；和/或，在没有由所述第二类触发事件触发的其他第四调度请求挂起时，所述维护单元在所述终端设备的高层将所述第二调度请求计数器或相应变量置为0。
  16. 根据权利要求8所述的装置，其中，所述维护单元设置第一变量用于记录所述第一调度请求的发送次数，设置第二变量用于记录所述第二调度请求的发送次数。
  17. 根据权利要求11所述的装置，其中，所述高层是MAC层，所述低层是物理层。
  18. 一种计数器维护装置，其中，应用于终端设备，所述装置包括：
    触发单元，其用于在终端设备的高层触发第一调度请求，其中，所述第一调度请求是由第一类触发事件触发的；
    处理单元，其用于在没有由第一类触发事件触发的第三调度请求挂起时，所述终端设备的高层将记录第一调度请求计数器或相应变量置为0；或者，
    取消单元，其用于在终端设备的高层取消挂起的第一调度请求，其中，所述第一调度请求是由第一类触发事件触发的；
    处理单元，其用于在所述终端设备的高层将记录第一调度请求发送次数的计数器或相应变量置为0。
  19. 根据权利要求18所述的装置，其中，所述第一类触发事件是逻辑信道触发或非逻辑信道触发。
  20. 根据权利要求19所述的装置，其中，非逻辑信道触发包括辅小区BFR触发和/或持续LBT失败触发。
PCT/CN2020/091674 2020-05-21 2020-05-21 计数器维护方法，调度请求接收方法以及装置 WO2021232384A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/091674 WO2021232384A1 (zh) 2020-05-21 2020-05-21 计数器维护方法，调度请求接收方法以及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/091674 WO2021232384A1 (zh) 2020-05-21 2020-05-21 计数器维护方法，调度请求接收方法以及装置

Publications (1)

Publication Number Publication Date
WO2021232384A1 true WO2021232384A1 (zh) 2021-11-25

Family

ID=78708960

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/091674 WO2021232384A1 (zh) 2020-05-21 2020-05-21 计数器维护方法，调度请求接收方法以及装置

Country Status (1)

Country Link
WO (1) WO2021232384A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018204770A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Scheduling request in a wireless device and wireless network
WO2019051770A1 (zh) * 2017-09-15 2019-03-21 Oppo广东移动通信有限公司 一种调度请求的配置方法、终端设备及计算机存储介质
CN110167188A (zh) * 2019-05-27 2019-08-23 南京邮电大学 一种未授权频段中的sr自适应配置方法
CN110519794A (zh) * 2018-10-31 2019-11-29 展讯通信（上海）有限公司 上行传输方法、装置、计算机可读存储介质及终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018204770A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Scheduling request in a wireless device and wireless network
WO2019051770A1 (zh) * 2017-09-15 2019-03-21 Oppo广东移动通信有限公司 一种调度请求的配置方法、终端设备及计算机存储介质
CN110519794A (zh) * 2018-10-31 2019-11-29 展讯通信（上海）有限公司 上行传输方法、装置、计算机可读存储介质及终端
CN110167188A (zh) * 2019-05-27 2019-08-23 南京邮电大学 一种未授权频段中的sr自适应配置方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG ELECTRONICS R&D INSTITUTE UK: "Text Proposal for TS 38.321 covering SR operation in NR", 3GPP DRAFT; R2-1710336 TEXT PROPOSAL FOR TS 38.321 COVERING SR OPERATION IN NR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20171009 - 20171013, 8 October 2017 (2017-10-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051342384 *

Similar Documents

Publication Publication Date Title
EP3576452B1 (en) Information transmission method and apparatus for power headroom reporting in a multi-numerology or multi-beam scenario
KR102650985B1 (ko) 빔 표시 방법, 디바이스 및 시스템
US11937324B2 (en) Data transmitting/receiving apparatuses and methods and communication system
US11564255B2 (en) Method and apparatus for processing LBT monitoring failures and system
KR102647538B1 (ko) 무선 통신 방법, 단말기 디바이스 및 네트워크 디바이스
US20200313991A1 (en) Service receiving or transmitting method and device, and communication system
US20230025873A1 (en) Method and apparatus for consistent lbt failure detection and recovery
WO2021087929A1 (zh) 一种随机接入的方法和装置
WO2021092861A1 (zh) 无线通信的方法、终端设备和网络设备
US20220007396A1 (en) Uplink transmission method, uplink scheduling method, apparatuses thereof and system
US20230345331A1 (en) Communication method, apparatus, and system
US20230353223A1 (en) Method and apparatus for detecting beam failure
JP2024503648A (ja) リソース選択方法、装置及びシステム
WO2021056702A1 (zh) 上行信号的发送和接收方法以及装置
WO2021232384A1 (zh) 计数器维护方法，调度请求接收方法以及装置
WO2021159402A1 (zh) Lbt失败的处理方法及装置
KR20230146656A (ko) 사이드링크 불연속 수신 커맨드 트리거 방법, 장치, 및 시스템
WO2020087361A1 (zh) 信号发送方法、天线面板信息的指示方法、装置和系统
WO2021203395A1 (zh) 指示lbt失败的方法及装置
WO2023205975A1 (zh) 辅小区波束失败恢复的方法和装置
WO2021203390A1 (zh) 随机接入方法、资源配置方法以及装置
WO2024031696A1 (zh) 信道状态信息的上报方法和装置
EP4287748A1 (en) Information transmission method and apparatus
WO2021232379A1 (zh) 调度请求的处理方法、装置和系统
WO2021138762A1 (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: 20936447

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20936447

Country of ref document: EP

Kind code of ref document: A1