WO2023277126A1 - Terminal and wireless communication method - Google Patents

Abstract

A terminal comprising a reception unit for receiving system information including instruction information indicating that a tracking reference signal is available at a resource and/or an opportunity configured for the tracking reference signal, and a control unit which, using as a reference timing a timing related to reception of the system information, a timing related to reception of system information other than the system information, or a boundary of or an update period, determines a start timing of a timer related to a valid period of the instruction information.

Description

Terminal and wireless communication method Cross-reference to related applications

This application is based on Japanese Patent Application No. 2021-108258 filed on June 30, 2021, and claims the benefit of its priority. incorporated herein by reference.

The present disclosure relates to terminals and wireless communication methods.

In the Third Generation Partnership Project (3GPP), an international standardization organization, Long Term Evolution (LTE), which is the 3.9th generation Radio Access Technology (RAT), and LTE-Advanced, which is the 4th generation RAT As a successor, Release 15 of New Radio (NR), which is a fifth generation (5G) RAT, has been specified (for example, Non-Patent Document 1). LTE and/or LTE-Advanced is also called Evolved Universal Terrestrial Radio Access (E-UTRA).

Currently, in 3GPP, a reference signal for tracking (hereinafter referred to as "tracking reference signal (TRS)") is used to synchronize in the time domain and/or frequency domain (hereinafter referred to as "time/frequency synchronization" ) is being considered. For example, a terminal in an idle state or an inactive state uses the TRS instead of a synchronization signal to perform time/frequency synchronization before a paging occasion (PO). is expected to reduce the power consumption of the terminal.

In addition, notifying the terminal of instruction information (hereinafter referred to as "TRS availability instruction") regarding the availability of the TRS in the resource and / or period set for the TRS, and / or the instruction information It is also considered to be able to control whether or not TRS is actually transmitted in the relevant resource and/or period by providing a validity period to .
The present disclosure has been made in view of such circumstances, and aims to provide a terminal and a wireless communication method capable of appropriately controlling operations related to TRS.

A terminal according to an aspect of the present disclosure includes a receiving unit that receives system information including indication information indicating that the tracking reference signal is available in resources and / or opportunities configured for the tracking reference signal; a control unit that determines the start timing of a timer related to the validity period of the instruction information, using the timing related to the reception of system information, the timing related to the reception of system information other than the system information, or the boundary of an update period as a reference timing.

An object of one aspect of the present disclosure is to provide a terminal and a wireless communication method capable of appropriately controlling operations related to TRS.

FIG. 1 is a diagram showing an example of an outline of a wireless communication system according to this embodiment. FIG. 2 is a diagram showing an example of acquisition of an SI message according to this embodiment. FIGS. 3A and 3B are diagrams showing examples of TRS availability indications and validity periods according to this embodiment. FIG. 4 is a diagram showing another example of the TRS availability indication and validity period according to this embodiment. FIG. 5 is a diagram showing an example of TRS-related operations during cell reselection according to the present embodiment. FIG. 6 is a diagram illustrating another example of TRS-related operations during cell reselection according to the present embodiment. FIGS. 7A and 7B are diagrams showing an example of the operation during activation of the valid timer according to this embodiment. FIG. 8 is a diagram showing an example of an SI update procedure according to this embodiment. FIG. 9 is a diagram showing an example of the control operation of the validity period of the TRS availability indication according to this embodiment. FIG. 10 is a diagram showing another example of the control operation of the validity period of the TRS availability indication according to this embodiment. FIG. 11 is a diagram showing an example of the hardware configuration of each device in the wireless communication system according to this embodiment. FIG. 12 is a diagram showing an example of a functional block configuration of a terminal according to this embodiment. FIG. 13 is a diagram showing an example of the functional block configuration of the base station according to this embodiment.

The present embodiment will be described below with reference to the accompanying drawings. In order to facilitate understanding of the description, the same constituent elements in each drawing are denoted by the same reference numerals as much as possible, and overlapping descriptions are omitted.

FIG. 1 is a diagram showing an example of an overview of a wireless communication system according to this embodiment. As shown in FIG. 1, the wireless communication system 1 may include a terminal 10, a base station 20, and a core network 30. Note that the numbers of terminals 10 and base stations 20 shown in FIG. 1 are merely examples, and are not limited to the numbers shown.

As the radio access technology (RAT) of the wireless communication system 1, for example, NR is assumed, but it is not limited to this, and various RATs such as the 6th generation or later RAT can be used.

The terminal 10 is, for example, a predetermined terminal or device such as a smartphone, a personal computer, an in-vehicle terminal, an in-vehicle device, a stationary device, a telematics control unit (TCU), or the like. Terminal 10 may also be called a User Equipment (UE), a Mobile Station (MS), a User Terminal, a Radio apparatus, a subscriber terminal, an access terminal, and so on. The terminal 10 may be mobile or stationary. The terminal 10 is configured to be able to communicate using, for example, NR as the RAT.

The base station 20 forms one or more cells C and communicates with the terminal 10 using the cells. Cell C may be interchangeably referred to as serving cell, carrier, component carrier (CC), and the like. For example, the base station 20 may configure one primary cell and one or more secondary cells for the terminal 10 for communication (also called carrier aggregation). That is, one or more cells C include at least primary cells and may include secondary cells.

Also, one or more bandwidth parts (BWP) may be set for one cell C. Here, the BWP mainly used when the terminal 10 initially accesses the cell is also called initial downlink BWP (Initial DL BWP) and initial uplink BWP (Initial UL BWP). For example, the base station 20 broadcasts the information used for setting the frequency position, bandwidth, subcarrier spacing and/or cyclic prefix for each of the initial downlink BWP and the initial uplink BWP in the system information. may

Base station 20 includes gNodeB (gNB), en-gNB, Next Generation-Radio Access Network (NG-RAN) node, low-power node, Central Unit (CU), Distributed Unit (DU), gNB -DU, Remote Radio Head (RRH), Integrated Access and Backhaul/Backhauling (IAB) node, etc. The base station 20 is not limited to one node, and may be composed of a plurality of nodes (for example, a combination of a lower node such as DU and an upper node such as CU).

The core network 30 is, for example, an NR-compatible core network (5G Core Network: 5GC), but is not limited to this. A device on the core network 30 (hereinafter also referred to as “core network device”) performs mobility management such as paging and location registration of the terminal 10 . A core network device may be connected to the base station 20 via a predetermined interface (eg, S1 or NG interface).

The core network device includes, for example, an Access and Mobility Management Function (AMF) that manages C-plane information (e.g., information related to access and mobility management), and a User that controls transmission of U-plane information (e.g., user data). At least one Plane Function (UPF) may be included.

In the wireless communication system 1, the terminal 10 receives downlink (DL) signals from the base station 20 and/or transmits uplink (UL) signals. One or more cells C are configured in the terminal 10, and at least one of the configured cells is activated. The maximum bandwidth of each cell is, for example, 20 MHz or 400 MHz.

Also, the terminal 10 performs a cell search based on a synchronization signal (eg, Primary Synchronization Signal (PSS) and/or Secondary Synchronization Signal (SSS)) from the base station 20. Cell search is a procedure by which the terminal 10 acquires time and frequency synchronization in a cell and detects the identifier of the cell (eg, physical layer cell ID).

Blocks containing at least one of the synchronization signal, broadcast channel (for example, Physical Broadcast Channel (PBCH)) and broadcast channel demodulation reference signal (DMRS) are synchronization signal blocks (Synchronization Signal Also called Block: SSB), SS/PBCH block, and the like. One or more SSBs may constitute one SS burst, and one or more SS bursts may constitute one SS burst set. The SS burst set may be transmitted at regular intervals (eg, 20 ms (2 radio frames)). In the case of multi-beam operation, SSBs with different indices correspond to different beams and may be transmitted by sequentially switching beam directions by beam sweeping.

Terminal 10 determines a search space and/or a control resource set (Control Resource Set: CORESET) based on parameters included in a radio resource control (RRC) message (hereinafter referred to as "RRC parameters"). , Within the search space associated with the CORESET, perform downlink control information transmitted via a downlink control channel (for example, physical downlink control channel (PDCCH)) (Downlink Control Information: DCI) monitoring Note that the RRC message may include, for example, an RRC setup message, an RRC reconfiguration message, an RRC resume message, system information, and the like.

DCI monitoring means that the terminal 10 blind-decodes the PDCCH candidate (PDCCH candidate) in the search space set in the assumed DCI format. The number of bits (also referred to as size, bit width, etc.) of the DCI format is predetermined or derived according to the number of bits of fields included in the DCI format. The terminal 10 specifies the number of bits in the DCI format and the scramble (hereinafter referred to as “CRC scramble”) of the cyclic redundancy check (CRC) bits (also referred to as CRC parity bits) of the DCI format. DCI for the terminal 10 is detected based on the Radio Network Temporary Identifier (RNTI). DCI monitoring is also called PDCCH monitoring, monitor, and the like. Also, the period during which DCI is monitored is also called a PDCCH monitoring occasion.

A search space set is a set of one or more search spaces. A search space set commonly used by one or more terminals 10 (hereinafter referred to as a "common search space (CSS) set") and a terminal-specific search space set (UE-specific search space (USS) set), and The search space set used for PDCCH monitoring of the terminal 10 uses upper layer parameters (for example, RRC Information Element (IE) 'SearchSpace', RRC IE 'pagingSearchSpace', RRC IE 'searchSpaceSIB1', RRC IE 'searchSpaceOtherSystemInformation', etc.). may be set in the terminal 10 by Terminal 10 detects DCI that is CRC-scrambled by a specific RNTI (eg, Cell (C)-RNTI, Paging (P)-RNTI, etc.) by PDCCH monitoring using a search space set, and uses the DCI to Controls reception of the scheduled PDSCH and/or transmission of an uplink shared channel (eg, physical uplink shared channel (PUSCH)).

(System information)
The system information broadcast in Cell C may include a Master Information Block (MIB) and/or one or more System Information Blocks (SIB). The MIB is broadcast via a broadcast channel (BCH). MIB and SIB1 are also called Minimum System Information, and SIB1 is also called Remaining Minimum System Information (RMSI). SIB1 is broadcast via a downlink shared channel (DL-SCH). SIBx (an arbitrary character string such as x=2, 3, . . . ) other than SIB1 is also called Other System Information (OSI). SIB1 is cell-specific and SIBx other than SIB1 is cell-specific or area-specific containing one or more cells. This area is also called a system information area or the like.

One or more SIBx are mapped to a system information (SI) message, and the SI message is broadcast via DL-SCH. Each SI message may be associated with a periodically occurring time-domain window (hereinafter “SI window”) and sent within the SI window. Note that BCH and DL-SCH may be interchanged with PBCH and physical downlink shared channel (PDSCH), respectively.

FIG. 2 is a diagram showing an example of obtaining an SI message according to this embodiment. In FIG. 2, as an example, it is assumed that SIBx and SIBy are mapped to SI message #0 and SIBz is mapped to SI message #1. Here, x, y, and z are arbitrary character strings such as 2, 3, . The SI messages #0 and #1 may be broadcast at predetermined intervals, or may be broadcast on demand in response to a request from the terminal 10. FIG. Also, each SI message #0 may be identical within the modification period. It should be noted that FIG. 2 is only an example, the number of SI messages, the number of SIBs mapped to each SI message, whether SIBx, SIBy and SIBz are area-specific or cell-specific, etc. are not shown. Not limited.

For example, as shown in FIG. 2, the terminal 10 detects the SSB and acquires the MIB broadcasted via the PBCH. Terminal 10 monitors a search space set (eg, Type0-PDCCH CSS set) configured for SIB1 to detect a CRC-scrambled DCI with a specific RNTI (eg, System Information (SI)-RNTI), SIB1 is received via the PDSCH scheduled by the DCI. The search space set for SIB1 may be set based on parameters in the MIB, but is not limited to this.

SIB1 may also include at least one of the following:
Information about each SI message (e.g. each 'schedulingInfo' in the RRC IE 'schedulingInfoList')
- Identification of the area to which the area-specific SIB belongs (e.g. "systemInformationAreaID" in the RRC IE)
- Information about the length of the SI window (e.g. "si-WindowLength" in the RRC IE), where the length is indicated e.g. in number of slots.
• Information about the period of each SI message (eg 'si-Periodicity' in the RRC IE 'schedulingInfo'), where the period is indicated eg in number of radio frames.
Information about each SIB mapped to each SI message (e.g., each 'SIB-TypeInfo' in 'SIB-Mapping' in the RRC IE 'schedulingInfo'), where the information about each SIB is, for example, information about the SIB type (e.g., RRC IE "type"), information about the version or update count of each SIB (hereinafter referred to as "version information", e.g., RRC IE "valueTag"), information indicating that each SIB is area-specific (e.g. , RRC IE “areaScope”). Note that not including information indicating that each SIB is area-specific may indicate that each SIB is cell-specific.

Terminal 10 monitors a search space set (eg, Type0A-PDCCH CSS set) configured for OSI to detect a DCI that is CRC scrambled with a specific RNTI (eg, SI-RNTI), and performs scheduling using the DCI. SI messages #0 and #1 are received via the PDSCH, and operations are performed based on the OSI (here, SIBx, SIBy, and SIBz) included in the SI messages #0 and #1, respectively.

For example, in FIG. 2, SIBx and SIBy included in SI message #0 are area-specific, and SIBz included in SI message #1 is cell-specific. Also, the version information of SIB1 (for example, RRC IE "valueTag") shall indicate that SIBx and SIBz have been updated once and have a version of v1, and SIBy has not been updated and have a version of v0. For example, the terminal 10 may determine whether or not the stored SIBx is valid based on the version indicated by the version information and the version of the SIBx stored in the terminal 10 itself. For example, when "v1" indicated by valueTag in SIB1 matches the version of stored SIBz, terminal 10 does not need to re-receive SI message #1 including SIBz. On the other hand, if the version “v1” indicated by the valueTag in SIB1 does not match the version of the stored SIBx, the terminal 10 may re-receive the SI message #0 including SIBx. In this way, SIBx, SIBy, and SIBz may have their valuetags incremented by one each time the content is changed.

(paging)
In paging, when the terminal 10 is in an idle state or an inactive state, a network-initiated message for setting up a connection (hereinafter, a “paging message”) is transmitted to the terminal 10 . Also, in paging, for example, system information change notifications and/or short messages used for public warnings (e.g., Earthquake and Tsunami Warning System (ETWS), Commercial Mobile Alert Service (CMAS), etc.) is transmitted to terminal 10 . The short message may be transmitted to the terminal 10 regardless of the state of the terminal 10 (eg, idle state, inactive state, connected state, etc.).

Here, the idle state is a state in which an RRC layer connection (hereinafter referred to as "RRC connection") between the terminal 10 and the base station 20 is not established. Also called etc. A terminal 10 in an idle state receives system information broadcast in a cell on which it camps. The terminal 10 in the idle state transitions to the connected state when the RRC connection is established.

In addition, the inactive state is a state in which the RRC connection is established but suspended, and is also called RRC_INACTIVE state, inactive mode, RRC inactive mode, and the like. The terminal 10 in the inactive state receives system information broadcasted in the cell on which it camps. The terminal 10 in the inactive state transitions to the connected state when the RRC connection is restarted, and transitions to the idle state when the RRC connection is released.

The connected state is a state in which the RRC connection is established, and is also called RRC_CONNECTED state, connected mode, RRC connected mode, and the like. The terminal 10 in the connected state transitions to the idle state when the RRC connection is released, and transitions to the inactive state when the RRC connection is suspended.

A terminal 10 in an idle state or an inactive state receives a paging message at a paging occasion (PO), which is a period of a predetermined period, by discontinuous reception (DRX). A PO is associated with a paging frame (PF) having a predetermined period. The PF may, for example, consist of radio frames identified by a specific number (eg, System frame number (SFN)). A PO may be composed of, for example, a subframe, a slot, or a predetermined number of symbols.

Here, the radio frame may consist of 10 subframes, and one subframe may be 1 ms. A slot is a time unit based on numerology (eg, Subcarrier spacing (SCS)), eg, one slot may equal one subframe if SCS = 15 kHz. One slot may include a predetermined number of symbols (eg, 14 symbols).

For example, in the terminal 10, PFs may be set with a cycle determined based on the DRX cycle (hereinafter referred to as "paging cycle"), and one PO may be set for each PF. That is, the PO may be set in the terminal 10 in the paging cycle. A PO may contain one or more PDCCH monitoring opportunities. In the following, PO is exemplified as a paging period, but it is of course not limited to this, and other terms corresponding to PF or paging period may be used.

The terminal 10 monitors a search space set (eg, Type2-PDCCH CSS set) set by a higher layer parameter (eg, RRC IE "pagingSearchSpace") to obtain a specific RNTI (eg, paging (P)-RNTI) CRC-scrambled DCI (hereinafter also referred to as “paging DCI”) may be detected. The terminal 10 receives the paging message via the PDSCH scheduled using the paging DCI. Here, information indicating the specific RNTI (for example, P-RNTI) may be set in the terminal 10 by higher layer signaling.

Also, the terminal 10 may receive a short message transmitted by the paging DCI. Thus, the paging DCI is used for scheduling the PDSCH used for paging message transmission and/or short message transmission.

(TRS)
Terminal 10 is under study to perform time/frequency synchronization using TRS. For example, a terminal 10 in an idle or inactive state will, in principle, be in a sleep state with reduced power consumption between POs by DRX, but for a predetermined period before the next PO, for time/frequency synchronization. A wake-up state is entered. Specifically, it is assumed that the terminal 10 is in the deep sleep state from the previous PO to the predetermined period, and is in the micro sleep state after the predetermined period until the next PO.

Here, the deep sleep state is a state in which power consumption is further reduced than the micro sleep state. For example, when performing time/frequency synchronization using a TRS arranged at a time position closer to the next PO than an SS burst, compared to performing time/frequency synchronization using the SS burst, The period of the deep sleep state of the terminal 10 can be lengthened. Therefore, it is expected that the power consumption of the terminal 10 will be reduced by time/frequency synchronization using TRS.

Here, the TRS is composed of, for example, a channel state information reference signal (CSI-RS), but is not limited to this. TRS may also be referred to as CSI-RS, non-zero power CSI-RS (Non zero power-CSI-RS: NZP-CSI-RS), TRS/CSI-RS, reference signal, or the like.

The use of TRS may be, for example, at least one of the time/frequency synchronization, tracking, path delay spread, Doppler spread estimation, and loop convergence. Tracking is to track and/or compensate for time and/or frequency variations of the local oscillator of terminal 10 . The TRS can be any signal used for the above applications. Also, when the TRS is configured in the terminal 10, the terminal 10 can achieve time/frequency synchronization without referring to the SS burst.

The above resources for TRS (hereinafter, "TRS resources" are, for example, one or more resources for NZP-CSI-RS (hereinafter, "NZP-CSI-RS resources") set (hereinafter, "NZP -CSI-RS resource set"). The TRS resource is a predetermined number of slots in a predetermined period (hereinafter referred to as "TRS period", for example, 10, 20, 40 or 80ms period), a predetermined number A predetermined periodic period (eg, the predetermined number of slots) containing TRS resources is also called a TRS occurrence, a TRS/CSI-RS opportunity, and so on.

The terminal 10 receives information (hereinafter referred to as "TRS resource/opportunity information") regarding TRS resources and/or TRS opportunities (hereinafter referred to as "TRS resources/opportunities"). Terminal 10 may configure TRS resources/opportunities based on TRS resource/opportunity information from base station 20 .

Note that the TRS resource/opportunity information for the terminal 10 in the idle or inactive state may be at least part of the TRS resource/opportunity information for the terminal 10 in the connected state. TRS resource/opportunity information for terminal 10 in connected state (for example, RRC IE 'NZP-CSI-RS ResourceSet', RRC IE 'CSI-ResourceConfig', etc.) is an RRC message (for example, RRC setup for establishing an RRC connection). message (RRCSetup message) or an RRC reconfiguration message (RRCReconfiguration message) that reconfigures the RRC connection.

On the other hand, TRS resource/opportunity information for idle or inactive terminals 10 may be system information (eg, SIB1 or SIBx) and/or RRC messages (eg, RRC may be included in release messages (such as RRCRelease message). For example, the TRS resource/opportunity information for terminals 10 in an idle or inactive state includes information on TRS power (e.g., powerControlOffsetSS indicating TRS power offset with respect to SSS), information on TRS scrambling ID (scramblingID), Information on the time domain resource to which the TRS is mapped (for example, firstOFDMSymbolInTimeDomain indicating the first symbol for TRS), information on the frequency domain resource to which the TRS is mapped (for example, startingRB indicating the starting resource block of TRS, resource block of TRS nrofRBs, etc.) may be included.

In addition, the TRS resource/opportunity information for terminals 10 in an idle or inactive state may include information on Quasi Co-Location (QCL), and an SSB index may be set. That is, the terminal 10 may identify the pseudo collocation relationship between the TRS transmitted in the corresponding TRS resource/opportunity and the SSB by setting the index of the SSB as the TRS resource/opportunity information. Here, pseudo-colocation assumes that the large-scale properties of one signal (e.g., TRS) are the same in whole or in part as those of another signal (e.g., SSB). You can show that you get For example, when two antenna ports are pseudo-colocated, the signal (or channel) transmitted at one antenna port is estimated from the signal (or channel) transmitted at another antenna port. You can show that you get Here, for example, the wide area characteristics may include Doppler spread, Doppler shift, delay spread, average gain, and/or average delay. good.

Here, the SSB index set as the information about the pseudo collocation may be the index of the SSB (also called Cell-Defining SSB) related to SIB1. That is, when information about pseudo collocation is configured for the terminal 10 as TRS resource/opportunity information for the terminal 10 in idle or inactive state, an index of SSBs associated with SIB1 may be configured. Based on the index of the SSB associated with SIB1 set by the base station 20, the terminal 10 determines that the TRS transmitted in the corresponding TRS resource/opportunity and the SSB are pseudo collocations (a relationship of pseudo collocations ) can be considered. Here, SIB1 may be referred to as RMSI (Remaining Minimum System Information).

Also, at least one parameter used for configuring TRS resources/opportunities for idle or inactive terminals 10 may be predetermined in the specification. The parameters are, for example, information on BWP (e.g., bwp-id indicating BWP ID), information on TRS resources in the time domain (e.g., resourceType indicating aperiodic, semi-persistent, or periodic), information on repetition ( For example, repetition that indicates repetition on or off), aperiodicTriggeringOffset that indicates the time offset between the aperiodic TRS trigger and the TRS resource, the antenna port of all NZP CSI-RS resources in the CSI-RS resource set are the same trs-Info indicating that, information on TRS power (eg, powerControlOffset indicating PDSCH power offset for NZP-CSI-RS), information on the number of antenna ports for TRS (eg, nrofPorts indicating the number of ports), time domain Information on resources (e.g., firstOFDMSYmbolInTimeDomain2 indicating time domain allocation within a resource block), cdm-Type indicating the type of TRS code division multiplexing (CDM), information on the density of TRS resources (e.g., density) It may be at least one. As mentioned above, the TRS here may be rephrased as NZP CSI-RS or the like.

In addition, the TRS resource/opportunity information may include parameters commonly used for configuring multiple TRS resources/opportunities and/or parameters used independently. Each of the multiple TRS resources/opportunities may be indexed. For example, an index may be provided for each parameter (eg, set of parameters) that is used independently to configure multiple TRS resources/opportunities. That is, parameters that are commonly used to configure multiple TRS resources/opportunities may not be indexed. Thus, TRS resources/opportunities may be controlled based on higher layer parameters (eg, RRC parameters and/or MAC CE, etc.) and/or physical layer parameters (eg, DCI format, etc.).

　Consideration is underway to signal from the base station 20 to the terminal 10 the instruction information regarding the availability of TRS in the TRS resource/opportunity as described above (hereinafter referred to as "TRS availability instruction"). It should be noted that TRS availability can be interchanged with TRS transmission availability on a TRS resource/opportunity, and the like. Also, hereinafter, "TRS is actually transmitted or not (from base station 20)" can be rephrased as "TRS (terminal 10) is available or not available".

The TRS availability indication consists of a predetermined number of bits, a first value of which (eg, '1') indicates that the TRS is available (i.e., actually transmitted from base station 20). and a second value of that bit (eg, '0') may indicate that the TRS is not available (ie not actually transmitted from base station 20). A predetermined number of bits that make up the TRS availability indication may also indicate whether TRS is available (i.e., actually transmitted from base station 20) on a particular TRS resource/opportunity. good. For example, if the TRS resources are configured in the NZP-CSI-RS resource set including NZP-CSI-RS resources #0 to #3, the first bit value (eg, '000') indicates that the NZP-CSI- A second bit value (eg, '001' to '110', etc.) indicating that no TRS is transmitted in the entire RS resource set is part of the NZP-CSI-RS resource set, and the second bit Indicates that the TRS is transmitted on the NZP-CSI-RS resource indicated by the value, and a third bit value (eg, '111') indicates that the TRS is transmitted on the entire NZP-CSI-RS resource set. may

Also, for example, the base station 20, the value set as the TRS availability indication (eg, "000", "001" to "110", etc., and / or each of "111") and the NZP-CSI-RS The association with resource sets may be configured using higher layer signaling such as RRC messages. Here, #0 to #3 in NZP-CSI-RS resources #0 to #3 may correspond to indices given to TRS resources/opportunities. For example, as described above, each of the parameters (e.g., sets of parameters) that are used independently to configure multiple TRS resources/opportunities are indexed and correspond to TRS availability indications (or bit values). Each of a plurality of TRS resources/opportunities may be identified by indicating the index as . That is, the terminal 10, a parameter commonly used for setting a plurality of TRS resources / opportunities, and a TRS availability indication (or bit value) based on the parameter of the TRS resource / opportunity corresponding to the index indicated , may identify TRS resources/opportunities. Terminal 10 may also determine TRS availability on the identified TRS resource/opportunity based on the TRS availability indication (or bit value).

Alternatively, the TRS availability indication may indicate that TRS is available (that is, actually transmitted from base station 20). For example, the TRS availability indication is notified (or set to true) to the terminal 10 only when the TRS is actually transmitted from the base station 20 in the TRS resource/opportunity, and the TRS availability indication is not transmitted when the TRS is not actually transmitted. may not be notified to the terminal 10 . Conversely, the TRS availability indication may be notified to the terminal 10 only when the TRS is not actually transmitted.

Physical layer (L1)-based signaling (hereinafter referred to as “L1 signaling”) or RRC layer signaling (hereinafter referred to as “RRC signaling”) may be used for such TRS availability indication signaling. .

When using L1 signaling, the TRS availability indication may be the value of a predetermined field in DCI, or a specific signal (eg, SSB or TRS, etc.) or a specific sequence of such specific signals. The DCI including the TRS availability indication may be the DCI used for scheduling the PDSCH that carries the paging message (also referred to as "paging DCI"), or may be used for paging early indication (PEI). field (also called "PEI DCI"), for example, paging DCI and/or PEI DCI may be a specific RNTI configured using higher layer signaling such as RRC messages (e.g., P- RNTI) may be CRC scrambled.

The PEI is instruction information regarding paging targets in the PO. Based on the PEI (or based on whether or not the PEI is detected), the terminal 10 determines whether the terminal 10 or the group (or subgroup) to which the terminal 10 belongs is a paging target in the PO. do. The terminal 10 can reduce power consumption by skipping PDCCH monitoring and/or reception and/or decoding of paging messages for POs not targeted for paging. Note that the PEI is not limited to the value of a predetermined field of DCI, but may be a specific signal (eg, SSB or TRS) or a specific sequence of the specific signal. This particular signal may be used as a TRS availability indication.

When using RRC signaling, the TRS availability indication is the value of a parameter or IE included in system information (such as SIB1 or SIBx other than SIB1) or an RRC message (such as an RRC release message used to release an RRC connection). may be

The period during which the TRS availability indication as described above is considered valid (hereinafter referred to as "validity time") may be defined in advance by specifications. Alternatively, information about the valid period (hereinafter referred to as “valid period information”) may be signaled from the base station 20 to the terminal 10 . The lifetime information may be included, for example, in system information, RRC messages, or DCI (eg, the paging DCI or PEI DCI described above). The validity period may be indicated by the number of predetermined time units (e.g., radio frames, slots, subframes, symbols, etc.), may be indicated by time (e.g., milliseconds, etc.), or may be indicated by the number of paging cycles. , PO or the number of DRX cycles. If the terminal receives a TRS availability indication within the validity period, the terminal may not reacquire another TRS availability indication within the validity period.

The validity period may be controlled using a timer (hereinafter referred to as "validity timer"). The valid timer may, for example, be started based on detection of TRS availability indication, may be started based on detection of system information, paging DCI or PEI DCI, SSB, SS burst or It may be initiated based on the PO. The validity timer may expire when a period predetermined by the specification or a period indicated by validity period information elapses. Terminal 10 may assume that TRS is not available on the TRS resource/opportunity in question if no TRS availability indication is received by the expiration of the validity timer.

　Figs. 3(A) and 3(B) are diagrams showing an example of a TRS availability indication and a validity period according to this embodiment. For example, in FIGS. 3A and 3B, the deep sleep state is set from the end timing T0 of the previous PO to the start timing T1 of receiving the SS burst, and from the end timing T3 of the SS burst to the start timing T4 of the next PO. Until then, the micro-sleep state is assumed except for the TRS availability indication and TRS reception periods. Timings T5 to T9 are the same as timings T0 to T4. Note that FIGS. 3A and 3B are merely examples, and the period during which the terminal 10 is in the deep sleep state and/or the micro sleep state can be changed as appropriate.

For example, in FIG. 3(A), the TRS availability indication is included in the PEI DCI. The terminal 10 detects the PEI DCI through monitoring at PDCCH monitoring opportunities configured for PEI. The terminal 10 determines whether TRS is transmitted before the subsequent PO based on the TRS availability indication in the PEI DCI. For example, the terminal 10 determines, based on the PEI DCI detected at timing T2, that TRS will be transmitted on the TRS resource/opportunity before the next PO. On the other hand, the terminal 10 determines, based on the PEI DCI detected at timing T8, that no TRS will be transmitted on the TRS resource/opportunity before the next PO.

As shown in FIG. 3(A), the effective period of the TRS availability indication indicating that the TRS is available is from the detection timing of the PEI DCI including the TRS availability indication to the start timing of the next PO. good. Note that in FIG. 3A, the timer may be started at the PEI DCI detection timing T2, and stopped or expired at the next PO start timing T4.

On the other hand, FIG. 3(B) differs from FIG. 3(A) in that the TRS availability indication is included in the paging DCI. In FIG. 3(B), the terminal 10 may operate by replacing PEI DCI in FIG. 3(A) with paging DCI. As shown in FIG. 3B, the effective period of the TRS availability indication may be from the end timing of the PO that detected the paging DCI including the TRS availability indication to the start timing of the next PO. According to the TRS availability indication using paging DCI, it is possible to flexibly change whether to transmit TRS in the configured TRS resources even if PEI is not transmitted.

FIGS. 4A and 4B are diagrams showing other examples of TRS availability indications and validity periods according to this embodiment. FIGS. 4A and 4B differ from FIGS. 3A and 3B in that the validity period of the TRS availability indication spans one or more POs.

FIG. 4(A) will explain the TRS availability indication included in the paging DCI, focusing on the differences from FIG. 3(B). Note that the validity period over one or more POs can also be applied to the TRS availability indication using the PEI described in FIG. 3(A). For example, in FIG. 4A, the validity period of the TRS availability indication may be 4 paging cycles. For example, as shown in FIG. 4A, when paging DCI including a TRS availability indication is detected in a certain PO, the TRS availability indication is TRS in the TRS resource set for 4 paging cycles from the PO. may indicate whether or not is sent.

FIG. 4(B) shows an example of a TRS availability indication in system information (eg, SIB1 or SIBx). Terminal 10 may determine whether TRS is transmitted on TRS resources configured before each PO based on the availability indication in the system information. According to the TRS availability indication using system information, it is suitable for the case where the valid period is relatively long.

　In addition, in FIGS. 3 and 4, the PDCCH monitoring opportunity for DCI used for TRS availability indication may be determined based on the time position of at least one of the SS burst, the SS burst set, and the PO. For example, the PDCCH monitoring occasion may be determined based on the time position and the time offset for the time position. The time offset may be based on the subcarrier spacing of the SSB or Bandwidth part (BWP).

(TRS related operation)
As described above, by notifying the terminal 10 of the TRS availability indication and/or providing a valid period for the TRS availability indication, it is possible to control whether or not to actually transmit the TRS in the TRS resource/period. When doing so, it is desirable to appropriately control operations related to TRS (hereinafter referred to as “TRS-related operations”). In the following, (1) when performing reselection of the cell where the terminal 10 camps on (hereinafter referred to as "cell reselection"), (2) when the valid timer is running, (3) using system information TRS related operations are described in the case where the TRS availability is indicated by the

In the following, SIBx other than SIB1 (where x is an SIB type identifier such as 2, 3, 4, etc.) will be described as an example of system information, but the system information in this embodiment is not limited to SIBx. Also, although the terminal 10 is assumed to be in an idle state or an inactive state below, this does not preclude application in a connected state.

(1) TRS-related operation during cell reselection TRS-related operation of the terminal 10 during cell reselection will be described. The terminal 10 receives SIBx during cell selection or cell reselection. It is assumed that the SIBx is either area-specific or cell-specific. When performing cell reselection between cells in the same area, terminal 10 does not need to re-receive area-specific SIBx. The SIBx used for TRS resource/opportunity configuration is assumed to be either area-specific or cell-specific.

Therefore, when reselecting a cell to camp on, the terminal 10 can use TRS in the TRS resource/opportunity based on whether the SIBx used for setting the TRS resource/opportunity is area-specific. Controls the validity timer for the validity period of the TRS availability indication.

FIG. 5 is a diagram showing an example of TRS-related operations during cell reselection according to this embodiment. For example, in FIG. 5, cells #0 and #1 are included in area #1, and cells #2 and #3 are included in area #2. In FIG. 5, terminal 10 camps on cell #0 and receives area #1 specific SIBx from base station 20 forming cell #0. Terminal 10 may configure the TRS resource/opportunity based on the TRS resource/opportunity information included in the SIBx.

Also, the terminal 10 camping on cell #0 receives the TRS availability indication. The TRS availability indication may be included in any of the area #1 specific SIBx, paging DCI, PEI DCI, TRS as PEI or RRC messages. The terminal 10 starts a valid timer for the TRS availability indication at timing T1.

For example, in FIG. 5, the terminal 10 reselects the cell #1 belonging to the same area #1 as the cell #0 at timing T2. Since the SIBx received in cell #0 is specific to area #1 and the reselected cell #1 belongs to the same area #1 as cell #0, terminal 10 does not stop the validity timer at timing T2. continue running the relevant TRS-related operations. Also, since terminal 10 receives SIBx specific to area #1 in cell #0, it is not necessary to receive SIBx again when cell #1 is reselected.

Also, in FIG. 5, terminal 10 reselects cell #2 belonging to area #2 different from cell #1 at timing T3. Since the reselected cell #2 belongs to the area #2 different from the area #1 to which the cell #1 belongs, the terminal 10 stops the validity timer at the timing T3 without waiting for the expiration at the timing T4. Note that stopping (stopping) the validity timer may be translated into resetting or discarding (discard).

When cell #2 is reselected, terminal 10 receives SIBx from base station 20 forming cell #2 because the area IDs to which cells #1 and #2 belong are different. In FIG. 5, it is assumed that the SIBx is specific to area #2, but the present invention is not limited to this. Terminal 10 may configure the TRS resource/opportunity based on the TRS resource/opportunity information included in the SIBx. The terminal 10 camping on the cell #2 may receive the TRS availability indication and start the valid timer of the TRS availability indication at timing T3. The validity timer expires at time T5, terminating the validity period of the TRS availability indication received in cell #2.

Thus, if the SIBx containing the TRS resource/opportunity information is area-specific, the terminal 10 resets the validity timer if cell reselection is performed between cells #0 and #1 belonging to the same area #1. continue without On the other hand, if the terminal 10 performs cell reselection between cells #1 and #2 belonging to different areas #1 and #2, respectively, it resets the validity timer. Therefore, even when the terminal 10 moves between cells belonging to the same area or between cells belonging to different areas, it is possible to appropriately control the valid period of the TRS availability indication.

FIG. 6 is a diagram showing another example of TRS-related operations during cell reselection according to this embodiment. For example, in cells #4 and #5 in FIG. 6, cell-specific SIBx shall be broadcast respectively. In FIG. 6, terminal 10 camps on cell #4 and receives SIBx unique to cell #4 from base station 20 forming cell #4. Terminal 10 may configure the TRS resource/opportunity based on the TRS resource/opportunity information included in the SIBx.

Also, the terminal 10 camping on cell #4 receives the TRS availability indication. The TRS availability indication may be included in any of the cell #4 specific SIBx, paging DCI, PEI DCI, TRS as PEI or RRC messages. The terminal 10 activates the validity timer of the TRS availability indication at timing T1. For example, in FIG. 6, the valid period is from timing T1 to T3.

In FIG. 6, terminal 10 reselects cell #5, which is different from cell #4, at timing T2. The terminal 10 stops the validity timer at timing T2 without waiting for the expiration at timing T3. Also, the terminal 10 receives SIBx specific to cell #5 and configures TRS resources/opportunities based on the TRS resource/opportunity information in the SIBx. The terminal 10 that camps on cell #5 may receive the TRS availability indication and start the validity timer of the TRS availability indication at timing T2. The validity timer expires at time T4, ending the validity period of the TRS availability indication received in cell #5.

As described above, the terminal 10 controls the validity timer of the TRS availability indication based on whether the SIBx containing the TRS resource/opportunity information is area-specific. Therefore, even when the terminal 10 moves between cells, it is possible to appropriately control the effective period of the TRS availability indication.

(2) TRS-Related Operation During Activation of Valid Timer Next, the operation of the terminal 10 when TRS transmission is stopped during activation of the valid timer will be described. The terminal 10 may use a valid timer to control the valid period of the TRS availability indication. For example, the terminal 10 may determine that the TRS availability indication is valid from the start of the validity timer to the expiration or stop of the validity timer (that is, while the validity timer is running). An operation in which TRS transmission is stopped for reasons such as the fact that there is no terminal in the connected state in the cell even while the valid timer is running is also assumed.

FIGS. 7(A) and (B) are diagrams showing an example of TRS operation during valid timer activation according to the present embodiment. In FIGS. 7(A) and (B), the TRS availability indication shall be included in, but not limited to, the paging DCI, higher layer signaling such as system information or RRC messages, or PEI DCI or It may be signaled to the terminal 10 using physical layer signaling such as a specific signal. Further, it goes without saying that the start timing of the valid timer is not limited to the illustrated one.

FIG. 7(A) shows an example in which the validity timer started at timing T1 expires at timing T2. As shown in FIG. 7A, terminal 10 detects paging DCI including a TRS availability indication (first indication information) indicating that TRS can be used at PDCCH monitoring opportunities in PO#0. The terminal 10 may start a valid timer in response to detection of the TRS availability indication, and determine the period until the valid timer expires as the valid period of the TRS availability indication. Based on the TRS availability indication, terminal 10 determines that TRS is available on the TRS resource/opportunity within the validity period.

Also, terminal 10 detects a paging DCI indicating that TRS is not available at the PDCCH monitoring opportunity in PO#4 after expiration of the validity timer. Terminal 10 determines that TRS is not available in TRS resources/opportunities based on the paging DCI.

FIG. 7(B) shows an example in which the valid timer started at timing T1 is stopped at timing T1'. As shown in FIG. 7B, terminal 10 receives a TRS availability indication (second indication information) indicating that TRS is not available at timing T1′ during activation of the valid timer. (A) is different. FIG. 7(B) will be described with a focus on differences from FIG. 7(A).

Terminal 10 detects a paging DCI containing a TRS availability indication indicating that TRS is not available at the PDCCH monitoring opportunity in PO#2 while the validity timer is running. Terminal 10 stops the validity timer upon detection of the TRS availability indication. Terminal 10 determines that TRS is not available in TRS resources/opportunities after stopping the timer. In this way, when the valid timer is stopped at timing T1', the terminal 10 may determine that the valid period of the TRS availability indication detected at PO#0 has expired without waiting for the expiration of the valid timer. .

Note that the TRS availability indication indicating that the TRS that is notified during activation of the valid timer is not available is a specific value of at least some bits of the reserved field of the paging DCI (for example, 2 bits out of 6 bits value "00").

As described above, when the TRS availability indication indicating that the TRS is not available is received while the validity timer for the validity period of the TRS availability indication indicating that the TRS is available is being activated, the terminal 10 receives the It may stop the validity timer and assume that no TRS is available on subsequent TRS resources/opportunities. As a result, the terminal 10 can operate properly even when the operation of the system side changes whether or not to transmit the TRS.

(3) TRS-related operation based on SIBx Next, the operation of the terminal 10 when indicating TRS availability using SIBx will be described. Specifically, (3.1) change operation of the instruction regarding the availability of TRS using SIBx, and (3.2) control operation of the effective period of the instruction regarding the availability of TRS using SIBx will be described. .

(3.1) Change operation of TRS availability indication using SIBx As described in FIG. (hereinafter referred to as “SI Change Notification”) and in the next update period, obtain the SI message containing the changed SIBx. The SI change notification is also called "SI change indication" or the like. For the SI change notification, for example, a short message in paging DCI may be used. The paging DCI may be monitored at each PO within the certain update period.

The terminal 10 may receive an SI message containing SIBx updated in the next update period based on the SI change notification detected in the previous update period. The update period may, for example, consist of a predetermined number of radio frames. The update period boundary may be determined, for example, based on the SFN and the number of radio frames that make up the update period.

By the way, it is desirable to be able to change whether or not TRS is actually transmitted in TRS resources/opportunities depending on various factors. For example, when overall system traffic increases, it is assumed that TRS overhead is reduced by not actually transmitting TRS on configured TRS resources/opportunities. On the other hand, when the traffic of the entire system decreases, it is assumed that the power consumption reduction effect of the terminal 10 is enhanced by actually transmitting the TRS in the set TRS resource/opportunity.

Thus, when it is changed whether or not TRS is actually transmitted in the TRS resource/opportunity, the problem is how to notify the terminal 10 of the change. Here, when the terminal 10 determines whether TRS is actually transmitted on the TRS resource/opportunity based on the TRS availability indication in SIBx, an update procedure for the SI message (hereinafter “SI update procedure”) is assumed to be used.

However, the SI update procedure does not assume that the value of the TRS availability indication in SIBx (or whether SIBx includes the TRS availability indication) is changed. Therefore, there is a possibility that the timing at which the TRS availability indication becomes effective and/or the validity period of the TRS availability indication cannot be appropriately controlled only by using the SI update procedure.

Therefore, if the TRS availability indication in SIBx modified by the SI update procedure indicates that TRS is actually transmitted on the TRS resource/opportunity, the terminal 10 may set the reference timing (hereinafter "reference timing )”) may be used to determine when the TRS availability indication becomes valid (ie, when the validity timer starts).

The reference timing may be, for example, the timing for the reception of SIBx containing the TRS availability indication indicating that the TRS is available, the timing for the reception of SIBx or SIB1 other than the SIBx, or the boundary of the update period. . The timing related to reception may be the start or end timing of a received radio frame, slot or symbol, or may be the start or end timing of a period used for reception (for example, SI window).

Also, the terminal 10 may determine the start timing of the valid timer based on the reference timing and the offset with respect to the reference timing. The offset may be defined by the number of slots, the number of radio frames, the number of hyper-radio frames, time (eg, milliseconds), integer multiples of paging cycles, integer multiples of DRX periods, or the like. The offset may be specified in advance or notified from the base station 20 . Also, the value of the offset may be 0, and the terminal 10 may determine the reference timing as the timing at which the TRS availability indication becomes valid.

Also, the terminal 10 may receive information about the offset (hereinafter referred to as "offset information") from the base station 20. The offset information may be included in SIBx containing the TRS availability indication, may be included in another SIBx, may be included in SIB1, or may be included in another RRC message. good.

FIG. 8 is a diagram showing an example of an SI update procedure according to this embodiment. For example, in FIG. 8, the TRS availability indication in SIBx indicates that TRS is actually transmitted on the TRS resource/opportunity, and if TRS is not actually transmitted, SIBx shall not contain the TRS availability indication. However, as noted above, it should be appreciated that a TRS availability indication may be included in SIBx indicating whether or not TRS is actually transmitted on the TRS resource/opportunity.

For example, in FIG. 8, the SIBx transmitted within the previous update period does not contain a TRS availability indication, indicating that no TRS is actually transmitted on the TRS resource/opportunity. On the other hand, if a TRS should actually send a trigger within the previous update period, the base station 20 sends an SI change notification in the SI message containing SIBx on the PO. When terminal 10 detects the SI change notification through PDCCH monitoring in PO, terminal 10 receives SIB1 in the next update period, and receives an SI message including changed SIBx based on SIB1. Although not shown, the terminal 10 may receive the MIB before the SIB1 after the boundary.

Also, the version information of SIBx in SIB1 in FIG. 8 (eg, RRC IE "valueTag") indicates v1 incremented by 1 from v0. Since the version information of SIBx in SIB1 (here, v1) does not match the version information of SIBx (here, v0) stored in terminal 10, terminal 10 acquires an SI message containing SIBx of v1. You may Terminal 10 determines that TRS is actually transmitted on the TRS resource/opportunity based on the TRS availability indication in SIBx for v1.

Also, in FIG. 8, the terminal 10 may use the boundary of the update period as the reference timing, and determine the timing at which the TRS availability indication becomes effective based on the reference timing and the offset. The terminal 10 may start the valid timer at the determined timing. The terminal 10 may determine the period from when the valid timer is started until the valid timer expires as the valid period of the TRS availability indication. The valid period may be defined as an integral multiple of the update period.

As shown in FIG. 8, the base station 20 stops transmitting TRS on the TRS resource/opportunity when the valid timer expires. Also, the base station 20 may stop reporting SIBx of v1. The base station 20 does not have to transmit the SI change notification even if it stops transmitting the TRS after the valid timer expires. That is, the base station 20 does not need to broadcast SIBx of v2 indicating that the TRS will not be transmitted after the valid timer expires. Moreover, version information of SIBx in SIB1 is not updated, and v1 may be maintained.

In FIG. 8, the boundary of the update period is used as the reference timing. It may be the timing related to the window, the timing related to the reception of SIB1, or the like.

As described above, even if the TRS availability indication in SIBx modified by the SI update procedure indicates that TRS is actually transmitted on the TRS resource/opportunity, the start timing of the valid timer and/or the TRS availability You have good control over how long instructions are valid.

(3.2) Validity period control operation using SIBx By the way, while the terminal 10 camping on a certain cell is activating the valid timer based on SIBx, another terminal 10 It is assumed that camp-on will start. In this case, when the valid timer expires, the base station 20 does not actually transmit the TRS in the TRS resource/opportunity, so between the terminals 10 belonging to the same cell, the expiration timing of the valid timer (that is, the TRS in SIBx The end timing of the validity period of the availability indication) must match.

Therefore, the base station 20 broadcasts information on the effective period of the TRS availability instruction (hereinafter referred to as "effective period information") based on the elapsed time from the start of the active timer. Generate information. The validity time information may be included in SIBx including the TRS availability indication, or may be included in other SIBs (eg, other SIBx or SIB1, etc.). For example, the validity time information may indicate how long the TRS availability indication is valid. Note that the elapsed time from the start of the activated valid timer may be rephrased as the remaining time until the valid timer expires.

The valid period information may indicate, for example, the remaining time until the expiration timing of the valid timer, and the remaining time may be updated based on the elapsed time from the start timing of the valid period. Alternatively, the validity period information may indicate, for example, the expiration timing of the validity timer, the number of the radio frame, the number of the hyper radio frame, or the like. That is, the validity period information may absolutely indicate the expiration timing of the validity timer. For example, lifetime information may be defined using Universal Time Coordinated (UTC) time to indicate when a TRS availability indication (eg, the contents of the TRS availability indication) will expire.

FIG. 9 is a diagram showing an example of control operation for the valid period of the TRS availability indication according to this embodiment. For example, in FIG. 9, it is assumed that the terminal 10A is camping on a certain cell and the validity timer indicating the validity period of the TRS availability indication in SIBx is being activated. In FIG. 9, the start timing of activation of the validity timer is equal to the end timing of reception of SIBx, but this is only an example and is not limited to this. As described above, the start timing may be determined based on the reference timing and the offset.

For example, in FIG. 9, the validity period information in SIBx indicates the remaining time until the validity timer expires. As shown in FIG. 9, when SIBx is broadcast at a predetermined cycle, the remaining time indicated by the valid period information included in each SIBx is determined based on the elapsed time from the start of the valid timer from the initial value. good too. For example, validity period information in SIBx received while the validity timer is not running indicates an initial value of 10 seconds. On the other hand, the validity period information in SIBx received while the validity timer is running may indicate a remaining time of 3 seconds based on the elapsed time from the initial value of 10 seconds.

In this way, the value indicated by the validity period information in SIBx may be updated based on the elapsed time from the start timing of the validity timer. As a result, even when the terminal 10B camps on the same cell as the terminal 10A while the valid timer of the terminal 10A is running, it is possible to avoid mismatching of the expiration timings of the valid timers between the terminals 10A and 10B.

It should be noted that, as shown in FIG. 9, the remaining time indicated by the validity period information in SIBx may be updated for each cycle of SIBx. The base station 20 may not transmit the SI change notification even if the valid period information in SIBx is updated. On the other hand, when extending the initial value (10 seconds in FIG. 9) indicated by the valid period information in SIBx, the base station 20 performs the SI update procedure based on the SI change notification, and the extended initial value is You may broadcast SIBx of v2 containing the effective period information to show.

FIG. 10 is a diagram showing another example of the control operation of the validity period of the TRS availability indication according to this embodiment. For example, in FIG. 10, the validity period information indicates SFN#128 as the expiration timing of the validity period. Other operations in FIG. 10 are as explained in FIG.

In this way, the validity period information in SIBx indicates the time at which the validity period expires or the index in units of time, so that it is not necessary to update sequentially based on the elapsed time from the start timing of the validity timer. Therefore, it is possible to avoid mismatching of expiration timings of valid timers between the terminals 10 without performing the updating operation of the valid period information in the base station 20 described with reference to FIG.

(Configuration of wireless communication system)
Next, the configuration of each device of the radio communication system 1 as described above will be described. Note that the following configuration is for showing the configuration required in the description of the present embodiment, and does not exclude that each device has functional blocks other than those illustrated.

<Hardware configuration>
FIG. 11 is a diagram showing an example of the hardware configuration of each device in the wireless communication system according to this embodiment. Each device in the wireless communication system 1 (for example, the terminal 10, the base station 20, the CN 30, etc.) includes a processor 11, a storage device 12, a communication device 13 that performs wired or wireless communication, an input device that receives various input operations, and various It includes an input/output device 14 for outputting information.

The processor 11 is, for example, a CPU (Central Processing Unit) and controls each device within the wireless communication system 1 . The processor 11 may read and execute the program from the storage device 12 to execute various processes described in this embodiment. Each device within the wireless communication system 1 may be configured with one or more processors 11 . Each device may also be called a computer.

The storage device 12 is composed of storage such as memory, HDD (Hard Disk Drive) and/or SSD (Solid State Drive). The storage device 12 may store various types of information necessary for execution of processing by the processor 11 (for example, programs executed by the processor 11, etc.).

The communication device 13 is a device that communicates via a wired and/or wireless network, and may include, for example, network cards, communication modules, chips, antennas, and the like. Further, the communication device 13 may include an amplifier, an RF (Radio Frequency) device that performs processing related to radio signals, and a BB (BaseBand) device that performs baseband signal processing.

For example, the RF device generates a radio signal to be transmitted from the antenna A by performing D/A conversion, modulation, frequency conversion, power amplification, etc. on the digital baseband signal received from the BB device. Further, the RF device generates a digital baseband signal by performing frequency conversion, demodulation, A/D conversion, etc. on the radio signal received from the antenna, and transmits the digital baseband signal to the BB device. The BB device performs a process of converting a digital baseband signal into a packet and a process of converting the packet into a digital baseband signal.

The input/output device 14 includes input devices such as keyboards, touch panels, mice and/or microphones, and output devices such as displays and/or speakers.

The hardware configuration described above is just an example. Each device in the wireless communication system 1 may omit part of the hardware shown in FIG. 11, or may include hardware not shown in FIG. Also, the hardware shown in FIG. 11 may be configured by one or a plurality of chips.

<Functional block configuration>
≪Device≫
FIG. 12 is a diagram showing an example of a functional block configuration of a terminal according to this embodiment. As shown in FIG. 12 , terminal 10 includes receiver 101 , transmitter 102 , and controller 103 .

All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 can be realized using the communication device 13. All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 and the control unit 103 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium. The storage medium storing the program may be a non-transitory computer readable medium. The non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.

The receiving unit 101 receives the downstream signal. Also, the receiving section 101 may receive information and/or data transmitted via a downlink signal. Here, "receiving" may include, for example, performing processing related to reception such as at least one of receiving, demapping, demodulating, decoding, monitoring, and measuring radio signals. The downlink signal may include, for example, at least one of PDSCH, PDCCH, downlink reference signal, synchronization signal, PBCH, and the like.

Receiving section 101 monitors PDCCH candidates in the search space to detect DCI. Receiving section 101 receives downlink user data and/or higher layer control information (eg, Medium Access Control Element (MAC CE), RRC message, NAS message, etc.) via PDSCH scheduled using DCI. may

Specifically, the receiving unit 101 receives SIBx (system information). Also, the receiving unit 101 may receive indication information indicating that the TRS can be used in the TRS resource/period (resource and/or period) (see (1) and (2) above, for example). The indication information may be included in SIBx, paging DCI or PEI DCI.

Further, the receiving unit 101 may receive indication information (second indication information) indicating that the TRS is available in the TRS resource/opportunity while the valid timer is running (for example, the (2)). The indication information may be included in the paging DCI, or may be a specific value of at least some bits of the reserved field of the paging DCI.

Also, the receiving unit 101 may receive SIBx including indication information indicating that TRS is available in the TRS resource/opportunity (see (3) above, for example). The receiving unit 101 may receive the SIBx in the next update period based on the SI change notification (system information change notification) detected in the previous update period (see FIG. 8, for example). Also, the receiving section 101 may receive offset information with respect to the reference timing.

Also, the receiving unit 101 may receive validity period information regarding the validity period of the indication information indicating that the TRS is available in the TRS resource/opportunity. The validity period information may indicate the remaining time until expiration of the validity timer, and the remaining time may be updated based on the elapsed time from the start timing of the validity period (eg, FIG. 9). Alternatively, the validity period information may indicate the time of expiration timing, the radio frame number, or the hyper radio frame number (eg, FIG. 10).

The transmission unit 102 transmits an upstream signal. Also, the transmitting section 102 may transmit information and/or data transmitted via an uplink signal. Here, "transmitting" may include performing processing related to transmission, such as at least one of encoding, modulation, mapping, and transmission of radio signals. The uplink signal is, for example, an uplink shared channel (e.g., Physical Uplink Shared channel: PUSCH), a random access preamble (e.g., Physical Random Access Channel: PRACH), at least an uplink reference signal, etc. may contain one.

Transmitting section 102 may transmit uplink user data and/or higher layer control information (eg, MAC CE, RRC messages, etc.) via PUSCH scheduled using the DCI received by receiving section 101. good.

The control unit 103 performs various controls in the terminal 10.

For example, the control unit 103 may configure TRS resources/opportunities based on SIBx or RRC messages.

Further, the control unit 103, when performing reselection of the cell to camp on, based on whether SIBx is area-specific, may control a valid timer related to the valid period of the TRS availability indication (for example, (1) above, see FIGS. 5 and 6). Specifically, when SIBx is area-specific, control section 103 may continue the valid timer if cell reselection is performed between cells belonging to the same area while the valid timer is running. Further, when SIBx is area-specific, control section 103 may stop the valid timer if cell reselection is performed between cells belonging to different areas while the valid timer is running. Also, if SIBx is not area-specific, control section 103 may stop the valid timer if cell reselection is performed between cells while the valid timer is running.

Also, the control unit 103 controls a validity timer regarding the validity period of the TRS availability indication. Specifically, the control unit 103 starts a timer related to the validity period of the first indication information indicating that the TRS is available in the TRS resource/opportunity (for example, (2) above, FIG. 7A) reference). Also, the control unit 103 stops the valid timer if the receiving unit 101 receives the second indication information indicating that the TRS is not available in the TRS resource/opportunity while the valid timer is running. (See (2) above and FIG. 7B, for example).

Specifically, when the control unit 103 detects a DCI (for example, paging DCI) that is CRC scrambled by a specific RNTI in the PDCCH monitoring opportunity in the PO, based on the second indication information in the DCI, A valid timer may be stopped (see, for example, FIG. 7B). Also, the control unit 103 may determine that the TRS is not transmitted in the TRS resource/opportunity after a predetermined timing after the valid timer is stopped (see FIG. 7B, for example).

In addition, the control unit 103 may determine the start timing of the valid timer using the timing related to the reception of SIBx, the timing related to the reception of system information other than the system information, or the boundary of the update period as a reference timing (for example, the above ( 3), see FIG. 8). The control unit 103 may determine the start timing of the valid timer based on the reference timing and the offset indicated by the offset information. Also, the control unit 103 may determine the expiration timing of the valid timer based on the valid period information.

≪Base station≫
FIG. 13 is a diagram showing an example of the functional block configuration of the base station according to this embodiment. As shown in FIG. 13, the base station 20 includes a receiver 201, a transmitter 202, and a controller 203. FIG.

All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 can be realized using the communication device 13. All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 and the control unit 203 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium. The storage medium storing the program may be a computer-readable non-temporary storage medium. The non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.

The receiving unit 201 receives the upstream signal. Also, the receiving section 201 may receive information and/or data transmitted via the uplink signal.

The transmission unit 202 transmits the downlink signal. Also, the transmitting section 202 may transmit information and/or data transmitted via the downlink signal. Specifically, transmitting section 202 transmits SIBx (system information). Also, the transmitting unit 202 may transmit indication information indicating that the TRS can be used in the TRS resource/period (resource and/or period).

In addition, while the valid timer is running, the transmitting unit 202 may transmit indication information (second indication information) indicating that the TRS is available in the TRS resource/opportunity (for example, the (2)).

Also, the transmitting unit 202 may transmit SIBx including indication information indicating that TRS is available in the TRS resource/opportunity (see (3) above, for example). The transmitter 202 may transmit the SIBx in the next update period based on the SI change notification (system information change notification) detected in the previous update period (see FIG. 8, for example). Also, the transmitting section 202 may transmit offset information with respect to the reference timing. Also, the transmitting unit 202 may transmit valid period information regarding the valid period.

The control unit 203 performs various controls in the base station 20. For example, the control unit 203 may control whether or not to transmit TRS on a TRS resource/opportunity based on various factors. Part of the information transmitted from the transmission unit 202 of the base station may be transmitted by a transmission unit within the device on the core network 30 .

(supplement)
Various signals, information and parameters in the above embodiments may be signaled in any layer. That is, the above-mentioned various signals, information, parameters are higher layers (eg, Non Access Stratum (NAS) layer, RRC layer, MAC layer, etc.), lower layers (eg, physical layer), etc. Signals, information, may be replaced by parameters. Further, the notification of the predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, by not notifying the information or using other information).

Also, the names of various signals, information, parameters, IEs, channels, time units, and frequency units in the above embodiments are merely examples, and may be replaced with other names. For example, a slot may be named any unit of time having a predetermined number of symbols. Also, RB may be any name as long as it is a frequency unit having a predetermined number of subcarriers. Also, the "first .

In addition, the use of the terminal 10 in the above embodiment (for example, for RedCap, IoT, etc.) is not limited to those illustrated, as long as it has similar functions, any use (for example, eMBB, URLLC, Device-to- Device (D2D), Vehicle-to-Everything (V2X), etc.). Also, the format of various information is not limited to the above embodiment, and may be appropriately changed to bit representation (0 or 1), true/false value (Boolean: true or false), integer value, character, or the like. Also, singularity and plurality in the above embodiments may be interchanged.

The embodiments described above are for facilitating understanding of the present disclosure, and are not for limiting interpretation of the present disclosure. Flowcharts, sequences, elements included in the embodiments, their arrangement, indexes, conditions, and the like described in the embodiments are not limited to those illustrated and can be changed as appropriate. Moreover, it is possible to partially replace or combine at least part of the configurations described in the above embodiments.

Reference Signs List 1 wireless communication system 20 base station 30 core network 101 receiver 102 transmitter 103 controller 201 receiver 202 transmitter 203 controller 11 processor 12... storage device, 13... communication device, 14... input/output device

Claims (8)

1. a receiving unit for receiving system information including indication information indicating that the tracking reference signal is available on resources and/or opportunities configured for the tracking reference signal;
   a control unit that determines the start timing of a timer related to the effective period of the instruction information, using the timing related to the reception of the system information, the timing related to the reception of the system information other than the system information, or the boundary of an update period as a reference timing;
   terminal with
2. The receiving unit receives the system information including the instruction information in the next update period based on the system information change notification detected in the previous update period.
   A terminal according to claim 1 .
3. The receiving unit receives information about an offset with respect to the reference timing,
   The control unit determines start timing of the timer based on the reference timing and the offset.
   The terminal according to claim 1 or 2.
4. The valid period from the start of the timer to the expiration of the timer is defined as an integral multiple of the update period,
   A terminal according to any one of claims 1 to 3.
5. the system information includes information about the validity period of the indication information;
   The control unit determines the expiration timing of the timer based on the information about the valid period,
   A terminal according to any one of claims 1 to 4.
6. The information on the valid period indicates the remaining time until the expiration timing,
   the remaining time is updated based on the elapsed time from the start timing of the valid period;
   A terminal according to claim 5 .
7. The information about the valid period indicates the time of the expiration timing, the number of the radio frame, or the number of the hyper radio frame.
   A terminal according to claim 5 .
8. receiving system information including indication information indicating that the tracking reference signal is available on resources and/or opportunities configured for the tracking reference signal;
   determining the start timing of a timer relating to the effective period of the instruction information, using the timing relating to the reception of the system information, the timing relating to the reception of the system information other than the system information, or the boundary of the update period as a reference timing;
   A wireless communication method for a terminal having

Images