KR20230162269A - Method and Apparatus for in-Device coexistence in wireless communication system - Google Patents

Abstract

According to an embodiment of the present disclosure, in the UE method, transmitting UECapabilityInformation to a base station, the UECapabilityInformation includes UE-NR-Capability, the UE-NR-Capability includes inDeviceCoexInd, and receive RRCReconfiguration from the base station. And, transmit UEAssistanceInformation to the base station, where the UEAssistanceInformation includes all or part of the first IDC support information, second IDC support information, and third IDC support information, receive a second RRCReconfiguration from the base station, and the second RRCReconfiguration is reconfigurationWithSync and if transmission of the UEAssistanceInformation for the second IDC assistance information started in the first cell in the last 1 second and the UE is still configured to provide the second IDC assistance information, second IDC support from the second cell to the base station. Transmits UEAssistanceInformation containing information.

Description

{Method and Apparatus for in-Device coexistence in wireless communication system}

The present disclosure relates to a method and device for in-device coexistence in a wireless mobile communication system.

To meet the increasing demand for wireless data traffic following the commercialization of the 4G communication system, the 5G communication system was developed. To achieve high data rates, 5G communication systems have introduced ultra-high frequency (mmWave) bands (such as the 60-gigabit (60GHz) band). In order to alleviate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, the 5G communication system uses beamforming, massive array multiple input/output (massive MIMO), and full dimension multiple input/output (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are used. In the 5G communication system, scalability is increased by dividing the base station into a central unit and a distributed unit. Additionally, the 5G communication system aims to support extremely high data rates and extremely low transmission delays in order to support a variety of services.

An increasing number of UEs are equipped with multiple radio transceivers to enable users to ubiquitously access various networks and services. For example, the UE may be equipped with NR, WiFi and Bluetooth transceivers and GNSS receivers. Due to the extreme proximity of multiple radio transceivers within the same UE operating at adjacent or sub-harmonic frequencies, the interference power from the transmitters of the deployed radios may be much higher than the actual received power level of the desired signal for the receiver. This situation is It causes IDC (Intra-Device Coexistence) interference and is called IDC problem. The challenge lies in avoiding or minimizing IDC interference between deployed wireless transceivers, as current state-of-the-art filter technologies may not provide sufficient rejection for certain scenarios.

The present disclosure seeks to provide a method and device for in-device coexistence in a wireless mobile communication system.

According to an embodiment of the present disclosure, in the UE method, transmitting UECapabilityInformation to a base station, the UECapabilityInformation includes UE-NR-Capability, the UE-NR-Capability includes inDeviceCoexInd, and receive RRCReconfiguration from the base station. and transmit UEAssistanceInformation to the base station, where the UEAssistanceInformation includes all or part of the first IDC support information, second IDC support information, and third IDC support information, and receive a second RRCReconfiguration from the base station, and the second RRCReconfiguration is reconfigurationWithSync and if transmission of UEAssistanceInformation for second IDC assistance information has started in the first cell in the last 1 second and the UE is still configured to provide second IDC assistance information, second IDC support from the second cell to the base station. Transmits UEAssistanceInformation containing information.

The present disclosure provides a method and apparatus for in-device coexistence in a wireless mobile communication system.

FIG. 1A is a diagram illustrating the structure of a 5G system and NG-RAN according to an embodiment of the present disclosure.
FIG. 1B is a diagram illustrating a wireless protocol structure in an NR system according to an embodiment of the present disclosure.
FIG. 1C is a diagram illustrating transitions between RRC states according to an embodiment of the present disclosure.
Figure 1D is a diagram showing bandwidth portion adjustment and bandwidth portion.
Figure 1e is a diagram explaining the search interval and control resource set.
FIG. 2A is a diagram explaining the operation of a terminal and a base station according to an embodiment of the present disclosure.
FIG. 3A is a flowchart for explaining the operation of a terminal according to an embodiment of the present disclosure.
Figure 4a is a block diagram showing the internal structure of a terminal to which the present invention is applied.
Figure 4b is a block diagram showing the internal structure of a base station to which the present invention is applied.

Hereinafter, embodiments of the present invention will be described in detail with the accompanying drawings. Additionally, when describing the present invention, if it is determined that a detailed description of a related known function or configuration may 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.

For convenience of description below, the present invention uses terms and names defined in the 3rd Generation Partnership Project (3GPP) standard, which is the latest standard among currently existing communication standards. However, the present invention is not limited by the above terms and names, and can be equally applied to systems complying with other standards.

Table 1 lists the abbreviations used in the present invention.

Acronym Full name Acronym Full name 5GC 5G Core Network RACH Random Access Channel ACK Acknowledgment RAN Radio Access Network A.M. Acknowledged Mode RA-RNTI Random Access RNTI AMF Access and Mobility Management Function RAT Radio Access Technology ARQ Automatic Repeat Request RB Radio Bearer AS Access Stratum R.L.C. Radio Link Control ASN.1 Abstract Syntax Notation One RNA RAN-based Notification Area BSR Buffer Status Report RNAU RAN-based Notification Area Update BWP Bandwidth Part RNTI Radio Network Temporary Identifier CA Carrier Aggregation RRC Radio Resource Control C.A.G. Closed Access Group RRM Radio Resource Management CG Cell Group RSRP Reference Signal Received Power C-RNTIs Cell RNTI RSRQ Reference Signal Received Quality CSI Channel State Information RSSI Received Signal Strength Indicator DCI Downlink Control Information SCell Secondary Cell D.R.B. (user) Data Radio Bearer SCS Subcarrier Spacing DRX Discontinuous Reception SDAP Service Data Adaptation Protocol HARQ Hybrid Automatic Repeat Request SDU Service Data Unit I.E. Information element SFN System Frame Number LCG Logical Channel Group S-GW Serving Gateway MAC Medium Access Control SI System Information MIB Master Information Block SIB System Information Block NAS Non-Access Stratum SpCell Special Cell NG-RAN NG Radio Access Network S.R.B. Signaling Radio Bearer NR NR Radio Access SRS Sounding Reference Signal PBR Prioritized Bit Rate SSB SS/PBCH block PCell Primary Cell SSS Secondary Synchronization Signal PCI Physical Cell Identifier SUL Supplementary Uplink PDCCH Physical Downlink Control Channel TM Transparent Mode PDCP Packet Data Convergence Protocol UCI Uplink Control Information PDSCH Physical Downlink Shared Channel UE User Equipment PDU Protocol Data Unit UM Unacknowledged Mode PHR Power Headroom Report IDC In-Device Coexistence PLMN Public Land Mobile Network PRS Positioning Reference Signal PRACH Physical Random Access Channel CS-RNTI Configured Scheduling-RNTI PRB Physical Resource Block TAG Timing Advance Group P.S.S. Primary Synchronization Signal SDT Small Data Transmission PUCCH Physical Uplink Control Channel RA-SDT Random Access-SDT PUSCH Physical Uplink Shared Channel CG-SDT Configured Grant-SDT PTAG PRIMARY TAG STAG Secondary TAG

Table 2 defines terms frequently used in the present invention.

Terminology Definition allowedCG-List List of configured grants for the corresponding logical channel. This restriction applies only when the UL grant is a configured grant. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any configured grant configurations. allowedSCS-List List of allowed sub-carrier spacings for the corresponding logical channel. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated numerology. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured numerology. allowedServingCells List of allowed serving cells for the corresponding logical channel. If present, UL MAC SDUs from this logical channel can only be mapped to the serving cells indicated in this list. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured serving cell of this cell group. Carrier frequency center frequency of the cell. Cell combination of downlink and optionally uplink resources. The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources. Cell Group in dual connectivity, a group of serving cells associated with either the MeNB or the SeNB. Cell selection A process to find a better suitable cell than the current serving cell based on the system information received in the current serving cell Cell selection A process to find a suitable cell either blindly or based on the stored information Dedicated signaling Signalling sent on DCCH logical channel between the network and a single UE. discardTimer Timer to control the discard of a PDCP SDU. Starting when the SDU arrives. Upon expiry, the SDU is discarded. F The Format field in MAC subheader indicates the size of the Length field. Field The individual contents of an information element are referred to as fields. Frequency layer set of cells with the same carrier frequency. Global cell identity An identity to uniquely identify an NR cell. It is comprised of cellIdentity and plmn-Identity of the first PLMN-Identity in plmn-IdentityList in SIB1. gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. Handover procedure that changes the serving cell of a UE in RRC_CONNECTED. Information element A structural element containing single or multiple fields is referred as information element. L The Length field in MAC subheader indicates the length of the corresponding MAC SDU or of the corresponding MAC CE LCID 6 bit logical channel identity in MAC subheader to denote which logical channel traffic or which MAC CE is included in the MAC subPDU MAC-I Message Authentication Code - Integrity. 16 bit or 32 bit bit string calculated by NR Integrity Algorithm based on the security key and various fresh inputs Logical channels a logical path between a RLC entity and a MAC entity. There are multiple logical channel types depending on what type of information is transferred e.g. CCCH (Common Control Channel), DCCH (Dedicate Control Channel), DTCH (Dedicate Traffic Channel), PCCH (Paging Control Channel) LogicalChannelConfig The IE LogicalChannelConfig is used to configure the logical channel parameters. It includes priority, prioritisedBitRate, allowedServingCells, allowedSCS-List, maxPUSCH-Duration, logicalChannelGroup, allowedCG-List etc logicalChannelGroup ID of the logical channel group, as specified in TS 38.321, which the logical channel belongs to MAC C.E. Control Element generated by a MAC entity. Multiple types of MAC CEs are defined, each of which is indicated by corresponding LCID. A MAC CE and a corresponding MAC sub-header comprises MAC subPDU Master Cell Group in MR-DC, a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells. maxPUSCH-Duration Restriction on PUSCH-duration for the corresponding logical channel. If present, UL MAC SDUs from this logical channel can only be transmitted using uplink grants that result in a PUSCH duration shorter than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel can be transmitted using an uplink grant resulting in any PUSCH duration. NR NR radio access PCell SpCell of a master cell group. PDCP entity reestablishment The process triggered upon upper layer request. It includes the initialization of state variables, reset of header compression and manipulating of stored PDCP SDUs and PDCP PDUs. The details can be found in 5.1.2 of 38.323 PDCP suspend The process triggered upon upper layer request. When triggered, transmitting PDCP entity set TX_NEXT to the initial value and discard all stored PDCP PDUs. The receiving entity stop and reset t-Reordering, deliver all stored PDCP SDUs to the upper layer and set RX_NEXT and RX_DELIV to the initial value PDCP-config The IE PDCP-Config is used to set the configurable PDCP parameters for signaling and data radio bearers. For a data radio bearer, discardTimer, pdcp-SN-Size, header compression parameters, t-Reordering and whether integrity protection is enabled are configured. For a signaling radio bearer, t-Reordering can be configured PLMN ID Check the process that checks whether a PLMN ID is the RPLMN identity or an EPLMN identity of the UE. Primary Cell The MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Primary SCG Cell For dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure. priority Logical channel priority, as specified in TS 38.321. an integer between 0 and 7. 0 means the highest priority and 7 means the lowest priority PUCCH SCell a Secondary Cell configured with PUCCH. Radio Bearer Logical path between a PDCP entity and upper layer (i.e. SDAP entity or RRC) RLC bearer RLC and MAC logical channel configuration of a radio bearer in one cell group. RLC bearer configuration The lower layer part of the radio bearer configuration comprising the RLC and logical channel configurations. RX_DELIV This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited for. RX_NEXT This state variable indicates the COUNT value of the next PDCP SDU expected to be received. RX_REORD This state variable indicates the COUNT value following the COUNT value associated with the PDCP Data PDU which triggered t-Reordering. Serving Cell For a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. For a UE in RRC_CONNECTED configured with CA/ DC the term 'serving cells' is used to denote the set of cells comprising of the Special Cell(s) and all secondary cells. SpCell primary cell of a master or secondary cell group. Special Cell For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term Special Cell refers to the PCell. S.R.B. Signalling Radio Bearers" (SRBs) are defined as Radio Bearers (RBs) that are used only for the transmission of RRC and NAS messages. SRB0 SRB0 is for RRC messages using the CCCH logical channel SRB1 SRB1 is for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using DCCH logical channel; SRB2 SRB2 is for NAS messages and for RRC messages which include logged measurement information, all using DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by the network after AS security activation; SRB3 SRB3 is for specific RRC messages when UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel SRB4 SRB4 is for RRC messages which include application layer measurement reporting information, all using DCCH logical channel. Suitable cell A cell on which a UE may camp. Following criteria apply
- The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list
-The cell is not barred
- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas for Roaming" (TS 22.011 [18]), which belongs to a PLMN that fulfills the first bullet above.
- The cell selection criterion S is fulfilled (ie RSRP and RSRQ are better than specific values t-Reordering Timer to control the reordering operation of received PDCP packets. Upon expiry, PDCP packets are processed and delivered to the upper layers. TX_NEXT This state variable indicates the COUNT value of the next PDCP SDU to be transmitted. UE Inactive AS Context UE Inactive AS Context is stored when the connection is suspended and restored when the connection is resumed. It includes information below.
the current KgNB and KRRCint keys, the ROHC state, the stored QoS flow to DRB mapping rules, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell, the spCellConfigCommon within ReconfigurationWithSync of the NR PSCell (if configured) and all other parameters configured except for:
- parameters within ReconfigurationWithSync of the PCell;
- parameters within ReconfigurationWithSync of the NR PSCell, if configured;
- parameters within MobilityControlInfoSCG of the E-UTRA PSCell, if configured;
-servingCellConfigCommonSIB; TAG A group of Serving Cells that is configured by RRC and that, for the cells with a UL configured, using the same timing reference cell and the same Timing Advance value. A Timing Advance Group containing the SpCell of a MAC entity is referred to as Primary Timing Advance Group (PTAG), whereas the term Secondary Timing Advance Group (STAG) refers to other TAGs.

In the present invention, “trigger” or “is triggered” and “initiate” or “is initiated” may be used with the same meaning. In the present invention, “radio bearer for which the second resumption procedure is allowed”, “radio bearer for which the second resumption procedure is configured”, and “radio bearer for which the second resumption procedure is enabled” may all be used with the same meaning.

In the present invention, the second restart procedure may be used in the same sense as SDT (Small Data Transmission).

In the present invention, terminal and UE may be used with the same meaning. In the present invention, base station and NG-RAN node may be used with the same meaning.

FIG. 1A is a diagram illustrating the structures of a 5G system and NG-RAN according to an embodiment of the present disclosure.

The 5G system consists of NG-RAN (1a-01) and 5GC (1a-02). The NG-RAN node is one of the two below.

1: gNB providing NR user plane and control plane towards UE; or

2: ng-eNB providing E-UTRA user plane and control plane towards UE.

gNB (1a-05 to 1a-06) and ng-eNB (1a-03 to 1a-04) are interconnected through the Xn interface. The gNB and ng-eNB are connected to the Access and Mobility Management Function (AMF) (1a-07) and the User Plane Function (UPF) (1a-08) through the NG interface. AMF (1a-07) and UPF (1a-08) can be configured as one physical node or as separate physical nodes.

gNB (1a-05 to 1a-06) and ng-eNB (1a-03 to 1a-04) host the functions listed below.

Radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink, downlink and sidelink (scheduling), IP and Ethernet header compression, uplink data decompression and encryption of user data streams, Selection of AMF if the AMF cannot be selected with the information provided, routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (from AMF or O&M);

Configuration of measurements and measurement reporting for mobility and scheduling, session management, QoS flow management and mapping for data radio bearers, RRC_INACTIVE support, radio access network sharing;

Tight interaction between NR and E-UTRA, support for network slicing.

AMF (1a-07) hosts functions such as NAS signaling, NAS signal security, AS security control, S-GW selection, authentication, mobility management, and location management.

UPF (1a-08) hosts functions such as packet routing and forwarding, transport level packet marking on the uplink and downlink, QoS management, and mobility anchoring for mobility.

Figure 1b- is a diagram showing the wireless protocol structure of the 5G system.

The user plane protocol stack is SDAP (1b-01 to 1b-02), PDCP (1b-03 to 1b-04), RLC (1b-05 to 1b-06), MAC (1b-07 to 1b-08), PHY It consists of (1b-09 to 1b-10). The control name protocol stack consists of NAS (1b-11 to 1b-12), RRC (1b-13 to 1b-14), PDCP, RLC, MAC, and PHY.

Each protocol sublayer performs functions related to the operations listed in Table 3.

Sublayer Functions NAS Authentication, mobility management, security control, etc. RRC System information, paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, detection and recovery from radio link failure, NAS message transmission, etc. SDAP Mapping between QoS flows and data radio bearers, QoS flow ID (QFI) marking of DL and UL packets. PDCP Data transmission, header compression and restoration, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and ordered delivery, etc. R.L.C. Transmission of upper layer PDU, error correction through ARQ, segmentation and re-division of RLC SDU, reassembly of SDU, re-establishment of RLC, etc. MAC Mapping between logical channels and transport channels, multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in the transport block (TB) delivered at the physical layer, information reporting schedule, priority processing between UEs, priority between single UE logical channels Ranking processing, etc. PHY Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

The terminal supports three RRC states. Table 4 lists the characteristics of each state.

RRC state Characteristic RRC_IDLE PLMN selection;Broadcast of system information;Cell re-selection mobility;
Paging for mobile terminated data is initiated by 5GC;
DRX for CN paging configured by NAS. RRC_INACTIVE PLMN selection;Broadcast of system information;Cell re-selection mobility;Paging is initiated by NG-RAN (RAN paging);
RAN-based notification area (RNA) is managed by NG- RAN;
DRX for RAN paging configured by NG-RAN;
5GC - NG-RAN connection (both C/U-planes) is established for UE;
The UE AS context is stored in NG-RAN and the UE;
NG-RAN knows the RNA which the UE belongs to. RRC_CONNECTED 5GC - NG-RAN connection (both C/U-planes) is established for UE;The UE AS context is stored in NG-RAN and the UE;NG-RAN knows the cell which the UE belongs to;Transfer of unicast data to /from the UE;
Network controlled mobility including measurements.

Figure 1c is a diagram showing RRC state transition.

Between RRC_CONNECTED (1c-11) and RRC_INACTIVE (1c-13), a state transition occurs through the exchange of a Resume message and a Release message containing a Suspend IE.

Between RRC_ CONNECTED (1c-11) and RRC_IDLE (1c-15), state transition occurs through RRC connection establishment and RRC connection release.

A state transition from RRC_INACTIVE (1c-13) to RRC_IDLE (1c-15) occurs through RRC disconnection.

The state transition from RRC_INACTIVE to RRC_CONNECTED involves not only signal exchange between the terminal and the base station, but also context transfer and data path change between base stations. If the terminal has enough data to transmit, these additional procedures can be fully justified, but if not, network efficiency may be reduced due to excessive overhead.

The present invention introduces a new resume procedure that allows data transmission and reception without transitioning to RRC_CONNECTED. Hereinafter, the resumption procedure aimed at transitioning the terminal in the RRC_INACTIVE state to the RRC_CONNECTED state is referred to as the first resumption procedure, and the procedure in which the terminal in the RRC_INACTIVE state transmits and receives data while maintaining the RRC_INACTIVE state is referred to as the second resumption procedure. Through the first resume procedure, the terminal can resume the suspended RRC connection, and through the second resume procedure, the terminal can resume data transmission and reception. The terminal may switch to the first resume procedure while performing the second resume procedure.

The second resumption process may proceed through a random access process or through a configured grant. These are called RA-SDT and CG-SDT, respectively.

RRC_INACTIVE UE generally does not transmit uplink signals such as SRS and does not receive downlink signals such as PDCCH.

FIG. 1D is a diagram illustrating an example of a bandwidth part.

Bandwidth adaptation (BA) allows the UE's receive and transmit bandwidth to be adjusted so that it is not necessarily as large as the cell's bandwidth. It can also be commanded to change in width (e.g., scale back during periods of low activity to save power) or move its location in the frequency domain (e.g. to increase scheduling flexibility). Subcarrier spacing may also be changed (e.g. to allow different services). A subset of a cell's total cell bandwidth is called BWP(s). BA is achieved by configuring multiple BWPs for the UE and telling the UE which of the configured BWPs is active. In Figure 1d, a scenario in which three different BWPs are configured is shown below.

1: BWP1 (1d-11 to 1d-19) with a width of 40 MHz and a subcarrier spacing of 15 kHz

2: BWP2 (1d-13 to 1d-17) with a width of 10MHz and a subcarrier spacing of 15kHz

3: BWP3 (1d-15) with subcarrier spacing of 20 MHz wide and 60 kHz

Figure 1e is a diagram illustrating an example of a search interval and control resource set.

Multiple SSs can be set in one BWP. The terminal monitors PDCCH candidates according to the SS settings of the currently activated BWP. One SS consists of an SS identifier, a CORESET identifier indicating the associated CORESET, the period and offset of the slot to be monitored, the slot unit duration, the symbol to be monitored within the slot, and the SS type. The information may be set explicitly and individually, or may be set as a predetermined index related to predetermined values.

One CORESET consists of a CORESET identifier, frequency domain resource information, symbol unit duration, and TCI status information.

Basically, CORESET can be understood as providing frequency domain information to be monitored by the terminal, and SS provides time domain information to be monitored by the terminal.

CORESET#0 and SS#0 can be set in IBWP. One CORESET and multiple SS can be additionally set in IBWP. When the terminal receives MIB (1e-01), it recognizes CORESET#0 (1e-02) and SS#0 (1e-03) for receiving SIB1 using predetermined information included in the MIB. The terminal receives SIB1 (1e-05) through CORESET#0 (1e-02) and SS#0 (1e-03). SIB1 contains information for setting CORESET#0 (1e-06) and SS#0 (1e-07) and information for setting another CORESET, such as CORESET#n (1e-11) and SS#m (1e-13). may be included. The terminal uses the CORESETs and SSs set in SIB1 to receive necessary information from the base station before the terminal enters the RRC connection state, such as receiving SIB2, receiving paging, and receiving a random access response message. CORESET#0 (1e-02) set in MIB and CORESET#0 (1e-06) set in SIB1 may be different from each other, and the former is called 1st CORESET#0 and the latter is called 1st CORESET#0. SS#0 (1e-03) set in MIB and SS#0 (1e-07) set in SIB1 may be different, and the former is called the first SS#0 and the latter is called the second SS#0. SS#0 and CORESET#0 set for the RedCap terminal are called 3rd SS#0 and 3rd CORESET#0. 1st SS#0, 2nd SS#0, and 3rd SS#0 may be the same or different from each other. The first CORESET#0, the second CORESET#0, and the third CORESET#0 may be the same or different from each other. SS#0 and CORESET#0 are each indicated with a 4-bit index. The 4-bit index indicates a setting predetermined in the standard. Except for SS#0 and CORESET#0, the detailed configuration of SS and CORSESET are set as individual information elements.

When an RRC connection is established, additional BWPs may be configured for the terminal.

A serving cell may consist of one or multiple BWPs.

The UE may be configured with multiple DL BWPs and multiple UL BWPs for one serving cell. If the serving cell operates in a paired spectrum (i.e., FDD band), the number of DL BWPs and the number of UL BWPs may be different. If the serving cell operates in an unpaired spectrum (i.e., TDD band), the number of DL BWPs and the number of UL BWPs are the same.

SIB1 includes DownlinkConfigCommonSIB, UplinkConfigCommonSIB, and tdd-UL-DL-ConfigurationCommon.

tdd-UL-DL-ConfigurationCommon is the cell-specific TDD UL/DL configuration. It consists of subfields such as referenceSubcarrierSpacing, pattern1, and pattern2.

referenceSubcarrierSpacing is a reference SCS used to determine time domain boundaries in UL-DL patterns.

pattern1 and pattern2 are TDD uplink and downlink patterns. It consists of subfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

dl-UL-TransmissionPeriodicity represents the period of the DL-UL pattern.

nrofDownlinkSlots indicates the number of consecutive full DL slots in each DL-UL pattern.

nrofDownlinkSymbols indicates the number of consecutive DL symbols from the start of the slot following the last full DL slot.

nrofUplinkSlots indicates the number of consecutive full UL slots in each DL-UL pattern.

nrofUplinkSymbols indicates the number of consecutive UL symbols at the end of the slot before the first full UL slot.

The slot between the last full DL slot and the first full UL slot is a flexible slot. A full UL slot is also called a static UL slot. In this disclosure, the UL slot is a static UL slot.

DownlinkConfigCommonSIB contains BWP-DownlinkCommon for the initial DL BWP. UplinkConfigCommonSIB contains BWP-UplinkCommon for the initial UL BWP. The BWP-id of initialDownlinkBWP is 0.

The RRCReconfiguration message includes multiple BWP-Downlinks, multiple BWP-Uplinks, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, and BWP-DownlinkDedicated for the initial DL BWP.

BWP-Downlink includes bwp-Id, BWP-DownlinkCommon, and BWP-DownlinkDedicated.

BWP-Uplink includes bwp-Id, BWP-UplinkCommon, and BWP-UplinkDedicated.

bwp-Id is an integer between 0 and 4. bwp-Id 0 is only used for BWP indicated in SIB1. bwp-Id1 ~ 4 can be used for the BWP indicated in the RRCReconfiguration message.

BWP-DownlinkCommon contains the following information: frequency domain location and bandwidth of this portion of bandwidth, subcarrier spacing to be used in this BWP, cell-specific parameters for the PDCCH of this BWP, and cell-specific parameters for the PDSCH of this BWP.

BWP-UplinkCommon contains the following information: frequency domain location and bandwidth of this portion of bandwidth, subcarrier spacing to be used in this BWP, cell-specific parameters for the PUCCH of this BWP, cell-specific parameters for the PUSCH of this BWP, cell Certain random access parameters.

BWP-DownlinkDedicated is used to configure dedicated (UE-specific) parameters of the downlink BWP. This includes cell-specific parameters for the PDCCH of this BWP, and cell-specific parameters for the PDSCH of this BWP.

BWP-UplinkDedicated is used to configure dedicated (UE-specific) parameters of the uplink BWP.

firstActiveDownlinkBWP-Id contains the ID of the DL BWP to be activated when performing RRC (re)configuration.

defaultDownlinkBWP-Id is the ID of the downlink bandwidth portion to be used when the BWP inactivity timer expires.

bwp-InactivityTimer is the duration in ms after the UE falls back to its default bandwidth portion.

Figure 2a is a diagram showing the operation of a terminal and a base station.

In step 2a-11, the UE transmits UECapabilityInformation to the GNB. GNB receives UECapabilityInformation from UE.

The GNB determines whether to configure IDC support for the UE based on the received capability information.

Prior to the above step, the terminal receives system information including SIB1 from the first cell.

In step 2a-16, GNB transmits the first RRCReconfiguration to the UE. The UE receives the first RRCReconfiguration from GNB.

The first RRCReconfiguration message includes CellGroupConfig (master cell group or secondary cell group configuration) and otherConfig. otherConfig may include 0 or 1 idc_AssistanceConfig_1 and 0 or 1 idc_AssistanceConfig_2 and 0 or 1 idc_AssistanceConfig_3.

In step 2a-21, the UE determines whether it is configured to provide IDC assistance information based on the received idc_AssistanceConfig.

If the received otherConfig includes idc_AssistanceConfig_1 and idc_AssistanceConfig_1 is set to setup, the UE considers itself set to provide IDC_Assistance_1.

If the received otherConfig includes idc_AssistanceConfig_1 and idc_AssistanceConfig_1 is set to release, the UE considers that it is not configured to provide IDC_Assistance_1.

If the received otherConfig includes idc_AssistanceConfig_2, the UE considers itself to be configured to provide IDC_Assistance_2.

If the received otherConfig does not include idc_AssistanceConfig_2, the UE considers itself not configured to provide IDC_Assistance_2.

If the received otherConfig includes idc_AssistanceConfig_3, the UE considers itself to be configured to provide IDC_Assistance_3.

If the received otherConfig does not include idc_AssistanceConfig_3, the UE considers itself not configured to provide IDC_Assistance_3.

If the received otherConfig includes idc_AssistanceConfig_1 and idc_AssistanceConfig_2, and idc_AssistanceConfig_1 is set to setup, the UE considers itself set to provide IDC_Assistance_1 and IDC_Assistance_2.

If the received otherConfig includes idc_AssistanceConfig_1 and idc_AssistanceConfig_3, and idc_AssistanceConfig_1 is set to setup, the UE considers that it is set to provide IDC_Assistance_1 and IDC_Assistance_3.

If the received otherConfig includes idc_AssistanceConfig_1, idc_AssistanceConfig_2, and idc_AssistanceConfig_3, and idc_AssistanceConfig_1 is set to setup, the UE considers that it is set to provide IDC_Assistance_1, IDC_Assistance_2, and IDC_Assistance_3.

To ensure compatibility with previous versions, idc_AssistanceConfig_3 is placed after idc_AssistanceConfig_1.

In step 2a-26, the UE transmits GNB UEAssistanceInformation to report the IDC problem. GNB receives UEAssistanceInformation from the UE.

A UE capable of providing IDC assistance information in RRC_CONNECTED and configured to do so may initiate the UEAssistanceInformation transmission procedure when A or B occurs. A is an IDC problem detection when the UE has not transmitted IDC assistance information since it was configured to provide IDC indication. B is a change in IDC problem information.

If the UE is configured to provide IDC_Assistance_1 and the UE has not transmitted UEAssistanceInformation with IDC_Assistance_1 since it was configured to provide IDC_Assistance_1, and the UE is experiencing IDC problems that it cannot resolve on its own on one or more frequencies included in candidateServingFreqListNR, the UE will provide IDC_Assistance_1 Starts transmission of UEAssistanceInformation to provide.

The UE is configured to provide IDC_Assistance_1 and the UE has not transmitted UEAssistanceInformation with IDC_Assistance_1 since the UE was configured to provide IDC_Assistance_1, and an IDC problem that the UE cannot resolve on its own in one or more supported UL CA combinations containing the carrier frequencies included in candidateServingFreqListNR If experiencing, the UE starts transmitting UEAssistanceInformation to provide IDC_Assistance_1.

If the UE is configured to provide IDC_Assistance_1 and the current IDC_Assistance_1 is different from that indicated in the last transmission of UEAssistanceInformation, the UE starts transmission of UEAssistanceInformation to provide IDC_Assistance_1.

The UE is configured to provide IDC_Assistance_2 and the UE has not transmitted UEAssistanceInformation with IDC_Assistance_2 since the UE was configured to provide IDC_Assistance_2, and there is an IDC that the UE cannot resolve on its own in one or more frequency resource portions (contiguous PRBs of the BWP) of one or more active serving cells. If experiencing a problem, the UE starts transmitting UEAssistanceInformation to provide IDC_Assistance_2.

If the UE is configured to provide IDC_Assistance_2 and the current IDC_Assistance_2 is different from that indicated in the last transmission of UEAssistanceInformation, the UE starts transmission of UEAssistanceInformation to provide IDC_Assistance_2.

Since the UE is configured to provide IDC_Assistance_2 and IDC_Assistance_3 and since the UE is configured to provide IDC_Assistance_2 and IDC_Assistance_3, the UEAssistanceInformation has not been transmitted together with IDC_Assistance_2 and IDC_Assistance_3 and has not been transmitted in one or more frequency resource portions (contiguous PRBs of the BWP) of one or more active serving cells. If the UE is experiencing an IDC problem that it cannot resolve on its own, the UE begins transmitting UEAssistanceInformation to provide IDC_Assistance_2 and IDC_Assistance_3.

If the UE is configured to provide IDC_Assistance_1 and IDC_Assistance_3 and the UE has not transmitted UEAssistanceInformation with IDC_Assistance_1 and IDC_Assistance_3 since it was configured to provide IDC_Assistance_1 and IDC_Assistance_3, and the UE is experiencing an IDC problem on one or more frequencies included in candidateServingFreqListNR that it cannot resolve on its own. If present, the UE starts transmitting UEAssistanceInformation to provide IDC_Assistance_1 and IDC_Assistance_3.

If the UE is configured to provide IDC_Assistance_3 and the current IDC_Assistance_3 is different from that indicated in the last transmission of UEAssistanceInformation, the UE starts transmission of UEAssistanceInformation to provide IDC_Assistance_3.

When transmission of UEAssistanceInformation begins to provide IDC_Assistance_1, the UE includes the following fields in UEAssistanceInformation: 0 or 1 affectedCarrierFreqList and 0 or 1 affectedCarrierFreqCombList.

When transmission of UEAssistanceInformation begins to provide IDC_Assistance_2, the UE includes the following fields in UEAssistanceInformation: 0 or 1 affectedResourceList and 0 or 1 affectedResourceComboList.

When transmission of starts to provide IDC_Assistance_3, the UE includes the following field in UEAssistanceInformation: idc_TimePatternList.

In step 2a-31, GNB transmits the second RRCReconfiguration to the UE. The UE receives the second RRCReconfiguraiton from GNB.

The GNB may decide to order a handover to alleviate IDC problems reported by the UE.

In RRCReconfiguration, if reconfigurationWithSync is included in the CellGroupConfig for the master cell group, the UE performs a random access procedure and transmits RRCReconfigurationComplete to the GNB.

In step 2A-36, ReconfigurationWithsync was included in CELLGROUPCONFIG for master cell groups of RRCONFIGURATION, and the UE was the last one second of IDC_ASSISTANCE_1 (or IDC_ASSISTANCE_2 or IDC_ASSISTANCE _3) The transmission of the UEASSISTANCEINFORMATION has been disclosed, and the UE is still IDC_ASSISTANCE_1 (or IDC_ASSISTANCE_2 or IDC_ASSISTANCE_3 ), the UE starts transmitting UEAssistanceInformation for IDC_Assistance_1 (or IDC_Assistance_2 or IDC_Assistance_3).

Although the first base station successfully received the first UEAssistanceInformation transmitted from the first cell, it may have failed to transmit it to the second base station, so the terminal transmits the second UEAssistanceInformation from the second cell after handover.

In step 2a-41, GNB transmits RRCRlease to the UE. UE receives RRCRlease from GNB.

If there is currently no data about the UE, but there is a possibility that there will be data about the UE in the near future, the GNB may decide to transition the UE to RRC_INACTIVE.

If the RRCRlease message includes SuspendConfig, the UE enters the RRC_INACTIVE state. If SuspendConfig includes SDT-config, the UE can start the SDT procedure during RRC_INACTIVE state when new data arrives at SRB1.

In the RRC_INACTIVE state, when the IDC problem disappears and transmission of IDC_Assistance_1 (and/or IDC_Assistance_2 and/or IDC_Assistance_3) begins, the UE starts the SDT procedure and transmits IDC_Assistance_1 (or IDC_Assistance_2 or IDC_Assistance_3) through SRB1. Reporting during RRC_INACTIVE only causes UE battery drain because IDC problems generally do not exist in RRC_INACTIVE state. To avoid this, the UE releases idc_AssistanceConfig_1 (and/or idc_AssistanceConfig_2 and/or idc_AssistanceConfig_3) when an RRCReelease message is received and the RRCRelease message contains SuspendConfig and SuspendConfig contains SDT-Cofnig.

In step 2a-46, if the RRCReelease message is received and the RRCRelease message contains SuspendConfig and SuspendConfig does not contain SDT-Cofnig, the UE sets idc_AssistanceConfig_1 (and/or idc_AssistanceConfig_2 and/or idc_AssistanceConfig_3) when the RRC connection resumption procedure begins. Release.

UECapabilityInformation includes the following IDC-related capability information: inDeviceCoexInd and inDeviceCoexInd_2 and inDeviceCoexInd_3.

inDeviceCoexInd indicates whether the UE supports the first IDC assistance information (i.e., whether the UE supports IDC_AssistanceConfig_1 reception and IDC_Assistance_1 transmission).

inDeviceCoexInd_2 indicates whether the UE supports second IDC assistance information (i.e., whether the UE supports reception of IDC_AssistanceConfig_2 and transmission of IDC_Assistance_2).

inDeviceCoexInd_3 indicates whether the UE supports third IDC assistance information (i.e., whether the UE supports IDC_AssistanceConfig_3 reception and IDC_Assistance_3 transmission).

CellGroupConfig is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group consists of one MAC entity, associated RLC entity and logical channels, and a primary cell (SpCell) and one or more secondary cells (SCells). CellGroupConfig contains zero or one spCellConfig and zero or one SCellConfig fields.

SpCellConfig is a parameter for the SpCell of this cell group (PCell in MCG or PSCell in SCG). SpCellConfig includes the fields servCellIndex, reconfigurationWithSync, and ServingCellConfig.

SCellConfig is a parameter for SCell. SpCellConfig includes the fields sCellIndex, ServingCellConfigCommon, and ServingCellConfig.

SCellIndex is a short ID to identify the SCell.

reconfigurationWithSync is a parameter of SpCell. If SpCellConfig in RRCReconfiguration's CellGroupConfig includes reconfigurationWithSync, handover begins. reconfigurationWithSync includes the following fields: ServingCellConfigCommon, newUE-Identity, t304, and rach-ConfigDedicated.

newUE-Identity indicates the C-RNTI to be used in the target cell after handover.

ServingCellConfigCommon includes 1 DownlinkConfigCommon and 2 UplinkConfigCommon. One UplinkConfigCommon is for normal uplink (NUL, Normal Uplink) and the other UplinkConfigCommon is for supplementary uplink (SUL, Supplementary Uplink). UplinkConfigCommon for NUL is located before UplinkConfigCommon for SUL.

DownlinkConfigCommon includes FrequencyInfoDL and BWP-DownlinkCommon. BWP-DownlinkCommon is for the initial DL BWP and includes PDCCH-ConfigCommon and PDSCH-ConfigCommon.

UplinkConfigCommon includes FrequencyInfoUL and TimeAlignmentTimer and BWP-UplinkCommon. BWP-UplinkCommon is for the initial UL BWP. BWP-UplinkCommon includes RACH-ConfigCommon, PUSCH-ConfigCommon, PUCCH-ConfigCommon, and a plurality of RACH-ConfigCommon_fc.

DownlinkConfigCommon is the common downlink configuration of the serving cell. It consists of subfields such as FrequencyInfoDL and BWP-DownlinkCommon.

FrequencyInfoDL is the basic parameter of the downlink carrier. It consists of subfields such as frequency band list and carrier bandwidth for each SCS.

BWP-DownlinkCommon is a configuration of the second downlink IBWP. It consists of subfields such as BWP, PDCCH-ConfigCommon, and PDSCH-ConfigCommon. The first IBWP has a frequency domain corresponding to the first CORESET#0 of the MIB and has subcarrier spacing indicated in the MIB. The first IBWP is an IBWP indicated in MIB and receives 1, and the second IBWP is an IBWP indicated in 1 and receives 2, paging, random access response message, etc.

BWP is an IE that configures the general parameters of BWP. It consists of subfields such as locationAndBandwidth, which indicates the bandwidth and location of the BWP, and subcarrierSpacing, which indicates the SCS of the BWP.

ServingCellConfig contains BWP-DownlinkDedicated (for the second initial downlink BWP) and zero or one BWP-Downlink IE (for dedicated downlink BWP) and UplinkConfig IE (for normal uplink) and UplinkConfig IE (for secondary uplink). Includes. UplinkConfig IE includes BWP-UplinkDedicated (for the second initial uplink BWP) and zero or one or more BWP-Uplink IEs (for dedicated uplink BWPs).

BWP-Downlink consists of BWP-Id IE, BWP-DownlinkCommon IE, and BWP-DownlinkDedicated IE.

BWP-Uplink consists of BWP-Id IE, BWP-UplinkCommon IE, and BWP-UplinkDedicated IE.

BWP-DownlinkDedicated consists of PDCCH-Config and PDSCH-Config. PDCCH-Config is used to configure UE-specific PDCCH parameters such as control resource set (CORESET), search space and additional parameters for acquiring PDCCH. PDSCH-Config is used to configure UE-specific PDSCH parameters.

BWP-UplinkDedicated consists of PUCCH-Config and PUSCH-Config. PUCCH-Config is used to configure UE-specific PUCCH parameters. PUSCH-Config is used to configure UE-specific PUSCH parameters.

The idc_AssistanceConfig_1 field is set to setup or release. If the idc_AssistanceConfig_1 field is set to setup, this field contains the IDC_AssistanceConfig_1 IE. IDC_AssistanceConfig_1 IE sets the UE that detects an IDC problem to report assistance information that notifies the gNB. IDC_AssistanceConfig_1 IE is configured with CandidateServingFreqListNR. CandidateServingFreqListNR indicates the center frequency at which the UE is requested to report IDC problems for each candidate NR serving cell. CandidateServingFreqListNR contains one or more ARFCN-ValueNR_1. If the idc_AssistanceConfig_1 field is set to set, the UE determines the contents of IDC_Assistance_1 based at least in part on the frequency indicated in CandidateServingFreqListNR.

The idc_AssistanceConfig_2 field represents a single value of TRUE. If idc_AssistanceConfig_2 is included, the UE determines the contents of IDC_Assistance_1 based at least in part on the currently active serving cell.

The idc_AssistanceConfig_3 field represents a single value of TRUE. If idc_AssistanceConfig_3 is included, the UE determines the contents of IDC_Assistance_3 based at least in part on the specific serving cell. More specifically, consider PCell's TDD-UL-DL-ConfigCommon.

IDC_Assistance_1 is used to report carriers where IDC problems have been detected.

IDC_Assistance_2 is used to report the PRB (or BWP) where an IDC issue has been detected.

IDC_Assistance_3 is used to report the time pattern required to resolve detected IDC issues.

IDC_Assistance_1 contains 0 or 1 AffectedCarrierFreqList and 0 or 1 AffectedCarrierFreqCombList.

AffectedCarrierFreqList represents a list of NR carrier frequencies affected by the IDC problem. AffectedCarrierFreqList consists of one or more AffectedCarrierFreq. AffectedCarrierFreq consists of one or more ARFCN_ValueNR_1 and interferenceDirection. InterferenceDirection indicates the direction of IDC interference. Value_nr indicates that only NR is the victim of IDC interference, Value_other indicates that only the other radio is the victim of IDC interference, and Value_both indicates that both NR and the other radio are the victim of IDC interference.

affectedCarrierFreqCombList represents a list of NR carrier frequency combinations affected by IDC problems due to harmonics and Inter-Modulation Distortion of NR when configured as UL CA. affectedCarrierFreqCombList consists of one or more AffectedCarrierFreqComb. AffectedCarrierFreqComb consists of multiple ARFCN_ValueNR_2 and vitimSystemType. vitimSystemType represents a list of vitimSystemTypes that will cause IDC interference in NR when configured with UL CA. Value_gps, Value_glonass, Value_bds, Value_galileo and Value_navIC represent the type of GNSS. Value_wlan represents WLAN and Value_bluetooth represents Bluetooth.

IDC_Assistance_2 includes: affectedResourceList and affectedResourceComboList.

affectedResourceList represents a list of frequency resource parts affected by the IDC problem. affectedResourceList contains one or more affectedResources. affectedResource consists of ARFCN_ValueNR2, locationAndBandwidth, interferenceDirection and 0 or 1 vitimSystemType fields. affectedResource represents a portion of a frequency domain resource.

locationAndBandwidth represents the frequency domain location and bandwidth of the frequency portion affected by the IDC problem. locationAndBandwidth indicates the starting PRB and number of PRBs. The value of the field is interpreted as a resource indicator value (RIV) with the size of the BWP set to 275. RIV represents adjacent resource blocks (i.e., frequency resource portions) within the BWP. RIV corresponds to the offset of the frequency resource portion from the lowest resource block and the length of the frequency resource portion.

The location of PRB0 in the frequency domain is determined based on ARFCN_ValueNR2, and the frequency domain resource portion indicated by the start PRB and the number of PRBs is determined based on the frequency domain location of PRB0.

vitimSystemType is included in IDC_Assistance_2 when interferenceDirection is set to Value_other or Value_both.

Alternatively, the affectedResource consists of the fields servCellIndex, DL_UL_SUL_indicator, bwp-Id, 0 or 1 locationAndBandwidth, interferenceDirection, and 0 or 1 vitimSystemType.

servCellIndex is used to uniquely identify the serving cell. Value_0 applies to PCell. The SCellIndex previously assigned to the SCell is applied to the SCell. servCellIndex indicates the serving cell to which the frequency resource portion with IDC problem belongs.

DL_UL_SUL_indicator indicates downlink, uplink, or additional uplink.

bwp-Id indicates the BWP to which the frequency resource portion with the IDC problem belongs.

Which PRBs in which BWP in which serving cell are experiencing IDC problems is determined based at least in part on servCellIndex and DL_UL_SUL_indicator and bwp-Id and locationAndBandwidth.

If locationAndBandwidth does not exist in the affectedResource, the entire BWP (all PRBs in the BWP) pointed to by bwp-id and DL_UL_SUL_indicator is experiencing an IDC problem.

affectedResourceComboList represents a list of combinations of frequency resource parts affected by IDC problems due to Inter-Modulation Distortion and harmonics of NR when configured with UL CA. affectedResourceComboList consists of one or more affectedResourceCombos. affectedResourceCombo consists of multiple affectedResource2 and vitimSystemType.

affectedResource2 consists of ARFCN_ValueNR2 and locationAndBandwidth. Alternatively, affectedResource2 consists of servCellIndex, UL_SUL_indicator, bwp-Id and locationAndBandwidth.

If UL_SUL_indicator is not included in registeredResource2, the predefined uplink for affectedResource2 is applied. The predefined uplink is normal uplink or secondary uplink.

IDC_Assistance_3 includes idc_TimePatternList. idc_TimePatternList is a list of one or more slot patterns that indicate which slots NR has been requested to refrain from using. A value of 0 indicates that NR has been requested to refrain from using that slot. idc_TimePatternList contains one or more idc_TimePattern. The idc_TimePattern field includes FR_indicator, reference_cell, and TimePatternBitmap fields.

FR_indicator is the frequency range associated with TimePatternBitmap. FR_indicator indicates FR1 or FR2-1 or FR2-2. FR1 is the frequency range below 6 GHz. FR2-1 is a frequency range of 24GHz to 52.6GHz. FR2-2 is the frequency range above 52.6GHz.

reference_cell represents a serving cell that provides a time reference for TimePatternBitmap. reference_cell represents PCell or PSCell. Or reference_cell represents servCellIndex.

TimePatternBitmap is either Bitmap1 (10 bits) or Bitmap2 (20 bits) or Bitmap3 (40 bits) or Bitmap4 (80 bits) or Bitmap5 (160 bits). The size of each bitmap is determined by the SCS of the serving cell and the periodicity of the serving cell's TDD-UL-DL-ConfigCommon. The serving cell is indicated as reference_cell. Each bit of the bitmap corresponds to a slot of the serving cell. Therefore, the size of the Bitmap is equal to the number of slots within one UL/DL configuration cycle. For example, if the SCS of the serving cell is 160KHz and the period of the serving cell is 10ms, one UL/DL configuration consists of 160 slots and the size of the corresponding Bitmap is 160 bits.

The UE decides based on the IDC problem which slots of which serving cell (and which FR) to refrain from using to solve the IDC problem. The UE creates the corresponding Bitmap and transmits the Bitmap in IDC_Assistance_3.

ARFCN_ValueNR is used to indicate the ARFCN applicable to the downlink, uplink, or two-way (TDD) NR global frequency raster.

ARFCN_ValueNR_1 is associated with the ARFCN_ValueNR of the serving frequency (intra-freqUEncy) or non-serving/neighboring frequency (inter-freqUEncy). ARFCN_ValueNR_1 indicates the frequency of the SS (Synchronization Signal) related to the measurement target (if the IDC is in the surrounding frequency) or the frequency of the SSB to be used in the serving cell (if the IDC is in the serving frequency).

ARFCN_ValueNR_2 is ARFCN_ValueNR indicating Point A of the uplink carrier or downlink carrier. ARFCN_ValueNR_2 is the absolute frequency of the reference resource block (Common RB 0). The lowest subcarrier of Common RB0 is known as Point A. ARFCN_ValueNR_2 represents Point A of the carrier wave.

ARFCN_ValueNR_3 is ARFCN_ValueNR related to BWP. ARFCN_ValueNR_3 is the absolute frequency of the lowest subcarrier of the lowest resource block of BWP.

SuspendConfig can include the fields below.

1. First terminal identifier: Identifier of the terminal that can be included in the ResumeRequest when the state transitions to RRC_CONNECTED. It has a length of 40 bits.

2. Second terminal identifier: A terminal identifier that can be included in the ResuemeRequest when the state transitions to RRC_CONNECTED. It has a length of 24 bits.

3. ran-PagingCycle: Paging cycle to apply in RRC_INACTIVE state

4. ran-NotificationAreaInfo: Configuration information of ran-NotificationArea consisting of a list of cells, etc. The terminal starts the restart procedure when ran_NotificationArea is changed.

5. t380: Timer associated with periodic resume procedure

6. NCC (nextHopChaningCount): Counter used to derive a new security key after performing the resume procedure.

7. sdt-Config: Configuration information for SDT.

SDT (Small Data Transmission) is a procedure that allows data and/or signaling transmission while maintaining the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state).

The sdt-Config field contains SDT-Config IE. SDT-Config IE includes the fields sdt-DRB-List, sdt-SRB2-Indication, sdt-MAC-PHY-CG-Config, and sdt-DRB-ContinueEHC.

sdt-DRB-ContinueEHC contains IE representing either cell or rna. This field indicates whether the PDCP entity for the radio bearer configured for SDT continues or resets the EHC header compression protocol during PDCP reset during the SDT procedure. The Value cell indicates that ROHC header compression continues when SDT is resumed in the same cell as the PCell upon receipt of the RRCRlease message. The rna value indicates that EHC header compression continues when resuming for SDT in a cell belonging to the same RNA as the PCell upon receipt of the RRCRlease message. If the field is missing, the PDCP entity for the radio bearer configured for SDT will reset the EHC header compression protocol during PDCP reset during the SDT procedure.

sdt-DRB-List contains 0 or more DRB-Identities. This field indicates the ID of the DRB configured for SDT. If the size of the sequence is 0, the UE assumes that DRB is not configured for SDT.

sdt-SRB2-Indication contains an IE indicating that it is allowed. This field indicates whether SRB2 is configured for SDT. If the field is missing, SRB2 is not configured for SDT.

The operations of the terminal and base station are described below.

The terminal transmits UECapabilityInformation to the base station.

The base station receives UECapabilityInformation from the terminal.

UECapabilityInformation includes UE-NR-Capability.

UE-NR-Capability includes 0 or 1 inDeviceCoexInd and 0 or 1 inDeviceCoexInd_2 and 0 or 1 inDeviceCoexInd_3.

inDeviceCoexInd indicates whether the terminal supports the first IDC support information.

The first IDC support information consists of information about one or more carriers related to the IDC issue.

inDeviceCoexInd_2 indicates whether the terminal supports second IDC support information.

The second IDC support information consists of information about one or more frequency resources related to the IDC problem. The frequency resource consists of consecutive PRBs within the BWP.

inDeviceCoexInd_3 indicates whether the terminal supports third IDC support information.

The third IDC support information consists of information about one or more time patterns. A time pattern consists of one bitmap. The length of the bitmap is related to the periodicity of the TDD-UL-DL-ConfigCommon of the first serving cell and the SCS of the first BWP of the first serving cell. The first serving cell is PCell. The first BWP is the currently active BWP or the initial BWP.

inDeviceCoexInd_1 must be included in UE-NR-Capability for inDeviceCoexInd_2 to be included in UE-NR-Capability.

inDeviceCoexInd_1 must be included in UE-NR-Capability for inDeviceCoexInd_3 to be included in UE-NR-Capability.

The base station transmits the first RRCReconfiguration to the terminal.

The terminal receives the first RRCReconfiguration from the base station.

The first RRCReconfiguration includes 0 or 1 idc_AssistanceConfig_1 and 0 or 1 idc_AssistanceConfig_2 and 0 or 1 idc_AssistanceConfig_3.

The first RRCReconfiguration may include idc_AssistanceConfig_1 or idc_AssistanceConfig_2 or idc_AssistanceConfig_1 and idc_AssistanceConfig_3 or idc_AssistanceConfig_2 and idc_AssistanceConfig_3.

If idc_AssistanceConfig_1 is not included in the first RRCReconfiguration message, idc_AssistanceConfig_2 is included in the first RRCReconfiguration.

idc_AssistanceConfig_1 consists of one or more ARFCN_ValueNR_1.

idc_AssistanceConfig_2 consists of a first IE representing a single value. If idc_AssistanceConfig_2 is included in RRCReconfiguration and set to the first value, the terminal considers itself to be configured to provide second IDC assistance information.

idc_AssistanceConfig_3 consists of a second IE representing a single value. If idc_AssistanceConfig_3 is included in RRCReconfiguration and set to the second value, the terminal considers itself to be configured to provide third IDC assistance information.

ARFCN_ValueNR_1 (absoluteFrequencySSB) represents the center frequency of the SS block. ARFCN_ValueNR_1 represents the center frequency of the carrier wave.

ARFCN_ValueNR_2(absoluteFrequencyPointA) represents the absolute frequency of the reference resource block. ARFCN_ValueNR_2 indicates the lowest subcarrier of the reference resource block. ARFCN_ValueNR2 indicates the lowest frequency of the reference resource block.

The terminal transmits UEAssistanceInformation to the base station.

The base station receives UEAssistanceInformation from the terminal.

UEAssistanceInformation includes 0 or 1 first IDC support information, 0 or 1 second IDC support information, and 0 or 1 third IDC support information. The first IDC support information and the second IDC support information are not included in UEAssistanceInformation at the same time.

The first IDC support information consists of information about one or more carriers related to the IDC issue.

The second IDC support information consists of information about one or more frequency resources related to the IDC problem. Frequency resources consist of consecutive PRBs within the BWP.

The third IDC support information consists of one or more time patterns. The time pattern consists of one bitmap. The length of the bitmap is related to the periodicity of the TDD-UL-DL-ConfigCommon of the first serving cell and the SCS of the first BWP of the first serving cell.

The first serving cell is PCell. The first BWP is the currently active BWP or the initial BWP.

The terminal transmits UEAssistanceInformation to the base station.

The base station receives UEAssistanceInformation from the terminal.

UEAssistanceInformation includes second IDC assistance information.

The second IDC support information includes affected_Resource_List.

affected_Resource_List consists of one or more affected_Resources.

affected_Resource consists of at least ARFCN_ValueNR2 and locationAndBandwidth.

locationAndBandwidth represents one or more contiguous PRBs affected by the IDC issue.

The terminal transmits UEAssistanceInformation to the base station.

The base station receives UEAssistanceInformation from the terminal.

UEAssistanceInformation includes second IDC assistance information.

The second IDC support information includes affected_Resource_List.

affected_Resource_List consists of one or more affected_Resources.

affected_Resource consists of at least servCellIndex and DL_UL_SUL_indicator and bwp -Id and locationAndBandwidth.

locationAndBandwidth represents one or more contiguous PRBs affected by the IDC issue.

The one or more consecutive PRBs are PRBs of the first BWP of the first link of the first cell. The first BWP is denoted by bwp -Id. The first link is indicated by DL_UL_SUL_indicator and is one of downlink, general uplink, and auxiliary uplink. The first cell is indicated by servCellIndex.

The terminal transmits UEAssistanceInformation to the base station.

The base station receives UEAssistanceInformation from the terminal.

UEAssistanceInformation includes second IDC assistance information.

The second IDC support information includes affected_Resource_Combo_List.

affected_Resource_Combo_List consists of one or more affected_Resource_Combos.

The affected_Resource_Combo consists of two or more affected_Resource2.

affected_Resource2 consists of at least ARFCN_ValueNR2 and locationAndBandwidth.

The locationAndBandwidth of the affected_Resource2 indicates one or more contiguous PRBs affected by the IDC problem when aggregated (or used together) with one or more contiguous PRBs represented by another affected_Resource2 in the same affected_Resource_Combo.

The terminal transmits UEAssistanceInformation to the base station.

The base station receives UEAssistanceInformation from the terminal.

UEAssistanceInformation includes second IDC assistance information.

The second IDC support information includes affected_Resource_Combo_List.

affected_Resource_Combo_List consists of one or more affected_Resource_Combos.

affected_Resource_Combo consists of two or more affected_Resource2.

affected_Resource2 consists of at least servCellIndex, UL_SUL_indicator, bwp -Id, and locationAndBandwidth.

The locationAndBandwidth of the affected_Resource2 indicates one or more contiguous PRBs affected by the IDC problem when aggregated (or used together) with one or more contiguous PRBs represented by another affected_Resource2 in the same affected_Resource_Combo.

The one or more consecutive PRBs are PRBs of the first BWP of the first uplink of the first cell. The first BWP is denoted by bwp -Id. The first uplink is determined by the presence of UL_SUL_indicator. If UL_SUL_indicator is present, the first link is normal uplink, and if not, it is secondary uplink. The first cell is indicated by servCellIndex.

The base station transmits the second RRCReconfiguration to the terminal in the first cell.

If the second RRCReconfiguration includes reconfigurationWithSync and the transmission of the UEAssistanceInformation for the second IDC assistance information started in the first cell in the last second and the UE is still configured to provide the second IDC assistance information, the base station Receives UEAssistanceInformation including second IDC support information from the terminal.

The terminal receives the second RRCReconfiguration from the base station in the first cell.

If the second RRCReconfiguration includes reconfigurationWithSync and transmission of the UEAssistanceInformation for the second IDC assistance information started in the first cell in the last 1 second and the UE is still configured to provide the second IDC assistance information, the UE is configured to provide the second IDC assistance information transmits UEAssistanceInformation including second IDC support information to the base station.

The base station transmits RRCRlease to the terminal in the second cell.

If the RRCRelease includes suspendConfig and suspendConfig includes SDT-Config, the terminal releases idc_AssistanceConfig_1 (and/or idc_AssistanceConfig_2 and/or idc_AssistanceConfig_3) in the second cell before entering RRC_INACTIVE.

If the RRCRelease includes suspendConfig and suspendConfig does not include SDT-Config, the terminal releases idc_AssistanceConfig_1 (and/or idc_AssistanceConfig_2 and/or idc_AssistanceConfig_3) in the third cell after entering RRC_INACTIVE and before starting transmission of RRCResumeRequest. .

Figure 3a is a diagram showing the operation of the terminal.

In step 3a-05, the terminal transmits UECapabilityInformation to the base station. UECapabilityInformation includes UE-NR-Capability. UE-NR-Capability includes inDeviceCoexInd.

In step 3a-10, the UE receives the first RRCReconfiguration from the base station in the first cell. The first RRCReconfiguration includes 0 or 1 idc_AssistanceConfig_1 and 0 or 1 idc_AssistanceConfig_2 and 0 or 1 idc_AssistanceConfig_3.

In step 3a-15, the terminal transmits UEAssistanceInformation to the base station. UEAssistanceInformation includes all or part of the first IDC support information, second IDC support information, and third IDC support information.

In step 3a-20, the UE receives the second RRCReconfiguration from the base station.

In step 3a-25, if the second RRCReconfiguration includes reconfigurationWithSync and transmission of UEAssistanceInformation for second IDC assistance information has started in the first cell in the last second and the UE is still configured to provide second IDC assistance information , the terminal transmits UEAssistanceInformation including second IDC support information from the second cell to the base station.

Figure 4a is a block diagram showing the internal structure of a terminal to which the present invention is applied.

Referring to the drawing, the terminal includes a control unit (4a-01), a storage unit (4a-02), a transceiver (4a-03), a main processor (4a-04), and an input/output unit (4a-05).

The control unit 4a-01 controls overall operations of the UE related to mobile communication. For example, the control unit 4a-01 transmits and receives signals through the transceiver 4a-03. Additionally, the control unit 4a-01 writes and reads data into the storage unit 4a-02. For this purpose, the control unit 4a-01 may include at least one processor. For example, the control unit 4a-01 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (4a-01) controls the storage unit and the transceiver to perform the terminal operations of FIGS. 2A and 3A. The transceiver is also called a transmitter and receiver.

The storage unit 4a-02 stores data such as basic programs, application programs, and setting information for operation of the terminal. The storage unit 4a-02 provides stored data upon request from the control unit 4a-01.

The transver (4a-03) includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions to transmit and receive signals through wireless channels, such as converting the signal band and amplifying it. That is, the RF processing unit up-converts the baseband signal provided from the baseband processing unit into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. The RF processing unit 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. The RF processing unit can perform MIMO and can receive multiple layers when performing MIMO operation. The baseband processing unit performs a conversion function between baseband signals and bit strings according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit. The transceiver is also called a transmitter and receiver.

The main processor (4a-04) controls overall operations excluding mobile communication-related operations. The main processor (4a-04) processes the user's input transmitted from the input/output unit (4a-05), stores the necessary data in the storage unit (4a-02), and controls the control unit (4a-01) to enable mobile communication. It performs related operations and transmits output information to the input/output unit (4a-05).

The input/output unit 4a-05 is composed of a device that receives user input, such as a microphone or screen, and a device that provides information to the user, and inputs and outputs user data under the control of the main processor.

Figure 4b is a block diagram showing the configuration of a base station according to the present invention.

As shown in the figure, the base station includes a control unit (4b-01), a storage unit (4b-02), a transceiver (4b-03), and a backhaul interface unit (4b-04).

The control unit 4b-01 controls overall operations of the base station. For example, the control unit 4b-01 transmits and receives signals through the transceiver 4b-03 or through the backhaul interface unit 4b-04. Additionally, the control unit 4b-01 writes and reads data into the storage unit 4b-02. For this purpose, the control unit 4b-01 may include at least one processor. The control unit 4b-01 is a transceiver so that the base station operation shown in FIG. 2A is performed. storage unit. Controls the backhaul interface unit.

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

The transceiver (4b-03) includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit upconverts the baseband signal provided from the baseband processing unit into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmission filter, reception filter, amplifier, mixer, oscillator, DAC, ADC, etc. The RF processing unit can perform downlink MIMO operation by transmitting one or more layers. The baseband processing unit performs a conversion function between baseband signals and bit strings according to physical layer standards. For example, when transmitting data, the baseband processing unit generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit. The transceiver is also called a transmitter and receiver.

The backhaul interface unit 4b-04 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 4b-04 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 to heat.

Claims (1)

In a wireless communication system, in a terminal method,
Transmitting UECapabilityInformation to a base station, the UECapabilityInformation includes UE-NR-Capability, and the UE-NR-Capability includes inDeviceCoexInd,
Receiving RRCReconfiguration from a base station, the RRCReconfiguration includes idc_AssistanceConfig,
Transmitting UEAssistanceInformation to a base station, wherein the UEAssistanceInformation includes all or part of first IDC support information, second IDC support information, and third IDC support information,
Receiving a second RRCReconfiguration from the base station and
If the second RRCReconfiguration includes reconfigurationWithSync and the transmission of the UEAssistanceInformation for the second IDC assistance information has started in the first cell in the last second and the UE is still configured to provide the second IDC assistance information, then the base station in the second cell A method comprising transmitting UEAssistanceInformation containing second IDC support information.