Device and method

Abstract

To realize an improvement of an accuracy of a scheduling of UL data at the time of scheduling in response to a scheduling request.SOLUTION: According to one aspect of the present disclosure, there is provided an apparatus (200) including: a communication processing part (233) that receives a message including setting information for specifying one of a plurality of types of a scheduling request and transmits one scheduling request of the plurality of types specified based on the setting information; and an information acquisition part (231) that acquires the setting information included in the message. The plurality of types includes at least a first type and a second type, and the scheduling request of the second type corresponds to a value of a buffer status report used to provide information about an uplink data amount.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present disclosure relates to an apparatus and a method. [Background technology]

[0002] Mobile communication technologies are proposed by 3GPP (3rd Generation Partnership Project) (registered trademark) and defined in technical specifications (TS). In particular, 5G (5th Generation) technologies are currently being proposed and defined in TS.

[0003] In the above mobile communication system, a base station allocates communication resources for uplink (UL) transmission to a user equipment (UE). As described in Non-Patent Document 1, the user equipment transmits a scheduling request (SR) to the base station to request allocation of communication resources for the UL transmission. The user equipment transmits UL data to the base station using the allocated communication resources.

[0004] Furthermore, as described in Non-Patent Document 1, the UE transmits a buffer status report (BSR) to the base station to provide information on the amount of UL data. The BSR indicates a range of buffer sizes for UL data. This allows the base station to allocate communication resources according to the range of UL data buffer sizes indicated by the BSR. Note that, since the BSR indicates a range of buffer sizes, it is subject to quantization error. Furthermore, as described in Non-Patent Document 2, the SR parameters and BSR parameters are set in the RRC (radio resource control) layer.

[0005] Furthermore, as described in Non-Patent Documents 3 to 5, it has recently been proposed to apply the above mobile communication system to XR (extended reality) services.

[0006] Here, in existing systems, there are fewer transmission opportunities for UL traffic than for downlink (DL) traffic. Furthermore, in UL data transmission, an SR may be transmitted first, followed by a BSR, and then UL data transmission. That is, UL data transmission may be delayed until communication resources for UL data transmission are allocated through the transmission of the SR and BSR. On the other hand, XR services may have delay requirements (e.g., packet delay budgets (PDBs)). Therefore, in existing systems where UL data transmission may be delayed, it may be difficult to meet the delay requirements of the XR service.

[0007] As a countermeasure, Non-Patent Document 5 proposes extending the SR so that it can provide one or two bits of information corresponding to the BSR value. Specifically, instead of transmitting an unmodulated signal to indicate the SR, it is considered to transmit a signal modulated with BPSK (binary phase shift keying) or QPSK (quadrature phase shift keying) as the SR. This can fill the gap in buffer information between the SR, which does not have UL data buffer information, and the BSR, which provides detailed buffer information. As a result, it is possible to improve the accuracy of UL data scheduling at the time of scheduling according to the SR. In other words, the delay and waiting time of UL data transmission are reduced. [Prior art documents] [Non-patent literature]

[0008] [Non-Patent Document 1] 3GPP TS 38.321 V17.0.0 (2022-03), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 17)” [Non-patent document 2] 3GPP TS 38.331 V17.1.0 (2022-06), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 17)” [Non-patent document 3] 3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203607, “Discussion on XR specific capacity enhancements techniques” [Non-patent document 4] 3GPP TSG-RAN WG1 Meeting #109-e, Online, May 9th - 20th, 2022, R1-2203639, “Discussion on capacity enhancements for XR” [Non-Patent Document 5] 3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203928, “Considerations on XR Capacity Improvements” Summary of the Invention [Problem to be solved by the invention]

[0009] As a result of detailed investigations by the inventors, the following problem was found: In non-patent literature, the concept of SR that can be expanded to provide information has been proposed, but no specific method has been proposed.

[0010] An object of the present disclosure is to provide an apparatus and a method capable of improving the accuracy of UL data scheduling at the time of scheduling according to SR. [Means for solving the problem]

[0011] An apparatus (200) according to one aspect of the present disclosure includes: a communication processing unit (233) that receives a message including configuration information for identifying one of a plurality of types of scheduling requests and transmits one of the plurality of types identified based on the configuration information; and an information acquisition unit (231) that acquires the configuration information included in the message, wherein the plurality of types include at least a first type and a second type, and the second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data.

[0012] An apparatus (100) according to one embodiment of the present disclosure includes an information acquisition unit (141) that acquires configuration information for identifying one of a plurality of types of scheduling requests, and a communication processing unit (143) that transmits a message including the configuration information and receives one of a plurality of types of scheduling requests identified based on the configuration information, wherein the plurality of types include at least a first type and a second type, and the second type of scheduling request corresponds to a value of a buffer status report used to provide information about an uplink data volume.

[0013] A method performed by an apparatus (200) according to one aspect of the present disclosure includes receiving a message including configuration information for identifying one of a plurality of types of scheduling requests, transmitting one of a plurality of types of scheduling requests identified based on the configuration information, and obtaining the configuration information included in the message, wherein the plurality of types include at least a first type and a second type, and the second type of scheduling request corresponds to a value of a buffer status report used to provide information about an amount of uplink data.

[0014] A method performed by an apparatus (100) according to one aspect of the present disclosure includes obtaining configuration information for identifying one of a plurality of types of scheduling requests, transmitting a message including the configuration information, and receiving one of a plurality of types of scheduling requests identified based on the configuration information, the plurality of types including at least a first type and a second type, and the second type of scheduling request corresponds to a value of a buffer status report used to provide information about an amount of uplink data. [Effects of the Invention]

[0015] According to the present disclosure, it is possible to improve the accuracy of UL data scheduling at the time of scheduling according to SR. Note that the present disclosure may achieve other effects instead of or in addition to the effect. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 10 is an explanatory diagram showing an example of UL data transmission. [Figure 2] FIG. 1 is a diagram showing Short BSR. [Figure 3] FIG. 10 is a diagram illustrating a table of buffer sizes. [Figure 4] FIG. 1 is a diagram illustrating Long BSR. [Figure 5] FIG. 1 is an explanatory diagram illustrating an example of a schematic configuration of a system according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a block diagram illustrating an example of a schematic functional configuration of a base station according to an embodiment of the present disclosure. [Figure 7] FIG. 2 is a block diagram illustrating an example of a schematic hardware configuration of a base station according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a block diagram illustrating an example of a schematic functional configuration of a user device according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a block diagram illustrating an example of a schematic hardware configuration of a user device according to an embodiment of the present disclosure. [Figure 10] FIG. 1 is a diagram for explaining UL data transmission according to an embodiment of the present disclosure. [Figure 11] FIG. 10 is a diagram illustrating an example of setting information for identifying the type of SR according to an embodiment of the present disclosure. [Figure 12] FIG. 10 is a diagram for explaining an example of an SR value according to an embodiment of the present disclosure. [Figure 13] FIG. 1 is a sequence diagram illustrating an example of a schematic flow of a process according to an embodiment of the present disclosure. [Figure 14] FIG. 10 is a diagram showing an example of setting information including the setting information according to the first modified example 1 of the embodiment of the present disclosure. [Figure 15] FIG. 10 is a diagram showing an example of setting information including the setting information according to the first modified example 2 of the embodiment of the present disclosure. [Figure 16] FIG. 10 is a diagram illustrating an example of the setting information according to a second modified example 1 of the embodiment of the present disclosure. [Figure 17] FIG. 10 is a diagram illustrating an example of the setting information according to a second modified example 2 of the embodiment of the present disclosure. [Figure 18] FIG. 10 is a diagram for explaining an example of an SR value according to the third modified example 1 of the embodiment of the present disclosure. [Figure 19] FIG. 10 is a diagram for explaining an example of an SR value according to the third modified example 2 of the embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, elements that can be similarly described will be designated by the same reference numerals, and redundant description will be omitted.

[0018] The explanation will be given in the following order: 1. Related technologies 2. System Configuration 3. Base Station Configuration 4. User equipment configuration 5. Example of operation 6. Variations

[0019] <1. Related technologies> As techniques related to the embodiments of the present disclosure, a scheduling request (SR) and a buffer status report (BSR) will be described.

[0020] (1) Scheduling Request (SR) The SR is used by a UE to request a communication resource allocation for a new UL transmission from a base station. For example, the SR may be used to request resources for an uplink-shared channel (UL-SCH) for an initial transmission. Here, the UL-SCH may be mapped to a physical uplink shared channel (PUSCH). In this embodiment, data on the UL-SCH is also referred to as UL data. As communication resources for the SR, multiple bandwidth parts (BWPs) and / or a set of physical uplink control channel (PUCCH) resources across a cell are allocated. For each logical channel, up to one PUCCH resource is allocated for the SR in each BWP. For example, one or more downlink BWPs and / or one or more uplink BWPs may be configured in each of one or more cells (also referred to as serving cells). For example, a set of PUCCH resources may be configured for each of one or more uplink BWPs.

[0021] With reference to FIG. 1, an example of UL transmission using SR will be described. When UL data arrives, the UE triggers SR. The SR is transmitted to the base station using the PUCCH. The base station, having received the SR, allocates resources for UL data transmission to the UE. The UL resource allocation is transmitted to the UE using a physical downlink control channel (PDCCH). The UE, having received the UL resource allocation, transmits UL data to the base station using the allocated PUSCH resources. A BSR may also be transmitted together with the UL data. In this embodiment, the UL resource allocation includes allocation of UL-SCH and / or allocation of PUSCH resources. Furthermore, the PUSCH resource allocation includes frequency domain resource assignment for PUSCH and / or time domain resource assignment for PUSCH. For example, the base station may transmit downlink control information (DCI) used for scheduling the PUSCH using the PDCCH. That is, the DCI may include information (one or more fields) for allocating PUSCH resources.

[0022] SR parameters are configured using SchedulingRequestConfig and / or SchedulingRequestResourceConfig, which are RRC configuration information. For example, SR parameters are parameters used for SR transmission and / or SR resource configuration, and are also referred to as SR configurations. SR parameters may include SchedulingRequestConfig and / or SchedulingRequestResourceConfig. The SR parameters may also include schedulingRequestID, sr-ProhibitTimer, sr-TransMax, periodicityAndOffset, phy-PriorityIndex, and / or resource, etc. Each SR configuration corresponds to one or more logical channels. For example, each SR configuration may correspond to one or more logical channels (and / or beam failure recovery (BFR)) via schedulingRequestID. The schedulingRequestID may be used to identify an SR instance at the MAC layer. The sr-ProhibitTimer may be used to configure a timer for SR transmission in the PUCCH. sr-TransMax may be used to set the maximum number of SR transmissions. periodicityAndOffset may be used to set the SR periodicity and offset. phy-PriorityIndex may be used to set the priority of the SR resource in PHY layer prioritization or multiplexing. The parameter "resource" may be used to set the ID (identifier) ​​of the PUCCH resource used for SR transmission. For example, a PUCCH resource corresponding to the PUCCH resource ID included in the SR parameter may be configured for SR transmission based on the SR parameter. The PUCCH resource may be configured using PUCCH format 0 or PUCCH format 1, which includes information used to configure the PUCCH resource.

[0023] Here, the RRC configuration information may include information transmitted and / or received in the RRC layer between the base station and the UE. That is, the base station may transmit an RRC message including an SR configuration to the UE. Alternatively, the UE may receive an RRC message including an SR configuration and perform SR transmission based on the SR configuration. Alternatively, the UE may receive an RRC message including an SR configuration and determine PUCCH resources to be used for SR transmission based on the SR configuration. For example, the RRC message may include an RRC reconfiguration message.

[0024] (2) Buffer Status Report (BSR) The BSR procedure (also referred to as a buffer status reporting procedure) is used to provide information about the amount (volume) of UL data in a UE to a base station. That is, the BSR is used in a procedure (buffer status reporting) for providing information about the amount (volume) of UL data of a MAC entity to a base station. The BSR is transmitted using a MAC CE (Control Element). That is, operations related to the BSR may be performed and / or processed in a MAC layer (e.g., a MAC entity) in the UE. Also, operations related to the BSR may be performed and / or processed in a MAC layer (e.g., a MAC entity) in a base station. In this embodiment, the higher layer includes a layer higher than the MAC layer. For example, the higher layer may include an RRC layer.

[0025] BSR-related parameters are configured using RRC configuration information. BSR parameters include periodicBSR-Timer, retxBSR-Timer, logicalChannelSR-DelayTimerApplied, logicalChannelSR-DelayTimer, logicalChannelSR-Mask, and logicalChannelGroup. The periodicBSR-Timer may be used to set a timer for the BSR period. The retxBSR-Timer may be used to set a timer for BSR retransmission. The logicalChannelSR-DelayTimerApplied may be used to set whether to apply a delay timer to SR transmission for a logical channel. The logicalChannelSR-DelayTimer may be used to set a delay timer for SR transmission for a logical channel. The logicalChannelSR-Mask may be used to set SR trigger control (i.e., whether to set SR masking) when a configured grant is set. The logicalChannelGroup may be used to set the ID of the logical channel group to which the logical channel belongs. The base station may send an RRC message including BSR-related parameters to the UE. The UE may also receive an RRC message including parameters related to the BSR, and perform reporting (ie, transmission) of the BSR based on the parameters related to the BSR.

[0026] The BSR is reported for each logical channel group (LCG). Each logical channel is assigned to one of the LCGs by the logicalChannelGroup, which indicates the ID of the LCG.

[0027] A BSR may be triggered when any of the following occurs for an activated cell group. Note that, according to the trigger mechanism below, BSRs are classified into Regular BSRs corresponding to (A) and (C), Periodic BSRs corresponding to (D), and Padding BSRs corresponding to (B). (A) UL data of logical channels belonging to one of the LCGs becomes available to the MAC entity. (B) UL resources are allocated, and the number of padding bits for the UL resources is equal to or greater than the size of the BSR MAC CE. (C) The period indicated by retxBSR-Timer expires and at least one logical channel belonging to any LCG contains UL data. (D) The period indicated by the periodic BSR-Timer expires.

[0028] Next, the BSR MAC CE will be described. The BSR MAC CE may correspond to the MAC CE used to transmit the BSR described above. For example, the format of the BSR MAC CE (hereinafter also referred to as BSR format) is defined as several types (e.g., Short BSR, Long BSR), and is identified by a MAC subheader including an LCID / eLCID. That is, an LCID (Logical Channel Identifier) / eLCID (Extended LCID) may be used to identify the type of the corresponding MAC CE. Also, an LCID / eLCID may be defined for each of a Downlink Shared Channel (DL-SCH) and / or an UL-SCH. Hereinafter, LCID / eLCID refers to an LCID and / or an eLCID.

[0029] The format 20A of the Short BSR will be described with reference to Figures 2 and 3. The size of the Short BSR is fixed. As shown in Figure 2, the Short BSR has an LCG ID field and a Buffer Size field. The LCG ID field identifies the LCG ID for which the buffer size is reported. The size of the LCG ID field is 3 bits. The Buffer Size field identifies the total amount of data available for all logical channels belonging to the LCG indicated by the LCG ID. The size of the Buffer Size field is 5 bits. The Buffer Size field indicates an index corresponding to the buffer size in table T1 for the 5-bit Buffer Size field shown in Figure 3.

[0030] The format 20B of the Long BSR will be described with reference to FIG. 4. The size of the Long BSR is variable. As shown in FIG. 4, the Long BSR has an LCGi field and a Buffer Size j field. LCGi is the LCG with the i-th ID, and the LCGi field indicates the presence of a Buffer Size field for LCGi. The LCGi field is set to 1 if a buffer size is reported, and set to 0 otherwise. Alternatively, the LCGi field may indicate whether LCGi has available data. The Buffer Size j field identifies the total amount of data available for all logical channels belonging to the corresponding LCGi. The size of the Buffer Size j field is 8 bits. The Buffer Size j field indicates an index corresponding to the buffer size in a table for the 8-bit Buffer Size field (not shown). Note that the Buffer Size j fields are included in ascending order according to the LCGi.

[0031] The BSR format is selected according to the method specified in TS (TS 38.321 5.4.5 and 5 / 4.7).

[0032] For example, in the case of Regular BSR and Periodic BSR, if there are two or more LCGs with available data when the MAC PDU containing the BSR is built, Long BSR is reported, otherwise Short BSR is reported. Furthermore, for MAC entities for which logicalChannelGroup-IABExt is configured by higher layers, Extended Long BSR or Extended Short BSR may be reported.

[0033] For example, in the case of Padding BSR, in addition to the above BSR format, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, and Extended Long Truncated BSR are reported depending on the conditions.

[0034] Also, for example, the Pre-emptive BSR and the Extended Pre-emptive BSR are used by an IAB-MT (Mobile Termination).

[0035] <2. System Configuration> An example of the configuration of a system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 5. Referring to Fig. 5, the system 1 includes a base station 100 and a UE 200.

[0036] For example, the system 1 is a system that complies with 3GPP TS. More specifically, for example, the system 1 is a system that complies with 5G or NR (New Radio) TS. Naturally, the system 1 is not limited to this example.

[0037] (1) Base station 100 The base station 100 is a node in a radio access network (RAN) and communicates with UEs (eg, UE 200) located within the coverage area 10 of the base station 100.

[0038] For example, the base station 100 communicates with a UE (e.g., the UE 200) using a RAN protocol stack. For example, the protocol stack includes radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and a physical (PHY) layer protocol. Alternatively, the protocol stack may include only some of these protocols, rather than all of them.

[0039] For example, the base station 100 is a gNB. The gNB is a node that provides NR user plane and control plane protocol terminations toward the UE and is connected to a 5G Core Network (5GC) via an NG interface. Alternatively, the base station 100 may be an en-gNB. The en-gNB is a node that provides NR user plane and control plane protocol terminations toward the UE and operates as a secondary node in E-UTRA-NR Dual Connectivity (EN-DC).

[0040] The base station 100 may include multiple nodes. The multiple nodes may include a first node hosting a higher layer included in the protocol stack and a second node hosting a lower layer included in the protocol stack. The higher layer may include RRC, SDAP, and PDCP, and the lower layer may include RLC, MAC, and a PHY layer. The first node may be a central unit (CU), and the second node may be a distributed unit (DU). The multiple nodes may include a third node that performs processing below the PHY layer, and the second node may perform processing above the PHY layer. The third node may be a radio unit (RU).

[0041] Alternatively, the base station 100 may be one of the plurality of nodes, or may be connected to other units of the plurality of nodes.

[0042] The base station 100 may be an integrated access and backhaul (IAB) donor or an IAB node.

[0043] (2)UE200 The UE 200 communicates with the base station 100. For example, the UE 200 communicates with the base station 100 when the UE 200 is located within the coverage area 10 of the base station 100.

[0044] For example, the UE 200 communicates with a base station (eg, the base station 100) using the above protocol stack.

[0045] Furthermore, the UE 200 transmits an SR and a BSR to the base station as described in <1. Related Art>. Furthermore, the UE 200 may be a device that supports the XR service (in other words, an XR scenario).

[0046] <3. Base station configuration> An example of the configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to FIGS.

[0047] (1) Functional configuration First, an example of a functional configuration of a base station 100 according to an embodiment of the present disclosure will be described with reference to Fig. 6. Referring to Fig. 6, the base station 100 includes a radio communication unit 110, a network communication unit 120, a storage unit 130, and a processing unit 140.

[0048] The wireless communication unit 110 transmits and receives signals wirelessly. For example, the wireless communication unit 110 receives signals from UEs and transmits signals to UEs.

[0049] The network communication unit 120 receives signals from the network and transmits signals to the network.

[0050] The storage unit 130 stores various information for the base station 100 .

[0051] The processing unit 140 provides various functions of the base station 100. The processing unit 140 includes an information acquisition unit 141, a first communication processing unit 143, and a second communication processing unit 145. The processing unit 140 may further include other components in addition to these components. That is, the processing unit 140 may also perform operations other than those of these components. The specific operations of the information acquisition unit 141, the first communication processing unit 143, and the second communication processing unit 145 will be described in detail later.

[0052] For example, the processing unit 140 (first communication processing unit 143) communicates with a UE (e.g., UE 200) via the radio communication unit 110. For example, the processing unit 140 (second communication processing unit 145) communicates with another node (e.g., a network node in a core network or another base station) via the network communication unit 120.

[0053] (2) Hardware configuration Next, an example of a hardware configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to Fig. 7. Referring to Fig. 7, the base station 100 includes an antenna 181, an RF (radio frequency) circuit 183, a network interface 185, a processor 187, a memory 189, and a storage 191.

[0054] Antenna 181 converts signals into radio waves and radiates the radio waves into space. Antenna 181 also receives radio waves in space and converts the radio waves into signals. Antenna 181 may include a transmitting antenna and a receiving antenna, or may be a single antenna for both transmission and reception. Antenna 181 may be a directional antenna and may include multiple antenna elements.

[0055] The RF circuit 183 performs analog processing of signals transmitted and received via the antenna 181. The RF circuit 183 may include a high-frequency filter, an amplifier, a modulator, a low-pass filter, and the like.

[0056] The network interface 185 is, for example, a network adapter, and transmits signals to and receives signals from a network.

[0057] The processor 187 performs digital processing of signals transmitted and received via the antenna 181 and the RF circuit 183. The digital processing includes processing of a protocol stack of the RAN. The processor 187 also processes signals transmitted and received via the network interface 185. The processor 187 may include multiple processors or may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

[0058] Memory 189 stores programs executed by processor 187, parameters related to the programs, and various other information. Memory 189 may include at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), and a flash memory. All or a portion of memory 189 may be included within processor 187.

[0059] The storage 191 stores various information and may include at least one of an SSD (solid state drive) and an HDD (hard disc drive).

[0060] The wireless communication unit 110 may be implemented by an antenna 181 and an RF circuit 183. The network communication unit 120 may be implemented by a network interface 185. The memory unit 130 may be implemented by a storage 191. The processing unit 140 may be implemented by a processor 187 and a memory 189.

[0061] A part or all of the processing unit 140 may be virtualized. In other words, a part or all of the processing unit 140 may be implemented as a virtual machine. In this case, a part or all of the processing unit 140 may operate as a virtual machine on a physical machine (i.e., hardware) including a processor, memory, etc., and a hypervisor.

[0062] Considering the above hardware configuration, base station 100 may include a memory (i.e., memory 189) that stores a program, and one or more processors (i.e., processor 187) that can execute the program, and the one or more processors may execute the program to perform the operations of processing unit 140. The program may be a program that causes the processor to perform the operations of processing unit 140.

[0063] <4. User device configuration> An example of the configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to FIGS.

[0064] (1) Functional configuration First, an example of a functional configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to Fig. 8. Referring to Fig. 8, the UE 200 includes a radio communication unit 210, a storage unit 220, and a processing unit 230.

[0065] The wireless communication unit 210 transmits and receives signals wirelessly. For example, the wireless communication unit 210 receives a signal from a base station and transmits the signal to the base station. For example, the wireless communication unit 210 receives a signal from another UE and transmits the signal to the other UE.

[0066] The storage unit 220 stores various information for the UE 200 .

[0067] The processing unit 230 provides various functions of the UE 200. The processing unit 230 includes an information acquisition unit 231 and a communication processing unit 233. The processing unit 230 may further include other components in addition to these components. That is, the processing unit 230 may also perform operations other than those of these components. The specific operations of the information acquisition unit 231 and the communication processing unit 233 will be described in detail later.

[0068] For example, the processing unit 230 (communication processing unit 233) communicates with a base station (for example, the base station 100) or other UE via the wireless communication unit 210.

[0069] (2) Hardware configuration Next, an example of a hardware configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to Fig. 9. Referring to Fig. 9, the UE 200 includes an antenna 281, an RF circuit 283, a processor 285, a memory 287, and a storage 289.

[0070] Antenna 281 converts signals into radio waves and radiates the radio waves into space. Antenna 281 also receives radio waves in space and converts the radio waves into signals. Antenna 281 may include a transmitting antenna and a receiving antenna, or may be a single antenna for both transmission and reception. Antenna 281 may be a directional antenna and may include multiple antenna elements.

[0071] The RF circuit 283 performs analog processing of signals transmitted and received via the antenna 281. The RF circuit 283 may include a high-frequency filter, an amplifier, a modulator, a low-pass filter, and the like.

[0072] The processor 285 performs digital processing of signals transmitted and received via the antenna 281 and the RF circuitry 283. The digital processing includes processing of a RAN protocol stack. The processor 285 may include multiple processors or may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

[0073] The memory 287 stores programs executed by the processor 285, parameters related to the programs, and various other information. The memory 287 may include at least one of a ROM, an EPROM, an EEPROM, a RAM, and a flash memory. All or a part of the memory 287 may be included within the processor 285.

[0074] The storage 289 stores various information and may include at least one of an SSD and an HDD.

[0075] The wireless communication unit 210 may be implemented by an antenna 281 and an RF circuit 283. The memory unit 220 may be implemented by a storage 289. The processing unit 230 may be implemented by a processor 285 and a memory 287.

[0076] The processing unit 230 may be implemented by a system on chip (SoC) including a processor 285 and a memory 287. The SoC may include an RF circuit 283, and the wireless communication unit 210 may also be implemented by the SoC.

[0077] Considering the above hardware configuration, UE 200 may include a memory (i.e., memory 287) that stores a program, and one or more processors (i.e., processor 285) that can execute the program, and the one or more processors may execute the program to perform the operation of processing unit 230. The program may be a program that causes the processor to perform the operation of processing unit 230.

[0078] <5. Example of operation> As described above, in existing mobile communication systems where UL data transmission may be put on hold, it may be difficult to meet the delay requirements of XR services. This will be explained in more detail with reference to FIG. 10.

[0079] The following describes a case where UL data is transmitted in the following procedure: First, the UE transmits a PUCCH for SR. Then, the UE transmits a PUSCH for reporting BSR. Then, the UE transmits a PUSCH for UL data scheduled according to the BSR.

[0080] For example, as shown in Fig. 10, when UL data arrives, the UE triggers SR and transmits a PUCCH for the SR (step S31). The base station transmits a PDCCH for scheduling information of the BSR in response to the received SR (step S33). The UE transmits a PUSCH for reporting the BSR (or BSR + data) based on the scheduling information of the BSR (step S35). The base station transmits a PDCCH for scheduling information of the UL data in response to the BSR (step S37). The UE transmits a PUSCH for the UL data based on the scheduling information of the UL data (step S39).

[0081] In the example of Figure 10, the UL-DL configuration is DDDDU. Therefore, the SR, BSR, and UL data are transmitted at UL transmission opportunities set every 5 slots. In the example of Figure 10, there is a time lag of at least 10 slots between the arrival and transmission of the UL data. This corresponds to a delay of at least 10 ms when the subcarrier spacing (SCS) is 15 kHz. As a result, the XR data may be large in volume, making it difficult for the UE to meet the delay requirement.

[0082] In contrast, in an embodiment of the present disclosure, a message including configuration information for specifying one of multiple SR types (hereinafter also referred to as SR type configuration information) is transmitted and received, and one SR of multiple types specified based on the configuration information is transmitted and received. The multiple types include at least a first type and a second type, and the second type SR corresponds to the value of the BSR. This makes it possible to configure an SR that is extended to provide one or two bits of information corresponding to the BSR value, thereby improving the accuracy of UL data scheduling at the time of scheduling according to the SR.

[0083] An example of the operation of the base station 100 and the UE 200 according to the embodiment of the present disclosure will be described with reference to FIGS.

[0084] (1) SR type setting information Configuration information for specifying one of multiple types of SR is defined. The multiple types include at least a first type and a second type. The second type of SR (hereinafter also referred to as enhanced-SR) corresponds to a BSR value used to provide information about the amount of UL data. The first type of SR is not modulated and does not provide any information other than a scheduling request. In other words, the first type of SR is a legacy SR. Note that the second type of SR is modulated and provides information other than a scheduling request.

[0085] The SR type setting information is included in the SR setting information. As a result, the SR type setting information is set for each SR. Since each SR corresponds to a communication resource associated with each SR, it can also be said that the SR type setting information is set for the communication resource associated with each SR.

[0086] The SR type configuration information will be described in detail with reference to Fig. 11. Fig. 11 shows an example of configuration information including the SR type configuration information and the relationship between various types of configuration information. As shown in Fig. 11, LogicalChannelConfig (blocks 41A to 41C), which is configuration information for logical channels, SchedulingRequestConfig (blocks 51A to 51B), which is configuration information for SR, and SchedulingRequestResourceConfig (blocks 61A to 61B), which is configuration information for SR communication resources, are associated with each other via a schedulingRequestID. Furthermore, PUCCH-Resource (block 71A), which is configuration information for PUCCH resources, is associated with SchedulingRequestResourceConfig (block 61B) via a PUCCH-ResourceId.

[0087] The SR type setting information is included in SchedulingRequestResourceConfig. For example, as shown in blocks 61A and 61B in Fig. 11, Sr-Type as SR type setting information is included as a parameter of SchedulingRequestResourceConfig. Since SchedulingRequestResourceConfig is set for schedulingRequestID, Sr-Type is also set for schedulingRequestID. Note that the SR type setting information may also be included in SchedulingRequestConfig that is set for schedulingRequestID.

[0088] The SR type setting information is a flag corresponding to multiple SR types. For example, as shown in blocks 61A and 61B in FIG. 11, when Sr-Type is present, it indicates that the UE 200 is configured to transmit enhanced-SR. Conversely, when Sr-Type is absent, it indicates that the UE 200 is not configured to transmit enhanced-SR, i.e., is configured to transmit legacy SR. Furthermore, the SR type setting information may indicate which SR type is used depending on its value. For example, when Sr-Type has a value of 0, it indicates that a 1-bit SR is used, and when it has a value of 1, it indicates that a 2-bit SR is used.

[0089] 11, Sr-Type=0 is set for schedulingRequestID=1, and Sr-Type=1 is set for schedulingRequestID=2. That is, the SR for schedulingRequestID=1 is transmitted using 1 bit, and the SR for schedulingRequestID=2 is transmitted using 2 bits.

[0090] The SR type setting information is also associated with the logical channel setting information via the SR ID.

[0091] (2) SR value The second type of SR (i.e., enhanced-SR) in this embodiment corresponds to the value of BSR used to provide information about the amount of UL data. Specifically, enhanced-SR corresponds to the type of UL data.

[0092] Here, the BSR is used to provide information about the amount of UL data, such as buffer size information for UL data. However, the buffer size may differ depending on the type of UL data. Therefore, the value reported by the BSR may also change depending on the type of UL data. As a countermeasure, it may be possible to change the table of values ​​reported by the BSR depending on the type of UL data, as described below.

[0093] Therefore, enhanced-SR according to this embodiment corresponds to the type of UL data, and thus an approximate buffer size (i.e., the amount of UL data) according to the type of UL data can be indicated to base station 100 prior to BSR.

[0094] The SR values ​​corresponding to the types of UL data will be described in detail with reference to Fig. 12. An example of a 2-bit SR is shown in Fig. 12. Note that the SR values ​​shown in Table T2 of Fig. 12 may also be set for a 1-bit SR.

[0095] For example, as shown in table T2 in Fig. 12, data types pose / control and video are associated with SR values ​​01 and 10, respectively. Note that an SR value of 11 is undetermined.

[0096] Note that a table indicating the correspondence between the above-mentioned enhanced-SR and the type of UL data may be set and referenced by the base station 100 and the UE 200. Furthermore, setting information of the table may be transmitted from the base station 100 to the UE 200.

[0097] (3) Message containing configuration information The SR type setting information according to this embodiment is transmitted in a message, which may be an RRC message.

[0098] For example, the SR type configuration information is transmitted in an RRC message including SchedulingRequestResourceConfig. The RRC message may be, for example, RRCReconfiguration, RRCResume, or RRCSetup. Alternatively, an RRC message different from the above RRC message may be used.

[0099] (4) Operation of UE200 The UE 200 according to this embodiment receives SR type setting information according to this embodiment. The UE 200 acquires setting information from a message including the received SR type setting information. The UE 200 identifies the type of SR to use from a plurality of types based on the acquired SR type setting information.

[0100] Specifically, the UE 200 identifies the type of SR based on SR type configuration information acquired from the received RRC message. For example, the UE 200 selects either enhanced-SR or legacy SR for each SR ID based on the SR type configuration information included in the SR configuration information. When enhanced-SR is selected, either 1-bit SR or 2-bit SR is further selected. The UE 200 transmits an SR of the selected type at the SR transmission timing.

[0101] The UE 200 may select the type of SR at the timing of transmitting the SR. For example, when the SR type setting information is included in the SchedulingRequestResourceConfig, the UE 200 identifies the type of SR based on the SR type setting information at the timing of transmitting the SR on the communication resource associated with the SchedulingRequestResourceConfig (i.e., the timing indicated by the period and offset).

[0102] Furthermore, the UE 200 according to this embodiment may select a table corresponding to the value of the BSR (hereinafter also referred to as a BSR table) according to the transmitted enhanced-SR. Specifically, the transmitted enhanced-SR corresponds to the type of UL data, and the BSR table is selected according to the type of UL data.

[0103] Multiple BSR tables may be defined, and the range of buffer sizes that each of the multiple BSR tables can indicate may be different. Furthermore, the range or granularity of buffer sizes corresponding to the indexes of each of the multiple BSR tables may also be different. For example, a table that can indicate buffer sizes from 0 to 1 Kbytes and a table that can indicate buffer sizes of 1 Kbyte or more may be defined. Furthermore, for example, a table that corresponds to index 1 with a buffer size range of ≦10 and a table that corresponds to the same index 1 with a buffer size range of ≦20 may be defined.

[0104] A BSR table to be used is selected from multiple BSR tables according to the type of UL data. For example, UE 200 selects a BSR table according to the type of UL data indicated by enhanced-SR, as shown in FIG. 12. If the type of buffered UL data is video, enhanced-SR indicates a value of 10 corresponding to video, and a BSR table capable of indicating a buffer size of 1 Kbyte or more corresponding to video is selected. Also, if the type of buffered UL data is pose / control, enhanced-SR indicates a value of 01 corresponding to pose / control, and a BSR table capable of indicating a buffer size of 0 to 1 Kbyte corresponding to pose / control is selected. UE 200 transmits a BSR using the selected BSR table.

[0105] Note that base station 100 may select a BSR table according to the received enhanced-SR. The method of selecting a BSR table is substantially the same as that of UE 200, and therefore description thereof will be omitted. Alternatively, a BSR table may be selected based on SR type setting information.

[0106] (5) Processing flow An example of processing according to this embodiment will be described with reference to FIG.

[0107] The base station 100 sets the SR type setting information in the RRC message (step S310). For example, the base station 100 obtains the Sr-Type as shown in Fig. 11 and sets the Sr-Type in SchedulingRequestResourceConfig.

[0108] The base station 100 transmits an RRC message including the SR type setting information to the UE 200 (step S320). For example, the base station 100 transmits to the UE 200 an RRC message (for example, RRCReconfiguration, RRCResume, or RRCSetup) including SchedulingRequestResourceConfig in which Sr-Type is set.

[0109] When the UE 200 receives the RRC message including the SR type setting information, the UE 200 transmits an RRC message in response to the RRC message to the base station 100 (step S330). For example, when the UE 200 receives an RRC message including SchedulingRequestResourceConfig in which Sr-Type is set, the UE 200 transmits an RRC message in response (for example, RRCReconfigurationComplete, RRCResumeComplete, or RRCSetupComplete) to the base station 100.

[0110] The UE 200 identifies the type of SR to use based on the received SR type setting information (step S340). For example, when the timing to transmit the triggered SR arrives, if the Sr-Type in the SchedulingRequestResourceConfig set for the SR indicates 0, the UE 200 selects a 1-bit SR. If the Sr-Type indicates 1, the UE 200 selects a 2-bit SR. Note that if the Sr-Type is not set, the UE 200 selects a legacy SR.

[0111] The UE 200 transmits the first or second SR to the base station 100 (step S350). For example, the UE 200 transmits a legacy SR as the first SR, or a 1-bit SR or a 2-bit SR as the second SR to the base station 100. The UE 200 also selects a BSR table according to the transmitted 1-bit SR or 2-bit SR.

[0112] Thus, according to an embodiment of the present disclosure, a message including configuration information for specifying one of multiple types of SRs is transmitted and received, and one of the multiple types of SRs specified based on the configuration information is transmitted and received, the multiple types including at least a first type and a second type, and the second type of SR corresponds to a BSR value used to provide information about the amount of UL data. This allows for the configuration of an SR that is extended to provide one or two bits of information corresponding to the BSR value. In other words, it is possible to improve the accuracy of UL data scheduling at the time of scheduling according to the SR.

[0113] The setting information is included in the setting information of the SR, which allows the setting information to be set for each SR (for example, the ID of the SR or the communication resource associated with the SR).

[0114] Furthermore, the setting information is a flag corresponding to the plurality of types, which allows the setting information to be handled with a small amount of data, thereby suppressing an increase in communication resources for signaling the setting information.

[0115] Furthermore, a table corresponding to the value of the BSR is selected according to the second type of SR. This allows the BSR table to be dynamically selected using the SR without adding information to the BSR. In particular, since the size of XR data can vary greatly depending on the type, the value reported in the BSR and the table corresponding to the value can be dynamically changed, thereby improving scheduling efficiency.

[0116] The second type of SR corresponds to the type of UL data. This allows the type of buffered UL data to be indicated to base station 100 using the SR. Therefore, at the time of scheduling according to the SR, scheduling according to the amount of UL data estimated from the type of UL data becomes possible. Also, a BSR table corresponding to the type of UL data can be selected.

[0117] <6. Variations> First to fourth modified examples according to the first embodiment of the present disclosure will be described with reference to Figures 14 to 19. Note that two or more of these modified examples may be combined.

[0118] (1) First Modification: Another Example of Setting Information Including SR Type Setting Information In the above-described embodiment of the present disclosure, the SR type setting information is included in the SR setting information. However, the setting information including the SR type setting information according to the embodiment of the present disclosure is not limited to this example.

[0119] As a first modified example 1 of this embodiment, the SR type setting information may be included in the setting information of the logical channel. The setting information of the logical channel is associated with the setting information of the SR via the ID of the SR. Therefore, it can be said that the SR type setting information is set for the SR while being included in the setting information of the logical channel. With reference to FIG. 14, the SR type setting information included in the setting information of the logical channel will be described in detail.

[0120] SR type setting information is included in LogicalChannelConfig. For example, as shown in blocks 43A to 43C in Fig. 14, Sr-Type as SR type setting information is included as a parameter of LogicalChannelConfig. LogicalChannelConfig includes schedulingRequestID, and schedulingRequestID may be duplicated in multiple LogicalChannelConfigs. Therefore, it can be said that Sr-Type is set for schedulingRequestID. For example, in blocks 43A and 43B where schedulingRequestID is 1, Sr-Type is set to 0, and in block 43C where schedulingRequestID is 2, Sr-Type is set to 1.

[0121] The UE 200 identifies the type of SR by referring to the SR type setting information set for the logical channel of the UL data for which the SR is triggered. For example, when the UL data of the logical channel of block 43A shown in Fig. 14 is buffered and an SR is triggered for the UL data, the UE 200 refers to block 43A. In block 43A, Sr-Type is set and its value is 0, so the UE 200 selects a 1-bit SR as the type of the SR.

[0122] Also, as a first modified example 2 of this embodiment, the SR type configuration information may be included in the configuration information of the UL control channel resource for SR. The UL control channel may be the PUCCH. The configuration information of the PUCCH resource is associated with the configuration information of the SR via the ID of the PUCCH resource. Therefore, it can be said that the SR type configuration information is configured for the PUCCH resource. The SR type configuration information included in the configuration information of the PUCCH resource will be described in detail with reference to FIG. 15.

[0123] SR type setting information is included in PUCCH-Resource. For example, as shown in block 75A in Fig. 15 , Sr-Type as SR type setting information is included as a parameter of PUCCH-Resource. PUCCH-Resource and SchedulingRequestResourceConfig are associated via PUCCH-ResourceId. Therefore, Sr-Type is set for PUCCH-ResourceId. For example, in the example of Fig. 15 , block 75A in which Sr-Type is 1 and block 65B in which schedulingRequestID is 2 are associated via a certain PUCCH-ResourceId. On the other hand, although not shown, PUCCH-Resource in which Sr-Type is 0 and block 65A in which schedulingRequestID is 1 may be associated via a different PUCCH-ResourceId.

[0124] The UE 200 identifies the configuration information of the SR associated with the ID of the SR configured for the logical channel of the UL data for which the SR is triggered, and identifies the type of the SR by referring to the configuration information of the UL control channel resource associated with the configuration information of the SR. For example, when the UL data of the logical channel of block 45C shown in FIG. 15 is buffered and an SR is triggered for the UL data, the UE 200 refers to block 45C. The UE 200 identifies the associated blocks 55B and 65B based on the schedulingRequestID configured in block 45C. The UE 200 identifies the associated block 75A based on the PUCCH-ResourceId configured in block 65B. Since the Sr-Type is configured in block 75A and its value is 1, the UE 200 selects the 2-bit SR as the type of the SR.

[0125] As described above, according to the first modified example 1 of this embodiment, the SR type setting information may be included in the setting information of the logical channel. This allows the SR type setting information to be set using the setting information of the logical channel. For example, even if it is difficult to add a parameter to the SR setting information, the SR type setting information can be set for each SR.

[0126] Furthermore, according to the first modified example 2 of this embodiment, the SR type configuration information may be included in the configuration information of the UL control channel resource for SR. This makes it possible to configure the SR type configuration information for the UL control channel resource for SR. Therefore, it is possible to configure the SR type configuration information according to the selection of the UL control channel resource associated with the SR. Furthermore, even if it is difficult to add a parameter to the configuration information of the SR, it is possible to indirectly configure the SR type configuration information for each SR.

[0127] (2) Second Modification: Another Example of SR Type Setting Information In the above-described embodiment of the present disclosure, the SR type setting information is a flag corresponding to a plurality of SR types. However, the SR type setting information according to the embodiment of the present disclosure is not limited to this example.

[0128] As a second modified example 1 of this embodiment, the SR type setting information may be information used to indicate the number of bits of the SR. Specifically, the SR type setting information may be a flag corresponding to the number of bits of the SR. The SR type setting information according to the second modified example 1 will be described in detail with reference to FIG.

[0129] For example, in SchedulingRequestResourceConfig, 1bit_SR or 2bit_SR is set as SR type setting information. As shown in FIG. 16 , 1bit_SR is set to true in block 67A, and 2bit_SR is set to true in block 67B. When 1bit_SR and 2bit_SR exist or are set to true, they indicate that UE 200 is configured to transmit enhanced-SR. Conversely, when both 1bit_SR and 2bit_SR do not exist or are set to false, they indicate that UE 200 is not configured to transmit enhanced-SR, that is, is configured to transmit legacy SR. For example, in the example of FIG. 16 , 1bit_SR=true is set for schedulingRequestID=1, and 2bit_SR=true is set for schedulingRequestID=2. That is, the SR for schedulingRequestID=1 is transmitted using 1 bit, and the SR for schedulingRequestID=2 is transmitted using 2 bits.

[0130] The SR type setting information may indicate the number of SR bits or a value corresponding to the number of bits to indicate which type of SR to use. For example, if the SR type setting information has a value of 0, it indicates that the number of SR bits is 1, and if the SR type setting information has a value of 1, it indicates that the number of SR bits is 2.

[0131] Furthermore, as a second modified example 2 of this embodiment, the SR type setting information may be information used to indicate the type of UL data that triggers SR. For example, the type of UL data may be pose / control, video, etc. The SR type setting information according to the second modified example 2 will be described in detail with reference to FIG. 17.

[0132] For example, in SchedulingRequestResourceConfig, Pose / control or Video is set as the SR type setting information. As shown in FIG. 17, Pose / control is set to true in block 69A, and Video is set to true in block 69B. When Pose / control and Video exist or are set to true, this indicates that UE 200 is set to transmit enhanced-SR. Conversely, when both Pose / control and Video do not exist or are set to false, this indicates that UE 200 is not set to transmit enhanced-SR, i.e., is set to transmit legacy SR. For example, in the example of FIG. 17, Pose / control=true is set for schedulingRequestID=1, and Video=true is set for schedulingRequestID=2. That is, the SR for schedulingRequestID=1 is triggered when the type of UL data is Pose / control and is transmitted with 1 bit, and the SR for schedulingRequestID=2 is triggered when the type of UL data is Video and is transmitted with 2 bits.

[0133] In this way, according to the second modification 1 of the present embodiment, the SR type setting information may be information used to indicate the number of bits of the SR, which makes it possible to directly indicate the number of bits of the enhanced-SR.

[0134] Furthermore, according to the second modified example 2 of this embodiment, the SR type setting information may be information used to indicate the type of UL data that triggers SR. This allows different SR types to be used for different types of UL data. Therefore, the SR can indicate the characteristics of the buffered UL data to the base station 100 prior to the BSR. In particular, the characteristics of XR data vary greatly depending on the data type. Therefore, by scheduling according to the type of XR data at the time of scheduling according to SR, scheduling suitable for XR data becomes possible.

[0135] In the above, an example has been described in which the SR type setting information is included in SchedulingRequestResourceConfig, but the SR type setting information may be included in other setting information as described in the first modified example.

[0136] (3) Third Modification: Other Examples of SR Values In the above-described embodiment of the present disclosure, the second type of SR (i.e., enhanced-SR) corresponds to the type of UL data, but the enhanced-SR according to the embodiment of the present disclosure is not limited to this example.

[0137] As a third modification 1 of this embodiment, enhanced-SR may correspond to information roughly indicating the amount of UL data. Specifically, enhanced-SR corresponds to a range of UL data amounts that includes the amount of UL data to be transmitted. SR values ​​corresponding to information roughly indicating the amount of UL data will be described in detail with reference to Fig. 18. Fig. 18 shows an example of a 2-bit SR. Note that SR values ​​such as those in Table T3 of Fig. 18 may also be set for 1-bit SR.

[0138] For example, as shown in table T3 in Fig. 18, an SR value of 01 corresponds to a range of UL data volume ≦1000, and an SR value of 10 corresponds to a range of UL data volume >1000. Note that an SR value of 11 is undetermined. Also, the SR value may be expressed as values ​​such as small and large instead of the above-mentioned range of values.

[0139] Also, as a third modified example 2 of this embodiment, enhanced-SR may correspond to the type of BSR table. Specifically, enhanced-SR corresponds to the type of BSR table according to the buffered UL data. SR values ​​corresponding to the BSR table will be described in detail with reference to FIG. 19. FIG. 19 shows an example of a 2-bit SR. Note that SR values ​​such as those in table T4 of FIG. 19 may also be set for a 1-bit SR.

[0140] For example, as shown in table T4 in Fig. 19, BSR table 1 corresponds to SR value 01, and BSR table 2 corresponds to SR value 10. Note that SR value 11 is undetermined. For example, BSR table 1 is a table that can indicate buffer sizes from 0 to 1K bytes, and BSR table 2 is a table that can indicate buffer sizes of 1K bytes or more.

[0141] As described above, according to the third modification 1 of the present embodiment, enhanced-SR may correspond to information roughly indicating the amount of UL data. This allows the base station 100 to be notified of the approximate amount of UL data using SR. Therefore, at the time of scheduling according to SR, scheduling according to the approximate amount of UL data becomes possible. Furthermore, a BSR table corresponding to the approximate amount of UL data can be selected.

[0142] Furthermore, according to a third modification example 2 of this embodiment, enhanced-SR may correspond to the type of BSR table. This allows the type of BSR table corresponding to the buffered UL data to be indicated to base station 100 using SR. Therefore, at the time of scheduling according to SR, scheduling according to the buffered UL data estimated from the BSR table becomes possible. Also, it is possible to select a BSR table corresponding to the buffered UL data.

[0143] Note that a table indicating the correspondence between the SR value of the above-mentioned enhanced-SR and the range of the UL data amount or the BSR table may be set and referenced by the base station 100 and the UE 200. Furthermore, setting information of the table may be transmitted from the base station 100 to the UE 200.

[0144] (4) Fourth Variant: Compliance with Other TS In the above-described example of the embodiment of the present disclosure, the system 1 is a system that complies with 5G or NR TS. However, the system 1 according to the embodiment of the present disclosure is not limited to this example.

[0145] In a fourth modification of this embodiment, the system 1 may be a system compliant with other 3GPP TSs. As an example, the system 1 may be a system compliant with LTE (Long Term Evolution), LTE-A (LTE Advanced), or 4G TSs, and the base station 100 may be an eNB (evolved Node B). Alternatively, the base station 100 may be an ng-eNB. As another example, the system 1 may be a system compliant with 3G TSs, and the base station 100 may be a Node B. As yet another example, the system 1 may be a system compliant with next-generation (e.g., 6G) TSs.

[0146] Alternatively, the system 1 may be a system that complies with the TS of another standardization organization for mobile communications.

[0147] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely examples and that various modifications are possible without departing from the scope and spirit of the present disclosure.

[0148] For example, the steps in the processes described herein do not necessarily have to be performed in chronological order according to the order depicted in the flowcharts or sequence diagrams. For example, the steps in the processes may be performed in an order different from that depicted in the flowcharts or sequence diagrams, or may be performed in parallel. Furthermore, some of the steps in the processes may be deleted, and additional steps may be added to the processes.

[0149] For example, a method including the operation of one or more components of the apparatus described herein may be provided, or a program for causing a computer to execute the operation of the components may be provided. Also, a non-transitory tangible computer-readable storage medium having the program recorded thereon may be provided. Naturally, such methods, programs, and non-transitory tangible computer-readable storage media are also included in the present disclosure.

[0150] For example, one or more components of the base station described herein may be included in a module for the base station, or the module may be provided, i.e., a module for the base station that performs the processing for the base station described herein may be provided.

[0151] For example, one or more components of a user equipment (UE) described herein may be included in or provided as a module for the UE, i.e., a module for the UE that performs the processing for the UE described herein may be provided.

[0152] For example, in this disclosure, user equipment (UE) may be referred to by other names such as terminal apparatus, terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber device, subscriber unit, radio station, radio terminal, radio device, radio unit, wireless station, wireless terminal, wireless device, wireless unit, access station, access terminal, access device, access unit, remote station, remote terminal, remote device, or remote unit.

[0153] For example, in the present disclosure, a UE may be a mobile phone terminal such as a smartphone, a tablet terminal, a personal computer, a mobile router, or a wearable device. Alternatively, a UE may be a device installed in a mobile object, or the mobile object itself. The mobile object may be a vehicle such as a car or train, an air vehicle such as an airplane or drone, or another mobile object such as a ship. Alternatively, in the present disclosure, a UE may be other Internet of Things (IoT) devices such as sensors and cameras. The UE may be mobile or fixed.

[0154] For example, in the present disclosure, "transmit" may mean performing processing at least one layer in a protocol stack used for transmission, or may mean physically transmitting a signal wirelessly or via a wire. Alternatively, "transmit" may mean a combination of performing processing at least one layer and physically transmitting a signal wirelessly or via a wire. Similarly, "receive" may mean performing processing at least one layer in a protocol stack used for reception, or may mean physically receiving a signal wirelessly or via a wire. Alternatively, "receive" may mean a combination of processing at least one layer and physically receiving a signal wirelessly or via a wire. The at least one layer may be rephrased as at least one protocol.

[0155] For example, in this disclosure, "obtain / acquire" may mean obtaining information from stored information, obtaining information from information received from other nodes, or obtaining information by generating the information.

[0156] For example, in this disclosure, "include" and "comprise" do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items.

[0157] For example, in this disclosure, "or" does not mean an exclusive or, but rather a logical or.

[0158] The technical features included in the above-described embodiments may be expressed as the following features: Naturally, the present disclosure is not limited to the following features.

[0159] (Feature 1) a communication processing unit (233) that receives a message including setting information for specifying one of a plurality of types of scheduling requests, and transmits one of the plurality of types of scheduling requests specified based on the setting information; an information acquisition unit (231) that acquires the setting information included in the message; Equipped with the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. Equipment (200).

[0160] (Feature 2) The setting information is included in the setting information of the scheduling request. Feature 1. The device according to feature 1.

[0161] (Feature 3) The setting information is included in the setting information of the logical channel. Feature 1. The device according to feature 1.

[0162] (Feature 4) The configuration information is included in uplink control channel resource configuration information for the scheduling request. Feature 1. The device according to feature 1.

[0163] (Feature 5) The setting information is a flag corresponding to the plurality of types. The device according to any one of Features 1 to 4.

[0164] (Feature 6) The setting information is information used to indicate the number of bits of a scheduling request. The device according to any one of Features 1 to 4.

[0165] (Feature 7) The configuration information is information used to indicate the type of uplink data that triggers a scheduling request. The device according to any one of Features 1 to 4.

[0166] (Feature 8) In response to the second type of scheduling request, a table corresponding to the value of the buffer status report is selected. The device according to any one of Features 1 to 7.

[0167] (Feature 9) The second type of scheduling request corresponds to a type of uplink data. 9. The device according to feature 8.

[0168] (Feature 10) The second type of scheduling request corresponds to information roughly indicating the amount of uplink data. 9. The device according to feature 8.

[0169] (Feature 11) The second type of scheduling request corresponds to a type of table corresponding to the value of the buffer status report. 9. The device according to feature 8.

[0170] (Feature 12) The device is a user equipment or a module for a user equipment. The device according to any one of Features 1 to 11.

[0171] (Feature 13) an information acquisition unit (141) that acquires setting information for identifying one of a plurality of types of scheduling requests; a communication processing unit (143) that transmits a message including the setting information and receives one scheduling request out of a plurality of types identified based on the setting information; Equipped with the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. Equipment (100).

[0172] (Feature 14) The device is a base station or a module for a base station. 14. The device according to claim 13.

[0173] (Feature 15) A method performed by an apparatus (200), comprising: receiving a message including configuration information for identifying one of a plurality of types of scheduling requests, and transmitting a scheduling request of one of a plurality of types identified based on the configuration information; obtaining the setting information included in the message; Including, the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. method.

[0174] (Feature 16) A method performed by an apparatus (100), comprising: obtaining configuration information for identifying one of a plurality of types of scheduling requests; transmitting a message including the configuration information and receiving a scheduling request of one of a plurality of types identified based on the configuration information; Including, the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. method.

[0175] (Feature 17) receiving a message including configuration information for identifying one of a plurality of types of scheduling requests, and transmitting a scheduling request of one of a plurality of types identified based on the configuration information; obtaining the setting information included in the message; A program that causes a computer to execute the the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. program.

[0176] (Feature 18) obtaining configuration information for identifying one of a plurality of types of scheduling requests; transmitting a message including the configuration information and receiving a scheduling request of one of a plurality of types identified based on the configuration information; A program that causes a computer to execute the the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. program.

[0177] (Feature 19) receiving a message including configuration information for identifying one of a plurality of types of scheduling requests, and transmitting a scheduling request of one of a plurality of types identified based on the configuration information; obtaining the setting information included in the message; A non-transitory computer-readable recording medium on which a program for causing a computer to execute the above is recorded, the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. Non-transitive physical recording media.

[0178] (Feature 20) obtaining configuration information for identifying one of a plurality of types of scheduling requests; transmitting a message including the configuration information and receiving a scheduling request of one of a plurality of types identified based on the configuration information; A non-transitory computer-readable recording medium on which a program for causing a computer to execute the above is recorded, the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. Non-transitive physical recording media. [Explanation of symbols]

[0179] 1 System 100 base stations 141 Information Acquisition Department 143 First communication processing unit 145 Second communication processing unit 200 User Equipment 231 Information Acquisition Department 233 Communication Processing Unit

Claims

1. a communication processing unit (233) that receives a message including setting information for specifying one of a plurality of types of scheduling requests, and transmits one of the plurality of types of scheduling requests specified based on the setting information; an information acquisition unit (231) that acquires the setting information included in the message; Equipped with the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. Device (200).

2. The setting information is included in the setting information of the scheduling request.

10. The apparatus of claim 1.

3. The setting information is included in the setting information of the logical channel.

10. The apparatus of claim 1.

4. The configuration information is included in uplink control channel resource configuration information for the scheduling request.

10. The apparatus of claim 1.

5. The setting information is a flag corresponding to the plurality of types. The device according to any one of claims 1 to 4.

6. The setting information is information used to indicate the number of bits of a scheduling request. The device according to any one of claims 1 to 4.

7. The configuration information is information used to indicate the type of uplink data that triggers a scheduling request. The device according to any one of claims 1 to 4.

8. In response to the second type of scheduling request, a table corresponding to the value of the buffer status report is selected. The device according to any one of claims 1 to 4.

9. The second type of scheduling request corresponds to a type of uplink data.

9. The apparatus of claim 8.

10. The second type of scheduling request corresponds to information roughly indicating the amount of uplink data.

9. The apparatus of claim 8.

11. The second type of scheduling request corresponds to a type of table corresponding to the value of the buffer status report.

9. The apparatus of claim 8.

12. an information acquisition unit (141) that acquires setting information for identifying one of a plurality of types of scheduling requests; a communication processing unit (143) that transmits a message including the setting information and receives one scheduling request out of a plurality of types identified based on the setting information; Equipped with the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. Apparatus (100).

13. A method performed by an apparatus (200), comprising: receiving a message including configuration information for identifying one of a plurality of types of scheduling requests, and transmitting a scheduling request of one of a plurality of types identified based on the configuration information; obtaining the setting information included in the message; Including, the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. method.

14. A method performed by an apparatus (100), comprising: obtaining configuration information for identifying one of a plurality of types of scheduling requests; sending a message including the configuration information and receiving a scheduling request of one of a plurality of types identified based on the configuration information; Including, the plurality of types includes at least a first type and a second type; The second type of scheduling request corresponds to a value of a buffer status report used to provide information about the amount of uplink data. method.

Images