WO2019147538A1 - Gestion de puissance de dispositif à commande électronique - Google Patents

Gestion de puissance de dispositif à commande électronique Download PDF

Info

Publication number
WO2019147538A1
WO2019147538A1 PCT/US2019/014467 US2019014467W WO2019147538A1 WO 2019147538 A1 WO2019147538 A1 WO 2019147538A1 US 2019014467 W US2019014467 W US 2019014467W WO 2019147538 A1 WO2019147538 A1 WO 2019147538A1
Authority
WO
WIPO (PCT)
Prior art keywords
power management
electronically controlled
controlled device
system information
parameter
Prior art date
Application number
PCT/US2019/014467
Other languages
English (en)
Inventor
Kenneth James PARK
Original Assignee
Sharp Laboratories Of America, Inc.
FG Innovation Company Limited
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 Sharp Laboratories Of America, Inc., FG Innovation Company Limited filed Critical Sharp Laboratories Of America, Inc.
Publication of WO2019147538A1 publication Critical patent/WO2019147538A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/0277—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof according to available power supply, e.g. switching off when a low battery condition is detected
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the technology relates to electronically controlled devices, and particularly to methods and apparatus for power management of electronically controlled devices.
  • a radio access network generally comprises one or more access nodes (such as a base station) which communicate on radio channels over a radio or air interface with plural wireless terminals.
  • access nodes such as a base station
  • UE User Equipment
  • 3GPP 3GPP Long Term Evolution
  • LTE-A 3GPP LTE Advanced
  • UMTS Universal Mobile Telecommunications System
  • SI system information
  • Each access node such as an evolved NodeB (“eNB”)
  • eNB evolved NodeB
  • SIBs System Information Blocks
  • a wireless terminal (“UE”) after entering a coverage area of an eNB, is required to obtain all the SIBs which are necessary to access to the system.
  • the eNB periodically broadcasts all SIBs relevant for offered services, not just SIBs that are required for access to the system.
  • Each type of SIBs is transmitted in a designated radio resource(s) with its own pre-determined/configurable frequency.
  • Public Warning System requirements are described, e.g., in 3GPP TR 22.869.
  • the requirements for Public Warning System specified in 3GPP Release 8 onwards provide a text-based and language-dependent PWS Message to mobile users who have conventional mobile devices (e.g., it is assumed the user’s device can display a text-based messages and has some form of a user interface for interaction with the message.
  • Enhancements to TR 22.869 may consider cases that describe scenarios where user equipments (UEs) with no user interface (e.g., are not intended for human type communication) are connected to a 3GPP network and receive a PWS Message when a disaster occurs. Such UEs may take pre-defmed actions (e.g., shutting down an escalator when an earthquake occurs to prevent harm to users and damage to the device) to minimize damages caused by disasters and to protect humans.
  • UEs user equipments
  • Such UEs may take pre-defmed actions (e.g., shutting down an escalator when an earthquake occurs to prevent harm to users and damage to the device) to minimize damages caused by disasters and to protect humans.
  • the action triggered by the PWS Message causes the device to turn off, or to minimize power its consumption, or to stop the physical aspects controlled by the devices, that action will occur in a near simultaneous manner across the devices receiving the PWS Message, and the resulting load to the electrical distribution system will be minimized in a near simultaneous manner (e.g., the change in load to the electrical system is nearly synchronized with the LTE system broadcast).
  • the action triggered by the termination of the PWS Message may cause the device to turned on, or to maximize its power consumption, or to resume the physical aspects controlled by the device, and that action will also occur in a near simultaneous manner across the devices, and the resulting load spike to the electrical distribution system will also occur in a near simultaneous manner (e.g., the change in load on the electrical distribution system is again nearly synchronized with the LTE system broadcast).
  • Such a spike in electrical demand may cause significant harm to an electrical distribution system that may already be under stress due to the original emergency situation.
  • the technology disclosed herein concerns an electronically controlled device.
  • the electronically controlled device comprises receiver circuitry and processor circuitry.
  • the receiver circuitry is configured to obtain broadcast system information from a base station node over a radio interface.
  • the processor circuitry configured to use the broadcast system information to control a power management function of the electronically controlled device.
  • the processor circuitry is configured to determine a wait period before performing the power management function.
  • the technology disclosed herein concerns a method for operating an electronically controlled device. In a basic mode the method comprises using receiver circuitry to obtain broadcast system information from a base station node over a radio interface; and processor circuitry using the broadcast system information to control a power management function of the electronically controlled device.
  • the technology disclosed herein concerns a server which communicates with an electronically controlled device.
  • the server comprises processor circuitry and a communications interface.
  • the processor circuitry is configured to generate a parameter paring selection criteria signal.
  • the parameter paring selection criteria signal comprises an indication of which of plural possible parameter parings are to be utilized by an electronically controlled device in conjunction with a power management function performed by the electronically controlled device.
  • Each of the plural possible parameter parings comprising a wait factor as a first parameter of the pair and a wait time as a second parameter of the pair.
  • the communications interface is configured to transmit the parameter paring selection criteria signal to the electronically controlled device.
  • Fig. 1 is a schematic view showing an example embodiment of an electronically controlled device, such as an internet of things device, in the example non-limiting context of a system comprising a plurality of premises of other electronically controlled devices.
  • Fig. 2A - Fig. 2G are diagrammatic views of Si-based power management controllers of differing example embodiments and modes of electronically controlled devices and basic acts performed thereby.
  • Fig. 3 A - Fig. 3E are diagrammatic views of power level utilization as a function of operation of the Si-based power management controllers of the respective embodiments and modes of Fig. 2A - Fig. 2E.
  • Fig. 4 is a diagrammatic view showing example electronic machinery which may comprise server electronic machinery or electronically controlled device electronic machinery.
  • FIG. 5 is a diagrammatic view showing figures which illustrate data flows and computer program routines associated with execution of an electronically controlled device of a consolidated example embodiment and mode in which various features of the example embodiments and modes of Fig. 2A - Fig. 2G may be optionally and selectively implemented, either alone or in various differing combinations.
  • FIG. 6 and Fig. 7 are diagrammatic views showing a respective first data flow and second data flow for the consolidated example embodiment and mode of Fig. 5
  • Fig. 8 is a flowchart showing basic, representative acts or steps comprising a routine executed by an application programmable interface of the Si-based power management controller of the example embodiment and mode of Fig. 5.
  • Fig. 8-1 through Fig. 8-4 including Fig. 8-2A and Fig. 8-2B and Fig. 8-4A and Fig. 8-4B, are flowcharts showing basic, representative acts or steps comprising respective subroutines invoked by the application programmable interface of Fig. 8.
  • Fig. 9 shows basic introductory acts comprising a process logic routine executed by a Si-based power management controller of the consolidated example embodiment and mode of Fig. 5.
  • Fig. 9-1 through Fig. 9-4, including Fig. 9-2A and Fig. 9-2B, are flowcharts showing basic, representative acts or steps comprising respective subroutines invoked by the process logic routine of Fig. 9.
  • Fig. 10 together with Fig. 10A and Fig. 10B, show basic substantive acts comprising a process logic routine executed by a Si-based power management controller of the consolidated example embodiment and mode of Fig. 5.
  • Fig. 10-1 through Fig. 10-4 including Fig. 10-3 A and Fig. 10-3B, are flowcharts showing basic, representative acts or steps comprising respective subroutines invoked by the process logic routine of Fig. 10.
  • the term“core network” can refer to a device, group of devices, or sub-system in a telecommunication network that provides services to users of the telecommunications network. Examples of services provided by a core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc.
  • the term“wireless terminal” can refer to any electronic device used to communicate voice and/or data via a telecommunications system, such as (but not limited to) a cellular network.
  • wireless terminals can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants (“PDAs”), laptop computers, netbooks, e-readers, wireless modems, etc.
  • PDAs personal digital assistants
  • the term“access node”,“node”, or“base station” can refer to any device or group of devices that facilitates wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system.
  • a non-limiting example of a base station can include, in the 3GPP specification, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB or some other similar terminology.
  • NB Node B
  • eNB enhanced Node B
  • HeNB home eNB
  • gNB giga Node B
  • Another non-limiting example of a base station is an access point.
  • An access point may be an electronic device that provides access for wireless terminal to a data network, such as (but not limited to) a Local Area Network (“LAN”), Wide Area Network (“WAN”), the Internet, etc.
  • LAN Local Area Network
  • WAN Wide Area Network
  • the Internet etc.
  • the term“telecommunication system” or“communications system” can refer to any network of devices used to transmit information.
  • a non-limiting example of a telecommunication system is a cellular network or other wireless communication system.
  • the term“cellular network” can refer to a network distributed over cells, each cell served by at least one fixed-location transceiver, such as a base station.
  • a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (“IMTAdvanced”).
  • All or a subset of the cell may be adopted by 3GPP as licensed bands (e.g., frequency band) to be used for communication between a base station, such as a Node B, and a UE terminal.
  • a cellular network using licensed frequency bands can include configured cells.
  • Configured cells can include cells of which a UE terminal is aware and in which it is allowed by a base station to transmit or receive information.
  • Fig. 1 shows an electronically controlled device 20 which obtains electrical power for its operation, at least in part, from an electrical power grid 22.
  • the device 20 performs one or more device-native operations, e.g., operations for which the device 20 is configured to provide a function or service.
  • the device-native operation(s) may depend upon the nature or purpose of the location/premise 24 in which the device 20 is employed or connected.
  • the device 20 may be a household device such as a refrigerator which performs a refrigeration operation; an air conditioning or heating device which performs a cooling, heating, and/or air handling operation(s) for a home; a remote or central vacuum system which performs a home cleaning operation; or other home appliance or system.
  • the device 20 may be a tool or piece of equipment or a robot that is located in a shop or factory.
  • an electronically controlled device 20 is an internet of things (IoT) device.
  • An internet of things device is an electronically controlled device 20 that is addressable using an internet address and/or communicates using internet protocol.
  • IoT internet of things
  • the devices 20 of Fig. 1 and herein are generally referenced as internet of things devices 20. But it should be understood that the devices 20 are not confined to those having internet compatibility.
  • “electrical power grid”,“grid”, or“electrical power” encompasses any suitable network form of electrical power supply, such as a public electrical power grid (e.g., the conventional public service that provides 120 volts alternating current (AC) to, e.g., businesses and residences, as well as private power grids or private power networks.
  • a provide power grid may, for example, supply electrical power (e.g., direct current (DC) power) to a particular premise(s) or factory(ies).
  • Fig. 1 illustrates that plural devices 20 may be situated at any given location or premise 24.
  • Fig.l shows that devices 20i,i, ...20i.j and 20 2,i ...20 2,k are situated at or connected to premises 24i.
  • the devices 20 at premises 241 may be grouped or organized into different classes or ranks, as indicated by the first subscripts for the respective devices 20.
  • devices 20i,i, ...20i.j may comprise a first class or rank of devices 20, while devices 20 2,I ...20 2,k may comprise a first class or rank of devices 20.
  • the criteria for grouping or dividing into classes or ranks can be various, such as sub-location within the premise 24, type of functions of the devices 20, anticipated hours or extent of operation of the devices 20, as a few examples. All of the devices 20 of the premise 24 obtain electrical power for operation, at least in part, from an electrical power grid 22.
  • “device 20” shall refer to a generic,
  • representative device 20 may be included in one or more, all, or less than all of the devices 20.
  • Reference to device 20 in conjunction with an alphabetical suffix may have reference to an embodiment figure corresponding to the suffix.
  • a premise 24 may optionally comprise one or more server(s) 26.
  • the server(s) 26 may be configured to control one or more of the devices 20, either in individual or coordinated fashion.
  • server(s) 26 may also be connected to electrical power grid 22, although the server(s) 26 preferably also have backup power.
  • the server(s) 26 may be connected to one or more of the devices 20 of the premise 24 either by hardwire or (more preferably) wireless connections.
  • Fig. 1 shows the server(s) 26 as comprising server wireless communication interface 28.
  • the protocol/technology utilized for wireless communication interface 28 may be any suitable protocol/technology, such as BluetoothTM, Wi-Fi, 3 GPP LTE, 3 GPP 5G.
  • Fig. 1 shows that the electrical power grid 22 may supply electrical power to plural premises 24, such as premise 241 (which is illustrated in more detail in Fig. 1), premise 24 2 , and premise 24N. It should be understood that the other premises may comprise one or more other device 20s, either of same or differing types, and have same or different configurations, as the premise 241 which is more conspicuously shown in Fig. 1.
  • the electrical power grid 22 may have many devices 20 of many premises 24 dependent thereon for electrical power. Under certain circumstances it may be desired or required electrical power to one or more devices 20 be shut-down (e.g., terminated), so that the one or more devices 20 are essentially disconnected from the electrical power grid 22.
  • the termination or disconnection of a device 20 from electrical power grid 22 is usually only temporary, and may be for reason of protection to the electrical power grid 22, protection of the device 20, and may be related to or involved with a public safety event or warning. After the termination or disconnection, the devices 20 are generally permitted to reconnect to the electrical power grid 22.
  • simultaneous electrical disconnection or reconnection to electrical power grid 22 may tax or overload the electrical power grid 22.
  • An aspect of the technology disclosed herein is a device 20 for which a power management function, such as (for example) termination of grid power utilization or resumption of power grid utilization, is controlled to mitigate grid tax or overload.
  • the device 20 uses broadcast system information obtained over a radio interface from a base station node to control the power management function of the electronically controlled device 20.
  • Fig. 1 further shows that the representative device 20 (e.g., device 20i,i) comprises power management function 30.
  • the power management function 30 in turn comprise mechanisms for electrical connection to and/or disconnection from electrical power grid 22, and particularly to electrical distribution line(s) 32 which connect the power management function 30 to electrical power grid 22.
  • the distribution line(s) 32 may connect plural devices 20, and plural premises 24, to electrical power grid 22.
  • the device 20 further comprises a system information-based power management controller, illustrated as Si-based power management controller 34 in Fig. 1. As explained herein, the Si-based power management controller 34 uses broadcast system information to control the power
  • the device 20 further comprises device native operation controller 36.
  • the device native operation controller 36 governs the operation of the native function of device 20, whether a household function, factory or shop function, or other function.
  • the native function in turn may employ, and thus device 20 may further comprise, mechanical mechanisms such as actuators, servo motors, that are utilized to implement the native function(s).
  • One or more of such mechanism may utilize the electrical power obtained from electrical power grid 22 when the power management function 30 maintains connection of the device 20 to the electrical power grid 22.
  • the Si-based power management controller 34 and the device native operation controller 36 may comprise the same controller(s) or be dedicated controllers. When plural controllers are employed, the controllers may be distributed and/or co-operating.
  • the Si-based power management controller 34 and device native operation controller 36 are illustrated as comprising processor circuitry 38.
  • the processor circuitry 38 may comprise one or more processors.
  • Fig. 1 further shows that device 20 comprises memory 40.
  • the memory 40 comprises read-only-memory (ROM) 42 and non-volatile memory (NV-memory) 44.
  • ROM read-only-memory
  • NV-memory non-volatile memory
  • memory 40 may store, on non-transitory medium, one or more computer programs in the form of coded instructions.
  • the memory 40 and the program(s) are configured to, working with the at least one processor 38, to cause the device 20 to perform, e.g., the control of the native device operations and, as described herein, control of the power management function 30 as by Si-based power management controller 34.
  • One such computer program described herein for a non-limiting example embodiment and mode is a Power Management Life Cycle System program.
  • Fig. 1 further shows that representative device 20 also comprises device communication interface(s) 50.
  • the device communication interface(s) 50 comprises radio network interface 52 and server interface 54.
  • the radio network interface 52 comprises at least a receiver for receiving, over a wireless or radio interface 56, communications from a radio access network node 60.
  • the communications may be, for example, Long Term Evolution (LTE) communications.
  • radio network interface 52 may comprise merely a receiver, but other example embodiment and modes the radio network interface 52 may comprise a transceiver with transmitting capabilities.
  • the radio network interface 52 obtains system information broadcast over radio interface 56 from the radio access network node 60.
  • the server interface 54 is configured to communicate with the wireless communication interface 28 of server(s) 26.
  • the radio network interface 52 and server interface 54 may be combined in or consolidated in a same interface(s), and may share circuitry such as e.g., amplifier(s), modulation circuitry, demodulation circuitry, and other conventional receiver/transmission equipment, and antennas. Alternatively, each radio network interface 52 and server interface 54 may have dedicated such circuitry.
  • the device 20 may include, but is not required to include, an unillustrated user interface for interaction with a user.
  • an unillustrated user interface for interaction with a user.
  • such device user interface may serve for both user input and output operations, and may comprise (for example) a screen such as a touch screen that can both display information to the user and receive information entered by the user.
  • the user interface may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.
  • the device 20 does not have such user interface, but instead is otherwise controlled, if at all, by external equipment such as server(s) 26.
  • the radio access network node 60 may be any suitable type of radio access network node, such as a base station (which may be, for example, an eNodeB (eNB) or gNB (for the New Radio System Technology), or an access point such as for WiFi and similar technologies.
  • a base station which may be, for example, an eNodeB (eNB) or gNB (for the New Radio System Technology), or an access point such as for WiFi and similar technologies.
  • radio access network node 60 comprises a system information controller or system information (SI) generator 62 and transmitter 64.
  • SI system information generator 62
  • transmitter 64 The nature of the system information generated by system information (SI) generator 62, for use by the device 20 for control of the power management function 30, for some non-limiting example embodiment and modes is further described herein.
  • the radio access network node 60 may communicate with devices 20 at plural premises 24.
  • the Si-based power management controller 34 of each example embodiment and mode of device 20 uses broadcast system information to control a power management function of the electronically controlled device.
  • the device 20 does not rely upon or utilize any other aspect of the radio access network communications for its device native operation.
  • the device 20 does not typically function as a wireless device, such as a user equipment (UE), which requires radio communications with a radio access network for it native operation. That is, other than the broadcast system information, no other information transmitted by the radio access network is particularly necessary for the native operation of the device 20.
  • the broadcast system information which the device 20 does obtain from the radio access network is utilized for other than radio access network purposes. That is, the broadcast system information is not used for control of radio communications, but instead for determining a wait period in conjunction with a power management operation of the device 20.
  • Fig. 2A - Fig. 2G illustrate basic distinguishing aspects of differing embodiment and modes of the Si-based power management controller 34, and thus correspondingly differing embodiment and modes of devices 20A- 20E.
  • Fig. 3A - Fig. 3E correspondingly illustrate basic power management phenomena associated with the respective embodiment and modes of Fig. 2A - Fig. 2E.
  • the example embodiment and modes may be implemented separately or in combination with one or more of the other example embodiment and modes.
  • example scenarios of operation of the device 20 are described with reference to a composite example embodiment and mode of Fig. 5.
  • the example embodiment and mode of Fig. 5 is termed as“composite” since it provides an illustration of either total or optional/selective implementation of one, two, more or all of the distinguishing aspects of the differing embodiment and modes of Fig. 2A - 2G.
  • the Si-based power management controller 34 determines, from the broadcast system information, a wait period before performing the power management function.
  • a wait period encompasses and comprises, but is not limited to, determining and/or obtaining one or more parameters upon which a wait period depends, e.g., one or more parameters which are input to a function that determines the wait period.
  • the power management controller 34A of device 20A determines, from the broadcast system information, a wait period before performing termination of power grid utilization.
  • the power management function performed by power management function 30 but controlled by Si-based power management controller 34A is termination of power grid utilization.
  • Fig. 2A and Fig. 3A show as act 34A-1 the device 20 receiving a power termination command, as act 34A-2 the Si-based power management controller 34A waiting the duration of the wait period, and as act 34A-3 the Si-based power management controller 34 A sending a signal to power management function 30 to terminate power grid utilization.
  • the power management controller 34B of device 20B determines, from the broadcast system information, a wait period before performing resumption of power grid utilization.
  • the power management function performed by power management function 30 but controlled by Si-based power management controller 34B is resumption of power grid utilization.
  • the power management controller 34C of device 20C determines, from the broadcast system information, a wait period before performing device power-up, e.g., start-up of power grid utilization.
  • a wait period before performing device power-up e.g., start-up of power grid utilization.
  • the power management function performed by power management function 30 but controlled by Si-based power management controller 34C is start-up of power grid utilization.
  • Fig. 2C and Fig. 3C show as act 34C-0 the device 20C receiving a power-up command, which may be received, e.g., from a device user interface or from server(s) 26.
  • act 34C-1 the Si-based power management controller 34C checks if device 20C is experiencing a power avoidance event.
  • experiencing a“power avoidance event” comprises the Si-based power management controller 34C receiving a notification, e.g., based on broadcast system information, that the device 20C should avoid power grid utilization, including avoiding power grid utilization upon start up.
  • the power avoidance is a power-up delay event.
  • the Si-based power management controller 34C waits the duration of the wait period before issuing a signal to power management function 30 to commence actual start-up of power grid utilization (to actual power up the device 20C). If it is determined as act 34C-1 that the device 20C is not experiencing a power avoidance event, then the Si-based power management controller 34C proceeds directly without wait to commence actual start-up of power grid utilization (as 34C-3).
  • the power management controller 34D of device 20D determines, from the broadcast system information, a wait period before performing its power management function, but also determines if the device 20D is requested to be attached to the radio access network node 60 before commencing the wait period.
  • Fig. 2D and Fig. 3D show as act 34D-0 the device 20D receiving a power management command.
  • the power management command may be received either from radio access network node 60 or from server(s) 26.
  • the power management command of act 34D-0 may be, in differing scenarios, either the power termination command (see Fig. 2A), the power resumption command (see Fig.
  • the Si-based power management controller 34D checks if device 20D has been requested to post-pone implementation of the power management function corresponding to the power management command, and whatever wait period may be applicable, until the device 20D is attached to the radio access network node 60.
  • “attach” or“attachment” is understood from Figure 5.2.2-1: RRC IDLE Cell Selection and Reselection in TS 36.304, from which it is understood that“Detached” is when the UE is in“Any Cell Selection State”, and“Attached” is when the UE is not in“Any Cell Selection State”.
  • the Si-based power management controller 34D imposes the wait period before issuing a signal to power management function 30 to perform (as act 34D-3) the requested power management function. If it is determined as act 34D-1 that the device 20D is attached, or that attachment is not requested or required, the Si-based power management controller 34D proceeds directly without wait to commence implementation of the power management function (as act 34D-3).
  • the power management controller 34E of device 20E determines, from the broadcast system information, a wait period before performing its power management function, but also determines if the device 20E is requested to be connected to the server(s) 26 before commencing the wait period.
  • Fig. 2E and Fig. 3E show as act 34E-0 the device 20E receiving a power management command.
  • the power management command may be received from radio access network node 60.
  • the power management command of act 34E-0 may be, in differing scenarios, either the power termination command (see Fig. 2A), the power resumption command (see Fig.
  • the Si-based power management controller 34E checks if device 20E has been requested to post-pone implementation of the power management function corresponding to the power management command, and whatever wait period may be applicable, until the device 20E is connected to the server(s) 26.
  • “connect” or“connection”, e.g., to the server(s) 26, comprises the ability to receiving signals and/or data from the server(s) 26, either through wired or wireless channels.
  • the Si-based power management controller 34E imposes the wait period before issuing a signal to power management function 30 to perform (as act 34E-3) the requested power management function. If it is determined as act 34E-1 that the device 20E is already connected to server(s) 26, or that connection to server(s) 26 is not requested or required, the Si-based power management controller 34E proceeds directly without wait to commence implementation of the power management function (as 34E-3).
  • the power management controller 34F of device 20F determines, from broadcast system information, whether any wait period (also communicated in the broadcast system information) is applicable to the device 20F.
  • system information 70 broadcasted from radio access network node 60 comprises one or more wait parameter(s) 72 and one or more broadcast events 74.
  • the broadcast events 74 may be, for example, public safety events or warnings, such as a weather warning (tornado, tsunami, flood, earthquake, etc.), an emergency notification (missing persons alert (e.g., amber alert), police notification (e.g., terrorist alert), or an environmental notification (e.g., toxic spill or leakage).
  • Fig. 2F shows possible broadcast events BE1, BE2, ... BEn, with broadcast event BE2 being active or set.
  • the Si-based power management controller 34F of Fig. 2F is configured to obtain from the broadcast system information an indication of one or more broadcast events (BE1, BE1, ... BEn), and (as act 34F-0) to determine if any one or more such indications of broadcast events corresponds to any trigger event or configuration event (CE1, CE2, ... CEm) which is configured at the device 20F.
  • the Si-based power management controller 34F thus has access to, e.g., stored in memory 40, an indication of one or more such trigger or configuration event(s) for/to which the device 20F is affected for power grid utilization reasons.
  • the indication of one or more such trigger or configuration event(s) may take the form of a list or a bitmap, as non-limiting examples.
  • the system information 70 includes an indication of an active broadcast event BE2 (as indicated by the BE2 block of Fig. 2F being stippled), and that the device 20F is configured to be affected by the BE2 event as shown by configured event CE2 (also stippled).
  • a configured or trigger event such as event CE2 may be pre-configured at (e.g., in memory 40 or processor 34F) or may be downloaded to or updated at the Si-based power management controller 34F.
  • the broadcast event 74 of system information 70 of Fig. 2F is applicable to SI- based power management controller 34F of device 20F.
  • the device 20F receiving a power management command to perform a corresponding power management function.
  • the power management command may be received from radio access network node 60 or server(s) 26.
  • the power management command of act 34F-1 may be, in differing scenarios, either the power termination command (see Fig. 2A), the power resumption command (see Fig. 2B), or the power start-up command (see Fig. 2C), as non-limiting examples.
  • the Si-based power management controller 34F imposes the wait period before issuing a signal to power management function 30 to perform (as act 34F-3) the corresponding requested power management function.
  • the Si-based power management controller 34F may be configured to obtain the indication of one or more public safety events from either system information block 10 (SIB 10) or system information block 12 (SIB12) of the broadcast system information.
  • SIB 10 system information block 10
  • SIB12 system information block 12
  • the power management controller 34G of device 20G is configured to obtain two parameters from the broadcast system information used by the processor circuitry to determine the wait period.
  • system information 70 broadcasted from radio access network node 60 comprises one or more wait parameter(s) 72.
  • the non-limiting example depiction of Fig. 2G shows the wait parameter(s) 72 as comprising plural parings 76 of a first parameter and a second parameter, and wherein for each parameter pair 76 the first parameter is a wait factor and the second parameter is a wait time.
  • the Si-based power management controller 34G is configured to use the wait factor and the wait time of a selected one of the parameter pairings 76 as inputs for a random determination of the wait period.
  • the Si-based power management controller 34G may be configured to utilize a configured one of the plural pairings 76 to obtain the wait factor and the wait time.
  • the Si-based power management controller 34G is configured to select the two parameters from the first the parameter pairings that actually contains the two parameters wait factor and wait time.
  • the first pairing 76i is the first of the plural parameter pairings 76 to actually contain parameter values. It should be understood that in some situations not all of the parameter pairings 76 may include content, e.g., that some of the parameter pairings 76 may be empty.
  • the Si-based power management controller 34G In the situation of the Si-based power management controller 34G being configured to select the first parameter pairing 76 with actual content, should the first parameter pairing 76i be empty, the Si-based power management controller 34G would, in numerical order, select the next of the parameter pairings 762 - 765 that includes parameter.
  • the configuration of Si-based power management controller 34G may change or otherwise be configured to select another one of the parameter pairings 76 (e.g., the second one of the parameter pairings 76 that has actual content, rather than the first of the parameter pairings 76 that has actual content).
  • which of the parameter pairings e.g., first parameter paring, second parameter paring, or other parameter paring selection criteria, may be configured at the device 20 (e.g., at the Si-based power management controller).
  • Such configuration of parameter paring selection criteria, or logic for selecting a parameter paring may be pre-configured, or may be downloaded or otherwise communicated to the device 20, e.g., by or from server(s) 26 .
  • an algorithm that selects ac-BarringF actor and ac-BarringTime from one of the plurality of IE in the SIB2 that contained that information may be configured such that a specific IE (e.g. ssac- BarringForMMTEL-Video-r9) is associated with a specific device (e.g., a security monitor), and that the ac-BarringF actor and ac-BarringTime associated with that specific IE is selected for use by a specific type of device.
  • a specific IE e.g. ssac- BarringForMMTEL-Video-r9
  • a specific device e.g., a security monitor
  • one or more server(s) 26 may generate a parameter paring selection criteria signal to send to the device(s) 20.
  • the parameter paring selection criteria signal comprises an indication of which of plural possible parameter parings are to be utilized by an electronically controlled device 20 in conjunction with a power management function performed by the electronically controlled device.
  • the power management function may comprise termination of grid power utilization by the electronically controlled device.
  • Each of the plural possible parameter parings may comprise a wait factor as a first parameter of the pair and a wait time as a second parameter of the pair.
  • the server(s) 26 comprise hardware or processor circuitry for generating the parameter paring selection criteria signal (such as processor 90 of Fig. 4) and a communications interface (such as interface 27 of Fig. 1) or interface 96 of Fig. 4 for transmitting the parameter paring selection criteria signal to the electronically controlled device.
  • the communications interface may be hardwired or wireless.
  • the processor circuitry of the server(s) 26 may be configured to generate the parameter paring selection criteria signal dependent upon type of electronically controlled device to which the parameter paring selection criteria signal is transmitted.
  • Fig. 2G shows as act 34G-0 the Si-based power management controller 34G obtaining two parameters from the broadcast system information used by the processor circuitry to determine the wait period.
  • Act 34G-1 comprises the Si-based power management controller 34G making a determination of the wait period using the two parameters.
  • the Si-based power management controller 34G may use the wait factor and the wait time of a selected one of the parameter pairings 76 as inputs for a random determination of the wait period, as depicted by randomization function 78.
  • act 34G-2 the device 20G receives a power management command to perform a corresponding power management function.
  • the power management command may be received from radio access network node 60 or server(s) 26.
  • the power management command of act 34G-2 may be, in differing scenarios, either the power termination command (see Fig. 2A), the power resumption command (see Fig. 2B), or the power start-up command (see Fig. 2C), as non limiting examples.
  • act 34G-3 the Si-based power management controller 34G imposes the wait period before issuing a signal to power management function 30 to perform (as act 34G-4) the corresponding requested power management function.
  • Certain units and functionalities of device 20 and/or server(s) 26 are, in example embodiments, implemented by electronic machinery, computer, and/or circuitry.
  • processor circuitry 38 of the example embodiments of devices 20 and processor circuitry of server(s) 26 herein described and/or encompassed may be comprised by the computer circuitry of Fig. 4.
  • Fig. 4 shows an example of such electronic machinery or circuitry, whether node or terminal, as comprising one or more processor(s) circuits 90, program instruction memory 92; other memory 94 (e.g., RAM, cache, etc.); input/output interfaces 96; peripheral interfaces 98; support circuits 99; and busses 100 for communication between the aforementioned units.
  • the program instruction memory 92 may comprise coded instructions which, when executed by the processor(s), perform acts including but not limited to those described herein.
  • each of device 20 and servers 26, for example, may comprise memory in which non-transient instructions are stored for execution.
  • the memory 94 may be one or more of readily available memory such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or remote, and is preferably of non-volatile nature.
  • RAM random access memory
  • ROM read only memory
  • floppy disk hard disk
  • flash memory any other form of digital storage, local or remote, and is preferably of non-volatile nature.
  • the support circuits 99 are coupled to the processors 90 for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input/output circuitry and subsystems, and the like.
  • Fig. 5 shows various data flows and computer program routines that may be associated with a consolidated example embodiment and mode of an electronically controlled device 20 that obtains a wait period from broadcast system information, and which may selectively implement one or more (in any desired combination) of the distinctive differing aspects of the example embodiments and modes of Fig. 2A - Fig. 2G.
  • the data flows and computer program routines of Fig. 5 involve a first data flow depicted by Fig. 6; a second data flow depicted by Fig. 7; basic acts comprising a routine executed by an application programmable interface (RRC Msg API routine) are depicted by Fig. 8.
  • RRC Msg API routine application programmable interface
  • RRC Msg API depicted by Fig. 8
  • basic acts comprising a SIBl Msg subroutine are depicted by Fig. 8-1
  • basic acts comprising a SIB2_Msg subroutine are depicted by Fig. 8-2A and Fig. 8-2B
  • basic acts comprising a SIBlO Msg subroutine are depicted by Fig. 8-3
  • basic acts comprising a NAS_Msg subroutine are depicted by Fig. 8-4A and Fig. 8-4B.
  • Fig. 9 shows basic introductory acts comprising a process logic routine executed by Si-based power management controller 34, with Fig. 9-1 through Fig. 9-4 showing further basic acts comprising initialization subroutines including an initialize working variables subroutine of Fig. 9-1; a Get ROM Cfg Data subroutine of Fig. 9-2A and Fig. 9-2B; a Get_NV_Cfg_Data subroutine of Fig. 9-3; and a GET NV_PWS_Wait_State subroutine of Fig 9-4.
  • Fig. 10A and Fig. 10B show basic substantive acts comprising a process logic routine executed by Si-based power management controller 34, while Fig. 10-1 shows basic acts comprising an Attach_Wait subroutine; Fig. 10-2 shows basic acts comprising a
  • Fig. 5 The example consolidated embodiment and mode of Fig. 5 involves data flows such as shown in Fig. 6 and Fig. 7, and comprises a Power Management Life Cycle System configured to provide aspects of the technology disclosed herein.
  • a LTE eNB or NR gNB may correspond, for example, to radio access network node 60 of Fig. 1; an LTE/NR UE RxTx Device may correspond to radio network interface 52 of Fig.
  • the Power Management Life Cycle System may correspond to Si-based power management controller 34 of Fig.1; a Device Power Control Logic may correspond to power management function 30 of Fig. 1 ; a ROM may correspond to ROM 42 of Fig. 1; and a Non-Volatile Memory may correspond to non-volatile memory (NV-memory) 44 of Fig. 1.
  • NV-memory non-volatile memory
  • The“Power Management Life Cycle System” (“PMLCS”) of the consolidated example embodiment and mode is configured to manage the functionality expressed by device 20 as associated with the receipt, and though receipt-end, of a message or command (such as that labeled in LTE/New Radio (NR) Public Warning System (PWS) Message) that would trigger, for example, a“Power Down” event.
  • a message or command such as that labeled in LTE/New Radio (NR) Public Warning System (PWS) Message
  • PWS Public Warning System
  • a PWS message may include ETWS and CMAS messages, and as used herein the term “PWS Message” may refer to one or the other or both types of messages.
  • the Management Life Cycle System determines when to signal to the“Device Power Control Logic” (aka Controlled Device) the transition of a variable“Device Power State” from Low to Normal, and vise-versa.
  • the Power Management Life Cycle System may be implemented by a Si-based power management controller 34, and may particularly illustrate the routines described herein including the routines of Fig. 8 and Fig. 10.
  • the Power Management Life Cycle System may set the Device Power State variable to Low upon The Device system power on, and then upon determining that there are no PWS Messages received by an“LTE Device” that would trigger The Device to action, set the Device Power State variable to Normal, as understood (for example) with reference to Fig. 2C and Fig. 3C.
  • the Power Management Life Cycle System may set the Device Power State variable to Low upon initial receipt of the PWS Message from an“LTE Device” (such as radio access network node 60) that would trigger The Device to action, maintain the Device Power State through the period that the PWS Message is continuously received, maintain the Device Power State through to the termination of that PWS Message, and maintain the Device Power State for a period of time following the termination of the PWS Message.
  • the RRC Msg API routine of Fig. 8 may run independently of the LTE/NR UE Device, but can share data objects such as RRC Msg Event and RRC Msg Data.
  • the RRC Msg API routine of Fig. 8 may run independently of the System and Life Cycle for Power Mgmt.
  • IoT Device e.g., Si-based power management controller 34
  • PWS Message Logic can share data objects such as Cfg_Data and PWS_State.
  • LTE/NR UE RxTx Device e.g., radio network interface 52
  • RRC_Msg_ API an“RRC Msg Event”
  • RRC Msg Data which holds the received message(s).
  • messages particularly of interest are messages which include system information block (SIB) 1 (which are handled by the subroutine of Fig. 8-1); messages which include system information block (SIB) 2 (which are handled by the subroutine of Fig.
  • SIB system information block
  • NAS non-access stratum
  • SIB system information block
  • the schedulinglnfoList is contained in SystemlnformationBlockTypel .
  • the device 20 receives ETWS notification in SIB10 according to Scheduling data in SIB1.
  • the SIBs to be broadcast are divided into multiple schedulinginfo, each schedulinginfo may contain one or multiple SIBs.
  • the subroutine of Fig. 8-1 searches each schedulinginfo of the schedulinglnfoList to determine if a PWS Message (i.e. SIB10) is being broadcasted by the system.
  • SIB system information block
  • a Rel-l4 SIB2 can carry five different AC-BarringConfig IEs.
  • the subroutine of Fig. 8-2 selects one of the five, if available, per configuration data. After selecting one, the BarringF actor and BarringTime is copied into Lcl ACB Data and maybe copied into Cfg Data.
  • SIB system information block
  • Non-access stratum (NAS) messages are handled by the subroutine of Fig. 8-4.
  • the subroutine of Fig. 8-4 updates Cfg data with new parameters received from the system; saves the updated copy back into Non-Volatile Memory; adjusts the Cfg_Data as necessary per configuration for ac-barringF actor and ac-barringTime received via SIB msg.
  • Fig. 9 shows basic introductory acts comprising a process logic routine executed by the Power Management Life Cycle System, e.g., by Si-based power management controller of the consolidated example embodiment and mode of Fig. 5.
  • Fig. 9-1 is a routine which initializes certain working variables;
  • Fig. 9-2 is a subroutine which obtains ROM configured data (from ROM 42);
  • Fig. 9-3 is a subroutine which obtains configured data from the non volatile memory (NV-memory) 44;
  • Fig. 9-4 is a subroutine which, e.g., obtains a variable NV_PWS_Wait_State from non-volatile memory (NV-memory) 44.
  • Fig. 10A and Fig. 10B shows basic substantive acts comprising a process logic routine executed by a Si-based power management controller of the consolidated example embodiment and mode of Fig. 5.
  • the routine of Fig. 10 waits in a loop for LTE Device (e.g., radio access network node 60) to signal receipt of a PWS_Message, and then changes the Device Power State signal to the Controlled Device accordingly.
  • LTE Device e.g., radio access network node 60
  • PWS_Message type map to one of the Trigger_States (e.g. an Earthquake message type).
  • the process may be selectively configured to be dependent upon any one or more of the following before signaling to the device:
  • the routine of Fig. 10A and Fig. 10B may ultimately invoke the subroutines of Fig. 10-1 through Fig. 10-4.
  • the subroutine of Fig. 10-1 pertains, e.g., to the example embodiment and mode of Fig. 2D and Fig. 3D which concerns waiting for the device 20 to attach to a radio access network.
  • the subroutine of Fig. 10-1 randomizes a wait time and then starts a background process that will initialize the timer (first parameter) with a value (second parameter) and then decrement the timer at a fixed rate (e.g. 1 per second) until it reaches zero.
  • the subroutine then waits until the end of the eNB_Attach_Wait_Timer.
  • the subroutine uses the random factor to determine if the process should begin another wait time cycle.
  • the subroutine of Fig. 10-2 pertains, e.g., to the example embodiment and mode of Fig. 2E, which involves a wait for connection to the server(s) 26.
  • the subroutine of Fig. 10-2 pertains, e.g., to the example embodiment and mode of Fig. 2E, which involves a wait for connection to the server(s) 26.
  • the subroutine of Fig. 10-2 pertains, e.g., to the example embodiment and mode of Fig. 2E, which involves a wait for connection to the server(s) 26.
  • 10-2 begins with a request to the LTE Device to establish a connection to the data server as identified by Cfg_Data.Server_Address.
  • the subroutine then waits for either a connection to be established, or time out on the wait loop. If a PWS PS State is detected while waiting, the subroutine waits for the PWS PS State to end, and then returns to finish this wait loop.
  • the subroutine also may get the address of the server from the configuration data and store into variable shared with the LTE Device.
  • the subroutine may send an event to the LTE Device via shared data object that it should attempt to connect to the data server identified.
  • the subroutine starts a background process that will initialize the timer (first parameter) with a value (second parameter) and then decrement the timer at a fixed rate (e.g. 1 per second) until it reaches zero. The subroutine then waits until either the end of the timer (first parameter) with a value (second parameter) and then decrement the timer at a fixed rate (e.g. 1 per second) until it reaches zero. The subroutine then waits until either the end of the timer (first parameter) with a value (second parameter) until it reaches zero. The subroutine then waits until either the end of the timer (first parameter) with a value (second parameter) until it reaches zero. The subroutine then waits until either the end of the timer (first parameter) with a value (second parameter) until it reaches zero. The subroutine then waits until either the end of the timer (first parameter) with a value (second parameter) until it reaches zero. The subroutine then waits until either the end
  • the subroutine waits for the PWS_State to end.
  • PWS_Message is received, in which case the subroutine goes back to the top of the subroutine and waits for PWS Message to end again.
  • the subroutine may check if LTE Device is attached to the eNB before testing for PWS_State to prevent“stale” data from being used (e.g. if LTE Device detaches, and PWS State was TRUE, then PWS State would remain in that state until re-attach or Power Cycle). Before ending, the subroutine sets the state of
  • PWS_Wait_State to FALSE in Non-Volatile memory after PWS_Wait_Timer has expired.
  • the subroutine of Fig. 10-4 begins by randomizing the wait time.
  • the subroutine then starts a background process that will initialize the timer (first parameter) with a value (second parameter) and then decrement the timer at a fixed rate (e.g. 1 per second) until it reaches zero.
  • the subroutine then waits until the end of the eNB_Attach_Wait_Timer. If LTE device detaches from eNB while waiting, then the subroutine may exit. If enabled to do so, then following the end of the wait, the subroutine may use the random factor to determine if the process should begin another wait time cycle.
  • a different order of operation for Random F actor and Wait Time for the subroutine of Fig.
  • the PMLCS may signal to the Controlled Device a Low Device Power State when the PMLCS receives from the LTE Device an indication that the LTE Device has received a PWS Message (i.e. an ETWS SystemlnformationBlockTypelO, aka SIB10, CMAS SystemInformationBlockTypel2, aka SIB 12), and the PMLCS has determined that that PWS Message maps to one or more Trigger Types configured in the Controlled Device.
  • a Trigger Type may be, for example, an Earthquake.
  • Trigger Types configured in the Controlled Device, and if one or more of the mapped Trigger Types also maps to an Delay Type configured in the Controlled Device, then before the
  • PMLCS will signal to the Controlled Device a Low Device Power State the PMLCS may wait some amount of time.
  • Trigger Types may be used by PMLCS.
  • the Trigger Types may be initially configured at time of The Device manufacture and may be stored as default in ROM.
  • the Trigger Types may be individually or group reconfigured by reception of an LTE NAS message.
  • a reconfigured Trigger Type may be stored in NV Memory.
  • a Trigger Type stored in NV Memory may supersede the related Trigger Type stored in ROM.
  • the PMLCS system may be disabled by configuring all Trigger Types as disabled.
  • the Delay Types may be initially configured at time of The Device manufacture and may be stored as default in ROM.
  • the Delay Types may be individually or group reconfigured by reception of an LTE NAS message.
  • a reconfigured Delay Type may be stored in NV Memory.
  • a Delay Type stored in NV Memory may supersede the related Delay Type stored in ROM.
  • schedulinglnfoList i.e. a detection
  • the PMLCS may continue to signal to the Controlled Device a Low Device Power State, and the PMLCS may wait some amount of time before its signals to the Controlled Device a Normal Device Power State. If not so configured, the PMLCS may signal to the Controlled Device a Normal Device Power State without waiting.
  • the parameter(s) used by PMLCS to determine wait times may be any parameter(s) used by PMLCS to determine wait times.
  • the parameters used may be per the values stored in ROM (i.e. default values) or per the values stored in NV Memory (i.e. values received via NAS message), and may be further configured to use values received from one of multiple possible SIB2 AC- BarringConfig Information Element (IE), which are not stored in NV Memory.
  • IE SIB2 AC- BarringConfig Information Element
  • the length of time that PMLCS will wait following the determined/detected end of PWS Message and before it signals to the Controlled Device a Normal Device Power State may be configurable. It may be configured, for example, that the there is a 90% chance that a wait period will occur, and the subsequent wait period may be a random number of seconds, for example, between 0 and 32. Following the first wait, there may be again another 90% chance that a second wait between 0 and 32 seconds will occur... .etc. until a 10% chance event occurs that no wait period will occur and the wait ends.
  • the PMLCS may continue to signal to the Controlled Device a Low Device Power State, and the PMLSC may resume waiting for a determined/detected end of a PWS Message. If the PMLCS should then determine/detect the end of the PWS Message, then if the PMLCS is configured to do so, the PMLCS may continue to signal to the Controlled Device a Low Device Power State, and the PMLCS may wait some amount of time before its signals to the Controlled Device a Normal Device Power State. Otherwise if the PMLCS is configured to do so, the PMLCS signals to the Controlled Device a Normal Device Power State without waiting.
  • the PMLCS may continue to signal to the Controlled Device a Low Device Power State, and the PMLCS may wait some amount of time before its signals to the Controlled Device a Normal Device Power State (i.e. PMLCS must wait the full amount of time without interruption from a PWS Message before indicating Normal).
  • the LTE Device must be“Attached” to eNB before the
  • PMLCS may consider signaling to the Controlled Device a Normal Device Power State. If not configured so, the PMLCS may only consider the PWS Message state before signaling to the Controlled Device the Low Device Power State.
  • Rattling of Device Power State that may result from LTE system instability or poor RF conditions may be prevented.
  • a wait timer is used to ensure that when the LTE Device indicates a transitions from detached to Attached, that the LTE Device remains Attached without interruption for at least some amount of time before the PMLCS may take further consideration, and before signaling to the Controlled Device a Normal Device Power State.
  • the wait timer may be configured with a random number of seconds, for example, between 0 and 32. Following the wait, it is configurable that there is, for example, 90% chance that a second wait between 0 and 32 seconds will occur....etc. Until a 10% chance event occurs that no wait period will occur and the wait ends.
  • the PMLCS will wait some amount of time.
  • the wait time may be configured with a random number of seconds, for example, between 0 and 32.
  • PMLCS may at time of power on attempt to connect to a server. If the PMLCS cannot connect to the server after a configurable amount of time it will signal to the Controlled Device a Low Device Power State. The PMLCS may continue to try to connect to the server and signal to the Controlled Device a Low Device Power State until a server connection is made. [000101] 14. If configured to do so, and the LTE Device is attached to the eNB, the
  • the PMLCS may at a configurable periodicity attempt to connect to a server. If the PMLCS cannot connect to the server after a configurable amount of time it will signal to the Controlled Device a Low Device Power State. The PMLCS may continue to try to connect to the server and signal to the Controlled Device a Low Device Power State until a server connection is made.
  • the technology disclosed herein thus provides a distribution function that distributes the actions taken by an electronically controlled device when the action is triggered by a broadcasted PWS Message.
  • the various example embodiments and modes the distribution function takes into account the density of devices that it is trying to distribute. To account for density, in various example embodiments and modes the function may be configurable.
  • Such configuration is not dependent upon establishment of a data channel to a server that might provide such that configuration data, since a server with an individual data channel to each individual device to (re)configure the distribution function of the device with a new data set, could potentially require millions of individual connections, which would result in inefficient use of system resources and long latency to effect a system wide
  • an example embodiment and mode of the technology disclosed herein provides that a distribution function is configured to use the ac-BarringF actor and ac- BarringTime values carried in/by the SystemInformationBlockType2 IE. Because the SIB2 is a system broadcast IE, it can address the issues of inefficiency and latency incurred by using an individual connection to a device for the purpose of (re)configuring the distribution function.
  • a distribution function uses the ac-BarringF actor and ac-BarringTime values is provided as part of a Power Management Life Cycle System.
  • the Power Management Life Cycle System may, in its various and selectively optional aspects, address issues such as how long the device should remain in a mode triggered by a PWS Message, what the device should do after PWS Message is no longer transmitted by the system, or when it can no longer receive a PWS Message, or what the device should do when executing a mode triggered by a PWS Message and device power is lost and then restored .
  • Example Embodiment 1 An electronically controlled device configured to perform a device-native operation, the electronically controlled device comprising:
  • receiver circuitry configured to obtain broadcast system information from a base station node over a radio interface; processor circuitry configured to use the broadcast system information to control a power management function of the electronically controlled device.
  • Example Embodiment 2 The device of claim 1, wherein the processor circuitry is configured to determine a wait period before performing the power management function.
  • Example Embodiment 3 The device of claim 2, wherein the power management function comprises termination of grid power utilization by the electronically controlled device.
  • Example Embodiment 4 The device of claim 2, wherein the power management function comprises resumption of grid power utilization by the electronically controlled device.
  • Example Embodiment 5 The device of claim 2, wherein the power management function comprises power start-up of the electronically controlled device.
  • Example Embodiment 6 The device of claim 2, the processor circuitry is configured to:
  • Example Embodiment 7 The device of claim 2, the processor circuitry is configured to:
  • Example Embodiment 8 The device of claim 1, wherein the processor circuitry is configured to obtain from the broadcast system information an indication of one or more public safety events, and wherein the processor circuitry is configured to control the power management function of the electronically controlled device when the one or more public safety events corresponds to a triggered event configured at the electronically controlled device.
  • Example Embodiment 9 The device of claim 8, wherein the processor circuitry is configured to obtain the indication of one or more public safety events from either system information block 10 (SIB10) or system information block 12 (SIB12) of the broadcast system information.
  • SIB10 system information block 10
  • SIB12 system information block 12
  • Example Embodiment 10 The device of claim 2, wherein the processor circuitry is configured to obtain two parameters from the broadcast system information used by the processor circuitry to determine the wait period, and wherein the first parameter is a wait factor and the second parameter is a wait time.
  • Example Embodiment 11 The device of claim 10, wherein the processor circuitry is configured to use the wait factor and the wait time as inputs for a random determination of the wait period.
  • Example Embodiment 12 The device of claim 10, wherein the processor circuitry is configured to obtain the two parameters from the system information block 2 (SIB2) of the broadcast system information.
  • SIB2 system information block 2
  • Example Embodiment 13 The device of claim 12, wherein system information block 2 (SIB2) of the broadcast system information comprises plural parings of a first parameter and a second parameter, and wherein the processor circuitry is configured to utilized a configured one of the plural pairings to obtain the wait factor and the wait time.
  • Example Embodiment 14 A method in electronically controlled device configured to perform a device-native operation, the method comprising:
  • Example Embodiment 15 The method of claim 14, further comprising the processor circuitry determining a wait period before performing the power management function.
  • Example Embodiment 16 The method of claim 15, wherein the power management function comprises termination of grid power utilization by the electronically controlled device.
  • Example Embodiment 17 The method of claim 15, wherein the power management function comprises resumption of grid power utilization by the electronically controlled device.
  • Example Embodiment 18 The method of claim 15, wherein the power management function comprises power start-up of the electronically controlled device.
  • Example Embodiment 19 The method of claim 15, further comprising the processor circuitry:
  • Example Embodiment 20 The method of claim 15, further comprising the processor circuitry: determining that the electronically controlled device is connected to a server that transmit signals to the electronically controlled device; and then imposing the wait period before performing the power management function.
  • Example Embodiment 21 The method of claim 14, further comprising the processor circuitry obtaining from the broadcast system information an indication of one or more public safety events, and controlling the power management function of the
  • Example Embodiment 22 The method of claim 21, further comprising the processor circuitry obtaining the indication of one or more public safety events from either system information block 10 (SIB10) or system information block 12 (SIB12) of the broadcast system information.
  • Example Embodiment 23 The method of claim 15, further comprising the processor circuitry obtaining two parameters from the broadcast system information used by the processor circuitry to determine the wait period, and wherein the first parameter is a wait factor and the second parameter is a wait time.
  • Example Embodiment 24 The method of claim 23, further comprising the processor circuitry using the wait factor and the wait time as inputs for a random determination of the wait period.
  • Example Embodiment 25 The method of claim 23, further comprising the processor circuitry obtaining the two parameters from the system information block 2 (SIB2) of the broadcast system information.
  • Example Embodiment 26 The method of claim 25, wherein system information block 2 (SIB2) of the broadcast system information comprises plural parings of a first parameter and a second parameter, and further comprising the processor circuitry utilizing a configured one of the plural pairings to obtain the wait factor and the wait time.
  • a server comprising:
  • processor circuitry configured to generate a parameter paring selection criteria signal, the parameter paring selection criteria signal comprising an indication of which of plural possible parameter parings are to be utilized by an electronically controlled device in conjunction with a power management function performed by the electronically controlled device, each of the plural possible parameter parings comprising a wait factor as a first parameter of the pair and a wait time as a second parameter of the pair;
  • a communications interface configured to transmit the parameter paring selection criteria signal to the electronically controlled device.
  • Example Embodiment 28 The server of claim 27, wherein the processor circuitry is configured to generate the parameter paring selection criteria signal dependent upon type of electronically controlled device to which the parameter paring selection criteria signal is transmitted.
  • Example Embodiment 29 The server of claim 27, wherein the power management function comprises termination of grid power utilization by the electronically controlled device.
  • the embodiments may be implemented in software as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware.
  • the software routines of the disclosed embodiments are capable of being executed on any computer operating system, and is capable of being performed using any CPU architecture.
  • the instructions of such software are stored on non-transient computer readable media.
  • the functions of the various elements including functional blocks, including but not limited to those labeled or described as“computer”,“processor” or“controller”, may be provided through the use of hardware such as circuit hardware and/or hardware capable of executing software in the form of coded instructions stored on computer readable medium.
  • functions and illustrated functional blocks are to be understood as being either hardware-implemented and/or computer-implemented, and thus machine-implemented.
  • the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) [ASIC], and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein.
  • the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed.
  • use of the term“processor” or“controller” shall also be construed to refer to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.
  • the technology disclosed herein is directed to solving radio communications-centric issues and is necessarily rooted in computer technology and overcomes problems specifically arising in radio communications. Moreover, in at least one of its aspects the technology disclosed herein improves the functioning of the basic function of a wireless terminal and/or node itself so that, for example, the wireless terminal and/or node can operate more effectively by prudent use of radio resources.

Landscapes

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

Abstract

L'invention concerne un dispositif à commande électronique (20) conçu pour effectuer une opération native de dispositif et comprenant un circuit récepteur (52) et un circuit processeur (38). Le circuit récepteur (52) est conçu pour obtenir des informations de système de diffusion en provenance d'un nœud de station de base sur une interface radio. Le circuit processeur (38) est conçu pour utiliser les informations de système de diffusion pour commander une fonction de gestion de puissance du dispositif à commande électronique (20).
PCT/US2019/014467 2018-01-23 2019-01-22 Gestion de puissance de dispositif à commande électronique WO2019147538A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862620627P 2018-01-23 2018-01-23
US62/620,627 2018-01-23

Publications (1)

Publication Number Publication Date
WO2019147538A1 true WO2019147538A1 (fr) 2019-08-01

Family

ID=67396189

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/014467 WO2019147538A1 (fr) 2018-01-23 2019-01-22 Gestion de puissance de dispositif à commande électronique

Country Status (1)

Country Link
WO (1) WO2019147538A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080002646A1 (en) * 2006-06-30 2008-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Enhancing coverage for high speed downlink packet access (hsdpa) channel
WO2015103732A1 (fr) * 2014-01-07 2015-07-16 Qualcomm Incorporated Commande de puissance de pusch initial pour eimta en lte
US20150350859A1 (en) * 2014-05-29 2015-12-03 Motorola Solutions, Inc. Public safety network relay service management
US20160037419A1 (en) * 2013-04-12 2016-02-04 Huawei Technologies Co., Ltd. Control method for power configuration on heterogeneous network, and user equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080002646A1 (en) * 2006-06-30 2008-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Enhancing coverage for high speed downlink packet access (hsdpa) channel
US20160037419A1 (en) * 2013-04-12 2016-02-04 Huawei Technologies Co., Ltd. Control method for power configuration on heterogeneous network, and user equipment
WO2015103732A1 (fr) * 2014-01-07 2015-07-16 Qualcomm Incorporated Commande de puissance de pusch initial pour eimta en lte
US20150350859A1 (en) * 2014-05-29 2015-12-03 Motorola Solutions, Inc. Public safety network relay service management

Similar Documents

Publication Publication Date Title
EP3627863B1 (fr) Procédé de resélection de cellule et dispositif associé
US20210168810A1 (en) Resource Configuration Method and Apparatus
US11582828B2 (en) Method and device for controlling RRC state, and computer storage medium
EP3678425B1 (fr) Procédé de transmission de données et dispositif associé
JP6997787B2 (ja) 専用システム情報および共用システム情報の管理
CN106961727B (zh) 一种寻呼及其控制方法及装置
JP2021520680A (ja) 接続状態からの遷移のリリース要因
CA3078410C (fr) Procede et appareil de controle de capacite d'ue restreinte, et support de stockage informatique
US11317338B2 (en) Access control method and apparatus
WO2017121070A1 (fr) Procédé, appareil et dispositif de transmission d'informations système liées à l'activation
CN114026897A (zh) 用于在无线通信***中处理紧急服务的方法和装置
WO2021138376A1 (fr) Prise en charge de dispositifs ayant des capacités de bande passante différentes dans un réseau de communication
CN106851790B (zh) 一种功耗变化控制方法及***以及移动终端
US20160135133A1 (en) Methods and devices for adjusting signal strength of router
CN102448142B (zh) 控制终端选择网络的方法和装置
US20190387395A1 (en) Method and apparatus for indicating restricted resources of wireless terminal
JP2023554088A (ja) ネットワーク選択方法、装置、機器及び記憶媒体
CN105940729B (zh) D2d发现信息的接收方法和装置
CN104205994A (zh) 用于在无线通信***中的操作状态同步的设备和方法
WO2020006763A1 (fr) Procédé et appareil d'indication pour signalisation de commande, et terminal, station de base et support d'informations
WO2019147538A1 (fr) Gestion de puissance de dispositif à commande électronique
CN108668343B (zh) 一种终端设备的状态控制方法、网络侧设备及终端设备
CN116158099A (zh) 基于用户装备能力的网络接入请求
CN115150908A (zh) 一种寻呼方法及装置
CN115699655A (zh) 一种bwp配置方法及装置、终端设备、网络设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 27.10.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 19744566

Country of ref document: EP

Kind code of ref document: A1