Transceiver and dispatch equipment

By repeatedly sending scheduling requests on the media access control layer and using multiple opportunities of PUCCH to send scheduling requests, the delay and reliability of signal transmission in non-terrestrial networks is solved, and efficient signal transmission in large-scale user environments is achieved .

CN113330803BActive Publication Date: 2024-11-08PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080010375.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-02-22
Filing Date
2020-01-30
Publication Date
2024-11-08
Estimated Expiration
2040-01-30

AI Technical Summary

Technical Problem

In non-terrestrial networks, due to the large round-trip delay, the retransmission of scheduling requests increases the transmission delay, and the radio resources are tight, so it is difficult for the prior art to effectively improve the reliability of signal transmission and reduce the delay.

Method used

By repeatedly sending scheduling requests on the media access control layer, scheduling requests are sent using multiple opportunities of PUCCH, the overhead of additional resource configuration is avoided, signal reliability is improved and delay is reduced.

Benefits of technology

It realizes the effect of improving signal transmission reliability and reducing delay in non-terrestrial networks, avoiding the overhead of additional resource allocation, and is suitable for non-terrestrial network environments of large-scale users.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113330803B_ABST
    Figure CN113330803B_ABST
Patent Text Reader

Abstract

The present disclosure provides a transceiver device, comprising: a circuit, which repeats a scheduling request on a medium access control (MAC) layer by instructing the transceiver to send the scheduling request on multiple opportunities of a physical uplink control channel (PUCCH); and a transceiver, which sends the scheduling request via the PUCCH.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the transmission and reception of signals in a communication system. In particular, the present disclosure relates to methods and apparatus for such transmission and reception. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is working on technical specifications for the next generation of cellular technology, also known as fifth generation (5G), including the "New Radio" (NR) radio access technology (RAT), which operates in the spectrum range from sub-1 GHz to millimeter wave bands. NR is a follower of technologies represented by Long Term Evolution (LTE) and LTE Advanced (LTE-A).

[0003] For systems such as LTE, LTE-A, and NR, further modifications and selections may facilitate efficient operation of the communication system and specific devices related to the system. Summary of the invention

[0004] One non-limiting and exemplary embodiment facilitates providing reliable and low latency requests for resource allocations.

[0005] In one embodiment, the technical features disclosed herein are characterized by a transceiver device, including: a circuit that repeats a scheduling request on a medium access control MAC layer by instructing the transceiver to send a scheduling request on multiple opportunities of a physical uplink control channel PUCCH; and a transceiver that sends a scheduling request via the PUCCH.

[0006] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0007] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. These benefits and / or advantages can be obtained individually by various embodiments and features of the specification and drawings, and all of these embodiments and features do not need to be provided in order to obtain one or more such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Hereinafter, exemplary embodiments are described in more detail with reference to the accompanying drawings and diagrams.

[0009] Figure 1 An exemplary architecture of a 3GPP NR system is shown, including an exemplary user and control plane architecture of LTE eNB, gNB and UE;

[0010] Figure 2 A non-terrestrial network scenario with a transparent satellite is shown.

[0011] Figure 3A non-terrestrial network scenario with gNB implemented on satellite is shown.

[0012] Figure 4 A scheduling request configuration information element for configuring a scheduling request defined in 3GPP TR 38.321 is shown.

[0013] Figure 5 The sending of scheduling requests configured according to a certain period is shown.

[0014] Figure 6 This is a schematic diagram of repeated transmission of scheduling requests through PUCCH.

[0015] Figure 7 is a block diagram illustrating functional components of a scheduling device and a transceiver device according to an embodiment.

[0016] Figure 8 is a schematic diagram of sending a scheduling request on multiple opportunities triggered on the MAC layer according to an embodiment.

[0017] Fig. 9 The mapping of a single scheduling request configuration per logical channel is schematically shown.

[0018] Fig.10 An example of an NR logical channel configuration element including a specification of the number of scheduling request transmissions allowed is shown.

[0019] Fig.11 The number of SR transmissions configured for the high priority logical channel is shown, while for the low priority logical channel, no SR repetition is configured.

[0020] Fig.12 It is a schematic diagram of sending scheduling requests on multiple opportunities triggered on the MAC layer according to an embodiment, wherein a scheduling request prohibit timer is started after sending the scheduling requests on the multiple opportunities.

[0021] Fig.13 It is a schematic diagram of sending scheduling requests on multiple opportunities triggered on the MAC layer according to an embodiment, wherein a scheduling request prohibit timer is started after the scheduling request is sent multiple times, and a periodicity of time slot n of every second frame is applied.

[0022] Fig.14 is a flow chart illustrating sending a scheduling request over multiple opportunities according to an embodiment.

[0023] Fig.15 A logical channel configuration element indicating a configuration according to an embodiment is shown.

[0024] Fig.16 The mapping of two scheduling request configurations per logical channel is schematically shown.

[0025] Fig.17 An example is shown where a high priority logical channel is mapped to both SR configuration 1 and SR configuration 2, while a low priority logical channel is mapped to SR configuration 2 only.

[0026] Fig.18 It is a schematic diagram of sending scheduling requests on multiple opportunities triggered on the MAC layer according to an embodiment, wherein the sending of scheduling is triggered on the opportunity according to two scheduling request configurations.

[0027] Fig.19 is a flow chart illustrating sending scheduling requests on multiple opportunities according to two scheduling request configurations according to an embodiment.

[0028] Fig. 20 A logical channel mapped to two SR configurations with a configured number of SR repetitions is shown.

[0029] Fig.21 A logical channel configuration element indicating a configuration according to an embodiment is shown.

[0030] Fig. 22 It is a schematic diagram of sending a scheduling request on an opportunity triggered on a MAC layer according to an embodiment, wherein the sending of the scheduling request is triggered on an opportunity according to two scheduling request configurations and a configured SR sending quantity. DETAILED DESCRIPTION

[0031] Figure 1 An exemplary example of a communication system including a base station and a terminal and a core network is shown. Such a communication system may be a 3GPP system, such as NR and / or LTE and / or UMTS. For example, Figure 1 As shown, the base station (BS) can be a gNB (gNodeB, such as an NR base station) or an eNB (eNodeB, such as an LTE base station). However, the present disclosure is not limited to these 3GPP systems or any other system. Even if some terms of the 3GPP system are used to describe the embodiments and exemplary implementations, the present disclosure is also applicable to any other communication system, in particular in any cellular, wireless and / or mobile system.

[0032] NR is planned to help provide a single technology framework to address several use cases, requirements and defined deployment scenarios, including, for example, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type communications (mMTC), etc. For example, eMBB deployment scenarios may include indoor hotspots, dense cities, rural areas, urban streets and highways; URLLC deployment scenarios may include industrial control systems, mobile health (remote monitoring, diagnosis and treatment), vehicle real-time control, smart grid wide-area monitoring systems; mMTC may include scenarios with a large number of devices with non-time-critical data transmission (such as smart wearable devices and sensor networks). The similarity between eMBB and URLLC services is that they both require very wide bandwidth, but the difference is that URLLC services require ultra-low latency. In NR, the physical layer is based on time-frequency resources (such as orthogonal frequency division multiplexing OFDM, similar to LTE) and can support multi-antenna operation.

[0033] The terminal is called user equipment (UE) in LTE and NR. This can be a mobile device such as a wireless phone, a smartphone, a tablet or a USB (Universal Serial Bus) stick with user equipment functionality. However, the term mobile device is not limited to this, and in general, a relay can also have the functionality of such a mobile device, and a mobile device can also work as a relay.

[0034] A base station is a network node, for example, forming part of a network to provide services to a terminal. A base station is a network node that provides wireless access to a terminal. The communication between a terminal and a base station is generally standardized. In LTE and NR, the radio interface protocol stack includes a physical layer, a media access layer (MAC), and higher layers. In the control plane, a higher layer radio resource control protocol is provided. Via RRC, the base station can control the configuration of the terminal, and the terminal can communicate with the base station to perform control tasks such as connection and bearer establishment, modification, measurements, and other functions.

[0035] A service that delivers data provided by a layer to a higher layer is generally referred to as a channel. For example, LTE and NR distinguish between logical channels provided by the MAC layer to a higher layer, transport channels provided by the physical layer to the MAC layer, and physical channels that define mapping on physical resources.

[0036] Logical channels are different types of data transfer services provided by MAC. Each logical channel type is defined by the type of information transferred. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only to transfer control plane information. Traffic channels are used only to transfer user plane information.

[0037] The MAC layer then maps the logical channels to transport channels. For example, the logical traffic channel and some logical control channels can be mapped to a transport channel called the downlink shared channel DL-SCH in the downlink and a transport channel called the uplink shared channel UL-SCH in the uplink.

[0038] Non-terrestrial networks

[0039] In 3GPP, NR-based operations in non-terrestrial networks (NTN) are studied and described (e.g., see 3GPP TR 38.811, New Radio (NR) Studies to Support Non-Terrestrial Networks, Release 15.0.0, and 3GPP TR 38.821, NR Solutions to Support Non-Terrestrial Networks, Release 0.3.0).

[0040] Due to the wide service coverage capability and reduced vulnerability of space / airborne vehicles to physical attacks and natural disasters, NTN can facilitate the operation of NR services in unserved areas that are not covered by terrestrial NR networks (e.g., isolated or remote areas, on aircraft or ships) and unserved areas (e.g., suburban and rural areas). In addition, NTN can enhance the reliability of NR services by providing service continuity for passengers on mobile platforms or ensuring service availability (especially critical communications) anywhere.

[0041] These benefits involve either separately operated non-terrestrial networks or integrated terrestrial and non-terrestrial networks, which may affect coverage, user bandwidth, system capacity, service reliability or availability.

[0042] For example, a non-terrestrial network refers to a network or network segment that uses RF resources on a satellite. NTN is usually characterized by the following system elements: NTN terminals, which can refer to 3GPP UEs or terminals specific to satellite systems in the case where the satellite does not directly serve 3GPP UEs; service links, which refer to the radio links between user equipment and space / airborne platforms; airborne platforms that carry payloads; gateways that connect space / airborne platforms to the core network; feeder links, which refer to the radio links between gateway-centric space / airborne platforms.

[0043] Figure 2 A scenario of a non-terrestrial network is shown, where transmissions between terminals (UEs) are performed via remote radio units comprising geostationary satellites and NTN gateways. The gNB is located at the gateway as a scheduling device. The satellite payload implements frequency conversion and RF amplifiers in both uplink and downlink directions. Thus, the satellite repeats the NR radio interface from the feeder link (between the NTN gateway and the satellite) to the serving link (between the satellite and the UE) and vice versa.

[0044] Figure 3A scenario of a non-terrestrial network is shown, where transmissions between terminals (UEs) are performed via geostationary satellites including gNBs as scheduling devices.

[0045] Non-terrestrial networks and round-trip delays

[0046] Every electromagnetic wave-based signal transmission is subject to signal transmission delay due to the speed of light. Specifically, twice the one-way propagation delay of a radio signal between a source and a destination is called the round-trip delay (RTD). The processing time used to generate a response signal at a processing node can also be included in the RTD.

[0047] Specifically, the round trip delay depends on the distance between the source node (e.g., terminal (UE)) and the destination node. In NTNs that transmit signals via satellites, etc., the value of RTD may be much larger than in terrestrial networks. For example, in the case of transmitting signals via satellites in geosynchronous orbit (i.e., at an altitude of about 35786km), in the case where the scheduling equipment (e.g., gNB in ​​NR) is located at the gateway, the RTD can be as large as 541.14ms, as shown in Figure 2. Figure 2 shown.

[0048] Figure 2 The scenario shown is associated with a round-trip latency of 541.14ms, Figure 3 The scenario shown is associated with a round trip latency of 271.57ms. Table 1 summarizes the Figure 2 and 3 Round trip delay values ​​for the scenario shown in .

[0049]

[0050] Table 1

[0051] Scheduling

[0052] In 3GPP, scheduling in NR based operation is described (see, e.g., 3GPP TR 38.321, NR; Medium Access Control (MAC) Protocol Specification, Version 15.4.0).

[0053] Scheduling is a central part of communication systems such as NR and / or LTE. For each time instance, the scheduler determines to which UE the shared time-frequency resources should be assigned. Uplink, downlink and / or sidelink transmissions can be scheduled.

[0054] Specifically, the uplink scheduler may be responsible for dynamically controlling which terminals will transmit on their uplink shared channel (UL-SCH).Each scheduled terminal is provided with a scheduling grant that includes a set of resources on which the terminal should transmit its UL-SCH.

[0055] In other words, the function of uplink scheduling is to dynamically determine which devices to send and on which uplink resources. Dynamic scheduling is usually performed through the physical downlink control channel (PDCCH). The physical downlink control channel carries scheduling authorization and other control information, which can also be called downlink control information DCI. Each terminal (UE) monitors the PDCCH. This means that the UE (blind) decodes specific resources called search spaces. The PDCCH search space is an area in the downlink resource grid that can carry the PDCCH. The UE performs blind decoding in these search spaces, trying to find PDCCH data (DCI). In order to decode the PDCCH, the UE applies its own RNTI (radio network temporary identifier) ​​and attempts to decode the PDCCH in a resource called a control channel element CCE. If the decoding is successful (which can be checked by an error detection code such as a cyclic redundancy check), the DCI is received. The UE can also blindly try various parameter values ​​for some selected transmission parameters. Each terminal can monitor more than one PDCCH. The PDCCH can be shared by a group of UEs (in this case, the UE uses a common group RNTI) or dedicated to a specific UE.

[0056] The standard (LTE or NR) defines several different DCI formats. These formats differ from each other by their usage. For example, the format used to carry uplink grants (such as format 0 or 4) is different from the format that carries downlink grants or no grants at all. In addition, there are different formats defined depending on the utilization of beamforming, broadcast / multicast, etc.

[0057] Correspondingly, in the uplink, the control information on the physical layer is carried by the physical uplink control channel. PUCCH carries a set of parameters called UCI (uplink control information). This is similar to the PDCCH that carries the above-mentioned DCI. Depending on the type of information carried by the UCI in the PUCCH, the PUCCH also has different formats. For example:

[0058] -Format 1 carries a scheduling request SR,

[0059] -Format 4 carries SR and channel state information (CSI),

[0060] - Format 3 carries SR with HARQ acknowledgment (positive or negative) and CSI,

[0061] There are other formats defined by LTE and / or NR.

[0062] The basis of uplink scheduling is the scheduling grant, which contains device information about the resources used for the transmission of UL-SCH and the associated transmission format. In other words, a DCI with a specific format (e.g., defined in the standard) can carry a resource allocation (RA) corresponding to the resource grant and some other transmission parameters, such as the modulation and coding scheme (MCS), the configuration for multiple-input multiple-output (MIMO) transmission, etc.

[0063] If the terminal has a valid grant, it is allowed to map its corresponding UL-SCH to the Physical Uplink Shared Channel (PUSCH) specified by the resource assignment.

[0064] That is, the scheduler needs knowledge that a terminal has data to send and therefore needs to be scheduled with uplink resources. It is not necessary to provide uplink resources to a device that has no data to send, as this will cause the device to perform padding to fill the granted resources. Therefore, the scheduler needs to know whether a device has data to send and should give a grant.

[0065] Scheduling Request

[0066] Scheduling requests may be used for terminals that do not have a valid scheduling grant. Scheduling requests may be sent on the Physical Uplink Control Channel (PUCCH). Each terminal may be assigned a dedicated scheduling request resource, present once every n subframes. A scheduling request may be a simple flag, initiated (set) by a terminal to request uplink resources from the uplink scheduler. With a dedicated scheduling request mechanism, the identity of the requesting terminal does not have to be provided with the scheduling request, as the identity of the terminal is implicitly known from the resource on which the request is sent. These are configured by a scheduling node (such as a gNB), for example by a higher layer control protocol.

[0067] When a scheduling request is received, the scheduling device may assign a scheduling grant to the terminal. If the terminal receives a scheduling grant, it sends its data in the scheduled resources. The data to be sent on the PUSCH may include a first buffer status, which informs the scheduling node of the amount of data that the UE has to send. Based on the buffer status, the scheduling node can then schedule the actual data resources on the PUSCH. However, this is only an option, and in general, the data resources can also be scheduled directly. In some systems, the scheduling request can also be associated with a specific amount of data requested to be scheduled.

[0068] If the terminal does not receive the scheduling grant until the next possible time, the scheduling request may be repeated.

[0069] Therefore, a contention-free scheduling request mechanism on the PUCCH is provided, where each terminal in the cell is given reserved resources on which the terminal can send requests for uplink resources.

[0070] The UE MAC entity can be configured with zero, one or more SR configurations. An SR configuration consists of a set of PUCCH resources for scheduling requests across different bandwidth parts (BWPs). For a logical channel (LCH), at most one PUCCH resource is configured for SR per BWP. Each SR configuration corresponds to one or more logical channels. The mapping between logical channels and SR configurations can be configured via Radio Resource Control (RRC) messaging.

[0071] As mentioned above, when a regular buffer status report (BSR) is triggered but the uplink radio resources for sending the BSR are not available in the UE, the SR procedure can be started. During the SR procedure, the UE can perform the transmission of the SR via the PUCCH or initiate a random access (RA) procedure, depending on whether the UE is configured with PUCCH resources for SR. The RA procedure is initiated only when the PUCCH resources for SR are not configured.

[0072] When the UE MAC entity has an SR transmission position on a valid PUCCH resource configured for SR, it instructs the physical layer (PHY) to signal SR on a valid PUCCH resource of SR. Subsequently, the SR prohibition timer (SR_prohibitTimer) starts. At the time of continuous SR transmission, if the SR prohibition timer is running, the MAC does not instruct the PHY to signal SR.

[0073] In NR, SR resources are configured with a certain periodicity. Once an SR is sent by the UE, the SR prohibit timer is started, and as long as the SR prohibit timer is running, no SR is sent on the configured resources.

[0074] As follows and Figure 4 , a scheduling request configuration information element for configuring a scheduling request is shown, as defined in 3GPP TS 38.331 (“NR; Radio Resource Control (RRC); Protocol specification”, Version 15.4.0, Section 6.3.2).

[0075] SchedulingRequestConfig Information Element

[0076]

[0077] Specifically, even if no scheduling grant is received, the scheduling request prohibit timer is configured by sr-ProhibitTimer and indicates the duration for which no scheduling request is sent after sending an SR. The maximum number of scheduling requests is defined by sr-TransMax. sr-ProhibitTimer and sr-TransMax are provided to the UE from the scheduling node via RRC signaling, for example.

[0078] Figure 5 The transmission of a scheduling request with a specific periodicity configuration is shown. In this example, the opportunity to send an SR is configured in each time slot n of the subsequent frame, and each frame includes time slots n to n+9. Once the UE indicates SR transmission on the MAC layer, the SR prohibit timer is started, such as Figure 5 As shown by the bold arrow in . When the SR prohibit timer is running, the UE MAC does not trigger SR transmission in the opportunity after the opportunity for SR transmission. Figure 5 In , the periodicity of the SR transmission opportunity is every time slot n of consecutive frames, but the SR configuration periodicity is not limited to this, and any other periodicity can be configured.

[0079] Scheduling Requests and Round Trip Latency

[0080] As described above, in NTN, the round trip delay is large, so that when the SR prohibit timer expires, the terminal may not receive the scheduling grant sent by the scheduling device (e.g., gNB in ​​NR) in response to the reception of the SR. That is, the configuration of the SR prohibit timer should take into account the round trip delay.

[0081] However, when the SR prohibit timer is extended to take into account a large round trip delay and the transmitted SR is lost, retransmission of the SR is performed by the UE after the SR prohibit timer expires. As a result, the UE may take a long time to obtain uplink resources, making the transmission delay in the NTN larger.

[0082] Furthermore, as in NTN, the cell size may be large, with a single cell serving a large number of users. Therefore, the radio resources used for transmission on NTN are tight. That is, compared to transmission through, for example, a terrestrial network, limited radio resources are used by a large number of devices.

[0083] Considering the enlarged round trip delay in NTN compared to terrestrial networks, additional resources can be allocated for full PUCCH retransmissions on the physical layer by increasing the SR prohibit timer and simultaneously repeatedly sending scheduling requests to provide low transmission latency. Figure 5 Shown in.

[0084] Figure 6Schematic diagram of repeatedly sending scheduling requests through PUCCH repetition. Specifically, resources can be reserved for repetition of the entire PUCCH on the physical layer. In addition to SR, PUCCH can also contain other information such as hybrid automatic repeat request, HARQ and / or channel state information CSI. That is, when repetition is performed through repetition of the entire PUCCH on the physical layer, additional resources are required, resulting in significantly higher overhead. Since the size of NTN cells is usually large and a large number of UEs need to be served, a large amount of resources must be reserved in order to provide repeated SR transmissions.

[0085] The technology provided by the present disclosure can help improve reliability by repeatedly sending SR without configuring additional resources for repetition. In addition, the present disclosure provides a technology that does not require additional overhead.

[0086] To this end, in the embodiments of the communication method and the communication device described below, the transceiver device repeats the scheduling request on the medium access control (MAC) layer by indicating that the scheduling grant is sent on multiple opportunities of the PUCCH. The scheduling request is sent by the receiver through the PUCCH.

[0087] The present disclosure provides Figure 7 The transceiver device and scheduling device shown. The transceiver device 110 includes a circuit 120 (or a processing circuit) that repeats the scheduling request on the medium access control MAC layer by instructing the transceiver to send the scheduling request on multiple opportunities of the physical uplink control channel PUCCH. In addition, the transceiver device 110 includes a transceiver 130 (a transmitter and / or receiver including (multiple) hardware components such as one or more antennas and a control circuit that controls the operation of the hardware components) that sends the scheduling request via the PUCCH.

[0088] For example, the transceiver device 110 is a UE in an NR NTN. Therefore, the transceiver 130 and the circuit 120 are also retained as the "UE transceiver" and "UE circuit" of the present disclosure. However, these terms are only used to distinguish the circuit 120 and the transceiver 130 from the circuits and transceivers included by other devices such as a scheduling device or a base station. The transceiver device 110 may be a terminal device, a relay device, or a communication device of a similar communication system. The UE circuit may be considered or include a "scheduling request repetition circuit".

[0089] Further Offer Figure 7 The illustrated scheduling device 210 (or scheduling node) comprises a circuit 230 for determining a grant request indicator indicating a permitted number of scheduling requests, and a transceiver 220 for transmitting the grant request indicator.

[0090] Alternatively, the scheduling device 210 (or scheduling node) may include a circuit 230 for determining a scheduling request configuration indicator indicating a plurality of scheduling request configurations, and a transceiver 220 for transmitting the scheduling request configuration indicator.

[0091] For example, the scheduling device is a network node (base station) in an NR NTN system (gNB) or a similar wireless communication system. Circuit 220 is also referred to as a "grant request determination circuit" or a "scheduling request configuration determination circuit" to distinguish it from other circuits such as UE circuit 120, "network node circuit".

[0092] A method is also provided, comprising repeating the scheduling request on a medium access control MAC layer by indicating that the scheduling request is sent on multiple opportunities of a physical uplink control channel PUCCH, and sending the scheduling request through the PUCCH.

[0093] A method is also provided that includes determining a grant request indicator indicating an allowed number of scheduling requests; and sending the grant request indicator.

[0094] A method is also provided, comprising determining a scheduling request configuration indicator indicating a plurality of scheduling request configurations; and sending the scheduling request configuration indicator.

[0095] In the further description, unless explicitly stated or the context indicates otherwise, the details and embodiments apply to each of the transceiver device 110, the scheduling node (or scheduling device) 210, and the method.

[0096] The UE circuit 120 of the transceiver device repeats the transmission of the scheduling request on the MAC layer. This is performed by instructing the transceiver 130 to transmit the scheduling request on multiple opportunities of the PUCCH configured to transmit the SR. In this way, the repeated SR transmission is performed by the transceiver device so that the reliability is increased by the repetition, while no additional resources need to be configured for the repetition. Therefore, no additional overhead is generated regarding the repetition of the entire PUCCH.

[0097] In other words, the MAC layer entity triggers the sending of a scheduling request on resources configured for sending scheduling. That is, the physical layer (PHY) is instructed to send a scheduling request on an opportunity for SR sending. The MAC layer entity repeatedly instructs the PHY to send a scheduling request on resources configured for SR sending, for example, through RRC message transmission. In other words, the MAC layer provides the physical layer with repeated instructions for sending SR, for example, through internal signaling of the UE.

[0098] A special benefit of MAC layer SR repetition is that it can be repeated on a per-logical channel basis, so only one of the multiple logical channels requires SR repetition. The MAC can trigger only one repetition instead of all repetitions. However, in PHY layer PUCCH repetition, it is not possible to trigger repetition for some logical channels, but for all logical channels.

[0099] For example, in NR, the UE may be configured by higher layer parameters with a set of configurations for SR in PUCCH transmissions using PUCCH format 0 or PUCCH format 1.

[0100] Furthermore, for PUCCH formats 1, 3 or 4, the UE may be configured with multiple slots for repeated PUCCH transmissions.

[0101] Furthermore, 3GPP TS 38.331 ("NR; Radio Resource Control (RRC); Protocol specification", Version 15.4.0) Section 6.3.2 describes the identifier of the PUCCH resource and the parameters related to the PUCCH format and the number of SR transmission slots. If PUCCH format 1 is configured for SR and the number of slots is set to a number greater than 1, the UE performs SR repetition based on a single SR configuration.

[0102] In some embodiments, the scheduling device 210 determines an allowed request indicator indicating an allowed number of scheduling requests. That is, the scheduling device 210 indicates the maximum number of repeated transmissions of the scheduling request to the transceiver device, and the transceiver device 110 or specifically, the circuit 120 repeatedly instructs the transceiver 130 to send the scheduling request at the opportunity configured as the SR transmission, wherein the scheduling request is sent according to the maximum number of repeated transmissions indicated by the scheduling device 210. In other words, the transmission of the scheduling request is triggered by the UE MAC entity until the number of SRs transmitted is equal to the configured maximum (allowed) number of SR transmissions.

[0103] The number of scheduling requests sent is not limited to being determined according to the allowed number of scheduling requests received from the scheduling device 210, but may be a decision of the transceiver.

[0104] In some embodiments, the scheduling device 210 determines a scheduling request configuration indicator, which indicates multiple scheduling request configurations for each logical channel. That is, the logical channel can be mapped to multiple SR configurations. The transceiver device 11, or specifically, the circuit 120, instructs the transceiver 130 to send a scheduling request according to the multiple SR configurations.

[0105] Figure 81 is a schematic diagram of repeatedly sending a scheduling request on multiple opportunities triggered by the UE circuit 120 on the MAC layer according to an embodiment. As shown in the figure, in this example, the UE MAC layer triggers the SR transmission three times with a configured periodicity. Specifically, the SR is sent via the PUCCH on multiple opportunities. As described above, these opportunities are resources configured for SR transmission, and the transceiver device 110 can send a resource request on it when the transceiver device 110 has data to send but is not assigned resources for uplink transmission via the UL-SCH.

[0106] Repetition of a single SR configuration per LCH

[0107] In some embodiments, the scheduling device 210 may configure N SR repetitions per logical channel, where each logical channel is mapped to one SR configuration, such as Fig. 9 shown.

[0108] The allowed number of scheduling requests can be configured in the NR logical channel configuration element as follows and Fig.10 shown.

[0109] LogicalChannelConfig Information Element

[0110]

[0111] Specifically, the number of repetitions of the scheduling request can be configured via additional parameters. Fig.10 In the examples shown above, the additional parameter is indicated as "number of SR repetitions".

[0112] Each logical channel may allow repetitions of SR transmission, where the number of SR repetitions is configured by the scheduling device (e.g., gNB) via an RRC message (e.g., see 3GPP 38.331, version 15.4.0). For example, the number of SR repetitions may be configured differently based on the priority of the logical channel. For example, a high priority logical channel may be configured to allow more SR repetitions than a low priority logical channel.

[0113] like Fig.11 As shown in , the SR transmission quantity can be configured for a high priority logical channel (e.g., high priority eMBB traffic), while for a low priority channel (low priority eMBB traffic), SR repetition may not be configured. Therefore, the value of SR repetition may be different depending on the priority of the logical channel.

[0114] Additionally or alternatively, the allowed number of repetitions may be configured based on uplink channel quality. For example, a sounding reference signal (SRS) may be utilized to assess uplink channel quality. The sounding reference signal is sent by the terminal to the scheduling device to enable the scheduling device to perform channel sounding, e.g., to support frequency domain scheduling (e.g., see 3GPP TS 36.211, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation", Version 15.4.0, Section 5.5.3).

[0115] Fig.12 It is a schematic diagram of sending a scheduling request on multiple opportunities triggered on the MAC layer according to an embodiment, wherein a scheduling request prohibit timer is started after sending the scheduling request multiple times.

[0116] Specifically, the scheduling device may configure N allowed scheduling request transmissions for each logical channel. The transmission of the scheduling request is triggered by the UE MAC layer entity in each time slot n of three consecutive frames n to n+2. After the third scheduling request is sent, the SR prohibit timer starts, and as long as the SR prohibit timer has not expired, SR transmission will not be triggered on the opportunity configured for SR transmission. Fig.12 In the example shown, the UE MAC layer entity triggers three transmissions of SR. However, the present disclosure is not limited to three transmissions, but any number configured by the scheduling device can be used as the maximum number of SR transmission repetitions. In this case, the SR prohibition timer starts after the last SR is sent.

[0117] Additionally or alternatively, the UE may send scheduling requests using a different periodicity. Fig.13 It is a schematic diagram of sending a scheduling request on multiple opportunities triggered on the MAC layer according to an embodiment, wherein a scheduling request prohibit timer is started after the scheduling request is sent multiple times, and a periodicity of time slot n of every second frame is applied.

[0118] Specifically, the scheduling device may configure N allowed scheduling requests for each logical channel. Fig.13 In the example shown, N is equal to 2, and the sending of the scheduling request is triggered by the UE MAC layer entity in each time slot n of two frames n and n + 2. After sending the second scheduling request, the SR prohibit timer is started, and as long as the SR prohibit timer has not expired, SR transmission will not be triggered on the opportunities configured for SR transmission.

[0119] In the case where the UE receives an uplink grant from the scheduling device, the SR prohibit timer is terminated. In addition, when the SR prohibit timer expires and no uplink grant is received from the scheduling device, the process of sending the scheduling request can be restarted. That is, the UE MAC layer entity triggers the sending of SR on multiple opportunities of PUCCH again.

[0120] A particular benefit of this approach is improved reliability and reduced latency for uplink data transmission. Specifically, if the scheduling device (e.g., gNB) does not receive the first SR transmission from the UE, the scheduling device may receive the second or third SR transmission and may send a resource grant to the transceiver device even if the SR prohibit timer has not expired.

[0121] Fig.14 is a flow chart showing sending a scheduling request on multiple opportunities according to an embodiment. In step S100, the UE MAC layer entity is configured to perform N SR repetitions. This can be performed by receiving an RRC configuration indicating a repetition pattern of resources configured as opportunities for sending scheduling requests. In step S110, it is determined whether the number of scheduling requests sent so far is lower than the configured number N of SR transmission repetitions. In the case where the SR transmission number is equal to or greater than the configured SR transmission repetition number N (step S110 is no), the SR prohibit timer is started in step S140. In the case where it is determined that the SR transmission repetition number is lower than the configured SR transmission repetition number N, the UE MAC layer entity instructs the physical layer (transceiver) to signal the SR on the configured opportunity of the PUCCH. In addition, in step S130, the SR transmission repetition number is increased by 1, and the process returns to step S110. Specifically, the UE can use a counter (e.g., SR_COUNTER of the logical channel configuration in NR) to track the number of scheduling requests sent without receiving a scheduling grant.

[0122] Repetition of multiple SR configurations per LCH

[0123] In some embodiments, the scheduling device 210 may configure multiple SR configurations for each logical channel, wherein each logical channel is mapped to multiple SR configurations. Fig.16 As shown, the LCH is mapped to two SR configurations denoted as configuration 1 and 2. In other words, multiple opportunities for SR transmission are provided via multiple SR configurations per logical channel, and SR repetition is based on different SR configurations.

[0124] Despite Fig.16 , the LCH is mapped to two SR configurations, but the present disclosure is not limited thereto, and the LCH may be mapped to more than two SR configurations.

[0125] As follows and Fig.15 As shown, the logical channel configuration information element defines the configuration of logical channels in NR, where LCH is mapped to two scheduling request configurations via the second scheduling request ID "schedulingRequestID2".

[0126] LogicalChannelConfig Information Element

[0127]

[0128] The scheduling device can determine whether to configure multiple SR configurations for the LCH based on the priority of the LCH. For example, a higher priority LCH can be mapped to more than one SR configuration. This method improves the reliability and latency of the scheduling request process for high priority logical channels.

[0129] Fig.17 An example is shown where a high priority logical channel (e.g., high priority eMBB traffic) is mapped to SR configuration 1 and SR configuration 2 for repeated SR transmission, while a low priority logical channel (e.g., low priority eMBB traffic) is mapped only to SR configuration 2.

[0130] Fig.18 It is a schematic diagram of sending a scheduling request on multiple opportunities triggered on a UE MAC layer according to an embodiment, wherein the sending of scheduling is triggered on multiple opportunities according to two scheduling request configurations.

[0131] Specifically, in time slot n, according to a first SR configuration with an associated first periodicity, a first sending of a scheduling request is triggered on the UE MAC layer. After the first SR is sent, a first SR prohibit timer is started, and as long as the first SR prohibit timer has not expired, the UE MAC layer does not trigger SR sending according to the first SR configuration. In addition, in time slot n+1, according to a second SR configuration with an associated second periodicity, a second sending of a scheduling request is triggered on the UE MAC layer. After the second SR is sent, a second SR prohibit timer is started, and as long as the second SR prohibit timer has not expired, the UE MAC layer entity does not trigger SR sending according to the second SR configuration.

[0132] exist Fig.18 In the example shown, two SR transmissions are triggered on the UE MAC layer according to two SR transmission configurations. However, the present disclosure is not limited to two transmissions, but any number of SR transmission configurations may be configured by the scheduling device. In this case, after the transmission of the SR is triggered according to the respective SR configurations, an SR prohibit timer may be started for each SR transmission.

[0133] In the case where the UE receives an uplink grant from the scheduling device, the SR prohibit timer is stopped / terminated. In addition, when one of the SR prohibit timers has expired and no uplink grant is received from the scheduling device, the repeated transmission of the SR is restarted according to the corresponding SR configuration. That is, the UE MAC layer is again instructed to send the SR on each opportunity of the PUCCH.

[0134] A particular benefit of this approach is improved reliability and reduced latency for uplink data transmission. Specifically, if the scheduling device (e.g., gNB) does not receive the first SR transmission from the UE, the scheduling device may receive the second SR transmission and may send a resource grant to the transceiver device even if the SR prohibit timer has not expired.

[0135] Furthermore, if one configuration between the transceiver device (e.g., UE) and the scheduling device (e.g., gNB) is misaligned, a second SR configuration may still be used.

[0136] Another benefit is latency. In the case of a single SR configuration, for example, with SR periodicity after every k slots, repetition will be performed at the earliest after every k slots. In the case of multiple SR configurations, the SR resources of the multiple configurations are independent. If configuration 1 is configured on slot k, and configuration 2 is configured on slot k+1, the first SR transmission can be performed on slot k, and SR repetition can be performed according to configuration 2 on slot k+1. Therefore, the overall latency can be further reduced.

[0137] Additionally or alternatively, additional SR configurations and / or additional resources for SR transmission may not have to be configured, however, for example, a high priority logical channel may duplicate the SR configuration / resources of a lower priority logical channel.

[0138] Fig.19 is a flow chart showing the repetition of the sending of a scheduling request on the MAC layer by instructing a transceiver to send a scheduling request on multiple opportunities according to an embodiment. The UE MAC layer entity may be configured to perform SR repetition according to two SR configurations, for example, via an RRC message. In step S200, a first SR sending according to a first SR configuration is triggered on the UE MAC layer. In addition, in step S210, a first SR prohibit timer is started. Next, in step S220, the MAC layer triggers a second SR sending according to a second SR configuration. Subsequently, in step S230, a second SR prohibit timer is started. As long as the SR prohibit timer has not expired, the UE MAC layer entity will not trigger SR sending according to the corresponding SR configuration. When the SR prohibit timer has expired and no uplink grant is received from the scheduling device, the UE MAC layer triggers SR sending again according to the corresponding SR configuration.

[0139] Based on the repetition of multiple SR configurations per LCH, the delay prohibit timer starts

[0140] In some embodiments, the scheduling device 210 may configure an allowed (maximum) number N of SR transmissions per logical channel, where each logical channel is mapped to multiple SR configurations.

[0141] For example, Fig. 20 As shown, the LCH is mapped to two SR configurations denoted as configuration 1 and 2. In other words, multiple opportunities for SR transmission are provided via multiple SR configurations per logical channel, and SR repetition is based on different SR configurations and the number N of SR transmissions.

[0142] The following and Fig.21 0 shows a logical channel configuration element indicating the configuration of LCH according to an embodiment.

[0143] LogicalChannelConfig Information Element

[0144]

[0145] As indicated, the logical channel configuration may include multiple scheduling request configurations ("schedulingRequestID1", "schedulingRequestID2") and an allowed number of scheduling requests ("number of SR repetitions"). The allowed number of SR repetitions per LCH and the mapping to more than one SR configuration may be configured in RRC by the scheduling device (e.g., gNB).

[0146] Fig. 22 1 is a schematic diagram of sending a scheduling request on multiple opportunities triggered on the UE MAC layer according to an embodiment, wherein the sending of the scheduling request is indicated on multiple opportunities according to two scheduling request configurations and the configured number of SR transmissions. The total number of SR transmissions can be configured by the scheduling device via an RRC message.

[0147] Specifically, a first sending of a scheduling request is triggered on the UE MAC layer according to a first SR configuration with an associated first periodicity in time slot n. In addition, a second sending of a scheduling request is triggered on the UE MAC layer according to a second SR configuration with an associated second periodicity in time slot n+1. In addition, a third sending of a scheduling request is triggered on the UE MAC layer according to the first SR configuration. In addition, a fourth sending of a scheduling request is triggered on the UE MAC layer entity according to the second SR configuration.

[0148] exist Fig. 22In the example shown, the allowed number of SR transmissions (repetitions) is 4, and the number of SR configurations per LCH is 2.

[0149] After multiple SR transmissions are performed on multiple opportunities according to the two SR configurations, the first and second SR prohibit timers are started (turned on). That is, after all four SR transmissions are sent, the two SR prohibit timers are turned on together. As long as the SR prohibit timer has not expired, SR transmission according to each SR transmission configuration is not indicated on the UE MAC layer.

[0150] Alternatively, the SR prohibit timer may run on each logical channel.Once all SR repetitions have been sent, the UE may start the SR prohibit timer.

[0151] exist Fig.14 In the example shown, the number N of SR transmissions configured by the scheduling device is 4. However, the present embodiment is not limited to four, and the scheduling device may configure any number of SR transmissions.

[0152] The present disclosure can be implemented by software, hardware or software in collaboration with hardware. Each functional block used in the description of each of the above embodiments can be implemented in part or in whole by LSI (large scale integration) such as integrated circuit (IC), and each process described in each embodiment can be controlled in part or in whole by the same LSI or a combination of LSI. LSI can be formed as a chip alone, or a chip can be formed to include some or all functional blocks. LSI can include data input and output coupled thereto. Depending on the degree of integration, the LSI here can be referred to as IC, system LSI, super LSI or ultra LSI. However, the technology for implementing integrated circuits is not limited to LSI, and can be implemented by using a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (field programmable gate array) or a reconfigurable processor that can be programmed after LSI manufacturing can be used, wherein the connection and setting of the circuit unit arranged inside the LSI can be reconfigured. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces large-scale integrated circuits due to the advancement of semiconductor technology or other derivative technologies, these functional blocks can be integrated using future integrated circuit technology. Biotechnology can also be applied.

[0153] The present disclosure may be implemented by any kind of device, apparatus, or system having a communication function, which is referred to as a communication device.

[0154] Some non-limiting examples of such communication devices include phones (e.g., cellular (cell) phones, smart phones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medical) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0155] Communication devices are not limited to portable or transportable, and may also include any type of device, apparatus, or system that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other “things” in a network of the “Internet of Things (IoT)”.

[0156] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

[0157] The communication device may include a device such as a controller or a sensor that is coupled to the communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or a sensor that generates a control signal or a data signal used by the communication device that performs the communication functions of the communication device.

[0158] Communications equipment may also include infrastructure such as base stations, access points, and any other device, apparatus, or system that communicates with or controls devices such as those in the above non-limiting examples.

[0159] As described above, apparatus and methods are provided for achieving robust transmission of scheduling requests in non-terrestrial networks (or similar wireless communication systems) without incurring significantly higher overhead.

[0160] A transceiver device is provided, comprising: a circuit that repeats a scheduling request on a medium access control (MAC) layer by instructing the transceiver to send the scheduling request on multiple opportunities of a physical uplink control channel (PUCCH); and a transceiver that sends the scheduling request via the PUCCH.

[0161] In some embodiments, the circuit starts a scheduling request prohibit timer and does not instruct the transceiver to send a scheduling request if the scheduling request prohibit timer is running.

[0162] In some embodiments, the transceiver receives a grant request indicator indicating an allowed number of scheduling requests; and the circuit starts a scheduling request prohibit timer after scheduling requests have been sent on a number of opportunities equal to the allowed number of scheduling requests indicated by the grant request indicator.

[0163] In some embodiments, the grant request indicator indicates a allowed number of scheduling requests per logical channel.

[0164] In some embodiments, the transceiver receives a resource allocation indicator via a physical downlink control channel (PDCCH) indicating resources allocated to the transceiver device for transmission; the circuit determines the allocated resources based on the resource allocation indicator and stops the scheduling request prohibit timer.

[0165] In some embodiments, the transceiver receives a scheduling request configuration indicator indicating a plurality of scheduling request configurations, and the circuitry instructs the transceiver to send scheduling requests on a plurality of opportunities according to the plurality of scheduling request configurations.

[0166] In some embodiments, the circuitry initiates a plurality of scheduling request inhibit timers, each scheduling request inhibit timer being associated with one of the plurality of scheduling request configurations, and does not instruct the transceiver to opportunistically send a scheduling request according to one of the plurality of scheduling request configurations if the scheduling request inhibit timer associated with one of the plurality of scheduling request configurations is running.

[0167] In some embodiments, the circuitry starts each scheduling request inhibit timer when a scheduling request according to one of a plurality of scheduling request configurations associated with the scheduling request inhibit timer is sent.

[0168] In some embodiments, the transceiver receives a grant request indicator indicating an allowed number of scheduling requests for each logical channel; and the circuit starts each scheduling request prohibit timer after the scheduling request has been sent on multiple opportunities according to the allowed number of scheduling requests indicated by the grant request indicator.

[0169] In some embodiments, the transceiver receives a resource allocation indicator via a physical downlink control channel (PDCCH) indicating resources allocated to the transceiver device for transmission; the circuit determines the allocated resources based on the resource allocation indicator and stops a plurality of scheduling request prohibit timers.

[0170] A scheduling device is also provided, comprising: a circuit to determine a grant request indicator indicating an allowed number of scheduling requests; and a transceiver to transmit the grant request indicator.

[0171] In some embodiments, an allowed number of scheduling requests is determined per logical channel.

[0172] In some embodiments, the allowed number of scheduling requests for each logical channel may be determined according to the priority of the logical channel.

[0173] For example, it may be determined that the allowed number of scheduling requests for high priority logical channels is greater than the allowed number of scheduling requests for low priority logical channels. In other words, the number of scheduling requests allowed for each logical channel may be determined according to the priority of the logical channel.

[0174] In some embodiments, the grant request indicator indicates a allowed number of scheduling requests per logical channel.

[0175] In some embodiments, the transceiver receives a scheduling request on an opportunity of a physical uplink control channel, PUCCH, and sends a resource allocation indicator via a physical downlink control channel, PDCCH, indicating resources allocated to the transceiver device for transmission.

[0176] A scheduling device is also provided, comprising: a circuit to determine a grant request indicator indicating an allowed number of scheduling requests; and a transceiver to transmit the grant request indicator.

[0177] In some embodiments, an allowed number of scheduling requests is determined per logical channel.

[0178] In some embodiments, the allowed number of scheduling requests per logical channel may be determined according to the priority of the logical channel.

[0179] For example, it may be determined that the allowed number of scheduling requests for high priority logical channels is greater than the allowed number of scheduling requests for low priority logical channels. In other words, the allowed number of scheduling requests for each logical channel may be determined according to the priority of the logical channel.

[0180] In some embodiments, the grant request indicator indicates a allowed number of scheduling requests per logical channel.

[0181] In some embodiments, the transceiver receives a scheduling request on an opportunity of a physical uplink control channel, PUCCH, and sends a resource allocation indicator via a physical downlink control channel, PDCCH, indicating resources assigned to the transceiver device for transmission.

[0182] A scheduling device is also provided, comprising: a circuit to determine a scheduling request configuration indicator indicating a plurality of scheduling request configurations; and a transceiver to transmit the scheduling request configuration indicator.

[0183] In some embodiments, the number of scheduling request configurations is determined per logical channel.

[0184] In some embodiments, the number of scheduling request configurations may be determined according to the priority of the logical channel.

[0185] For example, it may be determined that the number of scheduling request configurations for high priority logical channels is greater than the number of scheduling request configurations for low priority logical channels. In other words, the number of scheduling request configurations may be determined according to the priority of the logical channel.

[0186] In some embodiments, the transceiver receives a scheduling request on an opportunity of a physical uplink control channel, PUCCH, and sends a resource allocation indicator via a physical downlink control channel, PDCCH, indicating resources assigned to the transceiver device for transmission.

[0187] A method is also provided, comprising repeating the scheduling request on a medium access control (MAC) layer by indicating that the scheduling request is sent on multiple opportunities of a physical uplink control channel (PUCCH); and sending the scheduling request via the PUCCH.

[0188] In some embodiments, the method includes starting a scheduling request prohibit timer and not instructing sending a scheduling request if the scheduling request prohibit timer is running.

[0189] In some embodiments, the method includes receiving a grant request indicator indicating an allowed number of scheduling requests; starting a scheduling request prohibit timer after scheduling requests have been sent at opportunities equal to the allowed number of scheduling requests indicated by the grant request indicator.

[0190] In some embodiments, the grant request indicator indicates a allowed number of scheduling requests per logical channel.

[0191] In some embodiments, the method includes receiving a resource allocation indicator via a physical downlink control channel (PDCCH) indicating resources allocated to the transceiver device for transmission; and determining the allocated resources according to the resource allocation indicator and stopping the scheduling request prohibit timer.

[0192] In some embodiments, the method includes receiving a scheduling request configuration indicator indicating a plurality of scheduling request configurations, and sending scheduling requests on a plurality of opportunities according to the plurality of scheduling request configuration indications.

[0193] In some embodiments, the method includes starting multiple scheduling request prohibit timers, each scheduling request prohibit timer is associated with one of the multiple scheduling request configurations, and while the scheduling request prohibit timer associated with one of the multiple scheduling request configurations is running, not indicating to send a scheduling request on an opportunity according to one of the multiple scheduling request configurations.

[0194] In some embodiments, the method includes starting each scheduling request inhibit timer upon sending a scheduling request in accordance with one of a plurality of scheduling request configurations associated with the scheduling request inhibit timer.

[0195] In some embodiments, the method includes receiving a grant request indicator indicating an allowed number of scheduling requests for each logical channel; and starting each scheduling request prohibit timer after the scheduling request has been sent on multiple opportunities according to the allowed number of scheduling requests indicated by the grant request indicator.

[0196] In some embodiments, the method includes receiving a resource allocation indicator via a physical downlink control channel (PDCCH) indicating resources allocated to a transceiver device for transmission; and determining the allocated resources according to the resource allocation indicator and stopping a plurality of scheduling request prohibit timers.

[0197] A method is also provided that includes determining a grant request indicator indicating an allowed number of scheduling requests; and sending the grant request indicator.

[0198] In some embodiments, an allowed number of scheduling requests is determined per logical channel.

[0199] In some embodiments, the allowed number of scheduling requests for each logical channel may be determined according to the priority of the logical channel.

[0200] For example, it may be determined that the allowed number of scheduling requests for high priority logical channels is greater than the allowed number of scheduling requests for low priority logical channels. In other words, the allowed number of scheduling requests for each logical channel may be determined according to the priority of the logical channel.

[0201] In some embodiments, the grant request indicator indicates a allowed number of scheduling requests per logical channel.

[0202] In some embodiments, the method comprises receiving a scheduling request on an opportunity of a physical uplink control channel, PUCCH, and sending a resource allocation indicator via a physical downlink control channel, PDCCH, indicating resources assigned to the transceiver device for transmission.

[0203] A method is also provided, comprising determining a scheduling request configuration indicator indicating a plurality of scheduling request configurations; and sending the scheduling request configuration indicator.

[0204] In some embodiments, the number of scheduling request configurations is determined per logical channel.

[0205] In some embodiments, the number of scheduling request configurations may be determined according to the priority of the logical channel.

[0206] For example, it may be determined that the number of scheduling request configurations for high priority logical channels is greater than the number of scheduling request configurations for low priority logical channels. In other words, the number of scheduling request configurations may be determined according to the priority of the logical channel.

[0207] In some embodiments, the method comprises receiving a scheduling request on an opportunity of a physical uplink control channel, PUCCH, and sending a resource allocation indicator via a physical downlink control channel, PDCCH, indicating resources assigned to the transceiver device for transmission.

Claims

1. A transceiver device, comprising: A circuit for repeating the scheduling request on a medium access control (MAC) layer by instructing the transceiver to send the scheduling request on multiple opportunities of a physical uplink control channel (PUCCH); and a transceiver, sending the scheduling request via the PUCCH, in, The transceiver receives a scheduling request configuration indicator indicating a plurality of scheduling request configurations, the plurality of scheduling request configurations including a first scheduling request configuration having an associated first periodicity and a second scheduling request configuration having an associated second periodicity, and The circuitry instructs the transceiver to send the scheduling requests on the plurality of opportunities according to the plurality of scheduling request configurations.

2. The transceiver device according to claim 1, wherein The circuit: Start the dispatch request inhibit timer, and In case the scheduling request prohibit timer is running, the transceiver is not instructed to send the scheduling request.

3. The transceiver device according to claim 2, wherein The transceiver receives a grant request indicator indicating a granted number of scheduling requests; and The circuitry starts the scheduling request prohibit timer after the scheduling request has been sent at a number of opportunities equal to a allowed number of scheduling requests indicated by the grant request indicator.

4. The transceiver device according to claim 3, wherein The grant request indicator indicates a allowed number of scheduling requests for each logical channel.

5. The transceiver device according to any one of claims 2 to 4, wherein The transceiver receives a resource allocation indicator via a physical downlink control channel (PDCCH) indicating resources allocated to the transceiver device for transmission; and The circuit: determining the allocated resources according to the resource allocation indicator, and The dispatch request prohibit timer is stopped.

6. The transceiver device according to claim 1, wherein The circuit: starting a plurality of scheduling request inhibit timers, each scheduling request inhibit timer being associated with one of the plurality of scheduling request configurations, and The transceiver is not instructed to opportunistically send the scheduling request according to the one of the plurality of scheduling request configurations in the event that a scheduling request prohibit timer associated with the one of the plurality of scheduling request configurations is running.

7. The transceiver device according to claim 6, wherein The circuitry starts each scheduling request inhibit timer when a scheduling request according to one of the plurality of scheduling request configurations associated with the scheduling request inhibit timer is sent.

8. The transceiver device according to claim 6, wherein: The transceiver receives a grant request indicator indicating a permitted number of scheduling requests for each logical channel; as well as The circuitry starts each scheduling request prohibit timer after the scheduling request has been sent over a plurality of opportunities according to a allowed number of the scheduling requests indicated by the grant request indicator.

9. The transceiver device according to claim 5, wherein The transceiver receives a resource allocation indicator via a physical downlink control channel (PDCCH) indicating resources allocated to the transceiver device for transmission; and The circuit: determining the allocated resources according to the resource allocation indicator, and The plurality of scheduling request prohibit timers are stopped.

10. A dispatching device comprising circuitry that determines a scheduling request configuration indicator indicative of a plurality of scheduling request configurations, the plurality of scheduling request configurations comprising a first scheduling request configuration having an associated first periodicity, and a second scheduling request configuration having an associated second periodicity; and a transceiver, sending the scheduling request configuration indicator and receiving a scheduling request; in, The scheduling request is repeated on a medium access control (MAC) layer by being sent on multiple opportunities of a physical uplink control channel (PUCCH) according to the multiple scheduling request configurations.

11. A method for communication, comprising: Repeating the scheduling request at the medium access control MAC layer by indicating that the scheduling request is sent at multiple opportunities of the physical uplink control channel PUCCH; Sending the scheduling request via the PUCCH, in, The method also includes receiving a scheduling request configuration indicator indicating a plurality of scheduling request configurations, the plurality of scheduling request configurations including a first scheduling request configuration having an associated first periodicity and a second scheduling request configuration having an associated second periodicity, and The sending of the scheduling request includes sending the scheduling request on the multiple opportunities according to the multiple scheduling request configurations.

12. A method for communication, comprising: determining a scheduling request configuration indicator indicating a plurality of scheduling request configurations, the plurality of scheduling request configurations comprising a first scheduling request configuration having an associated first periodicity, and a second scheduling request configuration having an associated second periodicity; sending the scheduling request configuration indicator; as well as Receive scheduling requests, The scheduling request is repeated on a medium access control (MAC) layer by being sent on multiple opportunities of a physical uplink control channel (PUCCH) according to the multiple scheduling request configurations.

13. An integrated circuit controlling a process of a transceiver device, the process comprising: Repeating the scheduling request at the medium access control MAC layer by indicating that the scheduling request is sent at multiple opportunities of the physical uplink control channel PUCCH; Sending the scheduling request via the PUCCH, The process further comprises receiving a scheduling request configuration indicator, the scheduling request configuration indicator indicating a plurality of scheduling request configurations, the plurality of scheduling request configurations comprising a first scheduling request configuration having an associated first periodicity, and a second scheduling request configuration having an associated second periodicity, and The sending of the scheduling request includes sending the scheduling request on the multiple opportunities according to the multiple scheduling request configurations.

14. An integrated circuit controlling a process of scheduling a device, the process comprising: determining a scheduling request configuration indicator indicating a plurality of scheduling request configurations, the plurality of scheduling request configurations comprising a first scheduling request configuration having an associated first periodicity, and a second scheduling request configuration having an associated second periodicity; sending the scheduling request configuration indicator; as well as Receive scheduling requests, The scheduling request is repeated on a medium access control (MAC) layer by being sent on multiple opportunities of a physical uplink control channel (PUCCH) according to the multiple scheduling request configurations.