JP2016514445A - System and method for managing a distributed wireless power transfer network for electrical devices - Google Patents

Abstract

The present disclosure provides a central management server that manages a wireless power transfer network for power transfer to an electrical device and communicates with a cloud-based network that includes at least one wireless power outlet and at least one management server The present invention relates to a system and method. The management system of the present disclosure allows for all remote health checks and remote maintenance of wireless power outlets in the network. In addition, the management system associates with commands and controls that function to determine system administrator rights and allowed / disabled functionality while delivering power to specific field electrical devices. Allows for complete monitoring of deployment according to policy management. [Selection] Figure 7A

Description

  The present disclosure relates herein to systems and methods for managing a wireless power transfer network for electrical devices. In particular, the present invention relates to a wireless power outlet cloud-based network management system that enables remote health checkup, maintenance, and policy management along with network element commands and controls.

  Mobile devices such as mobile phones, media players, tablet computers, laptops / notebooks / netbooks, and ultrabooks charge the mobile device while the user is out and about to move or on the move Therefore, there is an increasing demand for users to access a power point that can transmit power.

  There is a need for a system that conveniently provides an opportunity for a mobile device user to transmit power to charge an electrical device in a public space that may stay for a long time, such as several minutes or more. Among other things, such public spaces may include restaurants, coffee shops, airport lounges, trains, buses, taxis, sports stadiums, halls, theaters, cinemas, and the like. In addition, while power transfer locations around the current location may meet user expectations, it is easy to track power transfer locations in public spaces as soon as the need arises, ie when the battery level is low There is a need for such a system that makes it possible.

  Such systems may be distributed in a variety of sites and require complex network architectures to provide a desire for wireless power transfer in public spaces.

  The present invention addresses the needs described above.

  At least one wireless power outlet unit operable to transfer power to at least one electrical device associated with the wireless power receiver, and at least one management server in communication with the at least one wireless power outlet unit. Presenting a system for managing a wireless power transfer network, according to one aspect of the present disclosure, wherein at least one management server receives an identification code from at least one wireless power outlet unit; An operation can be performed to execute instructions directed to managing power transfer from at least one wireless power outlet unit.

  Optionally, at least one management server of the system is directed to monitoring the health of the at least one wireless power outlet unit and to implement remote maintenance of the at least one wireless power outlet unit. May be further manipulated to execute an instruction to

  Where appropriate, at least one management server of the system is further operable to communicate with at least one electrical device.

  Where appropriate, a system for managing power transfer may be operated by at least one power management policy, which determines power transfer conditions of at least one wireless power outlet unit.

  Optionally, the at least one power management policy is selected from the group consisting of a user identification policy, a service type policy, a device type policy, a dynamic policy, and combinations thereof.

  Optionally, at least one power management policy is selected for at least one wireless power outlet unit according to the identification code.

  Optionally, the at least one wireless power outlet device has a default power management policy for determining default power transfer conditions.

  Additionally or additionally, the selected power management policy replaces the power management default policy.

  Optionally, the at least one power management policy is distributed in response to the change of the at least one power management policy at the at least one management server.

  Optionally, at least one power management policy is distributed according to a distribution schedule.

  Optionally, the at least one power management policy is distributed during communication requests from at least one wireless power outlet device.

  Where appropriate, the user identification policy includes an action selected from the group consisting of user identification, location identification, start time, end time, duration of power transfer, and combinations thereof.

  Where appropriate, the type of service policy determines the level of current applied during power transfer from the at least one wireless power outlet.

  Where appropriate, the dynamic policy includes actions selected from the group consisting of real-time management of power consumption, real-time management of battery health, location traffic control, and combinations thereof.

  In various embodiments of the present disclosure, providing remote maintenance includes starting, stopping, restarting, software updating, controlling a visual user interface, controlling a user audio interface. , And performing a step selected from the group consisting of combinations thereof.

  In various embodiments of the present disclosure, monitoring health includes a wireless power outlet responding to a communication signal within a timeout limit.

  Optionally, the communication signal is transmitted according to a schedule.

  Optionally, the communication signal is transmitted on demand.

  In another aspect of the present disclosure, a computer-implemented method is taught for managing a wireless power transfer network, the wireless power transfer network being (1) at least one electrical device associated with a wireless power receiver. At least one wireless power outlet unit operable to transmit power, and (2) at least one management server in communication with the at least one wireless power outlet unit, the method comprising at least one management The server includes receiving an identification code from at least one wireless power outlet unit, and the at least one management server managing power transmission from the at least one wireless power outlet unit.

  The method comprises: at least one management server monitoring the health of at least one wireless power outlet unit; and at least one management server providing remote maintenance of at least one wireless power outlet unit. Further may be included.

  Additionally or alternatively, the method can be further operated to communicate with at least one electrical device through at least one management server.

  Optionally, the step of managing power transfer is operated by at least one power management policy, wherein the at least one power management policy is configured to set power transfer conditions for at least one wireless power outlet unit. The

  Optionally, the at least one power management policy is selected from the group consisting of a user identification policy, a service type policy, a device type policy, a dynamic policy, and combinations thereof.

  Optionally, at least one power management policy is selected for the at least one wireless power outlet unit according to an identification code.

  Optionally, the at least one wireless power outlet unit is configured with a default power management policy to determine default power transfer conditions.

  When appropriate, the selected power management policy replaces the power management default policy.

  Optionally, the at least one power management policy is further distributed at least one management server in response to the change of the at least one power management policy.

  Optionally, at least one power management policy is distributed according to a distribution schedule.

  Optionally, at least one power management policy is distributed upon communication requests from at least one wireless power outlet unit.

  Optionally, the user identification policy includes an action selected from the group consisting of user identification, location identification, start time, end time, duration of power transfer, and combinations thereof.

  Optionally, the type of service policy determines the level of current applied during power transfer from at least one wireless power outlet.

  Optionally, the dynamic policy includes an action selected from the group consisting of real-time management of power consumption, real-time management of battery health, location traffic control, and combinations thereof.

  Optionally providing remote maintenance includes starting, stopping, restarting, updating software, controlling visual user interface, controlling user audio interface, and combinations thereof Performing a step selected from the group consisting of:

  If necessary, monitoring health includes the wireless power outlet responding to a communication signal within a timeout limit.

  Optionally, the communication signal is transmitted according to a schedule.

  Optionally, the communication signal is transmitted on demand.

  Another aspect of the present disclosure is to teach a method for managing wireless power transfer including at least one management server in communication with at least one wireless power outlet unit, the method comprising at least one The management processor receives at least one status report message from the power outlet unit, processes at least one status report message, and sends at least one response message to the at least one power outlet unit. Including executing an instruction to perform the operation including.

  Variously, the management processor is operable to periodically receive at least one status report message. Optionally, the status report message includes data regarding the operating mode of the power outlet unit, which may take a value selected from CHARGING and NOT-CHARGING.

  Optionally, processing the at least one status report message includes determining an appropriate value for the at least one control signal. The at least one response message may include a control signal. Thus, the control signal may include a COMMAND parameter that communicates power to the power outlet unit and a CHARGE value operable to instruct the power outlet unit to transmit power to the wireless power receiver. It has at least one value selected from DO-NOT-CHARGE that can be manipulated to command no. Additionally and alternatively, the control signal may include an INTERVAL parameter that instructs the power outlet device to transmit at least one second status report message after a length of delay determined by the value. Have a value selected to do. Additionally and alternatively, the control signal may include a request for an extended report message. Additionally and alternatively, the control signal may include a request for a configuration report message.

  Another aspect of the present disclosure is to teach a method for managing a wireless power transfer network including at least one management server in communication with at least one wireless power outlet unit, the method comprising at least one The power outlet processor transmits at least one status report message to the management server, receives at least one response message from the management server, and instructions encoded with a control signal included in the response message Including executing an instruction to execute an operation including executing.

  Optionally, the power outlet processor is operable to periodically transmit at least one status report message. Optionally, the status report message includes data regarding the operation mode of the power outlet unit, a transmitter identification code associated with the power outlet unit, a wireless power receiver associated with the power outlet unit, and operation information.

  Variously, the steps of executing the instructions include detecting a COMMAND parameter and transmitting power to a wireless power receiver if the COMMAND parameter has a value of CHARGE, or the COMMAND parameter setting a value of DO-NOT-CHARGE. If so, it may include terminating transferring power to the wireless power receiver. Additionally and alternatively, the step of executing the instructions includes detecting an INTERVAL parameter, sending at least one second status report message after a length of delay determined by the value, and an extended report message to the management server. May be included. The extended report message may include data regarding the operating temperature of at least one element of the power outlet, the operating current of at least one circuit of the power outlet, or the operating voltage of the power outlet.

  Another aspect of the present disclosure is to teach a method for managing a wireless power transfer network including at least one management server in communication with at least one wireless power outlet unit, the method comprising at least one Instructions encoded by one power outlet processor to transmit at least one configuration report message to the management server, to receive at least one configuration response message from the management server, and to a configuration command included in the configuration response message Execution of an instruction for performing an operation including executing.

  Optionally, the power outlet processor is operable to send at least one configuration report message periodically and / or upon startup. Variously, the configuration report message may include a transmitter identification code associated with the power outlet unit, a receiver identification code associated with the wireless power receiver associated with the power outlet unit, at least one software or firmware version executed by the power outlet processor, It may include data regarding the outlet unit hardware version, or at least one of the reasons for sending the configuration report message.

  Optionally, the power outlet unit communicates with the management server via the communication module, and the configuration report message includes data regarding the gateway identification code associated with the communication module.

  Where appropriate, executing the instructions includes updating at least one software version executed by the power outlet processor, for example, by detecting a software package version code and updating to the software package; Disabling, restarting power outlets, enabling optical feedback, enabling optical feedback, disabling optical feedback, enabling audio feedback, disabling audio feedback Including setting a current limit on the power outlet, setting a voltage limit on the power outlet, setting a sensitivity level on a sensor associated with the power outlet, and the like.

  Another aspect of the present disclosure is to teach a method for managing a wireless power transfer network including at least one management server in communication with at least one wireless power outlet unit, the method comprising at least one One management processor receives at least one configuration report message from the power outlet unit, processes at least one configuration report message, and sends at least one configuration response message to the at least one power outlet unit Execution of an instruction for executing an operation including the above.

  Optionally, the configuration report message may include a transmitter identification code associated with the power outlet unit, a receiver identification code associated with the wireless power receiver associated with the power outlet unit, and / or the power outlet unit via the communication module. When communicating with, includes data regarding a gateway identification code associated with the communication module. Further, the configuration report message may include data regarding at least one software or firmware version executed by the power outlet processor, a hardware version of the power outlet unit, or a reason for sending the configuration report message.

  Accordingly, processing the configuration report message may include determining an appropriate value for the at least one configuration command. Variety, at least one setting response message, CHARGER_FIRMWARE_VERSION parameters VENDOR_ID parameters ZB_FIRMWARE_VERSION parameters UPDATE_CHARGER_FIRMWARE parameters UPDATE_Z_FIRMWARE parameters RESET parameter LEDS parameters SOUND parameters DISABLE_CHARGER parameters CURRENT_LIMIT parameters INDUCTION_SENSOR_SENSITIVITY parameters, and / or DC_PEAK_LIMIT_THRESHOLD parameters like Including at least one configuration command that may include the following parameters:

  Another aspect of the present disclosure teaches a method for managing a wireless power transfer network including at least one management server that communicates with at least one wireless power outlet unit via at least one communication module. The method includes: at least one management processor receiving at least one health report message from the communication module; processing at least one health report message; and at least one in at least one communication module. Executing instructions for performing operations including sending a response message.

  Optionally, the health report message includes data relating to a gateway identification code and / or error code associated with the communication module. Thus, processing the at least one health report message may include determining an appropriate value for the at least one control signal. Variously, the at least one configuration response message includes at least one configuration command that may include a parameter, such as an INTERVAL parameter, wherein the INTERVAL parameter is after at least one second delay after a length of time determined by the value. Having the value selected to instruct the communication module unit to send a health report message. Additionally or alternatively, the control signal may include an ALLOW-JOIN parameter that instructs the communication module to add a candidate power outlet to the power transfer network.

  Another aspect of the present disclosure teaches a method for managing a wireless power transfer network including at least one communication server that communicates with at least one wireless power outlet via at least one communication module. And the method includes at least one communication module processor transmitting at least one health report message to the management server, receiving at least one response message from the management server, and a control signal included in the response message. Including a method that includes executing an instruction to perform an operation that includes executing the instruction to be encoded.

  Variously, the health report message includes data regarding a gateway identification code and / or an error code associated with the communication module.

  Optionally, executing the instructions includes detecting an INTERVAL parameter and transmitting at least one second health report message after a length delay determined by the value. Additionally or alternatively, executing the instructions includes detecting an ALLOW-JOIN parameter and adding a candidate power outlet to the power transfer network.

  Another aspect of the present disclosure teaches a method for managing a wireless power transfer network including at least one management server that communicates with at least one wireless power outlet unit via at least one communication module. The method includes: at least one management processor receiving at least one configuration report message from the communication module; processing the at least one configuration report message; and at least one configuration for the at least one communication module. Executing instructions for performing operations including sending a response message.

  Variously, the configuration report message can be a gateway identification code associated with the communication module, at least one firmware version executed by the communication module, at least one firmware or software version executed by the communication module, available to the communication module Data regarding at least one of memory, flash memory available to the communication module, percentage utilization of the communication module processor, flash memory available to the communication module, and / or the reason for sending the configuration report message may be included.

  Accordingly, processing the configuration report message may include determining an appropriate value for the at least one configuration command. Variously, the at least one configuration response message may include FIRMWARE_VERSION parameter, SW_VERSION parameter, UPDATE_FIRMWARE parameter, UPDATE_SOFTWARE parameter, REBOOT parameter, AGGREGATION_INTERVAL parameter, INIT_PAN parameter, LOG_APPENDER parameter, LOG_APPENDER parameter, LOG_APPENDER parameter, Contains at least one configuration command.

  Another aspect of the present disclosure teaches a method for managing a wireless power transfer network including at least one management server that communicates with at least one wireless power outlet unit via at least one communication module. And the method includes at least one communication module processor transmitting at least one configuration report message to the management server, receiving at least one configuration response message from the management server, and the configuration response message. Including a method including executing an instruction to perform an operation including executing an instruction encoded with the set command.

  Variously, the communication module processor may be operable to periodically transmit at least one configuration report message. The configuration report message includes a gateway identification code associated with the communication module, at least one firmware version executed by the communication module, at least one software version executed by the communication module, memory available to the communication module, used by the communication module It may include data regarding at least one of possible flash memory, percentage utilization of the communication module processor, flash memory available to the communication module, and / or the reason for sending the configuration report message.

  Thus, executing the instructions includes updating at least one software version executed by the communication module processor, detecting a software package version code, updating to a software package, and restarting the communication module. At least one of the following.

  Another aspect of the present disclosure is to teach a method for managing a wireless power transfer network including at least one management server in communication with at least one communication module, the method comprising at least one communication The module processor includes at least one request message for adding at least one candidate wireless power outlet to the network, receiving at least one request response from the management server, and included in the request response Executing an instruction to perform an operation including executing an instruction encoded with the command.

  Variously, the request message includes data regarding at least one of a gateway identification code associated with the communication module and a power outlet identification code associated with the candidate power outlet module.

  Thus, the step of executing the instruction detects a request response acknowledge command and adds a candidate radio power outlet to the network, or detects a request response unapproved command and rejects the candidate radio power outlet from the network. May be included.

  Another aspect of the present disclosure is to teach a method for managing a wireless power transfer network including at least one management server in communication with at least one communication module, the method comprising at least one management Receiving at least one request message from the communication module for the processor to add at least one candidate wireless power outlet to the network; processing the at least one request message; and sending a request response to the communication module. Including a method including executing an instruction to perform an operation including:

  Variously, the request message includes data regarding at least one of a gateway identification code associated with the communication module and a power outlet identification code associated with the candidate power outlet module.

  Thus, processing at least one request message includes including an approval command in the request response or including an unapproved command in the request response.

  For a better understanding of the embodiments and to show how it can be put into practice, reference is now made to the accompanying drawings purely by way of example.

  Referring now in particular to the drawings in detail, the details shown are by way of example only and are for illustrative purposes only of selected embodiments and are most useful and easy to understand in principle and conceptual aspects. It is emphasized that they are presented to provide what is believed to be an understandable explanation. In this respect, more detailed structural details than are necessary for a fundamental understanding are made in conjunction with the drawings that will clarify to those skilled in the art how some selected embodiments may be implemented. No attempt is made to give an explanation.

FIG. 2 is a schematic diagram of selected elements of a distributed system for powering an electrical device via a wireless power outlet and a power receiver. FIG. 2 is a schematic diagram of selected elements of a distributed wireless power transfer network for supplying power to an electrical device via a local gateway. FIG. 2 is a block diagram representing a possible software module architecture for a distributed system that implements wireless power transfer. In a block diagram representing selected actions of possible procedures, covering aspects of management server management functionality, such as health check, remote maintenance, and provision and control of power transfer by policy (s) is there. FIG. 6 is a schematic diagram of a possible power transfer network view accessible on a management console that allows a field gateway to be selected for additional actions. FIG. 2 is a schematic diagram of a possible field gateway summary diagram and a list of associated wireless power outlets accessible under the management console. FIG. 6 is a schematic diagram of a possible power transfer network diagram accessible on a management console that allows selection of a wireless power outlet for additional actions such as performing a remote restart, software update, and the like. FIG. 5 is a schematic diagram of a possible summary of a possible wireless power outlet detail that is accessible at the management console and optionally displayed when accessing the output. FIG. 6 is a flow chart representing selected actions of a possible method for processing a wireless power outlet health check sequence. FIG. 6 is a flow chart representing selected actions of a possible method for processing a software update sequence for a wireless power outlet. FIG. 2 is a system diagram that schematically illustrates selected components of a network architecture having various application interfaces. FIG. 6 is a flow chart representing selected actions of a possible method for handling policy uploads and wireless power outlet restarts. 6 is a flowchart representing various communications between a network management server and other elements of a wireless power transfer network. 6 is a flowchart representing various communications between a network management server and other elements of a wireless power transfer network. 6 is a flowchart representing various communications between a network management server and other elements of a wireless power transfer network. 6 is a flowchart representing various communications between a network management server and other elements of a wireless power transfer network. 6 is a flowchart representing various communications between a network management server and other elements of a wireless power transfer network. 6 is a flowchart representing various communications between a network management server and other elements of a wireless power transfer network.

  Aspects of the invention relate to providing a system and method for managing a wireless power transfer network for electrical devices. A centralized management system that communicates with a management server using a cloud-based management console may execute the power management software of the present disclosure. The power management software provides a platform that centrally covers the power management aspects of the network of wireless power transfer outlets that are distributed in public space. The power management software may provide site managers with the ability to manage wireless power outlets (hot spots) installed at the site. Optionally, the same management software system with higher system management rights may allow for some field power management, or may manage the overall organized power transfer outlet network. Power management software provides remote control and monitoring, maintenance of wireless power outlets combined with system remote health check, enables provisioning functionality, and uses policy enforcement techniques to maintain security and business objectives Can be operated.

  The wireless power outlet network management system is a network outlet discovery, availability and uptime that identifies outlet units present in the network or field, network outlet monitoring to determine the health of outlet network components, network element mapping, maintenance and A set of functionality may be provided such as event management, performance data and usage data collectors, management data browsers and intelligent notifications that allow configurable alerts corresponding to specific outlet network scenarios.

  Thus, management server collection of data usage may provide valuable statistics accessible to end users, partners, service providers, field owners, and the like.

  Optionally, the policy may be based on historical usage analysis of a specific wireless power outlet, a specific user, or a specific group of users.

  The power management and maintenance software may include operational aspects such as remote stop / start, remote restart, remote software upgrade and update. Optionally, the remote maintenance functionality may include a remote user display control test (LED, voice).

  The power management software performs remote health check by verifying that the remote wireless power outlet is active by performing a software quality or hardware quality test procedure for the remote wireless outlet or by testing the response to the communication signal. May be possible. Optionally, the health procedure may be tested for “health” parameters such as temperature, power consumption, connectivity status, current, and the like. Further, the test procedure may be a scheduled process or may be performed on demand. Display alerts may be triggered when appropriate.

  The power management software may enforce policies for commands and controls, which define the power management policy, the type of service (current) to define who, when, where and for how long Group consisting of policy to define, policy to define device type, real-time management of power consumption, real-time management of battery health, location traffic control in the field (send users to the field based on real-time parameter values) Operation modes such as a dynamic policy that is arbitrarily selected from the above may be included.

  The power management software may include an operational aspect that provides a power transfer aspect or control billing aspect associated with the electrical device. Therefore, the power management software will stop the power delivery at the power delivery outlet, continue the power delivery, modify the service, or possibly implement the new policy etc. according to the received operational signal, eg May be operable to provide features such as controlling one or more aspects of the. The power management software may be further operable to process user accounts, device registration, user-specific information, billing information, user credit, etc.

  It is noted that the management software may be further operable to detect undesirable situations while combining health check functions and remote maintenance. For example, events such as the addition or removal of wireless power outlets in the field may be detected.

  Optionally, the system may be configured to automatically respond when the system installs an appropriate policy when a new wireless power outlet is detected.

Additionally or alternatively, the system may be configured to send an alert to the system administrator with an appropriate message.
Management console

  The system provides a management console that communicates with a management server software application layer that may provide facility managers with the ability to manage hotspots installed at the facility, either directly or through a field gateway. Optionally, an administrator with higher administrator authority may control a larger portion of the wireless power transfer organization network. The management console may be accessed through a web browser or application on a computer, laptop, tablet or the like.

  The management console may allow an administrator to perform various tasks such as power provisioning process, remote maintenance, system health check, system monitoring, policy management and the like. Administrators can, for example, display real-time on / off status of hotspots, remote software updates or restart wireless power outlets, view usage statistics, and generate reports per user / location / hotspot / time, location / It may be possible to create, edit, and assign usage policies by day / time / user.

  The system may provide, for example, three levels of access and management: administrator, MAdmin, and MUser.

  Administrator-level administrators may have administrator rights to access all information and settings in the system.

  MAdmin level administrators have access to general settings for all locations of a particular facility or group of facilities. MAdmin can create / delete / edit MAdmin and Muser accounts and assign rights to them.

  A MUser level administrator may have rights to one or more locations where the administrator can view status, manage specific policies, and obtain reports.

  It is noted that additional administrator privileges associated with additional system administrators may be configured to meet diverse field needs and provide, for example, read-only access, read-write access as needed. The

  In certain embodiments, the system may have a flat hierarchy of MUsers where MUsers cannot be defined as administrators of other MUsers and there is no hierarchical inheritance of rights from one user to another. Alternatively, the users may be arranged in a hierarchical structure.

  Each customer may then start with one MAadmin account that may then create other MAadmin accounts and MUser accounts. Once an Admin account is created, the following may be set: company, management type, full name, e-mail, right to manage a specific list of locations, etc.

  All activities that MAdmin and MUsers perform in the system may be recorded in the system log (date / time, user, activity type, details).

  The management console may allow the MAdmin or MUuser to see a schematic of the location of the hot spot in the field, as illustrated in FIG. 5C. The figure may show the status of the hotspot with color display and pattern display. The status may include On, Off, Note-Used-Recently, failure, and the like. The management console may also be operable to display user / hotspot / hourly usage statistics in the form of on-screen graphs, formatted printable reports, exportable CSV formats, and the like. Other possible reports include, for example, the charging pattern over time, the list of hot spots used, and the number of each usage over time, the number of users charged and / or the number of visits over time Includes a list of places, usage statistics for various user plans, etc. In the case of a graph, the time scale may have a slider that enables time scale adjustments—from minute data points to weekly data points. For example, it is possible to have a non-continuous scale such as 1 minute-15 minutes-1 hour-4 hours-1 day-1 week.

The MUser may set a policy for the “memory promotion” layer of service. That is, the free charge fraction is added to the top of T _free based on the standard. Qualified users / user groups are allowed to charge the device for a variety of times, in the specified number of minutes, in the specified location, for the specified day of the week, in the specified time slot. You can. The policy may have a validity period, such as valid between Date1 and date2, for example, where date1 <= date2 and date2 may be equal to “no expiration”.

  A server administrator may have access to perform one or more of the following actions in the system.

  An administrator (Admin) may be able to do everything a MUser can do and may have rights to all customer accounts and all locations.

  Admin may be able to override a policy for a particular device (by RxID) by disabling the basic policy for that device. Such a device may be used during installation or maintenance to ensure proper operation of the Hotspot. Policy invalidation may be limited in time and may return to the previous default policy when time is up. Admin may be able to access devices that are designated with an “always on” or “never on” policy, sometimes referred to as a “gold recipient”.

  Administrators are satisfied with the status of installed components, for example, alerts for gateways that have not communicated with the server for a specified time period, alerts for Hotspots that have not communicated with the server for a specified time period, etc. May have visibility to.

  It is noted that a power provisioning software application may be installed on the mobile device and may be operated to receive data regarding the mobile device's wireless power transfer network.

  Further, the power provisioning software application may be operated to be executed on a mobile device and may allow management of power requirements within a wireless power transfer network. The power transfer network system is controlled via a management console and can be operated to manage wireless power transfer using a power receiver of a mobile device (in public space) at least one wireless power outlet, at least one At least one management server in communication with the wireless power outlet and a database deployment operable to store data received by the management server from the at least one power transmission outlet in communication with the management server may be used. .

  Where appropriate, wireless power transfer systems may enable wireless power transfer to users' electrical devices such as mobile devices, smart phones, tablet computers, laptop computers in homes, offices and various public areas. May be centrally monitored and controlled.

  The wireless power outlet can be operated to communicate with electrical mobile devices, perform identification to verify user credentials and margins, and execute software modules with near field communication features to further communicate with the management server It is noted that The management server allows detailed user or device usage information, power status information to be collected, and operates to receive a communication request from a wireless power outlet containing at least one data package for storing data in a database. You can do it. The collected data may include location information and geographic information, user ID and device ID, as well as other possible identification data, battery remaining information, and the like.

  As used herein, the term “virtual session” or “session” is hosted in a virtual computing environment associated with a particular user that may be accessed from one or more client devices other than the host. May point to a session. For example, sessions may include thin client sessions, virtual application sessions, virtual machine sessions, virtual operating system sessions, and the like. As used herein, a session described as being “between” a host device and a terminal device refers to an exchange of data between the host device and the terminal device, where the data is Related to sessions hosted on.

  As described herein, the term “terminal device” refers to a device configured to provide a user interface to a virtual session hosted remotely for a user associated with the virtual session.

  As described herein, the term “management server” is configured to provide power transfer to an electric mobile electrical device and control power charging between a wireless power outlet associated with the electric mobile device. Refers to a server configured to manage a plurality of induced power outlets. The term “management server” may be referred to variously herein as “control server”, “central server”, or “server”.

  As used herein, a mobile electrical device is used herein to refer variously to a “user device”, “electric device”, “electronic device”, “mobile device”, “communication device”, or “device”. May be called. The device may be an electric device with a battery, such as a mobile phone, media player, tablet computer, laptop / notebook / netbook / ultrabook, PDA, etc. Alternatively, the device may be a battery accessory such as an earphone or a stand-alone battery. In addition, the device may alternatively be any power device including an electric device without a battery.

  A wireless power outlet point may be referred to variously herein as a “PAP”, “hot spot”, or “charger”.

  As used herein, the term “memory” or “memory device” refers to read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage media, optical storage media, It may represent one or more devices for storing data, including flash memory devices, or other computer readable media for storing information. The term “computer-readable medium” refers to portable storage devices or persistent storage devices, optical storage devices, wireless channels, “SIM” cards, other smart cards, and a variety of that can store, include, or carry instructions or data. Including, but not limited to, other media.

For clarity in the description, the following description describes a system, apparatus, method, and software for dynamically updating a session based on data received from an access card reader. However, the same principle applies to any type of peripheral device or stand-alone access device or authentication device including an access card reader, smart card reader, biometric information reader, keypad, button, near field communication (NFC) device, etc. It should be understood that it may be applied to receiving authentication data from
Management server functionality

  The management server may be integrated with an external server or server. There are integrations that are data validation and external validation of user or device rights, network management and monitoring, remote device maintenance, policy enforcement, user management, device management, billing, advertising, socializing, etc. It may also be an integration for managing specific functional aspects.

Various functionality may be available through power management software, and third party applications may be available through an application programming interface (API) for a server application or another client application. Without limiting the scope of the application, the selected functionality may include, among others:
• Display a map with nearby public hotspots using satellite positioning, antenna triangulation, wireless network location or indoor positioning location information.
Reserving Hotspots in advance, so the reserved Hotspot is dedicated to registered users when the registered user arrives and is identified by a unique RxID and does not charge for other users.
-Device registration.
• Check power transfer statistics.
・ Purchase of accessories and charging policy.
• Check real-time power transfer balance for registered devices.
・ Set notification method and receive notifications.
• Set up automatic check-in to Hotspot locations.
・ Setting up automatic interactions using social networks such as automatic check-ins, tweets, status updates, etc. Providing promotional updates for.
Use accumulated information on the use of wireless transmission services including location etc. to better target users in promotions / advertisements.
• Create a loyalty plan for the field based on the use of wireless transmission services within the facility.
Provide a service to the user based on information indicating that the user's social network connection is close or close.
Launch third party applications on the user's device based on past or current usage of the power transfer service and the user's microlocation.
• Collect statistical information associated with application usage.

It is noted that if communication with the server cannot be established, the application may be able to provide power transfer based on a predetermined “offline policy”.
System architecture

  Some embodiments representing the current system architecture may use client / server technology, but are not limited and may use other network architectures, such as a peer-to-peer architecture where each node has equal responsibilities.

  In software engineering, client / server architecture refers to a network architecture in which each computer, device, or process on the network is either a client or a server. Such a network architecture can be applied to enterprise applications, and generally the presentation function, application processing function, and data management function are logically separated and can be operated in various nodes (hierarchies) of the system.

  Client software (which may be referred to as a user agent) allows interaction between the client machine (dashboard terminal, workstation, dedicated wireless power outlet, or electrical mobile device) and the application layer. When a web-based application is used, a client node (usually a browser) can interpret a client-side or server-side presentation layer, for example, by interpreting HTML controls, Java applet controls, or ActiveX controls. Provides a user interface that may be generated.

  The presentation layer is software that enables visualization functions for applications (on dashboard terminals, electric mobile devices), including images, static objects such as form fields that receive data retrieved from the database layer Or dynamically generated objects may be used to properly load the data and display the results of the analysis or calculation generated by the application layer. The output of the presentation layer may be submitted to a dashboard and further formatted to be presented, for example, on a terminal dashboard. In web-based applications, the presentation layer may be implemented by a web server.

  The application layer provides the business logic of the distributed system of the wireless power transfer network, and the management software may be installed on the management server. The application layer may receive a procedure call from the presentation layer that returns the result of application logic (calculation or analysis) executed on the management server. The application layer may further communicate with the database layer to store, update, and retrieve data. The management database layer may store application data such as business logic and policies, third party business related information, user information, geographical location, device ID, power transfer duration, and additional related information. The management database software may be installed on the management server or on a separate server (node). In any case, a database interface is required to implement business logic and to be able to connect to database server (s) to retrieve, update and store data. Sometimes.

  It is noted that in software engineering, such a complex client / server network architecture in which presentation functions, application processing functions, and data management functions are logically separated is called a multi-tier architecture. The most widespread use of a multi-tier architecture is that the client is the first tier (presentation layer), the management server is the second tier (application logic processing), and the database server is the third tier (data management). It is a certain three-tier architecture.

  Furthermore, the interaction between the electric mobile device and the wireless power outlet is adapted under the technology of a two-tier client / server architecture, where the wireless power outlet may serve as either a server or a client as required. Good. Furthermore, the wireless power outlet in the mode of data transmission acts as a client that responds to application logic requests (from the management server).

The client-server architecture is sometimes referred to in its simplest form as a two-node (hierarchical) architecture. The three-node (hierarchical) architecture of a client / server system is usually composed of a presentation node, a business node or data access node, and a data node.
Management and user identification

  Data collection of wireless power transfer system deployments distributed in various geographic locations may provide additional revenue channels to the enterprise using advanced data analysis methods applicable to the collected data, such as use Direct and indirect incentives to relevant companies and individual users by increasing the product, maintenance future purchases, deployment changes to meet demand by providing a data analysis layer of reports, statistics and trends It is noted that may be provided.

  To enable this type of model, a simple and convenient method for associating a user with a specific electric mobile device and a specific wireless power outlet (wired or wireless) based on the identification data is needed, It may possibly be synchronized by the device's close handshake communication.

  The present disclosure relates to a system for enabling this task to be accomplished automatically and without user intervention. The system may take advantage of existing transmitters that may be common among many mobile electrical devices that have additional software management applications for them. Such an implementation may allow mass deployment of the system with little additional cost or inconvenience for the user.

  Although the present disclosure is primarily described with respect to inductive chargers, it is particularly noted that it may be applied to any power delivery scheme and is not limited to, for example, a wired charging scheme or a wireless charging scheme.

  Optionally, the customer settings management portal can manage various functions such as wireless power outlet management, field management, user management, policy management, reporting, configuration system events and management system events auditing, security management, etc. Various screens may be used to enable.

  Optionally, wireless power outlet management may allow a summary view of live status and a detailed view of a particular store to allow management of store hotspots and gateways.

  Optionally, the user's management allows a new customer administrator to create or delete stores, assign or unassign stores to customer administrators (system administrator functionality), assign stores to operators, or Reassign, install stores (with gateways and hotspots), perform various component uninstall operations, enable or disable customer users, issue reports for all sites, etc. You may be able to do that.

  Optionally, the report may allow: That is, a single device, a single store, or a graphic representation of multiple stores and display of a text output file. Each report may be tailored to visualize data for a defined week / month / quarter within the last 12 months Graphic reports may be displayed in a graphic format, printed, or saved to a file Or it may be saved to a file in a data format used to generate the report. If desired, the generated report may provide, for example, usage per store of total power transfer time in minutes for a defined period, where the store per store ID, per hot spot per store Provide an average daily time in minutes, for example, utilization of a charging hotspot, eg a 24-hour cycle, a linear trend line, and possibly the dates of all stores on a given weekday and / or weekend displayed For every day, for example, providing total power transfer time in minutes and usage per trend, session length and average session length distribution, all per hour of day for a given period of time Charging per hour providing total store charge, repeated usage providing rate of returning users and repeated visits for power transfer, and minutes per device type It may be identified by the type of device that provides.

  Optionally, the audit may allow: That is, the installation or removal of gateways, the installation or removal of hot spots, the rejection of hot spots (not in the production database) as hot spots that are not “legal”, the definition or cancellation of users, customers or stores, SN Create log data for all important events in the system, including generator file creation and more.

  Optionally, policy management may allow: That is, the basic policy for power transmission for each day of the week, the power transmission policy specific to the weekend, for example, per hot spot where the hot spot is active from 8 am to 1 pm and from 4 pm to 7 pm Create time slot resolution for (or all hotspots in a store). Further, the policy may be executed at once for all hot spots per store, such as disabling all hot spots or enabling all. Optionally, when a hotspot is configured as “unavailable” for each policy, its status may be shown as a red LED color, for example, if it is “unavailable”.

It is noted that hot spot availability is greater than the advertised time.
Description of embodiment

  The systems and methods of the present invention described herein may not be limited in their application to the details of the construction and arrangement of components or methods described in the specification or illustrated in the drawings and examples. Be noted. The systems and methods of the present invention may enable other embodiments or may be practiced or implemented in various ways.

  Alternative methods and materials similar or equivalent to those described herein may be used in the practice or testing of embodiments of the present invention. Nevertheless, the specific methods and materials are described herein for illustrative purposes only. The materials, methods, and examples are not necessarily intended to be limiting.

  Thus, various embodiments may omit, substitute, or add various procedures or components as needed. For example, it should be understood that the methods may be performed in a different order than that described, and that various steps may be added, omitted, or combined. Also, aspects and components described in connection with a particular embodiment may be combined in a variety of other embodiments. It is also understood that the system, device, and software may be components of a larger system, individually or collectively, and other procedures may override the application, or otherwise modify the application. It should be.

  Here, distributed systems 100 and 100 ′ for assisting power transfer requirements and for providing power transfer to mobile devices using at least one location searchable using a power management software application. Reference is made to FIG. 1 and FIG. In accordance with this disclosure, the distributed system 100 of FIG. 1 provides external network connectivity and Internet access through each wireless power outlet 112. On the other hand, the distributed system 100 ′ of FIG. 2 provides external network connectivity to the wireless power outlet 112 via the local field gateway (s) 118.

  Power management software combines the status, user selection, and current location of the power storage unit of the electric mobile device to provide various power related recommendations and potential places to serve wireless power transfer It is noted that it provides device power storage management functionality that guides the user to the nearest power transfer location accessible in accordance with.

  FIG. 1 illustrates an external network connection and Internet access for each wireless power outlet 112 searchable by a power management software application that provides the electrical device with wireless power transfer technology and at least one location for wireless power transfer in accordance with this disclosure. 1 schematically represents a distributed wireless power management 100 for The distributed system 100 includes a power transfer component 110, a management server 130, a management database 150, a communication network 160, and a mobile communication network 170. The section indicated by “AA” in FIG. 1 represents the user's public space using the mobile device 120 ′ installed with the power management software application.

  Optionally, the distributed wireless power management system 100 includes a dashboard terminal 140.

  Optionally or in addition, each user in a public space denoted “A-A” uses an electric mobile device 120 ′ that is connectable via a social network, and data and information with other members of the social community. Allows sharing.

  The wireless power transfer component 110 includes two sub-components, and a wireless power outlet 112, optionally embedded in the surface 101, includes a primary inductor 114, such as a power source (not shown) and a smart phone 120 or tablet 122. Secondary inductors 116 that can be connected to electrical mobile devices, each connected to a load and can be coupled to primary inductor 114, allow wireless power transfer to the electrical mobile devices. The wireless power outlet 112 may alternatively be referred to as a hot spot (HS) and may further include an LED display operable to display an on signal / off signal / dimmer signal / fade-in-out signal.

  It is noted that the electric mobile devices 120, 122 may each have a unique identifier that may be referred to as a receiver identification (RxID). The electric mobile devices 120, 122 may be identified by the wireless power outlet 112 when the electric mobile devices 120, 122 and the wireless power outlet 112 are in proximity. The wireless power outlet 112 may have a unique identifier that may be referred to as a transmitter identification (TxID).

  Communication between the wireless power outlet 112 and the electrical devices 120, 122 may use the communication channel 115A to communicate between each other and optionally establish a credential exchange to allow power transfer. It is further noted that.

  The wireless power outlet 112 communicates with the communication network 160 via the communication channel 124A, enables Internet-based communication, may further communicate with the management server 130 via the communication channel 132A, and the management server and the management database are located on the same machine. Management server 130 may communicate with management database 150 using communication channel 152A as well, whether or not installed separately.

  Optionally, the wireless power outlet 112 may communicate externally using the cellular communication infrastructure 170.

  The communication process between the wireless power outlet 112 and the management server 130 may be operable to perform transmission of various periodic status and aperiodic events. Various events include TxID, RxID identification parameters, power transfer start, power transfer stop, service modification in some way, server authorization command, on / off command for power transfer abort or resume, charge balance Additional information such as status reception may be included.

  Terminal dashboard 140 (optionally, other types of clients such as electric mobile devices) may communicate with the application layer of management server 30 using communication channel 142A.

  It is noted that the wireless power outlet 112 may communicate with the electric mobile devices 120, 122 exchanging identification information and further send periodic status messages and aperiodic events to the management server 130. This type of communication uses wireless power transfer, but provides a more accurate location-based recommendation combined with user selection, in the event that any other positioning system is not operational. Provides an accurate indication of the current location.

  FIG. 2 schematically represents a distributed power transfer system 100 'for providing wireless power transfer services to electrical mobile devices and communicating externally via a local field gateway in accordance with the present disclosure. Distributed power transfer system 100 ′ includes two sets of wireless power outlets 112 located in Region A and Region B, a local field gateway 118, a management server 130, a management database 150, a communication network 160, and a mobile communication network 170. The section indicated by “A-A” in FIG. 1 represents the public space of the user using the mobile device 120 ′ installed with the power management software application.

  Optionally, the distributed wireless power management system 100 includes a dashboard terminal 140.

  Optionally or in addition, each user in a public space denoted “A-A” uses an electric mobile device 120 ′ that is connectable via a social network, and data and information with other members of the social community. Allows sharing.

  The section indicated by “AA” in FIG. 2 may represent a public space of a user using a mobile device 120 ′ installed with a power management software application.

  Optionally, the distributed wireless power management system 100 includes a dashboard terminal 140.

  Optionally or in addition, each user in a public space denoted “A-A” uses an electric mobile device 120 ′ that is connectable via a social network, and data and information with other members of the social community. Allows sharing.

  Communication between the power module 112 and the network management server 130 may be provided via the communication module 113. Variously, the communication modules 113A, 113B may be incorporated into the power module 112 and may provide services to the host power module alone. Alternatively, the communication module 113B may be incorporated into the field gateway 118B and may serve multiple connected power modules.

  The wireless power outlet 112 may be able to communicate with local field gateways 118A, 118B (collectively 118) wirelessly or using field Ethernet resources. The local field gateway 118 can access the communication network 160 through the communication channel 124A, enable the wireless power outlet 112 to send periodic status events and aperiodic events, and report the management server 130.

  Region A and Region B represent two different sets of wireless power outlets, and each wireless power outlet in the set is evented via the local field gateway 118, possibly according to the configuration configuration of the local field gateway 118 or the settings of the wireless power outlet 112 itself. Note that notification messages may be communicated. Optionally, the wireless power outlet 112 may be configured to function in a dual mode through the local field gateway 118 or to communicate directly with the communication network 160 to provide improved online functionality. Accordingly, the wireless power outlet 112 of the distributed system 100 'may be different from similar units of the system 100 of FIG.

  It is further noted that region A and region B may be, for example, separate rooms within the same site, or may represent separate facilities at different sites. In addition, a single gateway 118 may manage a limited number of wireless power outlets, such as six, and additional gateways may be required if the deployment requires more wireless power outlets. .

  Reference is now made to the block diagram of FIG. 3 representing a possible software module architecture for the distributed wireless power transfer system 100 ″.

  The distributed wireless power transfer system 100 ″ includes a wireless power outlet 112, a management server 130, a data repository 150, and a communication network (not shown). Optionally, the distributed wireless power transfer system 100 includes a dashboard terminal 140 and may further include a business entity machine of a third party vendor (not shown).

  It is noted that for clarity, the electrical device and associated software application modules have been deleted.

  The wireless power outlet 112 may include a software module having submodules such as an interface 212A, a near field communication module 212B, and an identification module 212C. Communication with the management server may use the communication channel 214 using Internet connectivity or through a local business gateway (not shown).

  The management server 130 may include the following modules: an interface module 232, a report generation module 233, and optionally an authentication module 234, a monitoring module 235, and an encryption module 236.

  The data repository 150 includes a database (DB) interface module 252. The DB interface module may be subdivided into several submodules if the data repository consists of several databases or if there are additional secondary data sources.

  In addition, the communication module 262 allows communication to be established between various components. The communication module is between various components such as communication between the wireless power outlet unit and the electric mobile device, communication between the wireless power outlet and the management server, and communication between the dashboard terminal and the management server. Various communication techniques may be used to enable communication.

  The use of the term “communication module” implies that in the communication module section, the components or functionality described or claimed as part of the communication module described below are all comprised of a common package. It is noted that there is no.

  Optionally, if there is a third party business entity machine, the business entity machine needs to be installed with a business software module 272 that can be operated to interface with the management server 130 accordingly.

Optionally, if a dashboard terminal is present, the dashboard terminal needs to be installed with an appropriate web interface module 242 to allow access and visualization of the distributed system, for example.
Communication module

Communication modules reflect various aspects of communication requirements between components of a wireless power transfer distributed system and may differ while responding to different communication needs of components. For example, the communication needs between an electric mobile device and a wireless power outlet expose different functionality and technologies compared to the communication needs between the wireless power outlet and the management server. Thus, when referring to a communication module, it is intended to clarify various aspects and communication techniques that may be associated with a particular interaction.
Communication with the management server

  Optionally, the electric mobile device may have a wireless LAN / WAN communication unit that may not necessarily match the LAN / WAN transmission unit of the wireless power outlet. Further, the electric mobile device may include a near field communication module that can communicate with the module on the wireless power outlet.

The management server or control server may communicate with the wireless power outlet, the electric mobile device, or both. The communication channel may be mediated by a wireless access point, cellular network (FIG. 1), wired network, etc. that may provide an Internet Protocol (IP) connection to at least one of an electrical device or a wireless power outlet. It is further noted that optionally, the communication channel to the wireless power outlet may be mediated indirectly via the electrical device and the close communication module. Similarly, the communication channel for an electrical device may be mediated indirectly via a wireless power outlet.
Tx-Rx communication

  Each electrical device may have a unique identifier in the system that allows its recognition, which may be referred to as a receiver identification (RxID). RxID may be a MAC address. The management server may store related information such as power transfer related data, billing information, and user credits in addition to RxID.

  Where appropriate, the wireless power outlet may have a unique identifier in the system that allows its recognition, which may be referred to as transmitter identification (TxID).

  For exemplary purposes only, possible methods for providing access to electrical power for public space electrical devices are presented below. The method may allow a user to transmit power from a wireless power outlet or charge an electrical device such as a mobile phone, tablet, etc., and the power supplier manages power transfer while collecting power transfer related information You can do it.

  A user may install an electrical device or connect the electrical device to a wireless power outlet. For example, an inductively enabled device may be installed at a wireless power outlet. Alternatively or additionally, the power source may be conductively connected to the electrical device.

The power access point may detect an electrical device connection. For example, a wired connection may be detected by detecting a load, and a wireless connection may be detected using various remote sensors such as a hall sensor, an analog ping method, and the like.
Initial authentication / handshake

The wireless power outlet may allow power transfer for a predetermined time T _free during which user credentials may be authenticated.

  Optionally, the wireless power outlet may send a random pattern to the device via close communication. The wireless power outlet may further send the same pattern to the control server via the WAN / LAN connection.

  For example, a software application running on the electrical device may be operable to receive the pattern and relay the pattern along with the user identification token to the management server.

  Variously, the management server and the electrical device may exchange multiple messages to complete user authentication.

  Optionally, the wireless power outlet may provide credentials that initiate the registration process and allow access to the management server upon initial interaction with the management server to determine initial setup. Initial authentication may be used for the management server's consent to manage the outlet Tx, as well as the identity of each side for any additional communications, ie the consent for the identity of the outlet Tx and the identity of the management server. It is also noted that.

  The management server may thereby be able to associate a particular wireless power outlet with a particular electrical device. If the user is deemed authorized to use the service, the management server may send a confirmation signal that allows the wireless power outlet to continue providing service to the electrical device. If required, the confirmation signal may define a specific period during which the service is granted or may send a disconnect event at the end of that period.

  Where appropriate, the management server may additionally or alternatively define multiple levels of service, eg expressed in units of current provided to different users. As an example, a paying user may be allowed to access full power supply functions, perhaps up to 20 watts and so on. On the other hand, users who do not make payments may have enough access to charge only low-power devices or perform trickle charging of a fully depleted battery, for example limited access to 0.5 watts. May be provided.

  During operation, the wireless power outlet may be operable to receive an operation signal from the management server. Depending on the received operational signal, the wireless power outlet may be operable to perform various actions such as continuing to provide power, aborting power transfer, modifying the service in some way, and so on.

As noted herein, various methods for enabling intimate communication between an electrical device and a wireless power outlet may be implemented.
Voice communication

  In one particular embodiment, the close communication channel between the device and the power access point has a specific audible band, such as between 20 and 2 kilohertz, or between 300 and 20 kilohertz, for example. It may be based on an audio signal that is used and sensed through a microphone of the electrical device. The audio signal may be emitted from an audio emitter such as a speaker associated with the wireless power outlet. Many electrical devices, such as cell phones, may have a microphone and software applications may have access to the microphone.

  It is noted that supplying power to the microphone unit itself may require power. As a result, a software application running on the electrical device may activate the microphone only if a “charge-connect” event is detected in the system. Thus, upon device detection, the wireless power outlet may implement initial power transfer to supply power to the microphone. After a short interval, the identification signal may be transmitted via an audio signal.

The audio signal may include additional tones not related to the communication pattern that may mask the random pattern being communicated. For example, the voice identification signal may be masked by a connection tone that serves to provide the user with an indication that a connection has been made.
Data-over-coil (DOC) communication:

  Alternatively or additionally, a close communication channel may be provided by a wireless power outlet that alternately activates power transfer to the electrical device. Power supply alternations are detected by most electrical devices as power transfer connection and power transfer disconnect events communicated to the application layer on these devices.

The switching pattern may be coded with an identification signal such as a random pattern. The wireless power outlet may need to perform this switching at intervals that are sufficiently spaced that the electrical device can detect and report power transfer connection and power transfer disconnection events to the application level.
Bluetooth and NFC

  Still other embodiments may use Bluetooth or near field communication (NFC) to achieve a close communication channel. These could be combined with basic power signals to trigger their activation and thereby conserve power.

  In various embodiments of this system, the LAN / WAN interface of the device may be a WLAN connection or a cellular 2G / 3G / 4G connection. Connecting to a WLAN or cellular access point may include manual or automatic insertion of user credentials. In this case, the information may be communicated to the management server to validate user identification. Information provided to grant access may be stored by the device application and later provided directly to the management server.

In addition or alternatively, the LAN / WAN connection of the wireless power outlet may be achieved via a charged device. The wireless power outlet may encrypt messages to the management server and deliver them to applications on the electrical device via a close communication channel between them. The application may then send a message to the server via its LAN / WAN connection.
Database interface

  The management server uses an application program interface (API) to allow various component applications to access the management server using more applicable access to data stored in the database (s). May provide. Direct access to the database from the management server may use a command shell that may be sold in combination with almost any database selected.

  Data can be documented in tables (relational databases such as Oracle, Informix, Microsoft SQL Server, MySQL, NoSQL, and more), objects (object-oriented databases), or documents / files (XML-extensible markup language, etc.) Stored in an oriented database).

  The same physical machine or a separately installed database may be accessed through a common database interface such as Sequence Query Language (SQL).

  Alternatively, the database may be accessed by an object-oriented API and provide a database abstraction API to create, retrieve, update, and delete objects, or to use XML-based APIs and the like.

  It is noted that each API may be implemented in a variety of computer languages such as C, C ++, C #, Java (registered trademark), JavaScript (registered trademark), Python, and the like.

It is also noted that interaction with the database may be transaction based and allow a set of commands to be configured. For example, something between the “transaction start” method and the “transaction commit” method is not executed until “transaction commit” is called if no exception occurs. Change rollback and undo actions use the “transaction rollback” method to bring the database back to its original state if there are problems even though many changes may have been made to the database tables. You can bring it back.
Encryption module

  The encryption module may be responsible for encrypting instructions from the server to the wireless power outlet and is further delivered to the charged device that relays the instructions back to the wireless power outlet via a close communication channel. It's okay.

  Where applicable, encryption may only allow the server and wireless power outlet to encrypt / decrypt the message, but will prevent the charged device from modifying or creating a legitimate message. Thus, message transfer from the server to the wireless power outlet may require the presence of a two-way close communication channel. In the case of audio signals, this may be accomplished by using a device speaker and including a microphone in the wireless power outlet.

  Additionally or alternatively, a bi-directional power-based signaling scheme may be achieved by modulating the device load at the wireless power outlet. Many devices do not allow the application to directly control the charging current or system load being used, so to change the load, a modulated screen illumination backlight for LCD and direct pixel activity for OLED It may be necessary to use some indirect techniques such as

  It is further noted that the wireless power transfer system may provide additional options for close communication channels.

  Reference is now made to the block diagram of FIG. 4 representing selected actions of a possible procedure for providing an administrator with administrative functionality for monitoring and controlling deployment of a wireless power outlet configuration in the field. Possible management procedures may include provisioning (450) data, remote maintenance 460, policy management 470, and remote health check 480.

  Management server 130 may support direct interaction via network 160 with each remote wireless power outlet 112 at a particular site, or communicate with field gateway 118 to control each wireless power outlet 112. It is noted that Although only one gateway 118 is described for illustrative purposes only, it will be understood that multiple gateways 118 may be controlled by the common management server 130.

  The provisioning 450 procedure may include communication with a provisioning software application of the electrical device to provide a user with a provisioning policy when communicating with a wireless power outlet at a location. The provisioning 450 procedure may further provide reporting functionality, mapping of power transfer locations according to electrical device locations, and the like. The provisioning software application of the electrical device may be used for paid power transfer to allow monitoring and controlling the device's power charging.

  The remote maintenance 460 procedure may provide remote management of wireless power outlets, including remote stop / start 461A, remote restart 462A, remote software update 463A, and visual interface such as LED indicators or other such sound generator speakers. Remote user display 464A, such as an audio interface, etc. may be included.

  The power management policy management unit 470 provides the functionality to determine various sets of policies for controlling the wireless power outlet when interacting with the power receiver of the electrical device. The power management policy management 470 procedure may generate a variety of power management policies that may be appended to a single control policy. Policy management unit 470 may include device type policy 471A, service type policy, and power transfer policy 473A. Policy management 470 may further include various dynamic policies 474A, such as real-time optimization of power consumption, real-time optimization of battery health, etc., for example, for user selections that suggest meeting friends based on real-time parameters. Site site traffic may be further controlled by communicating with members in the social space to add more traffic to the site, such as by advertising a business that is close to the features involved.

  A remote health check 480 that tests the remote wireless power outlet may be used to test the accessibility and operability of the outlet unit and whether the outlet is reachable across the network. In addition, the process analyzes the latency of the connection and determines the network speed that may also be presented to the system administrator. Such a health check may be triggered on-demand for a specific wireless power outlet at a specific site and test its status, or when the network system is presented to the management server console at the time of an administrator communication request Sequentially triggered for all listed potentially operable wireless power outlets in the network may provide a variety of related parameters including the status of the wireless power outlet itself.

  Accordingly, the health check procedure 48 may send a control signal to the remote wireless power outlet and wait for a response in time.

  It is noted that the provisioning procedure 450 may communicate with the wireless power outlet and allow more accurate data for provisioning software applications such as location. Information regarding the location of the Hotspot may be associated with the TxID of the wireless power outlet. Such location information may be programmed into Hotspot at the time of installation, providing very accurate location information that may be more accurate than that provided by other methods such as GPS or antenna triangulation. It's okay. If the power provisioning software is an application configured for a mobile device, Hotspot may send information about itself (eg, TxID, location, etc.) to the device, which then forwards the information to the application. The application may further identify the location using GPS, antenna triangulation, indoor positioning methods, etc. Such data may be transmitted to the provisioning layer of the management server via a wireless power outlet.

  Various policies and other business-related matters of the policy management procedure 470 may be centrally stored in the database of the management server (130, FIG. 1), from the power supply policy of the service supplier and / or provider, from the end user's perspective. It is further noted that various policies, arrangements, offers, etc. of public entities that may be relevant may be included.

  The result of the set of procedures is to reduce or increase the number of possible options for managers or users to obtain addresses and opening hours, to locate public utilities on the map, to obtain driving directions Various actions such as adjusting search radius, filtering by public entity brand, ranking social space members, number of hotspots in specific public entities, coupons and promotions, selling receiver accessories, etc. You may create options that make it possible.

  Reference is now made to FIGS. 5A-5D which show various schematic diagrams accessible on the management console, and FIGS. 5A and 5C show schematic diagrams of possible power transfer network views of various architectures. 5B and 5D show a detailed display view of the selected device, such as an icon representing the gateway 118 or an icon representing the wireless power outlet 112.

  Throughout the description of FIGS. 5A-5D, whenever an element is referenced within the view of an element that is accessible on the management console, such as a gateway, wireless power outlet, management server, etc., these terms are represented by their icons. Note that it refers to the display.

  The management server's power management software may provide outlet power management functionality in various aspects such as wireless power transfer and provisioning, remote maintenance, policy management, unit health checkups, and even in various system architectures It is noted that. Power management may further interact with the database to store relevant data and deliver the required functionality and services, or may be integrated within the same physical machine.

  Accordingly, the configuration of FIG. 5C represents a system architecture that displays a view accessible on the management console, whereby all wireless power outlets are centrally managed by at least one gateway at a particular site. Such a view may be accessible by selecting an icon representing the gateway 118 of FIG. 5A. Optionally, the configuration of FIG. 5C may display a stand-alone view that represents a system architecture in which all wireless power outlets are centrally managed by at least one management server 130.

  FIG. 5A schematically illustrates a distributed wireless power transfer network view 500 accessible on the management console, optionally displayed on the management console, with the gateway managing several wireless power outlets for a particular site. Provides an overview of the deployment that will be performed. The distribution diagram 500 includes a central management 130, an associated dashboard terminal 140 (management console), and a communication network 160 to allow the management server to communicate with at least one field gateway 118.

  Such distributed display allows an administrator to get an overview of the overall network under his control, optionally selecting other views, selecting specific areas of the display, selecting gateway 118, Analyzing various other aspects of the network by displaying its status and information in a pop-up window 118A, or selecting a gateway 118 and opening a subnetwork of wireless power outlets managed and monitored by that gateway You may do it. Viewing the wireless power outlet sub-network may further allow actions to control and monitor the particular outlet 112 of FIG. 5C.

  It is noted that a particular site may include one or more gateway devices 118, each controlling one or more wireless power outlets.

  FIG. 5B is a schematic diagram of a possible oil summary view 118A accessible on the management console of field gateway 118, whose controlled wireless power outlet is distributed in FIG. 5A to present detailed gateway information. It can be accessed by selecting a field gateway from diagram 500 and selecting the appropriate menu option, such as opening or displaying. Optionally, this view may be accessible by double-clicking the field gateway icon display to receive detailed information in a pop-up window, for example. The summary view 118A accessible on the management console may include a gateway ID field 502B, a location field 504B, administrator relationship information 506B, a table of contents with a heading of device id 508B, a status 510B, a policy 512B, and more. A particular row 514B represents relationship data for a particular wireless power outlet and an activation button open 516B.

  Optionally, clicking on the activation button Open 516 when selecting row 514 opens a pop-up window that displays detailed information for the selected row 514, such as 112A in FIG. 5D, and the associated information shown in FIG. 5C. Details of the wireless power outlet 112 may be provided.

  FIG. 5C schematically represents a partially distributed wireless power transfer network diagram 500 'accessible on a management console where a single field gateway controls all wireless power outlets for a particular field. Provide a possible overview of successful field deployments. Field distribution diagram 500 ′ includes field gateway 118, wired or possibly wireless communication network 160, allowing the gateway to communicate with at least one wireless power outlet 112.

  It is noted that a site may have several wireless power outlets that require more than a single gateway to control and monitor the site.

  Field gateway network display 500 'allows a variety of monitoring and control operations to be performed on a single selected wireless power outlet, or provides functionality common to outlets where multiple selections are selected. It is further noted that it may be possible to provide. Such an action may allow an outlet to be selected to obtain a summary view of the device, and may further enable an administrator action as shown below in FIG. 5D.

  FIG. 5D is optional on the management console by clicking the open action button 516 when the associated power outlet unit row 514 of FIG. 5C is selected, for example, to present detailed information about the outlet. 12B is a schematic representation of a possible status and summary detail diagram 112A of a wireless power outlet 112 that is selectively accessible. Optionally, this figure may be accessible by double clicking on the wireless power outlet 112 shown in FIG. 5C to receive detailed information in a pop-up window. Summary diagram 112A may include a device ID field 502D, a device type field 504D, a status field 506D, a location field 508D, a software release field 510D, and a policy field 512D. The display 112A further includes a “report” action button 514D, a “maintenance” action button 516D, an “add” action button 518D, a “policy” action button 520D, a “test” action button 522D, and administrator relationship information 524D.

  If desired, a “Report” action button 514D may allow the generation of a set of reports related to wireless power outlets, such as usage over time, idle time, failure events, maintenance history, and the like.

  As needed, the “Maintenance” action button 516D may allow maintenance operations such as restarting the selected wireless power outlet, installing an updated software module, or updating a currently executing policy.

  If necessary, the “policy” action button 520D may enable a policy-related operation such as a local setting change. Optionally, this policy adjustment may be maintained via maintenance action button 516D.

  If desired, a “Test” action button 522D may allow a health check test to be performed for a remote selected wireless power outlet.

  If desired, an “add” action button 518D may allow access to additional action buttons such as various administrator setting options, user management, provisioning related activities, and the like.

  Reference is now made to the flowchart of FIG. 6A representing selected actions showing a possible method 600A for performing a system check of a remote wireless power outlet system in a network deployment. Such a health check may be triggered on-demand for a specific wireless power outlet at a specific site to test its status, or when an administrator communication request is made, the network system will connect to a management server console in the network. When presented, all listed potentially operable wireless power outlets may be triggered sequentially to provide a variety of related parameters including the status of the wireless power outlet itself.

  The status of the wireless power outlet may change through its operation during a specific request, such as a restart when a software update is uploaded to the outlet unit, or may be in a fault status due to some malfunction of the outlet unit It is noted that.

  It is further noted that the network may allow control of power provision in public spaces such as restaurants, coffee shops, airport lounges, trains, buses, taxis, sports stadiums, halls, theaters, cinemas and the like. Therefore, the operability of each outlet in the network is required. In addition, such systems provide a platform for efficient power supply services that are boosted with remote monitoring combined with maintenance functionality (remote restart, remote software updates, etc.) to improve efficiency and availability Therefore, it is necessary to enable tracking of individual wireless power outlet units.

  For example, the method 600A for system health check may include activities automatically performed by the management server, if so configured, or may be triggered upon a specific administrator request. The wireless power outlet is expected to respond to the communication request within the time limit, verify its satisfactory health status, and reflect an “on” status. No response implies a timeout situation and may present the wireless power outlet status as “off”. For example, if the response is slow, the status of the wireless power outlet may be referred to as “failure”.

  It is noted that the remote wireless power outlet health check is used to determine if the remote outlet is reachable across the network. In addition, the process analyzes the latency of the connection and determines the network speed that may also be presented to the system administrator.

  The process begins with a request 610A to establish communication with the target wireless power outlet, followed by a timer start 611A to allow response time measurement, and a communication signal is then transmitted to the remote selected wireless power outlet 612A. When the communication signal is received 613A, the wireless power outlet then responds with the communication signal 614A, and when the communication signal transmitted from the wireless power outlet is received at the management server, the timer is stopped 616A, eg, “ON”, Response time is analyzed 617A to allow display of current outlet unit status such as “off”, “failure”, and the like. If appropriate, the operation may be repeated as set, e.g., four times to allow for an appropriate display, and the cycle may be repeated further at certain time intervals, or may be repeated continuously. The time interval for repeated methods or measurements may use default settings or may be set by the system administrator.

  It may be noted that the status display during network configuration of the management console can be enhanced with additional text effects, color effects, flashing effects, and the like.

  It is further noted that technically, such a process may use a dedicated communication protocol, ie, a known communication tool such as Internet Control Message Protocol (ICMP) or “ping”. Optionally, “ping” is a computer network tool used to test whether a particular host is reachable across an IP network.

  Reference is now made to the flowchart of FIG. 6B representing selected actions illustrating a possible method 600B for performing system software updates for remote wireless power outlets in a network deployment. Such software updates may be triggered on demand for a specific wireless power outlet at a specific site, for example to solve an outlet unit problem, or listed on the site or all of the network by a system administrator. , May be performed sequentially on operable wireless power outlets. Optionally, after a wireless power outlet software update, the device needs to be restarted to shut down the previous version and perform the new update. Where appropriate, previous software versions may be stored in the wireless power outlet storage unit for backup and provide restore functionality.

  It is noted that installing software updates may be required to correct known faults or may be required to take advantage of new software features.

  Individual wireless power to improve efficiency and availability by providing a platform for efficient power supply services combined with maintenance functionality (remote restart, remote software updates, etc.) and boosted by remote monitoring It is further noted that there is a need for a system that enables outlet unit tracking.

  System software update method 600B includes activities performed by the management server. These actions may be triggered automatically when configured as such, or alternatively or additionally, actions may be triggered upon specific administrator requests for a single unit, or according to multiple selections A set of software updates may be installed. Optionally, the wireless power outlet may reboot after storing the software update package and execute the post-boot package depending on the nature of the software update. Such an option may be specifically set for each software update.

  The process begins with a request 610B to establish communication with the target wireless power outlet, followed by a 611B step of creating a software update package, then the software package is sent to the remote outlet unit 612B, and the software package is received at the remote outlet unit 613B. Optionally, stored in that storage unit, creating a backup copy of the current software package 614B, followed by sending a response signal 615B indicating the current status to the management server, upon receipt of the send response 615B from the remote outlet unit, The management server continues with a restart command sent to the remote outlet unit 617B, and a device restart occurs 618B. Thus, when the outlet unit restarts, a new software package may be executed 619B to complete the installation process, and upon completion, the outlet unit sends a display message to the management server 620B, software for a particular outlet unit. Notify that a new version of has been updated. This communication is then received 621B by the management console.

  It may be noted that various outlet units may have different software versions depending on the device type and its operability.

  Updating an existing power management policy installed on a wireless power outlet is similar to the steps described in FIG. 7B herein, ie when installing a new power management policy on a remote outlet unit. It is also noted that the steps of storing the new policy in a temporary location, restarting the outlet unit, and activating the new power management policy to become the active control policy may be performed.

It is further noted that having an update policy installed at the remote wireless power outlet is essential to meet business problems.
Network API

  The deployment of a wireless power transfer infrastructure may enable providing convenient access to wireless power transfer at public sites. Accordingly, a smart and manageable global wireless power transfer network is disclosed that may allow for a wider deployment of wireless power equipment for mainstream technology and network architecture and associated API standardization possibilities.

  Reference is now made to the system diagram of FIG. 7A showing a network architecture representation of a wireless power transfer system 700A having various application interfaces.

  Network architecture representation 700A, ie entities and associated application interfaces, to facilitate standardization of application programming interfaces (APIs) between various entities while retaining the flexibility to accommodate innovative approaches. It is particularly noted that it may be used.

  A network architecture representation 700A includes a first field architecture 702A, a second network architecture that can be connected to a certified device manufacturer (PCDM) 706-1 and a wireless charging spot provider (WCSP) 708-1 through a cloud network service (PCS) 704-1. Field architecture 702B. The first field architecture 702A and the second field architecture 702B may further include a variety of network entities.

  Illustratively, in this particular embodiment, the first field architecture 702A is a radio that is connectable to at least one radio power transmitter (Tx) 716A entity that communicates with at least one transmitter gateway (T-GW) 718A entity. A power receiver (Rx) 714A may be included. The wireless power receiver 714A entity may be further connectable to a user control function (UCF) 712A entity. The second field architecture 702A includes a wireless power receiver 714B, a wireless power transmitter 716B, and a transmitter gateway (T-GW) 718 entity, perhaps in a similar network architecture with a different number of network entities depending on the field service capability. It's okay.

  Where appropriate, a wireless power receiver is probably the entity that receives power to charge or supply power to the electrical client device.

  Where appropriate, a wireless power transmitter is an entity that transmits power. Optionally, the wireless power transmitter may be operable to support a single power receiver and multiple power receivers simultaneously.

  The term T-GW refers to a transmitter gateway function that connects one or more wireless power transmitter entities to the Internet and acts as an aggregator for multiple wireless power transmitter devices located in the field.

  The term UCF refers to a user control function, ie a logic function that provides the user with an interface to a charging service. Thus, when appropriate, the UCF can be operated to provide services to the user such as wireless charging spot location search, device activation, service subscription, status monitoring and the like. Optionally, the UCF may be located with the power receiver or may be implemented in a separate device.

  The term PCS refers to a cloud service, a centralized system that provides cloud service management for a wireless power transfer network.

  The term PCDM refers to a certified device manufacturer.

  The term WCSP refers to a wireless charging spot service provider that ranges from a large provider that controls wireless charging spot deployments across multiple borders to a single wireless charging spot coffee shop.

  It is particularly noted that the various network entities can be connected via an associated application programming interface API that is applicable to interface any two connectable network entities as described below. The

  The network architecture representation 700A includes an RX-TX API interface P1 between the radio power receiver and the transmitter, an RX-UCF API interface P2 between the UCF and the radio power receiver, and a TX-TGW API between the transmitter and the transmitter gateway. Interface NP5, TGW-PCS API interface N1 between transmitter gateway and cloud server or network management server, UFC-PCS API interface N2 between cloud service or network management server and user control function entity, cloud service and wireless PCS-WCSP API interface N3 with charging spot service provider, cloud service and certified manufacturer, wireless Including PCS-PCDM API interface N4 between UCF API interface S1 of a UCF placed with Wareshiba.

  It is noted that the RX-UCF API interface P2 may not be required depending on the type of radio receiver, if appropriate, allowing support for embedded UCF functions as well as after-service add-ons. Therefore, the P2 API may be technology-selective (technology agnostic).

  It is further noted that the TX-TGW API interface NP5 may be an open interface left in the vendor specific implementation.

  TGW-PCS API interface N1 provides initial provisioning and initialization of wireless power transmitters and T-GWs, continuous usage reporting between two entities, and continuous provisioning and policies for wireless power transmitters connected to T-GWs It may be an IP-based interface that supports configuration. Further included is support for admission control and change management for the wireless power receiver device combined with control of the wireless power transmitter. An example message for the TGW-PCS API interface N1 is presented below.

  The UCF-PCS API interface N2 may be an IP-based interface carried by an OOB bearer service of UCF (cellular WLAN or the like). Optionally, interface N2 may be carried via a wireless charge receiver and a wireless charge transmitter. The UCF-PCS API interface N2 may support charging and service subscription provisioning including billing information, charging status reports, and charging spot location data if required. In addition, target value messaging from service providers via PCS may be further supported. An example of a UCF-PCS API interface N2 message is presented below.

  PCS-WCSP API interface N3 provides initial and continuous provisioning and monitoring of its network entities (transmitters and T-GWs), authorization policy settings for power receivers on different power transmitter devices, and different power transmitters. It may be an IP-based interface that supports usage information combined with statistics at the device and the power receiver device. PCS-WCSP API interface N3 further supports power receiver subscription handling (support for centralized or pass-through models for processing subscriptions and billing information) and targeted messaging settings based on policy and usage To do.

  The PCS-PCDM API interface N4 may support power receiver identifier (RXID) registration and authorized power transmitter identifier (TXID) registration. The interface may allow a certified OEM / ODM to pre-register the device with the PCS. Registration may provide company and device details as needed via a registration form.

  The UCF API S1 internal interface may provide a set of S / W APIs to a specific OS that allows the application layer to access the power receiver information exposed via the RX-UCF API interface P2. For example, in the case of Android, these may be APIs for Dalvik applications that access RXID information and power receiver registers, among others. The internal interface may provide an API for applications such as Java to access power receiver resources on the platform.

  As a non-limiting example provided for illustration only, the interface may be described for an Android OS platform, and those skilled in the art will envision other examples. With respect to the Android interface, most of its applications are written in Java® and no Java® virtual machine is used, rather a separate API, the Dalvik API, is used. Similar APIs may be defined for other mainstream OSes in the home appliance space.

  The API may allow UCF application development extracted from a specific hardware implementation.

If the existing functionality in Android may include “public static final int BATTERY_PLUGGED_WIRELESS”, the current API may provide additional functionality as follows.
A final static String getPMAReceiverID () that may return the ID of the PMA receiver
-The value of the "arg" register of the host controller interface may be retrieved, final static inc getHCIreg (int arg)
Val may be set in the “arg” register of the host controller interface (R / W register) void setHCIreg (int arg, int value)
API example

  The UCF-PCS API interface N2 may be implemented using JavaScript® object notation (JSON) over the UCF-to-PCS HTTPS link. Establishing an HTTPS session may include mutual authentication to enable client identity validation.

  Examples of various communication message types that can be communicated between the UCF and the PCS as needed include:

  A GET_PACKAGES message that may be sent to the cloud service to retrieve a list of packages (including daily passes) available for purchase. Such purchases may be enabled via online marketplaces such as Apple App store, Google Play and the like.

  An ADD_ALLOWANCES message that may be sent to the cloud server once the package has been purchased, whereby the client sends purchase information including receipt of validation and adds the day path from which the service was purchased.

  A REDEEM_GIFT_CARD message that may be sent to the cloud server to send a gift card ID so that the server fulfills the daily pass to the associated account.

  A GET_ALOWANCES message that may be sent to the cloud server to retrieve the number of daily passes for the associated account and the free daily minutes that this account is eligible to receive.

  A GET_NEARBY_LOCATIONS message that may be sent to the cloud server to retrieve the location closest to the indicated location.

  For example, an ADD_ACCOUNT message that may be sent to the cloud server to create an unnamed account for the client, identified by a unique identifier associated with the hardware.

  A REGISTER_ACCOUNT message that may be sent to the cloud service to add personal information to the account.

  A PUSH_ID message that may be sent to the cloud server to send the ID added to the account used to send the push notification to the client to the server.

  ASSOCIATE_RX message that may be sent to the cloud server to add the receiver to the user account.

  DISASSOCIATE_RX message that may be sent to the client server to remove Rx from the associated account.

  A RETRIVE_RX message that may be sent to the cloud server to retrieve a list of receivers associated with a particular account.

  A GET_COUNTERSY_CUSTOMER message that may be sent to the cloud server to retrieve the free wireless charge minutes sponsored by the customer.

  The following example provides a JSON message format for querying the location of the nearest charging spot.

  The GET_NEARBY_LOCATIONS message helps to locate a nearby field location that provides a wireless power charging service. Thus, the UCF may provide data about the device location to the cloud server simultaneously with other related parameters.

  The GET_NEARBY_LOCATIONS message may include data regarding a license key, which is a key provided by the server authorizing this request.

Other parameters of the “Get Nearby” message may include various parameters such as:
“LICENSE KEY” parameter to provide the license key of the user of the current device,
A “MESSAGE_TYPE” parameter for providing a message name such as “GET_NEARBY_LOCATIONS”;
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “LATITUDE” parameter to provide the current latitude of the current device,
A “LONGITUDE” parameter to provide the current longitude of the current device,
A “NUMBER OF RESULTS” parameter to provide the maximum number to the nearest site sent in response,
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
Format [“SBX”, “CBTL”, “MCD”,. . . , “*”] “CUSTOMERS” parameter to provide a list of chains to filter the resulting list. The value is an acronym for the chain and “*” is a wildcard.

The GET_NEARBY_LOCATIONS response may include multiple sets of various data response parameters for the “Get Near Location” message as follows.
A “MESSAGE_TYPE” parameter for providing a message name such as “GET_NEARBY_LOCATIONS”;
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “LOCATIONS” parameter that may include an array of sites to provide a list of sites that are filtered according to requirements, as defined below
For each entry in the list, the “ARRAY OF VENUES” parameter to provide to the nearest location array with the following parameters:
"STORE" parameter for providing the name of the store such as "134 5th AVENUE",
・ Latitudinal value of “LATITUDE” of stores such as 40.3878952 ・ Longitude latitude value of stores such as −73.991988 ・ Distance from required location such as “DISTANCE” and X (meter) ・ CUSTOMERS, “SBX -Chain acronym (may represent Starbucks)-The value of the chain acronym to which this site is affiliated

GET_NEARBY_LOCATIONS, eg, all messages may share a common standardized header. For example, a request message for obtaining a nearby charging spot location may have a header of the following form:

Similarly, a response message for obtaining a nearby charging spot location may have a header of the following form:

  The message body itself may follow a similar standard, for example, where applicable. That is, the body of the HTTPS message delivered to the network server may contain several concatenated messages of the JSON array, and the array contained messages for both the power module (or wireless power outlet) and the communication module. Different types of API messages may be included.

ＧＥＴ＿ＮＥＡＲＢＹ＿ＬＯＣＡＴＩＯＮＳ応答はメッセージフォーマット（ヘッダ削除済み）をとってよく、パラメータの複数のセットが、複数の近くのホットスポット場所を示す共通の見出しの下に提供されることに留意されたい。

For example, the message body of GET_NEARBY_LOCATIONS may include a plurality of messages as follows:

Note that the GET_NEARBY_LOCATIONS response may take a message format (header removed) and multiple sets of parameters are provided under a common heading indicating multiple nearby hotspot locations.

  The GET_PACKAGES message may retrieve a list of packages or a set of daily passes available for the user to purchase.

The parameters of the “GET_PACKAGES” message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “GET_PACKAGES”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;

The response to the “GET_PACKAGES” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “GET_PACKAGES”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.
A “COST” parameter indicating the cost of the related package.
A “DAY_PASSES” parameter indicating the number of day passes provided in the relevant package.
“FREE_PASSES” parameter indicating the number of free paths provided in the related package.

は、以下の応答を引き出してよい。

For example, “GET_PACKAGES” message:

May elicit the following response:

  The “ADD_ALLOWANCES” message sends purchase information associated with the purchase package including validation receipt, and the service adds the purchased day path.

The parameters of the “ADD_ALLOWANCES” message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “ADD_ALLOWANCES”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
・ "TRANSACTION_ID" parameter,
・ "RECEIPT" parameter,
・ "ACCOUNT_ID" parameter,
A “PACKAGE” parameter indicating the ID associated with the purchased package;

The response to the “ADD_ALLOWANCES” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “ADD_ALLOWANCES”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.
・ "ALLOWANCE_ID" parameter,

は、以下の応答を引き出してよい。

For example, an “ADD_ALLOWANCES” message:

May elicit the following response:

  The “REDEEM_GIFT_CARD” message may send a gift card ID so that the server will fulfill the daily pass to the account.

The parameters of the “REDEEM_GIFT_CARD” message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “REDEEM_GIFT_CARD”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
・ "GIFT_CODE" parameter,
・ "ACCOUNT_ID" parameter,

The response to the “REDEEM_GIFT_CARD” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “REDEEM_GIFT_CARD”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.
The “ADDED_DAYS” parameter indicates the number of days to be added to the allowable period.

は、以下の応答を引き出してよい。

For example, a “REDEEM_GIFT_CARD” message:

May elicit the following response:

  The GET_ALOWANCES message may derive the number of daily passes available for a particular account and the daily free minutes that the account is eligible to receive.

The parameters of the “GET_ALOWANCES” message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
"MESSAGE_TYPE" for providing a message name such as "GET_ALOWANCES",
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
・ "ACCOUNT_ID" parameter,

The response to the “GET_ALOWANCES” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “GET_PACKAGES”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
・ "ACTIVE_UNTIL" parameter,
・ "ACTIVE_DAYS" parameter,
・ "DAILY_FREE_MINUTES" parameter,
・ "COUNTERSY_OF" parameter,
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.

は、以下の応答を引き出してよい。

For example, “XXX” message:

May elicit the following response:

  The ADD_ACCOUNT message may create an unnamed account for the client identified by a hardware related unique identifier.

The parameters of the “ADD_ACCOUNT” message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “ADD_ACCOUNT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
・ "ACCOUNT_TYPE" parameter,
“DEVICE_ID” parameter.

The response to the “ADD_ACCOUNT” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “ADD_ACCOUNT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.
-“ACCOUNT_ID” parameter.

は、以下の応答を引き出してよい。

For example, “ADD_ACCOUNT” message:

May elicit the following response:

  The PUSH_ID message may send an OD added to the account used to send a push notification to the client to the server.

The parameters of the PUSH_ID message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “PUSH_ID”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
“ACCOUNT_ID” parameter, and “PUSH_ID” parameter.

The response to the “PUSH_ID” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “PUSH_ID”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols, and a “STATUS” parameter to provide additional operational information or errors Where this parameter may take a value from 0 to 255 that can be interpreted according to the list of error codes outlined below.

は、以下の応答を引き出してよい。

For example, “PUSH_ID” message:

May elicit the following response:

  The ASSOCIATE_RX parameter may add a receiver to the account.

The parameters of the ASSOCIATE_RX message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “ASSOCIATE_RX”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
“ACCOUNT_ID” parameter, and “RX_ID” parameter.

The response to the “ASSOCIATE_RX” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “ASSOCIATE_RX”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.

は、以下の応答を引き出してよい。

For example, an “ASSOCIATE_RX” message:

May elicit the following response:

  The DISASSOCIATE_RX message may delete the receiver from the account.

The parameters of the DISASSOCIATE_RX message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
-“MESSAGE_TYPE” to provide a message name such as “DISASSOCIATE_RX”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
“ACCOUNT_ID” parameter, and “RX_ID” parameter.

The response to the “DISASSOCIATE_RX” message may include various parameters as follows.
-“MESSAGE_TYPE” to provide a message name such as “DISASSOCIATE_RX”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols, and a “STATUS” parameter to provide additional operational information or errors Thus, this parameter may take a value including 0 to 255 that can be interpreted according to the list of error codes outlined below.

は、以下の応答を引き出してよい。

For example, a “DISASSOCIATE_RX” message:

May elicit the following response:

  The RETRIVE_RX message may retrieve a receiver list associated with the user account.

The parameters of the RETRIVE_RX message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “RETRIEVE_RX”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
An “ACCOUNT_ID” parameter that provides the account ID of the account for which information is requested.

The response to the “RETRIEVE_RX” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “RETRIEVE_RX”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.
An “RX_LIST” parameter that provides a set of receiver IDs associated with the receiver associated with the account ID.

は、以下の応答を引き出してよい。

For example, “RETRIEVE_RX” message:

May elicit the following response:

  The GET_COUNTERSY_CUSTOMER message may retrieve information related to the wireless charging free fraction that the customer sponsors.

The parameters of the GET_COUNTERSY_CUSTOMER message may include various parameters as follows.
“LICENSE KEY” parameter to provide the license key of the user of the current device,
“MESSAGE_TYPE” for providing a message name such as “GET_COUNTERSY_CUSTOMER”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “TIMESTAMP” parameter to provide a UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values; and An “ACCOUNT_ID” parameter that provides the account ID of the account for which information is requested.

The response to the “GET_COUNTERSY_CUSTOMER” message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “GET_COUNTERSY_CUSTOMER”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “STATUS” parameter for providing additional operational information or errors, which may take values including 0 to 255, which can be interpreted according to the list of error codes outlined below.
A “CUSTOMER” parameter that provides the requested customer information.

は、以下の応答を引き出してよい。

For example, a “GET_COUNTRESY_CUSTOMER” message:

May elicit the following response:

  Various status values of the status parameter may indicate multiple status indications. For example, a value of “1” may indicate ACCOUNT_ALREADY EXISTS, EXISTENT ACCOUNT ID RETURNED, a value of “0” may indicate OPERATION COMPLETED SUCCESSFULLY, and a value of 1 may indicate GENERAL ERROR-2. The value of CONNECTION ERROR. TRY AGAIN may be indicated, a value of “−3” may indicate ACCOUNT DOES N′T EXIST, a value of “−4” may indicate INVALID PACKAGE OR CALLBACK NOT RECEIVED, and a value of “−5” may indicate INVALID. RECEIPT may be indicated, a value of “−6” may indicate INVALID GIFT CODE, a value of “−7” may indicate GIFT CODE ALREADY USED, and a value of “−8” indicates MAIL ALREADY EXISTS Well, a value of “−9” may indicate INVALID RX, a value of “−10” indicates RX ALREADY ASSOCIATED TO ANOTHER ACCOUNT, and a value of “−11” indicates DEVICE ALREADY ASSO. It may indicate IATED TO ANOTHER ACCOUNT, a value of “−12” may indicate INVALID PARAMETERS, a value of “−13” may indicate TOO MANY RX, and a value of “−14” indicates PUSH_ID ALREADY_EXISTS A value of “−17” may indicate TRANSACTION_ALREADY_EXISTS.

  A variety of registers may be used in the system, for example, the “RECEIVER_TYPE” register may indicate the type of receiver, the “TRANSMITTER-_NANOLOCATION” register may indicate a particular location of the transmitter, and so on. Further additional registers may be utilized as needed to indicate other aspects such as transmitter type, device type, manufacturer ID, and the like.

  Reference is now made to the flowchart of FIG. 7B representing selected actions illustrating a possible method 700B of policy upload to a remote wireless power outlet combined with reactivation to enforce a newly loaded power management policy. Is done.

  It is noted that the current method 700B refers to the process of installing an updated power management policy immediately after installing a new wireless power outlet. New outlet units may be configured without any policy and allow power transfer to any mobile device by default. Optionally, the newly installed outlet unit may be configured not to allow any power transfer unless a policy governing power transfer is installed. Where appropriate, newly installed wireless power outlets may be configured with a default power management policy that includes default conditions to allow / disallow power transfer.

  Method 700B includes the management server receiving a communication message that includes an identification code for wireless power outlet 702 to allow for the identification of the outlet unit subject to previous registrations. If no policy is installed at the outlet unit or the current power management policy is not valid, for example with a temporary default power management policy 704, the new basic power management policy includes a user identification parameter 706. Generated by the management server. Optionally, if no user identification is sent, a default value may be inserted and updated the first time the user attempts to interact with the wireless power outlet for power transfer. Further, additional data related to the service type policy may be appended to the basic power management policy 708 combined with the data related to the device type as identified at 710. If a dynamic policy such as real-time management of power consumption or real-time management of battery health exists, it may be further appended to 712 and basic policy 714. Policies may be uploaded to the remote wireless power outlet 716 when configured as a single policy or a set of related policies. If necessary, a new policy may be stored in the outlet unit storage, and the current active policy 718 may be further backed up, followed by optionally stopping the current power transfer service and the uploaded policy directed There will be a reactivation of the uploaded policy 720 which will resume the service when it is doing. Where appropriate, activation of uploaded policies may require a restart of the outlet unit 722.

  It is noted that all policies may include various default values such as minimum power level limits, iteration times, etc. and may be configurable by the field system administrator.

  A distributed system for providing power transfer as disclosed herein may include a wireless power transfer network. The wireless power transfer network may be a managed network of outlets that provides wireless charging to the device via a wireless charging transmitter or wireless power receiver. The network management server may provide a management layer for wireless outlets that may be installed in public places. Accordingly, asset management services, monitoring, configuration, maintenance, conditional access, and control may be provided.

  The wireless power transfer network may include a network management server that communicates with wireless power outlets such as publicly installed charging spots. The management server may control the power provision service from each wireless power outlet according to a flexible policy engine, such as disclosed herein. Such a policy may be set by the site and based on location, time, user, or action requested by the user. A field facility may consist of several wireless power outlets that may be operable to communicate with a possible network management server, such as via a communication module. Where appropriate, protocols such as standard HTTPS may be used to provide security and simple IT integration, for example using certificates.

  Referring back to FIG. 7A, the TGW-PCS API interface N1 may allow communication between the network management server and satellite elements such as wireless power outlets, communication modules, gateway modules, and the like. The TGW-PCS API interface N1 may use an application programming interface (API) based on, for example, JavaScript (registered trademark) object notation (JSON), extensible markup language (XML), or the like. Therefore, the network management server may manage the satellite elements remotely.

  TGW-PCS API interface N1 or network messaging protocol is a message that provides tools to maintain the health, configuration, and control of power module (PM) or wireless power outlets, for communication module (CM) health and configuration Or various messages used for network management such as access grant messages for new network elements such as power transmitters to join the wireless power transfer network.

  Communication security may be provided by using a secure communication channel such as an HTTPS connection. Further, the communication may include MAC address filtering using a transmitter identification code (TXID), a receiver identification code (RXID), a gateway identification code (GWID), etc. to control network access. Thus, the TXID may be pre-registered with the network management server and validated before the associated power outlet is authorized to join the network and communications.

  The network message may include a version number that uniquely identifies the message format. This may allow network management to be backward compatible and communicate with satellite elements such as power outlets using multiple versions of the communication protocol.

  The message may be further labeled with a time stamp and a sequential message identification code (message ID) so that the received message can be verified. For example, the message timestamp may be reported as a UTC time zone so that messages sent to the network server can be filtered by time. Thus, old messages and future time stamped messages may be ignored, while recent messages can be processed.

  According to another validation method, the time stamp and message ID may be compared as a check that messages may be sent in the order in which they occurred. For example, if a message with a timestamp older than the previous message is sent to the transmitter, the message is ignored. Thus, if message n with a 4:30:50 time stamp is received after message n + 1 with an earlier time stamp of 4:30:10, message n is ignored and likewise 4:29:10. Message n + 1 is received after message 29 with a time stamp of 4:29:40, message n + 1 is ignored.

同様に、要求応答は、以下の形式の見出しを有してよい。

All messages share a common standardized header. For example, the request message may have a header of the following form:

Similarly, the request response may have a header of the following form:

The message body structure itself may follow, for example, similar standards where applicable.
-The body of the HTTPS message delivered to the network server may contain several concatenated messages of the JSON array.
The array may include different types of API messages, including messages for both power modules (or wireless power outlets) and communication modules.
If the communication module provides communication to multiple power modules, the JSON array may contain API messages from multiple or all of its TxIDs.

For example, the message body may include a plurality of messages as follows.

  The message in the example above is labeled with two message types, status report (labeled POWERMATRIX_TX_REPORT here) and extended status report (here POWERMARTIX_TX_REPORTEXT), as described herein. Is included).

  Examples of various communication message types that may be used as needed include:

  A status report message that may be sent to the management server by the power outlet periodically, on demand, or on an ad hoc basis to report the charging status of the power outlet, the ID of the coupled power receiver, and operational errors.

  The extended status report message may be sent by the power outlet to the management server in response to a request to provide hardware dependent diagnostic information from the management server network.

  A status report message that may be sent from the management server to the power outlet in response to a status report message or an extended status report message to provide a control command to instruct the power outlet to perform a specific action.

  A configuration report message that may be sent to the management server by the power outlet periodically or when commanded to do so in a response message. The configuration report message may provide information to the network administrator regarding the power outlet hardware and software.

  A configuration response message that may be sent from the management server to the power outlet in response to a configuration report message to provide a configuration command to instruct the power outlet to perform certain actions related to the configuration, such as software updates.

  Health status report messages that may be sent to the management server periodically, when instructed to do so, or on an ad hoc basis to provide health status to the network management server.

  A health status response message that may be sent from the management server to the communication module in response to a health status report to provide a control command to instruct the communication module to perform a specific action.

  Periodically, a gateway configuration report message that may be sent to the management server by the communication module when instructed to do so or on an ad hoc basis. The configuration report message may provide information about the communication module hardware and software to the network administrator.

  Provide configuration commands to instruct the power outlet to perform specific configuration actions such as firmware update, software update, clear cache, reboot, log archiving, set defaults such as log size, etc. A gateway setting response message that may be sent from the management server to the communication module in response to the gateway setting report message.

  A join request message that may be sent by the communication module to the management server to provide details of candidate power modules to be added to the network.

  A participation request response message that may be sent from the management server to the communication module in response to the participation request message to allow the addition of the candidate power outlet to the network or to reject the candidate power outlet.

  To better illustrate the communication protocol of a particular embodiment described herein, reference is now made to the flowcharts of FIGS. 8A-8F illustrating selected actions included in the communication protocol.

  With particular reference to the flowchart of FIG. 8A, selected actions of status report communication between the power module and the network management server are presented. Such power module messages may be transferred directly or via a communication module, such as described herein as needed. A power module added to a wireless power delivery network, such as a wireless power outlet, may send status report messages 802 at regular intervals. Optionally, the duration of the interval between sender status reports may be determined by instructions received from the network management server as described below.

  The status report message may include data regarding the operating mode of the power module. Thus, the report may include a MODE parameter that may take a value of “CHARGING” or “NOT_CHARGING” as required.

Other parameters of the status report message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_RPORT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.
A “RX_ID” parameter for providing a unique MAC address identifier of the receiver receiving the service, which has a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example. You can.
A “STATUS” parameter to provide additional hardware-dependent operational information or errors, this parameter including 0 to 255, which can be interpreted according to the list of error codes outlined herein You may take a value.
A “ERROR_DATA” parameter for providing supplementary extended hardware dependent data to the STATUS parameter, which may take a value from 0 to 255.

  Various error codes may be used as examples, and the error code of a specific embodiment includes a 0 “Idle, no charge” code representing normal operation, a “Charging Active” code representing normal operation, unknown 2 “Rx End of Charge (EOC)” code representing normal operation which may take a value indicating an EOC reason such as 0 in case of (battery full or Rx safety) or 1 if required by the network server, 3 “Tx End of charge, no Rx” representing normal operation, 4 “No charge, invalid RxID” code representing usage error, 5 “No charge, charging disabled by network manager” code representing warning, Celsius Value indicating temperature 6 “over temperature” code indicating a good error, mA value, 7 “18v current limit” code indicating a warning that can take current, 8 value indicating an error that can take a value and voltage in MV units “Out of voltage range” code, mV unit value, 10 “24v current limit” code indicating an error that may take a current, 32 “Last ZB Tx failed” code indicating a warning, and 33 “Last ZB Tx failed” code indicating a warning "Lost TbdRx messages" code, 34 "out of frequency range" codes representing warnings, and 48 "Remote Firmware Update error" codes representing errors that can take values between 0 and 255 . It will be appreciated that other error code schemes may be applied as needed.

  The network management server may receive the status report message 804 and perform a message validity check 806. If the message is deemed invalid, for example, if the message ID is not sequential as described above, the received message may be ignored 808. Otherwise, the message data is processed 810 and a control command is generated for 812 which is returned to the power module in a response message. The response message may be received by the power module and the command may be executed 814 by the power outlet processor.

  The control command may provide an instruction to allow or not allow power supply as needed. Thus, the response message may include a COMMAND parameter that may take a value of CHARGE or DO-NOT-CHARGE as required.

Other parameters of the status report response message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_REPORT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.
A “RX_ID” parameter for providing a unique MAC address identifier of the receiver receiving the service, which has a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example. It's okay.
“INTERVAL” parameter to provide an expected interval between subsequent status report messages, the parameter may take a value from 1 to 1000 seconds until the value of INTERVAL is changed.
A “SEND_EVENTS” parameter that may take the value of TRUE or FALSE, which causes the operation mode to change or an error occurs, another status report message is requested, and INTERVAL is reset during TRUE.
A “SEND_REPORTEXT_ON_ERROR” parameter that may take a value of TRUE or FALSE, which causes an error and requests an extended status report message during TRUE.
A “SEND_REPORTEXT” parameter that may take the value of TRUE or FALSE, so that when TRUE, the extended status report message a is requested immediately.
A “SEND_TX_CONFIG” parameter, which may take the value of TRUE or FALSE, so that when TRUE, the S report is immediately requested.

For example, a possible status report message may take the following form:

A similar example of a possible status response message may take the following form:

Referring now to the flowchart of FIG. 8B, selected actions for extended status report communication between the power module and the network management server are presented. Such power module messages may be forwarded directly through the communication module, such as directly or as needed herein. The network management server may request 816 such an extended status report, such as described above via the “SEND_REPORTEXT” parameter or the “SEND_REPORTEXT_ON_ERROR” parameter. Accordingly, the power module may send 818 an extended status report message. The extended status report message is an extensive list of diagnostic information related to the hardware. In particular, the parameters of the extended status report message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_REPORTEXT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.
A “RX_ID” parameter for providing a unique MAC address identifier of the receiver receiving the service, which has a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example. You can.
A “MODE” parameter that may take the value of “CHARGING” or “NOT_CHARGING” as required.
A “STATUS” parameter to provide additional operating information or errors depending on the hardware, this parameter including, for example, 0 to 255, which can be interpreted according to the list of error codes described herein. You can take the value.
A “ERROR_DATA” parameter for providing supplementary extended hardware dependent data to the STATUS parameter, which may take a value from 0 to 255.
A “TEMPERATURE_1” parameter for providing a temperature reading from the MCU board of the power module, this parameter can take a value between 0 and 255 degrees Celsius, and a negative measurement must be transmitted as 0 A “TEMPERATURE_2” parameter to provide a temperature reading from the upper board of the power module, which may take a value between 0 and 255 degrees Celsius, and a negative measurement must be transmitted as 0 A “CURRENT_1” parameter for providing a first ammeter measurement, which may take a value between 0 and 255 indicating the current measured in mA divided by 16.
A “CURRENT_2” parameter for providing a second ammeter measurement, which may take a value from 0 to 255 indicating the current measured in milliamps divided by 16.
A “VOLTAG_IN” parameter for providing a voltage measurement, which may take a value between 0 and 255 indicating the voltage measured in millivolts divided by 176.
A “VOLTAGE_DC2DC” parameter for providing a voltage measurement, which may take a value between 0 and 255 indicating the voltage measured in millivolts divided by 176.
A “DC_PEAK” parameter for indicating the presence of an object on the power outlet, which may take a value from 0 to 255 in millivolts divided by 16.
An “OVER_DECREMENT” parameter to provide the maximum allowable decrement, which may take a value from 0 to 255 in millivolts divided by 16

  Accordingly, the network management server may receive the extended status report message 820 and perform 806 a message validity check. If the message is deemed invalid, for example, if the message ID is not sequential as described above, the received message may be ignored 808. Otherwise, the message data is processed 810 and a control command is generated for 812 which is returned to the power module in a response message. The response message may be received by the power module and the command may be executed by the power outlet processor 814.

以下のような応答を引き出してよい。

For example, a possible extended status report message may take the following form:

You may elicit the following response:

  Referring now to the flowchart of FIG. 8C, the selected action of configuration report communication between the power module and the network management server is presented. Such power module messages may be transferred directly or via a communication module, such as described herein as needed. The configuration report may be sent to the network management server 826 at startup 822. Alternatively, the network management server may request 824 such a configuration report, such as described above via the “SEND_TX_CONFIG” parameter of the status report response message. Accordingly, the power module may send a configuration report message 826. The configuration report message is a message issued by the power module to provide information about the configuration of the power module. The response message provides a mechanism for remote configuration and maintenance.

  For example, the “CHARGER_FIRMWARE_VERSION” parameter and the “HW_VERSION” parameter may include firmware and hardware versions for the power module device.

In particular, the parameters of the power module configuration report message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_CONFIG”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example.
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.
A “CHARGER_FIRMWARE_VERSION” parameter for providing the firmware version of the power module, which is an “X. Y ”.
A “ZB_FIRMWRE_VERSION” parameter for providing the firmware version of the Zigbee® component in the power module, which, when implemented, is “X. The value of “Y” may take the value, or if it does not exist, the parameter may take the value of “0.0”.
A “HW_VERSION” parameter for providing the hardware version of the power module, which is an “X. Y ”.
A “REASON” parameter for providing a reason for issuing a message, and this parameter may take a value selected from “RESET” or “BY_REQUEST” as necessary.

  Accordingly, the network management server may receive the configuration report message 828 and perform 806 a message validity check. If the message is deemed invalid, for example, if the message ID is not sequential as described above, the received message may be ignored 808. Otherwise, the message data is processed 810 and a configuration command is generated for returning 830 the power module in a response message 830. The response message may be received by the power module and the set command may be executed 832 by the power outlet processor. It will be appreciated that message validity checks may be performed as needed by the power outlet processor.

  In response to the configuration report message, the network management server may issue a command to change the firmware version using, for example, UPDATE_CHARGER_FIRMWARE, or to perform remote maintenance such as a reset (RESET).

In particular, the parameters of the setup response message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_CONFIG”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
A “TIMESTAMP” parameter to provide a UTC-based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values;
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example.
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.
A “CHARGER_FIRMWARE_VERSION” parameter for providing a firmware version that the power module needs to be upgraded if the “UPDATE_CHARGER_FIRMWARE” parameter is TRUE, this parameter being an “X” where X and Y are positive integers . Y ”.
A “VENDOR_ID” parameter for providing a power module vendor identification code, which may take the value of a hexadecimal string.
A “ZB_FIRMWARE_VERSION” parameter for providing a Zigbee® component version that needs to be upgraded when the “UPDATE_ZB_FIRMWARE” parameter is TRUE, where X and Y are correct "X. The parameter may take a value of “0.0”, which may have a value of “Y”, or when this is not present.
A “UPDATE_CHARGER_FIRMWARE” parameter that may take the value of TRUE to instruct the power module processor to update the power module firmware, or the value of “FALSE” if the firmware version should not be updated.
TRUE value to instruct the power module processor to update the power module Zigbee component, or "FALSE" value if the Zigbee component should not be updated "UPDATE_ZB_FIRMWARE" parameter that can be taken.
A “RESET” parameter that may take the value of TRUE to instruct the power module processor to reset itself, or the value of “FALSE” otherwise. Enable optical feedback to the power module processor A “LEDS” parameter that may take a value of TRUE to command or a “FALSE” value to command the power module processor to disable optical feedback.
“SOUND” which may take the value of TRUE to instruct the power module processor to enable audio feedback, or the value of “FALSE” to instruct the power module processor to disable audio feedback Parameter.
“DISABLE_CHARGER” which may take the value of TRUE to instruct the power module processor to disable the power module, or the value of “FALSE” otherwise.
A “CURRENT_LIMIT” parameter for limiting the amount of current sent to the receiver, the parameter may have a value of (x−350) / 20, where x is the value for which the limit is set, “CURRENT_LIMIT” parameter.
An “INDUCTION_SENSOR_SENSITIVITY” parameter for setting the analog ping voltage detection sensitivity, and the parameter may have a value of (x−10) / 20 where x is a value for which sensitivity is set.
A “DC_PEAK_LIMIT_THRESHOLD” parameter for setting a primary peak threshold as needed, and the parameter may have a value of (x−100) / 250 where x is a value for which a threshold is set.
A “TSLEEEP” parameter for setting a delay time after the power module attempts to transfer power, where the parameter is x−1 where x is a fraction, or 255 to disable retry May have a value.

以下のような設定応答メッセージを引き出してよい。

For example, a possible configuration report message may take the following form:

The following setting response message may be extracted.

  Referring now to the flowchart of FIG. 8D, selected actions for health report communication between the communication module or gateway and the network management server are presented. A communication module may be added to the wireless power supply network to allow communication and control of the power module from the network management server. Such a communication module may send periodic health report messages 834 at regular intervals. The health report message may provide data relating to the health status of the communication module.

Accordingly, the health report message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_GW_REPORT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “37290B2597A8”, for example.
A “STATUS” parameter to provide additional operating information or errors depending on the hardware, this parameter including, for example, 0 to 255, which can be interpreted according to the list of error codes described herein. You can take the value.
Optionally, an “ERROR_DATA” parameter for providing supplementary extended hardware dependent data to the STATUS parameter, which may take a value from 0 to 255.

  The network management server may receive 836 the health report message and perform 806 a message validity check. If the message is considered invalid, for example, if the message ID is not sequential as described above, the message may be ignored 808. Otherwise, the message data is processed 810 and a control command is generated for 838 to be returned to the power module in a response message. The response message may be received by the power module and the configuration command may be executed 840 by the control module processor. It will be appreciated that message validity checks may be performed by the communication module processor as needed.

The network administrator may generate various responses to the health report message 836 that may be communicated with the health report response message. Accordingly, the health report message may include various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_GW_REPORT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “37290B2597A8”, for example.
An “INTERVAL” parameter for providing an expected interval between subsequent health report message requests until the value of INTERVAL is changed, and this parameter may take a value from 1 to 1000 seconds.
An “ALLOW_JOIN” parameter that may take a default value of FALSE, but may instruct the communication module processor to request addition of a power module to the network by taking a value of TRUE.

以下のような応答を引き出してよい。

For example, a possible health report message may take the following form:

You may elicit the following response:

  Referring now to the flowchart FIG. 8E, the selected action of configuration report communication between the communication module and the network management server is presented. The configuration report may be sent 842 to the network management server periodically or at startup at regular intervals. Accordingly, the power module may send a configuration report message 842. A configuration report message is a message issued by the communication module to provide information about the configuration of the communication module. The response message provides a mechanism for remote configuration and maintenance of the gateway.

In particular, the parameters of the communication module configuration report message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_GW_REPORT”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example.
A “FIRMWARE_VERSION” parameter for providing a firmware version of the communication module, which is an “X. Y ”.
A “SOFTWARE_VERSION” parameter for providing the software version of the communication module, and this parameter includes “X. Y ”.
A “FREE_MEMORY” parameter for providing the amount of available memory, which may take a value representing the number of free kilobytes.
A “FREE_FLASH” parameter for providing the amount of available flash memory, which may take a value representing the number of free kilobytes.
Percentage Communication Module Processor “CPU” parameter to provide CPU utilization, this parameter may take a percentage value • “REASON” parameter to provide a reason for issuing a message Thus, this parameter may take a value selected from “RESET” or “BY_REQUEST” as necessary.

  Accordingly, the network management server may receive 844 the configuration report message and perform 806 a message validity check. If the message is deemed invalid, for example, if the message ID is not sequential as described above, the received message may be ignored 808. Otherwise, the message data is processed 810 and a configuration command is generated for 846 to be returned to the communication module in a response message. The response message may be received by the communication module and the configuration command may be executed by the communication module processor 848. It will be appreciated that message validity checks may be performed by the communication module processor as needed.

In particular, the parameters of the configuration response message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_GW_CONFIG”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example.
A “FIRMWARE_VERSION” parameter for providing a firmware version that the communication module must be upgraded to when the “UPDATE_FIRMWARE” parameter is TRUE, this parameter being an “X. Y ”.
A “SW_VERSION” parameter for providing a software version that the communication module must be upgraded to when the “UPDATE_SOFTWARE” parameter is TRUE, this parameter being an “X. Y ”.
A “UPDATE_FIRMWARE” parameter that may take the value of TRUE to instruct the communication module processor to update the communication module firmware, or the value of “FALSE” if the firmware version should not be updated.
A “UPDATE_SOFTWARE” parameter that may take the value of TRUE to instruct the communication module processor to update the communication module software, or the value of “FALSE” if the firmware version should not be updated.
A “REBOOT” parameter that may have a default value of FALSE and take the value of TRUE to instruct the power module processor to reboot itself.
A “AGGREGATION_INTERVAL” parameter that provides a random interval in which the power module response message is collected from the power module associated with the communication module and forwarded to the network server, where the parameter is 1 to N seconds per path You may take a value that represents a random number.
An “INIT_PAN” parameter that may have a default value of FALSE and take the value of TRUE to instruct the processor to clean up the network data that is cached in the communication module.
A “LOG_APPENDER” parameter for determining the status of communication module log creation and archiving, and the parameter may take a value of “OFF”, “FILE”, or “FTP” as necessary.
A “LOG_URL” parameter for providing the URL of the FTP log location when the “LOG_APPENDER” parameter has a value of “FTP”, and the “LOG_URL” parameter has the format “[user: pass @] host: [port ]
A “LOG_SIZE” parameter for providing the size of the log file, which may have a default value of 1024 kilobytes and may take a value from 50 KB to 5 MB as required.

以下のような設定応答メッセージを引き出してよい。

For example, a possible configuration report message may take the following form:

The following setting response message may be extracted.

  Referring now to the flowchart FIG. 8F, selected actions for participation request communication between the communication module and the network management server are presented. The join request message is a transaction request from the communication module to the network management server for permission to add a new power module to the network. Accordingly, a join request message may be sent 852 to the network management server when a new power module is discovered 850.

In particular, the parameters of the join request message may include:
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_JOIN”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “37290B2597A8”, for example.
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.

  The network management server may receive the join request message 854 and perform 806 a message validity check. If the message is considered invalid, for example, if the message ID is not sequential as described above, the message may be ignored 808. Otherwise, the message data is processed 810 and an authentication response is generated for transmission 856 back to the communication module. If required, rules may apply to the request, eg, a power module ID (TxID) needs to be previously registered in the network, and another communication module to be granted and added to the network. There is no need to have already joined through.

  The authentication response may be received and processed by the power module. If approved, a new power module may be added to the network 860, otherwise the new power module may be rejected 858.

Therefore, the authentication message may have various parameters as follows.
“MESSAGE_TYPE” for providing a message name such as “POWERMATRIX_TX_JOIN”,
A “VERSION” parameter that provides a version of the message format, thereby allowing the management server to be compatible with multiple communication protocols;
A “MESSAGE_ID” parameter for detecting a data loss and providing a serial number used in a validity check to guarantee sequence control, the value of this parameter being a repeating sequence from 1 to 255 Good,
“TIMESTAMP” parameter to provide UTC based report time with format YYYY-MM-DDTHH: MM: SSZ, where “−”, “:”, “T” and “Z” are constant values.
A “GW_ID” parameter for providing a unique MAC address identifier of the communication module, which may have a 12-digit hexadecimal address value without a separator, such as “4C766604FC3E”, for example.
A “TX_ID” parameter for providing a unique MAC address identifier of the power module, which may have a 12-digit hexadecimal address value without a separator, such as “F05DC8011FFB”, for example.
"COMMAND" which may take the value of APPPROVE to instruct the communication module processor to add a new power module to the network, or the value of REJECT to instruct the communication module to reject the new power module Parameter.

以下のような認証応答メッセージを引き出してよい。

For example, a possible participation request message may take the following form:

The following authentication response message may be extracted.

  While only message type and format choices are described herein for purposes of illustration, it is understood that other message types may be transmitted as needed. In certain embodiments, empty messages may be periodically sent by the communication module to the network management server. Such an empty message may be used to retrieve a response message from the network management server as needed. In other embodiments, the network management server may not respond to communication if there are no functional changes required for the power module or the communication module. Still other message types and formats may be used in adapted protocol versions, as will occur to those skilled in the art as needed.

  Technical and scientific terms used herein should have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure relates. Nevertheless, many related systems and methods are expected to be developed during the lifetime of a patent that matures from the present application. Accordingly, the scope of terms such as computing device, network, display, memory, server, etc. is intended to encompass all such new technologies a priori.

  As used herein, the term “about” refers to at least ± 10%.

  The terms “comprising”, “comprising”, “including”, “including”, “having”, and their conjuncts mean “including but not limited to” and listed configurations Indicates that an element is included but generally does not exclude other components. Such terms include the terms “consisting of” and “consisting essentially of”.

  The expression “consisting essentially of” means that a component or method does not significantly alter the basic and novel characteristics of the claimed composition or method. Or it may include steps.

  As used herein, the singular forms “a”, “an”, and “the” may include a plurality of references unless the context clearly indicates otherwise. For example, the term “a compound” or “at least one compound” may include a plurality of compounds, including mixtures thereof.

  The word “exemplary” is used herein to mean “serving as an example, instance, or illustration”. Any embodiment described as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments, or to exclude the incorporation of features from other embodiments.

  The word “optionally” is used herein to mean “provided in some embodiments but not in other embodiments”. Any particular embodiment of the present disclosure may include a plurality of “optional” features as long as such features do not conflict.

  Whenever a numerical range is indicated herein, that range is intended to include any cited numerical representation (fractional or integer) within the indicated range. The expression first indicator number and second indicator number “was fluctuating / fluctuating”, and the first indicator number to the second indicator number “in” “passing / crossing” are described herein. It is intended to be used interchangeably in a book, including the first and second indicator numbers, and all fractional and integer number representations in between. Accordingly, it should be understood that the description of the range format is merely for convenience and clarity and should not be construed as an inflexible limitation on the scope of the present disclosure. Accordingly, the description of a range should be considered to have specifically disclosed all the possible subranges as well as individual numerical values within that range. For example, the description of a range from 1 to 6 etc. is specifically described as a partial range such as 1 to 3, 1 to 4, 1 to 5, 2 to 4, 2 to 6, 3 to 6 and the like. It should also be considered to have individual numbers within, for example 1, 2, 3, 4, 5, and 6, and non-integer intermediate values. This applies regardless of the width of the range.

  It should also be understood that certain features of the invention described in the context of separate embodiments for clarity may be provided in combination in a single embodiment. Conversely, various features of the present disclosure that are described in the context of a single embodiment for the sake of brevity are described separately or in any appropriate sub-combination or any other description of the present disclosure. May be provided as appropriate in certain embodiments. Certain features that are described in the context of various embodiments should not be viewed as essential features of those embodiments, unless the embodiment is inoperable without those elements.

  While the invention has been described in conjunction with specific embodiments thereof, it is evident that other alternatives, modifications, variations, and equivalents will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications, variations and equivalents that fall within the spirit of the invention and the broad scope of the appended claims.

  Moreover, the various embodiments described herein above have been described with reference to exemplary block diagrams, flowcharts, and other diagrams. As will be apparent to those skilled in the art, the illustrated embodiment and its various alternatives may be implemented without limitation to the illustrated example. For example, block diagrams and accompanying descriptions should not be construed as ordering a particular architecture, layout, or configuration.

  The presence of a spread word, such as “one or more”, “at least”, “but not limited to” or other similar expressions in some instances, is absent of such spread expressions. It should not be construed to mean that a narrower case is intended or required in any possible instance. The term “module” does not imply that the components or functionality described or claimed as part of the module are all configured in one common package. In fact, any or all of the various components of the module can be combined into a single package, or maintained separately, regardless of whether they are control logic or other components. Can be distributed in multiple groups or packages, or across multiple locations.

  Further, the embodiments may be implemented in hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. When implemented in software, firmware, middleware, or microcode, program code or code segments for performing the required tasks may be stored on a computer-readable medium, such as a storage medium. The processor may perform the necessary tasks.

  All publications, patents, and patent applications mentioned in this specification are specifically and individually indicated so that each individual publication, patent, or patent application is incorporated herein by reference. To the same extent as the above, it is incorporated herein by reference in its entirety. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present disclosure. As long as section headings are used, they should not necessarily be construed as limiting.

  The scope of the disclosed subject matter is defined by the appended claims, and includes various combinations and subcombinations of the various features described above, as well as variations and modifications thereof that will occur to those skilled in the art upon reading the foregoing description. Including.

Claims (25)

A system for managing a wireless power transfer network,
At least one wireless power outlet unit operable to transfer power to at least one electrical device associated with the wireless power receiver;
At least one management server communicating with the at least one wireless power outlet unit;
At least one operable to execute instructions directed to receiving an identification code from the at least one wireless power outlet unit and managing power transfer from the at least one wireless power outlet unit; And the management server. The at least one management server is
The apparatus of claim 1, further operable to execute instructions directed to monitoring health of the at least one wireless power outlet unit and providing remote maintenance of the at least one wireless power outlet unit. The system described in.   The system of claim 1, wherein the at least one management server is further operable to communicate with the at least one electrical device.   Managing the power transfer is operated by at least one power management policy, wherein the at least one power management policy determines power transfer conditions for the at least one wireless power outlet unit. The described system.   The system of claim 4, wherein the at least one power management policy is selected from the group consisting of a user identification policy, a service type policy, a device type policy, a dynamic policy, and combinations thereof.   The system of claim 5, wherein the at least one power management policy is selected for the at least one wireless power outlet unit according to the identification code.   The system of claim 6, wherein the at least one wireless power outlet unit has a default power management policy to determine default power transfer conditions.   The system of claim 7, wherein the selected power management policy replaces the power management default policy.   The system of claim 8, wherein the at least one power management policy is distributed in response to changes in the at least one power management policy at the at least one management server.   The system of claim 8, wherein the at least one power management policy is distributed according to a distribution schedule.   The system of claim 8, wherein the at least one power management policy is distributed upon communication requests from the at least one wireless power outlet unit.   6. The system of claim 5, wherein the user identification policy comprises an action selected from the group consisting of user identification, location identification, start time, end time, duration of power transfer, and combinations thereof.   6. The system of claim 5, wherein the type of service policy determines a level of current applied during power transfer from the at least one wireless power outlet.   The system of claim 5, wherein the dynamic policy comprises an action selected from the group consisting of real-time management of power consumption, real-time management of battery health, location traffic control, historical usage data analysis, and combinations thereof.   Providing the remote maintenance is selected from the group consisting of starting, stopping, restarting, software updating, controlling a visual user interface, controlling a user audio interface, and combinations thereof The system of claim 2, comprising performing the steps of:   The system of claim 2, wherein monitoring the health includes the wireless power outlet responding to a communication signal within a timeout limit.   The system of claim 16, wherein the communication signal is transmitted according to a schedule.   The system of claim 16, wherein the communication signal is transmitted on demand.   15. The system of claim 14, wherein the historical usage data analysis is selected from a group consisting of usage analysis of the at least one wireless power outlet unit, user usage analysis, user group usage analysis, and combinations thereof. . A computer-implemented method for managing a wireless power transfer network, wherein the wireless power transfer network is operable to (1) transfer power to at least one electrical device associated with a wireless power receiver At least one wireless power outlet unit; and (2) at least one management server communicating with the at least one wireless power outlet unit and further communicating with a management database;
The at least one management server receiving an identification code from the at least one wireless power outlet unit;
Said at least one management server managing power transfer from said at least one wireless power outlet unit. The at least one management server monitoring the health of the at least one wireless power outlet unit;
21. The method of claim 20, further comprising the step of the at least one management server providing remote maintenance of the at least one wireless power outlet unit.   21. The method of claim 20, wherein the at least one management server is further operable to communicate with the at least one electrical device.   The step of managing power transfer is operated by at least one power management policy, wherein the at least one power management policy is configured to set power transfer conditions for the at least one wireless power outlet unit. 21. The method of claim 20, wherein   24. The method of claim 23, wherein the at least one power management policy is selected from the group consisting of a user identification policy, a service type policy, a device type policy, a dynamic policy, and combinations thereof.   24. The method of claim 23, wherein the at least one power management policy is selected for the at least one wireless power outlet unit according to the identification code.

Images