WO2021118438A1 - Opportunité de diffusion pour la réception d'un signal - Google Patents

Opportunité de diffusion pour la réception d'un signal Download PDF

Info

Publication number
WO2021118438A1
WO2021118438A1 PCT/SE2020/051180 SE2020051180W WO2021118438A1 WO 2021118438 A1 WO2021118438 A1 WO 2021118438A1 SE 2020051180 W SE2020051180 W SE 2020051180W WO 2021118438 A1 WO2021118438 A1 WO 2021118438A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless device
network node
group
wireless
network
Prior art date
Application number
PCT/SE2020/051180
Other languages
English (en)
Inventor
Jose Angel LEON CALVO
Erik Stare
Jörg Huschke
Stefan Parkvall
Ratheesh Kumar MUNGARA
Mats Folke
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 WO2021118438A1 publication Critical patent/WO2021118438A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02Arrangements for increasing efficiency of notification or paging channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for determining a broadcast occasion for receiving a signal by a wireless device while in an idle or inactive reception mode (IIRM).
  • IIRM idle or inactive reception mode
  • a New Radio (NR) paging mechanism allows the network to communicate a message or deliver data to user equipments (UEs) in 5GMM-registered or 5GMM-Idle state, which are known at tracking area level.
  • UEs user equipments
  • 5GMM-registered or 5GMM-Idle state which are known at tracking area level.
  • the paging is initiated, and paging area is maintained by core network (CN) during Radio Resource Control IDLE (RRC IDLE) state while the paging is initiated and Radio Access Network-based notification area (RNA) is maintained by NR Radio Access Network (NR RAN) during Radio Resource Control INACTIVE (RRC INACTIVE) state.
  • CN Core network
  • RRC IDLE Radio Resource Control IDLE
  • RNA Radio Access Network-based notification area
  • NR RAN Radio Access Network
  • RRC INACTIVE Radio Resource Control INACTIVE
  • a UE in RRC INACTIVE or IDLE is able to monitor the paging messages.
  • a UE is registered in a tracking area or RNA and, therefore, the network sends the paging message in all the possible cells within the tracking area.
  • the UE monitors Paging Occasions (POs) where the paging Downlink Control Indicator (DCI) can be sent once per cycle using Discontinuous Reception (DRX).
  • P-RNTI Paging- Radio Network Temporary Identifier
  • These paging DRX cycles are configured by the network:
  • a default cycle is broadcast in system information (e.g., SIB1).
  • SIB1 system information
  • a UE specific cycle can be configured by via Non- Access Stratum (NAS) signaling (Requested DRX parameters: 5GS DRX parameters).
  • NAS Non- Access Stratum
  • a UE-specific cycle is configured via Radio Resource Control (RRC) signaling (RRC Release: SuspendConfig).
  • RRC Radio Resource Control
  • a UE in RRC IDLE uses the shortest of the first two-cycles above, while a UE in RRC INACTIVE uses the shortest of the three cycles.
  • a UE in RRC CONNECTED monitors the paging channels in any PO signaled in the system information (SI) message for any SI change indication and Public Warning System (PWS) notification.
  • SI system information
  • PWS Public Warning System
  • the same paging message is created for Radio Access Network (RAN) or CN-initiated paging.
  • the UE initiates RRC Connection Resume procedure upon receiving RAN-initiated paging. If the UE receives CN-initiated paging in RRC_INACTIVE state, the UE moves to RRC IDLE and informs NAS.
  • a Paging Frame can contain several paging occasions or starting points for Paging Occasions (POs).
  • the PF and PO for paging are determined by the following formulae in current NR:
  • SFN System Frame Number
  • T DRX cycle of the UE N: number of total paging frames in T Ns: Number of paging occasions for a PF PF offset: offset used for PF (Paging Frame) determination T div N: indicates the remainder free division operation of T/N Index(i s): indicates the index of the PO for one of the multiple potential Paging Occasions
  • MBMS Multimedia Broadcast Multicast Services
  • MBSFN Multimedia Broadcast multicast service Single Frequency Network
  • MBMS reception is supported in RRC IDLE mode.
  • Scheduling is not based on the Physical Downlink Control Channel (PDCCH) but on a combination of SIB 13 and Multicast Control CHannel (MCCH).
  • SIB13 defines which subframes are allocated for MBMS and the MBSFN areas, and for each, how to obtain the MCCH.
  • All Multicast Channels (MCHs) within one MBSFN area use a common subframe allocation (CSA) pattern. Among the subframes defined by the CSA, consecutive subframes are allocated to the same MCH.
  • the MCCH defines the CSA of the MBSFN area. A change notification for the MCCH is transmitted on the PDCCH.
  • This reception mode is an addition to the LTE MBMS idle mode reception.
  • the UEs can be in three different scenarios:
  • Scenario 1 The UE receives both unicast and broadcast service from same Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the UE acts in RoM: the UE receives broadcast MBMS service without PLMN subscription over Evolved Universal Terrestrial Radio Access Network (E-UTRAN) without the need to access and register with the PLMN offering the MBMS service.
  • a UE configured to operate in RoM camps on a network cell in an enhanced MBMS (eMBMS) Broadcast carrier, shall attempt to receive MBMS service based only on a standardised Temporary Mobile Group Identifier (TMGI) value range for RoM.
  • TMGI Temporary Mobile Group Identifier
  • the UE shall not attempt to receive MBMS service for TMGIs outside the standardized TMGI range.
  • the UE shall refrain from any Mobility Management or other signalling with the network offering MBMS.
  • the UE uses the acquired system information to receive MBMS broadcast.
  • Use of RoM does not require Universal Subscriber Identity Module (USIM) for the UE.
  • USIM Universal Subscriber Identity Module
  • the UE acts in RoM with independent unicast: The UE receives unicast service from one serving PLMN (e.g. the PLMN for which it has unicast subscription) and receive MBMS service through a different PLMN.
  • a UE may be configured as RoM with independent unicast using Enhanced Packet Service (EPS) bearer contexts.
  • EPS Enhanced Packet Service
  • This configuration option allows a UE to operate as RoM for MBMS broadcast service, and independently follows regular NAS/RRC procedures for unicast service with a PLMN. This mode of operation requires USIM and PLMN subscription to receive unicast service. No additional subscription or credentials are required to receive MBMS broadcast service.
  • FIGURE 1 illustrates Scenarios 2 and 3, as described above,
  • Any device that is equipped with a MBMS broadcast receiver and is configured to operate in RoM is able to receive the broadcast content, with the following characteristics:
  • the UE can only access broadcast services without subscription.
  • the UE is preconfigured with all the necessary information for the UE to acquire the system information and receive MBMS service.
  • This information includes:
  • TMGI is composed by an MBMS Service ID and a PLMN ID (Mobile Country Code/ Mobile Network Code (MCC/MNC)).
  • MCC/MNC Mobile Country Code/ Mobile Network Code
  • the TMGI(s) for each MBMS service need to be configured in the UE.
  • the UE may be configured to receive TMGI(s) via Service Announcement
  • each UE is individually paged without the possibility to select a group of UEs by using the same transmitted signal. This is due to the nature of the paging message which is a function of the individual UE_ID, i.e., the message is specific for that particular UE. In some cases, e.g., for Vehi cl e-to- Any thing (V2X) and National Security and Public Safety (NSPS) use cases, it is beneficial to include a paging mechanism that is able to address specific groups of UEs in a multicast manner.
  • V2X Vehi cl e-to- Any thing
  • NSPS National Security and Public Safety
  • a UE or group of UEs is in RRC IDLE or RRC INACTIVE mode, they need to transition to RRC CONNECTED mode before being able to receive any transmission other than paging or system information, which may lead to a higher latency in the communications and a potential cumbersome signaling if it is a highly dense scenario.
  • UEs user equipments
  • a method by a wireless device includes receiving, from a network node, system information that is scrambled with a radio network temporary identifier (RNTI) specific for an idle or inactive reception mode (IIRM) or specific for a group of wireless devices. Based on the system information, the wireless device determines at least one broadcast occasion (BO) for receiving at least one signal. While in the IIRM, the wireless device receives the at least one signal during the at least one BO.
  • RNTI radio network temporary identifier
  • IIRM idle or inactive reception mode
  • a wireless device includes processing circuitry configured to receive, from a network node, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices. Based on the system information, the processing circuitry determines at least one BO for receiving at least one signal. While in the IIRM, the processing circuitry receives the at least one signal during the at least one BO.
  • a method by a network node includes determining at least one BO for transmitting at least one signal.
  • the network node transmits, to a wireless device, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices.
  • the system information indicates the at least one BO. While the wireless device is in the IIRM, the network node transmits the at least one signal to the wireless device during the at least one BO.
  • a network node includes processing circuitry configured to determine at least one BO for transmitting at least one signal.
  • the processing circuitry transmits, to a wireless device, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices.
  • the system information indicates the at least one BO. While the wireless device is in the IIRM, the processing circuitry transmits the at least one signal to the wireless device during the at least one BO.
  • Certain embodiments may provide one or more of the following technical advantages.
  • one technical advantage may be that certain embodiments provide a definition of a group identity for a set of UEs, by selecting groups of UEs with the same specific geographical area or service requirements that can be signaled at the same time, facilitates an efficient design from the perspective of resource utilization.
  • a technical advantage may be that certain embodiments obtain an optimal scheme with respect to the allocated resources.
  • one technical advantage may be that certain embodiments enable the reception of messages by a single or a group of UEs without transitioning from RRC IDLE/INACTIVE mode into RRC CONNECTED mode. Accordingly, certain embodiments bring benefits in terms of battery consumption for particular UEs or groups of users.
  • a technical advantage may be that certain embodiments allow a particular set of UEs to be signaled to transition into IIRM of NR MBMS if they are in RRC CONNECTED mode based on successful or unsuccessful HARQ reports received by the network. This may save power, for example.
  • a technical advantage may be that certain embodiments enable a UE to have different IIRM DRX scheduling profiles, i.e., a UE may belong to several groups at the same time or may be interested in different types of services with different priorities. This hierarchy of transmissions creates a more optimal scheduling for reception of broadcast/multicast messages in RRC IDLE/INACTIVE mode.
  • a technical advantage may be that certain embodiments increase the reception performance, i.e., reliability for the downlink, for the UEs in IDLE/INACTIVE mode without using uplink from the UEs, i.e., there is no Hybrid Automatic Repeat Request (HARQ) protocol, and using the same amount of Physical Resource Blocks (PRBs) in the downlink that would be transmitted using normal HARQ operation.
  • HARQ Hybrid Automatic Repeat Request
  • a technical advantage may be that certain embodiments enable several coexisting Discontinuous Reception (DRX) schedules for the UEs. This may lead to optimized monitoring whenever the receiving UEs are interested in certain broadcast messages or services.
  • DRX Discontinuous Reception
  • FIGURE 1 illustrates several scenarios defined for Long Term Evolution (LTE) taken from 3 GPP TS 23.246 vl6.1;
  • FIGURE 2 illustrates an exemplary scenario defining different Geo-Group Area Identifiers (GGAI) for User Equipments (UEs) within the same geographical location or requiring the same service, according to certain embodiments;
  • GGAI Geo-Group Area Identifiers
  • FIGURE 3 illustrates an example wireless network, according to certain embodiments
  • FIGURE 4 illustrates an example network node, according to certain embodiments.
  • FIGURE 5 illustrates an example wireless device, according to certain embodiments
  • FIGURE 6 illustrate an example user equipment, according to certain embodiments.
  • FIGURE 7 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 8 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 9 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 10 illustrates a method implemented in a communication system, according to one embodiment
  • FIGURE 11 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 12 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 13 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 14 illustrates an example method by a wireless device, according to certain embodiments
  • FIGURE 15 illustrates an example virtual apparatus, according to certain embodiments.
  • FIGURE 16 illustrates another example method by a wireless device, according to certain embodiments.
  • FIGURE 17 illustrates another example virtual apparatus, according to certain embodiments.
  • FIGURE 18 illustrates an example method by a network node, according to certain embodiments.
  • FIGURE 19 illustrates another example virtual apparatus, according to certain embodiments.
  • FIGURE 20 illustrates another example method by a network node, according to certain embodiments.
  • FIGURE 21 illustrates another example virtual apparatus, according to certain embodiments.
  • 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
  • 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.
  • gNodeB could be considered as device 1
  • UE could be considered as device 2 and these two devices communicate with each other over some radio channel.
  • the transmitter or receiver could be either gNB, or UE.
  • a mechanism is disclosed for paging or signaling a selected number of UEs, which may belong to a particular group or be associated with a particular group of users, at the same time (or in a coordinated manner).
  • a group of UEs may be defined with a common Paging Frame (PF) and common Paging Occasions (POs) for all the UEs within the group by including a common value for all the UEs within the group in the formulae for PF and PO.
  • PF Paging Frame
  • POs Paging Occasions
  • a mechanism for paging or signaling a particular group of users, within a certain geographical area or to a set of UEs interested on the same service using a newly defined NR group signalling/paging.
  • a group of UEs may be defined or otherwise determined, and a Group ID may be assigned to these UEs based on some (pre-)defined criterion, e.g., geographical area or same service requirements.
  • a mechanism is disclosed to page/signal a group of UEs defined by their geographical area or required service based on a group ID.
  • the group paging mechanism uses the previously defined group structure to optimally use the resources within the group of users. Because of this further categorization/grouping, a new Geo-Group Area Identifier (GGAI) generally smaller than a RAN area or Tracking Area Identity (TAI) is disclosed and provides a higher flexibility to the network. Additionally, a method is disclosed to coordinate the uplink access for the UEs within the group is developed.
  • GGAI Geo-Group Area Identifier
  • TAI Tracking Area Identity
  • not all of the wireless devices in the network or in a cell may be a part of the group of wireless devices.
  • FIGURE 2 illustrates an exemplary scenario defining different GGAI for UEs within the same geographical location or requiring the same service.
  • the GGAI may be related to infrastructure such as, for example street comers.
  • group(s) of wireless devices or users may be defined within emergency zones for NSPS or intersections and parking lots for V2X.
  • a network node such as a gNB, may define Geo-Group areas and generate a GGAI for each Geo-Group area.
  • grouping of UEs based on geographical area
  • grouping according to geographical area is just one example for grouping UEs.
  • the grouping of UEs may be based on other criteria.
  • the group paging procedure described herein may be used as a baseline to define an RRC IDLE/INACTIVE reception mode (IIRM) of NR MBMS.
  • IIRM RRC IDLE/INACTIVE reception mode
  • the UEs may be able to listen to and receive periodic and aperiodic traffic.
  • a mechanism is disclosed that allows the wireless devices or groups of wireless devices, which may include UEs or group of UEs, in certain embodiments, to receive broadcast/multicast messages in IIRM without transitioning into RRC CONNECTED mode. Stated differently, instead of transitioning into RRC CONNECTED mode, which happens in the current NR and legacy systems, the signaled UEs remain in RRC IDLE/INACTIVE mode and are able to receive the transmission.
  • the IIRM mode may be similar to the ordinary IDLE/INACTIVE mode defined by 3GPP with a new functionality to monitor a BO.
  • IDLE/INACTIVE reception mode IIRM
  • IIRM IIRACTIVE reception mode
  • the UE in IIRM mode may, for example, only monitor in the BO.
  • the triggering mechanism for transitioning into IIRM may be based on RRC or network messages received while the UEs are in RRC CONNECTED mode. Additionally or alternatively, the triggering mechanism may be based on an uplink transmission or radio link monitoring (RLM) metrics.
  • RLM radio link monitoring
  • a method to trigger the IIRM mode may be defined based on a number of ACK/NACK not delivered. Certain embodiments may save power.
  • a common time alignment may be defined for different UEs.
  • a common IIRM of NR MBMS DRX (IIRM DRX) cycle for INACTIVE/IDLE UEs may be defined based on the (pre-)defined Group ID.
  • the IIRM DRX may be used by UEs in the group for reception and/or listening of potential messages. Using this mechanism, the UEs belonging to the same group can check Broadcast Occasions (BO) at the same time or in a coordinated manner.
  • BO Broadcast Occasions
  • the network may nevertheless decide to send retransmissions in a (pre-)determined way to increase the reliability. For example, transmissions may be repeated a certain number of times without use of HARQ.
  • a wireless device such as a UE, for example, can have different DRX profiles coexisting since the same UE can be part of different groups at the same time.
  • a prioritization based on service or group location is described.
  • different priorities are defined for the IIRM DRX patterns in order to solve conflicts whenever different receptions or transmissions could collide.
  • UEs may be grouped according to geographical areas such as GGAI. According to certain embodiments, the UEs may be registered in this area. These new Geo-Group areas may be typically smaller than a Radio Access Network-based notification area (RNA) or Tracking Area Identifier (TAI) defined in NR, in particular embodiments.
  • RNA Radio Access Network-based notification area
  • TAI Tracking Area Identifier
  • GNSS UE-intemal Global Navigation Satellite System
  • 3GPP-based solution or a combination of methods, may be used.
  • each UE may send its location to the network node.
  • each UE may send its location by means of Radio Resource Control (RRC) message in a periodic way or in an event-triggered fashion such as, for example, after moving a certain number of meters.
  • RRC Radio Resource Control
  • the gNB may signal to the transmitting UE that it is in a GGAI and consequently the UE will start monitoring the corresponding PO and PF.
  • the network node may signal to the UE the GGAI by means of the geo-area definition (polygon, radius, etc.) together with the GGAI, and the UE may determine whether it is in the specified geo-area and only then monitors the PO and PF.
  • the geo-area definition polygon, radius, etc.
  • each beam may broadcast a GGAI and the UE can register with the network node when the UE selects the beam broadcasting a particular GGAI.
  • each of the UEs may receive the Group ID in a unicast manner upon connection establishment. For example, each UE may receive the Group ID the first time it gets into RRC CONNECTED with this gNB, in a particular embodiment. In another embodiment, if the group is defined while the UE is already in RRC CONNECTED, the UE may receive the Group ID via unicast transmission.
  • the UEs may receive their Group ID via a “PTM Group definition message” targeting all connected UEs, where a list of all UE IDs that are part of the group (as defined by upper layers) is transmitted.
  • this list could be broadcast and may include some compression method in the way the list is defined such as, for example, including ranges of UE IDs, e.g. UE_ID #N to UE_ID #M.
  • the individual UEs may then react depending on whether they are part of the list or not. For large number of UEs, this may be more efficient than addressing individual UEs via unicast.
  • the group information such as, for example, the Group ID, may be shared with the gNB and higher layers by means of RRC messages sent via uplink by the UEs.
  • the previously defined Group ID may have a similar design as the 5G Temporary Mobile Subscriber Identity (TMSI) for an individual UE and consist of 32 bits in order to allocate a sufficient number of groups.
  • TMSI 5G Temporary Mobile Subscriber Identity
  • the PF and PO associated to the legacy paging mechanism are determined by the UE ID.
  • a group paging mechanism may be implemented to address all the UEs in the group using the same transmission. Therefore, the PO and PF associated to a group paging are allocated as a function of the Group ID or any common identifier for the (pre-)defined group
  • Another possibility is to replace the UE ID in the following formulae by the Group ID generated by the gNB or which has been (pre-)configured into the UEs as follows:
  • the UEs belonging to the same group may monitor the different POs where the group paging/signalling downlink control information (DCI) is sent once per cycle using the (pre- )configured DRX pattern for this specific group.
  • the group paging/signalling DCI may be scrambled using a new Group Paging RNTI (GP-RNTI) unique for each group.
  • GP-RNTI Group Paging RNTI
  • the GP-RNTI can work in parallel to the normal P- RNTI.
  • a group of UEs may be signalled simultaneously, i.e., a certain message is addressed to a pre-defined group of users.
  • this signalling involves the group paging mechanism, i.e., UEs transition from IDLE/INACTIVE into CONNECTED mode.
  • a time coordination mechanism is provided to distribute in time the uplink access of the group of UEs transitioning from IDLE/INACTIVE to CONNECTED mode. This may avoid congestion in the uplink due to a large number of UEs trying to connect at the same time.
  • the UE starts by performing the Random Access procedure. In the state-of-the- art NR, this does not imply a randomization in time.
  • the UEs within the same group may randomly select their Random Access opportunity based on some time distribution within a (pre-) defined time window [0, T] using e.g. a rectangular distribution.
  • each UE may also be allocated an ACCESS ID, which is used to ensure that all UEs connect in a time window, but not only with equal probability but in a way which deterministically ensures that an equal number of UEs connect per time unit during this connection time window.
  • the ACCESS ID may e.g., be a simple ordering, so that UEs with ACCESS_ID#1 connect first, followed by UEs with ACCESS_ID#2 etc. up to the UEs with the highest ACCESS_ID, which are the last to connect. Additionally, this ACCESS ID can be created by mapping the UE ID which is unique for each of the UEs within the group.
  • a wireless device and/or a particular group of wireless devices which may include UEs, in a particular embodiment, listen and/or receive broadcast (BC) or multicast (MC) messages while remaining in IDLE or INACTIVE mode.
  • the wireless devices may not have an uplink established with the network node, and the wireless devices may only be able to monitor BC/MC transmissions which are included in the Broadcast Occasion (BO) defined by paging-like messages.
  • the BO could also be referred to as a broadcast opportunity.
  • the paging-like messages may include any kind of messages intended for a specific group and may not have any specific properties other than that the paging-like messages indicate the BO.
  • a paging message is used to “wake-up” the UE, for example, to transition from idle/inactive to connected mode
  • these paging-like messages have a similar structure to paging messages but are not intended to “wake-up” the UEs. Rather, the paging-like messages are intended to indicate the BO to a specific group of inactive/idle UE(s).
  • the BO is sent in a paging-like message (or something similar) or in system information because the UE does not listen to anything else in the IDLE/INACTIVE mode.
  • the wireless devices normally have no uplink channel activated/enabled when in idle/inactive mode, there is no possibility to signal whether transmitted information (such as a signal or message transmitted by a network node) was successfully or unsuccessfully received, e.g., ACK/NACK, using the HARQ feedback. Nevertheless, the network node may decide to send retransmissions in a (pre)determined way. The reason for this is to increase the time diversity, i.e., the same amount of physical resource blocks (PRBs) would be transmitted as without HARQ but distributed in time over several occasions. In some reception conditions, this may result in a very significant improvement in reception performance, although at the expense of increased latency. It will be appreciated that retransmission may for example be performed for all data transport blocks that are transmitted in the BOs.
  • PRBs physical resource blocks
  • a common time alignment for reception i.e., common IIRM DRX cycle for INACTIVE/IDLE UEs, based on Group ID for reception/listening of potential messages for the UEs in the group is defined so they all check for Broadcast Occasions (BO) contained in the system information, e.g., paging-like messages, sent by the network at the same time.
  • BO Broadcast Occasions
  • the BO is controlled/signaled via system information. All the users in the group may have the same BO.
  • the BO is received in the system information, and there it will be scrambled with an RNTI (which may for example be referred to as GP-RNTI) that is associated with (or based on) the Group ID.
  • RNTI which may for example be referred to as GP-RNTI
  • the system information block containing the BO information element is not scrambled with the GP-RNTI but the information element additionally contains the Group ID.
  • the group wireless devices monitor the BO that they receive using System Information sent by the network node, which may include a gNB, in a particular embodiment.
  • the network informs the wireless devices using a message, e.g., paging-like messages, which is scrambled using the GP-RNTI.
  • a message e.g., paging-like messages
  • the target UEs there are two potential outcomes after being decoded by the target UEs: 1.
  • the message is scrambled using GP-RNTI and it is intended to be a group paging, i.e., the UE will transition into RRC CONNECTED mode.
  • the message contains the Group ID, which determines the PO (Paging Occasions) and PF (Paging Frame) so the UE can monitor and decode them.
  • the message is scrambled using GP-RNTI and its goal is to transition the receiving UEs into IIRM.
  • a field within the message signals that the UEs should move into IIRM and it includes the BO or it indicates that the BO are transmitted in the system information, in either case so the UE or the group of UEs can monitor it.
  • every UE that transitions into IDLE or INACTIVE mode may be (pre-)configured to go into IIRM by default within these areas.
  • the triggering of the IIRM by the network for a particular UE can be based on downlink HARQ, i.e., a (pre-)defined number of ACK/NACK is not received by the gNB or based on an Radio Link Management (RLM) notification.
  • RLM Radio Link Management
  • a motivation for doing so can be that in the case where the uplink from the UE to the gNB is anyways so bad that ACK/NACK message do not get through, it may not make sense for the UE to stay in RRC -connected, so it may transition to IIRM.
  • a triggering for UEs to move into IIRM is signaled by the network in unicast manner when the UE is in RRC CONNECTED mode.
  • This transition into IIRM is signaled using RRC messages or other network messages. Since the gNB has knowledge of the UEs in the cell, i.e., UEs which are under its coverage, it is possible to signal only a subset of the UEs so they transition to the IIRM mode.
  • the network may decide that a subset of UEs do not move into IIRM, i.e., they do not receive information in RRC IDLE/INACTIVE mode, by signaling these particular UEs.
  • a UE may potentially listen to several different DRX patterns signalled in SIB, i.e., a UE can belong to different groups at the same time, in parallel to the legacy cell-specific paging.
  • the UEs may be configured by the network to have two (or more) different DRX scheduling, i.e., one for the normal PO and one or more for the BO.
  • the reception in the BO does not require an additional DRX pattern, as the UE is just waking up for the BO which is fully specified by embodiments described above.
  • the new IIRM DRX scheduling can be signaled using RRC messages.
  • the scheduling can be configured to support several retransmissions of the same packet.
  • the priorities are defined based on service requirements, e.g., NSPS for critical services has the highest priority, or based on geographical location. This mechanism is required since the same UE could potentially belong to several groups at the same time.
  • the priority of the DRX scheduling may be signaled in the RRC messages.
  • the BO can be scrambled using a new IIRM-RNTI so only UEs in IIRM can decode it. If a UE goes into IDLE/INACTIVE mode, it automatically receives/selects the IIRM-RNTI so it can by default listen to IIRM BC/MC. The IIRM-RNTI can be sent once the UE joins the network for the first time so there is no need to transmit this information once the UE goes into IDLE/INACTIVE mode.
  • FIGURE 3 illustrates a wireless network, in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in FIGURE 3.
  • the wireless network of FIGURE 3 only depicts network 106, network nodes 160 and 160b, and wireless devices 110.
  • 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 4 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/multi cast 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/multi cast 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 4 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., aNodeB component and aRNC component, or aBTS component and aBSC 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 190 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 omni-directional 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 4 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 maher 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 5 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 (V oIP) 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.
  • V oIP voice over IP
  • PDA personal digital assistant
  • 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 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.
  • a wireless device as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, 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 114 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 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 6 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 4, 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 6 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 6, 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 presence-sensitive 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 non-volatile 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
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 221 may allow UE 200 to access computer-executable 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 7 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
  • NFV network function virtualization
  • 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 8 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 8 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. For example, 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 9 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 9) 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 9) 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 non-human 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 9 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 8, respectively.
  • the inner workings of these entities may be as shown in FIGURE 9 and independently, the surrounding network topology may be that of FIGURE 8.
  • 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 10 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 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 10 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 11 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 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 11 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 12 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 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 12 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 13 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 8 and 9. For simplicity of the present disclosure, only drawing references to FIGURE 13 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 14 depicts a method 1000 by a wireless device 110, according to certain embodiments.
  • the wireless device determines at least one BO for receiving at least one signal. While in an idle or inactive reception mode, the wireless device receives the at least one signal during the at least one BO, at step 1004.
  • the term signal is to be interpreted broadly.
  • a signal may comprise/carry/convey information such as one or more messages and/or one or more bits.
  • a wireless device while in the IIRM of NR MBMS, a wireless device is able to receive/listen to periodic and aperiodic traffic. In this mode, instead of transitioning into RRC CONNECTED mode, which happens in the current NR and legacy systems, the signaled UEs remain in RRC IDLE/INACTIVE mode and are able to receive the transmission.
  • the at least one signal comprises at least one periodic signal. In a particular embodiment, the at least one signal comprises at least one aperiodic signal.
  • the wireless device detects an occurrence of a trigger event and, in response to detecting the occurrence of the trigger event, transitions into the idle or inactive reception mode.
  • the trigger event comprises a signal received from a network node.
  • the trigger event comprising the signal received from the network node is a RRC message.
  • the trigger event comprises occurrence/absence of ACK/NACK.
  • the wireless device obtains information associating the wireless device with at least one group of wireless devices.
  • the obtaining comprises receiving the information from a network node; or obtaining information stored in the wireless device; or determining the information.
  • the information comprises at least one group identifier.
  • the at least one BO is determined based on the information associating the wireless device with the at least one group of wireless devices.
  • the at least one BO is the same for all wireless devices in the at least one group of wireless devices.
  • the at least one BO is determined in response to a paging like message transmitted to the at least one group of wireless devices.
  • the wireless device is associated with a plurality of groups of wireless devices. Each of the groups of devices being associated with a respective DRX pattern. For each group of the plurality of groups, the wireless device monitors for the respective DRX pattern (or the wireless device monitors in accordance with the respective DRX pattern) associated with that group. In a further particular embodiment, each of the DRX patterns is assigned a priority.
  • the wireless device receives system information from a network node and determining the at least one BO based on the system information.
  • the wireless device transitions into the idle or inactive reception mode based on the system information. In a particular embodiment, the wireless device determines that the wireless device is within a geographical area and transitions into the idle or inactive reception mode in response to determining that the wireless device is within the geographical area.
  • the wireless device determines that the network node has not received more than a threshold number of HARQ messages and transitioning from a connected mode into the idle or inactive reception mode in response to determining that the network node has not received more than the threshold number of HARQ messages.
  • the wireless device receives a radio resource control message and transitions into the idle or inactive reception mode in response to receiving the radio resource control message.
  • the network node is a base station.
  • At least one of the wireless devices in the group of wireless devices is a user equipment.
  • FIGURE 15 illustrates a schematic block diagram of a virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 3).
  • Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 14 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 14 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 determining module 1110, receiving module 1120, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.
  • determining module 1110 may perform certain of the determining functions of the apparatus 1100. For example, determining module 1110 may determines at least one broadcast occasion (BO) for receiving at least one signal.
  • BO broadcast occasion
  • receiving module 1120 may perform certain of the receiving functions of the apparatus 1100. For example, receiving module 1120 may receive the at least one signal during the at least one BO while in an idle or inactive reception mode.
  • the term 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 16 depicts another method 1200 by a wireless device 110, according to certain embodiments.
  • Method 1200 is similar to method 1000 and may include similar steps and features and may be considered a more particular embodiment of method 1000.
  • the method begins at step 1202 when the wireless device 110 receives, from a network node 160, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices. Based on the system information, the wireless device 110 determines at least one BO for receiving at least one signal, at step 1204. At step 1206, while in the IIRM, the wireless device 110 receives the at least one signal during the at least one BO.
  • the system information is scrambled with a RNTI specific for a group of wireless devices, and the wireless device 110 obtains association information associating the wireless device 110 with the group of wireless devices.
  • obtaining the association information may include receiving the association information from a network node 160 or obtaining the association information stored in the wireless device 110 or determining the association information.
  • the association information comprises at least one group identifier.
  • the at least one BO is determined based on the association information associating the wireless device 110 with the group of wireless devices. In a particular embodiment, determining the at least one BO may include descrambling the system information using the association information associating the wireless device 110 with the group of wireless devices and determining the at least one BO based on the descrambled system information.
  • the system information is scrambled with a RNTI specific for the IIRM
  • determining the at least one BO may include descrambling the system information using the RNTI specific for the IIRM and determining the at least one BO based on the descrambled system information.
  • the at least one BO is the same for all wireless devices in the group of wireless devices.
  • the system information is a message transmitted to the group of wireless devices, and the at least one BO is determined based on the message.
  • the message may be a paging-like message.
  • the wireless device 110 is associated with a plurality of groups of wireless devices, and each of the groups of wireless devices is associated with a respective DRX pattern. For each group of the plurality of groups, the wireless device 110 may monitor the respective DRX pattern associated with that group. In a further particular embodiment, each DRX pattern is assigned a priority.
  • the wireless device 110 detects an occurrence of a trigger event and, in response to detecting the occurrence of the trigger event, transitions into the IIRM.
  • detecting the occurrence of the trigger event may include at least one of: determining that the wireless device is within a geographical area; determining that the network node has not received more than a threshold number of HARQ messages in a certain time period; receiving a signal from the network node; receiving the system information from the network node; receiving a RRC message from the network node; detecting an occurrence of an ACK from the network node; detecting an absence of the ACK from the network node; detecting an occurrence of a NACK from the network node; and/or detecting an absence of the NACK from the network node.
  • the wireless device may be in connected mode when detecting the occurrence of the trigger event. In another particular embodiment, the wireless device may be in an idle or inactive mode when detecting the occurrence of the trigger event. In a particular embodiment, the at least one signal includes at least one periodic signal or at least one aperiodic signal.
  • the wireless device 110 receives, from the network node 160, the RNTI specific for the IIRM or the group of wireless devices.
  • FIGURE 17 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 3).
  • Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 16 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 16 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 first receiving module 1310, determining module 1320, second receiving module 1330, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • first receiving module 1310 may perform certain of the receiving functions of the apparatus 1300. For example, first receiving module 1310 may receive, from a network node 160, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices.
  • determining module 1320 may perform certain of the determining functions of the apparatus 1300. For example, based on the system information, determining 1320 may determine at least one BO for receiving at least one signal.
  • second receiving module 1330 may perform certain of the receiving functions of the apparatus 1300. For example, while in the IIRM, the second receiving module 1330 may receive the at least one signal during the at least one BO.
  • FIGURE 18 depicts a method 1400 by a network node 160, according to certain embodiments.
  • the network node determines at least one broadcast occasion (BO) for transmitting at least one signal. While a wireless device is in the idle or inactive reception mode, the network node transmits the at least one signal to the wireless device during the at least one BO, at step 1404.
  • BO broadcast occasion
  • a wireless device while in the idle or inactive reception mode (IIRM) of NR MBMS, a wireless device is able to receive/listen to periodic and aperiodic traffic.
  • IIRM idle or inactive reception mode
  • the signaled UEs instead of transitioning into RRC CONNECTED mode, which happens in the current NR and legacy systems, the signaled UEs remain in RRC IDLE/INACTIVE mode and are able to receive the transmission.
  • the at least one signal comprises at least one periodic signal.
  • the at least one signal comprises at least one aperiodic signal.
  • the network node transmits another signal to the wireless device to trigger the wireless device to transition into the idle or inactive reception mode.
  • the other signal transmitted to the wireless device to trigger the wireless device to transition into the idle or inactive reception mode comprises a radio resource control (RRC) message.
  • the trigger comprises occurrence/ absence ofACK/NACK
  • the network node obtains information associating the wireless device with at least one group of wireless devices.
  • the obtaining comprises receiving the information from a network node; or obtaining information stored in the wireless device; or determining the information.
  • the information comprises at least one group identifier.
  • the at least one BO is determined based on the information associating the wireless device with the at least one group of wireless devices.
  • the at least one BO is the same for all wireless devices in the at least one group of wireless devices. In a particular embodiment, the at least one BO is determined in response to a paging like message transmitted to the at least one group of wireless devices.
  • the wireless device is associated with a plurality of groups of wireless devices each of the groups of devices is associated with a respective DRX pattern. In a particular embodiment, each of the DRX patterns is assigned a priority.
  • the network node transmits system information to the wireless device, wherein the at least one BO is determined based on the system information.
  • the network node configures the wireless device to transition into the idle or inactive reception mode based on the system information.
  • the network node configures the wireless device to transition into the idle or inactive reception mode in response to determining that the wireless device is within the geographical area.
  • the network node configures the wireless device to transition into the idle or inactive reception mode in response to receiving a radio resource control message, and the network node transmits the radio resource control message.
  • the network node is a base station.
  • At least one of the wireless devices in the group of wireless devices is a user equipment.
  • FIGURE 19 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 3).
  • Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 18 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 18 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 determining module 1510, transmitting module 1520, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
  • determining module 1510 may perform certain of the determining functions of the apparatus 1500. For example, determining module 1510 may determine at least one broadcast occasion (BO) for transmitting at least one signal.
  • BO broadcast occasion
  • transmitting module 1520 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1520 may transmit, while a wireless device is in the idle or inactive reception mode, the at least one signal to the wireless device during the at least one BO.
  • FIGURE 20 depicts another method 1600 by a network node 160, according to certain embodiments.
  • Method 1600 is similar to method 1400 and may include similar steps and features.
  • Method 1600 may be considered a more particular embodiment of method 1400.
  • the method begins at step 1602 when the network node 160 determines at least one BO for transmitting at least one signal.
  • the network node 160 transmits, to a wireless device 110, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices.
  • the system information indicates the at least one BO.
  • the network node 160 transmits the at least one signal to the wireless device 110 during the at least one BO, at step 1606.
  • the system information is scrambled with a RNTI specific for a group of wireless devices, and the network node 160 obtains association information associating the wireless device 110 with the group of wireless devices.
  • obtaining the association information may include receiving the association information from a wireless device or obtaining the association information stored in the network node or determining the association information.
  • the network node 160 may transmit, to the wireless device 110, the association information associating the wireless device 110 with the group of wireless devices.
  • the association information comprises at least one group identifier.
  • the at least one BO is determined based on the association information associating the wireless device with the group of wireless devices.
  • the at least one BO is the same for all wireless devices in the group of wireless devices.
  • the wireless device is associated with a plurality of groups of wireless devices, and each of the groups of wireless devices is associated with a respective DRX pattern.
  • each DRX pattern is assigned a priority.
  • the network node 160 configures the wireless device 110 to detect an occurrence of an event and transition into the IIRM based on detecting the occurrence of the event.
  • configuring the wireless device 110 to detect the occurrence of the event may include configuring the wireless device to perform at least one of: detecting that the wireless device 110 has received the system information; determining that the wireless device 110 is within a geographical area; detecting that the network node 160 has not received more than a threshold number of HARQ messages in a certain time period; detecting that the wireless device 110 has received a signal from the network node 160; detecting that the wireless device 110 has received a RRC message from the network node 160; detecting that the wireless device 110 has received an ACK from the network node 160; detecting that the wireless device 110 has not received an ACK from the network node 160; detecting that the wireless device 110 has received aNACK from the network node 160; and/or detecting that the wireless device 110 has not received a NACK from the network node 160.
  • the at least one signal comprises at least one periodic signal or at least one aperiodic signal.
  • the network node 160 transmits, to the wireless device 110, the RNTI specific for the IIRM or the group of wireless devices.
  • FIGURE 21 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 3).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 3).
  • Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 20 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 20 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1700 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 transmitting module 1720, determining module 1710, second transmitting module 1730, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
  • determining module 1710 may perform certain of the determining functions of the apparatus 1700. For example, determining module 1710 may determine at least one BO for transmitting at least one signal.
  • first transmitting module 1720 may perform certain of the transmitting functions of the apparatus 1700. For example, first transmitting module 1720 may transmit, to a wireless device 110, system information that is scrambled with a RNTI specific for an IIRM or specific for a group of wireless devices. The system information indicates the at least one BO.
  • second transmitting module 1730 may perform certain other of the transmitting functions of the apparatus 1700. For example, while the wireless device is in the IIRM, second transmitting module 1730 may transmit the at least one signal to the wireless device 110 during the at least one BO.
  • Example Embodiment 1 A wireless device comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is operative to perform any of the steps of any of Claims 1 to 18.
  • Example Embodiment 2. A wireless device, the wireless device comprising: processing circuitry configured to perform any of the steps of any of Claims 1 to 18; and power supply circuitry configured to supply power to the wireless device.
  • Example Embodiment 3 A network node configured to perform any of the steps of any of Claims 19 to 32.
  • Example Embodiment 4 A network node comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the network node is operative to perform any of the steps of any of Claims 19 to 32.
  • Example Embodiment 5 A network node comprising processing circuitry and a memory, the memory storing instructions that when executed by the processing circuitry causes the network node to perform any of the steps of any of Claims 19 to 32.
  • Example Embodiment 6 A network node comprising: processing circuitry configured to perform any of the steps of any of Claims 19 to 32; power supply circuitry configured to supply power to the network node.
  • Example Embodiment 7 A user equipment (UE) for improving network efficiency, the UE 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 Claims 1 to 18; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • Example Embodiment 8 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 user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Claims 19 to 32.
  • UE user equipment
  • Example Embodiment 9 The communication system of the previous example embodiment further including the base station.
  • Example Embodiment 10 The communication system of the previous 2 example embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 11 The communication system of the previous 3 example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • Example Embodiment 12 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of Claims 19 to 32.
  • UE user equipment
  • Example Embodiment 13 The method of the previous example embodiment, further comprising, at the base station, transmitting the user data.
  • Example Embodiment 14 The method of the previous 2 example embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
  • Example Embodiment 15 A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 example embodiments.
  • UE user equipment
  • Example Embodiment 16 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 user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of Claims 1 to 18.
  • UE user equipment
  • Example Embodiment 17 The communication system of the previous example embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Example Embodiment 18 The communication system of the previous 2 example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • Example Embodiment 19 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of Claims 1 to 18.
  • UE user equipment
  • Example Embodiment 20 The method of the previous example embodiment, further comprising at the UE, receiving the user data from the base station.
  • Example Embodiment 21 A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of Claims 22.
  • UE user equipment
  • Example Embodiment 23 The communication system of the previous example embodiment, further including the UE.
  • Example Embodiment 24 The communication system of the previous 2 example embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • Example Embodiment 25 The communication system of the previous 3 example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • Example Embodiment 26 The communication system of the previous 4 example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’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 Embodiment 27 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of Claims 1 to 18.
  • UE user equipment
  • Example Embodiment 28 The method of the previous example embodiment, further comprising, at the UE, providing the user data to the base station.
  • Example Embodiment 29 The method of the previous 2 example embodiments, further comprising: at the UE, 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 Embodiment 30 The method of the previous 3 example embodiments, further comprising: at the UE, executing a client application; and at the UE, 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 Embodiment 31 A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Claims 19 to 32.
  • UE user equipment
  • Example Embodiment 32 The communication system of the previous example embodiment further including the base station.
  • Example Embodiment 33 The communication system of the previous 2 example embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 34 The communication system of the previous 3 example embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE 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 Embodiment 35 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of Claims 1 to 18.
  • Example Embodiment 36 The method of the previous example embodiment, further comprising at the base station, receiving the user data from the UE.
  • Example Embodiment 37 The method of the previous 2 example embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Landscapes

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

Abstract

Un procédé (1200) par un dispositif sans fil (110) comprend la réception (1202), en provenance d'un nœud de réseau (160), d'informations système qui sont embrouillées avec un identifiant temporaire de réseau radio, RNTI, spécifique pour un mode de réception au repos ou inactif, IIRM, ou spécifique pour un groupe de dispositifs sans fil. Sur la base des informations système, le dispositif sans fil détermine (1204) au moins une opportunité de diffusion, BO, pour la réception d'au moins un signal. Pendant qu'il est dans l'IIRM, le dispositif sans fil reçoit (1206) le ou les signaux pendant la ou les BO.
PCT/SE2020/051180 2019-12-11 2020-12-09 Opportunité de diffusion pour la réception d'un signal WO2021118438A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962946658P 2019-12-11 2019-12-11
US62/946,658 2019-12-11

Publications (1)

Publication Number Publication Date
WO2021118438A1 true WO2021118438A1 (fr) 2021-06-17

Family

ID=73835684

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/051180 WO2021118438A1 (fr) 2019-12-11 2020-12-09 Opportunité de diffusion pour la réception d'un signal

Country Status (1)

Country Link
WO (1) WO2021118438A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023128618A1 (fr) * 2021-12-29 2023-07-06 Lg Electronics Inc. Procédé et appareil de gestion de connexion sur la base d'un type de multidiffusion dans un système de communication sans fil

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008155739A2 (fr) * 2007-06-19 2008-12-24 Nokia Corporation Appareil, procédé et produit de programme d'ordinateur permettant une réception discontinue en mode veille
GB2568513A (en) * 2017-11-17 2019-05-22 Tcl Communication Ltd Paging systems
US20190297577A1 (en) * 2018-03-23 2019-09-26 Samsung Electronics Co., Ltd. Method and apparatus for power saving signal design in nr

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008155739A2 (fr) * 2007-06-19 2008-12-24 Nokia Corporation Appareil, procédé et produit de programme d'ordinateur permettant une réception discontinue en mode veille
GB2568513A (en) * 2017-11-17 2019-05-22 Tcl Communication Ltd Paging systems
US20190297577A1 (en) * 2018-03-23 2019-09-26 Samsung Electronics Co., Ltd. Method and apparatus for power saving signal design in nr

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.246 V16.1
3GPP TS 23.246 VL6.1

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023128618A1 (fr) * 2021-12-29 2023-07-06 Lg Electronics Inc. Procédé et appareil de gestion de connexion sur la base d'un type de multidiffusion dans un système de communication sans fil

Similar Documents

Publication Publication Date Title
US20230239661A1 (en) Multicast and broadcast services for user equipments in idle and inactive states
EP3857971B1 (fr) Support pour transmission dans des ressources de liaison montante préconfigurées
US11546934B2 (en) Scheduling a single cell multicast traffic channel via a single cell multicast control channel
US11917695B2 (en) Early mobile-terminated data transmission
US20210250739A1 (en) Methods, Apparatus, and Computer-Readable Media for Discovery of Application Server and/or Services for V2X Communications
CN111919499B (zh) 在5g网络中连接建立期间管理具有扩展长度的临时订户标识符
WO2020144024A1 (fr) Adaptation de liaison pour une diffusion de groupe sur liaison latérale
US11589201B2 (en) Network node, user equipment (UE) and methods for handling communication in a narrowband internet of things (NB-IoT) or machine type communication (MTC) network
CN115428541A (zh) 用于减少虚假寻呼的无线装置分组机制和网络配置
US20230077297A1 (en) Method and Apparatus for Privacy Protection
EP3874849B1 (fr) Signalisation de réveil dans un système de communication sans fil
WO2021118438A1 (fr) Opportunité de diffusion pour la réception d'un signal
US12114362B2 (en) Mobile terminated access load control
WO2021118439A1 (fr) Recherche de groupe pour un système new radio
EP4140194A1 (fr) Procédure à la demande pour demander une référence temporelle de 5g
US20220022165A1 (en) Method for communication system with group service
US20240080801A1 (en) Mapping of paging early indicator to multiple paging occasions
US20240235785A1 (en) Beam related tracking reference signal availability signaling
US20240267986A1 (en) Method and Apparatus for Sidelink Discontinuous Reception
US20240244529A1 (en) Method and Apparatus for Controlling the Use of Paging Early Indication or Wake-Up Signals
EP4338541A1 (fr) Envoi d'informations de bloc d'informations de système avant l'établissement d'une commande de ressources radio pc5

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: 20824708

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: 20824708

Country of ref document: EP

Kind code of ref document: A1