WO2022152841A1 - Configuration flexible d'indicateur précoce de radiomessagerie basé sur des informations de commande de liaison descendante - Google Patents

Configuration flexible d'indicateur précoce de radiomessagerie basé sur des informations de commande de liaison descendante Download PDF

Info

Publication number
WO2022152841A1
WO2022152841A1 PCT/EP2022/050738 EP2022050738W WO2022152841A1 WO 2022152841 A1 WO2022152841 A1 WO 2022152841A1 EP 2022050738 W EP2022050738 W EP 2022050738W WO 2022152841 A1 WO2022152841 A1 WO 2022152841A1
Authority
WO
WIPO (PCT)
Prior art keywords
pei
wireless device
information
paging
network
Prior art date
Application number
PCT/EP2022/050738
Other languages
English (en)
Inventor
Ali Nader
Ajit Nimbalker
Andres Reial
Sina MALEKI
Niklas Andgart
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022152841A1 publication Critical patent/WO2022152841A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • a 5 th Generation (5G)/New Radio (NR) user equipment (UE) in RRC IDLE and RRC INACTIVE states operates in a so-called discontinuous reception (DRX) mode enabling it to save power.
  • the UE occasionally wakes up according to a network (NW)- configured scheme and listens to a paging channel.
  • NW network
  • the paging message from the NW can be either initiated by the Core NW (CN) or the base station (e.g., gNB) itself.
  • the CN-Initiated paging is used to reach the UEs in RRC IDLE state
  • the gNB-Initiated paging (aka Radio Access Node (RAN) paging) is used to reach UEs in RRC INACTIVE state.
  • RAN Radio Access Node
  • the paging message from the NW is carried out via a Physical Downlink Control Channel (PDCCH)/Physical Downlink Shared Channel (PDSCH) combination similar to other scheduled data in the downlink (DL).
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • DCI Downlink Control Information
  • CRC Cyclic Redundancy Check
  • the NW typically configures several paging occasions per DRX cycle (e.g., 128 Paging Occasions (POs) within a DRX cycle of 1.28 seconds).
  • the paging configuration i.e., amount of POs and positions in time, is broadcast over the air in system information (part of SIB1 contents).
  • a UE registers in the NW it gets assigned a UE identity called 5G-Shortened-Temporary Mobile Subscriber Identity (5G-S-TMSI). This identity is used by the UE and NW in a formula specified by 3 rd Generation Partnership Project (3GPP) to derive in which of the configured occasions the UE will listen for a potential paging message.
  • 3GPP 3 rd Generation Partnership Project
  • UEs could be listening for a potential paging message at the very same occasion (i.e., in the same PO).
  • the UEs detect a paging DCI (i.e., DCI 1 0 with P-RNTI-scrambled CRC)
  • the UEs have to look in the payload of PDSCH to see whether their identity is present and, thus, if the paging message was intended for them.
  • the payload of the PDSCH might carry up to 32 identities; i.e. up to 32 UEs may be paged at the very same occasion. Even though a UE’s 5G-S-TMSI ID is used in the formulas for deriving the occasion, the identity that the UE looks for inside the PDSCH may be of other type. In case the UE is in RRC IDLE state it looks for its 5G-S-TMSI (i.e., looks for CN-Initiated paging message), whereas in case the UE is in RRC INACTIVE state, it has to look for both for 5G-S-TMSI, and the RAN-assigned Inactive-Radio Network Temporary Identifier (I-RNTI) identity. I.e., a UE in RRC INACTIVE state may be either paged by the CN or the RAN and, thus, it needs to look for both assigned identities.
  • I-RNTI Inactive-Radio Network Temporary Identifier
  • Short Messages (8 bits). If only the scheduling information for Paging is carried, this bit field is reserved. Bits 4-8 are reserved for future use
  • Time domain resource assignment (4 bits). If only the short message is carried, this bit field is reserved.
  • multiple synchronization signals i.e., synchronization signal blocks (SSBs)
  • SSBs synchronization signal blocks
  • the SSBs are transmitted in an SSB burst fashion.
  • a typical SSB burst periodicity is 20ms. For example, if only one SSB is transmitted in the cell (assumed for simplicity throughout the rest of the document), the same SSB is transmitted every 20ms in the cell.
  • FIGURE 1 illustrates SSB transmissions for different Subcarrier Spacing (SCS).
  • SCS Subcarrier Spacing
  • Paging signaling (PDCCH and PDSCH) are specified to have a quasi -colocation relation with an SSB in a cell, meaning that a UE that receives an SSB with a certain receiver configuration can rely on that the same spatial RX configuration and Timing/Frequency (T/F) offsets will be valid for paging reception.
  • T/F Timing/Frequency
  • channel estimates are typically carried out on the SSB(s) prior to the PO occasion.
  • the number of SSBs required for channel estimation prior to PO reception depends on UE perceived coverage level, whether the reception is for PDCCH only or both PDCCH/PDSCH, the hardware architecture (e.g., number of Rx chains) and alike.
  • Paging Early Indicator Paging Early Indicator
  • Each PO monitoring operation is associated with significant processing at the UE. Specifically, the UE must wake ahead of the PO time to obtain T/F synchronization for the paging PDCCH reception, then collect the PDCCH samples and perform tentative decoding. Depending on the Signal-Interference-to-Noise Ratio (SINR), the UE may need to use more than one SSB for loop convergence in preparation for potential paging PDSCH reception, making the T/F sync overhead quite large compared to the PO monitoring (i.e., PO PDCCH reception) itself.
  • SINR Signal-Interference-to-Noise Ratio
  • a PEI signal may be used to indicate to the UE whether paging signaling (PDCCH/PDSCH) is expected in an upcoming PO. If the PEI does not indicate a need to monitor the PO, the UE may skip high-quality loop convergence efforts and instead go to deep sleep state (low power consuming state) when there are no paging signals to receive. If, on the other hand, the PEI indicates that a paging PDCCH/PDSCH is expected, the UE will prepare for possible PDSCH reception and monitor the PDCCH to find out whether it is being targeted.
  • paging signaling PDCCH/PDSCH
  • the UE regularly decodes/searches for PEI at preconfigured occasions.
  • a PEI which may also be referred to as Wake Up Signal (WUS)
  • WUS Wake Up Signal
  • a PEI is transmitted by the NW based on which the UE knows that it shall wake up, prepare itself for reception (perform channel estimate), and receive a potential message at specified occasion, see FIGURE 2.
  • WUS Wake Up Signal
  • Such PEI signals are transmitted by the NW in addition to existing paging-related transmission.
  • PEI transmission is a cost for the NW/gNB, in terms of resources not available for data transmission, and due to the need to wake up from sleep states to perform additional transmissions.
  • PEI if activated, needs to be provided to all UEs in the NW or in a cell when they are paged.
  • a DCI based PEI is an additional DCI transmission (in addition to paging DCI) when the UE is paged.
  • the transmission applicable to different POs may differ depending on current NW paging load and the type of UEs being paged per PO, for example usage of TB Scaling by the NW which may be relevant at low loads and/or when UEs with simple receivers are being paged. Or perhaps at very high NW load, the NW needs to, with short notice/immediately, turn off provision of PEI.
  • the NW needs also see to that the UE reception of combination of PEI and PO DCI are reliable enough to avoid missed paging.
  • not all UEs in the NW need or are expected to utilize the transmitted PEI. For example, UEs in good link conditions, UEs with advanced receivers/HW components, or UEs with certain use cases of traffic scenarios where Idle mode power consumption accounts for a small portion of total consumed power may not need to utilize the transmitted PEI.
  • the invention describes solution aspects in the NW for a flexible DCI-based PEI configuration and transmission occasions for UEs or POs, including the following (with examples):
  • one technical advantage may be that certain embodiments provide a flexible configuration of a DCI-based PEI that helps the UE in reducing of IDLE/INACTIVE power consumption and at the same time enables reduction of NW signaling overhead caused by the said PEI transmission.
  • Overhead now occurs only when the first PO is not utilized for scheduling a paging PDSCH transmission for the first set of UEs. This is in contrast to schemes with dedicated WUS transmission where an additional transmission (e.g., PDCCH) is required for every occupied PO.
  • PDCCH additional transmission
  • a more general term “network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node.
  • network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT, test equipment (physical node or software), etc.
  • MSR multi-standard radio
  • RNC radio network
  • the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.
  • terminologies such as base station/gNodeB and UE should be considered nonlimiting and do in particular not imply a certain hierarchical relation between the two; in general, “gNodeB” could be considered as device 1 and “UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.
  • idle/IDLE is used to refer to both RRC IDLE and RRC INACTIVE states.
  • FIGURE 3 illustrates the idea of utilizing the PDCCH of PO assigned to UE1 to convey PEI for the PO assigned to UE2.
  • the NW is utilizing the already existing transmissions to convey the PEI for a UE.
  • the only occasions when the NW has to transmit the PEI as an extra transmission is when no UE is paged at all at a certain PO, see last occasion on timeline of FIGURE 3.
  • Previous techniques use the currently reserved bits of the paging DCI (DCI 1-0 with CRC scrambled with P-RNTI).
  • PEI- DCI a separate PEI-specific DCI
  • PO-DCI superimposing/multiplexing DCI for paging
  • PEI- DCI a separate PEI-specific DCI
  • the UEs neither legacy or PEI- capable UEs are aware of the multiplexing and legacy UEs are thereby not impacted.
  • certain embodiments may allow for dynamic (temporal e.g., in case temporarily a certain service is ongoing in the cell) and/or future (potentially permanent) separation of PEI- and PO-DCIs, in any of the cases for which the current reserved bits of DCI may be needed for other purposes or in case more information is to be carried by the PEI-DCI.
  • dynamic temporary e.g., in case temporarily a certain service is ongoing in the cell
  • future (potentially permanent) separation of PEI- and PO-DCIs in any of the cases for which the current reserved bits of DCI may be needed for other purposes or in case more information is to be carried by the PEI-DCI.
  • TBS Transport Block Size
  • the UE will know in advance to PO PDSCH reception whether the upcoming PDSCH is TB scaled. If so, the UE may then avoid excessive SSB/TRS/(any other RS) decoding between the PEI occasion and the PO PDSCH as it knows that the channel is heavily encoded (lower coding rate).
  • this information is PO-specific rather than a common (pre-)configuration that is broadcast and applicable to all PO-PDSCHs; i.e., the NW can based on current load and/type of UEs that are being paged, decide for TB Scaling and inform the UEs per PO in advance.
  • this PEI-DCI optionally carries more information as outlined below.
  • the said information i.e., contents of this PEI-DCI
  • its configuration/formation i.e., its configuration/formation
  • its activation/deactivation i.e., its activation/deactivation
  • its time-relation to PO i.e., its time-relation to PO
  • applicability to various POs are discussed below.
  • PEI Format In order to achieve the possibility to superimpose the newly introduced PEI-DCI on top of the PO-DCI as depicted in FIGURE 3, we define a DCI with flexible bit position for each information element carried within. Furthermore, we introduce a configurable PEI-RNTI used in the CRC (de- /)scrambling process. Choosing the information element positions carefully, and configuring in the UE the PEI-RNTI to be equal to P-RNTI, allows the NW to in a single transmission carry two DCIs; one PO-DCI decoded by the UEs decoding their PO PDCCH, and one PEI-DCI decoded by the UEs decoding their PEI at the same occasion.
  • FIGURE 4 This is depicted in FIGURE 4, where the PEI-DCI provides information at positions and/or with code points that are either reserved by PO-DCI or share the same contents at the transmission occasion. More specifically, the left side of FIGURE 4 illustrates the existing PO-DCI format. The right side of FIGURE 4 illustrates the newly introduced PEI-DCI.
  • the gNB typically uses the same TB Scaling scheme during a longer period (i.e., same value configured in both the current PO where PO-DCI is provided and in the upcoming PO to which PEI-DCI is pointing at), then the very same position can be used to convey both. Otherwise, other bits may be used in PEI-DCI to convey this information and the TB scaling positions of PO-DCI are kept as reserved/unknown in PEI-DCI.
  • PEI-RNTI The configuration of PEI-RNTI is provided to the UE as part of PEI-Configuration (either broadcast or dedicated as outlined further below) and can be changed when NW finds it suitable. This allows for dynamic change in the multiplexing decision by the NW. For example, temporarily the NW may want to raise the aggregation level of one of the DCIs (e.g., PEI) but not necessarily the other DCI. Alternately, temporarily a service is ongoing for which more bits are needed in one or the other DCI leading to that the overlap cannot be maintained.
  • the NW may want to raise the aggregation level of one of the DCIs (e.g., PEI) but not necessarily the other DCI.
  • a service is ongoing for which more bits are needed in one or the other DCI leading to that the overlap cannot be maintained.
  • the NW can change/configure another RNTI for PEI and/or simply change the overlap occasions between PEI and POs to non-overlapping and thereby keep them (PEI- and PO-DCI) separate at the cost of not being able to co-transmit them.
  • the NW may also decide to un-configure one or more of the bitfields such that the payload size fits within CoresetO BW.
  • the NW may have configured PEI with a first bitfield, and a second bitfield, where the first bitfield may be the indication related to paging, while the second bitfield may be TB Scaling or TRS presence indication, etc.
  • the NW notes that there is no sufficient space within the same PO to transmit both paging as well as PEI DCI, and as such the NW may decide to unconfigure the first, or second, or any other bitfield from PEI.
  • the NW prioritize keeping the bitfield associated with the paging indication.
  • FIGURE 5 illustrates an example of new information elements and number of bits relevant to PEI contents in addition to PO-DCI.
  • the “Group indicator” indicates whether the PEI is relevant to the UEs paging group. Depending on the current paging load in the NW, the NW may want to use configurable number of groups (2 and 4 groups exemplified herein).
  • the “TRS presence ” indicates whether the NW is providing TRS for idle mode UEs. In one aspect, the validity timer (for how long the UE can assume that TRS is present) is also provided.
  • the “PEI Cfg update Indicator” tells the UE to re-read the broadcast PEI configuration immediately. I.e., rather than using the regular broadcast update mechanisms applicable at modification period boundaries and affecting all UEs of a cell, this indicator is used to only indicate a change on the broadcast channel for the UEs interested/consuming the PEI-DCI.
  • PEI on/off switch is used to dynamically and potentially per PO (if configured to be interpreted per PO in PEI-Config outlined further below) controls whether PEI is applicable.
  • PEI configuration (called PEI-Config hereafter) is provided as part of broadcast system information (e.g., as part of SIB1).
  • This configuration may also be provided to the UE in a dedicated message in which case its contents override the parameters provided in broadcast manner.
  • the configuration is only applicable to a specific bandwidth part (BWP). This is especially applicable if the NW has configured multiple BWPs (e.g. for connected mode traffic) for which paging is configured. For example, the NW might not have capacity in a BWP to provide PEI and therefore wishes not to configure PEI therein.
  • BWP bandwidth part
  • Reference source not found outlines an exemplary top-level set of parameters and their meaning. Note that most parameters are optional. The optionality of each of these configuration parameters can either be indicated directly on top level or through invalid bit position configuration as described below with regard to Pei-DCI-FormatConfig.
  • the NW configures the position of the parameters (information elements (IEs)) in the PEI-DCI.
  • IEs information elements
  • the NW can explicitly indicate the starting position and the length of each field in the PEI DCI, along with the size of PEI DCI, or the NW can explicitly indicate the starting position in the PEI DCI, with a pre-determined order of fields (e.g. tb- ScalinglnfoPositionlnPei (if present), followed by trs-PresencelnfoPositioninPei (if present), and so on).
  • a pre-determined order of fields e.g. tb- ScalinglnfoPositionlnPei (if present), followed by trs-PresencelnfoPositioninPei (if present), and so on.
  • L3 typically higher layer
  • the NW configures the position of PEI-DCI (or PEI monitoring occasion(s)) in relation to the UE’s PO.
  • Configuring the PEI search window wisely i.e., with overlap of one UE’s PEI-DCI and another UE’s PO-DCI
  • the NW can see to that PEI and other UE’s PO-DCI are superimposed/multiplexed when possible.
  • configuring the same PEI search window for multiple POs leads to that one PEI can invoke or control multiple POs. From a UE’s perspective, the overlap/multiplexing is not necessarily known. Two options for a PEI search window is configured.
  • the PEI occasions and PO occasions can be separately configured, and a mapping function is used to associate one or more PEI occasions with one or more PO occasions. For example, a given PO can be associated with the most recent PEI occasion(s) that occur with an offset (e.g. X milliseconds/slot/seconds) relative to the start of the PO.
  • FIGURE 6 illustrates PEI search window configuration and UEs timeline.
  • the NW may want to provide more than one single PEI-Config (outlined in previous sections). As can be seen in the example depicted in FIGURE 7, quite many POs can be configured in a cell. In this example 1024 (256 Frames x 4 POs per frame) are configured during a DRX cycle of 2,56 seconds. The NW might not find one single configuration applicable to all POs suitable. Perhaps the NW does not have the capacity to provide PEI for every single PO and may want to prioritize the configuration and provision of PEI for a subset of these POs.
  • the NW can configure specific UEs with a dedicated PEI-Config in which case the dedicated configuration parameters override the broadcast counterparts. NW may even allow/di sallow PEI usage per UE (e.g., UEs with poor receivers that have shown to be unreliable to receive both PEI and PO PDCCH and run high risk for missed page).
  • FIGURE 8 illustrates broadcast configuration alternatives.
  • Option A is the simplest form, one single PEI-Config applies to everything.
  • Option B up to 4 configurations (one per PO instance of the frames).
  • Option C includes one or more configurations where each is applicable to a range of POs.
  • Option D includes one or more configurations with full dynamics per PO.
  • One or more reference configurations broadcast. But only applicable to a PO if the PO indicates applicability.
  • Option D is the aspect with finest granularity but without excessive configuration provided as part of PEI-Config. In this invention, it is not seen as viable to provide a list of configurations for each of e.g., the 1024 POs exemplified above. Instead, one/few configurations are provided but the applicability of these are controlled through the PO- and PEI. DCIs per PO. More specifically, Per PO, in the PO-DCI, there is an indicator added saying whether this PO obeys/conforms to the PEI- Config (in one version this indicator is applicable only to a group of UEs sharing the same PO with other UEs).
  • PO-DCI is extended, e.g., reserved code points are taken to indicate applicable configuration (true/false or on/off if only one PEI-Config broadcast. If several PEI- Configs broadcast, via an index to the relevant configuration) and relevant group.
  • PEI-DCI can then similar to the PO-DCI turn off applicability dynamically, i.e., a UE decoding PEI periodically can be “commanded” to fallback to regular PO decoding. If UE for any reason did not try to decode PEI-DCI (occupied with other activity such as inter-freq measurements or alike), it shall assume that PEI applicability was turned off and fall back to regular PO decoding to check in the PO-DCI whether PEI is applicable again.
  • this is configured in PEI-Config (see pei-perPO-applicability in PEI-Config top level configuration above). If this feature/aspect is configured in PEI-Config, and if PO-DCI does not indicate that it obeys PEI-Config, then PEI is not applicable to that specific PO.
  • FIGURE 9 illustrates an example of Option D.
  • FIGURE 9 is an example of per-PO control of PEI applicability and UEs timeline.
  • FIGURE 10 illustrates a wireless network, in accordance with some embodiments.
  • the wireless network of FIGURE 10 only depicts network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 160 and wireless device 110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 160 and wireless device 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • FIGURE 11 illustrates an example network node 160, according to certain embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162.
  • network node 160 illustrated in the example wireless network of FIGURE 11 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.
  • Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.
  • processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174.
  • radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units.
  • processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170.
  • some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non
  • Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190.
  • processing circuitry 170 and device readable medium 180 may be considered to be integrated.
  • Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or wireless devices 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170.
  • Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • all or some of RF transceiver circuitry 172 may be considered a part of interface 190.
  • interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).
  • Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.
  • Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187.
  • an external power source e.g., an electricity outlet
  • power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187.
  • the battery may provide backup power should the external power source fail.
  • Other types of power sources, such as photovoltaic devices, may also be used.
  • network node 160 may include additional components beyond those shown in FIGURE 11 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.
  • FIGURE 12 illustrates an example wireless device 110.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term wireless device may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a wireless device may be configured to transmit and/or receive information without direct human interaction.
  • a wireless device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a wireless device may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a wireless device may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another wireless device and/or a network node.
  • the wireless device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the wireless device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a wireless device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • wireless device 110 may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal.
  • a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137.
  • Wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within wireless device 110.
  • Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and be connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.
  • interface 114 comprises radio front end circuitry 112 and antenna 111.
  • Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116.
  • Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120.
  • Radio front end circuitry 112 may be coupled to or a part of antenna 111.
  • wireless device 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111.
  • some or all of RF transceiver circuitry 122 may be considered a part of interface 114.
  • Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other wireless device 110 components, such as device readable medium 130, wireless device 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.
  • processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 120 of wireless device 110 may comprise a SOC.
  • RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 122 may be a part of interface 114.
  • RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
  • processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of wireless device 110, but are enjoyed by wireless device 110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120.
  • Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120.
  • processing circuitry 120 and device readable medium 130 may be considered to be integrated.
  • User interface equipment 132 may provide components that allow for a human user to interact with wireless device 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction may be via a touch screen; if wireless device 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, wireless device 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.
  • Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used, wireless device 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • an external power source e.g., an electricity outlet
  • wireless device 110 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of wireless device 110 to which power is supplied.
  • FIGURE 13 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 200 as illustrated in FIGURE 11, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 13 is a UE, the components discussed herein are equally applicable to a wireless device, and vice-versa.
  • UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof.
  • Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIGURE 13, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 201 may be configured to process computer instructions and data.
  • Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 200 may be configured to use an output device via input/output interface 205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200.
  • the input device may include a touch-sensitive or presencesensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 211 may be configured to provide a communication interface to network 243a.
  • Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243a may comprise a Wi-Fi network.
  • Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 219 may be configured to provide computer instructions or data to processing circuitry 201.
  • ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a nonvolatile memory.
  • Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227.
  • Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • Blu-Ray optical disc drive holographic digital data storage (HDDS) optical disc drive
  • DIMM
  • Storage medium 221 may allow UE 200 to access computerexecutable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.
  • processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231.
  • Network 243a and network 243b may be the same network or networks or different network or networks.
  • Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b.
  • communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.
  • communication subsystem 231 may be configured to include any of the components described herein.
  • processing circuitry 201 may be configured to communicate with any of such components over bus 202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURE 14 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390.
  • Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 300 comprises general -purpose or special -purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360.
  • Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360.
  • Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.
  • processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.
  • hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.
  • CPE customer premise equipment
  • MANO management and orchestration
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225.
  • Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.
  • FIGURE 15 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414.
  • Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c.
  • Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415.
  • a first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c.
  • a second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.
  • Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 430 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider.
  • Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420.
  • Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).
  • the communication system of FIGURE 15 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430.
  • the connectivity may be described as an over-the- top (OTT) connection 450.
  • Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications.
  • base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.
  • FIGURE 16 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500.
  • Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities.
  • processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518.
  • Software 511 includes host application 512.
  • Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.
  • Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530.
  • Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 16) served by base station 520.
  • Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 16) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • processing circuitry 528 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 520 further has software 521 stored internally or accessible via an external connection.
  • Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538.
  • Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or nonhuman user via UE 530, with the support of host computer 510.
  • an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510.
  • client application 532 may receive request data from host application 512 and provide user data in response to the request data.
  • OTT connection 550 may transfer both the request data and the user data.
  • Client application 532 may interact with the user to generate the user data that it provides.
  • host computer 510, base station 520 and UE 530 illustrated in FIGURE 16 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 15, respectively.
  • the inner workings of these entities may be as shown in FIGURE 16 and independently, the surrounding network topology may be that of FIGURE 15.
  • OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.
  • FIGURE 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 15 and 16. For simplicity of the present disclosure, only drawing references to FIGURE 17 will be included in this section.
  • the host computer provides user data.
  • substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 640 the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 15 and 16. For simplicity of the present disclosure, only drawing references to FIGURE 18 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 15 and 16. For simplicity of the present disclosure, only drawing references to FIGURE 19 will be included in this section.
  • step 810 the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data.
  • substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application.
  • substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer.
  • step 840 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 20 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 15 and 16. For simplicity of the present disclosure, only drawing references to FIGURE 20 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • FIGURE 21 depicts a method 1000 by a wireless device, according to certain embodiments.
  • the wireless device receives PEI configuration information. Based on the PEI configuration information, the wireless device receives a signal comprising a paging early indicator (PEI) for at least the first wireless device, at step 1004.
  • the signal further comprises downlink control information for paging (PO-DCI) for at least a second wireless device.
  • PO-DCI includes DCI for a paging occasion.
  • the term also includes, inter alia and as just one example, DCI format 1 0 with CRC scrambled by P-RNTI.
  • FIGURE 22 illustrates a schematic block diagram of a virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 10).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 10).
  • Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 21 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 21 is not necessarily carried out solely by apparatus 1100. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause first receiving module 1110, second receiving module 1120, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.
  • first receiving module 1110 may perform certain of the receiving functions of the apparatus 1100. For example, first receiving module 1110 may receive PEI configuration information.
  • second receiving module 1120 may perform certain other of the receiving functions of the apparatus 1100. For example, based on the PEI configuration information, second receiving module 1120 may receive a signal comprising a paging early indicator (PEI) for at least the first wireless device, at step 1004. The signal further comprises downlink control information for paging (PO-DCI) for at least a second wireless device.
  • PEI paging early indicator
  • PO-DCI downlink control information for paging
  • virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group A and Group D Example Embodiments described below.
  • module or unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 23 depicts a method 1200 by a wireless device, according to certain embodiments.
  • the wireless device receives a signal comprising downlink control information for paging (PO-DCI), wherein the signal further comprises a paging early indicator (PEI) for at least a second wireless device.
  • PO-DCI downlink control information for paging
  • PKI paging early indicator
  • the method may include one or more of any of the steps or features of the Group B and Group D Example Embodiments described below.
  • FIGURE 24 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 10).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 10).
  • Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 23 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 23 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving module 1310 and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1310 may perform certain of the receiving functions of the apparatus 1100. For example, receiving module 1310 may receive a signal comprising downlink control information for paging (PO-DCI), wherein the signal further comprises a paging early indicator (PEI) for at least a second wireless device.
  • PO-DCI downlink control information for paging
  • PKI paging early indicator
  • virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group B and Group D Example Embodiments described below.
  • FIGURE 25 depicts a method 1400 by a network node, according to certain embodiments.
  • the network node transmits a paging early indicator (PEI) for at least a first wireless device and downlink control information for paging (PO-DCI) for at least a second wireless device.
  • PEI paging early indicator
  • PO-DCI downlink control information for paging
  • the method may include one or more of any of the steps or features of the Group C and Group D Example Embodiments described below.
  • FIGURE 26 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 10).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 10).
  • Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 25 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 25 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause transmitting module 1510 and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
  • transmitting module 1510 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1510 may transmit a paging early indicator (PEI) for at least a first wireless device and downlink control information for paging (PO-DCI) for at least a second wireless device.
  • PEI paging early indicator
  • PO-DCI downlink control information for paging
  • virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group C and Group D Example Embodiments described below.
  • Example Al A method by a first wireless device comprising: receiving PEI configuration information; and based on the PEI configuration information, receiving a signal comprising a paging early indicator (PEI) for at least the first wireless device, and wherein the signal further comprises downlink control information for paging (PO-DCI) for at least a second wireless device .
  • PEI paging early indicator
  • PO-DCI downlink control information for paging
  • Example A2 The method of Example Embodiment Al, wherein the PO-DCI is multiplexed with the PEI.
  • Example A3. The method of any one of Example Embodiments Al to A2, wherein the first wireless device is associated with a PEI-Radio Network Identifier (PEI-RNTI), and wherein the PEI- RNTI is the same as a Paging-Radio Network Temporary Identifier (P-RNTI) associated with the second wireless device.
  • PEI-RNTI PEI-Radio Network Identifier
  • P-RNTI Paging-Radio Network Temporary Identifier
  • Example A4 The method of Example Embodiment A3, further comprising descrambling or decoding the signal using CRC based on the PEI-RNTI.
  • Example A5 The method of any one of Example Embodiments Al to A4, wherein the signal is received in a paging occasion using at least one transmission resource.
  • Example A6 The method of any one of Example Embodiments Al to A5, wherein the PEI comprises Transport Block Size (TBS) scaling information, the TBS scaling information associated with the paging occasion
  • TBS Transport Block Size
  • Example A7 The method of any one of Example Embodiments Al to A6, further comprising receiving, by the first wireless device, PEI configuration information.
  • Example A8 The method of Example Embodiment A7, wherein the PEI configuration information associated a first bitfield with paging information and a second bitfield with TBS scaling information.
  • Example A9 The method of any one of Example Embodiments A7 to A8, wherein the PEI configuration information is received as broadcast system information.
  • Example Al 0. The method of any one of Example Embodiments A7 to A8, wherein the PEI configuration information is received in a dedicated message.
  • Example Al l The method of any one of Example Embodiments A7 to A10, wherein the PEI configuration information comprises a respective position for a plurality of information elements within the signal.
  • Example A12 The method of Example Embodiment Al l, wherein the plurality of information elements are associated with: bit positions defined as reserved and/or bit positions that are not used for the PO-DCI.
  • Example A13 The method of Example Embodiment Al l, wherein a respective position of each of the plurality of information elements is carried in the PEI.
  • Example Al 4 The method of Example Embodiment A13, further comprising receiving an indication from the network node of at least one of: a starting position of each information element, a length of each information element, and a size of the signal.
  • Example A15 The method of Example Embodiment A14, further comprising receiving an indication from the network node of a starting position of the PEI and an order of the plurality of information elements.
  • Example Al 6 The method of any one of Example Embodiment Al 1 to Al 5, wherein the plurality of information elements comprises at least one of: a size of the PEI, TBS scaling information, TRS scaling information, group information, short message information, configuration update information, on off switch information, one to many relation information, and wakeup information.
  • Example A17 The method of any one of Embodiments A7 to A16, wherein the PEI configuration information comprises a respective starting position and a respective length of each of a plurality of information elements in the signal.
  • Example A18 The method of any one of Example Embodiments A7 to A17, wherein the PEI configuration information comprises at least one PEI offset, each one of the at least one PEI offset indicating a position of the PEI in relation to a respective one of a plurality of positioning occasions for paging.
  • Example Al 9 The method of any one of Example Embodiments A7 to Al 8, wherein receiving the PEI configuration information comprises: receiving a first PEI configuration information message associating a first PEI with a first paging occasion; and receiving a second PEI configuration information message associating a second PEI with a second paging occasion.
  • Example A20 The method of any one of Example Embodiments A7 to Al 9, wherein the PEI configuration information applies to a range of paging occasions.
  • Example A21 The method of any one of Example Embodiments A7 to Al 9, wherein the PEI configuration information applies to all paging occasions.
  • Example A22 The method of any one of Example Embodiments A7 to Al 9, wherein the PEI configuration information applies to a single paging occasion.
  • Example A23 The method of any one of Example Embodiments A7 to A22, wherein the PO-DCI comprises an indicator indicating whether the PEI configuration information applies to a paging occasion.
  • Example A24 A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Al to A23.
  • Example A25 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Al to A23.
  • Example A26 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Al to A23.
  • Example A27 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Al to A23.
  • Example Bl A method by a first wireless device comprising: receiving a signal comprising downlink control information for paging (PO-DCI), wherein the signal further comprises a paging early indicator (PEI) for at least a second wireless device.
  • PO-DCI downlink control information for paging
  • PKI paging early indicator
  • Example B2 The method of Example Embodiment Bl, wherein the PO-DCI is multiplexed with the PEI.
  • Example B3 The method of any one of Example Embodiments Bl to B2, wherein the first wireless device is associated with A Paging-Radio Network Temporary Identifier (P-RNTI), and wherein the P-RNTI is the same as a PEI-Radio Network Identifier (PEI-RNTI) associated with the second wireless device.
  • P-RNTI Paging-Radio Network Temporary Identifier
  • PEI-RNTI PEI-Radio Network Identifier
  • Example B4 The method of Example Embodiment B3, further comprising descrambling or decoding the signal using CRC based on the P-RNTI.
  • Example B5 The method of any one of Example Embodiments Bl to B4, wherein the signal is received in a paging occasion using at least one transmission resource.
  • Example B6 The method of any one of Example Embodiments Bl to B5, wherein the PEI comprises Transport Block Size (TBS) scaling information, the TBS scaling information associated with the paging occasion.
  • TBS Transport Block Size
  • Example B7 The method of any one of Example Embodiments Bl to B6, wherein the PO-DCI comprises an indicator indicating whether PEI configuration information for the second wireless device applies to a paging occasion.
  • Example B8 A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Bl to B7.
  • Example B9 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Bl to B7.
  • Example BIO A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Bl to B7.
  • Example Bl 1.
  • a non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Bl to B7.
  • Example Cl A method by a network node comprising: transmitting a paging early indicator (PEI) for at least a first wireless device and downlink control information for paging (PO-DCI) for at least a second wireless device.
  • PEI paging early indicator
  • PO-DCI downlink control information for paging
  • Example C2 The method of Example Embodiment Cl, wherein a subset of bit positions in the PO-DCI is populated with at least one information element associated with the PEI.
  • Example C3 The method of any one of Example Embodiments Cl to C2, further comprising: configuring at least the first wireless device with a PEI-Radio Network Identifier (PEI-RNTI); and configuring at least the second wireless device with a Paging-Radio Network Temporary Identifier (P-RNTI), wherein the PEI-RNTI and the P-RNTI are the same.
  • PEI-RNTI PEI-Radio Network Identifier
  • P-RNTI Paging-Radio Network Temporary Identifier
  • Example C4 The method of Example Embodiment C3, wherein the signal is scrambled using CRC based on the PEI-RNTI.
  • Example C5 The method of any one of Example Embodiments Cl to C4, wherein at least a portion of information in the PEI is intended for both the first wireless device and the second wireless device.
  • Example C6 The method of Example Embodiment C5, wherein the portion of information in the PEI that is intended for both the first wireless device and the second wireless device comprises at least one of: an Earthquake and Tsunami Warning Systems (ETWS) indication, a Commercial Mobile Alert Service (CMAS) indication, and TB scaling information.
  • EWS Earthquake and Tsunami Warning Systems
  • CMAS Commercial Mobile Alert Service
  • Example C7 The method of any one of Example Embodiments Cl to C6, wherein the signal is transmitted in a paging occasion using at least one transmission resource.
  • Example C8 The method of any one of Example Embodiments Cl to C7, wherein the PEI comprises Transport Block Size (TBS) scaling information, the TBS scaling information associated with the paging occasion
  • TBS Transport Block Size
  • Example C9 The method of any one of Example Embodiments Cl to C8, further comprising transmitting PEI configuration information to at least the second wireless device.
  • Example CIO The method of Example Embodiment C9, wherein the PEI configuration information associated a first bitfield with paging information and a second bitfield with TBS scaling information.
  • Example Cl l The method of any one of Example Embodiments C9 to CIO, wherein the PEI configuration information is transmitted as broadcast system information.
  • Example C12 The method of any one of Example Embodiments C9 to CIO, wherein the PEI configuration information is transmitted in a dedicated message.
  • Example C13 The method of any one of Example Embodiments C9 to CIO, wherein the PEI configuration information comprises a respective position for a plurality of information elements within the signal.
  • Example C14 The method of Example Embodiment C13, wherein the plurality of information elements comprises at least one of: a size of the PEI, TBS scaling information, TRS scaling information, group information, short message information, configuration update information, on off switch information, one to many relation information, and wakeup information.
  • Example Cl 5 The method of any one of Embodiments C9 to Cl 4, wherein the PEI configuration information comprises a respective starting position and a respective length of each of a plurality of information elements in the signal.
  • Example Cl 6 The method of any one of Example Embodiments C9 to Cl 5, wherein the PEI configuration information comprises at least one PEI offset, each one of the at least one PEI offset indicating a position of the PEI in relation to a respective one of a plurality of positioning occasions for paging.
  • Example Cl 7 The method of any one of Example Embodiments C9 to Cl 6, wherein transmitting the PEI configuration information comprises: transmitting a first PEI configuration information message associating a first PEI with a first paging occasion; and transmitting a second PEI configuration information message associating a second PEI with a second paging occasion.
  • Example C18 The method of any one of Example Embodiments C9 to C17, wherein the PEI configuration information applies to a range of paging occasions.
  • Example C20 The method of any one of Example Embodiments C9 to Cl 7, wherein the PEI configuration information applies to all paging occasions.
  • Example C21 The method of any one of Example Embodiments C9 to Cl 7, wherein the PEI configuration information applies to a single paging occasions.
  • Example C22 The method of any one of Example Embodiments C9 to C21, wherein the PO-DCI comprises an indicator indicating whether the PEI configuration information applies to a paging occasion.
  • Example C23 The method of any one of Example Embodiments C9 to C22, further comprising configuring at least the first wireless device and at least the second wireless device to decode the decode the signal using a single decoding scheme.
  • Example C24 A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C23.
  • Example C25 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C23.
  • Example C26 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C23.
  • Example C27 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Cl to C23.
  • Example DI A wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A and Group B Example Embodiments; and power supply circuitry configured to supply power to the wireless device.
  • Example D2 A network node comprising: processing circuitry configured to perform any of the steps of any of the Group C Example Embodiments; power supply circuitry configured to supply power to the wireless device.
  • Example D3 A wireless device, the wireless device comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A and Group B Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the wireless device.
  • Example D4 A wireless device, the wireless device comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A and Group B Example Embodiments; an input interface connected to the processing circuitry and configured
  • a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a wireless device, wherein the cellular network comprises a network node having a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of the Group C Example Embodiments.
  • Example D5 The communication system of the previous embodiment further including the network node.
  • Example D6 The communication system of the previous 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.
  • Example D7 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device comprises processing circuitry configured to execute a client application associated with the host application.
  • Example D8 A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the network node performs any of the steps of any of the Group C Example Embodiments.
  • Example D9 The method of the previous embodiment, further comprising, at the network node, transmitting the user data.
  • Example DIO The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the wireless device, executing a client application associated with the host application.
  • Example Dl l A wireless device configured to communicate with a network node, the wireless device comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • Example D12 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a wireless device, wherein the wireless device comprises a radio interface and processing circuitry, the wireless device’s components configured to perform any of the steps of any of the Group A and Group B Example Embodiments.
  • Example D13 The communication system of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the wireless device.
  • Example D14 The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application.
  • Example DI 5 A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the wireless device performs any of the steps of any of the Group A and Group B Example Embodiments.
  • Example DI 6 The method of the previous embodiment, further comprising at the wireless device, receiving the user data from the network node.
  • Example DI 7 A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the wireless device comprises a radio interface and processing circuitry, the wireless device’s processing circuitry configured to perform any of the steps of any of the Group A and Group B Example Embodiments.
  • Example D18 The communication system of the previous embodiment, further including the wireless device.
  • Example DI 9 The communication system of the previous 2 embodiments, further including the network node, wherein the network node comprises a radio interface configured to communicate with the wireless device and a communication interface configured to forward to the host computer the user data carried by a transmission from the wireless device to the network node.
  • the network node comprises a radio interface configured to communicate with the wireless device and a communication interface configured to forward to the host computer the user data carried by a transmission from the wireless device to the network node.
  • Example D20 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • Example D21 The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • Example D22 A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, receiving user data transmitted to the network node from the wireless device, wherein the wireless device performs any of the steps of any of the Group A and Group B Example Embodiments.
  • Example D23 The method of the previous embodiment, further comprising, at the wireless device, providing the user data to the network node.
  • Example D24 The method of the previous 2 embodiments, further comprising: at the wireless device, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.
  • Example D25 The method of the previous 3 embodiments, further comprising: at the wireless device, executing a client application; and at the wireless device, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.
  • Example D26 A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the network node comprises a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of the Group C Example Embodiments.
  • Example D27 The communication system of the previous embodiment further including the network node.
  • Example D28 The communication system of the previous 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.
  • Example D29 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the wireless device is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • Example D30 A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the network node has received from the wireless device, wherein the wireless device performs any of the steps of any of the Group A and Group B Example Embodiments.
  • Example D31 The method of the previous embodiment, further comprising at the network node receiving the user data from the wireless device.
  • Example D32 The method of the previous 2 embodiments, further comprising at the network node, initiating a transmission of the received user data to the host computer.
  • Example D33 The method of any of the previous embodiments, wherein the network node comprises a base station.
  • Example D34 The method of any of the previous embodiments, wherein the wireless device comprises a user equipment (UE).
  • UE user equipment
  • E-SMLC Evolved-Serving Mobile Location Centre
  • ECGI Evolved CGI eMBB Enhanced Mobile Broadband eNB
  • NodeB/eNodeB ePDCCH enhanced Physical Downlink Control Channel
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • GERAN GSM EDGE Radio Access Network gNB gNode B (a base station in NR; a Node B supporting NR and connectivity to NGC)
  • PCFICH Physical Control Format Indicator Channel PCH Paging Channel
  • PCI Physical Cell Identity /Identifier PCDCCH Physical Downlink Control Channel
  • PDP Profile Delay Profile PCFICH Physical Control Format Indicator Channel
  • PDSCH Physical Downlink Shared Channel
  • PEI Paging Early Indicator
  • PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel
  • PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation
  • SI System Information SIB System Information Block SIB1 System Information Block Type 1 SINR Signal to Interference and Noise Ratio SNR Signal to Noise Ratio

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des procédés sont réalisés par des dispositifs sans fil, les procédés comprenant la réception d'un signal comprenant un indicateur précoce de radiomessagerie, PEI, pour un premier dispositif sans fil, le signal comprenant également des informations de commande de liaison descendante pour la radiomessagerie, PO-DCI, pour un second dispositif sans fil. Le procédé est mis en œuvre par le premier dispositif sans fil, et comprend également la réception d'informations de configuration de PEI, la réception du signal comprenant la réception du PEI sur la base des informations de configuration de PEI. L'Invention concerne également un procédé de transmission des informations de configuration de PEI, du PEI et des PO-DCI par un nœud de réseau, ainsi qu'un dispositif sans fil et un nœud de réseau correspondants.
PCT/EP2022/050738 2021-01-15 2022-01-14 Configuration flexible d'indicateur précoce de radiomessagerie basé sur des informations de commande de liaison descendante WO2022152841A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163137859P 2021-01-15 2021-01-15
US63/137,859 2021-01-15

Publications (1)

Publication Number Publication Date
WO2022152841A1 true WO2022152841A1 (fr) 2022-07-21

Family

ID=80218491

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/050738 WO2022152841A1 (fr) 2021-01-15 2022-01-14 Configuration flexible d'indicateur précoce de radiomessagerie basé sur des informations de commande de liaison descendante

Country Status (1)

Country Link
WO (1) WO2022152841A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.212
MEDIATEK INC: "Report of email discussion [Post111-e][907][ePowSav] UE grouping (Mediatek)", vol. RAN WG2, no. Online; 20201102 - 20201113, 23 October 2020 (2020-10-23), XP051942615, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_112-e/Docs/R2-2009784.zip R2-2009784 Report of [Post111-e][907][ePowSav] UE grouping (Mediatek).docx> [retrieved on 20201023] *
MODERATOR (MEDIATEK): "Summary for Potential Paging Enhancements", vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 19 November 2020 (2020-11-19), XP051955954, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_103-e/Docs/R1-2009753.zip R1-2009753_Summary for Potential Paging Enhancements.docx> [retrieved on 20201119] *

Similar Documents

Publication Publication Date Title
CN112020842B (zh) 用于指示针对rrc连接之前的物理下行链路共享信道的时域资源分配的方法
CN111727620A (zh) Rlm和波束监视参数的优化的重新配置
US11696278B2 (en) Methods, apparatus and computer-readable media related to semi-persistent scheduling configuration
EP3808129B1 (fr) Détermination de périodicité de ssb/rmsi pour noeud iab
CN111201827B (zh) 用于免授权pusch上的uci的传输的方法及装置
EP3909326A2 (fr) Procédés et appareils de positionnement sur la base du signal de référence de sonde
JP2023509799A (ja) 低複雑度ユーザ機器のためのランダムアクセス
US20230189338A1 (en) COT/FFP Scheduling in Unlicensed Spectrum
US20230043789A1 (en) Wake Up Signal Monitoring Span Capability Signaling
JP2024054127A (ja) 低遅延通信のためのｈａｒｑコードブック決定方法
CN115278824A (zh) 解码plmn信息的方法及其设备
WO2021162617A1 (fr) Mécanismes de regroupement de dispositifs sans fil et configuration de réseau pour réduction de fausse radiomessagerie
WO2022031205A1 (fr) Rlm pour scg en mode d&#39;économie d&#39;énergie
EP4169197A1 (fr) Procédés fournissant des informations de commande de liaison descendante et des données de liaison descendante utilisant des ressources se chevauchant, ainsi que dispositifs de communication associés et noeuds de réseau d&#39;accès radio associés
US20240235875A1 (en) Harq feedback codebook for multicast and unicast
WO2022152843A1 (fr) Robustesse améliorée de réception de radiomessagerie assistée par pei
EP3753192B1 (fr) Fiabilité améliorée de décodage de dci
EP3753309B1 (fr) Fiabilité de pcfich améliorée à l&#39;aide d&#39;une amplification de puissance
WO2022152841A1 (fr) Configuration flexible d&#39;indicateur précoce de radiomessagerie basé sur des informations de commande de liaison descendante
CN113615261B (zh) 延长不连续接收活动时间
US11296825B2 (en) Configuration of additonal system information block repetitions
CN116076112A (zh) 用于新无线电（nr）的用户设备定位
EP4229925A1 (fr) Réception de données récurrentes dans un ue en veille/inactif
WO2022029120A1 (fr) Retard d&#39;application de commutation de groupe défini par un ss
CN113615261A (zh) 延长不连续接收活动时间

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22702611

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22702611

Country of ref document: EP

Kind code of ref document: A1