Method and device for cell classification of terminal in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates and satisfying various service requirements. Provided is a method performed by a UE in a wireless communication system. The method comprises the steps of: receiving, from a base station, an SIB including information about a cell indicating whether the cell is barred for a specific UE type, wherein the information about the cell is configured barred, the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, and the cell is not considered barred due to other reasons except that the information about the cell is configured barred; and considering the cell as an acceptable cell for initiating the emergency call when a cell selection criterion is satisfied.

Description

Method and device for cell classification of a terminal in a wireless communication system

[0001] The present disclosure relates generally to terminal and base station operations in a wireless communication system, and more specifically to a method and device for classifying cells in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz band ('Sub 6GHz'), such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band ('Above 6GHz'), also known as millimeter wave (mmWave), such as 28GHz and 39GHz. Furthermore, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), it is expected that it will be very important to secure new frequency resources, such as the sub-6GHz band, ultra-high frequency bands, and the upper mid band (7-24GHz), to handle the rapidly increasing data traffic due to the spread of artificial intelligence (AI) technology and the increase in streaming services and to improve user experience. It is expected that it will become very important to secure new frequency resources, such as the mid-frequency band (7-24GHz), also called the upper mid band, and to utilize all available frequency resources efficiently as needed. To this end, reallocating, reusing, or sharing existing frequency bands from 2G to 5G for 6G may be considered. Separately, since the introduction of 5G, the communications market has seen a growing focus on system operational efficiency, sustainability, and improved user experience. Consequently, in addition to improving traditional communication performance, such as data transmission speed and latency, the adoption of new innovative technologies like AI, operational cost reduction, energy efficiency improvements, expanded service coverage, and the introduction of new services are becoming increasingly important.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase radio transmission distances, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (band-width part), new channel coding methods such as LDPC (low density parity check) codes for large-capacity data transmission and polar codes for reliable transmission of control information, L2 pre-processing, and networks that provide dedicated networks specialized for specific services. Standardization of slicing (network slicing) etc. has been progressing.

[0004] Since the early days of 5G mobile communication technology, discussions have been held on improving and enhancing the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, including V2X (vehicle-to-everything) to help autonomous vehicles make driving decisions based on their own location and status information transmitted by the vehicle and to increase user convenience, NR-U (new radio unlicensed) for the purpose of system operation that meets various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE power saving), non-terrestrial network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, positioning, NR support up to 71 GHz, support of reduced capability NR devices for lower cost and complexity compared to general terminals, UE power saving enhancement for improved power management in preparation for the use of various terminal types, and sidelink. Evolution of duplexing technology (duplex enhancements) that researches a new type of duplexing called subband non-overlapping full duplex (SBFD), sidelink enhancement, network energy saving that secures the idle period in which the base station operates in maximum power saving mode and reduces power consumption.Physical layer standardization has been carried out for technologies such as network controlled repeaters, which have improved performance compared to existing repeaters by having the ability to receive and process side control information from the network.

[0005] In addition, it supports new services through linkage and convergence with other industries, including the Industrial Internet of Things (IIoT), an intelligent factory, IAB (Integrated Access and Backhaul) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, 2-step RACH for NR that simplifies random access procedures, multicast and broadcast, standardization of support for multi USIM devices that provide services to users using information from two or more subscriber identity modules (SIMs), sidelink relay that provides relay-related functions to support connections between terminals in long distances and between terminals and networks, small data transmission (SDT) that transmits small data or signaling in an inactive state without transitioning to a connected state, and lower layer triggered mobility (L1 / L2 triggered mobility, LTM) / continuous Standardization of the radio interface architecture / protocol layer for technologies such as mobility enhancements including subsequent conditional PScell ​​addition / change (SCPAC) / conditional handover with candidate SCGs, and extended reality support (XR enhancement) to support XR services in NR systems has also been progressing.5G baseline architecture for integrating network functions virtualization (NFV) and software-defined networking (SDN) technologies (e.g., service-based architecture, service-based interface), mobile edge computing (MEC) that provides services based on the location of the terminal, non-public networks (NPN) that can be used only by some permitted terminals for non-public purposes, disaster roaming that supports the use of communication services through other carrier networks in the event of a communication disaster, proximity-based service via 5G system, support of UAS to support remote identification, tracking, and authorization of uncrewed aerial vehicles (UAVs), structural enhancements to support XR and interactive media services, 5GS to support AI / ML (artificial intelligence / machine learning) services, and advanced mobile edge computing that provides edge computing services in a roaming network. Standardization of system architecture / service fields for the back has also been carried out.

[0006] Currently, at the physical layer, standardization is in progress for technologies such as beam prediction using AI / ML technology, CSI (channel state information) prediction to improve positioning accuracy, ultra-low power terminal technology using low-power wake-up receivers, technology for transmitting LTE (long term evolution) broadcasts to 5G networks, MIMO transmission technology using multiple base stations, and ultra-low power terminals (ambient IoT) that transmit data by obtaining power from an external source without a battery. At the radio interface architecture / protocol layer, standardization is in progress for technologies such as support for LTM scenarios and conditional LTM between Central Units (CUs), support for the same XR service simultaneously between multiple devices, NTN coverage enhancement and evolution, AI / ML-based mobility support, and terminal-to-terminal connection relay across multiple hops between terminals and the network. Furthermore, standardization is underway for satellite communication optimization, energy management and efficiency improvement of 5G systems, SBI-based user plane evolution, Ambient IoT technology, data service provision methods over the IP multimedia subsystem (IMS), and system architecture / service standardization for avatar communication services. Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices.To this end, additional new research will be conducted on eXtended Reality (XR), AI / ML-based 5G performance improvement and complexity reduction, AI service support, metaverse service support, drone communications, etc. to efficiently support augmented reality (AR), virtual reality (VR), and mixed reality (MR).

[0007] Furthermore, the advancement of 5G mobile communication systems is expected to enhance 5G performance and ultimately serve as the foundation for its evolution to 6G. In the 6G era, the three major 5G services mentioned above—eMBB, URLLC, and mMTC—are expected to evolve and expand into immersive communication (IC), hyper-reliable and low-latency communication (HRLLC), and massive communication (MC) services, respectively. In addition, new services such as artificial intelligence (AI) and communication, integrated sensing and communication, and ubiquitous connectivity will be additionally supported. To meet these diverse 6G services, improved performance requirements compared to 5G are essential, and standardization to define these requirements is currently underway.

[0008] In this way, to meet the expanded services and enhanced performance requirements of 6G, it is expected that not only will it be essential to improve existing communication performance, but also to optimize and streamline system operation through the introduction of AI technology, improved energy efficiency, expanded coverage, and application of next-generation security technologies, as well as the development of sustainable communication technologies.

[0009] To this end, the latest AI technology is applied to all areas from the communication system design stage to development, management, and operation to improve communication performance and realize network automation and efficiency; AI-embedded technology that improves user-perceived performance and network operation efficiency by improving power consumption of networks and terminals; technology that reduces power consumption in core base station components such as RF (radio frequency) and modems and in the process of channel coding and signal modulation and demodulation transmission and reception; multi-antenna transmission technology (eXtreme MIMO, X-MIMO) that utilizes large-scale antennas to overcome propagation path loss due to high frequency compared to the 3.5 GHz band of 5G communication and provide equivalent coverage; multiple base station-based transmission and reception technology (distributed MIMO, D-MIMO) to improve quality in cell edge areas; full-duplex communication (sub-band non-overlapping full duplex, SBFD) technology to improve frequency efficiency and system network; next-generation encryption technology (post quantum cryptography, PQC) and zero trust architecture (ZTA) technology to strengthen 6G communication security; initial access delay and mobility Research will be focused on technologies to minimize delay, designing a hardware-friendly protocol structure for ultra-high-speed data processing, and expanding the application of integrity protection technologies.

[0010] In addition, research will be conducted on the structure of mobile communication systems (preventing redundant functions, simplifying functions, etc.), introducing new planes for providing service providers, protecting user privacy, realistic services, enhancing network resiliency, network sharing technologies, improved security technologies (false base stations, lower layer protection, etc.), and intent-based network operation and management.

[0011]

[0012] Various embodiments of the present disclosure can provide a method and apparatus for classifying cells in a wireless communication system.

[0013] In one embodiment of the present disclosure in a wireless communication system, if a cell does not bar the cell according to a barring indicator according to a terminal type, or if, in one embodiment of the present disclosure, the cell is regarded as an acceptable cell (exceptionally) by satisfying a predetermined condition even if the cell is barred by the barring indicator according to a terminal type, or if, in one embodiment of the present disclosure, the cell is regarded as an acceptable cell by satisfying a predetermined condition such as a setting of a support function or capability of a terminal, in one embodiment of the present disclosure, a method and device are provided that may not exclude the cell from a cell selection and / or reselection candidate, or may include the cell.

[0014] The technical problems to be achieved in various embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from various embodiments of the present disclosure described below.

[0015]

[0016] To address the above-described problems, the present disclosure provides a method performed by a user equipment (UE) in a wireless communication system. The method comprises the steps of: receiving, from a base station, a system information block (SIB) including information about a cell indicating whether the cell is barred for a specific UE type, wherein the information about the cell is set to barred or not barred, and the UE supports the specific UE type; if the information about the cell is set to barred and the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, determining whether the cell is considered barred for a reason other than the fact that the information about the cell is set to barred and whether a cell selection criterion is met; and if the cell is not considered barred for the other reason and the cell selection criterion is met, considering the cell as an acceptable cell for initiating the emergency call.

[0017] According to the present disclosure, a method performed by a base station in a wireless communication system is provided. The method comprises the steps of: generating information about a cell indicating whether the cell is barred for a specific user equipment (UE) type, wherein the information about the cell is set to barred or not barred; and transmitting a system information block (SIB) including the information about the cell to the UE, wherein the UE supports the specific UE type, and the information about the cell is set to barred, and the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, and wherein the cell is not considered barred for a reason other than the information about the cell being set to barred, and if a cell selection criterion is met, the cell is considered an acceptable cell for initiating the emergency call.

[0018] According to the present disclosure, a UE is provided in a wireless communication system. The UE comprises: at least one transceiver; at least one processor communicatively connected to the at least one transceiver; And a memory communicatively connected to the at least one processor and executable by the at least one processor, wherein the UE receives, from a base station, a system information block (SIB) including information about the cell indicating whether the cell is barred for a specific UE type, wherein the information about the cell is set to barred or not barred and the UE supports the specific UE type, and when the information about the cell is set to barred and the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, determine whether the cell is considered barred for a reason other than the information about the cell being set to barred and whether a cell selection criterion is met, and if the cell is not considered barred for the other reason and the cell selection criterion is met, consider the cell as an acceptable cell for initiating the emergency call.

[0019] According to the present disclosure, a base station is provided in a wireless communication system. The base station comprises: at least one transceiver; at least one processor communicatively connected to the at least one transceiver; And a memory communicatively connected to the at least one processor, and executable by the at least one processor, storing instructions that cause the base station to generate information about the cell indicating whether the cell is barred for a specific user equipment (UE) type, wherein the information about the cell is set to barred or not barred, and transmit a system information block (SIB) including the information about the cell to the UE, wherein the UE supports the specific UE type, and the information about the cell is set to barred, and the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, and wherein the cell is not considered barred for a reason other than the information about the cell being set to barred, and if a cell selection criterion is met, the cell is considered an acceptable cell for initiating the emergency call.

[0020] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.

[0021]

[0022] Various embodiments of the present disclosure may provide a method and apparatus for classifying cells in a wireless communication system.

[0023] According to the present disclosure, in a wireless communication system, even if a cell is barred by a barring indicator according to the terminal type for a terminal in an RRC_IDLE or RRC_INACTIVE state, if the terminal's supported function or capability does not match the settings of the cell, there may be cases where the cell is barred because no service, including limited services, can be used accordingly.

[0024] In such cases, there may be cases where a cell is not considered an acceptable cell (even exceptionally) due to failure to satisfy cell selection and / or reselection conditions for a given period of time. To address this, a method and device are provided that allows a terminal to perform an operation to consider a cell (exceptionally) acceptable, by not excluding the cell from cell selection and / or reselection candidates, or to include the cell if the cell satisfies the given conditions. This allows for the use of limited services (e.g., emergency calls).

[0025] According to one embodiment of the present disclosure, it can be applied to a terminal in standby or inactive mode.

[0026] According to one embodiment of the present disclosure, it can be applied to a RedCap terminal, an eRedCap terminal, or a 2RX XR terminal.

[0027] The effects that can be obtained from various embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly derived and understood by a person having ordinary skill in the art based on the detailed description below.

[0028]

[0029] The accompanying drawings are intended to aid in understanding various embodiments of the present disclosure, and provide various embodiments of the present disclosure together with detailed descriptions. However, the technical features of the various embodiments of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing represent structural elements.

[0030] FIG. 1 is a diagram illustrating the structure of a mobile communication system according to one embodiment of the present disclosure.

[0031] FIG. 2 is a diagram for explaining a wireless connection state transition in a mobile communication system according to an embodiment of the present disclosure.

[0032] FIG. 3 is a diagram illustrating a method by which an inactive mode or standby mode terminal considers a cell as an acceptable cell according to one embodiment of the present disclosure.

[0033] FIG. 4 is a diagram illustrating the internal structure of a terminal according to an embodiment of the present disclosure.

[0034] FIG. 5 is a diagram illustrating the structure of a base station according to an embodiment of the present disclosure.

[0035]

[0036] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

[0037] In describing the embodiments herein, descriptions of technical details that are well-known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present invention by omitting unnecessary explanations and to convey the gist more clearly.

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

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

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

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

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

[0043] Here, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, according to some embodiments, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within the device or secure multimedia card. Furthermore, according to some embodiments, the '~parts' may include one or more processors.

[0044] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (high speed packet access), LTE (long term evolution or E-UTRA (evolved universal terrestrial radio access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (high rate packet data), UMB (ultra mobile broadband), and IEEE's 802.16e.

[0045] As a representative example of the above broadband wireless communication system, the LTE system adopts the orthogonal frequency division multiplexing (OFDM) method in the downlink (DL) and the single carrier frequency division multiple access (SC-FDMA) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (user equipment (UE) or mobile station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0046] As a future communication system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC).

[0047] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must provide both the peak data rate and the increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz bands.

[0048] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require broader coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be comprised of low-cost terminals, and because frequent battery replacement is difficult, they may require extremely long battery lifespans, such as 10 to 15 years.

[0049] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanaged aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and at the same time, a 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller transmit time interval (TTI) than other services, while simultaneously requiring design considerations such as allocating a wide range of resources in the frequency band to ensure communication link reliability.

[0050] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0051] In the following description, terms referring to broadcast information, terms referring to control information, terms related to communication coverage, terms referring to state changes (e.g., events), terms referring to network entities, terms referring to messages, terms referring to device components, etc. are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

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

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

[0054]

[0055] FIG. 1 is a diagram illustrating the structure of a mobile communication system according to one embodiment of the present disclosure.

[0056] Referring to FIG. 1, a wireless access network of a mobile communication system (new radio, NR) according to one embodiment of the present disclosure may be composed of a base station (next generation Node B, hereinafter referred to as gNB) (1a-10) and an AMF (1a-05, new radio core network).

[0057] According to one embodiment of the present disclosure, a user terminal (new radio user equipment, hereinafter referred to as NR UE or terminal) (1a-15) can access an external network through a gNB (1a-10) and an AMF (1a-05).

[0058] According to one embodiment of the present disclosure, the mobile communication system may be a next-generation mobile communication system, and the base station may be a next-generation base station.

[0059] According to one embodiment, the gNB (1a-10) in FIG. 1 may correspond to the eNB (1a-30, evolved Node B) of the existing LTE system. The gNB (1a-10) is connected to the NR UE (1a-15) via a wireless channel and may provide a service superior to that of the existing Node B (1a-20). In the next-generation mobile communication system according to one embodiment of the present disclosure, since all user traffic is serviced through a shared channel, a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling may be required, and this may be performed by the gNB (1a-10). According to one embodiment, one gNB (1a-10) may typically control multiple cells. In order to implement ultra-high-speed data transmission, it may have a bandwidth greater than the existing maximum, and orthogonal frequency division multiplexing (OFDM) may be used as a wireless access technology, and additional beamforming technology may be incorporated. Additionally, an adaptive modulation & coding (AMC) method can be applied, which determines the modulation scheme and channel coding rate according to the channel status of the terminal.

[0060] According to one embodiment, in FIG. 1, the AMF (1a-05) can perform functions such as mobility support, bearer setup, and QoS (quality of service) setup. The AMF (1a-05) is a device that is responsible for various control functions as well as mobility management functions for a terminal and can be connected to multiple base stations. In addition, the mobile communication system according to one embodiment of the present disclosure can also be linked with an LTE system, and for example, the AMF (1a-05) can be connected to an MME (1a-25) via a network interface.

[0061] According to one embodiment, the MME (1a-25) may be connected to an existing base station, eNB (1a-30). For example, in FIG. 1, a terminal supporting LTE-NR Dual Connectivity may transmit and receive data while maintaining connection to not only the gNB (1a-10) but also the eNB (1a-30) (1a-35).

[0062]

[0063] FIG. 2 is a diagram for explaining a wireless connection state transition in a mobile communication system according to an embodiment of the present disclosure.

[0064] According to one embodiment of the present disclosure, a mobile communication system may have three radio access states (RRC (radio resource control) states) or RRC modes.

[0065] According to FIG. 2, the connected mode (RRC_CONNECTED, 1b-05) may be a wireless connection state in which the terminal can transmit and receive data. Additionally, the standby mode (RRC_IDLE, 1b-30) may correspond to a wireless connection state in which the terminal monitors whether paging is being transmitted to itself. The above two modes are wireless connection states also applicable to the LTE system, and the detailed description may be identical to that of the LTE system. The mobile communication system according to an embodiment of the present disclosure may be a next-generation mobile communication system.

[0066] According to one embodiment of the present disclosure, a new inactive (RRC_INACTIVE) radio connection state (1b-15) may be defined in a mobile communication system. In this radio connection state (1b-15), a terminal context (UE context) may be maintained between a base station and a terminal, and radio access network (RAN)-based paging may be supported. The characteristics of this new radio connection state (1b-15) may include at least one of the following:

[0067] - Cell re-selection mobility;

[0068] - CN - NR RAN connection (both C / U-planes (control plane / user plane)) has been established for UE;

[0069] - The UE AS(Access Stratum) context is stored in at least one gNB and the UE;

[0070] - Paging is initiated by NR RAN;

[0071] - RAN-based notification area is managed by NR RAN;

[0072] - NR RAN knows the RAN-based notification area which the UE belongs to;

[0073] According to one embodiment of the present disclosure, a terminal in an INACTIVE wireless connection state (1b-15) can use a specific procedure and transition to a connected mode (1b-05) or a standby mode (1b-30). The terminal can transition from the INACTIVE mode (1b-15) to the connected mode (1b-05) using a Resume procedure, and can transition from the connected mode (1b-05) to the INACTIVE mode (1b-15) using a Release procedure including suspend configuration information (1b-10). The procedure can be performed by transmitting and receiving one or more RRC messages between the terminal and the base station, and can consist of one or more steps. In addition, according to one embodiment, transitioning from the INACTIVE mode (1b-15) to the standby mode (1b-30) can be possible through a Release procedure after the Resume procedure (1b-20). The transition between the connected mode (1b-05) and the standby mode (1b-30) can be performed according to LTE technology. Additionally, according to FIG. 2, switching between the above modes can be achieved through an establishment or release procedure (1b-25).

[0074] A 2RX XR terminal or 2RX XR UE (extended reality user equipment with 2 RX (reception) antenna ports or extended reality user equipment with 2 RX branches) can be defined as shown in Table 1 below.

[0075]

[0076] RedCap terminals or RedCap UE (reduced capability user equipment) and eRedCap terminals or eRedCap UE (enhanced reduced capability user equipment) can be defined as shown in Table 2 below.

[0077]

[0078] In one embodiment of the present disclosure, the (e)RedCap terminal may be at least one type of terminal among the following.

[0079] - RedCap terminal

[0080] - eRedCap terminal

[0081] In one embodiment of the present disclosure, the terminal may be at least one type of terminal among the following.

[0082] - 2RX XR terminal

[0083] - RedCap terminal

[0084] - eRedCap terminal

[0085] In one embodiment of the present disclosure, the (e)RedCap terminal may support 1 Rx branch (or 1 Rx antenna port) and / or 2 Rx branches (or 2 Rx antenna ports) (per specific frequency or frequency band).

[0086] In one embodiment of the present disclosure, the (e)RedCap terminal may support only half duplex FDD (frequency division duplex) or may support full duplex FDD (frequency division duplex).

[0087]

[0088] In one embodiment of the present disclosure, a terminal in inactive mode (RRC_INACTIVE) or standby mode (RRC_IDLE) can classify cells as shown in Table 3 below.

[0089]

[0090] In one embodiment of the present disclosure, a terminal in inactive mode (RRC_INACTIVE) or standby mode (RRC_IDLE) can classify cells based on indicators included in system information (e.g., MIB or SIB1) as shown in Table 4 below.

[0091]

[0092]

[0093]

[0094] In one embodiment of the present disclosure, a terminal in an inactive mode (RRC_INACTIVE) or standby mode (RRC_IDLE) may determine or set a cell as a barred cell or consider a cell as a barred cell based on an indicator included in the system information (e.g., SIB1) listed in Table 4, as shown in Table 5 below.

[0095]

[0096] In one embodiment of the present disclosure, if a cell is not barred according to Table 3 and satisfies cell selection conditions, the terminal may consider the cell as an acceptable cell and may use limited services (e.g., performing an emergency call (EM) call, receiving an earthquake and tsunami warning system (ETWS) and commercial mobile alert service (CMAS) notification) in the acceptable cell. If the cell is barred, the cell may no longer be an acceptable cell and the terminal may not be able to use the limited services.

[0097] In one embodiment of the present disclosure, even if a cell is barred, a terminal may exceptionally consider the cell as an acceptable cell and use limited services if certain conditions are satisfied.

[0098]

[0099] For example, a 1 Rx branch RedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied:

[0100] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true)

[0101] - If the terminal supports only 1 Rx branch (not supporting 2 Rx branches)

[0102] - If the base station sets the cellBarredRedCap1Rx indicator to "barred" via system information (e.g. SIB1).

[0103] - If the cell selection condition is satisfied for the cell in question

[0104] - If the terminal supports only half duplex FDD, and the base station sets the halfDuplexRedCapAllowed indicator to "true" through system information (e.g. SIB1).

[0105] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0106]

[0107] For example, a 2 Rx branch RedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied:

[0108] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true).

[0109] - If the terminal supports 2 Rx branches

[0110] - If the base station sets the cellBarredRedCap2Rx indicator to "barred" via system information (e.g. SIB1).

[0111] - If the cell selection condition is satisfied for the cell in question

[0112] - Only when the terminal supports only half duplex FDD, if the base station indicates halfDuplexRedCapAllowed as "true" through system information (e.g. SIB1).

[0113] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0114] The above RedCap terminal operation can follow Table 6.

[0115]

[0116] For example, a 1 Rx branch eRedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied:

[0117] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true).

[0118] - If the terminal supports only 1 Rx branch (not supporting 2 Rx branches)

[0119] - If the base station sets the cellBarred-eRedCap1Rx (or cellBarredeRedCap1Rx) indicator to "barred" via system information (e.g. SIB1).

[0120] - If the cell selection condition is satisfied for the cell in question

[0121] - If the terminal supports only half duplex FDD, and the base station sets the halfDuplexRedCapAllowed indicator to "true" through system information (e.g. SIB1).

[0122] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0123]

[0124] For example, a 2 Rx branch eRedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied:

[0125] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true).

[0126] - If the terminal supports 2 Rx branches

[0127] - If the base station sets the cellBarred-eRedCap2Rx (or cellBarredeRedCap2Rx) indicator to "barred" via system information (e.g. SIB1).

[0128] - If the cell selection condition is satisfied for the cell in question

[0129] - Only when the terminal supports only half duplex FDD, if the base station indicates halfDuplexRedCapAllowed as "true" through system information (e.g. SIB1).

[0130] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0131]

[0132] For example, a 2 Rx XR terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied:

[0133] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true).

[0134] - If the terminal supports 2 Rx branches

[0135] - If the base station sets the cellBarred2RxXR indicator to (“barred”) via system information (e.g. SIB1).

[0136] - If the cell selection condition is satisfied for the cell in question

[0137] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0138] The operation of the above eRedCap terminal or 2 Rx XR terminal may follow Table 7.

[0139]

[0140] However, the following issues may arise with respect to the operation of the aforementioned (e)RedCap terminal or 2 Rx XR terminal.

[0141] Issue 1: According to the above-described operation, even if the terminal bars the cell according to the terminal type-specific barring indicator (e.g., cellBarredRedCap1Rx, cellBarredRedCap2Rx, cellBarred-eRedCap1Rx, cellBarred-eRedCap2Rx, cellBarred2RxXR) in the system information (e.g., SIB1), if a certain condition is satisfied, the cell is regarded as an acceptable cell and can use a limited service (e.g., an operation of performing an emergency call (EM) call, an operation of receiving an earthquake and tsunami warning system (ETWS) and commercial mobile alert service (CMAS) notification). However, even if the terminal bars the cell by the terminal type-specific barring indicator (e.g., cellBarredRedCap1Rx, cellBarredRedCap2Rx, cellBarred-eRedCap1Rx, cellBarred-eRedCap2Rx, cellBarred2RxXR), if the terminal's supported function or capability does not match the configuration of the cell, the terminal may have to bar the cell because no service (e.g., including limited services) can be used accordingly. For example, if an inactive or standby terminal does not satisfy at least one of the conditions in Table 8 when receiving SIB1, the terminal may bar the cell.

[0142] - 조건 1. UE supports one or more of the frequency bands indicated in the frequencyBandList or frequencyBandListAerial for downlink for TDD, or one or more of the frequency bands indicated in the frequencyBandList or frequencyBandListAerial for uplink for FDD, and they are not downlink only bands - 조건 2. UE is IAB-MT or wide area NCR-MT (see TS 38.106

[0079] ) or supports at least one additionalSpectrumEmission in the nr-NS-PmaxList or nr-NS-PmaxListAerial for a supported band in the downlink for TDD, or a supported band in uplink for FDD - 조건 3. UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1

[0015] , TS 38.101-2

[0039] , and TS 38.101-5

[0075] ) which - is smaller than or equal to the carrierBandwidth (indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for (e)RedCap UE, of the RedCap-specific initial uplink BWP if configured), and which - is wider than or equal to the bandwidth of the initial uplink BWP or, for (e)RedCap UE, of the RedCap-specific initial uplink BWP if configured - 조건 4. UE supports a downlink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1

[0015] , TS 38.101-2

[0039] , and TS 38.101-5

[0075] ) which - is smaller than or equal to the carrierBandwidth (indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or, for (e)RedCap UE, of the RedCap-specific initial downlink BWP if configured), and which - is wider than or equal to the bandwidth of the initial downlink BWP or, for (e)RedCap UE, of the RedCap-specific initial downlink BWP if configured, - 조건 5.frequencyShift7p5khz is present and the UE supports corresponding 7.5kHz frequency shift on this band; or frequencyShift7p5khz is not present - Condition 6. UE is neither a RedCap nor an eRedCap UE, or for TDD if the UE is an (e)RedCap UE, or for FDD if the UE is an (e)RedCap UE and halfDuplexRedCapAllowed is present, or if the UE is an (e)RedCap UE and the (e)RedCap UE supports full-duplex FDD operation on this band.

[0143] As another example, when an inactive or standby mode terminal receives SIB1, even if all of the above conditions (conditions 1 to 6) are satisfied, if condition 7 of Table 9 is satisfied, the terminal can bar the corresponding cell.

[0144] - Condition 7: Neither trackingAreaCode nor trackingAreaList is provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list

[0145]

[0146] The above terminal operation may be as shown in Table 10.

[0147]

[0148] If a terminal rejects a cell according to the conditions in Table 8 and / or Table 9, or according to Table 10, this may mean that the terminal's supported functions or capabilities do not match the configuration of the cell, and the terminal may not be able to use any services (including, for example, limited services) in the cell. Accordingly, if the terminal does not satisfy at least one of the conditions in Table 8, or if it satisfies the conditions in Table 9, the terminal may not consider the cell as an acceptable cell.

[0149] In one embodiment of the present disclosure, terminal operation may be as shown in Table 11.

[0150] In one embodiment of the present disclosure, a 1 Rx branch RedCap terminal may consider a cell as an (exceptional) acceptable cell if at least one of the following conditions is satisfied: - If the base station allows the terminal operation (the operation of considering the cell as an (exceptional) acceptable cell) through system information (e.g., SIB1) (e.g., if the indicator barringExemptEmergencyCall is set to true) - If the terminal supports only 1 Rx branch (does not support 2 Rx branches) - If the base station sets the cellBarredRedCap1Rx indicator to "barred" through system information (e.g., SIB1) - If a cell selection condition is satisfied for the cell - If the terminal supports only half duplex FDD, the base station sets the halfDuplexRedCapAllowed indicator to "true" through system information (e.g., SIB1) - If the base station does not set the cellBarred indicator to "barred" through system information (e.g., MIB) - All of Table 8 If a condition (or one or more conditions) is satisfied - If a condition in Table 9 is not satisfied, as an example of an embodiment of the present disclosure, a 2 Rx branch RedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied.- If the base station allows the terminal operation (operation to regard the corresponding cell as an (exceptionally) acceptable cell) through system information (e.g., SIB1) (e.g., indicator barringExemptEmergencyCall is set to true) - If the terminal supports 2 Rx branches - If the base station sets the cellBarredRedCap2Rx indicator to "barred" through system information (e.g., SIB1) - If the cell selection condition is satisfied for the corresponding cell - If the terminal supports only half duplex FDD, and the base station indicates halfDuplexRedCapAllowed to "true" through system information (e.g., SIB1) - If the base station does not set the cellBarred indicator to "barred" through system information (e.g., MIB) - If all conditions (or one or more conditions) of Table 8 are satisfied - If the conditions of Table 9 are not satisfied In one embodiment of the present disclosure, a 1 Rx branch eRedCap terminal may select the corresponding cell if at least one of the following conditions is satisfied: (Exceptionally) can be considered as an acceptable cell.- If the base station allows the terminal operation (operation to regard the corresponding cell as an (exceptionally) acceptable cell) through system information (e.g., SIB1) (e.g., indicator barringExemptEmergencyCall is set to true) - If the terminal supports only 1 Rx branch (does not support 2 Rx branches) - If the base station sets the cellBarred-eRedCap1Rx (or cellBarredeRedCap1Rx) indicator to "barred" through system information (e.g., SIB1) - If the cell selection condition is satisfied for the corresponding cell - If the terminal supports only half duplex FDD, the base station sets the halfDuplexRedCapAllowed indicator to "true" through system information (e.g., SIB1) - If the base station does not set the cellBarred indicator to "barred" through system information (e.g., MIB) - If all conditions (or one or more conditions) of Table 8 are satisfied - If the conditions of Table 9 are not satisfied, the present disclosure As an example, a 2 Rx branch eRedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied.- If the base station allows the terminal operation (operation to regard the corresponding cell as an (exceptionally) acceptable cell) through system information (e.g., SIB1) (e.g., if the indicator barringExemptEmergencyCall is set to true) - If the terminal supports 2 Rx branches - If the base station sets the cellBarred-eRedCap2Rx (or cellBarredeRedCap2Rx) indicator to "barred" through system information (e.g., SIB1) - If a cell selection condition is satisfied for the corresponding cell - If the terminal supports only half duplex FDD, and the base station indicates halfDuplexRedCapAllowed to "true" through system information (e.g., SIB1) - If the base station does not set the cellBarred indicator to "barred" through system information (e.g., MIB) - If all conditions (or one or more conditions) of Table 8 are satisfied - If the conditions of Table 9 are not satisfied In one embodiment of the present disclosure, a 2 Rx XR terminal may be configured as follows: A cell can be considered (exceptionally) acceptable if at least one of the conditions is satisfied.- If the base station allows the above terminal operation (to consider the corresponding cell as an (exceptionally) acceptable cell) via system information (e.g. SIB1) (e.g. indicator barringExemptEmergencyCall is set to true) - If the terminal supports 2 Rx branches - If the base station sets the cellBarred2RxXR indicator to ("barred") via system information (e.g. SIB1) - If the cell selection condition is satisfied for the corresponding cell - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB) - If all conditions (or one or more conditions) of Table 8 are satisfied - If the conditions of Table 9 are not satisfied.

[0151]

[0152] In one embodiment of the present disclosure, terminal operation may be as shown in Table 12.

[0153] In one embodiment of the present disclosure, a 1 Rx branch RedCap terminal may consider a cell as an (exceptional) acceptable cell if at least one of the following conditions is satisfied: - If the base station has permitted the terminal operation (of considering the cell as an (exceptional) acceptable cell) through system information (e.g., SIB1) (e.g., indicator barringExemptEmergencyCall is set to true) - If the terminal supports only 1 Rx branch (does not support 2 Rx branches) - If the base station has set the cellBarredRedCap1Rx indicator to "barred" through system information (e.g., SIB1) - If a cell selection condition is satisfied for the cell - If the base station has set the halfDuplexRedCapAllowed indicator to "true" through system information (e.g., SIB1) only if the terminal supports only half duplex FDD - If the base station has not set the cellBarred indicator to "barred" through system information (e.g., MIB) - If the base station has not set the cellBarred indicator to "barred" through system information (e.g., MIB) - If the base station has not set the cellBarred indicator to "barred" through system information (e.g., MIB) Even if the information (e.g. SIB1) does not set the cellBarredRedCap1Rx indicator to "barred", in one embodiment of the present disclosure, if the terminal does not bar the cell (for other reasons), the 2 Rx branch RedCap terminal may (exceptionally) consider the cell as an acceptable cell if at least one of the following conditions is satisfied:- If the base station allows the terminal operation (operation to regard the corresponding cell as an (exceptionally) acceptable cell) through system information (e.g., SIB1) (e.g., indicator barringExemptEmergencyCall is set to true) - If the terminal supports 2 Rx branches - If the base station sets the cellBarredRedCap2Rx indicator to "barred" through system information (e.g., SIB1) - If a cell selection condition is satisfied for the corresponding cell - If the terminal indicates halfDuplexRedCapAllowed to "true" through system information (e.g., SIB1) only if it supports half duplex FDD - If the base station does not set the cellBarred indicator to "barred" through system information (e.g., MIB) - Even assuming that the base station does not set the cellBarredRedCap2Rx indicator to "barred" through system information (e.g., SIB1), if the terminal does not bar the corresponding cell (for other reasons), one embodiment of the present disclosure For example, a 1 Rx branch eRedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied:- If the base station allows the above UE operation (regarding the cell as an (exceptionally) acceptable cell) via system information (e.g. SIB1) (e.g. indicator barringExemptEmergencyCall is set to true) - If the UE supports only 1 Rx branch (does not support 2 Rx branches) - If the base station sets the cellBarred-eRedCap1Rx (or cellBarredeRedCap1Rx) indicator to "barred" via system information (e.g. SIB1) - If the cell selection condition is satisfied for the cell - If the base station sets the halfDuplexRedCapAllowed indicator to "true" via system information (e.g. SIB1) only if the UE supports only half duplex FDD - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB) - If the base station sets the cellBarred-eRedCap1Rx (or cellBarredeRedCap1Rx) indicator to "barred" via system information (e.g. SIB1) Even if the cellBarredeRedCap1Rx) indicator is not set to "barred", in one embodiment of the present disclosure, if the terminal does not bar the cell (for other reasons), the 2 Rx branch eRedCap terminal may (exceptionally) consider the cell as an acceptable cell if at least one of the following conditions is satisfied:- If the base station allows the above UE operation (to regard the cell as an (exceptionally) acceptable cell) via system information (e.g. SIB1) (e.g. indicator barringExemptEmergencyCall is set to true) - If the UE supports 2 Rx branches - If the base station sets the cellBarred-eRedCap2Rx (or cellBarredeRedCap2Rx) indicator to "barred" via system information (e.g. SIB1) - If the cell selection condition is satisfied for the cell - If the base station indicates halfDuplexRedCapAllowed to "true" via system information (e.g. SIB1) only if the UE supports only half duplex FDD - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB) - If the base station sets the cellBarred-eRedCap2Rx (or cellBarredeRedCap2Rx) indicator to "barred" via system information (e.g. SIB1) Even if it is not set to "barred", if the terminal does not bar the cell (for other reasons), as an example of an embodiment of the present disclosure, the 2 Rx XR terminal may (exceptionally) consider the cell as an acceptable cell if at least one of the following conditions is satisfied.- If the base station has permitted the above terminal operation (to regard the cell as an (exceptionally) acceptable cell) via system information (e.g. SIB1) (e.g. indicator barringExemptEmergencyCall is set to true) - If the terminal supports 2 Rx branches - If the base station has set the cellBarred2RxXR indicator to ("barred") via system information (e.g. SIB1) - If the cell selection condition is satisfied for the cell - If the base station has not set the cellBarred indicator to "barred" via system information (e.g. MIB) Even if it is assumed that the base station has not set the cellBarred2RxXR indicator to "barred" via system information (e.g. SIB1), if the terminal does not bar the cell (for other reasons).

[0154]

[0155] In one embodiment of the present disclosure, the RedCap terminal operation according to the embodiment in Table 12 may be as shown in Table 13.

[0156] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0157] In one embodiment of the present disclosure, the operation of an eRedCap or XR terminal according to the embodiment in Table 12 may be as in Table 14.

[0158] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0159] Issue 2: In one embodiment of the present disclosure, according to Tables 6 and 7 described above, even if a cell is barred, if certain conditions are met, the terminal may exceptionally consider the cell as an acceptable cell and use limited services. However, if a cell is barred (e.g., as in Tables 15 and 16), the terminal may exclude the cell from cell selection / reselection candidates for a certain period of time (e.g., 300 seconds).

[0160]

[0161]

[0162] As a result, the terminal may not meet the cell selection conditions for the cell for a given period of time. Consequently, the terminal may not (exceptionally) consider the cell as an acceptable cell.

[0163] In one embodiment of the present disclosure, to address the above issue and perform operations that a terminal exceptionally considers as an acceptable cell (e.g., Tables 6, 7, 11, 12, 13, 14), the terminal may not exclude a cell from cell selection and / or reselection candidates or may include the cell in the cell selection and / or reselection candidates, even if the cell is barred, if a predetermined condition is satisfied for the cell (e.g., Tables 6, 7, 11, 12, 13, 14). For example, the terminal may operate as in Table 17.

[0164]

[0165] As another example, the terminal may operate as shown in Table 18.

[0166] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0167] As an example of the present disclosure, to address the above issue and perform operations that the terminal exceptionally considers an acceptable cell (e.g., Tables 6, 7, 11, 12, 13, and 14), the terminal may not bar the cell and instead consider the cell as an acceptable cell only (not a suitable cell). For example, the terminal may operate as in Tables 19, 20, and 21 upon receiving SIB1.

[0168] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0169] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0170] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0171]

[0172] In one embodiment of the present disclosure, to address the above issue and perform operations that a terminal exceptionally considers an acceptable cell (e.g., Tables 6, 7, 11, 12, 13, and 14), the terminal may not bar the cell and instead consider the cell as an acceptable cell only (not a suitable cell). To this end, the terminal may consider the cell as an acceptable cell if it is a suitable cell. For example, the terminal may operate as in Tables 22, 23, and 24.

[0173] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0174] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0175] In one embodiment of the present disclosure, the phrases in parentheses may be included or omitted.

[0176] FIG. 3 is a diagram illustrating a method by which an inactive mode or standby mode terminal considers a cell as an acceptable cell according to one embodiment of the present disclosure.

[0177] In step 1c-05, the terminal may be in an inactive mode or a standby mode.

[0178] In step 1c-10, the terminal can receive system information (e.g., MIB, SIB1) from one cell.

[0179] In step 1c-15, the terminal may check barring for the corresponding cell based on the received system information and check the barring exemption condition according to the embodiment described above.

[0180] Specifically, in the above-described embodiment according to the present disclosure, even if a cell is barred according to the conditions set forth in Table 6 or Table 7, the terminal may exceptionally consider the cell as an acceptable cell and use limited services if the conditions are satisfied. The conditions set forth above are set according to the type of terminal.

[0181] More specifically, a 1Rx branch RedCap or 1Rx branch eRedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied.

[0182] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true)

[0183] - If the terminal supports only 1 Rx branch (not supporting 2 Rx branches)

[0184] - If the base station sets the cellBarredRedCap1Rx (or cellBarred-eRedCap1Rx) indicator to "barred" via system information (e.g. SIB1).

[0185] - If the cell selection condition is satisfied for the cell in question

[0186] - If the terminal supports only half duplex FDD, and the base station sets the halfDuplexRedCapAllowed indicator to "true" through system information (e.g. SIB1).

[0187] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0188] More specifically, a 2 Rx branch RedCap or 2Rx branch eRedCap terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied.

[0189] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true).

[0190] - If the terminal supports 2 Rx branches

[0191] - If the base station sets the cellBarredRedCap2Rx (or cellBarred-eRedCap2Rx) indicator to "barred" via system information (e.g. SIB1).

[0192] - If the cell selection condition is satisfied for the cell in question

[0193] - Only when the terminal supports only half duplex FDD, if the base station indicates halfDuplexRedCapAllowed as "true" through system information (e.g. SIB1).

[0194] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0195] More specifically, a 2 Rx XR terminal may (exceptionally) consider a cell as an acceptable cell if at least one of the following conditions is satisfied.

[0196] - If the base station allows the above terminal operation (the operation of considering the cell as an (exceptionally) acceptable cell) through system information (e.g. SIB1) (e.g. if the indicator barringExemptEmergencyCall is set to true).

[0197] - If the terminal supports 2 Rx branches

[0198] - If the base station sets the cellBarred2RxXR indicator to (“barred”) via system information (e.g. SIB1).

[0199] - If the cell selection condition is satisfied for the cell in question

[0200] - If the base station does not set the cellBarred indicator to "barred" via system information (e.g. MIB).

[0201] Specifically, in the above-described embodiment according to the present disclosure, even if the terminal bars the cell by a terminal type-specific barring indicator (e.g., cellBarredRedCap1Rx, cellBarredRedCap2Rx, cellBarred-eRedCap1Rx, cellBarred-eRedCap2Rx, cellBarred2RxXR), if the terminal's supported function or capability does not match the setting of the cell, the terminal may have to bar the cell because no service (e.g., including limited services) can be used accordingly.

[0202] For example, if an inactive or standby terminal does not satisfy at least one of the conditions in Table 8 when receiving SIB1, the terminal may bar the corresponding cell.

[0203] As another example, when an inactive or standby mode terminal receives SIB1, even if all of the above conditions (conditions 1 to 6) are satisfied, if condition 7 of Table 9 is satisfied, the terminal can bar the corresponding cell.

[0204] Accordingly, a cell may be considered (exceptionally) an acceptable cell if it satisfies the conditions for terminal operations according to Tables 6 and 7, as shown in Table 11, and satisfies all conditions (or one or more conditions) of Table 8 and / or does not satisfy the conditions of Table 9.

[0205] According to one embodiment of the present disclosure, the barring exemption condition may mean a predetermined condition for operation of the terminal according to Table 12.

[0206]

[0207] In step 1c-20, if the barring exemption condition is satisfied according to the above-described embodiment, the terminal may determine / consider the cell as an acceptable cell and may use limited services (e.g., emergency calls) in the cell.

[0208] In one embodiment of the present disclosure, when a terminal considers a cell as an acceptable cell, it may mean that the terminal determines / uses / treats the cell as an acceptable cell.

[0209] In one embodiment of the present disclosure, when a terminal considers a cell as a barred cell, it may mean that the terminal determines / uses / treats the cell as a barred cell.

[0210] In one embodiment of the present disclosure, when a terminal considers a cell as a suitable cell, it may mean that the terminal determines / uses / treats the cell as a suitable cell.

[0211]

[0212] FIG. 4 is a diagram illustrating the internal structure of a terminal according to an embodiment of the present disclosure.

[0213] Referring to FIG. 4, the terminal may include an RF (Radio Frequency) processing unit (1d-10), a baseband processing unit (1d-20), a storage unit (1d-30), and a control unit (1d-40).

[0214] The RF processing unit (1d-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. For example, the RF processing unit (1d-10) may up-convert a baseband signal provided from the baseband processing unit (1d-20) into an RF band signal and transmit the same through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1d-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In FIG. 4, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (1d-10) may include multiple RF chains. In addition, the RF processing unit (1d-10) may perform beamforming. For the above beamforming, the RF processing unit (1d-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO (multi-input multi-output) and can receive multiple layers when performing MIMO operation.

[0215] The baseband processing unit (1d-20) above can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1d-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1d-20) can restore a reception bit stream by demodulating and decoding a baseband signal provided from the RF processing unit (1d-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (1d-20) can generate complex symbols by encoding and modulating a transmission bit stream, and after mapping the complex symbols to subcarriers, can configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (1d-20) can divide the baseband signal provided from the RF processing unit (1d-10) into OFDM symbol units, restore signals mapped to subcarriers through FFT (fast Fourier transform) operation, and then restore the received bit string through demodulation and decoding.

[0216] The baseband processing unit (1d-20) and the RF processing unit (1d-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1d-20) and the RF processing unit (1d-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (1d-20) and the RF processing unit (1d-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (1d-20) and the RF processing unit (1d-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.

[0217] The storage unit (1d-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (1d-30) can store information related to a second access node that performs wireless communication using wireless access technology. In addition, the storage unit (1d-30) can provide the stored data upon request from the control unit (1d-40).

[0218] The above control unit (1d-40) can control the overall operations of the terminal. For example, the control unit (1d-40) can transmit and receive signals through the baseband processing unit (1d-20) and the RF processing unit (1d-10). In addition, the control unit (1d-40) can record and read data in the storage unit (1d-30). For this purpose, the control unit (1d-40) can include at least one processor. For example, the control unit (1d-40) can include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs, and can include a multi-connection processing unit (1d-42) as illustrated in the drawing.

[0219]

[0220] FIG. 5 is a diagram illustrating the structure of a base station according to an embodiment of the present disclosure.

[0221] Referring to FIG. 5, according to an example of the present disclosure, a base station may be configured to include an RF processing unit (1e-10), a baseband processing unit (1e-20), a backhaul communication unit (1e-30), a storage unit (1e-40), and a control unit (1e-50).

[0222] The RF processing unit (1e-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1e-10) may up-convert a baseband signal provided from the baseband processing unit (1e-20) into an RF band signal and transmit the same through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1e-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is illustrated, but the base station may have multiple antennas. In addition, the RF processing unit (1e-10) may include multiple RF chains. In addition, the RF processing unit (1e-10) may perform beamforming. For the above beamforming, the RF processing unit (1e-10) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.

[0223] The baseband processing unit (1e-20) above can perform a conversion function between a baseband signal and a bit stream according to the physical layer standard of the wireless access technology. For example, when transmitting data, the baseband processing unit (1e-20) can generate complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1e-20) can restore a reception bit stream by demodulating and decoding a baseband signal provided from the RF processing unit (1e-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (1e-20) can generate complex symbols by encoding and modulating a transmission bit stream, and after mapping the complex symbols to subcarriers, configure OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (1e-20) can divide the baseband signal provided from the RF processing unit (1e-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operation, and then restore the received bit string through demodulation and decoding. The baseband processing unit (1e-20) and the RF processing unit (1e-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1e-20) and the RF processing unit (1e-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0224] The above backhaul communication unit (1e-30) can provide an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (1e-30) can convert a bit string transmitted from the main base station to another node, such as an auxiliary base station or a core network, into a physical signal, and can convert a physical signal received from the other node into a bit string.

[0225] The storage unit (1e-40) can store data such as basic programs, application programs, and setting information for the operation of the main base station. In particular, the storage unit (1e-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (1e-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (1e-40) can provide stored data upon request from the control unit (1e-50).

[0226] The control unit (1e-50) can control the overall operations of the base station. For example, the control unit (1e-50) can transmit and receive signals through the baseband processing unit (1e-20) and the RF processing unit (1e-10) or through the backhaul communication unit (1e-30). In addition, the control unit (1e-50) can record and read data in the storage unit (1e-40). For this purpose, the control unit (1e-50) can include at least one processor and, as illustrated in the drawing, can include a multi-connection processing unit (1e-52).

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

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

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

[0230] Meanwhile, the order of description in the drawings explaining the method of the present disclosure does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0231] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.

[0232] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.

[0233] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

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

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

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

[0238] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined to operate a base station and a terminal. Furthermore, the embodiments of the present disclosure can be applied to other communication systems, and other modifications based on the technical idea of ​​the embodiments can also be implemented. For example, the embodiments can be applied to LTE systems, 5G, NR systems, or 6G systems. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the claims.

Claims

1. In a method performed by a UE (user equipment) in a wireless communication system, A step of receiving, from a base station, a system information block (SIB) including information about a cell indicating whether the cell is barred for a specific UE type, wherein the information about the cell is set to barred or not barred, and the UE supports the specific UE type; If the information about the cell is set to barred and the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, a step of checking whether the cell is considered barred for a reason other than the information about the cell being set to barred and whether a cell selection criterion is met; and A method of a UE, comprising: a step of considering the cell as an acceptable cell for initiating the emergency call, if the cell is not considered barred for the other reasons mentioned above and the cell selection criteria are met; 2. In paragraph 1, The above cells considered as acceptable cells are not considered as barred cells, and A method of a UE, characterized in that the specific UE type includes a RedCap (reduced capability) UE, an eRedCap (enhanced RedCap) UE, and a 2Rx XR (2 reception extended reality) UE.

3. In paragraph 1, The above other reasons include that the conditions and tracking area codes and tracking area list are not provided, The above conditions are: A first condition wherein the UE supports one or more frequency bands indicated by the base station and the one or more frequency bands are not downlink-only bands; A second condition wherein the UE is an integrated access backhaul mobile terminal (IAB-MT) or a wide area network control repeater MT (NCR-MT), or the UE supports additional spectrum emission; A third condition that the UE supports an uplink channel bandwidth having a first maximum transmission bandwidth setting associated with the uplink; A fourth condition wherein the UE supports a downlink channel bandwidth having a second maximum transmission bandwidth setting associated with the downlink; A fifth condition in which the UE supports frequency shift or the frequency shift is disabled; and A method of a UE, characterized in that it includes a sixth condition; wherein the UE is neither a RedCap (reduced capability) UE nor an eRedCap (enhanced RedCap) UE, or the UE is a RedCap / eRedCap UE in time division duplex (TDD), or the UE is the RedCap / eRedCap UE and the cell supports half-duplex FDD RedCap / eRedCap UE in frequency division duplex (FDD), or the UE is the RedCap / eRedCap UE and the RedCap / eRedCap UE supports full-duplex FDD operation.

4. In paragraph 3, A method of a UE, characterized in that the above other reason includes not satisfying at least one of the above conditions.

5. In a method performed by a base station in a wireless communication system, A step of generating information about the cell indicating whether the cell is barred for a specific UE (user equipment) type, wherein the information about the cell is set to barred or not barred; and A step of transmitting a SIB (system information block) including the information about the cell to the UE; The above UE supports the above specific UE type, and A method of a base station, characterized in that the information about the cell is set to barred, the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, and the cell is not considered barred for a reason other than that the information about the cell is set to barred, and a cell selection criterion is satisfied, the cell is considered an acceptable cell for initiating the emergency call.

6. In paragraph 5, The above cells considered as acceptable cells are not considered as barred cells, and A method of a base station, characterized in that the specific UE type includes a RedCap (reduced capability) UE, an eRedCap (enhanced RedCap) UE, and a 2Rx XR (2 reception extended reality) UE.

7. In paragraph 5, The above other reasons include that the conditions and tracking area codes and tracking area list are not provided, The above conditions are: A first condition wherein the UE supports one or more frequency bands indicated by the base station and the one or more frequency bands are not downlink-only bands; A second condition wherein the UE is an integrated access backhaul mobile terminal (IAB-MT) or a wide area network control repeater MT (NCR-MT), or the UE supports additional spectrum emission; A third condition that the UE supports an uplink channel bandwidth having a first maximum transmission bandwidth setting associated with the uplink; A fourth condition wherein the UE supports a downlink channel bandwidth having a second maximum transmission bandwidth setting associated with the downlink; A fifth condition in which the UE supports frequency shift or the frequency shift is disabled; and A method of a base station, characterized in that it includes a sixth condition; wherein the UE is neither a RedCap (reduced capability) UE nor an eRedCap (enhanced RedCap) UE, or the UE is a RedCap / eRedCap UE in time division duplex (TDD), or the UE is the RedCap / eRedCap UE and the cell supports half-duplex FDD RedCap / eRedCap UE in frequency division duplex (FDD), or the UE is the RedCap / eRedCap UE and the RedCap / eRedCap UE supports full-duplex FDD operation.

8. In paragraph 7, A method of a base station, characterized in that the above other reason includes not satisfying at least one of the above conditions.

9. In a wireless communication system, in the UE (user equipment), At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor and executable by the at least one processor, wherein the UE, Receive from a base station a system information block (SIB) containing information about a cell indicating whether the cell is barred for a specific UE type, wherein the information about the cell is set to barred or not barred, and the UE supports the specific UE type; If the information about the cell is set to barred and the SIB further includes information indicating that the cell allows emergency bearer service associated with an emergency call, it is checked whether the cell is considered barred for a reason other than the information about the cell being set to barred and whether cell selection criteria are met, and A UE comprising a memory storing a command to consider the cell as an acceptable cell for initiating the emergency call if the cell is not considered barred for the other reasons mentioned above and the cell selection criteria are met.

10. In paragraph 9, The above cells considered as acceptable cells are not considered as barred cells, and A UE characterized in that the specific UE type includes a RedCap (reduced capability) UE, an eRedCap (enhanced RedCap) UE, and a 2Rx XR (2 reception extended reality) UE.

11. In paragraph 9, The above other reasons include that the conditions and tracking area codes and tracking area list are not provided, The above conditions are: A first condition wherein the UE supports one or more frequency bands indicated by the base station and the one or more frequency bands are not downlink-only bands; A second condition wherein the UE is an integrated access backhaul mobile terminal (IAB-MT) or a wide area network control repeater MT (NCR-MT), or the UE supports additional spectrum emission; A third condition that the UE supports an uplink channel bandwidth having a first maximum transmission bandwidth setting associated with the uplink; A fourth condition wherein the UE supports a downlink channel bandwidth having a second maximum transmission bandwidth setting associated with the downlink; A fifth condition in which the UE supports frequency shift or the frequency shift is disabled; and A UE characterized in that it includes a sixth condition; wherein the UE is neither a RedCap (reduced capability) UE nor an eRedCap (enhanced RedCap) UE, or the UE is a RedCap / eRedCap UE in time division duplex (TDD), or the UE is the RedCap / eRedCap UE and the cell supports half-duplex FDD RedCap / eRedCap UE in frequency division duplex (FDD), or the UE is the RedCap / eRedCap UE and the RedCap / eRedCap UE supports full-duplex FDD operation.

12. In paragraph 11, A UE characterized in that the above other reason includes not satisfying at least one of the above conditions.

13. In a wireless communication system, at a base station, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor and executable by the at least one processor, the base station, Generate information about the cell indicating whether the cell is barred for a specific UE (user equipment) type, and wherein the information about the cell is set to barred or not barred, and A memory storing a command to transmit a SIB (system information block) including the above information about the cell to the UE, The above UE supports the above specific UE type, and A base station characterized in that the information about the cell is set to barred, the SIB further includes information indicating that the cell allows an emergency bearer service associated with an emergency call, and the cell is not considered barred for a reason other than that the information about the cell is set to barred, and if a cell selection criterion is satisfied, the cell is considered an acceptable cell for initiating the emergency call.

14. In paragraph 13, The above cells considered as acceptable cells are not considered as barred cells, and A base station, characterized in that the specific UE types include RedCap (reduced capability) UE, eRedCap (enhanced RedCap) UE, and 2Rx XR (2 reception extended reality) UE.

15. In paragraph 13, The above other reasons include that the conditions and tracking area codes and tracking area list are not provided, The above conditions are: A first condition wherein the UE supports one or more frequency bands indicated by the base station and the one or more frequency bands are not downlink-only bands; A second condition wherein the UE is an integrated access backhaul mobile terminal (IAB-MT) or a wide area network control repeater MT (NCR-MT), or the UE supports additional spectrum emission; A third condition that the UE supports an uplink channel bandwidth having a first maximum transmission bandwidth setting associated with the uplink; A fourth condition wherein the UE supports a downlink channel bandwidth having a second maximum transmission bandwidth setting associated with the downlink; A fifth condition in which the UE supports frequency shift or the frequency shift is disabled; and The sixth condition includes that the UE is neither a RedCap (reduced capability) UE nor an eRedCap (enhanced RedCap) UE, or the UE is a RedCap / eRedCap UE in time division duplex (TDD), or the UE is the RedCap / eRedCap UE and the cell supports half-duplex FDD RedCap / eRedCap UE in frequency division duplex (FDD), or the UE is the RedCap / eRedCap UE and the RedCap / eRedCap UE supports full-duplex FDD operation; and A base station, characterized in that the above other reason includes not satisfying at least one of the above conditions.

Images