WO2021220438A1 - Terminal - Google Patents

Abstract

A terminal receives downlink control information from a network, and uses the downlink control information to schedule a plurality of component carriers. The terminal determines the active/inactive state of a secondary cell, and applies the active/inactive state commonly to the plurality of component carriers.

Description

Terminal

The present disclosure relates to a terminal that executes wireless communication, particularly a terminal that executes wireless communication using a plurality of component carriers.

The 3rd Generation Partnership Project (3GPP) specifies the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and next-generation specifications called Beyond 5G, 5G Evolution or 6G. We are also proceeding with the conversion.

Release 15 and Release 16 (NR) of 3GPP specify the operation of multiple frequency ranges, specifically, bands including FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). ..

In addition, studies are underway on NR that supports up to 71 GHz beyond 52.6 GHz (Non-Patent Document 1). In addition, Beyond 5G, 5G Evolution or 6G (Release-18 or later) aims to support frequency bands above 71GHz.

If the usable frequency band is expanded in this way, it is expected that the possibility that more component carriers (CC) will be set will increase.

Carrier Aggregation (CA) stipulates the number of CCs that can be set. For example, in 3GPP Release 15 and Release 16, the maximum number of CCs that can be set for a terminal (User Equipment, UE) is 16 for downlink (DL) and uplink (UL), respectively.

On the other hand, the physical layer (PHY) and medium access control layer (MAC) settings are executed for each CC. For example, since one downlink control information (DCI: Downlink Control Information) can be scheduled for only one CC, a large number of DCIs are required to schedule a large number of CCs.

Further, in NR, it is possible to activate and deactivate the secondary cell (SCell), but it is stipulated that when the SCell is deactivated, the BWP (Bandwidth part) is also deactivated (Non-Patent Document 2). ).

Considering the above situation, it is conceivable to control multiple CCs using a single DCI.

However, in such a case, when the SCell is deactivated, it may occur that only a part of the CCs among the plurality of CCs is deactivated.

As mentioned above, deactivating an SCell also deactivates the BWP, so when the SCell is reactivated, there is a problem that it is unclear which BWP should be applied to the CC to be reactivated. be. Moreover, such a problem is not limited to BWP, but is the same for TCI (Transmission Configuration Indication).

Therefore, the following disclosure was made in view of such a situation, and aims to provide a terminal capable of adapting to activation and deactivation of SCell even when controlling a plurality of CCs using DCI. do.

One aspect of the present disclosure is a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information from the network, and a control unit (control unit) that schedules a plurality of component carriers using the downlink control information. The control unit is a terminal (UE200) that determines the active / inactive state of the secondary cell and applies the active / inactive state to the plurality of component carriers in common.

One aspect of the present disclosure includes a receiving unit that receives downlink control information from a network, and a control unit (control unit 270) that schedules a plurality of component carriers using the downlink control information. , A terminal that applies the setting state of the reference component carrier included in the plurality of component carriers to other reactivated component carriers.

One aspect of the present disclosure includes a receiving unit that receives downlink control information from a network, and a control unit (control unit 270) that schedules a plurality of component carriers using the downlink control information. , A terminal that holds the set state of the component carrier associated with the deactivated secondary cell and applies the held set state to the reactivated component carrier.

One aspect of the present disclosure is a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information from the network, and a control unit (control unit) that schedules a plurality of component carriers using the downlink control information. The control unit is a terminal that determines the dormant / non-sleeping state of the secondary cell and applies the dormant / non-sleeping state to the plurality of component carriers in common.

One aspect of the present disclosure is a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information from the network, and a control unit (control unit) that schedules a plurality of component carriers using the downlink control information. The control unit is a terminal that applies the setting state of the reference component carrier included in the plurality of component carriers to another component carrier that returns from the dormant state to the non-sleeping state.

One aspect of the present disclosure is a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information from the network, and a control unit (control unit) that schedules a plurality of component carriers using the downlink control information. 270), the control unit holds the set state of the component carrier related to the secondary cell that transitions to the dormant state, and holds the component carrier that returns from the dormant state to the non-sleep state. It is a terminal to which the setting state is applied.

FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10. FIG. 2 is a diagram showing a frequency range used in the wireless communication system 10. FIG. 3 is a diagram showing a configuration example of a wireless frame, a subframe, and a slot used in the wireless communication system 10. FIG. 4 is a functional block configuration diagram of the UE 200. FIG. 5 is an explanatory diagram of a problem in the case of adapting to SCell activation / deactivation. FIG. 6 is an explanatory diagram of a problem in the case of adapting to SCell activation / deactivation. FIG. 7 is a diagram showing an example of the BWP setting state according to the operation example 1-1. FIG. 8 is a diagram showing a configuration example (part) of a new MAC CE according to operation example 1-1. FIG. 9 is a diagram showing an example of the BWP setting state according to the operation example 1-2. FIG. 10 is a diagram showing an example of the BWP setting state according to the operation example 1-3. FIG. 11 is a diagram showing an example of problem occurrence (No. 1) in the case of adapting to SCell dormancy indication. FIG. 12 is a diagram showing an example of problem occurrence (No. 2) in the case of adapting to SCell dormancy indication. FIG. 13 is a diagram showing an example (No. 1) of the BWP setting state according to the operation example 2-1. FIG. 14 is a diagram showing an example (No. 2) of the BWP setting state according to the operation example 2-1. FIG. 15 is a diagram showing an example of the BWP setting state according to the operation example 2-2. FIG. 16 is a diagram showing an example of the hardware configuration of the UE 200.

Hereinafter, embodiments will be described based on the drawings. The same functions and configurations are designated by the same or similar reference numerals, and the description thereof will be omitted as appropriate.

(1) Overall Schematic Configuration of Wireless Communication System FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system according to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN20, and a terminal 200 (hereinafter, UE200)).

Note that the wireless communication system 10 may be a wireless communication system according to a method called Beyond 5G, 5G Evolution or 6G.

NG-RAN20 includes a radio base station 100A (hereinafter, gNB100A) and a radio base station 100B (hereinafter, gNB100B). The specific configuration of the wireless communication system 10 including the number of gNBs and UEs is not limited to the example shown in FIG.

The NG-RAN20 actually includes multiple NG-RANNodes, specifically gNB (or ng-eNB), and is connected to a core network (5GC, not shown) according to 5G. In addition, NG-RAN20 and 5GC may be simply expressed as "network".

GNB100A and gNB100B are radio base stations that comply with 5G, and execute wireless communication according to UE200 and 5G. The gNB100A, gNB100B and UE200 are Massive MIMO (Multiple-Input Multiple-Output) and multiple component carriers (CC) that generate more directional beam BM by controlling radio signals transmitted from multiple antenna elements. ) Can be bundled and used for carrier aggregation (CA), and dual connectivity (DC) for simultaneous communication between the UE and each of the two NG-RAN Nodes.

In addition, the wireless communication system 10 supports a plurality of frequency ranges (FR). FIG. 2 shows the frequency range used in the wireless communication system 10.

As shown in FIG. 2, the wireless communication system 10 corresponds to FR1 and FR2. The frequency bands of each FR are as follows.

・ FR1: 410 MHz to 7.125 GHz
・ FR2: 24.25 GHz to 52.6 GHz
In FR1, Sub-Carrier Spacing (SCS) of 15, 30 or 60kHz is used, and a bandwidth (BW) of 5 to 100MHz may be used. FR2 has a higher frequency than FR1, SCS of 60 or 120kHz (240kHz may be included) is used, and a bandwidth (BW) of 50 to 400MHz may be used.

SCS may be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

Furthermore, the wireless communication system 10 also supports a higher frequency band than the FR2 frequency band. Specifically, the wireless communication system 10 corresponds to a frequency band exceeding 52.6 GHz and up to 71 GHz. Such a high frequency band may be referred to as "FR2x" for convenience.

To solve this problem, when using a band exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread (DFT-) with a larger Sub-Carrier Spacing (SCS) S-OFDM) may be applied.

FIG. 3 shows a configuration example of a wireless frame, a subframe, and a slot used in the wireless communication system 10.

As shown in FIG. 3, one slot is composed of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in FIG. For example, 480kHz, 960kHz and the like may be used.

Further, the number of symbols constituting one slot does not necessarily have to be 14 symbols (for example, 28, 56 symbols). In addition, the number of slots per subframe may vary from SCS to SCS.

The time direction (t) shown in FIG. 3 may be referred to as a time domain, a symbol period, a symbol time, or the like. Further, the frequency direction may be referred to as a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), or the like.

BWP may be interpreted as a continuous set of PRBs (Physical Resource Blocks) selected from a continuous subset of common resource blocks for a given numerology on a given carrier.

The BWP information (bandwidth, frequency position, subcarrier spacing (SCS)) that the UE200 should use for wireless communication can be set in the UE200 using signaling from the upper layer (eg, the radio resource control layer (RRC)). A different BWP may be set for each UE200 (terminal). The BWP may be changed by higher layer signaling or lower layer (specifically, physical layer (L1) signaling (such as DCI described later)). ..

The wireless communication system 10 may support a large number of CCs for CA in order to achieve higher throughput. For example, if the maximum bandwidth of CCs is 400MHz, FR2x, specifically, up to 32 CCs can be placed in the frequency band of 57GHz to 71GHz. The maximum number of CCs to be set may exceed 32 or may be less than that.

Furthermore, the wireless communication system 10 may support dynamic BWP switching (switching) of a plurality of CCs via one downlink control information (DCI). That is, in the wireless communication system 10, a single DCI can be used to schedule a plurality of CCs. The details of dynamic BWP switching using a single DCI will be described later.

The wireless communication system 10 may support switching of transmission setting display (TCI: Transmission Configuration Indication) states of a plurality of CCs via one downlink control information (DCI). That is, in the wireless communication system 10, a single DCI can be used to schedule a plurality of CCs. The details of TCI switching using a single DCI will be described later.

TCI may be specified by the parameters of the upper layer (for example, the field of tci-PresentInDCI). The tci-PresentInDCI may indicate whether the TCI field is present in the DL-related DCI. The UE200 may consider the TCI to be absent or invalid if the TCI field does not exist.

In the case of cross-carrier scheduling, the network can effectively set the TCI field for CORESET (control resource sets) used for cross-carrier scheduling in the scheduling cell. The TCI provides information on pseudo-collocation (QCL: Quasi Co-Location) of an antenna port for PDCCH (Physical Downlink Control Channel), for example.

A QCL is, for example, when the characteristics of the channel on which the symbol on one antenna port is carried can be inferred from the channel on which the symbol on the other antenna port is carried, the two antenna ports are in pseudo-same location. It may be interpreted as being.

DCI may contain the following information.

(I) Uplink (UL) resource allocation (persistent or non-persistent)
(Ii) Description of downlink (DL) data transmitted to UE200 DCI schedules downlink data channel (eg PDSCH (Physical Downlink Shared Channel)) or uplink data channel (eg PUSCH (Physical Uplink Shared Channel)). It may be interpreted as a set of information that can be used. Such a DCI may be specifically referred to as a scheduling DCI.

In the wireless communication system 10, the secondary cell (SCell) can be activated and deactivated (activation / deactivation). SCell activation / deactivation is specified in Chapter 5.9 of 3GPP TS 38.321.

Also, in the wireless communication system 10, the SCell can be set to the dormancy state. SCelldormancy indication is specified in Release-16 of 3GPP, and realizes efficient and low-delay SCell dormant (sleeping) / non-dormant state layer 1 (L1) display. SCell dormancy indication is specified in Chapter 10.3 of 3GPP TS38.213.

(2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configuration of UE200 will be described.

FIG. 4 is a functional block configuration diagram of the UE 200. As shown in FIG. 4, the UE 200 includes a radio signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, a coding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270. ..

The wireless signal transmitter / receiver 210 transmits / receives a wireless signal according to NR. The radio signal transmission / reception unit 210 corresponds to Massive MIMO, a CA that bundles and uses a plurality of CCs, and a DC that simultaneously communicates between a UE and each of two NG-RAN Nodes.

The amplifier unit 220 is composed of PA (Power Amplifier) / LNA (Low Noise Amplifier) and the like. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. Further, the amplifier unit 220 amplifies the RF signal output from the radio signal transmission / reception unit 210.

The modulation / demodulation unit 230 executes data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB100A or other gNB). Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread (DFT-S-OFDM) may be applied to the modulation / demodulation unit 230. Further, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).

The control signal / reference signal processing unit 240 executes processing related to various control signals transmitted / received by the UE 200 and processing related to various reference signals transmitted / received by the UE 200.

Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB 100A via a predetermined control channel, for example, control signals of the radio resource control layer (RRC). Further, the control signal / reference signal processing unit 240 transmits various control signals to the gNB100A via a predetermined control channel.

The control signal / reference signal processing unit 240 executes processing using a reference signal (RS) such as Demodulation Reference Signal (DMRS) and Phase Tracking Reference Signal (PTRS).

DMRS is a known reference signal (pilot signal) between the base station and the terminal of each terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for the purpose of estimating phase noise, which is a problem in high frequency bands.

In addition to DMRS and PTRS, the reference signal may include ChannelStateInformation-ReferenceSignal (CSI-RS), SoundingReferenceSignal (SRS), PositioningReferenceSignal (PRS) for position information, and the like. ..

In addition, the channel includes a control channel and a data channel. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, Random Access Radio Network Temporary Identifier (RA-RNTI), Downlink Control Information (DCI)), and Physical. Broadcast Channel (PBCH) etc. are included.

Data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data means data transmitted over a data channel. The data channel may be read as a shared channel.

In this embodiment, the control signal / reference signal processing unit 240 receives downlink control information (DCI) from the network. In the present embodiment, the control signal / reference signal processing unit 240 constitutes a receiving unit.

Specifically, the control signal / reference signal processing unit 240 can receive a plurality of types (formats) of DCI including scheduling DCI. The DCI format may include PUSCH, PDSCH scheduling, slot format, TPC (Transmit Power Control) command for PUCCH, PUSCH, and the like. More specifically, the DCI format specified in Chapter 7.3.1 of 3GPP TS38.212 may be targeted.

The coding / decoding unit 250 executes data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100A or other gNB).

Specifically, the coding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into a predetermined size, and executes channel coding for the divided data. Further, the coding / decoding unit 250 decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

The data transmission / reception unit 260 executes transmission / reception of Protocol Data Unit (PDU) and Service Data Unit (SDU). Specifically, the data transmitter / receiver 260 is a PDU / SDU in a plurality of layers (such as a medium access control layer (MAC), a wireless link control layer (RLC), and a packet data convergence protocol layer (PDCP)). Assemble / disassemble. Further, the data transmission / reception unit 260 executes data error correction and retransmission control based on the hybrid ARQ (Hybrid automatic repeat request).

The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 can schedule a plurality of component carriers (CCs) using DCI.

As described above, the wireless communication system 10 can support dynamic BWP switching of a plurality of CCs via one downlink control information (DCI). In order to support such dynamic BWP switching, the control unit 270 schedules a plurality of CCs using one (single) DCI received via the control signal / reference signal processing unit 240. good. That is, the control unit 270 can apply the BWP information indicated by DCI to a plurality of CCs.

In addition, the wireless communication system 10 can support switching of TCIs of a plurality of CCs via one downlink control information (DCI). In order to support such TCI switching, the control unit 270 may schedule a plurality of CCs using one (single) DCI received via the control signal / reference signal processing unit 240. That is, the control unit 270 can apply the TCI information indicated by DCI to a plurality of CCs.

Further, the control unit 270 can determine the active / inactive state (activation / deactivation) of the secondary cell (SCell). As mentioned above, SCell activation / deactivation is specified in Chapter 5.9 of 3GPP TS38.321. SCellactivation / deactivation can be controlled by the network sending an SCell Activation / Deactivation MAC CE to the UE200.

Note that the SCell can form a serving cell together with the primary cell (PCell, PSCell (Primary SCell) may be included). A serving cell may simply be interpreted as a cell to which the UE200 is connected, but more strictly speaking, in the case of an RRC_CONNECTED UE with no carrier aggregation (CA) set, only one serving cell constitutes the primary cell. It may be. For RRC_CONNECTED UEs configured with CA, the serving cell may be interpreted to represent a set of one or more cells including the primary cell and all secondary cells.

The control unit 270 can apply the active / inactive state of the SCell to the above-mentioned multiple CCs in common. That is, the control unit 270 can apply the active / inactive state of a common SCell to a plurality of CCs controlled by one DCI.

Specifically, when a plurality of CCs included in the same group are related to an SCell, the control unit 270 has the same active / inactive state of the SCell, that is, an active state or an inactive state for the plurality of CCs. Can be assumed.

Further, the control unit 270 may apply the setting state of the reference component carrier (reference CC) included in the plurality of CCs to other reactivated component carriers.

For example, the control unit 270 can apply the setting state of reference CC (setting related to BWP and / or TCI, etc.) to other CCs included in the plurality of CCs. The selection criteria for reference CC will be described later.

Further, the control unit 270 may hold the CC setting state related to the deactivated SCell. Specifically, the control unit 270 can hold the setting state (setting related to BWP and / or TCI, etc.) of the CC related to the deactivated SCell among the plurality of CCs. The term "retention" as used herein may mean that information on the set state is stored in a storage device or storage medium inside or outside the UE 200.

The control unit 270 may apply the held setting state to the CC that has been reactivated after being deactivated. Specifically, the control unit 270 may hold the set state for each CC, and applies the set state of the held CC to the reactivated CC.

Further, in the present embodiment, as described above, the SCell can be set to a dormant state (dormancy) or a non-dormancy state (non-dormancy). SCell dormancy indication is specified in Chapter 10.3 of 3GPP TS38.213 and Chapter 7.3.1.3.7 of 3GPP TS38.212.

Specifically, SCelldormancy indication can be specified together with Wake-up indication by the parameters (PS-RNTI, dci-Format2-6) of the upper layer (RRC). In addition, DCI Format 2_6 notifies information about power saving outside the DRX (Discontinuous Reception) active time of one or more UEs.

The dormancy state of the SCell may be interpreted as the state in which the UE200 does not have to monitor the PDCCH, and the non-dormancy state of the SCell may be interpreted as the state in which the UE200 monitors the PDCCH.

The control unit 270 can determine the dormant / non-diapause state of the SCell. The control unit 270 can commonly apply the dormant state (dormancy) / non-dormancy state (non-dormancy) of the SCell to the above-mentioned plurality of CCs. That is, the control unit 270 can apply a common SCell dormant / non-diapause state to a plurality of CCs controlled by one DCI.

Specifically, when a plurality of CCs included in the same group are related to the SCell, the control unit 270 has the same dormant / non-diapause state of the SCell, that is, a dormant state or a non-sleeping state. Can be assumed.

Further, the control unit 270 may apply the setting state of the reference component carrier included in the plurality of CCs to another component carrier that returns from the dormant state to the non-sleeping state.

For example, the control unit 270 can apply the setting state of the reference CC (settings related to BWP and / or TCI, etc.) to other CCs included in the plurality of CCs in the same manner as the above-mentioned SCell activation / deactivation.

Further, the control unit 270 may hold the CC setting state related to the SCell that transitions to the dormant state. Specifically, the control unit 270 can hold the setting state (setting related to BWP and / or TCI, etc.) of the CC related to the SCell transitioning to the dormant state among the plurality of CCs.

The control unit 270 may apply the held setting state to the CC that returns from the dormant state to the non-sleeping state. Specifically, the control unit 270 may hold the set state for each CC, and applies the set state of the held CC to the CC that returns to the non-dormant state.

(3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the operation of UE200 that adapts to SCell activation / deactivation or SCell dormancy indication while controlling a plurality of CCs using DCI will be mainly described.

(3.1) Prerequisite The wireless communication system 10 corresponds to the frequency band (FR2x) exceeding 52.6 GHz and up to 71 GHz as described above. High frequency bands such as FR2x are essentially different from FR1 and FR2 in the following respects.

(Channel / radio wave propagation)
-Expansion of usable bandwidth (approx. 13 GHz (for 57 to 71 GHz unlicensed))
・ Low delay spread due to large path loss due to non-line of sight (NLOS) (device (terminal))
・ Small size antenna element according to wavelength (large-scale (massive) antenna)
・ High directivity based on analog beamforming (narrow beam width)
・ Decrease in power amplifier efficiency (increase in peak-to-average power ratio (PAPR))
• Increased phase noise (higher SCS and shorter symbol time applicability)
Also, the wider the available bandwidth, the more CC is likely to be configured unless a very large CC bandwidth is supported. As mentioned above, when the maximum bandwidth of CCs is 400MHz like FR2, up to 32 CCs can be arranged in the frequency band of 57GHz to 71GHz.

In carrier aggregation (CA), there is a limit to the number of CCs that can be set. Specifically, in 3GPP Release-15 and 16, the maximum number of CCs that can be set for UE200 is 16 for DL and UL, respectively (Chapter 5.4.1 of 3GPP 38.300).

On the other hand, the physical layer (L1, PHY) and medium access control layer (MAC) settings are executed for each CC. In 3GPP Release-15,16, one DCI can schedule only one CC, so a large number of DCIs are required to schedule a large number of CCs. Especially in cross-carrier scheduling, the capacity of PDCCH can be tight.

Also, one transport block (TB) can only be transmitted by one CC (that is, one TB cannot be mapped to multiple CCs), and many CCs have many Hybrid Automatic repeat requests. (HARQ) Acknowledgement (ACK) bit is required.

Furthermore, BWP switching is also executed for each CC. For example, if it is necessary to change the SCS for multiple CCs according to service requirements (delay, etc.), a separate display is required for each CC.

In addition, beam management (TCI status display) is also executed for each CC. Specifically, in 3GPP Release-16, one MAC-CE can update / activate the TCI state of a plurality of CCs, but one DCI can update only the TCI state of one CC.

Despite these restrictions, it is assumed that the channel characteristics of multiple CCs within a single broadband are not so different, so operation at the individual PHY and MAC layers for each CC is not always necessary and efficient. It is assumed that it is not.

Therefore, in the present embodiment, as described above, BWP and / or TCI information is applied to a plurality of CCs based on a single DCI.

(3.2) Adaptation to SCell activation / deactivation (3.2.1) Problem As described above, SCell activation / deactivation can be controlled by SCell Activation / Deactivation MAC CE.

If the SCell is deactivated before the UE200 receives the SCell Activation / Deactivation MAC CE, the upper layer parameters firstActiveDownlinkBWP-Id and DLBWP and ULBWP indicated by the firstActiveUplinkBWP-Id will be activated ( See Chapter 5.9 of 3GPP TS38.321). That is, in order to change the SCell from the inactive state to the active state, activate firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id.

Also, all BWPs related to the SCell that is the target of deactivation are deactivated together with the SCell.

The field of BWP indicator included in DCI may be determined by signaling (BandwidthPart-Config) of the upper layer, and BWP can be applied to a group (or subgroup) of multiple CCs by BWP indicator.

Here, if a part of multiple CCs scheduled based on a single DCI is deactivated and then reactivated, how to apply BWP to the part of the multiple CCs. Is a problem.

For multiple CCs, when scheduling, TCI state, BWP switching or HARQ-ACK feedback, etc. are controlled by a single DCI, the network (specifically, gNB) and UE always operate on the same active BWP. It is desirable to do. Moreover, such a problem is not limited to BWP, but is the same for TCI.

5 and 6 are explanatory diagrams of problems in adapting to SCell activation / deactivation. Specifically, FIG. 5 shows a plurality of BWPs (# 1, 2, 3) having different contents, and one of these BWPs (DL BWPs), that is, the same BWP is applied to a plurality of CCs. Will be done. That is, the BWP specified by a single DCI is applied to multiple CCs (here, firstActiveDownlinkBWP-Id is BWP # 1 and ULBWP is the same).

As shown in FIG. 6, a single DCI is applied to multiple CCs (# 1, 2, 3), but CC # 2 is subject to SCell activation / deactivation, is deactivated, and then When reactivated, if BWP switching is performed during this time, it is unclear which BWP should be applied to CC # 2 to be reactivated. According to firstActiveDownlinkBWP-Id, it becomes BWP # 1, but in this case, the BWP applied to multiple CCs (# 1, 2, 3) does not match.

In the following, we will explain the operation that can avoid the mismatch of BWP applied to multiple CCs even if SCell activation / deactivation occurs while controlling multiple CCs using DCI.

(3.2.2) Operation example 1
(3.2.2.1) Operation example 1-1
In this operation example, the UE 200 can apply the active / inactive state of the SCell to the above-mentioned plurality of CCs in common.

As mentioned above, if scheduling, TCI state, BWP switching or HARQ-ACK feedback, etc. are controlled by a single DCI, for multiple CC groups (or subgroups) configured by the upper layer (RRC). New conditions need to be considered to ensure normal operation.

FIG. 7 shows an example of the BWP setting state according to the operation example 1-1. As shown in FIG. 7, the active / inactive state is common for a plurality of CCs (SCells) belonging to the same group (subgroup).

Specifically, as shown in FIG. 7, CC # 1, 2, and 3 may be deactivated at the same time, that is, at the same timing, and reactivated at the same time.

In order to realize such an operation, a new MAC CE may be defined and the UE 200 may be instructed to activate or deactivate in units of groups belonging to the SCell.

Further, the UE 200 may not expect the group to which the SCell belongs to receive an activation or deactivation instruction of the SCell different from the existing SCell Activation / Deactivation MAC CE.

Alternatively, when the UE200 receives the SCell Activation / Deactivation MAC CE targeting a specific SCell belonging to the group by the SCell Activation / Deactivation MAC CE, the setting for the group is permitted by the signaling of the upper layer (RRC). If so, the SCell Activation / Deactivation MAC CE may be applied to all SCells (CCs) in the group.

In this case, the sCellDeactivationTimer used to deactivate the SCell may be set and maintained for each group. Also, in this operation example, since PCell / PSCell cannot be deactivated (because sCellDeactivationTimer is not configured for PUCCHPCell), a group (subgroup) that does not include PCell / PSCell (and / or PUCCHSCell). May be applied as a target.

In addition, the new MAC CE described above may have the same configuration as the existing SCell Activation / Deactivation MAC CE. However, a new Logical Channel ID (LCID) for the new MAC CE may be set.

FIG. 8 shows a configuration example (part) of a new MAC CE according to operation example 1-1. Specifically, FIG. 8 shows an example in which eight groups (C_0 to C_7) are configured. For example, in the case of 16 groups, 2 octets of MAC CE may be used.

C_i (i = 1 to 7) may indicate activation / deactivation of the SCell group in the group index (i). For example, a value of 1 may indicate activation, and a value of 0 may indicate deactivation. It should be noted that the numerical value and the activation / deactivation may not be fixedly linked in this way, and activation or deactivation may be executed (so-called toggle expression) when the numerical value is changed from the previous numerical value. ..

Also, the sCellDeactivationTimer may be set and managed for each group. For all SCells belonging to a group, if the MAC PDU is sent by a configured ULgrant or received by a configured DL resource allocation, the UE200 may restart the sCellDeactivationTimer associated with that group. ..

(3.2.2.2) Operation example 1-2
In this operation example, the UE 200 can apply the setting state of the reference component carrier (reference CC) included in the plurality of CCs to other reactivated component carriers.

Specifically, any CC included in the group may be predefined and set as a reference CC based on a predetermined rule. When reactivating a CC (SCell) included in the same group, the UE200 applies all the settings of the reference CC in the group (such as settings related to BWP and / or TCI) to the CC to be reactivated. good.

FIG. 9 shows an example of the BWP setting state according to the operation example 1-2. In FIG. 9, CC # 2 is the target of SCell activation / deactivation, as in FIG.

In Fig. 9, CC # 1 is the reference CC, and after reactivation, the CC # 1 setting (BWP # 3) is applied to all CCs.

The reference CC may be selected from PCell, PSCell, the cell with the smallest cell index in the group or PUCCH Cell, or any cell set by the upper layer (RRC).

The UE200 only needs to monitor the DCI applied to the DL reference CC, and a single DCI applied to multiple CCs can be used to reduce blind decoding (BD).

Note that the DL reference CC and the UL reference CC may be set separately. For example, the UE 200 may report uplink control information (UCI) via PUCCH / PUSCH on UL reference CC.

Also, the reference CC setting may be applied to all groups (or subgroups) regardless of whether PCell / PSCell / PUCCHCell is included in the group.

Instead of setting the reference CC, the upper layer (RRC) targets multiple CCs controlled by a single DCI, and the specific BWP and / or TCI state is set as the reference BWP / TCI state, and the active BWP. And / or may be set as a TCI state.

In this case, when the SCell is reactivated, the reference BWP / TCI state may be applied to all CCs in the same group (subgroup).

(3.2.2.3) Operation example 1-3
In this operation example, the UE 200 holds the CC setting state related to the deactivated SCell, and can apply the held setting state to the reactivated CC.

Specifically, when controlling multiple CCs with a single DCI, the UE200 will set the BWP and / or TCI (which may contain other configuration information) per CC when the SCell is deactivated. Can be held in.

Further, when the deactivated SCell is reactivated, the UE 200 may apply the setting state of the CC held to the CC associated with the reactivated SCell. Specifically, the UE200 retains (remembers) the reactivated SCell (and associated CC) instead of applying the firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id settings and the CC. The existing BWP and / or TCI state (which may include other configuration information) may be applied.

Keeping the CC settings related to the deactivated SCell and applying the settings to the reactivated CC are all regardless of whether PCell / PSCell is included in the group. May be applied to a group (or subgroup) of.

FIG. 10 shows an example of the BWP setting state according to the operation example 1-3. In FIG. 10, CC # 2 is the target of SCell activation / deactivation, as in FIG.

In FIG. 10, the BWP setting state (BWP # 2) at the time when CC # 2 (and related SCell) is deactivated is held by the UE200 (see (M: # 2) in the figure). After that, BWP switching is executed and active BWP (may be called activate BWP) is switched to BWP # 3, but UE200 also changes the setting state of BWP applied to CC # 2 to BWP # 3 (Fig.) (See (M: # 3) inside) and keep holding.

After that, when CC # 2 (and related SCell) is reactivated, UE200 can apply the retained BWP # 3 to CC # 2.

When multiple CCs are deactivated / reactivated at the same time, BWP mismatch between CCs as shown in FIG. 10 does not occur.

(3.3) Adaptation to SCell dormancy indication (3.3.1) Task When the transition from the dormant state (dormancy) to the non-dormancy state (non-dormancy) of the SCell is executed, it is set by the upper layer (RRC). The specific BWP that is created becomes the active BWP after transitioning to non-dormancy.

In this case, the BWP applied to multiple CCs associated with the SCell may differ from the BWP applied to one or more CCs associated with the other SCell and controlled by the same (single) DCI. .. Therefore, as with SCell activation / deactivation according to operation example 1, the problem that BWP applied to multiple CCs (# 1, 2, 3) does not match is the transition between dormancy / non-dormancy of SCell (hereinafter, It also exists in SCell dormancy indication).

In addition, the BWP (and TCI) mismatch associated with SCell activation / deactivation and the BWP (and TCI) mismatch associated with SCell dormancy indication may occur at the same time.

FIGS. 11 and 12 show an example of the occurrence of a problem when applying to SCell dormancy indication.

As shown in FIG. 11, when updating the scheduling or TCI status of multiple CCs (# 1, 2, 3), the problem is how to control by a single DCI.

The active BWP applied to multiple CCs belonging to the same group may not be the same when returning from dormancy to non-dormancy (see CC # 3). The first-non-dormant-BWP-ID-xxx may be notified to the UE 200 by the upper layer (RRC).

Further, as shown in FIG. 12, the same problem may occur when both SCell activation / deactivation and SCell dormancy indication are executed. Specifically, FIG. 12 shows an example in which CC # 2 is the target of SCell activation / deactivation and CC # 3 is the target of SCell dormancy indication.

(3.3.2) Operation example 2
An operation example of UE200 applicable to SCelldormancy indication will be described below. Since the operation examples 2-1 to 2-3 correspond to the above-mentioned operation examples 1-1 to 1-3, the description thereof will be omitted as appropriate for the same parts.

(3.3.2.1) Operation example 2-1
In this operation example, the dormant / non-dormant state of SCell can be applied to the above-mentioned plurality of CCs in common.

Specifically, a common (that is, the same) dormant state (dormancy) and / or non-dormancy state (non-dormancy) may be applied to a plurality of CCs belonging to a group (subgroup).

The "SCell group" set for the SCell dormancy indication is preferably the same as the group composed of multiple CCs. Therefore, a single dormancy or non-dormancy state may be applied to the SCell group.

Alternatively, the UE200 may not expect the SCell group (or subgroup) to be notified of a different SCell dormancy indication.

Alternatively, when the UE200 receives a dormancy / non-dormancy instruction for any SCell by an existing DCI, the SCell dormancy indication is given if the setting for the group is permitted by the signaling of the upper layer (RRC). , May be applied to all SCells (CCs) in the group.

Note that dormancy / non-dormancy may be applied only to any state (SCell dormancy indication) such as both at the same time or only non-dormancy.

In addition, since this operation example cannot be applied to PCell / PSCell / PUCCH SCell in the non-diapause state, it may be applied only to the group (subgroup) that does not include PCell / PSCell / PUCCH SCell.

13 and 14 show an example of the BWP setting state according to the operation example 2-1. Specifically, FIG. 13 shows an operation example in which both a dormant state (dormancy) and a non-dormancy state (non-dormancy) are common among a plurality of CCs.

FIG. 14 shows an operation example in which only the non-dormancy state is common among a plurality of CCs. As shown in FIG. 14, the timing of transition to dormancy does not match (not common) between CC # 1, 2, and 3, but the timing of transition (return) to non-dormancy does match.

(3.3.2.2) Operation example 2-2
In this operation example, the UE 200 can apply the setting state of the reference component carrier (reference CC) included in the plurality of CCs to other component carriers that return from the dormant state to the non-sleeping state.

Specifically, any CC included in the group may be predefined and set as a reference CC based on a predetermined rule. When CCs (SCells) included in the same group are placed in the non-dormancy state, the UE200 sets all the settings of the reference CC in the group (such as settings related to BWP and / or TCI) to the non-dormancy state. May be applied to.

FIG. 15 shows an example of the BWP setting state according to the operation example 2-2. In FIG. 15, CC # 2 is the target of SCell dormancy indication. In addition, CC # 1 is reference CC, and after returning to the non-dormancy state, the setting of CC # 1 (BWP # 3) is applied to all CCs.

The reference CC may be selected from PCell, PSCell, the cell having the smallest cell index in the group or PUCCH Cell, or any cell set by the upper layer (RRC), as in operation example 1. ..

The UE200 only needs to monitor the DCI applied to the DL reference CC, and a single DCI applied to multiple CCs can be used to reduce blind decoding (BD).

Note that the DL reference CC and the UL reference CC may be set separately. For example, the UE 200 may report ULreference CC by uplink control information (UCI) via PUCCH / PUSCH.

Also, the reference CC setting may be applied to all groups (or subgroups) regardless of whether PCell / PSCell / PUCCHCell is included in the group.

Instead of setting the reference CC, the upper layer (RRC) targets multiple CCs controlled by a single DCI, and the specific BWP and / or TCI state is set as the reference BWP / TCI state, and the active BWP. And / or may be set as a TCI state.

In this case, when the SCell returns to the non-dormancy state, the reference BWP / TCI state may be applied to all CCs in the same group (subgroup).

(3.3.2.3) Operation example 2-3
In this operation example, the UE 200 holds the CC setting state related to the SCell that has transitioned to the dormant state, and the held setting state can be applied to the CC that has returned to the non-sleeping state.

Specifically, when controlling multiple CCs with a single DCI, the UE200 retains the configuration status for BWP and / or TCI (which may include other configuration information) for each CC when the SCell transitions to dormancy. can do.

Further, when the SCell that has transitioned to dormancy returns to non-dormancy, the UE200 may apply the setting state of the CC held to the CC associated with the SCell that returns to non-dormancy. Specifically, the UE200 holds for the SCell (and associated CC) that returns to non-dormancy instead of applying the first-non-dormant-BWP-ID-xxx setting and the CC. The (stored) BWP and / or TCI state (which may include other configuration information) may be applied.

Keeping the CC setting state related to the SCell that has transitioned to dormancy and applying the setting state to the CC that returns to non-dormancy are all regardless of whether PCell / PSCell is included in the group or not. May be applied to a group (or subgroup) of.

(3.4) Other operation examples Even if the operation examples 1-1 to 1-3 related to SCell activation / deactivation and the operation examples 2-1 to 2-3 related to SCell dormancy indication are combined as follows. good.

-(Operation example 1-1 and operation example 2-1): Application of common SCell activation / deactivation and SCell dormancy indication to multiple CC groups (subgroups)-(Operation example 1-2 and operation example 2-2): DL / UL reference CC settings common to SCell activation / deactivation and SCell dormancy indication ・ (Operation example 1-3 and operation example 2-3): UE200 retains the setting state during deactivation / dormancy. , Apply the held setting state when switching (returning) to the reactivation / non-diapause state ・ (Operation example 1-1 and operation example 2-2): For groups (subgroups) of multiple CCs Application of common SCell activation / deactivation and setting of reference CC for DL / UL for SCell dormancy indication ・ (Operation example 1-2 and operation example 2-1): Common SCell dormancy for multiple CC groups (subgroups) Application of indication and setting of reference CC for DL / UL for SCell activation / deactivation Note that the combination of operation examples is not limited to the above-mentioned example.

(4) Action / Effect According to the above-described embodiment, the following action / effect can be obtained. Specifically, the UE 200 can determine the active / inactive state of the SCell and apply the determined active / inactive state to a plurality of CCs controlled by a single DCI in common.

The UE200 can also apply the setting state of the reference CC included in the multiple CCs to other reactivated CCs.

The UE200 holds the setting state of the CC related to the deactivated SCell, and can apply the held setting state to the reactivated CC.

Therefore, UE200 can adapt to SCell activation / deactivation even when controlling multiple CCs using DCI.

In addition, the UE200 can determine the dormant / non-diapause state of the SCell and apply the determined dormant / non-diapause state to a plurality of CCs controlled by a single DCI in common.

The UE200 can also apply the setting state of the reference CC included in the plurality of CCs to other CCs that return to the non-sleeping state.

The UE200 holds the setting state of the CC related to the SCell that transitions to the dormant state, and can apply the held setting state to the CC that returns to the non-sleeping state.

Therefore, UE200 can adapt to SCelldormancy indication even when controlling multiple CCs using DCI.

(5) Other Embodiments Although the embodiments have been described above, it is obvious to those skilled in the art that various modifications and improvements are possible without being limited to the description of the embodiments.

For example, in the above-described embodiment, the use of a high frequency band such as FR2x was assumed, but the use of such a high frequency band is not always necessary. That is, even when FR1 or FR2 is used, the BWP information represented by a single DCI as described above may be applied to a plurality of CCs in common.

Further, a plurality of CCs may be scheduled separately for Primary Component Carrier (PCC) and Secondary Component Carrier (SCC).

Further, the block configuration diagram (FIG. 4) used in the description of the above-described embodiment shows a block for each functional unit. These functional blocks (components) are realized by any combination of at least one of hardware and software. Further, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or two or more physically or logically separated devices can be directly or indirectly (eg, for example). , Wired, wireless, etc.) and may be realized using these plurality of devices. The functional block may be realized by combining the software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and assumption. Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but limited to these I can't. For example, a functional block (constituent unit) for functioning transmission is called a transmitting unit or a transmitter. As described above, the method of realizing each of them is not particularly limited.

Further, the UE 200 described above may function as a computer that processes the wireless communication method of the present disclosure. FIG. 16 is a diagram showing an example of the hardware configuration of the UE 200. As shown in FIG. 16, the UE 200 may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

In the following explanation, the word "device" can be read as a circuit, device, unit, etc. The hardware configuration of the device may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

Each functional block of the UE200 (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

In addition, each function in the UE 200 is such that the processor 1001 performs an operation by loading predetermined software (program) on the hardware such as the processor 1001 and the memory 1002, and controls the communication by the communication device 1004, or the memory 1002 and the memory 1002. It is realized by controlling at least one of reading and writing of data in the storage 1003.

Processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.

Further, the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. Further, the various processes described above may be executed by one processor 1001 or may be executed simultaneously or sequentially by two or more processors 1001. Processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunication line.

The memory 1002 is a computer-readable recording medium, and is composed of at least one such as ReadOnlyMemory (ROM), ErasableProgrammableROM (EPROM), Electrically ErasableProgrammableROM (EEPROM), and RandomAccessMemory (RAM). May be done. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can execute the method according to the embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, an optical disk such as Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, an optical magnetic disk (for example, a compact disk, a digital versatile disk, or a Blu-ray). It may consist of at least one (registered trademark) disk), smart card, flash memory (eg, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. Storage 1003 may be referred to as auxiliary storage. The recording medium described above may be, for example, a database, server or other suitable medium containing at least one of memory 1002 and storage 1003.

The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like.

The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

In addition, each device such as the processor 1001 and the memory 1002 is connected by the bus 1007 for communicating information. Bus 1007 may be configured using a single bus or may be configured using different buses for each device.

Further, the device includes hardware such as a microprocessor, a digital signal processor (Digital Signal Processor: DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA). The hardware may implement some or all of each functional block. For example, processor 1001 may be implemented using at least one of these hardware.

Further, the notification of information is not limited to the mode / embodiment described in the present disclosure, and may be performed by using another method. For example, information notification includes physical layer signaling (for example, Downlink Control Information (DCI), Uplink Control Information (UCI), upper layer signaling (eg, RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block)). (MIB), System Information Block (SIB)), other signals or a combination thereof. RRC signaling may also be referred to as an RRC message, for example, RRC Connection Setup. ) Message, RRC Connection Reconfiguration message, etc. may be used.

Each aspect / embodiment described in the present disclosure includes LongTermEvolution (LTE), LTE-Advanced (LTE-A), SUPER3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system ( 5G), FutureRadioAccess (FRA), NewRadio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UltraMobile Broadband (UMB), IEEE802.11 (Wi-Fi (registered trademark)) , IEEE802.16 (WiMAX®), IEEE802.20, Ultra-WideBand (UWB), Bluetooth®, and other systems that utilize appropriate systems and at least one of the next-generation systems extended based on them. It may be applied to one. In addition, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.

In some cases, the specific operation performed by the base station in the present disclosure may be performed by its upper node. In a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (for example, MME or). It is clear that it can be done by at least one of (but not limited to, S-GW, etc.). Although the case where there is one network node other than the base station is illustrated above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).

Information and signals (information, etc.) can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input / output may be performed via a plurality of network nodes.

The input / output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information can be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (Boolean: true or false), or by comparing numerical values (for example, a predetermined value). It may be done by comparison with the value).

Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched with execution. Further, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit one, but is performed implicitly (for example, the notification of the predetermined information is not performed). May be good.

Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, is an instruction, instruction set, code, code segment, program code, program, subprogram, software module. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be broadly interpreted.

Further, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, a website that uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technology (infrared, microwave, etc.) When transmitted from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.

Note that the terms explained in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, the signal may be a message. Further, the component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values from predetermined values, or using other corresponding information. It may be represented. For example, the radio resource may be one indicated by an index.

The names used for the above parameters are not limited in any respect. Further, mathematical formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. Since various channels (eg, PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in any respect limited names. is not it.

In this disclosure, "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", " "Access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "cell group" Terms such as "carrier" and "component carrier" can be used interchangeably. Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.

The base station can accommodate one or more (for example, three) cells (also called sectors). When a base station accommodates multiple cells, the entire base station coverage area can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small indoor base station (Remote Radio)). Communication services can also be provided by Head: RRH).

The term "cell" or "sector" refers to a base station that provides communication services in this coverage, and part or all of the coverage area of at least one of the base station subsystems.

In the present disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" may be used interchangeably. ..

Mobile stations can be used by those skilled in the art as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless. It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, or the like. At least one of the base station and the mobile station may be a device mounted on the mobile body, the mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be. It should be noted that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

Further, the base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, communication between a base station and a mobile station has been replaced with communication between a plurality of mobile stations (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Each aspect / embodiment of the present disclosure may be applied to the configuration. In this case, the mobile station may have the functions of the base station. In addition, words such as "up" and "down" may be read as words corresponding to communication between terminals (for example, "side"). For example, the upstream channel, the downstream channel, and the like may be read as a side channel.

Similarly, the mobile station in the present disclosure may be read as a base station. In this case, the base station may have the functions of the mobile station.
The radio frame may be composed of one or more frames in the time domain. Each one or more frames in the time domain may be referred to as a subframe. Subframes may further consist of one or more slots in the time domain. The subframe may have a fixed time length (eg, 1 ms) that is independent of numerology.

The numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology includes, for example, SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, transmission / reception. At least one of a specific filtering process performed by the machine in the frequency domain, a specific windowing process performed by the transceiver in the time domain, and the like may be indicated.

The slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. Slots may be in numerology-based time units.

The slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain. The mini-slot may also be referred to as a sub-slot. A minislot may consist of a smaller number of symbols than the slot. PDSCH (or PUSCH) transmitted in time units larger than the minislot may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (or PUSCH) mapping type B.

The wireless frame, subframe, slot, minislot and symbol all represent the time unit when transmitting a signal. The radio frame, subframe, slot, minislot and symbol may have different names corresponding to each.

For example, one subframe may be referred to as a transmission time interval (TTI), a plurality of consecutive subframes may be referred to as TTI, and one slot or one minislot may be referred to as TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (eg, 1-13 symbols), or a period longer than 1ms. It may be. The unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units. The definition of TTI is not limited to this.

The TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation. When a TTI is given, the time interval (for example, the number of symbols) to which the transport block, code block, code word, etc. are actually mapped may be shorter than the TTI.

When one slot or one mini slot is called TTI, one or more TTIs (that is, one or more slots or one or more mini slots) may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like. TTIs shorter than normal TTIs may also be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots, and the like.

The long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (for example, shortened TTI, etc.) may be read as less than the TTI length of the long TTI and 1 ms. It may be read as a TTI having the above TTI length.

The resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain. The number of subcarriers contained in RB may be the same regardless of numerology, and may be, for example, 12. The number of subcarriers contained in the RB may be determined based on numerology.

Further, the time domain of RB may include one or more symbols, and may have a length of 1 slot, 1 mini slot, 1 subframe, or 1 TTI. Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.

One or more RBs include a physical resource block (Physical RB: PRB), a sub-carrier group (Sub-Carrier Group: SCG), a resource element group (Resource Element Group: REG), a PRB pair, an RB pair, and the like. May be called.

Further, the resource block may be composed of one or a plurality of resource elements (ResourceElement: RE). For example, 1RE may be a radio resource area of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (which may also be called partial bandwidth, etc.) may represent a subset of consecutive common RBs (common resource blocks) for a neurology in a carrier. good. Here, the common RB may be specified by the index of the RB with respect to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP). One or more BWPs may be set in one carrier for the UE.

At least one of the configured BWPs may be active, and the UE may not expect to send or receive a given signal / channel outside the active BWP. In addition, "cell", "carrier" and the like in this disclosure may be read as "BWP".

The above-mentioned structures such as wireless frames, subframes, slots, minislots and symbols are merely examples. For example, the number of subframes contained in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in RB. The number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or connection between two or more elements, and each other. It can include the presence of one or more intermediate elements between two "connected" or "combined" elements. The connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in the present disclosure, the two elements use at least one of one or more wires, cables and printed electrical connections, and, as some non-limiting and non-comprehensive examples, the radio frequency domain. , Electromagnetic energy with wavelengths in the microwave and light (both visible and invisible) regions, etc., can be considered to be "connected" or "coupled" to each other.

The reference signal can also be abbreviated as Reference Signal (RS) and may be called a pilot (Pilot) depending on the applicable standard.

The phrase "based on" as used in this disclosure does not mean "based on" unless otherwise stated. In other words, the statement "based on" means both "based only" and "at least based on".

The "means" in the configuration of each of the above devices may be replaced with "part", "circuit", "device" and the like.

Any reference to elements using designations such as "first", "second" as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Therefore, references to the first and second elements do not mean that only two elements can be adopted there, or that the first element must somehow precede the second element.

When "include", "including" and variations thereof are used in the present disclosure, these terms are as comprehensive as the term "comprising". Is intended. Moreover, the term "or" used in the present disclosure is intended not to be an exclusive OR.

In the present disclosure, if articles are added by translation, for example, a, an and the in English, the disclosure may include that the nouns following these articles are plural.

The terms "determining" and "determining" used in this disclosure may include a wide variety of actions. "Judgment" and "decision" are, for example, judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry). (For example, searching in a table, database or another data structure), ascertaining may be regarded as "judgment" or "decision". Also, "judgment" and "decision" are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (Accessing) (for example, accessing data in memory) may be regarded as "judgment" or "decision". In addition, "judgment" and "decision" mean that the things such as solving, selecting, choosing, establishing, and comparing are regarded as "judgment" and "decision". Can include. That is, "judgment" and "decision" may include considering some action as "judgment" and "decision". Further, "judgment (decision)" may be read as "assuming", "expecting", "considering" and the like.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". The term may mean that "A and B are different from C". Terms such as "separate" and "combined" may be interpreted in the same way as "different".

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure may be implemented as an amendment or modification without departing from the purpose and scope of the present disclosure, which is determined by the description of the scope of claims. Therefore, the description of the present disclosure is for the purpose of exemplary explanation and does not have any limiting meaning to the present disclosure.

10 Radio communication system 20 NG-RAN
100A, 100B gNB
UE 200
210 Radio signal transmission / reception unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Coding / decoding unit 260 Data transmission / reception unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims (3)

1. A receiver that receives downlink control information from the network,
   A control unit that schedules a plurality of component carriers using the downlink control information is provided.
   The control unit
   Determine the active / inactive state of the secondary cell and
   A terminal that commonly applies the active / inactive state to the plurality of component carriers.
2. A receiver that receives downlink control information from the network,
   A control unit that schedules a plurality of component carriers using the downlink control information is provided.
   The control unit is a terminal that applies the setting state of the reference component carrier included in the plurality of component carriers to other reactivated component carriers.
3. A receiver that receives downlink control information from the network,
   A control unit that schedules a plurality of component carriers using the downlink control information is provided.
   The control unit
   Holds the configuration state of the component carrier associated with the deactivated secondary cell and
   A terminal that applies the held setting state to the reactivated component carrier.

Images