Method executed by user equipment and user equipment
By optimizing the number of packets and the CRC length of LP-WUS and selecting an appropriate CRC generator polynomial, the problem of excessive power consumption of user equipment in idle or inactive states is solved, achieving efficient reception of low-power wake-up signals, reducing false alarm rates, and extending battery life.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- SHARP KK
- Filing Date
- 2025-12-29
- Publication Date
- 2026-07-23
Smart Images

Figure CN2025146578_23072026_PF_FP_ABST
Abstract
Description
Methods executed by user equipment and user equipment Technical Field
[0001] This disclosure relates to the field of wireless communication technology, and specifically to a method and related actions performed by a user equipment for determining downlink resource parameters and related reception processes, as well as the corresponding user equipment. Background Technology
[0002] This section provides information that can help to better understand the various aspects of this disclosure. Therefore, the statements in this section should be read in this context and should not be construed as an admission of what is prior art or what is not prior art.
[0003] In 5G systems, besides latency, reliability, and availability, the energy efficiency of user equipment (UAE) is also a key factor. Typically, UAE consumes tens of milliwatts in idle or inactive states and hundreds of milliwatts in connected states. Depending on the application scenario, UAE may need to be charged weekly or daily, causing inconvenience in practical applications. Therefore, further reducing UAE power consumption and extending battery life are essential for improving energy efficiency and achieving a better user experience. For devices using micro-batteries or those where charging is inconvenient, such as sensors, automatic controllers, and wearable devices, where standby time may be 1-2 weeks or longer, improving their energy efficiency is even more critical.
[0004] User equipment (UE) can typically save power using discontinuous reception (DRX). To ensure connectivity, UE needs to periodically wake up in each DRX cycle to detect the control channel. Even when there is no data transmission for the UE, there is still periodic power consumption. If the UE could only wake up when there is a service transmission requirement, its power consumption would be significantly reduced. Therefore, the UE can be configured with a low-power auxiliary receiver to detect the low-power wake-up signal (LP-WUS) sent by the base station. The UE's main receiver can remain in a low-power state (e.g., sleep mode) until the low-power receiver receives the LP-WUS signal and wakes up the main receiver according to its indications for appropriate data processing. This allows the UE's service processing needs to be met with lower power consumption. To achieve this design goal, several issues need to be addressed in the system, such as how to ensure that the LP-WUS reception performance meets relevant requirements under various configurations, including false alarm rate requirements and how to determine the sequence used for LP-WUS based on user packet information. Summary of the Invention
[0005] To address at least some of the aforementioned problems, this disclosure provides a method and a user equipment that are executed by a user equipment, enabling LP-WUS to meet relevant requirements in various configurations and to determine the sequence used by LP-WUS based on user packet information.
[0006] According to this disclosure, a method performed by a user equipment (UE) is proposed, comprising: determining the number of packets for an LP-WUS detection opportunity LMO in an LP-WUS opportunity LO based on configuration parameters of a low-power wake-up signal LP-WUS in a system information block (SIB); and determining the length of a cyclic redundancy check (CRC) or the number of encoded bits used by the LP-WUS based on the number of packets.
[0007] Preferably, the method further includes: determining the generator polynomial of the CRC based on the determined CRC length.
[0008] Preferably, the determined CRC length is not less than the CRC length required to satisfy the single false detection rate (FAR) corresponding to the number of packets.
[0009] Preferably, the method further includes: in addition to the number of packets, determining the CRC length or the number of encoded bits based on the number of LP-WUS codewords or the number of payload bits.
[0010] Additionally, according to this disclosure, a method performed by a user equipment (UE) is proposed, comprising: determining a number of LP-WUS codewords based on the number of UE packets associated with a low-power wake-up signal LP-WUS on a pager opportunity (PO); and determining a set of sequences for detecting LP-WUS based on the number of LP-WUS codewords.
[0011] Preferably, the smallest set that can satisfy the determined number of codewords is selected.
[0012] Preferably, the method further includes: determining the number of OFDM symbols occupied by LP-WUS based on the determined set of sequences.
[0013] Furthermore, according to this disclosure, a user equipment is proposed, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the methods described above.
[0014] Invention Effects
[0015] According to this disclosure, the receiving performance of LP-WUS under various configurations can be guaranteed to meet the relevant requirements, and the sequence used by LP-WUS can be determined according to the user packet situation. Attached Figure Description
[0016] The above and other features of this disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:
[0017] Figure 1 is a schematic diagram showing the PO of a UE in a paging cycle according to the present disclosure.
[0018] Figure 2 is a flowchart illustrating a method performed by a user equipment according to Embodiment 1 of the present disclosure.
[0019] Figure 3 is a flowchart illustrating a method performed by a user equipment according to Embodiment 3 of the present disclosure.
[0020] Figure 4 is a block diagram illustrating the user equipment (UE) involved in this disclosure. Detailed Implementation
[0021] The present disclosure will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below, which are provided merely as examples to convey the scope of the subject matter to those skilled in the art. Furthermore, for the sake of simplicity, detailed descriptions of well-known technologies not directly related to the present disclosure have been omitted to prevent confusion in understanding the present disclosure.
[0022] Generally, unless a different meaning is clearly given and / or implied in the context of its use, all terms used in this disclosure shall be interpreted according to their ordinary meaning in the relevant art. Unless expressly stated otherwise, all references to an element, device, apparatus, component, part, step, etc., shall be publicly interpreted as referring to at least one instance of that element, device, apparatus, component, part, step, etc. Unless it must be explicitly described that a step follows or precedes another step and / or implicitly imply that a step must follow or precede another step, the steps of any method in the embodiments of this disclosure need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment of this disclosure may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa.
[0023] The following description uses 5G / NR mobile communication systems and their subsequent evolutions as example application environments to specifically describe several implementations according to this disclosure. However, it should be noted that this disclosure is not limited to the following implementations, but is applicable to many other wireless communication systems, such as communication systems after 5G and 4G and 3G mobile communication systems before 5G, 802.11 wireless networks, etc.
[0024] The following describes some of the terminology used in this disclosure. Unless otherwise specified, the terminology used in this disclosure is as defined herein. The terminology given in this disclosure may be used differently in 4G / LTE, 4G+ / LTE-Advanced, LTE-Advanced Pro, 5G / NR and later wireless communication systems or other communication systems, but a uniform terminology is used in this disclosure to simplify description. When applying the methods and processes of this disclosure to a specific system, the terminology used in that system can be substituted.
[0025] 3GPP: 3rd Generation Partnership Project
[0026] LTE: Long Term Evolution
[0027] NR: New Radio, New Wireless, New Air Interface
[0028] UE: User Equipment
[0029] gNB: NR base station
[0030] BWP: Bandwidth Part
[0031] SFN: System frame number
[0032] OFDM: Orthogonal Frequency Division Multiplexing
[0033] SCS: Sub-carrier spacing
[0034] RB: Resource Block
[0035] TDD: Time Division Duplexing
[0036] FDD: Frequency Division Duplexing
[0037] CSI: Channel State Information
[0038] DCI: Downlink Control Information
[0039] CRC: Cyclic Redundancy Check
[0040] QCL: Quasi-co-location
[0041] HARQ: Hybrid Automatic Repeat Request.
[0042] CORESET: Control resource set.
[0043] MIB: Master Information Block
[0044] SIB: System Information Block
[0045] SSB: SS / PBCH block, Synchronization Signal / Physical Broadcast Channel Block
[0046] SRS: Sounding Reference Signal
[0047] DMRS: Demodulation Reference Signal
[0048] CSI-RS: Channel State Information Reference Signal
[0049] RACH: Random-access channel
[0050] PBCH: Physical broadcast channel
[0051] PUCCH: Physical Uplink Control Channel
[0052] PUSCH: Physical Uplink Shared Channel
[0053] PRACH: Physical random-access channel
[0054] PDSCH: Physical downlink shared channel
[0055] PDCCH: Physical downlink control channel
[0056] UL-SCH: Uplink Shared Channel
[0057] DL-SCH: Downlink Shared Channel
[0058] C-RNTI: Cell Radio Network Temporary Identifier
[0059] P-RNTI: Paging RNTI, Temporary Identifier for Paging Wireless Network
[0060] RA-RNTI: Random Access RNTI, Temporary Identifier for Random Access Wireless Networks
[0061] CS-RNTI: Configured Scheduling RNTI, a temporary identifier for configuring and scheduling wireless networks.
[0062] SI-RNTI: System Information RNTI, Temporary Identifier for Wireless Networks
[0063] TC-RNTI: Temporary C-RNTI, Temporary Cell Radio Network Identifier
[0064] LP-WUS: Low Power Wake-Up Signal
[0065] RRM: Radio Resource Management
[0066] RRC: Radio Resource Control
[0067] TCI: Transmission Configuration Indicator
[0068] MSB: Most Significant Bit
[0069] LSB: Least Significant Bit
[0070] PO: paging occasion
[0071] PF: paging frame
[0072] RRM: Radio Resource Management
[0073] PCI: Physical Cell Identifier
[0074] UAI: UE Assistance Information
[0075] The following is a description of the technologies associated with this disclosure. Unless otherwise specified, the same terms in the specific embodiments have the same meaning as in the associated technologies.
[0076] It is worth noting that the user equipment (UE) involved in this disclosure refers to any end device that accesses a communication network and receives services from it, such as a smartphone, mobile phone, tablet computer, mobile station, access terminal, sensor, wearable device, etc. When describing the methods used by the user equipment or performing related processes in this disclosure, terms such as "user" and "terminal" may be used. This disclosure does not specifically distinguish or limit these different terms in its descriptions and may use them interchangeably to describe the relevant steps and methods from different perspectives. Network equipment refers to devices that communicate with the user equipment, including but not limited to wireless base stations, gNBs, eNBs, wireless access points, wireless relays, user equipment with relay capabilities, etc. This disclosure may use a wireless base station as one form of network equipment implementation, but other forms of network equipment can be easily used to replace it in specific implementations.
[0077] In NR networks, User Equipment (UE) can maintain network connectivity even when there is no service data transmission, enabling always-on network service. For example, UEs in idle state (RRC_IDLE state) or inactive state (RRC_INACTIVE state) can periodically check if the base station has sent them paging information. When paging information is detected, the UE can establish a radio connection based on the paging information and related signaling to transmit service data.
[0078] To receive paging information from the network, the UE can determine several paging cycles (DRX cycles) and paging occasions (POs) within each paging cycle based on network configuration parameters, and detect the paging PDCCH on the PDCCH monitoring occasion (MO) associated with the paging occasion. If the UE detects the paging PDCCH, it performs relevant processing based on the information indicated in the DCI transmitted by the PDCCH, such as receiving the paging PDSCH or receiving a short message. According to relevant protocols in NR (e.g., 38.304 v17.0.0), an idle or inactive UE can determine one PO in each DRX cycle for detecting its own paging information. In a specific example, the UE can determine several paging parameters based on network configuration: the paging cycle parameter value T, which represents the length of a paging cycle as T frames (also called radio frames); the number of paging frames (PFs) N in a paging cycle; and the number of POs Ns for a PF, etc. A paging frame is a radio frame and may contain one or more Points of Interest (POs) or the start of a PO. This can be simply referred to as a PF associated with or containing Ns POs. For simplicity, this PF can be called the PF of a PO, and the PO can also be simply called the PO of the PF or the PO associated with the PF; therefore, the PF used to determine the PO for the UE can also be called the UE's PF. A paging opportunity (PO) consists of several PDCCH monitoring occasions for paging (PDCCH MOs, or simply MOs). When using multi-beam transmission in the network, different MOs can correspond to different beams, allowing user equipment using different downlink beams to obtain better reception. In each paging cycle, the user equipment determines a PO to monitor the paging PDCCH. Then, the user equipment can select the MOs in the PO to monitor the PDCCH based on relevant conditions. For example, the user equipment may select the MOs of one or more SSB beams to monitor the paging PDCCH based on SSB measurement information. The UE can determine the PO used to monitor its own paging information based on these configured paging parameters.
[0079] For example, based on relevant configuration parameters, there are N paging frames in T radio frames of a paging cycle. The user equipment (UE) determines one paging frame (PF) in the paging cycle as the paging frame used by the UE to detect paging information. When a paging frame PF has multiple POs, the UE determines one of them as the UE's PO. The UE can obtain the frame number (SFN) of the PF corresponding to the PO that the user needs to detect based on parameters such as the UE_ID. The SFN is determined to satisfy the following conditions:
[0080] (SFN+PF_offset)mod T=(T / N)*(UE_ID mod N)
[0081] Wherein, PF_offset is the offset value configured by the network to determine the paging frame, T is the paging cycle parameter determined by the user equipment, N is the number of paging frames in a paging cycle, mod is the modulo operation, and UE_ID is the UE identifier value used to determine the paging parameters according to the relevant protocol in NR (e.g., 38.304 v17.0.0), such as using some low bits of 5G-S-TMSI.
[0082] The UE determines the frame number of the paging frame (PF) and then determines the PO to be detected. According to network configuration parameters, one PF can be associated with Ns POs. The UE checks the relevant PDCCH on the MO of one of the POs to determine if there is a corresponding paging message, etc. This PO can also be called the UE's PO. For example, the user equipment can determine the PO to be detected based on the PO's sequence number i_s, where i_s can be obtained according to the following formula:
[0083] i_s = floor(UE_ID / N) mod Ns
[0084] Where Ns is the number of POs in a PF. floor is the floor operation. mod is the modulo operation.
[0085] A specific example is shown in Figure 1. In Figure 1, a UE can determine the SFN of its PF based on the aforementioned process and parameters such as UE_ID. Here, Ns = 2. The UE can also determine the sequence number of its PO in the PF's POs, i_s = 1. Then, the UE can determine the position of the PO that needs to be detected in the paging PDCCH during the paging cycle, which is the UE's PO in the figure. The figure only shows a schematic diagram of the UE's PO in two consecutive paging cycles. The situations in other paging cycles and examples using other paging parameters can be obtained similarly.
[0086] After the User Equipment (UE) determines the Point of Purchase (PO), it can determine the information of each Detection Opportunity (MO) based on parameters such as the search space set of the paging PDCCH configured in the network. For example, starting from the PF radio frame, the UE can determine the sequence number of the PO associated with the PF and the S*X consecutive MOs of the PO based on the search space set configuration and CORESET configuration of the paging PDCCH. Here, S is the number of SSBs actually transmitted in one SSB cycle in the network, i.e., the number of SSB beams, which can be determined, for example, by the ssb-PositionsInBurst parameter in SIB1. The default value of X is 1, but it can also be configured by higher layers. Each of the S MOs of the PO is associated with S different SSB sequence numbers, or in other words, they satisfy the QCL relationship according to the SSB numbering order. At this point, the MO of the x*S+Kth paging PDCCH is the PO associated with the Kth transmitted SSB, where x is a value of 0, 1, ..., X-1, and K is a value of 1, 2, ..., S. The paging PDCCH MO does not overlap with uplink symbols and is sequentially numbered starting from 0, beginning with the first paging PDCCH MO of the PF. Optionally, if additional time slots and / or symbol offset parameters are configured, the UE also determines the specific location of the MO from an offset following the PF radio frame.
[0087] User equipment can perform paging PDCCH detection on relevant time-frequency resources according to the method described above. The DCI in the paging PDCCH contains information such as whether the user needs to receive a corresponding paging message, whether there is a specific short message, etc. If a paging message is to be received, the DCI also indicates the PDSCH resource parameters used to transmit the paging message, including time-domain resources, frequency-domain resources, modulation scheme, etc. The user equipment can receive the paging PDSCH according to these parameters.
[0088] Based on the preceding procedures, several UEs within the same cell may detect the same PO (e.g., several UEs with the same UE_ID mod N and the same i_s value). Following similar analysis, the paging PDCCH transmitted on the PO may be used to indicate paging information for one or more of these UEs. Typically, UEs need to periodically detect relevant POs, even if the paging PDCCH on the PO does not indicate data transmission related to the UE or the paging message sent is unrelated to the UE. This consumes significant UE power, impacting battery life and reducing user experience.
[0089] One feasible method to reduce user power consumption is for the user equipment (UE) to use a low-power wake-up signal receiver (LR) to detect the wake-up signal (WUS) sent by the base station. When there is no data transmission, the UE's main radio (MR) remains in sleep mode to minimize power consumption. When data needs to be transmitted, the base station notifies the UE via the WUS. When the UE detects the wake-up information carried in the WUS, it wakes up the MR and performs corresponding data processing. Since this WUS is used for low-power receiver detection, it can also be called LP-WUS (low-power WUS). This specification may also refer to LP-WUS simply as WUS, without further explanation. The LP-WUS can carry relevant information needed to wake up the UE, such as information related to the UE ID, or indicator bits corresponding to the UE or UE packet, or codeword values related to the UE or UE packet, or a specific sequence corresponding to the UE or UE packet, etc., which can be called LP-WUS information. The UE can determine whether it has been woken up by the LP-WUS signal based on the LP-WUS information. Only when the user equipment (UE) detects LP-WUS information indicating the need to wake up its own user, its user group, or all users, will the UE wake up the master receiver to perform relevant data transmission. This includes detecting the paging PDCCH on the associated paging opportunity (PO) or transmitting PRACH. In this way, the UE can maintain its connection to the network with minimal power consumption and without affecting its fast response performance to network paging. When implementing LR and MR functions, the UE may not necessarily use independent modules; it may simply be a logical division of internal modules and functions. No specific limitations are made here.
[0090] In NR networks, base stations can configure one or more sets of LP-WUS resources and other parameters. UEs can determine certain time-frequency resources based on these parameters for LP-WUS detection. UEs can detect LP-WUS on the LP-WUS resources determined by these parameters. Since these resources repeat periodically in time, and base stations do not always transmit LP-WUS on all resources (for example, if no UE needs to be woken up on a paging cycle, LP-WUS may not be transmitted), these time-frequency resources that may be used to transmit LP-WUS are also called LP-WUS monitoring occasions (LMOs). Base stations may use beam (also called spatial filters) scanning to cover the cell, using different beams to transmit LP-WUS on different LMOs, so that the UE can select the LMO with the optimal beam for LP-WUS detection. Base stations may also use repetition to transmit the same LP-WUS on multiple LMOs using the same beam to improve the performance of UE-side LP-WUS reception and detection. Additionally, the base station may use different LMOs to transmit different LP-WUS to indicate information about different UEs associated with the same PO. In this case, the set of several LMOs can be called a LO (LP-WUS occasion). For simplicity, a LO can be said to contain or be associated with several LMOs, and the LMOs can be called the LMOs of the LO. The UE can determine the LO to be detected according to the relevant configuration and detect LP-WUS on the LMOs therein. In this disclosure, for ease of description, sometimes the description is from the perspective of the base station configuring LO / LMO resources, and sometimes it is from the perspective of the UE detecting LO / LMOs. These two descriptions can be considered equivalent and interchangeable.
[0091] LP-WUS can use OOK (On-Offkeying) waveforms for transmission to reduce receiver complexity and UE power consumption. For compatibility with existing NR equipment, OOK can be generated using a method compatible with downlink CP-OFDM symbols in NR, making it easy for base stations to transmit signals with different waveforms. For example, the base station can use DFT-IFFT to generate LP-WUS OOK symbols. In this case, an OFDM symbol can contain an integer F OOK symbols within the LP-WUS bandwidth, where F is an integer from 1 / 2 / 4 / 8 / 16. Therefore, the time-domain parameters of relevant LP-WUS resources, or LO or LMO, such as length and location, can also be described using OFDM symbols, time slots, and frames. When generating LP-WUS, the base station may use different multi-carrier parameters to generate OOK symbols. For example, it may use CP-OFDM symbols with different subcarrier spacings (SCS) for the generation of LP-WUS / LP-SS. In this case, the SCS parameters can also be simply referred to as the SCS parameters of LP-WUS or LP-SS.
[0092] In NR, different SCS parameters can be applied to different frequency bands. For example, for the FR1 band, an SCS of 15kHz or 30kHz can be used for downlink signal transmission; for the FR2 band, an SCS of 60kHz or 120kHz can be used; and for the FR2-2 band, an SCS of 480kHz or 960kHz may be used. These SCS parameters are typically represented by the u parameter in NR, for example, an SCS of 2... u *15kHz means that u=0 corresponds to an SCS of 15kHz; u=1 corresponds to an SCS of 30kHz; ...; u=6 corresponds to an SCS of 960kHz, and so on. Using the u parameter to describe the SCS is completely equivalent to directly using the size of the SCS (e.g., 15kHz / 30kHz...).
[0093] In addition, the LP-WUS transmitted by the base station occupies a certain bandwidth. For ease of explanation, the bandwidth used by LP-WUS can also be configured / described using the number of subcarriers of the OFDM symbol (i.e., the number of REs, which can also be converted into the number of RBs). Furthermore, for the convenience of UE receiver implementation, some guard bands are reserved outside the effective bandwidth and are not used for signal transmission; these can be called guard bands. In this invention, unless otherwise specified, the frequency domain bandwidth used for transmitting LP-WUS includes the bandwidth actually used for transmitting OOK symbols and the guard band.
[0094] The base station can also transmit LP-SS (lower power synchronization signal) for UE to perform related synchronization and RRM measurements. LP-SS can use similar waveforms and modulation schemes as LP-WUS, etc. The parameter descriptions of LP-WUS in this disclosure, such as SCS, bandwidth RB, and symbols, also apply to LP-SS and will not be described in detail here.
[0095] If the base station provides LP-WUS related resource configuration, and the UE has the capability to perform LP-WUS detection, and the measurement values used to determine whether the UE meets the LP-WUS detection conditions also meet the threshold requirements, the UE can apply relevant procedures to detect LP-WUS on the LO. For example, the UE can detect the LO according to a configured period, and the UE detects at least one LO in each period. This period can be called a LO monitoring cycle. The LO monitoring cycle may have different names, such as LP-WUS minitoring cycle, LP-WUS detection period, or LO detection period, etc. In the following text, we will use LO monitoring cycle for related explanations. Since the UE detects the LO to determine whether the PO needs to detect the PDCCH in the corresponding paging cycle, the monitoring cycle can be related to the UE's paging cycle. For example, the monitoring cycle (length) is always equal to the paging cycle (length) used by the UE. In this case, the base station does not need to specifically configure relevant LO monitoring cycle parameters for the UE, and the UE can use the determined paging cycle length to determine the LO monitoring cycle length.
[0096] When a base station uses LP-WUS to indicate the UE's wake-up information, it can use the OOK signal to represent the relevant wake-up information. For example, the ON and OFF states of the OOK signal can be used to represent "1" and "0", with one "1" or "0" representing one OOK symbol. In this way, several OOK symbols can be used to represent LP-WUS information.
[0097] When a UE detects LP-WUS, it needs to ensure that the LP-WUS reception performance meets requirements, such as the false alarm rate (FAR, also known as the false alarm probability) and the missed detection rate (MDR, also known as the missed detection probability). FAR refers to the ratio of LP-WUS information that the UE incorrectly detects but mistakenly identifies as correct. If the UE uses LP-WUS information that it doesn't actually use to wake itself up, or misinterprets other signals or noise as LP-WUS information to wake itself up, the UE will be falsely woken up at times when it doesn't need to, resulting in less or no power saving effect. Therefore, the UE's LP-WUS detection FAR needs to be below a certain requirement to ensure the power saving effect of the UE in the system. This disclosure describes how the UE determines another set of parameters based on the relevant LP-WUS configuration parameters to meet the relevant reception requirements. Furthermore, this disclosure describes the relevant methods and processes using UEs in idle state (RRC_IDLE state) or inactive state (RRC_INACTIVE state) as examples. To simplify the description, the state descriptions of relevant steps may be omitted, and the UE or user equipment may be referred to directly. If the UE is in other states, such as a UE in connected state (RRC_CONNECTED state), LP-WUS may also be used to detect wake-up information to save power, and similar methods or steps may be applied in this case. The processing steps for connected UEs will not be illustrated here; they can be easily implemented through analogy.
[0098] The implementation of each step in this disclosure will be described in more detail below in specific embodiments.
[0099]
Example 1
[0100] When configuring LP-WUS resources, a single LO (Location-Oriented Array) can contain several LMOs (Local Mobile Objects) for different purposes. For example, they can be used to transmit the same LP-WUS information on LMOs of different beams to enhance coverage, or to repeatedly transmit the same LP-WUS information on LMOs of the same beam to improve reception performance, or to transmit different LP-WUS information on different LMOs to mitigate potential latency during multiple UE wake-up calls and improve the efficiency of UE wake-up in the system. For instance, in a LO, each beam has K LMOs, which can be divided into M groups, with R LMOs in each group. The same LP-WUS information is transmitted repeatedly on the R LMOs within the same group to improve downlink reception performance. LMOs in different groups can transmit different LP-WUS information; for example, they can transmit LP-WUS information for waking up different UE groups to improve the efficiency of UE wake-up in the system. Here, the number of packets M can also be equivalent to the number of different LP-WUS (information) packets that may be transmitted in a single LO, or the number of different LP-WUS (information) packets that a UE may detect in a single LO. Depending on the base station configuration, R and M can be values of 1 or greater than 1. For example, if the base station does not configure the R parameter, the UE can use R=1; otherwise, the UE determines the value of R based on the R parameter configured by the base station. Typically, for these M groups of LMOs, the UE cannot know in advance whether there will be LP-WUS transmissions or which group of LMOs will be used to wake up the UE's LP-WUS information. Therefore, if the UE has not yet detected the LP-WUS that will wake it up in one LMO packet in the LO, it needs to continue detecting LMOs in the remaining packets.
[0101] When a UE detects LP-WUS, it typically needs to meet certain FAR (Failure Rate of Arrival) requirements, such as a FAR of no more than 1% on a single LO (Local Opening), ensuring that the UE is not falsely woken up more than 1%, thus guaranteeing power saving for the UE. CRC (Cyclic Redundancy Check) can be used to ensure FAR. When transmitting LP-WUS, the base station generates several CRC bits based on the CRC generator polynomial and the bits used to indicate LP-WUS information (i.e., the payload, which represents LP-WUS information using several bits), and transmits them together with the payload. The UE can determine whether the received information is erroneous based on the received information, including the payload and CRC, reducing the rate of mistaking erroneous information for correct information, thereby avoiding false alarms. Generally, the CRC length (i.e., the number of CRC bits) is related to the achievable FAR. For example, assuming random errors, the FAR value is approximately 1 / 2. nHere, n is the CRC length. That is, using a CRC of length n, in the case of random errors, the CRC check ensures that the FAR (Failure Rate) is no higher than 1 / 2. n In real-world scenarios, due to the fact that the assumption of random error is not fully satisfied, the actual FAR may deviate slightly from this value, which will not be discussed further here.
[0102] When a UE detects LP-WUS in a LO, the total FAR (Failure Rate of Detection) is also related to the number of times the UE performs the detection. For example, suppose the probability of a false detection in a single detection is p, and the probability of no false detection is 1-p. Then the probability of detecting M LMO packets that may be transmitting different LP-WUS without any false detection is (1-p). M The probability of at least one false positive is 1-(1-p). M If the total false positive rate (FAR) of M tests is required to be no higher than the expected FAR value P, then the corresponding false positive rate p for each test is no higher than 1-(1-P). 1 / M When the p-value is very small (e.g., not greater than 1%), 1-(1-P) 1 / M Approximately equal to P / M. Table 1 provides a specific example. In the table, assuming the demand P is 1%, then the FAR for each row corresponding to different M values satisfies the condition that p is less than 1 / 2. n The value of n.
[0103] Table 1:
[0104] Using OOK symbols to transmit LP-WUS requires certain resources. For example, one OFDM symbol can transmit F OOK symbols. Depending on the configuration, F can be 1, 2, or 4, meaning one downlink OFDM symbol can transmit F bits of information. If we also consider using encoding methods (such as Manchester encoding, where two OOK symbols represent one valid bit, for example, '01' for 0 and '10' for 1), transmitting one bit of information using multiple OOK symbols requires more OFDM symbols to transmit the same number of bits of payload. When LP-WUS uses codewords to represent LP-WUS information, it may use several bits to represent the codeword; for example, using k bits can represent 2^k bits. k The codeword value is specified. Additionally, if CRC is used, n bits are required as CRC check bits. To improve system resource utilization, network devices can transmit LP-WUS with as few symbols as possible while meeting relevant performance requirements.
[0105] In an optional embodiment, the UE determines the CRC length used by LP-WUS based on the number M of LMO packets in LO.
[0106] Figure 2 is a flowchart illustrating a method performed by a user equipment according to Embodiment 1 of the present disclosure.
[0107] As shown in Figure 2, in step 201, the UE determines the number of LMO packets M in LO according to the LP-WUS configuration parameters of the base station in SIB.
[0108] In step 203, the UE determines the CRC length used by LP-WUS based on the number of packets M. For example, the CRC length determined by the UE is not less than the CRC length required to satisfy the single FAR requirement corresponding to M.
[0109] In step 205, the UE also determines the generator polynomial of the CRC based on the determined CRC length.
[0110] The UE can use a defined CRC generator polynomial to verify the received LP-WUS information.
[0111] In an optional example, the base station configures the number of LMO packets M in the LO or the number of different LP-WUS that may be transmitted in the LO in the LP-WUS configuration parameters in the SIB. The UE determines the value of M according to the configuration parameters. Optionally, the UE may also obtain the value of the number of packets M by other methods. For example, when the base station does not configure the number of packets M parameter, the UE can use M=1; or the UE obtains M by dividing the number of LMOs K of each beam by the repetition parameter R, i.e., M=K / R. Here, the number of packets M can also be equivalent to the number of different (information) LP-WUS that may be transmitted in a LO, or the number of (different information) LP-WUS that a UE may detect in a LO. In another optional example, if the network also supports dividing the K LMOs of a beam into G groups, with R*M LMOs in each group, a UE only needs to detect the LMOs in one subgroup of the G groups, where R is the repetition parameter and M is the number of different LP-WUS that the LMOs in that group may transmit, or the number of packets in the subgroup. At this point, the UE determines the number of packets M as the number of LMO packets within a subgroup, or the number of different LP-WUS that may be transmitted in the LMO subgroup related to the UE in the LO, or the number of LP-WUS (different information) that a UE may detect in a LO.
[0112] In one aspect of an optional embodiment, the UE determines the CRC length used by LP-WUS based on the number of packets M. For example, the CRC length determined by the UE is not less than the CRC length required to satisfy the single FAR requirement corresponding to M.
[0113] In optional examples, when M=1, the UE determines the first CRC length. When M=2, the UE determines the second CRC length. When M=3, the UE determines the third CRC length. When M=4, the UE determines the fourth CRC length. Here, the second CRC length is not less than the first CRC length, the third CRC length is not less than the second CRC length, and the fourth CRC length is not less than the third CRC length. In one specific example, the UE determines the first, second, third, and fourth CRC lengths to be 7, 8, 9, and 9 based on the aforementioned requirement of 1% total FAR. In another specific example, the same CRC lengths used with other radio channels in NR can be used; for example, the UE determines the first, second, third, and fourth CRC lengths to be 8, 8, 11, and 11. In yet another specific example, the same CRC lengths used with other 3GPP radio channels can be used; for example, the UE determines the first, second, third, and fourth CRC lengths to be 8, 8, 10, and 10. In yet another specific example, the impact of other factors on FAR can be considered; for example, the UE determines the first, second, third, and fourth CRC lengths to be 6, 8, 10, and 10. The specific values mentioned above are examples, and the system may set other values considering other factors. For example, multiple values may be determined through a predefined table in the network, and the UE can select one as the CRC length based on the number of packets M.
[0114] In an optional example, when M=1 or M=2, the UE determines the first CRC length. When M=3 or 4, the UE determines the second CRC length. Here, the second CRC length is not less than the first CRC length.
[0115] In one optional embodiment, LP-WUS uses codepoints to indicate UE wake-up information (LP-WUS information), for example, using different codepoint values to correspond to different UE groups. There may be multiple methods for the UE to determine the number of codepoints (i.e., the number of different codepoint values transmitted on LP-WUS, or the number of different LP-WUS messages that LP-WUS can indicate). Depending on the relevant paging parameter configuration, several UEs may detect paging PDCCH on the same PO. To improve the power saving effect of using LP-WUS, these UEs can be grouped so that different codepoint values can be used to wake up UEs in different groups. This reduces the probability of waking up irrelevant UEs and improves the overall power saving effect of the system. The base station can configure the number of UE groups on the PO via RRC signaling, and the UE can determine the corresponding group number based on relevant parameters (e.g., UE_ID) and the number of groups. The UE may also directly obtain the corresponding group number through higher-layer signaling. When a LO is associated with a PO, each UE packet on the PO can be assigned a codeword value (i.e., this codeword value is used to wake up the UE in the corresponding UE packet), and one codeword value can be assigned to all UE packets (i.e., this codeword value is used to wake up all UE packets). In this case, the number of codewords is the number of UE packets plus 1. Optionally, if a LO is associated with X POs (X > 1), each UE packet can be assigned a codeword value, and one codeword can be assigned to all UE packets. In this case, the number of codewords is X * the number of UE packets + 1. Optionally, if a LO is associated with X POs (X > 1), each UE packet can be assigned a codeword value, and one codeword can be assigned to all UE packets on a PO. In this case, the number of codewords is X * (the number of UE packets + 1). Optionally, when Y LOs are associated with one PO (Y > 1), all UE packets on the PO can be further divided into Y subgroups. Each UE packet in a subgroup corresponds to a codeword value (that is, this codeword value is used to wake up the corresponding UE packet), and a codeword value is used to correspond to all UE packets in the subgroup (that is, this codeword value is used to wake up all UE packets in the subgroup). In this case, the number of codewords is the number of UE packets in the subgroup plus 1. Optionally, the LP-WUS codeword can be represented by a numerical value of several payload bits. The UE can determine the number of payload bits based on the determined number of LP-WUS codewords Nc, for example, the number of payload bits = ceil(log2(Nc)). ceil is the floor operation, and log2 is the logarithm operation with base 2.
[0116] In optional embodiments, the UE further determines the CRC length based on the number of codewords and the number of packets M. For example, the UE determines the CRC length such that the total number of payload bits and CRC bits is not less than the total number of bits associated with the number of packets M. Furthermore, the total number of bits for M=2 is not less than the total number of bits for M=1, the total number of bits for M=3 is not less than the total number of bits for M=2, and the total number of bits for M=4 is not less than the total number of bits for M=3. Table 2 provides a specific example: when the number of codewords is a value from 1 to 9, when M=1, the UE determines the CRC length to be 6, and the total number of bits is greater than 7. When M=2, 3, or 4, the UE determines the CRC length to be 8, and the total number of bits is greater than 9. When the number of codewords is a value from 10 to 33, when M=1, the UE determines the CRC length to be 3, and the total number of bits is greater than 7. When M=2, the UE determines the CRC length to be 6, and the total number of bits is greater than 10. When M=3 or 4, the UE determines the CRC length to be 8, and the total number of bits is greater than 12. The specific values mentioned above are examples, and the system may set other values by taking into account other factors. For example, multiple values may be determined through a predefined table in the network, and the UE may also determine / select one as the CRC length based on the number of codewords and the number of packets M.
[0117] Table 2
[0118] In optional embodiments, the UE further determines the CRC length based on the number of payload bits and the number of packets M. For example, the UE determines the CRC length such that the total number of payload bits and CRC bits is not less than the total number of bits related to the number of packets M. Furthermore, the total number of bits for M=2 is not less than the total number of bits for M=1, the total number of bits for M=3 is not less than the total number of bits for M=2, and the total number of bits for M=4 is not less than the total number of bits for M=3. Table 3 provides a specific example: when the number of payload bits is 1, 2, or 3, when M=1, the UE determines the CRC length to be 6, and the total number of bits is greater than 7. When M=2, 3, or 4, the UE determines the CRC length to be 8, and the total number of bits is greater than 9. When the number of payload bits is 4, 5, or 6, when M=1, the UE determines the CRC length to be 3, and the total number of bits is greater than 7. When M=2, the UE determines the CRC length to be 6, and the total number of bits is greater than 10. When M=3 or 4, the UE determines the CRC length to be 8, and the total number of bits is greater than 12. The specific values above are examples; other values may be set in the system considering other factors. For example, multiple values can be determined in the network through a predefined table, and the UE can also determine / select one as the CRC length based on the number of payload bits and the number of packets M.
[0119] Table 3
[0120] In another optional embodiment, after determining the CRC length, the UE also determines the generator polynomial of the CRC based on the determined CRC length.
[0121] In an optional example, when the CRC length determined by the UE is 3, the CRC polynomial is one of the following polynomials:
[0122] ●g(D)=D³+D+1
[0123] In an optional example, when the CRC length determined by the UE is 6, the CRC polynomial is one of the following polynomials:
[0124] ●g(D)=D6+D5+1
[0125] ●g(D)=D6+D5+D3+D2+D1+1
[0126] ●g(D)=D6+D2+D+1
[0127] In an optional example, when the CRC length determined by the UE is 7, the CRC polynomial is one of the following polynomials:
[0128] ●g(D)=D7+D3+1
[0129] ●g(D)=D7+D6+D5+D3+1
[0130] In an optional example, when the CRC length determined by the UE is 8, the CRC polynomial is one of the following polynomials:
[0131] ●g(D)=D8+D7+D4+D3+D+1
[0132] ●g(D)=D8+D6+D3+1
[0133] In an optional example, when the CRC length determined by the UE is 10, the CRC polynomial is one of the following polynomials:
[0134] ●g(D)=D10+D9+D8+D7+D6+D4+D3+1
[0135] In an optional example, when the CRC length determined by the UE is 11, the CRC polynomial is one of the following polynomials:
[0136] ●g(D)=D11+D10+D9+D5+1
[0137] In an optional example, when the CRC length determined by the UE is 12, the CRC polynomial is as follows:
[0138] One type of polynomial:
[0139] ●g(D)=D12+D11+D3+D2+D+1
[0140] ●g(D)=D12+D11+D10+D9+D8+D4+D+1
[0141]
Example 2
[0142] In optional embodiments, besides adding CRC check bits, LP-WUS can also meet the performance requirements of LP-WUS detection by channel coding of the LP-WUS information. The UE can determine the number of encoded bits based on the determined number of packets M, so that the LP-WUS detection performance meets the requirements. Encoding may use various methods, such as repeating the encoding of the bits of the codeword values used in the LP-WUS information, or performing base sequence-based block coding on the bits of the codeword values used in the LP-WUS information, to generate encoded bits. The encoded bits can be used to generate LP-WUS; for example, the encoded bits can be processed using Manchester encoding and OOK waveforms to generate LP-WUS. The method by which the UE determines the number of packets M can be referred to in other embodiments, and will not be repeated here.
[0143] As an optional example, the UE determines that the number of encoded bits is not less than the total number of bits associated with the number of packets M. Furthermore, the total number of bits for M=2 is not less than the total number of bits for M=1, the total number of bits for M=3 is not less than the total number of bits for M=2, and the total number of bits for M=4 is not less than the total number of bits for M=3. For example, the UE determines that the number of encoded bits is 7 when M=1, 8 when M=2, 9 when M=3, and 9 when M=4.
[0144] Optionally, when using the encoding scheme, LP-WUS can first generate a length greater than the total number of bits, and then truncate the first few bits to ensure that the number of bits after encoding is the number of bits determined by the UE.
[0145] In optional embodiments, the UE further determines the number of encoded bits based on the number of codewords and the number of packets M. For example, the total number of bits when M=2 is not less than the total number of bits when M=1, the total number of bits when M=3 is not less than the total number of bits when M=2, and the total number of bits when M=4 is not less than the total number of bits when M=3. Table 4 provides a specific example: when the number of codewords is a value from 1 to 9, when M=1, the UE determines the number of encoded bits to be 6. When M=2, the UE determines the number of encoded bits to be 8. When M=3 or 4, the UE determines the number of encoded bits to be 9. When the number of codewords is a value from 10 to 33, when M=1, the UE determines the number of encoded bits to be 12. When M=2, the UE determines the number of encoded bits to be 14, and so on. The specific values mentioned above are examples, and the system may consider other factors and set other values. For example, if multiple values are determined through a predefined table in the network, the UE can also select one of them as the number of encoded bits based on the number of codewords and the number of packets M.
[0146] Table 4
[0147] Optionally, the UE also determines the number of encoded bits based on the number of payload bits and the number of packets M. Table 5 provides a specific example: when the number of payload bits is 1, 2, or 3, the UE determines the number of encoded bits to be 6 when M = 1. When M = 2, the UE determines the number of encoded bits to be 8. When M = 3 or 4, the UE determines the number of encoded bits to be 9. When the number of payload bits is 4, 5, or 6, the UE determines the number of encoded bits to be 12 when M = 1. When M = 2, the UE determines the number of encoded bits to be 14, and so on. The specific values above are examples; the system may consider other factors and set other values. For example, if multiple values are determined through a predefined table in the network, the UE can also select one as the number of encoded bits based on the number of payload bits and the number of packets M.
[0148] Table 5
[0149] In another optional embodiment, the UE also determines the number of encoded bits based on the number of OOK symbols that can be transmitted on one OFDM symbol. Transmitting LP-WUS information using OOK symbols in the network requires certain resources. For example, F OOK symbols can be transmitted on one OFDM symbol, where F is also called the chip rate. Depending on the configuration, F can be 1, 2, or 4, meaning one downlink OFDM symbol can transmit 1, 2, or 4 OOK symbols. Manchester encoding can also be used to transmit LP-WUS in the network, using 2 OOK symbols to transmit 1 valid bit of information, simplifying receiver processing. Optionally, when the UE determines F to be 4 and uses Manchester encoding, the number of bits available for transmitting LP-WUS information on the OFDM symbol occupied by LP-WUS is always an even number. The UE can determine the even number of encoded bits that is closest to and not less than the number of encoded bits determined by the above method as the number of encoded bits. For example, if the number of encoded bits determined by the UE based on the number of blocks M and the number of codewords is 9, the UE determines to use 10 as the actual number of encoded bits; if the number of encoded bits determined by the UE based on the number of blocks M and the number of codewords is 14, the UE determines to use 14 as the actual number of encoded bits. When F is determined by the UE to be 1 or 2, the number of encoded bits determined by the UE according to the above method is the actual number of encoded bits.
[0150]
Example 3
[0151] In the network, binary sequences represented by OOK symbols may also be used to represent LP-WUS information, with different sequences corresponding to different codepoint values. These sequences can be defined in some way; for example, a set of sequences can be formed by searching for several sequences that meet the requirements (e.g., satisfying the FAR requirement under a certain signal-to-noise ratio) using a computer, or a set of sequences can be generated according to some method (e.g., using orthogonal coding, or small block length coding based on a predetermined base sequence). Different sequences in the set can be used to represent different codepoint values. Generally, to ensure performance requirements (e.g., FAR requirements), the number of codewords a sequence can represent is positively correlated with the sequence length. The sequence length is also positively correlated with the amount of system resources occupied by LP-WUS. Different sizes of sequence sets can be defined in the system to meet different codepoint requirements and to achieve better system resource utilization.
[0152] The UE can detect LP-WUS on the LO, for example, by using correlation detection to detect sequences in a sequence set on the LMO. If the detection result of a certain sequence meets the requirements (e.g., the maximum correlation value is higher than a threshold), the UE can determine that the sequence has been detected and use sequence-related codewords to determine the LP-WUS information. The number of codewords is the number of different LP-WUS information that an LP-WUS on an LMO can indicate.
[0153] There are several methods for a UE to determine the number of codewords. For example, depending on the relevant paging parameter configuration, several UEs may detect the paging PDCCH on the same PO. To improve the power saving effect of using LP-WUS, these UEs can be grouped so that LP-WUS can wake up UEs in different groups using different codeword values. This can reduce the probability of waking up irrelevant UEs and improve the power saving effect of the entire system.
[0154] Figure 3 is a flowchart illustrating a method performed by a user equipment according to Embodiment 3 of the present disclosure.
[0155] As shown in Figure 3, in step 301, the UE determines the number of LP-WUS codewords based on the number of UE packets on the PO. Here, the number of UE packets on the PO is the number of UE packets that use LP-WUS for wake-up indication, or the number of UE packets associated with LP-WUS.
[0156] When a LO is associated with a PO, each UE packet on the PO can be assigned a codeword value (i.e., this codeword value is used to wake up the corresponding UE packet), and one codeword value can be assigned to all UE packets (i.e., this codeword value is used to wake up all UE packets). In this case, the number of codewords is the number of UE packets plus 1. Optionally, if a LO is associated with X POs (X > 1), each UE packet can be assigned a codeword value, and one codeword can be assigned to all UE packets. In this case, the number of codewords is X * the number of UE packets plus 1. Optionally, if a LO is associated with X POs (X > 1), each UE packet can be assigned a codeword value, and one codeword can be assigned to all UE packets on a PO. In this case, the number of codewords is X * (the number of UE packets + 1). Optionally, when Y LOs are associated with one PO (Y > 1), all UE packets on the PO can be further divided into Y subgroups. Each UE packet in the subgroup corresponds to a codeword value (that is, the codeword value is used to wake up the corresponding UE packet), and a codeword value is used to correspond to all UE packets in the subgroup (that is, the codeword value is used to wake up all UE packets in the subgroup). In this case, the number of codewords is the number of UE packets in the subgroup plus 1.
[0157] In step 303, the UE determines the set of sequences used for LP-WUS detection based on the number of LP-WUS codewords.
[0158] Once the UE has determined the set of sequences for detecting LP-WUS, it can detect the received LP-WUS based on the sequences in the set.
[0159] In an optional example, the UE determines a sequence set as one of a set of several sequences, and the UE selects the smallest set that satisfies the number of codewords.
[0160] Sequence sets can be generated based on formulas or predefined tables. Table 6 provides a specific example. The system defines three sets of sequences: the first set is for sequences with no more than 33 codewords, the second set is for sequences with no more than 17 codewords, and the third set is for sequences with no more than 9 codewords. The sequence length and number in the first set are greater than those in the second set; the sequence length and number in the second set are greater than those in the third set.
[0161] Table 6:
[0162] In this example, when the number of codewords determined by the UE is 1-8, the UE selects the third set; when the number of codewords determined by the UE is 9-17, the UE selects the second set; and when the number of codewords determined by the UE is 9-17, the UE selects the first set.
[0163] Optionally, the UE determines the sequence set based on the configuration given to the base station, and the determined set is not less than the number of codewords determined by the UE. For a specific example, see Table 6. When the number of codewords determined by the UE is not greater than 9, the base station can configure any one of sets 1 / 2 / 3 as the set of sequences for detecting LP-WUS. When the number of codewords determined by the UE is not greater than 17 but greater than 9, the base station can configure any one of sets 1 / 2 as the set of sequences for detecting LP-WUS. When the number of codewords determined by the UE is not greater than 33 but greater than 17, the base station can configure set 1 as the set of sequences for detecting LP-WUS. The UE does not expect the set configured by the base station to fail to meet the codeword number requirement determined by the UE, or the UE does not expect the number of sequences in the set configured by the base station to be less than the number of codewords determined by the UE.
[0164] In another optional embodiment, each sequence in the sequence set may correspond to a sequence number, and the UE determines the codeword value based on the sequence number. When the codeword value corresponds to the UE group to which the UE belongs, or the codeword corresponds to all UE groups, the UE detects the associated PO. Optionally, the UE determines that the codeword value is equal to the sequence number. Optionally, the UE determines the association between the sequence number and the codeword value based on the size of the set and the number of codewords. For example, codeword value = floor(sequence number / interval); interval = floor(number of sequences in the set / number of codewords). Floor is a rounding operation.
[0165] Optionally, the UE determines a specific sequence of codeword values used to indicate that all UEs are to be woken up, and a sequence number used to indicate that the codeword value of a UE group is equal to the sequence number.
[0166] In another optional embodiment, the UE determines the number of OFDM symbols occupied by LP-WUS based on the sequence set determined by the preceding method. Transmitting LP-WUS using OOK symbols requires certain resources. For example, F OOK symbols can be transmitted on one OFDM symbol; depending on the configuration, F can be 1, 2, or 4, and one downlink OFDM symbol can transmit F bits of information. If the use of encoding methods (e.g., Manchester encoding) is also considered, using multiple OOK symbols to transmit one bit of information results in a higher number of OFDM symbols required to transmit the same amount of payload.
[0167] For example, the UE determines the number of OFDM symbols occupied by LP-WUS based on the sequence length in the sequence set. For instance, the number of symbols is ceil(sequence length * 2 / F), where the sequence length is the sequence in the sequence set. ceil is the floor function. F is the number of OOK symbols that can be transmitted on one OFDM symbol.
[0168] The following description uses FIG4 to illustrate a user equipment that can perform the methods described in detail above in this disclosure as an embodiment.
[0169] Figure 4 is a block diagram illustrating the user equipment (UE) involved in this disclosure.
[0170] As shown in Figure 4, the user equipment UE400 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 402 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Program instructions are stored on the memory 402. When executed by the processor 401, these instructions can perform the methods described in detail herein, executed by the user equipment.
[0171] The methods and related devices of this disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are merely exemplary, and the various embodiments described above can be combined with each other without contradiction. Furthermore, to avoid repetition, some steps or methods already described in one embodiment may not be repeated in the description of other aspects or embodiments if they may be reused in other aspects or embodiments, in order to avoid excessive redundancy. Those skilled in the art can combine related steps and methods. In addition, the methods of this disclosure are not limited to the steps and order shown above. The network nodes and user equipment shown above may include more modules, such as modules that can be developed or will be developed in the future for use with base stations, MMEs, or UEs, etc. The various identifiers shown above are merely exemplary and not restrictive, and this disclosure is not limited to the specific information elements exemplified by these identifiers. Those skilled in the art can make many variations and modifications based on the teachings of the illustrated embodiments. For example, in this disclosure, "1" and "0" are used to represent related indications or information, and they can be interchanged without contradiction. That is, "0" is used to indicate information indicated by "1" in this disclosure, and "1" is used to indicate information indicated by "0" in this disclosure. As another example, in the examples of this disclosure, some sequence numbers are arranged in ascending order to correspond to bits from MSB to LSB. Without contradiction, they could also be arranged in descending order to correspond to bits from MSB to LSB. Furthermore, unless otherwise specified, the sequence numbers in the examples of this disclosure are counted incrementally starting from 0. Sequence number 0 can correspond to the first element of the sequence, sequence number 0 can correspond to the second element of the sequence, and so on. These variations do not affect the process by which the UE determines the related information based on the related indication.
[0172] It should be understood that the above embodiments of this disclosure can be implemented by software, hardware, or a combination of both. For example, the various components inside the base station and user equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and so on.
[0173] In this disclosure, "base station" can refer to a mobile communication data and control switching center with high transmission power and wide coverage, including functions such as resource allocation and scheduling, and data reception and transmission. "User equipment" can refer to user mobile user equipment, such as mobile phones, laptops, and other user equipment that can wirelessly communicate with base stations or micro base stations.
[0174] Furthermore, the embodiments of this disclosure disclosed herein can be implemented on a computer program product. More specifically, the computer program product is one that has a computer-readable medium on which computer program logic is encoded, which, when executed on a computing device, provides related operations to implement the above-described technical solutions of this disclosure. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of this disclosure. This configuration of the disclosure is typically provided as software, code, and / or other data structures set or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk, or other media such as firmware or microcode on one or more ROM, RAM, or PROM chips, or downloadable software images, shared databases, etc., in one or more modules. The software or firmware or such configuration can be installed on a computing device to cause one or more processors in the computing device to perform the technical solutions described in the embodiments of this disclosure.
[0175] Furthermore, each functional module or feature of the base station equipment and user equipment used in each of the above embodiments can be implemented or executed by circuitry, which is typically one or more integrated circuits. Circuitry designed to perform the various functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs) or general-purpose integrated circuits, field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine. The aforementioned general-purpose processor or each circuit may be configured by digital circuitry or by logic circuitry. Furthermore, when advancements in semiconductor technology lead to advanced technologies that can replace current integrated circuits, this disclosure may also utilize integrated circuits obtained using such advanced technologies.
[0176] Although the present disclosure has been illustrated above in conjunction with preferred embodiments, those skilled in the art will understand that various modifications, substitutions, and changes can be made to the disclosure without departing from its spirit and scope. Therefore, the disclosure should not be limited by the above embodiments, but rather by the appended claims and their equivalents.
Claims
1. A method executed by a user equipment (UE), comprising: The number of packets for LP-WUS detection opportunity LMO in LP-WUS opportunity LO is determined based on the configuration parameters of the low-power wake-up signal LP-WUS in the System Information Block (SIB); and The length of the Cyclic Redundancy Check (CRC) or the number of encoded bits used by LP-WUS is determined based on the number of groups.
2. The method according to claim 1, further comprising: The generator polynomial of the CRC is determined based on the determined CRC length.
3. The method according to claim 1, wherein, The determined CRC length is not less than the CRC length required to satisfy the single false detection rate (FAR) corresponding to the number of packets.
4. The method according to claim 1, further comprising: In addition to the number of packets, the CRC length or the number of encoded bits is also determined based on the number of LP-WUS codewords or the number of payload bits.
5. A method performed by a user equipment (UE), comprising: The number of LP-WUS codewords is determined based on the number of UE packets associated with the low-power wake-up signal LP-WUS on the paging device PO; as well as The set of sequences used for LP-WUS detection is determined based on the number of LP-WUS codewords.
6. The method according to claim 5, wherein, Select the smallest set that satisfies the determined number of codewords.
7. The method according to claim 5, further comprising: The number of OFDM symbols occupied by LP-WUS is determined based on the set of sequences.
8. A user equipment, comprising: processor; as well as Memory, which stores instructions The instructions, when executed by the processor, perform the method described in any one of claims 1 to 7.