Terminal and communication method
The proposed terminal and communication method dynamically skip measurement gaps or SMTC windows using DCI notifications to address scheduling restrictions caused by XR traffic, improving system capacity and efficiency.
Patent Information
- Application Number
- JP2024201191
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-11-18
- Publication Date
- 2025-10-15
AI Technical Summary
Current wireless communication systems face issues with scheduling restrictions due to overlapping SMTC windows or measurement gaps with XR traffic, leading to capacity loss and measurement disruptions.
A terminal and communication method that dynamically skips specific measurement gaps or SMTC windows based on DCI notifications, allowing flexible scheduling to accommodate XR traffic without disrupting measurements.
Reduces the impact of scheduling restrictions on measurements, enhancing system capacity and efficiency by enabling dynamic adjustment of measurement periods.
Smart Images

Figure 2025157101000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a terminal and a communication method. [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has developed specifications for the 5th generation mobile communication system (also known as 5G, New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution or 6G.
[0003] For 5G, technologies that satisfy the requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).
[0004] The expansion of mobile communication systems as described above is expected to lead to the use and spread 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). 3GPP is currently discussing XR expansion in preparation for Release 19 (see, for example, Non-Patent Document 2).
[0005] In relation to XR extensions, for example, extensions regarding Measurement Gap (MG) and scheduling restrictions have been widely discussed.
[0006] For example, it may be within the scope of future standards to specify extensions to the scheduling restrictions for inter-frequency RRM measurements in FR1 and FR2 with measurement gaps and intra-frequency RRM measurements in FR2 without measurement gaps to reduce the impact on capacity and on individual terminals. [Prior art documents] [Non-patent literature]
[0007] [Non-Patent Document 1] 3GPP TS 38.300 V17.6.0 (2023-09) [Non-patent document 2] “Moderator's summary for REL-19 RAN2 topic Enhancements for XR”, RP-232619, 3GPP TSG-RAN Meeting #101, 3GPP, September 2023 Summary of the Invention
[0008] In current wireless communication systems, measurements using synchronization signal blocks (SSBs) (SSB-based measurements) are used.
[0009] For SSB measurements, the terminal is notified of the measurement timing configuration (SMTC: SSB-based Measurement Timing Configuration), and the terminal performs measurements based on the signal to be measured within the configured SMTC window. Also, for SSB measurements, the terminal may be notified of the measurement gap configuration for switching the used frequency (RF: Radio Frequency), etc.
[0010] Due to the periodicity of XR traffic, if the SMTC window or measurement gap overlaps with the transmission and reception of signals related to XR traffic, the signals cannot be scheduled, which can lead to problems due to scheduling restrictions associated with measurements, such as capacity loss.
[0011] In addition, in current wireless communication systems, other measurements such as measurements using a Channel State Information Reference Signal (CSI-RS) (CSI-RS measurement: CSI-RS based measurement) are also used, and the above-mentioned problems may occur in various measurements. Furthermore, the above-mentioned problems may also occur in transmission and reception of signals other than signals related to XR traffic.
[0012] One aspect of the present disclosure provides a terminal and a communication method that can reduce the impact caused by scheduling restrictions on measurements.
[0013] A terminal according to one embodiment of the present disclosure comprises a communication unit that receives or transmits signals and a control unit that performs measurements during a measurement period, and the control unit determines whether to skip the measurements during a particular measurement period based on a field of downlink control information received by the communication unit that schedules uplink signals and / or downlink signals on a set of cells, and determines which cells in the set of cells to apply the measurement skip to based on the field type of the downlink control information. [Brief explanation of the drawings]
[0014] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an example of a frequency range used in a wireless communication system according to an embodiment of the present disclosure. [Figure 3] 1A to 1C are diagrams illustrating exemplary configurations of radio frames, subframes, and slots used in a radio communication system according to an embodiment of the present disclosure. [Figure 4] FIG. 10 is a diagram illustrating an example of notification of skipping a measurement gap opportunity by DCI according to an embodiment of the present disclosure. [Figure 5] FIG. 10 is a diagram illustrating an example of notification of skipping a measurement gap opportunity by DCI according to an embodiment of the present disclosure. [Figure 6]FIG. 10 is a diagram illustrating an example of notification of skipping a measurement gap opportunity by DCI according to an embodiment of the present disclosure. [Figure 7] FIG. 10 is a diagram illustrating an example of the operation of a terminal according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a block diagram illustrating an example of a configuration of a terminal according to an embodiment of the present disclosure. [Figure 10] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. [Figure 11] 1 is a diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present disclosure. [Figure 12] FIG. 11 is a diagram explaining the RAN1#118 agreement. [Figure 13] FIG. 10 is a diagram illustrating Proposal 5-1. [Figure 14] This is a diagram explaining Proposal 5-2. [Figure 15] This is a diagram explaining Proposal 5-3. [Figure 16] FIG. 10 is a diagram illustrating Proposal 6. [Figure 17] FIG. 1 is a diagram illustrating a Type-1A field. [Figure 18] FIG. 10 is a diagram illustrating a Type-1B field. [Figure 19] FIG. 1 is a diagram illustrating a Type-1C field. [Figure 20] FIG. 10 is a diagram illustrating a Type-2 field. [Figure 21] A diagram showing DCI field classification in DCI formats 0_3 / 1_3. [Figure 22] FIG. 10 is a diagram illustrating the determination of the DCI field / format size in a Type-1A field. [Figure 23] FIG. 10 is a diagram illustrating the determination of the DCI field / format size in a Type-1B field. [Figure 24]FIG. 10 is a diagram illustrating the determination of the DCI field / format size in a Type-2 field. [Figure 25] FIG. 1 is a diagram illustrating a DCI monitor. [Figure 26] FIG. 10 is a diagram illustrating setting 3 for FDRA type 0. [Figure 27] FIG. 10 is a diagram illustrating Proposal 8. [Figure 28] FIG. 10 is a diagram illustrating an example in which skipping is also applied to other serving cells if certain conditions are met. DETAILED DESCRIPTION OF THE INVENTION
[0015] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings.
[0016] (Embodiment) <Wireless communication system> 1 is a diagram illustrating 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 conforming to 5G NR, and includes a Next Generation-Radio Access Network 20 (hereinafter, referred to as NG-RAN 20) and a terminal 200 (hereinafter, also referred to as UE (User Equipment) 200).
[0017] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.
[0018] The NG-RAN 20 includes a base station 100A (hereinafter also referred to as gNB 100A) and a base station 100B (hereinafter also referred to as gNB 100B). When it is not necessary to distinguish between the gNB 100A, the gNB 100B, etc., they are collectively referred to as gNBs or base stations 100. Furthermore, the number of gNBs and UEs is not limited to the example shown in FIG. 1.
[0019] The NG-RAN 20 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 the NG-RAN 20 and 5GC may simply be referred to as a "network." In the following description, the term "gNB" may be replaced with the term "network (NW)."
[0020] As an example, the gNB100A and the gNB100B are base stations conforming to 5G, and perform 5G wireless communication with the UE 200. The gNB100A, the gNB100B, and the UE 200 may support MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, carrier aggregation (CA), which uses a bundle of multiple component carriers (CC), and dual connectivity (DC), which performs communication between the UE and each of two NG-RAN nodes.
[0021] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FR). Fig. 2 is a diagram showing an example of FRs used in the wireless communication system 10. As shown in Fig. 2, the wireless communication system 10 may support FR1 and FR2. The frequency bands of each FR are, for example, as follows: FR1: 410MHz~7.125GHz FR2: 24.25GHz~52.6GHz
[0022] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 kHz or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.
[0023] Note that the SCS may be interpreted as a numerology, which is defined in 3GPP TS 38.300 and corresponds to one subcarrier spacing in the frequency domain.
[0024] Furthermore, the wireless communication system 10 may support a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support a frequency band exceeding 52.6 GHz up to 114.25 GHz. For convenience, such a high frequency band may be referred to as "FR2x." When using a frequency band 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] Fig. 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in Fig. 3, one slot is made up 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 Fig. 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 may be 28 or 56 symbols, etc.) Furthermore, the number of slots per subframe may differ depending on the SCS.
[0027] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.
[0028] The gNB100 transmits control information, configuration information, etc. to the UE200 as a downlink (DL) signal.
[0029] Also, for example, gNB100 receives control information, data signals, information regarding the processing capabilities of UE200 (terminal capabilities (information); for example, UE capability), etc. from UE200 as uplink (UL) signals.
[0030] Channels used for transmitting DL signals include, for example, data channels and control channels. 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, the gNB 100 transmits control information to the UE 200 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel, and the PDCCH is an example of a downlink control channel. Note that the PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.
[0031] The reference signal included in the DL signal may include, for example, at least one of a DMRS (Demodulation Reference Signal), a PTRS (Phase Tracking Reference Signal), a CSI-RS (Channel State Information - Reference Signal), an SRS (Sounding Reference Signal), and a PRS (Positioning Reference Signal) for positioning information. For example, reference signals such as the DMRS and PTRS are used to demodulate DL data signals and are transmitted using the PDSCH.
[0032] The UE 200 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable device, or an M2M (Machine-to-Machine) communication module.
[0033] The UE 200 receives control signals or data signals from the gNB 100 via DL and transmits control signals or data signals to the gNB 100 via UL, thereby utilizing various communication services provided by the wireless communication system 10. The UE 200 also receives various reference signals transmitted from the gNB 100 and measures the propagation path quality based on the reception results of the reference signals.
[0034] For example, UE200 receives control information, configuration information, etc. from gNB100 as a DL signal.
[0035] Also, for example, UE200 transmits control information, data signals, terminal capability information of UE200, etc. to gNB100 as UL signals.
[0036] The channels used for UL signal transmission include, for example, data channels and control channels. For example, the data channels may include a Physical Uplink Shared Channel (PUSCH), and the control channels may include a Physical Uplink Control Channel (PUCCH). For example, UE200 transmits control information using PUCCH and 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 rewritten with 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 position information. For example, reference signals such as DMRS and PTRS are used for demodulation of UL data signals and are transmitted using PUSCH.
[0038] <Discussion situation regarding XR> XR presents attractive use cases for future wireless communication systems. On the other hand, XR also poses issues that need to be studied and addressed. One of them is that in 3GPP, discussions on XR enhancements for Release 19 are underway (see, for example, Non-Patent Document 2), and extensive discussions are being held on enhancements regarding measurement gaps and scheduling limitations.
[0039] <RAN1#118 agreement items> When Alt.1 of the RAN1#117 agreement is supported, it was agreed that the minimum time offset X between the skip indication 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> Some signals and / or channels transmitted from a base station to a terminal are periodically transmitted, and examples of such signals and / or channels include Synchronization Signal Blocks (SSBs).
[0041] The SSB is used by a terminal to measure, for example, 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)) (SSB measurement). This measurement is an example of RRM (Radio Resource Management) measurement.
[0042] For SSB measurements, the measurement timing configuration (SMTC) is notified to the terminal. The 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 configured SMTC window.
[0043] Furthermore, for SSB measurements, measurement gap settings may be notified to the terminal when switching the operating frequency (RF: Radio Frequency). A measurement gap is an extended period for measurements in which additional periods may be added before and after the SMTC window. The measurement gap settings may also include the length, period, etc.
[0044] Examples of RRM measurements also include measurements based on CSI-RS (CSI-RS measurements).
[0045] In NR, the following RRM measurements are utilized, including SSB measurements and CSI-RS measurements, with or without measurement gaps: (1) Co-frequency measurement or Intra-frequency measurement (2) Hetero-frequency measurement or Inter-frequency measurement
[0046] The terminal can perform the above-mentioned RRM measurements and signal transmission and reception using at least one of the first frequency band (FR1) and the second frequency band (FR2) (carrier frequency).
[0047] <Scheduling restrictions regarding RRM measurements> Regarding intra-frequency SSB measurements, the scheduling restrictions (terminal operation restrictions) regarding intra-frequency SSB measurements without measurement gaps, intra-frequency SSB measurements with NCSG (Network Configured Small Gap), and intra-frequency SSB measurements with measurement gaps are described in the following locations in the current standard. Intra-frequency SSB measurements without measurement gaps: TS 38.133 clause 9.2.5.3 (Briefly stated, scheduling restrictions are imposed on the SSB symbols measured within the SMTC window or all symbols within the SMTC window when the conditions are met) Intra-frequency SSB measurements with NCSG: TS 38.133 clause 9.2.5.3 Intra-frequency SSB measurements with measurement gaps: TS 38.133 clause 9.1.2
[0048] Regarding inter-frequency SSB measurements, the scheduling restrictions (terminal operation restrictions) regarding inter-frequency SSB measurements without measurement gaps, inter-frequency SSB measurements with NCSG, and inter-frequency SSB measurements with measurement gaps are described in the following locations in the current standard. Inter-frequency SSB measurements without measurement gaps: TS 38.133 clause 9.3.5.3 (in brief, scheduling restrictions are imposed on SSB symbols measured within the SMTC window or on all symbols within the SMTC window if the condition is met) Inter-frequency SSB measurements with NCSG: TS 38.133 clause 9.2.10.3 (briefly, a scheduling restriction is imposed on the union of SSB symbols measured within the SMTC window for all Measurement Occasions (MOs) or the union of all symbols within the SMTC window for all MOs, if the condition is met). Inter-frequency SSB measurements with measurement gaps: TS 38.133 clause 9.1.2
[0049] Regarding intra-frequency CSI-RS measurements, scheduling restrictions (terminal operation restrictions) regarding intra-frequency CSI-RS measurements without measurement gaps are described in the following sections of the current standard. Intra-frequency CSI-RS measurements without measurement gaps: TS 38.133 clause 9.10.2.6 (in brief, scheduling restrictions are imposed on configured CSI-RS symbols if the condition is met)
[0050] Regarding inter-frequency CSI-RS measurements, scheduling restrictions (terminal operation restrictions) regarding inter-frequency CSI-RS measurements with measurement gaps are described in the following sections of the current standard. Inter-frequency CSI-RS measurements with measurement gaps: TS 38.133 clause 9.1.2
[0051] Due to the periodicity of XR traffic, if the SMTC window or measurement gap overlaps with the transmission and reception of signals related to XR traffic, the signals cannot be scheduled, which can lead to problems due to scheduling restrictions associated with measurements, such as capacity loss.
[0052] Incidentally, the terminal may perform measurements for radio link monitoring, measurements for L1-RSRP, measurements for beam obstruction detection, and the like.
[0053] The above-mentioned problems may occur in CSI-RS measurements and various other measurements including these measurements. The above-mentioned problems may also occur in transmission and reception of signals other than signals related to XR traffic.
[0054] Currently, extensions to scheduling constraints are being considered, but specific operations related to control to realize such extensions have not been fully considered.
[0055] Therefore, the following describes a proposal for reducing the influence caused by the scheduling restrictions on measurements (a proposal for relaxing the scheduling restrictions on measurements).
[0056] More specifically, a proposal is described regarding support for dynamic notification by DCI to skip (or disable) certain measurement gaps / RRM measurements / SMTC windows.
[0057] The following proposal will be explained assuming that the measurement gap is periodic. For example, the measurement gap (configuration) may be configured by an existing measurement gap configuration information element (e.g., MeasGapConfig IE), which is an RRC parameter, or a (new) information element similar to the existing information element, and the period of the measurement gap may be configured in such an information element.
[0058] Also, the following suggestions are applicable to intra-frequency SSB and / or CSI-RS measurements and / or inter-frequency SSB and / or CSI-RS measurements with measurement gaps / RRM measurements / SMTC windows.
[0059] In the following proposal, the skipping of measurement gaps / RRM measurements / SMTC windows is notified by DCI. The operation of terminal 200 regarding skipping measurement gaps / RRM measurements / SMTC windows may be based on the notification by base station 100.
[0060] For example, when terminal 200 is notified by base station 100 that a measurement gap / RRM measurement / SMTC window will be skipped, terminal 200 may receive / transmit DL / UL channels / signals without performing RRM measurements (and / or Positioning Reference Signal (PRS) measurements) in the measurement gap / RRM measurement / SMTC window.
[0061] The items described in the following proposals may be combined as appropriate as long as no contradictions arise.
[0062] In this application, the notation " / " may mean "and / or" unless otherwise specified.
[0063] In addition, in this application, the expression "not receiving / transmitting" may be interpreted as "not assuming reception / transmission," "reception / transmission is disabled," "reception / transmission is not performed," "reception / transmission is restricted," "reception / transmission is assumed to be disabled," etc.
[0064] Furthermore, in this application, the expression "deactivate" may be read as "disable," "turn off," "put into an inactive (or disabled) state (disabled state, off state)," etc., and "enable" may be read as "enable," "turn on," "put into an active (or disabled) state (disabled state, off state)," etc.
[0065] In addition, in this application, the expression "notification" may be read as the expression "instruction."
[0066] In addition, in this application, signals such as SSB and CSI-RS used to measure received power, received quality, etc. may be referred to as measurement signals, measurement signals, etc.
[0067] In addition, in this application, "skipping ~" may be interpreted as "not performing measurements (e.g., RRM measurements) on ~" or "assuming that scheduling restrictions do not apply on ~ (do not assume that scheduling restrictions apply)," etc.
[0068] In addition, in this application, "measurement gap opportunity," "RRM measurement opportunity," and "SMTC window opportunity" may be abbreviated to "measurement gap," "RRM measurement," and "SMTC window," respectively. Also, "measurement gap / RRM measurement / SMTC window" may be abbreviated to "measurement gap, etc."
[0069] In this application, a measurement gap or the like (opportunity) may also be referred to as an extended period or interval for measurement.
[0070] <Proposal> The following describes a proposal for supporting dynamic notification by DCI to skip specific measurement gaps / RRM measurements / SMTC windows. Note that dynamic notification by DCI may also be referred to as information indicating that measurements will not be performed (during part of the periodic extended period for measurements), etc.
[0071] Terminal 200 may be notified of skipping of measurement gaps, etc. by receiving dynamic notification by the DCI from base station 100, and may determine which measurement gaps, etc. to skip and which measurement gaps, etc. not to skip based on the DCI. Dynamic notification by DCI may comply with Proposal 1 to Proposal 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 particular measurement gap / RRM measurement / SMTC window is to be skipped.
[0073] A 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 measurement / inter-frequency measurement, a measurement gap whose gap length is a specific value or within a specific value range, a measurement gap for a specific ID, a measurement gap with a repetition period (provided by mgrp) that is a specific value or within a specific value range, etc.
[0074] Furthermore, the specific RRM measurement may be, for example, an RRM measurement with / without a measurement gap, an SSB-based / CSI-RS-based RRM measurement, an intra-frequency / inter-frequency RRM measurement, an RRM measurement of a specific ID (measObjectId, etc.), etc.
[0075] (Option 1-1: New DCI format) To indicate skipping of a particular measurement gap, etc., a new DCI format or an existing DCI format including a CRC scrambled with a new RNTI may be used.
[0076] (Option 1-2: Existing DCI format) To notify skipping of a particular measurement gap, etc., an existing DCI format including a CRC scrambled with an existing RNTI may be used.
[0077] <Proposal 2: DCI field> The DCI field may indicate that certain measurement gaps, etc. will be skipped.
[0078] (Option 2-1) If the DCI is based on a new DCI format or an existing field containing a CRC scrambled with a new RNTI, the DCI format may include a DCI field as described in Proposal 3 below to indicate skipping of certain measurement gaps etc.
[0079] (Option 2-2) If the DCI is in the existing DCI format with a CRC scrambled by the existing RNTI, one of the following sub-options may be used to indicate that a particular measurement gap, etc. will be skipped.
[0080] (Option 2-2-1: New Field) A new field may indicate skipping of a particular measurement gap or the like.
[0081] Whether the new field is present in the DCI format may be configured by the RRC.
[0082] The content of the new fields to indicate skipping of specific measurement gaps etc. is described in Proposal 3 below.
[0083] (Example of new fields) Examples of new fields include: (Example 1): New fields in non-fallback DL grant DCI (e.g. DCI1_1 / 1_2 / 1_3) with (or without) scheduling PDSCH (Example 2): New fields in non-fallback UL grant DCI (e.g. DCI0_1 / 0_2 / 0_3) with or without PUSCH scheduling (Example 3): New fields in DCI format 2_1 with (or without) DL preemption indication (Example 4): New fields in DCI format 2_4 with (or without) UL cancel indication
[0084] (Option 2-2-2: Reinterpreting existing fields) Certain existing fields may be reinterpreted to indicate skips of certain measurement gaps, etc.
[0085] The contents of existing fields to indicate skipping of specific measurement gaps etc. are described in Proposal 3 below.
[0086] (Example of an existing field) Examples of existing fields include: (Example 1): Existing fields in non-fallback DL grant DCI (e.g., DCI1_1 / 1_2 / 1_3) without scheduling PDSCH (Example 2): Existing fields in non-fallback UL grant DCI (e.g., DCI0_1 / 0_2 / 0_3) without scheduling PUSCH (Example 3): Existing fields of DCI2_1 without DL preemption indication (Example 4): Existing field of DCI2_4 without UL cancel instruction
[0087] Whether or not the DCI format can be reinterpreted to indicate the skipping of certain measurement gaps etc. may be enabled / configured by the RRC.
[0088] If enabled / configured, the decision to reinterpret these fields or leave the DCI with its existing interpretation may be based on the value of the particular DCI field.
[0089] For example, if the DCI indicates a specific value for a specific 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 indication to skip a specific measurement gap, etc.
[0090] (Option 2-2-3: New flag field + Option 2-2-1) A new 1-bit flag field (eg, a "skip indication field") and a new field for skip indication may indicate skipping of a particular measurement gap or the like.
[0091] In this case, a flag field (e.g., a "skip indication field") indicates whether the DCI includes an indication to skip a specific measurement gap, etc. If the 1-bit flag has a specific value (e.g., "0" (or "1")), it indicates that a new field (similar to option 2-2-1) for indicating the skipping of a specific measurement gap, etc. is present in the DCI, and if it has any other value (e.g., "1" (or "0")), it indicates that a new field for indicating the skipping of a specific measurement gap, etc. is not present in the DCI.
[0092] Whether a flag field (eg, a "skip indication field") is present in the DCI format may be configured by the RRC.
[0093] (Option 2-2-4: New flag field + Option 2-2-2) A new 1-bit flag field (eg, a "skip indication field") and reinterpretation of existing fields may indicate the skipping of a particular measurement gap, etc.
[0094] In this case, a flag field (e.g., a "skip instruction field") indicates whether the DCI includes an instruction to skip a specific measurement gap, etc. If the 1-bit flag is a specific value (e.g., "0" (or "1")), terminal 200 reinterprets the existing DCI field as an instruction to skip a specific measurement gap, etc. (similar to option 2-2), and if the flag is any other value (e.g., "1" (or "0")), terminal 200 maintains the existing interpretation of the DCI.
[0095] Whether a flag field (eg, a "skip indication field") is present in the DCI format may be configured by the RRC.
[0096] <Proposal 3: DCI field contents> The contents of the DCI fields to indicate the 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 a specific measurement gap, etc. is to be skipped.
[0098] If the 1-bit flag is a specific value (e.g., "0" (or "1")), it indicates that a specific measurement gap, etc. is to be skipped, and if it is any other value (e.g., "1" (or "0")), it indicates that the specific measurement gap, etc. is not to be skipped.
[0099] In this case, the number N (N is an integer equal to or greater than 1) of skipped opportunities (such as measurement gaps) may be configured by the RRC, defined by a standard, or signaled by the DCI.
[0100] When the number N of opportunities to be skipped is N=1, it is determined that the flag instruction is applied only to the first opportunity determined to be skipped, and when N>1, it is determined that the flag instruction is applied to N consecutive opportunities from the first opportunity determined to be skipped.
[0101] The first of the N skipped opportunities (e.g., measurement gaps) may be the first measurement gap K_offset symbols / slots after the start / end symbol of the DCI (or the PDSCH / PUSCH scheduled by the DCI). Terminal 200 may thus determine the first skipped opportunity (e.g., measurement gap) based on the DCI.
[0102] K_offset is an offset value, which may be set by RRC, defined by the standard, or signaled by DCI.
[0103] Measurement gap occasions that are not included in the N consecutive measurement gap occasions are not skipped, and terminal 200 must perform RRM measurements in the non-skipped measurement gap occasions, and scheduling restrictions defined in the current standard apply to non-skipped measurement gap occasions. In the N consecutive measurement gap occasions, terminal 200 may receive / transmit DL / UL channels / signals without performing RRM measurements.
[0104] 4 shows an example of notification of skipping of measurement gap opportunities based on Option 3-1, in which the DCI notifies that N consecutive measurement gap opportunities (N=2 in the example shown in FIG. 4) will be skipped. In this example, the first and second measurement gap opportunities shown in the figure are skipped. Therefore, terminal 200 may decide to skip the first and second measurement gap opportunities shown in the figure, and may receive / transmit DL / UL channels / signals without performing RRM measurements during these measurement gap opportunities.
[0105] (Variation) K_offset symbols / slots may vary per SCS and may depend on the UE capabilities.
[0106] The K_offset symbols / slots may be determined based on the SCS of the serving cell of the DCI, or based on the minimum value between the SCS of the serving cell of the DCI and the SCS of the serving cell of the scheduled PDSCH / PUSCH, or based on the minimum value between the SCSs of the configured serving cells (within the same frequency range / band as the cell of the DCI).
[0107] The K_offset symbols / slots may be counted based on any of the following SCSs: DCI's serving cell's SCS SCS of the serving cell of the scheduled PDSCH / PUSCH (if any) Explicitly configured SCS
[0108] The skipped opportunities (such as specific measurement gaps) may be applied regardless of the measurement gap type / measurement gap ID / serving cell, or may be applied only for 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., per UE, FR1 / FR2), may be determined regardless of the measurement gap ID, and may be determined regardless of the serving cell for which the RRM measurement and / or SMTC window is set.
[0110] If there are multiple measurement gap / RRM measurement / SMTC window opportunities with the same starting symbol / slot on multiple serving cells, the first opportunity is the one configured on the serving cell with the smallest serving cell index.
[0111] Note that if there are multiple measurement gaps with the same starting symbol / slot, the opportunity with the smallest measurement gap ID may be the first opportunity to be skipped.
[0112] (Example 3-1-b) The first opportunity to be skipped may be determined from a specific measurement gap type (e.g., per UE, FR1 / FR2), from a specific measurement gap ID, or from a measurement gap with a specific cell.
[0113] The particular measurement gap type may be configured by the RRC, may be configured for the corresponding frequency range of the serving cell of the DCI, may be defined by the standard, or may be indicated by the DCI.
[0114] The specific measurement gap ID may be configured by the RRC or indicated by the DCI.
[0115] The particular serving cell may be the serving cell that receives the DCI, may be configured by RRC, or may be indicated by the DCI (eg, reusing the CIF field).
[0116] (Variation) The DCI may include multiple fields corresponding to a measurement gap type / measurement gap ID / serving cell, respectively.
[0117] For example, the flags in the M fields of the DCI may be a flag indicating whether to skip the RRM measurement / SMTC window in serving cell #1, a flag indicating whether to skip the RRM measurement / SMTC window in serving cell #2, ..., a flag indicating whether to skip the RRM measurement / SMTC window in serving cell #M.
[0118] For example, the flags in the three fields of the DCI may be a flag indicating whether to skip measurement gaps for each UE type, a flag indicating whether to skip measurement gaps for the FR1 type, and a flag indicating whether to skip measurement gaps for the FR2 type.
[0119] For example, the flags in the M fields of the DCI may be a flag indicating whether to skip measurement gap ID#1, a flag indicating whether to skip measurement gap ID#2, ..., a flag indicating whether to skip measurement gap ID#M.
[0120] (Option 3-2) Option 3-2 describes an indication of one or more consecutive opportunities (eg, a particular measurement gap) to be skipped (within a time window).
[0121] (Option 3-2-1) The first opportunity to be skipped and / or the number of skip opportunities may be indicated by the DCI. The opportunities to be skipped may be determined based on the following:
[0122] The DCI may indicate an offset value (e.g., K_offset) that indicates the offset between the starting symbol / slot of the skipped opportunity (such as a measurement gap) and the starting / ending symbol / slot of the DCI (or PDSCH / PUSCH scheduled by the DCI). Note that if K_offset is not specified by the DCI, it may be configured by the RRC or defined by the standard.
[0123] The number N of consecutive opportunities (e.g., measurement gaps) to be skipped may be indicated by the DCI, or if N is not indicated by the DCI, N may be configured by the RRC or defined by the standard.
[0124] (Option 3-2-2) A skip window may be indicated by the DCI. The skip window may also be referred to as a no-measurement period, a period during which measurements are not performed, etc. In this case, all opportunities (such as measurement gaps) within the skip window are skipped. The skip window may be determined based on the following:
[0125] An offset (e.g., K_offset) representing 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) may be indicated by the DCI. Note that if K_offset is not specified by the DCI, it may be configured by the RRC or defined by a standard.
[0126] The length of the skip window (N slots / symbols) may be indicated by the DCI. Note that if N is not indicated by the DCI, N may be configured by the RRC or defined by the standard.
[0127] Terminal 200 may determine the start position and length of the skip window based on the DCI.
[0128] Measurement gaps etc. that are not included in the skip window are not skipped, and terminal 200 must perform RRM measurements in the non-skipped measurement gaps etc., and scheduling restrictions defined in the current standard apply to non-skipped measurement gaps etc. In measurement gaps etc. that are included in the skip window, terminal 200 may receive / transmit DL / UL channels / signals without performing RRM measurements.
[0129] 5 shows an example of notification of skipping of measurement gap opportunities based on Option 3-2-2, in which the DCI notifies that measurement gap opportunities included in the skip window will be skipped. In this example, the first and second measurement gap opportunities shown in the figure are skipped. Therefore, terminal 200 may decide to skip the first and second measurement gap opportunities shown in the figure, and may receive / transmit DL / UL channels / signals without performing RRM measurements during these measurement gap opportunities.
[0130] (Variation) K_offset symbols / slots may vary per SCS and may depend on the UE capabilities.
[0131] The K_offset symbols / slots may be determined based on the SCS of the serving cell of the DCI, or based on the minimum value between the SCS of the serving cell of the DCI and the SCS of the serving cell of the scheduled PDSCH / PUSCH, or based on the minimum value between the SCSs of the configured serving cells (within the same frequency range / band as the cell of the DCI).
[0132] The K_offset symbols / slots may be counted based on any of the following SCSs: DCI's serving cell's SCS SCS of the serving cell of the scheduled PDSCH / PUSCH (if any) Explicitly configured SCS
[0133] The skipped opportunities (e.g., specific measurement gaps) within the skip window may apply regardless of the measurement gap type / measurement gap ID / serving cell, or may apply only to specific measurement gap types / measurement gap IDs / serving cells.
[0134] (Example 3-2-a) The opportunities to be skipped within the skip window may be determined regardless of the measurement gap type (e.g., per UE, FR1 / FR2), regardless of the measurement gap ID, and regardless of the serving cell for which the RRM measurement and / or SMTC window is configured.
[0135] (Example 3-2-b) The opportunities to be skipped within the skip window may be determined from a specific measurement gap type (e.g., per UE, FR1 / FR2), from a specific measurement gap ID, or from a measurement gap with a specific cell.
[0136] The particular measurement gap type may be configured by the RRC, may be configured for the corresponding frequency range of the serving cell of the DCI, may be defined by the standard, or may be indicated by the DCI.
[0137] The specific measurement gap ID may be configured by the RRC or indicated by the DCI.
[0138] The particular serving cell may be the serving cell that receives the DCI, may be configured by RRC, or may be indicated by the DCI (eg, reusing the CIF field).
[0139] (Variation) The DCI may include multiple fields corresponding to a measurement gap type / measurement gap ID / serving cell, respectively.
[0140] For example, M fields of the DCI may indicate the K_offset of the RRM measurement / SMTC window of serving cell #1, the K_offset of the RRM measurement / SMTC window of serving cell #2, ..., the K_offset of the RRM measurement / SMTC window of serving cell #M.
[0141] For example, three fields of the DCI may indicate the K_offset of the measurement gap for each UE type, the K_offset of the FR1 type measurement gap, and the K_offset of the FR2 type measurement gap.
[0142] For example, M fields of the DCI may indicate K_offset for measurement gap ID#1, K_offset for measurement gap ID#2, . . . , K_offset for measurement gap ID#M.
[0143] (Option 3-3) Option 3-3 describes notification of whether to skip or not skip each of N consecutive opportunities (such as a specific measurement gap) (N is an integer equal to or greater than 1) using a bitmap indicating a skip pattern.
[0144] (Option 3-3-1) The bitmap is shown for N consecutive specific measurement gaps, etc., and each bit indicates whether or not to skip the corresponding measurement gap, etc. For example, a bit value of "0" may indicate "not skipping (not skipped)" and a bit value of "1" may indicate "skip (skipped)," or alternatively, a bit value of "1" may indicate "not skipping (not skipped)" and a bit value of "0" may indicate "skip (skipped)."
[0145] For measurement gaps etc. notified as "skipped", terminal 200 does not perform RRM measurements during the measurement gaps etc., and scheduling restrictions defined in the current standard do not apply, and terminal 200 may receive / transmit DL / UL channels / signals. On the other hand, for measurement gap occasions notified as "not skipped", terminal 200 must perform RRM measurements during the measurement gap occasions, and scheduling restrictions defined in the current standard apply during non-skipped measurement gap occasions.
[0146] The first opportunity among the N opportunities (e.g., measurement gaps) indicated by the bitmap may be the first measurement gap K_offset symbols / slots after the start / end symbol of the DCI (or the PDSCH / PUSCH scheduled by the DCI). Terminal 200 may thus determine the first opportunity (e.g., measurement gap) to be skipped based on the DCI.
[0147] K_offset is an offset value, which may be set by RRC, defined by the standard, or signaled by DCI.
[0148] The value of N may also be defined by a standard, may be set by the RRC, or may be notified by the DCI.
[0149] 6 shows an example of notification of skipping of measurement gap opportunities based on Option 3-3-1, in which the DCI notifies a skip pattern of N consecutive measurement gap opportunities (N=4 in the example shown in FIG. 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 in the figure is skipped. Therefore, terminal 200 decides to skip the second measurement gap opportunity shown in the figure, and may receive / transmit DL / UL channels / signals without performing RRM measurements during this measurement gap opportunity.
[0150] (Option 3-3-2) Multiple skip patterns (each skip pattern corresponding to a bitmap, such as option 3-3-1) may be configured by the RRC or defined by a standard, and a pattern index may be indicated by the DCI.
[0151] A single skip pattern (for example, "0000") for not skipping measurement gaps or the like may be set by the RRC or may be defined by a standard.
[0152] The methods for determining / indicating skipped measurement gaps etc. described in Option 3-1 / Option 3-2 can be applied to determine / indicate specific measurement gaps etc. for bitmap applications.
[0153] (Variation) The DCI may include multiple fields, each corresponding to a measurement gap type, a measurement gap ID, and a serving cell.
[0154] For example, M fields of the DCI may indicate a bitmap of RRM measurement / SMTC windows for serving cell #1, a bitmap of RRM measurement / SMTC windows for serving cell #2, ..., a bitmap of RRM measurement / SMTC windows for serving cell #M.
[0155] For example, three fields of the DCI may indicate a bitmap of measurement gaps per UE type, a bitmap of FR1 type measurement gaps, and a bitmap of FR2 type measurement gaps.
[0156] For example, M fields of the DCI may indicate a bitmap of measurement gap ID#1, a bitmap of measurement gap ID#2, . . . , a bitmap of measurement gap ID#M.
[0157] (Option 3-4) Option 3-4 describes a case where Option 3-1 and Option 3-2 are combined, i.e., the DCI includes a one-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 a time window).
[0158] Note that if the 1-bit flag indicates that measurement gaps etc. are not to be skipped, then the field for indicating the skipped opportunities (measurement gaps etc.) does not exist / is not necessary.
[0159] (Options 3-5) Option 3-5 describes a case where Option 3-1 and Option 3-3 are combined. That is, DCI includes a 1-bit flag field indicating whether to skip measurement gaps, etc., and a bitmap field indicating the skip pattern.
[0160] Note that if a 1-bit flag indicates that measurement gaps etc. are not to be skipped, the field of the bitmap indicating the skip pattern does not exist / is not necessary.
[0161] <Proposal 4: Processing timeline> The timeline for skipping certain measurement gaps etc. is shown below.
[0162] The processing time of a DCI indicating the skipping of a particular measurement gap etc. is defined as the minimum time required to process the skip indication. The skip indication processing time T_proc_skip may be defined by the standard. The value of T_proc_skip may also vary from SCS to SCS and may depend on the UE capabilities.
[0163] (Variation) The standard defines a new table containing the values of T_proc_skip for various SCSs.
[0164] The value of T_proc_skip is the PDSCH processing procedure time T as per TS 38.214, section 5.3. proc, 1 May be smaller / larger.
[0165] The value of T_proc_skip is the PUSCH preparation procedure time T as per TS 38.214, section 6.4. proc, 2 May be smaller / larger.
[0166] The value of T_proc_skip is T proc, 1 +d skip It may be equal to d skip The value of may be defined by standards. skip The value of may vary from SCS to SCS and may depend on the UE capabilities.
[0167] The value of T_proc_skip is T proc, 2 May be equivalent to +dskip. d skip The value of may be defined by standards. skip The value of may vary from SCS to SCS and may depend on the UE capabilities.
[0168] For example, terminal 200 may not assume that it will detect DCI indicating skipping of a measurement gap or the like that starts / ends up to T_proc_skip after the ending symbol / slot of the DCI.
[0169] For example, terminal 200 does not need to assume that the value of K_offset in proposal 3 is smaller than T_proc_skip.
[0170] <Analysis> At the RAN1#118 meeting, a working assumption was made to support dynamic indication of gap / restriction skipping (see Figure 12). One of the issues is the DCI format for indicating gap / restriction skipping. At the RAN1#118bis meeting, it will be discussed whether to support DCI format 0_3 / 1_3 for indication.
[0171] If DCI format 0_3 / 1_3 is supported for indication, it is preferable to clarify how to determine the gap / limit to be skipped by the indication of DCI format 0_3 / 1_3.
[0172] <Proposal Summary> Proposal 5: Skipping instruction field in DCI format 0_3 / 1_3 Proposal 5-1: Only 1-bit fields 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: Determining the minimum time offset
[0173] <Suggestion 5> A skipping instruction field is provided in DCI format 0_3 / 1_3. The following suggestions 5-1 to 5-3 are provided for the skipping instruction field in DCI format 0_3 / 1_3.
[0174] (Proposal 5-1) If DCI format 0_3 / 1_3 scheduling PUSCH / PDSCH on a set of cells is configured for gap / restriction skipping indication, only a 1-bit field of DCI format 0_3 / 1_3 is used to indicate skipping (see Figure 13). For skipping indication by the 1-bit field of DCI format 0_3 / 1_3, the following options are provided:
[0175] Option 1 The gap / restriction indication field applies to the scheduling cell (ie, the cell of the DCI).
[0176] Option 2 The gap / restriction indication 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 (a variation of Option 2) The gap / restriction indication field applies on the scheduled cell where the (first) scheduled PDSCH / PUSCH is after the minimum time offset (applied for skip indication as agreed in FIG. 12).
[0178] Option 3 The Gap / Limit Indication field applies to one of the scheduled cells. For the determination of "one of the scheduled cells", the following options 3-1 to 3-3 are provided.
[0179] Option 3-1 The scheduled cells with the minimum / maximum cell index
[0180] Option 3-2 Scheduled cells with minimum / maximum SCS 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 (a variation of Option 3) The Gap / Restriction Indicator field applies to the one on which the (first) scheduled PDSCH / PUSCH is after the minimum time offset.
[0183] For the determination of "one of the scheduled cells whose (first) scheduled PDSCH / PUSCH is after the minimum time offset", options 3-1 / 3-2 / 3-3 are reused by replacing "scheduled cell" with "scheduled cell whose (first) scheduled PDSCH / PUSCH is after the minimum time offset".
[0184] Option 4 The gap / restriction indication field is applied to one of the scheduling cell and the scheduled cell. For the determination of "one of the scheduling cell and the scheduled cell", the following options 4-1 to 4-3 are provided.
[0185] Option 4-1 The cell with the minimum / maximum cell index between the scheduling cell and the scheduled cell
[0186] Option 4-2 The cell with the minimum / maximum SCS among the scheduling cell and the scheduled cell 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 between the scheduling cell and the scheduled cell
[0188] Option 4a (a variation of Option 4) The gap / restriction indication field applies to one of the scheduling and scheduled cells whose (first) scheduled PDSCH / PUSCH is after the minimum time offset.
[0189] For the determination of "one of the scheduled cell and the scheduled cell whose (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 whose (first) scheduled PDSCH / PUSCH is after the minimum time offset".
[0190] Option 5 The gap / restriction indication field applies to the scheduling cell and to all scheduled cells.
[0191] Option 5a (a variation of Option 5) The gap / restriction indication field applies to the scheduling cell and the scheduled cell whose (first) scheduled PDSCH / PUSCH is after the minimum time offset.
[0192] Option 6 The Gap / Limit Indicator field applies to the scheduling cell and one of the scheduled cells. For the determination of "one of the scheduled cells", see option 3.
[0193] Option 6 (variation of option 6) The Gap / Restriction Indicator field applies to the scheduling cell whose (first) scheduled PDSCH / PUSCH is after the minimum time offset and to one scheduled cell. For the determination of "one of the scheduled cells", see Option 3.
[0194] (Proposal 5-2) If DCI format 0_3 / 1_3 that schedules PUSCH / PDSCH on a set of cells is configured for gap / restriction skipping indication, a separate bit (or separate bit field) of DCI format 0_3 / 1_3 is used to indicate the skipping indication for each scheduled cell, respectively (see Figure 14).
[0195] The number of bits in the skip indication field (or the number of skip indication 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 CC idx, respectively.
[0197] (Proposal 5-3) If DCI format 0_3 / 1_3 that schedules PUSCH / PDSCH on a set of cells is configured for gap / restriction skipping indication, the skipping field of DCI format 0_3 / 1_3 indicates joint indication of skipping indication on the scheduled cells (see Figure 15).
[0198] The skipping field indicates a row index, with each row containing a separate bit indication for each scheduled cell.
[0199] Each bit is associated with a co-scheduled cell in ascending / descending order of CC idx, respectively.
[0200] <Suggestion 6> If the UE determines that a gap / restriction indication in DCI format 0_3 / 1_3 applies to a particular cell, the indicated gap / restriction is determined as the first gap / restriction on / for the cell with the minimum time offset after the DCI (e.g., T_min_offset) (see Figure 16).
[0201] If T_min_offset is in slots / symbols (i.e., X slots / symbols as time offset), it is required to specify the SCS for T_min_offset. The following Alt. is provided for specifying 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 the 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 among the SCSs of the scheduled cells.
[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 frequency range of the scheduled cell, e.g., if the scheduled cell is in FR1, the minimum / maximum SCS of the FR1 cell applies.
[0207] Alt.6 T_min_offset is determined based on the minimum / maximum SCS of the scheduling cell and the SCS of the (configured / activated) serving cell within the frequency range of the scheduled cell.
[0208] Alt.7 T_min_offset is determined based on the minimum / maximum SCS among the SCSs of all configured / activated serving cells.
[0209] Alt.8 T_min_offset is determined based on the SCS of the reference cell (set by the 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 determined appropriately.
[0211] Below, we will explain Proposals 7 to 9. First, we will explain the background.
[0212] <Background> It has been agreed that the DCI format for multi-carrier scheduling of PUSCH is called DCI format 0_3. It has been agreed that the DCI format for multi-carrier scheduling of PDSCH is called DCI format 1_3. DCI formats 0_3 / 1_3 are scrambled by C-RNTI / MCS-C-RNTI. DCI formats 0_3 / 1_3 can be simultaneously scheduled for combinations of cells included in a scheduling set of cells.
[0213] Scheduling / configuration flexibility and DCI overhead There is a trade-off between scheduling / configuration flexibility and DCI overhead. Two types of DCI fields can be specified: Type 1 and Type 2. Type 1 is further divided into three types. Type-1 field: A single value is indicated between co-scheduled cells. Type-1A field: A single value applies to all simultaneously scheduled cells (see Figure 17). Type-1B field: A single value indicates a row in the "joint-indication table" (see Figure 18). Type-1C field: A single value applies to only one cell in the cell set (see Figure 19). Type-2 field: A separate value is specified for each cell (see Figure 20).
[0214] Figure 21 shows DCI field classification in DCI formats 0_3 / 1_3.
[0215] DCI field / format size determination Type-1A field: The maximum field size among the active BWPs of all cells in the cell set is determined (see Figure 22). Type-1B field: The Type-1B field is determined based on the size of the "joint instruction table" (see Figure 23). Type-2 field: The size of each block in each cell is based on the size of the active BWP field of the cell. The overall size of the Type-2 field can be changed depending on the combination of simultaneously scheduled cells (see Figure 24).
[0216] "3+1" DCI size budget The "3+1" DCI size budget is maintained as legacy and no changes are made to the specifications. The UE can also monitor legacy DCI formats within the budget (see Figure 25).
[0217] After step 4C of the DCI size alignment procedure, an additional DCI size alignment procedure is performed: zero padding is performed for smaller DCI formats, if necessary, from DCI format 0_3 or DCI format 1_3.
[0218] DCI field size compression scheme The size of the FDRA field is relatively large, so a coarser RBG size, setting 3, for FDRA type 0 is introduced (see Figure 26).
[0219] <Analysis> If DCI format 0_3 / 1_3 is supported for indication, the gap / limit skipping field in DCI format 0_3 / 1_3 may be used (see, for example, <Proposal 5>).
[0220] Considering a type 1 field (i.e., a single value for all co-scheduled cells) or a type 2 field (i.e., separate values for each co-scheduled cell) for the gap / limit skipping indication field may be useful in various use cases. Therefore, configurability for the indication type of the gap / limit skipping indication field may be considered (proposal 7).
[0221] If separate bit values are supported for different cells, there may be restrictions on bit values between cells. For example, gap / limit considerations for one cell may also apply to other cells within the same band. In such cases, it may be necessary to restrict the same bit values for such intra-band cells (Proposal 8).
[0222] <Suggestion 7> The field indication type for the gap / restriction skipping field in DCI format 0_3 / 1_3 is configured by higher layer signaling such as RRC, for example, the field indication type such as a type 1a / 1b field or a type 2 field is configured by RRC.
[0223] A new RRC parameter, MC-DCI-SetOfCells, is set to indicate whether it is a Type 1a / 1b or Type 2 field for DCI format 0_3 / 1_3. MC-DCI-SetOfCells is a parameter that configures, for example, the set of cells for multi-cell PDSCH / PUSCH scheduling.
[0224] If the instruction type is set to Type 1a, suggestion 5-1 above applies. For example, gap / restriction skipping is applied to all cells in the set. For example, gap / restriction skipping applies to all serving cells (regardless of set).
[0225] If the instruction type is set to Type 1b, suggestion 5-3 above applies. For example, gap / restriction skipping is applied to combinations of serving cells in the set. For example, gap / restriction skipping applies to any combination of serving cells (regardless of set).
[0226] If the instruction type is set to Type 2, suggestion 5-2 above applies. For example, gap / restriction skipping is applied to each serving cell in the set. For example, gap / restriction skipping is applied to each serving cell (regardless of set).
[0227] <Suggestion 8> If the indication type of the gap / restriction skipping indication field in DCI format 0_3 / 1_3 is type 2 (i.e., separate value for each cell as in proposal 5-2) (or type 1b as in proposal 5-3), there may be restrictions on the indicated bit values for different cells (see Figure 27). Constraint #1: The UE expects the same bit values for simultaneously scheduled cells in the same band. Constraint #2: If there is an overlap between corresponding gaps / limits of co-scheduled cells in the same band, the UE expects the same bit values for co-scheduled cells in the same band.
[0228] <Suggestion 9> When gap / restriction skipping indication is applied to a serving cell, gap / restriction skipping is also applied to other serving cells according to the conditions (based on TS38.133 9.1.2 and 9.2.5.3).
[0229] Condition #1: If the UE is configured with per-UE gap (per-UE GAP) and gap skipping is applied to the gap, gap skipping is applied to all serving cells.
[0230] Condition #2: If the UE is configured with a per-FR gap and skipping is applied to the gap, gap skipping is applied to all serving cells in the same FR.
[0231] Condition #3: If skipping is applied to a scheduling restriction occasion on a serving cell with intraband CA, restricted skipping is applied to other cells in the same band on symbols that fully or partially overlap with the skipped symbols on the serving cell.
[0232] Condition #4: If skipping is applied to restricted scheduling opportunities on an FR1 serving cell with interband CA and the UE does not support simultaneousRxTxInterBandCA for the band pair, restricted skipping is applied to other cells in different bands on symbols that fully or partially overlap with the skipped symbols on the serving cell. simultaneousRxTxInterBandCA relates to the capability of interband carrier aggregation, e.g., for simultaneous reception / transmission.
[0233] FIG. 28 is a diagram illustrating an example in which skipping is also applied to other serving cells when certain conditions are met.
[0234] <Summary of Proposals 7-9> In the skipping instruction by DCI format 0_3 / 1_3 in Type 1 / Type 2, the gap / limit can be appropriately determined.
[0235] <Variations> Whether Proposal 5-1 / 5-2 / 5-3 apply may be defined by the specification or set by the gNB.
[0236] <Terminology> A scheduling cell may be considered to be a cell for controlling data transfer, such as managing data transfer and allocating resources. A scheduled cell may be considered to be a cell in which data transfer is performed. For example, a scheduling cell allocates resources (is scheduled), and a scheduled cell transfers data using the allocated resources. A co-scheduled cell may be considered to be a scenario in which multiple cells (base stations) are scheduled to operate simultaneously and cooperatively.
[0237] DCI format 0_3 may be considered as DCI in multi-carrier scheduling of PUSCH. DCI format 1_3 may be considered as DCI in multi-carrier scheduling of PDSCH. DCI formats 0_3 / 1_3 can be simultaneously scheduled for combinations of cells included in a set of cells to be scheduled.
[0238] <Example of operation> Next, an example of the operation of the terminal 200 will be described with reference to FIG.
[0239] In step S21, terminal 200 receives first information regarding an extended period for measurement using a measurement signal from base station 100. 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 the existing information element.
[0240] In step S22, the terminal 200 periodically sets an extended period for measurement using the measurement signal based on the received first information.
[0241] In step S23, the terminal 200 receives second information from the base station 100 dynamically indicating not to perform measurements during part of the periodic extended period.
[0242] In step S24, the terminal 200 performs reception or transmission of signals to or from the base station without performing measurements during a part of the periodic extended period based on the received second information.
[0243] (effect) According to the above proposal, certain measurement gaps etc. (opportunities) can be skipped based on dynamic notification by the DCI, thereby reducing the impact of scheduling restrictions on measurements.
[0244] <UE capability> The UE capability indicating 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.
[0245] Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by DCI Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping using new DCI formats Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by new RNTI Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by DCI1_1 / 1_2 / 1_3 using scheduling PDSCH Information defining whether the terminal supports dynamic indication of measurement gap / RRM measurement / SMTC window skipping by DCI0_1 / 0_2 / 0_3 due to PUSCH scheduling Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by DCI2_1 with DL preemption indication Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping via DCI2_4 with UL cancellation indication Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by DCI1_1 / 1_2 / 1_3 without scheduling PDSCH Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping via DCI0_1 / 0_2 / 0_3 without scheduling PUSCH Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by DCI2_1 without DL preemption indication Information defining whether the terminal supports dynamic indication of measurement gaps / RRM measurements / SMTC window skipping by DCI2_4 without UL cancellation indication Information defining whether the terminal supports dynamic indication of multiple measurement gaps / RRM measurements / SMTC window skipping Information defining whether the terminal supports dynamic indication of discontinuous measurement gaps / RRM measurements / SMTC window skipping New UE capability and report signaling (and RRC configuration) for some or all of the following (e.g., per UE / FR / FC) may be defined: Information defining whether the terminal supports dynamic indication of skipping of MG / RRM measurement / SMTC opportunities by DCI format 0_3 Information defining whether the terminal supports dynamic indication of skipping of MG / RRM measurement / SMTC opportunities by DCI format 1_3
[0246] Define new UE capabilities and report signaling (and RRC configuration) for some or all of the following (per UE / FR / FC / etc.): Support for Type 1 fields for gap / limit skipping indication via DCI format 0_3. Support for Type 1 fields for gap / limit skipping indication via DCI format 1_3. Support for Type 2 field for gap / limit skipping indication via DCI format 0_3. Support for Type 2 fields for gap / limit skipping indications via DCI format 1_3. Support for configurability between Type 1 and Type 2 fields for gap / limit skipping indication via DCI format 0_3. Support for configurability between Type 1 and Type 2 fields for gap / limit skipping indication via DCI format 1_3.
[0247] In the above, an example has been described in which notifications, requests (skip patterns, etc.) to skip measurement gaps / RRM measurements / SMTC windows (opportunities) are exchanged between base station 100 and terminal 200, but notifications, requests (skip patterns, etc.) not to skip measurement gaps / RRM measurements / SMTC windows (opportunities) may also be exchanged.
[0248] Next, the configurations of base station 100 and terminal 200 will be described. Note that the configurations of base station 100 and terminal 200 described below are examples of functions related to the present embodiment. Base station 100 and terminal 200 may have functions not shown. Furthermore, the functional divisions and / or names of functional units are not limited as long as the functions perform operations related to the present embodiment.
[0249] <Base station configuration> 8 is a block diagram showing an example of the configuration of base station 100 according to this embodiment. Base station 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 100 communicates with terminal 200 (see FIG. 9) by radio.
[0250] Transmitter 101 transmits a downlink (DL) signal to terminal 200. For example, transmitter 101 transmits a DL signal (for example, the above-mentioned RRC, SIB, MAC CE, DCI, notification, confirmation, etc.) under the control of controller 103.
[0251] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of terminal 200 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.
[0252] Channels used for transmitting 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.
[0253] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.
[0254] The receiver 102 receives an uplink (UL) signal transmitted from the terminal 200. For example, under the control of the controller 103, the receiver 102 receives an UL signal (for example, the above-mentioned request, notification, etc.).
[0255] The transmitting unit 101 and the receiving unit 102 may be collectively referred to as a communication unit.
[0256] The control unit 103 controls the communication operations of the base station 100, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit .
[0257] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.
[0258] For example, 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 (e.g., data and control information, etc.) received from terminal 200 and / or data and control information, etc. acquired from a higher layer. Information related to the allocated resources may be included in control information transmitted to terminal 200.
[0259] <Device configuration> 9 is a block diagram showing an example of the configuration of terminal 200 according to the present embodiment. Terminal 200 includes, for example, receiving section 201, transmitting section 202, and control section 203. Terminal 200 communicates with base station 100, for example, wirelessly.
[0260] In relation to the above proposal, for example, the receiver 201 may receive, from the base station 100, first information (such as an RRC) regarding an extended period (such as a measurement gap opportunity) for measurements (such as SSB measurements) using a measurement signal (such as an SSB). For example, the receiver 201 may receive, from the base station 100, second information (such as an RRC, SIB, MAC CE, or DCI) indicating that measurements will not be performed during a portion of the periodic extended period. For example, after receiving the second information, the receiver 201 may receive, from the base station 100, information (such as a MAC CE or DCI) indicating that measurements will be performed during another portion of the periodic extended period. The receiver 201 may receive, from the base station 100, a signal during a portion of the periodic extended period.
[0261] The transmitter 202 transmits an UL signal to the base station 100. For example, under the control of the controller 203, the transmitter 202 transmits an UL signal (for example, the above-mentioned request, notification, etc.).
[0262] In relation to the above proposal, for example, the transmitter 202 may transmit a signal to the base station 100 during a portion of a periodic extended period (such as a measurement gap opportunity) for measurements (such as SSB measurements) using a measurement signal (such as SSB).
[0263] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of terminal 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.
[0264] Channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, terminal 200 transmits uplink control information to base station 100 using the PUCCH and transmits uplink data signals using the PUSCH.
[0265] 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, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).
[0266] The receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.
[0267] The control unit 203 controls the communication operations of the terminal 200 , including the reception processing in the reception unit 201 and the transmission processing in the transmission unit 202 .
[0268] For example, the control unit 203 acquires information such as data and control information from a higher layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the higher layer.
[0269] For example, the control unit 203 controls 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, 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 UCI.
[0270] In relation to the above proposal, for example, the control unit 203 may periodically set an extended period (such as a measurement gap opportunity) for measurements (such as SSB measurements) using a measurement signal (such as SSB) based on the first information. For example, the control unit 203 may determine a portion of the periodic extended period during which no measurements are performed based on the second information, or may not perform measurements during the determined portion of the periodic extended period.
[0271] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.
[0272] The above configuration can reduce the impact of scheduling restrictions on measurements.
[0273] <Summary of the embodiment> As described above, according to one aspect of the present disclosure, a communication unit that receives or transmits a signal; A terminal is provided which includes a control unit that performs measurements during a measurement period, and the control unit determines whether to skip the measurements during a specific measurement period based on a field of downlink control information received by the communication unit.
[0274] With the above configuration, it is possible to not perform measurements during a specific measurement period based on a field in the downlink control information, and to perform signal reception or transmission, thereby reducing the impact of scheduling restrictions on measurements.
[0275] In one example, the field of the downlink control information is a 1-bit flag field, and when the flag field has a specific value, the control unit skips the measurement in the specific measurement period.
[0276] In one example, the downlink control information indicates a skip window, and the control unit skips the measurement in all measurement periods within the skip window.
[0277] In one example, the downlink control information indicates a skip pattern using a bitmap, and the control unit skips the measurement in a measurement period corresponding to a bit having a specific value in the bitmap.
[0278] 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 in 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 in that period.
[0279] With the above configuration, it is possible to not perform measurements during a specific measurement period based on a field in the downlink control information, and to perform signal reception or transmission, thereby reducing the impact of scheduling restrictions on measurements.
[0280] In one example, the control unit may determine whether to skip the measurement in a specific measurement period based on a field of downlink control information received by the communication unit, the field scheduling uplink and / or downlink signals for a set of cells, and determine cells among the set of cells to which the measurement skip applies based on a field type of the downlink control information. The format of the downlink control information may be DCI format 0_3 / 1_3.
[0281] In one example, the communication unit may receive the field type of the downlink control information through higher layer signaling such as RRC.
[0282] In one example, the controller may apply the skipping of measurement to all cells in the set of cells when a field type of the downlink control information is a type instructing all simultaneously scheduled cells by a single value, and the type may be Type-1A.
[0283] In one example, the control unit may apply the skipping of measurements to a combination of serving cells within the set of cells when the field type of the downlink control information is a type that indicates a row of a joint indication table with a single value and indicates a combination of simultaneously scheduled cells.
[0284] In one example, the control unit may apply the skipping of measurements individually in each serving cell in the set of cells when the field type of the downlink control information is a type that indicates for each simultaneously scheduled cell by an individual value.
[0285] <Hardware configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.
[0286] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.
[0287] For example, a base station, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 10 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 100 and terminal 200 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0288] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of base station 100 and terminal 200 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0289] Each function in the base station 100 and the terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.
[0290] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.
[0291] Furthermore, the processor 1001 reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. 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 similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.
[0292] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.
[0293] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.
[0294] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.
[0295] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0296] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0297] Furthermore, base station 100 and terminal 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
[0298] (Supplementary explanation of the embodiment) Although the 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, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; features described in two or more items may be used in combination as needed, and features described in one item may apply to features described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagrams do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, base stations and terminals have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of a base station in accordance with an embodiment of the present disclosure, and the software operated by the processor of a terminal in accordance with an embodiment of the present 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.
[0299] <Information notification, signaling> The notification of information is not limited to the embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0300] <Applicable systems> Embodiments described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), 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, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable systems, and next generation systems extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.
[0301] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0302] <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. 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 may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.
[0303] <Input / output direction> Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input and output via multiple network nodes.
[0304] <Handling of input and output information> Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.
[0305] <Judgment method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0306] <Variations of form, etc.> Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).
[0307] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0308] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0309] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0310] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0311] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0312] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0313] <parameter, channel name> Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0314] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0315] <Base station> In this disclosure, terms such as "base station (BS)," "radio 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.
[0316] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.
[0317] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
[0318] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0319] 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 some other suitable terminology.
[0320] <Base station / mobile station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.
[0321] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present 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) or V2X (Vehicle-to-Everything)). In this case, the terminal may be configured to have the functions of the base station described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.
[0322] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.
[0323] Fig. 11 shows an example configuration of a vehicle 2001. As shown in Fig. 11, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0324] The drive unit 2002 is configured, for example, by 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 operated by the user.
[0325] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0326] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0327] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.
[0328] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0329] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0330] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029, which are provided in the vehicle 2001.
[0331] 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.
[0332] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0333] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices 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 to 2029, and the like provided in the vehicle 2001.
[0334] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0335] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0336] <Reference signal> The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0337] <The meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0338] <"First", "Second"> As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0339] <Means> In the configurations of each of the above devices, the "means" may be replaced with "section", "circuit", "device", etc.
[0340] <Open format> In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.
[0341] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio frame may be composed 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 be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) independent of numerology.
[0342] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.
[0343] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.
[0344] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0345] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[0346] 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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.
[0347] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.
[0348] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0349] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0350] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0351] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0352] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.
[0353] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0354] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.
[0355] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0356] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0357] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.
[0358] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0359] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0360] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0361] <Article> In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0362] <"Different"> In the present 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 "coupled" may also be interpreted in the same way as "different." [Industrial Applicability]
[0363] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]
[0364] 10. Wireless communication systems 20 NG-RAN 100 base stations (gNB) 200 User Equipment (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit
Claims
1. a communication unit that receives or transmits signals; a control unit that performs measurements during a measurement period; Equipped with The control unit determining whether to skip the measurement in a specific measurement period based on a field of downlink control information received by the communication unit that schedules uplink signals and / or downlink signals on a set of cells; determining a cell to which the measurement skip is to be applied from among the set of cells based on a field type of the downlink control information; Terminal.
2. The communication unit receives a field type of the downlink control information by higher layer signaling. The terminal according to claim 1 .
3. The control unit applies the skipping of measurement to all cells of the set of cells when a field type of the downlink control information is a type that indicates all simultaneously scheduled cells by a single value. The terminal according to claim 1 .
4. The control unit applies the skip of measurement to a combination of serving cells in the set of cells when a field type of the downlink control information indicates a row of a joint indication table by a single value and indicates a simultaneously scheduled cell. The terminal according to claim 1 .
5. When a field type of the downlink control information is a type instructing each of the simultaneously scheduled cells by an individual value, the control unit applies the skip of measurement to each serving cell in the set of cells. The terminal according to claim 1 .
6. The device is Set the measurement period, determining whether to skip measurements in a particular measurement period based on a field of downlink control information that schedules uplink and / or downlink signals on a set of cells; determining a cell to which the measurement skip is to be applied from among the set of cells based on a field type of the downlink control information; Communication method.