Terminal, base station, and terminal communication method

JPWO2023080131A5Pending Publication Date: 2024-11-12
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023558037
Authority / Receiving Office
JP · JP
Patent Type
Applications
Priority Date
2022-11-01
Filing Date
2022-11-01
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in appropriately controlling the monitoring of Paging Early Indication (PEI) DCI and paging DCI across different terminal states (idle, inactive, and connected), leading to inefficient power consumption and potential unnecessary monitoring by non-targeted terminals.

Method used

A terminal with a receiving unit to configure search spaces for monitoring downlink control information, including PEI information, based on its state, allowing controlled monitoring of PEI DCI and paging DCI, thereby optimizing power usage and reducing unnecessary monitoring.

Benefits of technology

This solution enables efficient power management by ensuring that terminals only monitor PEI DCI and paging DCI when necessary, reducing waste and maintaining compatibility with existing operations, especially in connected states where paging is not applicable.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The terminal according to the present disclosure is provided with: a reception unit which receives first downlink control information (PEI DCI) that includes information relating to paging in one or more paging opportunities detected by monitoring of a first search space set; and a control unit which controls monitoring of a second search space set of second downlink control information (paging DCI) the includes information relating to short messages and / or information relating to scheduling in downlink shared channels that transmit paging messages in the paging opportunities on the basis of the first downlink control information when in an idling or inactive state.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal, base station and wireless communication method CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on and claims the benefit of priority from Japanese Patent Application No. 2021-179764, filed on November 2, 2021, the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to a terminal, a base station, and a wireless communication method.

[0003] The Third Generation Partnership Project (3GPP), an international standardization organization, has specified Release 15 of New Radio (NR), a fifth generation (5G) RAT, as a successor to Long Term Evolution (LTE), a 3.9th generation radio access technology (RAT), and LTE-Advanced, a fourth generation RAT (see, for example, Non-Patent Document 1). LTE and / or LTE-Advanced are also called Evolved Universal Terrestrial Radio Access (E-UTRA).

[0004] 3GPP TS 38.300 V15.2.0 (2018-06)

[0005] In NR, a terminal monitors a downlink shared channel (e.g., a Physical Downlink Shared Channel (PDSCH)) that transmits paging messages during a predetermined period called a paging occasion (PO), etc., for downlink control information (DCI) (hereinafter referred to as "paging DCI", also referred to as "second downlink control information", etc.) that includes information regarding the scheduling of the downlink shared channel and / or information regarding short messages, and can receive paging messages and / or short messages based on the detected paging DCI.

[0006] Currently, 3GPP is considering notifying a terminal of information related to paging in one or more POs (hereinafter referred to as "Paging Early Indication (PEI) information") and controlling terminal operation in the PO based on the PEI information. Also, it is also considering including the PEI information in DCI transmitted on a downlink control channel (e.g., PDCCH).

[0007] However, when a DCI including PEI information (hereinafter referred to as "PEI DCI", also referred to as "first downlink control information", etc.) is newly introduced, there is a risk that a terminal may not be able to appropriately control monitoring of the PEI DCI and / or paging DCI depending on the state of the terminal (e.g., idle state, inactive state, or connected state). One object of the present disclosure is to provide a terminal, a base station, and a wireless communication method that are capable of appropriately controlling monitoring of the PEI DCI and / or paging DCI depending on the state of the terminal.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives information regarding the configuration of a search space set that is configured for monitoring downlink control information including paging early indication (PEI) information, and a control unit that controls whether or not to monitor the downlink control information including the PEI information in the search space set that is configured based on the information regarding the configuration, based on whether the terminal is in an idle state, an inactive state, or a connected state.

[0009] According to one aspect of the present disclosure, monitoring of PEI DCI and / or paging DCI can be appropriately controlled depending on the state of the terminal.

[0010] FIG. 1 is a diagram illustrating an example of an overview of a wireless communication system according to this embodiment. FIG. 2 is a diagram illustrating an example of a PO according to this embodiment. FIGS. 3A and 3B are diagrams illustrating an example of DRX control according to this embodiment. FIG. 4 is a diagram illustrating an example of the relationship between a PEI-O and a PO according to this embodiment. FIGS. 5A and 5B are diagrams illustrating an example of first monitoring control of PEI DCI and paging DCI according to this embodiment. FIGS. 6A-6C are diagrams illustrating examples of formats of PEI DCI and paging DCI used in the first monitoring control of this embodiment. FIGS. 7A and 7B are diagrams illustrating an example of second monitoring control of PEI DCI and paging DCI according to this embodiment. FIGS. 8A and 8B are diagrams illustrating examples of formats of PEI DCI and paging DCI used in the second monitoring control of this embodiment. FIG. 9 is a diagram illustrating an example of reception types related to the first and second monitoring controls of this embodiment. FIG. 10 is a diagram illustrating an example of combinations of reception types for each state of a terminal 10 related to the first monitoring control of this embodiment. Fig. 11 is a diagram showing an example of a combination of reception types for each state of the terminal 10 related to the second monitoring control of this embodiment. Fig. 12 is a diagram showing an example of the number of PDCCH candidates in the PEI search space according to this embodiment. Fig. 13 is a diagram showing an example of a specification change related to the setting of the PEI search space and the paging search space according to this embodiment. Fig. 14 is a diagram showing an example of the hardware configuration of each device in the wireless communication system according to this embodiment. Fig. 15 is a diagram showing an example of the functional block configuration of the terminal according to this embodiment. Fig. 16 is a diagram showing an example of the functional block configuration of the base station according to this embodiment.

[0011] Embodiments of the present disclosure will be described with reference to the accompanying drawings. In the drawings, components with the same reference numerals may have the same or similar configurations.

[0012] 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 terminals 10, base stations 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 in the figure.

[0013] The wireless communication system 1 is a system that communicates in accordance with a radio access technology (Radio Access Technology: RAT) defined by 3GPP. The wireless access technology that the wireless communication system 1 complies with is, for example, a fifth-generation RAT such as NR, but is not limited to this. For example, one or more RATs can be used, such as fourth-generation RATs such as LTE and LTE-Advanced, sixth-generation or later RATs, and non-3GPP RATs such as Wi-Fi (registered trademark). The wireless communication system 1 may also be configured to communicate in accordance with a radio access technology defined by a standardization organization other than 3GPP (for example, the Institute of Electrical and Electronics Engineers (IEEE) or the Internet Engineering Task Force (IETF)).

[0014] The terminal 10 is a device corresponding to a terminal (e.g., User Equipment (UE)) defined in the 3GPP specifications. The terminal 10 is a specific terminal or device, such as a smartphone, a personal computer, a car, an in-vehicle terminal, an in-vehicle device, a stationary device, a telematics control unit (TCU), a sensor, or other IoT device. The terminal 10 may also be called User Equipment (UE), a Mobile Station (MS), a User Terminal, a Radio Apparatus, a subscriber terminal, an access terminal, or the like. The terminal 10 may also be a so-called Reduced Capability (RedCap) terminal, such as an industrial wireless sensor, a surveillance camera, a wearable device, or the like. The terminal 10 may be mobile or fixed. The terminal 10 is configured to be able to communicate using one or more RATs, such as NR, LTE, LTE-Advanced, Wi-Fi (registered trademark), etc. The terminal 10 is not limited to a terminal defined in the 3GPP specifications, but may be a terminal that complies with standards defined by other standards development organizations. The terminal 10 does not have to be a terminal that complies with standards.

[0015] The base station 20 is a device equivalent to a base station (e.g., a gNodeB (gNB) or eNB) defined in the 3GPP specifications. The base station 20 forms one or more cells C and communicates with the terminal 10 using the cells. The cell C may be interchangeably referred to as a serving cell, a carrier, a component carrier (CC), etc. The cell C may have a predetermined bandwidth. For example, the base station 20 may communicate with the terminal 10 using one or more cell groups. Each cell group may include one or more cells C. Aggregating multiple cells C within a cell group is called carrier aggregation. The multiple cells C may include a primary cell (PCell) or a primary secondary cell group (SCG) cell (PSCell) and one or more secondary cells (SCG). Communication with the terminal 10 using two cell groups is also called dual connectivity. The terminal 10 is not limited to a base station defined in the 3GPP specifications, but may be a terminal that complies with a standard defined by another standard development organization. Also, the terminal 10 does not have to be a base station that complies with a standard.

[0016] The base station 20 may be called a 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, access point, etc. The base station 20 is not limited to one node, and may be configured with multiple nodes (for example, a combination of a lower node such as a DU and an upper node such as a CU).

[0017] The core network 30 may be, for example, a fifth-generation core network (5G Core Network: 5GC) or a fourth-generation core network (Evolved Packet Core: EPC), but is not limited to these. An apparatus on the core network 30 (hereinafter also referred to as a "core network apparatus") may perform mobility management such as paging and location registration of the terminal 10. The core network apparatus may be connected to the base station 20 or the terminal 10 via a predetermined interface (for example, an S1 or NG interface).

[0018] The core network device may include, for example, at least one of an Access and Mobility Management Function (AMF) that manages C-plane information (e.g., information related to access and mobility management, etc.) and a User Plane Function (UPF) that controls the transmission of U-plane information (e.g., user data).

[0019] In the wireless communication system 1, a terminal 10 receives a downlink (DL) signal from a base station 20 and / or transmits an uplink (UL) signal to the base station 20. 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.

[0020] Furthermore, the terminal 10 performs a cell search based on a synchronization signal (e.g., a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS)) from the base station 20. The cell search is a procedure in which the terminal 10 acquires time and frequency synchronization in a cell and detects an identifier of the cell (e.g., a physical layer cell ID).

[0021] The terminal 10 determines a search space set and / or a control resource set (CORESET) based on parameters (hereinafter referred to as "RRC parameters") included in a Radio Resource Control (RRC) message. The CORESET may be configured with frequency domain resources (e.g., a predetermined number of resource blocks) and time domain resources (e.g., a predetermined number of symbols). The RRC parameters may also be referred to as RRC information elements (IEs), etc.

[0022] The terminal 10 monitors downlink control information (DCI) transmitted via a downlink control channel (e.g., a physical downlink control channel (PDCCH)) within a search space set associated with the CORESET. Note that the RRC message may include, for example, an RRC setup message, an RRC reconfiguration message, an RRC resume message, an RRC reestablishment message, system information, etc. Hereinafter, the downlink control channel will be referred to as a PDCCH, but may be called by another name.

[0023] Monitoring DCI refers to the terminal 10 blind decoding of PDCCH candidates in a search space set using an 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 a field included in the DCI format. The terminal 10 detects DCI for the terminal 10 based on the number of bits of the DCI format and a specific Radio Network Temporary Identifier (RNTI) used for scrambling (hereinafter referred to as "CRC scrambling") Cyclic Redundancy Check (CRC) bits (also referred to as CRC parity bits) of the DCI format. DCI monitoring is also referred to as PDCCH monitoring, monitor, etc. A given period during which DCI or PDCCH monitoring is performed is also referred to as a PDCCH monitoring occasion.

[0024] The terminal 10 monitors the PDCCH using a search space set during a PDCCH monitoring opportunity, and receives (or detects) DCI that is CRC-scrambled by a specific RNTI (e.g., P-RNTI, Cell(C)-RNTI, etc.). The terminal 10 controls reception of a downlink shared channel (e.g., a Physical Downlink Shared Channel (PDSCH)) scheduled using the DCI, and / or transmission of an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)). Hereinafter, the downlink shared channel and the uplink shared channel are referred to as PDSCH and PUSCH, but may be called by other names.

[0025] A search space set is a collection of one or more search spaces, and may include a search space set (hereinafter referred to as a "Common search space (CSS) set") that is used in common by one or more terminals 10, and a terminal-specific search space set (UE-specific search space (USS) set). The terminal 10 receives information on the configuration of each search space set, and configures each search space set based on the information on the configuration.

[0026] For example, the terminal 10 may receive information regarding the configuration of a search space set for paging (hereinafter referred to as "paging search space") (hereinafter referred to as "paging search space configuration information", for example, the RRC parameter "pagingSearchSpace"), and may configure a paging search space (for example, Type2-PDCCH CSS set) based on the information. The terminal 10 may detect DCI that is CRC-scrambled by a specific RNTI (for example, "Paging(P)-RNTI").

[0027] The terminal 10 receives a paging message via a PDSCH scheduled using the DCI. Here, information indicating the P-RNTI may be set using a predefined value. Hereinafter, the DCI CRC-scrambled using the P-RNTI is referred to as a "paging DCI." Note that the format of the DCI may be, for example, DCI format 1_0. Furthermore, the terminal 10 may receive a short message based on the paging DCI.

[0028] The system information broadcast in cell C may include a Master Information Block (MIB) and / or one or more System Information Blocks (SIBs). The MIB is broadcast via a broadcast channel (e.g., a Physical Broadcast Channel (PBCH)). The MIB and SIB1 are also called Minimum System Information, and SIB1 is also called Remaining Minimum System Information (RMSI). SIBx (x = any character string such as 2, 3, ...) other than SIB1 are also called Other System Information (OSI). SIB1 and SIBx other than SIB1 are broadcast via PDSCH. SIB1 is cell-specific, and SIBx other than SIB1 may be cell-specific or area-specific including one or more cells.

[0029] A block including at least one of a synchronization signal, a PBCH, and a PBCH demodulation reference signal (DM-RS) is called a synchronization signal block (SSB). The SSB may also be called an SS / PBCH block, an SS block, or the like. The SSB may be composed of a predetermined number of symbols (e.g., four consecutive symbols) as a time domain resource and a predetermined number of subcarriers (e.g., 240 consecutive subcarriers) as a frequency domain resource.

[0030] An SS burst set, which is a set of one or more SSBs, is transmitted at a predetermined interval. An SS burst set may also be referred to as an SS burst. Each SSB in the SS burst set is identified by an index (hereinafter referred to as an "SSB index"). In the case of multi-beam operation, SSBs with different indices in the SS burst set correspond to different beams, and may be transmitted by sequentially switching the beam direction by beam sweeping. In the case of single-beam operation, an SSB (one or more SSBs) with a specific index in the SS burst set may be transmitted in all directions.

[0031] One or more bandwidth parts (BWPs) may be configured for one cell C. The BWPs may include a BWP for DL ​​(hereinafter referred to as a "DL BWP") and / or a BWP for UL (hereinafter referred to as a "UL BWP"). The BWPs may also include a BWP configured specifically for a cell (hereinafter referred to as an "initial BWP") and a BWP configured specifically for a terminal 10 (hereinafter referred to as a "dedicated BWP"). The initial BWP may be used for initial access and / or may be common to one or more terminals 10. The initial BWPs may include an initial BWP for DL ​​(hereinafter referred to as an "initial DL BWP") and an initial BWP for UL (hereinafter referred to as an "initial UL BWP"). The dedicated BWP is also called a "UE-specific BWP."

[0032] (Paging) Paging is used for network-initiated connection setup when the terminal 10 is in an idle state or an inactive state. Paging is also used for transmitting short messages. The short messages may be used to instruct system information updates and / or for a Public Warning System (PWS). The short messages may also be notified regardless of the state of the terminal 10. Examples of the PWS include an Earthquake and Tsunami Warning System (ETWS) and a Commercial Mobile Alert System (CMAS). The state of the terminal 10 may be an RRC state such as an idle state, an inactive state, or a connected state.

[0033] 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, and is also called RRC_IDLE, idle mode, RRC idle mode, etc. The terminal 10 in the idle state receives system information broadcast in the cell on which it is camped. When an RRC connection is established, the terminal 10 in the idle state transitions to the connected state.

[0034] The inactive state is a state in which the RRC connection is established but suspended, and is also called an RRC_INACTIVE state, an inactive mode, an RRC inactive mode, etc. A terminal 10 in the inactive state receives system information broadcast by a camped-on cell. A terminal 10 in the inactive state transitions to a connected state when the RRC connection is resumed, and transitions to an idle state when the RRC connection is released.

[0035] The connected state is a state in which the RRC connection is established, and is also called an RRC_CONNECTED state, a connected mode, an RRC connected mode, etc. The terminal 10 in the connected state transitions to an idle state when the RRC connection is released, and transitions to an inactive state when the RRC connection is temporarily suspended.

[0036] The terminal 10 performs discontinuous reception (DRX) to reduce power consumption. Specifically, the terminal 10 performs PDCCH monitoring at paging occasions (POs) and can sleep during periods other than the POs.

[0037] A PO is a given period consisting of one or more time units (e.g., one or more symbols, one or more slots, or one or more subframes). A PO may be composed of, for example, a set of one or more PDCCH monitoring opportunities. A PO may be provided at a predetermined period. A PO may be provided within a paging frame (PF). A radio frame (RF) constituting a PF is a predetermined time unit (e.g., a time unit consisting of 10 subframes) and is identified by an identification number (hereinafter referred to as a "system frame number (SFN)"). One or more PFs may be provided within a DRX cycle. A DRX cycle is also called a paging cycle.

[0038] Information regarding the configuration of paging in BWP (hereinafter referred to as "PCCH-Config") may be configured in the terminal 10 by the base station 20. The PCCH-Config may include at least one of information regarding a DRX cycle (hereinafter referred to as "PagingCycle"), information regarding the first PDCCH monitoring opportunity in a PO (hereinafter referred to as "firstPDCCH-MonitoringOccasionOfPO"), information indicating the number of PFs and / or a time offset in a paging cycle (hereinafter referred to as "nAndPagingFrameOffset"), information regarding the number of POs per PF (hereinafter referred to as "ns"), and information regarding the number of PDCCH monitoring opportunities per SSB in a PO (hereinafter referred to as "nrofPDCCH-MonitoringOccasionPerSSB-InPO"). The PCCH-Config may be a cell-specific RRC parameter.

[0039] The terminal 10 determines a PF for the terminal 10 based on at least one of a DRX cycle, the number of PFs within the DRX cycle, a time offset, and an identifier of the terminal 10. Here, for example, the terminal 10 may determine an SFN constituting a PF based on the following equation (1): (SFN+PF_offset) mod T = (T div N) * (UE_ID mod N) (Equation 1) Here, T is the DRX cycle determined based on the PagingCycle, N and PF_offset are the number of PFs within T and a predetermined offset determined based on the nAndPagingFrameOffset, and UE_ID is a value determined based on an identifier of the terminal 10 (e.g., a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI)). The PagingCycle may indicate, for example, 32, 64, 128, or 256 RFs. nAndPagingFrameOffset may indicate that the PF is placed for every x RFs in T (e.g., x=1, 2, 4, 8, or 16) and / or a time offset.

[0040] The terminal 10 may determine a PO within a PF based on at least one of the ID of the search space used as the paging search space, the firstPDCCH-MonitoringOccasionOfPO, and the nrofPDCCH-MonitoringOccasionPerSSB-InPO. A PO may be configured, for example, of S*X consecutive PDCCH monitoring opportunities (e.g., S*X consecutive symbols excluding UL symbols) from the time position indicated by firstPDCCH-MonitoringOccasionOfPO. Each PDCCH monitoring opportunity within a PO may be configured with a predetermined number of symbols. firstPDCCH-MonitoringOccasionOfPO may indicate, for example, the time position (e.g., the symbol position) of the first PDCCH monitoring opportunity within a PF. Note that S may be the number of SSBs actually transmitted within an SS burst set, and X may be the number of PDCCH monitoring opportunities per SSB within a PO.

[0041] Fig. 2 is a diagram showing an example of a PO according to this embodiment. As shown in Fig. 2, a PF is arranged for every predetermined number of RFs (here, 8 RFs) within a DRX cycle (here, 32 RFs). The terminal 10 may determine a PF (here, PF #2) for the terminal 10 based on the UE_ID, for example, by the above-mentioned formula 1. For example, in Fig. 2, two POs are included in PF #2 for the terminal 10, but this is not limited thereto, and the number of POs per PF may be one or more.

[0042] 3A and 3B are diagrams showing an example of DRX control according to this embodiment. The terminal 10 is turned on for each PO and is in a sleep state except for a predetermined period of time outside the PO. Specifically, the terminal 10 may be in a sleep state except for a period during which time and frequency synchronization is performed in the cell outside the PO. For example, one or more SSBs and / or tracking reference signals (hereinafter referred to as "Tracking Reference Signals (TRS)") are used for the time and frequency synchronization.

[0043] For example, as shown in FIG. 3(A), the terminal 10 may acquire time and frequency synchronization in the cell using one or more SSBs before the PO. In FIG. 3(A), the terminal 10 may be in deep sleep (DS) state from the previous PO to the first SSB, but may be in light sleep (LS) state from the first SSB to the next PO, which has less of an effect of reducing power consumption than DS. Alternatively, as shown in FIG. 3(B), the terminal 10 may acquire time and frequency synchronization in the cell using a TRS arranged at a time position closer to the next PO than an SSB. In FIG. 3(B), the terminal 10 can maintain DS for a longer period of time than in FIG. 3(A), thereby reducing power consumption compared to FIG. 3(A).

[0044] The terminal 10 monitors a paging search space in a PO based on time and frequency synchronization using the SSB and / or TRS. The terminal 10 may receive a paging message via a PDSCH scheduled by a paging DCI detected by monitoring the paging search space. The terminal 10 may also receive a short message based on the paging DCI.

[0045] Note that the TRS may be referred to as a Channel State Information-Reference Signal (CSI-RS), a Non-zero power-CSI-RS (NZP-CSI-RS), TRS / CSI-RS, etc. Resources for the TRS (hereinafter, "TRS resources") may be configured, for example, from a set (hereinafter, "NZP-CSI-RS resource set") of one or more resources for the NZP-CSI-RS (hereinafter, "NZP-CSI-RS resources"). The TRS resources may be configured from a predetermined number of symbols and a predetermined number of subcarriers at a predetermined period.

[0046] The terminal 10 may also receive information regarding the transmission of a TRS in a TRS resource (hereinafter referred to as "TRS availability information") and determine whether to perform time and frequency synchronization using the TRS based on the TRS availability information. The TRS availability information may indicate, for example, whether a TRS is actually transmitted in the TRS resource.

[0047] The terminal 10 controls the establishment of a connection with the network side (for example, the CN 30 and / or the base station 20) based on a list of one or more terminal identifiers in the paging message received in the PO (for example, the RRC parameter "pagingRecordList") and a terminal identifier assigned to the terminal 10. For example, the terminal 10 may start a procedure for establishing a connection with the network side when the list includes a terminal identifier assigned to the terminal 10. Here, the terminal identifier is an identifier of the terminal 10 and may be determined based on, for example, the 5G-S-TMSI.

[0048] According to the above formula 1, multiple terminals 10 can be assigned to the same PO. Meanwhile, even if a terminal 10 receives a paging DCI, it cannot determine which terminal 10 the paging is addressed to without decoding the list of terminal identifiers in the paging message. Therefore, among multiple terminals 10 sharing the same PO, terminals 10 that are not targeted for paging in the PO may unnecessarily perform time and frequency synchronization and PDCCH monitoring in the PO. As a result, power consumption of terminals 10 that are not targeted for paging in the PO may be wasted.

[0049] (Subgrouping) In order to reduce wasteful power consumption of terminals 10 that are not targeted for paging, it is being considered to divide the terminals 10 into a plurality of subgroups and perform paging for each subgroup, rather than performing paging for each group made up of multiple terminals 10 that use the same PO. The subgrouping may be performed based on the terminal identifiers described above, or may be performed on a network basis.

[0050] In the case of the terminal identifier-based method, the terminal 10 may determine the subgroup assigned to itself based on the terminal identifier. Specifically, the terminal 10 may determine the number of PFs N within the DRX cycle T, the number of POs N per PF, in addition to the terminal identifier. s and the total number of subgroups N sg An identifier of the subgroup (hereinafter referred to as "subgroup ID") may be determined based on at least one of the above.

[0051] On the other hand, in the network-based case, the base station 20 or the core network device may determine the subgroup to be assigned to the terminal 10 based on information managed on the network side (e.g., the mobility state of the terminal 10, the paging probability, and / or the power consumption profile of the terminal 10, etc.). The network-side device may notify the terminal 10 of information indicating the determined subgroup (e.g., a subgroup ID).

[0052] (PEI DCI) Currently, 3GPP is considering notifying the terminal 10 of PEI information related to paging in one or more POs and controlling the terminal operation in the PO based on the PEI information. It is also considering including the PEI information in DCI transmitted on the PDCCH.

[0053] The PEI information may include, for example, information about subgroups to be paged in the PO (hereinafter referred to as "subgroup information"). The subgroup information may be, for example, information (for example, a 1-bit value) indicating whether paging is performed for each subgroup (i.e., whether paging is performed for each subgroup or each group).

[0054] The PEI information may also include information indicating which subgroups in one or more POs are to be paged (hereinafter referred to as "paging sub-group indication information"). Note that one or more POs may be included in a single PF, or may be included in multiple PFs. For example, the PEI may correspond to up to four POs in one PF.

[0055] For example, the paging subgroup indication information may divide the terminals 10 sharing each PO into a predetermined number of subgroups (e.g., up to eight subgroups) and indicate whether each subgroup is a paging target in each PO (whether or not a paging message is sent to each subgroup). The paging subgroup indication information may be, for example, a bitmap with a number of bits corresponding to the number of subgroups in one or more POs, or may be information indicating identifiers of subgroups to be paged in each PO.

[0056] In addition to the PEI information, the PEI DCI may include information about short messages (hereinafter referred to as "short message information") and / or the above-mentioned TRS availability information.

[0057] The terminal 10 may determine the time position of a PDCCH monitoring opportunity (hereinafter referred to as "PEI-O") for a PEI DCI based on a PO (hereinafter referred to as "target PO") indicating which subgroup is to be paged by the PEI DCI detected in the PEI-O. For example, the time position of the PEI-O may be determined based on a time offset (e.g., a frame-level time offset) relative to the PF including the target PO. Alternatively, the time position of the PEI-O may be determined based on an SSB or SS burst before the target PO. The SS burst may be, for example, the Lth (e.g., L = 1, 2, or 3) SS burst before the first PDCCH monitoring opportunity before the PO. Alternatively, the time position of the PEI-O may be determined based on a time offset relative to the target PO.

[0058] 4 is a diagram showing an example of the relationship between the PEI-O and PO according to this embodiment. As shown in FIG. 4, a search space set (hereinafter referred to as "PEI search space") used for monitoring the PEI DCI may be provided in the PEI-O. The PEI DCI detected by monitoring the PEI search space may correspond to one or more POs (for example, up to four POs per PF). Note that one PEI DCI may correspond to multiple POs across multiple PFs, or may correspond to one or more POs within a single PF. Furthermore, multiple PEI DCIs may correspond to one PO.

[0059] For example, in Fig. 4, the start timing of the PF including POs #0 and #1 is set as the reference time, and the start timing of the PEI-O is determined using a time offset (for example, a time offset at the RF level) relative to the reference time. Note that, as described above, the start timing of the PEI-O is not limited to that shown in Fig. 4, and may be determined based on the SSB or SS burst before the PO, or may be determined based on the first PO. Furthermore, multiple POs corresponding to one PEI may span multiple PFs.

[0060] 4, a terminal 10 in an idle state or an inactive state detects a PEI DCI by monitoring a PEI search space. The terminal 10 skips monitoring the paging search space in PO #0 based on the paging subgroup indication information in the PEI DCI. Since the terminal 10 maintains a sleep state in PO #0, power consumption can be reduced. Meanwhile, the terminal 10 monitors a paging DCI in the paging search space in PO #1 based on the paging subgroup indication information in the PEI DCI.

[0061] As described above, when the terminal 10 is in an idle state or an inactive state, the power consumption of the terminal 10 can be reduced by controlling monitoring of paging DCI in one or more POs based on the PEI DCI detected by monitoring the PEI search space. On the other hand, it is also assumed that the terminal 10 does not need to monitor the PEI DCI when it is in a connected state. This is because paging is not performed for a terminal 10 in a connected state, and therefore it is not necessary to recognize whether the terminal 10 is a paging target in a PO using the PEI DCI. Another issue is how the terminal 10 receives short messages when it is in a connected state.

[0062] In this way, when PEI DCI is newly introduced, it is desirable for the terminal 10 to appropriately control the monitoring of PEI DCI in PEI-O and / or the monitoring of paging DCI in PO depending on the state of the terminal 10 (e.g., idle state, inactive state, or connected state).

[0063] Therefore, in this embodiment, monitoring control of the PEI DCI and / or paging DCI will be described. For example, the terminal 10 may monitor the PEI DCI when in an idle state or an inactive state, but may not monitor the PEI DCI when in a connected state (first monitoring control). Alternatively, the terminal 10 according to this embodiment may monitor the PEI DCI when in an idle state or an inactive state, and may also monitor the PEI DCI when in a connected state (second monitoring control).

[0064] In this embodiment, monitoring the PEI DCI may be blind decoding a specific DCI format (e.g., DCI format 1_X (e.g., X=any character string such as 0, 1, 2, ...)) that is CRC-scrambled using the first RNTI (e.g., PEI-RNTI) in a PEI search space (e.g., Type2A-PDCCH CSS set). Information indicating the first RNTI may be set by a predefined value, or may be transmitted from the base station 20 to the terminal 10 and set in the terminal 10.

[0065] Furthermore, monitoring the paging DCI may be blind decoding of a specific DCI format (e.g., DCI format 1_0) that is CRC-scrambled using a second RNTI (e.g., P-RNTI) for a paging search space (e.g., Type 2-PDCCH CSS set). Information indicating the second RNTI may be set by a predefined value.

[0066] In the following description, it is assumed that the first RNTI used for CRC scrambling of the PEI DCI (hereinafter referred to as "PEI-RNTI") and the second RNTI used for CRC scrambling of the paging DCI (hereinafter referred to as "P-RNTI") are different RNTIs. Hereinafter, the first RNTI and the second RNTI are referred to as the PEI-RNTI and the P-RNTI, respectively, but the names are not limited to these.

[0067] In the following description, it is assumed that the PEI DCI and the paging DCI are DCI formats of the same size and are distinguished by the PEI-RNTI and the P-RNTI, but this is not limiting. For example, this embodiment can also be applied as appropriate to cases where the PEI DCI and the paging DCI are DCI formats of different sizes. When the PEI DCI and the paging DCI are DCI formats of different sizes, both DCIs may be CRC-scrambled with the same RNTI (e.g., P-RNTI).

[0068] (First monitoring control) In the first monitoring control, the terminal 10 receives a PEI DCI (first downlink control information) including PEI information regarding paging in one or more POs detected by monitoring a PEI search space (first search space set).

[0069] When the terminal 10 is in an idle state or an inactive state, based on the PEI DCI, the terminal 10 controls monitoring in a paging search space (second search space set) of paging DCI (second downlink control information) including information (hereinafter referred to as "scheduling information") regarding the scheduling of the PDSCH (downlink shared channel) that transmits paging messages in the PO and / or short message information.

[0070] On the other hand, when the terminal 10 is in a connected state, the terminal 10 does not monitor the PEI DCI in the PEI search space, but monitors the paging DCI including short message information in the paging search space.

[0071] 5(A) and (B) are diagrams showing an example of first monitoring control of PEI DCI and paging DCI according to this embodiment. Figures 6(A) and (B) are diagrams showing an example of formats of PEI DCI and paging DCI used in the first monitoring control of this embodiment. It should be noted that differences between Figures 5(A) and (B) and Figure 4 will be mainly described. Furthermore, the formats shown in Figures 6(A) and (B) are merely examples, and may include fields not shown, or some fields may be omitted.

[0072] 5A shows an example of a first monitoring control by the terminal 10 in an idle state or an inactive state. As shown in FIG. 5A, when the terminal 10 is in an idle state or an inactive state, the terminal 10 monitors the PEI DCI in the PEI search space within the PEI-O to detect the PEI DCI. As shown in FIG. 6A, the PEI DCI may include, for example, paging subgroup indication information indicating a subgroup of paging targets of the target POs #0 and #1. The PEI DCI may also include the subgroup information, TRS availability information, and / or short message information.

[0073] 5(A), since the paging DCI includes short message information as will be described later, the PEI DCI does not need to include short message information. For example, a terminal 10 that supports the PEI DCI may receive a short message based on the short message information in the paging DCI regardless of whether the terminal 10 is in an idle state, an inactive state, or a connected state. In this case, the PEI DCI does not need to include short message information.

[0074] Alternatively, in Fig. 5(A), both the paging DCI and the PEI DCI may include short message information. For example, a terminal 10 that supports the PEI DCI may receive a short message based on the short message information in the PEI DCI when in an idle state or an inactive state in which the terminal 10 monitors the PEI DCI, and may receive a short message based on the short message information in the paging DCI when in a connected state in which the terminal 10 does not monitor the PEI DCI. In this case, the PEI DCI may include short message information.

[0075] 5(A), the paging subgroup indication information in the PEI DCI indicates that the subgroup to which the terminal 10 belongs in the target PO #0 is not a paging target, so the terminal 10 does not monitor the paging DCI in PO #0. On the other hand, the paging subgroup indication information indicates that the subgroup to which the terminal 10 belongs in the target PO #1 is a paging target, so the terminal 10 monitors the paging DCI in the paging search space of PO #1.

[0076] As shown in Fig. 6(B), the paging DCI detected in the paging search space of PO #1 includes scheduling information of the PDSCH that transmits the paging message. The scheduling information may be, for example, information regarding frequency domain resources and / or time domain resources allocated to the PDSCH. A terminal 10 in an idle state or an inactive state may receive the paging message via the PDSCH based on the scheduling information in the paging DCI.

[0077] 6(B), the paging DCI detected in the paging search space of PO#1 may include short message information. The terminal 10 in the idle state or the inactive state may receive a short message (e.g., an instruction to update system information, or at least one of ETWS and CMAS) based on the short message information in the paging DCI.

[0078] 5B shows an example of the first monitoring control by the connected terminal 10. As shown in FIG. 5B, when the terminal 10 is in the connected state, the terminal 10 does not monitor the PEI DCI in the PEI search space within the PEI-O.

[0079] In Fig. 5(B), the terminal 10 in the connected state monitors paging DCI in the paging search spaces of PO #0 and PO #1. As shown in Fig. 6(B), the paging DCI detected by the monitoring may include short message information. The terminal 10 may receive a short message (e.g., an instruction to update system information, or at least one of ETWS and CMAS) based on the short message information in the paging DCI. On the other hand, the terminal 10 in the connected state may skip receiving a paging message based on the scheduling information in the paging DCI.

[0080] For example, the terminal 10 in the connected state may monitor the paging DCI in at least one PO within a system information modification period to obtain a short message related to updating of system information. Also, the terminal 10 in the connected state may monitor the paging DCI in at least one PO within a predetermined period (e.g., a DRX period or a paging cycle) to obtain a short message related to notification of a PWS (e.g., at least one of an ETWS and a CMAS).

[0081] According to the first monitoring control, when the terminal 10 is in an idle state or an inactive state, based on the PEI DCI detected by monitoring the PEI search space, monitoring of the paging search space in one or more POs is controlled, thereby reducing power consumption of the terminal 10. Furthermore, when the terminal 10 is in a connected state, the terminal 10 receives a short message based on the paging DCI in the same way as a terminal 10 that does not support the PEI DCI, thereby reducing the design load associated with defining new operations for the terminal 10 in the connected state.

[0082] (Second Monitoring Control) In the above-described first monitoring control, when the terminal 10 is in a connected state, the terminal 10 does not monitor the PEI DCI in the PEI search space, but in the second monitoring control, when the terminal 10 is in a connected state, the terminal 10 monitors the PEI DCI including short message information in the PEI search space, which is different from the first monitoring control. The second monitoring control will be described mainly focusing on the differences from the first monitoring control.

[0083] 7(A) and (B) are diagrams showing an example of second monitoring control of PEI DCI and paging DCI according to this embodiment. Figures 8(A) and (B) are diagrams showing an example of the format of PEI DCI and paging DCI used in the second monitoring control of this embodiment. It should be noted that differences between Figures 7(A) and (B) and Figures 4 and 5(A) and (B) will be mainly described. Furthermore, the formats shown in Figures 8(A) and (B) are merely examples, and may include fields not shown, or some fields may be omitted.

[0084] 7A shows an example of second monitoring control by the terminal 10 in an idle state or an inactive state. As shown in FIG. 7A, when the terminal 10 is in an idle state or an inactive state, the terminal 10 monitors the PEI DCI in the PEI search space within the PEI-O to detect the PEI DCI. As shown in FIG. 8A, the PEI DCI may include, for example, paging subgroup indication information indicating a subgroup to be paged for the target POs #0 and #1. The PEI DCI may also include the subgroup information and / or TRS availability information (not shown).

[0085] The PEI DCI shown in Fig. 8A may include short message information. In Fig. 7A, the terminal 10 in the idle state or inactive state may receive a short message (e.g., a system information update instruction, ETWS, or CMAS) based on the short message information in the PEI DCI.

[0086] In FIG. 7A, a terminal 10 in an idle state or an inactive state does not monitor paging DCI in PO #0, but monitors paging DCI in the paging search space of PO #1. As shown in FIG. 8B, the paging DCI detected in the paging search space of PO #1 includes scheduling information for the PDSCH that transmits the paging message. A terminal 10 in an idle state or an inactive state may receive a paging message via the PDSCH based on the scheduling information in the paging DCI. Note that if the terminal 10 does not support PEI DCI (e.g., a terminal 10 prior to Release 16), the terminal 10 receives a short message based on the short message information in the paging DCI, and therefore the paging DCI in FIG. 8B may include short message information.

[0087] 7B shows an example of second monitoring control by the connected terminal 10. As shown in FIG. 7B, when the terminal 10 is in the connected state, the terminal 10 monitors the PEI DCI including short message information in the PEI search space within the PEI-O.

[0088] The terminal 10 may receive a short message (e.g., a system information update instruction, at least one of ETWS and CMAS) based on the short message information in the PEI DCI detected by the monitoring. For example, the terminal 10 in the connected state may monitor the PEI DCI in at least one PEI-O within a system information update period to obtain a short message related to the system information update. Furthermore, the terminal 10 in the connected state may monitor the PEI DCI in at least one PEI-O within a predetermined cycle (e.g., a DRX cycle or a paging cycle) to obtain a short message related to the notification of PWS (e.g., at least one of ETWS and CMAS).

[0089] Furthermore, if the terminal 10 does not detect a PEI DCI including short message information by monitoring the PEI search space in the PEI-O, the terminal 10 may assume that a short message will not be sent.

[0090] According to the second monitoring control, the terminal 10 can acquire a short message based on the short message information in the PEI DCI detected by monitoring the PEI search space, regardless of whether the terminal 10 is in an idle state, an inactive state, or a connected state. Therefore, unlike the first monitoring control, it is not necessary to monitor the paging DCI in the paging search space of the PO to acquire a short message.

[0091] (Example of specification change related to first and second monitoring control) An example of specification change related to the 3GPP specification related to the first and second monitoring control will be described with reference to Figures 9-11. Note that the following example of specification change is merely an example, and the example of specification change related to the first and second monitoring control of this embodiment is not limited to the one described below.

[0092] 9 is a diagram showing an example of reception types related to the first and second monitoring controls of this embodiment. In FIG. 9, the RNTI monitored by the terminal 10 is associated with the physical channel and transport channel associated with the DCI CRC-scrambled by the RNTI. The association between the RNTI and the physical channel and transport channel is identified by a reception type.

[0093] For example, reception type "P0" indicates that DCI CRC-scrambled by the PEI RNTI (i.e., PEI DCI) is transmitted via PDCCH only in the primary cell (PCell). Furthermore, reception type "P1" indicates that DCI CRC-scrambled by the PEI RNTI (i.e., PEI DCI) and DCI CRC-scrambled by the P-RNTI (i.e., paging DCI) are transmitted via PDCCH only in the PCell, and that a PDSCH is scheduled by the paging DCI and associated with the transport channel "paging channel (PCH)." Similarly, other reception types associate a physical channel with a monitored RNTI, or a physical channel, a monitored RNTI, and a transport channel.

[0094] 10 is a diagram showing an example of a combination of reception types for each state of the terminal 10 according to the first monitoring control of the present embodiment. For example, in FIG. 10, when the terminal 10 is in an idle state (RRC_IDLE) or an inactive state (RRC_INACTIVE), if the terminal 10 supports PEI DCI, the terminal 10 may receive a physical channel and / or a corresponding transport channel according to the reception type combination "A+(B and / or P1 and / or D0)+F0" of FIG. 9. On the other hand, if the terminal 10 does not support PEI DCI, the reception type "C1" may be applied instead of "P1".

[0095] When the terminal 10 is in a connected state (RRC_CONNECTED), the reception types that the terminal 10 uses to receive physical channels and / or corresponding transport channels do not include "P0" and "P1", as shown in Fig. 10. Therefore, the terminal 10 in the connected state does not monitor DCI that is CRC-scrambled by PEI-RNTI (i.e., PEI DCI).

[0096] Fig. 11 is a diagram showing an example of a combination of reception types for each state of the terminal 10 according to the second monitoring control of the present embodiment. For example, in Fig. 11, when the terminal 10 is in an idle state (RRC_IDLE) or an inactive state (RRC_INACTIVE), the terminal 10 operates in the same manner as in Fig. 10.

[0097] When the terminal 10 is in a connected state (RRC_CONNECTED), if the terminal 10 supports PEI DCI, the terminal 10 may receive physical channels and / or corresponding transport channels according to the reception type combination "A+P0+(B and / or (D0 or (m1*D1 and m2*D2))))+E+F0+n*F1+G+H+J0+J1+J2+K+O+L0+L1+M+N" of FIG. 9. The terminal 10 in the connected state may use reception type "P0" to monitor DCI CRC-scrambled by the PEI-RNTI (i.e., PEI DCI) and receive a short message in the PEI DCI. Note that if the terminal 10 does not support PEI DCI, "C0" may be applied instead of the reception type "P0".

[0098] (PEI Search Space Setting) The terminal 10 may receive information related to the setting of a PEI search space (hereinafter referred to as "PEI search space information") and set a PEI search space based on the PEI search space setting information. The PEI search space may be called, for example, a Type 2A-PDCCH CSS set.

[0099] The PEI search space configuration information is, for example, an RRC parameter, and may be included in information related to the configuration of the PDCCH (hereinafter referred to as "PDCCH configuration information") or may be included in system information. The PDCCH configuration information may be, for example, an RRC parameter "pdcch-ConfigCommon" related to the configuration of a cell-specific PDCCH (PDCCH in initial DL BWP), or an RRC parameter "pdcch-Config" related to the configuration of a PDCCH specific to the terminal 10.

[0100] The PEI search space configuration information may include at least one of, for example, an identifier of a search space used as a PEI search space (e.g., RRC parameter "searchSpaceId"), an identifier of a CORESET associated with the PEI search space (e.g., RRC parameter "controlResourceSetId"), information regarding the duration of PEI-O (e.g., RRC parameter "duration"), information regarding the first symbol for which PDCCH monitoring is performed within a slot (e.g., RRC parameter "monitoringSymbolsWithinSlot"), information regarding the periodicity and / or offset of PEI-O (e.g., RRC parameter "monitoringSlotPeriodicityAndOffset"), etc.

[0101] If the PEI search space setting information is not provided to the terminal 10 from the base station 20, the terminal 10 does not need to monitor the PEI DCI in the PEI search space.

[0102] The number of PDCCH candidates constituting the PEI search space may be determined by specifications, or may be configured in the terminal 10 by the base station 20. For example, information regarding the number of PDCCH candidates may be included in the PEI search space configuration information. Furthermore, the number of PDCCH candidates constituting the PEI search space may be determined or configured for each aggregation level (AL). AL is the aggregate number of control channel elements (CCEs) constituting one PDCCH candidate. When ALX (for example, X = 1, 2, 4, 8, 16, 32, etc.) is used, one PDCCH candidate is composed of X CCEs.

[0103] 12 is a diagram showing an example of the number of PDCCH candidates in a PEI search space according to this embodiment. For example, in FIG. 12, the PEI search space is configured with seven PDCCH candidates, including four PDCCH candidates for AL4, two PDCCH candidates for AL8, and one PDCCH candidate for AL16. The number of PDCCH candidates per AL shown in FIG. 12 is predetermined in the specifications and may be applied not only to the PEI search space but also to the paging search space. Thus, the number of PDCCH candidates per AL constituting the PEI search space may be the same as or different from the number of PDCCH candidates per AL constituting the paging search space.

[0104] The terminal 10 may not assume that it processes information from multiple DCI formats CRC-scrambled by a specific RNTI per slot. That is, the terminal 10 may assume that it processes a single DCI format CRC-scrambled by a specific RNTI per slot. For example, the terminal 10 may assume that the DCI CRC-scrambled by the PEI-RNTI is a PEI DCI (i.e., a single DCI format for the PEI DCI).

[0105] (Example of specification change related to setting of PEI search space) An example of specification change in the 3GPP specification related to setting of the PEI search space and the paging search space will be described with reference to Fig. 13. Note that the following example of specification change is merely an example, and the example of specification change related to setting of the PEI search space and the paging search space in this embodiment is not limited to the example described below.

[0106] As shown in FIG. 13, the terminal 10 may monitor a paging search space (e.g., Type2-PDCCH CSS set) configured by paging search space configuration information (e.g., RRC parameter "pagingSearchSpace") for a DCI format (i.e., paging DCI) CRC-scrambled by P-RNTI in a primary cell of a master cell group (MCG).

[0107] The terminal 10 may monitor the PEI search space (e.g., Type2A-PDCCH CSS set) configured by the PEI search space configuration information (e.g., the RRC parameter "pei-SearchSpace") for a DCI format (i.e., PEI DCI) CRC-scrambled by PEI-RNTI or P-RNTI in the primary cell of the MCG.

[0108] If the terminal 10 is not given PEI search space configuration information (e.g., the RRC parameter "pei-SearchSpace") for a PEI search space (e.g., Type2A-PDCCH CSS set), the terminal 10 may not monitor the PDCCH for the PEI search space in the DL BWP. The aggregation levels for the PEI search space and the number of PDCCH candidates per aggregation level may be given in the table shown in FIG. 12.

[0109] When one or more search space sets and one or more RNTIs are given to the terminal 10, the terminal 10 may assume that the DCI format CRC-scrambled with any RNTI per slot is a single DCI format, such as search space #0, a search space for SIB1 in the initial DL BWP of the PCell, a search space for other system information, a paging search space, a search space for random access, a PEI search space, or a CSS set.

[0110] Note that the search space #0 may be configured in the terminal 10 based on the RRC parameter "searchSpaceZero." The search space for SIB1 may be configured in the terminal 10 based on the RRC parameter "searchSpaceSIB1." The paging search space may be configured in the terminal 10 based on the RRC parameter "pagingSearchSpace." The search space for random access may be configured in the terminal 10 based on the RRC parameter "ra-SearchSpace." The PEI search space may be configured in the terminal 10 based on the RRC parameter "pei-SearchSpace."

[0111] Furthermore, the one or more RNTIs may be System Information (SI)-RNTI, P-RNTI, Random Access (RA)-RNTI, Message B (MsgB)-RNTI, Slot Format Indication (SFI)-RNTI, Interruption (INT)-RNTI, Transmit Power Control-Sounding Reference Signal (TPC-SRS)-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or PEI-RNTI.

[0112] (Configuration of wireless communication system) Next, we will explain the configuration of each device in the above-described wireless communication system 1. Note that the following configuration is intended to show the configuration necessary for explaining this embodiment, and does not exclude each device from having functional blocks other than those shown.

[0113] 14 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 (e.g., the terminal 10, the base station 20, the CN 30, etc.) includes a processor 11, a storage device 12, a communication device 13 for performing wired or wireless communication, and an input / output device 14 for accepting various input operations and outputting various information.

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

[0115] The storage device 12 is configured with storage such as a memory, a hard disk drive (HDD), and / or a solid state drive (SSD), etc. The storage device 12 may store various information necessary for the processor 11 to execute processing (e.g., programs executed by the processor 11, etc.).

[0116] The communication device 13 is a device that communicates via a wired and / or wireless network, and may include, for example, a network card, a communication module, a chip, an antenna, etc. The communication device 13 may also include an amplifier, an RF (Radio Frequency) device that processes wireless signals, and a BB (BaseBand) device that processes baseband signals.

[0117] The RF device generates a radio signal to be transmitted from the antenna by, for example, performing D / A conversion, modulation, frequency conversion, power amplification, etc. on the digital baseband signal received from the BB device. The RF device also 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.

[0118] The BB device performs a process of converting data into a digital baseband signal. Specifically, the BB device may map the data to subcarriers, perform IFFT to generate OFDM symbols, insert CPs into the generated OFDM symbols, and generate digital baseband signals. Note that the BB device may apply a transform precoder (DFT spreading) before mapping the data to the subcarriers.

[0119] The BB device also performs a process of converting a digital baseband signal into data. Specifically, the BB device may remove a CP from the digital baseband signal input from the RF device, perform an FFT on the signal from which the CP has been removed, and extract a frequency domain signal. The BB device may also apply an IDFT to the frequency domain signal.

[0120] The input / output device 14 includes input devices such as a keyboard, a touch panel, a mouse, and / or a microphone, and output devices such as a display and / or a speaker.

[0121] The hardware configuration described above is merely an example. Each device in the wireless communication system 1 may omit some of the hardware shown in Fig. 14 or may include hardware not shown in Fig. 14. Furthermore, the hardware shown in Fig. 14 may be configured using one or more chips.

[0122] <Functional Block Configuration> <Terminal> Fig. 15 is a diagram showing an example of the functional configuration of a terminal according to this embodiment. As shown in Fig. 15, the terminal 10 includes a receiving unit 101, a transmitting unit 102, and a control unit 103. The functional configuration shown in Fig. 15 is merely an example, and the names of the functional divisions and functional units may be any as long as they can execute the operations according to this embodiment. Furthermore, the receiving unit 101 and the transmitting unit 102 may be collectively referred to as a communication unit.

[0123] It should be noted that 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. Furthermore, 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. Furthermore, 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-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as a USB memory or a CD-ROM.

[0124] The receiving unit 101 receives a signal (e.g., a DL signal and / or a sidelink signal). The receiving unit 101 may also receive information and / or data transmitted via the signal. Here, "receiving" may include, for example, performing reception-related processing such as at least one of reception, demapping, demodulation, decoding, monitoring, and measurement of a radio signal. The DL signal may include, for example, at least one of a PDSCH, a PDCCH, a downlink reference signal, a synchronization signal, a PBCH, and the like.

[0125] The receiving unit 101 monitors PDCCH candidates within a search space and detects DCI. The receiving unit 101 may receive DL data via a PDSCH scheduled using the DCI. The DL data may include downlink user data and / or control information of higher layers (e.g., at least one parameter of a MAC layer, an RRC layer, and a Non Access Stratum (NAS) layer). The receiving unit 101 may receive system information via a PBCH and / or a PDSCH.

[0126] The transmitter 102 transmits a signal (e.g., an UL signal and / or a sidelink signal). The transmitter 102 may also transmit information and / or data transmitted via the signal. Here, "transmitting" may include performing processing related to transmission, such as at least one of encoding, modulation, mapping, and transmission of a radio signal. The UL signal may include at least one of a PUSCH, a PRACH, a PUCCH, an uplink reference signal, etc.

[0127] The transmitter 102 may transmit UL data via a PUSCH scheduled using the DCI received by the receiver 101. The UL data may transmit uplink user data and / or control information of higher layers (e.g., at least one parameter of a MAC layer, an RRC layer, and an NAS layer).

[0128] The control unit 103 performs various controls in the terminal 10. Specifically, the control unit 103 may control the operation of the terminal 10 based on information relating to various configurations (e.g., parameters of the RRC layer) received by the receiving unit 101 from the base station 20 or another terminal 10. The operation of the terminal 10 based on the information may be synonymous with "configuration information being set in the terminal 10."

[0129] The control unit 103 may control reception of signals in the receiving unit 101. The control unit 103 may also control transmission of signals in the transmitting unit 102. The control unit 103 may determine whether to apply a transform precoder to the signals transmitted by the transmitting unit 102.

[0130] In this embodiment, the terminal 10 may include a receiving unit 101 that receives first downlink control information (e.g., PEI DCI) including information regarding paging at one or more paging occasions detected by monitoring a first search space set (e.g., PEI search space), and a control unit 103 that, when in an idle state or an inactive state, controls monitoring in a second search space set (e.g., paging search space) of second downlink control information (e.g., paging DCI) including information regarding scheduling of a downlink shared channel that transmits paging messages at the paging occasions and / or information regarding short messages based on the first downlink control information.

[0131] When in a connected state, the control unit 103 may not monitor the first downlink control information in the first search space set, but may monitor the second downlink control information including information regarding the short message in the second search space set.

[0132] When in a connected state, the control unit 103 may monitor the first downlink control information in the first search space set, the first downlink control information including information about the short message. The information about the short message may include an instruction to update system information and / or information about a public warning system.

[0133] The receiving unit 101 may receive information regarding the configuration of the first search space set (e.g., PEI search space configuration information). The control unit 103 may monitor the first downlink control information in the first search space set configured based on the information regarding the configuration. If the receiving unit 101 does not receive information regarding the configuration, the control unit 103 may not monitor the first downlink control information in the first search space set.

[0134] The receiving unit 101 may receive information regarding the configuration of the second search space set (e.g., paging search space configuration information). The control unit 103 may monitor the second downlink control information in the second search space set configured based on the information regarding the configuration. If the information regarding the configuration is not received by the receiving unit 101, the control unit 103 may not monitor the second downlink control information in the second search space set.

[0135] The first downlink control information may have redundancy check code (CRC) bits added by a first Radio Network Temporary Identifier (RNTI) (e.g., PEI-RNTI), and the second downlink control information may have CRC bits scrambled by a second RNTI (e.g., P-RNTI) added. The control unit 103 may assume that the downlink control information to which the CRC bits scrambled by the first RNTI are added is the first downlink control information.

[0136] <<Base Station>> Fig. 16 is a diagram showing an example of the functional block configuration of a base station according to this embodiment. As shown in Fig. 16, the base station 20 includes a receiving unit 201, a transmitting unit 202, and a control unit 203. The functional configuration shown in Fig. 16 is merely an example, and the names of the functional divisions and functional units may be any as long as they can perform the operations according to this embodiment. Furthermore, the receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.

[0137] It should be noted that 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. Furthermore, 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. Furthermore, the program can be stored in a storage medium. The storage medium storing the program may be a computer-readable non-transitory storage medium. The non-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as a USB memory or a CD-ROM.

[0138] The receiver 201 receives a signal (e.g., an UL signal and / or a sidelink signal) and may also receive information and / or data (e.g., the above-mentioned UL data) transmitted via the signal.

[0139] The transmitter 202 transmits a signal (e.g., a DL signal and / or a sidelink signal). The transmitter 202 may also transmit information and / or data (e.g., the DL data) transmitted via the signal. Note that some of the information transmitted from the transmitter 202 may be transmitted by a transmitter within a core network device.

[0140] The control unit 203 performs various controls for communication with the terminal 10. Specifically, the control unit 203 may determine information related to various settings to be notified to the terminal 10. Sending the information to the terminal 10 may be synonymous with "setting the information in the terminal."

[0141] The control unit 203 may control the reception of signals by the receiving unit 201. The control unit 203 may also control the transmission of signals by the transmitting unit 202.

[0142] In this embodiment, the base station 20 may include a transmitter 202 that transmits first downlink control information (e.g., PEI DCI) including information about paging at one or more paging occasions in a first search space set (e.g., PEI search space), and a controller 203 that controls, based on the information about the paging, transmission of second downlink control information (e.g., paging DCI) including information about scheduling of a downlink shared channel that transmits paging messages at the paging occasions and / or information about short messages.

[0143] The transmitter 202 may transmit information related to the configuration of the first search space set (e.g., PEI search space configuration information). The transmitter 202 may transmit the first downlink control information in the first search space set that is configured based on the information related to the configuration.

[0144] The transmitter 202 may transmit information related to the configuration of the second search space set (e.g., paging search space configuration information). The transmitter 202 may transmit the second downlink control information in the second search space set configured based on the information related to the configuration.

[0145] (Supplementary Information) The various signals, information, and parameters in the above embodiments may be signaled in any layer. That is, the various signals, information, and parameters may be replaced with signals, information, and parameters of any layer, such as a higher layer (e.g., NAS layer, RRC layer, MAC layer, etc.) or a lower layer (e.g., physical layer). Furthermore, notification of predetermined information is not limited to explicit notification, and may be implicit (e.g., by not notifying information or by using other information).

[0146] Furthermore, 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 in any way as long as it is a time unit having a predetermined number of symbols. Furthermore, an RB may be named in any way as long as it is a frequency unit having a predetermined number of subcarriers. Furthermore, "first ..." and "second ..." merely identify multiple pieces of information or signals, and the order may be changed as appropriate.

[0147] For example, in the above-described embodiment, PDSCH, PUSCH, PDCCH, PBCH, PRACH, etc. are given as examples of the physical channel for transmitting DL data, the physical channel for transmitting UL data, the physical channel for transmitting DCI, the physical channel for transmitting broadcast information, and the physical channel for transmitting RA preambles, respectively, but the names of physical channels are not limited to these as long as they have similar functions. Furthermore, these physical channels may be referred to as transport channels to which the physical channels are mapped. Furthermore, the PDSCH, PUSCH, PDCCH, PBCH, PRACH, etc. may each be rephrased as a transport channel mapped to a physical channel (for example, a Downlink Shared Channel (DL-SCH), an Uplink Shared Channel (UL-SCH), a Broadcast Channel (BCH) and / or a Random Access Channel (RCH)), etc. Furthermore, these transport channels may also be rephrased as a logical channel to which the transport channels are mapped. Furthermore, DL data and UL data are downlink and uplink data, respectively, and the data may include user data and higher layer control information (for example, RRC parameters, Medium Access Control (MAC) parameters, etc.).

[0148] Furthermore, the applications of the terminal 10 in the above embodiments (e.g., for RedCap, IoT, etc.) are not limited to those exemplified, and the terminal 10 may be used for any application (e.g., eMBB, URLLC, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) as long as it has similar functions. Furthermore, the format of the various information is not limited to that in the above embodiments, and may be changed as appropriate to bit representation (0 or 1), boolean value (Boolean: true or false), integer value, character, etc. Furthermore, the terms singular and plural in the above embodiments may be interchangeable.

[0149] The above-described embodiments are intended to facilitate understanding of the present disclosure and are not intended to limit the present disclosure. The flowcharts, sequences, elements included in the embodiments, and their arrangements, indexes, conditions, etc. described in the embodiments are not limited to those exemplified and can be modified as appropriate. Furthermore, at least some of the configurations described in the above embodiments can be partially replaced or combined.

[0150] 1...wireless communication system, 20...base station, 30...core network, 101...receiving unit, 102...transmitting unit, 103...control unit, 201...receiving unit, 202...transmitting unit, 203...control unit, 11...processor, 12...storage device, 13...communication device, 14...input / output device

Claims

1. a receiving unit that receives system information from a base station, the system information including: information for configuring a first search space set for monitoring physical downlink control channel (PDCCH) candidates for first downlink control information (DCI) including a paging early indication (PEI); and information for configuring a second search space set for monitoring PDCCH candidates for second DCI including information used in scheduling a physical downlink shared channel (PDSCH) for a paging message and / or information indicating a short message; In an idle state, monitor the PDCCH candidates for the first DCI in a primary cell based on information for configuring the first search space set, monitor the PDCCH candidates for the second DCI in the primary cell based on information for configuring the second search space set, and control to receive the paging message from the base station based on information used for scheduling the PDSCH included in the second DCI; A control unit that, in a connected state, monitors the PDCCH candidates for the second DCI in the primary cell based on information for configuring the second search space set, and controls to receive information indicating a short message included in the second DCI from the base station, The number of the PDCCH candidates for the first search space set for each control channel element (CCE) aggregation level and the number of the PDCCH candidates for the second search space set for each CCE aggregation level are set to be the same. Terminal.

2. The control unit controls, in the idle state, to receive information indicating a short message included in the second DCI from the base station. The terminal according to claim 1.

3. When the control unit does not receive information for setting the first search space set from the base station, the control unit does not monitor the PDCCH candidates for the first DCI. A terminal according to claim 1 or 2.

4. The first DCI is appended with redundancy check code (CRC) bits scrambled by a paging advance indication-radio network temporary identifier (PEI-RNTI). A terminal according to any one of claims 1 to 3.

5. The second DCI is added with CRC bits scrambled by a paging RNTI (P-RNTI); A terminal according to any one of claims 1 to 4.

6. A transmitter that transmits system information to a terminal, the system information including: information for configuring a first search space set for monitoring physical downlink control channel (PDCCH) candidates for first downlink control information (DCI) including a paging early indication (PEI); and information for configuring a second search space set for monitoring PDCCH candidates for second DCI including information used in scheduling a physical downlink shared channel (PDSCH) for a paging message and / or information indicating a short message; When the terminal is in an idle state, control is performed so that a first DCI is transmitted to the terminal in a primary cell based on information for configuring the first search space set, the second DCI is transmitted to the terminal in the primary cell based on information for configuring the second search space set, and the paging message is transmitted to the terminal based on information used for scheduling the PDSCH included in the second DCI; A control unit that controls the second DCI including information indicating a short message to be transmitted to the terminal in the primary cell based on information for setting the second search space set when the terminal is in a connected state, The number of the PDCCH candidates for the first search space set for each control channel element (CCE) aggregation level and the number of the PDCCH candidates for the second search space set for each CCE aggregation level are set to be the same. Base station.

7. The control unit controls the terminal to transmit, in the idle state, the second DCI including information indicating the short message to the terminal. The base station according to claim 6.

8. When the control unit does not transmit information for setting the first search space set to the terminal, the control unit controls so as not to transmit the first DCI to the terminal. A base station as claimed in claim 6 or 7.

9. The first DCI is appended with redundancy check code (CRC) bits scrambled by a paging advance indication-radio network temporary identifier (PEI-RNTI). A base station according to any one of claims 6 to 8.

10. The second DCI is added with CRC bits scrambled by a paging RNTI (P-RNTI); A base station according to any one of claims 6 to 9.

11. receiving system information from a base station, the system information including: information for configuring a first search space set for monitoring physical downlink control channel (PDCCH) candidates for first downlink control information (DCI) including a paging early indication (PEI); and information for configuring a second search space set for monitoring PDCCH candidates for second DCI including information used for scheduling a physical downlink shared channel (PDSCH) for a paging message and / or information indicating a short message; In an idle state, monitoring the PDCCH candidates for the first DCI in a primary cell based on information for configuring the first search space set, monitoring the PDCCH candidates for the second DCI in the primary cell based on information for configuring the second search space set, and controlling to receive the paging message from the base station based on information used for scheduling the PDSCH included in the second DCI; In a connected state, the primary cell monitors the PDCCH candidates for the second DCI based on information for configuring the second search space set, and controls to receive information indicating a short message included in the second DCI from the base station; The number of the PDCCH candidates for the first search space set for each control channel element (CCE) aggregation level and the number of the PDCCH candidates for the second search space set for each CCE aggregation level are set to be the same. The communication method of the device.

12. and controlling the receiving unit to receive, in the idle state, information indicating a short message included in the second DCI from the base station. The communication method according to claim 11.

13. When information for setting the first search space set is not received from the base station, the PDCCH candidate for the first DCI is not monitored.

13. A communication method according to claim 11 or 12.

14. The first DCI is appended with redundancy check code (CRC) bits scrambled by a paging advance indication-radio network temporary identifier (PEI-RNTI). A communication method according to any one of claims 11 to 13.

15. The second DCI is added with CRC bits scrambled by a paging RNTI (P-RNTI); A communication method according to any one of claims 11 to 14.