WO2024034307A1 - Device and method - Google Patents

Abstract

A device (200) according to one embodiment of the present disclosure comprises a communication processing unit (233) for receiving a message including configuration information for identifying one of a plurality of types of scheduling request, and transmitting the one of the plurality of types of scheduling request identified on the basis of the configuration information, and an information acquiring unit (231) for acquiring the configuration information included in the message, wherein: the plurality of types include 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 relating to an uplink data volume.

Description

Apparatus and method Cross-reference of related applications

This application is based on Japanese Application No. 2022-127463 filed on August 9, 2022, and the contents thereof are incorporated herein.

The present disclosure relates to apparatus and methods.

Mobile communication technology has been proposed in the 3GPP (3rd Generation Partnership Project) (registered trademark) and is defined in technical specifications (TS). In particular, currently, 5G (5th Generation) technology has been proposed and defined as TS.

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

Additionally, as described in Non-Patent Document 1, the UE transmits a buffer status report (BSR) to the base station to provide information about the amount of UL data. The BSR indicates the range of buffer sizes for UL data. Therefore, the base station can allocate communication resources according to the range of the UL data buffer size indicated by the BSR. Note that since BSR indicates a range of buffer sizes, there is a quantization error. Further, as described in Non-Patent Document 2, SR parameters and BSR parameters are set in the RRC (radio resource control) layer.

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

Here, in existing systems, there are fewer transmission opportunities for UL traffic than for downlink (DL) traffic. Furthermore, in UL data transmission, there are cases where the SR is first transmitted, then the BSR is transmitted, and then the UL data is transmitted. That is, UL data transmission can be made to wait until communication resources for UL data transmission are allocated by transmission of SR and BSR. On the other hand, XR services may have delay requirements (eg, packet delay budget: PDB). Therefore, existing systems that can wait for UL data transmission may have difficulty meeting the delay requirements of XR services.

As a countermeasure, Non-Patent Document 5 proposes extending the SR so that 1 or 2 bits of information corresponding to the BSR value can be provided. Specifically, instead of transmitting an unmodulated signal to indicate SR, it is possible to transmit a signal modulated by BPSK (binary phase shift keying) or QPSK (quadrature phase shift keying) as SR. ing. This makes it possible to fill the gap in buffer information between the SR where there is no buffer information for UL data and the BSR where detailed buffer information is provided. As a result, it is possible to improve the accuracy of UL data scheduling at the time of scheduling according to the SR. That is, the delay and waiting time of UL data transmission is reduced.

As a result of detailed study by the inventor, the following problems were discovered. That is, in non-patent literature, a concept of SR that is extended to provide information has been proposed, but no specific method has been proposed.

An object of the present disclosure is to provide an apparatus and method that can improve the accuracy of UL data scheduling at the time of scheduling according to SR.

A device (200) according to an aspect of the present disclosure receives a message including configuration information for identifying one of a plurality of types of scheduling requests, and a device (200) that receives a message including configuration information for identifying one of multiple types of scheduling requests, and a communication processing unit (233) that transmits one of the scheduling requests; and an information acquisition unit (231) that acquires the setting information included in the message, and the plurality of types include at least a first type. and a second type of scheduling request, wherein 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.

A device (100) according to an aspect 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 message that transmits a message including the configuration information. and a communication processing unit (143) that receives a scheduling request of one of a plurality of types specified based on the setting information, wherein the plurality of types are at least a first type and a second type. , wherein 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.

A method performed by an apparatus (200) according to an aspect of the present disclosure includes receiving a message including configuration information for identifying one of a plurality of types of scheduling requests, and determining the type of scheduling request based on the configuration information. transmitting a scheduling request of one of a plurality of types; 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 the amount of uplink data.

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

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, according to the present disclosure, other effects may be achieved instead of or in addition to this effect.

It is an explanatory diagram showing an example of UL data transmission. It is a diagram showing Short BSR. FIG. 3 is a diagram showing a table of buffer sizes. It is a diagram showing Long BSR. FIG. 1 is an explanatory diagram showing an example of a schematic configuration of a system according to an embodiment of the present disclosure. FIG. 1 is a block diagram illustrating an example of a schematic functional configuration of a base station according to an embodiment of the present disclosure. FIG. 1 is a block diagram illustrating an example of a schematic hardware configuration of a base station according to an embodiment of the present disclosure. FIG. 1 is a block diagram illustrating an example of a schematic functional configuration of a user device according to an embodiment of the present disclosure. FIG. 1 is a block diagram illustrating an example of a schematic hardware configuration of a user device according to an embodiment of the present disclosure. FIG. 2 is a diagram for explaining UL data transmission according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of setting information for specifying the type of SR according to an embodiment of the present disclosure. FIG. 3 is a diagram for explaining an example of SR values according to an embodiment of the present disclosure. FIG. 2 is a sequence diagram for explaining an example of a schematic flow of processing according to an embodiment of the present disclosure. It is a figure which shows the example of the setting information containing the said setting information based on the 1st modification 1 of embodiment of this indication. FIG. 7 is a diagram illustrating an example of setting information including the above setting information according to the first modification example 2 of the embodiment of the present disclosure. It is a figure which shows the example of the said setting information based on the 2nd modification 1 of embodiment of this indication. It is a figure which shows the example of the said setting information based on the 2nd modification 2 of embodiment of this indication. FIG. 7 is a diagram for explaining an example of an SR value according to a third modification example 1 of the embodiment of the present disclosure. FIG. 7 is a diagram for explaining an example of an SR value according to a third modification example 2 of the embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Note that, in this specification and the drawings, elements that can be explained in the same manner are designated by the same reference numerals, so that repeated explanation can be omitted.

The explanation will be given in the following order.
1. Related technology 2. System configuration 3. Base station configuration 4. Configuration of user equipment 5. Operation example 6. Variant

<1. Related technology＞
Scheduling requests (SR) and buffer status reports (BSR) will be described as technologies related to embodiments of the present disclosure.

(1) Scheduling request (SR)
The SR is used by the UE to request the base station to allocate communication resources for new UL transmissions. For example, the SR may be used to request uplink-shared channel (UL-SCH) resources for initial transmission. Here, the UL-SCH may be mapped to a physical uplink shared channel (PUSCH). In this embodiment, UL-SCH data is also referred to as UL data. As communication resources for the SR, a set of multiple BWPs (bandwidth parts) and/or physical uplink control channel (PUCCH) resources across cells is allocated. For each logical channel, at most one PUCCH resource is allocated for 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.

An example of UL transmission using SR will be described with reference to FIG. The UE triggers the SR when UL data arrives. SR is transmitted to the base station using PUCCH. The base station that receives the SR allocates resources for UL data transmission to the UE. UL resource allocation is sent to the UE using a physical downlink control channel (PDCCH). The UE that has received the UL resource assignment transmits UL data to the base station using the assigned PUSCH resource. BSR may also be transmitted along with the UL data. In this embodiment, UL resource allocation includes UL-SCH allocation and/or PUSCH resource allocation. In addition, the PUSCH resource assignment includes a PUSCH frequency domain resource assignment (frequency domain resource assignment) and/or a PUSCH time domain resource assignment (time domain resource assignment). For example, the base station may transmit downlink control information (DCI) used for PUSCH scheduling on the PDCCH. That is, the DCI may include information (one or more fields) for allocating PUSCH resources.

The parameters of the SR are set 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 configuration. The parameters of the SR may include SchedulingRequestConfig and/or SchedulingRequestResourceConfig. Further, the SR parameters may include schedulingRequestID, sr-ProhibitTimer, sr-TransMax, periodicityAndOffset, phy-PriorityIndex, and/or resource. 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) via a schedulingRequestID. schedulingRequestID may be used to identify the SR instance at the MAC layer. sr-ProhibitTimer may be used to set a timer for SR transmission on PUCCH. sr-TransMax may be used to set the maximum number of SR transmissions. periodicityAndOffset may be used to set the period and offset of the SR. The phy-PriorityIndex may be used to set the priority of SR resources in PHY layer prioritization or multiplexing. The parameter "resource" may be used to set the ID (identifier) of the PUCCH resource used for transmitting the SR. For example, a PUCCH resource corresponding to an ID of a PUCCH resource included in an SR parameter may be configured for SR transmission based on the SR parameter. PUCCH resources may be configured in PUCCH format 0 or PUCCH format 1, which includes information used to configure PUCCH resources.

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 the SR configuration to the UE. Further, the UE may receive an RRC message including the SR settings, and perform SR transmission based on the SR settings. Further, the UE may receive an RRC message including the SR configuration, and determine PUCCH resources used for transmitting the SR based on the SR configuration. For example, the RRC message may include an RRCReconfiguration message.

(2) Buffer status report (BSR)
The BSR procedure (also called buffer status reporting procedure) is used to provide information to the base station about the UL data volume at the UE. That is, the BSR is used in a procedure (buffer status reporting) for providing information regarding the UL data amount of a MAC entity to a base station. BSR is transmitted using a MAC CE (Control Element). That is, operations related to BSR may be performed and/or processed at a MAC layer (eg, MAC entity) in the UE. Additionally, operations related to BSR may be performed and/or processed at a MAC layer (eg, MAC entity) in a base station. In this embodiment, the upper layer includes a layer higher than the MAC layer. For example, the upper layer may include an RRC layer.

Parameters related to BSR are configured using RRC configuration information. BSR parameters include periodicBSR-Timer, retxBSR-Timer, logicalChannelSR-DelayTimerApplied, logicalChannelSR-DelayTimer, logicalChannelSR-Mask, and logicalChannelGroup. periodicBSR-Timer may be used to set a timer for the BSR period. retxBSR-Timer may be used to set a timer for BSR retransmissions. logicalChannelSR-DelayTimerApplied may be used to set whether to apply a delay timer for SR transmission on a logical channel. logicalChannelSR-DelayTimer may be used to set a delay timer for SR transmission on a logical channel. logicalChannelSR-Mask may be used to set the control of the SR trigger (that is, whether to set SR masking) when the configured grant is set. 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 to the UE including parameters related to BSR. The UE may also receive an RRC message that includes parameters related to the BSR, and perform reporting (i.e., transmission) of the BSR based on the parameters related to the BSR.

BSR is reported for each logical channel group (LCG). Each logical channel is assigned to any LCG by logicalChannelGroup indicating the ID of the LCG.

BSR may be triggered for an activated cell group when any of the following occurs: Note that, according to the following trigger mechanism, BSR is classified into Regular BSR corresponding to (A) and (C), Periodic BSR corresponding to (D), and Padding BSR corresponding to (B).
(A) UL data of logical channels belonging to any LCG becomes available to the MAC entity.
(B) A UL resource is allocated, and the number of padding bits of the UL resource is greater than or equal to the size of the BSR MAC CE.
(C) The period indicated by retxBSR-Timer has expired, and UL data is included in at least one of the logical channels belonging to any LCG.
(D) The period indicated by periodicBSR-Timer expires.

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

The Short BSR format 20A will be described with reference to FIGS. 2 and 3. The size of Short BSR is fixed. As shown in FIG. 2, the Short BSR has an LCG ID field and a Buffer Size field. The LCG ID field identifies the LCG ID that reports the buffer size. The size of the LCG ID field is 3 bits. The Buffer Size field identifies the total amount of data available on 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 the index corresponding to the buffer size in table T1 for the 5-bit Buffer Size field shown in FIG.

With reference to FIG. 4, the Long BSR format 20B will be explained. The size of Long BSR is variable. As shown in FIG. 4, the Long BSR has an LCGi field and a Buffer Size j field. LCGi is an LCG with the i-th ID, and the LCGi field indicates the existence of a Buffer Size field for LCGi. The LCGi field is set to 1 if the buffer size is reported, and 0 otherwise. Alternatively, the LCGi field may indicate whether the LCGi has data available. The Buffer Size j field identifies the total amount of data available on 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 an 8-bit Buffer Size field (not shown). Note that the Buffer Size j field is included in ascending order according to LCGi.

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

For example, for Regular BSR and Periodic BSR, if there are two or more LCGs with data available when the MAC PDU containing the BSR is built, Long BSR will be reported, otherwise Short BSR will be reported. Ru. Furthermore, for a MAC entity for which logicalChannelGroup-IABExt is configured by an upper layer, Extended Long BSR or Extended Short BSR may be reported.

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.

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

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

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

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

For example, the base station 100 communicates with a UE (for example, UE 200) using a RAN protocol stack. For example, the protocol stack includes RRC (radio resource control), SDAP (service data adaptation protocol), PDCP (packet data convergence protocol), RLC (radio link control), MAC (medium access control), and physical: PHY) layer protocols. Alternatively, the protocol stack may not include all of these protocols, but may include some of these protocols.

For example, the base station 100 is a gNB. The gNB is a node that provides NR user plane and control plane protocol terminations to the UE and is connected to the 5GC (5G Core Network) via the 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 termination for the UE and operates as a secondary node in EN-DC (E-UTRA-NR Dual Connectivity).

The base station 100 may include multiple nodes. The plurality of nodes may include a first node that hosts a higher layer included in the protocol stack and a second node that hosts a lower layer included in the protocol stack. good. The upper layer may include RRC, SDAP, and PDCP, and the lower layer may include RLC, MAC, and PHY layer. The first node may be a CU (central unit), and the second node may be a DU (distributed unit). Note that the plurality of 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 an RU (radio unit).

Alternatively, the base station 100 may be one of the plurality of nodes, or may be connected to another unit among the plurality of nodes.

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

(2) UE200
UE 200 communicates with a base station. For example, the UE 200 communicates with the base station 100 when located within the coverage area 10 of the base station 100.

For example, the UE 200 communicates with a base station (for example, the base station 100) using the above protocol stack.

In addition, the UE 200 performs <1. SR and BSR as described in ``Related Techniques'' are transmitted to the base station. Further, the UE 200 may be a device that supports an XR service (in other words, an XR scenario).

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

(1) Functional Configuration First, with reference to FIG. 6, an example of the functional configuration of the base station 100 according to the embodiment of the present disclosure will be described. Referring to FIG. 6, the base station 100 includes a wireless communication section 110, a network communication section 120, a storage section 130, and a processing section 140.

The wireless communication unit 110 transmits and receives signals wirelessly. For example, the wireless communication unit 110 receives a signal from a UE and transmits a signal to the UE.

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

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

The processing unit 140 provides various functions of the base station 100. The processing section 140 includes an information acquisition section 141, a first communication processing section 143, and a second communication processing section 145. Note that the processing unit 140 may further include components other than these components. That is, the processing unit 140 can perform operations other than those of these components. Specific operations of the information acquisition section 141, first communication processing section 143, and second communication processing section 145 will be explained in detail later.

For example, the processing unit 140 (first communication processing unit 143) communicates with a UE (for example, UE 200) via the wireless communication unit 110. For example, the processing unit 140 (second communication processing unit 145) communicates with other nodes (for example, a network node in the core network or another base station) via the network communication unit 120.

(2) Hardware Configuration Next, with reference to FIG. 7, an example of the hardware configuration of the base station 100 according to the embodiment of the present disclosure will be described. 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.

The antenna 181 converts the signal into radio waves and radiates the radio waves into space. Further, the antenna 181 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 transmitting and receiving. Antenna 181 may be a directional antenna and may include multiple antenna elements.

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

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

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 the RAN protocol stack. Processor 187 also processes signals sent and received via network interface 185. Processor 187 may include multiple processors or may be a single processor. The plurality of processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

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

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

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

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

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

<4. User equipment 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. 8 and 9.

(1) Functional Configuration First, with reference to FIG. 8, an example of the functional configuration of the UE 200 according to the embodiment of the present disclosure will be described. Referring to FIG. 8, the UE 200 includes a wireless communication section 210, a storage section 220, and a processing section 230.

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 a signal to the base station. For example, the wireless communication unit 210 receives signals from other UEs and transmits signals to other UEs.

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

The processing unit 230 provides various functions of the UE 200. The processing section 230 includes an information acquisition section 231 and a communication processing section 233. Note that the processing unit 230 may further include components other than these components. That is, the processing unit 230 can perform operations other than those of these components. Specific operations of the information acquisition unit 231 and communication processing unit 233 will be explained in detail later.

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

(2) Hardware Configuration Next, with reference to FIG. 9, an example of the hardware configuration of the UE 200 according to the embodiment of the present disclosure will be described. 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.

The antenna 281 converts the signal into radio waves and radiates the radio waves into space. Further, the antenna 281 receives radio waves in space and converts the radio waves into signals. Antenna 281 may include a transmit antenna and a receive antenna, or may be a single antenna for transmitting and receiving. Antenna 281 may be a directional antenna and may include multiple antenna elements.

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

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

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

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

The wireless communication unit 210 may be implemented by an antenna 281 and an RF circuit 283. Storage unit 220 may be implemented by storage 289. Processing unit 230 may be implemented by processor 285 and memory 287.

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

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

<5. Operation example>
As mentioned above, existing mobile communication systems that can wait for UL data transmission may have difficulty meeting the delay requirements of XR services. The above will be described in detail with reference to FIG.

A case in which UL data is transmitted will be explained using the following procedure. First, the UE transmits PUCCH for SR. The UE then transmits a PUSCH to report the BSR. The UE then transmits a PUSCH for UL data, scheduled according to the BSR.

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

In the example of FIG. 10, the UL-DL setting is DDDDU. Therefore, the above SR, BSR, and UL data are transmitted at UL transmission opportunities set every 5 slots. In the example of FIG. 10, there is a time lag of at least 10 slots from when UL data arrives until it is transmitted. This corresponds to a delay of at least 10 ms when the SCS (subcarrier spacing) is 15 kHz. As a result, XR data can be large, making it difficult for the UE to meet delay requirements.

In contrast, in an embodiment of the present disclosure, a message including configuration information for identifying one of multiple types of SR (hereinafter also referred to as SR type configuration information) is sent and received, and the configuration information is One SR of a plurality of types specified based on the information is transmitted and received. The plurality of types include at least a first type and a second type, and the second type of SR corresponds to the value of the BSR. As a result, it is possible to set an SR that is extended to provide 1 or 2 bits of information corresponding to the BSR value, and it is possible to improve the accuracy of UL data scheduling at the time of scheduling according to the SR. can.

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. 11 to 13.

(1) SR Type Setting Information Setting information for specifying one of multiple types of SR is defined. The plurality of 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 the value of BSR used to provide information about the amount of UL data. The first type of SR is unmodulated and does not provide information other than scheduling requests. 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 scheduling requests.

The SR type setting information is included in the SR setting information. Thereby, SR type setting information is set for each SR. Since each SR corresponds to communication resources associated with each SR, it can also be said that SR type configuration information is set for communication resources associated with each SR.

SR type setting information will be explained in detail with reference to FIG. 11. FIG. 11 shows an example of configuration information including SR type configuration information and relationships between various types of configuration information. As shown in FIG. 11, LogicalChannelConfig (blocks 41A to 41C) is logical channel configuration information, SchedulingRequestConfig (blocks 51A to 51B) is SR configuration information, and SchedulingRequestResourceConfig (block 61A-61B) are associated via schedulingRequestID. Further, PUCCH-Resource (block 71A), which is the configuration information of the PUCCH resource, is associated with SchedulingRequestResourceConfig (block 61B) via PUCCH-ResourceId.

SR type configuration information is included in SchedulingRequestResourceConfig. For example, as shown in blocks 61A and 61B of 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 be included in SchedulingRequestConfig that is also set for schedulingRequestID.

Additionally, the SR type setting information is a flag corresponding to multiple SR types. For example, as shown in blocks 61A and 61B of FIG. 11, Sr-Type, if present, indicates that the UE 200 is configured to transmit enhanced-SR. On the other hand, if Sr-Type does not exist, it indicates that the UE 200 is not configured to transmit enhanced-SR, that is, it is configured to transmit legacy SR. Further, the SR type configuration information may indicate which SR type is used by a value. For example, when the value of Sr-Type is 0, it indicates that a 1-bit SR is used, and when the value is 1, it indicates that a 2-bit SR is used.

For example, in the example of FIG. 11, Sr-Type=0 is set for schedulingRequestID=1, and Sr-Type=1 is set for schedulingRequestID=2. That is, an SR with schedulingRequestID=1 is transmitted with 1 bit, and an SR with schedulingRequestID=2 is transmitted with 2 bits.

Note that the SR type configuration information is also associated with logical channel configuration information via the SR ID.

(2) SR Value The second type of SR (ie, enhanced-SR) according to the present 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.

Here, the BSR is used to provide information about the amount of UL data, for example, buffer size information of UL data. However, the buffer size may vary depending on the type of UL data. Therefore, depending on the type of UL data, the values reported in the BSR may also change. Furthermore, as a countermeasure, it is also possible to change the table of values reported in BSR according to the type of UL data, as will be described later.

Therefore, enhanced-SR according to this embodiment corresponds to the type of UL data. Thereby, the approximate buffer size (that is, the amount of UL data) according to the type of UL data can be indicated to the base station 100 in advance of the BSR.

With reference to FIG. 12, the SR values corresponding to the types of UL data will be explained in detail. FIG. 12 shows an example of 2-bit SR. Note that an SR value such as that shown in table T2 in FIG. 12 may also be set for the 1-bit SR.

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 the SR value 11 is undetermined.

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

(3) Message Containing Setting Information SR type setting information according to this embodiment is transmitted while being included in a message. The message may be an RRC message.

For example, SR type configuration information is sent in an RRC message that includes SchedulingRequestResourceConfig. The RRC message may be, for example, RRCReconfiguration, RRCResume, or RRCSetup. Further, an RRC message different from the above RRC message may be used.

(4) Operation of UE 200 The UE 200 according to this embodiment receives the SR type setting information according to this embodiment. UE 200 acquires configuration information from the received message including SR type configuration information. The UE 200 identifies the type of SR to be used from among multiple types based on the acquired SR type setting information.

Specifically, the UE 200 identifies the SR type based on the SR type setting information obtained 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. UE 200 transmits the selected type of SR at the SR transmission timing.

The UE 200 may select the SR type at the SR transmission timing. For example, when the SR type configuration information is included in SchedulingRequestResourceConfig, the UE 200 transmits the SR based on the SR type configuration information at the timing of transmitting the SR using the communication resource associated with the SchedulingRequestResourceConfig (that is, the timing indicated by the period and offset). Identify the type.

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

Multiple BSR tables may be defined, and the buffer size ranges that can be indicated by the multiple BSR tables may be different. Further, the range or granularity of buffer sizes corresponding to the indexes of each of the plurality of 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 Kbytes or more are defined. Further, for example, a table in which the buffer size range corresponding to index 1 is ≦10 and a table in which the buffer size range corresponding to the same index 1 is ≦20 are defined.

A BSR table to be used is selected from a plurality of BSR tables depending on the type of UL data. For example, the UE 200 selects a BSR table according to the type of UL data indicated by enhanced-SR, as shown in FIG. 12. When the type of buffered UL data is video, enhanced-SR indicates a value of 10 corresponding to video, and a BSR table that can indicate a buffer size of 1 Kbytes or more corresponding to video is selected. Additionally, if the type of buffered UL data is pose/control, enhanced-SR should indicate the value 01 corresponding to pose/control and indicate the buffer size from 0 to 1K bytes corresponding to pose/control. A BSR table that can perform the following is selected. UE 200 transmits the BSR using the selected BSR table.

Note that the base station 100 may select a BSR table depending on the received enhanced-SR. The method of selecting the BSR table is substantially the same as that of the UE 200, so a description thereof will be omitted. Further, a BSR table may be selected based on SR type setting information.

(5) Process Flow An example of the process according to this embodiment will be described with reference to FIG. 13.

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

The base station 100 transmits an RRC message including 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) that includes SchedulingRequestResourceConfig with Sr-Type set.

Upon receiving 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, upon receiving an RRC message including SchedulingRequestResourceConfig with Sr-Type set, the UE 200 transmits a response RRC message (for example, RRCReconfigurationComplete, RRCResumeComplete, or RRCSetupComplete) to the base station 100.

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

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 2-bit SR as the second SR to the base station 100. Furthermore, the UE 200 selects a BSR table depending on the transmitted 1-bit SR or 2-bit SR.

As described above, according to the embodiment of the present disclosure, a message including configuration information for identifying one of a plurality of types of SR is transmitted and received, and a message is transmitted and received that includes configuration information for identifying one of multiple types of SR, and one SR of the BSR used to provide information about the amount of UL data is transmitted and received, the plurality of types includes at least a first type and a second type, and the second type of SR is a BSR used to provide information about the amount of UL data. corresponds to the value of . This allows setting of an SR that is extended to provide 1 or 2 bits of information corresponding to the BSR value. That is, it is possible to improve the accuracy of UL data scheduling at the time of scheduling according to SR.

Additionally, the above setting information is included in the SR setting information. Thereby, the above setting information can be set for each SR (for example, the ID of the SR or the communication resource associated with the SR).

Additionally, the setting information is a flag corresponding to the plurality of types. Thereby, the above setting information can be handled with a small amount of data. Therefore, an increase in communication resources for signaling the configuration information can be suppressed.

Also, depending on the second type of SR, a table corresponding to the value of the BSR is selected. This makes it possible to dynamically select a BSR table using the SR without adding information to the BSR. In particular, since XR data can vary greatly in size depending on the type, scheduling efficiency can be improved by dynamically changing the values reported in the BSR and the table corresponding to the values.

Furthermore, the second type of SR corresponds to the UL data type. This allows the type of buffered UL data to be indicated to the base station 100 using the SR. Therefore, at the time of scheduling according to the SR, scheduling can be performed according to the amount of UL data estimated from the type of UL data. Additionally, a BSR table corresponding to the type of UL data can be selected.

<6. Modified example>
First to fourth modifications of the first embodiment of the present disclosure will be described with reference to FIGS. 14 to 19. Note that two or more of these modifications may be combined.

(1) First modification: Another example of configuration information including SR type configuration information In the embodiment of the present disclosure described above, the SR type configuration information is included in the SR configuration information. However, the configuration information including the SR type configuration information according to the embodiment of the present disclosure is not limited to this example.

As a first modification of the present embodiment, the SR type setting information may be included in the logical channel setting information. The logical channel configuration information is associated with the SR configuration information via the SR ID. Therefore, it can be said that the SR type setting information is set for the SR while being included in the logical channel setting information. The SR type setting information included in the logical channel setting information will be described in detail with reference to FIG. 14.

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. A LogicalChannelConfig includes a schedulingRequestID, and a 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 whose schedulingRequestID is 1, Sr-Type is set to 0, and in block 43C whose schedulingRequestID is 2, Sr-Type is set to 1.

The UE 200 refers to the SR type setting information set for the logical channel of the UL data for which the SR has been triggered, and identifies the type of the SR. For example, when the UL data of the logical channel of the block 43A shown in FIG. 14 is buffered and the SR is triggered for the UL data, the UE 200 refers to the block 43A. In block 43A, since Sr-Type is set and its value is 0, UE 200 selects 1-bit SR as the type of SR.

Furthermore, as the first modification example 2 of the present embodiment, the SR type configuration information may be included in the configuration information of the UL control channel resource for the SR. The UL control channel may be PUCCH. PUCCH resource configuration information is associated with SR configuration information via the PUCCH resource ID. Therefore, it can be said that SR type configuration information is configured for PUCCH resources. The SR type configuration information included in the PUCCH resource configuration information will be described in detail with reference to FIG. 15.

SR type setting information is included in PUCCH-Resource. For example, as shown in block 75A of 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 will be set for PUCCH-ResourceId. For example, in the example of FIG. 15, a block 75A whose Sr-Type is 1 and a block 65B whose schedulingRequestID is 2 are associated via a certain PUCCH-ResourceId. On the other hand, although not shown, the PUCCH-Resource whose Sr-Type is 0 and the block 65A whose schedulingRequestID is 1 may be associated via another PUCCH-ResourceId.

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

As described above, according to the first modification of the present embodiment, the SR type setting information may be included in the logical channel setting information. Thereby, the SR type setting information can be set using the logical channel setting information. For example, even if it is difficult to add parameters to the SR configuration information, SR type configuration information can be configured for each SR.

Furthermore, according to the first modification example 2 of the present embodiment, the SR type configuration information may be included in the configuration information of the UL control channel resource for the SR. Thereby, SR type setting information can be set for the UL control channel resource for SR. Therefore, SR type configuration information can be configured depending on the selection of the UL control channel resource associated with the SR. Furthermore, even if it is difficult to add parameters to the SR configuration information, the SR type configuration information can be indirectly configured for each SR.

(2) Second Modification: Other Examples of SR Type Setting Information In the embodiment of the present disclosure described above, 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.

As a second modification example 1 of the present 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 modification 1 will be described in detail with reference to FIG. 16.

For example, 1bit_SR or 2bit_SR is set as the SR type setting information in SchedulingRequestResourceConfig. As shown in FIG. 16, 1bit_SR is set to true in block 67A, and 2bit_SR is set to true in block 67B. 1bit_SR and 2bit_SR, if present or set to true, indicate that the UE 200 is configured to transmit enhanced-SR. Conversely, if both 1bit_SR and 2bit_SR are absent or set to false, it is indicated that the UE 200 is not configured to transmit enhanced-SR, that 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, an SR with schedulingRequestID=1 is transmitted with 1 bit, and an SR with schedulingRequestID=2 is transmitted with 2 bits.

Note that the SR type setting information may indicate which SR type is used by indicating the number of bits of the SR or a value corresponding to the number of bits. For example, when the value of the SR type setting information is 0, it indicates that the number of bits of the SR is 1, and when the value is 1, it indicates that the number of bits of the SR is 2.

Furthermore, as a second modification of the present 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 or video. With reference to FIG. 17, the SR type setting information according to the second modified example 2 will be described in detail.

For example, Pose/control or Video is set as the SR type setting information in SchedulingRequestResourceConfig. As shown in FIG. 17, Pose/control is set to true in block 69A, and Video is set to true in block 69B. Pose/control and Video, if present or set to true, indicate that the UE 200 is configured to transmit enhanced-SR. Conversely, if both Pose/control and Video are absent or set to false, it indicates that the UE 200 is not configured to transmit enhanced-SR, that is, configured 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, an SR with schedulingRequestID=1 is triggered and sent with 1 bit when the UL data type is Pose/control, and an SR with schedulingRequestID=2 is triggered and sent with 2 bits when the UL data type is Video. Sent in

As described above, according to the second modification example 1 of the present embodiment, the SR type setting information may be information used to indicate the number of bits of the SR. This allows the number of bits of enhanced-SR to be directly indicated.

According to the second modification example 2 of the present embodiment, the SR type setting information may be information used to indicate the type of UL data that triggers SR. This allows different types of SR to be used for each type of UL data. Therefore, the SR can indicate the characteristics of the buffered UL data to the base station 100 before 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.

Note that, although the example in which the SR type configuration information is included in SchedulingRequestResourceConfig has been described above, the SR type configuration information may be included in other configuration information as described in the first modification.

(3) Third modification: other examples of SR values In the embodiment of the present disclosure described above, the second type of SR (i.e., enhanced-SR) corresponds to the type of UL data. However, enhanced-SR according to the embodiment of the present disclosure is not limited to this example.

As a third modification example 1 of the present embodiment, enhanced-SR may correspond to information roughly indicating the amount of UL data. Specifically, enhanced-SR corresponds to a range of UL data amount that includes the amount of UL data to be transmitted. With reference to FIG. 18, the SR value corresponding to information roughly indicating the amount of UL data will be described in detail. FIG. 18 shows an example of 2-bit SR. Note that an SR value such as that shown in table T3 in FIG. 18 may also be set for the 1-bit SR.

For example, as shown in table T3 in FIG. 18, SR value 01 is associated with UL data amount range of ≦1000, and SR value 10 is associated with UL data amount range of >1000. Note that the SR value 11 is undetermined. Further, the SR value may be expressed by values such as small and large instead of the range of numerical values as described above.

Furthermore, as a third modification 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 depending on the UL data being buffered. The SR values corresponding to the BSR table will be described in detail with reference to FIG. 19. FIG. 19 shows an example of 2-bit SR. Note that an SR value like the table T4 in FIG. 19 may be set for the 1-bit SR as well.

For example, as shown in table T4 in FIG. 19, SR value 01 is associated with BSR table 1, and SR value 10 is associated with BSR table 2. Note that the SR value 11 is undetermined. For example, BSR table 1 is a table that can indicate buffer sizes from 0 to 1 Kbytes, and BSR table 2 is a table that can indicate buffer sizes of 1 Kbytes or more.

In this way, according to the third modification example 1 of the present embodiment, enhanced-SR may correspond to information roughly indicating the amount of UL data. This allows the approximate amount of UL data to be indicated to the base station 100 using the SR. Therefore, at the time of scheduling according to the SR, it is possible to perform scheduling according to the approximate amount of UL data. Furthermore, it is possible to select a BSR table that corresponds to the approximate amount of UL data.

According to the third modification example 2 of the present embodiment, enhanced-SR may correspond to the type of BSR table. Thereby, the type of BSR table corresponding to the buffered UL data can be indicated to the base station 100 using the SR. Therefore, at the time of scheduling according to the SR, scheduling can be performed according to the buffered UL data estimated from the BSR table. Furthermore, it is possible to select a BSR table according to the buffered UL data.

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

(4) Fourth modification: Compliance with other TSs 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.

In a fourth modification of the present embodiment, the system 1 may be a system compliant with another 3GPP TS. As an example, the system 1 may be a system compliant with LTE (Long Term Evolution), LTE-A (LTE Advanced), or 4G TS, and the base station 100 may be an eNB (evolved Node B). good. Alternatively, base station 100 may be an ng-eNB. As another example, the system 1 may be a 3G TS-compliant system, and the base station 100 may be a NodeB. As yet another example, the system 1 may be a system compliant with next generation (eg, 6G) TS.

Alternatively, the system 1 may be a system that complies with the TS of another standardization organization regarding mobile communications.

Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the embodiments. It will be understood by those skilled in the art that the embodiments are exemplary only and that various modifications can be made without departing from the scope and spirit of the disclosure.

For example, the steps in the process described in this specification do not necessarily have to be executed in chronological order in the order described in the flowchart or sequence diagram. For example, steps in a process may be performed in a different order than depicted in a flowchart or sequence diagram, or may be performed in parallel. Also, some of the steps in the process may be deleted, and additional steps may be added to the process.

For example, a method may be provided that includes operations of one or more components of the apparatus described herein, and a program may be provided that causes a computer to perform the operations of the components. Further, a computer-readable non-transitional physical recording medium may be provided on which the program is recorded. Of course, such methods, programs, and non-transitory tangible computer-readable storage media are also included in this disclosure.

For example, one or more components of a base station described herein may be included in or provided with a module for the base station. That is, a base station module that performs the base station processing described in this specification may be provided.

For example, one or more components of a user equipment (UE) described herein may be included in or provided with a module for the UE. That is, a UE module that performs the UE processing described in this specification may be provided.

For example, in the present disclosure, user equipment (UE) may refer to a terminal apparatus, a terminal, a mobile station, a mobile terminal, a mobile device, a mobile unit, a subscriber station, a subscriber terminal, subscriber equipment, 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.

For example, in the present disclosure, the 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, the UE may be a device installed in a mobile body, or may be the mobile body itself. The moving object may be a vehicle such as a car and a train, a flying object such as an airplane or a drone, or another moving object such as a ship. Alternatively, in the present disclosure, the UE may be other IoT (Internet of Things) devices such as sensors and cameras. A UE may be mobile or fixed.

For example, in this disclosure, "transmit" may mean performing at least one layer of processing within a protocol stack used for transmission, or transmitting a signal wirelessly or by wire to a physical It may also mean sending to. Alternatively, "transmitting" may mean a combination of processing the at least one layer and physically transmitting the signal wirelessly or by wire. Similarly, "receive" may mean processing at least one layer within the protocol stack used for receiving, or physically receiving a signal, wirelessly or by wire. It can also mean that. Alternatively, "receiving" may mean a combination of processing the at least one layer and physically receiving the signal wirelessly or by wire. The at least one layer may be translated into at least one protocol.

For example, in this disclosure, "obtain/acquire" may mean obtaining information from among stored information, or obtaining information from among information received from other nodes. It may also mean to obtain the information by generating the information.

For example, in this disclosure, "include" and "comprise" do not mean including only the listed items, and may include only the listed items, or may include only the listed items, or This means that it may contain further items in addition to.

For example, in the present disclosure, "or" does not mean an exclusive OR, but a logical OR.

Note that the technical features included in the embodiments described above may be expressed as the following features. Of course, the present disclosure is not limited to the following features.

(Feature 1)
A communication processing unit ( 233) and
an information acquisition unit (231) that acquires the setting information included in the message;
Equipped with
The plurality of types include 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. The apparatus (200).

(Feature 2)
The device according to feature 1, wherein the configuration information is included in configuration information of a scheduling request.

(Feature 3)
The device according to feature 1, wherein the configuration information is included in logical channel configuration information.

(Feature 4)
The apparatus according to feature 1, wherein the configuration information is included in configuration information of uplink control channel resources for scheduling requests.

(Feature 5)
The device according to any one of features 1 to 4, wherein the setting information is a flag corresponding to the plurality of types.

(Feature 6)
The device according to any one of features 1 to 4, wherein the configuration information is information used to indicate the number of bits of a scheduling request.

(Feature 7)
The apparatus according to any one of features 1 to 4, wherein the configuration information is information used to indicate a type of uplink data that triggers a scheduling request.

(Feature 8)
8. The apparatus of any one of features 1-7, wherein a table corresponding to a value of the buffer status report is selected in response to the second type of scheduling request.

(Feature 9)
9. The apparatus of feature 8, wherein the second type of scheduling request corresponds to a type of uplink data.

(Feature 10)
The apparatus according to feature 8, wherein the second type of scheduling request corresponds to information roughly indicating the amount of uplink data.

(Feature 11)
9. The apparatus of feature 8, wherein the second type of scheduling request corresponds to a type of table that corresponds to a value of the buffer status report.

(Feature 12)
The device according to any one of features 1 to 11, wherein the device is a user equipment or a module for a user equipment.

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

(Feature 14)
14. The device according to feature 13, wherein the device is a base station or a module for a base station.

(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 the multiple types identified based on the configuration information;
obtaining the configuration information included in the message;
including;
The plurality of types include 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 uplink data amount.

(Feature 16)
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 one of a plurality of types of scheduling requests identified based on the configuration information;
including;
The plurality of types include 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 uplink data amount.

(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 the multiple types identified based on the configuration information;
obtaining the configuration information included in the message;
A program that causes a computer to execute
The plurality of types include at least a first type and a second type,
The second type of scheduling request corresponds to the value of a buffer status report used to provide information about the amount of uplink data.

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

(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 the multiple types identified based on the configuration information;
obtaining the configuration information included in the message;
A computer-readable non-transitional physical recording medium that records a program that causes a computer to execute,
The plurality of types include at least a first type and a second type,
The second type of scheduling request corresponds to the value of a buffer status report used to provide information about the amount of uplink data on a non-transitive physical storage medium.

(Feature 20)
obtaining configuration information for identifying one of a plurality of types of scheduling requests;
Sending a message including the configuration information and receiving one of a plurality of types of scheduling requests identified based on the configuration information;
A computer-readable non-transitional physical recording medium that records a program that causes a computer to execute,
The plurality of types include at least a first type and a second type,
The second type of scheduling request corresponds to the value of a buffer status report used to provide information about the amount of uplink data on a non-transitive physical storage medium.

Claims (14)

1. A communication processing unit ( 233) and
   an information acquisition unit (231) that acquires the setting information included in the message;
   Equipped with
   The plurality of types include 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. The apparatus (200).
2. The device according to claim 1, wherein the configuration information is included in configuration information of a scheduling request.
3. The apparatus according to claim 1, wherein the configuration information is included in logical channel configuration information.
4. The apparatus according to claim 1, wherein the configuration information is included in configuration information of uplink control channel resources for scheduling requests.
5. The apparatus according to claim 1, wherein the setting information is a flag corresponding to the plurality of types.
6. The apparatus according to any one of claims 1 to 4, wherein the configuration information is information used to indicate the number of bits of a scheduling request.
7. The apparatus according to any one of claims 1 to 4, wherein the configuration information is information used to indicate the type of uplink data that triggers a scheduling request.
8. The apparatus according to any one of claims 1 to 4, wherein a table corresponding to the value of the buffer status report is selected in response to the second type of scheduling request.
9. 9. The apparatus of claim 8, wherein the second type of scheduling request corresponds to a type of uplink data.
10. 9. The apparatus of claim 8, wherein the second type of scheduling request corresponds to information roughly indicating the amount of uplink data.
11. 9. The apparatus of claim 8, wherein the second type of scheduling request corresponds to a type of table that corresponds to a value of the buffer status report.
12. an information acquisition unit (141) that acquires configuration information for identifying one of the plurality of types of scheduling requests;
    a communication processing unit (143) that transmits a message including the configuration information and receives a scheduling request of one of a plurality of types specified based on the configuration information;
    Equipped with
    The plurality of types include at least a first type and a second type,
    The second type of scheduling request corresponds to the value of a buffer status report used to provide information about the amount of uplink data. The 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 the multiple types identified based on the configuration information;
    obtaining the configuration information included in the message;
    including;
    The plurality of types include 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 uplink data amount.
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 one of a plurality of types of scheduling requests identified based on the configuration information;
    including;
    The plurality of types include 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 uplink data amount.