KR20240021691A - Apparatus and method for configuring candidate target pscell upon excuting conditional handover in mobile wireless networks - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. The present invention discloses. The present disclosure discloses a method and device for applying specific secondary cell group settings when performing handover to a specific PCell.

Description

Method and device for setting candidate PSCell during conditional handover in next-generation mobile communication {APPARATUS AND METHOD FOR CONFIGURING CANDIDATE TARGET PSCELL UPON EXCUTING CONDITIONAL HANDOVER IN MOBILE WIRELESS NETWORKS}

This disclosure relates to the operation of a terminal in a mobile communication system. Specifically, it is about a technology that applies specific secondary cell group settings when performing handover to a specific PCell.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

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

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

As various services can be provided as described above and with the development of mobile communication systems, there is a need for a method to effectively provide these services. For example, the terminal can perform a conditional handover to a specific PCell. In this case, based on the changed MN (master node), a secondary cell group (SCG) is added, or the existing SCG is changed to another SCG. When multiple SCGs such as this are established, there may be a problem of separate delays.

Accordingly, the purpose of the present invention is to enable the target master node to transmit configuration information received from multiple target secondary nodes to the terminal in a wireless communication system, so that even if the terminal hands over to the target master node, the target master node transmits configuration information received from multiple target secondary nodes to the terminal without a separate signal after satisfying a specific condition. , It provides a method to perform PSCell change to a specific target secondary node.

The present invention to solve the above problems is a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; And transmitting a second control signal generated based on the processing to the base station.

According to an embodiment of the present invention, when a terminal performs a conditional handover and connects to a PSCell, there is an effect of being able to have a reliable connection state.

Figure 1 is a diagram showing the structure of a general LTE system.
Figure 2 is a diagram showing the wireless protocol structure of a general LTE system.
Figure 3 is a diagram showing the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
Figure 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
Figure 5 is a block diagram showing the internal structure of a terminal according to an embodiment of the present disclosure.
Figure 6 is a block diagram showing the configuration of an NR base station according to an embodiment of the present disclosure.
Figure 7 is a diagram to explain the structure of the conditional reconfiguration field received by the terminal.
Figure 8 is a diagram for explaining the operation upon initial setting of the operation proposed in this disclosure.
FIG. 9 is a diagram illustrating a procedure for reflecting the setting in the CHO with candidate SCG setting in response to a change in the current MCG setting of the S-MN after setting the conditional handover for the first candidate SCG to the UE. am.
FIG. 10 is a diagram illustrating the necessary procedures when it is desired to release the candidate SCG maintained in the T-SN after initially setting Cho with candidate SCG.
Figure 11 is a diagram to explain the operations and sequences performed by the terminal when receiving RRCReconfiguration and problematic parts in some steps.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the attached drawings. In the following description of the present invention, if a detailed description of a related known function or configuration is judged to unnecessarily obscure the gist of the present invention, the detailed description will be omitted. The terms described below are defined in consideration of the functions in the present invention, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Terms used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, and a term referring to various types of identification information. The following are examples for convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.

Hereinafter, the base station is the entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel types. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which embodiments of the present disclosure can be applied, and 5G hereinafter refers to existing LTE, LTE-A, and It may be a concept that includes other similar services. In addition, this disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge. At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions.

These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially simultaneously, or it is possible for the blocks to be performed in reverse order depending on the corresponding function. At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' refers to what roles. It can be done. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

For convenience of description below, the present invention uses terms and names defined in the 5GS and NR standards, which are standards defined by the 3GPP (The 3rd Generation Partnership Project) organization among currently existing communication standards. However, the present invention is not limited by the above terms and names, and can be equally applied to wireless communication networks complying with other standards. For example, the present invention can be applied to 3GPP 5GS/NR (5th generation mobile communication standard).

Figure 1 is a diagram showing the structure of a general LTE system.

Referring to FIG. 1, as shown, 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) (1-05, 1-10, 1-15, 1-20) and It may be composed of a Mobility Management Entity (MME) (1-25) and S-GW (1-30, Serving-Gateway). User equipment (hereinafter referred to as UE or terminal) (1-35) can access an external network through ENB (1-05 to 1-20) and S-GW (1-30).

In Figure 1, ENBs (1-05 to 1-20) may correspond to existing Node B of the UMTS system. The ENB is connected to the UE (1-35) through a wireless channel and can perform a more complex role than the existing Node B. In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) through the Internet protocol, can be serviced through a shared channel. Therefore, a device is needed to perform scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs, and ENBs (1-05 to 1-20) can be responsible for this. One ENB can typically control multiple cells. For example, in order to implement a transmission speed of 100 Mbps, the LTE system can use Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology in, for example, a 20 MHz bandwidth.

Additionally, the Adaptive Modulation & Coding (AMC) method can be applied, which determines the modulation scheme and channel coding rate according to the channel status of the terminal. The S-GW (1-30) is a device that provides data bearers, and can create or remove data bearers under the control of the MME (1-25). The MME is a device that handles various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations.

Figure 2 is a diagram showing the wireless protocol structure of the existing LTE system.

Referring to Figure 2, the wireless protocols of the LTE system are Packet Data Convergence Protocol (PDCP) (2-05, 2-40) and Radio Link Control (RLC) (Radio Link Control, RLC) in the terminal and ENB, respectively. 2-10, 2-35), and Medium Access Control (MAC) (2-15, 2-30). PDCP can be responsible for operations such as IP header compression/restoration. The main functions of PDCP can be summarized as follows.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

- Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM

- Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

Radio Link Control (RLC) (2-10, 2-35) can perform ARQ operations, etc. by reconfiguring the PDCP Packet Data Unit (PDU) to an appropriate size. Main features of RLC The functions can be summarized as follows.

- Data transfer function (Transfer of upper layer PDUs)

- ARQ function (Error Correction through ARQ (only for AM data transfer))

- Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)

- Re-segmentation of RLC data PDUs (only for AM data transfer)

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

- Duplicate detection (only for UM and AM data transfer)

- Error detection function (Protocol error detection (only for AM data transfer))

- RLC SDU deletion function (RLC SDU discard (only for UM and AM data transfer))

- RLC re-establishment function

MAC (2-15, 2-30) is connected to several RLC layer devices configured in one terminal, and can perform operations of multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing and demultiplexing function (Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels)

- Scheduling information reporting

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification function

- Transport format selection function

- Padding function

The physical layer (2-20, 2-25) channel-codes and modulates the upper layer data, creates OFDM symbols and transmits them to the wireless channel, or demodulates and channel decodes the OFDM symbols received through the wireless channel and transmits them to the upper layer. You can do the following actions.

Figure 3 is a diagram showing the structure of a next-generation mobile communication system.

Referring to Figure 3, the radio access network of the next-generation mobile communication system (hereinafter referred to as NR or 5g) includes a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (3-10) and a next-generation wireless core network (New Radio Core). Network, NR CN) (3-05). The next-generation wireless user equipment (New Radio User Equipment, NR UE or UE) (3-15) can access an external network through NR gNB (3-10) and NR CN (3-05).

In Figure 3, NR gNB (3-10) may correspond to an eNB (Evolved Node B) of the existing LTE system. NR gNB is connected to NR UE (3-15) through a wireless channel and can provide superior services than the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device is needed to perform scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs, and the NR NB 3-10 may be responsible for the scheduling. One NR gNB can control multiple cells. In the next-generation mobile communication system, in order to implement ultra-high-speed data transmission compared to general LTE, a bandwidth exceeding the general maximum bandwidth may be applied. In addition, beamforming technology can be additionally applied using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. Additionally, an Adaptive Modulation & Coding (AMC) method that determines the modulation scheme and channel coding rate according to the channel status of the terminal may be applied. NR CN (3-05) can perform functions such as mobility support, bearer setup, and QoS setup. NR CN is a device that handles various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations. Additionally, the next-generation mobile communication system can also be linked to the LTE system, and NR CN can be connected to MME (3-25) through a network interface. The MME can be connected to an LTE base station, eNB (3-30).

Figure 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied. .

Referring to FIG. 4, the wireless protocols of the next-generation mobile communication system are NR Service Data Adaptation Protocol (SDAP) (4-01, 4-45) and NR PDCP (4-05, 4-05) in the terminal and NR base station, respectively. 4-40), NR RLC (4-10, 4-35), NR MAC (4-15, 4-30) and NR PHY (4-20, 4-25).

The main functions of NR SDAP (4-01, 4-45) may include some of the following functions:

Transfer of user plane data

Mapping function of QoS flow and data bearer for uplink and downlink (mapping between a QoS flow and a DRB for both DL and UL)

Marking QoS flow ID in both DL and UL packets for uplink and downlink

A function to map the relective QoS flow to the data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

For SDAP layer devices, the terminal uses a Radio Resource Control (RRC) message to determine whether to use the header of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel, or whether to use the function of the SDAP layer device. can be set. When the SDAP header is set, the terminal sets the 1-bit indicator (NAS reflective QoS) reflecting the Non-Access Stratum (NAS) QoS (Quality of Service) of the SDAP header and the Access Stratum (AS) QoS The reflective setting 1-bit indicator (AS reflective QoS) can indicate that the terminal can update or reset mapping information for uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

The main functions of NR PDCP (4-05, 4-40) may include some of the following functions:

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

In the above description, the reordering function of the NR PDCP device may mean the function of reordering PDCP PDUs received from the lower layer in order based on PDCP sequence number (SN). The reordering function of the NR PDCP device may include a function of delivering data to a higher layer in the reordered order, or may include a function of directly delivering data without considering the order, and may include a function of transmitting data directly without considering the order, and reordering the data may cause loss. It may include a function to record lost PDCP PDUs, it may include a function to report the status of lost PDCP PDUs to the transmitter, and it may include a function to request retransmission of lost PDCP PDUs. there is.

The main functions of NR RLC (4-10, 4-35) may include some of the following functions:

- Data transfer function (Transfer of upper layer PDUs)

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection function

- Protocol error detection

- RLC SDU deletion function (RLC SDU discard)

- RLC re-establishment function

In the above description, the in-sequence delivery function of the NR RLC device may mean the function of delivering RLC SDUs received from the lower layer to the upper layer in order. When one RLC SDU is originally received by being divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering it.

The in-sequence delivery function of the NR RLC device may include a function to rearrange the received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), and rearrange the order to prevent loss. It may include a function to record lost RLC PDUs, it may include a function to report the status of lost RLC PDUs to the transmitting side, and it may include a function to request retransmission of lost RLC PDUs. there is.

The in-sequence delivery function of the NR RLC device may include a function of delivering only the RLC SDUs up to the lost RLC SDU in order when there is a lost RLC SDU to the upper layer.

The in-sequence delivery function of the NR RLC device may include a function of delivering all RLC SDUs received before the timer starts to the upper layer in order if a predetermined timer expires even if there are lost RLC SDUs. there is.

The in-sequence delivery function of the NR RLC device may include a function of delivering all RLC SDUs received to date to the upper layer in order if a predetermined timer expires even if there are lost RLC SDUs.

The NR RLC device can process RLC PDUs in the order they are received and deliver them to the NR PDCP device, regardless of the order of the sequence number (out-of sequence delivery).

When the NR RLC device receives a segment, it can receive segments stored in a buffer or to be received later, reconstruct them into one complete RLC PDU, and then transmit it to the NR PDCP device.

The NR RLC layer may not include a concatenation function, and may perform the function in the NR MAC layer or replace it with the multiplexing function of the NR MAC layer.

In the above description, the out-of-sequence delivery function of the NR RLC device may refer to the function of directly delivering RLC SDUs received from a lower layer to the upper layer regardless of their order. The out-of-sequence delivery function of the NR RLC device may include a function of reassembling and delivering when one RLC SDU is originally received by being divided into several RLC SDUs. The out-of-sequence delivery function of the NR RLC device may include a function of storing the RLC SN or PDCP SN of received RLC PDUs, sorting the order, and recording lost RLC PDUs.

NR MAC (4-15, 4-30) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC may include some of the following functions.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing and demultiplexing function (Multiplexing/demultiplexing of MAC SDUs)

- Scheduling information reporting

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification function

- Transport format selection function

- Padding function

The NR PHY layer (4-20, 4-25) channel-codes and modulates the upper layer data, creates OFDM symbols and transmits them to the wireless channel, or demodulates and channel decodes the OFDM symbols received through the wireless channel and transmits them to the upper layer. The transfer operation can be performed.

Figure 5 is a block diagram showing the structure of a terminal according to an embodiment of the present invention.

Referring to Figure 5, the terminal includes an RF (Radio Frequency) processing unit 5-10, a baseband processing unit 5-20, a storage unit 5-30, and a control unit 5-40. .

The RF processing unit 5-10 performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. The RF processing unit 5-10 upconverts the baseband signal provided from the baseband processing unit 5-20 into an RF band signal and transmits it through an antenna, and converts the RF band signal received through the antenna into a baseband signal. Downconvert to a full-band signal. For example, the RF processing unit 5-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. You can. In the drawing, only one antenna is shown, but the terminal may be equipped with multiple antennas. Additionally, the RF processing unit 5-10 may include multiple RF chains. Furthermore, the RF processing unit 5-10 can perform beamforming. For the beamforming, the RF processing unit 5-10 can adjust the phase and size of each signal transmitted and received through a plurality of antennas or antenna elements. Additionally, the RF processing unit can perform MIMO and can receive multiple layers when performing a MIMO operation.

The baseband processing unit 5-20 performs a conversion function between baseband signals and bit strings according to the physical layer standard of the system. For example, when transmitting data, the baseband processing unit 5-20 generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit 5-20 restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 5-10. For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit 5-20 generates complex symbols by encoding and modulating the transmission bit stream, and transmits the complex symbols to subcarriers. After mapping, OFDM symbols are configured through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. In addition, when receiving data, the baseband processing unit 5-20 divides the baseband signal provided from the RF processing unit 5-10 into OFDM symbols and maps them to subcarriers through FFT (fast Fourier transform). After restoring the received signals, the received bit string is restored through demodulation and decoding.

The baseband processing unit 5-20 and the RF processing unit 5-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 5-20 and the RF processing unit 5-10 may be referred to as a transmitting unit, a receiving unit, a transceiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit 5-20 and the RF processing unit 5-10 may include multiple communication modules to support multiple different wireless access technologies. Additionally, at least one of the baseband processing unit 5-20 and the RF processing unit 5-10 may include different communication modules to process signals in different frequency bands. For example, the different wireless access technologies may include wireless LAN (eg, IEEE 802.11), cellular network (eg, LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (e.g., 60GHz) band.

The storage unit 5-30 stores data such as basic programs, application programs, and setting information for operation of the terminal. In particular, the storage unit 5-30 may store information related to a second access node that performs wireless communication using a second wireless access technology. Additionally, the storage unit 5-30 provides stored data upon request from the control unit 5-40.

The control unit 5-40 controls overall operations of the terminal. For example, the control unit 5-40 transmits and receives signals through the baseband processing unit 5-20 and the RF processing unit 5-10. Additionally, the control unit 5-40 writes and reads data into the storage unit 5-40. For this purpose, the control unit 5-40 may include at least one processor. For example, the control unit 5-40 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

Figure 6 is a block diagram showing the configuration of an NR base station according to an embodiment of the present invention.

As shown in FIG. 6, the base station includes an RF processing unit 6-10, a baseband processing unit 6-20, a backhaul communication unit 6-30, a storage unit 6-40, and a control unit 6-50. It is composed including.

The RF processing unit 6-10 performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. The RF processing unit 6-10 upconverts the baseband signal provided from the baseband processing unit 6-20 into an RF band signal and transmits it through an antenna, and converts the RF band signal received through the antenna into a baseband signal. Downconvert to a full-band signal. For example, the RF processing unit 6-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is shown, but the first access node may be equipped with multiple antennas. Additionally, the RF processing unit 6-10 may include multiple RF chains. Furthermore, the RF processing unit 6-10 can perform beamforming. For the beamforming, the RF processing unit 6-10 can adjust the phase and size of each signal transmitted and received through a plurality of antennas or antenna elements. The RF processing unit can perform downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 6-20 performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the first wireless access technology. For example, when transmitting data, the baseband processing unit 6-20 generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit 6-20 restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 6-10. For example, in the case of OFDM, when transmitting data, the baseband processing unit 6-20 generates complex symbols by encoding and modulating the transmission bit stream, maps the complex symbols to subcarriers, and performs IFFT. OFDM symbols are constructed through operations and CP insertion. In addition, when receiving data, the baseband processing unit 6-20 divides the baseband signal provided from the RF processing unit 6-10 into OFDM symbols and restores signals mapped to subcarriers through FFT operation. After that, the received bit string is restored through demodulation and decoding. The baseband processing unit 6-20 and the RF processing unit 6-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 6-20 and the RF processing unit 6-10 may be referred to as a transmitting unit, a receiving unit, a transceiving unit, a communication unit, or a wireless communication unit.

The backhaul communication unit 6-30 provides an interface for communicating with other nodes in the network. The backhaul communication unit 6-30 converts a bit string transmitted from the main base station to another node, for example, an auxiliary base station, a core network, etc., into a physical signal, and converts the physical signal received from the other node into a bit string. Convert.

The storage unit 6-40 stores data such as basic programs, application programs, and setting information for operation of the main base station. In particular, the storage unit 6-40 can store information about bearers assigned to the connected terminal, measurement results reported from the connected terminal, etc. Additionally, the storage unit 6-40 can store information that serves as a criterion for determining whether to provide or suspend multiple connections to the terminal. Additionally, the storage unit 6-40 provides stored data upon request from the control unit 6-50.

The control unit 6-50 controls overall operations of the base station. For example, the control unit 6-50 transmits and receives signals through the baseband processing unit 6-20 and the RF processing unit 6-10 or through the backhaul communication unit 6-30. Additionally, the control unit 6-50 writes and reads data into the storage unit 6-40. For this purpose, the control unit 6-50 may include at least one processor.

In the present invention, when performing conditional PCell handover, the terminal can receive an RRCReconfiguration message including a conditional Reconfiguration field with the following structure from the network. Hereinafter, it will be described with reference to FIG. 7.

Figure 7 shows the structure of the conditional reconfiguration field received by the terminal.

The Conditional Reconfiguration field has a list structure, and one entry in the list consists of a condReconfiguration Id, a condition, and an RRCReconfiguration message that the terminal must apply if the condition is satisfied. Each element is as follows.

- Here, condReconfiguration Id is created/assigned by S-MN. It is linked to each condition and the RRCReconfiguration message to be applied when the condition is met. All IDs must be unique for each target MCG.

- The condition is created by the S-MN and expressed as a measurement ID corresponding to the condition in the measurement setting information set by the S-MN to the terminal. Therefore, the S-MN must implement the measurement Id, measurement object, and report configuration corresponding to this ID in the measurement settings and set them to the terminal.

- RRCReconfiguration is created in T-MN. This again consists of target MCG settings, target SCG settings, and internal conditional Reconfiguration fields. Each part has additional explanation as follows.

■ Target MCG settings are created by T-MN in response to a specific PCell. For a specific T-MN, PCell/i.e., MCG may also be multiple. Additionally, the T-MN itself may be multiple MN. This includes the reconfigurationWithSync field.

■ Target SCG setting is based on the target MCG, so that a specific T-SN is directly applied when performing CHO (conditional handover) in response to a specific PSCell among its cells. The RECONFIGURATIONWITHSYNC field may or may not be included. If included, the new SCG can be applied immediately, and if not included, it can be used to update the current SCG settings.

■ The internal conditional reconfiguration field is written by T-MN. This conditional Reconfiguration field has a list structure, and one entry in the list consists of a condReconfiguratoin Id, a condition, and an RRCReconfiguration message that the terminal must apply if the condition is satisfied. Each element is as follows.

◆ condReconfig ID is created/assigned by T-MN. It is linked to each condition and the RRCReconfiguration message to be applied when the condition is met. The Id must be unique for each specific T-MN or specific target MCG.

◆ Condition is determined by T-MN. The measurement setting information that the T-MN sets for the terminal is expressed as a measurement ID corresponding to the condition. Therefore, the T-MN must implement the measurement Id, measurement object, and report configuration corresponding to this ID in the measurement settings and set them in the target MCG settings delivered together.

◆ RRCReconfiguration consists of target MCG settings and one specific candidate SCG setting information. Target MCG settings are settings based on the target MCG present in RRCReconfiguration in the external conditional Reconfiguration field or based on the target PCell. Candidate SCG config includes a reconfigurationWithSync field.

The terminal that has received the RRCReconfiguration message including the external conditional Reconfiguration from the S-MN can configure the id, condition, and condRRCReconfig (i.e., RRCReconfiguration message) into respective entries and store them in terminal variables. You can then start measuring for the relevant conditions and begin evaluating the conditions. If one of the conditions of external conditional Reconfiguration is satisfied, condRRCReconfig associated with it is applied. At this time, when performing operations according to the existing RRC standard, the following problems may occur. This will be described later with reference to FIG. 11 .

The operation of the terminal applying RRCReconfiguration is sequentially

1) Apply specific settings,

2) Check whether conditional Reconfiguration is included in RRCReconfiguration. If so, perform the conditional Reconfiguration entry add/modification/release given in the terminal variable, then start evaluating the condition and jump back to the RRCReconfig execution action when the condition is satisfied.

3) Apply specific settings

4) Write RRCReconfigurationComplete

5) Operation after RACH success

6) If the MCG or SCG includes reconfigurationWithSync, all entries in the terminal variable are deleted, and the reportconfig for condition is deleted from the measConfig of the source SPCell, the MO for only conditional Reconfig is also deleted, and the reportconfig for condition and the measId associated with it are also deleted.

Previously, it was not possible to include another conditional Reconfiguration field inside a conditional Reconfiguration. Accordingly, step 2) was performed only when the terminal received conditional Reconfiguration from the network (when performing CHO / CPAC, the operation of applying the RRCReconfiguration is performed again, but in this case, step 2) was skipped. ). However, according to this proposal, if another conditional Reconfiguration field is stored within the conditional Reconfiguration field, step 2) must be performed again when performing CHO/CPAC. Accordingly, by performing a new add/modify/release operation on the variable where the existing entry currently operated by the terminal is stored, the cond Reconfig ID can also have the same value, and unnecessary existing conditional reconfiguration entries and new entries can be added in the future. It gets mixed up. In addition, since all information, including the new entry just added in step 6), is erased, the information that the terminal must maintain is also erased.

As a solution to this, three methods are possible.

Opt 1. During the reconfiguration application process, the fulfilled condRRCReconfig is temporarily stored in the terminal's internal buffer, and its value is used when applying the terminal, so deleting the terminal variable contents in step 6) affects the storage of new conditional reconfiguration information. Assumption that it is not given.

In this case, in step 2), it is separated based on the information on whether CHO/CPAC is being performed or not, and if this RRCReconfiguration application is not for CHO/CPAC execution, the existing conditional Reconfiguration terminal variables add/mod/release and After performing target cell monitoring and execution operations, performing all other existing RRCReconfiguration application sequences, and clearing the terminal's variables and related measurement setting information, if this RRCReconfiguration application is for CHO/CPAC performance, it corresponds to the terminal variable. A process can be introduced that adds/mod/releases entries for conditional reconfiguration, monitors the target cell (candidate PSCell in this case), evaluates the condition, and performs CPAC when the condition is satisfied.

The operation is as follows.

If the conditions of CHO (conditions written by S-MN of external conditional reconfiguration) are satisfied, section 5.3.5.3 of the RRC standard begins.

1) Apply specific settings,

2) Check whether conditional Reconfiguration is included in RRCReconfiguration, and if the application of this RRCReconfiguration is not for the application of conditional reset, then after performing the conditional Reconfiguration entry add/modification/release given in the terminal variable, the corresponding condition evaluation begins and when the condition is satisfied, RRCReconfig Jump back to the action performed

3) Apply specific settings

4) Write RRCReconfigurationComplete

5) Operation after RACH success

6) If the MCG or SCG includes reconfigurationWithSync, all entries in the terminal variable are deleted, and the reportconfig for condition is deleted from the measConfig of the source spcell. The MO for only conditional Reconfig is also deleted, and the reportconfig for condition and the measId associated with it are also deleted.

7) Check whether conditional Reconfiguration is included in RRCReconfiguration, and if the application of this RRCReconfiguration is for the application of conditional reset, then perform the conditional Reconfiguration entry add/modification/release given in the terminal variable, then start evaluating the condition and perform RRCReconfig when the condition is satisfied. jump back into motion

(Start 5.3.5.3

ㆍ Skipped

ㆍ 1> if the RRCReconfiguration message includes the conditionalReconfiguration, and to apply this RRCReconfiguration is not for conditionalReconfiguration execution :

2> perform conditional reconfiguration as specified in 5.3.5.13; (i.e. add/mod/release, target cell monitoring, and execution)

ㆍThe rest is the same skipped

ㆍ Complete msg creation / RACH successful execution

ㆍIf reconfig withSync is included

Delete the existing UE Var entry and delete measId.

1. If the RRCReconfiguration message includes the conditionalReconfiguartion, and to apply this RRCReconfiguration is for conditionalReconfiguration execution:

ㆍ2> perform conditional reconfiguration as specified in 5.3.5.13

)

Opt 2.

Using the new UE Var, information related to internal conditional reconfiguration is separately added/mod/released, the target cell is monitored, and condition evaluation is performed. The operation is as follows.

If the conditions of CHO (conditions written by S-MN of external conditional reconfiguration) are satisfied, section 5.3.5.3 of the RRC standard begins.

1) Apply specific settings,

2) Check whether conditional Reconfiguration is included in RRCReconfiguration, and if the application of this RRCReconfiguration is not for the application of conditional reset, then perform the conditional Reconfiguration entry add/modification/release given in the terminal variable and start evaluating the condition, and when the condition is satisfied, RRCReconfig Jump back to the action performed;

2-1) Check whether conditional Reconfiguration is included in RRCReconfiguration, and if the application of this RRCReconfiguration is for the application of conditional reset, then perform the conditional Reconfiguration entry add/modification/release given in the new terminal variable and start evaluating the condition and when the condition is satisfied. Jump back to RRCReconfig performing action;

3) Apply specific settings

4) Write RRCReconfigurationComplete

5) Operation after RACH success

6) If the MCG or SCG includes reconfigurationWithSync, all entries in the terminal variable are deleted, and the reportconfig for condition is deleted from the measConfig of the source spcell. The MO for only conditional Reconfig is also deleted, and the reportconfig for condition and the measId associated with it are also deleted.

ㆍ(5.3.5.3 Start

ㆍ Skipped

ㆍ1> if the RRCReconfiguration message includes the conditionalReconfiguration, and to apply this RRCReconfiguration is not for conditionalReconfiguration execution :

ㆍ2> perform conditional reconfiguration as specified in 5.3.5.13; (i.e. add/mod/release, target cell monitoring, and execution)

1. If the RRCReconfiguration message includes the conditionalReconfiguartion, and to apply this RRCReconfiguration is for conditional Reconfiguration execution:

ㆍ2> perform conditional reconfiguration as specified in 5.3.5.13 to new UE Variable CPAC;

ㆍThe rest is the same skipped

ㆍ Complete msg creation / RACH successful execution

ㆍIf reconfig withSync is included

Delete the existing UE Var entry and delete measId.

)

Opt 3. In the operation of deleting existing terminal variable entries, delete the remaining entries except for the entry containing RRCReconfiguration to be applied, and delete the rest after necessary work. The following is the corresponding operation.

If the conditions of CHO (conditions written by S-MN of external conditional reconfiguration) are satisfied, section 5.3.5.3 of the RRC standard begins.

1) Apply specific settings,

2) Check whether conditional Reconfiguration is included in RRCReconfiguration, and if the application of this RRCReconfiguration is not for the application of conditional reset, then perform the conditional Reconfiguration entry add/modification/release given in the terminal variable and start evaluating the condition, and when the condition is satisfied, RRCReconfig Jump back to the action performed

3) Apply specific settings

4) Write RRCReconfigurationComplete

5) Operation after RACH success

6) If MCG or SCG includes reconfigurationWithSync, delete all entries of terminal variables except the entry corresponding to RRCReconfiguration currently being applied, delete reportconfig for condition from measConfig of source spcell, also delete MO for only conditional Reconfig, condition Also delete reportconfig and the measId associated with it.

7) Check whether conditional Reconfiguration is included in RRCReconfiguration, and if the application of this RRCReconfiguration is for the application of conditional reset, then perform the conditional Reconfiguration entry add/modification/release given in the terminal variable, then start evaluating the condition and perform RRCReconfig when the condition is satisfied. jump back into motion

8) Delete the entry corresponding to the currently applied RRCReconfiguration from the terminal variables.

ㆍ(5.3.5.3 Start

ㆍ Skipped

ㆍ1> if the RRCReconfiguration message includes the conditionalReconfiguration, and this RRCReconfiguration is not for conditionalReconfiguration execution :

2> perform conditional reconfiguration as specified in 5.3.5.13; (i.e. add/mod/release, target cell monitoring, and execution)

ㆍThe rest is the same skipped

ㆍComplete msg creation/RACH successful execution

ㆍIf reconfig withSync is included

In the existing UE Var, delete the rest except the triggered entry, and delete the measId.

1. If the RRCReconfiguration message includes the conditionalReconfiguartion, and this is for conditional Reconfiguration execution:

ㆍ2> perform conditional reconfiguration as specified in 5.3.5.13

ㆍDelete triggered entry from existing UE Var.

)

Figure 8 shows the operation upon initial setting of the operation proposed in this disclosure.

The UE can transmit processing capability information to the S-MN indicating that conditional handover including multiple candidate SCG settings is possible. After that, S-SN is set as the SN for dual connection. The S-MN, which receives the terminal's measurement results, determines the target PCell and transmits a HOReq message to the corresponding T-MN. At this time, along with the conditional handover indicator, an indicator to operate the candidate SCG setting may be included. A combination of the two indicators or the latter indicator alone may indicate an instruction to the T-MN to perform CPAC setting.

The T-MN that receives this determines the T-SN and sends a SNAddReq message to the T-SN, including a CPAC indicator, an indicator requesting conditional PSCell change, or an indicator requesting conditional CHO + CPC settings. Can be transmitted. At this time, multiple SNs may be selected as T-SN candidate SNs. Each SN can determine its own PSCell and transmit information (PSCell PCI, frequency) and configuration information (candidate SCG configuration information) of the PSCell to the T-MN through the SNAddReqACK message.

The T-MN, which has received the above information, satisfies the requirements for application of the received candidate SCG configuration information, MCG configuration information (i.e., MCG configuration information) reflecting the corresponding SCG configuration information, and each candidate SCG (PSCell) determined by the T-MN. The conditions to be configured are grouped into one condReconfig ID, and multiple lists are stored in the conditional Reconfiguration field. The above condition information may include at least one of the following information.

- Among RRM reporting settings for conditions, it indicates events of A3 and/or A4 and/or A5, which are events used for size comparison between cells based on radio signals, or B1 or B2, which are size comparisons between inter-RAT cells. information,

- And/or for information indicating each event, as parameter information required for the indicated event,

■ For A4, or B1, RSRP/RSRQ/RSSI value as a threshold for the measurement value of the corresponding candidate PSCell

■ For A3, RSRP/RSRQ/RSSI value as the offset value of the measurement value difference between the terminal's current PSCell and the corresponding candidate PSCell.

■ For A5 or B2, the RSRP/RSRQ/RSSI value as the threshold for the measurement value of the current PSCell and the threshold for the measurement value of the corresponding candidate PSCell.

In addition, when the current conditional handover is performed, the configuration information for the target PCell, that is, the target MCG configuration information, and the target SCG configuration information to be applied immediately along with the target MCG are all combined into one RRCReconfiguration message. At this time, the condition information may be included in an Xn field or RRC field separate from the target MCG and target SCG setting information and transmitted from T-MN to S-MN.

The T-MN transmits the RRCReconfiguration message and/or condition-related information to the S-MN through the HOReqACK message.

The S-MN that has received this can create conditions for applying the MCG for the received RRCReconfiguration message or the received specific target MCG configuration information and SCG configuration information pair. And the conditions for applying the MCG, the conditions for applying the SCG settings among the pair, and the RRCReconfiguration corresponding to the MCG and SCG setting pair are grouped into condReconfig Id, and the list is configured with each entry in the conditional Reconfiguration field to be sent to the terminal. Deliver. At this time, the message can use the RRCReconfiguration message created by the S-MN.

The conditions for applying the SCG settings among the pairs can be determined by the S-MN by considering the condition information corresponding to the specific SCG transmitted from the T-MN. For example, when the T-MN transmits event type A4 and/or threshold value for a specific SCG to the S-MN, the S-MN configures the frequency of the PSCell indicating the corresponding SCG as a measurement object in its measurement configuration. And, the event type delivered by the S-MN can be configured as conditional event A4 in its reportConfiguration and delivered to the terminal.

The terminal that receives this stores the id, condition, and condRRCReconfig (i.e., RRCReconfiguration message for each entry) included in the external conditional Reconfiguration in a terminal variable and begins evaluating the condition by performing measurements corresponding to the condition. If a specific condition is satisfied, condRRCReconfig (RRCReconfiguration) associated with that condition is applied. In this process, the terminal follows one of the RRC setting application methods (opt 1, 2, and 3) described above in relation to FIG. 12.

The terminal notifies the completion of target MCG configuration by sending an RRCReconfigurationComplete message to the T-MN operating the corresponding MCG, that is, the PSCell, based on the target MCG with which the satisfied conditions are associated. And when the RRCReconfiguration application is completed, the internal conditional reconfiguration is stored in the terminal variable, the settings of the candidate SCGs based on the target MCG are stored in the terminal variable, and each candidate SCG is assigned based on the measurement information set by the relevant T-MN. Start measuring for the conditions and begin evaluating the conditions. (CPAC evaluation begins). Afterwards, if one of the CPAC conditions being evaluated is satisfied, an operation is performed to apply the corresponding candidate SCG.

Figure 9 shows a procedure for reflecting the setting in the CHO with candidate SCG setting if there is a change in the current MCG setting of the S-MN after setting the conditional handover for the first candidate SCG to the UE.

After the UE receives the initial CHO with candidate SCG configuration, if the configuration of the source MCG needs to be changed, the S-MN transmits the HOReq message to the T-MN, including an indicator that the candidate SCG configuration information must be modified. The T-MN that received this can deliver the SNAddReq message including the CPAC update indicator to the T-SNs for which the existing candidate SCG has been established, and the T-SN that received this can update the message based on the existing S-MCG settings. The candidate SCG settings can be updated and delivered to the T-MN, and the T-MN delivers them to the S-MN. Finally, the S-MN updates the updated candidate SCG settings information for each cond Reconfig ID maintained in the existing conditionalReconfiguration. You can instruct to modify the RRCReconfiguratoin message.

FIG. 10 is a diagram illustrating the necessary procedures when it is desired to release the candidate SCG maintained in the T-SN after initially setting Cho with candidate SCG.

T-SN can release a specific candidate SCG if it wishes. In this case, candidate SCG or candidate PSCell ID (PCI, and/or CGI) information can be delivered to the T-MN as an Xn message. The T-MN that has received this information can remove the entry containing the candidate SCG from the internal conditional reconfiguration and include the release of unnecessary measurement configuration in the target MCG config. This changed setting can be reflected in the RRCREconfiguration message and delivered to the S-MN. At this time, the cause value can be transmitted including an indicator indicating the release of the candidate SCG or change in the settings of the target MCG. After receiving this, the S-MN delivers the changed RRCReconfiguration message to the cond Reconfig ID entry corresponding to the changed RRCReconfiguration message. The terminal overwrites the newly received RRCReconfiguration message in the entry of the corresponding condReconfig ID.

Figure 11 shows the operations and sequence performed by the terminal when receiving the current RRCReconfiguration and the problematic part in that case. The left part refers to section 5.3.5.3 of the RRC standard, that is, terminal operation when receiving RRCReconfiguration. This content is the same as the content mentioned previously and is a more condensed version of the next step. (Step 1 is omitted in the content below.)

1) Apply specific settings,

2) Check whether conditional Reconfiguration is included in RRCReconfiguration. If so, perform the conditional Reconfiguration entry add/modification/release given in the terminal variable, then start evaluating the condition and jump back to the RRCReconfig execution action when the condition is satisfied.

3) Apply specific settings

4) Write RRCReconfigurationComplete

5) Operation after RACH success

6) If the MCG or SCG includes reconfigurationWithSync, all entries in the terminal variable are deleted, and the reportconfig for condition is deleted from the measConfig of the source SPCell, the MO for only conditional Reconfig is also deleted, and the reportconfig for condition and the measId associated with it are also deleted.

The right side of the drawing explains the problematic part in the specific step above.

Methods according to embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present invention.

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM: Compact Disc-ROM), Digital Versatile Discs (DVDs), or other types of It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.

In addition, the program may be operated through a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present invention through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present invention.

In the specific embodiments of the present invention described above, components included in the invention are expressed in singular or plural numbers depending on the specific embodiment presented. However, singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the patent claims described later, but also by the scope of this patent claim and equivalents.

Claims (1)

In a control signal processing method in a wireless communication system,
Receiving a first control signal transmitted from a base station;
processing the received first control signal; and
A control signal processing method comprising transmitting a second control signal generated based on the processing to the base station.