WO2024034306A1 - 装置及び方法 - Google Patents

装置及び方法 Download PDF

Info

Publication number
WO2024034306A1
WO2024034306A1 PCT/JP2023/025358 JP2023025358W WO2024034306A1 WO 2024034306 A1 WO2024034306 A1 WO 2024034306A1 JP 2023025358 W JP2023025358 W JP 2023025358W WO 2024034306 A1 WO2024034306 A1 WO 2024034306A1
Authority
WO
WIPO (PCT)
Prior art keywords
bsr
field
logical channel
information
configuration information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2023/025358
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
樹 長野
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Corp
Original Assignee
Denso Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Denso Corp filed Critical Denso Corp
Priority to JP2024540318A priority Critical patent/JPWO2024034306A1/ja
Priority to EP23852289.0A priority patent/EP4572391A4/en
Priority to CN202380058412.8A priority patent/CN119678543A/zh
Publication of WO2024034306A1 publication Critical patent/WO2024034306A1/ja
Priority to US19/045,154 priority patent/US20250185102A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to apparatus and methods.
  • a base station allocates communication resources for uplink (UL) transmission to user equipment (UE).
  • UE user equipment
  • a user equipment transmits a scheduling request (SR) to a base station to request communication resource allocation for the UL transmission.
  • SR scheduling request
  • the user equipment transmits UL data to the base station using the allocated communication resources.
  • the UE transmits a buffer status report (BSR) to the base station to provide information about the amount of UL data.
  • BSR buffer status report
  • 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.
  • RRC radio resource control
  • Non-Patent Documents 3 to 5 it has been proposed to apply the above mobile communication system to XR (extended reality) services.
  • the data of the XR service is characterized by large volume and high variability. Therefore, communication resources are wasted and scheduling becomes inefficient due to quantization errors in BSR.
  • Non-Patent Document 3 proposes determining a precise buffer size through BSR.
  • XR services may have delay requirements (eg, packet delay budget: PDB).
  • PDB packet delay budget
  • Non-Patent Document 4 proposes to satisfy the PDB by including delay information in the BSR and performing scheduling in consideration of the delay.
  • 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)” 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)” 3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203607, “Discussion on XR specific capacity enhancements techniques” 3GPP TSG-RAN WG1 Meeting #109-e, Online, May 9th - 20th, 2022, R1-2203639, “Discussion on capacity enhancements for XR” 3GPP TSG WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203928, “Considerations on XR
  • An object of the present disclosure is to provide an apparatus and method that can improve the efficiency of UL data scheduling using BSR.
  • An apparatus (200) sends a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field.
  • the buffer status report includes a communication processing unit (233) that receives the information, and an information acquisition unit (231) that acquires the configuration information included in the message, and the buffer status report is configured to provide information about the amount of uplink data.
  • the at least one first field indicates at least one logical channel group for which buffer status is to be reported
  • the at least one modified second field corresponds to the at least one logical channel group; Regarding uplink data amount.
  • An apparatus (100) obtains configuration information for determining whether to use a buffer status report that includes at least one first field and at least one modified second field.
  • the buffer status report is used to provide information about the amount of uplink data;
  • one first field indicates at least one logical channel group for which the buffer status is reported;
  • said at least one modified second field corresponds to said at least one logical channel group and is related to the uplink data amount.
  • a method performed by an apparatus (200) includes configuration information for determining whether to use a buffer status report that includes at least one first field and at least one modified second field. and obtaining the configuration information included in the message, wherein the buffer status report is used to provide information about an amount of uplink data, and the buffer status report is used to provide information about an amount of uplink data,
  • a first field indicates at least one logical channel group for which buffer status is reported, and said at least one modified second field corresponds to said at least one logical channel group and relates to an amount of uplink data.
  • a method performed by an apparatus (100) includes configuration information for determining whether to use a buffer status report that includes at least one first field and at least one modified second field. and transmitting a message including the configuration information, wherein the buffer status report is used to provide information about an amount of uplink data, and the at least one first field is , indicating at least one logical channel group for which buffer status is reported, said at least one modified second field corresponding to said at least one logical channel group and relating to an amount of uplink data.
  • FIG. 1 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 illustrating an example of a BSR according to the first embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of setting information for determining whether to use BSR according to the first embodiment of the present disclosure.
  • FIG. 3 is a diagram for explaining an example of the setting information according to the first embodiment of the present disclosure.
  • FIG. 2 is a sequence diagram for explaining an example of a schematic flow of processing according to the first embodiment of the present disclosure. It is a figure showing an example of the above-mentioned setting information concerning the 1st modification 1 of the 1st embodiment of this indication.
  • 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 illustrating an example of a BSR according to the first embodiment of the present disclosure.
  • FIG. 3
  • FIG. 7 is a diagram for explaining an example of the setting information according to the first modification example of the first embodiment of the present disclosure.
  • FIG. 7 is a diagram showing an example of the setting information according to the first modification example 2 of the first embodiment of the present disclosure.
  • FIG. 7 is a diagram for explaining an example of the setting information according to the first modification example 2 of the first embodiment of the present disclosure.
  • FIG. 7 is a diagram showing an example of the setting information according to the first modification example 3 of the first embodiment of the present disclosure.
  • FIG. 7 is a diagram for explaining an example of the setting information according to the first modification example 3 of the first embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating an example of setting information including the above setting information according to a second modification of the first embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating an example of a BSR according to a second embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating another example of a BSR according to the second embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating an example of setting information for determining whether to use BSR according to a second embodiment of the present disclosure.
  • FIG. 7 is a diagram for explaining an example of the setting information according to the second embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating an example of a BSR according to a fourth modification of the second embodiment of the present disclosure.
  • SR Scheduling requests
  • BSR buffer status reports
  • the SR is used by the UE to request the base station to allocate communication resources for new UL transmissions.
  • the SR may be used to request uplink-shared channel (UL-SCH) resources for initial transmission.
  • the UL-SCH may be mapped to a physical uplink shared channel (PUSCH).
  • PUSCH physical uplink shared channel
  • 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.
  • 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).
  • a set of PUCCH resources may be configured for each of one or more uplink BWPs.
  • UL transmission using SR 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.
  • UL resource allocation includes UL-SCH allocation and/or PUSCH resource allocation.
  • 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).
  • 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.
  • DCI downlink control information
  • the parameters of the SR are set using SchedulingRequestConfig and/or SchedulingRequestResourceConfig, which are RRC configuration information.
  • 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.
  • 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.
  • 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.
  • 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.
  • BSR Buffer status report
  • 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.
  • the upper layer includes a layer higher than the MAC layer.
  • the upper layer may include an RRC layer.
  • 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.
  • 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.
  • the BSR MAC CE may correspond to the MAC CE used for BSR transmission described above.
  • 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.
  • LCID/eLCID for each of the Downlink-Shared Channel (DL-SCH) and/or UL-SCH may be defined.
  • 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.
  • 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.
  • the Long BSR format 20B will be explained.
  • the size of Long BSR is variable.
  • 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).
  • Short Truncated BSR Long Truncated BSR
  • Extended Short Truncated BSR Extended Long Truncated BSR
  • Pre-emptive BSR and Extended Pre-emptive BSR are used by IAB-MT (Mobile Termination).
  • system 1 includes a base station 100 and a UE 200.
  • 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.
  • 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.
  • RAN radio access network
  • the base station 100 communicates with a UE (for example, UE 200) using a RAN protocol stack.
  • 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.
  • the protocol stack may not include all of these protocols, but may include some of these protocols.
  • 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.
  • 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).
  • 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).
  • 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.
  • IAB integrated access and backhaul
  • (2) UE200 UE 200 communicates with a base station.
  • the UE 200 communicates with the base station 100 when located within the coverage area 10 of the base station 100.
  • the UE 200 communicates with a base station (for example, the base station 100) using the above protocol stack.
  • a base station for example, the base station 100
  • 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).
  • 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.
  • 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.
  • 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.
  • the processing unit 140 (first communication processing unit 143) communicates with a UE (for example, UE 200) via the wireless communication unit 110.
  • 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.
  • 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.
  • RF radio frequency
  • 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.
  • a physical machine ie, hardware
  • a processor, memory, etc., and a hypervisor ie, hardware
  • 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.
  • 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.
  • 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.
  • the processing unit 230 communicates with a base station (eg, base station 100) or other UE via the wireless communication unit 210.
  • a base station eg, base station 100
  • other UE via the wireless communication unit 210.
  • 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.
  • SoC System on Chip
  • the SoC may include the RF circuit 283, and the wireless communication unit 210 may also be implemented by the SoC.
  • 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.
  • configuration information for determining whether to use BSR (hereinafter also referred to as enhanced-BSR) including a first field and a modified second field is transmitted from a base station to a UE. Ru.
  • enhanced-BSR BSR
  • Setting information for the purpose is transmitted from the base station 100 to the UE 200.
  • the BS extended BSR includes a first field and a modified second field, where the first field indicates a logical channel group (LCG) for which the buffer status is reported. It's okay.
  • the second field corresponds to the logical channel group and relates to the amount of uplink data.
  • the changed second field may be a field in which the size of the second field is increased (hereinafter also referred to as an expanded second field).
  • the expanded second field may be larger in size than the second field before expansion (that is, the data length may be longer or the number of bits may be greater).
  • UE 200 may calculate a data volume and determine the amount of uplink data available for a logical channel.
  • the UE 200 may determine the Buffer Size level based on the amount of uplink data, and may set an index corresponding to the determined Buffer Size level in the second field.
  • the extended second field is a Buffer Size field (hereinafter also referred to as an extended Buffer Size field) that indicates information used to indicate the total amount of data of the logical channels of the corresponding logical channel group.
  • the extended Buffer Size field of the BS extended BSR is longer than the Buffer Size field of the legacy BSR (hereinafter also referred to as the legacy Buffer Size field).
  • the legacy BSR is the BSR from which the enhanced-BSR is changed.
  • the legacy BSR may be a BSR classified as the above-mentioned Regular BSR, Periodic BSR, or Padding BSR.
  • the legacy BSR is Short BSR, Long BSR, Extended Short BSR, Extended Long BSR, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, Extended Long Trunc. ated BSR, Pre-emptive BSR, or Extended Pre-emptive BSR It's good to be there.
  • a code point (or index) corresponding to each legacy BSR may be defined as the LCID/eLCID value for the UL-SCH.
  • the LCID/eLCID values for UL-SCH are Short BSR, Long BSR, Extended Short BSR, Extended Long BSR, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, Extended Long Truncated BSR, Pre-emptive BSR, And/or a code point (or index) corresponding to each Extended Pre-emptive BSR may be defined.
  • the UE 200 may transmit any of the legacy BSRs identified by the LCID/eLCID values based on the settings and/or conditions from the base station 100.
  • FIG. 10 shows an example of the MAC CE format of the BS extended BSR in which the Buffer Size field of the legacy Long BSR is expanded.
  • the BS extended BSR is not limited to the legacy Long BSR, and may be a BSR in which the Buffer Size field of a legacy BSR in another format is extended.
  • the BS extended BSR includes an LCGi field as the first field and an extended Buffer Size j field as the extended second field, as shown in format 21 in FIG.
  • the LCGi field indicates the existence of an extended Buffer Size j field for LCGi.
  • the Extended Buffer Size j field is used to identify the total amount of data available on all logical channels belonging to the corresponding LCGi.
  • the size of one extended Buffer Size j field is, for example, 16 bits (or 8 bits), which is longer than the 8 bits (or 5 bits) of the legacy Buffer Size j field.
  • the legacy Buffer Size j field is the Buffer Size field from which the extended Buffer Size j field is changed. Note that the size of the extended Buffer Size j field is not limited to this, and may be any other size longer than the legacy Buffer Size j field (for example, 24 bits, etc.). Further, the size of the extended Buffer Size j field may differ depending on the corresponding LCGi.
  • 8 bits is also called 1 octet. That is, 16 bits is also called 2 octets.
  • the extended Buffer Size j field indicates an index corresponding to Buffer Size (eg, Buffer Size level, Buffer Size value, or Buffer Size range) in a table for, for example, a 16-bit Buffer Size field (not shown). Note that the extended Buffer Size j field is included in ascending order according to the LCGi (for example, according to the value of i of the LCGi).
  • BS Extended BSR is distinguished from BSR of other formats.
  • LCID/eLCID indicating BS extended BSR is defined.
  • a code point (or index) corresponding to the BS extended BSR may be defined as the LCID/eLCID value for the UL-SCH.
  • the MAC CE of the BS extended BSR may be transmitted while being included in a MAC PDU (protocol data unit).
  • a MAC PDU may include one or more MAC subPDUs, and each MAC subPDU may include a MAC subheader and a MAC CE.
  • the MAC subheader may include LCID/eLCID.
  • the MAC subheader including the LCID/eLCID indicating the BS extended BSR and the MAC CE of the BS extended BSR are included in the MAC subPDU, and the MAC PDU including the MAC subPDU is transmitted.
  • BS extended BSR setting information (hereinafter also referred to as BS extended BSR setting information) for determining whether to use the BS extended BSR according to this embodiment is defined.
  • the BS extended BSR configuration information is included in the logical channel configuration information. Thereby, the BS extended BSR is configured for each logical channel.
  • BS extended BSR configuration information will be described in detail with reference to FIGS. 11 and 12.
  • the BS extended BSR configuration information is included in LogicalChannelConfig. That is, the configuration information of the logical channel may correspond to LogicalChannelConfig.
  • LogicalChannelConfig may be used to configure parameters of a logical channel.
  • LogicalChannelConfig may include parameters related to the BSR.
  • one or more parameters included in LogicalChannelConfig may be used to identify one logical channel.
  • LogicalChannelConfig may include a parameter (logicalChannelGroup) that indicates the index of the logical channel group to which the one logical channel belongs. That is, the logical channel group to which the one logical channel belongs may be identified based on a parameter indicating the index of the logical channel group.
  • the base station 100 may transmit LogicalChannelConfig including one or more parameters for the one logical channel to the UE 200.
  • the base station 200 may transmit an RRC message including the LogicalChannelConfig to the UE 200.
  • UE 200 may identify the one logical channel based on one or more parameters included in LogicalChannelConfig.
  • the UE 200 may identify the logical channel group to which the one logical channel belongs based on a parameter indicating the index of the logical channel group included in LogicalChannelConfig.
  • the UE 200 may transmit a BSR for a logical channel group to which one or more logical channels belong.
  • BSR-BSExtApplied as BS extended BSR configuration information may be included as a parameter of LogicalChannelConfig.
  • the BS extended BSR configuration information is a flag.
  • BSR-BSExtApplied indicates that the UE 200 is configured to report the BS extended BSR, if present. Conversely, if BSR-BSExtApplied is not present, it is indicated that the UE 200 is not configured to report BS enhanced BSR, ie configured to report legacy BSR.
  • the BS extended BSR setting information is not limited to a flag that indicates whether or not to use the BS extended BSR depending on whether it exists, but may be a flag that indicates whether or not to use the BS extended BSR based on a value.
  • the BS enhanced BSR configuration information may have a value of 0 to indicate that legacy BSR is to be used, and a value of 1 to indicate to use BS enhanced BSR.
  • BSR-BSExtApplied exists may correspond to the case where BSR-BSExtApplied exists in LogicalChannelConfig. That is, the case where BSR-BSExtApplied exists may correspond to the case where BSR-BSExtApplied is included in LogicalChannelConfig. Furthermore, the case where BSR-BSExtApplied does not exist may correspond to the case where BSR-BSExtApplied does not exist in LogicalChannelConfig.
  • BSR-BSExtApplied does not exist may correspond to the case where BSR-BSExtApplied is not included in LogicalChannelConfig.
  • BSR-BSExtApplied exists or the case where BSR-BSExtApplied does not exist, but if BSR-BSExtApplied exists, it will be replaced when the value of BS extended BSR setting information is 1. It's okay to be hit.
  • BSR-BSExtApplied does not exist, it may be replaced with a value of 0 in the BS extended BSR configuration information.
  • BSR-BSExtApplied exists is also described as the case where BSR-BSExtApplied is set.
  • BSR-BSExtApplied does not exist is also described as the case where BSR-BSExtApplied is not set.
  • the message may be an RRC message.
  • BS extended BSR configuration information is transmitted in an RRC message including LogicalChannelConfig.
  • the RRC message may be, for example, RRCReconfiguration, RRCResume, or RRCSetup. Further, an RRC message different from the above RRC message may be used.
  • the base station 100 may transmit LogicalChannelConfig including BS extended BSR configuration information to the UE 200.
  • the base station 100 may transmit an RRC message including LogicalChannelConfig to the UE 200.
  • the UE 200 may determine operations related to BSR based on the BS extended BSR configuration information. For example, the UE 200 may identify the logical channel group to which the logical channel belongs based on the BS extended BSR configuration information, and transmit the BSR for the logical channel group.
  • UE 200 receives configuration information for determining whether to use the BS extended BSR according to this embodiment.
  • UE 200 acquires configuration information from the received message including configuration information.
  • the UE 200 determines the BSR to use based on the acquired configuration information.
  • the UE 200 determines whether to use the BS extended BSR based on the BS extended BSR configuration information obtained from the received RRC message. For example, the UE 200 determines whether to use the BS extended BSR for each logical channel based on the BS extended BSR configuration information included in the logical channel configuration information. The UE 200 uses the BS extended BSR when reporting the buffer status for the LCG to which the logical channel determined to use the BS extended BSR belongs.
  • the UE 200 uses the BS extended BSR as the BSR for the LCG that includes the logical channel to which the LogicalChannelConfig is set. do.
  • the base station 100 sets configuration information for determining whether to use enhanced-BSR (that is, BS enhanced BSR configuration information in this embodiment) in the RRC message (step S310). For example, the base station 100 obtains BSR-BSExtApplied as shown in FIG. 11, and sets BSR-BSExtApplied to LogicalChannelConfig.
  • the base station 100 transmits an RRC message including BS extended BSR configuration information to the UE 200 (step S320).
  • the base station 100 transmits to the UE 200 an RRC message (for example, RRCReconfiguration, RRCResume, or RRCSetup) that includes LogicalChannelConfig with BSR-BSExtApplied set.
  • RRC message for example, RRCReconfiguration, RRCResume, or RRCSetup
  • the UE 200 Upon receiving the RRC message including the BS extended BSR configuration 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 LogicalChannelConfig with BSR-BSExtApplied set, UE 200 transmits a response RRC message (for example, RRCReconfigurationComplete, RRCResumeComplete, or RRCSetupComplete) to base station 100.
  • a response RRC message for example, RRCReconfigurationComplete, RRCResumeComplete, or RRCSetupComplete
  • the UE 200 determines the use of enhanced-BSR based on the received configuration information (step S340). For example, when the BSR is triggered, the UE 200 uses the BS extended BSR if BSR-BSExtApplied is included in the LogicalChannelConfig for any logical channel belonging to the LCG that reports the buffer status in the BSR. Otherwise, the UE 200 uses a legacy BSR, ie, a BSR in which the Buffer Size field is not expanded. That is, the UE 200 reports the BS enhanced BSR (i.e., enhanced-BSR MAC CE) based on the fact that BSR-BSExtApplied is set for at least one of the logical channels belonging to the LCG for the reported BSR. It's okay.
  • BS enhanced BSR i.e., enhanced-BSR MAC CE
  • the UE 200 may report the legacy BSR based on the fact that BSR-BSExtApplied is not set for any of the logical channels belonging to the LCG for the reported BSR. In other words, the UE 200 determines whether to report the BS enhanced BSR (for example, enhanced-BSR MAC CE) depending on whether BSR-BSExtApplied is configured (for example, whether BSR-BSExtApplied is configured by an upper layer). It may be determined based on Furthermore, the UE 200 may determine whether to transmit the BS enhanced BSR (for example, enhanced-BSR MAC CE) based on whether the LogicalChannelConfig includes BSR-BSExtApplied.
  • the BS enhanced BSR for example, enhanced-BSR MAC CE
  • the BS extended BSR format may be used for Regular BSR, Periodic BSR, and/or Padding BSR.
  • the UE 200 may report BS extended BSR based on BSR-BSExtApplied being set.
  • BSR-BSExtApplied the UE 200 has BSR-BSExtApplied set, and the LCG with available data when the MAC PDU including BSR is built. Based on the presence of two or more, the BS extended BSR may be reported.
  • the UE 200 has BSR-BSExtApplied set and an LCG with data available when the MAC PDU including BSR is built.
  • the BS extended BSR may be reported based on the presence of one or more.
  • the UE 200 has BSR-BSExtApplied set, and there are two LCGs with data that can be used when the MAC PDU including BSR is built. or more (or one or more), and the BS extended BSR may be reported based on the ID of the largest LCG among the configured LCGs being greater than 7.
  • the UE 200 has BSR-BSExtApplied set, and there are two LCGs with data that can be used when the MAC PDU including BSR is built.
  • the BS extended BSR may be reported based on the fact that there are more than one (or one or more) and the ID of the largest LCG among the configured LCGs is greater than 256.
  • the UE 200 may report the BS enhanced BSR for all LCGs that have data available for transmission.
  • the UE 200 may report legacy BSR for Regular BSR, Periodic BSR, and/or Padding BSR based on the fact that BSR-BSExtApplied is not set. Additionally, for Regular BSR, Periodic BSR, and/or Padding BSR, the UE 200 has BSR-BSExtApplied set and an LCG with data available when the MAC PDU including BSR is built. A legacy BSR may be reported based on being one. In addition, for Regular BSR, Periodic BSR, and/or Padding BSR, the UE 200 has BSR-BSExtApplied set, and there are two LCGs with data that can be used when the MAC PDU including BSR is built.
  • the legacy BSR may be reported based on the fact that the ID of the largest LCG among the set LCGs is 7 or smaller than 7.
  • the UE 200 has BSR-BSExtApplied set, and there are two LCGs with data that can be used when the MAC PDU including BSR is built.
  • the legacy BSR may be reported based on the fact that the ID of the largest LCG among the set LCGs is 256 or smaller than 256.
  • the UE 200 may report the legacy BSR for all LCGs that have data available for transmission.
  • legacy BSRs are Short BSR, Long BSR, Extended Short BSR, Extended Long BSR, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, Extended Long Truncated BSR, Pre-emptive BSR, or Extended Pre -emptive May be BSR.
  • the maximum number of LCGs set using logicalChannelGroup may be eight (for example, eight LCGs with IDs from 0 to 7). That is, the LCG ID set using logicalChannelGroup may have any value from 0 to 7. Further, the maximum number of LCGs set using logicalChannelGroup-IAB-Ext-r17 may be 256 (for example, 256 LCGs with IDs from 0 to 255).
  • the UE 200 may report the legacy BSR for the LCG corresponding to the ID value that can be set using the logicalChannelGroup and/or the logicalChannelGroup-IAB-Ext-r17.
  • the UE 200 determines whether BSR-BSExtApplied is set and the number of padding bits is larger than the size of the legacy BSR (and/or the subheader of the legacy BSR). , may report the BS extended BSR. Furthermore, for Padding BSR, the UE 200 determines whether BSR-BSExtApplied is set and the number of padding bits is smaller than the size of the legacy BSR (and/or the subheader of the legacy BSR). , may report legacy BSR. Here, the UE 200 may report the BS enhanced BSR or legacy BSR for all LCGs that have data available for transmission. Furthermore, the UE 200 may report the BS extended BSR or legacy BSR for the LCG to which the logical channel determined based on the prioritization belongs, among the logical channels having data available for transmission.
  • the UE 200 transmits the enhanced-BSR MAC CE to the base station 100 (step S350). For example, the UE 200 sets an index corresponding to the Buffer Size of the UL data in the extended Buffer Size field corresponding to the LCG, as shown in FIG. 10, and generates the BS extended BSR MAC CE. UE 200 transmits the generated BS extended BSR MAC CE to base station 100. For example, the UE 200 may transmit the enhanced-BSR MAC CE by applying a logical channel prioritization (LCP) procedure.
  • LCP logical channel prioritization
  • the logical channel prioritization procedure may be a procedure applied when initial transmission is performed.
  • logical channels may be prioritized in the following order: In the following, logical channels with higher priority are listed first.
  • - MAC CE for C-RNTI or data from UL-CCCH - MAC CE for (Extended) BSR, with exception of BSR included for padding
  • - MAC CE for (Extended) Pre-emptive BSR - data from any Logical Channel, except data from UL-CCCH - MAC CE for BSR included for padding
  • enhanced-BSR MAC CE may have higher priority than MAC CE for (Extended) BSR, with exception of BSR included for padding.
  • enhanced-BSR MAC CE may be defined as having lower priority than MAC CE for C-RNTI, or data from UL-CCCH, and higher priority than MAC CE for (Extended) BSR. Furthermore, the enhanced-BSR MAC CE may have a higher priority than the MAC CE for (Extended) Pre-emptive BSR. For example, enhanced-BSR MAC CE is specified with lower priority than MAC CE for (Extended) BSR, with exception of BSR included for padding, and with higher priority than MAC CE for (Extended) Pre-emptive BSR. Good too. Furthermore, enhanced-BSR MAC CE may have higher priority than data from any Logical Channel, except data from UL-CCCH.
  • enhanced-BSR MAC CE may be defined as having lower priority than MAC CE for (Extended) Pre-emptive BSR, and higher priority than data from any Logical Channel, except data from UL-CCCH. Additionally, the enhanced-BSR MAC CE may have a higher priority than the MAC CE for BSR included for padding. For example, enhanced-BSR MAC CE may be defined as having lower priority than data from any Logical Channel, except data from UL-CCCH, and higher priority than MAC CE for BSR included for padding. For example, the UE 200 may report the enhanced-BSR MAC CE according to the priority in a logical channel prioritization (LCP) procedure.
  • LCP logical channel prioritization
  • messages are sent and received that include configuration information for determining whether to use a BSR that includes at least one first field and at least one modified second field.
  • the BSR is used to provide information about the UL data amount
  • the at least one first field indicates at least one LCG for which the buffer status is reported
  • the at least one modified second field The field corresponds to the at least one LCG and relates to the amount of UL data.
  • the amount of information regarding the amount of UL data in the BSR can be increased compared to the BSR including the first field and the second field (ie, legacy BSR). Therefore, it becomes possible to improve the efficiency of UL data scheduling using BSR.
  • the above setting information is included in the logical channel setting information.
  • the above setting information can be set for each logical channel.
  • logical channels can be associated with XR traffic, so that substantially the above configuration information can be configured for XR traffic.
  • the above setting information is a flag. 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.
  • the at least one modified second field is the second field whose size has been increased.
  • the amount of information regarding the amount of UL data can be increased by following the manner of the second field.
  • the range or granularity of the amount of UL data that can be handled can be expanded. That is, it becomes possible to raise the upper limit of the UL data amount or to subdivide the granularity.
  • the at least one modified second field is a Buffer Size field indicating information used to indicate the total amount of data of each logical channel of the corresponding at least one LCG.
  • Buffer Size field indicating information used to indicate the total amount of data of each logical channel of the corresponding at least one LCG. This allows the range or granularity of Buffer Size that can be handled in the Buffer Size field to be expanded. Therefore, it is possible to reduce quantization errors for UL data (for example, XR data) that has a large capacity and fluctuates widely.
  • the BS extended BSR configuration information is a flag.
  • the BS extended BSR configuration information according to the embodiment of the present disclosure is not limited to this example.
  • the BS extended BSR configuration information may be information regarding the length of at least one changed second field.
  • the BS extended BSR configuration information is information indicating the length of the second field whose size has been increased.
  • BS extended BSR configuration information according to this modification will be described in detail with reference to FIGS. 14 and 15.
  • BSR-BufferSizeFieldLength as BS extended BSR configuration information is included as a parameter of LogicalChannelConfig.
  • BSR-BufferSizeFieldLength indicates the length of the Buffer Size field.
  • BSR-BufferSizeFieldLength indicates whether to use BS extended BSR depending on whether it exists.
  • BSR-BufferSizeFieldLength if present, indicates that the UE 200 is configured to report the BS extended BSR and indicates the length of the extended Buffer Size field in the BS extended BSR. Conversely, if BSR-BufferSizeFieldLength does not exist, it is indicated that the UE 200 is not configured to report BS enhanced BSR, ie configured to report legacy BSR.
  • BSR-BufferSizeFieldLength may indicate information for indicating the length of the Buffer Size field.
  • BSR-BufferSizeFieldLength indicates an index corresponding to the length of the Buffer Size field (eg, the value or range of the length).
  • the BS extended BSR configuration information may be information for identifying an LCG that uses BS extended BSR. That is, the BS extended BSR configuration information may indicate the ID of the LCG.
  • the BS extended BSR configuration information may indicate the ID of the LCG to which the logical channel belongs.
  • the UE 200 may determine the ID of the LCG to which the logical channel belongs based on the ID of the LCG indicated by the BS extended BSR configuration information.
  • logicalChannelGroup-XR-Ext-r18 as BS extended BSR configuration information is included as a parameter of LogicalChannelConfig.
  • logicalChannelGroup-XR-Ext-r18 may indicate the LCG ID.
  • logicalChannelGroup-XR-Ext-r18 may indicate the LCG ID to which the logical channel belongs, if it exists.
  • logicalChannelGroup-XR-Ext-r18 may indicate that the UE 200 is configured to report the BS extended BSR for the LCG ID.
  • logicalChannelGroup-XR-Ext-r18 does not exist, it may be indicated that the UE 200 is not configured to report the BS enhanced BSR, ie, configured to report the legacy BSR.
  • logicalChannelGroup-XR-Ext-r18 when logicalChannelGroup-XR-Ext-r18 is set, the settings of other LCG IDs may be ignored. In this case, for example, logicalChannelGroup and/or logicalChannelGroup-IAB-Ext-r17 as shown in FIG. 16 may be ignored. In other words, if the logical channel config includes logicalChannelGroup-XR-Ext-r18 indicating the LCG ID, the UE 200 may ignore the logicalChannelGroup and/or logicalChannelGroup-IAB-Ext-r17 included in the logical channel config. good. As described above, logicalChannelGroup and/or logicalChannelGroup-IAB-Ext-r17 indicates the LCG ID.
  • the maximum number of LCGs that can be set using logicalChannelGroup-XR-Ext-r18 is 8 (for example, 8 LCGs with IDs from 0 to 7, or 8 LCGs with IDs 8 to 15). ). That is, the LCG ID set using logicalChannelGroup-XR-Ext-r18 may be any value from 0 to 7 (or any value from 8 to 15). For example, by setting the LCG ID set using logicalChannelGroup-XR-Ext-r18 from 8 to 15, you can specify an LCG ID that is different from the LCG ID set using logicalChannelGroup (i.e., 0 to 7). It becomes possible to set.
  • the maximum number of LCGs that can be set using logicalChannelGroup-XR-Ext-r18 is 16 (for example, 16 LCGs with IDs from 0 to 15, or 16 LCGs with IDs 8 to 23). It may be. That is, the LCG ID set using logicalChannelGroup-XR-Ext-r18 may be any value from 0 to 15 (or any value from 8 to 23). For example, by setting the number of LCG IDs set using logicalChannelGroup-XR-Ext-r18 to 16, the number of LCG IDs set using logicalChannelGroup (i.e., 8) is greater than the number of LCG IDs set using logicalChannelGroup. It becomes possible to set an ID.
  • the maximum number of LCGs that can be set using logicalChannelGroup-XR-Ext-r18 is 256 (for example, 256 LCG IDs from 0 to 255, or 256 LCG IDs from 256 to 511). It may be. That is, the LCG ID set using logicalChannelGroup-XR-Ext-r18 may be any value from 0 to 255 (or any value from 256 to 511).
  • the LCG ID set using logicalChannelGroup-XR-Ext-r18 from 256 to 511
  • the LCG ID set using logicalChannelGroup and/or logicalChannelGroup-IAB-Ext-r17 it is possible to set different LCG IDs (from 0 to 255).
  • the UE 200 ignores the settings of other LCG IDs and performs BSR-related operations without setting the LCG ID using different parameters. can be easily executed.
  • the BS extended BSR configuration information may be information used to indicate the type of UL data.
  • the type of UL data may be pose/control or video.
  • BSR-DataType-XR as BS extended BSR configuration information is included as a parameter of LogicalChannelConfig.
  • LogicalChannelConfig For example, as shown in Table 47 of FIG. 19, if BSR-DataType-XR exists, the UE 200 will report the BS extended BSR for the LCG to which the logical channel in which the indicated type of UL data is buffered belongs. Indicates that it is set to . Conversely, if BSR-DataType-XR does not exist, it is indicated that the UE 200 is not configured to report BS enhanced BSR, ie configured to report legacy BSR.
  • the BS extended BSR configuration information may be information regarding the length of at least one changed second field.
  • the information regarding the length of the modified second field can also indicate whether to use the BS extended BSR. Therefore, an increase in communication resources for signaling BS extended BSR configuration information can be suppressed.
  • the BS extended BSR configuration information indicates the length of the second field whose size has been increased, so that the size of the second field after the change can be dynamically changed.
  • the BS extended BSR configuration information may be information for identifying an LCG that uses BS extended BSR.
  • the LCG ID and whether to use the BS extended BSR into one piece of information, it is possible to specify the LCG ID of the logical channel and at the same time determine whether to use the BS extended BSR.
  • the BS extended BSR configuration information may be information used to indicate the type of UL data. This makes it possible to indicate whether to use the BS extended BSR for each type of UL data. Therefore, an appropriate BSR can be selected depending on the type of UL data. In particular, the characteristics of XR data vary greatly depending on the data type. Therefore, by selecting an appropriate BSR according to the type of XR data, scheduling suitable for XR data becomes possible.
  • Second modification Another example of configuration information including BS extended BSR configuration information
  • BS extended BSR configuration information is included in the logical channel configuration information.
  • the BS extended BSR configuration information according to the embodiment of the present disclosure is not limited to this example.
  • the BS extended BSR configuration information may be included in the LCG configuration information. Thereby, the BS extended BSR is set for each LCG. This modification will be described in detail with reference to FIG. 20.
  • LCG configuration information 51 is newly added as RRC configuration information, and BS extended BSR configuration information is included in LCG configuration information 51 as shown in FIG.
  • the configuration information 51 of the LCG is included in the RRC message and transmitted to the UE 200.
  • the BS extended BSR configuration information may be included in the SR configuration information.
  • the BS extended BSR is set for each SR.
  • the BS extended BSR configuration information is included in SchedulingRequestConfig or SchedulingRequestResourceConfig as an example of SR configuration information 53 as shown in FIG. 20, and is associated with schedulingRequestID.
  • the schedulingRequestID is also included in the logical channel setting information. Therefore, the UE 200 refers to the BS extended BSR configuration information included in the SR configuration information 53 via the schedulingRequestID set in the logical channel belonging to the LCG, and determines whether to use the BS extended BSR for the LCG. . In other words, it can be said that the BS extended BSR is indirectly configured for each logical channel via the schedulingRequestID.
  • the BS extended BSR configuration information may be included in the BSR configuration information. That is, it is indicated whether to use the BS extended BSR as the BSR of the UE 200. Thereby, the BS extended BSR is set for each UE 200.
  • the BS extended BSR configuration information is included in BSR-Config, which is an example of BSR configuration information 55 as shown in FIG.
  • the UE 200 refers to the BS extended BSR configuration information included in the BSR-Config and determines whether to use the BS extended BSR.
  • the BS extended BSR configuration information may be included in the LCG configuration information.
  • BS extended BSR setting information can be set for each LCG. Since BSR is reported for LCG, processing can be reduced compared to when BS extended BSR is configured for logical channels.
  • the BS extended BSR configuration information may be included in the SR configuration information.
  • BS extended BSR configuration information can be configured for each SR. Therefore, it is possible to collectively manage whether or not to use the BS extended BSR for at least one logical channel configured for the same SR.
  • the BS extended BSR configuration information may be included in the BSR configuration information.
  • BS extended BSR configuration information can be configured for each UE 200. Therefore, all the BSRs used by the UE 200 can be switched at once to whether or not they are BS extended BSRs.
  • the BS extended BSR includes a first field and a modified second field.
  • the BS extended BSR according to embodiments of the present disclosure is not limited to this example.
  • the BS extended BSR may further include at least one second field.
  • the at least one extended second field corresponds to an LCG identified based on BS extended BSR configuration information among the plurality of LCGs, and the at least one second field corresponds to a BS extended BSR configuration among the plurality of LCGs. It corresponds to an LCG other than the LCG specified based on the information. In other words, only the Buffer Size field corresponding to the LCG specified based on the BS extended BSR configuration information among the plurality of LCGs is expanded.
  • the BS extended BSR includes multiple LCG fields, at least one extended Buffer Size field, and at least one legacy Buffer Size field.
  • At least one extended Buffer Size field corresponds to an LCG among the plurality of LCGs for which it is determined to use the BS extended BSR based on the BS extended BSR configuration information.
  • at least one legacy Buffer Size field corresponds to an LCG other than the above LCG among the plurality of LCGs.
  • Buffer Size 1 corresponds to LCG0 and Buffer Size 2 corresponds to LCG1. If it is decided to use the BS extended BSR for LCG0, the BS extended BSR includes a Buffer Size 1 field that is longer than the legacy Buffer Size field as an extended Buffer Size field. Furthermore, if it is not determined to use the BS extended BSR for LCG1, the BS extended BSR includes a Buffer Size 2 field as a legacy Buffer Size field.
  • the BS extended BSR further includes at least one second field, the at least one LCG is a plurality of LCGs, and the at least one extended BSR
  • the second field corresponds to an LCG identified based on the BS extended BSR configuration information among the multiple LCGs, and at least one second field corresponds to an LCG other than the LCG identified based on the configuration information among the multiple LCGs.
  • the system 1 is a system that complies with 5G or NR TS.
  • the system 1 according to the embodiment of the present disclosure is not limited to this example.
  • the system 1 may be a system compliant with another 3GPP TS.
  • 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.
  • base station 100 may be an ng-eNB.
  • the system 1 may be a 3G TS-compliant system, and the base station 100 may be a NodeB.
  • the system 1 may be a system compliant with next generation (eg, 6G) TS.
  • system 1 may be a system that complies with the TS of another standardization organization regarding mobile communications.
  • Second embodiment> configuration information for determining whether to use a BSR in which the changed second field includes delay information (hereinafter also referred to as delay BSR) is transmitted from the base station 100 to the UE 200. Sent. Note that descriptions of contents that are substantially the same as those in the first embodiment will be omitted.
  • the modified second field of the delayed BSR includes a second field and a third field different from the second field.
  • the modified second field is obtained by adding the third field to the second field.
  • the changed second field includes a Buffer Size field as the second field and a delay information field as the third field.
  • the delay information field indicates information used to indicate delay information of the LCG.
  • the delay information indicates information used to indicate the remaining time until the allowable delay of data belonging to the corresponding LCG.
  • FIGS. 21A and 21B show an example of the MAC CE format of the delayed BSR in which the Buffer Size field of the legacy Long BSR has been changed.
  • the delayed BSR is not limited to the legacy Long BSR, and may be a BSR in which the Buffer Size field of the legacy BSR in other formats described above is changed.
  • the delayed BSR includes the LCGi field as the first field, and the reduced Buffer Size j field and Delay Info j field as the modified second field, as shown in format 23A of FIG. 21A.
  • the LCGi field indicates the existence of the reduced Buffer Size j field and Delay Info j field for LCGi.
  • the reduced Buffer Size j field like the legacy Buffer Size j field, identifies the total amount of data available for all logical channels belonging to the corresponding LCGi.
  • the size of the reduced Buffer Size j field is, for example, 6 bits, which is shorter than the 8 bit size of the legacy Buffer Size j field. Note that the size of the reduced Buffer Size j field is not limited to this, and may be any other size shorter than the legacy Buffer Size j field. Furthermore, the size of the reduced Buffer Size j field may differ depending on the corresponding LCGi.
  • the reduced Buffer Size j field indicates, for example, an index corresponding to Buffer Size (for example, Buffer Size level, Buffer Size value, or Buffer Size range) in a table for a 6-bit Buffer Size field (not shown).
  • Buffer Size for example, Buffer Size level, Buffer Size value, or Buffer Size range
  • the Delay Info j field as the third field indicates information used to indicate delay information of the corresponding LCGi.
  • the size of the Delay Info j field is, for example, 2 bits, which is shorter than the 8-bit size of the legacy Buffer Size j field.
  • the sum of the size of the reduced Buffer Size j field and the size of the Delay Info j field is equal to the size of the legacy Buffer Size j field.
  • the size of the Delay Info j field is not limited to this, and may be any other size shorter than the legacy Buffer Size j field. Further, the size of the Delay Info j field may differ depending on the corresponding LCGi.
  • the Delay Info j field indicates the remaining time (for example, indicated in ms, slot, or subframe units) until the allowable delay of data belonging to the corresponding LCG.
  • the Delay Info j field may indicate an index corresponding to the remaining time (for example, the value or range of the remaining time), and may also indicate a flag corresponding to the remaining time (for example, a flag indicating the size of the remaining time). May be shown.
  • the Reduction Buffer Size j field and Delay Info j field are treated as one, and combinations thereof are included in ascending order according to LCGi.
  • the delayed BSR may include the LCGi field as the first field, and the legacy Buffer Size j field and Delay Info i field as the modified second fields, as shown in format 23B of FIG. 21B.
  • the Delay Info j field is replaced with part of the legacy Buffer Size field
  • the Delay Info i field is added to the legacy Buffer Size field.
  • the Delay Info i field is added between the LCGi field and the legacy Buffer Size field. Note that the Delay Info i field may be added after the legacy Buffer Size field.
  • the contents and size of the Delay Info i field are the same as in format 23A.
  • the Buffer Size j field and the Delay Info i field are each included in ascending order according to LCGi.
  • Delayed BSR is distinguished from other formats of BSR. For example, an LCID/eLCID indicating a delayed BSR is defined. This allows the delayed BSR to be transmitted as a MAC CE. Note that the MAC CE of the delayed BSR may be transmitted while being included in the MAC PDU. That is, the MAC subheader including the LCID/eLCID indicating the delayed BSR and the MAC CE of the delayed BSR are included in the MAC subPDU, and the MAC PDU including the MAC subPDU is transmitted.
  • delayed BSR setting information Setting information of delayed BSR Setting information (hereinafter also referred to as delayed BSR setting information) for determining whether to use the delayed BSR according to this embodiment is defined.
  • the delayed BSR configuration information is included in the logical channel configuration information. A delay BSR is thereby set for each logical channel.
  • the delayed BSR configuration information will be described in detail with reference to FIGS. 22 and 23.
  • the delayed BSR configuration information is included in LogicalChannelConfig.
  • BSR-DelayApplied as delay BSR setting information may be included as a parameter of LogicalChannelConfig.
  • the LogicalChannelConfig according to this embodiment may be substantially the same as the LogicalChannelConfig described in the first embodiment except for BSR-BSExtApplied, and the portion related to BSR-BSExtApplied may be replaced with BSR-DelayApplied. It's fine.
  • the delayed BSR setting information is a flag.
  • BSR-DelayApplied if present, indicates that the UE 200 is configured to report delayed BSR.
  • the absence of BSR-DelayApplied indicates that the UE 200 is not configured to report delayed BSR, ie configured to report legacy BSR.
  • the delayed BSR setting information is not limited to a flag that indicates whether to use the delayed BSR depending on whether it exists or not, but may be a flag that indicates whether to use the delayed BSR based on a value.
  • the delayed BSR configuration information may have a value of 0 to indicate that a legacy BSR is used, and a value of 1 to indicate that a delayed BSR is used.
  • a message including delayed BSR configuration information is substantially the same as a message including BS extended BSR configuration information, so a description thereof will be omitted.
  • UE 200 determines whether to use delayed BSR based on delayed BSR configuration information acquired from the received RRC message. For example, the UE 200 determines whether to use delayed BSR for the logical channel based on delayed BSR configuration information included in the logical channel configuration information. The UE 200 uses the delayed BSR when reporting the buffer status for the LCG to which the logical channel determined to use the delayed BSR belongs.
  • the UE 200 uses the delayed BSR as the BSR for the LCG that includes the logical channel to which the LogicalChannelConfig is set. .
  • the UE 200 transmits the enhanced-BSR MAC CE to the base station 100 (step S350). For example, for each LCG as shown in FIG. 21A, the UE 200 sets an index corresponding to the Buffer Size of the UL data in the corresponding reduced Buffer Size field, sets delay information in the corresponding Delay Info field, and sets the delay information in the corresponding Delay Info field. Generate BSR MAC CE. Alternatively, as shown in FIG. 21B, for each LCG, the UE 200 sets an index corresponding to the Buffer Size of the UL data in the corresponding Buffer Size field, sets delay information in the corresponding Delay Info field, and sets the delay BSR. Generate MAC CE. The UE 200 transmits the generated delayed BSR MAC CE to the base station 100. Note that, similarly to the first embodiment, the UE 200 may transmit the enhanced-BSR MAC CE (that is, the delayed BSR MAC CE) by applying the logical channel prioritization (LCP) procedure.
  • LCP logical channel prioritization
  • the modified second field included in the enhanced-BSR includes the second field and a third field different from the second field. This makes it possible to add information with different content and/or format from the information indicated by the second field.
  • the second field is a Buffer Size field indicating information used to indicate the total amount of data of each logical channel of the corresponding at least one LCG
  • the third field is delay information of the corresponding at least one LCG.
  • This field indicates information used to indicate the delay information
  • the delay information indicates information used to indicate the remaining time until the allowable delay of data belonging to the corresponding at least one LCG. This allows reporting of delay information about buffered data. Therefore, it is possible to schedule the data in consideration of delay information.
  • a PDB may be imposed on XR data
  • reporting delay information using a delayed BSR for XR data enables scheduling that satisfies the PDB.
  • delayed BSR configuration information is a flag.
  • the delayed BSR configuration information according to embodiments of the present disclosure is not limited to this example.
  • the delayed BSR configuration information may be information regarding the length of at least one changed second field.
  • the delayed BSR setting information is information indicating the length of the third field.
  • BSR-DelayInfoFieldLength as delay BSR setting information is included as a parameter of LogicalChannelConfig.
  • BSR-DelayInfoFieldLength indicates the length of the Delay Info field, like BSR-BufferSizeFieldLength shown in table 43 of FIG. 15.
  • BSR-DelayInfoFieldLength if present, indicates that the UE 200 is configured to report a delayed BSR and indicates the length of the Delay Info field in the delayed BSR. Conversely, if BSR-DelayInfoFieldLength is not present, it is indicated that the UE 200 is not configured to report delayed BSR, ie configured to report legacy BSR.
  • BSR-DelayInfoFieldLength may indicate information for indicating the length of the Delay Info field.
  • BSR-DelayInfoFieldLength indicates an index corresponding to the length of the Delay Info field (eg, the value or range of the length).
  • the delayed BSR configuration information may be information regarding the length of at least one changed second field. Further, since the delayed BSR configuration information indicates the length of the third field, the length of the third field and the changed second field can be dynamically changed.
  • the delayed BSR setting information may be information for identifying an LCG that uses delayed BSR. Note that this modification example is realized by replacing the BS extended BSR according to the first modification example 2 of the first embodiment with a delayed BSR, so a description thereof will be omitted.
  • the delayed BSR setting information may be information used to indicate the type of UL data. Note that this modification is realized by replacing the BS extended BSR according to the first modification 3 of the first embodiment with a delayed BSR, so the description will be omitted.
  • Second modification Another example of configuration information including delayed BSR configuration information
  • delayed BSR configuration information is included in the configuration information of the logical channel.
  • the delayed BSR configuration information according to embodiments of the present disclosure is not limited to this example.
  • the delayed BSR configuration information may be included in the LCG configuration information. Note that this modification is realized by replacing the BS extended BSR according to the second modification 1 of the first embodiment with a delayed BSR, so the description will be omitted.
  • delayed BSR configuration information may be included in SR configuration information.
  • this modification example is realized by replacing the BS extended BSR according to the second modification example 2 of the first embodiment with a delayed BSR, so a description thereof will be omitted.
  • the delayed BSR setting information may be included in the BSR setting information. Note that this modification example is realized by replacing the BS extended BSR according to the second modification example 3 of the first embodiment with a delayed BSR, so a description thereof will be omitted.
  • delayed BSR includes a first field and a modified second field.
  • delayed BSR according to embodiments of the present disclosure is not limited to this example.
  • the delayed BSR may further include at least one second field.
  • the at least one modified second field corresponds to an LCG identified based on the delayed BSR configuration information among the plurality of LCGs
  • the at least one second field corresponds to the LCG identified based on the delayed BSR configuration information among the plurality of LCGs. This corresponds to an LCG other than the LCG specified based on the LCG.
  • the third field is added only to the second field corresponding to the LCG identified based on the delayed BSR configuration information among the plurality of LCGs, and only the second field is changed.
  • the delay BSR includes a plurality of LCG fields, at least one reduced Buffer Size field and a set of Delay Info fields, and at least one legacy Buffer Size field.
  • At least one set of the reduced Buffer Size field and the Delay Info field corresponds to an LCG that is determined to use a delayed BSR based on the delayed BSR configuration information, among the plurality of LCGs.
  • at least one legacy Buffer Size field corresponds to an LCG other than the above LCG among the plurality of LCGs.
  • Buffer Size 1 corresponds to LCG0
  • Buffer Size 3 (not shown) corresponds to LCG1.
  • the delayed BSR includes a set of a 6-bit Buffer Size 1 field and a 2-bit Delay Info 1 field as a set of reduced Buffer Size and Delay Info fields.
  • the delayed BSR includes an 8-bit Buffer Size 3 field as a legacy Buffer Size field.
  • the delayed BSR may include a plurality of LCG fields, at least one set of legacy Buffer Size and Delay Info fields, and at least one legacy Buffer Size field without a Delay Info field.
  • At least one set of a legacy Buffer Size field and a Delay Info field corresponds to an LCG that is determined to use a delayed BSR based on the delayed BSR configuration information, among the plurality of LCGs.
  • at least one legacy Buffer Size field without the Delay Info field corresponds to an LCG other than the above LCG among the plurality of LCGs.
  • Buffer Size 1 corresponds to LCG0
  • Buffer Size 3 (not shown) corresponds to LCG1.
  • the delayed BSR includes a set of an 8-bit Buffer Size 1 field and a 2-bit Delay Info 0 field as a set of legacy Buffer Size and Delay Info fields.
  • the delayed BSR includes an 8-bit Buffer Size 3 field as a legacy Buffer Size field, and does not include Delay Info 1, unlike FIG. 23B.
  • the modified second field includes the second field and the third field.
  • the modified second field according to embodiments of the present disclosure is not limited to this example.
  • the changed second field may be one field that serves as both the second field and the third field.
  • the at least one modified second field contains information used to indicate the total amount of data of each logical channel of the corresponding at least one LCG, and delay information of the corresponding at least one LCG. This is the field to indicate.
  • FIG. 24 shows an example of the MAC CE format of the delayed BSR in which the Buffer Size field of the legacy Long BSR has been changed. Note that the delayed BSR according to this modification is not limited to the legacy Long BSR, and may be a BSR in which the Buffer Size field of a legacy BSR in another format is changed.
  • the delayed BSR includes multiple LCG fields and at least one Buffer Size/Delay Info field.
  • the LCGi field indicates the existence of the Buffer Size/Delay Info j field for LCGi.
  • the Buffer Size/Delay Info field indicates an index corresponding to a set of Buffer Size and delay information.
  • a table is defined that shows the correspondence between the index and a set of Buffer Size and delay information. Note that the Buffer Size/Delay Info j field is included in ascending order according to LCGi.
  • FIG. 24 shows an example in which the size of the Buffer Size/Delay Info field is the same as the size of the legacy Buffer Size field, it may be larger or smaller than the size of the legacy Buffer Size field.
  • the size of the Buffer Size/Delay Info field may be 16 bits, 24 bits, or more.
  • the delayed BSR may further include at least one second field.
  • the second field corresponding to the LCG identified based on the delay BSR setting information among the plurality of LCGs is changed to the Buffer Size/Delay Info field.
  • At least one modified second field contains the total amount of data of each logical channel of the corresponding at least one LCG and the corresponding This field indicates information used to indicate delay information of at least one LCG.
  • This allows the BSR to manage Buffer Size and delay information in one field. Therefore, the BSR reception process (ie, field analysis process) can be simplified.
  • the system 1 is a system that complies with 5G or NR TS.
  • the system 1 according to the embodiment of the present disclosure is not limited to this example.
  • the system 1 may be a system compliant with other TSs as in the fourth modification of the first embodiment.
  • 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.
  • 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.
  • some of the steps in the process may be deleted, and additional steps may be added to the process.
  • 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.
  • a program may be provided that causes a computer to perform the operations of the components.
  • a computer-readable non-transitional physical recording medium may be provided on which the program is recorded.
  • 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.
  • 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.
  • UE user equipment
  • user equipment 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.
  • 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.
  • 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.
  • the UE may be other IoT (Internet of Things) devices such as sensors and cameras.
  • IoT Internet of Things
  • a UE may be mobile or fixed.
  • 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.
  • transmitting may mean a combination of processing the at least one layer and physically transmitting the signal wirelessly or by wire.
  • recipient 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.
  • 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.
  • “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.
  • a communication processor receiving a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; an information acquisition unit (231) that acquires the setting information included in the message; Equipped with The buffer status report is used to provide information about the amount of uplink data; the at least one first field indicates at least one logical channel group for which buffer status is to be reported; The at least one modified second field corresponds to the at least one logical channel group and relates to an uplink data amount.
  • Apparatus (200).
  • (Feature 8) The device according to any one of features 1 to 3, wherein the configuration information is information for identifying a logical channel group that uses the buffer status report.
  • the buffer status report further includes at least one second field; the at least one logical channel group is a plurality of logical channel groups; The at least one modified second field corresponds to a logical channel group identified based on the configuration information among the plurality of logical channel groups, The device according to any one of features 1 to 9, wherein the at least one second field corresponds to a logical channel group other than the logical channel group specified based on the configuration information among the plurality of logical channel groups. .
  • (Feature 12) 12 The apparatus of feature 11, wherein the at least one modified second field is a buffer size field indicating information used to indicate the total amount of data for each logical channel of the corresponding at least one logical channel group.
  • the second field is a buffer size field indicating information used to indicate the total amount of data of each logical channel of the corresponding at least one logical channel group
  • the third field is a field indicating information used to indicate delay information of the corresponding at least one logical channel group, 14.
  • the at least one modified second field is used to indicate a total amount of data of each logical channel of the corresponding at least one logical channel group and delay information of the corresponding at least one logical channel group.
  • a field that indicates information The apparatus according to any one of the features 1 to 10, wherein the delay information indicates information used to indicate the remaining time until an allowable delay of data belonging to the corresponding at least one logical channel group.
  • an information acquisition unit (141) that acquires configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; a communication processing unit (143) that transmits a message including the setting information; Equipped with The buffer status report is used to provide information about the amount of uplink data; the at least one first field indicates at least one logical channel group for which buffer status is to be reported; The at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.
  • the buffer status report is used to provide information about the amount of uplink data;
  • the at least one first field indicates at least one logical channel group for which buffer status is to be reported;
  • the at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.
  • the buffer status report is used to provide information about the amount of uplink data;
  • the at least one first field indicates at least one logical channel group for which buffer status is to be reported;
  • the at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.
  • (Feature 21) receiving a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; obtaining the configuration information included in the message;
  • a program that causes a computer to execute The buffer status report is used to provide information about the amount of uplink data; the at least one first field indicates at least one logical channel group for which buffer status is to be reported;
  • the at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.
  • (Feature 22) obtaining configuration information for determining whether to use a buffer status report that includes at least one first field and at least one modified second field; Sending a message including the configuration information;
  • a program that causes a computer to execute The buffer status report is used to provide information about the amount of uplink data; the at least one first field indicates at least one logical channel group for which buffer status is to be reported;
  • the at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.
  • (Feature 23) receiving a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; 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 buffer status report is used to provide information about the amount of uplink data; the at least one first field indicates at least one logical channel group for which buffer status is to be reported;
  • the at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.
  • (Feature 24) obtaining configuration information for determining whether to use a buffer status report that includes at least one first field and at least one modified second field; Sending a message including the configuration information;
  • a computer-readable non-transitional physical recording medium that records a program that causes a computer to execute, The buffer status report is used to provide information about the amount of uplink data; the at least one first field indicates at least one logical channel group for which buffer status is to be reported; The at least one modified second field corresponds to the at least one logical channel group and relates to an amount of uplink data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2023/025358 2022-08-09 2023-07-07 装置及び方法 Ceased WO2024034306A1 (ja)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2024540318A JPWO2024034306A1 (https=) 2022-08-09 2023-07-07
EP23852289.0A EP4572391A4 (en) 2022-08-09 2023-07-07 DEVICE AND METHOD
CN202380058412.8A CN119678543A (zh) 2022-08-09 2023-07-07 装置及方法
US19/045,154 US20250185102A1 (en) 2022-08-09 2025-02-04 Communication apparatus, base station and method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022127462 2022-08-09
JP2022-127462 2022-08-09

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/045,154 Continuation US20250185102A1 (en) 2022-08-09 2025-02-04 Communication apparatus, base station and method

Publications (1)

Publication Number Publication Date
WO2024034306A1 true WO2024034306A1 (ja) 2024-02-15

Family

ID=89851375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/025358 Ceased WO2024034306A1 (ja) 2022-08-09 2023-07-07 装置及び方法

Country Status (5)

Country Link
US (1) US20250185102A1 (https=)
EP (1) EP4572391A4 (https=)
JP (1) JPWO2024034306A1 (https=)
CN (1) CN119678543A (https=)
WO (1) WO2024034306A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025171675A1 (zh) * 2024-02-18 2025-08-21 北京小米移动软件有限公司 通信方法、终端、网络设备、通信系统和存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024210559A1 (en) * 2023-04-05 2024-10-10 Samsung Electronics Co., Ltd. Method and apparatus for selecting bsr format in wireless communication system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020126018A1 (en) * 2018-12-20 2020-06-25 Telefonaktiebolaget Lm Ericsson (Publ) Buffer status reporting in wireless communication systems
JP2022127462A (ja) 2021-02-19 2022-08-31 富士フイルムヘルスケア株式会社 受信コイル装置及びそれを備えた磁気共鳴イメージング装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016112512A1 (zh) * 2015-01-15 2016-07-21 富士通株式会社 Mac控制元素的上行配置方法、装置以及通信系统
CN110149718B (zh) * 2018-02-14 2022-03-29 华为技术有限公司 数据发送的方法和通信设备
CN112106325B (zh) * 2018-05-10 2022-10-04 华为技术有限公司 通信方法、通信装置和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020126018A1 (en) * 2018-12-20 2020-06-25 Telefonaktiebolaget Lm Ericsson (Publ) Buffer status reporting in wireless communication systems
JP2022127462A (ja) 2021-02-19 2022-08-31 富士フイルムヘルスケア株式会社 受信コイル装置及びそれを備えた磁気共鳴イメージング装置

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 17", 3GPP TS 38.321 V17.0.0, March 2022 (2022-03-01)
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 17", 3GPP TS 38.331 V17.1.0, June 2022 (2022-06-01)
"Considerations on XR Capacity Improvements", 3GPP TSG RAN WG1 #109-E, E-MEETING, 9 May 2022 (2022-05-09)
"Discussion on capacity enhancements for XR", 3GPP TSG-RAN WG1 MEETING #109-E, 9 May 2022 (2022-05-09)
"Discussion on XR specific capacity enhancements techniques", 3GPP TSG RAN WG1 #109-E, E-MEETING, 9 May 2022 (2022-05-09)
ERICSSON: "Discussion on capacity enhancements for XR", 3GPP DRAFT; R1-2203639, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Online; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052153087 *
SAMSUNG: "Correction for Enhanced NR IIoT and URLLC in 38.321", 3GPP DRAFT; R2-2205710, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20220509 - 20220520, 25 April 2022 (2022-04-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052139146 *
See also references of EP4572391A4
ZTE, SANECHIPS: "Discussion on XR specific capacity enhancements techniques", 3GPP DRAFT; R1-2203607, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052153072 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025171675A1 (zh) * 2024-02-18 2025-08-21 北京小米移动软件有限公司 通信方法、终端、网络设备、通信系统和存储介质

Also Published As

Publication number Publication date
JPWO2024034306A1 (https=) 2024-02-15
EP4572391A1 (en) 2025-06-18
CN119678543A (zh) 2025-03-21
US20250185102A1 (en) 2025-06-05
EP4572391A4 (en) 2025-10-08

Similar Documents

Publication Publication Date Title
US11096198B2 (en) Method, apparatus, and system for implementing data scheduling
US11051322B2 (en) Data processing method, apparatus, and system
CN116017727B (zh) 传输bsr的方法及装置
US9713030B2 (en) Transmission data processing method and devices
CN111181694B (zh) 一种上行控制信息的传输方法及装置
JP7367838B2 (ja) サイドリンクスケジューリングリクエストのトリガー方法、装置及びシステム
CN106063361B (zh) 一种传输资源请求的方法和装置
CN107006020B (zh) 一种终端、基站，以及调度请求的传输方法
CN102685895B (zh) 一种上行数据的调度方法、系统及装置
CN111356172B (zh) 通信方法、装置、终端、网络设备及存储介质
KR20200039753A (ko) 데이터 전송 방법, 장치 및 통신 시스템
WO2018094872A1 (zh) sidelink资源调度方法、装置和系统
EP3706488B1 (en) Uplink data packet resource allocation method and user terminal
US20250185102A1 (en) Communication apparatus, base station and method
KR20110111984A (ko) 이동통신시스템에서 효율적인 경쟁기반 역방향 전송 방법
CN101695194A (zh) 一种lte系统半静态调度中上行逻辑信道的复用方法
WO2023013610A1 (ja) 通信装置、基地局装置及び通信方法
CN117561781A (zh) 无线通信方法、终端设备和网络设备
US20180343666A1 (en) Method for wireless communication, network device and terminal device
WO2023068356A1 (ja) 通信装置、基地局、及び通信方法
WO2022163374A1 (ja) ユーザ機器及び基地局
EP4626070A1 (en) Communication method, communication apparatus, and communication system
WO2024095791A1 (ja) 端末装置及び基地局装置
WO2019200507A1 (en) Control of d2d duplication
WO2023013547A1 (ja) 通信装置、基地局及び通信方法

Legal Events

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

Ref document number: 23852289

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024540318

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202380058412.8

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2023852289

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023852289

Country of ref document: EP

Effective date: 20250310

WWP Wipo information: published in national office

Ref document number: 202380058412.8

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2023852289

Country of ref document: EP