Terminal and communication method

Abstract

This terminal comprises a communication unit that receives or transmits signals, and a control unit that performs measurements in a measurement period, wherein the control unit determines whether or not to skip the measurements in a specific measurement period on the basis of a field of downlink control information which is received by the communication unit and which schedules an uplink signal and / or a downlink signal on a set of cells.

Description

Terminals and communication methods

[0001] This disclosure relates to terminals and communication methods.

[0002] The 3rd Generation Partnership Project (3GPP®) has standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)), and is also working on standardizing the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] In 5G, technologies are being considered that meet requirements such as large-capacity systems, high-speed data transmission rates, low latency, simultaneous connection of numerous terminals, low cost, and low power consumption (for example, Non-Patent Document 1).

[0004] With the expansion of mobile communication systems as described above, the use and widespread adoption of XR (extended reality), such as VR (virtual reality), AR (augmented reality), and MR (mixed reality), which enable the combination of the real world and the virtual world (virtual content), is expected. 3GPP is discussing XR extensions toward Release 19 (see, for example, Non-Patent Document 2).

[0005] In relation to XR extensions, for example, extensions concerning the measurement gap (MG) and scheduling limitations have been widely discussed.

[0006] For example, regarding scheduling constraints for inter-frequency RRM measurements of FR1 and FR2 with a measurement gap and intra-frequency RRM measurements of FR2 without a measurement gap, identifying extensions to reduce the impact on capacity and individual terminals may be included in the scope of the standard in the future.

[0007] 3GPP TS 38.300 V17.6.0 (2023-09)“Moderator's summary for REL-19 RAN2 topic Enhancements for XR”, RP-232619, 3GPP TSG-RAN Meeting #101, 3GPP, September 2023

[0008] Current wireless communication systems utilize measurements using a Synchronization Signal Block (SSB) (SSB-based measurement).

[0009] For SSB measurements, the terminal is notified of the measurement timing settings (SMTC: SSB-based Measurement Timing Configuration), and the terminal performs measurements based on the signal being measured within the configured SMTC window. In addition, settings related to the measurement gap may be notified to the terminal for SSB measurements, such as for switching the operating frequency (RF: Radio Frequency).

[0010] Due to the periodicity of XR traffic, if the transmission and reception of signals related to XR traffic overlap with the SMTC window or measurement gap, it may become impossible to schedule the signals, potentially leading to capacity loss and other problems caused by scheduling limitations associated with measurement.

[0011] Furthermore, current wireless communication systems utilize other measurement methods, such as measurements using the Channel State Information - Reference Signal (CSI-RS) (CSI-RS based measurement), and the aforementioned problems can occur in various measurements as well. Moreover, the aforementioned problems can also occur in the transmission and reception of signals other than those related to XR traffic.

[0012] One aspect of this disclosure provides a terminal and a communication method that can reduce the impact caused by scheduling limitations related to measurement.

[0013] A terminal according to one aspect of the present disclosure comprises a communication unit that receives or transmits signals, and a control unit that performs measurements during a measurement period, wherein the control unit determines whether or not to skip the measurement during a particular measurement period based on a field of downlink control information that schedules uplink and / or downlink signals on a set of cells, which is received by the communication unit.

[0014] This figure shows an example of a wireless communication system according to an embodiment of the present disclosure. This figure shows an example of a frequency range used in a wireless communication system according to an embodiment of the present disclosure. This figure shows an example of the configuration of wireless frames, subframes, and slots used in a wireless communication system according to an embodiment of the present disclosure. This figure shows an example of notification of skipping a measurement gap opportunity by DCI according to an embodiment of the present disclosure. This figure shows an example of notification of skipping a measurement gap opportunity by DCI according to an embodiment of the present disclosure. This figure shows an example of notification of skipping a measurement gap opportunity by DCI according to an embodiment of the present disclosure. This figure shows an example of terminal operation according to an embodiment of the present disclosure. This block diagram shows an example of the configuration of a base station according to an embodiment of the present disclosure. This block diagram shows an example of the configuration of a terminal according to an embodiment of the present disclosure. This figure shows an example of the hardware configuration of a base station and terminal according to an embodiment of the present disclosure. This figure shows an example of the configuration of a vehicle according to an embodiment of the present disclosure. This figure illustrates the RAN1#118 agreement. This figure illustrates Proposal 5-1. This figure illustrates Proposal 5-2. This figure illustrates Proposal 5-3. This figure illustrates Proposal 6.

[0015] Hereinafter, an embodiment relating to one aspect of this disclosure will be described with reference to the drawings.

[0016] (Embodiment) <Wireless Communication System> Figure 1 is a diagram showing an example of a wireless communication system 10 according to an embodiment of the present disclosure. The wireless communication system 10 is a wireless communication system in accordance with 5G NR and includes Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN 20) and terminal 200 (hereinafter also referred to as UE (User Equipment) 200).

[0017] The wireless communication system 10 may be a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G.

[0018] NG-RAN20 includes base station 100A (hereinafter also referred to as gNB100A) and base station 100B (hereinafter also referred to as gNB100B). When it is not necessary to distinguish between gNB100A, gNB100B, etc., they are collectively referred to as gNB or base station 100. Furthermore, the number of gNBs and UEs is not limited to the example shown in Figure 1.

[0019] NG-RAN20 actually includes multiple NG-RAN nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN20 and 5GC may simply be referred to as "the network." Furthermore, in the following, gNB may be read as "network (NW)."

[0020] gNB100A and gNB100B are, for example, base stations compliant with 5G, and perform 5G-compliant wireless communication with UE200. gNB100A, gNB100B, and UE200 may support MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling the radio signals transmitted from multiple antenna elements; Carrier Aggregation (CA), which uses multiple component carriers (CC); and Dual Connectivity (DC), which enables communication between the UE and each of the two NG-RAN nodes.

[0021] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FRs). Figure 2 shows an example of an FR used in the wireless communication system 10. As shown in Figure 2, the wireless communication system 10 may support FR1 and FR2. The frequency bands of each FR are, for example, as follows: ・FR1: 410 MHz to 7.125 GHz ・FR2: 24.25 GHz to 52.6 GHz

[0022] In FR1, a subcarrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and an SCS of 60 kHz or 120 kHz (240 kHz may be included) may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0023] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS 38.300 and corresponds to a single subcarrier interval in the frequency domain.

[0024] Furthermore, the wireless communication system 10 may support higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands exceeding 52.6 GHz and up to 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x". When using a bandwidth exceeding 52.6 GHz, CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplexing) / DFT-S-OFDM (Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing) with a larger SCS may be applied.

[0025] Figure 3 shows an example of the configuration of wireless frames (system frames), subframes, and slots used in the wireless communication system 10. As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

[0026] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it could be 28 or 56 symbols, etc.). In addition, the number of slots per subframe may differ depending on the SCS.

[0027] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, bandwidth part (BWP), or similar.

[0028] The gNB100 transmits control information, setting information, etc., to the UE200 as a downlink (DL) signal.

[0029] Furthermore, for example, the gNB100 receives control information, data signals, and information regarding the processing capabilities of the UE200 (terminal capability information; e.g., UE capability) from the UE200 as uplink (UL) signals.

[0030] The channels used to transmit DL signals include, for example, a data channel and a control channel. For example, the data channel may include a Physical Downlink Shared Channel (PDSCH), and the control channel may include a Physical Downlink Control Channel (PDCCH). For example, gNB100 transmits control information to UE200 using the PDCCH and transmits DL data signals using the PDSCH. Note that PDSCH is an example of a Downlink Shared Channel, and PDCCH is an example of a Downlink Control Channel. Note that PDCCH may be interpreted as Downlink Control Information (DCI), control information, etc., transmitted in the PDCCH.

[0031] The reference signals included in the DL signal may include, for example, at least one of the following: DMRS (Demodulation Reference Signal), PTRS (Phase Tracking Reference Signal), CSI-RS (Channel State Information - Reference Signal), SRS (Sounding Reference Signal), and PRS (Positioning Reference Signal) for position information. For example, reference signals such as DMRS and PTRS are used to demodulate the DL data signal and are transmitted using PDSCH.

[0032] The UE200 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module.

[0033] The UE200 receives control signals or data signals from the gNB100 via DL and transmits control signals or data signals to the gNB100 via UL, thereby utilizing various communication services provided by the wireless communication system 10. The UE200 also receives various reference signals transmitted from the gNB100 and performs propagation path quality measurements based on the reception results of these reference signals.

[0034] For example, UE200 receives control information, setting information, etc., from gNB100 as DL signals.

[0035] Furthermore, for example, UE200 transmits control information, data signals, terminal capability information of UE200, etc., to gNB100 as UL signals.

[0036] The channels used to transmit UL signals include, for example, a data channel and a control channel. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, UE200 transmits control information using PUCCH and transmits UL data signals using PUSCH. Note that PUSCH is an example of an uplink shared channel, and PUCCH is an example of an uplink control channel. Note that PUSCH or PUCCH may be interpreted as Uplink Control Information (UCI), control information, etc., transmitted in PUSCH or PUCCH.

[0037] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRSRS, and PRS for location information. For example, reference signals such as DMRS and PTRS are used to demodulate the UL data signal and are transmitted using PUSCH.

[0038] <Current Status of XR Discussions> XR presents attractive use cases for future wireless communication systems. On the other hand, XR also presents challenges that need to be considered and addressed. One such challenge is that 3GPP is discussing XR extensions toward Release 19 (see, for example, Non-Patent Document 2), and extensions related to measurement gaps and scheduling limitations are being widely discussed.

[0039] <RAN1#118 Agreement> If Alt.1 of the RAN1#117 agreement is supported, it was agreed that the minimum time offset X between the skip instruction and the skipped measurement opportunity would be discussed and determined for a specific value in RAN4 (see Figure 12).

[0040] <Regarding SSB and SSB Measurement>Signals and / or channels transmitted from a base station to a terminal include those transmitted periodically. Examples of such signals and / or channels include Synchronization Signal Blocks (SSBs).

[0041] SSBs are used by a terminal for measurements (SSB measurements) such as received power (e.g., SS-RSRP: Synchronization Signal Reference Signal Received Power) and received quality (e.g., SS-RSRQ: Synchronization Signal Reference Signal Received Quality). Such measurements are an example of RRM (Radio Resource Management) measurements.

[0042] For SSB measurements, timing settings related to the measurements (SMTC) are notified to the terminal. SMTC may include the length, period, timing offset, etc. of the SSB measurement period (which may also be called the SMTC window, measurement timing, etc.). The terminal performs measurements based on the signal to be measured within the set SMTC window.

[0043] Also, for switching of the operating frequency (RF: Radio Frequency), etc., settings related to measurement gaps may be notified to the terminal for SSB measurements. A measurement gap is an extended period for measurements where additional periods may be added before and after the SMTC window. The settings related to the measurement gap may also include the length, period, etc.

[0044] Also, examples of RRM measurements include measurements based on CSI-RS (CSI-RS measurements).

[0045] In NR, the following RRM measurements are used, including SSB and CSI-RS measurements, with or without a measurement gap: (1) Intra-frequency measurement (2) Inter-frequency measurement

[0046] The terminal can perform the RRM measurement and signal transmission / reception described above using at least one frequency band (carrier frequency) from the first frequency band (FR1) and the second frequency band (FR2).

[0047] <Scheduling Restrictions Regarding RRM Measurement> Regarding in-frequency SSB measurements, scheduling restrictions (terminal operation restrictions) for in-frequency SSB measurements without a measurement gap, in-frequency SSB measurements with NCSG (Network Configured Small Gap), and in-frequency SSB measurements with a measurement gap are described in the following sections of the current standard: In-frequency SSB measurements without a measurement gap: TS 38.133 clause 9.2.5.3 (In short, if the conditions are met, scheduling restrictions are imposed on SSB symbols measured within the SMTPC window or on all symbols within the SMTPC window) In-frequency SSB measurements with NCSG: TS 38.133 clause 9.2.5.3 In-frequency SSB measurements with a measurement gap: TS 38.133 clause 9.1.2

[0048] Regarding inter-frequency SSB measurements, scheduling restrictions (terminal operation restrictions) for inter-frequency SSB measurements without a measurement gap, inter-frequency SSB measurements with an NCSG, and inter-frequency SSB measurements with a measurement gap are described in the following sections of the current standard. Inter-frequency SSB measurements without a measurement gap: TS 38.133 clause 9.3.5.3 (In short, if the conditions are met, scheduling restrictions are imposed on SSB symbols measured within an SMTC window or on all symbols within an SMTC window) Inter-frequency SSB measurements with NCSG: TS 38.133 clause 9.2.10.3 (In short, if the conditions are met, scheduling restrictions are imposed on the union of SSB symbols measured within an SMTC window for all measurement occasions (MOs) or on the union of all symbols within an SMTC window for all MOs) Inter-frequency SSB measurements with a measurement gap: TS 38.133 clause 9.1.2

[0049] Regarding in-frequency CSI-RS measurements, scheduling restrictions (terminal operation restrictions) for in-frequency CSI-RS measurements without a measurement gap are described in the following section of the current standard: In-frequency CSI-RS measurements without a measurement gap: TS 38.133 clause 9.10.2.6 (In short, scheduling restrictions are imposed on the set CSI-RS symbols if the conditions are met).

[0050] Regarding inter-frequency CSI-RS measurements, scheduling restrictions (terminal operation restrictions) for inter-frequency CSI-RS measurements with a measurement gap are described in the following section of the current standard: Inter-frequency CSI-RS measurements with a measurement gap: TS 38.133 clause 9.1.2

[0051] Due to the periodicity of XR traffic, if the transmission and reception of signals related to XR traffic overlap with the SMTC window or measurement gap, it may become impossible to schedule the signals, potentially leading to capacity loss and other problems caused by scheduling limitations associated with measurement.

[0052] Incidentally, the terminal may also perform measurements for wireless link monitoring, L1-RSRP measurements, beam fault detection measurements, and so on.

[0053] The problems described above can occur in CSI-RS measurements and various other measurements, including those mentioned above. Furthermore, these problems can also occur in the transmission and reception of signals other than those related to XR traffic.

[0054] Currently, extensions to the scheduling limits are being considered, but the specific control mechanisms required to implement these extensions have not been fully investigated.

[0055] Therefore, the following describes proposals to mitigate the effects caused by scheduling limitations related to measurements (proposals to relax scheduling limitations related to measurements).

[0056] More specifically, this document describes a proposal for DCI's support for dynamic notifications to skip (or disable) specific measurement gaps / RRM measurements / SMTC windows.

[0057] The following proposals are explained assuming that the measurement gap is periodic. For example, the measurement gap (configuration) may be set by an existing measurement gap configuration information element (e.g., MeasGapConfig IE) which is an RRC parameter, or by a similar (new) information element, and the period of the measurement gap may be set in such an information element.

[0058] Furthermore, the following proposals are applicable to in-frequency SSB and / or CSI-RS measurements, and / or inter-frequency SSB and / or CSI-RS measurements, with measurement gap / RRM measurement / SMTC window.

[0059] Furthermore, in the following proposal, DCI will notify the system to skip the measurement gap / RRM measurement / SMTC window. The operation of terminal 200 regarding skipping the measurement gap / RRM measurement / SMTC window may be based on the notification from base station 100.

[0060] For example, if terminal 200 is notified by base station 100 to skip the measurement gap / RRM measurement / SMTC window, terminal 200 may not perform RRM measurement (and / or Positioning Reference Signal (PRS) measurement) in the measurement gap / RRM measurement / SMTC window, and may instead receive / transmit DL / UL channels / signals.

[0061] The matters described in the following proposals may be combined as appropriate, provided that they do not create contradictions.

[0062] In this application, the notation " / " may mean "and / or" unless otherwise specified.

[0063] Furthermore, in this application, the expression "do not receive / send" may be reinterpreted as "do not assume receiving / sending," "make receiving / sending impossible," "do not perform receiving / sending," "restrict receiving / sending," "assume that receiving / sending is not possible," etc.

[0064] Furthermore, in this application, the expression "deactivate" may be reinterpreted as "disable," "turn off," or "set to an inactive state (disabled state, off state)," and the expression "activate" may be reinterpreted as "enable," "turn on," or "set to an active state (disabled state, off state)."

[0065] Furthermore, in this application, the expression "notification" may be replaced with the expression "instruction."

[0066] Furthermore, in this application, signals such as SSB and CSI-RS used for measuring received power, reception quality, etc., may be referred to as measurement signals, measurement signals, etc.

[0067] Furthermore, in this application, "skipping ~" may be interpreted as "not performing a measurement (e.g., RRM measurement) in ~", or "assuming that scheduling restrictions do not apply in ~ (not assuming that scheduling restrictions apply)".

[0068] Furthermore, in this application, "measurement gap opportunity," "RRM measurement opportunity," and "SMTC window opportunity" may be abbreviated as "measurement gap," "RRM measurement," and "SMTC window," respectively. Also, "measurement gap / RRM measurement / SMTC window" may be abbreviated as "measurement gap, etc."

[0069] Furthermore, in this application, the measurement gap, etc. (opportunity) may be referred to as an extended period or interval for measurement, etc.

[0070] <Proposal> The following is a proposal regarding DCI's support for dynamic notifications that skip specific measurement gaps / RRM measurements / SMTC windows. Note that DCI's dynamic notifications may also be referred to as information indicating that measurements will not be performed (during a periodic extended time for measurements).

[0071] The terminal 200 may be notified of skipping measurement gaps, etc., by receiving the dynamic notification from the base station 100 via DCI, and may decide which measurement gaps, etc., to skip and which not to skip based on the DCI. The dynamic notification via DCI may follow proposals 1 to 4 below.

[0072] <Proposal 1: DCI Format> A new DCI format may be used, or an existing DCI format may be used, to indicate that a specific measurement gap / RRM measurement / SMTC window should be skipped.

[0073] The specific measurement gap may be, for example, a measurement gap for each terminal, for each specific frequency band (e.g., FR1 / FR2), a measurement gap for intra-frequency / inter-frequency measurements, a measurement gap whose gap length is a specific value or within a specific range of values, a measurement gap for a specific ID, a measurement gap with a repeating period (provided by mgrp) that is a specific value or within a specific range of values, etc.

[0074] Furthermore, specific RRM measurements may include, for example, RRM measurements with or without a measurement gap, SSB-based or CSI-RS-based RRM measurements, in-frequency or inter-frequency RRM measurements, and RRM measurements of specific IDs (such as measObjectId).

[0075] (Option 1-1: New DCI format) A new DCI format, or an existing DCI format including a scrambled CRC with a new RNTI, may be used to indicate that certain measurement gaps, etc., should be skipped.

[0076] (Option 1-2: Existing DCI format) An existing DCI format, including CRC scrambled by an existing RNTI, may be used to indicate that certain measurement gaps, etc., should be skipped.

[0077] <Proposal 2: DCI Field> A DCI field may be used to notify that certain measurement gaps, etc., should be skipped.

[0078] (Option 2-1) If the DCI is based on a new DCI format or on an existing field including a scrambled CRC with a new RNTI, the DCI format may include the DCI fields described in Proposal 3 below to indicate that certain measurement gaps, etc., should be skipped.

[0079] (Option 2-2) If the DCI is in an existing DCI format with CRC scrambled by an existing RNTI, you may indicate to skip certain measurement gaps, etc., using one of the following sub-options.

[0080] (Option 2-2-1: New field) A new field may indicate skipping of certain measurement gaps, etc.

[0081] Whether a new field exists in the DCI format may be determined by RRC.

[0082] The content of the new fields used to indicate skips such as specific measurement gaps is described in Proposal 3 below.

[0083] (Examples of new fields) The following are specific examples of new fields: (Example 1): A new field in a non-fallback DL grant DCI with (or without) scheduling PDSCH (e.g., DCI1_1 / 1_2 / 1_3) (Example 2): A new field in a non-fallback UL grant DCI with (or without) PUSCH scheduling (e.g., DCI0_1 / 0_2 / 0_3) (Example 3): A new field in DCI format 2_1 with (or without) DL preemption instructions (Example 4): A new field in DCI format 2_4 with (or without) UL cancellation instructions

[0084] (Option 2-2-2: Reinterpretation of existing fields) Certain existing fields may be reinterpreted to indicate skips such as specific measurement gaps.

[0085] The contents of existing fields used to indicate skips such as specific measurement gaps are described in Proposal 3 below.

[0086] (Examples of existing fields) The following are specific examples of existing fields: (Example 1): Existing fields in non-fallback DL grant DCI without scheduling PDSCH (e.g., DCI1_1 / 1_2 / 1_3) (Example 2): Existing fields in non-fallback UL grant DCI without scheduling PUSCH (e.g., DCI0_1 / 0_2 / 0_3) (Example 3): Existing fields in DCI2_1 without DL preemption instruction (Example 4): Existing fields in DCI2_4 without UL cancellation instruction

[0087] Whether or not the DCI format can be reinterpreted to indicate skips such as specific measurement gaps may be enabled / configured by the RRC.

[0088] If enabled / configured, whether these fields are reinterpreted or the DCI is reverted to the existing interpretation may be determined based on the values ​​of specific DCI fields.

[0089] For example, if DCI indicates specific values ​​for a particular DCI field (e.g., HPN is all "0", FDRA is all "0", TDRA is all "0", MCS is all "0", etc.), terminal 200 reinterprets the existing DCI field as an instruction to skip a specific measurement gap or the like.

[0090] (Option 2-2-3: New flag field + Option 2-2-1) A new 1-bit flag field (e.g., "skip instruction field") and a new field for skip instructions may indicate a skip of a specific measurement gap or the like.

[0091] In this case, the flag field (e.g., the "skip instruction field") indicates whether the DCI contains instructions for skipping a specific measurement gap or the like. A one-bit flag, if it has a specific value (e.g., "0" or "1"), indicates that a new field (similar to option 2-2-1) exists in the DCI to indicate the skipping of a specific measurement gap or the like, and if it has any other value (e.g., "1" or "0"), indicates that a new field for indicating the skipping of a specific measurement gap or the like does not exist in the DCI.

[0092] Whether or not a flag field (e.g., a "skip instruction field") exists in the DCI format may be set by the RRC.

[0093] (Option 2-2-4: New flag field + Option 2-2-2) A new 1-bit flag field (e.g., a "skip indicator field") and a reinterpretation of an existing field may indicate a skip of a specific measurement gap or the like.

[0094] In this case, the flag field (e.g., the "skip instruction field") indicates whether the DCI contains an instruction to skip a specific measurement gap or the like. If the 1-bit flag is a specific value (e.g., "0" (or "1")), the terminal 200 reinterprets the existing DCI field as an instruction to skip a specific measurement gap or the like (similar to option 2-2), and if it is any other value (e.g., "1" (or "0")), the DCI is interpreted as it is.

[0095] Whether or not a flag field (e.g., a "skip instruction field") exists in the DCI format may be set by the RRC.

[0096] <Proposal 3: Contents of the DCI Field> The contents of the DCI field, which is used to indicate skipping of specific measurement gaps, etc., are shown below.

[0097] (Option 3-1) Option 3-1 describes a case where a 1-bit flag indicates whether or not to skip a specific measurement gap, etc.

[0098] A single-bit flag indicates whether to skip a specific measurement gap, etc., if it is a specific value (e.g., "0" or "1"), or whether to not skip a specific measurement gap, etc., if it is any other value (e.g., "1" or "0").

[0099] In this case, the number of skipped opportunities (such as measurement gaps) N (where N is an integer greater than or equal to 1) may be set by RRC, defined by a standard, or notified by DCI.

[0100] If the number of opportunities to be skipped N is N = 1, it is decided to apply the flag instruction only to the first opportunity that has been determined to be skipped. If N > 1, it is decided to apply the flag instruction to the N consecutive opportunities starting from the first opportunity that has been determined to be skipped.

[0101] The first of the N opportunities (measurement gaps, etc.) to be skipped may be the first measurement gap, etc. after the K_offset symbol / slot following the start / end symbol of DCI (or PDSCH / PUSCH scheduled by DCI). Terminal 200 may thus determine the first opportunity (measurement gap, etc.) to be skipped based on DCI.

[0102] K_offset is an offset value, which may be set by RRC, defined by a standard, or notified by DCI.

[0103] Measurement gap opportunities not included in N consecutive measurement gap opportunities are not skipped, and terminal 200 must perform RRM measurements in measurement gap opportunities that are not skipped, and the scheduling restrictions defined in the current standard apply to measurement gap opportunities that are not skipped. In N consecutive measurement gap opportunities, terminal 200 may not perform RRM measurements and may instead receive / transmit DL / UL channels / signals.

[0104] Figure 4 shows an example of notification of skipping measurement gap opportunities based on option 3-1, where DCI notifies that it will skip N consecutive measurement gap opportunities (N=2 in the example shown in Figure 4). In this example, the first and second measurement gap opportunities shown are skipped. Therefore, terminal 200 may decide to skip the first and second measurement gap opportunities shown and receive / transmit DL / UL channels / signals without performing RRM measurements during these measurement gap opportunities.

[0105] (Variations) The K_offset symbol / slot may differ for each SCS and may depend on the capabilities of the UE.

[0106] The K_offset symbol / slot may be determined based on the SCS of the DCI serving cell, based on the minimum value between the SCS of the DCI serving cell and the SCS of the scheduled PDSCH / PUSCH serving cell, or based on the minimum value between the SCS of the configured serving cells (within the same frequency range / band as the DCI cell).

[0107] The K_offset symbol / slot may be counted based on any of the following SCSs: • SCS of the DCI serving cell • SCS of the scheduled PDSCH / PUSCH serving cell (if any) • Explicitly set SCS

[0108] The opportunities to skip (such as specific measurement gaps) may be applied regardless of the measurement gap type / measurement gap ID / serving cell, or they may be applied only to specific measurement gap types / measurement gap IDs / serving cells.

[0109] (Example 3-1-a) The first opportunity to be skipped may be determined regardless of the measurement gap type (e.g., UE, FR1 / FR2), regardless of the measurement gap ID, and regardless of the serving cell in which the RRM measurement and / or SMTC window is set.

[0110] If there are multiple opportunities for measurement gaps / RRM measurements / SMTC windows with the same start symbol / slot across multiple serving cells, the first opportunity is the one set on the serving cell with the smallest serving cell index.

[0111] If there are multiple measurement gaps with the same starting symbol / slot, the opportunity with the smallest measurement gap ID may be considered the first opportunity to be skipped.

[0112] (Example 3-1-b) The first opportunity to skip may be determined by a specific measurement gap type (e.g., UE, FR1 / FR2 each), by a specific measurement gap ID, or by a measurement gap having a specific cell.

[0113] A specific measurement gap type may be set by RRC, set for the corresponding frequency range of the DCI serving cell, defined by a standard, or indicated by DCI.

[0114] A specific measurement gap ID may be set by RRC or indicated by DCI.

[0115] A particular serving cell may be a serving cell that receives a DCI, may be configured by an RRC, or may be indicated by a DCI (for example, by reusing a CIF field).

[0116] (Variations) DCI may include multiple fields corresponding to the measurement gap type, measurement gap ID, and serving cell, respectively.

[0117] For example, the flags in the M fields of DCI could be flags indicating whether to skip the RRM measurement / SMTC window in serving cell #1, flags indicating whether to skip the RRM measurement / SMTC window in serving cell #2, ..., flags indicating whether to skip the RRM measurement / SMTC window in serving cell #M.

[0118] For example, the three field flags of DCI could be flags indicating whether or not to skip the measurement gap for each UE type, a flag indicating whether or not to skip the measurement gap for FR1 type, and a flag indicating whether or not to skip the measurement gap for FR2 type.

[0119] For example, the flags in the M fields of DCI could be flags indicating whether to skip measurement gap ID #1, flags indicating whether to skip measurement gap ID #2, ..., flags indicating whether to skip measurement gap ID #M.

[0120] (Option 3-2) Option 3-2 describes the indication of one or more consecutive opportunities (such as a specific measurement gap) to be skipped (within the time window).

[0121] (Option 3-2-1) The first opportunity to be skipped and / or the number of skipped opportunities may be indicated by DCI. The opportunities to be skipped may be determined based on the following:

[0122] An offset value (e.g., K_offset) representing the offset between the start symbol / slot of a skipped opportunity (such as a measurement gap) and the start / end symbols / slots of the DCI (or PDSCH / PUSCH scheduled by the DCI) may be indicated by the DCI. If K_offset is not specified by the DCI, it may be set by the RRC or defined by the standard.

[0123] The number N of consecutive opportunities to be skipped (e.g., measurement gaps) may be indicated by DCI. If N is not indicated by DCI, it may be set by RRC or defined by the standard.

[0124] (Option 3-2-2) A skipping window may be indicated by DCI. The skipping window may also be called a measurement non-performance period, a period during which no measurements are performed, etc. In this case, all opportunities (measurement gaps, etc.) within the skipping window are skipped. The skipping window may be determined based on the following:

[0125] The DCI may specify an offset (e.g., K_offset) that represents the offset between the start position of the skip window and the start / end symbol / slot of the DCI (or PDSCH / PUSCH scheduled by the DCI). If K_offset is not specified by the DCI, it may be set by the RRC or defined by the standard.

[0126] The length of the skip window (N slots / symbols) may be indicated by DCI. If N is not indicated by DCI, N may be set by RRC or defined by a standard.

[0127] Terminal 200 may determine the starting position and length of the skip window based on DCI.

[0128] Measurement gaps, etc., that are not included in the skip window are not skipped, and terminal 200 is required to perform RRM measurements in measurement gaps, etc. that are not skipped, and the scheduling restrictions defined in the current standard apply to measurement gaps, etc., that are not skipped. In measurement gaps, etc., that are included in the skip window, terminal 200 may not perform RRM measurements and may receive / transmit DL / UL channels / signals.

[0129] Figure 5 shows an example of notification of skipping measurement gap opportunities based on option 3-2-2, where DCI notifies that it will skip measurement gap opportunities included in the skip window. In this example, the first and second measurement gap opportunities shown are skipped. Therefore, terminal 200 may decide to skip the first and second measurement gap opportunities shown and receive / transmit DL / UL channels / signals without performing RRM measurements during these measurement gap opportunities.

[0130] (Variations) The K_offset symbol / slot may differ for each SCS and may depend on the capabilities of the UE.

[0131] The K_offset symbol / slot may be determined based on the SCS of the DCI serving cell, based on the minimum value between the SCS of the DCI serving cell and the SCS of the scheduled PDSCH / PUSCH serving cell, or based on the minimum value between the SCS of the configured serving cells (within the same frequency range / band as the DCI cell).

[0132] The K_offset symbol / slot may be counted based on any of the following SCSs: • SCS of the DCI serving cell • SCS of the scheduled PDSCH / PUSCH serving cell (if any) • Explicitly set SCS

[0133] The opportunities to skip within the skip window (such as specific measurement gaps) may be applied regardless of the measurement gap type / measurement gap ID / serving cell, or they may be applied only to specific measurement gap types / measurement gap IDs / serving cells.

[0134] (Example 3-2-a) The opportunities to be skipped within a skip window may be determined regardless of the measurement gap type (e.g., UE, FR1 / FR2), regardless of the measurement gap ID, and regardless of the serving cell in which the RRM measurement and / or SMTC window is set.

[0135] (Example 3-2-b) The opportunities to be skipped within the skip window may be determined by a specific measurement gap type (e.g., UE, FR1 / FR2 each), by a specific measurement gap ID, or by a measurement gap having a specific cell.

[0136] A specific measurement gap type may be set by RRC, set for the corresponding frequency range of the DCI serving cell, defined by a standard, or indicated by DCI.

[0137] A specific measurement gap ID may be set by RRC or indicated by DCI.

[0138] A particular serving cell may be a serving cell that receives a DCI, may be configured by an RRC, or may be indicated by a DCI (for example, by reusing a CIF field).

[0139] (Variations) DCI may include multiple fields corresponding to the measurement gap type, measurement gap ID, and serving cell, respectively.

[0140] For example, the M fields of DCI may represent the K_offset of the RRM measurement / SMTC window for serving cell #1, the K_offset of the RRM measurement / SMTC window for serving cell #2, ..., and the K_offset of the RRM measurement / SMTC window for serving cell #M.

[0141] For example, the three fields of DCI may represent the K_offset of the measurement gap for each UE type, the K_offset of the measurement gap for the FR1 type, and the K_offset of the measurement gap for the FR2 type.

[0142] For example, the M fields of DCI may represent the K_offset of measurement gap ID #1, the K_offset of measurement gap ID #2, ..., the K_offset of measurement gap ID #M.

[0143] (Option 3-3) Option 3-3 describes a notification of whether to skip or not skip each of N consecutive opportunities (such as a specific measurement gap) (where N is an integer greater than or equal to 1) using a bitmap indicating the skip pattern.

[0144] (Option 3-3-1) The bitmap is shown for N consecutive specific measurement gaps, and each bit indicates whether to skip or not skip the corresponding measurement gap. For example, a bit value of "0" may indicate "not skipped" and a bit value of "1" may indicate "skip", or a bit value of "1" may indicate "not skipped" and a bit value of "0" may indicate "skip".

[0145] For measurement gaps, etc., that are notified as "to be skipped," terminal 200 may not perform RRM measurements during those measurement gaps, the scheduling restrictions defined in the current standard will not apply, and it may receive / transmit DL / UL channels / signals. On the other hand, for measurement gap opportunities that are notified as "not to be skipped," terminal 200 is required to perform RRM measurements during those measurement gap opportunities, and the scheduling restrictions defined in the current standard will apply to measurement gap opportunities that are not skipped.

[0146] The first of the N opportunities (measurement gaps, etc.) indicated by the bitmap may be the first measurement gap, etc. after the K_offset symbol / slot following the start / end symbol of DCI (or PDSCH / PUSCH scheduled by DCI). Terminal 200 may thus determine the first opportunity (measurement gap, etc.) to be skipped based on DCI.

[0147] K_offset is an offset value, which may be set by RRC, defined by a standard, or notified by DCI.

[0148] Furthermore, the value of N may be defined by a standard, set by RRC, or notified by DCI.

[0149] Figure 6 shows an example of notification of skipping a measurement gap opportunity based on option 3-3-1, where DCI notifies a skip pattern for N consecutive measurement gap opportunities (N=4 in the example shown in Figure 6) using a bitmap. In this example, the bitmap (skip pattern) is "0100" (in this example, "0": not skipped, "1": skipped), and the second measurement gap opportunity shown is skipped. Therefore, terminal 200 may decide to skip the second measurement gap opportunity shown and may not perform an RRM measurement during this measurement gap opportunity, instead receiving / transmitting DL / UL channels / signals.

[0150] (Option 3-3-2) Multiple skip patterns (each corresponding to a bitmap, as in Option 3-3-1) may be set by RRC or defined by a standard. The pattern index may also be indicated by DCI.

[0151] A skip pattern (e.g., "0000") to prevent skipping measurement gaps, etc., may be set by RRC or defined by a standard.

[0152] The methods for determining / instructing measurement gaps, etc., to be skipped, as described in Options 3-1 and 3-2, can be applied to determine / instruct specific measurement gaps, etc., in a bitmap application.

[0153] (Variations) DCI may include multiple fields for each field, corresponding to the measurement gap type, measurement gap ID, and serving cell, respectively.

[0154] For example, the M fields of DCI may represent the bitmaps of the RRM measurement / SMTC window of serving cell #1, the RRM measurement / SMTC window of serving cell #2, ..., the RRM measurement / SMTC window of serving cell #M.

[0155] For example, the three fields of DCI may represent bitmaps of measurement gaps for each UE type, bitmaps of measurement gaps for FR1 type, and bitmaps of measurement gaps for FR2 type.

[0156] For example, the M fields of DCI may represent the bitmap for measurement gap ID #1, the bitmap for measurement gap ID #2, ..., the bitmap for measurement gap ID #M.

[0157] (Option 3-4) Option 3-4 describes the case where options 3-1 and 3-2 are combined. Specifically, the DCI includes a 1-bit flag field indicating whether or not to skip measurement gaps, etc., and a field indicating one or more consecutive opportunities (specific measurement gaps, etc.) to be skipped (within the time window).

[0158] Furthermore, if a single-bit flag indicates that measurement gaps, etc., will not be skipped, then there is no / no need for a field to indicate the opportunities for skipping (measurement gaps, etc.).

[0159] (Option 3-5) Option 3-5 describes the case where options 3-1 and 3-3 are combined. Specifically, DCI includes a 1-bit flag field indicating whether or not to skip measurement gaps, etc., and a bitmap field indicating the skip pattern.

[0160] Furthermore, if a single-bit flag indicates that measurement gaps, etc., should not be skipped, then a bitmap field indicating the skip pattern does not exist / is not necessary.

[0161] <Proposal 4: Processing Timeline> The timeline for processing that skips specific measurement gaps, etc., is shown below.

[0162] The processing time for DCIs indicating skips such as specific measurement gaps is defined as the minimum time required to process the skip instruction. The skip instruction processing time T_proc_skip may be defined by the standard. Furthermore, the value of T_proc_skip may differ for each SCS and may depend on the capabilities of the UE.

[0163] (Variations) The standard defines a new table containing T_proc_skip values ​​for various SCSs.

[0164] The value of T_proc_skip is the PDSCH processing procedure time, as defined in TS 38.214, section 5.3. proc, 1 It can be smaller or larger.

[0165] The value of T_proc_skip may be smaller or larger than the PUSCH preparation procedure time T as defined in TS 38.214, section 6.4. proc, 2 It may be smaller or larger.

[0166] The value of T_proc_skip may be equal to proc, 1 T skip + d. The value of d skip may be defined by the standard. Also, the value of d skip may vary for each SCS and may depend on the UE's capabilities.

[0167] The value of T_proc_skip may be equal to proc, 2 T skip + dskip. The value of d skip may be defined by the standard. Also, the value of d

[0168] For example, it is not necessary to assume that the terminal 200 detects a DCI indicating that it skips a measurement gap or the like that starts / ends by T_proc_skip after the end symbol / slot of the DCI.

[0169] For example, it is not necessary to assume that the value of K_offset in Proposal 3 is smaller than T_proc_skip.

[0170] <Analysis> In the RAN1#118 meeting, the working assumption was set to support a dynamic indication that indicates the skipping of gaps / restrictions (see Figure 12). One of the issues is the DCI format for indicating the skipping of gaps / restrictions. In the RAN1#118bis meeting, it was discussed whether to support DCI format 0_3 / 1_3 for the indication.

[0171] If DCI format 0_3 / 1_3 is supported for the indication, it is preferable to clarify how to determine the gaps / restrictions skipped by the indication of DCI format 0_3 / 1_3.

[0172] <Summary of Proposals> Proposal 5: Skipping indication field in DCI format 0_3 / 1_3 Proposal 5-1: Only 1 bit field in DCI format 0_3 / 1_3 Proposal 5-2: Separate bit (or separate bit field) in DCI format 0_3 / 1_3 for each scheduled cell Proposal 5-3: Joint-indication of skipping indication in scheduled cells Proposal 6: Determination of minimum time offset

[0173] <Proposal 5> A skipping instruction field is provided within the DCI format 0_3 / 1_3. The following proposals 5-1 to 5-3 are provided regarding the skipping instruction field within the DCI format 0_3 / 1_3.

[0174] (Proposal 5-1) When DCI format 0_3 / 1_3 for scheduling PUSCH / PDSCH on a set of cells is set for gap / limit skipping instructions, only one bit field of DCI format 0_3 / 1_3 is used to instruct the skipping (see Figure 13). The following options are provided for skipping instructions using one bit field of DCI format 0_3 / 1_3:

[0175] Option 1: The gap / restriction indication field is applied to the scheduling cell (i.e., the DCI cell).

[0176] Option 2: The gap / limit indicator field applies to all scheduled cells (i.e., the set of cells indicated by the “scheduled cell set indicator” field in DCI format 0_3 / 1_3).

[0177] Option 2a (Variation of Option 2): The gap / limit instruction field is applied to the scheduled cell where the (first) scheduled PDSCH / PUSCH is after the minimum time offset (applied for skip instruction, as agreed in Figure 12).

[0178] Option 3: The gap / limit instruction field is applied to one of the scheduled cells. Options 3-1 to 3-3 below are provided for determining "one of the scheduled cells".

[0179] Option 3-1: The cell with the smallest / largest cell index among the scheduled cells.

[0180] Option 3-2: The cell with the minimum / maximum SCS among the scheduled cells. If there are multiple cells with the same minimum / maximum SCS, the cell with the minimum / maximum cell index is determined.

[0181] Option 3-3: Scheduled cells with the minimum / maximum carrier frequency.

[0182] Option 3a (Variation of Option 3): The gap / limit instruction field is applied to one of the scheduled cells where the (first) scheduled PDSCH / PUSCH is after the minimum time offset.

[0183] Regarding the determination of "one of the scheduled cells where the (first) scheduled PDSCH / PUSCH is after the minimum time offset," options 3-1 / 3-2 / 3-3 are reused by replacing "scheduled cell" with "the scheduled cell where the (first) scheduled PDSCH / PUSCH is after the minimum time offset."

[0184] Option 4: The gap / limit instruction field is applied to one of the scheduling cell and one of the scheduled cells. Options 4-1 to 4-3 below are provided for determining "one of the scheduling cell and one of the scheduled cells".

[0185] Option 4-1: The cell with the minimum / maximum cell index among the scheduling cell and the scheduled cell.

[0186] ...Option 4-2 The cell with the minimum / maximum SCS among scheduling cells and scheduled cells. If there are multiple cells with the same minimum / maximum SCS, the cell with the minimum / maximum cell index is determined.

[0187] ...Option 4-3 The cell with the minimum / maximum carrier frequency among scheduling cells and scheduled cells.

[0188] Option 4a (Variation of Option 4): The gap / limit instruction field is applied to one of the scheduled cells and the (first) scheduled PDSCH / PUSCH after the minimum time offset.

[0189] Regarding the determination of "one of the scheduling cells and scheduled cells where the (first) scheduled PDSCH / PUSCH is after the minimum time offset," options 4-1 / 4-2 / 4-3 are reused by replacing "scheduled cell" with "the scheduled cell where the (first) scheduled PDSCH / PUSCH is after the minimum time offset."

[0190] Option 5: The gap / limit instruction field applies to the scheduling cell and all scheduled cells.

[0191] Option 5a (Variation of Option 5): The gap / limit instruction field is applied to the scheduling cell and the scheduled cell where the (first) scheduled PDSCH / PUSCH is after the minimum time offset.

[0192] Option 6: The Gap / Limit Display field applies to the scheduling cell and one of the scheduled cells. Option 3 is referenced for determining "one of the scheduled cells".

[0193] Option 6 (Variation of Option 6): The gap / limit instruction field is applied to the scheduling cell and one scheduled cell after the minimum time offset of the (first) scheduled PDSCH / PUSCH. Option 3 is referenced for determining "one of the scheduled cells".

[0194] (Proposal 5-2) When DCI format 0_3 / 1_3 for scheduling PUSCH / PDSCH on a set of cells is set for gap / limit skipping instructions, individual bits (or individual bit fields) of DCI format 0_3 / 1_3 are used to indicate the skipping instruction for each scheduled cell (see Figure 14).

[0195] The number of bits in the skip instruction field (or the number of skip instruction fields) is the same as the number of scheduled cells.

[0196] Each bit is associated with a co-scheduled cell in ascending / descending order of the CC idx.

[0197] (Proposal 5-3) If DCI format 0_3 / 1_3 is set for gap / limit skipping instructions to schedule PUSCH / PDSCH on a set of cells, the skipping field of DCI format 0_3 / 1_3 indicates joint instructions for skipping instructions on the scheduled cells (see Figure 15).

[0198] The skipping field indicates the row index, and each row contains a separate bit instruction for each scheduled cell.

[0199] Each bit is associated with a co-scheduled cell in ascending / descending order of the CC idx.

[0200] <Proposal 6> If the UE determines that a gap / limit indication in DCI format 0_3 / 1_3 is applied to a particular cell, the indicated gap / limit is determined as the first gap / limit on / to the cell with the minimum time offset after DCI (e.g., T_min_offset) (see Figure 16).

[0201] If T_min_offset is in slot / symbol units (i.e., X slots / symbols as time offset), then it is required to clarify the SCS for T_min_offset. The following Alt. is provided for clarifying the SCS for T_min_offset.

[0202] Alt.1 T_min_offset is determined based on the SCS of the corresponding application cell. For example, if a skipping instruction is applied to cell #1, the SCS of cell #1 is applied.

[0203] Alt.2 T_min_offset is determined based on the SCS of the scheduling cell.

[0204] Alt.3 T_min_offset is determined based on the minimum / maximum SCS of the scheduled cell.

[0205] Alt.4 T_min_offset is determined based on the minimum / maximum SCS of the scheduling cell and the scheduled cell.

[0206] Alt.5 T_min_offset is determined based on the minimum / maximum SCS of the configured / activated serving cells within the scheduled cell's frequency range. For example, if the scheduled cell is in FR1, the minimum / maximum SCS of the FR1 cell is applied.

[0207] Alt.6 T_min_offset is determined based on the minimum / maximum SCS of the scheduling cell and the (configured / activated) serving cells within the frequency range of the scheduled cell.

[0208] Alt.7 T_min_offset is determined based on the minimum / maximum SCS among all configured / activated serving cells.

[0209] Alt.8 T_min_offset is determined based on the SCS of the reference cell (set by gNB for multi-cell scheduling).

[0210] <Summary of Proposals 5 and 6> In skipping instructions using DCI format 0_3 / 1_3, gaps / limits can be appropriately determined.

[0211] <Variations> Whether to apply proposals 5-1 / 5-2 / 5-3 may be defined by the specification or set by gNB.

[0212] <Terminology> A scheduling cell can be thought of as a cell that controls data transfer, such as managing data transfer and allocating resources. A scheduled cell can be thought of as a cell where data transfer takes place. For example, resource allocation (scheduling) is performed in the scheduling cell, and data transfer is performed in the scheduled cell using the allocated resources. A co-scheduled cell can be thought of as a scenario in which multiple cells (base stations) are scheduled to operate in coordination simultaneously.

[0213] DCI format 0_3 can be considered as DCI in PUSCH's multi-carrier scheduling. DCI format 1_3 can be considered as DCI in PDSCH's multi-carrier scheduling. DCI formats 0_3 / 1_3 can be simultaneously scheduled for combinations of cells included in the set of cells to be scheduled.

[0214] <Example of Operation> Next, an example of the operation of terminal 200 will be explained with reference to Figure 7.

[0215] In step S21, terminal 200 receives first information from base station 100 regarding an extended period for measurement using a measurement signal. For example, the first information may be an existing measurement gap configuration information element (e.g., MeasGapConfig IE) which is an RRC parameter, or a new information element similar to that information element.

[0216] In step S22, the terminal 200 periodically sets an extended period for measurement using the measurement signal based on the received first information.

[0217] In step S23, terminal 200 receives second information from base station 100 that dynamically indicates that measurements will not be performed during a periodic extended period.

[0218] In step S24, the terminal 200, based on the received second information, does not perform measurements during a portion of the periodic extended period, but instead receives or transmits signals to and from the base station.

[0219] (Effects) According to the above proposal, specific measurement gaps (opportunities) can be skipped based on dynamic notifications from DCI, thereby reducing the impact caused by scheduling limitations related to measurements.

[0220] <UE capability> The UE capability, which indicates the capabilities of the terminal, may include the following information indicating the capabilities of the terminal. Terminal 200 may report the following information indicating the capabilities of the terminal to base station 100. Note that the information indicating the capabilities of the terminal may correspond to information defining the capabilities of the terminal.

[0221] - Information defining whether the terminal supports dynamic instruction for skipping measurement gap / RRM measurement / SMTC window using DCI - Information defining whether the terminal supports dynamic instruction for skipping measurement gap / RRM measurement / SMTC window using a new DCI format - Information defining whether the terminal supports dynamic instruction for skipping measurement gap / RRM measurement / SMTC window using a new RNTI - Information defining whether the terminal supports dynamic instruction for skipping measurement gap / RRM measurement / SMTC window using DCI1_1 / 1_2 / 1_3 with scheduling PDSCH Information and terminals that define whether to support dynamic instruction for skipping the SMTC window, Information and terminals that define whether to support dynamic instruction for skipping the measurement gap / RRM measurement / SMTC window by DCI0_1 / 0_2 / 0_3 via PUSCH scheduling, Information and terminals that define whether to support dynamic instruction for skipping the measurement gap / RRM measurement / SMTC window by DCI2_1 with DL preemption instruction, Measurement gap / RRM measurement / SMTC by DCI2_4 with UL cancellation instruction Information / terminals that define whether to support dynamic instruction for skipping C windows, information / terminals that define whether to support dynamic instruction for skipping measurement gap / RRM measurement / SMTC windows by DCI1_1 / 1_2 / 1_3 without scheduling PDSCH, information / terminals that define whether to support dynamic instruction for skipping measurement gap / RRM measurement / SMTC windows by DCI0_1 / 0_2 / 0_3 without scheduling PUSCH, measurement gap / RRM measurement by DCI2_1 without DL preemption instruction Information and terminals that define whether to support dynamic instruction for skipping RM measurement / SMTC windows, information and terminals that define whether to support dynamic instruction for skipping measurement gaps / RM measurement / SMTC windows by DCI2_4 without UL cancellation instruction, information and terminals that define whether to support dynamic instruction for skipping multiple measurement gaps / RM measurement / SMTC windows, and some or all of the following information that defines whether to support dynamic instruction for skipping discontinuous measurement gaps / RM measurement / SMTC windows (for example,New UE capabilities and reporting signaling (and RRC settings) may be defined for each UE / FR / FC. This includes: information defining whether the terminal supports dynamic display of skipping MG / RRM measurements / SMTC opportunities using DCI format 0_3; and information defining whether the terminal supports dynamic display of skipping MG / RRM measurements / SMTC opportunities using DCI format 1_3.

[0222] In addition, the above describes an example in which notifications and requests (such as skip patterns) are exchanged between the base station 100 and the terminal 200 to skip the measurement gap / RRM measurement / SMTC window (opportunity). However, notifications and requests (such as skip patterns) to not skip the measurement gap / RRM measurement / SMTC window (opportunity) may also be exchanged.

[0223] Next, the configuration of the base station 100 and terminal 200 will be described. Note that the configuration of the base station 100 and terminal 200 described below is an example of the functions related to this embodiment. The base station 100 and terminal 200 may have functions not shown. Furthermore, the function classification and / or the name of the function unit are not limited as long as the function performs the operation according to this embodiment.

[0224] <Base Station Configuration> Figure 8 is a block diagram showing an example of the configuration of a base station 100 according to this embodiment. The base station 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 100 communicates with a terminal 200 (see Figure 9) wirelessly.

[0225] The transmitting unit 101 transmits downlink (DL) signals to the terminal 200. For example, the transmitting unit 101 transmits DL signals (e.g., RRC, SIB, MAC CE, DCI, notification, confirmation, etc. as described above) under the control of the control unit 103.

[0226] The DL signal may include, for example, data signals for the downlink and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission by terminal 200 (e.g., UL grant). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include a reference signal.

[0227] The channels used to transmit DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, base station 100 transmits downlink control information to terminal 200 using the PDCCH and transmits downlink data signals using the PDSCH.

[0228] The reference signals included in the DL signal may include, for example, at least one of the following: Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS). For example, reference signals such as DMRS and PTRS are used for demodulating the downlink data signal and are transmitted using PDSCH.

[0229] The receiving unit 102 receives uplink (UL) signals transmitted from the terminal 200. For example, the receiving unit 102 receives UL signals (e.g., the requests and notifications mentioned above) under the control of the control unit 103.

[0230] The transmitting unit 101 and the receiving unit 102 may together be referred to as the communication unit.

[0231] The control unit 103 controls the communication operations of the base station 100, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102.

[0232] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101. The control unit 103 also outputs the data and control information received from the receiving unit 102 to the upper layer.

[0233] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals received from the terminal 200 (e.g., data and control information, etc.) and / or data and control information, etc. acquired from higher layers. Information regarding the allocated resources may be included in the control information transmitted to the terminal 200.

[0234] <Terminal Configuration> Figure 9 is a block diagram showing an example of the configuration of a terminal 200 according to this embodiment. The terminal 200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The terminal 200 communicates with, for example, a base station 100 wirelessly.

[0235] In relation to the above proposal, for example, the receiving unit 201 may receive first information (RRC, etc.) from the base station 100 regarding an extended period (measurement gap opportunity, etc.) for measurement using a measurement signal (SSB, etc.) (SSB measurement, etc.). For example, the receiving unit 201 may receive second information (RRC, SIB, MAC CE, DCI, etc.) from the base station 100 indicating that measurement will not be performed during a portion of the periodic extended period. For example, after receiving the second information, the receiving unit 201 may receive information (MAC CE, DCI, etc.) from the base station 100 indicating that measurement will be performed during another portion of the periodic extended period. The receiving unit 201 may receive a signal from the base station 100 during a portion of the periodic extended period.

[0236] The transmitting unit 202 transmits the UL signal to the base station 100. For example, the transmitting unit 202 transmits the UL signal (e.g., the request, notification, etc. mentioned above) under the control of the control unit 203.

[0237] In relation to the above proposal, for example, the transmitting unit 202 may transmit a signal to the base station 100 during a periodic extended period (such as a measurement gap opportunity) for measurement using a measurement signal (such as SSB) (such as SSB measurement).

[0238] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of terminal 200 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

[0239] The channels used to transmit UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes PUCCH (Physical Uplink Control Channel). For example, terminal 200 transmits uplink control information to base station 100 using PUCCH and transmits uplink data signals using PUSCH.

[0240] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (e.g., PUSCH).

[0241] The receiving unit 201 and the transmitting unit 202 may together be referred to as the communication unit.

[0242] The control unit 203 controls the communication operation of the terminal 200, including the receiving process in the receiving unit 201 and the transmission process in the transmitting unit 202.

[0243] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.

[0244] For example, the control unit 203 controls the transmission of information to be fed back to the base station 100. The information to be fed back to the base station 100 may include, for example, a HARQ-ACK, Channel State Information (CSI), or a Scheduling Request (SR). The information to be fed back to the base station 100 may be included in the UCI.

[0245] In relation to the above proposal, for example, the control unit 203 may periodically set an extended period (measurement gap opportunity, etc.) for measurement using a measurement signal (SSB, etc.) (SSB measurement, etc.) based on the first information. For example, the control unit 203 may determine a portion of the periodic extended period in which no measurement is performed based on the second information, and may choose not to perform a measurement during the determined portion of the periodic extended period.

[0246] The channels used for transmitting DL signals and UL signals are not limited to the examples described above. For example, the channels used for transmitting DL signals and UL signals may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). RACH may be used, for example, to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI).

[0247] With the above configuration, the impact caused by scheduling limitations related to measurements can be reduced.

[0248] <Summary of Embodiments> As described above, according to one aspect of the present disclosure, a terminal is provided comprising: a communication unit that receives or transmits signals; and a control unit that performs measurements during a measurement period, wherein the control unit determines whether or not to skip the measurement during a specific measurement period based on the field of downlink control information received by the communication unit.

[0249] With the above configuration, based on the downlink control information field, it is possible to perform signal reception or transmission without performing measurements during a specific measurement period, thereby reducing the impact caused by scheduling limitations related to measurements.

[0250] In one example, the field of the downlink control information is a 1-bit flag field, and the control unit skips the measurement during the specific measurement period if the flag field has a specific value.

[0251] In one example, the downlink control information indicates a skip window, and the control unit skips the measurement during all measurement periods within the skip window.

[0252] In one example, the downlink control information indicates a skip pattern using a bitmap, and the control unit skips the measurement during the measurement period corresponding to a bit having a specific value in the bitmap.

[0253] According to one aspect of the present disclosure, a communication method is provided in which a terminal sets a measurement period, determines whether to skip the measurement during a specific measurement period based on a field of downlink control information, and, if the measurement is to be skipped, receives or transmits a signal during that period.

[0254] With the above configuration, based on the downlink control information field, it is possible to perform signal reception or transmission without performing measurements during a specific measurement period, thereby reducing the impact caused by scheduling limitations related to measurements.

[0255] <Hardware Configuration, etc.> The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0256] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0257] For example, a base station, terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the communication method of the present disclosure. Figure 10 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The base station 100 and terminal 200 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0258] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 100 and terminal 200 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0259] Each function in the base station 100 and terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0260] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may be implemented by the processor 1001.

[0261] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 203 of the terminal 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0262] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0263] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including at least one of the memory 1002 and the storage 1003.

[0264] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 may be implemented by the communication device 1004.

[0265] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0266] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0267] Furthermore, the base station 100 and terminal 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0268] (Supplement to Embodiments) While embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, base stations and terminals have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. Software operated by a processor in a base station according to embodiments of this disclosure, and software operated by a processor in a terminal according to embodiments of this disclosure, may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0269] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0270] <Applicable Systems> The embodiments described in this disclosure include LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0271] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, as long as there is no contradiction. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0272] <Base Station Operation> The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides the base station, but it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0273] <Direction of Input / Output> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes.

[0274] <Handling of Input / Output Information, etc.> Input and output information, etc. may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, etc. may be overwritten, updated, or appended to. Output information, etc. may be deleted. Input information, etc. may be transmitted to other devices.

[0275] <Determination Method> The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0276] <Variations of Embodiments, etc.> Each embodiment / appearance described in this disclosure may be used individually, in combination, or switched between during implementation. Furthermore, notification of predetermined information (for example, notification that "it is X") is not limited to explicit notification, but may also be implicit (for example, by not providing notification of the predetermined information).

[0277] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure may be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Accordingly, the descriptions in the present disclosure are for illustrative purposes only and are not intended to be restrictive in any way.

[0278] <Software> Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0279] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0280] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0281] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0282] <Systems and Networks> The terms “systems” and “networks” as used in this disclosure are interchangeable.

[0283] <Parameters, Channel Names> Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0284] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0285] <Base Station> In this disclosure, terms such as "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", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0286] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0287] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0288] <Mobile Station> In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" may be used interchangeably.

[0289] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0290] <Base Station / Mobile Station> At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of a base station and a mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes cases where the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0291] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the embodiments of this disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminal may have the functions that the base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0292] Similarly, the term "terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the terminal described above.

[0293] Figure 11 shows an example of the configuration of vehicle 2001. As shown in Figure 11, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0294] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0295] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0296] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0297] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0298] The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to the outside (e.g., displays, speakers, LED lamps, touch panels, etc.).

[0299] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0300] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029 provided in the vehicle 2001.

[0301] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0302] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

[0303] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0304] <Meaning and Interpretation of Terms> As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having "judgmented" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having "judgmented" or "decided" about some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0305] The terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0306] <Reference Signal> The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0307] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on".

[0308] <"First", "Second"> Any reference to elements using the designations "first", "second", etc. as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to first and second elements do not imply that only two elements may be adopted, or that the first element must precede the second element in any way.

[0309] <Means> The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0310] <Open Format> Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

[0311] <Time units such as TTI, frequency units such as RB, and wireless frame configuration> A wireless frame may consist of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0312] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0313] A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology.

[0314] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

[0315] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0316] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0317] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0318] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0319] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0320] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0321] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0322] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0323] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0324] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0325] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0326] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0327] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0328] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0329] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0330] <Maximum Transmit Power> The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0331] <Articles> In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may also include the fact that the noun following these articles is plural.

[0332] <"Different"> In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0333] This patent application claims priority based on Japanese Patent Application No. 2024-181217, filed on 16 October 2024, and the entire contents of Japanese Patent Application No. 2024-181217 are incorporated herein by reference.

[0334] One aspect of this disclosure is useful for wireless communication systems.

[0335] 10 Wireless communication system 20 NG-RAN 100 Base station (gNB) 200 Terminal (UE) 101, 202 Transmitting unit 102, 201 Receiving unit 103, 203 Control unit

Claims

1. A terminal comprising: a communication unit that receives or transmits signals; and a control unit that performs measurements during a measurement period, wherein the control unit determines whether or not to skip the measurement during a specific measurement period based on a field of downlink control information that schedules uplink and / or downlink signals on a set of cells, received by the communication unit.

2. The terminal according to claim 1, wherein the field of the downlink control information is a 1-bit field, and the control unit skips the measurement in the specific measurement period in the scheduling cell if the field is a specific value.

3. The terminal according to claim 1, wherein the field of the downlink control information is a multi-bit field corresponding to a plurality of cells, and the control unit skips the measurement of the cell corresponding to the certain bit during the specific measurement period if a certain bit of the field is a specific value.

4. The terminal according to claim 1, wherein the field of the downlink control information includes a row index of information relating a row index to a skipping instruction on a scheduled cell, and the control unit skips the measurement during the specific measurement period on the scheduled cell corresponding to the row index included in the field.

5. The terminal according to claim 1, wherein the control unit skips the measurement during the specific measurement period after a minimum time offset following the downlink control information.

6. A communication method in which a terminal sets a measurement period and determines whether to skip a measurement during a particular measurement period based on a field of downlink control information that schedules uplink and / or downlink signals on a set of cells.

Images