Method by device, method, storage medium, method by base station, and base station

Abstract

This device may perform, on the basis of detection of a WUS for the device, paging monitoring at a paging occasion for the device within a paging frame for the device during a paging monitoring window, wherein the start of the paging monitoring window is the start of a first paging frame after a predetermined duration from a slot in which the WUS is has been received.

Description

Method by device, method and storage medium, and method by base station, and base station

[0001] This specification relates to wireless communication systems.

[0002] Various devices and technologies, such as machine-to-machine (M2M) communication, machine-type communication (MTC), and smartphones and tablet PCs (personal computers) that require high data transmission rates, are emerging and becoming widespread. Consequently, the amount of data required to be processed on cellular networks is rapidly increasing. To meet this rapidly increasing data processing demand, technologies such as carrier aggregation and cognitive radio are being developed to efficiently utilize more frequency bands, while multi-antenna technology and multi-BS cooperation technology are being developed to increase the data capacity transmitted within a limited frequency range.

[0003] As more and more communication devices demand greater capacity, the need for enhanced mobile broadband (eMBB) communications is emerging, surpassing legacy radio access technology (RAT). Furthermore, massive machine type communication (mMTC), which connects multiple devices and objects to provide diverse services anytime, anywhere, is a key issue to be considered in next-generation communications.

[0004] Additionally, discussions are underway on communication systems designed to accommodate reliability- and latency-sensitive services and user equipment (UE). The introduction of next-generation wireless access technologies is being discussed, including enhanced mobile broadband (eMBB), mMTC, and ultra-reliable and low latency communication (URLLC).

[0005] One technical task of this specification is to provide a method and device for reducing UE power consumption.

[0006] Another technical challenge of this specification is to provide a paging method and device for a UE using a low-power (LP) receiver.

[0007] Another technical challenge of this specification is to provide a method and device by which a UE using a low-power receiver can efficiently monitor paging.

[0008] The technical tasks to be achieved by this specification are not limited to the technical tasks mentioned above, and other technical tasks not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0009] In one aspect of the present disclosure, a method performed by a device is provided. In another aspect of the present disclosure, a device is provided, comprising: at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, storing at least one program code comprising instructions that, when executed, cause the at least one processor to perform operations. The method or the operations may include: obtaining a paging-related setting; determining, based on the paging-related setting and an identifier of the device, paging frames for the device and at least one paging occasion for the device within each of the paging frames; and performing paging monitoring for paging reception at at least one paging occasion within the at least one paging frame for the device during a paging monitoring window, based on detecting a wake-up signal (WUS) for the device.

[0010] In each aspect of this specification, the start of the paging monitoring window may be the start of the first paging frame after a predetermined length of time after the slot in which the WUS is received.

[0011] In each aspect of this specification, the paging monitoring window may have a time length equal to i) the time length of one system frame, ii) a time length including a first predetermined number of paging epochs, iii) a time length of a paging discontinuous reception cycle, iv) a time length corresponding to the length of a paging discontinuous reception cycle divided by the number of paging epochs, or v) a time length including a second predetermined number of slots.

[0012] In each aspect of the present specification, the WUS monitoring may be performed via a first receiver of the device, and the paging monitoring may be performed via a second receiver of the device.

[0013] In each aspect of the present specification, the method or the operations may include: receiving paging-related control information within the paging monitoring window and transitioning to a sleep state based on not acquiring the identifier of the device from a data channel received based on the paging-related control information.

[0014] In each aspect of the present specification, the method or the operations may include: transitioning to a sleep state at the end of the paging monitoring window based on failure to receive paging-related control information within the paging monitoring window.

[0015] In each aspect of the present specification, the method or the operations may include: receiving paging-related control information within the paging monitoring window and transitioning to a sleep state at the end of the paging monitoring window based on not obtaining the identifier of the device from a data channel received based on the paging-related control information.

[0016] In each aspect of the present specification, the method or the operations may include: receiving paging-related control information within the paging monitoring window and extending the paging monitoring window at the end of the paging monitoring window based on not obtaining the identifier of the device from a data channel received based on the paging-related control information.

[0017] In another aspect of the present disclosure, a method performed by a base station is provided. In another aspect of the present disclosure, a base station is provided, comprising: at least one transceiver; at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, storing at least one program code comprising instructions that, when executed, cause the at least one processor to perform operations. The method or the operations may include: transmitting a paging-related setting; and transmitting a paging message at a paging time for a device within a paging frame for the device during a paging monitoring window based on transmitting a wake-up signal (WUS) for the device. The paging frame and the paging time within the paging frame may be determined based on the paging-related setting and an identifier of the device.

[0018] In each aspect of this specification, the start of the paging monitoring window may be the start of the first paging frame after a predetermined length of time after the slot in which the WUS is transmitted.

[0019] In each aspect of this specification, the paging monitoring window may have a time length equal to i) the time length of one system frame, ii) a time length including a first predetermined number of paging epochs, iii) a time length of a paging discontinuous reception cycle, iv) a time length corresponding to the length of a paging discontinuous reception cycle divided by the number of paging epochs, or v) a time length including a second predetermined number of slots.

[0020] In each aspect of this specification, the WUS may be for a first receiver of the device, and the paging time may be for a second receiver of the device.

[0021] In each aspect of the present specification, the method or the operations may include: transmitting paging-related control information within the paging monitoring window and determining that the device is transitioning to a sleep state based on a data channel transmitted based on the paging-related control information not including the identifier of the device.

[0022] In each aspect of the present specification, the method or the operations may include: determining that the device transitions to a sleep state at the end of the paging monitoring window based on not transmitting paging-related control information within the paging monitoring window.

[0023] In each aspect of the present specification, the method or the operations may include: transmitting paging-related control information within the paging monitoring window and determining that the device transitions to a sleep state at the end of the paging monitoring window based on a data channel transmitted based on the paging-related control information not including the identifier of the device.

[0024] In each aspect of the present specification, the method or the operations may include: transmitting paging-related control information within the paging monitoring window and extending the paging monitoring window at the end of the paging monitoring window based on a data channel transmitted based on the paging-related control information not including the identifier of the device.

[0025] The above problem solving methods are only some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person having ordinary knowledge in the relevant technical field based on the detailed description below.

[0026] Some implementations of this specification may reduce signaling overhead by determining paging timing based on a low-power (LP) radio wake-up signal (WUS).

[0027] Some implementations of this specification may improve the reliability of LP-WUS transmissions.

[0028] Some implementations of this specification can reduce power consumption of the UE by minimizing unnecessary UE wake-ups.

[0029] According to some implementations of this specification, a UE using a low-power receiver can efficiently monitor paging.

[0030] According to some implementations of this specification, delay / latency occurring during wireless communication between communicating devices can be reduced.

[0031] The effects according to this specification are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0032] To aid in understanding implementations of this specification, the accompanying drawings, which are included as part of the detailed description, provide examples of implementations of this specification and, together with the detailed description, illustrate implementations of this specification:

[0033] To aid in understanding implementations of this specification, the accompanying drawings, which are included as part of the detailed description, provide examples of implementations of this specification and, together with the detailed description, illustrate implementations of this specification:

[0034] Figure 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied;

[0035] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification;

[0036] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification;

[0037] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP) based wireless communication system;

[0038] Figure 5 illustrates a resource grid of slots;

[0039] FIG. 6 illustrates physical channels used in a 3GPP-based communication system, which is an example of a wireless communication system, and a signal transmission / reception process using the channels;

[0040] Figure 7 illustrates a process for acquiring system information (SI);

[0041] Figure 8 illustrates a random access process that may be applied to implementation(s) of this specification;

[0042] FIG. 9 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH;

[0043] FIG. 10 illustrates a discontinuous reception (DRX) operation that may be applied to implementation(s) of the present specification;

[0044] Figure 11 illustrates paging times according to several scenarios;

[0045] FIG. 12 illustrates an example of LP-WUS transmission according to some implementations of this specification;

[0046] FIG. 13 is a diagram illustrating a control channel monitoring window for paging reception according to some implementations of the present specification;

[0047] Figure 14 illustrates a flow of UE operations to which some implementations of this specification may be applied;

[0048] Figure 15 illustrates the flow of BS operations to which some implementations of this specification may be applied.

[0049] Hereinafter, implementations according to this specification will be described in detail with reference to the attached drawings. The detailed description provided below, together with the attached drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only possible implementations of this specification. The detailed description below includes specific details to provide a thorough understanding of this specification. However, one of ordinary skill in the art will appreciate that this specification may be practiced without these specific details.

[0050] In some cases, to avoid ambiguity in the concepts of this specification, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device. Furthermore, identical components are described using the same drawing reference numerals throughout this specification.

[0051] The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented in wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented in wireless technologies such as Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved-UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System), and 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS that uses E-UTRA.3GPP LTE adopts OFDMA for the downlink (DL) and SC-FDMA for the uplink (UL). LTE-A (LTE-advanced) is an evolved form of 3GPP LTE.

[0052] For convenience of explanation, the following description assumes that this specification applies to 3GPP-based communication systems, such as LTE and NR. However, the technical features of this specification are not limited to this. For example, although the detailed description below is based on a mobile communication system corresponding to a 3GPP LTE / NR system, it can also be applied to any other mobile communication system, except for features specific to 3GPP LTE / NR.

[0053] For terms and technologies used in this specification that are not specifically explained, reference may be made to 3GPP-based standard documents, such as 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.321, 3GPP TS 38.331, etc.

[0054] In the examples of this specification described below, the expression "assumes" that a device "assumes" that the entity transmitting the channel transmits the channel in a manner consistent with the "assume." The entity receiving the channel may mean that, under the assumption that the channel was transmitted in a manner consistent with the "assume," the entity receiving the channel receives or decodes the channel in a manner consistent with the "assume."

[0055] In this specification, ' / ' can mean 'and / or'.

[0056] In this specification, UE may be fixed or mobile, and includes various devices that communicate with a BS (base station) to transmit and / or receive user data and / or various control information. UE may be called (Terminal Equipment), MS (Mobile Station), MT (Mobile Terminal), UT (User Terminal), SS (Subscribe Station), wireless device, PDA (Personal Digital Assistant), wireless modem, handheld device, etc. In addition, in this specification, BS generally refers to a fixed station that communicates with UE and / or other BS, and exchanges various data and control information with UE and other BS. BS may be called by other terms such as ABS (Advanced Base Station), NB (Node-B), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point, PS (Processing Server), etc. In particular, the BS in UTRAN is called a Node-B, the BS in E-UTRAN is called an eNB, and the BS in a new radio access technology network is called a gNB. For convenience of explanation, BSs are collectively referred to as BSs below, regardless of the type or version of communication technology.

[0057] In this specification, a node refers to a fixed point that can transmit / receive radio signals by communicating with a UE. Various types of BSs can be used as nodes regardless of their names. For example, BSs, NBs, eNBs, pico-cell eNBs (PeNBs), home eNBs (HeNBs), relays, and repeaters can be nodes. Furthermore, a node may not be a BS. For example, it can be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a lower power level than the BS. Since an RRH or RRU (hereinafter referred to as RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between an RRH / RRU and a BS can be performed more smoothly than cooperative communication between BSs that are generally connected via a wireless line. Each node is equipped with at least one antenna. The antenna may be a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is also called a point.

[0058] In this specification, a cell refers to a certain geographical area where one or more nodes provide communication services. Therefore, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to the specific cell. In addition, the downlink / uplink signal of a specific cell refers to a downlink / uplink signal from / to a BS or node that provides communication services to the specific cell. A cell that provides uplink / downlink communication services to a UE is specifically referred to as a serving cell. In addition, the channel state / quality of a specific cell refers to the channel state / quality of a channel or communication link formed between a BS or node that provides communication services to the specific cell and the UE. In a 3GPP-based communication system, a UE can measure a downlink channel state from a specific node using CRS (Cell-specific Reference Signal) resources transmitted by antenna port(s) of the specific node on CRS resources allocated to the specific node and / or CSI-RS (Channel State Information Reference Signal) resources transmitted.

[0059] Meanwhile, 3GPP-based communication systems use the concept of cells to manage radio resources, and cells associated with radio resources are distinguished from cells in geographical areas.

[0060] A "cell" in a geographical area can be understood as the coverage over which a node can provide a service using a carrier, and a "cell" in a radio resource is associated with a bandwidth (BW), which is a frequency range configured by the carrier. Since downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a node can receive a valid signal from a UE, depend on the carrier carrying the signal, the coverage of a node is also associated with the coverage of the "cell" of the radio resource used by the node. Therefore, the term "cell" can sometimes be used to mean the coverage of a service by a node, sometimes a radio resource, and sometimes the range over which a signal using the radio resource can reach with a valid intensity.

[0061] Meanwhile, the 3GPP communication standard uses the concept of a cell to manage radio resources. A "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), i.e., a combination of a DL component carrier (CC) and an UL CC. A cell can be configured with DL resources alone or a combination of DL resources and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. For example, the combination of DL resources and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency can be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is established, the UE has only one radio resource control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information during RRC connection establishment / re-establishment / handover, and one serving cell provides security input during RRC connection re-establishment / handover. Such a cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs initial connection establishment procedures or initiates connection re-establishment procedures.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. An Scell ​​can be configured after an RRC (Radio Resource Control) connection establishment has been made, and is a cell that provides additional radio resources in addition to the resources of a special cell (SpCell). The carrier corresponding to a Pcell in downlink is called a downlink primary CC (DL PCC), and the carrier corresponding to a Pcell in uplink is called an UL primary CC (UL PCC). The carrier corresponding to an Scell ​​in downlink is called a DL secondary CC (DL SCC), and the carrier corresponding to the Scell ​​in uplink is called an UL secondary CC (UL SCC).

[0062] For dual connectivity (DC) operation, the term special cell (SpCell) refers to a Pcell of a master cell group (MCG) or a primary secondary cell (PSCell) of a secondary cell group (SCG). A SpCell supports PUCCH transmission and contention-based random access and is always activated. An MCG is a group of serving cells associated with a master node (e.g., BS) and consists of a SpCell (Pcell) and optionally one or more Scells. For a UE configured for DC, an SCG is a subset of serving cells associated with a secondary node and consists of a primary secondary cell (PSCell) and zero or more Scells. A PSCell is a primary Scell ​​of an SCG. For a UE in RRC_CONNECTED state that is not configured for CA or DC, there is only one serving cell consisting of Pcells. For a UE in RRC_CONNECTED state that is configured for CA or DC, the term serving cells refers to the set of cells consisting of SpCell(s) and all Scell(s). In DC, two medium access control (MAC) entities are configured in the UE: one for the MCG and one for the SCG.

[0063] For a UE for which CA is set and DC is not set, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells and a Scell ​​PUCCH group (also referred to as a secondary PUCCH group) consisting of only Scell(s) may be set. In the case of an Scell, an Scell ​​(hereinafter referred to as a PUCCH Scell) on which a PUCCH associated with the cell is transmitted may be set. An Scell ​​for which a PUCCH Scell ​​is indicated belongs to an Scell ​​PUCCH group (i.e., a secondary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the PUCCH Scell, and an Scell ​​for which a PUCCH Scell ​​is not indicated or which is a Pcell and is indicated as a cell for PUCCH transmission belongs to a Pcell PUCCH group (i.e., a primary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the Pcell. Hereinafter, if a UE is configured with an SCG and some implementations of this specification related to PUCCH are applied to the SCG, the primary cell may refer to a PSCell of the SCG. If a UE is configured with a PUCCH Scell ​​and some implementations of this specification related to PUCCH are applied to a secondary PUCCH group, the primary cell may refer to a PUCCH Scell ​​of the secondary PUCCH group.

[0064] In a wireless communication system, a UE receives information from a base station (BS) via the downlink (DL), and the UE transmits information to the base station via the uplink (UL). The information transmitted and / or received by the BS and UE includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and / or receive.

[0065] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from higher layers, and downlink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, and reference signals and synchronization signals (SS) are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal with a predefined, special waveform that is known to the BS and UE. For example, the demodulation reference signal (DMRS) and the channel state information RS (CSI-RS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from higher layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers.For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

[0066] In this specification, PDCCH (Physical Downlink Control CHannel) refers to a set of time-frequency resources (e.g., resource elements (REs)) that carry DCI (Downlink Control Information), and PDSCH (Physical Downlink Shared CHannel) refers to a set of time-frequency resources that carry downlink data. In addition, PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) refer to sets of time-frequency resources that carry UCI (Uplink Control Information), uplink data, and random access signals, respectively (respectively). Hereinafter, the expression that a user equipment transmits / receives a PUCCH / PUSCH / PRACH is used with the same meaning as that uplink control information / uplink data / random access signals are transmitted / received on or through the PUCCH / PUSCH / PRACH, respectively. Additionally, the expression that BS transmits / receives PBCH / PDCCH / PDSCH is used with the same meaning as transmitting broadcast information / downlink control information / downlink data on or through PBCH / PDCCH / PDSCH, respectively.

[0067] In this specification, radio resources (e.g., time-frequency resources) scheduled or configured by the BS to the UE for transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0068] Since the communication device receives a synchronization signal block (SSB), DMRS, CSI-RS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on a cell, it cannot selectively receive through an RF receiver only radio signals including only a specific physical channel or only a specific physical signal, or selectively receive through an RF receiver only radio signals excluding only a specific physical channel or only a physical signal. In actual operation, the communication device first receives radio signals on a cell through an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and decodes a physical signal and / or a physical channel within the baseband signals using one or more processors. Thus, in some implementations of the present specification, not receiving a physical signal and / or a physical channel may not actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather that it does not attempt to recover the physical signal and / or physical channel from the wireless signals, e.g., does not attempt to decode the physical signal and / or the physical channel.

[0069] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, massive MTC, which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / UEs is being discussed. The introduction of next-generation RATs that take advanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) into account is currently under discussion. 3GPP is currently conducting studies on next-generation mobile communication systems beyond EPC. For convenience, this technology is referred to as new RAT (NR) or 5G RAT, and a system that uses or supports NR is referred to as an NR system.

[0070] FIG. 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied. Referring to FIG. 1, the communication system (1) applied to the present specification includes a wireless device, a BS, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. Mobile devices may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. Home appliances may include a TV, a refrigerator, a washing machine, etc. IoT devices may include sensors, smart meters, etc. For example, a BS or network may also be implemented as a wireless device, and a specific wireless device may act as a BS / network node to other wireless devices.

[0071] Wireless devices (100a to 100f) can be connected to a network (300) via a BS (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via a network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the BS (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the BS / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0072] Wireless communication / connection (150a, 150b) can be performed between wireless devices (100a~100f) / BS (200) - BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection can be performed through various wireless access technologies (e.g., 5G NR) for uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication). Through the wireless communication / connection (150a, 150b), the wireless device and the BS / wireless device can transmit / receive wireless signals to / from each other. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of this specification.

[0073] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification. Referring to FIG. 2, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the BS (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 1.

[0074] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement functions, procedures, and / or methods described / suggested below. For example, the processor (102) may process information in the memory (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). In addition, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0075] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the functions, procedures, and / or methods described / suggested below. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0076] The wireless communication technology implemented in the wireless device (100, 200) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0077] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) may receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification.

[0078] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, suggestions and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The functions, procedures, suggestions and / or methods disclosed in this specification may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0079] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0080] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or flowcharts of this specification, to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the functions, procedures, proposals, methods and / or flowcharts of this specification, from one or more other devices. For example, one or more transceivers (106, 206) may be coupled to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, or the like, as referred to in the functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this specification, via one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals for processing using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0081] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 2 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0082] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 1, 100a), a vehicle (Fig. 1, 100b-1, 100b-2), an XR device (Fig. 1, 100c), a portable device (Fig. 1, 100d), a home appliance (Fig. 1, 100e), an IoT device (Fig. 1, 100f), a UE for digital broadcasting, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 1, 400), a BS (Fig. 1, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0083] In FIG. 3, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0084] In this specification, at least one memory (e.g., 104 or 204) can store instructions or programs that, when executed, cause at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0085] In this specification, a computer-readable (non-volatile) storage medium can store at least one instruction or computer program, which when executed by at least one processor causes the at least one processor to perform operations according to some embodiments or implementations of this specification.

[0086] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one computer memory may store instructions or programs, which, when executed, cause at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0087] In this specification, a computer program may be stored in at least one computer-readable (non-volatile) storage medium and may include program code that, when executed, performs operations according to some implementations of the present specification or causes at least one processor to perform operations according to some implementations of the present specification. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-volatile) storage medium.

[0088] A communications device of the present specification comprises at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to the example(s) of the present specification described below.

[0089] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.

[0090] The structure of the frame in Fig. 4 is merely an example, and the number of subframes, the number of slots, and the number of symbols in the frame can be varied. In an NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be set differently between multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., a subframe, a slot, or a transmission time interval (TTI)) consisting of the same number of symbols may be set differently between the aggregated cells. Here, the symbol may include an OFDM symbol (or a cyclic prefix - orthogonal frequency division multiplexing (CP-OFDM) symbol), an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol). In this specification, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbols are interchangeable.

[0091] Referring to Figure 4, in the NR system, uplink and downlink transmissions are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = 10 ms duration, divided into two half-frames of 5 ms each. Here, T is the basic time unit for NR. c = 1 / (△fmax *N f ) and △f max = 480*10 3 Hz, and N f =4096. For reference, T is the basic time unit for LTE. s = 1 / (△f ref *N f,ref ) and △f ref = 15*10 3 Hz, and N f,ref =2048. T s Wow T c is a constant κ = T s / T c = 64 relationship. Each half-frame consists of 5 subframes, and the duration of a single subframe is T. sf is 1ms. Subframes are further divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on the cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, and for an extended CP, each slot consists of 12 OFDM symbols. The numerology is exponentially scalable with a subcarrier spacing △f = 2. u *Depends on 15 kHz. The following table shows the subcarrier spacing for regular CP △f = 2. u *Number of OFDM symbols per slot at 15 kHz (N) slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0092]

[0093] The following table shows the subcarrier spacing for extended CP △f = 2. u*Indicates the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe at 15 kHz.

[0094]

[0095] For a subcarrier spacing setting u, slots are n in increasing order within a subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - Numbered as 1}.

[0096] Figure 5 illustrates the resource grid of a slot. A slot contains multiple symbols (e.g., 14 or 12) in the time domain. For each numeral (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N is indicated by higher layer signaling (e.g., radio resource control (RRC) signaling). start,u grid Starting from,N size,u grid,x *N RB sc Dog subcarriers and N subframe,u symb A resource grid of OFDM symbols is defined, where N size,u grid,x is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for downlink and UL for uplink. N RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB scis typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid is given to the UE by higher layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into common resource blocks (CRBs) and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for the subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for the subcarrier spacing configuration u coincides with 'Point A', which is a common reference point for the resource block grids. PRBs for subcarrier spacing u are defined within the bandwidth part (BWP) and range from 0 to N. size,u BWP,i -1, where i is the number of the bandwidth part. Common resource block n u CRB and bandwidth part i within physical resource block n PRB The relationship between the two is as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block (BRB) whose bandwidth part starts relative to CRB 0. A BWP comprises multiple consecutive RBs in the frequency domain. For example, a BWP may be a given numeral u within a BWP i on a given carrier. i A subset of contiguous CRBs defined for a carrier. A carrier may include up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the activated BWPs, and only a predetermined number (e.g., 1) of BWPs configured for the UE may be activated on the carrier.

[0097] For each serving cell in a set of DL BWPs or UL BWPs, the network configures at least an initial DL BWP and one (if the serving configuration is configured with uplink) or two (if supplementary uplink is used) initial UL BWPs. The network may also configure additional UL and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) cyclic prefix, and iii) N start BWP = Offset RB with the assumption of 275 set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates the resource indicator value (RIV). start BWP =O carrier +RB start and the number of contiguous RBs N size BWP =L RB , and the subcarrier spacing is provided by the RRC parameter offsetToCarrierO carrier; an index within the set of DL BWPs or UL BWPs; a set of BWP-common parameters and a set of BWP-specific parameters.

[0098] Virtual resource blocks (VRBs) are defined within the bandwidth part and are numbered from 0 to N. size,u BWP,i Numbered from -1, where i is the number of the bandwidth part. VRBs are mapped to physical resource blocks (PRBs) according to interleaved or non-interleaved mapping. In some implementations, for non-interleaved VRB-to-PRB mapping, VRB n may be mapped to PRB n.

[0099] A UE configured with carrier aggregation may be configured to use one or more cells. If the UE is configured to have multiple serving cells, the UE may be configured to have one or more cell groups. The UE may be configured to have multiple cell groups associated with different BSs. Alternatively, the UE may be configured to have multiple cell groups associated with a single BS. Each cell group of the UE consists of one or more serving cells, and each cell group includes a single PUCCH cell configured with PUCCH resources. The PUCCH cell may be a Pcell or an Scell ​​configured as a PUCCH cell among the Scells of the corresponding cell group. Each serving cell of the UE belongs to one of the cell groups of the UE and does not belong to multiple cell groups.

[0100] NR frequency bands are defined by two types of frequency ranges, FR1 and FR2, with FR2 also referred to as millimeter wave (mmW). The following table lists the frequency ranges in which NR can operate.

[0101]

[0102] Figure 6 illustrates physical channels used in a 3GPP-based communication system, which is an example of a wireless communication system, and a signal transmission / reception process using the channels.

[0103] When a UE is powered on again after being powered off or has been disconnected from a wireless communication system, it first searches for a suitable cell to camp on (search cell) and performs an initial cell search process, such as synchronizing with the cell or the BS of the cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an SSB / PBCH block) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE synchronizes with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). In addition, the UE can obtain broadcast information within the cell based on the PBCH. Meanwhile, the UE can check the downlink channel status by receiving a downlink reference signal (DL RS) during the initial cell search process.

[0104] A UE that has completed initial cell search can camp on the cell. After camping on the cell, the UE monitors the PDCCH on the cell and receives the PDSCH based on the downlink control information (DCI) carried by the PDCCH to obtain more specific system information (S12).

[0105] Thereafter, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, in the random access procedure, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) to the preamble through a PDCCH and a corresponding PDSCH (S14). If reception of the RAR for the UE fails, the UE may retry transmitting the preamble. In the case of contention-based random access, a contention resolution procedure (S16) may be performed, including transmission of a PUSCH based on UL resource allocation included in the RAR (S15) and reception of a PDCCH and a corresponding PDSCH.

[0106] The UE, which has performed the procedure described above, can then perform reception of PDCCH / PDSCH (S17) and transmission of PUSCH / PUCCH (S18) as a general uplink / downlink signal transmission process. The control information that the UE transmits to the BS is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK) (also referred to as HARQ-ACK), scheduling request (SR), channel state information (CSI), etc. CSI may include a channel quality indicator (CQI), a precoding matrix indicator (PMI), and / or a rank indicator. UCI is generally transmitted through PUCCH, but may be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, based on a request / instruction from the network, the UE can transmit UCI aperiodically via PUSCH.

[0107] Figure 7 illustrates a process for acquiring system information (SI). A UE can acquire AS / NAS information through the SI acquisition process. The SI acquisition process can be applied to UEs in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. RRC_CONNECTED is a state in which the UE has established an RRC connection with the network. RRC_IDLE is a state in which the UE is not registered in a specific cell and thus does not receive the access stratum (AS) context or other information received from the network. RRC_INACTIVE is a state in which the UE can move within an area established by the radio access network (RAN, e.g., BS(s)) without notifying the RAN while remaining in CM-CONNECTED, which is a state in which the UE has a signaling connection with the core network for connection management (CM). CM_CONNECTED is a state in which the UE has a non-access stratum (NAS) signaling connection with the core network, and CM_IDLE is a state in which the UE does not have any NAS signaling.

[0108] In a 3GPP-based system, SI can be divided into a master information block (MIB) and multiple system information blocks (SIBs). The MIB and multiple SIBs can be further divided into minimum SI and other SI. Here, minimum SI can be composed of MIB and System Information Block 1 (SIB1), and includes basic information required for initial connection and information for acquiring other SI. Here, SIB1 can be referred to as remaining minimum system information (RMSI). For more details, see the following.

[0109] - The MIB is always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms. The MIB contains information / parameters related to the reception of SIB1 and is transmitted over the PBCH of SSB. During initial cell selection, the UE assumes that half-frames with SSB(s) repeat with a period of 20 ms. Based on the MIB, the UE can check whether a control resource set (CORESET) for the Type0-PDCCH common search space exists. The Type0-PDCCH common search space is a type of PDCCH search space and is used to transmit the PDCCH that schedules the SI message. If a Type0-PDCCH common search space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbols that constitute a CORESET and (ii) PDCCH occasions (i.e., time domain locations for PDCCH reception) based on information in the MIB (e.g., pdcch-ConfigSIB1). If a Type0-PDCCH common search space does not exist, pdcch-ConfigSIB1 provides information about frequency locations where SSB / SIB1 exists and frequency ranges where SSB / SIB1 does not exist.

[0110] - SIB1 is transmitted on the downlink shared channel (DL-SCH) with a periodicity of 160 ms and a variable transmission repetition period within 160 ms. The default transmission repetition period of SIB1 is 20 ms, but the actual transmission repetition period may vary depending on the network implementation. SIB1 contains information related to the availability and scheduling (e.g., transmission period, SI window size) of the remaining SIBs (hereinafter, SIBx, where x is an integer greater than or equal to 2). For example, SIB1 may indicate whether SIBx is broadcast periodically or provided on-demand upon request of the UE. If SIBx is provided on-demand, SIB1 may contain information necessary for the UE to perform an SI request. SIB1 is a cell-specific SIB. The PDCCH scheduling SIB1 is transmitted through the Type0-PDCCH common search space, and SIB1 is transmitted through the PDSCH indicated by the PDCCH.

[0111] - SIBx is included in SI messages and transmitted over the PDSCH. Each SI message is transmitted within a periodically occurring time window (i.e., SI-window).

[0112] Figure 8 illustrates a random access process that may be applied to implementation(s) of the present specification. In particular, Figure 8(a) illustrates a four-step random access process, and Figure 8(b) illustrates a two-step random access process.

[0113] The random access procedure can be used for various purposes, such as initial access, uplink synchronization adjustment, resource allocation, handover, reconfiguration of radio links after radio link failure, and position measurement. The random access procedure is classified into a contention-based procedure and a dedicated (i.e., non-contention-based) procedure. The contention-based random access procedure is commonly used, including initial access, while the dedicated random access procedure is used for handovers, when downlink data arrives at the network, and to reestablish uplink synchronization in the case of position measurement. In the contention-based random access procedure, the UE randomly selects a random access (RA) preamble. Therefore, multiple UEs can transmit the same RA preamble simultaneously, necessitating subsequent contention resolution. In contrast, in the dedicated random access procedure, the UE uses an RA preamble uniquely assigned to the UE by the BS. Therefore, the UE can perform the random access procedure without collisions with other UEs.

[0114] Referring to Fig. 8(a), the contention-based random access process includes the following four steps. Hereinafter, the messages transmitted in steps 1 through 4 may be referred to as Msg1 through Msg4, respectively.

[0115] - Step 1: The UE transmits an RA preamble via PRACH.

[0116] - Step 2: The UE receives a random access response (RAR) from the BS via PDSCH.

[0117] - Step 3: The UE transmits UL data to the BS via PUSCH based on the RAR. Here, the UL data includes layer 2 and / or layer 3 messages.

[0118] - Step 4: The UE receives a contention resolution message from the BS via PDSCH.

[0119] A UE can receive information about random access from a BS through system information. For example, information about RACH occasions associated with SSBs on a cell can be provided through the system information. The UE can select an SSB among the SSBs received on the cell whose reference signal received power (RSRP) measured based on the SSB exceeds a threshold, and transmit an RA preamble through a PRACH associated with the selected SSB. For example, if random access is required, the UE transmits Msg1 (e.g., preamble) to the BS on the PRACH. The BS can distinguish each random access preamble through the time / frequency resource (hereinafter, RA occasion (RO)) on which the random access preamble was transmitted and the random access preamble index (PI). When the BS receives a random access preamble from the UE, the BS transmits an RAR message to the UE on the PDSCH. To receive a RAR message, the UE monitors an L1 / L2 control channel (e.g., PDCCH) CRC-masked with a Random Access-RNTI (RA-RNTI), which contains scheduling information for the RAR message, within a preset time window (e.g., ra-ResponseWindow). When scheduling information is received through the PDCCH masked with the RA-RNTI, the UE can receive an RAR message from a PDSCH indicated by the scheduling information. Thereafter, the UE determines whether an RAR for itself is included in the RAR message. Whether an RAR for itself exists can be determined by whether a Random Access preamble ID (RAPID) for a preamble transmitted by the UE exists. The index of the preamble transmitted by the UE and the RAPID may be the same.The RAR includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., timing advance command (TAC), UL scheduling information for Msg3 transmission (e.g., UL grant), and UE temporary identification information (e.g., Temporary-C-RNTI, TC-RNTI). The UE receiving the RAR transmits Msg3 through the PUSCH according to the UL scheduling information and timing offset value in the RAR. Msg3 may include the ID of the UE (or the global ID of the UE). In addition, Msg3 may include information related to an RRC connection request for initial access to the network (e.g., an RRCSetupRequest message). After receiving Msg3, the BS transmits Msg4, which is a contention resolution message, to the UE. If the UE receives the contention resolution message and the contention is successfully resolved, the TC-RNTI is changed to the C-RNTI. Msg4 includes the ID of the UE. And / or RRC connection related information (e.g., RRCSetup message) may be included. If the information transmitted via Msg3 does not match the information received via Msg4, or if Msg4 is not received for a certain period of time, the UE may consider contention resolution to have failed and retransmit Msg3.

[0120] Meanwhile, the dedicated random access process includes the following three steps. Hereinafter, the messages transmitted in steps 0 to 2 may be referred to as Msg0 to Msg2, respectively. The dedicated random access process may be triggered in the UE by the BS using a PDCCH (hereinafter, PDCCH order) for commanding the transmission of an RA preamble.

[0121] - Step 0: BS allocates RA preamble to UE through dedicated signaling.

[0122] - Step 1: The UE transmits an RA preamble via PRACH.

[0123] - Step 2: The UE receives RAR via PDSCH from the BS.

[0124] The operation of steps 1 and 2 of the dedicated random access process may be identical to steps 1 and 2 of the contention-based random access process.

[0125] NR systems may require lower latency than traditional systems. Furthermore, a four-step random access process may be undesirable, especially for latency-sensitive services such as URLLC. A low-latency random access process may be required in various scenarios within NR systems. When implementing implementations of this specification in conjunction with a random access process, implementations of this specification may be implemented in conjunction with the following two-step random access process to reduce the latency of the random access process.

[0126] Referring to Fig. 8(b), the two-step random access process may be composed of two steps: transmission of MsgA from a UE to a BS and transmission of MsgB from the BS to the UE. The MsgA transmission may include transmission of an RA preamble via a PRACH and transmission of an UL payload via a PUSCH. In the MsgA transmission, the PRACH and PUSCH may be transmitted using time division multiplexing (TDM). Alternatively, in the MsgA transmission, the PRACH and PUSCH may be transmitted using frequency division multiplexing (FDM).

[0127] A BS that receives MsgA can transmit MsgB to the UE. MsgB can include an RAR for the UE.

[0128] An RRC connection request related message (e.g., an RRCSetupRequest message) requesting to establish a connection between the RRC layer of the BS and the RRC layer of the UE may be transmitted in the payload of MsgA. In this case, MsgB may be used to transmit RRC connection related information (e.g., an RRCSetup message). Alternatively, the RRC connection request related message (e.g., an RRCSetupRequest message) may be transmitted via a PUSCH transmitted based on a UL grant in MsgB. In this case, the RRC connection related information (e.g., an RRCSetup message) related to the RRC connection request may be transmitted via a PDSCH associated with the PUSCH transmission after the PUSCH transmission based on MsgB.

[0129] Below, the physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.

[0130] The PDCCH carries DCI. For example, the PDCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the paging channel (PCH), system information on the DL-SCH, resource allocation information for control messages of a layer (hereinafter, upper layer) located above the physical layer in the protocol stacks of the UE / BS, such as a random access response (RAR) transmitted on the PDSCH, transmission power control commands, activation / release of configured scheduling (CS), etc. The DCI that includes resource allocation information for the DL-SCH is also called PDSCH scheduling DCI, and the DCI that includes resource allocation information for the UL-SCH is also called PUSCH scheduling DCI. The DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled with various identifiers (e.g., radio network temporary identifier (RNTI)) depending on the owner or intended use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked with the UE identifier (e.g., cell RNTI (C-RNTI)). If the PDCCH is for paging, the CRC is masked with the paging RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked with the system information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the random access RNTI (RA-RATI).

[0131] When a PDCCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, this is called cross-carrier scheduling. Cross-carrier scheduling using the carrier indicator field (CIF) can allow the PDCCH of a serving cell to schedule resources on another serving cell. On the other hand, when a PDSCH on a serving cell schedules a PDSCH or PUSCH on the serving cell, this is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS can provide the UE with information about the cell that schedules the cell. For example, the BS can provide the UE with information about whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by the serving cell, and if the serving cell is scheduled by another (scheduling) cell, which cell signals downlink assignments and uplink grants for the serving cell. In this specification, a cell that carries a PDCCH is called a scheduling cell, and a cell in which transmission of a PUSCH or PDSCH is scheduled by DCI included in the PDCCH, i.e., a cell that carries a PUSCH or PDSCH scheduled by the PDCCH, is called a scheduled cell.

[0132] The PDSCH is a physical layer DL channel for DL ​​data transport. PDSCH carries downlink data (e.g., DL-SCH transport blocks) and employs modulation methods such as Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM. Transport blocks (TBs) are encoded to generate codewords. A PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to radio resources along with the DMRS, generating an OFDM symbol signal and transmitting it through the corresponding antenna port.

[0133] Figure 9 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

[0134] The DCI carried by the PDCCH for scheduling the PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, which provides a value m for a row index m+1 of an allocation table for the PDSCH or PUSCH. A predefined default PDSCH time domain allocation is applied as the allocation table for the PDSCH, or a PDSCH time domain resource allocation table configured by the BS through RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH. A predefined default PUSCH time domain allocation is applied as the allocation table for the PUSCH, or a PUSCH time domain resource allocation table configured by the BS through RRC signaling pushch-TimeDomainAllocationList is applied as the allocation table for the PUSCH. The PDSCH time domain resource allocation table to be applied and / or the PUSCH time domain resource allocation table to be applied may be determined according to fixed / predefined rules (e.g., see 3GPP TS 38.214).

[0135] In the PDSCH time domain resource configurations, each indexed row defines a DL allocation-to-PDSCH slot offset K0, a start and length indicator value SLIV (or directly a starting position (e.g., a starting symbol index S) and an allocation length (e.g., a number of symbols L) of a PDSCH within a slot), and a PDSCH mapping type. In the PUSCH time domain resource configurations, each indexed row defines a UL grant-to-PUSCH slot offset K2, a starting position (e.g., a starting symbol index S) and an allocation length (e.g., a number of symbols L) of a PUSCH within a slot, and a PUSCH mapping type. K0 for PDSCH or K2 for PUSCH indicates the difference between a slot with a PDCCH and a slot with a PDSCH or PUSCH corresponding to the PDCCH. SLIV is a joint indication of a starting symbol S relative to the start of a slot with a PDSCH or PUSCH and the number L of consecutive symbols counted from the symbol S. For PDSCH / PUSCH mapping type, there are two mapping types: one is mapping type A and the other is mapping type B. For PDSCH / PUSCH mapping type A, a demodulation reference signal (DMRS) is mapped to a PDSCH / PUSCH resource at the beginning of a slot, and one or two symbols of the PDSCH / PUSCH resource can be used as DMRS symbol(s) depending on other DMRS parameters. For example, for PDSCH / PUSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in a slot depending on RRC signaling. For PDSCH / PUSCH mapping type B, the DMRS is mapped based on the first OFDM symbol of the PDSCH / PUSCH resource, and one or two symbols from the first symbol of the PDSCH / PUSCH resource can be used as DMRS symbol(s) depending on other DMRS parameters.For example, in the case of PDSCH / PUSCH mapping type B, DMRS is located in the first symbol allocated for PDSCH / PUSCH. In this specification, PDSCH / PUSCH mapping type may be referred to as mapping type or DMRS mapping type. For example, in this specification, PUSCH mapping type A may be referred to as mapping type A or DMRS mapping type A, and PUSCH mapping type B may be referred to as mapping type B or DMRS mapping type B.

[0136] The above scheduling DCI includes a frequency domain resource assignment (FDRA) field that provides allocation information regarding resource blocks used for PDSCH or PUSCH. For example, the FDRA field provides the UE with information regarding the cell for PDSCH or PUSCH transmission, information regarding the BWP for PDSCH or PUSCH transmission, and information regarding resource blocks for PDSCH or PUSCH transmission.

[0137] A control resource set (CORESET), which is a set of time-frequency resources for which a UE can monitor PDCCH, may be defined and / or configured. One or more CORESETs may be configured for a UE. A CORESET consists of a set of physical resource blocks (PRBs) with a duration of one to three OFDM symbols. The PRBs constituting the CORESET and the CORESET duration may be provided to the UE via higher layer (e.g., RRC) signaling. Within the configured CORESET(s), a set of PDCCH candidates is monitored according to the corresponding search space sets. In this specification, monitoring implies decoding (aka blind decoding) each PDCCH candidate according to the monitored DCI formats. The master information block (MIB) on the PBCH provides the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH for scheduling the PDSCH carrying the system information block 1 (SIB1). The PBCH may also indicate that there is no associated SIB1, in which case the UE may be instructed on other frequencies to search for the SSB associated with SIB1, as well as a frequency range in which it can assume that there is no SSB associated with SSB1. At least CORESET#0, which is the CORESET for scheduling SIB1, may be configured via the MIB or dedicated RRC signaling.

[0138] The set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets. The search space set may be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET configuration is associated with one or more search space sets, and each search space set is associated with one CORESET configuration.

[0139] A set of PDCCH candidates may be monitored in one or more CORESETs on an active DL BWP on each activated serving cell for which PDCCH monitoring is configured, where monitoring implies receiving each PDCCH candidate and decoding it according to the monitored DCI formats.

[0140] The following table illustrates the PDCCH search space.

[0141]

[0142] SS sets can be configured via system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Each DL BWP of a serving cell can have up to S (e.g., 10) SS sets configured. For example, the following parameters / information can be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration can be associated with one or more SS sets.

[0143] - searchSpaceId: Indicates the ID of the SS set.

[0144] - controlResourceSetId: Indicates the CORESET associated with the SS set.

[0145] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period period (in slot units) and the PDCCH monitoring period offset (in slot units).

[0146] - monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is configured. It is indicated through a bitmap, and each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDM symbol within the slot. The OFDMA symbol(s) corresponding to the bit(s) with a bit value of 1 corresponds to the first symbol(s) of the CORESET within the slot.

[0147] - nrofCandidates: AL={1, 2, 4, 8, 16} indicates the number of PDCCH candidates (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).

[0148] - searchSpaceType: Indicates whether the SS type is CSS or USS.

[0149] - DCI format: Indicates the DCI format of the PDCCH candidate.

[0150] Based on the CORESET / SS set configuration, the UE can monitor PDCCH candidates in one or more SS sets within a slot. The occasions (e.g., time / frequency resources) during which PDCCH candidates should be monitored are defined as PDCCH (monitoring) occasions. One or more PDCCH (monitoring) occasions can be configured within a slot.

[0151] Figure 10 illustrates a discontinuous reception (DRX) operation. In particular, Figure 10 illustrates a DRX cycle for a UE in RRC_CONNECTED state.

[0152] A UE may perform DRX operation while performing a process and / or method according to the implementation(s) of this specification. DRX configuration / operation is specified in the NR (e.g., Rel-17) standard. The features of DRX utilized for the purpose of reducing unnecessary power consumption of the UE are as follows. DRX defines a structure for a UE in an RRC_IDLE state (hereinafter referred to as I-DRX) and a structure for a UE in an RRC_CONNECTED state (hereinafter referred to as C-DRX), and both DRX structures are designed to reduce unnecessary power consumption in other periods by defining a period (e.g., an active time period or an on-duration period) in which the UE can expect to receive a DL signal to occur periodically. For reference, in the case of C-DRX, the start position of On-duration occurs periodically in the Rel-16 standard, and the size of the cycle that can be configured at this time (i.e., DRX cycle) can be determined / set through upper layer signaling, such as RRC signaling, provided by the BS to the UE.

[0153] Referring to FIG. 10, a DRX cycle consists of an On Duration and an Opportunity for DRX. The DRX cycle defines a time interval during which the On Duration is periodically repeated. The On Duration represents a time period during which the UE performs PDCCH monitoring to receive the PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE starts an inactivity timer and remains awake. On the other hand, if a PDCCH is not successfully detected during PDCCH monitoring, the UE enters a sleep state after the On Duration ends. Therefore, when DRX is configured, the UE may perform PDCCH monitoring / reception discontinuously in the time domain when performing a process and / or method according to the implementation(s) of this specification. For example, when DRX is configured, the PDCCH reception occasion (e.g., slot having PDCCH search space) in this specification may be configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, the UE may perform PDCCH monitoring / reception continuously in the time domain. For example, when DRX is not configured, the PDCCH reception occasion (e.g., slot having PDCCH search space) may be configured continuously. On the other hand, regardless of whether DRX is configured, PDCCH monitoring may be restricted in the time period configured as the measurement gap. DRX configuration information is received via upper layer (e.g., RRC) signaling, and whether DRX is turned on / off is controlled by the DRX command of the MAC layer. When DRX is configured, the UE may perform PDCCH monitoring discontinuously, as illustrated in FIG. 10.

[0154] The following table illustrates the UE processes related to DRX. Referring to the following table, DRX configuration information is received via upper layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by the DRX command of the MAC layer. When DRX is configured, the UE can perform PDCCH monitoring discontinuously, as illustrated in FIG. 10.

[0155]

[0156] Here, MAC-CellGroupConfig contains configuration information required to set MAC parameters for a cell group. MAC-CellGroupConfig may also contain configuration information related to DRX. For example, MAC-CellGroupConfig may contain DRX-related information as follows.

[0157] - Value of drx-onDurationTimer: Sets the duration at the start of the DRX cycle.

[0158] - Value of drx-SlotOffset: Sets the delay before starting drx-onDurationTimer.

[0159] - Value of drx-InactivityTimer: Sets the period after which a PDCCH epoch indicates a new UL or DL ​​transmission to the MAC entity.

[0160] - Value of drxRetransmissionTimerDL (per DL HARQ process except for the broadcast process): Sets the maximum duration until a DL retransmission is received.

[0161] - Value of drxRetransmissionTimerUL (per UL HARQ process): Sets the maximum duration until a grant for UL retransmission is received.

[0162] - Value of drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): Sets the maximum period of time after a DL initial transmission is received until a DL assignment for HARQ retransmission is received.

[0163] - Value of drx-HARQ-RTT-TimerUL (per UL HARQ process): Sets the maximum period from when a grant for UL initial transmission is received until a grant for UL retransmission is received.

[0164] - drx-LongCycleStartOffset: Sets the Long DRX cycle and drx-StartOffset, which defines the subframe where the Long and Short DRX cycles start.

[0165] - drx-ShortCycle (optional): Sets the short DRX cycle.

[0166] - drx-ShortCycleTimer (optional): Sets the duration for which the UE should follow the Short DRX cycle. For example, a value in multiples of the Short DRX cycle can be set by drx-CylceTimer. For example, the value of n can correspond to n*drx-ShortCycle.

[0167] The UE may perform PDCCH monitoring on serving cells within a DRX group when the DRX group is within its active time. Here, the DRX group is a group of serving cells configured by RRC and having the same DRX active time. When DRX is configured, the active time for serving cells within the DRX group is when i) drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or ii) drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell within the DRX group; or ra-ContentionResoultionTimer or msgB-RsponseWindow is running; Alternatively, the PDCCH indicating a new transmission addressed to the C-RNTI addressed to the MAC entity of the UE may include a time during which a random access response to a random access preamble not selected by the MAC entity among the contention-based random access preambles is not received.

[0168] Figure 11 illustrates paging times according to several scenarios. In particular, Figure 11 illustrates paging times according to the current NR standard.

[0169] If the UE has no ongoing data transmissions / receptions, the UE enters RRC_IDLE or RRC_INACTIVE to save power. When DL data for the UE arrives in the network, the network sends a paging message (e.g., paging DCI) at a paging occasion (PO) to trigger an RRC setup procedure, an RRC connection resume procedure, etc. A PO is a set of PDCCH monitoring occasions and may consist of multiple time slots (e.g., subframes or OFDM symbols), and a DCI with a CRC scrambled with a P-RNTI may be transmitted at the PO. For example, the following information may be transmitted by a DCI format with a CRC scrambled with a P-RNTI (e.g., DCI format 1_0):

[0170] - Short Messages Indicator according to Table 6

[0171] - Short messages according to Table 7. In Table 7, bit 1 is the most significant bit (MSB).

[0172] - Frequency domain resource allocation

[0173] - Time domain resource allocation

[0174] - VRB-to-PRB mapping according to Table 8

[0175] - Modulation and coding method

[0176] - Transport Block (TB) scaling

[0177] - Tracking reference signal (TRS) availability indication

[0178] - Reserved bits.

[0179]

[0180]

[0181]

[0182] In this specification, a PDCCH carrying a DCI format having a CRC scrambled with a P-RNTI is referred to as a paging PDCCH, and a PDSCH scheduled by the paging PDCCH is referred to as a paging PDSCH. A UE can decode the paging PDSCH based on scheduling information (e.g., frequency domain resource allocation, modulation and coding scheme, etc.) in the paging PDCCH. The paging PDSCH carries paging messages, which are used to notify one or more UEs and may include one or more UE identifiers (IDs). The following tables illustrate paging messages and descriptions of fields within the paging messages.

[0183]

[0184]

[0185] In multi-beam operations, the UE assumes that the same paging message is repeated across all transmitted beams. The paging message is the same for both radio access network (RAN)-initiated paging and core network (CN)-initiated paging.

[0186] In each DRX cycle, the UE remains in sleep mode during the OFF period, but is expected to wake up during paging occasions to monitor PDCCH for paging. The UE monitors one PO per DRX cycle. Paging DRX (also called idle mode DRX) is defined, where a UE in RRC_IDLE or RRC_INACTIVE is only required to monitor paging channels during one PO per DRX cycle. In each idle mode DRX (IDRX) cycle, the UE monitors only one PO within a specific PF. When a PDCCH for paging is received in a PO, the UE decodes the PDSCH to receive a paging message. If the paging is not for the UE, the UE falls back to sleep until the next PO. Figure 11 illustrates paging frames and paging occasions that can be monitored by a UE with a specific UE identifier.

[0187] A paging frame (PF) is a radio frame and may contain one or more POs or the starting point of a PO. The PF and PO for paging can be determined by predefined formulas. For example, in some implementations, the system frame number (SFN) for the PF may be determined by (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N), and the index i_s indicating the index of the PO may be determined by i_s = floor(UE_ID) mod Ns, where T is the DRX cycle of the UE determined by the minimum of UE-specific DRX value(s) and / or default DRX value broadcast with system information, N is the total number of paging frames within T, Ns is the number of paging occasions for the PF, PF_offset is an offset used for PF determination, and UE_ID is a value determined based on 5G-S-TMSI. A parameter Ns relating to the number of paging occasions per paging frame, a parameter nAndPagingFrameOffset used to derive the total number of paging frames in T, a parameter nrofPDCCH-MonitoringOccasionsPerSSB-InPO relating to the number of PDCCH monitoring occasions corresponding to SSBs in a paging occasion, and a length of a default DRX cycle may be signaled by SIB1, and the values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset. The PDCCH monitoring occasions for paging may be determined based on the parameter firstPDCCH-MonitoringOccasionOfPO indicating the first PDCCH monitoring occasion for paging of each PO of the PF, and the parameter nrofPDCCH-MonitoringOccasionsPerSSB-InPO.The above parameter firstPDCCH-MonitoringOccasionOfPO may be signaled by SIB1 for paging in the initial downlink BWP, and may be signaled with the corresponding BWP setting for paging in a DL BWP other than the initial downlink BWP.

[0188] To reduce power consumption, a UE may use Paging Early Indication (PEI) in RRC_IDLE and RRC_INACTIVE states. PEI informs the UE whether it will receive the next PO, and the UE may be notified whether it should monitor the PO ahead of its own PO. If PEI configuration is provided in the system information, a UE in RRC_IDLE or RRC_INACTIVE state that supports PEI may monitor PEI using the PEI parameters in the system information. The UE monitors one PEI per DRX cycle. A PEI occasion (PEI-O) is a set of PDCCH monitoring occasions and may consist of multiple time slots (e.g., subframes or OFDM symbols) in which a PEI can be sent. In multi-beam operations, the UE assumes that the same PEI is repeated on all transmitted beams. The time position of a PEI-O with respect to a PO of a UE is determined by a reference point and an offset, wherein the reference point is the beginning of a reference frame determined by a frame-level offset from the beginning of a first PF among PF(s) associated with the PEI-O, provided by pei-FrameOffset in SIB1, and the offset is a symbol-level offset from the reference point to the beginning of a first PDCCH monitoring occasion of this PEI-O, provided by firstPDCCH-MonitoringOccasionOfPEI-O in SIB1. If a PEI-O is associated with POs of two PFs, the two PFs are consecutive PFs computed by the parameters PF_offset, T, Ns, and N. When a UE detects a PEI (e.g., a DCI having a CRC scrambled with PEI-RNTI) and the PEI indicates a subgroup to which the UE belongs, the UE monitors the associated PO.If the UE does not detect a PEI during the monitored PEI period or if the PEI does not indicate a subgroup to which the UE belongs, the UE is not required to monitor the associated PO. When PEI and subgrouping are established, UEs monitoring the same PO can be divided into one or more subgroups. With subgrouping, the UE can monitor the associated PO if the corresponding bit for the subgroup to which the UE belongs is set to 1 by the PEI corresponding to its PO. For more details on PEI, refer to 3GPP TS 38.304 and 3GPP TS 38.213.

[0189] The following paging DRX cycles can be configured by the network: i) for CN-initiated paging, a default cycle is broadcast as system information, ii) for CN-initiated paging, a UE-specific cycle can be configured via non-access stratum (NAS) signaling, and iii) for radio access network (RAN)-initiated paging, a UE-specific cycle can be configured via RRC signaling. The UE uses the shortest of the applicable DRX cycles. For example, a UE in RRC_IDLE can use the shorter of the first two DRX cycles among the three DRX cycles, and a UE in RRC_INACTIVE can use the shortest of the three DRX cycles.

[0190] Power consumption depends on the length of wake-up periods (e.g., paging cycles). To meet battery life requirements, long eDRX cycles are expected to be used, resulting in high latency, making them unsuitable for services that require both long battery life and low latency. Because long eDRX cycles cannot meet latency requirements, eDRX may not be suitable for latency-critical use cases.

[0191] Recently, candidate technologies to support low-power wake-up signal (LP-WUS) and low-power wake-up receiver (LP-WUR) are being discussed to reduce power consumption of UE.

[0192] A UE in RRC_IDLE / RRC_INACTIVE state typically needs to wake up at least once per DRX cycle to receive signals, which accounts for a significant portion of power consumption during periods without signaling or data traffic. If the UE can receive signals (e.g., perform paging reception) for longer periods (e.g., every Nth DRX cycle rather than every DRX cycle), power consumption can be drastically reduced. This can be supported by having the LP-WUR perform some of the signal reception operations that the main radio (MR) would otherwise perform, and operate with ultra-low power consumption. The MR can be used for data transmission and reception, and can be set to a deep sleep mode where it is turned off or in deep sleep unless turned on. The following terms may be used in this specification:

[0193] > Main radio (MR): A transmit / receive module that operates for signals / channels other than those associated with low-power wake-up.

[0194] > LP-WUR (LR): A receiver module that operates to receive / process signals / channels related to low-power wake-up.

[0195] In RRC IDLE / INACTIVE mode, significant UE power saving gains (up to 90% or more) can be obtained by using LP-WUS / WUR to trigger UE MR paging monitoring compared to conventional I-DRX operation (with and without PEI) when sufficient relaxation is applied to MR radio resource management (RRM) measurements. Furthermore, compared to conventional eDRX operation, a significant reduction in paging latency and an acceptable level of UE power saving are observed when LP-WUS monitoring and the corresponding paging monitoring after MR wake-up are not constrained within the conventional paging time window (PTW) of eDRX.

[0196] In RRC CONNECTED mode, it is observed that using LP-WUS / WUR to trigger UE MR PDCCH monitoring yields modest UE power saving gains (up to 10%+) with little capacity impact compared to existing UE power saving techniques across various types of XR traffic and system load scenarios. Additionally, significant UE power saving gains (up to 60%+) and modest universal personal telecommunication (UPT) improvements (up to 10%+) are observed for file transfer protocol (FTP) and instant messaging (IM) traffic when the UE MR enters deep sleep during LR LP-WUS monitoring. Furthermore, the feasibility of offloading serving cell RRM measurements from UE MR to LP-WUR is validated in 3GPP Rel-18 studies through a reasonable evaluation methodology.

[0197] This specification describes several implementations of this specification related to a UE receiving a LP-WUS, receiving a paging PDCCH from a BS, and receiving the corresponding paging PDSCH. For example, several implementations of this specification are described where a UE starts and stops receiving a paging PDCCH from a BS after receiving an LP-WUS indicating its own identifier or the identifier of a UE group to which the UE belongs. Meanwhile, in order to save power consumption through LP-WUS, it may be important to minimize false alarms caused by waking up a UE that the BS does not intend to wake up, and to ensure that such a UE, if woken up, transitions to a sleep state. Taking this into account, several implementations of this specification are described where a UE woken up by an LP-WUS attempts to receive a PDCCH through an MR and transitions back to a sleep state.

[0198] This specification describes implementations of this specification based on the NR system, but implementations of this specification are not limited to the NR system unless otherwise specified. In addition, some implementations of this specification are described as examples based on the characteristics and structure of a DRX UE, but implementations of this specification are not limited to supporting a DRX UE unless otherwise specified. Therefore, implementations of this specification can be applied to other wireless communication transmission / reception and services even without a separate description.

[0199] The distinction between each method, implementation, or option in the following description is intended for clarity and is not intended to imply that each must be implemented independently. For example, the methods / implementations / options described below may be implemented individually, but at least some of them may be combined to the extent that they do not conflict with each other.

[0200] The timing of reception of LP-WUS by the UE may be separately described in some implementations of the present specification described below, or may be determined based on system information sent by the BS. For example, if LP-WUS can be received as 1-bit information in one unit (e.g., 1-slot or 1-symbol) through on-off keying, the offset and periodicity on the system frame can be simply set, and if decoded information is received through multiple on-off keyings for reliability, or information containing two or more bits is received, the time period during which the UE receives LP-WUS based on this, and the UE ID for LP-WUR for verification after LP-WUS reception can reuse the UE_ID used for conventional paging reception, similar to PEI.

[0201] As another example, it may be considered that the UE derives the reception location of the LP-WUS through the UE_ID given to the UE for LP-WUS reception. For example, the LP-WUS is repeated in a short period, and the BS may provide the UE with a parameter regarding the number of LP-WUS subgroups, N_LP-WUSsubgroup. This means the number of LP-WUS monitoring occasions (MOs) required for one UE subgroup, and in other words, the LP-WUS for one UE subgroup may be repeated for each LP-WUS MO. The UE may identify the LP-WUS MO to be monitored among the N_LP-WUSsubgroup MOs through the UE_ID given to the UE. In addition, when receiving K-bit information (e.g., K>2) through the LP-WUS monitoring, the LP-WUS reception may also be identified through the UE_ID.

[0202] Figure 12 illustrates an example of LP-WUS transmission according to some implementations of this specification.

[0203] In this specification, an LP-WUS occasion (LO) may be a concept that includes one or more LP-WUS monitoring occasions (MOs). For example, one LP-WUS MO may be replaced by one LO, or a LP-WUS MO group consisting of one or more LP-WUS MOs may be replaced by an LP-WUS occasion. This may be useful for associating each LP-WUS MO in an LO with a beam or reference signal given by the BS or predefined, and for allowing the UE to select and receive the best LP-WUS MO from the reference signal by having the BS always transmit the same information in the LP-WUS MO in the LO, or for improving reception performance by combining the signals received in each LP-WUS MO. The number of LP-WUS MOs in an LO may be directly configured through a message such as a SIB from the BS, or may be derived from the number of transmissions per periodicity of a reference signal, etc., that may be associated with each LP-WUS MO. Alternatively, without an explicit association, the UE may assume that each LP-WUS MO is a separate transmission. In a series of operations, the UE may assume that the same information is provided across LP-WUS MOs within the LO. Additionally, the LO may consider the following:

[0204] In a given LO, a UE may perform monitoring on all MOs within the LO or on only specific MOs.

[0205] The number of LP-WUS MOs within an LO may differ from the number of associated beams or reference signals. This may take into account the capacity of the LP-WUS MO. In this case, the UE may consider the following:

[0206] > In some implementations, if the number X of LP-WUS MOs in the LO is greater than the number Y of associated beams or reference signals, the UE may assume that the n-th LP-WUS MO is associated with the ((n-1) mod Y + 1)-th beam or transmitted reference signal.

[0207] > In some implementations, if the number X of LP-WUS MOs in an LO is less than the number Y of associated beams or reference signals, then i) the first LP-WUS MO may be associated with the "SFN mod Y"-th beam or reference signal, where SFN is the system frame number of the frame containing the LP-WUS MO, and ii) the other n-th LP-WUS MO may be associated with the ((m+n-1) mod Y + 1)-th beam or reference signal, if the first LP-WUS MO is associated with the m-th beam or reference signal.

[0208] FIG. 13 illustrates a PDCCH monitoring window for paging reception according to some implementations of the present specification.

[0209] <Method #1> PDCCH monitoring window after LP-WUS reception

[0210] A UE may receive a PO within a PF within a certain time window after receiving an LP-WUS indicating its own identifier or the identifier of a UE group to which it belongs. The start time and length of the window may be determined as follows.

[0211] > The start point of the window can be determined as follows:

[0212] >> In some implementations, the start point of the window may be the slot in which LP-WUS reception is completed.

[0213] >> In some implementations, the start of the window may be the start of the first slot after some time length T after the slot in which the LP-WUS reception is completed.

[0214] >> In some implementations, the start point of the window may be the frame in which LP-WUS reception is completed. For example, referring to FIG. 13, the start of PF #n may be the start of the paging PDCCH monitoring window for the UE with UE ID i. Or, as another example, referring to FIG. 13, the end of PF #n may be the start of the paging PDCCH monitoring window for the UE with UE ID i.

[0215] >> In some implementations, the start of the window may be the start of the first frame after a time length T following the slot in which LP-WUS reception is completed. For example, referring to FIG. 13, the start of PF #(n+1) may be the start of the paging PDCCH monitoring window for the UE with UE ID i.

[0216] >> In some implementations, the start of the window may be the start of the first paging frame after a time length T following the slot in which LP-WUS reception is completed. For example, referring to FIG. 13, the start of PF #(n+2) may be the start of the paging PDCCH monitoring window for the UE with UE ID i.

[0217] >> The above time length T may be a time considering the MR transition time in the LR of the UE, the wake-up time in the sleep state, etc., and may be a value given through SIB, a value included in the LP-WUS message, or a predefined value.

[0218] > The length of the window can be determined as follows:

[0219] >> In some implementations, the window length may be one system frame (e.g., 10 ms). For example, the window length may be the size of one paging frame, and the UE may attempt to receive the paging PDCCH in one paging frame after receiving the LP-WUS.

[0220] >> In some implementations, the length of the window may be determined based on the number of POs. For example, the UE may receive N POs from the start of the window. In some implementations, the length of the window may be the end of the Nth PO from the start (or the end of the slot / frame in which the Nth PO is located). In some implementations, N may be a value given via a SIB, a value included in an LP-WUS message, or a predefined value.

[0221] >> In some implementations, it may be considered to use only the method described with reference to FIG. 11 to determine the location of the Nth PO. For example, the location of the Nth PO may be determined by considering only POs determined in a conventional manner, excluding PFs and POs arbitrarily assumed by the UE as mentioned below.

[0222] >> In some implementations, the window length can be N slots, where N can be a value given via SIB, a value included in the LP-WUS message, or a predefined value.

[0223] >> In some implementations, the length of the window may increase until the UE successfully receives a paging DCI from the PO.

[0224] >> In some implementations, the length of the window is the interval between PFs (e.g. 'Paging DRX cycle length' / N s ) or may be an integer multiple of that value, where N s is the number of paging periods per PF.

[0225] >> In some implementations, the length of the window may be the paging DRX cycle length or an integer multiple of that value.

[0226] When a UE receives a paging PDCCH within a window, the following additional methods may be considered:

[0227] > A UE may assume that a frame within a window is its paging frame. In some implementations, this may be limited to the case where there is no paging frame of its own within a certain time period from the start of the window.

[0228] >> At this time, the UE can attempt to receive from all POs within the paging frame without considering the UE_ID.

[0229] >> Alternatively, the UE may attempt to receive only specific POs within a paging frame by taking into account the UE_ID as described with reference to FIG. 11.

[0230] > The UE can assume that the slot within the window is its paging time.

[0231] >> For example, assuming that a frame containing a slot within a window is its own paging frame, it can attempt to receive POs of all indices within the paging frame (regardless of whether the POs are POs that match its UE ID).

[0232] >> This may be limited to cases where there is no PO of one's own within a certain period of time from the start of the window.

[0233] > In order to receive a PO having a first PDCCH MO within a window, the UE may also receive PDCCH MOs outside the window. For example, a PO having a first PDCCH MO within a window is considered a PO within the window, and the UE may attempt to receive all PDCCH MOs of the PO within the window. Since a PO is a set of PDCCM MOs, even if some of the PDCCM MO(s) of the PO are within the window and the rest are outside the window, if the first PDCCM MO of the PO (e.g., the earliest PDCCH MO) is within the window, the UE and the BS may consider the entire PO to be within the window, and perform paging monitoring or paging DCI transmission on all PDCCM MOs of the PO.

[0234] <Method #2> Transition to sleep state during / after window

[0235] When a UE attempts to receive (e.g., monitors) a paging DCI within the paging PDCCH monitoring window determined via Method #1, it may operate considering conditions for stopping and transitioning to a sleep state within the window and conditions for transitioning to a sleep state outside the window. For example, the following may be considered.

[0236] > Method #2-1: If the UE succeeds in receiving at least one paging DCI within a window (e.g., if a paging DCI is detected on a paging PDCCH), the UE may not attempt to receive any more paging DCIs and may transition directly to sleep if the UE's identifier is not detected on the paging PDSCH received with that paging DCI.

[0237] > Method #2-2: The UE may continuously attempt to receive paging DCI within the window. The UE may continuously attempt to receive paging DCI within the window unless its identifier is detected in the paging PDSCH received with the corresponding paging DCI.

[0238] >> In this case (e.g., when the UE is triggered to detect a paging PDCCH by LP-WUS), the UE may attempt to receive multiple PDCCHs in a single paging epoch (e.g., if there are multiple PDCCH candidates in a paging epoch, it may continue to decode until the paging DCI is detected or until it completes decoding all of the multiple PDCCH candidates). This may be useful if the UE assumes any slot / frame as a paging epoch or paging frame due to LP-WUS.

[0239] > Method #2-3: The UE may transition to sleep immediately at the end of the window if it does not detect a paging DCI within the window.

[0240] > Method #2-4: If the UE detects a paging DCI within the window but does not receive its UE identifier on the paging PDSCH (or fails to receive the PDSCH), it can transition to sleep immediately at the end of the window.

[0241] > Method #2-5: If the UE detects a paging DCI within the window but does not receive its UE identifier on the paging PDSCH (or fails to receive the PDSCH), the paging PDCCH monitoring window may be extended by receiving an LP-WUS at the end of the window.

[0242] > Method #2-6: If the UE detects a PEI DCI within a window but does not receive its UE identifier within the PEI DCI, it can transition to sleep immediately at the end of the window.

[0243] > Method #2-7: The UE can transition to sleep immediately at the end of the window if it does not detect a paging DCI or PEI DCI within the window.

[0244] Method #1 or Method #2 described above can be applied independently or in combination of two or more.

[0245] According to some implementations of this specification, signaling overhead can be reduced by determining the paging time based on a low-power (LP) wake-up signal (WUS). According to some implementations of this specification, the reliability of LP-WUS transmission can be improved. According to some implementations of this specification, power consumption of the UE can be reduced by minimizing unnecessary waking up of the UE. According to some implementations of this specification, the reliability of LP-WUS transmission can be improved. According to some implementations of this specification, a UE using a low-power receiver can efficiently monitor paging.

[0246] Figure 14 illustrates a flow of UE operations to which some implementations of this specification may be applied.

[0247] A UE may perform operations according to some implementations of the present disclosure. The UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0248] Referring to FIG. 14, in the method of the UE, or in the UE, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: obtaining paging-related settings; determining paging frames for the device and at least one paging occasion for the device within each of the paging frames based on the paging-related settings and the identifier of the device; and performing paging monitoring for paging reception at at least one paging occasion within at least one paging frame for the device during a paging monitoring window based on detecting a wake-up signal (WUS) for the device (S1401) (S1403).

[0249] In some implementations, the start of the paging monitoring window may be the start of the first paging frame a predetermined length of time after the slot in which the WUS is received.

[0250] In some implementations, the paging monitoring window may have a time length equal to i) the length of one system frame, ii) a time length including a first predetermined number of paging epochs, iii) a time length of a paging discontinuous reception cycle, iv) a time length corresponding to the length of a paging discontinuous reception cycle divided by the number of paging epochs, or v) a time length including a second predetermined number of slots.

[0251] In some implementations, the WUS monitoring may be performed via a first receiver of the device, and the paging monitoring may be performed via a second receiver of the device.

[0252] In some implementations, the method or the operations may include: receiving paging-related control information within the paging monitoring window and transitioning to a sleep state based on not acquiring the identifier of the device from a data channel received based on the paging-related control information.

[0253] In some implementations, the method or the operations may include: transitioning to a sleep state at the end of the paging monitoring window based on failure to receive paging-related control information within the paging monitoring window.

[0254] In some implementations, the method or the operations may include: receiving paging-related control information within the paging monitoring window and transitioning to a sleep state at the end of the paging monitoring window based on not obtaining the identifier of the device from a data channel received based on the paging-related control information.

[0255] In some implementations, the method or the operations may include: receiving paging-related control information within the paging monitoring window and extending the paging monitoring window at an end of the paging monitoring window based on not obtaining the identifier of the device from a data channel received based on the paging-related control information.

[0256] Figure 15 illustrates the flow of BS operations to which some implementations of this specification may be applied.

[0257] A BS may perform operations according to some implementations of the present disclosure. The BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the BS may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0258] Referring to FIG. 15, in the method of the BS, or in the BS, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: transmitting paging-related settings; transmitting a paging message at a paging time for the device within a paging frame for the device during a paging monitoring window (S1503) based on transmitting a wake-up signal (WUS) for the device (S1501). The paging frame and the paging time within the paging frame may be determined based on the paging-related settings and an identifier of the device.

[0259] In some implementations, the start of the paging monitoring window may be the start of the first paging frame a predetermined length of time after the slot in which the WUS is transmitted.

[0260] In some implementations, the paging monitoring window may have a time length equal to i) the length of one system frame, ii) a time length including a first predetermined number of paging epochs, iii) a time length of a paging discontinuous reception cycle, iv) a time length corresponding to the length of a paging discontinuous reception cycle divided by the number of paging epochs, or v) a time length including a second predetermined number of slots.

[0261] In some implementations, the WUS may be for a first receiver of the device and the paging time may be for a second receiver of the device.

[0262] In some implementations, the method or the operations may include: transmitting paging-related control information within the paging monitoring window and determining that the device is transitioning to a sleep state based on a data channel transmitted based on the paging-related control information not including the identifier of the device.

[0263] In some implementations, the method or the operations may include: determining that the device is transitioning to a sleep state at the end of the paging monitoring window based on not transmitting paging-related control information within the paging monitoring window.

[0264] In some implementations, the method or the operations may include: transmitting paging-related control information within the paging monitoring window and determining that the device is transitioning to a sleep state at the end of the paging monitoring window based on a data channel transmitted based on the paging-related control information not including the identifier of the device.

[0265] In some implementations, the method or the operations may include: transmitting paging-related control information within the paging monitoring window and extending the paging monitoring window at an end of the paging monitoring window based on a data channel transmitted based on the paging-related control information not including the identifier of the device.

[0266] As described above, the examples disclosed herein are provided to enable those skilled in the art to implement and practice the present disclosure. While the examples have been described above with reference to the examples of the present disclosure, those skilled in the art will appreciate that various modifications and variations may be made to the examples of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the examples described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0267] Implementations of this specification can be used in wireless communication systems, BSs, UEs, and other equipment.

Claims

1. In a method performed by a device, Get paging related settings; Based on the paging-related settings and the identifier of the device, determining paging frames for the device and at least one paging time for the device within each of the paging frames; and Based on detecting a wake-up signal (WUS) for the device, performing paging monitoring for receiving paging in at least one paging period within at least one paging frame for the device during a paging monitoring window, The start of the above paging monitoring window is the start of the first paging frame after a predetermined length of time after the slot in which the above WUS is received. method.

2. In paragraph 1, The paging monitoring window has a time length equal to i) a time length of one system frame, ii) a time length including a first predetermined number of paging epochs, iii) a time length of a paging discontinuous reception cycle, iv) a time length corresponding to the length of a paging discontinuous reception cycle divided by the number of paging epochs, or v) a time length including a second predetermined number of slots. method.

3. In paragraph 1, The above WUS monitoring is performed through the first receiver of the device, The above paging monitoring is performed via the second receiver of the device. method.

4. In paragraph 1, Including receiving paging-related control information within the paging monitoring window and transitioning to a sleep state based on not acquiring the identifier of the device from a data channel received based on the paging-related control information. method.

5. In paragraph 1, Including transitioning to a sleep state at the end of the paging monitoring window based on failure to receive paging-related control information within the paging monitoring window; method.

6. In paragraph 1, Including receiving paging-related control information within the paging monitoring window and transitioning to a sleep state at the end of the paging monitoring window based on not acquiring the identifier of the device from a data channel received based on the paging-related control information. method.

7. In paragraph 1, Including receiving paging-related control information within the paging monitoring window and extending the paging monitoring window at the end of the paging monitoring window based on not obtaining the identifier of the device from the data channel received based on the paging-related control information. method.

8. At least one transmitter / receiver; at least one processor; and At least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Get paging related settings; Based on the above paging-related settings and the device identifier, determining paging frames for the device and at least one paging time for the device within each of the paging frames; and Based on detecting a wake-up signal (WUS) for the device, performing paging monitoring for receiving paging in at least one paging period within at least one paging frame for the device during a paging monitoring window, The start of the above paging monitoring window is the start of the first paging frame after a predetermined length of time after the slot in which the above WUS is received. machinery and tools.

9. In a computer-readable non-transitory storage medium, The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations, the operations comprising: Get paging related settings; Based on the above paging-related settings and the device identifier, determining paging frames for the device and at least one paging time for the device within each of the paging frames; and Based on detecting a wake-up signal (WUS) for the device, performing paging monitoring for receiving paging in at least one paging period within at least one paging frame for the device during a paging monitoring window, The start of the above paging monitoring window is the start of the first paging frame after a predetermined length of time after the slot in which the above WUS is received. Storage media.

10. In the method by the base station, Send paging related settings; Based on transmitting a wake-up signal (WUS) for the device, comprising transmitting control information for paging at a paging time for the device within a paging frame for the device during a paging monitoring window, The paging frame and the paging time within the paging frame are determined based on the paging-related settings and the identifier of the device, The start of the above paging monitoring window is the start of the first paging frame after a predetermined length of time after the slot in which the above WUS is transmitted. method.

11. In paragraph 10, The paging monitoring window has a time length equal to i) a time length of one system frame, ii) a time length including a first predetermined number of paging epochs, iii) a time length of a paging discontinuous reception cycle, iv) a time length corresponding to the length of a paging discontinuous reception cycle divided by the number of paging epochs, or v) a time length including a second predetermined number of slots. method.

12. In paragraph 10, The above WUS is for the first receiver of the above device, The above paging time is for the second receiver of the above device, method.

13. In paragraph 10, Including transmitting paging-related control information within the paging monitoring window and determining that the device transitions to a sleep state based on a data channel transmitted based on the paging-related control information not including the identifier of the device. method.

14. In paragraph 10, Including, based on the fact that the device does not transmit paging-related control information within the paging monitoring window, assuming that the device transitions to a sleep state at the end of the paging monitoring window; method.

15. In paragraph 10, Including transmitting paging-related control information within the paging monitoring window and considering that the device transitions to a sleep state at the end of the paging monitoring window based on a data channel transmitted based on the paging-related control information not including the identifier of the device. method.

16. In paragraph 10, Including transmitting paging-related control information within the paging monitoring window and extending the paging monitoring window at the end of the paging monitoring window based on the data channel transmitted based on the paging-related control information not including the identifier of the device. method.

17. At least one transmitter / receiver; at least one processor; and At least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Send paging related settings; Based on transmitting a wake-up signal (WUS) for the device, comprising transmitting control information for paging at a paging time for the device within a paging frame for the device during a paging monitoring window, The paging frame and the paging time within the paging frame are determined based on the paging-related settings and the identifier of the device, The start of the above paging monitoring window is the start of the first paging frame after a predetermined length of time after the slot in which the above WUS is transmitted. Base station.

Images