Method and device for recommending bit rate for multi-modality

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. In addition, the present disclosure relates to a method performed by a terminal in a wireless communication system and a device for performing same, the method comprising the steps of: transmitting, to a base station, terminal performance information including at least one of first information indicating the performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate; receiving, from the base station, a radio resource control (RRC) message including configuration information related to the recommended bit rate; and receiving, from the base station, a message including information about the recommended bit rate for a quality of service (QoS) flow on the basis of the configuration information.

Description

Method and device for recommending bit rates for multi-modality

[0001] The present invention relates to a terminal, a base station, and a node supporting wireless communication. Furthermore, the present invention relates to a bit rate recommendation method for multi-modality and a device for performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The technical problem to be solved by the embodiment of the present disclosure is to provide an improved method for a terminal, a base station, and a node supporting wireless communication.

[0009] In addition, a technical problem to be achieved in an embodiment of the present disclosure is to provide a bit rate recommendation method for multi-modality and a device for performing the same.

[0010] The technical problems to be achieved in the embodiments of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present invention pertains from the description below.

[0011] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may be provided. The method may include the steps of transmitting terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate to a base station, receiving a radio resource control message (RRC) message including configuration information related to the recommended bit rate from the base station, and receiving a message including information on the recommended bit rate for a quality of service (QoS) flow based on the configuration information from the base station.

[0012] In addition, according to one embodiment of the present disclosure, a method performed by a base station in a wireless communication system may be provided. The method may include the steps of receiving terminal performance information from a terminal, the terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate, the step of transmitting an RRC (radio resource control message) message including configuration information related to the recommended bit rate to the terminal, and the step of transmitting a message including information on the recommended bit rate for a quality of service (QoS) flow based on the configuration information to the terminal.

[0013] In addition, according to one embodiment of the present disclosure, a terminal of a wireless communication system may be provided. The terminal may include at least one transceiver, at least one processor communicatively connected to the at least one transceiver, and a memory that stores instructions communicatively connected to the at least one processor and executable individually or in any combination of the at least one processor, such that the terminal transmits terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate to a base station, receives an RRC (radio resource control message) message including configuration information related to the recommended bit rate from the base station, and receives a message including information on the recommended bit rate for a quality of service (QoS) flow based on the configuration information from the base station.

[0014] In addition, according to one embodiment of the present disclosure, a base station of a wireless communication system may be provided. The base station may include at least one transceiver, at least one processor communicatively connected to the at least one transceiver, and a memory communicatively connected to the at least one processor and configured to execute individually or in any combination of the at least one processor, such that the base station receives terminal performance information from a terminal, the terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate, transmits an RRC (radio resource control message) message including configuration information related to the recommended bit rate to the terminal, and transmits a message including information on the recommended bit rate for a quality of service (QoS) flow based on the configuration information to the terminal.

[0015] According to various embodiments of the present disclosure, improved methods can be provided for terminals, base stations, and nodes supporting wireless communication.

[0016] In addition, according to various embodiments of the present disclosure, a bit rate recommendation method for multi-modality and a device for performing the same can be provided.

[0017] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0018] FIG. 1 is a diagram illustrating the structure of an NR (new radio) system according to one embodiment of the present disclosure.

[0019] FIG. 2 is a diagram illustrating a wireless protocol structure in an NR system according to an embodiment of the present disclosure.

[0020] FIG. 3 is a diagram illustrating a process in which a terminal and a base station form an RRC (radio resource control) connection according to one embodiment of the present invention.

[0021] FIG. 4 is a diagram illustrating a recommended bit rate medium access control (MAC) CE (control element) structure according to one embodiment of the present disclosure.

[0022] FIG. 5 is a diagram illustrating a method for a terminal and a base station to query a recommended bit rate and set a recommended bit rate for each QoS (quality of service) flow according to an embodiment of the present disclosure.

[0023] FIG. 6 is a diagram illustrating a recommended bit rate MAC CE format for each QoS Flow according to an embodiment of the present disclosure.

[0024] FIG. 7 is a diagram illustrating a recommended bit rate MAC CE format for each QoS Flow according to one embodiment of the present disclosure.

[0025] FIG. 8 is a diagram illustrating a recommended bit rate MAC CE format for each QoS Flow according to an embodiment of the present disclosure.

[0026] FIG. 9 is a diagram illustrating a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0027] FIG. 10 is a diagram illustrating a base station in a wireless communication system according to an embodiment of the present disclosure.

[0028] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0029] In describing the embodiments of this disclosure, descriptions of technical details that are well known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to more clearly convey the gist of this disclosure without obscuring it by omitting unnecessary explanations.

[0030] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0031] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0032] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0033] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0034] Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0035] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0036] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0037] For convenience of explanation below, some terms and names defined in the 3rd generation partnership project (3GPP) LTE (long term evolution) standard and / or 3GPP NR (new radio) standard may be used. However, the present disclosure is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.

[0038] In various embodiments of the present disclosure, there are configurations that are described as operations of specific layers of the terminal, such as operations of a MAC layer device of the terminal, operations of an upper layer device of the terminal, operations of an SDAP layer, operations of a PHY layer, and operations of an RLC layer. Such operations of specific layer devices of the terminal may be interpreted not only as operations performed in a specific layer, but also as operations performed in a terminal including the terminal.

[0039] FIG. 1 is a diagram illustrating the structure of an NR system according to one embodiment of the present disclosure.

[0040] Referring to FIG. 1, the wireless communication system may be composed of multiple base stations (e.g., gNB (100), ng-eNB (110), ng-eNB (120), gNB (130)), an access and mobility management function (AMF) (140), and a user plane function (UPF) (150). Of course, the wireless communication system is not limited to the configuration illustrated in FIG. 1, and may include more or fewer components.

[0041] According to one embodiment of the present disclosure, a user equipment (hereinafter referred to as UE or terminal) (160) can access an external network through base stations (100, 110, 120, 130) and UPF (150).

[0042] In Fig. 1, base stations (100, 110, 120, 130) can serve as access nodes of a cellular network and provide wireless access to terminals accessing the network. For example, base stations (100, 110, 120, 130) can collect status information such as buffer status, available transmission power status, and channel status of terminals to schedule the collected information and support connections between terminals and a core network (CN; in particular, the CN of NR is referred to as 5GC) in order to service user traffic.

[0043] In Fig. 1, gNB (100, 130) can control multiple cells, and an adaptive modulation & coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal can be applied.

[0044] The core network, which handles various control functions as well as mobility management for terminals, can be connected to multiple base stations. 5GC can also be integrated with existing LTE systems.

[0045] Meanwhile, in a wireless communication system, a user plane (UP) related to transmission of actual user data and a control plane (CP) such as connection management may be configured separately. The gNB (100) and gNB (130) of FIG. 1 may use the UP and CP technologies defined in NR technology, and the ng-eNB (110) and ng-eNB (120), although connected to 5GC, may use the UP and CP technologies defined in LTE (long term evolution) technology.

[0046] AMF (140) is a device that is responsible for various control functions as well as mobility management functions for terminals and can be connected to multiple base stations.

[0047] UPF (150) may refer to a type of gateway device that provides data transmission. Although not illustrated in FIG. 1, the NR wireless communication system may also include a session management function (SMF). The SMF can manage packet data network connections, such as protocol data unit (PDU) sessions provided to terminals.

[0048] FIG. 2 is a diagram illustrating a wireless protocol structure in an NR system according to one embodiment of the present disclosure.

[0049] Referring to FIG. 2, the wireless protocol of the NR system may be composed of SDAP (service data adaptation protocol) (200)(290), PDCP (packet data convergence protocol) (210)(280), RLC (radio link control) (220)(270), MAC (medium access control) (230)(260), and PHY (physical) (240)(250) in the terminal and the base station, respectively.

[0050] SDAP (200)(290) can perform operations for transmitting user data, mapping QoS flows to specific data radio bearers (DRBs) for uplink and downlink, marking QoS flow IDs for uplink and downlink, and mapping reflective QoS flows to data bearers for uplink SDAP PDUs. SDAP settings corresponding to each DRB can be provided from a higher RRC layer. Of course, the present invention is not limited to the above examples.

[0051] PDCP (210)(280) can perform operations such as IP header compression / decompression. Furthermore, PDCP (210)(280) can provide sequential and out-of-order transmission functions, reordering, duplicate detection, retransmission, encryption, and decryption functions. Of course, the above examples are not limited thereto.

[0052] RLC (220) (270) can reconfigure PDCP PDUs to an appropriate size. In addition, RLC (220) (270) can provide sequential and out-of-order transmission functions, and can provide ARQ (automatic repeat request) functions, joining, segmentation, reassembly functions, re-segmentation functions, reordering functions, duplicate detection functions, and error detection functions. Of course, the present invention is not limited to the above examples.

[0053] The MAC (230) (260) is connected to multiple RLC layer devices configured in a terminal, and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. In addition, the MAC (230) (260) can provide a mapping function, a scheduling information reporting function, a HARQ (hybrid automatic repeat request) function, a priority control function between logical channels, a priority control function between terminals, an MBMS (multimedia broadcast multicast service) service confirmation function, a transmission format selection function, and a padding function. Of course, the present invention is not limited to the above examples.

[0054] The PHY layer (240)(250) performs an operation of channel coding and modulating upper layer data, converting it into an OFDM (orthogonal frequency division multiplexing) symbol and transmitting it through a wireless channel, or demodulating and channel decoding an OFDM symbol received through a wireless channel and transmitting it to a higher layer. In addition, the physical layer also uses HARQ (Hybrid ARQ) for additional error correction, and the receiver transmits 1 bit whether or not the packet transmitted by the transmitter has been received. The 1 bit information is called HARQ ACK / NACK (acknowledgement / negative-acknowledgement) information.

[0055] Downlink HARQ ACK / NACK information for uplink data transmission is transmitted through the physical hybrid-aRQ indicator channel (PHICH) physical channel in the case of LTE, and in the case of NR, whether retransmission is necessary or whether a new transmission can be performed can be determined through the UE's scheduling information on the physical dedicated control channel (PDCCH), which is a channel through which downlink / uplink resource allocation, etc. are transmitted. This is because NR applies asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission can be transmitted through the physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). PUCCH is generally transmitted in the uplink of the PCell (primary cell) described later, but if the UE supports it, the base station may additionally transmit it to the SCell (secondary cell) described later, which is called the PUCCH SCell.

[0056] Although not shown in Figure 2, an RRC (Radio Resource Control) layer exists above the PDCP layer of each terminal and base station, and the RRC layer can transmit and receive connection and measurement-related setting control messages for radio resource control.

[0057] Meanwhile, the physical layer can be composed of one or more frequencies / carriers, and the technology that sets and uses multiple frequencies simultaneously is called carrier aggregation (CA). CA technology can dramatically increase the transmission capacity by the number of secondary carriers by additionally using the primary carrier and one or more secondary carriers instead of using only one carrier for communication between the terminal and the base station. Meanwhile, in LTE / NR, a cell within a base station that uses a primary carrier is called a primary cell or PCell, and a cell within a base station that uses a secondary carrier is called a secondary cell or SCell. PCell can be defined as SpCell (special cell).

[0058] FIG. 3 is a diagram illustrating a procedure for a terminal to establish an RRC connection with a base station according to an embodiment of the present invention.

[0059] Figure 3 illustrates a procedure in which a terminal switches from RRC idle mode (RRC_IDLE) to RRC connected mode (RRC_CONNECTED) in the present invention to establish a connection with a network. In Figure 3, the terminal establishes uplink / downlink transmission synchronization with a base station through a random access process and transmits an RRC Setup Request message to the base station (300). The RRC Setup Request message includes an identifier of the terminal and a reason for establishing a connection (Establishment Cause). The base station transmits an RR CSetup message to the terminal so that the terminal establishes an RRC connection (305).

[0060] For example, the above message (RRC Setup) may include configuration information (RadioBearerConfig) for each radio bearer (radio bearer (DRB or SRB)). The Radio Bearer configuration information may include an identifier (ID) of each Radio Bearer, configuration information (PDCP-Config) for the PDCP layer device of the Radio Bearer, and an indicator indicating whether the Radio Bearer is a DAPS Bearer.

[0061] For example, the above message (RRC Setup) may include RLC Bearer configuration information (RLC-BearerConfig) for each cell group (Cell Group (MCG (master cell group), SCG (secondary cell group))) belonging to the corresponding Cell Group. The RLC Bearer configuration information may include the following information.

[0062] - Logical Channel Identifier (logicalChannelIdentity): Indicates the LCID corresponding to the RLC Bearer / RLC layer device (RLC Entity).

[0063] - servedRadioBearer: Indicates the Radio Bearer ID associated with the corresponding RLC Bearer / RLC layer device (RLC Entity). The Radio Bearer ID may indicate a specific DRB or SRB.

[0064] - RLC configuration (rlc-Config): Indicates the RLC layer parameter configuration information of the RLC layer device (RLC Entity) of the corresponding RLC Bearer.

[0065] For example, the above rlc-Config may include the following configuration information:

[0066] - When the RLC layer device is set to AM (acknowledged mode):

[0067] ■ ul-AM-RLC configuration information: sn-FieldLength (sequence number length), t-PollRetransmit (Poll retransmission timer size), pollPDU (Poll trigger PDU count threshold), pollByte (Poll trigger byte threshold), maxRetxThreshold (maximum number of retransmissions)

[0068] ■ dl-AM-RLC configuration information: sn-FieldLength (Sequence Number length), t-Reassembly (Reassembly timer size), t-StatusProhibit (Status PDU prohibition timer size)

[0069] - When the RLC layer device is set to UM (unacknowledged mode) Bi-Directional mode:

[0070] ■ ul-UM-RLC configuration information: sn-FieldLength (Sequence Number length)

[0071] ■ dl-UM-RLC configuration information: sn-FieldLength (Sequence Number length), t-Reassembly (Reassembly timer size)

[0072] - When the RLC layer device is set to UM Uni-Directional-UL mode:

[0073] ■ ul-UM-RLC configuration information: sn-FieldLength (Sequence Number length)

[0074] - When the RLC layer device is set to UM Uni-Directional-DL mode:

[0075] ■ dl-UM-RLC configuration information: sn-FieldLength (Sequence Number length), t-Reassembly (Reassembly timer size)

[0076] Referring to FIG. 3, a terminal that has established an RRC connection enters RRC_CONNECTED mode and transmits an RRCSetupComplete message to the base station (310). If the base station does not know the terminal capabilities of the terminal that is currently establishing a connection or wishes to determine the terminal capabilities, the base station can transmit a message inquiring about the terminal's capabilities (e.g., UE capability enquiry) to the terminal (315). In addition, the terminal can transmit a message reporting its capabilities (e.g., UE capability information) to the base station (320).

[0077] The base station transmits a SecurityModeCommand message to the terminal to set up security with the terminal (325), and the terminal transmits a SecurityModeComplete message to the base station (330). When the security setting is complete, the base station transmits an RRCReconfiguration message to the terminal (335).

[0078] For example, the above message (RRCReconfiguration) may include configuration information (RadioBearerConfig) for each Radio Bearer (DRB or SRB). The Radio Bearer configuration information may include the ID of each Radio Bearer, configuration information (PDCP-Config) for the PDCP layer device of the Radio Bearer, and an indicator indicating whether the Radio Bearer is a DAPS Bearer.

[0079] For example, the above message (RRCReconfiguration) may include RLC Bearer configuration information (RLC-BearerConfig) for each Cell Group (MCG, SCG) belonging to the corresponding Cell Group. The RLC Bearer configuration information may include the following information.

[0080] - logicalChannelIdentity: Indicates the LCID corresponding to the RLC Bearer / layer device.

[0081] - servedRadioBearer: Indicates the Radio Bearer ID associated with the RLC Bearer / layer device. The Radio Bearer ID may indicate a specific DRB or SRB.

[0082] - rlc-Config: Indicates the RLC layer parameter setting information of the RLC layer device of the corresponding RLC Bearer.

[0083] For example, the above rlc-Config may include the following configuration information:

[0084] - When the RLC layer device is set to AM (acknowledged mode):

[0085] ■ ul-AM-RLC configuration information: sn-FieldLength (Sequence Number length), t-PollRetransmit (Poll retransmission timer size), pollPDU (Poll trigger PDU count threshold), pollByte (Poll trigger byte threshold), maxRetxThreshold (maximum number of retransmissions). For example, if the terminal supports low-latency RLC polling proposed in this disclosure, settings related to the corresponding function may be added.

[0086] ■ dl-AM-RLC configuration information: sn-FieldLength (Sequence Number length), t-Reassembly (Reassembly timer size), t-StatusProhibit (Status PDU prohibit timer size). For example, if the terminal supports low-latency RLC Polling proposed in this disclosure, settings related to the corresponding function may be added.

[0087] - When the RLC layer device is set to UM (unacknowledged mode) Bi-Directional mode:

[0088] ■ ul-UM-RLC configuration information: sn-FieldLength (Sequence Number length)

[0089] ■ dl-UM-RLC configuration information: sn-FieldLength (Sequence Number length), t-Reassembly (Reassembly timer size)

[0090] - When the RLC layer device is set to UM Uni-Directional-UL mode:

[0091] ■ ul-UM-RLC configuration information: sn-FieldLength (Sequence Number length)

[0092] - When the RLC layer device is set to UM Uni-Directional-DL mode:

[0093] ■ dl-UM-RLC configuration information: sn-FieldLength (Sequence Number length), t-Reassembly (Reassembly timer size)

[0094] The terminal that receives the RRC Reconfiguration message transmits an RRC Reconfiguration complete message to the base station in response to the RRC Reconfiguration message (340).

[0095] As such, the general data transmission process largely consists of three steps: RRC connection setup, security setup, and DRB setup. Additionally, the base station may transmit an RRCReconfiguration message to the terminal to update, add, or change settings for a specific reason (350).

[0096] In one embodiment of the present disclosure, a terminal that has received an RRC message (RRCReconfiguration) sets up each Radio Bearer by the Radio Bearer setting of the message, sets up the corresponding PDCP layer device, sets up an RLC Bearer / layer device having an association with each Radio Bearer / PDCP layer device, and then establishes an association between the RLC layer device and the PDCP layer device, after which data transmission and reception (345, 355) can be performed.

[0097] As one embodiment of the present disclosure, referring to FIG. 3, a base station may transmit a UE capability request (UECapabilityEnquiry) message requesting a capability report to a UE in an RRC connected (RRC_CONNECTED) state. The base station may include information for requesting UE capability for each RAT (radio access technology) type in the UECapabilityEnquiry message. For example, when the base station requests the UE to generate a UECapabilityInformation message through the capability request message, the base station may include filtering information that may indicate conditions and restrictions. For example, the filtering information may include frequency band list information requesting a capability report for each RAT type. For example, the filtering information may indicate whether the UE for each RAT type should report whether it supports a specific function. For example, the filtering information may indicate whether the terminal should report support for a recommended bit rate (RBR) query message / MAC CE and support for a recommended bit rate message / MAC CE for a specific RAT type (e.g., NR).

[0098] In one embodiment of the present disclosure, referring to FIG. 3, a terminal may configure a terminal capability information (UECapabilityInformation) message corresponding to a UECapabilityEnquiry message and report it to a base station in response to a terminal capability request.

[0099] For example, the UECapabilityInformation message may include a field indicating whether the terminal supports the recommended bit rate query message transmitted to the base station. For example, the field may be expressed as 1-bit information (e.g., 1: supported, 0: not supported). For example, if the field is included, it may indicate that the corresponding function is supported, and if the field is not included, it may indicate that the corresponding function is not supported. In addition, the interpretation of the 1-bit information is only an example and does not exclude an opposite interpretation.

[0100] For example, the UECapabilityInformation message may include a field indicating whether the terminal supports the recommended bit rate message transmitted by the base station to the terminal. For example, the field may be expressed as 1-bit information (e.g., 1: supported, 0: not supported). For example, if the field is included, it may indicate that the corresponding function is supported, and if the field is not included, it may indicate that the corresponding function is not supported. In addition, the interpretation of the 1-bit information is only an example and does not exclude an opposite interpretation.

[0101] For example, the UECapabilityInformation message may include a field indicating whether the terminal supports a bit rate multiplier function of the recommended bit rate MAC CE. For example, the field may be expressed as 1-bit information (e.g., 1: supported, 0: not supported). For example, if the field is included, it may indicate that the corresponding function is supported, and if the field is not included, it may indicate that the corresponding function is not supported. In addition, the interpretation of the 1-bit information is only an example and does not exclude an opposite interpretation.

[0102] A field indicating whether the terminal supports a recommended bit rate query message transmitted to the base station, a field indicating whether the base station supports a recommended bit rate message transmitted to the terminal, and a field indicating whether the bit rate multiplier function of the recommended bit rate MAC CE is supported have been described, but the capability for at least two of the three fields may be indicated through one information field, and three-bit information may be used for each of the fields.

[0103] In one embodiment of the present disclosure, the base station can determine whether the terminal supports the recommended bit rate message through the UECapabilityInformation message (320) transmitted by the terminal. For example, if the base station determines that the terminal supports the recommended bit rate message, it can transmit a recommended bit rate MAC CE to the terminal.

[0104] In one embodiment of the present disclosure, the base station can determine whether the terminal supports the recommended bit rate query message through the UECapabilityInformation message transmitted by the terminal. For example, if the base station determines that the terminal supports the recommended bit rate query message, the base station can set a timer (e.g., bit rate query prohibit timer (bitRateQueryProhibitTimer)) for a specific logical channel of the terminal through an RRCReconfiguration message. The bitRateQueryProhibitTimer can be used for the purpose of restricting the terminal from transmitting the recommended bit rate query when the timer is running, in order to prevent the recommended bit rate query from occurring too frequently. The size of the timer can be set to a value having a specific time unit (e.g., second, millisecond, microsecond).

[0105] As one embodiment of the present disclosure, referring to FIG. 3, a recommended bit rate procedure may be used to provide information on a bit rate recommended by a base station to a terminal (provided to a MAC layer device (MAC Entity) of the terminal). The recommended bit rate procedure may broadly include a procedure in which, when a terminal has a desired bit rate, it transmits a recommended bit rate query message to the base station to notify the base station of the fact, and a procedure in which the base station transmits a recommended bit rate message to the terminal to set the bit rate recommended by the base station to the terminal. The upper layer of the terminal may determine uplink / downlink traffic settings / characteristics with reference to the recommended bit rate set by the base station. For example, when generating video traffic, the upper layer of the terminal (e.g., the Application layer) may determine a video compression rate with reference to the recommended bit rate for uplink set by the base station. For example, when the upper layer of the terminal (e.g., the Application layer) instructs the application server responsible for generating video traffic to determine the video compression rate, it may do so by referring to the recommended bit rate for the downlink set by the base station.

[0106] In one embodiment of the present disclosure, the bit rate may refer to a recommended bit rate of the physical layer. For example, for the bit rate, an averaging window of a default value (e.g., 2000 ms) may be applied as specified in a predefined manner (e.g., standard TS 26.114). The base station may transmit a recommended bit rate (RBR) MAC CE (365) to the terminal (to the MAC layer device of the terminal) to indicate a recommended bit rate for the terminal for a specific logical channel and a specific direction (uplink or downlink).

[0107] In one embodiment of the present disclosure, when a terminal receives a recommended bit rate (RBR) MAC CE transmitted by a base station, the MAC layer device of the terminal can inform a higher layer of a recommended bit rate for the indicated logical channel and direction.

[0108] In one embodiment of the present disclosure, the MAC layer device of a terminal may request the base station to indicate a recommended bit rate for a specific logical channel and a specific direction. For example, if the MAC layer device of the terminal receives a request from a higher layer to query the base station for a recommended bit rate (RBR) for a specific logical channel and a specific direction (i.e., uplink or downlink), the MAC layer device of the terminal may operate as follows.

[0109] 1> If a recommended bitrate query has not yet been triggered for that logical channel and that direction:

[0110] 2> It can trigger a recommended bitrate query (RBR Query) for the given logical channel, direction, and desired bitrate.

[0111] In one embodiment of the present disclosure, referring to FIG. 3, when there is a UL resource allocated for a new transmission in the MAC layer device of the terminal, the MAC layer device of the terminal may operate as follows.

[0112] 1> For each recommended bitrate query that has already been triggered but not yet canceled, as determined by the recommended bitrate procedure, the following actions can be taken:

[0113] 2> If the bitRateQueryProhibitTimer for the corresponding logical channel and corresponding direction of the corresponding Recommended Bitrate Query (RBR Query) is set and not running; and

[0114] 2> If the MAC layer device has UL resources allocated for a New Transmission and the UL resources can accommodate the Recommended Bit Rate MAC CE and its Subheader as a result of the LCP defined in Section 5.4.3.1 of TS38.321:

[0115] 3> The Multiplexing and Assembly procedure may be instructed to generate a Recommended Bit Rate (RBR) MAC CE (360) for the logical channel and direction of the corresponding Recommended Bit Rate Query (RBR Query).

[0116] 3> You can start / run the bitRateQueryProhibitTimer for the corresponding logical channel and corresponding direction of the corresponding recommended bit rate query (RBR Query).

[0117] 3> You can cancel the recommended bit rate query (RBR Query).

[0118] In one embodiment of the present disclosure, a recommended bit rate MAC CE for a recommended bit rate message transmitted by a base station to a terminal may be indicated by setting the LCID (Logical Channel ID) field of a MAC subheader to a predetermined value. For example, the LCID field may be set to a value corresponding to the MAC CE with reference to Table 1 below. Table 1 defines LCID values ​​for DL-DSCH.

[0119] [Table 1]

[0120]

[0121] In one embodiment of the present disclosure, a recommended bit rate MAC CE for a recommended bit rate query message transmitted by a terminal to a base station may be indicated as a corresponding MAC CE by setting the LCID (Logical Channel ID) field of a MAC subheader to a predetermined value. For example, the LCID field may be set to a value corresponding to the corresponding MAC CE with reference to Table 2 below. Table 2 defines LCID values ​​for the UL-SCH.

[0122] [Table 2]

[0123]

[0124] FIG. 4 is a diagram illustrating a recommended bit rate MAC CE structure according to one embodiment of the present disclosure.

[0125] Referring to FIG. 4, the recommended bit rate MAC CE may include at least one of the following fields:

[0126] - LCID (400): The LCID field may indicate the ID of a logical channel to which a recommended bit rate (transmitted by the base station to the terminal) or a recommended bit rate query (transmitted by the terminal to the base station) applies. For example, the length of the LCID field may be 6 bits.

[0127] - Uplink / Downlink (UL / DL, 410): The UL / DL field can indicate whether the recommended bit rate or recommended bit rate query applies to the uplink or downlink. The field can be 1 bit long, with 0 indicating downlink and 1 indicating uplink.

[0128] -Bit Rate (420, 430): The Bit Rate field may indicate one of the bit rate indices defined in a given bit rate table. For example, the bit rate table may be defined as in Table 3. For example, the length of the Bit Rate field may be 6 bits. For example, in the case of a recommended bit rate (transmitted by the base station to the terminal), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate the bit rate recommended by the base station. For example, in the case of a recommended bit rate query (transmitted by the terminal to the base station), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate the bit rate desired by the terminal.

[0129] -X(440): This field can indicate a bit rate multiplier. For example, if the terminal supports the recommended bit rate multiplier function, and the base station sets a bit rate multiplier (e.g., referred to as bitRateMultiplier) for the logical channel indicated by the LCID field (400) through an RRC message (e.g., RRCReconfiguration), and if the X field is set to 1, the actual bit rate value can be determined as a value obtained by multiplying the bit rate corresponding to the Index indicated by the Bit Rate field (430) by the bitRateMultiplier. For example, the bitRateMultiplier can be set by the base station to a specific value (e.g., one of 40, 70, 100, and 200) through an RRC message.

[0130] - R(450, 460): Reserved field that can be set to 0.

[0131] Table 3 defines the bit rates corresponding to the indices indicated by the Bit rate field.

[0132] [Table 3]

[0133]

[0134] The recommended bit rate or recommended bit rate query described above was set / executed on a per-logical channel basis. However, since multiple QoS Flows can be mapped to a single logical channel, a method for setting a recommended bit rate query or recommended bit rate for a specific QoS Flow is required for a terminal or base station to set a recommended bit rate query or recommended bit rate for a specific QoS Flow.

[0135] In one embodiment of the present disclosure, the QoS Flow-specific recommended bit rate query message and the QoS Flow-specific recommended bit rate message may be referred to as a Recommended Bit Rate for QoS Flow (RBR-Q) Query message and a Recommended Bit Rate for QoS Flow (RBR-Q) message, respectively. However, these names are merely examples, and the present disclosure does not limit the names of the messages.

[0136] In one embodiment of the present disclosure, the MAC CE generated for transmitting RBR-Q and RBR-Q Query messages may be referred to as a Recommended Bit Rate for QoS Flow (RBR-Q) MAC CE. However, this name is only an example, and the present disclosure does not limit the name of the MAC CE.

[0137] In one embodiment of the present disclosure, to prevent frequent RBR-Q MAC CE generation due to RBR-Q Query, the base station may set a specific timer (e.g., bitRateQueryProhibitTimer-Q) for each QoS Flow of the terminal via an RRC message (e.g., RRCReconfiguration). For example, the bitRateQueryProhibitTimer-Q may operate so that RBR-Q MAC CE can be generated only after RBR-Q Query is triggered when the bitRateQueryProhibitTimer-Q is not running.

[0138] FIG. 5 is a diagram illustrating a method for a terminal and a base station to query a recommended bit rate and set a recommended bit rate for each QoS Flow according to an embodiment of the present disclosure.

[0139] In one embodiment of the present disclosure, a MAC layer device of a terminal can request a base station to indicate an RBR-Q for a specific QoS Flow and a specific direction through an RBR-Q Query (500). For example, the above operation can be performed only when the base station has configured the terminal to be able to perform an RBR-Q Query for the corresponding QoS Flow through an RRC message (e.g., RRCReconfiguration). For example, the RBR-Q Query setting can be configured for each QoS Flow / logical channel / DRB.

[0140] In one embodiment of the present disclosure, the terminal may operate as follows.

[0141] If the MAC entity is requested by upper layers to query the gNB for the recommended bit rate for a QoS flow and for a direction (ie for uplink or downlink), the MAC entity shall:

[0142] 1> if a Recommended bit rate query for this (QoS Flow) / (logical channel) and this direction has not been triggered, and per QoS Flow query is configured by RRC:

[0143] 2> trigger a Recommended bit rate query for the corresponding (logical channel) / (QoS Flow), direction, and desired bit rate.

[0144] 1> if a Recommended bit rate query for this (logical channel) / (QoS Flow) and this direction has not been triggered , and per QF query is not configured by RRC :

[0145] 2> trigger a Recommended bit rate query for this logical channel, direction, and desired bit rate.

[0146] Referring to FIG. 5, in one embodiment of the present disclosure, an upper layer of a terminal (e.g., an Application layer) may request a base station to query the MAC layer of the terminal for an RBR-Q for a specific QoS Flow and a specific direction (i.e., uplink or downlink) through the SDAP layer of the terminal. Since the information about the QoS Flow within the terminal is managed by the SDAP layer, an RBR-Q query for a specific QoS Flow to the MAC layer of the terminal may be possible only if there is an instruction from the SDAP layer.

[0147] Referring to FIG. 5, for example, when a MAC layer device of a terminal is requested from a higher layer (e.g., SDAP layer, Application layer) to query (Query, 510) a base station for RBR-Q for a specific QoS Flow and a specific direction (i.e., uplink or downlink), the MAC layer device of the terminal may operate as follows.

[0148] 1> If an RBR-Q Query has not yet been triggered for the given QoS Flow channel and direction:

[0149] 2> It can trigger an RBR-Q Query (510) for the corresponding QoS Flow, direction and desired bit rate.

[0150] In one embodiment of the present disclosure, when a MAC layer device of a terminal has UL resources allocated for a new transmission, the MAC layer device of the terminal may operate as follows.

[0151] 1> For each RBR-Q Query (510) that has already been triggered but not yet canceled, the following actions can be taken.

[0152] 2> If bitRateQueryProhibitTimer-Q for the corresponding QoS Flow and direction of the corresponding RBR-Q Query is set and not running; and

[0153] 2> If the MAC layer device has UL resources allocated for a new transmission and the UL resources can accommodate the RBR-Q MAC CE and its subheader as a result of the LCP defined in section 5.4.3.1 of TS38.321:

[0154] 3> In the Multiplexing and Assembly procedure, it can be instructed to create an RBR-Q MAC CE for the QoS Flow and direction of the corresponding RBR-Q Query.

[0155] 3> You can start / run bitRateQueryProhibitTimer-Q for the corresponding QoS Flow and direction of the corresponding RBR-Q Query.

[0156] 3> The RBR-Q Query (510) can be canceled.

[0157] The terminal can transmit RBR-Q MAC CE to the base station (520).

[0158] In one embodiment of the present disclosure, referring to FIG. 5, a terminal receives an RBR-Q MAC CE transmitted by a base station (530). The MAC layer device of the terminal can inform an upper layer (e.g., forwarding to an SDAP layer (540), forwarding to an application layer (550)) of the RBR-Q for the indicated QoS Flow and direction based on the RBR-Q MAC CE received from the base station. For example, the MAC layer device can forward the RBR-Q to the SDAP layer, and the SDAP layer can forward the RBR-Q to the application layer.

[0159] FIG. 6 is a diagram illustrating an RBR-Q MAC CE format according to an embodiment of the present disclosure.

[0160] Referring to FIG. 6, the RBR-Q MAC CE may include at least one of the following fields.

[0161] - QFI (QoS Flow ID, 600): The QFI field can indicate the ID of the QoS Flow to which the RBR-Q message (sent by the base station to the terminal) or the RBR-Q Query message (sent by the terminal to the base station) applies. For example, the length of the QFI field can be 6 bits. For example, the length of the QFI field can be greater than 6 bits.

[0162] - Uplink / Downlink (UL / DL, 610): The UL / DL field can indicate whether the corresponding RBR-Q or RBR-Q Query applies to the uplink or the downlink. For example, if the field can have a length of 1 bit, it can indicate downlink with 0 and uplink with 1. For example, if the field can have a length of 1 bit, it can indicate downlink with 1 and uplink with 0. As another example, by allocating 1 bit to each of the UL field and the DL field, the corresponding RBR-Q or RBR-Q Query can be designed to be applied only to the UL (UL = 1, DL = 0), or only to the DL (UL = 0, DL = 1), or to both the UL and DL (UL = 1, DL = 1).

[0163] -Bit Rate (620, 630): The Bit Rate field may indicate one of the bit rate indices defined in a given bit rate table. For example, the bit rate table may be defined as in Table 3 described above. For example, the bit rate table may be a different table from Table 3. For example, the Bit Rate field may have a length of 6 bits, less than 6 bits, or greater than 6 bits. For example, in the case of RBR-Q (transmission from the base station to the terminal), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate a bit rate recommended by the base station. For example, in the case of RBR-Q Query (transmission from the terminal to the base station), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate a bit rate desired by the terminal.

[0164] -X(640): This field can indicate a bit rate multiplier. For example, if the terminal supports the RBR-Q multiplier function, and the base station sets a bit rate multiplier (e.g., referred to as bitRateMultiplier-Q) for the QoS Flow indicated by the QFI field (600) through an RRC message (e.g., RRCReconfiguration), if the X field is set to 1, the actual bit rate value can be determined as a value obtained by multiplying the bit rate corresponding to the Index indicated by the Bit Rate field (630) by the bitRateMultiplier-Q. For example, the bitRateMultiplier-Q can be set by the base station to a specific value (e.g., one of 40, 70, 100, and 200) through an RRC message.

[0165] - R(650, 660): Reserved field that can be set to 0.

[0166] FIG. 7 is a diagram illustrating an RBR-Q MAC CE format according to an embodiment of the present disclosure.

[0167] Referring to FIG. 7, in order to perform RBR-Q or RBR-Q Query for multiple QoS Flows through one RBR-Q MAC CE, the RBR-Q MAC CE may include at least one of the following fields.

[0168] - QFI (QoS Flow ID, 700): The QFI field can indicate the ID of the QoS Flow to which the RBR-Q message (sent by the base station to the terminal) or the RBR-Q Query message (sent by the terminal to the base station) applies. For example, the length of the QFI field can be 6 bits. For example, the length of the QFI field can be greater than 6 bits.

[0169] - Uplink / Downlink (UL / DL, 710): The UL / DL field can indicate whether the corresponding RBR-Q or RBR-Q Query applies to the uplink or the downlink. For example, if the field can have a length of 1 bit, it can indicate downlink with 0 and uplink with 1. For example, if the field can have a length of 1 bit, it can indicate downlink with 1 and uplink with 0. As another example, by allocating 1 bit to each of the UL field and the DL field, the corresponding RBR-Q or RBR-Q Query can be designed to be applied only to the UL (UL = 1, DL = 0), only to the DL (UL = 0, DL = 1), or to both the UL and DL (UL = 1, DL = 1).

[0170] -Bit Rate (730): The Bit Rate field may indicate one of the bit rate indices defined in a given bit rate table. For example, the bit rate table may be defined as in Table 3 described above. For example, the bit rate table may be a different table from Table 3. For example, the Bit Rate field may have a length of 6 bits, less than 6 bits, or greater than 6 bits. For example, in the case of RBR-Q (transmission from the base station to the terminal), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate a bit rate recommended by the base station. For example, in the case of RBR-Q Query (transmission from the terminal to the base station), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate a bit rate desired by the terminal.

[0171] -X(740): This field can indicate a bit rate multiplier. For example, if the terminal supports the RBR-Q multiplier function, and the base station sets a bit rate multiplier (e.g., referred to as bitRateMultiplier-Q) for the QoS Flow indicated by the QFI field (700) through an RRC message (e.g., RRCReconfiguration), if the X field is set to 1, the actual bit rate value can be determined as a value obtained by multiplying the bit rate corresponding to the Index indicated by the Bit Rate field (730) by the bitRateMultiplier-Q. For example, the bitRateMultiplier-Q can be set by the base station to a specific value (e.g., one of 40, 70, 100, and 200) through an RRC message.

[0172] - R(750): Reserved field, can be set to 0.

[0173] - E(760): The Extension field may be a flag indicating whether the immediately preceding RBR-Q is the last RBR-Q in the RBR-Q MAC CE. If the field is set to 1, it may indicate that at least one more RBR-Q is included in the RBR-Q MAC CE, and if the field is set to 0, it may indicate that the immediately preceding RBR-Q is the last RBR-Q in the RBR-Q MAC CE. For example, the RBR-Q may mean an information unit that indicates / queries a recommended bit rate for a specific QoS Flow and a specific direction as a combination including at least one field among QFI, UL / DL, Bit Rate, and X.

[0174] FIG. 8 is a diagram illustrating an RBR-Q MAC CE format according to an embodiment of the present disclosure.

[0175] Referring to FIG. 8, in order to perform RBR-Q or RBR-Q Query for multiple QoS Flows through one RBR-Q MAC CE, the RBR-Q MAC CE may include at least one of the following fields.

[0176] - Q Bitmap (800, 801, 802, 803, 804, 805, 806, 807): Each bit of the Q Bitmap can have a 1:1 mapping relationship with a QoS Flow ID (QFI) in a specific order. For example, the mapping relationship can be defined such that the first bit corresponds to QFI X, the second bit corresponds to QFI X+1 or QFI X-1, and so on. The value of the Q bit mapped to a specific QFI can be 1 or 0. For example, if the value of the bit is 1, it can indicate that an RBR (a combination of Bit Rate, X, and UL / DL fields) exists in the RBR-Q MAC CE for the corresponding QFI. If the value of the bit mapped to a specific QFI is 0, it can indicate that an RBR (a combination of Bit Rate, X, and UL / DL fields) does not exist in the RBR-Q MAC CE for the corresponding QFI. Accordingly, the number of RBRs (a combination of Bit Rate, X, and UL / DL fields) per QoS Flow included in the RBR-Q MAC CE may be equal to the number of bits set to 1 in the Q Bitmap, and the arrangement order of the RBRs (a combination of Bit Rate, X, and UL / DL fields) in the RBR-Q MAC CE may be determined by the ascending or descending order of QFIs among the QFIs set to 1 in the Q Bitmap.

[0177] -Bit Rate (810): The Bit Rate field may indicate one of the bit rate-specific Indices defined in a bit rate table for the corresponding QoS Flow. For example, the bit rate table may be defined as in Table 3 described above. For example, the bit rate table may be a different table from Table 3. For example, the Bit Rate field may have a length of 6 bits, or less than 6 bits, or greater than 6 bits. For example, in the case of RBR-Q (transmission from the base station to the terminal), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate a bit rate recommended by the base station. For example, in the case of RBR-Q Query (transmission from the terminal to the base station), the bit rate corresponding to the Index indicated by the Bit Rate field may indicate a bit rate desired by the terminal. Multiple Bit Rate fields may be defined, and each Bit Rate field may correspond to a QoS flow ID based on the Q Bitmap. For example, the Bit Rate field can be set to the number of times the value of the Q bitmap is set to 1, and the Bit Rate field can be defined to sequentially correspond to the QFIs whose value of the Q bitmap is set to 1.

[0178] - Uplink / Downlink (UL / DL, 830): The UL / DL field can indicate whether the RBR-Q or RBR-Q Query applies to the uplink or downlink for the corresponding QoS Flow. For example, if the field can have a length of 1 bit, it can indicate downlink with 0 and uplink with 1. For example, if the field can have a length of 1 bit, it can indicate downlink with 1 and uplink with 0. As another example, the UL field and the DL field can be each assigned 1 bit, so that the RBR-Q or RBR-Q Query can be designed to be applied only to the UL (UL = 1, DL = 0), only to the DL (UL = 0, DL = 1), or to both the UL and DL (UL = 1, DL = 1). Multiple UL / DL fields can be defined, and each Bit Rate field can correspond to a QoS flow ID based on the Q Bitmap. For example, the UL / DL fields can be set as many times as the number of times the value of the Q Bitmap is set to 1, and the UL / DL fields can be defined to sequentially correspond to QFIs whose value of the Q Bitmap is set to 1.

[0179] -X(820): This field can indicate a bit rate multiplier. For example, if the terminal supports the RBR-Q multiplier function, and the base station sets a bit rate multiplier (e.g., referred to as bitRateMultiplier-Q) for the corresponding QoS Flow through an RRC message (e.g., RRCReconfiguration), and if the X field is set to 1, the actual bit rate value can be determined as a value obtained by multiplying the bit rate corresponding to the Index indicated by the Bit Rate field (810) by the bitRateMultiplier-Q. For example, the bitRateMultiplier-Q can be set by the base station to a specific value (e.g., one of 40, 70, 100, and 200) through an RRC message. Multiple X fields can be defined, and each Bit Rate field can correspond to a QoS flow ID based on the Q Bitmap. For example, the X fields can be set as many times as the value value of the Q Bitmap is set to 1, and the X fields can be defined to sequentially correspond to QFIs whose value value of the Q Bitmap is set to 1.

[0180] As one embodiment of the present disclosure, referring to FIG. 3, a base station may transmit a UE capability request (UECapabilityEnquiry) message requesting a capability report to a UE in an RRC connected (RRC_CONNECTED) state. The base station may include a UE capability request for each RAT type in the UECapabilityEnquiry message. For example, when the base station requests the UE to generate a UECapabilityInformation message through the capability request message, the base station may include filtering information that may indicate conditions and restrictions. For example, the filtering information may include frequency band list information requesting a capability report for each RAT type. For example, the filtering information may indicate whether the UE for each RAT type should report whether it supports a specific function. For example, the filtering information may indicate whether the terminal should report support for RBR-Q Query message / MAC CE and RBR-Q message / MAC CE for a particular RAT type (e.g., NR).

[0181] In one embodiment of the present disclosure, referring to FIG. 3, a terminal may configure a terminal capability information (UECapabilityInformation) message corresponding to a UECapabilityEnquiry message and report it to a base station in response to the corresponding UE capability enquiry message.

[0182] For example, the terminal may include a field in the UECapabilityInformation message indicating whether the terminal supports the RBR-Q Query message transmitted to the base station. For example, the field may be expressed as 1-bit information (e.g., 1: supported, 0: not supported). For example, if the field is included, it may indicate that the corresponding function is supported, and if the field is not included, it may indicate that the corresponding function is not supported.

[0183] For example, the terminal may include a field in the UECapabilityInformation message indicating whether the base station supports the RBR-Q message transmitted to the terminal. For example, the field may be expressed as 1-bit information (e.g., 1: supported, 0: not supported). For example, if the field is included, it may indicate that the corresponding function is supported, and if the field is not included, it may indicate that the corresponding function is not supported.

[0184] For example, the terminal may include a field in the UECapabilityInformation message indicating whether it supports the bit rate multiplier function of the RBR-Q MAC CE. For example, the field may be expressed as 1-bit information (e.g., 1: supported, 0: not supported). For example, if the field is included, it may indicate that the corresponding function is supported, and if the field is not included, it may indicate that the corresponding function is not supported.

[0185] In one embodiment of the present disclosure, the base station can determine whether the terminal supports the RBR-Q message through the UECapabilityInformation message transmitted by the terminal. For example, if the base station determines that the terminal supports the RBR-Q message, the base station can transmit an RBR-Q MAC CE to the terminal.

[0186] In one embodiment of the present disclosure, the base station can determine whether the terminal supports the RBR-Q Query message through the UECapabilityInformation message transmitted by the terminal. For example, if the base station determines that the terminal supports the RBR-Q Query message, the base station can set bitRateQueryProhibitTimer-Q for each QoS Flow through an RRCReconfiguration message. The bitRateQueryProhibitTimer-Q can be used to restrict the terminal from transmitting the RBR-Q Query when the timer is running in order to prevent the RBR-Q Query from occurring too frequently. The size of the timer can be set to a value having a specific time unit (e.g., second, millisecond, microsecond).

[0187] In one embodiment of the present disclosure, the base station can determine whether the terminal supports the RBR-Q Query message through the UECapabilityInformation message transmitted by the terminal. For example, if the base station determines that the terminal supports the RBR-Q Query message, the base station can configure the terminal to perform an RBR-Q Query through an RRCReconfiguration message.

[0188] In one embodiment of the present disclosure, as a method of querying a recommended bit rate by QoS Flow, a terminal in an RRC_CONNECTED state can query a base station for a distribution ratio (Scaling Factor) of a recommended bit rate corresponding to each QoS Flow among the total recommended bit rates of the corresponding direction of the logical channel, for a QoS Flow included in the corresponding direction of a specific logical channel, for a specific direction of a specific logical channel. For example, the terminal can query the base station for a recommended bit rate distribution ratio of 0.5, 0.3, and 0.2 for three QoS Flows k-1, k-2, and k-3 included in the uplink of a specific logical channel K through an RRC message / MAC CE. At this time, the recommended bit rate distribution ratio by QoS Flow included in the query may mean a distribution ratio desired by the terminal. For example, the sum of the recommended bit rate distribution ratios of all QoS Flows belonging to the same direction of the same logical channel may be limited to 1.

[0189] In one embodiment of the present disclosure, as a method of setting a recommended bit rate per QoS Flow, a base station may set a recommended bit rate distribution ratio (Scaling Factor) corresponding to each QoS Flow among the total recommended bit rates of the corresponding direction of the logical channel for each QoS Flow included in the corresponding direction of a specific logical channel for a terminal in an RRC_CONNECTED state, for a specific direction of a specific logical channel. For example, the base station may set the recommended bit rate distribution ratios to 0.5, 0.3, and 0.2 for three QoS Flows k-1, k-2, and k-3 included in the uplink of a specific logical channel K to the terminal through an RRC message / MAC CE. In this case, the set recommended bit rate distribution ratio per QoS Flow may mean a distribution ratio recommended by the base station. For example, the sum of the recommended bit rate distribution ratios of all QoS Flows belonging to the same direction of the same logical channel may be limited to 1.

[0190] In one embodiment of the present disclosure, if a base station has already set a recommended bit rate distribution ratio for each QoS Flow included in a specific direction of a specific logical channel of a terminal, and the terminal receives an RBR MAC CE including an RBR for each logical channel and direction transmitted by the base station, the terminal can determine a recommended bit rate for each QoS Flow by the recommended bit rate distribution ratio for each QoS Flow included in the logical channel and direction, based on the recommended bit rate for the corresponding logical channel and direction received through the RBR MAC CE.

[0191] For example, if a base station sets a recommended bit rate for the uplink of logical channel K to 500 kbps, and if the recommended bit rate distributions of three QoS Flows k-1, k-2, and k-3 included in the uplink of the logical channel K are 0.5, 0.3, and 0.2, the recommended bit rates of the QoS Flows k-1, k-2, and k-3 can be determined as 250 kbps, 150 kbps, and 100 kbps, respectively.

[0192] In one embodiment of the present disclosure, an RBR-Q MAC CE transmitted by a base station to a terminal may be indicated as a corresponding MAC CE by setting the LCID (Logical Channel ID) or eLCID field of a MAC subheader to a predetermined value that is distinguished from other MAC CEs.

[0193] In one embodiment of the present disclosure, an RBR-Q MAC CE transmitted by a terminal to a base station may be indicated as the corresponding MAC CE by setting the LCID (Logical Channel ID) or eLCID field of the MAC subheader to a predetermined value that is distinguished from other MAC CEs.

[0194] In one embodiment of the present disclosure, when allocating uplink resources during Logical Channel Prioritization operation, including RBR-Q MAC CE, each logical channel may be prioritized in descending priority order.

[0195] - MAC CE for C-RNTI, or data from UL-CCCH;

[0196] - MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation;

[0197] - MAC CE for Sidelink Configured Grant Confirmation;

[0198] - MAC CE for LBT failure;

[0199] - MAC CE for SL LBT failure according to clause 5.31.2;

[0200] - MAC CE for Timing Advance Report;

[0201] - MAC CE for Delay Status Report;

[0202] - MAC CE for SL-BSR prioritized according to clause 5.22.1.6;

[0203] - MAC CE for (Extended) BSR, with exception of BSR included for padding;

[0204] - MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR or MAC CE for Single Entry PHR with assumed PUSCH, or MAC CE for Multiple Entry PHR with assumed PUSCH, or MAC CE for Enhanced Single Entry PHR for multiple TRP or MAC CE for Enhanced Multiple Entry PHR for multiple TRP, or MAC CE for Enhanced Single Entry PHR for multiple TRP STx2P or MAC CE for Enhanced Multiple Entry PHR for multiple TRP STx2P;

[0205] - MAC CE for Positioning Measurement Gap Activation / Deactivation Request;

[0206] - MAC CE for the number of Desired Guard Symbols;

[0207] - MAC CE for Case-6 Timing Request;

[0208] - MAC CE for (Extended) Pre-emptive BSR;

[0209] - MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding;

[0210] - MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

[0211] - data from any Logical Channel, except data from UL-CCCH;

[0212] - MAC CE for Recommended bit rate query or RBR-Q query;

[0213] - MAC CE for BSR included for padding;

[0214] - MAC CE for SL-BSR included for padding.

[0215] NOTE 2: Prioritization among MAC CEs of same priority is up to UE implementation.

[0216] In one embodiment of the present disclosure, when allocating uplink resources during a Logical Channel Prioritization operation, including RBR-Q MAC CE, each logical channel may be prioritized in descending priority order.

[0217] - MAC CE for C-RNTI, or data from UL-CCCH;

[0218] - MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation;

[0219] - MAC CE for Sidelink Configured Grant Confirmation;

[0220] - MAC CE for LBT failure;

[0221] - MAC CE for SL LBT failure according to clause 5.31.2;

[0222] - MAC CE for Timing Advance Report;

[0223] - MAC CE for Delay Status Report;

[0224] - MAC CE for SL-BSR prioritized according to clause 5.22.1.6;

[0225] - MAC CE for (Extended) BSR, with exception of BSR included for padding;

[0226] - MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR or MAC CE for Single Entry PHR with assumed PUSCH, or MAC CE for Multiple Entry PHR with assumed PUSCH, or MAC CE for Enhanced Single Entry PHR for multiple TRP or MAC CE for Enhanced Multiple Entry PHR for multiple TRP, or MAC CE for Enhanced Single Entry PHR for multiple TRP STx2P or MAC CE for Enhanced Multiple Entry PHR for multiple TRP STx2P;

[0227] - MAC CE for Positioning Measurement Gap Activation / Deactivation Request;

[0228] - MAC CE for the number of Desired Guard Symbols;

[0229] - MAC CE for Case-6 Timing Request;

[0230] - MAC CE for (Extended) Pre-emptive BSR;

[0231] - MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding;

[0232] - MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

[0233] - data from any Logical Channel, except data from UL-CCCH;

[0234] - MAC CE for Recommended bit rate query;

[0235] - MAC CE for RBR-Q query;

[0236] - MAC CE for BSR included for padding;

[0237] - MAC CE for SL-BSR included for padding.

[0238] NOTE 2: Prioritization among MAC CEs of same priority is up to UE implementation.

[0239] In one embodiment of the present disclosure, when allocating uplink resources during a Logical Channel Prioritization operation, including RBR-Q MAC CE, each logical channel may be prioritized in descending priority order.

[0240] - MAC CE for C-RNTI, or data from UL-CCCH;

[0241] - MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation;

[0242] - MAC CE for Sidelink Configured Grant Confirmation;

[0243] - MAC CE for LBT failure;

[0244] - MAC CE for SL LBT failure according to clause 5.31.2;

[0245] - MAC CE for Timing Advance Report;

[0246] - MAC CE for Delay Status Report;

[0247] - MAC CE for SL-BSR prioritized according to clause 5.22.1.6;

[0248] - MAC CE for (Extended) BSR, with exception of BSR included for padding;

[0249] - MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR or MAC CE for Single Entry PHR with assumed PUSCH, or MAC CE for Multiple Entry PHR with assumed PUSCH, or MAC CE for Enhanced Single Entry PHR for multiple TRP or MAC CE for Enhanced Multiple Entry PHR for multiple TRP, or MAC CE for Enhanced Single Entry PHR for multiple TRP STx2P or MAC CE for Enhanced Multiple Entry PHR for multiple TRP STx2P;

[0250] - MAC CE for Positioning Measurement Gap Activation / Deactivation Request;

[0251] - MAC CE for the number of Desired Guard Symbols;

[0252] - MAC CE for Case-6 Timing Request;

[0253] - MAC CE for (Extended) Pre-emptive BSR;

[0254] - MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding;

[0255] - MAC CE for IAB-MT Recommended Beam Indication, or MAC CE for Desired IAB-MT PSD range, or MAC CE for Desired DL Tx Power Adjustment;

[0256] - data from any Logical Channel, except data from UL-CCCH;

[0257] - MAC CE for RBR-Q query;

[0258] - MAC CE for Recommended bit rate query;

[0259] - MAC CE for BSR included for padding;

[0260] - MAC CE for SL-BSR included for padding.

[0261] NOTE 2: Prioritization among MAC CEs of same priority is up to UE implementation.

[0262] FIG. 9 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0263] Referring to FIG. 9, the terminal may include a transceiver, which refers to a terminal receiving unit (900) and a terminal transmitting unit (910), a memory (not shown), and a terminal processing unit (905, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (900, 910), the memory, and the terminal processing unit (905) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0264] A transceiver unit can transmit and receive signals to and from a base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0265] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0266] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0267] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform terminal component control operations by executing programs stored in memory.

[0268] FIG. 10 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0269] Referring to FIG. 10, the base station may include a transceiver, which refers to a base station receiver (1000) and a base station transmitter (1010), a memory (not shown), and a base station processor (1005, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (1000, 1010), the memory, and the base station processor (1005) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0270] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0271] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

[0272] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0273] The processor can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0274] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

[0275] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).

[0276] The various components and modules of the entity, base station or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0277] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0278] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0279] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0280] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0281] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the respective embodiments may be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment may be combined with each other to operate a base station and a terminal. In addition, the embodiments of the present disclosure are applicable to other communication systems, and other modifications based on the technical idea of ​​the embodiments may also be implemented.

Claims

1. In a method performed by a terminal in a wireless communication system, A step of transmitting terminal performance information to a base station, the terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate; A step of receiving an RRC (radio resource control message) message including setting information related to the above recommended bit rate from the base station; and A method comprising the step of receiving a message from the base station including information on the recommended bit rate for the QoS (quality of service) flow based on the above setting information.

2. In paragraph 1, comprising the step of transmitting a message querying the recommended bit rate for the QoS flow to the base station, and A method in which a message querying the above recommended bit rate includes a QFI (QoS flow ID) field and a bit rate field.

3. In paragraph 2, The message querying the above recommended bit rate includes information fields for multiple QoS flows, and A method in which the above QFI field and the above bit rate field are included for each of the plurality of QoS flows.

4. In paragraph 1, The above RRC message includes a recommended bit rate query prohibit timer per QoS flow, A method in which transmission of a message querying a recommended bit rate for a first QoS flow is prohibited when a bit rate query prohibit timer for the first QoS flow is running.

5. In a method performed by a base station in a wireless communication system, A step of receiving terminal performance information from a terminal, the terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate; A step of transmitting an RRC (radio resource control message) message including setting information related to the above recommended bit rate to the terminal; and A method comprising the step of transmitting a message including information on the recommended bit rate for a QoS (quality of service) flow to the terminal based on the above setting information.

6. In paragraph 5, comprising a step of receiving a message querying the recommended bit rate for the QoS flow from the terminal, and A method in which a message querying the above recommended bit rate includes a QFI (QoS flow ID) field and a bit rate field.

7. In paragraph 6, The message querying the above recommended bit rate includes information fields for multiple QoS flows, and A method in which the above QFI field and the above bit rate field are included for each of the plurality of QoS flows.

8. In paragraph 5, The above RRC message includes a recommended bit rate query prohibit timer per QoS flow, A method in which transmission of a message querying a recommended bit rate for a first QoS flow is prohibited when a bit rate query prohibit timer for the first QoS flow is running.

9. In the terminal of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor, and executable individually or in any combination of said at least one processor, such that said terminal, Transmitting terminal performance information to a base station, the terminal performance information including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate, Receive an RRC (radio resource control message) message including setting information related to the above recommended bit rate from the base station, and A memory storing a command for receiving a message including information about the recommended bit rate for a QoS (quality of service) flow from the base station based on the above setting information; A terminal including .

10. In paragraph 9, The above command causes the terminal to transmit a message querying the recommended bit rate for the QoS flow to the base station, and A method in which a message querying the above recommended bit rate includes a QFI (QoS flow ID) field and a bit rate field.

11. In paragraph 10, The message querying the above recommended bit rate includes information fields for multiple QoS flows, and The terminal in which the above QFI field and the above bit rate field are included for each of the plurality of QoS flows.

12. In paragraph 9, The above RRC message includes a recommended bit rate query prohibit timer per QoS flow, A terminal that is prohibited from sending a message querying a recommended bit rate for the first QoS flow when the bit rate query prohibit timer for the first QoS flow is running.

13. In a base station of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor, and executable individually or in any combination of said at least one processor, such that said base station, Receive terminal performance information from a terminal, including at least one of first information indicating performance for a query of a recommended bit rate (RBR) or second information indicating performance for application of the recommended bit rate; Transmitting an RRC (radio resource control message) message containing setting information related to the above recommended bit rate to the terminal, and A memory storing a command for transmitting a message including information about the recommended bit rate for a QoS (quality of service) flow to the terminal based on the above setting information; Base station including.

14. In paragraph 13, The Sangri command causes the base station to receive a message from the terminal querying the recommended bit rate for the QoS flow, and The message querying the above recommended bit rate includes a QFI (QoS flow ID) field and a bit rate field, The message querying the above recommended bit rate includes information fields for multiple QoS flows, and A base station in which the above QFI field and the above bit rate field are included for each of the plurality of QoS flows.

15. In paragraph 13, The above RRC message includes a recommended bit rate query prohibit timer per QoS flow, A base station that prohibits transmission of a message querying a recommended bit rate for the first QoS flow when the bit rate query prohibit timer for the first QoS flow is running.

Images