WO2014065442A1

WO2014065442A1 - Management protocol of wireless power transfer for multi-devices

Info

Publication number: WO2014065442A1
Application number: PCT/KR2012/008650
Authority: WO
Inventors: Yun Jae Won; Seung Ok Lim
Original assignee: Korea Electronics Technology Institute
Priority date: 2012-10-22
Filing date: 2012-10-22
Publication date: 2014-05-01

Abstract

This standard defines the interface for wireless power transfer to multiple devices (including one device) that require charging within several meters. In order to provide WPT for multi-devices, functionalities, system structure, primitives, frame format, and procedures are defined. This standard selectively utilizes various frequency bandwidths ranging from the low frequency of 50 kHz to the high frequency of 15 MHz for wireless power transfer. For system control, it requires supports of the signalling by which data and control signals can be exchanged. This standard can be applied to a multimedia industrial field for use of batteries such as mobile terminals, laptops, portable multimedia players, etc.

Description

MANAGEMENT PROTOCOL OF WIRELESS POWER TRANSFER FOR MULTI-DEVICES

This standard defines the interface for wireless power transfer to multiple devices (including one device) that require charging within several meters. In order to provide WPT for multi-devices, functionalities, system structure, primitives, frame format, and procedures are defined.

A wireless charging system using a magnetic induction phenomenon as wireless power transmission technologies wirelessly transmitting energy has been used.

For example, an electric toothbrush, a cordless razor, or the like, is charged by a principle of electromagnetic induction. In recent years, wireless charging products capable of charging portable devices such as mobile phones, PDAs, MP3 players, notebook computers, or the like, using the electromagnetic induction have been released.

However, the magnetic induction scheme inducing current through magnetic field from a single coil to another coil is very sensitive to a distance between the coils and a relative position of the coils to sharply degrade transmission efficiency even when the distance between two coils are slightly spaced or twisted from each other. Therefore, the wireless charging system according to the magnetic induction scheme may be used only in a short range of several centimeters or less.

Meanwhile, US Patent No. 7,741,734 discloses a method of wireless non-radiative energy transfer using coupling of resonant-field evanescent tails. The basis of this technique is that two same-frequency resonant objects tend to couple, while interacting weakly with other off-resonant environmental objects, which makes it possible to transfer energy farther away compared to the prior art magnetic induction scheme.

There are the complexity and inconvenience of wire cable chargers by transferring power wirelessly.

This standard selectively utilizes various frequency bandwidths ranging from the low frequency of 50 kHz to the high frequency of 15 MHz for wireless power transfer. For system control, it requires supports of the signalling by which data and control signals can be exchanged.

This standard can be applied to a multimedia industrial field for use of batteries such as mobile terminals, laptops, portable multimedia players, etc.

This technology can be applied to the following industry fields that require batteries.

* Mobile terminals: Charging services can be provided to mobile terminals anytime and anywhere.

* Home appliances: To make complicated cable wiring simple and convenient, use of this technology can give simple wiring and compact furniture arrangement features.

* Electric vehicles: This technology enables the users to evade from the danger due to high voltage charging by providing efficient and convenient charging services on the single standard basis.

* Medical devices: Use of this technology enables patients to have transplant devices with secure and various features.

Figure 1 Concept Diagram of MWPTS

Figure 2 Concept Diagram of MWPTS Services

Figure 3 Physical and Spatial Elements

Figure 4 General Procedure for TDMA-based MWPTS

Figure 5 Hierarchical View of Wireless Power Transfer System

Figure 6 MWPTS-D Recognition/Authentication and Charging Zone/Communication Zone

Figure 7 Simultaneous Power Transfer

Figure 8 Time-division Power Transfer

Figure 9 Foreign Material Removal

Figure 10 New MWPTS-D Appearance and Existing MWPTS-D Disappearance

Figure 11 Full Charge of Existing MWPTS-D

Figure 12 Power Transfer Termination

Figure 13 Power Transfer between Devices

Figure 14 Battery Discharge Rate Change Notification

1. Scope

3.2. Abbreviations

For the purposes of this document, the following abbreviations apply:

MWPTS Multi-device Wireless Power Transfer System

MWPTS-C Multi-device Wireless Power Transfer System-Charger

MWPTS-D Multi-device Wireless Power Transfer System-Device

4. Overview

Wireless power transfer (WPT) is the mechanism in which power is transferred from a source to either a destination or destinations. WPT system consists of two components: a charger which transfers power, and a device which receives the power from a charger. Multi-Device WPT System (MWPTS) is the system in which one charger (MWPTS-C) provides WPT to one or multiple devices (MWPTS-Ds). In order to effectively transfer power to multiple MWPTS-D (or for effective power transfer control), the system shall have an interface to manage the MWPTS network that became more complicated than the 1:1 MWPTS. After catching the current MWPTS status based on the power transfer data, MWPTS-C performs various procedures such as ID recognition, and authentication. Moreover, an optimal power transfer mode is selected for best transfer efficiency. It shall include the procedures and interfaces for emergency control and management such as counter actions to sudden MWPTS-D disappearance or detection.

Figure 1 Concept Diagram of MWPTS

n Mobile terminals: Charging services can be provided to mobile terminals anytime and anywhere.

n Home appliances: To make complicated cable wiring simple and convenient, use of this technology can give simple wiring and compact furniture arrangement features.

n Electric vehicles: This technology enables the users to evade from the danger due to high voltage charging by providing efficient and convenient charging services on the single standard basis.

n Medical devices: Use of this technology enables patients to have transplant devices with secure and various features.

Figure 2 Concept Diagram of MWPTS Services

In order to transfer wireless power to multiple devices, MWPTS-C performs the MWPTS function on the time-division scheduling basis. For wireless power transfer environment control, it also manages connection, separation, and release of MWPTS-D.

It provides MWPTS ranging from several watts to several hundred watts within a near field or several meters. It shall provide an enough efficiency level for the MWPTS in a short distance for each MWPTS-D product.

For efficient wireless power transfer and interoperability, each user can select any of various frequency bands.

In order to efficiently provide WPT services to multiple devices, a signalling system is required for exchange of power transfer data and control signals.

5. Functionalities

5.1. General

In order to transfer wireless power to multiple MWPTS-Ds, the MWPTS-D recognition and authentication procedure are required to determine each MWPTS-D identified by MWPTS-C is eligible for MWPTS service.

In order to provide fast power transfer service to multiple MWPTS-Ds, firstly basic data for MWPTS-D recognition/authentication is exchanged when the receiver is within the communication zone for wireless power transfer preparation. When a ready MWPTS-D comes within the charging zone, wireless power transfer is performed. This action can save the preparation time for fast service.

For efficient MWPTS service, the system can provide two different modes: 1. simultaneous power transfer mode that transfers wireless power to all devices within the charging zone at the same time. 2. time-division power transfer mode that transfers power to individual receivers in different divided times prioritized by the residual battery level or user dependent data.

When all receivers are fully charged, the power transfer ends or user can arbitrarily stop the service.

Because wireless power transfer is performed for multiple power receivers, abnormal situations can occur frequently. For effective counter actions, when any abnormal situation occurs on the network, the MWPTS-C recognizes it, stops the service before resolving the case, and informs the users of that situation.

5.2. MWPTS Recognition and Authentication

MWPTS-C periodically transmits the connection request signals and the MWPTS-Ds that have received the signals, response with their own IDs. Then MWPTS-C determines whether the MWPTS-Ds are candidates for wireless power transfer based on the received IDs. If they are service targets, MWPTS-C requests for wireless power transfer data. For non-service candidate, MWPTS-C informs that no service is to be provided.

5.3. MWPTS Modes

5.3.1. General

MWPTS Modes are divided into two: simultaneous power transfer mode and time-division power transfer mode. In every mode, MWPTS-C collects the charging data (residual battery level, battery discharge rate, received signal power level, voltage/current sensing data, etc.) from MWPTS-Ds through current/voltage sensing and communication. In addition, it performs charging frequency band selection, impedance matching, output power level adjustment, and the actions to provide the high efficiency wireless power transfer service to the corresponding MWPTS-D.

5.3.2. Simultaneous Power Transfer Mode

After MWPTS-D recognition and data exchange for power transfer are completed, the wireless power transfer service starts. During the wireless power transfer service, the simultaneous power transfer mode transfers power to all MWPTS-Ds within the charging zone at the same time. To increase the wireless power transfer efficiency before the power transfer, MWPTS-C adjusts the matching based on the impedance value calculated after sensing the antenna voltage and current. For fine tuning, the efficiency is calculated after receiving the reception power level information from the MWPTS-D. When the charging control is finished, wireless power transfer is simultaneously performed for all MWPTS-Ds. This is continually performed until wireless power transfer is completed.

5.3.3. Time-division Power Transfer Mode

After MWPTS-D recognition and data exchange for power transfer are completed, the wireless power transfer service starts. During the wireless power transfer service, the time-division power transfer mode grants priorities for all service waiting MWPTS-Ds and allocates divided times to the receivers for individual power transfer according to the given priorities. Wireless power transfer service is provided only for the time allocated to each MWPTS-D. When the service for all MWPTS-Ds is completed, the service ends.

5.4. Abnormal Situations Management

5.4.1. General

During the wireless power transfer service, if any abnormal situation happens, the service stops and the corresponding solution is performed. Abnormal situations can include unexpected materials detection, new MWPTS-D appearance, the existing MWPTS-D disappearance, and stopping the service after the full charge of an MWPTS-D. For all abnormal situations, MWPTS-C senses the change of voltage, current, and impedance at the antenna, recognizes the situation details, and performs the actions for each situation.

5.4.2. Unexpected Material Detection

When any unexpected material that can change the efficiency of wireless power transfer is detected, MWPTS-C recognizes it and informs the user of the status as an alarm format.

5.4.3. New MWPTS-D Appearance and Existing MWPTS-D Disappearance

When a new MWPTS-D appears or an existing MWPTS-D disappears, MWPTS-C stops the current power transfer service, and it performs the impedance matching to collect the status information and maximize the efficiency of MWPTS. After correcting the matching MWPTS service is started again.

5.4.4. Full Charge of Existing MWPTS-D

When an MWPTS-D that is receiving the power transfer service is fully charged, the service is stopped and the MWPTS-D informs MWPTS-C of its full charge. When MWPTS-C receives the full charge information, it restarts transferring wireless power to other MWPTS-Ds except the fully charged MWPTS-D.

5.5. MWPTS Termination

MWPTS can end when no MWPTS-D exists waiting for the wireless power transfer service and when the user wants to stop the service. In this case, the current wireless power transfer service stops and MWPTS-C is switched to the standby mode.

5.6. Wireless Power Transfer between MWPTS-Ds

If no MWPTS-C exists in the region or an MWPTS-D is not within the charging zone, an MWPTS-D can request wireless power transfer to a MWPTS-D in the neighborhood. The MWPTS-D that received signal can transfer wireless power to the requester according to the user selection.

6. MWPTS Management

6.1. General

MWPTS is divided into three: physical element, spatial element, and time element. The physical element consists of MWPTS-C and MWPTS-D, the spatial element consists of the charging zone and communication zone, and the time element means the time units based on the time-division for wireless power transfer.

The physical element of MWPTS means an MWPTS-C and MWPTS-Ds on the MWPTS-C centered star topology. On the MWPTS network, the centered MWPTS-C can exchange data with each MWPTS-D and transfer wireless power to MWPTS-Ds. MWPTS-C manages the entire MWPTS network and only one MWPTS-C exsists on the network. For the physical element, see Figure 3.

For effective MWPTS-Ds control within the MWPTS network, available MWPTS-Ds must be identified and authenticated and the data for wireless power transfer must be exchanged in advance as a preparation step. Accordingly, a virtual space including the charging zone and communication zone exists. An MWPTS-C starts to manage multiple MWPTS-Ds, among which the MWPTS-C transfers wireless power to the MWPTS-Ds that belongs to the charging zone. In case of the MWPTS using the in-band wireless communication, the communication range cannot reach a far distance so efficient charging zone and communication zone should be formed. However, in miscellaneous communication methods, the supportable sizes of the communication zone may vary so the number of MWPTS-Ds to consider can increase. To prevent this, MWPTS-C may require adjusting the output powers for miscellaneous communication methods.

Figure 3 Physical and Spatial Elements

The MWPTS network operates based on the TDMA (Time Division Multiple Access) communication method and it is managed by MWPTS-C. In addition power is distributed by the request of MWPTS-Ds and decision of MWPTS-C. Furthermore, various procedures including recognition, authentication, analysis, and termination are performed using the TDMA approach to transfer power to multiple devices.

Figure 4 General Procedure for TDMA-based MWPTS

6.2. WPT Flow Charts

TBD

6.2.1. WPT TX Flow Charts

TBD

6.2.2. WPT RX Flow Charts

TBD

6.3. MWPTS System Structure

6.3.1. System Structure

In order to transfer wireless power to multiple devices, communication and charging must be considered. Those actions are mainly performed based on the scheduling information. The wireless power transfer system has the following hierarchical layers:

Figure 5 Hierarchical View of Wireless Power Transfer System

The application block performs the entire system operation and management for wireless power transfer to multiple devices. For this purpose, required data can be exchanged between the power transmitter (MWPTS-C) and power receiver (MWPTS-D). The management block manages the operation of MWPTS-C and MWPTS-D including the coupler that transfers actual power.

6.3.2. Command Sets for interfacing blocks

TBD

6.4. Primitives between Application Blocks

6.4.1. General

This standard mainly focuses on the primitives between application blocks, between management block and application block, between management block and MAC layer, and between management block and a coupler for managing multi device charging. It does not handle the primitives exchange for communication-related parts such as between MAC layer and physical layer and between MAC layers.

In order to perform the functions defined in Chapter 5, the primitives including commands and data shall be exchanged between application blocks of MWPTS-C and MWPTS-D for efficient wireless power transfer. The system management and control shall be accompanied based on the exchanged parameters. The primitives exchanged between application blocks are as follows:

6.4.2. MWPTS-D ID Information

6.4.2.1. General

Based on the ID data from MWPTS-D, MWPTS-C determines whether the power receiver is eligible or not for the service. The definition of the primitive is as follows:

ATA-SCAN.request {

Req_join,

Dev_id,

}

6.4.2.2. MWPTS-D ID Request

6.4.2.2.1. Required Time

It is required when the wireless power transfer system sends the connection requests to MWPTS-Ds.

6.4.2.2.2. Result

MWPTS-D receives the ID request command from the MWPTS-C.

6.4.2.3. MWPTS-D ID Response

6.4.2.3.1. Required Time

It is required when the response is ready for the ID request from MWPTS-C.

6.4.2.3.2. Result

MWPTS-C receives the ID data from MWPTS-Ds. The data is used for MWPTS-C to determine whether the corresponding MWPTS-D is eligible for the wireless power transfer service.

6.4.3. Wireless Power Transfer Service Possibility Notification

6.4.3.1. General

MWPTS-C determines whether each MWPTS-D is eligible for wireless power transfer based on the received ID data and informs all MWPTS-Ds of the result. The definition of the primitives is as follows:

ATA-Service.inform {

Accept_deny,

Dev_num,

}

6.4.3.2. Required Time

It is required for MWPTS-C to determine whether the service is eligible or not and informs the corresponding MWPTS-D of the result.

6.4.3.3. Result

It selects eligible MWPTS-Ds for the service and provides the service to those MWPTS-Ds in the future.

6.4.4. MWPTS-D Information

6.4.4.1. General

This primitive is exchanged between MWPTS-C and an MWPTS-D for optimal power transfer according to the situation. The definition of the primitives is as follows:

ATA-DEV.request {

Frequency,

BattRemain,

BattDischarge,

MaxPwr,

Pwr,

Type,

RSSI,

}

6.4.4.2. MWPTS-D Information Request

6.4.4.2.1. Required Time

Before performing the wireless power transfer, it is required to recognize the wireless power transfer status.

6.4.4.2.2. Result

MWPTS-C acquires the required charging information from all MWPTS-Ds.

6.4.4.3. MWPTS-D Information Response

6.4.4.3.1. Required Time

It is required when the MWPTS-D information is ready to send the charging data to MWPTS-C.

6.4.4.3.2. Result

MWPTS-C acquires the required charging information from all MWPTS-Ds, and manages and controls for optimal wireless power transfer.

6.4.5. Charging zone/Communication zone Recognition

6.4.5.1. General

MWPTS-C determines each MWPTS-D belongs to which zone (charging zone or communication zone) based on the data sent from MWPTS-Ds, and informs those MWPTS-Ds of the result. The definition of the primitives is as follows:

ATA-ZONE.inform {

Zone,

}

6.4.5.2. Required Time

It is required for the MWPTS-C management block to determine the zone of each MWPTS-D and to send the result to the MWPTS-C application block.

6.4.5.3. Result

After determining the zones of all MWPTS-Ds, MWPTS-C prepares wireless power transfer service for MWPTS-Ds under the charging zone and keeps the standby status for MWPTS-Ds under the communication zone. When an MWPTS-D under the communication zone reaches the charging zone, the service is prepared.

6.4.6. MWPTS Mode Inform

6.4.6.1. General

Based on the collected information from all MWPTS-Ds, MWPTS-C computes and determines the best charging mode, and informs the selected charging mode to all MWPTS-Ds. The definition of the primitives is as follows:

ATA-Mode.inform {

CharMode,

}

6.4.6.2. Required Time

It is required when the MWPTS-C application block selects MWPTS mode and inform the MWPTS-D application block of the selected mode.

6.4.6.3. Result

After the MWPTS-D application block recognizes the MWPTS mode, preparation for receiving power is possible according to the direction from MWPTS-C.

6.4.7. MWPTS Mode Response

6.4.7.1. Required Time

It is required when the application block of an MWPTS-D receives the MWPTS mode from the MWPTS-C application block and informs the MWPTS-C application block of the response.

6.4.7.2. Result

After MWPTS-C confirms the response of an MWPTS-D, it starts the specified wireless power transfer mode.

6.4.8. Scheduling Information

6.4.8.1. General

It is the information used in the time-division prioritized charging mode. It includes the wireless power transfer priority and allocated time for each power receiver after scheduling. The definition of the primitives is as follows:

ATA-SCHEDULING.inform {

Priority,

TimeAmount,

}

6.4.8.2. Scheduling Information Notification

6.4.8.2.1. Required Time

It is required to inform each device of the scheduling information after calculating the scheduling value in the time-division prioritized charging mode.

6.4.8.2.2. Result

By informing the priority data, it prevents confusion of the wireless charging and performs the scheduling.

6.4.8.3. Scheduling Information Response

6.4.8.3.1. Required Time

It is required when the response is sent to MWPTS-C after receiving the scheduling data.

6.4.8.3.2. Result

MWPTS-C can check the response of MWPTS-D and perform the scheduling-based wireless power transfer.

6.4.9. Abnormal Situations Management Information and Commands

6.4.9.1. General

In case of any abnormal situation, MWPTS-C recognizes it and informs the corresponding MWPTS-D of the situation including the eligible command information. The definition of the primitives is as follows:

ATA-ABNORMAL.inform {

Abnormal,

CharOff,

Pwr

}

6.4.9.2. Abnormal Situations Management

6.4.9.2.1. Required Time

It is required when MWPTS-C recognizes a abnormal situation and provide a solution.

6.4.9.2.2. Result

In case of any abnormal situation, MWPTS-C sends information and command to the MWPTS-D application block for control.

6.4.9.3. Abnormal Situations Management Response

6.4.9.3.1. Required Time

It is required when an MWPTS-D provides the observed value and required information to MWPTS-C to solve an abnormal situation.

6.4.9.3.2. Result

MWPTS-C gets information from an MWPTS-D to make accurate and quick decision or action.

6.4.10. MWPTS-D Full Charge Notification

6.4.10.1. General

When an MWPTS-D is fully charged, MWPTS-D notifies MWPTS-C of this event. The definition of the primitives is as follows:

ATA-FULL.inform {

Full,

}

6.4.10.2. MWPTS-D Full Charge Notification

6.4.10.2.1. Required Time

It is required when full charge of an MWPTS-D needs to be informed to MWPTS-C.

6.4.10.2.2. Result

After MWPTS-C recognizing this event, it stops the power transfer service for the MWPTS-D and excludes the MWPTS-D from the service candidates.

6.4.10.3. MWPTS-D Full Charge Notification Response

6.4.10.3.1. Required Time

It is required when an MWPTS-C is ready to send the response packet for full charge notification.

6.4.10.3.2. Result

It informs the response to the notified MWPTS-D.

6.4.11. Power Transfer Termination Notification

6.4.11.1. General

When terminating the wireless power transfer by the request of user, the termination command is sent to all MWPTS-Ds to terminate the current power transfer service. The definition of the primitives is as follows:

ATA-END.inform {

End,

}

6.4.11.2. Power Transfer Termination Notification

6.4.11.2.1. Required Time

It is required when terminating the wireless power transfer by the request of user.

6.4.11.2.2. Result

The wireless power transfer is stopped.

6.4.11.3. Power Transfer Termination Reception Response

6.4.11.3.1. Required Time

It is required when sending the response after an MWPTS-D receives the wireless power transfer termination notification.

6.4.11.3.2. Result

It checks whether the MWPTS-D has received the power transfer stop event or not.

6.5. Primitives between Application and Management Blocks at MWPTS-C

6.5.1. Genaral

MWPTS-C application block performs management and control to efficiently provide wireless power transfer to multiple devices with information received from MWPTS-Ds. For MWPTS-C management and control, the application block performs various actions together with the management block.

6.5.2. Checking ID

The MWPTS-C application block sends the received MWPTS-D ID information to the MWPTS-C management block. After checking the corresponding device is eligible to receive the wireless power transfer service, it is informed to the application block with the required information. The definition of the primitives is as follows:

CATM-QUALIFICATION.request {

Req_qualification,

Dev_id,

Rsp_qualification,

}

6.5.2.1. ID Checking Request

6.5.2.1.1. Required Time

After receiving the ID information of an MWPTS-D from the MWPTS-D application block, the MWPTS-C application block determines whether or not to provide the service.

6.5.2.1.2. Result

After receiving the ID information of all MWPTS-Ds from the MWPTS-C application block, the MWPTS-C management block determines whether or not to receive the service.

6.5.2.2. ID Checking Response

6.5.2.2.1. Required Time

It is required when the MWPTS-C management block determines all MWPTS-Ds are eligible for the service based on the ID information received from the MWPTS-C application block and informs the application block of the information.

6.5.2.2.2. Result

It sends qualification of all MWPTS-Ds for WPT to the MWPTS-C application block.

6.5.3. Charging Zone/Communication Zone Recognition

6.5.3.1. General

When the MWPTS-C application block sends the received signal strength information received from the MWPTS-D application block to the MWPTS-C management block, the MWPTS-C management block determines to which zone (charging zone/communication zone) the MWPTS-D belongs. It includes the related information. The definition of the primitives is as follows:

CATM-ZONE.inform {

Req_Zone,

RSSI,

Rsp_Zone

}

6.5.3.2. Charging Zone/Communication Zone Recognition Request

6.5.3.2.1. Required Time

It is required when determining the location of MWPTS-D with the MWPTS-C application block providing the signal reception strength to the MWPTS-C management block,

6.5.3.2.2. Result

The MWPTS-C management block determines each MWPTS-D belongs to which zone (charging zone/communication zone) based on the received data.

6.5.3.3. Charging Zone/Communication Zone Recognition Response

6.5.3.3.1. Required Time

It is required when the MWPTS-C management block sends the zone information to the MWPTS-C application block after completing the zone recognition of each MWPTS-D.

6.5.3.3.2. Result

When the zone recognition information is sent to the MWPTS-C application block, the MWPTS-C application block notifies all MWPTS-D application blocks of the location recognition result and prepares the service for the MWPTS-Ds under the charging zone.

6.5.4. Wireless Power Transfer Frequency Control

6.5.4.1. General

In case of MWPTS-C that can support multiple wireless power transfer frequency bands, when a chargeable frequency is received from an MWPTS-D, the frequency information includes parameters for coupler setting creation and control for the management block. The definition of the primitives is as follows:

CATM-FREQ.control {

Dev_num,

Req_FreqControl,

}

6.5.4.2. Required Time

It is required when frequency change has to be followed before performing wireless power transfer.

6.5.4.3. Result

It notifies the management block of the corresponding frequency and the management block controls the coupler to perform wireless power transfer for the frequency.

6.5.5. Coupler Control and Command

6.5.5.1. General

In order to provide wireless power transfer to multiple devices with the consideration of the situation, it is required to control the coupler of MWPTS-C for receiving power at an optimal efficiency. For this purpose, it should include required information. The definition of the primitives is as follows:

CATM-COUPLER.control {

Dev_num,

Req_FreqControl,

}

6.5.5.2. Required Time

It is required when transferring power at a best efficiency after recognizing wireless communication status of the current MWPTS-D or all MWPTS-Ds.

6.5.5.3. Result

When the required status information is sent to the management block for the current coupler control, the management block generates the parameters to control the coupler based on the given information.

6.5.6. Output Power Level Control

6.5.6.1. General

In order not to violate the regulation and not to damage MWPTS-Ds, the output power of MWPTS-C shall be controlled so the required information for power control shall be included considering the power level depending on the MWPTS-D type. The definition of the primitives is as follows:

CATM-POWER.control {

Dev_num,

Req_PwrControl,

}

6.5.6.2. Required Time

It is required when controlling the output power of MWPTS-C considering the charging status such as MWPTS-D type, location, alignment, regulations, etc.

6.5.6.3. Result

The management block calculates the output power based on the charging status information received from the application block and informs the coupler to perform power control.

6.5.7. Scheduling Information

6.5.7.1. General

When the residual battery levels and battery discharge rates of all power receivers are received from the application blocks, the management block calculates parameters for scheduling based on the received data, and the scheduling result is sent to the application block. The definition of the primitives is as follows:

CATM-SCHEDULING.request {

Dev_num,

BattRemain,

BattDischarge,

Priority,

TimeAmount,

}

6.5.7.2. Request for Scheduling

6.5.7.2.1. Required Time

It is required when determining the sequences and times allocated for multiple devices in the time-division charging mode before the service starts.

6.5.7.2.2. Result

The management block derives the parameters for scheduling by performing the scheduling algorithm based on the residual battery level and discharge rate.

6.5.7.3. Scheduling Response

6.5.7.3.1. Required Time

It is required when replying with the scheduling result to the application block after the management block performs scheduling based on the scheduling request from the application block.

6.5.7.3.2. Result

It sends the scheduling result to the application block, which informs the result to all MWPTS-Ds to control the coupling of MWPTS-C according to the algorithm.

6.5.8. MWPTS-C Current/Voltage Sensing

6.5.8.1. General

MWPTS-C requires the current and voltage sensing information for power level control and impedance matching. The definition of the primitives is as follows:

CATM-SENSING.request {

Imp_change,

Current,

Voltage,

Impedance,

Change_inform,

}

6.5.8.2. MWPTS-C Current/Voltage Sensing Request

6.5.8.2.1. Required Time

The current and voltage values are always sensed during wireless power transfer to MWPTS-Ds.

6.5.8.2.2. Result

The sensing values helps MWPTS-C recognize unexpected occurrences, control the output power level, and perform the impedance matching.

6.5.8.3. MWPTS-C Current/Voltage Sensing Response

6.5.8.3.1. Required Time

It is required when the management block informs the application block of the measured value and calculated impedance value whose variations are greater than a certain threshold value.

6.5.8.3.2. Result

The application bock performs abnormal situation management, output power level control, and impedance matching based on the values of the calculated impedance and current/ voltage received from the management block.

6.5.9. MWPTS-D Full Charge

6.5.9.1. Genaral

When an MWPTS-D informs MWPTS-C of full charge, MWPTS-C stops wireless power transfer and it prepares for wireless power transfer to other MWPTS-Ds. The definition of the primitives is as follows:

CATM-Full.control {

Dev_Num,

Req_FullControl

}

6.5.9.2. Required Time

It is required when a full charge event has been sent from the MWPTS-D application block to the MWPTS-C application block.

6.5.9.3. Result

The MWPTS-C application block requests the wireless power transfer termination due to full charge to the MWPTS-C management block.

6.5.10. Wireless Power Transfer Termination

6.5.10.1. General

When wireless power transfer termination request is received from a user, the MWPTS-C application block stops the current service. The required information for termination is included. The definition of the primitives is as follows:

CATM-Full.control {

Req_EndControl

}

6.5.10.2. Required Time

It is required when the MWPTS-C application block receives the wireless power transfer termination request from a user.

6.5.10.3. Result

The MWPTS-C application block requests wireless power transfer termination to the MWPTS-C management block.

6.6. Primitives between Management Block and MAC Layer at MWPTS-C

6.6.1. General

The management block of MWPTS-C communicates with the MAC layer to support data exchange between application blocks of both MWPTS-C and MWPTS-D. The management block has the look-up table in which the MWPTS-D address of application block maps to its MAC address. In addition, the management block sends the frame type information to the MAC layer in order to create the proper frame in the MAC layer. The contents exchanged between the management block and MAC layer are as follows:

6.6.2. MWPTS-D ID Information

The management block sends the MAC address (received MWPTS-D ID from the application block) and type information (for MWPTS-D ID request) to the MAC layer so that it creates the proper packets according to the received type and send the packets to the MWPTS-D. The definition of the primitives is as follows:

CMTM-SCAN.request {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Req_join,

Dev_id,

}

6.6.2.1. MWPTS-D ID Information Request

6.6.2.1.1. Required Time

It is required when the MWPTS-C management block receives the parameters for join request from the MWPTS-C application block.

6.6.2.1.2. Result

The MAC layer of MWPTS-C sends the ID information request command to the MWPTS-D through the physical layer.

6.6.2.2. MWPTS-D ID Information Reception

6.6.2.2.1. Required Time

It is required for MWPTS-C to send the ID information received from the MWPTS-D to the application block through the MWPTS-C management block.

6.6.2.2.2. Result

The MWPTS-C management block sends the MWPTS-D ID information to the application block. The information is used for MWPTS-C to determine whether the MWPTS-D is eligible for the wireless power transfer service.

6.6.3. Wireless Power Transfer Serviceability Notification

6.6.3.1. General

The management block receives the MWPTS-D ID and eligibility information from the MWPTS-C application block, and notifies the MWPTS-D of them. The definition of the primitives is as follows:

CMTM-Service.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Accept_deny,

Dev_num,

}

6.6.3.2. Required Time

It is required when the MWPTS-C application block has sent the MWPTS-D ID and eligibility information to the management block.

6.6.3.3. Result

The MWPTS-C MAC layer sends the received parameters to the MWPTS-D through the physical layer.

6.6.4. MWPTS-D Information

6.6.4.1. General

It is the primitive that the MWPTS-C management block exchanges for wireless power transfer status recognition of MWPTS-Ds using the MAC layer to recognize wireless power transfer status. The definition of the primitives is as follows:

CMTM-DEV.request {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Frequency,

BattRemain,

BattDischarge,

MaxPwr,

Pwr,

Type,

RSSI,

}

6.6.4.2. MWPTS-D Information Request

6.6.4.2.1. Required Time

Before performing the wireless power transfer, it is required when the MWPTS-C application block has sent the information for wireless power transfer status request to the management block.

6.6.4.2.2. Result

The MWPTS-C MAC layer sends the wireless power transfer status request to the MWPTS-D through the physical layer.

6.6.4.3. MWPTS-D Information Response

6.6.4.3.1. Required Time

It is required when the MWPTS-C MAC layer sends the received MWPTS-D information to the management block.

6.6.4.3.2. Result

The MWPTS-C management block sends the received charging information to the MWPTS-C application block.

6.6.5. Charging Zone/Communication Zone Recognition Method

6.6.5.1. General

The MWPTS-C management block sends the zone information of the MWPTS-D (charging zone or communication zone) to the MWPTS-D through the MAC layer. The definition of the primitives is as follows:

CMTM-ZONE.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Zone,

}

6.6.5.2. Required Time

It is required when the MWPTS-C management block has received the request of the zone information of all MWPTS-Ds from the application block.

6.6.5.3. Result

The MWPTS-C MAC layer sends the zone information (communication or charging zone) request to all MWPTS-Ds through the physical layer.

6.6.6. Power Transfer Mode Notification

6.6.6.1. General

When the MWPTS-C application block determines the optimal wireless power transfer mode based on the charging information, the management block sends the received information to the corresponding MWPTS-Ds through the MAC layer. The definition of the primitives is as follows:

CMTM-MODE.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

CharMode,

}

6.6.6.2. Required Time

It is required when the MWPTS-C management block sends the wireless power transfer mode received from the application block to the target MWPTS-D through the MAC layer.

6.6.6.3. Result

The MWPTS-C MAC layer sends the charging mode to the desired MWPTS-D through the physical layer.

6.6.7. Power Transfer Mode Reception Response

6.6.7.1. Required Time

It is required when the MAC layer that has received the charging mode reception response, and informs the management block of the response.

6.6.7.2. Result

The MWPTS-C management block that has received the reception confirmation, sends the related information to the application block.

6.6.8. Scheduling Information

6.6.8.1. General

In the time-division priority charging mode, the MWPTS-C management block sends the received scheduling information to the MAC layer to send it to the target MWPTS-D. The definition of the primitives is as follows:

CMTM-SCHEDULING.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Priority,

TimeAmount,

}

6.6.8.2. Scheduling Information Notification

6.6.8.2.1. Required Time

It is required when the MWPTS-C management block sends the received scheduling information to the MAC layer.

6.6.8.2.2. Result

The MAC layer that has received the scheduling information sends the corresponding information to MWPTS-Ds through the physical layer.

6.6.8.3. Scheduling Information Response

6.6.8.3.1. Required Time

It is required when the MWPTS-C MAC layer sends the received scheduling reception information from an MWPTS-D to the management block.

6.6.8.3.2. Result

The MWPTS-C management block sends the received response information to the application block.

6.6.9. Abnormal Situation Management Information and Command

6.6.9.1. General

In case of any abnormal situation, the management block that has received the related information from the application block, informs the related MWPTS-D of it through the MAC layer. The definition of the primitives is as follows:

CMTM-ABNORMAL.inform {

Cmd_mode,

SrcMAC_id,

DstMAC_id,

Abnormal,

CharOff,

Pwr

}

6.6.9.2. Abnormal Situation Management Information and Command Provision

6.6.9.2.1. Required Time

It is required when the MWPTS-C application block sends the received abnormal situation information to the MAC layer.

6.6.9.2.2. Result

The MAC layer that has received abnormal situation information sends the related information to MWPTS-Ds through the physical layer.

6.6.9.3. Abnormal Situation Management Information Response

6.6.9.3.1. Required Time

It is required when the MWPTS-C MAC layer that has received the measured data and required information from an MWPTS-D, it provides the information to the management block to resolve the situation.

6.6.9.3.2. Result

The MWPTS-C management block that has received the measured data and required information of an MWPTS-D, sends the information to the application block.

6.6.10. MWPTS-D Full Charge Notification

6.6.10.1. General

CMTM-FULL.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Full,

}

6.6.10.2. MWPTS-D Full Charge Notification

6.6.10.2.1. Required Time

It is required when the MWPTS-C MAC layer that has received the full charge of an MWPTS-D, it informs the management block of the related information.

6.6.10.2.2. Result

The MWPTS-C management block that has received a full charge event, informs the application block of the event.

6.6.11. Power Transfer Termination Notification

6.6.11.1. General

When terminating the wireless power transfer by the request of user, the termination process is conducted by MWPTS-C. The definition of the primitives is as follows:

CMTM-END.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

End,

}

6.6.11.2. Power Transfer Termination Notification

6.6.11.2.1. Required Time

It is required when the management block that has received a wireless power transfer termination event, sends the related information to the MAC layer.

6.6.11.2.2. Result

The MAC layer that has received a wireless power transfer termination event sends the related information to the MWPTS-D through the physical layer.

6.6.11.3. Power Transfer Termination Reception Response

6.6.11.3.1. Required Time

It is required when the MAC layer that has received a wireless power transfer termination reception response, sends the related information to the management block.

6.6.11.3.2. Result

The MWPTS-C management block that has received the termination reception response, sends the related information to the application block.

6.7. Primitives between Couplers and Management Block at MWPTS-C

6.7.1. General

It defines the primitives between the coupler and the MWPTS-C management block for coupler management and control.

6.7.2. Wireless Power Transfer Frequency Control

6.7.2.1. General

It includes information for selection of frequency band that is used to transfer the current wireless power with the coupler. The definition of the primitives is as follows:

CMTC-FREQ.control {

Req_FreqControl,

}

6.7.2.2. Required Time

It is required when the management block calculates parameters for frequency change and provides them to the coupler when frequency change request is received.

6.7.2.3. Result

The management block calculates parameters to control the wireless power transfer frequency and sends them to the coupler.

6.7.3. Coupler Control

For optimization of impedance matching that varies depending on the situation, the impedance matching for the coupler is required. The required information is included. The definition of the primitives is as follows:

CMTC-COUPLER.control {

Req_MatchingControl,

}

6.7.3.1. Required Time

It is required when the management block calculates parameters for coupler change and provides them to the coupler when coupler control change request is received from an application block.

6.7.3.2. Result

The management block calculates parameters for coupler and matching control and sends them to the coupler.

6.7.4. Output Power Level Control

6.7.4.1. General

It includes information for the management block to control the coupler for output power level control of MWPTS-C. The definition of the primitives is as follows:

CMTC-POWER.control {

Req_PwrControl,

}

6.7.4.2. Required Time

It is required when the management block calculates parameters for output power level change and provides them to the coupler when output power level change request is received from an application block.

6.7.4.3. Result

With the received parameters, the coupler controls the output power level.

6.7.5. Scheduling Control

6.7.5.1. General

It includes information for the management block to control the coupler for priority handling in the time division charging mode. The definition of the primitives is as follows:

CMTC-SCHEDULING.control {

Req_SchedulingControl,

}

6.7.5.2. Required Time

It is required when the management block calculates parameters for scheduling and provides them to the coupler when scheduling request is received from an application block.

6.7.5.3. Result

With the received parameters, the coupler controls to perform power transfer service according to scheduling information.

6.7.6. Voltage/Current Sensing

6.7.6.1. General

It includes information required for the management block to perform coupler control through measurement of current and voltage that support for abnormal situation sensing and matching control. The definition of the primitives is as follows:

CMTC-SENSING.request {

Current,

Voltage,

}

6.7.6.2. Voltage/Current Sensing Request

6.7.6.2.1. Required Time

Voltage and current values are always sensed while MWPTS-C is performing the wireless power transfer service.

6.7.6.2.2. Result

The management block calculates parameters for voltage/current sensing and sends them to the coupler.

6.7.6.3. Voltage/Current Sensing Response

6.7.6.3.1. Required Time

It is required when providing the voltage and current measured during wireless power transfer to the management block on a specific interval basis.

6.7.6.3.2. Result

It sends the measured current and voltage to the management block as the response.

6.7.7. MWPTS-D Full Charge

6.7.7.1. General

When an MWPTS-D informs MWPTS-C of full charge, MWPTS-C stops the wireless power transfer by control of the coupler. The definition of the primitives is as follows:

CMTC-Full.control {

Req_FullControl

}

6.7.7.2. Required Time

It is required when the MWPTS-C management block receives the full charge event from the MWPTS-C application block.

6.7.7.3. Result

The MWPTS-C management block requests the wireless power transfer termination by full charge to the coupler of MWPTS-C.

6.7.8. Wireless Power Transfer Termination

6.7.8.1. General

When wireless power transfer termination request is received from a user, the MWPTS-C application block stops the current service and includes the required information until the request of the next user is received. The definition of the primitives is as follows:

CMTC-Full.control {

Req_EndControl

}

6.7.8.2. Required Time

It is required when the MWPTS-C management block receives the wireless power transfer termination request from the MWPTS-C application block.

6.7.8.3. Result

The MWPTS-C management block requests the wireless power transfer termination to the MWPTS-C coupler for the corresponding user.

6.8. Primitives between MWPTS-D Application block and Management block

6.8.1. General

It defines the primitives between the MWPTS-D application block and management block for the MWPTS-D application block to prepare the required information for wireless charging or to control the coupler of MWPTS-D when an MWPTS-C application block request is received.

6.8.2. MWPTS-D ID Information

It includes information for preparation to provide the MWPTS-D ID data for the ID request of MWPTS-C. The definition of the primitives is as follows:

DATM-DEVID.request {

Req_id,

Rsp_id,

}

6.8.2.1. MWPTS-D ID Request

6.8.2.1.1. Required Time

It is required when the MWPTS-D ID request is received from the application block of MWPTS-C.

6.8.2.1.2. Result

The MWPTS-D application block requests the ID information of MWPTS-D.

6.8.2.2. MWPTS-D ID Response

6.8.2.2.1. Required Time

It is required when the MWPTS-D management block has completed the ID information preparation to send to the MWPTS-D application block.

6.8.2.2.2. Result

The MWPTS-D application block prepares to send the ID information from the management block to the MWPTS-C application block.

6.8.3. MWPTS-D Information

6.8.3.1. General

In order to provide optimal power transfer depending on the situation, it includes information that the MWPTS-D prepares and sends according to the request of MWPTS-C. The definition of the primitives is as follows:

DATM-DEVINFO.request {

Req_Devinfo,

Freq,

MaxPwr,

BattRemain,

BattDischarge,

Pwr,

Type,

RSSI,

}

6.8.3.2. MWPTS-D Information Request

6.8.3.2.1. Required Time

It is required when the MWPTS-D information request is received from the MWPTS-C application block.

6.8.3.2.2. Result

The MWPTS-D application block requests the information of MWPTS-D to the MWPTS-D management block.

6.8.3.3. MWPTS-D Information Response

6.8.3.3.1. Required Time

It is required when the MWPTS-D management block has completed the MWPTS-D information preparation to send to the MWPTS-D application block.

6.8.3.3.2. Result

6.8.4. Scheduling Control

6.8.4.1. General

The MWPTS-D application block controls the coupler of MWPTS-D through the MWPTS-D management block based on the scheduling information from the MWPTS-C application block and includes the required information. The definition of the primitives is as follows:

DATM-SCHEDULING.request {

Req_SchedulingControl

Priority,

TimeAmount,

}

6.8.4.2. Required Time

It is required when the MWPTS-D receives the scheduling information from the MWPTS-C application block.

6.8.4.3. Result

The MWPTS-D application block sends the received scheduling information for the MWPTS-D management block to calculate the parameters for coupler control.

6.8.5. Current/Voltage Sensing

6.8.5.1. General

When the reception power level request is received from the MWPTS-C application block, it senses the current and voltage, performs power calculation, and includes information to send the information to the MWPTS-C application block. The definition of the primitives is as follows:

DATM-SENSING.request {

Current,

Voltage,

Pwr,

}

6.8.5.2. Current/Voltage Sensing Request

6.8.5.2.1. Required Time

It is required when the request for the test power reception level and reception power level is received from the MWPTS-C application block.

6.8.5.2.2. Result

The MWPTS-D application block requests the reception power level to the MWPTS-D management block based on the current and voltage sensing.

6.8.5.3. Current/Voltage Sensing Response

6.8.5.3.1. Required Time

It is required when the request is received from the MWPTS-D application block and the reception power level is calculated through the current and voltage sensing.

6.8.5.3.2. Result

The MWPTS-D management block sends the current/voltage sensing information or reception power level information to the MWPTS-D application block. This information is used for output power control of MWPTS-C.

6.8.6. Unexpected Occurrence Control

6.8.6.1. General

It includes information to solve an unexpected occurrence. MWPTS-D application block solves the problem based on the unexpected occurrence control information from the MWPTS-C application block. The definition of the primitives is as follows:

DATM-ABNORMAL.request {

Req_AbnormalControl,

}

6.8.6.2. Required Time

It is required when the MWPTS-D receives the unexpected occurrence control information from the MWPTS-C application block.

6.8.6.3. Result

The MWPTS-D application block sends the reception control information for the MWPTS-D management block to calculate the parameters for coupler control based on the received unexpected occurrence control information.

6.8.7. Power Transfer Termination Control

6.8.7.1. General

When the power transfer termination control is received from the MWPTS-C application block, the MWPTS-D application block includes information for MWPTS-D coupler control to terminate power transfer through the MWPTS-D management block. The definition of the primitives is as follows:

DATM-END.request {

Req_EndControl,

}

6.8.7.2. Required Time

It is required when the MWPTS-D receives the power transfer control information from the MWPTS-C application block.

6.8.7.3. Result

The MWPTS-D application block controls the coupler by sending the control information to the MWPTS-D management block for power transfer termination control.

6.8.8. Full Charge Notification

6.8.8.1. General

When the battery of MWPTS-D is fully charged, the receiver stops receiving power and sends the related information to MWPTS-C for power transfer termination. Accordingly, the MWPTS-D will exclude the MWPTS-D from the receivers for next wireless power transfer. The definition of the primitives is as follows:

DATM-FULL.request {

Inf_Full

Req_FullControl,

}

6.8.8.2. Required Time

It is required when the MWPTS-D management block confirms the full charge of the battery.

6.8.8.3. Result

6.8.9. Discharge Rate Change Notification

6.8.9.1. General

When an MWPTS-D senses the battery discharge rate change, it sends the related information to MWPTS-C for scheduling and power control. The definition of the primitives is as follows:

DATM-BATT.inform {

Inf_Batt,

Inf_BattChange,

}

6.8.9.2. Required Time

It is required when the MWPTS-D management block confirms the battery discharge rate change.

6.8.9.3. Result

The MWPTS-D management block informs the MWPTS-D application block of the battery discharge rate change and the amount of variation.

6.9. Primitives between Management Block and MAC Layer at MWPTS-D

6.9.1. General

The MWPTS-D management block receives a command and sends the response data through the MAC layer to exchange data between MWPTS-C and an MWPTS-D application block. The management block controls to response or send data to the correct MWPTS-C or MWPTS-D. The contents exchanged between the management block and MAC layer for control are as follows:

6.9.2. MWPTS-D ID Information

The MAC layer sends the MWPTS-D ID request from MWPTS-C to the management block. In addition, when the management block receives the MWPTS-D ID information from the application block, it sends the ID information through the MAC layer. The definition of the primitives is as follows:

DMTM-SCAN.request {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Req_join,

Dev_id,

}

6.9.2.1. MWPTS-D ID Request Reception

6.9.2.1.1. Required Time

It is required when an MWPTS-D management block receives the MWPTS-D ID request packet from MWPTS-C and sends the related information to the management block.

6.9.2.1.2. Result

The MWPTS-D management block sends the MWPTS-D ID request information to the application block.

6.9.2.2. MWPTS-D ID Information Response

6.9.2.2.1. Required Time

It is required when an MWPTS-D management block receives the response information for the ID request from the application block and sends it to the MAC layer.

6.9.2.2.2. Result

The MWPTS-D MAC layer sends the response ID information to MWPTS-C through the physical layer.

6.9.3. Wireless Power Transfer Serviceability Reception

6.9.3.1. General

The MAC layer that has received the serviceability information from MWPTS-C, sends the related information to the management block. The definition of the primitives is as follows:

DMTM-Service.inform {

SrcMAC_id,

DstMAC_id,

Accept_deny,

}

6.9.3.2. Required Time

It is required when the MWPTS-D MAC layer receives the serviceability information from MWPTS-C and sends it to the management block.

6.9.3.3. Result

The management block that has received the serviceability information, sends it to the application block.

6.9.4. MWPTS-D Information

6.9.4.1. General

The MWPTS-D MAC layer that has received a wireless power transfer status request from MWPTS-C, sends the related information to the management block. The management block that has received the status information from the application block as a response for the request, exchanges this information to send the related information to the MAC layer. The definition of the primitives is as follows:

DMTM-DEV.request {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Frequency,

BattRemain,

BattDischarge,

MaxPwr,

Pwr,

Type,

RSSI,

}

6.9.4.2. MWPTS-D Information Request Reception

6.9.4.2.1. Required Time

6.9.4.2.2. Result

The MWPTS-D management block that has received a request, send the information to the application block.

6.9.4.3. MWPTS-D Information Response

6.9.4.3.1. Required Time

It is required when the MWPTS-D management block must send the wireless power transfer status received from the application block to the MAC layer.

6.9.4.3.2. Result

The MAC layer that has received the status information sends the information to MWPTS-C through the physical layer.

6.9.5. Charging Zone/Communication Zone Recognition Method

6.9.5.1. General

The MWPTS-D MAC layer sends the location information (charging zone or communication zone) from MWPTS-C to the target MWPTS-D management block. The definition of the primitives is as follows:

DMTM-ZONE.inform {

SrcMAC_id,

DstMAC_id,

Zone,

}

6.9.5.2. Required Time

It is required when the MWPTS-D MAC layer receives the location information of the MWPTS-D and sends it to the management block.

6.9.5.3. Result

The management block that has received the location information, sends the information to the application block.

6.9.6. Power Transfer Mode Reception

6.9.6.1. General

The MWPTS-D MAC layer sends the wireless power transfer mode received from MWPTS-C to the management block and sends the reception check packet received from the management block to MWPTS-C. The definition of the primitives is as follows:

DMTM-MODE.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

CharMode,

}

6.9.6.2. Required Time

It is required when the MWPTS-D MAC layer sends the wireless power transfer mode received from MWPTS-C to the management block.

6.9.6.3. Result

The management block that has received a wireless power transfer mode, sends the related information to the application block.

6.9.6.4. Power Transfer Mode Reception Response Transmission

6.9.6.4.1. Required Time

It is required when the MWPTS-D management block receives the reception response from the application block and sends it to the MAC layer.

6.9.6.4.2. Result

The MAC layer that has received a reception response sends the related information to MWPTS-C through the physical layer.

6.9.7. Scheduling Information

6.9.7.1. General

In the time-division priority charging mode, the MAC layer sends the scheduling information received from MWPTS-C to the management block and the management block sends the response information for scheduling received from the application block to the MAC layer to send it to MWPTS-C. The definition of the primitives is as follows:

DMTM-SCHEDULING.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Priority,

TimeAmount,

}

6.9.7.2. Scheduling Information Reception

6.9.7.2.1. Required Time

It is required when the MWPTS-D MAC layer sends the scheduling information received from MWPTS-C to the management block.

6.9.7.2.2. Result

The management block that has received the scheduling information, sends the information to the application block.

6.9.7.3. Scheduling Information Response Transmission

6.9.7.3.1. Required Time

It is required when an MWPTS-D management block receives a response message for scheduling information reception check from the application block.

6.9.7.3.2. Result

The MAC layer that has received a reception response message sends the related information to MWPTS-C through the physical layer.

6.9.8. Abnormal Situation Management Information and Command

6.9.8.1. General

In case of any abnormal situation, when the MWPTS-D MAC layer that has received the related information from MWPTS-C, sends the information to the management block and the management block sends the received response information to the MAC layer. The definition of the primitives is as follows:

DMTM-ABNORMAL.inform {

Cmd_mode,

SrcMAC_id,

DstMAC_id,

Abnormal,

CharOff,

Pwr

}

6.9.8.2. Abnormal Situation Management Information and Command Reception

6.9.8.2.1. Required Time

It is required when the MAC layer that has received abnormal situation information, sends the related information to the management block.

6.9.8.2.2. Result

The management block that has received abnormal situation information, sends the information to the application block.

6.9.8.3. Abnormal Situation Management Information Response

6.9.8.3.1. Required Time

It is required when the management block that has received measured values and required information from the MWPTS-D application block, must provide the related information to the MAC layer to solve the situation.

6.9.8.3.2. Result

The MWPTS-D MAC layer sends the received information to MWPTS-C through the physical layer.

6.9.9. MWPTS-D Full Charge Notification

6.9.9.1. General

When an MWPTS-D is fully charged, the management block that has received the related information from the application block, sends the information to the MAC layer to send it to MWPTS-C. The definition of the primitives is as follows:

DMTM-FULL.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

Full,

}

6.9.9.2. Required Time

It is required when the MWPTS-D management block that has received the full charge of an MWPTS-D, informs the MAC layer of the related information.

6.9.9.3. Result

The MWPTS-D MAC layer sends the received full charge information to MWPTS-C through the physical layer.

6.9.10. Power Transfer Termination Notification

The MWPTS-D MAC layer receives the wireless power transfer termination notification and sends it to the management block and the management block sends the related information to the MAC layer. The definition of the primitives is as follows:

DMTM-END.inform {

Cmd_type,

SrcMAC_id,

DstMAC_id,

End,

}

6.9.10.1. Power Transfer Termination Notification Reception

6.9.10.1.1. Required Time

It is required when the MWPTS-D MAC layer that has received wireless power transfer termination information, sends the related information to the management block.

6.9.10.2. Result

The management block that has received wireless power transfer termination information, sends the related information to the application block.

6.9.10.3. Power Transfer Termination Reception Response Transmission

6.9.10.3.1. Required Time

It is required when the management block that has received wireless power transfer termination reception response from the application block, sends the related information to the MAC layer.

6.9.10.3.2. Result

The MAC layer that has received a termination reception response, sends the related information to MWPTS-C through the physical layer.

6.10. Primitives between MWPTS-D Management Block and Coupler

6.10.1. General

It defines the primitives between the MWPTS-D management block and coupler for coupler management and control of the MWPTS-D.

6.10.2. Scheduling Control

The MWPTS-D management block includes information for coupler control based on the received coupler control command to meet the scheduling. The definition of the primitives is as follows:

DMTC-SCHEDULING.request {

Req_SchedulingControl

}

6.10.2.1. Required Time

6.10.2.2. Result

The MWPTS-D management block controls the current coupler based on the received scheduling information.

6.10.3. Current/Voltage Sensing

6.10.3.1. General

The MWPTS-D management block performs the current/voltage sensing to sense the variation of the reception network or to calculate the reception power, and the management block defines the required information. The definition of the primitives is as follows:

DMTC-SENSING.request {

Req_Sensing,

Current,

Voltage,

}

6.10.3.2. Current/Voltage Sensing Request

6.10.3.2.1. Required Time

It requests sensing whenever wireless power is received for a specific time.

6.10.3.2.2. Result

The MWPTS-D management block sends the control command to the coupler to sense the voltage and current while receiving power.

6.10.3.3. Current/Voltage Sensing Response

6.10.3.3.1. Required Time

It is required when requesting the current/voltage sensing for the MWPTS-D management block to calculate the reception power.

6.10.3.3.2. Result

The MWPTS-D coupler sends the measured current and voltage to the MWPTS-D management block.

6.10.4. Abnormal Situation Control

6.10.4.1. General

The MWPTS-D management block controls the MWPTS-D coupler with the calculated parameters to solve an abnormal situation and includes the required information. The definition of the primitives is as follows:

DMTC-ABNORMAL.request {

Req_AbnormalControl,

}

6.10.4.2. Required Time

It is required when the abnormal situation control information is received from the MWPTS-D application block.

6.10.4.3. Result

The MWPTS-D management block controls the current coupler based on the received abnormal situation control information.

6.10.5. Power Transfer Termination Control

6.10.5.1. General

The MWPTS-D management block controls the coupler for power transfer termination and includes the related information. The definition of the primitives is as follows:

DMTC-END.request {

Req_EndControl,

}

6.10.5.2. Required Time

It is required when the power transfer termination control information is received from the MWPTS-D application block.

6.10.5.3. Result

The MWPTS-D management block controls the current coupler based on the received power transfer termination control information.

6.10.6. Full Charge Notification

6.10.6.1. General

When the battery of an MWPTS-D is fully charged, the coupler control is required for terminating the power transfer and the related information is included. The definition of the primitives is as follows:

DMTC-FULL.request {

Req_FullControl,

}

6.10.6.2. Required Time

6.10.6.3. Result

In order for the MWPTS-D management block not to receive power, it controls the MWPTS-D coupler.

7. Wireless Power Transfer Control Interface Protocol

7.1. General

It is the information that must be exchanged for efficient wireless power transfer. It is defined in a frame for wireless power transfer network control and management with an actual sending message.

7.2. Frame Format

7.2.1 Frame Structure

The frame including the data for wireless power transfer control consists of the primitives shown in Table 1. MWPTS-C sends control commands to MWPTS-Ds through the frame with the structure in Table 1 and each MWPTS-D sends power transfer information to MWPTS-C.

Table 1-Frame Structure

Table 1

	Frame
Field Name	Start	MWPTS-D Number	Code	Control		Payload	CRC	End
				Serial No.	Payload Length
Size (Bits)	8	8	8	4	4	N(0-120)	8	8
	Frame Header					Frame Body

Frame Header: To exchange data between MWPTS-C and MWPTS-Ds, the control-related information is located including the MWPTS-D number, code, serial number, payload length, etc. Using the information located here, MWPTS-Ds are distinguished that exchange the frame type and frame itself.

Frame Body: It consists of the payload that has exchange data between MWPTS-C and MWPTS-Ds and the frame check sequence (FCS) to check the error within the payload.

7.2.2. Field Description

1 Byte of start field indicates the start of one frame and has the fixed value of 0x7E.

1 Byte of number field of MWPTS-D is used for MWPTS-C to distinguish the MWPTS-D from the application block. If the number of MWPTS-D is 0xFF, it indicates all MWPTS-Ds.

1 Byte of code field is used to distinguish the type of transmission frame because different codes are allocated for each frame. For more details, see 8.3 Frame Type

1 Byte of control field provides the frame serial number and payload length for each code. The serial numbers are allocated to each consecutive code frame to prevent frame loss during message transfer. The payload length indicates the length (Bytes) of the payload field next to the control field. The payload field has a variable length (0 to N Bytes) to contain actual sending data. For more details, see 8.4 Payload Format

The CRC field (1 Byte) is used to check whether the frame body has been received with no error. The standard generator polynomial creating the frame test sequence is as follows:

The end field (1 Byte) indicates the end of frame. Like the start field, it has the fixed value of 0x7F.

Table 2 Field Description

Table 2

Field	Size	Description
Start
	1 Byte	The start of a frame has the fixed value of 0x7F.
MWPTS-D Number	1 Byte	Number to distinguish the MWPTS-D from the application block
Code
	1 Byte	Code allocated to each message to distinguish frames(See 8.3 Frame Type )
Control	1 Byte	The frame number and payload length for each payload code are provided.
Payload	Variable(0-N Bytes)	Actual data(See 8.4 Payload Format )
CRC	1 Byte	8 bits of the frame test sequence is used to check whether the frame body has been received with no error. It is generated using the following 8^th standard generator polynomial.
End	1 Byte	It indicates the end of message and it has the fixed value of 0x7F.

7.3. Frame Type

7.3.1. General

The frame type is defined with four types of frames as in Table 3: request frame, response frame, data frame, and response notification frame. Payload structure for each frame type is different, and details of payload are introduced in 8.4.

Table 3 Frame Type Values

Table 3

Frame Type	Value	Content	Section
Request Frame	0x00	Request for MWPTS-C connection, separation, data response, etc.
Response Frame	0x01	Response to MWPTS-D connection, separation, data, etc.
Data Frame	0x02	Used when an MWPTS-D sends data without request.
Response Notification Frame	0x03	Only the data reception is notified.
TBD

7.3.2. Request Frame

The request frame is used when MWPTS-C sends the requested packet to a specific MWPTS-D in the requested section or broadcasts information to all receivers. When the number of MWPTS-D in the frame header is 0xFF, the request frame is broadcasted.

7.3.3. Response Frame

The response frame is used when sending the response packet of MWPTS-D against the MWPTS-C request. It is mainly used when replying with the charge information of MWPTS-D by the request of MWPTS-C.

7.3.4. Data Frame

The data frame is used when an MWPTS-D notifies MWPTS-C of full charge of MWPTS-D or discharge amount change even upon no request of MWPTS-C.

7.3.5. Response Notification Frame

The reception notification frame is used to check whether an MWPTS-D has received charge mode, time-division sequence, and end of charging and whether MWPTS-C has received the full charge event. The data reception check frame consists of only the frame header without frame body.

7.4. Payload Format

7.4.1. General

The payload format varies depending on the frame type (request frame, response frame, data frame, reception check frame).

7.4.2. Request Frame

7.4.2.1. General

The payload format of the request frame consists of the length, request code, and one or more request blocks as shown in Table 4. If the number of MWPTS-D in the frame header is 0xFF, it requests replies to all groups of MWPTS-Ds. Each block includes the request data information.

Table 4 Payload Format of Request Frame

Table 4

1	1	L₁	L₂	…..	L_n
Length (= L_n)	Request Code	Request Block-1	Request Block-2	….	Request Block-n

Unit: Byte

7.4.2.2. Length

The length field (1 Byte) indicates the sum of request block lengths and the field value varies depending on the request block length and the number of blocks.

7.4.2.3. Request Code and Request Data

The contents for the request code in the payload and request block of the corresponding request code are as follows:

Table 5 Request Codes and Data

Table 5

Request Code	Code Definition [Code Name]	Description	Data	Data Description
0x01	Req_Join	MWPTS-D connection request by MWPTS-C	[Req_Join]	Req_Join: connection request
0x02	Inf_Service	Notification of whether wireless power transfer of MWPTS-D is eligible or not	[Accept/Deny][Dev #]	Accept: eligibleDeny: ineligibleDev #: MWPTS-D number given by MWPTS-C
0x03	Req_Scan	Request for all MWPTS-D information	[Req_Scan]	Req_Scan: information request
0x04	Inf_Zone	MWPTS-D s zone (charging zone/communication zone) notification	[Charging/Comm]	Charging: charging zoneComm: communication zone
0x05	Inf_Mode	Charging mode notification	[Time/Simultaneous]	Time: time-division modeSimultaneous: simultaneous mode
0x06	Req_Time	Scheduling information notification	[Priority][Time Amount]	Priority: priorityTime Amount: amount of time
0x07	Req_Unexpt	Abnormal situation management command	[Dev #][Coil]	Dev #: MWPTS-D numberCoil: MWPTS-D coil On/Off
TBD

7.4.3. Response Frame

7.4.3.1. General

The payload of the response frame has the response data against the request. The payload of the response frame is shown in Figure 6. The first 1 Byte is the group address, the next 1 Byte is the response data length (L) and response code, and the next L Bytes includes the response data.

Table 6 Payload Format of Response Frame

Table 6

1	1	L
Length (=L)	Response Code	Response Data

Unit: Byte

7.4.3.2. Length

The length field (1 Byte) indicates the length of the replay data and it varies depending on the response data type.

7.4.3.3. Response Codes and Response Data

The contents for the response code in the payload and data of the corresponding response code are as follows:

Table 7 Response Codes and Data

Table 7

Request Code	Code Definition [Code Name]	Description	Data	Data Description
0x01	Rsp_Join	Response for the connection request of MWPTS-D	[Dev_ID]	Dev_ID: receiver ID
0x02	Rsp_Scan	Response for the device information request	[RSSI][Freq][BattRemain][BattDischarge][MaxPwr][Pwr][Type]	RSSI: reception signal strengthFreq: frequency for wireless power transferBattRemain: residual battery levelBattDischarge: battery discharge rateMaxPwr: maximum reception powerPwr: current reception powerType: MWPTS-D type
0x03	Ack_Mode	Response for the communication mode notification of the current device	[BattRemain][BattDischarge][Pwr]	BattRemain: residual battery levelBattDischarge: battery discharge ratePwr: current reception power
0x04	Rsp_Unexpt	Response for abnormal situation action request	[Dev #][Pwr]	Dev #: MWPTS-D numberPwr: current reception power
0x05	Rsp_Pwr	Response for reception strength request	[Pwr]	Pwr: current reception power
TBD

7.4.4. Data Frame

7.4.4.1. General

The payload of the data frame has the data to inform MWPTS-C of the recognized abnormal situation upon no request of MWPTS-D. The payload of the response frame is shown in Table 8. The first 1 Byte is the data code and the next L Bytes are the data.

Table 8 Data Frame

Table 8

1	L
Data Code	Data

7.4.4.2. Data Codes and Blocks

The contents for the data code in the payload and data of the corresponding data code are as follows:

Table 9 Data Codes and Blocks

Table 9

Data Code	Code Definition [Code Name]	Description	Data	Data Description
0x01	Req_Full	Notification of full charge of MWPTS-D
0x02	Ack_Batt	Notification of discharge rate of MWPTS-D battery	[BattDischarge]
TBD

7.4.5. Reception Notification Frame

The payload of the response reception check frame informs MWPTS-C of reception by sending only the header with no frame payload to notify reception for wireless power transfer mode of MWPTS-D, reception scheduling information, wireless power transfer termination notification, and full charge information of MWPTS-C. It can be used for more cases in the future.

Table 10 Reception Notification Frame

Table 10

Frame
Start	MWPTS-D Number	Code	Control
			Serial No.	Payload Length
8	8	8	4	4

Unit: Byte

8. Wireless Power Transfer Control Interface Procedure

8.1. General

To provide the wireless power transfer service to multiple MWPTS-Ds, procedures for authentication, power transfer, and termination exist. The procedures include the procedures to be performed in the charging zone and communication zone after MWPTS-D recognition and authentication, the procedures to be performed for wireless power transfer in the power transfer mode, and the procedure to be performed when abnormal situation happens.

8.2. MWPTS-D Recognition/Authentication and Charging Zone/Communication Zone

When MWPTS-C sends the communication signal (join request) for the connection request, the MWPTS-D that has received the signal, sends its own ID as a response. MWPTS-C checks the received MWPTS-D ID. If the ID is not the candidate for wireless power transfer, MWPTS-C informs the MWPTS-D of it. Otherwise, MWPTS-C requests for data. The MWPTS-D that has received the data request, sends the information of MWPTS-D (residual battery level, battery discharge rate, charging frequency, required reception power strength, etc.) to MWPTS-C as a data response. MWPTS-C that has received the MWPTS-D information, analyzes the received data and recognizes the zone of the corresponding MWPTS-D based on the reception strength information. When the MWPTS-D is within the communication zone, it is informed to the MWPTS-D, which also sends the information to the user. When the MWPTS-D is within the charging zone, it is informed to the MWPTS-D and MWPTS-C considers the MWPTS-D the candidate for wireless power transfer service.

8.3. Simultaneous Power Transfer

In the simultaneous power transfer mode, MWPTS-C performs impedance matching for the best wireless transfer efficiency before the service. It changes to the wireless power transfer frequency from the MWPTS-D information and sends the test power to calculate the impedance through the sensed current and voltage of MWPTS-C. Through this procedure, the first impedance matching is performed, test power is transferred, and the reception power level is received from the MWPTS-D. Then the secondary in-depth impedance matching is performed. When the optimal impedance matching is completed, the wireless power transfer service starts. The service continues until abnormal situation or wireless power transfer termination.

Figure 7 Simultaneous Power Transfer

8.4. Time-division Power Transfer

In the time-division power transfer mode, MWPTS-C performs the scheduling calculation based on the MWPTS-D information and informs all MWPTS-Ds of the sequences and times. Based on the calculated sequences and times, the impedance matching for the best wireless transfer efficiency is performed for each MWPTS-D before the service. It changes to the wireless power transfer frequency from the MWPTS-D information and sends the test power to calculate the impedance through the sensed current and voltage of MWPTS-C. Through this procedure, the first impedance matching is performed, test power is transferred, and the reception power level is received from the MWPTS-D. Then the secondary in-depth impedance matching is performed. When the optimal impedance match is completed, the wireless power transfer service starts. The service is provided for the allocated time to each MWPTS-D according to the scheduled sequence. When any abnormal situation or wireless power transfer termination happens during wireless power transfer, the current service is terminated.

Figure 8 Time-division Power Transfer

8.5. Abnormal Situation

8.5.1. General

The current and voltage values are measured to sense abnormal situations. When the variations of measured current/voltage and derived impedance are too large, an abnormal situation is detected. Then MWPTS-C determines the case among foreign material, MWPTS-D appearance or disappearance, and full charge of MWPTS-D and it takes eligible actions according to the remaining procedures.

8.5.2. Removing Foreign Material

When the variations of the measured current/voltage and derived impedance are too large, an abnormal situation is detected. Then MWPTS-C stops wireless power transfer and requests charging information to all MWPTS-Ds. When all MWPTS-Ds exist currently, it is considered the foreign material case. To determine whether the interference for wireless power transfer is temporary or continuous, multiple current/voltage measurements are required through wireless power transfer. If the value persists, the foreign material is considered continuous and informs the user of it through the alarm function.

Figure 9 Foreign Material Removal

8.5.3. New MWPTS-D Appearance and Existing MWPTS-D Disappearance

When the variations of the measured current/voltage and derived impedance are too large, an abnormal situation is detected. Then MWPTS-C stops wireless power transfer and requests charging information to all MWPTS-Ds. When all MWPTS-Ds do not exist or additional MWPTS-D is detected, it is considered an impedance change by MWPTS-D appearance or disappearance. After checking the impedance change, the optimal matching is performed for wireless power transfer.

Figure 10 New MWPTS-D Appearance and Existing MWPTS-D Disappearance

8.5.4. Full Charge of Existing MWPTS-D

When a battery full charge is detected during wireless power transfer, the MWPTS-D informs MWPTS-C of its full charge and blocks the power antenna operation. When the full charge event is received, MWPTS-C excludes the MWPTS-D that has sent the event from the wireless power transfer candidates and starts the service for other MWPTS-Ds.

Figure 11 Full Charge of Existing MWPTS-D

8.6. Power Transfer Termination

When the user requests the wireless power transfer termination to MWPTS-C, MWPTS-C stops wireless power transfer and waits for the next request in the standby mode.

Figure 12 Power Transfer Termination

8.7. Power Transfer between Devices

When an MWPTS-D does not find MWPTS-C in the vicinity, it can request wireless power transfer to a near MWPTS-D. At this time, the MWPTS-D received the request provides its basic MWPTS-D information to determine whether power transfer is possible or not and it informs the user of it. When the user approves it, the response for the wireless power request is sent and both MWPTS-Ds inform the users of the required items and method for charge during the power reception period. When the condition is met according to the method, the wireless power transfer service is provided to the requester.

Figure 13 Power Transfer between Devices

8.8. Battery Discharge Rate Change Notification

When an MWPTS-D detects the change of battery discharge rate, it is considered existence of any person near the MWPTS-D and the judgment is informed to MWPTS-C to change the output power not to violate the human body hurtfulness standard. It stops the wireless power transfer service for a moment, changes the output power, and restarts the service.

Figure 14 Battery Discharge Rate Change Notification

This item supports wireless power transfer and several kbps data transmission in one frequency band based on a formed network within a distance of several meters. And it can be applied to various services and industries such as the following areas of application:

* Mobile phones: provide ubiquitous charging environments for portable devices

* Home appliances: allow desirable decoration and placement of appliances by elimination of wire cables and plugs

Claims

A multi-node wireless charging method using magnetic field communication for enabling a wireless power transmission apparatus to charge wireless charging devices using magnetic field communication in a multi-node wireless power transmission system including the wireless power transmission apparatus and the plurality of wireless charging devices spaced apart from the wireless power transmission apparatus, the method comprising:

transmitting an association request frame;

receiving an association response frame from the wireless charging devices;

transmitting a charging requirement request frame;

receiving a charging requirement response frame from the wireless charging devices;

transmitting a charging preparation request frame; and

transmitting power during a receiving period of the charging preparation response frame for the charging preparation request frame.