Method and apparatus for transmitting and receiving data in a wireless communication system

Abstract

In a wireless communication system, a method performed by a user equipment (UE) includes transmitting, to a base station, UE capability information including an indicator indicating that the UE supports cell global identifier (CGI) information reporting, receiving, from the base station, measurement configuration information including an indicator indicating a cell for which CGI information is to be reported, obtaining a list of non-public network (NPN) identifier information of the indicated cell, and transmitting, to the base station, a measurement report message including the list of NPN identifier information.

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for transmitting and receiving data in a wireless communication system. Background Technology

[0002] To meet the increasing demand for wireless data services following the commercialization of fourth-generation (4G) communication systems, considerable efforts have been made to develop enhanced 5G communication systems. In this context, 5G communication systems are referred to as super-4G network communication systems or post-Long Term Evolution (LTE) systems. To achieve high data rates, 5G communication systems are being developed to operate in ultra-high frequency bands (millimeter wave), such as the 60 GHz band. To reduce radio wave propagation path loss and increase propagation distance in the millimeter wave band, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO are being discussed in 5G communication systems. To improve the system network for 5G communication systems, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access networks (Cloud-RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receive interference cancellation. In addition, advanced coding and modulation (ACM) technologies such as hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM) (FQAM), and sliding window superposition coding (SWSC) have been developed for 5G communication systems, as well as advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse coded multiple access (SCMA).

[0003] New Radio (NR), or new 5G communication, has been designed to allow for the free reuse of time and frequency resources for various services. This allows for the dynamic or flexible allocation of waveform / parameter sets, reference signals, etc., based on the necessity of the corresponding service. Optimized data transmission through channel quality and interference measurements is crucial for providing the best service to terminals in the communication, making channel state measurements mandatory. However, unlike 4G communication, where channel and interference characteristics do not change significantly with frequency resources, 5G channels exhibit significantly different channel and interference characteristics depending on the service. Therefore, it is necessary to support subsets of Frequency Resource Groups (FRGs) for service segmentation and measurement. In NR systems, the types of services supported can be categorized as Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low Latency Communication (URLLC). eMBB can be a service for high-speed transmission of large amounts of data, mMTC can be a service for minimizing terminal power and supporting multiple terminal connections, and URLLC can be a service for high reliability and low latency. Different requirements can be applied depending on the type of service applied to the terminal.

[0004] In this way, multiple services can be provided to users in a communication system, and a method and apparatus for providing multiple services to users based on characteristics are required. Summary of the Invention

[0005] Solution to the problem

[0006] In a wireless communication system according to an embodiment of the present disclosure, a method performed by a user equipment (UE) includes: sending UE capability information to a base station, the UE capability information including an indicator indicating that the UE supports Cell Global Identifier (CGI) information reporting; receiving measurement configuration information from the base station, the measurement configuration information including an indicator indicating a cell to which CGI information is to be reported; obtaining a list of non-public network (NPN) identifier information for the indicated cell; and sending a measurement report message including the NPN identifier information list to the base station.

[0007] In a wireless communication system according to embodiments of the present disclosure, a method performed by a base station includes: receiving UE capability information from a user equipment (UE), the UE capability information including an indicator indicating that the UE supports Cell Global Identifier (CGI) information reporting; sending measurement configuration information to the UE, the measurement configuration information including an indicator indicating a cell to which CGI information is to be reported; and receiving from the UE a measurement report message including a list of non-public network (NPN) identifier information of the indicated cell.

[0008] In a wireless communication system according to embodiments of the present disclosure, a user equipment (UE) includes a transceiver and at least one processor, the at least one processor being configured to: transmit UE capability information to a base station, the UE capability information including an indicator indicating that the UE supports Cell Global Identifier (CGI) information reporting; receive measurement configuration information from the base station, the measurement configuration information including an indicator indicating a cell to which CGI information is to be reported; obtain a list of non-public network (NPN) identifier information for the indicated cell; and transmit a measurement report message including the NPN identifier information list to the base station.

[0009] In a wireless communication system according to an embodiment of the present disclosure, a base station includes a transceiver and at least one processor, the at least one processor being configured to: receive UE capability information from a user equipment (UE), the UE capability information including an indicator indicating that the UE supports Cell Global Identifier (CGI) information reporting; send measurement configuration information to the UE, the measurement configuration information including an indicator indicating a cell to which CGI information is to be reported; and receive from the UE a measurement report message including a list of non-public network (NPN) identifier information of the indicated cell. Attached Figure Description

[0010] Figure 1a This is a diagram of the architecture of a Long Term Evolution (LTE) system, which is cited to describe this disclosure.

[0011] Figure 1b This is a diagram of the radio protocol architecture in an LTE system, which is referenced to describe this disclosure.

[0012] Figure 1c This is a diagram of the architecture of a next-generation mobile communication system that applies this disclosure.

[0013] Figure 1d This is a diagram of a radio protocol architecture for a next-generation mobile communication system to which this disclosure can be applied.

[0014] Figure 1e This is a diagram illustrating the process by which a user equipment (UE) establishes an RRC connection with a base station via conventional access in a next-generation mobile communication system, performed by a user equipment (UE) in Radio Resource Control (RRC) Inactive Mode (RRC_INACTIVE) or RRC Idle Mode (RRC_IDLE) according to embodiments of this disclosure.

[0015] Figure 1f This is a diagram illustrating the process by which a UE establishes an RRC connection in a next-generation mobile communication system via a Closed Access Group (CAG) cell in a Public Network Integrated Non-Public Network (PNI-NPN) in RRC Inactive Mode (RRC_INACTIVE) or RRC Idle Mode (RRC_IDLE), according to embodiments of this disclosure.

[0016] Figure 1g This is a diagram illustrating the process by which a UE establishes an RRC connection in a next-generation mobile communication system by accessing an SNPN cell in a standalone non-public network (SNPN) in either RRC inactive mode (RRC_INACTIVE) or RRC idle mode (RRC_IDLE), according to embodiments of this disclosure.

[0017] Figure 1h This is a diagram illustrating UE operation when a UE accesses an NPN cell according to an embodiment of the present disclosure.

[0018] Figure 1i is a diagram illustrating the process by which a UE sends a measurement report message for automatic neighbor relationships to a base station in a next-generation mobile communication system, performed by the UE in RRC connected mode (RRC_CONNECTED) according to an embodiment of the present disclosure.

[0019] Figure 1j This is a diagram illustrating the process by which a UE sends a measurement report message for automatic neighbor relationships to a base station in a next-generation mobile communication system, performed by the UE in RRC connected mode (RRC_CONNECTED) according to embodiments of the present disclosure.

[0020] Figure 1k This is a flowchart of a process for collecting and reporting cell measurement information in a next-generation mobile communication system according to embodiments of the present disclosure.

[0021] Figure 11 This is a block diagram of the configuration of a terminal according to an embodiment of the present disclosure.

[0022] Figure 1m This is a block diagram of the configuration of a base station according to an embodiment of the present disclosure.

[0023] Figure 1n This is a block diagram of the configuration of a terminal according to an embodiment of the present disclosure.

[0024] Figure 1o This is a block diagram of the configuration of a base station according to an embodiment of the present disclosure. Detailed Implementation

[0025] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In describing the present disclosure, detailed descriptions of relevant functions or configurations may be omitted where it is deemed that such descriptions might unnecessarily obscure the essence of the disclosure. Furthermore, the terminology used below is defined in consideration of the functions in the present disclosure and may have different meanings depending on the intent, conventions, etc., of the user or operator. Therefore, the terminology used herein must be defined based on its meaning and the description throughout the specification.

[0026] The main features of this disclosure can be applied to other systems with similar technical backgrounds, with minor variations without departing from the scope of this disclosure, and such applicability can be determined by those skilled in the art or of ordinary skill. For reference, "communication system" is a term that generally includes the meaning of "broadcast system," but in this disclosure, when broadcast service is the primary service in a communication system, the communication system may be further clearly referred to as a broadcast system.

[0027] The advantages and features of this disclosure, as well as the methods for implementing these advantages and features, can be more readily understood by referring to the following detailed description and accompanying drawings of the embodiments. In this regard, embodiments of this disclosure may take different forms and should not be construed as limited to the description herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of this disclosure to those skilled in the art, and this disclosure will be defined only by the appended claims. Throughout the complete specification, the same reference numerals denote the same elements.

[0028] In the various embodiments of this disclosure described below, hardware methods are presented as examples. However, because the various embodiments of this disclosure include techniques using both hardware and software, software-based methods are not excluded.

[0029] The following disclosure relates to apparatus and methods for transmitting and receiving control information in a communication system. Specifically, this disclosure describes a technique for transmitting and receiving control information in a wireless communication system based on a Channel Quality Indicator (CQI) and Modulation and Coding Scheme (MCS) table.

[0030] In the following description, for ease of description, terms indicating signals, terms indicating channels, terms indicating control information, terms indicating network entities, terms indicating device components, etc., are exemplified. Therefore, the terminology used in this disclosure is not limited, and other terms with the same technical meaning may be used.

[0031] Furthermore, various embodiments of this disclosure are described using terminology used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP)), but these embodiments are merely examples for illustrative purposes. The various embodiments of this disclosure can be readily modified and applied to other communication systems.

[0032] Figure 1a This is a diagram of the architecture of a Long Term Evolution (LTE) system, which is cited to describe this disclosure.

[0033] Reference Figure 1aThe radio access network of the LTE system includes next-generation base stations (eNBs, Node Bs, or base stations) 1a-05, 1a-10, 1a-15, and 1a-20, a Mobility Management Entity (MME) 1a-25, and a Service Gateway (S-GW) 1a-30. User Equipment (UE) (or terminal) 1a-35 accesses external networks through eNB 1a-05 to 1a-20 and S-GW 1a-30.

[0034] exist Figure 1a In this context, eNBs 1a-05 to 1a-20 correspond to existing Node Bs in the Universal Mobile Telecommunications System (UMTS). eNBs 1a-05, 1a-10, 1a-15, or 1a-20 connect to UE 1a-35 via radio channels and perform more complex functions compared to existing Node Bs. In LTE systems, all user services, including real-time services such as Voice over Internet Protocol (VoIP), are served via shared channels, thus requiring entities to verify UE buffer status information, available transmission power status information, channel status information, etc., and to perform scheduling; these operations can be performed by eNBs 1a-05 to 1a-20. One eNB typically controls multiple cells. For example, an LTE system can achieve a data rate of 100 Mbps using radio access technologies such as Orthogonal Frequency Division Multiplexing (OFDM) with a 20 MHz bandwidth. Furthermore, an Adaptive Modulation and Coding (AMC) scheme is applied based on the channel state of UE 1a-35 to determine the modulation scheme and channel coding rate. S-GW 1a-30 is the entity used to provide data bearers and can generate or remove data bearers according to the control of MME1a-25. MME1a-25 is the entity that performs mobility management functions on UE 1a-35 and various control functions, and can be connected to multiple base stations (eNB 1a-05 to 1a-20).

[0035] Figure 1b This is a diagram of the radio protocol architecture in an LTE system, which is referenced to describe this disclosure.

[0036] Reference Figure 1b The radio protocol architecture of an LTE system may include Packet Data Convergence Protocol (PDCP) layers 1b-05 and 1b-40 for UE and eNB respectively, Radio Link Control (RLC) layers 1b-10 and 1b-35, and Media Access Control (MAC) layers 1b-15 and 1b-30. PDCP layers 1b-05 and 1b-40 can perform operations such as Internet Protocol (IP) header compression / reconstruction. The main functions of PDCP layers 1b-05 or 1b-40 are summarized below.

[0037] - Header compression and decompression: Robust header compression only (ROHC)

[0038] -Transmit user data

[0039] - Sequential delivery function in the PDCP reconstruction process for RLC Acknowledgment Mode (AM) (Sequential delivery of upper-layer protocol data units (PDUs))

[0040] - For split bearers in dual connectivity (DC) (RLC AM only): PDCPPDU routing for transmission and PDCPPDU reordering for reception)

[0041] - Duplicate detection of lower-level service data units (SDUs) during PDCP reconstruction for RLC AM

[0042] - Retransmission of PDCP SDUs during handover, and retransmission of PDCPPDUs during PDCP data recovery for separated bearers in the DC, for use in RLC AM.

[0043] - Encryption and decryption

[0044] - Timer-based SDU dropping in the uplink

[0045] RLC layer 1b-10 or 1b-35 performs Automatic Repeat Request (ARQ) operations by reconfiguring the PDCPPDU to the appropriate size. The main functions of RLC layer 1b-10 or 1b-35 are summarized below.

[0046] -Transmission of upper-layer PDUs

[0047] - Error correction via ARQ (for AM data transmission only)

[0048] - Cascading, segmentation, and reassembly of RLC SDUs (for Unacknowledged Mode (UM) and AM data transfer only)

[0049] - Resegmentation of RLC data PDUs (for AM data transmission only)

[0050] - Reordering of RLC data PDUs (for UM and AM data transfer only)

[0051] - Duplicate detection (only for UM and AM data transmission)

[0052] - Protocol error detection (for AM data transmission only)

[0053] -RLC SDU discard (only for UM and AM data transfer)

[0054] -RLC Reconstruction

[0055] MAC layer 1b-15 or 1b-30 can connect to multiple RLC layers configured for a UE, and can multiplex RLCPDUs into MACPDUs and demultiplex RLCPDUs from MACPDUs. The main functions of MAC layer 1b-15 or 1b-30 are summarized below.

[0056] Mapping between logical channels and transport channels

[0057] - Multiplexing MAC SDUs belonging to one or different logical channels into a transport block (TB) delivered to the physical layer on the transport channel / Demultiplexing MAC SDUs belonging to one or different logical channels from a transport block (TB) delivered to the physical layer on the transport channel.

[0058] - Scheduling Information Report

[0059] - Error correction via Hybrid Automatic Repeat Request (HARQ)

[0060] Priority processing between logical channels of a UE

[0061] - Prioritization among UEs is performed through dynamic scheduling.

[0062] -Multimedia Broadcast Multicast Service (MBMS) identifier

[0063] -Transmission format selection

[0064] -filling

[0065] PHY layer 1b-20 or 1b-25 can channel-code higher-layer data and modulate it into OFDM symbols, transmitting the OFDM symbols via radio channels. Alternatively, it can demodulate and channel-decode OFDM symbols received via radio channels and pass the OFDM symbols to higher layers. PHY layer 1b-20 or 1b-25 also uses HARQ for additional error correction, and the receiver sends information about the reception of packets sent from the transmitter in one bit. This is called HARQ acknowledgment (ACK) / non-acknowledgment (NACK) information. Downlink HARQ ACK / NACK information about uplink transmissions can be sent via the Physical HARQ Indicator Channel (PHICH), and uplink HARQ ACK / NACK information about downlink transmissions can be sent via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0066] PHY layers 1b-20 and 1b-25 may include one or more frequencies / carriers. The technique for simultaneously configuring and using multiple frequencies is called carrier aggregation (CA). According to CA, by using a primary carrier and one or more subcarriers instead of a single carrier for communication between a terminal (or UE) and a base station (E-UTRAN Node B or eNB), the transmission capacity can be significantly increased by the number of subcarriers. In LTE systems, a cell in an eNB using the primary carrier is called a primary cell (Pcell), and a cell in an eNB using subcarriers is called a secondary cell (Scell).

[0067] Although not shown, the RRC layer exists in each of the higher layers of the PDCP layers 1b-05 and 1b-40 of the UE and eNB, and can exchange access and measurement-related configuration control messages for RRC.

[0068] Figure 1c This is a diagram of the architecture of a next-generation mobile communication system that applies this disclosure.

[0069] refer to Figure 1c As shown in the figure, the radio access network of a next-generation mobile communication system may include NR Node B (NB) 1c-10 and NR Core Network (CN) or Next Generation (NG) CN 1c-05. New Radio User Equipment (NR UE) or Terminal 1c-15 can access external networks via NR NB 1c-10 and NRCN 1c-05.

[0070] exist Figure 1cIn this context, the NR NB 1c-10 corresponds to the eNB in ​​existing LTE systems. The NR NB 1c-10 connects to the NR UE 1c-15 via a radio channel and offers superior service compared to existing NBs. Because all user service data in next-generation mobile communication systems are served through a shared channel, entities are needed to verify UE buffer status information, available transmission power status information, channel status information, etc., and to perform scheduling; this operation can be performed by the NR NB 1c-10. One NR NB 1c-10 can typically control multiple cells. Compared to existing LTE, it can provide the maximum bandwidth or more to achieve high-speed data transmission, and OFDM can be used as a radio access technology for additional beamforming. Furthermore, an adaptive modulation and coding (AMC) scheme is applied based on the UE's channel state to determine the modulation scheme and channel coding rate. The NRcN 1c-15 performs functions including mobility support, bearer configuration, and quality of service (QoS) configuration. The NRcN 1c-05 is an entity used to perform mobility management functions and various control functions for the UE, and can connect to multiple base stations. Next-generation mobile communication systems can cooperate with existing LTE systems, and the NRcN 1c-05 connects to the MME1c-25 via a network interface. The MME1c-25 connects to the eNB 1c-30, which acts as an existing base station.

[0071] Figure 1d This is a diagram of a radio protocol architecture for a next-generation mobile communication system to which this disclosure can be applied.

[0072] refer to Figure 1d The radio protocol architecture of next-generation mobile communication systems may include NR Service Data Adaptation Protocol (SDAP) layers 1d-01 and 1d-45, NR PDCP layers 1d-05 and 1d-40, NRrLC layers 1d-10 and 1d-35, and NR MAC layers 1d-15 and 1d-30 for UE and NR base stations, respectively. The main functions of NR SDAP layer 1d-01 or 1d-45 may include some of the following functions.

[0073] -Transmission of user plane data

[0074] - Mapping between QoS flows and data radio bearers (DRBs) for both downlink (DL) and uplink (UL).

[0075] - Mark QoS flow IDs in DL and UL groups

[0076] - Reflective QoS flow for DRB mapping of UL SDAPPDU

[0077] Regarding SDAP layer 1d-01 or 1d-45, the UE can be configured via RRC messages to use either the header or functionality of SDAP layer 1d-01 or 1d-45 for each PDCP layer 1d-05 or 1d-40, for each bearer, or for each logical channel. When the SDAP header is configured, the 1-bit indicator for Non-Access Stratum (NAS) reflected QoS configuration and the 1-bit indicator for Access Stratum (AS) reflected QoS configuration can instruct the UE to update or reconfigure the mapping information between QoS flows and data bearers for UL and DL. The SDAP header may include a QoS flow ID indicating QoS. QoS information can be used as data processing priority information, scheduling information, etc., to support seamless service.

[0078] The main functions of NRPDCP layer 1d-05 or 1d-40 may include some of the following functions.

[0079] -Header compression and decompression: ROHC only

[0080] -Transmit user data

[0081] - Sequential delivery of upper-layer PDUs

[0082] -Disordered delivery of upper-layer PDUs

[0083] - Reordering of received PDCPPDUs

[0084] -Duplicate detection of lower-level SDUs

[0085] -PDCP SDU retransmission

[0086] - Encryption and decryption

[0087] - Timer-based SDU dropping in the uplink

[0088] Reordering in NRPDCP layer 1d-05 or 1d-40 can represent the function of reordering PDCPPDUs received from lower layers based on the PDCP sequence number (SN), and can include the function of transmitting data to higher layers in the reordered order. Alternatively, reordering can include the function of transmitting data immediately regardless of order, the function of recording lost PDCPPDUs by reordering, the function of reporting the status of lost PDCPPDUs to the transmitter, and the function of requesting retransmission of lost PDCPPDUs.

[0089] The main functions of NRrLC layers 1d-10 or 1d-35 may include some of the following functions.

[0090] -Transmission of upper-layer PDUs

[0091] - Sequential delivery of upper-layer PDUs

[0092] -Disordered delivery of upper-layer PDUs

[0093] -Error correction via ARQ

[0094] Cascading, segmentation, and reassembly of RLC SDUs

[0095] - Resegmentation of RLC data PDUs

[0096] - Reordering of RLC data PDUs

[0097] -Duplicate detection

[0098] -Protocol error detection

[0099] -RLC SDU discard

[0100] -RLC Reconstruction

[0101] In NRrLC layer 1d-10 or 1d-35, sequential delivery can represent the function of sequentially delivering RLC SDUs received from lower layers to higher layers. Sequential delivery can include: reassembling RLC SDU segments from RLC SDUs and transmitting RLC SDUs when segments are received; reordering received RLCPDUs based on the RLC SN or PDCP SN; recording lost RLCPDUs by reordering them; reporting the status of lost RLCPDUs to the transmitter; and requesting retransmission of lost RLCPDUs. Sequential delivery can include the following functions: when a lost RLC SDU exists, only RLC SDUs preceding the lost RLC SDU are sequentially delivered to higher layers; even when a lost RLC SDU exists, when a timer expires, all RLC SDUs received before the timer starts are sequentially delivered to higher layers; or when a timer expires, all currently received RLC SDUs are sequentially delivered to higher layers regardless of the lost RLC SDU. Furthermore, RLCPDUs can be processed in the order of receipt (arrival order regardless of sequence number) and passed out of order to PDCP layers 1d-05 or 1d-40 (out-of-order delivery). Segments to be received or stored in the buffer can be reassembled into complete RLCPDUs, processed, and passed to PDCP layers 1d-05 or 1d-40. NRrLC layers 1d-10 or 1d-35 may not have cascading functionality, and this cascading functionality can be performed by NR MAC layers 1d-15 or 1d-30, or it can be replaced by the multiplexing functionality of NR MAC layers 1d-15 or 1d-30.

[0102] The out-of-order delivery of NRrLC layer 1d-10 or 1d-35 indicates the function of immediately delivering RLC SDUs received from lower layers to higher layers regardless of order, and may include the function of reassembling and delivering segmented and received RLC SDUs when an RLC SDU is segmented into several RLC SDUs, and the function of recording lost RLCPDUs by storing the RLC SN or PDCP SN and reordering the received RLCPDUs.

[0103] NR MAC layer 1d-15 or 1d-30 can be connected to multiple NRrLC layers 1d-10 or 1d-35 configured for a single UE, and the main functions of NR MAC layer 1d-15 or 1d-30 may include some of the following functions.

[0104] Mapping between logical channels and transport channels

[0105] - MAC SDU multiplexing / demultiplexing

[0106] - Scheduling Information Report

[0107] - Error correction via HARQ

[0108] Priority processing between logical channels of a UE

[0109] - Prioritization among UEs is performed through dynamic scheduling.

[0110] -MBMS identifier

[0111] -Transmission format selection

[0112] -filling

[0113] The NRPHY layer 1d-20 or 1d-25 can perform channel coding on higher-layer data, modulate it into OFDM symbols, and transmit the OFDM symbols via radio channels, or demodulate and channel decode OFDM symbols received via radio channels and pass the OFDM symbols to higher layers.

[0114] Figure 1e This is a diagram illustrating, according to embodiments of the present disclosure, the process by which a UE establishes an RRC connection with a base station via conventional access in a next-generation mobile communication system, performed by the UE in Radio Resource Control (RRC) Inactive Mode (RRC_INACTIVE) or RRC Idle Mode (RRC_IDLE).

[0115] According to embodiments of this disclosure, normal access can mean that the UE establishes an RRC connection with a base station via a public network to receive normal services (for public use on a suitable cell). Specifically, the UE can determine that normal access to a suitable cell is possible when the following conditions for accessing a suitable cell are met.

[0116] Condition 1: The cell is part of the selected Public Land Mobile Network (PLMN), a registered PLMN, or an equivalent PLMN list.

[0117] Condition 2: The community meets the community selection criteria.

[0118] The criteria for selecting a residential community can be expressed as Equation 1 below.

[0119] Equation 1

[0120] Srxlev>0 and Squal>0

[0121] in:

[0122] Srxlev=Qrxlevmeas-(Qrxlevmin+Qrxlevminoffset)-Pcompensation-Qoffsettemp

[0123] Squal=Qqualmeas-(Qqualmin+Qqualminoffset)-Qoffsettemp

[0124] For the definition of the parameters used in Equation 1, refer to the 3GPP standard specification "38.304: User Equipment (UE) Procedures in Idle Mode". These parameters may be included in system information broadcast by the cell (e.g., SIB1 or SIB2). In the following, the contents of the 3GPP standard specification can be applied in the same way to embodiments of this disclosure that apply Equation 1.

[0125] Condition 3: The cell is not prohibited based on the information recently provided from the Non-Access Stratum (NAS) layer, and the cell is part of at least one tracking area (TA) that is not part of the "prohibited tracking area" list of the PLMN that satisfies Condition 1 above.

[0126] The cell is disabled when, for example, the “cellBarred” indicator is set to “barred” in at least the MIB, the “cellReservedForOperatorUse” indicator is set to “reserved” in SIB1, or “cellReservedForOtherUse” is set to “true”.

[0127] refer to Figure 1e During operation 1e-05, UE 1e-01 can establish an RRC connection with base station (e.g., gNB) 1e-02 and is therefore in RRC connection mode (RRC_CONNECTED).

[0128] When no data is sent or received for any reason or at any time, base station 1e-02 can send an RRC connection release message (RRCRelease) to UE 1e-01 (operation 1e-10). When the RRC connection release message includes suspend configuration information (suspendConfig), UE 1e-01 can switch to RRC inactive mode, and when it does not include suspend configuration information, UE 1e-01 can switch to RRC idle mode (operation 1e-15).

[0129] UE 1e-01 that has switched to RRC idle mode or RRC inactive mode can select a PLMN (1e-16). The AS layer of UE 1e-01 can report at least one available PLMN to the NAS layer either upon request from the NAS layer or autonomously (in the UE, the AS should report available PLMNs to the NAS layer either upon request from the NAS layer or automatically). During the PLMN selection process, a specific PLMN can be selected automatically or manually based on a priority list of PLMN identifiers. Each PLMN in the PLMN identifier list can be identified by a "PLMN identifier".

[0130] In the System Information (SIB1) signaled via the broadcast channel, UE 1e-01 can receive at least one PLMN identifier in a given cell (in the System Information regarding the broadcast channel, the UE can receive one or more "PLMN identifiers" in a given cell). The result of the PLMN selection process performed by the NAS layer is the identifier of the selected PLMN (the result of the PLMN selection performed by the NAS is the identifier of the selected PLMN). The NAS layer can provide an equivalent PLMN list to the AS layer through the PLMN selection process. The equivalent PLMN list refers to the list of PLMNs selected by UE 1e-01 for cell selection, cell reselection, and handover based on the information provided by the NAS, as well as the list of PLMNs considered equivalent by the UE for cell selection, cell reselection, and handover. The PLMN selection process can be performed before Operation 1e-16. For example, when UE 1e-01, which has already switched to RRC connection mode in Operation 1e-05, performs the location registration process, UE 1e-01 can maintain the registered PLMNs. Alternatively, UE1e-01 can maintain a list of selected PLMNs and equivalent PLMNs by selecting a PLMN before switching to RRC connection mode (before operation 1e-05).

[0131] When a PLMN is selected, UE 1e-01 can receive or acquire system information (operation 1e-20) and perform a cell selection procedure (operation 1e-25). That is, UE 1e-01 can receive / acquire at least one MIB and SIB1, and perform a cell selection procedure to camp on a suitable cell of the corresponding PLMN. The corresponding PLMN can refer to the PLMN corresponding to condition 1 above. Specifically, the PLMN corresponding to condition 1 can be determined by the cell access-related information element (CellAccessRelatedInfo information element) broadcast in SIB1.

[0132] The CellAccessRelatedInfo element may include a PLMN IdentityList element. The PLMN IdentityList element can be configured in the following ways.

[0133] The plmn-IdentityList can include a list of PLMN identifier information (plmn-IdentityInfoList).

[0134] -plmn-IdentityInfoList can be configured with one or more PLMN-IdentityInfos.

[0135] - Each PLMN-IdentityInfo can be configured with a plmn-IdentityList, which includes a logical cell identifier and one or more PLMN-Identities mapped to it.

[0136] - The PLMN identifier included in the PLMN identifier list information element can be configured as follows.

[0137]

[0138] For example, in Table 1 below, PLMN-IdentityInfoList includes PLMN-IdentityInfo 1 and PLMN-IdentityInfo 2. When PLMN-IdentityInfo 1 / PLMN-IdentityInfo 2 includes two PLMN-Identities, the PLMN index of the first PLMN-Identity included in PLMN-IdentityInfo 1 can be "1", and the PLMN index of the second PLMN-Identity can be "2". Furthermore, the PLMN index of the first PLMN-Identity included in PLMN-Identity Info 2 can be "3", and the PLMN index of the second PLMN-Identity can be "4".

[0139] [Table 1]

[0140]

[0141]

[0142]

[0143] A UE 1e-01 already camped on an appropriate cell can perform a cell reselection process (operation 1e-30). That is, a UE 1e-01 can reselect a cell based on SIB2, SIB3, SIB4, SIB5, SIB6, etc., which include cell reselection parameters.

[0144] In Operation 1e-35, UE 1e-01 can initiate an RRC connection for some reason, or send data to and receive data from base station 1e-02. Specifically, in Operation 1e-35, when UE 1e-01 is in RRC idle mode, UE 1e-01 can perform the RRC connection establishment process with base station 1e-02. UE 1e-01 in RRC idle mode can establish reverse synchronization with base station 1e-02 and send an RRC connection establishment request message (RRCSetupRequest message) to base station 1e-02 (Operation 1e-40). The RRC connection establishment request message can include the UE 1e-01's identifier (ue-Identity) and the reason for RRC connection establishment (establishment reason). Upon successfully receiving the RRC connection establishment request message, base station 1e-02 can send an RRC connection setup message (RRCSetup message) to UE 1e-01 (Operation 1e-45). RRC connection setup messages may include radio resource configuration information (radioBearerConfig) and primary cell group configuration information (primary cell group).

[0145] Upon successfully receiving the RRC connection setup message, UE 1e-01 can apply the configuration information included in the RRC connection setup message and switch to RRC connection mode (Operation 1e-50). The current cell can be considered the primary cell (PCell). UE 1e-01, which has already switched to RRC connection mode, can send an RRC connection setup complete message (RRCSetupComplete message) to base station 1e-02 by including the following content in the RRC connection setup complete message (Operation 1e-55).

[0146] - One of the PLMNs included in the plmn-IdentityList broadcast in SIB1 can be set as the PLMN selected by a higher layer (selectedPLMN-Identity) (selectedPLMN-Identity is set as the PLMN selected by a higher layer from the PLMNs included in the plmn-IdentityList in SIB1). For example, as described above, selectedPLMN-Identity can refer to the first PLMN identifier in the PLMN identifier list that maps to the cell identifier in the first PLMN identifier information (PLMN-IdentityInfo) in the PLMN identifier information list (PLMN-IdentityInfoList).

[0147] In Operation 1e-35, when UE 1e-01 is in RRC inactive mode, UE 1e-01 can perform an RRC connection restoration procedure with base station 1e-02. UE 1e-01 in RRC inactive mode can establish reverse synchronization with base station 1e-02 and send an RRC connection restoration request message (RRCResumeRequest or RRCesumeRequest1 message) to base station 1e-02 (Operation 1e-40). The RRC connection restoration request message may include UE 1e-01's identifier (resumeIdentity), a restoration message authentication code for integrity (hereinafter referred to as resumeMAC-1), and a restoration reason (resumeCause), etc. Upon successfully receiving the RRC connection restoration request message, base station 1e-02 can send an RRC connection restoration message (RRCResume message) to UE 1e-01 (Operation 1e-45). RRC connection recovery messages may include at least one of the following: radio resource configuration information (radiobearerConfig), master cell group configuration information (masterCellGroup), measurement configuration information (measConfig), an indicator indicating full configuration (fullConfig), second radio resource configuration information (radiobearerConfig2), or sk-Counter value.

[0148] Upon successfully receiving the RRC connection restoration message, UE 1e-01 can apply the configuration information included in the RRC connection restoration message and switch to RRC connection mode (operation 1e-50). UE 1e-01 can treat the current cell as PCell. UE 1e-01, having switched to RRC connection mode, can send an RRC connection restoration complete message (RRCResumeComplete message) to base station 1e-02 (operation 1e-55). When a higher layer has provided a PLMN, the selected PLMN (selectedPLMN-Identity) identifier can be set to the PLMN selected by the higher layer from one or more PLMNs included in the PLMN identifier list broadcast in SIB1 (setting the selected PLMN identifier to the PLMN selected by the higher layer from the PLMN identifier list included in SIB1). As described above, according to this embodiment, UE 1e-01 does not include the value of the selected PLMN identifier itself in the RRC connection restoration complete message, but can include the index value of the selected PLMN in the RRC connection restoration complete message.

[0149] Figure 1fThis is a diagram illustrating the process by which a UE establishes an RRC connection in a next-generation mobile communication system via a Closed Access Group (CAG) cell in a Public Network Integrated Non-Public Network (PNI-NPN) in RRC Inactive Mode (RRC_INACTIVE) or RRC Idle Mode (RRC_IDLE), according to embodiments of this disclosure.

[0150] According to embodiments of this disclosure, a PNI-NPN can represent an NPN deployed via a PLMN (a PNI-NPN is an NPN available via a PLMN). Therefore, in the case of an NPN formed via a PLMN, the UE has a subscription to the corresponding PLMN (when the NPN is available via a PLMN, the UE has a subscription to the PLMN). Specifically, a CAG can identify a group of subscribers permitted to access one or more CAG cells associated with that CAG. (A CAG identifies a group of subscribers permitted to access one or more CAG cells associated with that CAG). In other words, a CAG can prevent UEs without access rights to CAG cells from accessing the PNI-NPN (a CAG is used in the PNI-NPN to prevent UEs not permitted to access the NPN via associated cells from automatically selecting and accessing associated cells). A UE not in a Standalone Non-Public Network (SNPN) can be considered a suitable cell when the following conditions are met.

[0151] Condition 1-1: The cell is part of the selected PLMN, the registered PLMN, or a list of equivalent PLMNs, and the CAG-ID broadcast by the cell for the corresponding PLMN is included in the UE's allowed CAG list (e.g., the list of CAG identifiers the UE is allowed to access). The cell is part of the selected PLMN or a list of registered PLMNs or equivalent PLMNs. And for that PLMN, the list of allowed CAGs in the UE for that PLMN includes the CAG-ID broadcast by the cell for that PLMN.

[0152] Conditions 1-2: The cell is part of the selected PLMN, the registered PLMN, or the PLMN in the equivalent PLMN list, and only the CAG indication is not broadcast or false, and the CAG-ID is not broadcast (the cell is part of the selected PLMN, the registered PLMN, or the PLMN in the UE's equivalent PLMN list; for the UE, the PLMN-ID is broadcast by the cell without an associated CAG-ID, and for the UE, only the CAG indication is absent or false).

[0153] Condition 2: The community meets the community selection criteria.

[0154] The criteria for selecting a residential community can be expressed as Equation 1 below.

[0155] Equation 1

[0156] Srxlev>0 and Squal>0

[0157] in:

[0158] Srxlev=Qrxlevmeas-(Qrxlevmin+Qrxlevminoffset)-Pcompensation-Qoffsettemp

[0159] Squal=Qqualmeas-(Qqualmin+Qqualminoffset)-Qoffsettemp

[0160] For the definition of the parameters used in Equation 1, refer to the 3GPP standard specification "38.304: User Equipment (UE) Procedures in Idle Mode". These parameters may be included in system information broadcast by the cell (e.g., SIB1 or SIB2). In the following, the contents of the 3GPP standard specification can be applied in the same way to embodiments of this disclosure that apply Equation 1.

[0161] - Condition 3: The cell is not prohibited based on the information recently provided from the NAS layer, and the cell is not part of at least one tracking area (TA) of the PLMN that is part of the "prohibited tracking area" list that satisfies Condition 1-1 and / or Condition 1-2 (the cell is not part of at least one TA of the PLMN that is part of the "prohibited tracking area" list that satisfies the first condition above).

[0162] When, for example, the “cellBarred” indicator is set to “barred” in at least the MIB, the Rel-16 “cellReservedForOperatorUse” indicator is set to “reserved” in SIB1, the Rel-16 “cellReservedForFutureUse” indicator is set to “reserved”, or the Rel-15 “cellReservedForOtherUse” indicator is set to “true”, the cell is disabled and the CAG-ID is not broadcast in the cell.

[0163] refer to Figure 1f UE 1f-01 can establish an RRC connection with base station (e.g., gNB) 1f-02 and is therefore in RRC connection mode (RRC_CONNECTED) (operation 1f-05).

[0164] When no data is sent or received for some reason or at some time, base station 1f-02 can send an RRC connection release message (RRCRelease) to UE 1f-01 (operation 1f-10). When the RRC connection release message includes suspend configuration information (suspendConfig), UE 1f-01 can switch to RRC inactive mode, and when it does not include suspend configuration information, UE 1f-01 can switch to RRC idle mode (operation 1f-15).

[0165] UE 1f-01, which has been switched to RRC idle mode or RRC inactive mode as an SNPN access mode, can choose either CAG or PLMN (1f-16). The method for selecting a PLMN has been described in the above embodiments. For example, when UE 1f-01 selects a CAG, the AS layer of UE 1f-01 can scan all RF channels in the NR band according to its capability requested from the NAS layer of UE 1f-01, and search for one or more available CAGs (in the UE, according to the NAS request, the AS should scan all RF channels in the NR band according to its capability to find available CAGs). On each carrier, UE 1f-01 can search for at least one cell with the strongest signal, and report one or more PLMNs and one or more CAG IDs for them to the NAS layer by reading system information from that cell. When a human-readable network name (HRNN) is broadcast in the system information, the AS layer of UE 1f-01 can also report the received HRNN to the NAS layer. The UE should at least search for the strongest cell, read its system information, and report the available CAG ID along with its HRNN (if broadcast) and PLMN to the NAS. Higher layers can select the CAG and notify the AS layer of the CAG (if the NAS has already selected the CAG and made that selection available to the AS).

[0166] UE 1f-01 can receive / acquire system information (operation 1f-20) and perform a cell selection procedure (operation 1f-25). That is, UE 1f-01 can receive / acquire at least one MIB and SIB1, and perform a cell selection procedure to camp on a suitable cell belonging to the selected CAG. Specifically, condition 1 can be determined by the CellAccessRelatedInfo information element broadcast in SIB1.

[0167] The CellAccessRelatedInfo element may include at least one of the plmn-IdentityList or npn-IdentityInfoList elements. The plmn-IdentityList element may follow the embodiments described above. The npn-IdentityInfoList may include a list of NPN identification information. The total number of PLMNs included in the plmn-IdentityList and npn-IdentityInfoList elements may be limited to no more than 12. In this embodiment, the number of PLMNs may be limited by one of the following methods.

[0168] The total number of PLMNs (identified by the PLMN identifier), PNI-NPNs (identified by the PLMN identifier and CAG-ID), and SNPNs (identified by the PLMN identifier and NID) in the PLMN-IdentityInfoList and NPN-IdentityInfoList shall not exceed 12.

[0169] The total number of PLMNs (identified by the PLMN identifier itself in both the plmn-IdentityInfoList and npn-IdentityInfoList) does not exceed 12.

[0170] The ASN.1 structure for the CellAccessRelatedInfo information element can be represented as follows.

[0171]

[0172] According to the RAN sharing structure in the NPN of this embodiment, the npn-IdentityInfoList information element may include only the CAG identifier list (cag-IdentityList), only the nid-List (which defines the NPN identifier of the SNPN), or both cag-IdentityList and nid_List. When the NG-RAN is shared by one or more PNI-NPNs, or by one or more PNI-NPNs and one or more PLMNs included in the PLMN identifier list information, only the cag-IdentityList can be included in the npn-IdentityInfoList. Similarly, when the NG-RAN is shared by one or more SNPNs included in the PLMN identifier list information, or by one or more SNPNs included in the PLMN identifier list information and one or more PLMNs, only the nid-List can be included in the npn identifier information list. When the NG-RAN is shared by one or more PNI-NPs and one or more SNPs, both the cag-IdentityList and nid-List can be included in the npn-IdentityInfoList. In this case, one or more PLMNs may not be included in the PLMN identifier list information used for the above-described conventional access. When the NG-RAN is shared by one or more PNI-NPNs, or by one or more PNI-NPNs and one or more PLMNs or one or more SNPNs, the cag-IdentityList and nid-List can be included in the PLMN-IdentityList and npn-IdentityInfoList.

[0173] -cag-IdentityList can include one or more CAG identifiers (CAG-Identity).

[0174] - The information element for each CAG identity may include a list of PLMN identifiers (which may be indicated by a list of nPN identifiers), which includes one or more PLMN identifiers (or NPN identifiers) mapped to each PLMN identifier (or NPN identifier) ​​and a list of CAG identifiers to include identifiers of one or more PNI-NPNs. That is, the CAG-identity information element may include at least one of the following parameters.

[0175] -CellIdentity value

[0176] - A list of PLMN identifiers (npn identifier list) including one or more PLMN identifiers. Each PLMN identifier can be either a PLMN identifier value or a PLMN index value. For example, when the PLMN-Identity value included in the PLMN-IdentityList of SIB1 (an information element different from the npn-IdentityInfoList) is used in the same way, the PLMN-Index value may be included; otherwise, the PLMN-Identity value itself may be included. The PLMN index value is an integer value and can be determined as described below.

[0177]

[0178] - CAG Identity List (cag-IdentityList) indicates a list of CAG identifiers mapped to each PLMN identifier value or PLMN index value.

[0179] - Tracking region code

[0180] - Indicates the RAN area code

[0181] - The indicator (cellReservedForOperatorUse) indicates whether a reserved cell is used by the operator. This indicator can be applied to all PLMNs included in the CAG identifier.

[0182] - The indicator (cellReservedForfutureUse) indicates whether a cell has been reserved for future use. This indicator can be applied to all PLMNs included in the CAG-IdentityInfo.

[0183] UE 1f-01, which is already camped on an appropriate cell, can perform a cell reselection process (operation 1f-30). That is, UE 1f-01 can reselect a cell based on SIB2, SIB3, SIB4, SIB5, SIB6, etc., which include cell reselection parameters.

[0184] In operation 1f-35, UE 1f-01 can initiate an RRC connection for some reason, or send data to and receive data from base station 1f-02. Specifically, in operation 1f-35, when UE 1f-01 is in RRC idle mode, UE 1f-01 can perform the RRC connection establishment process with base station 1f-02. In RRC idle mode, UE 1f-01 can establish reverse synchronization with base station 1f-02 and send an RRC connection establishment request message (RRCSetupRequest message) to base station 1f-02 (operation 1f-40). The RRC connection establishment request message can include the UE 1f-01's identifier (ue-Identity) and the reason for RRC connection establishment (establishment reason). Upon successfully receiving the RRC connection establishment request message, base station 1f-02 can send an RRC connection setup message (RRCSetup message) to UE 1f-01 (operation 1f-45). RRC connection setup messages may include radio resource configuration information (radio beacon configuration) and primary cell group configuration information (primary cell group).

[0185] Upon successfully receiving the RRC connection setup message, UE 1f-01 can apply the configuration information included in the RRC connection setup message and switch to RRC connection mode (operation 1f-50). The current cell can be considered PCell. UE 1f-01, which has already switched to RRC connection mode, can send an RRC connection setup complete message (RRCSetupComplete message) to base station 1f-02 by including the following in the RRC connection setup complete message (operation 1f-55).

[0186] In this embodiment, the selected PLMN identifier can be set to the PLMN selected by a higher layer from one or more PLMNs included in the PLMN identifier list or npn-IdentityInfoList broadcast in SIB1 (setting the selected PLMN identifier to the PLMN selected by a higher layer from the PLMN identifier list or npn-IdentityInfoList included in SIB1), and the selected PLMN identifier (selectedPLMN-Identity) can be included in the RRC connection establishment completion message. Here, the method of setting the selected PLMN identifier (selectedPLMN-Identity) can vary depending on whether a CAG cell (meeting the conditions of a suitable cell, such as condition 1-1, condition 2, or condition 3) is selected in operation 1f-16, 1f-25, or 1f-30, or whether a cell for regular access is selected (meeting the conditions of a suitable cell, such as condition 1-2, condition 2, or condition 3).

[0187] - Case 1: When a CAG cell is selected, the selected PLMN and CAG ID can be included in the RRC connection establishment completion message.

[0188] - Including the PLMN index selected by the UE from the plmn-IdentityList and npn-IdentityInfoList fields included in SIB1 (PLMN index selected by the UE from the plmn-IdentityList and npn-IdentityInfoList fields included in SIB1).

[0189] - Because a PNI-NPN can be identified by a combination of a PLMN identifier (or an NPN identifier) ​​and a CAG ID, the CAG ID included in the UE's list of allowed CAGs for the selected PLMN can be included in the NAS message (due to security concerns). For example, a NAS message could refer to a dedicated NAS message, which is included in the RRC connection establishment completion message.

[0190] [Table 2]

[0191]

[0192] -Scenario 2: When selecting a cell for regular access.

[0193] - Includes PLMN indexes selected only by considering the plmn-IdentityList field included in SIB1 (PLMN indexes selected by the UE from the plmn-IdentityList included in SIB1).

[0194] In operation 1f-35, when UE 1f-01 is in RRC inactive mode, UE 1f-01 can perform an RRC connection restoration procedure with base station 1f-02. UE 1f-01 in RRC inactive mode can establish reverse synchronization with base station 1f-02 and send an RRC connection restoration request message (RRCResumeRequest or RRCesumeRequest1 message) to base station 1f-02 (operation 1f-40). The RRC connection restoration request message may include UE 1f-01's identifier (resumeIdentity), a restoration message authentication code for integrity (hereinafter referred to as resumeMAC-1), and a restoration reason (resumeCause), etc. Upon successfully receiving the RRC connection restoration request message, base station 1f-02 can send an RRC connection restoration message (RRCResume message) to UE 1f-01 (operation 1f-45). The RRC connection restoration message may include at least one of the following: radio resource configuration information (radioobearerConfig), master cell group configuration information (masterCell Group), measurement configuration information (measConfig), a full configuration indicator (fullConfig), second radio resource configuration information (radioobearerConfig2), or an sk-Counter value. Upon successful reception of the RRC connection restoration message, UE1f-01 may apply the configuration information included in the RRC connection restoration message and switch to RRC connection mode (operation 1f-50). The current cell may be considered a PCell. UE1f-01, having switched to RRC connection mode, may send an RRC connection restoration complete message (RRCResumeComplete message) to base station 1f-02 (operation 1f-55). The RRC connection restoration complete message may include PLMN information and / or CAG ID selected according to the above options.

[0195] Figure 1g This is a diagram illustrating the process by which a UE establishes an RRC connection in a next-generation mobile communication system by accessing an SNPN cell in a standalone non-public network (SNPN) in either RRC inactive mode (RRC_INACTIVE) or RRC idle mode (RRC_IDLE), according to embodiments of this disclosure.

[0196] According to embodiments of this disclosure, an SNPN can represent a network operated by an NPN operator, independent of network functions provided by a PLMN (the SNPN is operated by the NPN operator and independent of network functions provided by a PLMN). Therefore, when a UE is in SNPN access mode, the UE may not perform the normal PLMN selection process (when a UE is configured to operate in SNPN access mode, the UE does not perform the normal PLMN selection process). A UE operating in SNPN access mode can receive a list of one or more available PLMN IDs and available network identifiers (NIDs) from broadcast system information and apply them to the network selection process (a UE operating in SNPN access mode reads the list of available PLMN IDs and available NIDs from broadcast system information and considers them during network selection). That is, a UE operating in SNPN can be configured to have user identifier and credential information for identifying one or more SNPNs by a combination of PLMN IDs and NIDs, and thus can support SNPN access mode (a UE with SNPN enabled is configured to have user identifiers and credentials for identifying one or more SNPNs by a combination of PLMN IDs and NIDs, and thus can support SNPN access mode). A UE configured in SNPN access mode (a UE configured to operate in SNPN access mode) can consider a cell as a suitable cell when the following conditions are met.

[0197] Condition 1: When the cell belongs to the SNPN selected or registered by the UE (the cell is part of the SNPN selected or registered by the UE).

[0198] Condition 2: When the community meets the community selection criteria.

[0199] The criteria for selecting a residential community can be expressed as Equation 1 below.

[0200] Equation 1

[0201] Srxlev>0 and Squal>0

[0202] in:

[0203] Srxlev=Qrxlevmeas-(Qrxlevmin+Qrxlevminoffset)-Pcompensation-Qoffsettemp

[0204] Squal=Qqualmeas-(Qqualmin+Qqualminoffset)-Qoffsettemp

[0205] For the definition of the parameters used in Equation 1, refer to the 3GPP standard specification "38.304: User Equipment (UE) Procedures in Idle Mode". These parameters may be included in system information broadcast by the cell (e.g., SIB1 or SIB2). In the following, the contents of the 3GPP standard specification can be applied in the same way to embodiments of this disclosure that apply Equation 1.

[0206] - Condition 3: The cell is not prohibited based on the information recently provided from the NAS layer, and the cell is part of at least one tracking area (TA) that is not part of the “prohibited tracking area” list of the SNPN that satisfies Condition 1 (the cell is part of at least one TA that is not part of the “prohibited tracking area” list of the UE’s selected SNPN or registered SNPN).

[0207] For example, a cell is disabled when the “cellBarred” indicator is set to “barred” in at least the MIB, the Rel-16 “cellReservedForOperatorUse” indicator is set to “reserved” in SIB1, or the Rel-16 “cellReservedForFutureUse” indicator is set to “reserved”.

[0208] refer to Figure 1g During operation 1g-05, UE 1g-01 can establish an RRC connection with base station 1g-02 (e.g., gNB) and is therefore in RRC connection mode (RRC_CONNECTED).

[0209] When no data is sent or received for some reason or at some time, base station 1g-02 can send an RRC connection release message (RRCRelease) to UE 1g-01 (operation 1g-10). When the RRC connection release message includes suspend configuration information (suspendConfig), UE 1g-01 can switch to RRC inactive mode, and when it does not include suspend configuration information, UE 1g-01 can switch to RRC idle mode (operation 1g-15).

[0210] UE 1g-01, which has been switched to RRC idle mode or is in RRC inactive mode set to SNPN access mode, can select an SNPN (1g-16). For example, the AS layer of UE 1g-01 can scan all RF channels in the NR band and search for one or more available SNPNs based on its capabilities requested from the NAS layer of UE 1g-01 (in response to a request from the NAS, the AS should scan all RF channels in the NR band to find available SNPNs). On each carrier, UE 1g-01 can search for at least one cell with the strongest signal and report one or more SNPN identifiers to the NAS layer by reading system information from that cell. The AS layer of UE 1g-01 can also report the received HRNN to the NAS layer when the HRNN is broadcast in the system information. The UE should at least search for the strongest cell, read its system information, and report the SNPN identifier along with its HRNN (if broadcast) to the NAS. Higher layers can select an SNPN and notify the AS layer of the SNPN (if the NAS has already selected an SNPN and provided that selection to the AS).

[0211] UE 1g-01 can receive or acquire system information (operation 1g-20) and perform a cell selection procedure (operation 1g-25). That is, UE 1g-01 can receive / acquire at least one MIB and SIB1, and perform a cell selection procedure to camp on a suitable cell belonging to the selected SNPN. Specifically, condition 1 can be determined by the CellAccessRelatedInfo information element broadcast in SIB1.

[0212] The CellAccessRelatedInfo element may include at least one of the plmn-IdentityList or npn-IdentityInfoList elements. The plmn-IdentityList element may follow the embodiments described above. The npn-IdentityInfoList may include a list of NPN identification information. The total number of PLMNs included in the plmn-IdentityList and npn-IdentityInfoList elements may be limited to no more than 12. In this embodiment, the number of PLMNs may be limited by one of the following methods.

[0213] The total number of PLMNs (identified by the PLMN identifier), PNI-NPNs (identified by the PLMN identifier and CAG-ID), and SNPNs (identified by the PLMN identifier and NID) in the PLMN-IdentityInfoList and NPN-IdentityInfoList shall not exceed 12.

[0214] The total number of PLMNs (identified by the PLMN identifier itself in the PLMN-IdentityInfoList and NPN-IdentityInfoList) does not exceed 12.

[0215] The ASN.1 structure for the CellAccessRelatedInfo information element can be represented as follows.

[0216]

[0217] According to the RAN sharing structure in the NPN of this embodiment, the npn-Identity InfoList information element may include only cag-Identity related information, snpn-Identity related information, or both cag-Identity related information and snpn-Identity related information. When the NG-RAN is shared by one or more PNI-NPNs, or by one or more PNI-NPNs and one or more PLMNs included in the PLMN identification list information, only cag-Identity related information can be included in the npn identifier information list. Similarly, when the NG-RAN is shared by one or more SNPNs included in the PLMN identification list information, or by one or more SNPNs included in the PLMN identification list information and one or more PLMNs, only snpn-Identity related information can be included in the npn identifier information list. When the NG-RAN is shared by one or more PNI-NPs and one or more SNPs, both cag-Identity related information and snpn-Identity related information can be included in the npn-IdentityInfoList. In this case, one or more PLMNs may not be included in the PLMN identification list information used for regular access. When an NG-RAN is shared by one or more PNI-NPNs, one or more PNI-NPNs and one or more PLMNs, or one or more SNNPs, cag-Identity related information and snpn-Identity related information can be included in plmn-IdentityList and npn-IdentityInfoList.

[0218] -snpn-identifier related information can include one or more SNpn-identifier information elements.

[0219] Each SNPN identifier-related information element can include multiple PLMN identifiers and a list of NIDs mapped to the corresponding PLMN identifiers, thus including multiple SNPN identifiers. That is, the SNPN identifier-related information element can include at least one of the following parameters.

[0220] -CellIdentity value

[0221] - PLMN identifier value or PLMN index value. For example, when the PLMN identifier value included in the PLMN identifier list of SIB1 is used in the same way, the PLMN index value may be included; otherwise, the PLMN identifier value itself may be included. The PLMN identifier used for SNPN can be the same as the PLMN identifier value included in the PLMN identifier list, because the PLMN used for regular access can be used in the same way. The PLMN index value is an integer value and can be determined according to the following description.

[0222]

[0223] -plmn identifier value or NID mapped to PLMN index value

[0224] - Tracking region code

[0225] -Indicates RAN area code

[0226] - The indicator (cellReservedForOperatorUse) indicates whether a cell has been reserved for operator use. This indicator can be applied to each PLMN.

[0227] - The indicator (cellReservedForfutureUse) indicates whether a cell has been reserved for future use. This indicator can be applied to the PLMN.

[0228] UE 1g-01, which is already camped on an appropriate cell, can perform a cell reselection process (operation 1g-30). That is, UE 1g-01 can reselect a cell based on SIB2, SIB3, SIB4, SIB5, SIB6, etc., which include cell reselection parameters.

[0229] In operation 1g-35, UE 1g-01 can initiate an RRC connection for some reason, or send data to and receive data from base station 1g-02. Specifically, in operation 1g-35, when UE 1g-01 is in RRC idle mode, UE 1g-01 can perform the RRC connection establishment process with base station 1g-02. UE 1g-01 in RRC idle mode can establish reverse synchronization with base station 1g-02 and send an RRC connection establishment request message (RRCSetupRequest message) to base station 1g-02 (operation 1g-40). The RRC connection establishment request message can include the UE 1g-01's identifier (ue-Identity) and the reason for RRC connection establishment (establishment reason). Upon successfully receiving the RRC connection establishment request message, base station 1g-02 can send an RRC connection setup message (RRCSetup message) to UE 1g-01 (operation 1g-45). RRC connection setup messages may include radio resource configuration information (radio beacon configuration) and primary cell group configuration information (primary cell group).

[0230] Upon successfully receiving the RRC connection setup message, UE 1g-01 can apply the configuration information included in the RRC connection setup message and switch to RRC connection mode (Operation 1g-50). The current cell can be considered PCell. UE 1g-01, which has already switched to RRC connection mode, can send an RRC connection setup complete message (RRCSetupComplete message) to base station 1g-02 by including the following content in the RRC connection setup complete message (Operation 1g-55).

[0231] In this embodiment, the selected PLMN identifier can be set to a PLMN selected by a higher layer from one or more PLMNs included in the PLMN identifier list in SIB1 or the npn-IdentityInfoList broadcast (setting the selected PLMN identifier to a PLMN selected by a higher layer from the PLMN identifier list in SIB1 or the npn-IdentityInfoList). The selected PLMN identifier can be included in the RRC connection establishment completion message. Here, when selecting a suitable SNPN cell in operation 1g-16, 1g-25, or 1g-30, it is recommended to include the selected SNPN information in the RRC connection establishment completion message. Here, the selected PLMN identifier can be included in the following RRC connection establishment completion message.

[0232] - Including the PLMN index selected by the UE from the PLMN-IdentityList and npn-IdentityInfoList fields included in SIB1 (PLMN index selected by the UE from the PLMN-IdentityList and npn-IdentityInfoList fields included in SIB1).

[0233] -SNPN can be identified by a combination of PLMN identifier and NID. Therefore, because PLMN and NID are mapped one-to-one, UE 1g-01 may not include the NID in the RRC connection release message. Alternatively, UE 1g-01 may include the selected PLMN and NID (supported by UE 1g-01) or a list of NIDs mapped to it in the RRC connection establishment completion message. When the NID is mapped to a PLMN in the list, UE 1g-01 may also include the selected PLMN and the selected NID or NID list mapped to it in the RRC connection establishment completion message. Alternatively, UE 1g-01 may include the selected PLMN and the selected NID or NID list mapped to it in the NAS message included in the RRC connection establishment completion message. Thus, the NID or NID list can be included in the NAS message included in the RRC connection establishment completion message, or it can be included in the RRC connection establishment completion message itself.

[0234] [Table 3]

[0235]

[0236] In operation 1g-35, when UE 1g-01 is in RRC inactive mode, UE 1g-01 can perform an RRC connection restoration procedure with base station 1g-02. UE 1g-01 in RRC inactive mode can establish reverse synchronization with base station 1g-02 and send an RRC connection restoration request message (RRCResumeRequest or RRCesumeRequest1 message) to base station 1g-02 (operation 1g-40). The RRC connection restoration request message may include UE 1g-01's identifier (resumeIdentity), a restoration message authentication code for integrity (hereinafter referred to as resumeMAC-1), and a restoration reason (resumeCause), etc. Upon successfully receiving the RRC connection restoration request message, base station 1g-02 can send an RRC connection restoration message (RRCResume message) to UE 1g-01 (operation 1g-45). The RRC connection restoration message may include at least one of the following: radio resource configuration information (radioobearerConfig), master cell group configuration information (masterCell Group), measurement configuration information (measConfig), a full configuration indicator (fullConfig), second radio resource configuration information (radioobearerConfig2), or an sk-Counter value. Upon successful receipt of the RRC connection restoration message, UE 1g-01 may apply the configuration information included in the RRC connection restoration message and switch to RRC connection mode (operation 1g-50). The current cell may be considered a PCell. UE 1g-01, having switched to RRC connection mode, may send an RRC connection restoration complete message (RRCResumeComplete message) to base station 1g-02 (operation 1g-55). The RRC connection restoration complete message may include PLMN information and / or NID selected according to the above options.

[0237] This disclosure has referenced Figure 1e , 1f Section 1g describes the process of regular access, access to PNI-NPN, and access to UE's SNPN, and this process can be summarized as follows.

[0238] 1. Community Type

[0239]

[0240] As an NPN-only cell setting, SIB1 provides the following CellAccessRelatedInfo and is configured as follows.

[0241] - Set cellReservedForOtherUse to true.

[0242] - Set relevant information in npn-IdentityInfoList

[0243]

[0244]

[0245] 2. Type UE

[0246]

[0247] 3. Expected UE operation for each system

[0248]

[0249] For CAG UEs, when a shared cell allows access to both normal UEs and CAG UEs, it can be assumed that CAG access is prioritized. That is, this might mean selecting a PLMN that exists in the NPN list. (If the shared cell provides both normal and CAG access (i.e., when both lists contain the selected PLMN, the PLMN is selected from the NPN list), then the motivation for CAG access will also be prioritizing CAG access.)

[0250] 4. Contents included in SIB1 based on cell type

[0251]

[0252] In NPN-only cells, PLMN-IdentityInfoList is unnecessary, but it exists because the corresponding field is mandatory signaling.

[0253] 5. Cell type indication method and access restrictions

[0254]

[0255] Figure 1h This diagram illustrates UE operations for a UE to access an NPN cell according to embodiments of the present disclosure. Specifically, UE operations for accessing the PNI-NPN and the SNPN of a UE according to the above embodiments are presented.

[0256] In Operation 1h-05, the UE performs cell selection / reselection and can perform a cell selection procedure to camp on the appropriate cell to which the selected PLMN belongs by receiving / acquiring at least the MIB and SIB1. Specifically, this can be determined by the CellAccessRelatedInfo information element broadcast in SIB1. In Operation 1h-10, the UE can perform an operation to identify the parameters included in SIB1, specifically the CellAccessRelatedInfo, and then store the parameters to be used to determine whether to use system information stored in another cell (determining the validity of the system information). This corresponds to the operation of selecting and storing specific information included in SIB1, and the stored parameters correspond to the following values.

[0257] - AreaScope Value: An indicator that indicates whether system information is maintained at the area unit level. There is one value for each SIB, and it is set in the SIB-TypeInfo information element (IE) within the si-SchedulingInfo. The UE stores the corresponding area scope value indicated for each SIB.

[0258] -PLMN Identity: The UE stores the first PLMN identifier among multiple PLMN identifier values ​​included in the PLMN identifier information list.

[0259] -NPN Identity: The UE stores the first NPN identifier among multiple NPN identifier values ​​included in the NPN identifier information list. (For reference, in the case of SNPN, the NPN identifier indicates the SNPN identifier, while in the case of PNI-NPN, the NPN identifier indicates the PNI-NPN identifier.)

[0260] - Cell Identity: The UE stores the cell identification value included in the PLMN identifier information list, which includes the selected PLMN identifier and NPN identifier. That is, the UE stores the cell identification value included in the first PLMN-IdentityInfo or NPN-IdentityInfo among multiple PLMN-Identity values ​​included in the PLMN-IdentityInfoList.

[0261] -systemInformationAreaID: This is a value stored in SIB1 and applied to all SIB broadcasts within the corresponding cell. systemInformationAreaID is directly included in the SI-SchedulingInfo IE. The system information broadcast in a cell with this value is a unique area ID in the PLMN, and the same area ID is used to apply the same system information to the cell.

[0262] - ValueTag: This is a parameter indicating whether the system information has changed from a previously broadcast value, and is defined as a value between 0 and 31. A corresponding value is also set for each SIB and included in the SIB-TypeInfo IE within the si-SchedulingInfo, and the UE stores all values.

[0263]

[0264] In this disclosure, the following ASN.1 code has been added to the structural description of the fields and IE, and you may refer to the following ASN.1 code.

[0265]

[0266]

[0267]

[0268]

[0269] During operation 1h-15, the UE can select a first Tracking Area Code (TAC), a first Cell Identifier, and a first RAN Area Code (RANAC) associated with the selected PLMN and SNPN, and later use the same area codes to verify the validity of system information and determine the validity of the selected TAC cell and RANAC. In this disclosure, UE operations are categorized based on network type and the UE type applied in the operation.

[0270] 1. First condition: This corresponds to a PN-only cell, which is a cell that only allows access to normal UEs. That is, in this case, the NPN-IdentityInfoList is not included in the cellAccessRelatedInfo of the corresponding cell's SIB1.

[0271] - When the first condition is met, apply method 1 below.

[0272] 2. Second condition: This corresponds to a shared cell, which is a cell that both normal UEs and NPN UEs can access.

[0273] A. Condition (2-1): When only CAG UEs access the corresponding cell

[0274] - When condition (2-1) is met, apply method 2 below.

[0275] B. Condition (2-2): When both the CAG UE and the normal UE access the corresponding cell.

[0276] - When condition (2-2) is met, apply method 1 below.

[0277] C. Condition (2-3): When only the UE of the NPN accesses the corresponding cell

[0278] - When conditions (2-3) are met, apply method 2 below.

[0279] 3. Third condition: This corresponds to an NPN-only cell, which is a cell that only NPN UEs can access. That is, in this case, the NPN-IdentityInfoList is included in the cellAccessRelatedInfo of the corresponding cell's SIB1, and cellReservedForOtherUse is set to true.

[0280] - When the third condition is met, apply method 2 below.

[0281] As described above, the UE selects and applies the following parameters differently based on the network selection conditions in this disclosure.

[0282] 1. Method 1: The UE applies the PLMN-IdentityInfo and uses the relevant values ​​in subsequent processes. In other words, during operation 1h-15, the UE selects the first RANAC and the first cell identifier as the first TAC, and tracks the area code, RANAC, and cell identifier included in the TA identifier list selected by using the selected first TAC and the first cell identifier. (In the remaining process, the PLMN-IdentityList, trackingAreaCode, RANAC, and the cell identifier of the cell received in the corresponding PLMN-IdentityInfo containing the selected PLMN are used.)

[0283] 2. Method 2: The UE applies the NPN-IdentityInfo and uses the relevant values ​​in subsequent processes. In other words, the tracking area code, RANAC, and cell identifier included in the npn-IdentityList are selected as the first TAC, first RANAC, and first cell identifier. (In the remaining processes, the npn identifier, trackingAreaCode, RANAC, and the cell identifier of the cell received in the corresponding NPN identifier information containing the selected NPN are used.)

[0284] In Operation 1h-20, the UE can use the selected first TAC and first cell identifier to perform operations such as identifying whether access to the selected TAC and cell is prohibited, and identifying whether a TA update is needed. Operation 1h-20 identifies whether the selected first TAC exists in the prohibited TA list and whether the selected first cell identifier exists in the prohibited cell list by referring to information received from the NAS layer. Furthermore, the UE compares whether the selected first TAC is included in the valid TA list and determines whether a TA update is needed based on whether the selected first TAC is included in the valid TAC list.

[0285] In Operation 1h-25, depending on whether the UE has selected an SNPN or PLMN, when the selected PLMN is included in the npn-IdentityInfoList, the UE sends the HRNN information received from the SIB to the NAS layer so that the HRNN associated with the selected PLMN can be displayed on the user screen. Here, the HRNN information can be sent via the following ASN code, and is mapped one-to-one to the nPN identifier included in the npn-IdentityInfoList. That is, the HRNN information mapped to the selected NPN can be sent to the NAS layer. When the nth entry in the HRNN list is a certain value (e.g., hx00) or has a certain size (1 byte or 0 bytes), the same rules can be applied to the HRNN of the nth entry as to the HRNN of the (n-1)th entry in the HRNN list. In this way, signaling reduction can be achieved by reducing duplicate HRNN downloads.

[0286]

[0287]

[0288] During operation 1h-30, the UE can perform an operation to store system information for the corresponding cell, and the stored information corresponds to the values ​​used in operations 1h-10 to 1h-25. Specifically, the UE stores the first cell identifier that satisfies this procedure as a second cell identifier, and uses the first cell identifier to determine whether to use system information stored in other cells in the future / identification validity.

[0289] During operation 1h-35, the UE determines whether to update the TA and RNA using the stored first cell identifier, first TAC, and first RANAC values, and performs the following operations if necessary. The determination of whether to perform the operation can be based on the result of operation 1h-20, and operation 1h-35 can be performed simultaneously with operation 1h-30 or before operation 1h-30.

[0290] - Perform a TA update when only a TA update is required.

[0291] - Perform a TA update when both TA and RNA updates are required.

[0292] - Perform RNA updates when only RNA updates are needed.

[0293] Figure 1i is a diagram illustrating the process by which a UE sends a measurement report message for automatic neighbor relationships to a base station in a next-generation mobile communication system, performed by the UE in RRC connected mode (RRC_CONNECTED) according to an embodiment of the present disclosure.

[0294] Referring to Figure 1i, UE 1i-01 can establish an RRC connection with base station 1i-02 (e.g., gNB) and is therefore in RRC connection mode (RRC_CONNECTED) (operation 1i-05).

[0295] In operation 1i-10, UE 1i-01 can send a UE capability information message (UE capability information message) to base station 1i-02 through the UE capability transfer procedure. The UE capability information message may include at least one of the following related to whether Automatic Neighbor Relations (ANR) is supported.

[0296] - The indicator for the CGI-InfoEUTRA report used for E-UTRA is a possible indicator. This indicator can be represented by a separate indicator depending on the core type (e.g., EPC or 5GC).

[0297] - An indicator indicating that a CGI-InfoNR report for NR is possible. This indicator can be represented by a separate indicator depending on the UE type according to the above embodiments.

[0298] In operation 1i-15, base station 1i-02 may send an RRC message including measurement configuration information (MeasConfig) to UE 1i-01. For example, the RRC message may be an RRC connection reconfiguration message (RRC reconfiguration message). The measurement configuration information may include at least one of the following.

[0299] -MeasObjectToAddModList

[0300] -MeasObjectToAddModList can include MeasObjectToAddModList IE.

[0301] The -MeasObjectToAddModList IE can include one or more MeasObjectToAddMods.

[0302] - Each MeasObjectToAddMod can include a measObjectId and a MeasObject corresponding to the measObjectId.

[0303] -measObject can include one of the measurement objects of NR (i.e., measObjectNR) and the measurement objects of EUTRA (i.e., measObjectEUTRA).

[0304] - reportConfigToAddModList

[0305] -reportConfigToAddModList can include ReportConfigToAddModList IE.

[0306] The ReportConfigToAddModList IE can include one or more ReportConfigToAddMods.

[0307] - Each ReportConfigToAddMod can include ReportConfigId, and can include report configuration information (reportConfig) corresponding to ReportConfigId.

[0308] -reportConfig can include one of the NR reporting configuration (i.e., reportConfigNR) and the interRAT reporting configuration (i.e., reportConfigInterRAT).

[0309] - In this embodiment, reportConfigNR may include at least one reportConfigId, where reportType is set to reportCGI. reportCGI may include reportCGI, and reportCGI may be configured with at least one of an indicator (cellForWhichToReportCGI) or a useAutonomousGaps indicator that indicates which of one or more CGIs will be reported. Specifically, cellForWhichToReportCGI may include one or more PhysCellIDs (or PhysCellIdRange), and the userAutonomousGaps indicator is an indicator that indicates whether the UE can obtain system information of neighboring NR cells by using autonomous gaps.

[0310] -measIdToAddModList

[0311] -measIdToAddModList can include MeasIdToAddModList IE.

[0312] The -MeasIdToAddModList IE can include one or more MeasIdToAddMods.

[0313] Each MeasIdToAddMod can include a MeasID, and also includes a MeasObjectId and a reportConfigId corresponding to the MeasID.

[0314] In operation 1i-20, UE 1i-01 can apply measurement configuration information received from base station 1i-02. For example, when reportType is configured to reportCGI in the ReportConfig associated with a specific MeasID (if reportType is set to reportCGI in the reportConfig associated with that measid), UE 1i-01 can configure the value of the T321 timer and drive the T321 timer differently depending on which RAT (E-UTRA or NR) is considered based on the measObject associated with the measid. When considering NR, it depends on which frequency band (FR1 or FR2) is considered, and whether the ReportConfig associated with the MeasID includes useAutonomousGaps.

[0315] In Operation 1i-25, UE 1i-01 can perform measurements by applying the measurement configuration information received in Operation 1i-20.

[0316] In Operation 1i-30, UE 1i-01 can determine whether a measurement report has been triggered. For example, if the ReportConfig with report type set to reportCGI is included for each MeasID included in the MeasIdList belonging to VarMeasConfig, UE 1i-01 can consider a cell suitable for measurement report triggering when a cell with a physical cell identifier that matches the value of cellForWhichToReportCGI included in the ReportConfig belonging to VarMeasConfig is detected in the associated MeasObject (considering a cell detected on the associated MeasObject whose physical cell identifier matches the value of cellForWhichToReportCGI included in the corresponding ReportConfig within VarMeasConfig). When reportType is set to reportCGI, UE 1i-01 can stop the T321 timer when an SIB1 is acquired for the requested cell or when it is detected that no SIB1 is being sent in the requested cell. Then, UE 1i-01 can include measurement report entries from VarMeasReportList for MeasID, set numberOfReportsSent defined in VarMeasReportList to 0, and execute the measurement reporting procedure. When the T321 timer for MeasID expires, UE 1i-01 can include measurement report entries from VarMeasReportList for MeasID, set numberOfReportsSent defined in VarMeasReportList to 0, and execute the measurement reporting procedure.

[0317] In operation 1i-35, UE 1i-01 can send a Measurement Report message to base station 1i-02. UE 1i-01 can configure MeasResult in the Measurement Report message for each MeasID in which the measurement reporting process is triggered. For example, the measurement identifier that triggers the measurement report can be set to the MeasID. If at least one available neighboring cell exists to report (if at least one applicable neighboring cell exists to report), and the cell indicated by cellForWhichReportCGI is an NR cell, UE 1i-01 can perform the following actions to send the Measurement Report message to base station 1i-02.

[0318] - When the plmn-IdentityInfoList of cgi-info is obtained from the NR cell indicated by the cell (if the plmn-IdentityInfoList of cgi-info for the cell has already been obtained), the plmn-IdentityInfoList, the tracking area code (if possible), the ranac (if possible), the Cellidentity, and the cellReservedForOperatorUse for each entry in the plmn-IdentityInfoList, as well as the frequencyBandlist (if possible), can be included in the measurement report message (i.e., included in cgi-InfoNR).

[0319] - When obtaining the npn-IdentityInfoList of cgi-info from the NR cell indicated by cellForWhichReportCGI, the npn-IdentityInfoList, trackingAreaCode (if possible), ranac (if possible), cellIdentity, and cellReservedForOperatorUse for each entry of the npn-IdentityList, as well as cellReservedForOtherUse (if possible) or frequencybandlist (if possible) can be included in the measurement report message (i.e., included in cgi-InfoNR).

[0320] - When the NR cell indication SIB1 indicated by cellForWhichReportCGI is not broadcast via MIB, UE 1i-01 may include noSIB1 in the measurement report message (i.e., included in cgi-InfoNR), which includes ssb-SubCarrierOffset and pdcch-ConfigSIB1 obtained from MIB.

[0321] According to this embodiment, UE 1i-01 includes cellReservedForOtherUse in CGI-InfoNR because base station operation (e.g., handover) can be assisted by reporting the cell type of the indicated NR cell to base station 1i-02.

[0322] Figure 1jThis is a diagram illustrating the process by which a UE sends a measurement report message for automatic neighbor relationships to a base station in a next-generation mobile communication system, performed by the UE in RRC connected mode (RRC_CONNECTED) according to embodiments of the present disclosure.

[0323] Reference Figure 1j UE 1j-01 can establish an RRC connection with base station 1j-02 (e.g., gNB) and is therefore in RRC connection mode (RRC_CONNECTED) (operation 1j-05).

[0324] In operation 1j-10, UE 1j-01 can send a UE Capability Information message to base station 1j-02 through the UE Capability Transfer procedure. The UE Capability Information message may include at least one of the following related to whether Automatic Neighbor Relations (ANR) is supported.

[0325] - The indicator for the CGI-InfoEUTRA report used for E-UTRA is a possible indicator. This indicator can be represented by a separate indicator depending on the core type (e.g., EPC or 5GC).

[0326] - An indicator indicating that a CGI-InfoNR report for NR is possible. This indicator can be represented by a separate indicator depending on the UE type according to the above embodiments.

[0327] In operation 1j-15, base station 1j-02 may send an RRC message including measurement configuration information (MeasConfig) to UE 1j-01. For example, the RRC message may be an RRC connection reconfiguration message (RRC reconfiguration message). The measurement configuration information may include at least one of the following.

[0328] -MeasObjectToAddModList

[0329] -MeasObjectToAddModList can include MeasObjectToAddModList IE.

[0330] The -MeasObjectToAddModList IE can include one or more MeasObjectToAddMods.

[0331] - Each MeasObjectToAddMod can include a measObjectId and a MeasObject corresponding to the measObjectId.

[0332] -MeasObject can include one of the measurement objects of NR (i.e., measObjectNR) and the measurement objects of EUTRA (i.e., measObjectEUTRA).

[0333] -reportConfigToAddModList

[0334] -reportConfigToAddModList can include ReportConfigToAddModList IE.

[0335] The ReportConfigToAddModList IE can include one or more ReportConfigToAddMods.

[0336] - Each ReportConfigToAddMod can include a ReportConfigId, and can include a ReportConfigId corresponding to the ReportConfigId.

[0337] - reportConfig can include one of the NR report configuration (i.e., reportConfigNR) and the INTERRAT report configuration (i.e., reportConfigInterRAT).

[0338] In this embodiment, reportConfigNR may include at least one reportConfigId, where reportType is set to reportCGI. ReportCGI may include ReportCGI, and at least one of one or more cellForWhichToReportCGI, useAutonomousGaps indicator, or an indicator indicating whether to include npn-IdentityInfoList (includeNPN-IdentityInfoList indicator) may be set in ReportCGI. Specifically, cellForWhichToReportCGI may include one or more PhysCellIDs (or PhysCellIDrange), and when the useAutonomousGaps indicator is set, UE 1j-01 can obtain system information from neighboring NR cells using autonomous gaps, and when the indicator indicating whether to include npn-IdentityInfoList is set, the operation of including npn-IdentityInfoList in CGI-InfoNR can be performed.

[0339] -MeasIdToAddModList

[0340] -MeasIdToAddModList can include MeasIdToAddModList IE.

[0341] The -MeasIdToAddModList IE can include one or more MeasIdToAddMods.

[0342] Each MeasIdToAddMod can include a MeasID, and also includes a MeasObjectId and a reportConfigId corresponding to the MeasID.

[0343] In operation 1j-20, UE 1j-01 can apply measurement configuration information received from base station 1j-02. For example, when reportType is configured to be the reportCGI in the ReportConfig associated with a specific MeasID (if reportType is set to be the reportCGI in the ReportConfig associated with that MeasID), UE 1j-01 can configure the value of the T321 timer and drive the T321 timer differently depending on which RAT (E-UTRA or NR) is considered based on the MeasObject associated with the MeasID. When considering NR, it can also consider which frequency band (FR1 or FR2) is considered, and whether the ReportConfig associated with the MeasID includes useAutonomousGaps.

[0344] In Operation 1j-25, UE 1j-01 can perform measurements by applying the measurement configuration information received in Operation 1j-20.

[0345] In Operation 1j-30, UE 1j-01 can determine whether a measurement report has been triggered. For example, if a ReportConfig with report type (reportType) set to reportCGI is included for each MeasID included in the MeasIdList belonging to VarMeasConfig, UE 1j-01 can consider a cell suitable for measurement report triggering when a cell with a physical cell identifier that matches the value of cellForWhichToReportCGI included in the ReportConfig belonging to VarMeasConfig is detected in the associated MeasObject (considering a cell detected on the associated MeasObject whose physical cell identifier matches the value of cellForWhichToReportCGI included in the corresponding ReportConfig within the VarMeasConfig to be applied). With reportType set to reportCGI, UE 1j-01 can stop the T321 timer when an SIB1 is acquired for the requested cell or when it is detected that no SIB1 is being sent in the requested cell. Then, UE 1j-01 can include a measurement report entry in the VarMeasReportList used for MeasID, set the ReportsSent number defined in the VarMeasReportList to 0, and execute the measurement reporting procedure. When the T321 timer expires for MeasID, UE 1j-01 can include a measurement report entry in the VarMeasReportList used for MeasID, set the ReportsSent number defined in the VarMeasReportList to 0, and execute the measurement reporting procedure.

[0346] In operation 1j-35, UE 1j-01 can send a Measurement Report message to base station 1j-02. UE 1j-01 can configure the MeasResult in the Measurement Report message for each MeasID in which the measurement reporting process is triggered. For example, the measurement identifier that triggers the measurement report can be set to the MeasID. If at least one available neighboring cell exists to report (if at least one available neighboring cell exists), and the cell indicated by the cell WhichReportCGI is an NR cell, UE 1j-01 can perform the following actions to send the Measurement Report message to base station 1j-02.

[0347] - When the PLMN-IdentityInfoList of CGi-info is obtained from the NR cell indicated by cellForWhichReportCGI (if the PLMN-IdentityInfoList of CGi-info for the cell has already been obtained), the PLMN-IdentityInfoList, trackingAreaCode (if possible), ranac (if possible), Cellidentity, and cellreservedForOperatorUse for each entry of the PLMN-IdentityInfoList, as well as the frequencybandlist (if possible), can be included in the measurement report message (i.e., included in cgi-InfoNR).

[0348] - When the npn-IdentityInfoList of cgi-info is obtained from the NR cell indicated by cellForWhichReportCGI and the includenpn-IdentityInfoList indicator is set, the npn-IdentityInfoList, trackingAreaCode (if possible), ranac (if possible), CellIdentity, and cellReservedForOperatorUse for each entry of npn-IdentityList, as well as cellReservedForOtherUse (if possible) or frequencybandlist (if possible) can be included in the measurement report message (i.e., included in cgi-InfoNR). Unlike the above embodiments, when the includeNPN-IdentityInfoList indicator is not set, when the includeNPN-IdentityInfoList indicator is set but npn-IdentityInfoList is not included in SIB1, or when the includeNPN-IdentityInfoList indicator is not set, UE 1j-01 according to the embodiments of this disclosure does not include npn-IdentityInfoList and cellReservedForOtherUse (if possible) or frequencyBandlist (if possible) in cgi-InfoNR.

[0349] - When the NR cell indication SIB1 indicated by cellForWhichReportCGI is not broadcast via MIB, UE 1j-01 may include noSIB1 in the measurement report message (i.e., included in cgi-InfoNR), which includes ssb-SubCarrierOffset and pdcch-ConfigSIB1 obtained from MIB.

[0350] According to this embodiment, UE 1j-01 includes cellReservedForOtherUse in CGI-Info because base station operation (e.g., handover) can be assisted by reporting the cell type of the indicated NR cell to base station 1j-02.

[0351] Figure 1k This is a flowchart of a process for collecting and reporting cell measurement information in a next-generation mobile communication system according to embodiments of the present disclosure.

[0352] refer to Figure 1k UE 1k-05 can transition from RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) to RRC connected mode (RRC_CONNECTED) through an RRC establishment or RRC recovery procedure with base station 1k-10 (e.g., gNB) (operation 1k-15). Base station 1k-10 can provide UE 1k-05 with measurement configuration information related to the cell identifier using a predefined RRC message (operation 1k-20). The measurement configuration information related to the cell identifier can represent configuration information related to the following two measurement types.

[0353] Type I (ANR)

[0354] - Type II (Minimum Driven Testing (MDT))

[0355] The first type may include the PhysCellID for each radio access technology. The second type may include at least one of LoggingDuration, LoggingInterval, or AreaConfiguration. Area configuration can be configured using at least one of the following methods.

[0356] - Method 1: One or more CellGlobalNRs. The CellGlobalNR includes the first PLMN identifier and the cell identifier mapped to it in the first PLMN-IdentityInfo contained in SIB1.

[0357] -Method 2: One or more tracking region codes.

[0358] - Method 3: One or more tracking region identifiers. Tracking region identifiers may include a PLMN identifier and a tracking region code, and the PLMN identifier can be configured according to Method 1 above.

[0359] - Method 4: Based on the cell type in the above embodiments, a specific cell identifier and npn identifier can be included from the information included in the NPn identifier information list (NPn-IdentityInfoList). The method for configuring a specific cell identifier and npn identifier described in Method 4 can be limited as in Method 1, or it can be unrestricted.

[0360] - Method 5: One or more tracking region identifiers for NPN. The tracking region identifier may include an NPN identifier and a tracking region code, and the NPN identifier can be configured according to Method 4 above.

[0361] In addition, the second type may include PLMN-IdentityList and / or npn-IdentityList.

[0362] When operation 1k-20 includes measurement configuration information related to the cell identifier of the first type, UE 1k-05 can obtain the PLMN-IdentityInfoList from SIB1 of the neighboring cell corresponding to the indicated PhysCellID, and report the measurement results of the current serving cell and the PLMN-IdentityInfoList of the neighboring cells to base station 1k-10 as a predetermined RRC message. In operation 1k-25, according to the above embodiment, when the npn-IdentityInfoList is obtained from SIB1, at least one of npn-IdentityInfoList or cellReservedForOtherUse can be reported to base station 1k-10 as a predetermined RRC message.

[0363] When measurement configuration information related to the second type of cell identifier is included in Operation 1k-20, UE 1k-05 can store it in VarMeasConfig upon receiving LoggingDuration, LoggingInterval, and AreaConfiguration. Furthermore, when PLMN-IdentityList is included, one or more PLMNs included in the received PLMN-IdentityList and registered PLMNs (RPLMNs) can be set as PLMN-IdentityList in VarLogMeasReport (PLMN-IdentityList is set to include RPLMNs and PLMNs included in PLMN-IdentityList in VarLogMeasReport). When PLMN-IdentityList is not included, RPLMNs can be set as PLMN-IdentityList in VarLogMeasReport (PLMN-IdentityList is set to include RPLMNs in VarLogMeasReport). Alternatively, when the npn-IdentityList is included, the RPLMN or registered SNPN included in the received npn-IdentityList, along with one or more NPN-Identities, can be set to the npn-IdentityList in the VarLogMeasReport. When the npn-IdentityList is not included, the RPLMN or registered SNPN can be set to the npn-IdentityList in the VarLogMeasReport. Furthermore, when the LoggingDuration is received, its value can be used to drive the T330 timer.

[0364] In Operation 1k-30, base station 1k-10 can send an RRC connection release message (RRCRelease) to UE 1k-05 in RRC connected mode. Here, UE 1k-05 can switch to either RRC inactive mode (RRC_INACTIVE) or RRC idle mode (RRC_IDLE), depending on whether the received RRC connection release message includes pause configuration information (pause configuration). For example, when an RRC connection release message including pause configuration information is successfully received, UE 1k-05 in RRC connected mode can switch to RRC inactive mode. Conversely, when an RRC connection release message without pause configuration information is successfully received, UE 1k-05 in RRC connected mode can switch to RRC idle mode.

[0365] In Operation 1k-35, UE 1k-05, after switching to RRC idle mode or RRC inactive mode, can camp on a suitable NR cell by performing a cell selection procedure. When UE 1k-05 camps on a suitable cell, UE 1k-05 can be in a normal camping state and regard the camped cell as the serving cell. Even when reselecting a suitable cell in a normal camping state, the suitable cell can still be regarded as the serving cell.

[0366] In Operation 1k-40, UE 1k-05 in a normal camping state can perform login when there exists a PLMN-IdentityList in which the RPLMN is stored in the VarLogMeasReport and the current serving cell belongs to the area configuration. Alternatively, in Operation 1k-40, UE 1k-05 in a normal camping state can perform login when there exists a PLMN-IdentityList in the VarLogMeasReport and the current serving cell belongs to the area configuration. Alternatively, in Operation 1k-40, UE 1k-05 in a normal camping state can perform login when there exists a registered SNPN in the VarLogMeasReport and the current serving cell belongs to the area configuration.

[0367] When it is determined that login will be performed in operation 1k-40, UE 1k-05 can perform login in operation 1k-45. In other words, login can be performed periodically according to LoggingInterval. Furthermore, UE 1k-05 can record the global cell identifier of the currently camped cell in servCellIdentity. The serving cell identifier can represent the first PLMN identifier contained in the first PLMN-IdentityInfo in SIB1 and the cell identifier mapped to it, or it can represent the first npn-Identity in npn-IdentityInfoList and the cell identifier mapped to it. If possible, UE 1k-05 can also perform login for measurements of neighboring cells. Additionally, if possible, UE 1k-05 can perform login from the current cell to the cell ReservedForOtherUse received from SIB1.

[0368] UE 1k-05 can send an RRCSetupRequest or RRCResumeRequest message to base station 1k-10 to transition from idle or inactive mode to connected mode (operation 1k-50). UE 1k-05 receives an RRCSetupRequest or RRCResumeRequest message from base station 1k-10 as a response to the RRCSetupRequest or RRCResumeRequest message (operation 1k-55). UE 1k-05 sends an RRCSetupComplete or RRCResumeComplete message to base station 1k-10 (operation 1k-60). The RRCSetupComplete or RRCResumeComplete message may include an indicator (availability indicator) indicating the presence of a login result value.

[0369] Base station 1k-10 can send an RRC Reconfiguration message to UE 1k-05 to reconfigure the RRC connection (operation 1k-65). UE 1k-05 can send an RRC Reconfiguration Complete message to base station 1k-10 as a response to the RRC Reconfiguration message (operation 1k-70). The RRC Reconfiguration Complete message may include an indicator (availability indicator) indicating that a login result value exists.

[0370] Base station 1k-10 can request the retrieval of stored information using a UEInformationRequest message based on an availability indicator (Operation 1k-75). Upon receiving a UEInformationRequest message, UE 1k-05 can report the information stored in UE 1k-05 (logsMeasReport) to base station 1k-10 using a UEInformationResponse message (Operation 1k-80).

[0371] Figure 11 This is a block diagram of the configuration of a terminal according to an embodiment of the present disclosure.

[0372] like Figure 11 As shown, the terminal according to an embodiment of the present disclosure includes a transceiver 11-05, a controller 11-10, a multiplexer and a reverse multiplexer (or multiplexing and demultiplexing device) 11-15, various higher-level processors (or higher-level processors) 11-20 and 11-25, and a control message processor 11-30.

[0373] Transceiver 11-05 receives data and specific control signals through the forward channel of the serving cell and transmits data and specific control signals through the reverse channel. When multiple serving cells are configured, transceiver 11-05 performs data transmission and reception, as well as control signal transmission and reception, through multiple serving cells. Multiplexer and demultiplexer 11-15 multiplexes data generated by higher-level processors 11-20 and 11-25 or control message processor 11-30, or demultiplexes data received from transceiver 11-05, and sends the multiplexed or demultiplexed data to the appropriate higher-level processor 11-20 or 11-25 or control message processor 11-30. Control message processor 11-30 performs necessary operations by sending control messages to and receiving control messages from the base station. Necessary operations include processing control messages such as those from the MAC control unit (CE), and include reporting CBR measurements and receiving RRC messages for resource pool and terminal operations. Higher-level processors 11-20 and 11-25 represent DRB devices and can be configured for each service. Data generated in user services such as File Transfer Protocol (FTP) or Voice over Internet Protocol (VoIP) is processed and transmitted to multiplexers and demultiplexers 11-15, or data transmitted from multiplexers and demultiplexers 11-15 is processed and transmitted to higher-level service applications.

[0374] Controller 11-10 controls transceiver 11-05 and multiplexer and demultiplexer 11-15 to perform reverse transmission at appropriate times using appropriate transmission resources by recognizing scheduling commands (e.g., reverse authorization) received through transceiver 11-05. The terminal has been described as comprising multiple blocks performing different functions; however, this is merely one embodiment and not a limitation. For example, the functions performed by multiplexer and demultiplexer 11-15 can be performed by controller 11-10.

[0375] Figure 1m This is a block diagram of the configuration of a base station according to an embodiment of the present disclosure.

[0376] Figure 1m The base station includes transceiver 1m-05, controller 1m-10, multiplexer and demultiplexer (or multiplexing and demultiplexing equipment) 1m-20, control message processor 1m-35, various higher-level processors (or higher-level processors) 1m-25 and 1m-30, and scheduler 1m-15.

[0377] Transceiver 1m-05 transmits data and a control signal via a forward carrier and receives data and a control signal via a reverse carrier. When multiple carriers are configured, transceiver 1m-05 performs data transmission and reception, as well as control signal transmission and reception, via multiple carriers. Multiplexer and demultiplexer 1m-20 can multiplex data generated in higher-level processors 1m-25 and 1m-30 or control message processor 1m-35, or demultiplex data received from transceiver 1m-05, to send the data to the appropriate higher-level processors 1m-25 and 1m-30, control message processor 1m-35, or controller 1m-10. Based on the control of controller 1m-10, control message processor 1m-35 can generate a message to be sent to the terminal and send that message to a lower layer. The higher-level processors 1m-25 and 1m-30 can be configured for each service on each terminal and process data generated in user services such as FTP or VoIP and send it to the multiplexer and demultiplexer 1m-20, or process data sent from the multiplexer and demultiplexer 1m-20 and send it to the higher-level service application.

[0378] The controller 1m-10 controls the transceiver 1m-05, the scheduler 1m-15, the multiplexer and demultiplexer 1m-20, and the message processor 1m-35. The scheduler 1m-15 considers the terminal's buffer state, channel state, and terminal activity time, allocates transmission resources to the terminal at appropriate times, and processes or sends signals from the terminal to the transceiver 1m-05.

[0379] Figure 1n This is a block diagram of the configuration of a terminal according to an embodiment of the present disclosure.

[0380] refer to Figure 1n The terminal includes a radio frequency (RF) processor 1n-10, a baseband processor 1n-20, a memory 1n-30, and a controller 1n-40. However, the configuration of the terminal is not limited to this example, and the terminal may include more than [examples of other terminals]. Figure 1n The number of elements shown is less than the number of elements or more elements. Figure 1n The terminals in can correspond to Figure 11 The terminals.

[0381] RF processor 1n-10 performs functions such as signal band conversion and amplification to transmit and receive signals on a radio channel. That is, RF processor 1n-10 can up-convert baseband signals provided by baseband processor 1n-20 into RF band signals and transmit them through an antenna, and can down-convert RF band signals received through the antenna back into baseband signals. For example, RF processor 110 may include transmit filters, receive filters, amplifiers, mixers, oscillators, digital-to-analog converters (DACs), and analog-to-digital converters (ADCs). Although in Figure 1n Only a single antenna is shown, but the terminal may include multiple antennas. RF processor 110 may include multiple RF chains. Furthermore, RF processor 110 can perform beamforming. For beamforming, RF processor 110 can adjust the phase and amplitude of signals transmitted and received through multiple antennas or antenna elements.

[0382] The baseband processor 1n-20 can perform conversion functions between baseband signals and bit strings according to the system's physical layer standards. For example, during data transmission, the baseband processor 1n-20 can generate complex symbols by encoding and modulating the transmitted bit string. Furthermore, during data reception, the baseband processor 1n-20 can reconstruct the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1n-10. For example, according to an Orthogonal Frequency Division Multiplexing (OFDM) scheme, for data transmission, the baseband processor 1n-20 generates complex symbols by encoding and modulating the transmitted bit string, maps the complex symbols to subcarriers, and then configures the OFDM symbols by performing an inverse Fast Fourier Transform (IFFT) and cyclic prefix (CP) insertion. For data reception, the baseband processor 1n-20 can divide the baseband signal provided from the RF processor 1n-10 into OFDM symbol units, reconstruct the signal mapped to the subcarriers by performing a Fast Fourier Transform (FFT), and then reconstruct the received bit string by demodulating and decoding the signal.

[0383] As described above, the baseband processor 1n-20 and the RF processor 1n-10 transmit and receive signals. Therefore, the baseband processor 1n-20 and the RF processor 1n-10 can be referred to as transmitters, receivers, transceivers, or communicators. Furthermore, at least one of the baseband processor 1n-20 or the RF processor 1n-10 may include multiple communication modules to process signals in different frequency bands. These different frequency bands may include ultra-high frequency (SHF) bands (e.g., 2.5 GHz and 5 GHz) and millimeter wave (mmWave) bands (e.g., 60 GHz). A terminal can transmit signals to or receive signals from a base station using the baseband processor 1n-20 and the RF processor 1n-10, and these signals may include control information and data.

[0384] The memory 1n-30 can store data for terminal operation, such as basic programs, application programs, and configuration information. The memory 1n-30 may include storage media, such as read-only memory (ROM), random access memory (RAM), hard disk, CD-ROM or DVD, or combinations thereof. Furthermore, the memory 1n-30 can be configured among multiple memories. According to embodiments of this disclosure, the memory 1n-30 can store programs for the method of applying HARQ to multicast services by the terminal of this disclosure.

[0385] Controller 1n-40 can control the overall operation of the terminal. For example, controller 1n-40 can send and receive signals via baseband processor 1n-20 and RF processor 1n-10. Controller 1n-40 can record data on and read data from memory 1n-30. In this respect, controller 1n-40 may include at least one processor. For example, controller 1n-40 may include a communication processor (CP) for controlling communications and a higher-level application processor (AP) for controlling applications. Furthermore, at least one component in the terminal can be implemented as a chip. According to embodiments of this disclosure, controller 1n-40 may include a multi-connection processor 1n-42, which executes processes for operating in a multi-connection mode. For example, controller 1n-40 can control the terminal to perform... Figure 1f The process is shown in the operation diagram.

[0386] Figure 1o This is a block diagram of the configuration of a base station according to an embodiment of the present disclosure.

[0387] refer to Figure 1o The base station may include an RF processor 1o-10, a baseband processor 1o-20, a memory 1o-30, and a controller 1o-40. However, the configuration of the base station is not limited to this example, and the base station may include more... Figure 1o The elements shown are fewer or more. Figure 1o The base station can correspond to Figure 1m The base station.

[0388] RF processor 10 performs functions such as signal band conversion and amplification to transmit and receive signals on a radio channel. That is, RF processor 10 can up-convert baseband signals provided by baseband processors 1o-20 into RF band signals and transmit them through an antenna, and can down-convert RF band signals received through the antenna back into baseband signals. For example, RF processor 10 may include transmit filters, receive filters, amplifiers, mixers, oscillators, digital-to-analog converters (DACs), and analog-to-digital converters (ADCs). Although in Figure 1oOnly a single antenna is shown, but a base station may include multiple antennas. RF processors 1o-10 may include multiple RF chains. Furthermore, RF processors 1o-10 can perform beamforming. For beamforming, RF processors 10 can adjust the phase and amplitude of signals transmitted and received through multiple antennas or antenna elements.

[0389] The baseband processor 1o-20 can perform conversion functions between baseband signals and bit strings according to the system's physical layer standard. For example, during data transmission, the baseband processor 1o-20 can generate complex symbols by encoding and modulating the transmitted bit string. Furthermore, during data reception, the baseband processor 1o-20 can reconstruct the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1o-10. For example, according to an Orthogonal Frequency Division Multiplexing (OFDM) scheme, for data transmission, the baseband processor 1o-20 generates complex symbols by encoding and modulating the transmitted bit string, maps the complex symbols to subcarriers, and then configures the OFDM symbols by performing an inverse Fast Fourier Transform (IFFT) and cyclic prefix (CP) insertion. For data reception, the baseband processor 1o-20 can divide the baseband signal provided from the RF processor 1o-10 into OFDM symbol units, reconstruct the signal mapped to the subcarriers by performing a Fast Fourier Transform (FFT), and then reconstruct the received bit string by demodulating and decoding the signal.

[0390] The baseband processor 1o-20 and the RF processor 1o-10 transmit and receive signals as described above. Therefore, the baseband processor 1o-20 and the RF processor 1o-10 can be referred to as a transmitter, receiver, transceiver, or communicator. Furthermore, at least one of the baseband processor 1o-20 or the RF processor 1o-10 may include multiple communication modules to process signals in different frequency bands. These different frequency bands may include ultra-high frequency (SHF) bands (e.g., 2.5 GHz and 5 GHz) and millimeter wave (mmWave) bands (e.g., 60 GHz). The base station can transmit signals to or receive signals from the terminal using the baseband processor 1o-20 and the RF processor 1o-10, and these signals may include control information and data.

[0391] Memory 1o-30 may store data for base station operation, such as basic programs, application programs, and configuration information. Memory 1o-30 may include storage media, such as read-only memory (ROM), random access memory (RAM), hard disk, CD-ROM or DVD, or combinations thereof. Furthermore, memory 1o-30 may be configured in multiple memories. According to embodiments of this disclosure, memory 1o-30 may store programs for a method of applying HARQ to multicast services by a base station according to this disclosure.

[0392] Controller 1o-40 can control all operations of the base station. For example, controller 1o-40 can transmit and receive signals via baseband processor 1o-20 and RF processor 1o-10. Controller 1o-40 can record data on and read data from memory 1o-30. In this respect, controller 1o-40 may include at least one processor. For example, controller 1o-40 may include a communication processor (CP) for controlling communications and a higher-level application processor (AP) for controlling applications. Furthermore, at least one component in the base station can be implemented as a chip. According to embodiments of this disclosure, controller 1o-40 may include a multi-connection processor 1o-42, which executes processes for operating in a multi-connection mode. For example, controller 1o-40 can control the base station according to... Figure 1f The operation of the UE shown is executed in accordance with the operation of the corresponding base station.

[0393] The methods of embodiments of this disclosure as described in the claims or in the detailed description thereof can be implemented in hardware, software, or a combination of hardware and software.

[0394] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (e.g., software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that instruct the electronic device to perform the methods according to embodiments of this disclosure as described in the claims and specification.

[0395] Programs (e.g., software modules or software) can be stored in random access memory (RAM), including non-volatile memory such as flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM (CD-ROM), digital versatile disc (DVD), another type of optical storage device, or magnetic tape cassette. Alternatively, programs can be stored in a memory that includes some or all of the above storage media. Multiple such memories may be included.

[0396] The program can also be stored in an attachable storage device accessible via a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WAN), or storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Furthermore, additional storage devices on the communication network can access apparatuses executing embodiments of this disclosure.

[0397] In the above embodiments of this disclosure, elements included in this disclosure are represented in singular or plural form according to the embodiments. However, for ease of explanation, singular or plural forms are suitably chosen, and this disclosure is not limited thereto. Thus, elements represented in plural form may also be configured as a single element, and elements represented in singular form may also be configured as plural elements.

[0398] Furthermore, while specific embodiments have been described in the detailed description of this disclosure, various modifications can be made without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the above embodiments, but should be determined not only by the scope of the appended claims, but also by the equivalents of the claims.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Send UE capability information to the base station, the UE capability information including a first indicator indicating that the UE supports reporting Cell Global Identifier (CGI) information associated with a non-public network (NPN); The base station receives measurement configuration information, which includes reporting configuration information for a new radio (NR), and the reporting configuration information for the NR includes a second indicator indicating the cell in which CGI information will be reported. Obtain system information including an NPN identity information list from neighboring cells, wherein the NPN identity information list includes an NPN identity list and cellReservedForOperatorUse; as well as A measurement report message including the NPN identity information list is sent to the base station. The NPN identity information list includes the NPN identity list and the cellReservedForOperatorUse. The measurement report message also includes cellReservedForOtherUse obtained from the neighboring cell, and The neighboring cells are indicated by the second indicator.

2. The method according to claim 1, wherein, The NPN identity information list also includes at least one of the following: tracking area code, radio access network (RAN) area code, or cell identity.

3. The method according to claim 1, wherein, The system information also includes the cellReservedForOtherUse.

4. The method according to claim 1, wherein, The neighboring cell indicated by the second indicator is an NR cell.

5. The method according to claim 1, wherein, The UE supports NPN, and the neighboring cells are NPN-only cells.

6. A method performed by a base station in a wireless communication system, the method comprising: Receive UE capability information from the user equipment (UE), the UE capability information including a first indicator indicating that the UE supports reporting Cell Global Identifier (CGI) information associated with a non-public network (NPN); The measurement configuration information is sent to the UE, the measurement configuration information including reporting configuration information for new radio NR, the reporting configuration information for NR including a second indicator indicating the cell where CGI information will be reported; as well as When the UE obtains system information including an NPN identity information list from neighboring cells, it receives a measurement report message including the NPN identity information list from the UE. The NPN identity information list includes the NPN identity list and cellReservedForOperatorUse. The measurement report message also includes cellReservedForOtherUse obtained from the neighboring cell, and The neighboring cells are indicated by the second indicator.

7. The method according to claim 6, wherein, The NPN identity information list also includes at least one of the following: tracking area code, radio access network (RAN) area code, or cell identity.

8. The method according to claim 6, wherein, The system information also includes the cellReservedForOtherUse.

9. The method according to claim 6, wherein, The neighboring cell indicated by the second indicator is an NR cell.

10. The method according to claim 6, wherein, The UE supports NPN, and the neighboring cells are NPN-only cells.

11. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as At least one processor, which is coupled to the transceiver and configured to: Send UE capability information to the base station, the UE capability information including a first indicator indicating that the UE supports reporting Cell Global Identifier (CGI) information associated with a non-public network (NPN); The base station receives measurement configuration information, which includes reporting configuration information for a new radio (NR), and the reporting configuration information for the NR includes a second indicator indicating the cell in which CGI information will be reported. Obtain system information including an NPN identity information list from neighboring cells, wherein the NPN identity information list includes an NPN identity list and cellReservedForOperatorUse; as well as A measurement report message including the NPN identity information list is sent to the base station. The NPN identity information list includes the NPN identity list and the cellReservedForOperatorUse. The measurement report message also includes cellReservedForOtherUse obtained from the neighboring cell, and The neighboring cells are indicated by the second indicator.

12. The UE according to claim 11, wherein, The NPN identity information list also includes at least one of the following: tracking area code, radio access network (RAN) area code, or cell identity.

13. The UE according to claim 11, wherein, The neighboring cell indicated by the second indicator is an NR cell.

14. The UE according to claim 11, wherein, The UE supports NPN, and the neighboring cells are NPN-only cells.

15. A base station in a wireless communication system, the base station comprising: transceiver; as well as At least one processor, which is coupled to the transceiver and configured to: Receive UE capability information from the user equipment (UE), the UE capability information including a first indicator indicating that the UE supports reporting Cell Global Identifier (CGI) information associated with a non-public network (NPN); The measurement configuration information is sent to the UE, the measurement configuration information including reporting configuration information for new radio NR, the reporting configuration information for NR including a second indicator indicating the cell where CGI information will be reported; as well as When the UE obtains system information including an NPN identity information list from neighboring cells, it receives a measurement report message including the NPN identity information list from the UE. The NPN identity information list includes the NPN identity list and cellReservedForOperatorUse. The measurement report message also includes cellReservedForOtherUse obtained from the neighboring cell, and The neighboring cells are indicated by the second indicator.

Images