Method and apparatus for reporting UE capabilities using manufacturer-specific identifiers of UE capabilities in next generation mobile communication systems

Abstract

A communication technology and system for integrating a 5G communication system supporting a higher data transmission rate after a 4G system with IoT technology. Based on 5G communication technology and IoT-related technology, certain embodiments can be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail services, security and security-related services, etc.). A method and apparatus can report comprehensive UE capabilities by using a UE identifier instead of reporting UE capabilities by reporting the UE's own capabilities.

Description

Technical Field

[0001] The present disclosure relates to a mobile communication system, and more particularly to a method and apparatus capable of replacing the reporting of UE capabilities with the use of UE identifiers, which eliminates the need to report comprehensive UE capabilities in a method of reporting UE's own capabilities. Background Art

[0002] In order to meet the demand for wireless data traffic that has been growing since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "Beyond 4G Network" or "Post LTE System". 5G communication systems are considered to be implemented in higher (millimeter wave) frequency bands, for example, in the 60GHz band, thereby achieving higher data rates. In order to reduce the propagation damage of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development is underway to achieve system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, active networks, cooperative communications, coordinated multi-point (CoMP), and receiving-end interference elimination. In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have also been developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0003] The Internet, which is a human-centered connection network where people generate and consume information, has now evolved into the Internet of Things (IOT), in which distributed entities (e.g., things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology realized by connection with cloud servers, has emerged. Since technical elements such as "sensing technology", "wired / wireless communication and network facilities", "service interface technology" and "security technology" are required for the implementation of IoT, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been under research recently. Such an IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated among connected things. Through the integration and combination between existing information technology (IT) and various industry applications, IoT can be applied to a variety of fields, including but not limited to smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances and advanced medical services.

[0004] In keeping with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs), which are big data processing technologies described above, can also be considered as an example of the fusion of 5G technology and IoT technology.

[0005] The above information is provided as background information only to assist in understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above is applicable as prior art with respect to the present disclosure. Summary of the invention

[0006] Technical issues

[0007] In the case where a base station requests a UE for the UE's capabilities and the UE reports its capability information in response thereto, a method for performing related operations with reduced signaling overhead is needed.

[0008] Solution to the problem

[0009] One aspect of the present disclosure is to provide an example of a method for replacing a report of UE capabilities by using information of an identifier specified for a UE having the same UE capabilities through a series of processes in which the UE receives a request for UE capabilities from a base station and reports the UE capabilities to the base station in the NR system. In some embodiments, the method described above may employ the use of a manufacturer-specific UE identifier and the use of a PLMN-specific UE identifier. Specifically, the present disclosure provides an example of the general operation of a method for delivering UE capabilities by using a manufacturer-specific UE identifier.

[0010] Another aspect of the present disclosure is to provide an example of allowing release of an additional uplink for a specific UE belonging to a base station that supports both a basic uplink and an additional uplink in an NR system.

[0011] According to one aspect of the present disclosure, certain methods according to the present disclosure are performed by a terminal in a wireless communication system, and the method includes: receiving information from a base station for configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal; communicating with the base station on the UL or the SUL based on the information for configuring the UL and the SUL for the terminal; receiving information on reconfigurationwithsync from the base station; and releasing the SUL when the information on reconfigurationwithsync does not include information associated with the SUL configuration.

[0012] According to one aspect of the present disclosure, certain methods performed by a base station in a wireless communication system include: sending information to a terminal for configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal; communicating with the terminal on the UL or the SUL based on the information for configuring the UL and the SUL for the terminal; and sending information on reconfigurationwithsync to the terminal, wherein the SUL is released if the information on reconfigurationwithsync does not include information associated with the SUL configuration.

[0013] According to certain embodiments of the present disclosure, a terminal in a wireless communication system includes: a transceiver; and a controller, the controller being configured to: receive information configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal from a base station via the transceiver; communicate with the base station on the UL or the SUL based on the information configuring the UL and the SUL for the terminal; receive information on reconfigurationwithsync from the base station via the transceiver; and release the SUL if the information on reconfigurationwithsync does not include information associated with the SUL configuration.

[0014] According to some embodiments disclosed herein, a base station in a wireless communication system includes: a transceiver; and a controller, the controller being configured to: send information configuring an uplink (UL) of the base station and a supplementary uplink (SUL) of the base station for the terminal to a terminal via the transceiver; communicate with the terminal on the UL or the SUL based on the information configuring the UL and the SUL for the terminal; and send information on reconfigurationwithsync to the terminal via the transceiver, wherein the SUL is released if the information on reconfigurationwithsync does not include information associated with the SUL configuration.

[0015] Beneficial Effects of the Invention

[0016] According to some embodiments of the present disclosure, among some of the methods followed by an NR UE to report its capabilities, there is an effect of being able to use an identifier of the UE to replace the reporting of the UE capabilities without having to report the comprehensive UE capabilities.

[0017] Moreover, the configuration method of the base station provided by some embodiments of the present disclosure supports the basic uplink and the additional uplink in the cell. However, since a specific UE is allowed to release the additional uplink, the UE involved can complete the transmission and reception of data through the basic uplink. In this regard, there is an effect of being able to use more wireless resources or being able to use more capabilities of the UE.

[0018] Before commencing the detailed description below, it may be helpful to set forth the definitions of certain words and phrases used throughout this patent document: the words "include" and "comprising" and their derivatives mean including but not limited to; the word "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, being included within, interconnected with, containing, being included within, connected to or connected with, being communicable with, cooperating with, interleaved with, juxtaposed with, proximate to, bound to or with, having, or having the characteristics of, etc.; and the word "controller" means any device, system, or part thereof that controls at least one operation, such device may be implemented by hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0019] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable programming code and embodied in a computer-readable medium. The words "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation by appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transient" computer-readable media excludes wired, wireless, optical or other communication links that transmit transient electrical signals or other signals. Non-transient computer-readable media include media that permanently store data and media that can store data and can overwrite data later, such as rewritable optical disks or erasable memory devices.

[0020] Definitions are provided for certain words and phrases that appear throughout this patent document, those of ordinary skill in the art should understand that in many, if not most, instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] For a more thorough understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0022] Figure 1aAn example of the structure of an LTE system according to various embodiments of the present disclosure is shown;

[0023] Figure 1b An example of a radio protocol structure in an LTE system according to certain embodiments of the present disclosure is shown;

[0024] Figure 1c An example of the structure of a next generation mobile communication system according to some embodiments of the present disclosure is shown;

[0025] Figure 1d An example of a wireless protocol structure of a next generation mobile communication system according to various embodiments of the present disclosure is shown;

[0026] Figure 1e An example of a message structure for reporting UE capabilities in an NR system according to various embodiments of the present disclosure is shown;

[0027] Figure 1f An example of registering and deregistering a UE with a 5G core network in an NR system according to certain embodiments of the present disclosure is shown;

[0028] Figure 1g An example of operations for confirming UE capabilities by using a manufacturer-specific identifier of UE capabilities according to certain embodiments of the present disclosure is shown (referred to herein as a first reference example);

[0029] Figure 1h An example of an operation when confirmation of UE capabilities fails by using a manufacturer-specific identifier of UE capabilities according to various embodiments of the present disclosure is shown (referred to herein as a second reference example);

[0030] Figure 1i An example of operations for requesting a manufacturer-specific identifier of a UE capability and reporting the identifier, in particular generating a manufacturer-specific UE capability, is shown according to certain embodiments of the present disclosure;

[0031] Figure 1j illustrates an example of operations for receiving, by a UE, a request for manufacturer-specific UE capabilities and their identifiers and reporting the same in accordance with certain embodiments of the present disclosure;

[0032] Figure 1k illustrates an example of operations by a base station and a core network to request manufacturer-specific UE capabilities and their identifiers and receive a report therefor in accordance with certain embodiments of the present disclosure;

[0033] Figure 1l An example of a configuration of a UE according to various embodiments of the present disclosure is shown in a block diagram format;

[0034] Figure 1mAn example of a configuration of a base station according to various embodiments of the present disclosure is shown in a block diagram format;

[0035] Figure 2a An example of the structure of an LTE system according to some embodiments of the present disclosure is shown;

[0036] Figure 2b An example of a radio protocol structure in an LTE system according to certain embodiments of the present disclosure is shown;

[0037] Figure 2c An example of the structure of a next generation mobile communication system according to some embodiments of the present disclosure is shown;

[0038] Figure 2d An example of a radio protocol structure of a next generation mobile communication system according to some embodiments of the present disclosure is shown;

[0039] Figure 2e An example of a process in which a base station sends a cell-based uplink configuration to a UE and then releases the specific uplink configuration according to various embodiments of the present disclosure is shown;

[0040] Figure 2f An example of operations performed by a UE when releasing a UE-based uplink in an application-specific cell according to some embodiments of the present disclosure is shown;

[0041] Figure 2g An example of operations performed by a base station when a method of releasing a UE-based uplink in a specific cell is applied according to certain embodiments of the present disclosure is shown;

[0042] Figure 2h An example of the internal structure of a UE according to various embodiments of the present disclosure is shown in a block diagram format; and

[0043] Figure 2i An example of a configuration of a base station according to certain embodiments of the present disclosure is shown in a block diagram format. DETAILED DESCRIPTION

[0044] Discussed below Figures 1a to 2i The various embodiments used to describe the principles of the present disclosure in this patent document are only illustrative and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented by any appropriately arranged system or device.

[0045] Hereinafter, the operating principle according to some embodiments of the present disclosure will be described in detail in conjunction with the accompanying drawings. In the following description of the present disclosure, when the detailed description of the known functions or configurations combined herein may make the subject matter of the present disclosure quite uncertain, such detailed description will be omitted. The words to be described below are words that consider the functional definitions in the present disclosure, and may be different according to the user, user intention or convention. Therefore, the definition of these words can be made based on the content throughout this specification. In the following description, the words used to mark access nodes, the words used to refer to network entities, the words used to refer to messages, the words used to refer to interfaces between network entities, and the words used to refer to various identifiers, etc. are used in an illustrative manner for reasons of convenience. Therefore, the present disclosure is not limited by these words used below, and other words referring to objects with equivalent technical meanings can be used.

[0046] In the following description, the present disclosure uses the terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard for ease of description. However, the present disclosure is not limited to these terms and names, and can be applied to systems conforming to other standards in the same manner.

[0047] Figure 1a An example of a structure of an LTE system according to various embodiments of the present disclosure is shown.

[0048] refer to Figure 1a As a non-limiting example, the wireless access network of the LTE system includes a next-generation base station (evolved Node B; hereinafter referred to as "eNB", "Node B" or "base station") (1a-05, 1a-10, 1a-15, 1a-20), MME (mobile management entity, 1a-25) and S-GW (serving gateway) (1a-30). User equipment (hereinafter referred to as "UE") (1a-35) is connected to an external network via eNB (1a-05 to 1a-20) and S-GW (1a-30).

[0049] exist Figure 1a In a non-limiting example, the eNB (1a-05 to 1a-20) corresponds to an existing Node B of a UMTS (Universal Mobile Telecommunications System) system. The eNB is connected to the UE (1a-35) via a wireless channel and performs more complex tasks than the existing Node B. In the LTE system, since all user traffic including real-time services (e.g., VoIP (Voice over IP) via Internet Protocol Real-time) is provided through a shared channel, a device for collecting and scheduling status information (such as a buffer status of the UE, an available conversion power status, a channel status, etc.) is required. The eNB (1a-05 to 1a-20) is used as such a device.

[0050] According to some embodiments, one eNB often controls several cells. In order to achieve a transmission speed of 100 Mbps, the LTE system uses (for example) orthogonal frequency division multiplexing (hereinafter referred to as "OFDM") within a 20 MHz bandwidth as a wireless access technology. Moreover, the LTE system applies a modulation scheme that is adaptive to the channel state of the UE, and applies adaptive modulation and coding (hereinafter referred to as "AMC") to determine the channel coding rate. S-GW (1a-30) is a device that provides data bearers, which generates or removes data bearers according to the control of MME (1a-25). MME (1a-25) is a device that implements various controls and mobility management for UE and is connected to several base stations.

[0051] Figure 1b An example of a wireless protocol structure in an LTE system according to various embodiments of the present disclosure is shown.

[0052] refer to Figure 1b As a non-limiting example, the wireless protocols of the LTE system include PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40), RLC (Radio Link Control) (1b-10, 1b-35) and MAC (Media Access Control) (1b-15, 1b-30) at the UE and eNB respectively. PDCP (1b-05, 1b-40) compresses and restores IP headers, etc. through operations. The functions of PDCP include:

[0053] -Header compression and decompression (ROHC only)

[0054] -Transmission of user data

[0055] - For RLC AM, sequential delivery of upper layer PDUs during PDCP re-establishment

[0056] - For split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0057] - For RLC AM, duplicate detection of lower layer SDUs during PDCP re-establishment

[0058] - Retransmission of PDCP SDUs at handover for RLC AM and retransmission of PDCP PDUs during PDCP data recovery for split bearers in DC

[0059] -Encryption and decryption

[0060] - Timer-based SDU discard in uplink

[0061] Radio Link Control (hereinafter referred to as "RLC") (1b-10, 1b-35) reconstructs a PDCP PDU (Packet Data Unit) with an appropriate size and performs ARQ operations, etc. The functions of RLC include:

[0062] -Transmission of upper layer PDU

[0063] - Error correction through ARQ (for AM data transmission only)

[0064] -RLC SDU concatenation, segmentation and reassembly (only for UM and AM data transmission)

[0065] - Re-segmentation of RLC data PDU (only for AM data transmission)

[0066] - Reordering of RLC data PDUs (only for UM and AM data transmission)

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

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

[0069] -RLC SDU discard (only for UM and AM data transmission)

[0070] -RLC re-establishment

[0071] like Figure 1b As shown in the illustrative example of , MAC (1b-15, 1b-30) is connected to various RLC layer devices provided in the UE, and by performing operations, multiplexes RLC PDUs into MAC PDUs and demultiplexes RLC PDUs from MAC PDUs. The functions of MAC include:

[0072] - Mapping between logical channels and transport channels

[0073] Multiplex MAC SDUs belonging to one or more different logical channels into a transport block (TB) delivered to the physical layer on a transport channel, or demultiplex MAC SDUs belonging to one or more different logical channels from a transport block (TB) delivered by the physical layer on a transport channel

[0074] -Dispatch information report

[0075] - Error correction through HARQ

[0076] - Priority handling between logical channels of a UE

[0077] - Priority handling between UEs with dynamic scheduling

[0078] -MBMS service identification

[0079] -Transmission format selection

[0080] -filling

[0081] According to certain embodiments, the physical (PHY) layer (1b-20, 1b-25) operates channel coding and modulation of upper layer data, converts the data into OFDM symbols, transmits OFDM symbols via a wireless channel, demodulates OFDM symbols received via a wireless channel, operates channel decoding thereof, and transmits the decoded data to the upper layer. Moreover, in the physical layer, HARQ (Hybrid ARQ) is used to correct any additional errors. One bit is used to transmit information about whether the receiver has received a packet sent from a transmitter. That is, HARQ ACK / NACK information. Downlink HARQ ACK / NACK information for uplink transmission is transmitted via a physical channel of PHICH (Physical Hybrid ARQ Indicator Channel), and uplink HARQ ACK / NACK information for downlink transmission can be transmitted via PUCCH (Physical Uplink Control Signal) or PUSCH (Physical Uplink Shared Channel).

[0082] The PHY layer may include one carrier or multiple frequencies / carriers. The technology of configuring and using multiple frequencies at the same time is called carrier aggregation (hereinafter referred to as "CA"). According to various embodiments, the carrier is used for communication between the user equipment (UE) and the base station (E-UTRAN Node B, eNB). However, the CA technology uses one carrier or multiple secondary carriers in addition to the main carrier, thereby increasing the transmission amount according to the number of secondary carriers. In LTE, the cell using the main carrier in the base station is PCell (primary cell), and the secondary cell is Scell ​​(secondary cell).

[0083] In some embodiments, an RRC (Radio Resource Control) layer exists in the upper PDCP layer of the UE and the base station, respectively, which is not shown in the drawings. The RRC layer can complete the connection for radio resource control and exchange configuration control messages associated with measurement.

[0084] Figure 1c An example of a structure of a next-generation mobile communication system according to certain embodiments of the present disclosure is shown.

[0085] refer to Figure 1cAs a non-limiting example, the radio access network of the next generation mobile communication system includes a next generation base station (new radio node B; hereinafter referred to as "NR-NB") (1c-10) and a new radio core network or next generation core network (hereinafter referred to as "NG-CN") (1c-05). The new radio user equipment (hereinafter referred to as "NR UE") (1c-15) is connected to an external network via the NR NB (1c-10) and the NR CN (1c-05).

[0086] exist Figure 1c In the illustrative example of , NR NB (1c-10) corresponds to the eNB (evolved Node B) of the existing LTE system. NRNB is connected to NR UE (1c-15) via a wireless channel and is capable of providing more excellent services than the existing Node B. In certain embodiments of the next generation mobile communication system, since all user traffic is provided through a shared channel, a device for collecting and scheduling status information (such as the buffer status of the UE, the available transmission power status, the channel status, etc.) is required. In some embodiments, NR NB (1c-10) is used as such a device. In various embodiments, one NR NB often controls multiple cells. In order to achieve ultra-high-speed data transmission compared to the existing LTE, NR NB can have a bandwidth equal to or greater than the existing maximum bandwidth, and can additionally use beamforming technology by using orthogonal frequency division multiplexing (OFDM). Moreover, in some embodiments, adaptive modulation and coding (AMC) is applied to determine the modulation scheme, and a channel coding rate that is adaptive to the channel status of the UE is applied. NR NB (1c-05) plays the role of supporting mobility and setting up bearers and QoS, etc. NR CN is a device that performs various controls and mobility management for UE and is connected to several base stations. Moreover, the next generation mobile communication system can be associated with the existing LTE system, and NR CN is connected to MME (1c-25) through a network interface. In some embodiments, MME is connected to eNB (1c-30) which is an existing base station.

[0087] Figure 1d An example of a wireless protocol structure of a next-generation mobile communication system according to various embodiments of the present disclosure is shown.

[0088] refer to Figure 1d As an illustrative example, the wireless protocol of the next generation mobile communication system includes NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35) and NR MAC (1d-15, 1d-30) at the UE and NR, respectively.

[0089] The functions of NR SDAP (1D-01, 1D-45) include:

[0090] -Transmission of flat data

[0091] - Mapping between QoS flows and DRBs for both DL and UL

[0092] - Marking QoS Flow ID in both DL and UL packets

[0093] -For UL SDAP PDU, reflect the mapping of QoS flows to DRBs

[0094] As for the SDAP layer device, the UE can receive a configuration through an RRC message, which is about whether to use the header of the SDAP layer device for each PDCP layer device, each bearer or each logical channel, or whether to use the function of the SDAP layer device. In the case of setting the SDAP header, the SDAP layer device can command the UE to update or reset the QoS flow of the uplink and downlink and the mapping information for the data bearer through the 1-bit NAS reflection QoS indicator and the 1-bit AS reflection QoS indicator of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to assist in the smooth provision of services.

[0095] The functions of NR PDCP (1d-05, 1d-40) include:

[0096] - Header compression and decompression ROHC only

[0097] -Transmission of user data

[0098] - Sequential delivery of upper layer PDUs

[0099] - Out-of-order delivery of upper layer PDUs

[0100] - Reordering of received PDCP PDUs

[0101] - Duplicate detection of lower layer SDU

[0102] -Retransmission of PDCP SDU

[0103] -Encryption and decryption

[0104] - Timer-based SDU discard in uplink

[0105] In some embodiments, the reordering function of the NR PDCP device is a function of sequentially reordering the PDCP PDUs received by the lower layer based on the PDCP SN (sequence number). This function may include a function of transmitting data to an upper layer in a reordered order or directly transmitting data without considering the order and a function of recording lost PDCP PDUs by rearranging the order of PDCP PDUs. In addition, it may include a function of reporting the status of lost PDCP PDUs to the transmitter and requesting retransmission of lost PDCP PDUs.

[0106] The functions of NR RLC (1d-10, 1d-35) include:

[0107] -Transmission of upper layer PDU

[0108] - Sequential delivery of upper layer PDUs

[0109] - Out-of-order delivery of upper layer PDUs

[0110] - Error correction via ARQ

[0111] -RLC SDU concatenation, segmentation and reassembly

[0112] - Re-segmentation of RLC data PDUs

[0113] - Reordering of RLC data PDUs

[0114] - Duplicate detection

[0115] -Protocol error detection

[0116] -RLC SDU discarded

[0117] -RLC re-establishment

[0118] According to some embodiments, the sequential delivery of the NR RLC device is a function of sending the RLC SDUs received from the lower layer to the upper layer in sequence when the initial RLC SDU is segmented into several RLC SDUs and the segmented RLC SDUs are received, and may include the function of reassembling and sending the received RLC PDUs. It may also include the function of reordering the received RLC PDUs based on the RLC SN or PDCPSN, the function of rearranging the order of the received RLC PDUs and recording the lost RLC PDUs, the function of reporting the status of the lost RLC PDUs to the transmitter, and the function of requesting the retransmission of the lost RLC PDUs. In the case of any lost RLC SDUs, it may include the function of sending only the RLC SDUs before the lost RLC SDUs in sequence to the upper layer. In the case of any lost RLC SDUs, but the predetermined timer expires, it may include the function of sending all RLC SDUs received before the timer to the upper layer in sequence. In the case of any lost RLC SDUs, but the predetermined timer expires, it may include the function of sending all RLC SDUs received until now to the upper layer in sequence. Furthermore, the RLC PDUs may be processed in the order in which they are received (in order of arrival, regardless of the order of sequence numbers, ordinal numbers, etc.) and delivered to the PDCP device without regard to the order (out-of-order delivery). For the individual segments, the segments are stored in a buffer or the segments to be received later are received and then reconstructed into a complete single RLC PDU, which is then processed and delivered to the PDCP device. The NR RLC layer may not include the concatenation function, or this function may be performed on the NR MAC layer or in place of the multiplexing function of the NR MAC layer.

[0119] According to certain embodiments, the out-of-order delivery function of the NR RLC device is a function of delivering the RLC SDUs received from the lower layer directly to the upper layer without considering their order. In the case where the original single RLC SDU is segmented into several RLC SDUs and the segmented RLC SDUs are received, the function of reassembling these RLC SDUs may be included. It may also include the function of storing the RLC SN or PDCP SN of the received RLC PDU, arranging them in sequence, and recording the lost RLC PDU.

[0120] like Figure 1d As shown in the illustrative example of FIG. 1 , the NR MAC (1d-15, 1d-30) may be connected to several NR RLC layer devices included in the UE, and the main functions of the NR MAC may include one or more of the following functions:

[0121] - Mapping between logical channels and transport channels

[0122] -Multiplexing / demultiplexing of MAC SDU

[0123] -Dispatch information report

[0124] - Error correction through HARQ

[0125] - Priority handling between logical channels of a UE

[0126] - Priority handling between UEs with dynamic scheduling

[0127] -MBMS service identification

[0128] -Transmission format selection

[0129] -filling

[0130] According to certain embodiments, the NR PHY layer (1d-20, 1d-25) can operate channel coding and modulation of upper layer data to turn them into OFDM symbols, and send the OFDM symbols via a wireless channel, demodulate the OFDM symbols received through the wireless channel, operate channel decoding thereof, and send the decoded data to an upper layer link.

[0131] Figure 1e An example of a message structure for reporting UE capabilities in an NR system according to certain embodiments of the present disclosure is shown.

[0132] In some embodiments, a UE (1e-01) traverses a process to report the capabilities supported by the UE to a serving base station (1e-02), and this purpose is achieved when the UE is connected to the base station concerned. In some embodiments, in operation 1e-05, the base station submits a UE capability query message to the UE in a connected state, which requests a report on the UE capabilities. The message may include a request for UE capabilities by the base station based on each RAT type. The request based on the RAT type may include frequency band information requested according to the priority of the RAT type. Moreover, the UE capability query message may request multiple RAT types in one RRC message container, or submit a UE capability query message including a request based on the RAT type to the UE several times. That is, the UE capability query is repeated several times in 1e-05, and the UE can construct a corresponding UE capability information message, match a response to the request concerned, and then report the response. In the next generation mobile communication system, UE capabilities for MR-DC including NR, LTE, and EN-DC can be requested. For reference, the UE capability query message is generally submitted in the initial stage after the UE connection is completed, but it can also be requested under any conditions when the base station needs it.

[0133] In the above operation, the UE that has received a request to report UE capabilities from the base station will construct UE capabilities according to the RAT type and frequency band information requested by the base station. The following describes a method for constructing UE capabilities in an NR system performed by the UE according to various embodiments.

[0134] 1. The UE may receive a request for part or all of the RAT types of LTE, EN-DC, and NR from the base station (as a request for UE capabilities), and may receive a list of LTE and NR bands at the same time. The UE may construct a band combination (BC) for EN-DC and NR standalone networking (SA). That is, based on the bands requested by the FreqBandList from the base station, a candidate list of BCs for EN-DC and NR SA is constructed. The operations involved may be defined as operations for compiling candidate band combinations. Moreover, the priorities of these bands are determined in the order described in the FreqBandList. The operations involved may be performed once regardless of the RAT type or may be repeated according to each RAT type.

[0135] In the following operations, the procedures involved are performed for each RAT type and these procedures are operated according to the priority of NR, MR-DC and LTE, so that:

[0136] 2. If the "eutra-nr-only" flag or the "eutra" flag is set as the RAT type of the UE capability request message, the RAT type used for the NR SA BC is completely removed from the candidate list of BCs constructed above. This only happens when the LTE base station (eNB) requests the "eutra" capability.

[0137] 3. Then, the UE removes the fallback BC from the candidate list of BCs constructed in the above operation. The fallback BC is the case where the frequency band corresponding to at least one SCell is removed from any BC superset. Since the BC superset may have covered the fallback BC, it is possible to omit the fallback BC. In some embodiments, this operation is also applicable to EN-DC, that is, to LTE bands. The BC retained after this operation is the final "BC candidate list".

[0138] 4. The UE selects a BC suitable for the requested RAT type from the final "BC candidate list" and selects the BC to be reported from it. In this operation, the UE constructs the supportedBandCombinationList in a predetermined order. That is, the UE constructs the BC and UE capabilities to be reported according to the order of the previously set RAT types (nr→eutra-nr→eutra). Moreover, a featureSetCombination for the constructed spportedBandCombination is constructed, and a list of "candidate feature set combinations" from the candidate list of BCs (from which the list of fallback BCs (including capabilities at the same or lower level) is removed) is constructed. According to various embodiments, the "candidate feature set combinations" include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations of UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0139] 5. Furthermore, if the requested ratType is eutra-nr and there is an impact on the supportedBandCombination of the concerned EN-DC or MR-DC, then featureSetCombinations are adaptively set for the concerned ratType and are all contained in two containers of UE-MRDC Capabilities and UE-NR Capabilities. However, in some embodiments, the feature set of NR only includes UE-NR-Capabilities.

[0140] According to certain embodiments, after building the UE capabilities, the UE delivers a UE capability information message including the UE capabilities to the base station in 1e-10. Based on the UE capabilities received from the UE, the base station thereafter performs appropriate scheduling and transmission and reception management for the concerned UE.

[0141] In certain embodiments, as part of a method for reducing the complexity of existing processes for requesting and reporting UE capabilities applicable to NR systems, the present disclosure contemplates a method for implementing an alternative to UE capability reporting by an identifier (ID) representing UE capabilities. Generally, UEs are set to have the same UE capabilities according to the UE serial number or manufacturer-specific model specified by the manufacturer. Moreover, in the case where the base station and the core network have capabilities for the UE in question, it is possible to store and use the UE capabilities. If the same UE capabilities are reported for the same UE model, the base station and the core network will always receive the same UE capability report for the UE model in question, so they can perform optimizations for the operations in question. That is, if there is an identifier representing the capabilities of the UE model in question and the identifier is reported by the UE, the base station and the core network are able to determine the identifier in question and retrieve the UE capabilities. In order to use the identifier representing the above UE capabilities, there are two options as described below:

[0142] 1. Manufacturer-specific identifier (ID) of UE capabilities: It is possible to have an identifier for each manufacturer and each UE model (or for UEs of the same manufacturer with the same UE capabilities), which can be an identifier that uniquely represents the radio link UE capabilities of the UE. Moreover, the UE identifier concerned can represent all capabilities of the UE.

[0143] 2. PLMN-specific identifier (ID) of UE capabilities: In the case where the above-mentioned manufacturer-specific identifier of UE capabilities is not provided or the base station and core network involved cannot distinguish the identifier, an identifier that can be replaced is required. The base station and the core network can provide the UE-specific identifier according to the capabilities of the UE. The identifier involved should be applicable to the serving PLMN and explicitly allocated to the PLMN.

[0144] Among the operations of reporting UE capabilities through these two identifiers, certain embodiments of the present disclosure provide operations for requesting and providing a manufacturer-specific identifier of UE capabilities and confirming UE capabilities.

[0145] Figure 1f An example of registering and deregistering a UE with a 5G core network in an NR system according to various embodiments of the present disclosure is shown.

[0146] refer to Figure 1fAs a non-limiting example, until the UE is initially registered with the core network in the NR system, the UE is in a registration management (RM) blank state with respect to the core network involved in operation 1f-05. Then, if in operation 1f-20, the UE involved is activated in N1 mode (a mode capable of connecting to a 5G core network), the UE exists in the RM-DEREGISTRATION state for the core network involved as shown in 1f-10. That is, this means that the UE involved is able to connect to the 5G core network, but the connection and registration process has not yet been completed. The UE in this state will attempt to connect and initially register with the 5G core network in operation 1f-30. If this operation is completed, the UE transitions to the RM-REGISTRATION state in operation 1f-15. Then, even if the UE performs a process such as changing the serving cell, this is not an operation for initial registration (1f-40), so the UE maintains the RM-REGISTRATION state. If the UE is deregistered in operation 1f-35, the UE transitions to the RM-DEREGISTRATION state again. In some embodiments, if deactivation of the N1 mode is applied in the concern state, the UE transitions to the RM-NULL state.

[0147] Figure 1g An example (referred to herein as a first reference example) of an operation of confirming UE capabilities by using a manufacturer-specific identifier of UE capabilities according to various embodiments of the present disclosure is illustrated.

[0148] refer to Figure 1gAs a non-limiting example, a UE (1g-01) in an RRC IDLE state may perform an RRC connection procedure to a specific NR base station (gNB) (1g-02) in operation 1g-05. After performing the RRC connection procedure in question, a NAS message (e.g., ATTACH / REGISTRATION REQUEST) including a manufacturer-specific identifier of UE capabilities may be delivered to a core network (CN, 1g-03) (1g-10) to which the base station in question is connected. The core network having received the message identifies the manufacturer-specific identifier of the UE capabilities in operation 1g-15 and checks whether the UE capabilities corresponding to the identifier in question are stored, and is able to confirm the UE capabilities mapped with the identifier in question. In some embodiments, the manufacturer-specific identifier of the UE capabilities may exist within the core network as a table mapped with the UE capabilities. Thereafter, the UE and the core network perform a process of setting up NAS security (authentication) in operation 1g-20, and the core network delivers the UE capabilities that have been known as a result of confirming the manufacturer-specific identifier of the UE capabilities to the base station in operation 1g-25. The message may be included in an INTIAL CONTEXT SETUP REQUEST message (NAS message). In the above operations, the core network is able to deliver the manufacturer-specific identifier of the UE capabilities received from the UE together. In various embodiments, in operation 1g-30, the base station stores the UE capabilities received from the core network, and is then able to reflect the UE capabilities in the configuration of the RRC with the UE. Since the relevant base stations have been notified of the UE capabilities through these processes, the base stations may not trigger an operation to request the UE capabilities from the UE.

[0149] Figure 1h An example of an operation when confirmation of UE capabilities fails by using a manufacturer-specific identifier of UE capabilities according to various embodiments of the present disclosure is shown (referred to herein as a second reference example).

[0150] refer to Figure 1hAs a non-limiting example, a UE in an RRC IDEL state (1h-01) can perform an RRC connection procedure to a specific NR base station (gNB) (1h-02) in operation 1h-05. After the relevant RRC connection procedure is performed, a NAS message (e.g., ATTACH / REGISTRATION REQUEST) including a manufacturer-specific identifier of the UE capability can be delivered to a core network (CN) (1h-03) (1h-10) to which the relevant base station is connected. The core network having received the message identifies the manufacturer-specific identifier of the UE capability in operation 1h-15 and confirms whether the UE capability corresponding to the relevant identifier is stored, but cannot restore the UE capability mapped with the relevant identifier. For this operation, the manufacturer-specific identifier of the UE capability can exist in the core network in the form of a table mapped with the UE capability. However, in this process, the manufacturer-specific identifier of the UE capability provided by the UE may not be stored, and the manufacturer-specific identifier of the relevant UE capability may not be recognized. Then, the UE and the core network perform a process of setting up NAS security (authentication) in operation 1h-20. According to certain embodiments, in operation 1h-25, the core network notifies the base station that there is no UE capability about the UE, and can submit an INITIAL CONTEXT SETUP REQUEST message (NAS message) requesting UE capability to the base station. In the above operation, the core network can submit the manufacturer-specific identifier of the UE capability received from the UE together. In the above operation, the base station confirms the manufacturer-specific identifier of the UE capability received from the core network. If recovery is possible because the base station has UE capability information of the identifier concerned, the base station reports it to the core network, and then the UE capability request process can be omitted.

[0151] refer to Figure 1hAs a non-limiting example, in operation 1h-30, the base station confirms the request for UE capabilities received from the core network and can trigger the UE capability request. That is, in operation 1h-35, the UECapabilityEnquiry message (including the RAT type and filtering information for the UE capability request) is delivered to the UE. In operation 1h-40, the UE reflects the involved RAT type and filtering information and constructs the UE capabilities in response to the UE capability request message received in operation 1h-35, and then delivers the UECapabilityInformation message to the base station. In the above operations, the UE can include the manufacturer-specific identifier of the UE capabilities into the UECapabilityInfomation message. In operation 1h-45, the base station stores the UE capability information received from the UE. If the manufacturer-specific identifier of the UE capabilities is received from the UE together, the information involved is stored together. In operation 1h-50, the base station delivers the UECapabilityInfomation message received from the UE to the core network. According to certain embodiments, the UE capabilities involved may include filtering information in different containers according to each RAT type and may be delivered as is (UE-CapabilityRAT-ContainerList together with the filter). In operation 1h-55, the core network stores the UE capabilities received in the above operation and updates the UE capability mapping table including the manufacturer-specific identifier of the UE capabilities and the UE capabilities. Thereafter, the stored UE capabilities may be applied to the UE that provides the manufacturer-specific identifier of the UE capabilities involved.

[0152] Figure 1i Examples of operations for requesting manufacturer-specific identifiers of UE capabilities and reporting the identifiers, and in particular, generating manufacturer-specific UE capabilities, are shown in accordance with certain embodiments of the present disclosure.

[0153] refer to Figure 1iAs a non-limiting example, a UE (1i-01) in an RRC IDLE state may perform an RRC connection procedure to a specific NR base station (gNB, 1i-02) in operation 1i-05. After performing the RRC connection procedure in question, the UE may submit a NAS message (e.g., ATTACH / REGISTRATION REQUEST) including a manufacturer-specific identifier of the UE capabilities and a PLMN-specific identifier of the UE capabilities to a core network (CN) (1i-03) (1i-10) to which the base station in question is connected. In the above operations, in a case where the UE is in a previously connected state and there are PLMN-specific UE capabilities allocated during the UE capability submission process, the PLMN-specific identifier of the UE capabilities may be selectively included and submitted as a table including multiple entries. Moreover, the PLMN-specific identifier of the UE capabilities may be selected taking into account the PLMN of the base station that is currently in a state of being connected to the UE in question. That is, in some embodiments, only the identifier of the same PLMN as the serving cell may be reported. The core network that has received the PLMN identifier confirms the manufacturer-specific identifier of the UE capability in question and the PLMN-specific identifier of the UE capability in operation 1i-15, thereby confirming whether the UE capability of the identifier in question is stored, but may not restore the UE capability mapped with the identifier in question.

[0154] In some embodiments, for this operation, the manufacturer-specific identifier of the UE capability and the PLMN-specific identifier of the UE capability may exist in the core network as a mapping table. However, in this process, the manufacturer-specific identifier of the UE capability and the PLMN-specific identifier of the UE capability provided by the UE may not be stored, and the manufacturer-specific identifier of the UE capability and the PLMN-specific identifier of the UE capability involved may not be identified. Then, the UE and the core network perform a process of setting up NAS security (authentication) in operation 1i-20, and notify the base station of the absence of UE capability in operation 1i-25. According to various embodiments, an INITIAL CONTEXT SETUP REQUEST message (NAS message) requesting UE capability may be delivered to the base station.

[0155] In the above operations, the core network may request all UE capabilities from the base station, which may be used to obtain manufacturer-specific UE capabilities. Moreover, the core network may hand over the manufacturer-specific identifier of the UE capabilities received from the UE. In the above operations, the base station confirms the manufacturer-specific identifier of the UE capabilities that has been received from the core network. In some embodiments, if the base station has UE capability information for the identifier in question and it is possible to recover the UE capabilities, then the core network is notified of this and the UE capability request procedure is then omitted.

[0156] The base station confirms in 1i-30 that it has received the UE capability request from the core network and is able to trigger the UE capability request. That is, the UECapabilityEnquiry message (including the RAT type and filtering information for requesting UE capabilities) is delivered to the UE. The RRC message may include an option to request all UE capabilities, i.e., the manufacturer-specific UE capabilities in the filter. That is, the information for requesting all capabilities may be included in the filtering information, or the information may be delivered in an unfiltered state by omitting the filtering information according to each RAT type, and this may be used to indicate that all UE information should be reported. Moreover, the RRC message may include an identifier indicator indicating whether the UE is able to provide UE capabilities.

[0157] According to various embodiments, if the UE has an indicator indicating whether it is capable of providing the UE capability identifier of the base station (or an indicator indicating that the manufacturer-specific identifier of the UE capability is invalid) and a PLMN-specific identifier of the UE capability mapped to the UE request including the RAT type and filtering, then the UE is able to submit a UECapabilityInformation message including only the identifier concerned to the base station in operation 1i-40. However, if the UE does not have a PLMN-specific identifier of the UE capability mapped to the request from the base station, the UE reflects the RAT type and filtering information concerned as in the existing process, thereby generating and reporting the UE capability and constructing the UE capability in operations 1i-40 and 1i-45, and then submitting the UECapabilityInformation message to the base station. The operations below are dedicated to a process according to which the UE is requested from the base station to report the manufacturer-specific UE capability, and the UE reports the capability.

[0158] According to some embodiments, in operation 1i-40, the UE generates a UE capability message (UE capability information) in response to a request from the base station for its own UE capability. If the message in question exceeds 9000 bytes (the maximum size of a PDCP PDU), segmentation is applied. That is, it can be known that the entire UE capability information message is segmented into segments each having a size of 9000 bytes, and the last segment can be a segment having a remaining size (the sum of each segmented RRC message is subtracted from the entire message size). Moreover, assuming that a request for all UE capabilities (all capability indicators or unfiltered requests) is received in operation 1i-35, the UE can include the entire UE capability and an indicator indicating that the UE capability to be reported is a manufacturer-specific UE capability or a manufacturer-specific identifier of the UE capability. However, if the UE capability to be reported is not equivalent to the manufacturer-specific UE capability (all UE capabilities), information (indicator) indicating that the UE capability to be reported is not a manufacturer-specific UE capability (all UE capabilities) is included in the UE capability information message, and the message will be delivered as is (1i-45). According to certain embodiments, when delivering the message, each RAT type is included in each container present in UE-CapabilityRAT-ContainerList and delivered as is.

[0159] When the UE submits the manufacturer-specific identifier of the UE capability and the UE capability included together in the message in operation 1i-45, the base station and the core network store the submitted UE capability in a manner that associates the submitted UE capability with the manufacturer-specific identifier of the UE capability, which identifier can be interpreted and used as the UE capability later. The following operation is dedicated to the case where the UE does not submit the manufacturer-specific UE capability in operation 1i-45. That is, in the case where the UE submits the UE capability together with an indicator indicating that the UE capability is not a manufacturer-specific UE capability, the UE capability information submitted in operation 1i-50 is stored in an internal buffer (memory) together with the RAT type and filtering information requested by the base station associated therewith. In addition, the UE is able to store the registered PLMN information of the connected relevant service cell from the system information (SIB1) that has been received by the relevant service cell. It can be inferred that the UE stores the PLMN information, RAT type and filtering information and the reported UE capability in a group in the operation concerned.

[0160] like Figure 1iAs shown in the illustrative example of , in operation 1i-55, the base station submits the UECapabilityInformation message that has been received from the UE to the core network, and the UE capabilities involved include filtering information in different containers according to each RAT type, which will be transmitted as is (UE-CapabilityRAT-ConainterList together with the filter). Moreover, the message may include an indicator indicating that the UE capability is not a manufacturer-specific UE capability submitted from the UE. In operation 1i-60, the core network confirms that the UE capability has been received in the above operation. In the case where the PLMN-specific identifier of the UE capability mapped with the UE capability reported by the UE for the filtering information involved and the requested RAT type exists in the stored table, the identifier involved is assigned to the PLMN-specific identifier of the UE capability. However, if the reported UE capability is not available to the core network and is new, the core network can assign a new UE capability PLMN-specific identifier to it.

[0161] According to some embodiments, in operation 1i-65, the core network submits to the UE a PLMN-specific identifier of a UE capability adaptively attached to the UE capability reported by the UE through a NAS message (e.g., ATTACH / REGISTRATION RESPONSE). The message may include index information indicating whether the identifier is an identifier of any UE capability, or may be provided together with the RAT type and filtering information mapped to the UE capability involved. The reason why the operations involved are needed is that, in some embodiments, operations 1i-35, 1i-40, and 1i-45 are not completed at one time, but they may be completed successively. For example, the base station may submit an NR-associated UE capability request for the RAT type and filter in operation 1i-35. After the UE capability involved has been received from the UE in operation 1i-45, the base station repeats operation 1i-35 again and requests EN-DC UE capability, and receives a report on the UE capability involved in operation 1i-45. In this case, the PLMN-specific identifiers of the UE capabilities of the two UE capabilities that have been received successively should be distinguished to implement allocation. Therefore, index information distinguishing them may be included (eg, the UE's first capability report is set to 1, and the UE's second capability report is set to 2), or the archive information may be delivered together.

[0162] Moreover, in some embodiments, the method of allocating PLMN-specific identifiers of UE capabilities in operation 1i-60 of the core network can be applied in different ways according to network implementation. For example, the UE capabilities involved can be specified only for the case where a UE capability report for a specific UE is received and the number of UE reports providing the same UE capabilities as the UE capabilities involved is greater than a predetermined critical value (N), and the PLMN-specific identifier of the UE capabilities can be allocated thereto. That is, in some embodiments, an algorithm is required that does not allocate a PLMN-specific identifier of a specific UE capability for the case where there are only a few UE capability reports.

[0163] refer to Figure 1i As a non-limiting example, in operation 1i-70, the UE maps the PLMN-specific identifier of the UE capability that has been received from the core network in operation 1i-65 with the UE capability storage group reported and stored by the UE in operation 1i-50, and performs the latest storage. That is, the UE gathers the PLMN-specific identifier of the UE capability, the registered PLMN information, the RAT type and the filtering information, and the reported UE capability in the operation concerned and stores them in a group. Then, the PLMN-specific identifier of the UE capability assigned to represent the UE capability concerned can be used. Moreover, in the above operation, the number of PLMN-specific identifiers of the UE capability that the UE can store may be limited. If the UE capability for the PLMN-specific identifier of the new UE capability should be stored in a state where the UE has stored the predetermined number of PLMN-specific identifiers of the UE capability, the PLMN-specific identifier of the UE capability that has been previously stored and the UE capability group concerned can be erased and updated to a new value. Moreover, in some embodiments, it is possible to perform an operation to erase information for other PLMNs, thereby leaving only information for the same PLMN in the above operation.

[0164] Then, in operation 1i-75, the core network may deliver the PLMN-specific identifier of the UE capability that has been delivered to the UE to the base station via an N1 message, and the base station stores the PLMN-specific identifier of the UE capability, the registered PLMN information, the RAT type and filtering information, and the reported UE capability into a group based on the PLMN-specific identifier of the UE capability received in operation 1i-80, the UE capability received in operation 1i-45, and the RAT type and filtering information that have been delivered to the UE in operation 1i-35. Then, in the case where the UE uses the PLMN-specific identifier assigned to the UE capability representing the UE capability concerned, the base station that has received the PLMN-specific identifier of the UE capability may not trigger a UE capability request.

[0165] Figure 1jAn example of operations of receiving, by a UE, a request for manufacturer-specific UE capabilities and their identifiers and reporting the same is shown in accordance with certain embodiments of the present disclosure.

[0166] refer to Figure 1j As a non-limiting example, in operation 1j-05, the UE may reside on a specific serving cell and transition to an RRC connected state. Immediately after connecting to the concerned cell, the UE submits an identifier of the UE capabilities possessed by the UE to the core network connected to the concerned base station through a NAS message (e.g., an INITIAL ATTACH / REGISTRATION REQUEST message) in operation 1j-10. The identifiers concerned may include a manufacturer-specific identifier of the UE capabilities and a PLMN-specific identifier of the UE capabilities. According to certain embodiments, in a state where the PLMN-specific identifier of the UE capabilities has not yet been allocated, only the manufacturer-specific identifier of the UE capabilities may be included. In operation 1j-15, in the event that the core network or base station fails to restore the UE capabilities for the UE capability identifier that the UE has submitted, the UE will receive a message requesting a report of the UE capabilities through the base station. The UE capability request message may include a filter requesting all UE capabilities. Otherwise, the message may be submitted in an unfiltered state, where, by omitting all filtering information according to each RAT type, it can be used to imply that all UE information will be reported.

[0167] In operation 1j-20, the UE generates UE capability information in response to the above UE capability request message. That is, a UE capability message is generated taking into account that filtering information has been requested in operation 1j-15. If the size of the message exceeds 9000 bytes, the UE capability information is segmented to generate segmented information. Moreover, in some embodiments, in operation 1j-25, it is determined whether the UE capability information generated in operation 1j-20 is the same as the manufacturer-specific total UE capabilities (1j-30). If the generated UE capability information is the same as the manufacturer-specific total UE capabilities, the total capability information is reported in operation 1j-35. At the same time, an indicator indicating that the UE capability involved is the manufacturer-specific total UE capabilities and the manufacturer-specific total UE capabilities are included therein and reported to the base station.

[0168] like Figure 1jAs shown in the illustrative example of , in operation 1j-25, it is determined whether the UE capability information generated in operation 1j-20 is the same as the manufacturer-specific all UE capabilities (1j-30). When the generated UE capability information is different from the manufacturer-specific all UE capabilities, the UE includes an indicator indicating that the reported UE capabilities are not the manufacturer-specific all UE capabilities in operation 1j-40 and submits it. In operation 1j-45, the UE stores the reported UE capabilities in a buffer (memory). Then, in operation 1j-50, if the PLMN-specific identifier of the UE capability is indicated via a NAS message, the stored UE capability is associated with the PLMN-specific identifier of the UE capability, and then stored and used. That is, in the operation concerned, the UE stores the PLMN-specific identifier of the UE capability, the registered PLMN information, the RAT type and filtering information, and the reported UE capability into a group. Then, the PLMN-specific identifier assigned to the UE capability representing the concerned UE capability can be used.

[0169] Moreover, in the above operation, the number of PLMN-specific identifiers of UE capabilities stored by the UE may be limited. If the UE capability for the PLMN-specific identifier of a new UE capability should be stored in a state where the UE has stored the predetermined number of PLMN-specific identifiers of UE capabilities, the previously stored PLMN-specific identifier of the UE capability and the UE capability group concerned may be erased and updated to a new value. Furthermore, it is possible to perform an operation of erasing information for other PLMNs, thereby leaving only information for the same PLMN in the above operation.

[0170] Figure 1k An example of operations of requesting manufacturer-specific UE capabilities and their identifiers and receiving a report therefor by a base station and a core network according to various embodiments of the present disclosure is shown.

[0171] like Figure 1kAs shown in the non-limiting example of, in operation 1k-05, if the specific UE resides on the cell concerned, the base station performs an RRC connection process and transitions the UE to a connected state. The core network connected to the base station can receive an identifier of the UE capabilities possessed by the UE via a NAS message (e.g., an ATTACH / REGISTRATION REQUEST message). The identifier concerned may include a manufacturer-specific identifier of the UE capabilities and a PLMN-specific identifier of the UE capabilities. In some embodiments, in a state where the PLMN-specific identifier of the UE capabilities is not allocated, only the manufacturer-specific identifier of the UE capabilities may be included. In operation 1k-10, the core network determines whether the UE has UE capabilities based on the received identifier. If the UE concerned does not have manufacturer-specific UE capabilities, the core network can command the base station to start a process of requesting the required UE capabilities. The base station may receive an indicator requesting all UE capabilities from the core network in the operation concerned, or the core network may allow any necessity for all UE capabilities to appear within the base station.

[0172] According to some embodiments, in operation 1k-15, the base station can deliver a message requesting UE capabilities to the UE, and the message in question may include a RAT type and filtering information (such as frequency) or an indicator indicating that the request in question is to obtain manufacturer-specific UE capabilities of the UE. The above UE capability request message may include a filter requesting all UE capabilities, or the message may be delivered in an unfiltered state, omitting the filtering information according to each RAT type, which may be used to mean that all UE capability information should be reported.

[0173] In operation 1k-20, the UE submits UE capability information to the base station in response to the UE capability request message, and the base station decodes and interprets the received information concerned, thereby obtaining the UE capabilities. In the case where the indicator indicates whether the UE capability information received in operation 1k-25 is the same as the manufacturer-specific total UE capabilities, or the manufacturer-specific identifier of the UE capabilities is in the received message, the base station determines that the reported UE capabilities are the manufacturer-specific total UE capabilities and is able to store the concerned UE capabilities in a buffer and memory. The received UE capability information and indicator information are submitted to the core network in a NAS message (1k-30).

[0174] In the case where the indicator indicates whether the UE capability information received in operation 1k-25 is the same as the manufacturer-specific all UE capabilities, or the manufacturer-specific identifier of the UE capabilities is not in the received message, the base station determines that the reported UE capabilities are not the manufacturer-specific all UE capabilities and is able to store the relevant UE capabilities in the buffer and memory. The received UE capability information and indicator information are delivered to the core network in a NAS message (1k-40). Even in the case of delivering the relevant message, an indicator indicating that the reported UE capabilities are not the manufacturer-specific all UE capabilities may be included. Figure 1k In an illustrative example of , in operation 1k-45, if the base station receives a PLMN-specific identifier for the UE capabilities of the UE capabilities concerned from the AMF (core network), the base station associates the identifier with the stored UE capabilities and stores and manages them. They are then used for configuration of the UE.

[0175] Figure 1l An example of a configuration of a UE according to various embodiments of the present disclosure is shown in a block diagram format.

[0176] like Figure 1l As shown in the illustrative example, the UE according to an exemplary embodiment of the present disclosure includes a transceiver (1l-05), a controller (1l-10), a multiplexing and demultiplexing unit (1l-15), various uplink processors (1l-20, 1l-25) and a control message processor (1l-30).

[0177] The transceiver (11-05) receives data and predetermined control signals through the forward channel of the service cell, and transmits data and predetermined control signals through the reverse channel. When multiple service cells are set, the transceiver (11-05) performs data transmission and reception and control signal transmission and reception through the multiple service cells. The multiplexing and demultiplexing unit (11-15) plays the role of multiplexing the data generated in the uplink processor (11-20, 11-25) or the control message processor (11-30), or demultiplexing the data received by the transceiver (11-05), and submitting the data to the uplink layer processor (11-20, 11-25) or the control message processor (11-30).

[0178] According to certain embodiments, the control signal processor (11-30) receives and sends control messages from the base station and performs necessary operations on it. The operation includes the function of processing control messages such as RRC messages and MAC CE, the reporting of CBR measurement values, and the reception of resource pools and RRC messages used for operation by the UE. The uplink layer processor (11-20, 11-25) refers to a DRB device and can be configured according to each service. Data generated by user services such as FTP (File Transfer Protocol) or VoIP (Voice over Internet Protocol) is processed and delivered to the multiplexing and demultiplexing unit (11-15), or data delivered from the multiplexing and demultiplexing unit (11-15) is processed and delivered to the service application of the uplink layer. The controller (11-10) confirms the scheduling instruction received by the transceiver (11-05), for example, reverse permission and control of the transceiver (11-05) and the multiplexing and demultiplexing unit (11-15) so that reverse transmission to the appropriate transmission resource time can be properly performed.

[0179] The present disclosure has been described with reference to an example of a UE including a plurality of blocks and each block performing a different function, but this only constitutes an embodiment of the present disclosure and the present disclosure is not limited thereto. For example, the functions performed by the multiplexing and demultiplexing unit (11-15) may be performed by the controller (11-10) itself.

[0180] Figure 1m An example of a configuration of a base station according to certain embodiments of the present disclosure is shown in a block diagram format.

[0181] refer to Figure 1m As a non-limiting example, the base station equipment includes a transceiver (1m-05), a controller (1m-10), a multiplexing and demultiplexing unit (1m-20), a control message processor (1m-35), various uplink processors (1m-25, 1m-30) and a scheduler (1m-15).

[0182] The transceiver (1m-05) sends data and predetermined control signals through a forward carrier, and receives data and predetermined control signals through a reverse carrier. When multiple carriers are set, the transceiver (1m-05) performs data sending and receiving and control signal sending and receiving through multiple carriers. The function of the multiplexing and demultiplexing unit (1m-20) is to multiplex the data generated in the uplink processor (1m-25, 1m-30) or the control message processor (1m-35), or to demultiplex the data received by the transceiver (1m-05), and submit the data to the appropriate uplink layer processor (1m-25, 1m-30), control message processor (1m-35) or controller (1m-10).

[0183] According to certain embodiments, the control message processor (1m-35) receives an instruction from the controller, and generates a message to be delivered to the UE, and delivers the message to the downlink layer. The uplink layer processor (1m-25, 1m-30) can be constructed according to each UE and each service, and processes data generated by user services such as FTP or VoIP, and delivers the data to the multiplexing and demultiplexing unit (1m-20), or processes data delivered from the multiplexing and demultiplexing unit (1m-20) and delivers the data to the service application of the uplink layer. The scheduler (1m-15) allocates any transmission resources to the UE at an appropriate time taking into account the buffer status, channel status, active time of the UE, etc. of the UE, and processes the signal delivered by the UE to the transceiver or processes the data to be delivered to the UE.

[0184] Figure 2a An example of a structure of an LTE system according to various embodiments of the present disclosure is shown.

[0185] refer to Figure 2a As a non-limiting example, the wireless access network of the LTE system includes next generation base stations (evolved Node B, "eNB", "Node B" or "base station") (2a-05, 2a-10, 2a-15, 2a-20), MME (mobile management entity, 2a-25) and S-GW (serving gateway) (2a-30). User equipment ("UE") (2a-35) is connected to the external network via eNB (2a-05 to 2a-20) and S-GW (2a-30).

[0186] exist Figure 2a In the LTE system, the eNB (2a-05 to 2a-20) corresponds to the existing Node B of the UMTS (Universal Mobile Telecommunications System) system. The eNB is connected to the UE (2a-35) via a wireless channel, thereby performing more complex tasks than the existing Node B. In the LTE system, since all user traffic including real-time services (e.g., VoIP (Voice over IP) via Internet Protocol Real-time) is provided via a shared channel, a device for collecting and scheduling status information (such as the buffer status of the UE, the available conversion power status, the channel status, etc.) is required. The eNB (2a-05 to 2a-20) is used as such a device.

[0187] According to certain embodiments, one eNB often controls several cells. In order to achieve a transmission speed of 100 Mbps, the LTE system uses (for example) orthogonal frequency division multiplexing ("OFDM") within a 20 MHz bandwidth as a wireless access technology. Moreover, the LTE system applies a modulation scheme that is adaptive to the channel state of the UE, and applies adaptive modulation and coding ("AMC") to determine the channel coding rate. The S-GW (2a-30) is a device that provides data bearers, and generates or removes data bearers according to the control of the MME (2a-25). The MME (2a-25) is a device that implements various controls and mobility management for the UE.

[0188] Figure 2b A wireless protocol structure in an LTE system according to certain embodiments of the present disclosure is shown.

[0189] refer to Figure 2b As a non-limiting example, the wireless protocol of the LTE system includes a PDCP (Packet Data Convergence Protocol) layer (2b-05, 2b-40), an RLC (Radio Link Control) layer (2b-10, 2b-35), and a MAC (Media Access Control) layer (2b-15, 2b-30) at the UE and the eNB, respectively. The PDCP (2b-05, 2b-40) operates to compress and restore IP headers, etc. The functions of the PDCP layer include:

[0190] -Header compression and decompression: ROHC only

[0191] -Transmission of user data

[0192] - For RLC AM, sequential delivery of upper layer PDUs during PDCP re-establishment

[0193] - For split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission and reordering for reception

[0194] - For RLC AM, duplicate detection of lower layer SDUs during PDCP re-establishment

[0195] - Retransmission of PDCP SDUs at handover for RLC AM and retransmission of PDCP PDUs during PDCP data recovery for split bearers in DC

[0196] -Encryption and decryption

[0197] - Timer-based SDU discard in uplink

[0198] Radio Link Control ("RLC") (2b-10, 2b-35) reconstructs a PDCP PDU (Packet Data Unit) with an appropriate size and performs ARQ operations, etc. The functions of the RLC layer include:

[0199] -Transmission of upper layer PDU

[0200] - Error correction through ARQ (for AM data transmission only)

[0201] -RLC SDU concatenation, segmentation and reassembly (only for UM and AM data transmission)

[0202] - Re-segmentation of RLC data PDU (only for AM data transmission)

[0203] - Reordering of RLC data PDUs (only for UM and AM data transmission)

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

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

[0206] -RLC SDU discard (only for UM and AM data transmission)

[0207] -RLC re-establishment

[0208] The MAC layer (2b-15, 2b-30) is connected to various RLC layer devices provided in the UE, and by performing operations, multiplexes the RLC PDU into the MAC PDU and demultiplexes the RLC PDU from the MAC PDU. The functions of the MAC layer include:

[0209] - Mapping between logical channels and transport channels

[0210] Multiplex MAC SDUs belonging to one or more different logical channels into a transport block (TB) delivered to the physical layer on a transport channel, or demultiplex MAC SDUs belonging to one or more different logical channels from a transport block (TB) delivered by the physical layer on a transport channel

[0211] -Dispatch information report

[0212] - Error correction through HARQ

[0213] - Priority handling between logical channels of a UE

[0214] - Priority handling between UEs with dynamic scheduling

[0215] -MBMS service identification

[0216] -Transmission format selection

[0217] -filling

[0218] The root physical ("PHY") layer (2b-20, 2b-25) operates the channel coding and modulation of the upper layer data, converts the data into OFDM symbols, transmits the OFDM symbols via the wireless channel, demodulates the OFDM symbols received via the wireless channel, operates the channel decoding thereof, and transmits the decoded data to the upper link. Moreover, even in the physical layer, HARQ (Hybrid ARQ) is used to correct any additional errors. One bit is used to transmit information about whether the receiver has received the packet sent from the transmitter. That is, HARQ ACK / NACK information. The downlink HARQ ACK / NACK information for uplink transmission is sent via the physical channel of PHICH (Physical Hybrid ARQ Indicator Channel), and the uplink HARQ ACK / NACK information for downlink transmission can be sent via PUCCH (Physical Uplink Control Signal) or PUSCH (Physical Uplink Shared Channel).

[0219] The PHY layer may include one or more frequencies / carriers. The technology of configuring and using multiple frequencies at the same time is called carrier aggregation ("CA"). Only one carrier was used for communication between user equipment (UE) and base station (E-UTRAN Node B, eNB). However, CA technology uses one or more secondary carriers in addition to the primary carrier, thereby being able to dramatically increase the transmission volume according to the number of secondary carriers. In LTE, the cell using the primary carrier in the base station is the PCell (primary cell), and the secondary cell is the Scell ​​(secondary cell).

[0220] In addition, an RRC (Radio Resource Control) layer exists in the upper PDCP layer of the UE and the base station, respectively, which is not shown in the drawing. The RRC layer can complete a connection for radio resource control and exchange configuration control messages associated with measurement.

[0221] Figure 2c An example of a structure of a next-generation mobile communication system according to various embodiments of the present disclosure is shown.

[0222] refer to Figure 2c In an illustrative example, the radio access network of the next generation mobile communication system includes a next generation base station (new radio node B, i.e., "NR-NB") (2c-10) and a new radio core network or next generation core network ("NG-CN") (2c-05). The new radio user equipment ("NR UE") (2c-15) is connected to an external network via the NR NB (2c-10) and the NR CN (2c-05).

[0223] exist Figure 2c In the illustrative example, the NR NB (2c-10) corresponds to the eNB (evolved Node B) of the existing LTE system. The NRNB is connected to the NR UE (2c-15) via a wireless channel and is capable of providing more excellent services than the existing Node B. In the next generation mobile communication system, since all user traffic is provided through a shared channel, equipment for collecting and scheduling status information (such as the buffer status of the UE, the available transmission power status, the channel status, etc.) is required. NR NB (2c-10) is used as such a device. One NR NB often controls multiple cells. In order to achieve ultra-high-speed data transmission compared to the existing LTE, the NR NB can have a bandwidth equal to or greater than the existing maximum bandwidth, and can additionally implement beamforming technology by using orthogonal frequency division multiplexing (OFDM). Moreover, adaptive modulation and coding (AMC) is applied to determine the modulation scheme, and a channel coding rate that is adaptive to the channel state of the UE is applied.

[0224] According to certain embodiments, NR CN (2c-05) plays a role of supporting mobility and setting bearer and QoS, etc. NRCN is a device that provides various controls and mobility management for UE and is connected to several base stations. Moreover, the next generation mobile communication system can be associated with the existing LTE system, and NR CN is connected to MME (2c-25) through a network interface. MME is connected to eNB (2c-30) which is an existing base station.

[0225] Figure 2d An example of a wireless protocol structure of a next-generation mobile communication system according to various embodiments of the present disclosure is shown.

[0226] refer to Figure 2d As an illustrative example, the wireless protocol of the next generation mobile communication system includes NR SDAP (2d-01, 2d-45), NR PDCP (2d-05, 2d-40), NR RLC (2d-10, 2d-35) and NR MAC (2d-15, 2d-30) at the UE and NR, respectively.

[0227] The functionality of NR SDAP (2d-01, 2d-45) includes one or more of the following options:

[0228] -Transmission of flat data

[0229] - Mapping between QoS flows and DRBs for both DL and UL

[0230] - Marking QoS Flow ID in both DL and UL packets

[0231] -For UL SDAP PDU, reflect the mapping of QoS flows to DRBs

[0232] With respect to the SDAP layer device, the UE may receive a setting regarding whether to use the header of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel, or whether to use the function of the SDAP layer device. In the case of setting the SDAP header, the SDAP layer device may command the UE to update or reset the QoS flow of the uplink and downlink and the mapping information for the data bearer through the 1-bit NAS reflection QoS indicator and the 1-bit AS reflection QoS indicator of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority, scheduling information, etc. to assist in smooth service.

[0233] The functionality of NR PDCP (2d-05, 2d-40) may include one or more of the following options:

[0234] -Header compression and decompression: ROHC only

[0235] -Transmission of user data

[0236] - Sequential delivery of upper layer PDUs

[0237] - Out-of-order delivery of upper layer PDUs

[0238] - Reordering of received PDCP PDUs

[0239] - Duplicate detection of lower layer SDU

[0240] -Retransmission of PDCP SDU

[0241] -Encryption and decryption

[0242] - Timer-based SDU discard in uplink

[0243] The reordering function of the NR PDCP device is a function of sequentially reordering the PDCP PDUs received by the lower layer based on the PDCP SN (sequence number). This function may include the function of transmitting data to the upper layer in the reordered order or directly transmitting data without considering the order and the function of recording the lost PDCP PDU by rearranging the order of the PDCP PDU. In addition, it may include the function of reporting the status of the lost PDCP PDU to the transmitter and requesting the retransmission of the lost PDCP PDU.

[0244] The functions of NR RLC (2d-10, 2d-35) include one or more of the following options:

[0245] -Transmission of upper layer PDU

[0246] - Sequential delivery of upper layer PDUs

[0247] - Out-of-order delivery of upper layer PDUs

[0248] - Error correction via ARQ

[0249] -RLC SDU concatenation, segmentation and reassembly

[0250] - Re-segmentation of RLC data PDUs

[0251] - Reordering of RLC data PDUs

[0252] - Duplicate detection

[0253] -Protocol error detection

[0254] -RLC SDU discarded

[0255] -RLC re-establishment

[0256] refer to Figure 2dIn an illustrative example of, the sequential delivery of the NR RLC device is a function of transmitting the RLC SDUs received from the lower layer to the upper layer in sequence when the initial RLC SDU is segmented into several RLC SDUs and the segmented RLC SDUs are received, and may include the function of reassembling and transmitting the received RLC PDUs. It may also include the function of reordering the received RLC PDUs based on the RLC SN or PDCP SN, the function of rearranging the order of the received RLC PDUs and recording the lost RLC PDUs, the function of reporting the status of the lost RLC PDUs to the transmitter, and the function of requesting the retransmission of the lost RLC PDUs. In the case of any lost RLC SDUs, it may include the function of transmitting only the RLC SDUs before the lost RLC SDUs to the upper layer in sequence. In some embodiments, even if there are any lost RLC SDUs, but the predetermined timer expires, it may include the function of transmitting all RLC SDUs received before the timer to the upper layer in sequence. Even if there are any lost RLC SDUs, but the predetermined timer expires, it may include the function of transmitting all RLC SDUs received until now to the upper layer in sequence. Furthermore, the RLC PDUs may be processed in the order in which they are received (in order of arrival, regardless of sequence number, ordinal number, etc.) and delivered to the PDCP device without regard to the order (out-of-order delivery). For the individual segments, the segments are stored in a buffer or the segments to be received later are received and then reconstructed into a complete single RLC PDU, which is then processed and delivered to the PDCP device. The NR RLC layer may not include the concatenation function, or this function may be performed on the NR MAC layer or in place of the multiplexing function of the NR MAC layer.

[0257] According to certain embodiments, the out-of-order delivery function of the NR RLC device is a function of delivering the RLC SDUs received from the lower layer directly to the upper layer without considering their order. In the case where the original single RLC SDU is segmented into several RLC SDUs and the segmented RLC SDUs are received, the function of reassembling these RLC SDUs may be included. It may also include the function of storing the RLC SN or PDCP SN of the received RLC PDU, arranging them in sequence, and recording the lost RLC PDU.

[0258] refer to Figure 2d As a non-limiting example, NR MAC (2d-15, 2d-30) can be connected to several NR RLC layer devices included in the UE. The functions of NR MAC include one or more of the following options:

[0259] - Mapping between logical channels and transport channels

[0260] -Multiplexing / demultiplexing of MAC SDU

[0261] -Dispatch information report

[0262] - Error correction through HARQ

[0263] - Priority handling between logical channels of a UE

[0264] - Priority handling between UEs with dynamic scheduling

[0265] -MBMS service identification

[0266] -Transmission format selection

[0267] -filling

[0268] According to certain embodiments, the NR PHY layer (2d-20, 2d-25) can operate channel coding and modulation of upper layer data to turn them into OFDM symbols, send the OFDM symbols via a wireless channel, demodulate the OFDM symbols received via the wireless channel, operate channel decoding thereof, and send the decoded data to an upper layer link.

[0269] Figure 2e An example of a process followed by a base station transmitting a cell-based uplink configuration to a UE and then releasing the specific uplink configuration according to various embodiments of the present disclosure is shown.

[0270] refer to Figure 2eIn a non-limiting example, a UE (2e-01) in an RRC IDLE state remains resident after passing a cell selection process for a specific base station (2e-02) and is able to receive system information. Then, the UE performs an RRC connection process for the cell concerned in operation 2e-05, and the UE in the RRC connection state switches to the cell concerned. According to various embodiments, in operation 2e-10, the base station delivers an RRCReconfiguration message to the UE and provides configuration information applied to the UE in the cell concerned. The message may include, in particular, ServingCellConfigCommon as basic information in the serving cell concerned and ServingCellConfig configuration information as specific information based on the UE in the cell concerned. Specifically, if the base station supports the cell concerned, configuration information for a normal uplink (hereinafter referred to as "NUL") and a supplementary uplink (hereinafter referred to as "SUL") may be included in ServingCellConfigCommon. The configuration information concerned is the configuration information delivered to all UEs within the cell, if the base station supports these UEs on a cell basis. An example of ASN.1 code for implementing the functions described above is provided below:

[0271]

[0272] SupplementaryUplinkConfig

[0273] According to some embodiments, this field is optionally present if UplinkConfigcomon is set, but is not present in any other case. In the absence of this field, the UE releases SupplementaryUplinkConfig (if set in ServingCellConfig).

[0274] Moreover, in some embodiments, ServingCellConfigCommon may be included when ServingCellConfigCommon is delivered from the previous cell to the target cell at the time of handover. In this case, when a UE that has received support for NUL (normal UL) and SUL (supplementary UL) in the previous serving cell is handed over to a serving cell that only supports NUL, the configuration information for SUL may be released. That is, supplementaryUplinkConfg is discarded from ServingCellConfigCommon, and the UE releases the SUL configuration information.

[0275] However, according to the current standard, the serving cell supports both NUL and SUL, and there is no function to set only one UL for a specific UE. That is, in the case where the UE is isolated from the cell edge (moves to the cell center), the SUL configuration is not required, and support for more features may be desired. Moreover, in the case where SUL is set, due to capability limitations (e.g., limitations on UL MIMO, etc.) can be applied to the UE, and therefore if only NUL is set instead of the NUL+SUL configuration, more UE capabilities and wireless features can be used. The non-limiting example of the ASN.1 code shown below indicates that the current standard cannot release SUL for a specific UE. That is, in the ASN.1 code, the SupplementaryUplink field is set to OPTIONAL NEED M. This means that when the field in question is abandoned and submitted in the next configuration, if there is a previously set value, the previous value is maintained. That is, although NUL and SUL are set at the same time in the previous RRC configuration, and SUL is abandoned and submitted in the next configuration, this does not mean the release of SUL.

[0276]

[0277] refer to Figure 2e As a non-limiting example, in operation 2e-15, the UE can measure the serving cell and the serving frequency cell as well as the peripheral frequency and other RAT cells according to the measurement process, and include the measurement results in the measurement report message so that it is submitted to the base station. In operation 2e-20, the base station interprets the information of the measurement report received from the UE and is able to know that the current cell does not exist at the edge of the cell, but exists near the center of the serving cell. That is, this may be a situation where the UE's serving cell measurement value is good. In this case, the base station can decide to release the SUL that has been set for the UE in question. This will allow the UE to use more UE capabilities and provide more radio resources.

[0278] In operation 2e-25, the base station includes ReconfigurationWithSync and ServingCellConfigCommon including configuration information only for uplink (NUL) into the RRCReconfiguration message, and delivers the message to the UE. According to this configuration information, the UE is commanded to re-perform synchronization configuration via random access, release the SUL configuration from the cell concerned, and apply only the NUL configuration. In operation 2e-30, the UE applies the configuration for the set NUL, performs a random access procedure for the cell concerned, and obtains uplink and downlink synchronization. In operation 2e-35, the UE performs data transmission and reception with the base station. In this case, the new configuration value received in operation 2e-25 is applied, the SUL configuration is released, and communication is implemented by applying only NUL.

[0279] Specifically, the present disclosure is characterized in that, although the serving cell concerned supports both NUL and SUL, SUL is still not set for a specific UE. Under the current standard, cell-based uplink configuration information is continuously provided by ServingCellConfigCommon and ServingCellConfigCommonSIB (according to the support of the cell therefor). However, if the present disclosure is applied, there may be no SUL configuration information for a specific UE, which is independent of the cell capability. If the base station submits ServingCellConfigCommon from which the SUL configuration is discarded together with ReconfigurationWithSync, the UE releases the SUL configuration information present in ServingCellConfig as a dedicated RRC message.

[0280] In some embodiments, even if the UE receives SIB1 provided by the base station again after the relevant process has been performed (i.e., both the NUL configuration and the SUL configuration are included in the ServingCellConfigCommonSIB), the SUL cannot be used again because the SUL configuration information included in the dedicated message has been released. Currently, the ReconfigurationWithSync configuration is used in the case of changing the PCell (handover), and the most important system information in the target cell can be included therein. The present disclosure is characterized in that, if the present disclosure is applied, a method using ReconfigurationWithSync is applied to a cell-based UE.

[0281] Figure 2f An example of operations performed by a UE when releasing a UE-based uplink in a specific cell is applied as provided in the present disclosure is shown.

[0282] refer to Figure 2f As a non-limiting example, a UE in an RRC IDLE state remains resident after passing a cell selection process for a specific base station and is able to receive system information. Thereafter, the UE performs an RRC connection process with the cell in question and switches to the cell in question in an RRC connected state. In operation 2f-05, the UE receives an RRCReconfiguration message from the base station and receives configuration information applied to the UE in the cell in question. The message may include ServingCellConfigCommon as basic information in the cell in question and ServingCellConfig configuration information as specific information based on the UE. Specifically, if the base station supports the cell in question, configuration information for a normal uplink ("NUL") and a supplementary uplink ("SUL") may be included in ServingCellConfigCommon. The configuration information in question is configuration information submitted to all UEs in the cell if the base station supports it on a cell basis.

[0283] According to certain embodiments, in operation 2f-10, the UE may measure the serving cell, the cell of the serving frequency, the cell of the peripheral frequency, and other RAT cells according to the measurement process. In operation 2f-15, the UE may receive an RRCReconfiguration message submitted from the base station, and ReconfigurationWithSync and ServingCellConfigCommo having only the uplink configuration information may be included in the message concerned. According to this configuration information, the UE is commanded to re-execute synchronization configuration via random access, release the SUL configuration from the cell concerned, and apply only the NUL configuration. In operation 2f-20, the UE applies the configuration for the set NUL, performs a random access process for the cell concerned, and obtains uplink and downlink synchronization. In operation 2f-25, the UE performs data transmission and reception with the base station. In this case, the new configuration value received in operation 2f-15 is applied, the SUL configuration is released, and communication is implemented by applying only NUL.

[0284] Figure 2g An example of an operation performed by a base station when a method of releasing a UE-based uplink in a specific cell is applied according to various embodiments of the present disclosure is shown.

[0285] refer to Figure 2gAs a non-limiting example, a UE in an RRC IDLE state remains stationed after passing a cell selection process for a specific base station, and performs an RRC connection process with the cell concerned after receiving system information. The base station causes the UE concerned to transition to an RRC connected state. In operation 2g-05, the base station delivers an RRCReconfiguration message to the UE, and provides configuration information applied to the UE in the cell concerned. The message may include, in particular, ServingCellConfigCommon as basic information in the serving cell concerned and ServingCellConfig configuration information as UE-based specific information in the cell concerned. Specifically, if the base station supports the cell concerned, configuration information for a normal uplink (hereinafter referred to as "NUL") and a supplementary uplink (hereinafter referred to as "SUL") may be included in ServingCellConfigCommon. The configuration information concerned is configuration information delivered to all UEs in the cell if the base station supports these UEs on a cell basis.

[0286] According to certain embodiments, in operation 2g-10, the base station receives a measurement report submitted by the UE. The measurement report may include measurement values ​​of a serving cell, a cell of a serving frequency, and cells of peripheral frequencies and other RATs according to the measurement process. In operation 2g-15, the base station interprets the received information of the UE's measurements and is able to know that the current UE does not exist at the edge of the cell, but exists near the center of the serving cell. That is, there may be a situation where the measurement value of the UE's serving cell is good. In this case, the base station can decide to release the SUL set for the UE in question. This will allow the UE to use more UE capabilities and provide more radio resources.

[0287] In operation 2g-20, the base station sets an RRCREconfiguration message under the determination in the above operation, and delivers the message to the UE to configure the UE. The messages concerned may include ReconfigurationWithSync and ServingCellConfigCommon having only the uplink (NUL) configuration information. According to this configuration information, the UE is commanded to re-perform synchronization configuration via random access, release the SUL configuration from the concerned cell, and apply only the NUL configuration. In operation 2g-25, the UE applies the configuration for the set NUL and performs a random access procedure for the concerned cell, and the base station performs the concerned random access procedure. In operation 2f-30, the base station and the UE perform data transmission and reception.

[0288] Figure 2hAn example of the internal structure of a UE according to certain embodiments of the present disclosure is shown in a block diagram format.

[0289] refer to Figure 2h As a non-limiting example, the UE includes an RF (Radio Frequency) processor (2h-10), a baseband processor (2h-20), a storage device (2h-30) and a controller (2h-40).

[0290] According to various embodiments, the RF processor (2h-10) performs functions such as frequency band conversion, amplification, etc. of signals for transmitting and receiving signals via a wireless channel. That is, the RF processor (2h-10) performs an up-conversion of a baseband signal provided by the baseband processor (2h-20) to an RF band signal, and then transmits the RF band signal through an antenna, and performs a down-conversion of the RF band signal received through the antenna to a baseband signal. For example, the RF processor (2h-10) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC (digital-to-analog converter), an ADC (analog-to-digital converter), etc. Figure 2h Only one antenna is shown, but the UE may be provided with multiple antennas. Furthermore, the RF processor (2h-10) may include multiple RF chains. Furthermore, the RF processor (2h-10) may perform beamforming. For beamforming, the RF processor (2h-10) may adjust the phase and magnitude of corresponding signals transmitted and received by multiple antennas or antenna elements. Furthermore, the RF processor may be capable of performing MIMO and may receive multiple layers when performing MIMO operations.

[0291] According to some embodiments, the baseband processor (2h-20) performs a conversion between a baseband signal and a bit stream according to the physical layer specification of the system. For example, when sending data, the baseband processor (2h-20) encodes and modulates the bit stream sent, thereby generating a complex symbol. Moreover, when receiving data, the baseband processor (2h-20) demodulates and decodes the baseband signal provided from the RF processor (2h-10), thereby restoring the received bit stream. For example, according to the OFDM (Orthogonal Frequency Division Multiplexing) method, when sending data, the baseband processor (2h-20) encodes and modulates the bit stream sent, thereby generating a complex symbol. After mapping these complex symbols to subcarriers, the baseband processor (2h-20) constructs OFDM symbols through IFFT (Inverse Fast Fourier Transform) operations and CP (Cyclic Prefix) insertion. Moreover, when receiving data, the baseband processor (2h-20) segments the baseband signal provided from the RF processor (2h-10) according to the unit of OFDM symbols. After restoring the signal mapped to the subcarrier through FFT (Fast Fourier Transform), the baseband processor (2h-20) restores the received bit stream through demodulation and decoding.

[0292] As described above, the baseband processor (2h-20) and the RF processor (2h-10) transmit and receive signals. Accordingly, the baseband processor (2h-20) and the RF processor (2h-10) can be referred to as a transmitter, a receiver, a transceiver or a communicator. In addition, at least one of the baseband processor (2h-20) and the RF processor (2h-10) may include a plurality of communication modules to support several different wireless connection technologies. Moreover, at least one of the baseband processor (2h-20) and the RF processor (2h-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless connection technologies may include wireless LAN (e.g., IEEE 802.11), cellular networks (e.g., LTE), etc. Moreover, different frequency bands may include ultra-high frequency (SHF) (e.g., 2.NRHz, NRhz) bands and millimeter (MM) wave (e.g., 60GHz) bands.

[0293] like Figure 2h As shown in the illustrative example in , the storage device (2h-30) stores basic programs, applications and data (such as configuration information) for the operation of the UE. The storage device (2h-30) can store information associated with a second connection node that performs wireless communication using a second wireless connection technology. Moreover, the storage device (2h-30) provides the stored data according to a request from the controller (2h-40).

[0294] The controller (2h-40) controls the general operation of the UE. For example, the controller (2h-40) transmits and receives signals through the baseband processor (2h-20) and the RF processor (2h-10). Moreover, the controller (2h-40) records data on the storage device (2h-30) and reads the data. To this end, the controller (2h-40) may include at least one processor. For example, the controller (2h-40) may include a CP (communication processor) that performs control for communication and an AP (application processor) that controls an upper layer such as an application.

[0295] Figure 2i An example of a configuration of a base station according to various embodiments of the present disclosure is shown in a block diagram format.

[0296] refer to Figure 2i As a non-limiting example, the base station includes an RF processor (2i-10), a baseband processor (2i-20), a backhaul communicator (2i-30), a storage device (2i-40) and a controller (2i-50).

[0297] In some embodiments, the function of the RF processor (2i-10) is to receive and transmit signals via a wireless channel for frequency band change, amplification, etc. of the signals. That is, the RF processor (2i-10) performs an up-conversion of the baseband signal provided by the baseband processor (2i-20) to an RF band signal and transmits the RF band signal through an antenna, and performs a down-conversion of the RF band signal received through the antenna to a baseband signal. For example, the RF processor (2i-10) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Figure 2i In the figure, only one antenna is shown, but the first connection node may have multiple antennas. Moreover, the RF processor (2i-10) may include multiple RF chains. In addition, the RF processor (2i-10) may perform beamforming. For beamforming, the RF processor (2i-10) may adjust the phase and size of the corresponding signals received and transmitted by multiple antennas or antenna elements. Moreover, the RF processor may perform downward MIMO operation by sending one or more layers.

[0298] In some embodiments, the baseband processor (2i-20) performs a conversion between a baseband signal and a bit stream according to a physical layer specification of a first wireless connection technology. For example, when sending data, the baseband processor (2i-20) encodes and modulates the bit stream sent, thereby generating a complex symbol. Moreover, when receiving data, the baseband processor (2i-20) demodulates and decodes the baseband signal provided from the RF processor (2i-10), thereby restoring the received bit stream. For example, according to the OFDM (orthogonal frequency division multiplexing) method, when sending data, the baseband processor (2i-20) encodes and modulates the bit stream sent, thereby generating a complex symbol. After mapping these complex symbols to subcarriers, the baseband processor (2i-20) constructs OFDM symbols through IFFT (inverse fast Fourier transform) operations and CP (cyclic prefix) insertion. Moreover, when receiving data, the baseband processor (2i-20) segments the baseband signal provided from the RF processor (2i-10) according to the unit of OFDM symbols. After restoring the signal mapped to the subcarrier by FFT (Fast Fourier Transform), the baseband processor (2i-20) restores the received bit stream by demodulation and decoding. As described above, the baseband processor (2i-20) and the RF processor (2i-10) transmit and receive signals. Accordingly, the baseband processor (2i-20) and the RF processor (2i-10) can be referred to as a transmitter, a receiver, a transceiver, a communicator or a wireless communicator.

[0299] According to various embodiments, the backhaul communicator (2i-30) provides an interface for performing communication with other nodes in the network. That is, the backhaul communicator (2i-30) converts a bit stream sent from the main base station to any other node (e.g., a supplementary base station, a core network, etc.) into a physical signal, and the physical signal received from the other node is converted into a bit stream.

[0300] The storage device (2i-40) stores basic programs, applications and data (such as configuration information) for the operation of the main base station. Specifically, the storage device (2i-40) can store information associated with the bearer assigned to the connected UE, measurement results reported from the connected UE, etc. Moreover, the storage device (2i-40) can provide multiple connections for the UE, or can store information that can serve as a basis for determining a connection interruption. The storage device (2i-40) also provides the stored data at a request from the controller (2i-50).

[0301] The controller (2i-50) controls the general operation of the main base station. For example, the controller (2i-50) transmits and receives signals through the baseband processor (2i-20) and the RF processor (2i-10) or the backhaul communicator (2i-30). In addition, the controller (2i-50) records data on the storage device (2i-40) and reads data. To this end, the controller (2i-50) may include at least one processor.

[0302] In the detailed embodiments described above of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural according to the detailed embodiments introduced. However, the singular form or plural form is appropriately selected for the convenience of description for the situation introduced, and the present disclosure is not limited by the elements expressed in the singular or plural. Therefore, the elements expressed in the plural may also include a single element, or the elements expressed in the singular may also include multiple elements.

[0303] Although the present disclosure has been described using various embodiments, various changes and modifications may occur to those skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system, the method include: receiving a first radio resource control (RRC) reconfiguration message from a base station, the first RRC reconfiguration message comprising first configuration information about a serving cell of the base station, wherein the first configuration information about the serving cell comprises information about an uplink (UL) configuration of the serving cell and information about a supplementary uplink (SUL) configuration of the serving cell; communicating with the base station on the UL or SUL based on the information about the UL configuration or the information about the SUL configuration; receiving a second RRC reconfiguration message from the base station, the second RRC reconfiguration message including reconfigurationwithsync and second configuration information about the serving cell, wherein the second configuration information about the serving cell includes information about the UL configuration; and releasing the SUL if the second configuration information about the serving cell does not include information about the SUL configuration, Wherein, after the SUL is released, in case a system information block type 1 SIB1 message including information about the UL configuration and information about the SUL configuration is received from the base station, communication with the base station on the SUL is not performed.

2. The method according to claim 1, further comprising: include: sending a measurement report to the base station, The second RRC reconfiguration message is received based on the measurement report.

3. A method performed by a base station in a wireless communication system, the method include: Sending a first radio resource control (RRC) reconfiguration message to the terminal, wherein the first RRC reconfiguration message includes first configuration information about a serving cell of the base station, wherein the first configuration information about the serving cell includes information about an uplink (UL) configuration of the serving cell and information about a supplementary uplink (SUL) configuration of the serving cell; communicating with the terminal on the UL or SUL based on the information about the UL configuration or the information about the SUL configuration; and sending a second RRC reconfiguration message to the terminal, where the second RRC reconfiguration message includes reconfigurationwithsync and second configuration information about the serving cell, wherein the second configuration information about the serving cell includes information about the UL configuration, Wherein, in a case where the second configuration information about the serving cell does not include information about the SUL configuration, the SUL is released by the terminal, Wherein, after the SUL is released, in a case where a system information block type 1 SIB1 message including information about the UL configuration and information about the SUL configuration is sent to the terminal, communication with the terminal on the SUL is not performed.

4. The method according to claim 3, further comprising: include: receiving a measurement report from the terminal, The second RRC reconfiguration message is sent based on the measurement report.

5. A terminal in a wireless communication system, the terminal include: Transceiver; as well as A controller configured to: receiving, via the transceiver, a first radio resource control (RRC) reconfiguration message from a base station, the first RRC reconfiguration message comprising first configuration information about a serving cell of the base station, wherein the first configuration information about the serving cell comprises information about an uplink (UL) configuration of the serving cell and information about a supplementary uplink (SUL) configuration of the serving cell, communicating with the base station on the UL or SUL based on the information about the UL configuration or the information about the SUL configuration, receiving, via the transceiver, a second RRC reconfiguration message from the base station, the second RRC reconfiguration message including reconfigurationwithsync and second configuration information about the serving cell, wherein the second configuration information about the serving cell includes information about the UL configuration; and releasing the SUL if the second configuration information about the serving cell does not include information about the SUL configuration, Wherein, after the SUL is released, in case a system information block type 1 SIB1 message including information about the UL configuration and information about the SUL configuration is received from the base station, communication with the base station on the SUL is not performed.

6. The terminal according to claim 5, in, The controller is further configured to send a measurement report to the base station via the transceiver, and The second RRC reconfiguration message is received based on the measurement report.

7. A base station in a wireless communication system, the base station include: Transceiver; as well as A controller configured to: sending, via the transceiver, a first radio resource control (RRC) reconfiguration message to a terminal, the first RRC reconfiguration message comprising first configuration information about a serving cell of the base station, wherein the first configuration information about the serving cell comprises information about an uplink (UL) configuration of the serving cell and information about a supplementary uplink (SUL) configuration of the serving cell, communicating with the terminal on the UL or SUL based on the information about the UL configuration or the information about the SUL configuration, and sending a second RRC reconfiguration message to the terminal via the transceiver, the second RRC reconfiguration message including reconfigurationwithsync and second configuration information about the serving cell, wherein the second configuration information about the serving cell includes information about the UL configuration, Wherein, in a case where the second configuration information about the serving cell does not include information about the SUL configuration, the SUL is released by the terminal, Wherein, after the SUL is released, in a case where a system information block type 1 SIB1 message including information about the UL configuration and information about the SUL configuration is sent to the terminal, communication with the terminal on the SUL is not performed.

8. The base station according to claim 7, in, The controller is further configured to receive a measurement report from the terminal via the transceiver, and The second RRC reconfiguration message is sent based on the measurement report.

Images