Management of uplink / downlink transmissions

Abstract

Certain examples provide an apparatus (10, 100) comprising: means (11, 15) for receiving, from a network node (120), information (302) indicative of one or more resources (303) for the apparatus to send a request (306) to suspend at least one activity within a time period (309), where the at least one activity comprises at least one of: at least one receive Rx process; at least one transport Tx process; or monitoring a control channel; means (11) for determining whether to request a pause of the at least one activity for the time period based at least in part on an energy state of the device; means (11, 15) for sending a request to the network node via the one or more resources in response, at least in part, to a determination that the request suspends the at least one activity within the time period; and means (11) for suspending the at least one activity for the time period in response at least in part to the determination.

Description

Technical Field

[0001] Examples of this disclosure relate to managing uplink UL and / or downlink DL transmissions. Various examples provide apparatus, methods, systems, and computer programs for managing UL and / or DL ​​transmission sessions. Some examples (though without affecting the foregoing) relate to enabling energy harvesting (EH) devices to temporarily suspend the Hybrid Automatic Repeat Request (HARQ) process. Background Technology

[0002] Traditional systems used for managing UL and / or DL ​​transfers (such as conventional HARQ processes) are not always optimal.

[0003] In some cases, it can be expected to improve the management of UL and / or DL ​​transmissions. In some cases, it can be expected to improve spectrum utilization efficiency for UL and / or DL ​​transmission sessions and avoid redundant transmissions. In some cases, it can be expected to reduce the risk of Radio Link Failure (RLF) during UL and / or DL ​​transmission sessions. In some cases, it can be expected to reduce the risk of UE power consumption and energy depletion during UL and / or DL ​​transmission sessions.

[0004] Any previously disclosed documents or background information listed or discussed in this specification should not be construed as an admission that such documents or background information are part of the prior art or common general knowledge. One or more aspects / examples of this disclosure may or may not relate to one or more of the background issues. Summary of the Invention

[0005] The scope of protection sought by the various embodiments of the present invention is defined by the claims.

[0006] Based on various, but not all, examples provided in this disclosure are those set forth in the appended claims. Any examples and features described in this specification that do not fall within the scope of the independent claims should be construed as examples that help to understand various embodiments of the invention.

[0007] According to at least some examples of this disclosure, an apparatus is provided, comprising: A component for receiving information from a network node indicating one or more resources, wherein the one or more resources are used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; Used to determine, at least in part, whether to request the suspension of at least one active component for a period of time, based on the energy state of the device; A component for sending a request to a network node via one or more resources in at least part of a determination to suspend at least one activity during a time period; and A component used to suspend at least one activity for a period of time, in response at least partially to a determination.

[0008] Based on various, but not all, examples of this disclosure, a method is provided, including: At the device, information indicating one or more resources is received from the network node, the one or more resources being used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; At the device, the determination of whether to request a suspension of at least one activity during the time period is based at least in part on the device's energy state; In at least a partial response to a determination request to suspend at least one activity during a time period, the device sends a request to a network node via one or more resources; and At the device, at least in part in response to the determination, at least one activity is suspended for a period of time.

[0009] According to various, but not all, examples of this disclosure, a chipset is provided, including a processing circuitry system configured to perform the methods described above.

[0010] According to various, but not all, examples of this disclosure, a module, circuit system, device, and / or system is provided, including components for performing the methods described above.

[0011] According to various, but not all, examples of this disclosure, a computer program is provided, including instructions that, when executed by a device, cause the device to perform: Receive information from a network node indicating one or more resources, which are used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; and Whether to request a suspension of at least one activity during a time period is determined at least in part based on the energy state of the device; At least in part in response to a determination request to suspend at least one activity during a time period, a request is sent to a network node via one or more resources; and In response at least partially to the determination, at least one activity is suspended for the period of time.

[0012] According to various, but not all, examples of this disclosure, an apparatus is provided, comprising: At least one processor; and At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: Receive information from a network node indicating one or more resources, which are used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; and Whether to request a suspension of at least one activity during a time period is determined at least in part based on the energy state of the device; At least in part in response to a determination request to suspend at least one activity during a time period, a request is sent to a network node via one or more resources; and In response at least partially to the determination, at least one activity is suspended for the period of time.

[0013] According to various, but not all, examples of this disclosure, a non-transitory computer-readable medium is provided that utilizes instructions encoded thereon, which, when executed by at least one processor of the device, cause at least the following to be performed: Receive information from a network node indicating one or more resources, which are used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; and Whether to request a suspension of at least one activity during a time period is determined at least in part based on the energy state of the device; At least in part in response to a determination request to suspend at least one activity during a time period, a request is sent to a network node via one or more resources; and In response at least partially to the determination, at least one activity is suspended for the period of time.

[0014] According to at least some examples of this disclosure, an apparatus is provided, comprising: A component for sending information to a user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Scheduling control channel; Components for receiving requests from the UE via one or more resources; and A component used to suspend at least one activity for a period of time, at least in part, in response to a received request.

[0015] Based on various, but not all, examples of this disclosure, a method is provided, including: The device sends information to the user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Scheduling control channel; At the device, the UE receives a request via one or more resources; and At the device, at least one activity is suspended for a period of time, at least in part in response to a received request.

[0016] According to various, but not all, examples of this disclosure, a chipset is provided that includes a processing circuitry system configured to perform the methods described above.

[0017] According to various, but not all, examples of this disclosure, a module, circuit system, device, and / or system is provided, including components for performing the methods described above.

[0018] According to various, but not all, examples of this disclosure, a computer program is provided, including instructions that, when executed by a device, cause the device to perform: Sending information to a user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Scheduling control channel; Requests are received from the UE via one or more resources; and At least partially in response to a received request, suspend at least one activity for a period of time.

[0019] According to various, but not all, examples of this disclosure, an apparatus is provided, comprising: At least one processor; and At least one memory, storing instructions that, when executed by at least one processor, cause the device to at least: Sending information to a user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Scheduling control channel; Requests are received from the UE via one or more resources; and At least partially in response to a received request, suspend at least one activity for a period of time.

[0020] According to various, but not all, examples of this disclosure, a non-transitory computer-readable medium is provided that utilizes instructions encoded thereon, which, when executed by at least one processor of the device, cause at least the following to be performed: Sending information to a user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Scheduling control channel; Requests are received from the UE via one or more resources; and At least partially in response to a received request, suspend at least one activity for a period of time.

[0021] Based on various, but not all, examples of this disclosure, a method of using the apparatus and / or system as described herein is provided.

[0022] The following sections of this “Summary of the Invention” describe various features, which, with necessary modifications, can be features of any of the examples described in the preceding sections of this “Summary of the Invention”. Furthermore, the description of the function should also be considered as disclosing any component suitable for performing the function, or any instructions stored in at least one memory that, when executed by at least one processor, cause the device to perform the function.

[0023] In some, but not all, examples, determining whether to request a suspension of at least one activity for a period of time based at least in part on the device's energy state includes determining whether one or more criteria are met, and wherein one or more criteria are based at least in part on at least one of the following: Does the device have sufficient energy to complete at least one activity? The amount of energy stored at the device; The rate of energy harvesting at the device; An estimate of the energy and / or power available to the device; or Does the device need to suspend at least one activity during the time period in order to collect energy during the time period?

[0024] In some, but not all, examples, the device also includes: Components for at least partially transitioning to or remaining in energy harvesting mode in response to a determination; and / or A component used to collect energy over a period of time.

[0025] In some, but not all, examples, the at least one activity includes at least one of the following: Hybrid Automatic Repeat Request (HARQ) process; HARQ Rx; or HARQ Tx.

[0026] In some, but not all, examples show that a request to pause at least one activity within a time period is a request to pause at least one activity during at least one of the following periods: HARQ process; UL session; or DL session.

[0027] In some, but not all, examples, the time period is at least one of the following: Pre-configured, or Indicated by the network node.

[0028] In some, but not all, examples, the device also includes components for receiving information indicating one or more threshold parameter values, which enable the device to determine whether to send a request; and This determination is based, at least in part, on one or more threshold parameter values.

[0029] In some, but not all, examples, one or more threshold parameter values ​​include at least one of the following: An indication of the amount of data sent by the device; An indication of the estimation of the data received by the device; or An indication of the number of requests allowed within a time period.

[0030] In some, but not all, examples, the device also includes a component for resuming at least one activity in at least part of response to determining at least one of the following: The time period has expired; Before the time period expires, the device has sufficient energy to complete at least one activity; or Before the time period expires, the estimated amount of energy and / or power available to the device exceeds the threshold amount.

[0031] In some, but not all, examples, the device also includes a component for sending a request to a network node via one or more resources to change the radio resource control state of the device.

[0032] In some, but not all, examples, the apparatus also includes a component for sending information to network nodes indicating a request to restore at least one activity.

[0033] In some, but not all, examples, the device also includes: The component used to determine whether the device has been released from the RRC connection state, wherein the determination is based at least in part on the determination that a request to resume at least one activity has not been sent by the device to the network node within a time period.

[0034] In some, but not all, examples, the device also includes: A component for receiving information from a network node indicating that the device has been released from the RRC connection state, wherein the information is received at least in part in response to the device not sending a request to the network node to resume at least one activity within a time period.

[0035] In some, but not all, examples, the device is at least one of the following: User Equipment (UE); Energy harvesting (EH) equipment; Reduced capacity RedCap devices; Internet of Things (IoT) devices; or Environmental IoT (AIoT) devices.

[0036] Although the examples and optional features of this disclosure are described separately above, it should be understood that their provision in all possible combinations and arrangements is included in this disclosure. It should be understood that the various examples of this disclosure are capable of including any or all features described in aspects of other examples of this disclosure, and vice versa. Furthermore, it should be understood that any one or more features, in any combination, can be implemented / included / performed by means of apparatus, method, and / or computer program instructions as needed and appropriate. Attached Figure Description

[0037] Some examples will now be described with reference to the accompanying drawings, in which:

[0038] Figure 1 An example of a radio communication network applicable to the topics described herein is illustrated schematically;

[0039] Figure 2 An example of an RLF in the HARQ process for UL transmission is illustrated schematically;

[0040] Figure 3An example of a method based on the subject matter described herein is illustrated schematically;

[0041] Figure 4 An example of another approach based on the subject matter described herein is illustrated schematically;

[0042] Figure 5 A signaling diagram based on the topics described herein is illustrated schematically;

[0043] Figure 6 A flowchart illustrating the subject matter described herein is shown schematically;

[0044] Figure 7 Examples of apparatuses according to the subject matter described herein are illustrated schematically; and

[0045] Figure 8 An example of a computer program based on the subject matter described herein is illustrated schematically.

[0046] The accompanying drawings are not drawn to scale. For clarity and simplicity, some features and views may be shown schematically or enlarged to scale. For example, the dimensions of some elements may be enlarged relative to others for ease of illustration. Similar reference numerals are used in the accompanying drawings to indicate similar features. For clarity, not all reference numerals need to be shown in all figures. Abbreviations / Definitions

[0047] 3GPP Third Generation Partnership Project

[0048] 5G / 6G Fifth Generation / Sixth Generation Mobile Communication Technology

[0049] AIoT (Ambient Internet of Things)

[0050] BL reduces bandwidth and complexity

[0051] BS base station

[0052] BSR Cache Status Report

[0053] DL downlink

[0054] EH Energy Harvesting

[0055] HARQ Hybrid Automatic Repeat Request

[0056] gNB 5G / NR base station

[0057] IoT (Internet of Things)

[0058] NDI New Data Indicator

[0059] PDCCH (Physical Downlink Control Channel)

[0060] PDSCH (Physical Downlink Shared Channel)

[0061] PUSCH Physical Uplink Shared Channel

[0062] RAN (Radio Access Network)

[0063] RLF wireless link failure

[0064] RRC (Radio Resource Control)

[0065] Rx Receive

[0066] Tx transfer

[0067] UE User Equipment

[0068] UL uplink Detailed Implementation

[0069] Figure 1 An example of a network 100 applicable to the embodiments of this disclosure is schematically illustrated. This network (also referred to as an NW) includes multiple network nodes, including: a terminal node 110 (also referred to as a user equipment UE), an access node 120 (also referred to as a radio access network RAN ​​node or base station BS), and one or more core network nodes 130. Terminal node 110 and access node 120 communicate with each other. One or more core network nodes 130 may communicate with each other in some, but not all, examples. One or more access nodes 120 may communicate with each other in some, but not all, examples.

[0070] In this example, network 100 is a radio telecommunications network, i.e., RAN, in which at least some terminal nodes 110 and access nodes 120 communicate with each other using the transmission / reception of radio waves.

[0071] Network / RAN 100 may be a cellular network comprising multiple cells 122, each cell being served by access node 120. Access node 120 includes a cellular transceiver. Terminal node 110 includes a cellular transceiver.

[0072] In the specific examples shown and discussed below, Network 100 is the new radio NR network of the 3GPP (Third Generation Partnership Project) and its fifth-generation 5G technology. In other examples, Network 100 can be a network beyond 5G, such as a next-generation (i.e., sixth-generation 6G) radio network currently under development (i.e., an NR network and its evolution towards 5G technology).

[0073] The interface between terminal node 110 and access node 120 is radio interface 124 (e.g., Uu interface). The interface between access node 120 and one or more core nodes 130 is backhaul interface 128 (e.g., S1 and / or next-generation NG interface).

[0074] Depending on the specific deployment scenario, access node 120 can be a RAN node, such as an NG-RAN node. NG-RAN nodes can be gNodeBs or gNBs, providing NG user plane and control plane protocol termination for the UE. The gNB connects to the 5G core (5GC) via the NG interface; more specifically, it connects to the Access and Mobility Management Function (AMF) via the NG control plane NG-C interface and to the User Plane Function (UPF) via the NG user plane NG-U interface. Access nodes 120 can interconnect with each other via Xn interface 126.

[0075] Cellular network 100 can be configured to operate in licensed or unlicensed frequency bands (at least such as: unlicensed frequency bands that rely on the transmitting device to sense radio resources / mediums before transmission begins, such as via the Listen-Before-Speak (LBT) process; and 60 GHz unlicensed frequency bands that may require beamforming to achieve the desired coverage).

[0076] Access node 120 can be deployed in NG standalone network operations / scenarios. Access node 120 can be deployed in NG non-standalone network operations / scenarios. Access node 120 can be deployed in carrier aggregation (CA) operations / scenarios. Access node 120 can be deployed in dual-connectivity DC operations / scenarios, i.e., multi-radio access technology - dual-connectivity MR-DC or NR-DC. Access node 120 can also be deployed in multi-connectivity MC operations / scenarios.

[0077] In such a non-standalone / dual-connectivity deployment, access nodes 120 can interconnect with each other via X2 or Xn interfaces, and connect to the evolved packet core network (EPC) via the S1 interface, or to the 5GC via the NG interface.

[0078] Access node 120 is a network element in the network, responsible for radio transmission and reception with terminal node 110 within one or more cells 122. Access node 120 is the network terminal of the radio link. A gNB can carry one or more Transmitter Points (TRPs).

[0079] Access node 120 can be implemented as a single network device or have a split architecture that uses different functional separation architectures and different interfaces to be decoupled / distributed on two or more RAN nodes, such as central unit CU, distributed unit DU, and remote radio front-end RRH.

[0080] Terminal node 110 is a user-side network element in the network that terminates the radio link. They are devices that allow access to network services. Terminal node 110 may be referred to as User Equipment (UE), Mobile Terminal, or Mobile Station. The term "User Equipment" can be used to refer to mobile devices, including those used for authentication / encryption, such as smart cards and Subscriber Identity Modules (SIMs). A SIM / SIM card can be a memory chip, module, or Universal Subscriber Identity Module (USIM). The functions of terminal node 110 can also be performed by a mobile terminal (MT) that is part of an Integrated Access and Backhaul (IAB) node.

[0081] In the following description, the terminal node may be referred to as UE 110. In the following description, the access node, radio access network RAN ​​node, gNB, or TRP may be referred to as network node 120.

[0082] In some examples, the term "user equipment" can be used to refer to location / location tags, super / smart, super / smart sensors, or mobile devices, including circuitry embedded as part of the user equipment for authentication / encryption, such as software SIM.

[0083] Next, we will briefly discuss energy harvesting (EH) devices, such as environmental IoT (AIoT) devices.

[0084] An AIoT device is a category / class of device or UE that has lower complexity, data rate, coverage, cost, and energy consumption than narrowband IoT NB-IoT devices / enhanced machine-type communication eMTC devices. An AIoT device is an IoT device powered by energy harvesting (EH), either without a battery or with limited energy storage capacity (e.g., using capacitors or batteries). Energy for AIoT devices can be provided by harvesting the following: radio waves (ambient radio waves or radio waves broadcasting / transmitting energy signals), light, motion, wind, heat, or any other source that can be considered a suitable power source. In some examples, energy can be transferred from a network node to the AIoT device via wireless power transfer, such as broadcasting energy signals to the AIoT device via a gNB.

[0085] Use cases for AIoT devices include: identification, tracking, monitoring, sensing, logistics and supply chain management, transportation, manufacturing (factory automation), healthcare, energy, agriculture, smart cities, environment, extreme conditions, and hazardous environments in some use cases (environments where devices with batteries are not feasible).

[0086] There may be different types / categories of AIoT devices, such as: Type A AIoT devices, Type B AIoT devices, and Type C AIoT devices, where: AIoT device type A is characterized as having: no energy storage and no independent signal generation capability (in this respect, transmission is achieved via backscatter transmission). AIoT device type B is characterized as having: energy storage without independent signal generation capability (in this respect, transmission is achieved via backscattering; however, the stored energy can be used to amplify the reflected signal). AIoT device type C is characterized by having: energy storage and independent signal generation (i.e., having active RF components for transmission). Furthermore, sub-category device type C2 is characterized by having the full capability to perform uplink and downlink network registration, as well as mobile-initiated (MO) and mobile-terminated (MT) operations. In type C devices with active transmission and storage, transmission may be similar to NR UEs, so existing access protocols can still be used, but some changes are required—the main difference being the lack of stable power availability.

[0087] In some examples, AIoT devices may have the ability to send mobile-initiated (MO) and mobile-terminated (MT) data (e.g., type C AIoT devices). In this respect, AIoT devices can correspond to / be used as UEs capable of connecting to the RAN.

[0088] In the following description, the term "user equipment" may be used to refer to one or more of the following: energy harvesting (EH) equipment, redcap (RedCap) equipment; and Internet of Things (AIoT) equipment (which may include cellular IoT (CIoT) equipment, narrowband IoT (NBIoT) equipment, and environmental IoT (AIoT) equipment).

[0089] Next, we will briefly discuss the Hybrid Automatic Repeat Request (HARQ) process.

[0090] The HARQ process provides an error handling method for minimizing data loss and improving system transmission efficiency.

[0091] Examples of error handling methods include Forward Error Correction (FEC) and Automatic Repeat Request (ARQ). In FEC, the transmitter appends an extra error correction code to the data to be transmitted, allowing the receiver to use this code to correct for errors, thus reducing the need for data retransmission. In ARQ, when the received signal has errors that cannot be corrected under FEC, the transmitter retransmits the data so that the receiver can correct for the errors. Hybrid ARQ (HARQ) is a combination of FEC and ARQ.

[0092] According to the HARQ scheme, the receiver essentially attempts error correction as data is received and determines retransmission data by using an error detection code. For error detection, the transmitter can append a Cyclic Redundancy Check (CRC) as an error detection code to the data to be transmitted. The receiver can then detect errors in the received data using the appended CRC.

[0093] If no error is detected by the receiver using CRC, the receiver sends an ACK signal back to the transmitter as a response signal. Otherwise, after detecting an error in the received data, the receiver may send a NACK signal to the transmitter as a response signal. HARQ operation has been standardized for UL and DL transmissions (see, for example, 3GPP TS36.321, V17.6.0, 5.3.2).

[0094] For NB-IoT UEs or bandwidth-reduced low-complexity BL UEs, the standard / traditional HARQ sequence for DL ​​can be considered to mainly include the following steps: i) UE <-- Network: Repeated MPDCCH (including DCI for scheduling PDCCH) ii) UE <-- Network: Repeat MPDCCH iii) UE --> Network: HARQ ACK / NACK Where: MPDCCH = Machine Type Communication (MTC) Physical Downlink Control Channel (PDCCH) DCI = Downlink Control Information

[0095] For NB-IoT UEs, BL UEs, or UEs within enhanced coverage, the parameter DL_REPETITION_NUMBER is used to provide the number of repeating transmissions in a bundle. For each bundle, DL_REPETITION_NUMBER is set to a value provided by the lower layer. Within a bundle, after the initial (re)transmission, a DL_REPETITION_NUMBER-1 HARQ retransmission follows. HARQ feedback is sent for that bundle, and downlink assignments for new transmissions or retransmissions corresponding to that bundle are received after the last repetition of that bundle. A bundle's retransmission is itself a bundle.

[0096] For NB-IoT UEs or BL UEs, the standard / traditional HARQ sequence for UL can be considered to mainly include the following steps: i) UE <--NW: MPDCCH (including DCI for scheduling PUSCH), with UL authorized duplicates ii) UE --> NW: PUSCH repeat iii) One of the following situations occurs: Scenario 1: The NW successfully decodes the PUSCH. The NW stops here and completes the PUSCH reception process (no ACK transmission). If the UE does not receive the MPDCCH for PUSCH retransmission, the UE assumes that the PUSCH was correctly received by the NW. There is no PHICH in LTE M1 for sending ACK / NACK for PUSCH. Scenario 2: NW fails to decode PUSCH. NW sends MPDCCH for PUSCH retransmission (including DCI for scheduling PUSCH and New Data Indicator NDI). Where: PUSCH = Physical Uplink Shared Channel PHICH = Physical HybridARQ indicator channel

[0097] EHDs (such as Type C AIoT devices) can typically be used only in mobile-initiated communication MICO modes. Such EHDs ensure they have sufficient power at the start of a UL transmission / session. However, when using dynamic licensing, the network determines: the frequency of UL / DL transmissions, the allocation of these resources, and UL power control based on, for example, UL interference levels.

[0098] When the EHD initiates a UL transmission / session, it is unaware of such variables, which can lead to scenarios where the EHD's energy or power is depleted or nearly depleted during Radio Resource Control (RRC) connection status and during UL transmissions / sessions.

[0099] Figure 2 An example is shown in which the traditional simplified HARQ process fails due to insufficient energy / energy unavailability on the UE side.

[0100] In step 1, the BS sends scheduling information to the UE via the PDCCH.

[0101] In step 2, the UE sends UL data via PUSCH.

[0102] In step 3, BS checks the data used for decoding errors.

[0103] In step 4, based on the decoding error detected in step 3 and the need for retransmission or new transmission, the BS sends the DCI for scheduling the PUSCH, and the NDI is not flipped.

[0104] When the NDI is not flipped, in step 5, the UE will typically continue to retransmit the data that it has already stored in the buffer, that is, it retransmits the NDI bits for its unflipped HARQ process.

[0105] In the example shown, the UE's data retransmission fails (as shown in step 6) due to the low power used by the UE for its UL retransmission (in step 5), which is driven by low energy availability at the UE. Low energy availability at the UE may also alternatively cause the inability to perform the UL transmission in step 5.

[0106] Due to the gradual depletion of energy or power during the execution of steps 1 to 4, the data retransmission attempted by the UE fails in steps 5 and 6 (i.e., it is not received and / or decoded at the BS, for example, due to the low power used by the UE for UL retransmission driven by the low availability of the capabilities at the UE).

[0107] Energy / resource depletion can also cause similar problems for new UL transmissions or for DL ​​transmissions, since DL transmissions also require UL transmissions for HARQ layer 1 feedback.

[0108] Therefore, operating an EHD with low energy / energy or depleted power can lead to inefficient spectrum use, which can significantly impact key network performance indicators (KPIs) such as high RLF and call drop rates. Allowing an EHD in RRC connection mode to experience RLF is inefficient because it will require significant control plane transfers to attempt to restore the link and / or may require retransmitting a portion of the previously sent data.

[0109] Various examples of this disclosure may seek to manage UL and / or DL ​​transmissions for UEs (such as EH UEs) to prevent UEs with low energy / power levels from failing to transmit / receive, thereby causing further energy depletion.

[0110] Therefore, various examples can advantageously enable the use of spectrum and radio resources. Various examples can enable HARQ processes for EHDs with near-depleted energy / resources.

[0111] By way of a non-limiting overview of the examples in this disclosure, in some examples, the EHD UE is configured by the network NW with multiple Layer 1 or Layer 2 resources, through which the EHD UE can indicate a request to pause UL and DL transmissions. The EHD UE can determine, for example, based on configured criteria, whether it needs to request a pause in UL and DL transmissions to collect energy, or to collect sufficient energy to perform UL transmissions or DL ​​reception. After the UE transmits the pause request, the EHD UE and NW pause UL and DL transmissions (i.e., paused Tx / Rx) for a pre-configured time period. During the pause period, the EHD UE is able to collect energy without, for example, monitoring the PDCCH. From the NW's perspective, there is no need to waste resources on an EHD UE that may not be monitoring the PDCCH. Normal operation can be resumed after the timer associated with the pre-configured time expires.

[0112] Figure 3 An example of the method 300 of this disclosure for managing transmissions, such as a UL or DL ​​transmission session and / or HARQ procedure between UE 110 and network node 120, is illustrated schematically.

[0113] In some examples, the UE can be a RedCap device with reduced capabilities and / or an IoT device (e.g., at least such as a cellular IoT device; a narrowband IoT device; and an ambient IoT device).

[0114] As used herein, the term “UE” can be used interchangeably to refer to an AIoT device or an EH device (at least such as an AIoT / EHUE device, for example an AIoT / EH device capable of connecting to a network, such as a type C AIoT device).

[0115] As used in this article, the term "network node" can be used interchangeably to refer to the RAN access node or gNB.

[0116] Figure 3 Method 300 (and other method features and functions discussed below) each in Figure 3 This can be interpreted as representing one or more actions performed by / at multiple participants / entities (i.e., UE 110 and network node 120), and can therefore be interpreted as representing multiple methods. Figure 3 It can be viewed as showing multiple independent methods performed by each individual participant / entity among multiple participants / entities.

[0117] Figure 3 The component blocks are functional, and the described functions can be performed by a single physical entity, such as a device (e.g., embodied as a UE or network node), as referenced. Figure 7 The aforementioned functions can also be implemented by computer programs, such as those described above. Figure 8 As stated above, Therefore, Figure 3 The blocks shown can represent actions in a method, functions performed by a device, and / or instructions / code segments in a computer program.

[0118] In step 301, UE 110 receives information 302 from network node NW 120 indicating one or more resources 303, which are used by the UE to send a request to suspend at least one activity during a time period, wherein the activity includes at least one of the following: At least one receive Rx procedure (at least such as DL HARQ procedure or HARQ Rx). At least one transmission Tx process (at least such as a UL HARQ process or a HARQ Tx), and Monitor control channels (at least such as monitoring PDCCH).

[0119] The resource 303 configured / assigned to the UE by the network node can be a Layer 1 L1 or Layer 2 L2 resource, which the UE can use to send requests to the network node.

[0120] In some examples, the time period is pre-configured. In some examples, the network node indicates the time period to the UE. In this regard, the network node is able to include an indication of the time period (e.g., parameter "T_susp") in the information 302 received in step 301. In some examples, if the network node does not include an indication of the time period in information 302, the UE may assume a predetermined value for the time period.

[0121] After receiving the configuration information / resource allocation in box 301, the network node can subsequently schedule the activity. For example, the network node can schedule an Rx or Tx process.

[0122] In step 304, the UE determines whether to request a suspension of the activity for the time period, wherein this determination is based at least in part on the device's energy state. In this respect, the UE may determine whether to request a suspension of the activity based at least in part on the amount of energy / resources available to the UE.

[0123] The amount of energy / resources available to the UE can correspond to: The amount of energy (or an estimated amount) stored at the UE (e.g., battery level); The rate (or estimated rate) of energy collection at the UE (e.g., the rate at which energy is received, collected, accumulated and / or stored at the UE).

[0124] Determining whether to request a suspension of the activity can be based on an assessment of the following: Does the UE have sufficient energy to complete the activity (e.g., does the UE have sufficient energy to complete the Rx or Tx procedure scheduled after receiving the configuration information / resource allocation by the network node in box 301)? Does the UE need to pause the activity during the time period to collect energy during that time period (in some examples, the UE does not need to pause the activity to collect energy; instead, it can pause the activity to reduce energy consumption and collect some amount of energy required to perform the activity or otherwise)? and / or Does the UE need to pause the activity in order to collect a certain amount of energy (e.g., the energy required to perform this activity or another activity)?

[0125] In some examples, the UE receives from the network node an indication of one or more threshold parameter values ​​that enable the UE to determine whether to send a request. In this regard, the network node may indicate one or more of the following values ​​to the UE: The threshold quantity (or estimate) of energy. Threshold rate (or estimated rate) of energy harvesting. The threshold amount of energy / resources required to perform the activity; An indication of the amount of data sent by the UE (e.g., based on the UE's UL cache status report, BSR); The instructions for estimating the data received by the UE (e.g., derived from the DL BSR and based on the received DL Radio Link Control (RLC) acknowledgment mode AM packet segment and the maximum Protocol Data Unit (PDU) size); and An indication of the number of requests allowed within a time period (by way of a non-restrictive example, this can be represented by the parameters “Max_susp” and “T_max_susp”, indicating the maximum number of requests allowed within the time period [T_max_susp] [Max_susp].

[0126] In some examples, if the parameters “Max_susp” and “T_max_susp” are not indicated to the UE by the network node, the UE may assume predetermined values ​​for these parameters.

[0127] The UE may receive indications of one or more of the above thresholds, as well as indications of other parameters that enable the UE to determine whether to request a pause, together with the information received in step 301.

[0128] The UE can use the received threshold parameter value and evaluate / measure its own parameter value. The UE can then send a request in response to determining that its parameter value is smaller than the threshold parameter value. For example, the UE can send a request based on the fact that the UL data in its cache is smaller than an established threshold.

[0129] In step 305, the UE sends a request 306 to the network node via the configured resource 303 to suspend activity for the specified time period, wherein the request is sent at least in part based on the determination in step 304. For example, the request is sent at least in part in response to a determination (in step 304) to request the suspension of activity for the specified time period.

[0130] The request can be sent during at least one of the following periods: a HARQ process; a UL session; and a DL session. For example, by way of a non-limiting example, the request can be sent during... Figure 2 It is sent between steps 4 and 5.

[0131] In box 307, in response to the determination in step 304, the UE suspends the activity for the specified time period (this time period is shown relative to 309). In this respect, the UE can suspend: Receive Rx procedures (at least such as DL HARQ procedures or HARQ Rx). Transmission Tx process (at least such as UL HARQ process or HARQ Tx), and Monitoring of control channels (at least such as monitoring PDCCH).

[0132] In step 308, in response to receiving request 306, the network node suspends activity for time period 309. In this respect, the network node can suspend: Receive Rx process (at least such as UL HARQ process or HARQ Tx). Transmit Tx procedures (at least such as DL HARQ procedures or HARQ Rx), and Scheduling control channels (at least such as scheduling PDCCH for UE).

[0133] During time period 309, the UE can switch to energy harvesting mode and harvest energy. In some examples, the UE may be able to continuously harvest energy without pausing any activity, because, for example, the UE has a separate / independent circuitry system to achieve this functionality. In this case, the UE can remain in energy harvesting mode and continue harvesting energy during time period 309. In these examples, pausing activity may still be necessary because the UE does not have enough energy to perform the activity, and therefore must harvest energy to resume activity.

[0134] In some examples, the UE and network node resume activity in response to the expiration of a time period, as shown in steps 310 and 311. In this respect, activity can resume automatically in response to determining that a time period has expired.

[0135] In some examples, the activity can be resumed before the time period expires. In this regard, the UE can send a request to the network node to resume the activity before the time period expires. If the UE has been configured with a semi-persistent configuration grant SP-CG or a scheduling request SR, such a resumption request, indicating an early exit from the suspended state before the expiration of the time period (T_susp), can be sent.

[0136] Such a recovery request can be sent in response to the UE determining that the conditions that triggered the suspension of its initially requested activity no longer apply. For example, during the suspension period, the UE may determine (after performing some energy harvesting since the initial suspension and before the end of the suspension period) that it now has sufficient energy / power to complete the suspended activity. In this respect, the UE may determine that its now available energy and / or power exceeds a threshold amount of the required energy, and therefore the activity can be resumed.

[0137] In some examples, in response to determining that a request to resume activity has not been sent to the network node within the time period, the UE can determine that it has been released from the RRC connected state. In this regard, the network node can also release the UE from the RRC connected state in response to determining that a request to resume activity has not been received at the network node within the time period. In practice, in these examples, the UE does not automatically resume activity after the time period expires, but rather automatically changes its RRC state after the time period expires, for example, changing the UE's radio resource control state, such as changing from RRC connected mode to RRC idle mode or RRC inactive mode.

[0138] In some examples, the UE may send a request to change its RRC status before the time period expires, such as from RRC connected mode to RRC idle mode or RRC inactive mode. Such a request may be sent via resource 303 in response to the condition that the suspension triggering the UE's request for activity remains in effect before the time period expires. Such a request may also be sent if the UE has been configured with SP-CG.

[0139] Advantageously, the examples of this disclosure may provide one or more of the following: Make efficient use of network resources (e.g., avoid retransmissions to EHD UEs that may be running out of power). Reduce RLF failures and their adverse impact on network KPIs. Reduce power consumption in EHD UEs. Avoid additional C-plane transmissions for retransmissions of packets, such as those used for RRC reconstruction and partial transmission, which would otherwise be dropped due to RLF.

[0140] Figure 4 An example of another approach based on the subject matter described herein is illustrated schematically. Figure 4 The blocks shown can represent (e.g., actions performed by UE 110) actions in a method, as well as actions performed by (such as references) Figure 7 The device described performs functions and / or (such as, reference) Figure 8 (Description) Instructions / code segments in a computer program.

[0141] In the following Figure 4During the discussion, other diagrams (at least) will be used for ease of explanation. Figure 3 The figure labels for the features shown in the figure.

[0142] In block 10 (similar to) Figure 3 In step 301), UE 110 is in an RRC connection state with network NW 120 and receives configuration 303 from NW to enable UE to indicate / send a request 305 to NW to suspend Tx and / or Rx activities.

[0143] In block 20, the UE determines whether its energy / resources are insufficient to continue the RRC connection. In this regard, the UE may determine whether its energy / resources are insufficient to continue / complete Tx, Rx activities and / or continue monitoring the PDCCH.

[0144] In block 30 (similar to) Figure 3 In step 304), the UE responds at least partially to the determination in block 20 by instructing / sending a request to the NW to suspend Tx / Rx activities using the configured resources (received in block 10) 305.

[0145] In block 40 (similar to) Figure 3 In step 306), the UE suspends Tx / Rx activity and collects energy for a pre-configured number of time periods.

[0146] In block 50 (similar to) Figure 3 In step 309), normal Tx / Rx operations are resumed after the pre-configured timer expires.

[0147] The examples disclosed herein can be deployed in situations where, for example, the network does not receive continuous updates about the UE's energy state from the UE. Due to energy and control plane overhead, the UE may not be configured for periodic energy state reports from the network. In some cases, the UE can be configured to send energy state reports, but the transmission of such reports can be suspended, for example, due to low energy levels.

[0148] Figure 5 This is a signaling diagram showing an example sequence of messages between UE 110 (i.e., EHD such as AIoT type C device) and network node BS 120.

[0149] In step 1, the BS configures the UE to have Layer 1 UL resources, through which the UE can provide an indication for requesting a pause in the HARQ process, or request a change from an RRC connected state to an RRC idle or inactive state.

[0150] In one example, configuring a Layer 1 resource could be a "negative scheduling request (SR) resource," that is, a Layer 1 physical channel similar to a scheduling request (SR), but it would be interpreted such that, for example: The lack of a positive SR instruction indicates that a suspension of the HARQ process was not requested; There is a positive SR indication that a suspension of the HARQ process has been requested.

[0151] In some examples, Layer 1 resources are Layer 1 UL physical channels, which provide the ability for the UE to indicate more granular requests (albeit at a higher cost), such as: Instructions for suspending the HARQ process Instructions for switching to RRC idle Instructions for the request to switch to RRC inactivity No instructions are missing (i.e., none of the above instructions are missing).

[0152] The BS can also provide the UE with one or more of the following configuration parameters: Parameters that determine when a UE should request a pause or state transition to an RRC idle / inactive state include, for example, a UL BSR threshold based on the received DL RLC AM packet segments and the maximum PDU size, or a threshold for DL ​​BSR. The duration of the pause requested by the UE (T_susp) The number of pause requests made by the UE in RRC connected mode will be accepted based on the maximum number of pauses allowed during the time period (T_max_susp) (Max_susp). If the number of pause requests exceeds Max_susp during the T_max_susp time period, the UE should fall back to RRC idle after the transmission of the pause request.

[0153] The BS can also provide the UE with a semi-persistent configuration license SP-CG configuration, which will be used by the UE while T_susp is running (i.e., during the pause period).

[0154] The above configuration information and parameters can be provided to the UE after the UE transitions from RRC idle to RRC connected. If the UE subsequently transitions to RRC inactivity, the UE can store this configuration information / parameters. Therefore, if the serving cell / gNB has not changed, it may not be necessary for the serving cell to resend this configuration information / parameters to the UE.

[0155] In step 2, the BS performs dynamic scheduling of the UE according to the conventional scheduling process, that is, through the PDCCH.

[0156] In step 3, the UE determines that it has (or predicts) a power / energy shortage, and therefore decides to request a temporary suspension of the UL / DL HARQ process. This determination can be based at least in part on network-configured thresholds. These thresholds can also be configured based on, for example, the UE's EHD capability or EHD category / type, and additional information from the UE.

[0157] A request for a pause can be sent via the transmission of UL physical layer signals (such as a scheduling request specifically configured for this purpose as per step 1). This option can be used by the UE when no UL authorization is available. If the EHD has UL authorization for transmission, it can use that authorization to send a request for a pause via, for example, the Media Access Control element MAC-CE.

[0158] In step 3, the UE also enters a paused state, meaning the UE pauses UL / DLHARQ for a pre-configured time (T_susp). The UE also initiates a timer set to the value of T_susp. The pausing and initiation of the timer can occur substantially simultaneously with sending a request to pause the UL and DL transmissions in step 4, or in response to sending a request to pause the UL and DL transmissions in step 4.

[0159] After the timer for T_susp is paused and initiated, the UE stops monitoring dynamic scheduling (thus allowing the UE to collect energy for future process / UL and DL transfers after the timer for T_susp expires).

[0160] In step 4, the UE continues to send requests for pause of UL and DL transmissions (e.g., via pre-configured Layer 1 UL resources).

[0161] In step 5, upon receiving the pause request, the BS initiates a timer set to the value of T_susp, and the BS pauses all UL and DL transmissions used to request the UE for the period defined by T_susp. In this respect, all HARQ procedures (i.e., all dynamic scheduling) for the UE are paused by the BS within T_susp. In some examples, the BS may send energy to the UE (e.g., send a single RF energy to the UE / EHD) until the timer associated with a pre-configured time expires.

[0162] In steps 6 and 7, if the SP-CG configuration was provided in step 1, the SP-CG can be activated by the UE and the BS. The SP-CG will allow the UE to indicate to the BS that it is exiting the suspended state early. For example, if the UE has collected sufficient energy since entering the suspended state before the timer associated with T_susp expires, it can use the SP-CG resources to send an indication to the BS, such as via MAC-CE and / or via UL data transmission (if available).

[0163] In step 8, upon receiving such an instruction, the BS will resume the HARQ process and continue to resume normal scheduling according to step 11.

[0164] If the SP-CG configuration is not provided in step 1 (or if the SP-CG is provided, but no indication in step 8 is sent by the UE to exit the suspended state before the expiration of T_susp), then in steps 9 and 10, after the expiration of T_susp, the BS and UE will resume normal operation in step 11.

[0165] In an alternative example, if the SP-CG configuration is provided, but no indication in step 8 is sent by the UE to exit the suspended state before the expiration of T_susp, then after the expiration of T_susp, the network can explicitly release the UE from its RRC connection state and / or the UE can consider it to have been implicitly released.

[0166] After step 11, the UE may request additional pauses. However, the maximum number of pauses it can request (Max_susp) within a given time period (T_max_susp) is established by the network, either via parameters that can be provided in step 1, or otherwise predetermined (e.g., it can be defined in the specification and / or used as a default number if the network lacks the option to configure that number for the UE). If the UE seeks to request a Max_susp+1 pause within the time period T_max_susp, the BS may send an RRC connection release after T_susp expires, and / or the UE and the BS may consider the UE to have been implicitly released.

[0167] Figure 6 A flowchart illustrating the subject matter described herein is shown schematically. Figure 6 A flowchart is provided from the perspective of the UE (i.e., EHD UE) for scenarios where the UE has not yet been configured with SP-CG.

[0168] In block 10, the UE receives configuration from the gNB. This configuration includes resources for sending an indication to request a temporary scheduling pause (or exit the transition of the RRC connection). The configuration information may also include parameters such as T_susp, Max_susp, T_max_susp, and thresholds that the UE uses to evaluate whether to send the request.

[0169] Following block 10, in block 15, the UE determines whether to continue or resume normal monitoring of UL / DL scheduling.

[0170] Following block 15, in block 20, the UE determines whether there is a requirement for the following: Temporary scheduling pause, or Exit the RRC connection conversion.

[0171] If the transition to exit the RRC connection is required, in block 200, the UE sends a request to the gNB to exit the transition to exit the RRC connection. From thereafter, in block 210, the UE monitors the gNB that is in the RRC connection release request state, and then the UE proceeds according to the normal procedure (i.e., the UE changes the RRC state from RRC connected to RRC idle / inactive according to the normal RRC state change procedure).

[0172] If a temporary suspension of scheduling is required, the UE sends a request for a temporary suspension to the gNB in ​​block 30. When the first suspension is requested, the "Num_suspensions" parameter is initialized to zero. In block 40, the UE then increments the value of the "Num_suspensions" parameter by 1.

[0173] In block 50, the UE evaluates whether its "Num_suspensions" value is greater than the value of Max_susp. If yes, then in block 60, the UE switches to RRC idle and stops T_max_susp. If no, then in block 70, the UE starts a timer for pausing the requested observation period (T_max_susp) (if it has not already started). If the timer has already started, it continues to run.

[0174] While T_max_susp is running (from block 70 onwards), a parallel process, as shown in blocks 300 and 310, occurs to ensure that there are no more Max_susps within the T_max_susp period. In this regard, if T_max_susp is running, the UE determines whether it has expired. If it has not expired, the process loops back to block 300, and the UE again evaluates whether T_max_susp has expired. After determining that T_max_susp has expired, in block 310, the UE resets Num_suspensions, i.e., the UE sets it to 0.

[0175] From block 70 onwards, in block 80, the UE starts a timer for the pause time (T_susp).

[0176] In block 90, the UE evaluates whether T_susp has expired. If yes, the process returns to block 15. If no, the process loops back to block 90, and the UE evaluates whether T_susp has expired again.

[0177] It should be understood that Figures 3 to 6 Each block and combination of blocks shown, as well as the additional functions described above, can be implemented by various components, such as hardware, firmware, and / or software including one or more computer program instructions. For example, one or more of the functions described above can be performed by a suitably configured device (such as a device or UE including components for performing the functions described above). One or more of the functions / functionalities described above can be embodied by a suitably configured computer program (such as a computer program including computer program instructions embodying the functions / functionalities described above and capable of being stored in a memory storage device and executed by a processor).

[0178] It should be understood that any such computer program instructions can be loaded onto a computer or other programmable device (i.e., hardware) to produce a machine, such that when executed on the programmable device, these instructions generate components for implementing the function / functionality specified in the block. These computer program instructions can also be stored on a computer-readable medium that can instruct the programmable device to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of art including instruction components that implement the function specified in the block. Computer program instructions can also be loaded onto a programmable device to cause a series of operations to be performed on the programmable device to produce a computer-implemented process, such that the instructions executed on the programmable device provide for implementing the function / functionality specified in the block.

[0179] Various, but not necessarily all, examples of this disclosure can take the form of a method, apparatus, or computer program. Therefore, various, but not necessarily all, examples can be implemented in hardware, software, or a combination of hardware and software.

[0180] Various, but not necessarily all, examples of this disclosure are described using flowcharts and block diagrams. It should be understood that each block (of the flowcharts and block diagrams), and combinations thereof, can be implemented by computer program instructions of a computer program. These program instructions can be provided to one or more processors, processing circuitry systems, or controllers(s) such that instructions executing on these processors, processing circuitry systems, or controllers(s) create components for causing the implementation of the functions specified in the one or more blocks, thus enabling the method to be computer-implemented. The computer program instructions can be executed by the processor(s) to cause a series of operational blocks / steps / actions to be performed by the processor(s) to produce a computer-implemented process, such that instructions executing on the processor(s) provide blocks / steps for implementing the functions specified in the one or more blocks.

[0181] Therefore, these blocks support: combinations of components for performing specified functions; combinations of actions for performing specified functions; and computer program instructions / algorithms for performing specified functions. It should also be understood that each block, and combinations of blocks, can be implemented by a dedicated hardware system, or a combination of dedicated hardware and computer program instructions, that performs the specified function or action.

[0182] Various, but not all, examples of this disclosure provide both methods and corresponding apparatus, which include various modules, components, or circuit systems that provide functionality for performing / applying the actions of the method. These modules, components, or circuit systems can be implemented as hardware or as software or firmware executed by a computer processor. In the case of firmware or software, examples of this disclosure can be provided as a computer program product including a computer-readable storage structure on which computer program instructions (i.e., software or firmware) are embodied for execution by a computer processor.

[0183] Figure 7 This schematically illustrates the method for performing the actions described in this disclosure and Figures 3 to 6 The block diagram of the apparatus 10 for the methods, processes, procedures, and signaling shown is provided. In this respect, the apparatus is capable of performing the roles of UE 100 (e.g., EHD, at least such as type C AIoT device 110) or gNB 120 in the methods shown and described above. Figure 7 The component blocks in the document are functional, and the described functions can be performed by a single physical entity.

[0184] The device includes a controller 11, which can be provided in devices such as UE / EHD 110 or gNB 120.

[0185] The controller 11 can be embodied in a computing device, at least those mentioned above. In some, but not necessarily all, examples, the device can be implemented as a chip, chipset, circuit system, or module, i.e., used in any of the above. As used herein, "module" refers to a unit or device, excluding certain parts / components that will be added by the final manufacturer or user.

[0186] The controller 11 can be implemented as a controller circuit system. The controller 11 can be implemented solely in hardware, have certain aspects in software (including firmware only), or be a combination of software and hardware (including firmware).

[0187] The controller 11 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 14 in a general-purpose or special-purpose processor 12, which can be stored on a computer-readable storage medium 13 (e.g., a memory or a disk) and executed by such processor 12.

[0188] Processor 12 is configured to read data from and write data to memory 13. Processor 12 may also include an output interface through which data and / or commands are output; and an input interface through which data and / or commands are input to processor 12. The device may be coupled to or include one or more other components 15 (at least, for example, a radio transceiver, a sensor, an input / output user interface element, and / or other modules / devices / components for inputting and outputting data / commands).

[0189] Memory 13 stores instructions, such as computer program 14, which includes instructions (e.g., computer program instructions / code) that, when loaded into processor 12, control the operation of device 10. The instructions of computer program 14 provide logic and routines that enable the device to perform operations described in this disclosure and... Figures 3 to 6 The methods, processes, and steps are shown. Processor 12 can load and execute computer program 14 by reading memory 13.

[0190] These instructions can be included in computer programs, non-transitory computer-readable media, computer program products, and machine-readable media. As used herein, the term "non-transitory" refers to limitations of the medium itself (i.e., tangible rather than tactile), rather than limitations on the persistence of data storage (e.g., RAM and ROM). In some, but not all, examples, computer program instructions can be distributed across more than one computer program.

[0191] Although memory 13 is shown in the figure as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which can be integrated / movable, and / or can provide permanent / semi-permanent / dynamic / cached storage.

[0192] Although processor 12 is illustrated as a single component / circuit system, it can be implemented as one or more separate component / circuit systems, some or all of which can be integrated / movable. Processor 12 can be a single-core processor or a multi-core processor.

[0193] The device can include one or more components for implementing the functions described in this disclosure and Figures 3 to 6 The methods, processes, and procedures shown are intended to facilitate the integration of the functionality of these components into one or more components, or to be performed by other components with equivalent functionality. The description of the functionality should also be considered in light of any methods suitable for performing that functionality.

[0194] Each described structural feature can be replaced by a component that performs one or more functions of that structural feature, whether or not those functions are explicitly or implicitly described.

[0195] Although examples of the device have been described above in terms of including various components, it should be understood that these components can be embodied or otherwise controlled by a corresponding controller or circuit system (such as one or more processing elements or processors of the device). In this regard, each of the components described above can be one or more of any device, component, or circuit system that can be embodied in hardware, software, or a combination of hardware and software, and configured to perform the corresponding function of the corresponding component as described above.

[0196] For example, the device can be: a wireless communication device, a client device, a location / location tag, a super tag, a handheld portable electronic device, a mobile cellular phone, a server device, a base station in a mobile cellular telecommunications system, etc. The device can be embodied in a computing device, at least as those mentioned above. However, in some examples, the device can be embodied in a chip, chipset, circuit system, or module, i.e., used in any of the above.

[0197] In an example where the device is provided within the UE / EHD device 110, the device includes: At least one processor 12; and At least one memory 13 stores instructions that, when executed by at least one processor 12, cause the device to at least: Receive information from a network node indicating one or more resources, which are used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; Whether to request a suspension of at least one activity during the time period is determined at least in part based on the energy state of the device; At least in part in response to a determination request to suspend at least one activity during a time period, a request is sent to a network node via one or more resources; and In response to this determination, at least one activity shall be suspended for the period of time.

[0198] In an example where the device is provided within gNB 120, the device includes: At least one processor 12; and At least one memory 13 stores instructions that, when executed by the at least one processor 12, cause the device to at least: Sending information to a user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one Tx sending process; or Scheduling control channel; Requests are received from the UE via one or more resources; and At least partially in response to a received request, suspend at least one activity for a period of time.

[0199] According to some examples of this disclosure, a system is provided that includes at least one UE / EHD 110 and gNB 120 as described above.

[0200] The examples above serve as enabling components for applications including: tracking systems; automotive systems; telecommunications systems; electronic systems (including consumer electronics); distributed computing systems; media systems for generating or rendering media content (including audio, video, and audiovisual content, as well as mixed reality, mediated reality, virtual reality, and / or augmented reality); personal systems (including personal health systems or personal fitness systems); navigation systems; user interfaces (also known as human-machine interfaces); networks (including cellular networks, non-cellular networks, and optical networks); self-organizing networks; the Internet; the Internet of Things (IoT); vehicle-to-everything (V2X); virtualized networks; and related software and services.

[0201] According to one example of this disclosure, the device can be provided in an electronic device (e.g., a mobile terminal). However, it should be understood that a mobile terminal is merely an illustration of an electronic device that can benefit from implementations of this disclosure and should not be construed as limiting the scope of this disclosure to mobile terminals. While the device can be provided in a mobile terminal in some implementation examples, other types of electronic devices, such as, but not limited to, mobile communication devices, handheld portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices, and other types of electronic systems, can readily employ examples of this disclosure. Furthermore, examples of this disclosure can be readily employed regardless of whether the device is intended to provide mobility.

[0202] Figure 8 A computer program 14 that can be transmitted via a transmission mechanism 20 is shown. The transmission mechanism 20 can be any suitable transmission mechanism, such as a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a solid-state storage device, a recording medium (such as an optical disc read-only memory (CD-ROM) or a digital versatile optical disc (DVD)), or an article of manufacture that includes or tangibly embodies the computer program 14. The transmission mechanism can be a signal configured to reliably transmit the computer program. The apparatus is capable of receiving, propagating, or transmitting the computer program as a computer data signal.

[0203] In some examples of this disclosure, a computer program is provided that includes instructions, which, when executed by a device (UE / EHD 110), cause the device to perform at least the following, or are used to cause at least the following to be performed: Receive information from a network node indicating one or more resources, which are used by the device to send a request to suspend at least one activity during a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one Tx sending process; or Monitoring and control channels; Whether to request a suspension of at least one activity during a time period is determined at least in part based on the energy state of the device; At least in part in response to a determination request to suspend at least one activity during a time period, a request is sent to a network node via one or more resources; and In response to this determination, at least one activity shall be suspended for the period of time.

[0204] In some examples of this disclosure, a computer program is provided that includes instructions, which, when executed by a device (gNB 120), cause the device to perform at least the following, or are used to cause at least the following to be performed: Sending information to a user equipment (UE) instructing the UE to send a request for suspending at least one activity within a time period, wherein the at least one activity includes at least one of the following: At least one receiving Rx process; At least one Tx sending process; or Scheduling control channel; Requests are received from the UE via one or more resources; and At least partially in response to a received request, suspend at least one activity for a period of time.

[0205] References to “computer program,” “computer-readable storage medium,” “computer program product,” “tangible embodiment of a computer program,” or “controller,” “computer,” and “processor” should be understood to include not only computers with different architectures (such as single-processor / multi-processor architectures and sequential (von Neumann) / parallel architectures) but also special-purpose circuits (such as field-programmable gate arrays (FPGAs), special-purpose circuits (ASICs), signal processing devices, and other devices). References to computer programs, instructions, code, etc., should be understood to encompass software used in programmable processors or firmware, such as the programmable content of hardware devices, including instructions for processors and configuration settings for fixed-function devices, gate arrays, or programmable logic devices.

[0206] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems); and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) (Multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or a portion of (multiple) microprocessors) that require software (e.g. firmware) to operate, but may be absent when operation is not required.

[0207] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only the implementation of hardware circuitry or processors and their accompanying software and / or firmware. For example, if applicable to elements of a claim, the term "circuit system" also covers baseband integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0208] Although certain terms are used in this document, they are used only in a general and descriptive sense and not for restrictive purposes.

[0209] The features described in the foregoing description can be used in combinations other than those explicitly described.

[0210] Although the functions are described with reference to certain features, these functions can also be performed by other features (whether or not they are described).

[0211] Although features have been described with reference to certain examples, these features may also exist in other examples (whether or not they have been described). Therefore, a feature described with respect to one example / aspect of this disclosure may include any or all features described with respect to another example / aspect of this disclosure, and vice versa, to the extent that they do not contradict each other.

[0212] Although various examples of this disclosure have been described in the foregoing paragraphs, it should be understood that modifications to the given examples can be made without departing from the scope of the invention as defined in the claims.

[0213] The term "includes" is used in this document to mean inclusive rather than exclusive. That is, any reference to X including Y indicates that X may include only one Y, or may include more than one Y. If the intention is to use "includes" with an exclusive meaning, it will be made explicit in the context by referring to "includes only one..." or by using "comprises".

[0214] In this specification, the terms “connection,” “coupling,” and “communication,” and their derivatives, all refer to operational connection / coupling / communication. It should be understood that any or a combination of intermediate components (including no intermediate components) may exist to provide direct or indirect connection / coupling / communication. Any such intermediate component can include hardware and / or software components.

[0215] As used herein, the term “determine / determine” (and its grammatical variations) can include, but is not limited to: calculation, processing, deriving, measuring, investigating, identifying, searching (e.g., searching in a table, database, or other data structure), ascertaining, etc. Additionally, “determine” can also include receiving (e.g., receiving information), retrieving / accessing (e.g., accessing data in memory), obtaining, etc. Similarly, “determine / determine” can also include solving, selecting, choosing, establishing, reasoning, etc.

[0216] As used herein, a description of an action should also be considered as disclosing enabling, and / or causing, and / or controlling that action. For example, a description of transmitting information should also be considered as disclosing enabling, causing, and / or controlling the transmission of information. Similarly, for example, a description of a means of transmitting information should also be considered as disclosing at least one component or controller of a means of enabling, and / or causing, and / or controlling the transmission of information by that means.

[0217] As used in this specification and claims, the term "component" may refer to one or more individual elements configured to perform a function corresponding to the one or more said functions, or it may refer to a plurality of elements performing such one or more functions. Furthermore, the functions described in the claims may be performed by the same individual components or the same combination of components. For example, in a device, the performance of such one or more functions may be initiated by a processor executing instructions stored in the device's memory.

[0218] (Unless the context requires otherwise) references to parameters or parameter values ​​should be understood as "data indicating the relevant parameter / value," "data defining the relevant parameter / value," or "data representing the relevant parameter / value." This data may indicate the relevant parameter / value in any way and may be indicated directly or indirectly.

[0219] Various examples have been cited in this description. Descriptions of features or functionalities associated with a particular example indicate that those features or functionalities exist in that example. The use of the terms "example," "for example," "can," or "may," whether explicitly stated or not, indicates that those features or functionalities exist at least in the described example (whether or not they are described as examples), and that they can exist in some or all of the other examples, but are not necessarily present. Therefore, "example," "for example," "can," or "may" refers to a specific instance within a class of examples. An instance's property can be a property of only that instance, a property of the class, or a property of a subclass of the class (which includes some, but not all, instances within the class).

[0220] In this description, unless otherwise expressly stated, references to “a / an / the” [feature, element, component, part...] are inclusive rather than exclusive and should be interpreted as “at least one” [feature, element, component, part...]. That is, any statement that X includes one / the Y indicates that X can include only one Y, or can include more than one Y, unless the context explicitly indicates the opposite. If the use of “a” or “the” is intended to have an exclusive meaning, it should be made explicit in the context. In some cases, the use of “at least one” or “one or more” can be used to emphasize an inclusive meaning, but the omission of these terms should not be construed as having any exclusive meaning. As used herein, “at least one of the following: ” and “at least one of ” and similar expressions (where the list of two or more elements is connected by “and” or “or”) refer to at least any one element, or at least two or more elements, or at least all elements.

[0221] The presence of a feature (or combination of features) in a claim refers to the feature or combination of features itself, as well as features that achieve substantially the same technical effect (equivalent features). Equivalent features include, for example, variations and features that achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

[0222] In this specification, adjectives or adjective phrases have been used to describe the characteristics of various examples. Such descriptions of characteristics related to examples indicate that the characteristic exists exactly as described in some examples, and substantially as described in others.

[0223] In the foregoing description, the described apparatus may alternatively or additionally include an apparatus that, in some other examples, includes a distributed apparatus system, such as a client / server apparatus system. In examples where the provided apparatus forms (or the method is implemented as) a distributed system, each apparatus forming a component and / or part of the system provides (or implements) one or more features that collectively implement an example of this disclosure. In some examples, the apparatus is reconfigured by an entity other than its initial manufacturer to implement an example of this disclosure by being provided with additional software, such as software downloaded by a user, which, when executed, causes the apparatus to implement an example of this disclosure (this implementation is performed entirely by the apparatus or as part of a system such as the apparatus described above).

[0224] The foregoing description illustrates some examples of this disclosure; however, those skilled in the art will recognize that alternative structural and methodological features may exist that provide equivalent functionality to specific examples of such structures and features described above, and for the sake of brevity and clarity, have been omitted from the foregoing description. Nevertheless, unless such alternative structural or methodological features are expressly excluded in the foregoing description of examples of this disclosure, the foregoing description should be understood to implicitly include references to these alternative structural and methodological features that provide equivalent functionality.

[0225] While the foregoing description is intended to draw attention to features deemed important, applicants may still seek protection by means of any patentable feature or combination of features mentioned above and / or shown in the accompanying drawings, whether or not they are emphasized.

[0226] The examples and appended claims of this disclosure can be appropriately combined in any manner obvious to those skilled in the art. Separate references to “example,” “in some examples,” and / or similar terms in the specification do not necessarily refer to the same examples, and these examples are not contradictory unless otherwise stated and / or apparent to those skilled in the art from the specification. For example, a feature, structure, method, module, step, action, etc., described in one example may be included in other examples, but is not necessarily included in other examples.

[0227] Each and every claim is incorporated herein as a further disclosure, and these claims are embodiments of this disclosure. Furthermore, while the claims herein are provided to include specific dependencies, it should be contemplated that any claim can depend on any other claim, and that any alternative embodiments can be produced to some extent by combining, integrating, and / or omitting features of the claims and / or changing the dependencies of the claims, any such alternative embodiments and their equivalents are also within the scope of this disclosure.

Claims

1. An apparatus comprising: A component for receiving information from a network node indicating one or more resources, said one or more resources being used by the device to send a request to suspend at least one activity during a time period, said at least one activity including at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Monitoring and control channels; Components for determining whether to request a suspension of the at least one activity during the time period, based at least in part on the energy state of the device; A component for sending the request to the network node via the one or more resources in at least part of response to determining that the request is to suspend the at least one activity during the time period; as well as A component for suspending at least one activity during the time period, at least in part, in response to the determination.

2. The apparatus of claim 1, wherein determining whether to request a suspension of the at least one activity during the time period is based at least in part on the energy state of the apparatus comprises determining whether one or more criteria are met, and wherein said one or more criteria are based at least in part on at least one of the following: Does the device have sufficient energy to complete the at least one activity? The amount of energy stored at the device; The rate of energy harvesting at the device; An estimate of the energy and / or power available to the device; or Does the device need to pause at least one activity during the time period in order to collect energy during the time period? 3. The apparatus according to any of the preceding claims further includes: Components for transitioning to or remaining in energy harvesting mode in at least part of response to the determination; and / or Components used to collect energy during the time period.

4. The apparatus according to any of the preceding claims, wherein the at least one activity includes at least one of the following: Hybrid Automatic Repeat Request (HARQ) process; HARQ Rx; or HARQ Tx.

5. The apparatus according to any of the preceding claims, wherein the request to suspend the at least one activity during a time period is a request to suspend the at least one activity during at least one of the following periods: HARQ process; UL session; or DL session.

6. The apparatus according to any preceding claim, wherein the time period is at least one of the following: Pre-configured, or Indicated by the network node.

7. The apparatus according to any preceding claim further includes a component for receiving information indicating one or more threshold parameter values, said one or more threshold parameter values ​​being used to enable the apparatus to determine whether to send the request; and The determination is based, at least in part, on the values ​​of the one or more threshold parameters.

8. The apparatus of claim 7, wherein the one or more threshold parameter values ​​include at least one of the following: An indication of the amount of data transmitted by the device; An indication of the estimation of the data received by the device; or An indication of the number of requests allowed within a time period.

9. The apparatus according to any of the preceding claims further includes a component for resuming the at least one activity in at least a partial response to determining at least one of the following: The specified time period has expired; Before the expiration of the stated time period, the device has sufficient energy to complete the at least one activity; or Before the expiration of the time period, the estimated amount of energy and / or power available to the device exceeds a threshold amount.

10. The apparatus according to any of the preceding claims, further comprising: A component for sending a request to a network node via the one or more resources to change the radio resource control state of the device.

11. The apparatus according to any of the preceding claims, further comprising: A component for sending information to the network node indicating a request to resume the at least one activity.

12. The apparatus according to any of the preceding claims, further comprising: A component for determining whether the device has been released from the RRC connection state, wherein the determination is based at least in part on the determination that a request to resume the at least one activity has not been sent by the device to the network node during the time period.

13. The apparatus according to any of the preceding claims, further comprising: A component for receiving from the network node information indicating that the device has been released from the RRC connection state, wherein the information is received at least in part in response to the device not sending a request to the network node to resume the at least one activity during the time period.

14. The apparatus according to any preceding claim, wherein the apparatus comprises at least one of the following: User Equipment (UE); Energy harvesting (EH) equipment; Reduced capacity RedCap devices; Internet of Things (IoT) devices; or Environmental IoT (AIoT) devices.

15. An apparatus comprising: A component for sending information indicating one or more resources to a user equipment (UE), said one or more resources being used by the UE to send a request to suspend at least one activity during a time period, said at least one activity including at least one of the following: At least one receiving Rx process; At least one transmission Tx process; or Scheduling control channel; A component for receiving the request from the UE via the one or more resources; as well as A component for suspending at least one activity during the time period, at least in part, in response to the received request.

Images