WO2020149639A1 - Procédé et appareil permettant de rapporter la capacité ue d'un terminal dans un système de communication mobile de génération suivante - Google Patents

Procédé et appareil permettant de rapporter la capacité ue d'un terminal dans un système de communication mobile de génération suivante Download PDF

Info

Publication number
WO2020149639A1
WO2020149639A1 PCT/KR2020/000735 KR2020000735W WO2020149639A1 WO 2020149639 A1 WO2020149639 A1 WO 2020149639A1 KR 2020000735 W KR2020000735 W KR 2020000735W WO 2020149639 A1 WO2020149639 A1 WO 2020149639A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
capability
base station
message
information
Prior art date
Application number
PCT/KR2020/000735
Other languages
English (en)
Inventor
Seungri Jin
Kicheol NAM
Sangbum Kim
Kisung Park
Jangbok LEE
Original Assignee
Samsung Electronics Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Priority to EP20741312.1A priority Critical patent/EP3831108A4/fr
Priority to CN202080009373.9A priority patent/CN113302957A/zh
Publication of WO2020149639A1 publication Critical patent/WO2020149639A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/063—Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the disclosure relates to an operation of a terminal and a base station in a mobile communication system.
  • the disclosure relates to a mobile communication system and, more particularly, to a method in which a terminal reports its own user equipment (UE) capability. Further, the disclosure proposes a generalized terminal reporting procedure in the case where a terminal receives or does not receive a request for reporting UE capability from a base station in multiple radio access technologies, and includes a procedure capable of reflecting a temporary change in the capability of the terminal.
  • UE user equipment
  • the 5G communication system or the pre-5G communication system is called a beyond 4G network communication system or a post long term evolution (LTE) system.
  • LTE post long term evolution
  • an implementation of the 5G communication system in a mmWave band for example, 60 GHz band
  • a mmWave band for example, 60 GHz band
  • technologies such as beamforming, massive multiple input multiple output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, and large scale antenna are being discussed as means to mitigate a propagation path loss in the mm Wave band and increase a propagation transmission distance.
  • MIMO massive multiple input multiple output
  • FD-MIMO Full Dimensional MIMO
  • array antenna analog beam-forming
  • large scale antenna are being discussed as means to mitigate a propagation path loss in the mm Wave band and increase a propagation transmission distance.
  • the 5G communication system has developed technologies, such as an evolved small cell, an advanced small cell, a cloud Radio Access Network (RAN), an ultra-dense network, Device to Device communication (D2D), a wireless backhaul, a moving network, cooperative communication, Coordinated Multi-Points (CoMP), and received interference cancellation to improve the system network.
  • ACM Advanced Coding Modulation
  • FSK Hybrid Frequency-Shift Keying
  • QAM Quadrature Amplitude Modulation
  • SWSC Sliding Window Superposition Coding
  • advanced access technologies such as Filter Bank Multi Carrier (FBMC), Non Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA).
  • IoT Internet of Things
  • IoE Internet of Everything
  • IoT In order to implement IoT, technical factors, such as a detection technique, wired/wireless communication, network infrastructure, service-interface technology, and security technology are required, and research on technologies, such as a sensor network, Machine-to-Machine (M2M) communication, Machine-Type Communication (MTC), and the like for connection between objects has recently been conducted.
  • M2M Machine-to-Machine
  • MTC Machine-Type Communication
  • IT Internet Technology
  • the IoT may be applied to fields, such as those of a smart home, a smart building, a smart city, a smart car, a connected car, a smart grid, health care, a smart home appliance, or high-tech medical services through the convergence of the Information Technology (IT) of the related art and various industries.
  • IT Information Technology
  • the 5G communication technology such as a sensor network, machine-to-machine (M2M) communication, and machine-type communication (MTC)
  • M2M machine-to-machine
  • MTC machine-type communication
  • the application of a cloud RAN as the big data processing technology may be an example of convergence of the 5G technology and the IoT technology.
  • the disclosure considers a method in which a new radio (NR) terminal is able to make a request for base station management suitable for the current UE capability by reporting, to a base station, a temporary UE capability with respect to a temporary change in the UE capability of the terminal, in addition to a method of reporting its own UE capability upon a request from the base station.
  • NR new radio
  • the terminal In the existing procedure, only when a terminal receives a request for a UE capability report through a radio resource control (RRC) message from a base station, the terminal produces a UE capability for an indicated radio access technology (RAT) type according to the request by the base station and transmits the UE capability to the base station using a message reporting the same.
  • RRC radio resource control
  • RAT radio access technology
  • an aspect of the disclosure is to provide an operation of a terminal and a base station in a mobile communication system.
  • a method by a terminal in a wireless communication system includes receiving, from a base station, a first message including configuration information associated with overheating, identifying whether internal overheating is detected, and reporting, to the base station, a second message including overheating assistance information based on the configuration information, in a case where the internal overheating is detected, wherein the overheating assistance information includes information on at least one of a number of component carriers, a bandwidth, or a number of multiple input multiple output (MIMO) layers.
  • MIMO multiple input multiple output
  • a method by a base station in a wireless communication system includes transmitting, to a terminal, a first message including configuration information associated with overheating, and receiving, from the terminal, a second message including overheating assistance information based on the configuration information, wherein the overheating assistance information includes information on at least one of a number of component carriers, a bandwidth, or a number of MIMO layers.
  • a terminal in a wireless communication system includes a transceiver, and at least one processor configured to receive, from a base station via the transceiver, a first message including configuration information associated with overheating, identify whether internal overheating is detected, and report, to the base station via the transceiver, a second message including overheating assistance information based on the configuration information, in a case where the internal overheating is detected, wherein the overheating assistance information includes information on at least one of a number of component carriers, a bandwidth, or a number of MIMO layers.
  • a base station in a wireless communication system includes a transceiver, and at least one processor configured to transmit, to a terminal via the transceiver, a first message including configuration information associated with overheating, and receiving, from the terminal via the transceiver, a second message including overheating assistance information based on the configuration information, wherein the overheating assistance information includes information on at least one of a number of component carriers, a bandwidth, or a number of MIMO layers.
  • UE user equipment
  • a terminal is able to make a request to a base station for management suitable for the current UE capability by reporting, to the base station, a temporary UE capability according to a temporary change in the UE capability of the terminal, in addition to a method of reporting its own UE capability according to a request from the base station.
  • a new radio (NR) terminal is able to voluntarily report, to a base station, the UE capability changed due to a temporary change in the UE capability or the like, in addition to the case where the terminal receives a request for a UE capability report from the base station through an RRC message, thereby transmitting a dynamic UE capability report to the base station.
  • the base station can perform more appropriate resource allocation to the terminal and terminal management, and the terminal can also obtain the performance conforming to the actual UE capability.
  • FIG. 1 is a diagram illustrating a structure of a long term evolution (LTE) system according to an embodiment of the disclosure
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the disclosure
  • FIG. 3 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the disclosure
  • FIG. 4 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the disclosure
  • FIG. 5 is a diagram illustrating a structure of a message for reporting user equipment (UE) capability in a new radio (NR) system according to an embodiment of the disclosure
  • FIG. 6 is a diagram illustrating a method of a terminal in a radio resource control (RRC) connection state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 7 is a diagram illustrating a method of a terminal in an RRC connection state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 8 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 9 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • FIG. 10 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 11 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 12 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 13 is a diagram illustrating a method of a terminal in an RRC inactive state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 14 is a diagram illustrating a method of a terminal in an RRC inactive state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 15 is a diagram illustrating a method of a terminal in an RRC inactive state requesting a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 16 is a diagram illustrating an overall operation in which a terminal in an RRC connection state requests a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 17 is a diagram illustrating an overall operation in which a terminal in an idle or inactive state requests a temporary change in UE capability according to an embodiment of the disclosure
  • FIG. 18 is a diagram illustrating an overall operation of a base station that receives a temporary UE capability change of a terminal according to an embodiment of the disclosure
  • FIG. 19 is a diagram illustrating a configuration of a terminal according to an embodiment of the disclosure.
  • FIG. 20 is a diagram illustrating a configuration of a base station according to an embodiment of the disclosure.
  • 3GPP LTE 3rd-generation partnership project long-term evolution
  • a base station is an entity that performs resource allocation with respect to a terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a base station (BS), a radio access unit, a base station controller, or a node in a network.
  • the terminal may include user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function.
  • DL downlink
  • UL uplink of a signal transmitted from a terminal to a base station.
  • embodiments of the disclosure will be described based on an NR system below, the embodiments of the disclosure may be applied to other communication systems having a similar technical background or channel form. In addition, the embodiments of the disclosure may be applied to other communication systems through some modifications according to a determination of those skilled in the art without departing from the scope of the disclosure.
  • PDSCH Physical Downlink Shared Channel
  • higher layer signaling may be a method of transmitting a signal from a base station to a terminal using a downlink data channel of a physical layer or a signal from a terminal to a base station using an uplink data channel of a physical layer, and may also be referred to as "RRC signaling” or a “medium access control (MAC) control element (CE)".
  • RRC signaling or a “medium access control (MAC) control element (CE)
  • FIG. 1 is a diagram illustrating a structure of an LTE system according to an embodiment of the disclosure.
  • a radio access network of an LTE system includes next-generation base stations (Evolved Node Bs) (hereinafter, referred to as “eNBs”, “Node Bs”, or “base stations”) 1a-05, 1a-10, 1a-15, and 1a-20, a mobility management entity (MME) 1a-25, and a serving-gateway (S-GW) 1a-30.
  • eNBs next-generation base stations
  • MME mobility management entity
  • S-GW serving-gateway
  • User equipment 1a-35 accesses an external network through the eNBs 1a-05, 1a-10, 1a-15, and 1a-20 and the S-GW 1a-30.
  • the eNBs 1a-05, 1a-10, 1a-15, and 1a-20 correspond to existing Node Bs of a universal mobile telecommunication system (UMTS).
  • the eNB is connected to the UE 1a-35 via a radio channel and plays a more complex role than the existing Node B.
  • UMTS universal mobile telecommunication system
  • VoIP voice-over-IP
  • a device for collecting status information such as buffer status, available transmission power status, and channel status of UEs, and performing scheduling is required.
  • the eNBs 1a-05, 1a-10, 1a-15, and 1a-20 serve as such a device.
  • One eNB typically controls multiple cells.
  • the LTE system uses, as radio access technology, orthogonal frequency division multiplexing (hereinafter, referred to as "OFDM") in, for example, a 20 MHz bandwidth.
  • OFDM orthogonal frequency division multiplexing
  • AMC adaptive modulation and coding
  • the S-GW 1a-30 is a device for providing data bearers and generates or removes data bearers under the control of the MME 1a-25.
  • the MME 1a-25 is a device that performs various control functions, as well as a mobility management function for a terminal, and is connected to a plurality of base stations 1a-05, 1a-10, 1a-15, and 1a-20.
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the disclosure.
  • the radio protocol of an LTE system includes a packet data convergence protocol (PDCP) 1b-05 or 1b-40, a radio link control (RLC) 1b-10 or 1b-35, and a medium access control (MAC) 1b-15 or 1b-30 in a terminal and an eNB, respectively.
  • the PDCP 1b-05 or 1b-40 performs operations, such as IP header compression/decompression and the like.
  • the primary functions of the PDCP are summarized as follows.
  • PDUs packet data units
  • AM RLC acknowledged mode
  • the radio link control (hereinafter, referred to as "RLC") 1b-10 or 1b-35 reconfigures a PDCP PDU (packet data unit) to an appropriate size and performs automatic repeat query (ARQ) operation and the like.
  • RLC radio link control
  • the MAC 1b-15 or 1b-30 is connected to a plurality of RLC entities configured in a terminal or a base station, multiplexes RLC PDUs into MAC PDUs, and demultiplexes RLC PDUs from MAC PDUs.
  • the primary functions of the MAC are summarized as follows.
  • MBMS multimedia broadcast multicast service
  • the physical layers 1b-20 and 1b-25 channel-code and modulate higher layer data, and convert the same into OFDM symbols to then be transmitted through a radio channel, or demodulate OFDM symbols received through a radio channel and channel-decode the same to then be transmitted to higher layers.
  • hybrid ARQ HARQ
  • ACK HARQ acknowledgement
  • NACK Neg Acknowledgement
  • Downlink HARQ ACK/NACK information with respect to uplink transmission may be transmitted through a physical hybrid-ARQ indicator channel (PHICH), and uplink HARQ ACK/NACK information with respect to downlink transmission may be transmitted through a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
  • PHICH physical hybrid-ARQ indicator channel
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the PHY layer may include one or more frequencies/carriers, and a technique of simultaneously configuring and using a plurality of frequencies is called “carrier aggregation” (hereinafter, referred to as "CA").
  • CA carrier aggregation
  • the CA technique may use a primary carrier and one or more subcarriers, instead of using one carrier, for communication between a terminal ⁇ or user equipment (UE) ⁇ and a base station (E- UMTS terrestrial radio access network (UTRAN) Node B or eNB), thereby dramatically increasing the amount of transmission in proportion to the number of subcarriers.
  • a cell in the base station using a primary carrier is referred to as a "primary cell (PCell)”
  • SCell secondary cell
  • the radio resource control (RRC) layer is provided on the PDCP layer of a terminal and a base station, respectively, and the RRC layer may transmit and receive control messages related to access and measurement for radio resource control.
  • FIG. 3 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the disclosure.
  • a radio access network of a next-generation mobile communication system includes a new radio node B (hereinafter, referred to as an "NR NB") 1c-10 and a new radio core network (NR CN) ⁇ or a next-generation core network (NG CN) ⁇ 1c-05.
  • New radio user equipment (hereinafter, referred to as "NR UE” or a "terminal") 1c-15 accesses an external network 1c-20 through the NR NB 1c-10 and the NR CN 1c-05.
  • the NR CN 1c-05 may be used interchangeably with a "5G core network (5G CN)" or a "5G core (5GC)".
  • the NR NB 1c-10 corresponds to an evolved Node B (eNB) in an existing LTE system.
  • the NR NB is connected to the NR UE 1c-15 through a radio channel, and may provide services superior to those of the existing node B.
  • eNB evolved Node B
  • the NR NB 1c-10 serves as such a device.
  • One NR NB typically controls multiple cells.
  • the next-generation mobile communication system may have a bandwidth equal to or greater than the maximum bandwidth of the existing system, may employ, as wireless access technology, Orthogonal Frequency Division Multiplexing (hereinafter, referred to as "OFDM"), and may further employ a beamforming technique in addition thereto.
  • OFDM Orthogonal Frequency Division Multiplexing
  • all of a plurality of subcarrier spacings (SCS) may be supported by one system. It is also possible for the control signal and the data signal to have different SCSs.
  • the downlink transmission bandwidth and the uplink transmission bandwidth may be different from each other in a frequency-division duplexing (FDD) system in which the downlink and the uplink are separately operated by frequencies.
  • the channel bandwidth represents an RF bandwidth corresponding to a system transmission bandwidth.
  • Table 1-01 and Table 1-02 show some relationship of the system transmission bandwidth, the subcarrier spacing, and the channel bandwidth defined in the NR system in a frequency band below 6 GHz and in a frequency band above 6 GHz, respectively.
  • a transmission bandwidth of an NR system having a 100 MHz channel bandwidth and a 30 kHz subcarrier spacing includes 273 RBs.
  • N/A may be a combination of a bandwidth and a subcarrier, which are not supported by the NR system.
  • an adaptive modulation and coding (AMC) scheme in which a modulation scheme and a channel coding rate are determined according to the channel state of a terminal is applied.
  • AMC adaptive modulation and coding
  • BWPs bandwidth parts
  • the base station may configure one or more bandwidth parts with respect to the terminal, and may configure the following information for each bandwidth part.
  • the base station may configure information shown in Table 2 with respect to a terminal.
  • various parameters associated with the bandwidth part may be configured in a terminal.
  • the information may be transmitted to a terminal by a base station through higher layer signaling ⁇ e.g., radio resource control (RRC) signaling ⁇ .
  • RRC radio resource control
  • At least one of the configured bandwidth parts may be activated.
  • Information on whether or not to activate the configured bandwidth part may be semi-statically transmitted from the base station to the terminal through RRC signaling, or may be dynamically transmitted from the base station to the terminal through downlink control information (DCI).
  • DCI downlink control information
  • the terminal prior to an RRC connection may receive a configuration of an initial bandwidth part (BWP) for initial access from the base station through a master information block (MIB). More specifically, the terminal may receive configuration information on a control resource set (CORESET) and a search space through which a physical layer downlink control channel (PDCCH) for reception of system information ⁇ remaining system information, which may correspond to remaining minimum system information (RMSI) or system information block 1 (SIB1) ⁇ required for initial access through the MIB in the initial access phase may be transmitted.
  • the control resource set and the search space configured using an MIB may be regarded as an identifier (ID) "0", respectively.
  • the base station may notify the terminal of configuration information, such as frequency allocation information, time allocation information, numerology, and the like, for control resource set #0 through an MIB.
  • the base station may notify the terminal of configuration information on a monitoring period and an occasion for control resource set #0 (i.e., configuration information on search space #0) through an MIB.
  • the terminal may regard the frequency domain configured with control resource set #0 obtained from the MIB as an initial bandwidth part for initial access.
  • an identifier (ID) of the initial bandwidth part may be regarded as 0.
  • the configuration of the bandwidth part supported by the fifth generation (5G) may be used for various purposes.
  • the bandwidth supported by the terminal may be smaller than the system bandwidth, it may be supported by the configuration of the bandwidth part.
  • a frequency location of the bandwidth part may be configured in the terminal so that the terminal may transmit and receive data at a specific frequency location within the system bandwidth.
  • a base station may configure a plurality of bandwidth parts with respect to a terminal for the purpose of supporting different numerologies. For example, in order to support transmission and reception of data using a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz by a terminal, two bandwidth parts may be configured as a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz, respectively. Different bandwidth parts may be frequency-division-multiplexed, and in the case of transmitting and receiving data at a specific subcarrier spacing, a bandwidth part configured in the corresponding subcarrier spacing may be activated.
  • the base station may configure bandwidth parts having different bandwidths with respect to a terminal for the purpose of reducing power consumption of the terminal. For example, if a terminal supports a very large bandwidth (e.g., a 100 MHz bandwidth) and always transmits and receives data through the corresponding bandwidth, it may cause very large power consumption. In particular, it is very inefficient in terms of power consumption to monitor unnecessary downlink control channels with a large bandwidth of 100 MHz in the absence of traffic.
  • the base station may configure a bandwidth part having a relatively small bandwidth (e.g., a 20 MHz bandwidth part) with respect to the terminal. In the absence of traffic, the terminal may perform a monitoring operation through a 20 MHz bandwidth part, and, if data is produced, the terminal may transmit and receive data through a 100 MHz bandwidth part according to the indication of the base station.
  • the terminal that has not yet been RRC-connected may receive configuration information about an initial bandwidth part through a master information block (MIB) and/or an SIB in the initial access stage. More specifically, the terminal may be configured to have a control resource set (CORESET) for a downlink control channel through which downlink control information (DCI) for scheduling a system information block (SIB) is transmitted from an MIB of a physical broadcast channel (PBCH).
  • CORESET control resource set
  • DCI downlink control information
  • SIB system information block
  • the bandwidth of the control resource set configured through the MIB may be regarded as an initial bandwidth part, and the terminal may receive a PDSCH through which an SIB is transmitted through the configured initial bandwidth part.
  • the initial bandwidth part may be used for other system information (OSI), paging, and random access, as well as reception of an SIB. If an SIB received based on the MIB includes configuration information on the initial bandwidth part, the initial bandwidth part may be configured based on the SIB.
  • OSI system information
  • paging paging
  • random access paging
  • SIB system information
  • SIB received based on the MIB includes configuration information on the initial bandwidth part
  • the initial bandwidth part may be configured based on the SIB.
  • the NR CN 1c-05 performs functions, such as mobility support, bearer configuration, and quality of service (QoS) configuration.
  • the NR CN 1c-05 is a device that performs various control functions, as well as a mobility management function for a terminal, and is connected to a plurality of base stations.
  • the next-generation mobile communication system may interwork with an existing LTE system, and the NR CN 1c-05 is connected to the MME 1c-25 through a network interface.
  • the MME 1c-25 is connected to the eNB 1c-30, which is an existing base station.
  • FIG. 4 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the disclosure.
  • the radio protocol of the next-generation mobile communication system includes NR SDAP 1d-01 or 1d-45, NR PDCP 1d-05 or 1d-40, NR RLC 1d-10 or 1d-35, and NR MAC 1d-15 or 1d-30 in a terminal and an NR base station, respectively.
  • the primary functions of the NR service data adaptation protocol (SDAP) 1d-01 or 1d-45 may include some of the following functions.
  • the terminal may receive a configuration indicating whether or not to use a header of the SDAP layer entity or whether or not to use functions of the SDAP layer entity for each PDCP layer entity, for each bearer, or for each logical channel through an RRC message.
  • a 1-bit non-access stratum (NAS) reflective QoS configuration indicator and a 1-bit AS reflective QoS configuration indicator of the SDAP header may instruct the terminal to update or reconfigure mapping information between the QoS flow and the data bearers in uplink and downlink.
  • the SDAP header may include QoS flow ID information indicating the QoS.
  • the QoS information may be used as data processing priority, scheduling information, or the like in order to support effective services.
  • the primary functions of the NR PDCP 1d-05 or 1d-40 may include some of the following functions.
  • the above reordering function of the NR PDCP entity denotes a function of reordering PDCP PDUs received from a lower layer, based on a PDCP sequence number (SN), may include a function of transmitting data to an upper layer in the reordered order, may include a function of directly transmitting data to an upper layer without consideration of an order, may include a function of reordering the sequence and recording lost PDCP PDUs, may include a function of sending a status report of the lost PDCP PDUs to the transmitting end, and may include a function of making a request for retransmission of the lost PDCP PDUs.
  • SN PDCP sequence number
  • the primary functions of the NR RLC 1d-10 or 1d-35 may include some of the following functions.
  • the above in-sequence delivery function of the NR RLC entity denotes a function of transferring RLC SDUs received from a lower layer to an upper layer in sequence, may include a function of, if one original RLC SDU is divided into a plurality of RLC SDUs and received, reassembling and transmitting the same, may include a function of reordering the received RLC PDUs, based on an RLC sequence number (SN) or a PDCP sequence number (SN), may include a function of reordering the sequence and recording lost RLC PDUs, may include a function of sending a status report of the lost RLC PDUs to the transmitting end, may include a function of making a request for retransmission of the lost RLC PDUs, may include a function of, if there is a lost RLC SDU, transmitting only the RLC SDUs prior to the lost RLC SDU to an upper layer in sequence, may include a function of, if a predetermined timer expire
  • the RLC PDUs may be processed in the order of reception (in the order of arrival regardless of a serial number or a sequence number thereof), and may be transmitted to the PDCP entity in an out-of-sequence delivery manner.
  • the segments which are stored in the buffer or will be received later, may be received and reconfigured into one complete RLC PDU, and the RLC PDU may be processed and transmitted to the PDCP entity.
  • the NR RLC layer may not include a concatenation function, which may be performed in the NR MAC layer or may be replaced with a multiplexing function of the NR MAC layer.
  • the out-of-sequence delivery of the NR RLC entity denotes a function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of sequence, may include a function of, if one original RLC SDU is divided into a plurality of RLC SDUs and is received, reassembling and delivering the same, and may include a function of storing and ordering RLC SNs or PDCP SNs of the received RLC PDUs, thereby recording the lost RLC PDUs.
  • the NR MAC 1d-15 or 1d-30 may be connected to a plurality of NR RLC entities configured in a single terminal, and the primary functions of the NR MAC may include some of the following functions.
  • the NR PHY layers 1d-20 and 1d-25 may perform operations of channel-coding and modulating the upper layer data into OFDM symbols and transmitting the same through a radio channel, or operations of demodulating and channel-decoding the OFDM symbols received through the radio channel and transmitting the same to the upper layer.
  • FIG. 5 is a diagram illustrating a structure of a message for reporting UE capability in an NR system according to an embodiment of the disclosure.
  • a terminal 1e-01 is connected to a serving base station 1e-02, and performs a procedure of reporting the capability supported by the terminal 1e-01 to the base station 1e-02.
  • the base station 1e-02 transmits, to the connected terminal 1e-01, a UE capability enquiry message requesting capability reporting.
  • the message may include a UE capability request for each radio access technology (RAT) type made by the base station.
  • the request for each RAT type may include information on a requested frequency band.
  • RAT radio access technology
  • the UE capability enquiry message may include a single RRC message container requesting a plurality of RAT types, or an RRC message including a plurality of UE capability enquiry messages including a request for each RAT type may be transmitted to the terminal. That is, UE capability enquiry may be repeated multiple times in operation 1e-05, and the terminal may configure a plurality of UE capability information messages corresponding thereto, and may report the same multiple times.
  • UE capability request may be performed with respect to MR-DC, as well as NR, LTE, and EN-DC.
  • the UE capability enquiry message is generally transmitted in the process of establishing a DC connection by the terminal or after the DC connection is established, but may be transmitted in any condition when the base station requires the same.
  • the terminal receiving a request for a UE capability report from the base station in the above operation configures a UE capability according to the RAT type and band information requested by the base station.
  • a method of configuring UE capability by the terminal in an NR system is summarized below.
  • a terminal receives a list of LTE and/or NR bands through a request for UE capability from a base station, the terminal configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, the terminal configures a candidate list of BCs for EN-DC and NR SA, based on the bands requested by the base station through "FreqBandList”. In addition, the bands have priorities in the order described in "FreqBandList".
  • BC band combination
  • SA NR stand-alone
  • the NR SA BCs are completely removed from the configured candidate list of BCs. This may only happen in the case where the LTE base station (eNB) requests "eutra" capability.
  • the terminal removes fallback BCs from the candidate list of BCs configured in the above operation.
  • the fallback BC corresponds to the case in which a band corresponding to at least one SCell is removed from a certain super set BCs, and may be omitted since the super set BC can cover the fallback BC.
  • This operation is also applied to MR-DC (i.e., LTE bands).
  • the remaining BCs after this operation constitute a final "candidate BC list".
  • the terminal selects BCs to be reported by selecting BCs conforming to the requested RAT type from the final "candidate BC list" above.
  • the terminal configures "supportedBandCombinationList” in a predetermined order. That is, the terminal configures the BCs and UE capability to be reported in the order of a predetermined RAT type (nr -> eutra-nr -> eutra).
  • the terminal configures "featureSetCombination” for the configured "supportedBandCombinationList” and configures a list of "candidate feature set combinations" from the candidate BC list from which the list of fallback BCs (including equal or lower level capabilities) has been removed.
  • the "candidate feature set combination” may include feature set combinations for both NR and EUTRA-NR BC, and may be obtained from feature set combinations of UE-NR-capabilities and UE-MRDC-capabilities containers.
  • featureSetCombinations is included in two containers of "UE-MRDC-capabilities" and “UE-NR-capabilities”. However, the feature set of NR is included only in “UE-NR-capabilities”.
  • the terminal 1e-01 After the UE capability is configured, the terminal 1e-01 transmits a UE capability information message including the UE capability to the base station in operation 1e-10.
  • the base station 1e-02 then performs appropriate scheduling and transmission/reception management with respect to the corresponding terminal, based on the UE capability received from the terminal 1e-01.
  • the disclosure provides a method of configuring and reporting UE capability, based on the case in which the base station makes a request for reporting UE capability using "UECapabilityEnquiry” including “UE-CapabilityRAT-Request” as described above, and further considers the case in which the terminal transmits the UE capability that temporarily changes to the base station.
  • An operation method may vary according to various embodiments of the disclosure, and the disclosure and the following embodiments propose a method of supporting general UE capability restriction (temporary capability restriction) and specific application examples thereof.
  • a temporary change in UE capability may occur due to the following issues.
  • Change of a terminal mode ⁇ selectively determined from among dual mode.
  • the performance of the terminal may be configured differently between a folded state and an unfolded state thereof.
  • the performance of the terminal may differ in hardware (such as antenna performance, support or non-support for MIMO, or the like) depending on the mode of the terminal, or the terminal may be intentionally configured to have different UE capabilities. ⁇
  • FIG. 6 is a diagram illustrating a method of a terminal in an RRC connection state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a base station stores the request without acceptance/rejection of the base station and reflects the request through RRC reconfiguration.
  • a terminal 1f-01 performs an RRC connection procedure including random access, thereby switching to an RRC connection state (1f-05).
  • the terminal 1f-01 in the RRC connection state receives a request for reporting UE capability from the base station 1f-02 in operation 1f-05.
  • a plurality of "UE-CapabilityRAT-Requests" may be transmitted using "UECapabilityEnquiry", or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1f-01 configures a UE capability, based on the priority according to the RAT type request. For example, the terminal 1f-01 configures a UE capability container according to the following priority in LTE.
  • a report of another RAT type has a priority value, and the terminal 1f-01 must make a report according thereto.
  • the terminal 1f-01 transmits, to the base station 1f-02, "UECapabilityInformation" message including UE capability information configured according to the priority in the container thereof.
  • the message is transmitted to the base station 1f-02 through an RRC message, and includes static UE capability for the RAT type, band information, or the like, which are requested by the base station 1f-02.
  • the terminal 1f-01 may adjust implementation of the UE capability for the requested RAT type and band information and report the same, the terminal 1f-01 basically transmits static information on the terminal in this operation. This is due to the fact that information necessary to return to the previous static UE capability is required in the case where a temporary capability restriction request, which is reported later, expires.
  • the base station 1f-02 transmits the UE capability information received from the terminal 1f-01 to a 5G CN 1f-03, and the 5G CN 1f-03 stores the received static UE capability information.
  • the UE capability information stored in the 5G CN 1f-03 in the above operation may be maintained until the RRC connection of the terminal 1f-01 is released, and may be used for traffic configuration and mobility management with respect to the terminal 1f-01.
  • the UE capability is statically transmitted to the base station 1f-02 and the 5G CN 1f-03, and if there is no separate signaling, the inherent capability of the terminal 1f-01 remains.
  • the UE capability may need to be temporarily changed due to the four reasons described above and other reasons. That is, a temporary change in UE capability different from the performance of the static terminal may be generated/required due to sharing hardware with other communication modules in the terminal 1f-01, interference therewith, temporary heating, change of a terminal mode, and the like.
  • the terminal 1f-01 needs to report the same to the base station 1f-02 to make a request for scheduling and management conforming to the reduced UE capability.
  • the performance of the terminal in the case of a foldable terminal, if the performance of the terminal is a static UE capability when the display is unfolded, the performance of the terminal in the state in which the display is folded may be configured to be lower. That is, a change in the state of the terminal may make a difference in the performance of an antenna and MIMO applied to the terminal, power performance thereof, or the like.
  • a new signaling structure and a function thereof are required in addition to the existing method of reporting UE capability.
  • the terminal may have a higher UE capability than the static UE capability that has already been reported by the terminal.
  • the performance of the terminal in the case of a foldable terminal, if the performance of the terminal is a static UE capability when the display is folded, the performance of the terminal when the display is unfolded may be configured to be higher. That is, a change in the state of the terminal may make a difference in the performance of an antenna and MIMO applied to the terminal, power performance thereof, or the like.
  • a new signaling structure and a function thereof are required in addition to the existing method of reporting UE capability.
  • the embodiment proposes a method in which a terminal in a connection state requests a temporary capability restriction through an RRC message. If a condition required for a temporary change in UE capability is internally satisfied in operation 1f-25, the terminal 1f-01 may trigger the same. In operation 1f-30, the terminal 1f-01 requests a temporary capability restriction through an RRC message, such as UE assistance information.
  • the RRC message may include at least one piece of information, which may be requested by the terminal, such as a cause of a request for a temporary UE capability change (e.g., cause values: hardware sharing, interference, overheating, mode change, battery issue, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary UE capability change e.g., cause values: hardware sharing, interference, overheating, mode change, battery issue, and the like
  • a band and band combination information to be supported e.g., change values: hardware sharing, interference, overheating, mode change, battery issue, and the like
  • changes in the physical functions of the terminal a change in the number of component carriers, a change
  • the terminal reports a change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1f-35 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1f-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1f-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1f-02 to perform scheduling and management with respect to the terminal 1f-01.
  • the prohibit timer 1f-35 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message. Alternatively, the prohibit timer 1f-35 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1f-02 stores the temporary capability restriction information received from the terminal 1f-01 and determines whether or not to reflect the same. In this case, the received information is managed only in an access stratum (AS) area, instead of transmitting the same to the 5G CN. In an embodiment of the disclosure, the base station 1f-02 does not transmit a separate confirm/reject message after receiving the RRC message including the temporary capability restriction from the terminal 1f-01. If the base station 1f-02 is to reflect the temporary capability restriction from the terminal 1f-01, the base station 1f-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1f-01 through an RRC reconfiguration message in operation 1f-45.
  • AS access stratum
  • the base station 1f-02 may omit operation 1f-45 without reflecting the temporary capability restriction even in the state in which the temporary capability restriction is received from the terminal 1f-01. That is, the base station 1f-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation 1f-10.
  • the terminal 1f-01 receiving the RRC reconfiguration from the base station 1f-02 in operation 1f-45 transmits information indicating that the RRC reconfiguration has been received to the base station 1f-02 through an RRC reconfiguration complete message for the configuration (operation 1f-50).
  • the terminal 1f-01 If the terminal 1f-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1f-55), the terminal 1f-01 informs the base station 1f-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1f-60. Upon receiving the RRC message, the base station 1f-02 may transmit, to the terminal 1f-01, a release response RRC message indicating that the corresponding release message has been received in operation 1f-65.
  • the base station 1f-02 may determine that the terminal 1f-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message.
  • the release response message in operation 1f-65 may be omitted. That is, if the temporary capability restriction release message is received in operation 1f-60, the base station 1f-02 may transmit a new RRC reconfiguration message to the terminal 1f-01, instead of responding thereto.
  • the base station 1f-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1f-01.
  • a terminal switches to an RRC idle state or an RRC inactive state.
  • the terminal may switch to an RRC idle state or an RRC inactive state, based on a timer, according to request by a base station, or according to request by a terminal.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 7 is a diagram illustrating a method of a terminal in an RRC connection state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal receives an acceptance/rejection message of the base station, thereby determining whether or not to apply a request for a temporary UE capability change of the terminal.
  • a terminal 1g-01 performs an RRC connection procedure including random access, thereby switching to an RRC connection state (1g-05).
  • the terminal 1g-01 in the RRC connection state receives a request for reporting UE capability from the base station 1g-02 in operation 1g-05.
  • a plurality of "UE-CapabilityRAT-Requests" may be transmitted using "UECapabilityEnquiry", or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1g-01 configures a UE capability, based on the priority according to the RAT type request. For example, the terminal 1g-01 configures a UE capability container according to the following priority in LTE.
  • reporting of another RAT type has a priority value, and the terminal 1g-01 must make a report according thereto.
  • the terminal 1g-01 transmits, to the base station 1g-02, "UECapabilityInformation" message including the UE capability information configured according to the priority in the container thereof.
  • the message is transmitted to the base station 1g-02 through an RRC message, and includes static UE capability for the RAT type, band information, or the like, which are requested from the base station 1g-02.
  • the terminal 1g-01 may adjust implementation of the UE capability for the requested RAT type and band information and report the same, the terminal 1g-01 basically transmits static information on the terminal in this operation. This is due to the fact that information necessary to return to the previous static UE capability is required in the case where a temporary capability restriction request, which is reported later, expires.
  • the base station 1g-02 transmits the UE capability information received from the terminal 1g-01 to a 5G CN 1g-03, and the 5G CN 1g-03 stores the received static UE capability information.
  • the UE capability information stored in the 5G CN 1g-03 in the above operation may be maintained until the RRC connection of the terminal 1g-01 is released, and may be used for traffic configuration and mobility management with respect to the terminal 1g-01.
  • the UE capability is statically transmitted to the base station 1g-02 and the 5G CN 1g-03, and if there is no separate signaling, the inherent capability of the terminal 1g-01 remains.
  • the UE capability may need to be temporarily changed due to the four reasons described above and other reasons. That is, a temporary change in the UE capability different from the performance of the static terminal may be generated/required due to sharing hardware with other communication modules in the terminal 1g-01, interference therewith, temporary heating, change of a terminal mode, and the like.
  • the terminal 1g-01 In general, in the case where the UE capability is temporarily reduced, compared to the static UE capability, the terminal 1g-01 needs to report the same to the base station 1g-02 to make a request for scheduling and management conforming to the reduced UE capability. However, in a specific case, the terminal 1g-01 may have a UE capability higher than the static UE capability that has already been reported by the terminal 1g-01.
  • the performance of the terminal is a static UE capability when the display is folded
  • the performance of the terminal in the state in which the display is unfolded may be configured to be higher. That is, a change in the state of the terminal may make a difference in the performance of an antenna and MIMO applied to the terminal, power performance thereof, or the like.
  • a new signaling structure and a function thereof are required in addition to the existing method of reporting UE capability.
  • the embodiment proposes a method in which a terminal in a connection state requests a temporary capability restriction through an RRC message. If a condition required for a temporary change in UE capability is internally satisfied in operation 1g-25, the terminal 1g-01 may trigger the same. In operation 1g-30, the terminal 1g-01 requests a temporary capability restriction through an RRC message, such as UE assistance information.
  • the RRC message may include at least one piece of information, which may be requested by the terminal, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference therewith, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference therewith, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1g-35 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1g-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1g-02 to perform scheduling and management with respect to the terminal 1g-01.
  • the prohibit timer 1g-35 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message. Alternatively, the prohibit timer 1g-35 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1g-02 may transmit a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1g-02 accepts the temporary capability restriction request from the terminal 1g-01, the base station 1g-02 transmits a confirm message, and if the base station 1g-02 rejects the temporary capability restriction request, the base station 1g-02 transmits a reject message. Both the messages may be transmitted using RRC messages.
  • the base station 1g-02 stores or does not reflect the temporary capability restriction information received from the terminal 1g-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1g-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1g-03.
  • AS access stratum
  • a separate confirm/reject message is transmitted after receiving an RRC message including the temporary capability restriction from the terminal 1g-01.
  • the base station 1g-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1g-01 through an RRC reconfiguration message. However, if the base station 1g-02 rejects the temporary capability restriction request from the terminal 1g-01 (if the base station 1g-02 transmits a reject message in operation 1g-40), the base station 1g-02 may omit operation 1g-50 without reflecting the temporary capability restriction. That is, the base station 1g-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation 1g-10.
  • the terminal 1g-01 receiving the RRC reconfiguration from the base station 1g-02 in operation 1g-50 transmits information indicating that the RRC reconfiguration has been received to the base station 1g-02 through an RRC reconfiguration complete message for the configuration (operation 1g-55).
  • the terminal 1g-01 If the terminal 1g-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1g-60), the terminal 1g-01 informs the base station 1g-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1g-65. Upon receiving the RRC message, the base station 1g-02 may transmit, to the terminal 1g-01, a release response RRC message indicating that the corresponding release message has been received in operation 1g-70.
  • the base station 1g-02 may determine that the terminal 1g-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal 1g-01.
  • the release response message in operation 1g-70 may be omitted. That is, if the base station 1g-02 receives the temporary capability restriction release message in operation 1g-65, the base station 1g-02 may transmit a new RRC reconfiguration message to the terminal 1g-01, instead of responding thereto.
  • the base station 1g-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1g-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 8 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal requests a temporary UE capability restriction in the operation of requesting switching from an idle state to a connection state
  • the terminal if the terminal enters an RRC connection state, the terminal requests the content of the temporary UE capability restriction.
  • a terminal 1h-01 in an RRC idle state may have a temporary change in UE capability in operation 1h-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability of the terminal may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • the UE capability even if the UE capability is temporarily changed in the idle state, it is not necessary to trigger an RRC connection procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station. Therefore, it may be possible to trigger an RRC connection procedure only when a general RRC connection is required (when uplink/downlink data occurs). That is, although a temporary change in UE capability does not trigger the RRC connection procedure, if the RRC connection procedure is triggered for another reason, it is necessary to determine whether or not the terminal currently needs a temporary change in the UE capability, and, if the capability change is necessary, a subsequent procedure reflects the same.
  • the RRC connection procedure in order to notify the base station in advance that the UE capability has been temporarily changed in the idle state, the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1h-01 triggers random access to the base station 1h-02 in operation 1h-10. That is, the terminal 1h-01 transmits a random access preamble (msg 1) to the base station 1h-02 and starts an RRC connection procedure. In an embodiment of the disclosure, it is possible to notify of a temporary capability restriction using a random access preamble (msg 1). At least one of a preamble ID, a time resource, and a frequency resource, which are predefined, may be used. Alternatively, the random access preamble (msg 1) may include an indicator indicating a temporary capability restriction. In operation 1h-15, the terminal 1h-01 receives a random access response (msg 2) from the base station 1h-02 and synchronizes uplink.
  • msg 1 random access response
  • the terminal 1h-01 may include an indicator indicating a temporary capability restriction in an RRC Connection Setup Request message (msg 3).
  • an indicator indicating that there is a change in the UE capability in this operation the base station may recognize in advance that the terminal 1h-01 will request a temporary capability restriction later.
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • msg 3 of 56 bits is used, and the minimum uplink grant size is also 56 bits in NR.
  • msg 3 must have a good link performance within cell coverage because it is a request message to attempt to connect to a network.
  • the terminal coverage is extended.
  • LCID logical channel identifier
  • msg 3 cannot carry and transmit all of 5G-S-TMSI that is increased by 8 bits, compared to SAE-Temporary Mobile Subscriber Identity (S-TMSI) in LTE, msg 3 must transmit a portion of the 5G-S-TMSI, and msg 5 must transmit the remaining portions thereof.
  • S-TMSI SAE-Temporary Mobile Subscriber Identity
  • the base station 1h-02 transmits an RRC Connection Setup message (msg 4) to the terminal 1h-01 in response to the received RRC Connection Setup Request message.
  • the message may include a radio bearer configuration for signaling radio bearer (SRB) 1 and a master cell group (MCG) configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1h-02 for SRB 1 in this operation, and the terminal 1h-01 receives msg 4 and transmits an RRC Connection Setup Complete message (msg 5) in response to the configuration of SRB 1 in operation 1h-30.
  • the message may include a selected public land mobile network (PLMN) ID, a registered access and mobility management function (AMF), a globally unique AMF ID (GUAMI) type, a Single Network Slice Selection Assistance Information (S-NSSAI) list, a NAS message, and the like.
  • PLMN public land mobile network
  • AMF registered access and mobility management function
  • GUI globally unique AMF ID
  • S-NSSAI Single Network Slice Selection Assistance Information
  • operations 1h-35, 1h-40, and 1h-45 may be omitted, and operations 1h-35, 1h-40, and 1h-45 may be performed only when UE capability retrieve condition 2 is met.
  • the terminal 1h-01 may receive a request for reporting UE capability from the base station 1h-02 through an RRC message, and a plurality of "UE-CapabilityRAT-Requests" may be transmitted using "UECapabilityEnquiry” in the message, or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1h-01 configures a UE capability, based on the priority according to the RAT type request.
  • the request may include band information, a restriction on the report content, and the like.
  • the terminal 1h-01 configures a UE capability container according to the following priority in LTE.
  • reporting of another RAT type has a priority value, and the terminal 1h-01 must make a report according thereto.
  • the terminal 1h-01 transmits, to the base station 1h-02, "UECapabilityInformation" message including the UE capability information configured according to the priority in the container thereof.
  • the message is transmitted to the base station 1h-02 through an RRC message, and includes static UE capability for the RAT type, band information, or the like, which are requested from the base station 1h-02.
  • the terminal 1h-01 may adjust implementation of the UE capability for the requested RAT type and band information and report the same, the terminal 1h-01 basically transmits static information on the terminal in this operation. This is due to the fact that information necessary to return to the previous static UE capability is required in the case where a temporary capability restriction request, which is reported later, expires.
  • the base station 1h-02 transmits the UE capability information received from the terminal 1h-01 to a 5G CN 1h-03, and the 5G CN 1h-03 stores the received static UE capability information.
  • the UE capability information stored in the 5G CN 1h-03 in the above operation may be maintained until the RRC connection of the terminal 1h-01 is released, and may be used for traffic configuration and mobility management with respect to the terminal 1h-01.
  • the UE capability is statically transmitted to the base station 1h-02 and the 5G CN 1h-03, and if there is no separate signaling, the inherent capability of the terminal 1h-01 remains.
  • the UE capability may need to be temporarily changed due to the four reasons described above and other reasons. That is, a temporary change in UE capability different from the performance of the static terminal may be generated/required due to sharing hardware with other communication modules in the terminal, interference therewith, temporary heating, change of a terminal mode, and the like.
  • the terminal needs to report the same to the base station 1h-02 to make a request for scheduling and management conforming to the reduced UE capability.
  • the terminal may have a UE capability higher than the static UE capability that has already been reported by the terminal.
  • the performance of the terminal is a static UE capability when the display is folded
  • the performance of the terminal in the state in which the display is unfolded may be configured to be higher. That is, a change in the state of the terminal may make a difference in the performance of an antenna and MIMO applied to the terminal, power performance thereof, or the like.
  • a new signaling structure and a function thereof are required in addition to the existing method of reporting UE capability.
  • the embodiment proposes a method in which a terminal in a connection state requests a temporary capability restriction through an RRC message.
  • the terminal 1h-01 transmits information on a temporary change in UE capability (i.e., temporary capability restriction) and a request for the same through an RRC message, such as UE assistance information.
  • the RRC message may include at least one piece of information, which may be requested by the terminal 1h-01, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1h-55 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1h-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1h-02 to perform scheduling and management with respect to the terminal 1h-01.
  • the prohibit timer 1h-55 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message. Alternatively, the prohibit timer 1h-55 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1h-02 may transmit, to the terminal 1h-01, a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1h-02 accepts the temporary capability restriction request from the terminal, the base station 1h-02 transmits a confirm message, and if the base station 1h-02 rejects the temporary capability restriction request, the base station 1h-02 transmits a reject message. Both the messages may be transmitted using RRC messages.
  • the base station 1h-02 stores or does not reflect the temporary capability restriction information received from the terminal 1h-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1h-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1h-03.
  • the base station 1h-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1h-01 through an RRC reconfiguration message.
  • the base station 1h-02 may omit operation 1h-65 without reflecting the temporary capability restriction, or may configure RRC configuration, based on the original UE capability. That is, the base station 1h-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1h-01 receiving the RRC reconfiguration from the base station 1h-02 in operation 1h-65 transmits information indicating that the RRC reconfiguration has been received to the base station 1h-02 through an RRC reconfiguration complete message for the configuration (operation 1h-70).
  • the terminal 1h-01 If the terminal 1h-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1h-75), the terminal 1h-01 informs the base station 1h-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1h-80. Upon receiving the RRC message, the base station 1h-02 may transmit, to the terminal 1h-01, a release response RRC message indicating that the corresponding release message has been received in operation 1h-85.
  • the base station 1h-02 may determine that the terminal 1h-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal.
  • the release response message in operation 1h-85 may be omitted. That is, if the base station 1h-02 receives the temporary capability restriction release message in operation 1h-80, the base station 1h-02 may transmit a new RRC reconfiguration message to the terminal 1h-01, instead of responding thereto.
  • the base station 1h-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1h-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 9 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal requests a temporary UE capability restriction in the operation of requesting switching from an idle state to a connection state
  • the terminal if the terminal enters an RRC connection state, the terminal requests the content of the temporary UE capability restriction.
  • a terminal 1i-01 in an RRC idle state may have a temporary change in UE capability in operation 1i-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability of the terminal may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • the UE capability even if the UE capability is temporarily changed in the idle state, it is not necessary to trigger an RRC connection procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1i-01 triggers random access to the base station 1i-02 in operation 1i-10. That is, the terminal 1i-01 transmits a random access preamble (msg 1) to the base station 1i-02 and starts an RRC connection procedure. In an embodiment of the disclosure, it is possible to notify of a temporary capability restriction using a random access preamble (msg 1). At least one of a preamble ID, a time resource, and a frequency resource, which are predefined, may be used. Alternatively, the random access preamble (msg 1) may include an indicator indicating a temporary capability restriction. In operation 1i-15, the terminal 1i-01 receives a random access response (msg 2) from the base station 1i-02 and synchronizes uplink.
  • msg 1 random access response
  • the terminal 1i-01 may include an indicator indicating a temporary capability restriction in an RRC Connection Setup Request message (msg 3).
  • an indicator indicating that there is a change in the UE capability in this operation the base station may recognize in advance that the terminal 1i-01 will request a temporary capability restriction later.
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • msg 3 of 56 bits is used, and the minimum uplink grant size is also 56 bits in NR.
  • msg 3 must have a good link performance within cell coverage because it is a request message to attempt to connect to a network.
  • the terminal coverage is extended.
  • LCID logical channel identifier
  • msg 3 cannot carry and transmit all of 5G-S-TMSI that is increased by 8 bits, compared to S-TMSI in LTE, msg 3 must transmit a portion of the 5G-S-TMSI, and msg 5 must transmit the remaining portions thereof.
  • the base station 1i-02 transmits an RRC Connection Setup message (msg 4) in response to the received RRC Connection Setup Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1i-02 for SRB 1 in this operation, and the terminal 1i-01 receives msg 4 and transmits an RRC Connection Setup Complete message (msg 5) in response to the configuration of SRB 1 in operation 1i-30.
  • the message may include at least one of a selected PLMN ID, a registered AMF, a globally unique AMF ID (GUAMI) type, a Single Network Slice Selection Assistance Information (S-NSSAI) list, a NAS message, and the like.
  • the base station 1i-02 may retrieve the static capability and context of the terminal from the CN, and if there is no corresponding UE capability or if the base station 1i-02 fails to retrieve the same, the base station 1i-02 may request a report of the UE capability.
  • operations 1i-35, 1i-40, and 1i-45 may be omitted, and operations 1i-35, 1i-40, and 1i-45 may be performed only when UE capability retrieve condition 2 is met.
  • the terminal 1i-01 may receive a request for reporting UE capability from the base station 1i-02 through an RRC message.
  • a plurality of "UE-CapabilityRAT-Requests” may be transmitted using "UECapabilityEnquiry” in the message, or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1i-01 configures a UE capability, based on the priority according to the RAT type request.
  • the request may include band information, a restriction on the report content, and the like.
  • the terminal 1i-01 configures a UE capability container according to the following priority in LTE.
  • the base station 1i-02 may instruct the terminal 1i-01 to report the temporary UE capability. That is, it may include a 1-bit indicator or restriction information that may be reported by reflecting the changed capability. For example, signaling indicating that permission is allowed only for the restriction on MIMO, the restriction on the number of CCs, and the like may be included. In addition, prohibit timer information may be included.
  • the terminal 1i-01 transmits, to the base station 1i-02, "UECapabilityInformation" message including the information on the temporarily changed UE capability, which is configured according to the priority, based on the request of the base station, in the container thereof.
  • the message may be transmitted to the base station 1i-02 through an RRC message, or may be transmitted using a new message, such as UE assistance information or the like.
  • a prohibit timer 1i-45 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1i-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1i-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1i-02 to perform scheduling and management with respect to the terminal.
  • the prohibit timer 1i-45 may be configured to be included in msg4 during an RRC connection procedure, and may be included in an RRC reconfiguration message.
  • the prohibit timer 1i-45 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1i-02 may transmit a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1i-02 accepts the temporary capability restriction request from the terminal, the base station 1i-02 transmits a confirm message, and if the base station 1i-02 rejects the temporary capability restriction request, the base station 1i-02 transmits a reject message. Both the messages may be transmitted using RRC messages.
  • the base station 1i-02 stores or does not reflect the temporary capability restriction information received from the terminal 1i-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1i-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1i-03.
  • AS access stratum
  • the terminal information may be transmitted to the 5G CN 1i-03 (operation 1i-55). Thereafter, in the case where the terminal 1i-01 reports static UE capability information, the corresponding information is overridden by a new static UE capability.
  • the base station 1i-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1i-01 through an RRC reconfiguration message. However, if the base station 1i-02 rejects the temporary capability restriction request received from the terminal 1i-01, the base station 1i-02 may omit operation 1i-60 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1i-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1i-01 receiving the RRC reconfiguration from the base station 1i-02 in operation 1i-60 transmits information indicating that the RRC reconfiguration has been received to the base station 1i-02 through an RRC reconfiguration complete message for the configuration (operation 1i-65).
  • the terminal 1i-01 If the terminal 1i-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1i-70), the terminal 1i-01 informs the base station 1i-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1i-75. Upon receiving the RRC message, the base station 1i-02 may transmit, to the terminal 1i-01, a release response RRC message indicating that the corresponding release message has been received in operation 1i-80.
  • the base station 1i-02 may determine that the terminal 1i-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal, or may request a new static UE capability.
  • the release response message in operation 1i-80 may be omitted. That is, if the base station 1i-02 receives the temporary capability restriction release message in operation 1i-80, the base station 1i-02 may transmit a new RRC reconfiguration message, instead of responding thereto.
  • the terminal 1i-01 receiving the UE capability request in operation 1i-85 transmits the corresponding information to the base station 1i-02 by including the relevant static UE capability therein in operation 1i-90.
  • the base station 1i-02 may store the UE capability, and may transmit the same to the CN.
  • the base station 1i-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1i-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 10 is a diagram illustrating a method a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • the terminal in particular, in the case where a terminal requests a temporary UE capability restriction in the operation of requesting switching from an idle state to a connection state, the terminal makes a request by including a corresponding indicator in msg 5 and transmits the content of change in the UE capability in a connection state.
  • a terminal 1j-01 in an RRC idle state may have a temporary change in UE capability in operation 1j-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability of the terminal may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • the UE capability even if the UE capability is temporarily changed in the idle state, it is not necessary to trigger an RRC connection procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1j-01 triggers random access to the base station 1j-02 in operation 1j-10. That is, the terminal 1j-01 transmits a random access preamble (msg 1) to the base station 1j-02 and starts an RRC connection procedure. In an embodiment of the disclosure, it is possible to notify of a temporary capability restriction using a random access preamble (msg 1). At least one of a preamble ID, a time resource, and a frequency resource, which are predefined, may be used. Alternatively, the random access preamble (msg 1) may include an indicator indicating a temporary capability restriction. In operation 1j-15, the terminal 1j-01 receives a random access response (msg 2) from the base station 1j-02 and synchronizes uplink. Thereafter, in operation 1j-20, the terminal 1j-01 may transmit an RRC Connection Setup Request message (msg 3) to the base station 1j-02.
  • msg 3 RRC Connection Setup Request message
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • msg 3 of 56 bits is used, and the minimum uplink grant size is also 56 bits in NR.
  • msg 3 must have a good link performance within cell coverage because it is a request message to attempt to connect to a network.
  • the terminal coverage is extended.
  • a separate logical channel identifier is further allocated to a MAC header in order to distinguish between an uplink grant of 56 bits for transmission of a CCCH and an uplink grant of 56 bits or more (e.g., 72 bits).
  • LCID logical channel identifier
  • msg 3 cannot carry and transmit all of 5G-S-TMSI that is increased by 8 bits, compared to S-TMSI in LTE, msg 3 must transmit a portion of the 5G-S-TMSI, and msg 5 must transmit the remaining portions thereof.
  • the base station 1j-02 transmits an RRC Connection Setup message (msg 4) in response to the received RRC Connection Setup Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1j-02 for SRB 1 in this operation, and the terminal 1j-01 receives msg 4 and transmits an RRC Connection Setup Complete message (msg 5) in response to the configuration of SRB 1 in operation 1j-30.
  • the message may include at least one of a selected PLMN ID, a registered AMF, a globally unique AMF ID (GUAMI) type, a Single Network Slice Selection Assistance Information (S-NSSAI) list, a NAS message, and the like.
  • the message may include a temporary capability restriction indicator. That is, since the message includes an indicator indicating that the terminal 1j-01 has a temporary change in the UE capability, the base station 1j-02 may recognize the same.
  • the base station 1j-02 may retrieve the static capability and context of the terminal from the CN, and if there is no corresponding UE capability or if the base station 1j-02 fails to retrieve the same, the base station 1j-02 may request a report of the UE capability. That is, if UE capability retrieve condition 1 above is satisfied, operations 1j-35, 1j-40, and 1j-45 may be omitted, and operations 1j-35, 1j-40, and 1j-45 may be performed only when UE capability retrieve condition 2 is met.
  • the terminal 1j-01 may receive a request for reporting UE capability from the base station 1j-02 through an RRC message.
  • a plurality of "UE-CapabilityRAT-Requests" may be transmitted using "UECapabilityEnquiry” in the message, or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1j-01 configures a UE capability, based on the priority according to the RAT type request.
  • the request may include band information, a restriction on the report content, and the like.
  • the terminal 1j-01 configures a UE capability container according to the following priority in LTE.
  • reporting of another RAT type has a priority value, and the terminal 1j-01 must make a report according thereto.
  • the terminal 1j-01 transmits, to the base station 1j-02, "UECapabilityInformation" message including the UE capability information configured according to the priority in the container thereof.
  • the message is transmitted to the base station 1j-02 through an RRC message, and includes static UE capability for the RAT type, band information, or the like, which are requested from the base station 1j-02.
  • the terminal 1j-01 may adjust implementation of the UE capability for the requested RAT type and band information and report the same, the terminal basically transmits static information on the terminal in this operation. This is due to the fact that information necessary to return to the previous static UE capability is required in the case where a temporary UE capability restriction request, which is reported later, expires.
  • the base station 1j-02 transmits the UE capability information received from the terminal 1j-01 to a 5G CN 1j-03, and the 5G CN 1j-03 stores the received static UE capability information.
  • the UE capability information stored in the 5G CN 1j-03 in the above operation may be maintained until the RRC connection of the terminal 1j-01 is released, and may be used for traffic configuration and mobility management with respect to the terminal.
  • the UE capability is statically transmitted to the base station 1j-02 and the 5G CN 1j-03, and if there is no separate signaling, the inherent capability of the terminal 1j-01 remains.
  • the UE capability may need to be temporarily changed due to the four reasons described above and other reasons. That is, a temporary change in UE capability different from the performance of the static terminal may be generated/required due to sharing hardware with other communication modules in the terminal, interference therewith, temporary heating, change of a terminal mode, and the like.
  • the terminal In general, in the case where the UE capability is temporarily reduced, compared to the static UE capability, the terminal needs to report the same to the base station to make a request for scheduling and management conforming to the reduced UE capability.
  • the terminal may have a UE capability higher than the static UE capability that has already been reported by the terminal.
  • the performance of the terminal is a static UE capability when the display is folded, the performance of the terminal in the state in which the display is unfolded may be configured to be higher. That is, a change in the state of the terminal may make a difference in the performance of an antenna and MIMO applied to the terminal, power performance thereof, or the like.
  • a new signaling structure and a function thereof are required in addition to the existing method of reporting UE capability.
  • the embodiment proposes a method in which a terminal in a connection state requests a temporary capability restriction through an RRC message.
  • the terminal 1j-01 transmits information on a temporary change in UE capability (i.e., a temporary capability restriction) and a request for the same through an RRC message, such as UE assistance information.
  • the RRC message may include at least one piece of information, which may be requested by the terminal 1j-01, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1j-55 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1j-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1j-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1j-02 to perform scheduling and management with respect to the terminal 1j-01.
  • the prohibit timer 1j-55 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message.
  • the prohibit timer 1j-55 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1j-02 may transmit a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1j-02 accepts the temporary capability restriction request from the terminal 1j-01, the base station 1j-02 transmits a confirm message to the terminal 1j-01, and if the base station 1j-02 rejects the temporary capability restriction request, the base station 1j-02 transmits a reject message. Both the messages may be transmitted using RRC messages.
  • the base station 1j-02 stores or does not reflect the temporary capability restriction information received from the terminal 1j-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1j-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1j-03.
  • the base station 1j-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1j-01 through an RRC reconfiguration message.
  • the base station 1j-02 may omit operation 1j-65 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1j-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation 1j-10.
  • the terminal 1j-01 receiving the RRC reconfiguration from the base station 1j-02 in operation 1j-65 transmits information indicating that the RRC reconfiguration has been received to the base station 1j-02 through an RRC reconfiguration complete message for the configuration (operation 1j-70).
  • the terminal 1j-01 If the terminal 1j-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1j-75), the terminal 1j-01 informs the base station 1j-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1j-80. Upon receiving the RRC message, the base station 1j-02 may transmit, to the terminal 1j-01, a release response RRC message indicating that the corresponding release message has been received in operation 1j-85.
  • the base station 1j-02 may determine that the terminal 1j-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message.
  • the release response message in operation 1j-85 may be omitted. That is, if the base station 1j-02 receives the temporary capability restriction release message in operation 1j-80, the base station 1j-02 may transmit a new RRC reconfiguration message to the terminal 1j-01, instead of responding thereto.
  • the base station 1j-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1j-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 11 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • the terminal in particular, in the case where a terminal requests a temporary capability restriction in the operation of requesting switching from an idle state to a connection state, the terminal makes a request by including relevant information.
  • a terminal 1k-01 in an RRC idle state may have a temporary change in UE capability in operation 1k-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability of the terminal may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • the UE capability even if the UE capability is temporarily changed in the idle state, it is not necessary to trigger an RRC connection procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • RRC connection procedure only when a general RRC connection is required (when uplink/downlink data occurs). That is, although a temporary change in UE capability does not trigger the RRC connection procedure, if the RRC connection procedure is triggered for another reason, it is necessary to determine whether or not the terminal currently needs a temporary change in the UE capability, and, if the capability change is necessary, a subsequent procedure reflects the same.
  • the base station may receive the UE capability from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1k-01 triggers random access to the base station 1k-02 in operation 1k-10. That is, the terminal 1k-01 transmits a random access preamble (msg 1) to the base station 1k-02 and starts an RRC connection procedure. In an embodiment of the disclosure, it is possible to notify of a temporary capability restriction using a random access preamble (msg 1). At least one of a preamble ID, a time resource, and a frequency resource, which are predefined, may be used. Alternatively, the random access preamble (msg 1) may include an indicator indicating a temporary capability restriction. In operation 1k-15, the terminal 1k-01 receives a random access response (msg 2) from the base station 1k-02 and synchronizes uplink.
  • msg 1 random access response
  • the terminal 1k-01 may include a temporary capability restriction in an RRC Connection Setup Request message (msg 3).
  • the base station may recognize in advance that the terminal 1k-01 will request a temporary capability restriction later.
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • msg 3 of 56 bits is used, and the minimum uplink grant size is also 56 bits in NR.
  • msg 3 must have a good link performance within cell coverage because it is a request message to attempt to connect to a network.
  • the terminal coverage is extended.
  • a separate logical channel identifier is further allocated to a MAC header in order to distinguish between an uplink grant of 56 bits for transmission of a CCCH and an uplink grant of 56 bits or more (e.g., 72 bits).
  • LCID logical channel identifier
  • msg 3 cannot carry and transmit all of 5G-S-TMSI that is increased by 8 bits, compared to S-TMSI in LTE, msg 3 must transmit a portion of the 5G-S-TMSI, and msg 5 must transmit the remaining portions thereof.
  • the base station 1k-02 transmits an RRC Connection Setup message (msg 4) in response to the received RRC Connection Setup Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1k-02 for SRB 1 in this operation, and the terminal 1k-01 receives msg 4 and transmits an RRC Connection Setup Complete message (msg 5) in response to the configuration of SRB 1 (operation 1k-30).
  • the message may include at least one of a selected PLMN ID, a registered AMF, a globally unique AMF ID (GUAMI) type, a Single Network Slice Selection Assistance Information (S-NSSAI) list, a NAS message, and the like, and may include temporary capability restriction information.
  • This case may be established in the state in which the terminal has reported the static UE capability to the base station in the previous connection state (UE capability retrieve condition 1), or may be possible in the state in which there is no previous information.
  • the RRC message may include at least one piece of information, which may be requested by the terminal 1k-01, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1k-35 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1k-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1k-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1k-02 to perform scheduling and management with respect to the terminal.
  • the prohibit timer 1k-35 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message. Alternatively, the prohibit timer 1k-35 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1k-02 stores or does not reflect the temporary capability restriction information received from the terminal 1k-01 according to whether or not the temporary capability restriction determined in the operation is reflected. Based on the content of msg 5 transmitted from the terminal 1k-01, the base station 1k-02 may retrieve the static capability and context of the terminal from the core network (CN), and if there is no corresponding UE capability or if the base station 1k-02 fails to retrieve the same, the base station 1k-02 may request a report of the UE capability.
  • CN core network
  • operations 1k-45, 1k-50, and 1k-55 may be omitted, and operations 1k-45, 1k-50, and 1k-55 may be performed only when UE capability retrieve condition 2 is met.
  • the terminal 1k-01 may receive a request for reporting UE capability from the base station 1k-02 through an RRC message.
  • a plurality of "UE-CapabilityRAT-Requests” may be transmitted using "UECapabilityEnquiry” in the message, or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1k-01 configures a UE capability, based on the priority according to the RAT type request.
  • the request may include band information, a restriction on the report content, and the like.
  • the terminal 1k-01 configures a UE capability container according to the following priority in LTE.
  • reporting of another RAT type has a priority value, and the terminal must make a report according thereto.
  • the terminal 1k-01 transmits, to the base station 1k-02, "UECapabilityInformation" message including the UE capability information configured according to the priority in the container thereof.
  • the message is transmitted to the base station 1k-02 through an RRC message, and includes static UE capability for the RAT type, band information, or the like, which are requested from the base station 1k-02.
  • the terminal 1k-01 may adjust implementation of the UE capability for the requested RAT type and band information and report the same, the terminal 1k-01 basically transmits static information on the terminal in this operation. This is due to the fact that information necessary to return to the previous static UE capability is required in the case where a temporary UE capability restriction request, which is reported later, expires.
  • the base station 1k-02 transmits the UE capability information received from the terminal 1k-01 to a 5G CN 1k-03, and the 5G CN 1k-03 stores the received static UE capability information.
  • the UE capability information stored in the 5G CN 1k-03 in the above operation may be maintained until the RRC connection of the terminal 1k-01 is released, and may be used for traffic configuration and mobility management with respect to the terminal 1k-01.
  • the base station 1k-02 does not transmit, to the CN, the temporary capability restriction information received from the terminal 1k-01 in operation 1k-30.
  • the base station 1k-02 may reflect the temporary capability restriction received in operation 1k-30, thereby transmitting new RRC configuration information to the terminal 1k-01 through an RRC reconfiguration message. However, if the base station 1k-02 rejects the temporary capability restriction request received from the terminal 1k-01, the base station 1k-02 may omit operation 1k-60 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1k-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1k-01 receiving the RRC reconfiguration from the base station 1k-02 in operation 1k-60 transmits information indicating that the RRC reconfiguration has been received to the base station 1k-02 through an RRC reconfiguration complete message for the configuration (operation 1k-65).
  • the terminal 1k-01 If the terminal 1k-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1k-70), the terminal 1k-01 informs the base station 1k-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1k-75. Upon receiving the RRC message, the base station 1k-02 may transmit, to the terminal 1k-01, a release response RRC message indicating that the corresponding release message has been received in operation 1k-80.
  • the base station 1k-02 may determine that the terminal 1k-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal 1k-01.
  • the release response message in operation 1k-85 may be omitted. That is, if the base station 1k-02 receives the temporary capability restriction release message in operation 1k-75, the base station 1k-02 may transmit a new RRC reconfiguration message to the terminal 1k-01, instead of responding thereto.
  • the base station 1k-02 may identify a temporary capability change of the terminal 1k-01 in the following cases. The following conditions may be simultaneously applied to the terminal 1k-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • the terminal 1k-01 transmits, to the base station 1k-02, information on the temporary change in the UE capability (i.e., a temporary capability restriction) and a request therefor through an RRC message, such as UE assistance information in operation 1k-95.
  • information on the temporary change in the UE capability i.e., a temporary capability restriction
  • RRC message such as UE assistance information in operation 1k-95.
  • FIG. 12 is a diagram illustrating a method of a terminal in an RRC idle state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal requests a temporary UE capability restriction in the operation of requesting switching from an idle state to a connection state
  • the terminal if the terminal enters an RRC connection state, the terminal requests the content of the temporary UE capability restriction.
  • a terminal 1l-01 in an RRC idle state may have a temporary change in UE capability in operation 1l-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability of the terminal may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • the UE capability even if the UE capability is temporarily changed in the idle state, it is not necessary to trigger an RRC connection procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1l-01 triggers random access to the base station 1l-02 in operation 1l-10. That is, the terminal 1l-01 transmits a random access preamble (msg 1) to the base station 1l-02 and starts an RRC connection procedure. In an embodiment of the disclosure, it is possible to notify of a temporary capability restriction using a random access preamble (msg 1). At least one of a preamble ID, a time resource, and a frequency resource, which are predefined, may be used. Alternatively, the random access preamble (msg 1) may include an indicator indicating a temporary capability restriction. In operation 1l-15, the terminal 1l-01 receives a random access response (msg 2) from the base station 1l-02 and synchronizes uplink. Thereafter, in operation 1l-20, the terminal 1l-01 transmits an RRC Connection Setup Request message (msg 3).
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • msg 3 of 56 bits is used, and the minimum uplink grant size is also 56 bits in NR.
  • msg 3 must have a good link performance within cell coverage because it is a request message to attempt to connect to a network.
  • the terminal coverage is extended.
  • a separate logical channel identifier is further allocated to a MAC header in order to distinguish between an uplink grant of 56 bits for transmission of a CCCH and an uplink grant of 56 bits or more (e.g., 72 bits).
  • LCID logical channel identifier
  • msg 3 cannot carry and transmit all of 5G-S-TMSI that is increased by 8 bits, compared to S-TMSI in LTE, msg 3 must transmit a portion of the 5G-S-TMSI, and msg 5 must transmit the remaining portions thereof.
  • the base station 1l-02 transmits an RRC Connection Setup message (msg 4) in response to the received RRC Connection Setup Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1l-02 for SRB 1 in this operation, and the terminal 1l-01 receives msg 4 and transmits an RRC Connection Setup Complete message (msg 5) in response to the configuration of SRB 1 in operation 1l-30.
  • the message may include at least one of a selected PLMN ID, a registered AMF, a globally unique AMF ID (GUAMI) type, a Single Network Slice Selection Assistance Information (S-NSSAI) list, a NAS message, and the like, and may include an indicator indicating a temporary capability restriction.
  • GUI globally unique AMF ID
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the base station 1l-02 may retrieve the static capability and context of the terminal from the CN, and if there is no corresponding UE capability or if the base station 1l-02 fails to retrieve the same, the base station 1l-02 may request a report of the UE capability. That is, if UE capability retrieve condition 1 above is satisfied, operations 1l-35, 1l-40, and 1l-45 may be omitted, and operations 1l-35, 1l-40, and 1l-45 may be performed only when UE capability retrieve condition 2 is met.
  • the terminal 1l-01 may receive a request for reporting UE capability from the base station 1l-02 through an RRC message.
  • a plurality of "UE-CapabilityRAT-Requests” may be transmitted using "UECapabilityEnquiry” in the message, or a request for a report with respect to one RAT type may be transmitted. If a plurality of "UE-CapabilityRAT-Requests" is transmitted using "UECapabilityEnquiry” in the above operation, the terminal 1l-01 configures a UE capability, based on the priority according to the RAT type request.
  • the request may include band information, a restriction on the report content, and the like.
  • the terminal 1l-01 configures a UE capability container according to the following priority in LTE.
  • the base station 1l-02 may instruct the terminal 1l-01 to report the temporary UE capability. That is, it may include a 1-bit indicator or restriction information that may be reported by reflecting the changed capability. For example, signaling indicating that permission is allowed only for the restriction on MIMO, the restriction on the number of CCs, and the like may be included. In addition, prohibit timer information may be included.
  • the terminal 1l-01 transmits, to the base station 1l-02, "UECapabilityInformation" message including the information on the temporarily changed UE capability, which is configured according to the priority, based on the request of the base station 1l-02, in the container thereof.
  • the message may be transmitted to the base station 1l-02 through an RRC message, or may be transmitted using a new message, such as UE assistance information or the like.
  • a prohibit timer 1l-45 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1l-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1l-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1l-02 to perform scheduling and management with respect to the terminal 1l-01.
  • the prohibit timer 1l-45 may be configured to be included in msg4 during an RRC connection procedure, and may be included in an RRC reconfiguration message.
  • the prohibit timer 1l-45 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1l-02 may transmit a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1l-02 accepts the temporary capability restriction request from the terminal 1l-01, the base station 1l-02 transmits a confirm message to the terminal 1l-01, and if the base station 1l-02 rejects the temporary capability restriction request, the base station 1l-02 transmits a reject message. Both the messages may be transmitted using RRC messages.
  • the base station 1l-02 stores or does not reflect the temporary capability restriction information received from the terminal 1l-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1l-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1l-03.
  • AS access stratum
  • the terminal information may be transmitted to the 5G CN 1l-03 (operation 1l-55). Thereafter, in the case where the terminal 1l-01 reports static UE capability information, the corresponding information is overridden by a new static UE capability.
  • the base station 1l-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1l-01 through an RRC reconfiguration message. However, if the base station 1l-02 rejects the temporary capability restriction request received from the terminal 1l-01, the base station 1l-02 may omit operation 1l-60 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1l-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1l-01 receiving the RRC reconfiguration from the base station 1l-02 in operation 1l-60 transmits information indicating that the RRC reconfiguration has been received to the base station 1l-02 through an RRC reconfiguration complete message for the configuration (operation 1l-65).
  • the terminal 1l-01 If the terminal 1l-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1l-70), the terminal 1l-01 informs the base station 1l-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1l-75. Upon receiving the RRC message, the base station 1l-02 may transmit, to the terminal 1l-01, a release response RRC message indicating that the corresponding release message has been received in operation 1l-80.
  • the base station 1l-02 may determine that the terminal 1l-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal, or may request a new static UE capability.
  • the release response message in operation 1l-80 may be omitted. That is, if the base station 1l-02 receives the temporary capability restriction release message in operation 1l-80, the base station 1l-02 may transmit a new RRC reconfiguration message, instead of responding thereto.
  • the terminal 1l-01 receiving the UE capability request in operation 1l-85 transmits the corresponding information to the base station 1l-02 by including the relevant static UE capability therein in operation 1l-90.
  • the base station 1l-02 may store the UE capability, and may transmit the same to the CN.
  • the base station 1l-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1l-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 13 is a diagram illustrating a method of a terminal in an RRC inactive state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal requests a temporary UE capability restriction in the operation of requesting switching from an inactive state to a connection state
  • the terminal if the terminal enters an RRC connection state, the terminal requests the temporary UE capability restriction.
  • a terminal 1m-01 in an RRC inactive state may have a temporary change in UE capability in operation 1m-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • even if the UE capability is temporarily changed in an inactive state it is not necessary to trigger an RRC Resume procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • RRC Resume procedure only when a general RRC connection is required (when uplink/downlink data occurs). That is, although a temporary change in UE capability does not trigger the RRC Resume procedure, if the RRC Resume procedure is triggered for another reason, it is necessary to determine whether or not the terminal currently needs a temporary change in the UE capability, and, if the capability change is necessary, a subsequent procedure reflects the same.
  • the RRC connection procedure in order to notify the base station in advance that the UE capability has been temporarily changed in the inactive state, the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1m-01 may include an indicator indicating a temporary capability restriction in an RRC Resume Request message (msg 3) in operation 1m-10.
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • the base station 1m-02 transmits, to a 5G CN 1m-03, a retrieve message for determining whether or not there are context of the terminal and UE capability information stored in the 5G CN 1m-03 and for requesting the same, and receives a response thereto from the 5G CN 1m-03 in operation 1m-20. If there is the information, the base station 1m-02 stores the static UE capability.
  • the base station 1m-02 transmits an RRC Resume message (msg 4) in response to the received RRC Resume Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1m-02 for SRB 1 in this operation, and the terminal 1m-01 receives msg 4 and transmits an RRC Resume Complete message (msg 5) in response to the configuration of SRB 1 in operation 1m-30.
  • the message may include at least one of a selected PLMN ID, a NAS message, and the like.
  • the base station 1m-02 may retrieve the static capability and context of the terminal from the CN, and if there is no corresponding UE capability or if the base station 1m-02 fails to retrieve the same, the base station 1m-02 may request a report of the UE capability.
  • the terminal 1m-01 may make a request for temporary change of the UE capability to the base station 1m-02.
  • the information on the temporary change in the UE capability i.e., a temporary capability restriction
  • a request for the same may be transmitted through an RRC message, such as UE assistance information in the above operation.
  • the RRC message may include at least one piece of information, which may be requested by the terminal 1m-01, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1m-40 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1m-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1m-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1m-02 to perform scheduling and management with respect to the terminal.
  • the prohibit timer 1m-40 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message.
  • the prohibit timer 1m-40 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1m-02 may transmit, to the terminal 1m-01, a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1m-02 accepts the temporary capability restriction request from the terminal 1m-01, the base station 1m-02 transmits a confirm message to the terminal 1m-01, and if the base station 1m-02 rejects the temporary capability restriction request, the base station 1m-02 transmits a reject message to the terminal 1m-01. Both the messages may be transmitted using RRC messages.
  • the base station 1m-02 stores or does not reflect the temporary capability restriction information received from the terminal 1m-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1m-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1m-03.
  • the base station 1m-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1m-01 through an RRC reconfiguration message.
  • the base station 1m-02 may omit operation 1m-50 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1m-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1m-01 receiving the RRC reconfiguration from the base station 1m-02 in operation 1m-50 transmits information indicating that the RRC reconfiguration has been received to the base station 1m-02 through an RRC reconfiguration complete message for the configuration (operation 1m-55).
  • the terminal 1m-01 If the terminal 1m-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1m-60), the terminal 1m-01 informs the base station 1m-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1m-65. Upon receiving the RRC message, the base station 1m-02 may transmit, to the terminal 1m-01, a release response RRC message indicating that the corresponding release message has been received in operation 1m-70.
  • the base station 1m-02 may determine that the terminal 1m-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal 1m-01.
  • the release response message in operation 1m-70 may be omitted. That is, if the base station 1m-02 receives the temporary capability restriction release message in operation 1m-65, the base station 1m-02 may transmit a new RRC reconfiguration message, instead of responding thereto.
  • the base station 1m-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1m-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 14 is a diagram illustrating a method of a terminal in an RRC inactive state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal requests a temporary UE capability restriction in the operation of requesting switching from an inactive state to a connection state
  • the base station requests the content of a temporary UE capability restriction.
  • a terminal 1n-01 in an RRC inactive state may have a temporary change in UE capability in operation 1n-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • even if the UE capability is temporarily changed in an idle state it is not necessary to trigger an RRC connection procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • RRC connection procedure only when a general RRC connection is required (when uplink/downlink data occurs). That is, although a temporary change in UE capability does not trigger the RRC connection procedure, if the RRC connection procedure is triggered for another reason, it is necessary to determine whether or not the terminal currently needs a temporary change in the UE capability, and, if the capability change is necessary, a subsequent procedure reflects the same.
  • the RRC connection procedure in order to notify the base station in advance that the UE capability has been temporarily changed in the idle state, the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability of the terminal from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1n-01 transmits an RRC Resume Request message (msg 3) to the base station 1n-02 in operation 1n-10.
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • the base station 1n-02 transmits, to a 5G CN 1n-03, a retrieve message for determining whether or not there are context of the terminal and UE capability information stored in the 5G CN 1n-03 and for requesting the same, and receives a response thereto in operation 1n-20. If there is the information, the base station 1n-02 stores the static UE capability.
  • the base station 1n-02 transmits an RRC Resume message (msg 4) in response to the received RRC Resume Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1n-02 for SRB 1 in this operation, and the terminal 1n-01 receives msg 4 and transmits an RRC Resume Complete message (msg 5) in response to the configuration of SRB 1 in operation 1n-30.
  • the message may include at least one of a selected PLMN ID, a NAS message, and the like, and may include an indicator for a temporary capability restriction.
  • the base station 1n-02 may identify that there is a temporary change in the UE capability through the indicator, and may consider the same in the subsequent procedure. Based on the content of msg 5 transmitted from the terminal 1n-01, the base station 1n-02 may retrieve the static capability and context of the terminal from the CN, and if there is no corresponding UE capability or if the base station 1n-02 fails to retrieve the same, the base station 1n-02 may request a report of the UE capability.
  • the terminal 1n-01 may make a request for temporary change of the UE capability to the base station 1n-02.
  • the information on the temporary change in the UE capability i.e., a temporary capability restriction
  • a request for the same may be transmitted through an RRC message, such as UE assistance information in the above operation.
  • the RRC message may include at least one piece of information, which may be requested by the terminal 1n-01, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1n-40 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal 1n-01 from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1n-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1n-02 to perform scheduling and management with respect to the terminal.
  • the prohibit timer 1n-40 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message.
  • the prohibit timer 1n-40 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1n-02 may transmit, to the terminal 1n-01, a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1n-02 accepts the temporary capability restriction request from the terminal 1n-01, the base station 1n-02 transmits a confirm message to the terminal 1n-01, and if the base station 1n-02 rejects the temporary capability restriction request, the base station 1n-02 transmits a reject message. Both the messages may be transmitted using RRC messages.
  • the base station 1n-02 stores or does not reflect the temporary capability restriction information received from the terminal 1n-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1n-02 is able to manage the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1n-03.
  • the base station 1n-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1n-01 through an RRC reconfiguration message.
  • the base station 1n-02 may omit operation 1n-50 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1n-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1n-01 receiving the RRC reconfiguration from the base station 1n-02 in operation 1n-50 transmits information indicating that the RRC reconfiguration has been received to the base station 1n-02 through an RRC reconfiguration complete message for the configuration (operation 1n-55).
  • the terminal 1n-01 If the terminal 1n-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1n-60), the terminal 1n-01 informs the base station 1n-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1n-65. Upon receiving the RRC message, the base station 1n-02 may transmit, to the terminal 1n-01, a release response RRC message indicating that the corresponding release message has been received in operation 1n-70.
  • the base station 1n-02 may determine that the terminal 1n-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal 1n-01.
  • the release response message in operation 1n-70 may be omitted. That is, if the base station 1n-02 receives the temporary capability restriction release message in operation 1n-65, the base station 1n-02 may transmit a new RRC reconfiguration message to the terminal 1n-01, instead of responding thereto.
  • the base station 1n-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1n-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • FIG. 15 is a diagram illustrating a method of a terminal in an RRC inactive state requesting a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal transmits relevant information in the process of requesting a temporary UE capability restriction in the operation of requesting switching from an inactive state to a connection state.
  • a terminal 1o-01 in an RRC inactive state may have a temporary change in UE capability in operation 1o-05.
  • the UE capability may change due to sharing hardware with other communication technologies, interference therewith, heating, or the like while the terminal is in connection.
  • the UE capability may be affected by the use of other communication technologies, such as WLAN, Bluetooth, or the like, so that management is required in consideration of the same from the initial RRC connection state.
  • even if the UE capability is temporarily changed in an inactive state it is not necessary to trigger an RRC Resume procedure. Even if the changed UE capability is not reported in the state other than the RRC connection state, it does not affect the configuration by the base station.
  • the RRC connection procedure may be triggered even when the RRC connection is not necessary.
  • the base station may receive the UE capability of the terminal from the CN (UE capability retrieve condition 1), and in this case, the base station may not request the UE capability of the terminal after the RRC connection procedure.
  • the base station fails to retrieve the static UE capability of the terminal (UE capability retrieve condition 2), the base station may request and receive the UE capability of the terminal after the RRC connection procedure.
  • the operation of the base station and the terminal may be different according to the above conditions.
  • the terminal 1o-01 transmits an RRC Resume Request message (msg 3) to the base station 1o-02 in operation 1o-10.
  • msg 3 does not include details of the temporary capability restriction because msg 3 is sensitive to size and is not able to contain a large amount of information.
  • msg 3 may be a message, such as RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, or the like.
  • the base station 1o-02 transmits, to a 5G CN 1o-03, a retrieve message for determining whether or not there are context of the terminal and UE capability information stored in the 5G CN 1o-03 and for requesting the same, and receives a response thereto in operation 1o-20. If there is the information, the base station 1o-02 stores the static UE capability.
  • the base station 1o-02 transmits an RRC Resume message (msg 4) in response to the received RRC Resume Request message.
  • the message may include a radio bearer configuration for SRB 1 and an MCG configuration (an RLC bearer, "mac-CellGroupConfig", “physicalCellGroupConfig and spCellConfig", and the like).
  • the message includes general configurations of the base station 1o-02 for SRB 1 in this operation, and the terminal 1o-01 receives msg 4 and transmits an RRC Resume Complete message (msg 5) in response to the configuration of SRB 1 to the base station 1o-02 in operation 1o-30.
  • the message may include at least one of a selected PLMN ID, a NAS message, and the like, and may include information on a temporary capability restriction.
  • the base station 1o-02 may retrieve the static capability and context of the terminal from the CN, and if there is no corresponding UE capability or if the base station 1o-02 fails to retrieve the same, the base station 1o-02 may request a report of the UE capability.
  • the UE capability is statically transmitted to the base station and the 5G CN, and if there is no separate signaling, the inherent capability of the terminal remains.
  • the UE capability may need to be temporarily changed due to the four reasons described above and other reasons. That is, a temporary change in UE capability different from the performance of the static terminal may be generated/required due to sharing hardware with other communication modules in the terminal, interference therewith, temporary heating, change of a terminal mode, and the like.
  • the terminal needs to report the same to the base station to make a request for scheduling and management conforming to the reduced UE capability.
  • the terminal may have a UE capability higher than the static UE capability that has already been reported by the terminal.
  • the performance of the terminal is a static UE capability when the display is folded
  • the performance of the terminal in the state in which the display is unfolded may be configured to be higher. That is, a change in the state of the terminal may make a difference in the performance of an antenna and MIMO applied to the terminal, power performance thereof, or the like.
  • a new signaling structure and a function thereof are required in addition to the existing method of reporting UE capability.
  • msg 5 may include at least one piece of information, which may be requested by the terminal 1o-01, such as a cause of a request for a temporary change in UE capability (e.g., cause values: hardware sharing, interference, overheating, mode change, and the like), a band and band combination information to be supported, changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC, a change in the support power, a change in the frequency range to be supported, and the like), or the like.
  • a cause of a request for a temporary change in UE capability e.g., cause values: hardware sharing, interference, overheating, mode change, and the like
  • a band and band combination information to be supported e.g., changes in the physical functions of the terminal (a change in the number of component carriers, a change in the number of MIMO layers, changes in the band and bandwidth information to be supported for each CC,
  • the terminal reports the change in UE capability
  • a UE capability in which the temporary change is smaller than the static UE capability is reported, only a subset of the static UE capability can always be reported. That is, this is a request for temporarily having some reduced capability of the overall static UE capability.
  • a new UE capability higher than the UE capability reported in the previous static report must be signaled.
  • a prohibit timer 1o-40 for prohibiting a request for a change in UE capability may be configured in order to prevent the terminal from repeating or re-requesting the temporary capability restriction within a specific time after requesting the temporary capability restriction using an RRC message, and an application period of the requested UE capability may be guaranteed for a specific time according thereto. If the prohibit timer is not configured, the terminal 1o-01 may frequently transmit UE capability reports, which makes it difficult for the base station 1o-02 to perform scheduling and management with respect to the terminal.
  • the prohibit timer 1o-35 may be configured to be included in msg 4 during an RRC connection procedure, and may be included in an RRC reconfiguration message.
  • the prohibit timer 1o-35 may be configured as a default value according to internal settings of the terminal, or may be obtained from system information.
  • the base station 1o-02 may transmit, to the terminal 1o-01, a temporary capability restriction confirm/reject message in response to the temporary capability restriction request message. If the base station 1o-02 accepts the temporary capability restriction request from the terminal 1o-01, the base station 1o-02 transmits a confirm message, and if the base station 1o-02 rejects the temporary capability restriction request, the base station 1o-02 transmits a reject message to the terminal 1o-01. Both the messages may be transmitted using RRC messages.
  • the base station 1o-02 stores or does not reflect the temporary capability restriction information received from the terminal 1o-01 according to whether or not the temporary capability restriction determined in the operation is reflected.
  • the base station 1o-02 manages the received information only in an access stratum (AS) area, instead of transmitting the same to the 5G CN 1o-03.
  • the base station 1o-02 may reflect the temporary capability restriction, thereby transmitting new RRC configuration information to the terminal 1o-01 through an RRC reconfiguration message.
  • the base station 1o-02 may omit operation 1o-45 without reflecting the temporary capability restriction, or may configure RRC reconfiguration, based on the original UE capability. That is, the base station 1o-02 maintains the RRC configuration (RRC reconfiguration) based on the UE capability received in the previous operation.
  • the terminal 1o-01 receiving the RRC reconfiguration from the base station 1o-02 in operation 1o-45 transmits information indicating that the RRC reconfiguration has been received to the base station 1o-02 through an RRC reconfiguration complete message for the configuration (operation 1o-50).
  • the terminal 1o-01 If the terminal 1o-01 needs to release the temporary change of the UE capability in the state in which the temporarily changed UE capability is reflected through the above process of temporarily changing the UE capability and the RRC reconfiguration according thereto (operation 1o-55), the terminal 1o-01 informs the base station 1o-02 that the temporary change in the UE capability has been completed and that the terminal has returned to the original static UE capability through a temporary capability restriction release message in operation 1o-60. Upon receiving the RRC message, the base station 1o-02 may transmit, to the terminal 1o-01, a release response RRC message indicating that the corresponding release message has been received in operation 1o-65.
  • the base station 1o-02 may determine that the terminal 1o-01 has returned to the static UE capability, and may then transmit a new RRC reconfiguration message to the terminal 1o-01.
  • the release response message in operation 1o-65 may be omitted. That is, if the base station 1o-02 receives the temporary capability restriction release message in operation 1o-60, the base station 1o-02 may transmit, to the terminal 1o-01, a new RRC reconfiguration message, instead of responding thereto.
  • the base station 1o-02 may identify a temporary capability change of the terminal in the following cases. The following conditions may be simultaneously applied to the terminal 1o-01.
  • a retention period of the temporary capability restriction of the terminal is configured by providing a separate timer and in which the timer expires (the timer may be included in the RRC reconfiguration transmitted to the terminal.
  • a plurality of timers may be configured depending on the situation.
  • the timer may be configured to be different depending on cause values of the temporary UE capability restriction, or may be configured to have different values for each terminal in an RRC connection state, an idle state, and an inactive state). If the terminal requests an extension of the configured timer value, the terminal may request a timer desired to be extended in a manner using UE assistance information, a new RRC message, or MAC CE.
  • a first method allows msg 3 or msg 5 to include an indicator indicating that a temporary capability restriction has occurred and provides detailed information on the temporary capability restriction through a specific RRC message (e.g., "UEAssistanceInformation" message) in an RRC connection state.
  • a second method is to include detailed information on the temporary capability restriction in msg 3 or msg 5 and provide the same.
  • Embodiment 4 of the disclosure describes in more detail the method in which the terminal includes temporary capability restriction request information as described in embodiments 1, 2, and 3, and may be applied to all of the above embodiments.
  • Embodiment 4 primarily relates to a method of signaling detailed information on the temporary capability restriction using msg 3 and msg 5, and processes multiple values using bitmaps. That is, if a temporary capability restriction is performed by specifying more values using bitmaps, the terminal may dynamically, flexibly, and adaptively request adjustment of capability of the terminal according to a network environment, thereby providing the best user experience (UX) to a user.
  • UX user experience
  • bitmaps may be used by a method in which multiple causes can be explicitly transmitted at the same time.
  • UE capability feature items according to cause values may be actively limited by a terminal by mapping the same using bitmaps.
  • - Priority may be configured by setting additional bits (High 1/Low 0) for a desired UE capability feature.
  • the load of network for processing the restriction may be reduced.
  • the split bearer and adding bearer items used in EN-DC are also managed using bitmaps.
  • the RAT is limited in an environment with severe interference, thereby avoiding the situation.
  • Embodiment 4-1 is example 1 of a method of processing a request for a temporary capability restriction proposed by the disclosure, and shows a method of configuring a cause value of a temporary capability restriction using a bitmap. If the cause values of the temporary capability restriction include the following four items, a 4-bit bitmap may be configured to indicate the cause values. That is, the bitmap size is equal to the number of cause values.
  • the initial value may be "0000", or may be indicated in duplicate according to corresponding cause values. In the case where overheating occurs due to interference with other communication schemes, a corresponding value may be determined and transmitted as a value "0110".
  • Embodiment 4-2 is example 2 of a method of processing a request for a temporary capability restriction proposed by the disclosure, and shows a method of configuring cause values and priority of a temporary capability restriction using a bitmap.
  • the cause values of the temporary UE capability restriction include the following four items, and if the priority for each cause value is provided, corresponding cause values and priorities may be indicated by configuring a bitmap of 8 bits. That is, a bitmap size may be equal to the sum of the number of cause values and the number of priorities.
  • the priority means that the cause value having a higher priority, among the produced cause values, is to be determined.
  • the initial value may be "0000 0000", or may be indicated in duplicate according to corresponding cause values. If overheating has occurred due to interference with other communication schemes, and if it is determined that the of overheating has a greater influence, among the cause values, that is, if overheating has a higher priority than interference, priority #3 may be determined and transmitted. That is, an 8-bit bitmap "0110 0010" may be set.
  • Embodiment 4-3 is example 3 of a method of processing a request for a temporary capability restriction proposed by the disclosure, and shows a method of configuring a list of UE features desired to be changed (or reduced) due to the temporary capability restriction using a bitmap. If a list of changed UE capability features required for the terminal is determined by eight items or less, it is possible to configure an 8-bit bitmap and to determine and indicate an item selected from among the UE capability lists to request change. That is, the bitmap size may be equal to the number of UE capability lists to request change. If there are 8 UE capability lists as follows, the terminal determines and transmits corresponding bits.
  • the initial value may be "0000 0000", or may be indicated in duplicate according to corresponding values.
  • an 8-bit bitmap "0000 1100" may be set.
  • the method is to propose the limit of a bearer and RAT through a UE capability restriction when an issue occurs in the terminal due to a corresponding signaling, and, if the corresponding signaling is provided, signaling for values changed due to limitations is also required separately. That is, there must be a predetermined default value, or a value to be changed due to separate signaling must be indicated.
  • the separate signaling may also be provided in the same message, and may then be included in another RRC message to be transmitted.
  • the split bearer may be primarily proposed, or a value explicitly indicating one of the two may be transmitted using another signaling.
  • Embodiment 4-4 is example 4 of a method of processing a request for a temporary capability restriction proposed by the disclosure, and shows a method of configuring a list of UE features desired to be changed (or reduced) due to the temporary capability restriction and the priority using a bitmap. If lists of changed UE capability features required for the terminal is determined by six items or less, and if six priorities corresponding to the features are signaled, it is possible to configure a 12-bit bitmap, to determine an item selected from among the UE capability lists to request change, and to indicate the priority thereof. That is, the bitmap size may be equal to the sum of the number of UE capability lists to request change and the priorities.
  • the initial value may be "0000 0000 0000", or may be indicated in duplicate according to corresponding values.
  • a 12-bit bitmap "0000 1100 0010" may be set.
  • the method is to propose the limit of a bearer and RAT through UE capability restriction when an issue occurs in the terminal due to a corresponding signaling, and is to make a request for processing the control of a bearer with a higher priority. If the corresponding signaling is provided, signaling for values changed due to limitations are also required separately.
  • the split bearer may be primarily proposed, or a value explicitly indicating one of the two may be transmitted using another signaling.
  • a sequence and combination of values constituting the bitmap may be changed.
  • Embodiment 4-5 is example 5 of a method of processing a request for a temporary capability restriction proposed by the disclosure, and shows a method of configuring cause values of the temporary capability restriction, a list of UE features desired to be changed (or reduced), and the priorities of the corresponding values using a bitmap. If there are four candidate cause values for the temporary capability restriction of the terminal, if there are four priorities corresponding the values, if lists of changed UE capability features required for the terminal are determined by six items or less, and if six priorities corresponding to the features are signaled, it is possible to configure a 20-bit bitmap, to determine an item selected from the cause values and the UE capability lists to request change, and to indicate the priority thereof.
  • the bitmap size may be equal to the sum of the cause values, the priorities of the cause values, the number of UE capability lists to request change, and the priorities.
  • the overall bitmap size may be adjusted by adding reserved values, and the bitmap may be configured as a combination of the previous embodiments.
  • the initial value may be "0000 0000 0000 0000", or may be indicated in duplicate according to corresponding values. If cause values are interference and overheating, and if overheating has a greater influence, in order to indicate the change of a bearer and the change of an RAT type, and, in particular, in order to indicate that the bearer control has a higher priority than the RAT type, a 20-bit bitmap "0110 0010 0000 1100 0010" may be set.
  • the method is to propose the limit of a bearer and RAT through UE capability restriction when an issue (interference and overheating) occurs in the terminal due to a corresponding signaling (overheating has a greater influence), and is to make a request for processing the control of a bearer with a higher priority.
  • the corresponding signaling is provided, signaling for values changed due to limitations are also required separately. That is, there must be a predetermined default value, or a value to be changed must be indicated using separate signaling.
  • the separate signaling may also be provided in the same message, and may then be included in another RRC message to be transmitted.
  • the split bearer may be primarily proposed, or a value explicitly indicating one of the two may be transmitted using another signaling.
  • a sequence and combination of values constituting the bitmap may be changed.
  • changed values of UE features desired by the terminal may be selected and transmitted through separate signaling, instead of a bitmap. This may indicate a subset of static UE capability, or may be a value for requesting a new capability.
  • FIG. 16 is a diagram illustrating an overall operation in which a terminal in an RRC connection state requests a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal in an RRC connection state may have a temporary change in UE capability due to internal issues of the terminal (operation 1p-05). Thereafter, the terminal may internally produce a message by including a reason for requesting the change in UE capability and the changed content therein.
  • the message may be included in msg 3, msg 5, or another RRC message ("UEAssistanceInformation" or a new RRC message), and a detail description thereof has been made in the above embodiments. That is, the message may include an indicator for a temporary capability restriction or information about a requested temporary capability restriction.
  • the terminal transmits a message including the change content of the terminal to the base station, and operates a prohibit timer to prevent repetition of the request.
  • the terminal receives an RRC reconfiguration message from the base station and reflects the configuration for operation. In this operation, the base station may reflect the temporary capability restriction to provide the same, or may not reflect the same, or the operation may be omitted.
  • the terminal determines that the terminal has returned to the original UE capability and restores the previous configuration in operation 1p-25. That is, the terminal may return to the configuration before the temporary capability restriction is applied. Alternatively, if there is no separate signaling from the base station, the configuration (applied with the temporary capability restriction) may be maintained. If the prohibit timer does not expire in operation 1p-20, and if a release of the UE capability change occurs in the terminal in operation 1p-30, the terminal may transmit, to the base station, a message indicating that the UE capability change has been released in operation 1p-35, and may determine that the terminal has returned to the original UE capability, thereby restoring the previous configuration in operation 1p-40.
  • the terminal may return to the configuration before the temporary capability restriction is applied.
  • the configuration applied with the temporary capability restriction
  • the temporary capability restriction is required to be maintained without releasing the UE capability change in operation 1p-30, the changed UE capability is maintained (operation 1p-45).
  • FIG. 17 is a diagram illustrating an overall operation in which a terminal in an idle or inactive state requests a temporary change in UE capability according to an embodiment of the disclosure.
  • a terminal in an RRC idle/inactive state may have a temporary change in UE capability due to internal issues of the terminal (operation 1q-05). Thereafter, the terminal may internally produce a message by including a reason for requesting the change in UE capability and the changed content therein.
  • the message may be included in msg 3 or msg 5, or may be included in another RRC message ("UEAssistanceInformation" or a new RRC message) after an RRC connection procedure is completed, and a detail description thereof has been made in the above embodiments. That is, the message may include an indicator for a temporary capability restriction or information about a requested temporary capability restriction.
  • the terminal transmits a message including the change content of the terminal to the base station, and operates a prohibit timer to prevent repetition of the request.
  • the terminal switches to a connection state and operates by applying the temporary UE capability change.
  • the terminal may switch to an RRC connection state, and may immediately apply a corresponding configuration in this operation.
  • the base station may provide an RRC reconfiguration by reflecting the temporary capability restriction thereafter, or may not reflect the same, or the operation may be omitted.
  • the terminal determines that the terminal has returned to the original UE capability and restores the previous configuration in operation 1q-25. That is, the terminal may return to the configuration before the temporary capability restriction is applied. Alternatively, if there is no separate signaling from the base station, the configuration (applied with the temporary capability restriction) may be maintained. If the prohibit timer does not expire in operation 1q-20, and if a release of the UE capability change occurs in the terminal in operation 1q-30, the terminal may transmit, to the base station, a message indicating that the UE capability change has been released in operation 1q-35, and may determine that the terminal has returned to the original UE capability, thereby restoring the previous configuration in operation 1q-40.
  • the terminal may return to the configuration before the temporary capability restriction is applied.
  • the configuration applied with the temporary capability restriction
  • the temporary capability restriction is required to be maintained without releasing the UE capability change in operation 1q-30, the changed UE capability is maintained (operation 1q-45).
  • FIG. 18 is a diagram illustrating the overall operation of a base station that receives a temporary UE capability change of a terminal according to an embodiment of the disclosure.
  • the base station may determine whether to accept or reject the request message (operation 1r-10).
  • the message may be included in msg 3 or msg 5, or may be included in another RRC message ("UEAssistanceInformation" or a new RRC message) after an RRC connection procedure is completed, and a detail description thereof has been made in the above embodiments. That is, the message may include an indicator for a temporary capability restriction or information about a requested temporary capability restriction.
  • the base station may not provide the RRC reconfiguration reflecting the temporary UE capability change, and may ignore the same.
  • the base station may transmit a rejection message with respect to the temporary UE capability change request message of the terminal.
  • the base station may provide the terminal with a new RRC reconfiguration reflecting the temporary UE capability change in operation 1r-20.
  • the base station may transmit a confirm message indicating acceptance of the temporary UE capability change request message immediately after receiving the same, or may provide a new RRC reconfiguration reflecting the temporary UE capability change after transmitting the confirm message.
  • the base station may determine that the terminal has returned to the original configuration, and may manage the terminal according to the previous configuration, or may retransmit an RRC reconfiguration for the original configuration in operation 1r-30. Similarly, in the above operation, the base station may transmit a confirm message indicating acceptance of the temporary UE capability change release request message immediately after receiving the same, or may provide a new RRC reconfiguration reflecting the temporary UE capability change after transmitting the confirm message.
  • the base station determines that the terminal maintains the changed UE capability and manages the terminal by maintaining the RRC reconfiguration values reflecting the temporary UE capability change (operation 1r-35).
  • FIG. 19 is a diagram illustrating a configuration of a terminal according to an embodiment of the disclosure.
  • a terminal includes a transceiver 1s-05, a controller 1s-10, a multiplexer/demultiplexer 1s-15, various upper layer processors 1s-20 and 1s-25, and a control message processor 1s-30.
  • the transceiver 1s-05 receives data and predetermined control signals through a forward channel of a serving cell, and transmits data and predetermined control signals through a reverse channel thereof. In the case where a plurality of serving cells is configured, the transceiver 1s-05 performs transmission and reception of data and control signals through the plurality of serving cells.
  • the multiplexer/demultiplexer 1s-15 multiplexes data generated by the upper layer processors 1s-20 and 1s-25 or the control message processor 1s-30, or demultiplexes the data received by the transceiver 1s-05, thereby transmitting the same to the appropriate upper layer processor 1s-20 or 1s-25 or control message processor 1s-30.
  • the control message processor 1s-30 transmits and receives control messages to and from the base station, thereby performing necessary operations. These operations include processing control messages, such as an RRC message and a MAC CE, reporting channel busy ratio (CBR) measurement values, and receiving an RRC message for a resource pool and the terminal operation.
  • the upper layer processors 1s-20 and 1s-25 denote DRB devices, and may be configured for each service.
  • the upper layer processors 1s-20 and 1s-25 process data generated from user services, such as File Transfer Protocol (FTP) or Voice-over-Internet Protocol (VoIP), and transmit the same to the multiplexer/demultiplexer 1s-15, or process data transmitted from the multiplexer/demultiplexer 1s-15 and transmit the same to an upper level service application.
  • FTP File Transfer Protocol
  • VoIP Voice-over-Internet Protocol
  • the controller 1s-10 identifies scheduling commands (e.g., reverse grants) received through the transceiver 1s-05 and controls the transceiver 1s-05 and the multiplexer/demultiplexer 1s-15 so as to perform reverse transmission by means of appropriate transmission resources at an appropriate time.
  • scheduling commands e.g., reverse grants
  • the controller 1s-10 may perform a function performed by the multiplexer/demultiplexer 1s-15.
  • the controller 1s-10 may include at least one processor.
  • the controller 1s-10 may control the operation of the terminal according to the embodiment.
  • FIG. 20 is a diagram illustrating a configuration of a base station according to an embodiment of the disclosure.
  • a base station includes a transceiver 1t-05, a controller 1t-10, a multiplexer/demultiplexer 1t-20, a control message processor 1t-35, various upper layer processors 1t-25 and 1t-30, and a scheduler 1t-15.
  • the transceiver 1t-05 transmits data and predetermined control signals through a forward carrier and receives data and predetermined control signals through a reverse carrier. In the case where a plurality of carriers is configured, the transceiver 1t-05 performs transmission and reception of data and control signals through the plurality of carriers.
  • the multiplexer/demultiplexer 1t-20 multiplexes data generated by the upper layer processors 1t-25 and 1t-30 or the control message processor 1t-35, or demultiplexes data received by the transceiver 1t-05, thereby transmitting the same to the appropriate upper layer processor 1t-25 or 1t-30, the control message processor 1t-35, or the controller 1t-10.
  • the control message processor 1t-35 produces a message to be transmitted to the terminal and transmits the message to a lower layer under the control of the controller.
  • the upper layer processors 1t-25 and 1t-30 may be configured for each terminal and each service.
  • the upper layer processors 1t-25 and 1t-30 process data generated from user services, such as FTP or VoIP, and transmit the same to the multiplexer/demultiplexer 1t-20, or process data transmitted from the multiplexer/demultiplexer 1t-20 and transmit the same to an upper level service application.
  • the scheduler 1t-15 allocates transmission resources to the terminal at an appropriate time in consideration of the buffer status of the terminal, the channel status, the active time of the terminal, and the like, and allows the transceiver to processes the signals transmitted from the terminal or to transmit a signal to the terminal.
  • the controller 1t-10 may include at least one processor.
  • the controller 1t-10 may control the operation of the base station according to the embodiment.
  • a component included in the disclosure is expressed in the singular or the plural according to a presented detailed embodiment.
  • the singular form or plural form is selected for convenience of description suitable for the presented situation, and various embodiments of the disclosure are not limited to a single element or multiple elements thereof. Further, either multiple elements expressed in the description may be configured into a single element or a single element in the description may be configured into multiple elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une technique de communication permettant de fusionner, avec la technologie de l'Internet des objets (IdO), un système de communication de cinquième génération (5G) pour qu'il prenne en charge un débit de transmission de données supérieur à celui d'un système de quatrième génération (4G), et un système associé. La présente invention peut être appliquée à un service intelligent (par exemple, une maison intelligente, un bâtiment intelligent, une ville intelligente, une voiture intelligente ou connectée, des soins de santé, l'enseignement numérique, le commerce de détail, des services liés à la sécurité et à la sûreté, et similaires) sur la base d'une technologie de communication 5G et d'une technologie associée à l'IdO. L'invention concerne également un procédé de rapport de la capacité d'un équipement utilisateur (UE) d'un terminal et un dispositif associé.
PCT/KR2020/000735 2019-01-15 2020-01-15 Procédé et appareil permettant de rapporter la capacité ue d'un terminal dans un système de communication mobile de génération suivante WO2020149639A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20741312.1A EP3831108A4 (fr) 2019-01-15 2020-01-15 Procédé et appareil permettant de rapporter la capacité ue d'un terminal dans un système de communication mobile de génération suivante
CN202080009373.9A CN113302957A (zh) 2019-01-15 2020-01-15 在下一代移动通信系统中报告终端的ue能力的方法和装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2019-0005250 2019-01-15
KR1020190005250A KR102653811B1 (ko) 2019-01-15 2019-01-15 차세대 이동통신 시스템에서 단말의 단말 능력 보고 방법 및 장치

Publications (1)

Publication Number Publication Date
WO2020149639A1 true WO2020149639A1 (fr) 2020-07-23

Family

ID=71516228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/000735 WO2020149639A1 (fr) 2019-01-15 2020-01-15 Procédé et appareil permettant de rapporter la capacité ue d'un terminal dans un système de communication mobile de génération suivante

Country Status (5)

Country Link
US (1) US11553404B2 (fr)
EP (1) EP3831108A4 (fr)
KR (1) KR102653811B1 (fr)
CN (1) CN113302957A (fr)
WO (1) WO2020149639A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113795019A (zh) * 2021-08-09 2021-12-14 华为技术有限公司 一种通信控制方法和通信设备
WO2022242363A1 (fr) * 2021-05-21 2022-11-24 Oppo广东移动通信有限公司 Procédé et appareil de commande de connexion de réseau, dispositif terminal et support de stockage informatique

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11109305B2 (en) * 2019-01-28 2021-08-31 Qualcomm Incorporated Extended feature indication in NR
CN113424620A (zh) * 2019-02-19 2021-09-21 华为技术有限公司 跨LF和mmWave的服务连续性的方法和装置
US11265135B2 (en) 2020-06-03 2022-03-01 Dish Wireless Llc Method and system for slicing assigning for load shedding to minimize power consumption where gNB is controlled for slice assignments for enterprise users
US11202234B1 (en) 2020-06-03 2021-12-14 Dish Wireless L.L.C. Method and system for smart operating bandwidth adaptation during power outages
CN114071552A (zh) * 2020-07-29 2022-02-18 维沃移动通信有限公司 传输辅助信息的方法、终端设备和网络设备
US11470549B2 (en) 2020-07-31 2022-10-11 Dish Wireless L.L.C. Method and system for implementing mini-slot scheduling for all UEs that only are enabled to lower power usage
US11405941B2 (en) 2020-07-31 2022-08-02 DISH Wireless L.L.C Method and system for traffic shaping at the DU/CU to artificially reduce the total traffic load on the radio receiver so that not all the TTLs are carrying data
CN116391395A (zh) * 2020-10-16 2023-07-04 捷开通讯(深圳)有限公司 使用者设备、基站及识别使用者设备的方法
WO2022093511A1 (fr) * 2020-10-29 2022-05-05 Google Llc Informations de mesure d'assistance d'équipement utilisateur
US11799710B2 (en) * 2020-12-10 2023-10-24 Qualcomm Incorporated Techniques for signaling a source of dominant noise at a user equipment
US20240073675A1 (en) * 2021-01-15 2024-02-29 Sony Group Corporation Identification of reduced capability user equipment
EP4280791A1 (fr) * 2021-01-18 2023-11-22 LG Electronics Inc. Procédé de transmission et de réception de msg4 dans un système de communication sans fil, et dispositif correspondant
US11849507B2 (en) 2021-03-26 2023-12-19 Nokia Technologies Oy Temporary identification for a terminal device
US11838121B2 (en) * 2021-07-01 2023-12-05 Qualcomm Incorporated Downlink transmission requirement based on downlink compensation capability of a user equipment
WO2023239274A1 (fr) * 2022-06-10 2023-12-14 Beammwave Ab Procédé d'obtention d'une capacité pour un agencement d'émetteur et de récepteur à antennes multiples, produit programme d'ordinateur, support de stockage lisible par ordinateur non transitoire, dispositif sans fil et nœud d'émetteur-récepteur
KR20240039280A (ko) * 2022-09-19 2024-03-26 삼성전자주식회사 이통 통신 시스템에서 단말 보조 정보의 개선에 관한 방법 및 장치
WO2024077495A1 (fr) * 2022-10-11 2024-04-18 北京小米移动软件有限公司 Procédé et appareil de transmission d'informations de capacités, et support de stockage lisible

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120064909A1 (en) * 2008-02-25 2012-03-15 Bengt Lindoff Alleviating Mobile Device Overload Conditions in a Mobile Communication System
WO2019206238A1 (fr) 2018-04-28 2019-10-31 华为技术有限公司 Procédé de communication sans fil, et dispositif de communication sans fil

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2423456T3 (es) 2007-02-12 2013-09-20 Motorola Mobility Llc Aparato y método que proporcionan interfuncionamiento multi-RAT estableciendo prioridades
CN104969646B (zh) * 2013-02-06 2019-06-04 Lg 电子株式会社 在无线通信系统中限制频率的方法和设备
WO2017027057A1 (fr) 2015-08-13 2017-02-16 Intel IP Corporation Rapport de capacité d'équipement utilisateur
US10154455B1 (en) 2016-08-10 2018-12-11 Mbit Wireless, Inc. Method and apparatus for broadcast information transmission
US10993104B2 (en) * 2017-11-17 2021-04-27 Apple Inc. Temporary handling of wireless communication device capabilities
US20190215729A1 (en) * 2018-03-15 2019-07-11 Intel Corporation Session description protocol mechanisms for signaling radio access network capabilities in multimedia telephony sessions
US10986527B2 (en) * 2018-06-22 2021-04-20 Sharp Laboratories Of America, Inc. Method and apparatus for indicating restricted resources of wireless terminal and for indicating access node capability to support connection with a wireless terminal with restricted capabilities
EP3845007A1 (fr) * 2018-08-28 2021-07-07 Ofinno, LLC Transmission en liaison montante dans un système de communication sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120064909A1 (en) * 2008-02-25 2012-03-15 Bengt Lindoff Alleviating Mobile Device Overload Conditions in a Mobile Communication System
WO2019206238A1 (fr) 2018-04-28 2019-10-31 华为技术有限公司 Procédé de communication sans fil, et dispositif de communication sans fil

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Extension of overheating indication parameters", 3GPP DRAFT; R2-1818531, 16 November 2018 (2018-11-16), Spokane, USA, pages 1 - 2, XP051482379 *
HUAWEI; HISILICON: "CR on signalling introduction of UE overheating support in NR SA scenario", 3GPP DRAFT; R2-1819179, 16 November 2018 (2018-11-16), Spokane, Washington, USA, pages 1 - 20, XP051495403 *
HUAWEI; HISILICON: "UE overheating support for late drop", 3GPP DRAFT; R2-1818035, 16 November 2018 (2018-11-16), Spokane, Washington, USA, pages 1 - 2, XP051481915 *
HUAWEI; HISILICON: "UE overheating support in NR SA scenario", 3GPP DRAFT; R2-1815142, 8 October 2018 (2018-10-08), Chengdu, China, pages 1 - 3, XP051524508 *
See also references of EP3831108A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022242363A1 (fr) * 2021-05-21 2022-11-24 Oppo广东移动通信有限公司 Procédé et appareil de commande de connexion de réseau, dispositif terminal et support de stockage informatique
CN113795019A (zh) * 2021-08-09 2021-12-14 华为技术有限公司 一种通信控制方法和通信设备
CN113795019B (zh) * 2021-08-09 2022-12-30 华为技术有限公司 一种通信控制方法和通信设备

Also Published As

Publication number Publication date
US11553404B2 (en) 2023-01-10
KR20200088667A (ko) 2020-07-23
US20200229076A1 (en) 2020-07-16
EP3831108A1 (fr) 2021-06-09
KR102653811B1 (ko) 2024-04-03
CN113302957A (zh) 2021-08-24
EP3831108A4 (fr) 2021-10-06

Similar Documents

Publication Publication Date Title
WO2020149639A1 (fr) Procédé et appareil permettant de rapporter la capacité ue d'un terminal dans un système de communication mobile de génération suivante
WO2020159227A1 (fr) Procédé et appareil pour améliorer l'agrégation de porteuse dans un système de communication mobile de nouvelle génération
WO2019160270A1 (fr) Procédé et appareil permettant une opération efficace lors de l'activation et de la désactivation d'une duplication de paquets dans un système de communication sans fil de prochaine génération
WO2018147677A1 (fr) Procédé et appareil pour une opération en mode inactif dans un système de communication sans fil
WO2019190245A1 (fr) Appareil et procédé de mesure dans un système de communication sans fil
WO2020159222A1 (fr) Procédé et dispositif d'activation et de désactivation par liaison permettant de réduire la consommation d'énergie dans un système de communication mobile de prochaine génération
WO2018174483A1 (fr) Procédé et appareil pour prendre en charge un mode de réception discontinue de mode connecté dans un système de communication mobile
WO2019225888A1 (fr) Procédé et appareil de classification et de traitement d'une pdu de commande sdap dans un système de communication mobile de prochaine génération
WO2021010759A1 (fr) Procédé et appareil pour l'exploitation efficace de la partie dormante d'une largeur de bande dans un système de communication mobile de nouvelle génération
WO2021251804A1 (fr) Procédé et appareil pour la prise en charge d'un mbs dans un système de communication sans fil
WO2019190180A1 (fr) Procédé et dispositif de renseignements csi en mode drx dans un système de communication sans fil de nouvelle génération
WO2022031053A1 (fr) Procédé et dispositif pour prendre en charge de multiples configurations de scg dans une connectivité double prise en charge par un système de communication mobile de nouvelle génération
WO2020032702A1 (fr) Procédé et appareil de configuration d'une connexion de réseau dans un système de communication mobile
WO2019194605A1 (fr) Procédé et appareil de fourniture efficace d'informations de commande de configuration de contrôle d'accès dans un système de communication sans fil de prochaine génération
WO2020060178A1 (fr) Procédé et appareil de signalement de rmtp sélectionné d'eu en mode de commande de ressource radio rrc inactive dans un système de communications de la prochaine génération
WO2020145682A1 (fr) Procédé et appareil pour réaliser une communication dans un système de communication sans fil
WO2021029750A1 (fr) Procédé et dispositif de mesure dans un système de communication sans fil
WO2020162733A1 (fr) Procédé et appareil pour mettre à jour une liste de cellules à mesurer dans une resélection de cellule en mode veille dans un système de communication sans fil de prochaine génération
WO2020190007A1 (fr) Procédé et appareil pour l'exécution d'une resélection de cellule dans un système de communications sans fil
WO2022035281A1 (fr) Procédé et appareil d'activation et de réactivation de scell prenant en considération la partie de bande passante actuellement activée et les des informations de configuration de partie de bande passante dans un système de communication mobile de prochaine génération
WO2018226024A1 (fr) Procédé et appareil de configuration d'un dispositif pdcp et d'un dispositif sdap dans un système de communication mobile de prochaine génération
WO2020111745A1 (fr) Procédé et appareil de coordination entre nœuds pour une relation de voisinage automatique
WO2021158061A1 (fr) Procédé et appareil de configuration de bande passante dans un système de communication sans fil
WO2022015028A1 (fr) Procédé et appareil pour traiter la mini transmission de données avec rrc à l'état inactif dans un système de communication sans fil
WO2021091088A1 (fr) Procédé et appareil de configuration dynamique de mesure de perte de canal dans un système de communication mobile de prochaine génération

Legal Events

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

Ref document number: 20741312

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020741312

Country of ref document: EP

Effective date: 20210305

NENP Non-entry into the national phase

Ref country code: DE