WO2024075967A1 - Method and device for performing wireless recharging in high power mode with fast authentication in wireless power transmission system - Google Patents

Abstract

The present disclosure relates to a method for performing wireless recharging in a high power mode with fast authentication in a wireless power transmission system, wherein when wireless charging is interrupted in the high power mode, a wireless power transmitter reenters a configuration phase, a negotiation phase, and a power transfer phase. In the reentered negotiation phase, the wireless power transmitter receives a general request (GRQ) packet from a wireless power receiver. In the reentered negotiation phase, the wireless power transmitter transmits an Auth packet to the wireless power receiver in response to the GRQ packet.

Description

Method and device for performing wireless recharging in high power mode with fast authentication in wireless power transfer system

This specification relates to wireless power transfer.

Wireless power transmission technology is a technology that transmits power wirelessly between a power source and electronic devices. For example, wireless power transmission technology allows charging the battery of a wireless terminal such as a smartphone or tablet simply by placing it on a wireless charging pad, making it more efficient than the wired charging environment using an existing wired charging connector. It can provide excellent mobility, convenience, and safety. In addition to wireless charging of wireless terminals, wireless power transmission technology is used in various fields such as electric vehicles, various wearable devices such as Bluetooth earphones and 3D glasses, home appliances, furniture, underground facilities, buildings, medical devices, robots, and leisure. It is attracting attention as a replacement for the existing wired power transmission environment.

The wireless power transmission method is also called a contactless power transmission method, a no point of contact power transmission method, or a wireless charging method. The wireless power transmission system includes a wireless power transmission device that supplies electrical energy through a wireless power transmission method, and a wireless power reception device that receives electrical energy supplied wirelessly from the wireless power transmission device and supplies power to power receiving devices such as battery cells. It can be configured as a device.

Wireless power transmission technology includes a method of transmitting power through magnetic coupling, a method of transmitting power through radio frequency (RF), a method of transmitting power through microwaves, and ultrasonic waves. There are various ways to transmit power through. Methods based on magnetic coupling are further classified into magnetic induction and magnetic resonance methods. The magnetic induction method is a method of transmitting energy using the current induced in the receiving coil due to the magnetic field generated by the transmitting coil battery cell according to electromagnetic coupling between the coil on the transmitting side and the coil on the receiving side. The magnetic resonance method is similar to the magnetic induction method in that it uses a magnetic field. However, in the magnetic resonance method, resonance occurs when a specific resonance frequency is applied to the coil on the transmitting side and the coil on the receiving side, which causes energy to be transferred by the phenomenon of concentrated magnetic fields on both the transmitting and receiving sides. It is different from self-induction.

According to an embodiment of the present specification, the wireless power receiver transmits a CFG (Configuration) packet to the wireless power transmitter in the configuration phase.

The wireless power receiver enters a negotiation phase with the wireless power transmitter based on the CFG packet.

The wireless power receiver enters the high power mode by performing authentication in the power transfer phase after the negotiation phase.

When wireless charging is interrupted in the high power mode, the wireless power receiver may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entered negotiation phase, the wireless power receiver may transmit a General Request (GRQ) packet to the wireless power transmitter. In the re-entered negotiation phase, the wireless power receiver may receive an Auth packet in response to the GRQ packet from the wireless power transmitter.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power receiver may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

In other words, this embodiment provides a method of performing quick authentication through confirmation of previously authenticated information by exchanging simple information in the negotiation phase (or power transfer phase) when the authenticated wireless device enters recharging. suggest. As a result, it is possible to quickly authenticate the product and enter high-speed charging, and it is possible to authenticate the wireless device before entering the power transfer phase of wireless charging, which has the effect of enabling rapid entry into high-speed charging.

The effects that can be achieved through specific examples of the present specification are not limited to the effects listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of the present specification are not limited to those explicitly described in the present specification, and may include various effects that can be understood or derived from the technical features of the present specification.

1 is a block diagram of a wireless power system 10 according to one embodiment.

Figure 2 is a block diagram of a wireless power system 10 according to another embodiment.

Figure 3 shows examples of various electronic devices in which a wireless power transmission system is introduced.

Figure 4 is a block diagram of a wireless power transmission system according to one embodiment.

Figure 5 is a diagram showing an example of a Bluetooth communication architecture to which an embodiment according to the present specification can be applied.

Figure 6 is a block diagram showing a wireless power transmission system using BLE communication according to an example.

Figure 7 is a block diagram showing a wireless power transmission system using BLE communication according to another example.

Figure 8 is a state transition diagram for explaining the wireless power transfer procedure.

Figure 9 schematically shows an example of the protocol of the ping phase 810.

Figure 10 schematically shows an example of the protocol of the configuration phase 820.

FIG. 11 is a diagram illustrating a message field of a configuration packet (CFG) of a wireless power reception device according to an embodiment.

Figure 12 is a flowchart schematically illustrating a protocol of a negotiation stage or a renegotiation stage according to an embodiment.

FIG. 13 is a diagram illustrating a message field of a capability packet (CAP) of a wireless power transmission device according to an embodiment.

Figure 14 schematically shows a flowchart of the data flow for the power transfer phase 840 in the baseline protocol.

Figure 15 schematically shows a flowchart of the data flow for the power transfer phase 840 in the extended protocol.

FIG. 16 illustrates an application-level data stream between the wireless power transmitter 100 and the wireless power receiver 200 according to an example.

Figure 17 shows a power control control method according to one embodiment.

Figure 18 schematically shows the structure of an MPP ID packet.

Figure 19 schematically shows an example of an XID packet in MPP.

Figure 20 schematically shows the protocol in MPP restricted mode.

Figures 21 and 22 schematically show the protocol in MPP full mode.

Figure 23 shows an example of an authentication message header.

Figure 24 shows an example of the authentication protocol version field.

Figure 25 shows an example of the message type field for an authentication request.

Figure 26 shows an example of the message type field for an authentication response.

Figure 27 shows an example of GET_DIGESTS.

Figure 28 shows an example of GET_CERTIFICATE.

Figure 29 shows an example of CHALLENGE.

Figure 30 shows an example of DIGESTS.

Figure 31 shows an example of CERTIFICATE.

Figure 32 shows an example of CHALLENGE_AUTH.

Figure 33 shows an example of ERROR.

Figure 34 is a flowchart of a method for transmitting wireless power, according to an embodiment of the present specification.

Figure 35 shows problems that may occur in existing technology when charging is stopped due to detection of foreign substances, etc.

Figure 36 shows an example of performing Fast Authentication through SRQ/auth of PRx.

Figure 37 shows an example of re-entry into High power mode through Fast Authentication in Negotiation.

Figure 38 shows an example of performing Fast Authentication through GRQ/Auth packet.

Figure 39 shows another example of re-entry into high power mode through fast authentication in negotiation.

Figure 40 shows an example of performing Fast Authentication through GRQ/Auth packet.

Figure 41 shows an example of re-entering high power mode through Fast Authentication in the power transfer phase.

Figure 42 is a flowchart of a method of re-entering the fast power mode through fast authentication from the perspective of a wireless power transmitter, according to an embodiment of the present specification.

Figure 43 is a flowchart of a method of re-entering the fast power mode through fast authentication from the perspective of a wireless power receiver, according to an embodiment of the present specification.

As used herein, “A or B” may mean “only A,” “only B,” or “both A and B.” In other words, in this specification, “A or B” may be interpreted as “A and/or B.” For example, as used herein, “A, B or C” means “only A,” “only B,” “only C,” or “any and all combinations of A, B, and C ( It can mean “any combination of A, B and C)”.

The slash (/) or comma used in this specification may mean “and/or.” For example, “A/B” can mean “A and/or B.” Accordingly, “A/B” can mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” can mean “A, B, or C.”

As used herein, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” In addition, in this specification, the expression “at least one of A or B” or “at least one of A and/or B” means “at least one It can be interpreted the same as “at least one of A and B.”

In addition, as used herein, “at least one of A, B and C” means “only A”, “only B”, “only C”, or “A, B and C”. It can mean “any combination of A, B and C.” In addition, “at least one of A, B or C” or “at least one of A, B and/or C” means It may mean “at least one of A, B and C.”

Additionally, parentheses used in this specification may mean “for example.” Specifically, when “control information (PDCCH)” is indicated, “PDCCH” may be proposed as an example of “control information.” In other words, “control information” in this specification is not limited to “PDCCH,” and “PDCCH” may be proposed as an example of “control information.” Additionally, even when “control information (i.e., PDCCH)” is indicated, “PDCCH” may be proposed as an example of “control information.”

Technical features described individually in one drawing in this specification may be implemented individually or simultaneously. The term "wireless power" used hereinafter refers to any form of electric field, magnetic field, electromagnetic field, etc. transmitted from a wireless power transmitter to a wireless power receiver without the use of physical electromagnetic conductors. It is used to mean the energy of. Wireless power may also be called a wireless power signal, and may refer to an oscillating magnetic flux enclosed by a primary coil and a secondary coil. Described herein is power conversion in a system for wirelessly charging devices including, for example, mobile phones, cordless phones, iPods, MP3 players, headsets, etc. In general, the basic principles of wireless power transmission include, for example, a method of transmitting power through magnetic coupling, a method of transmitting power through radio frequency (RF), and a method of transmitting power through microwaves. ) and methods of transmitting power through ultrasonic waves.

1 is a block diagram of a wireless power system 10 according to one embodiment.

Referring to FIG. 1, the wireless power system 10 includes a wireless power transmission device 100 and a wireless power reception device 200.

The wireless power transmission device 100 receives power from an external power source (S) and generates a magnetic field. The wireless power receiving device 200 receives power wirelessly by generating current using the generated magnetic field.

Additionally, in the wireless power system 10, the wireless power transmission device 100 and the wireless power reception device 200 can transmit and receive various information necessary for wireless power transmission. Here, communication between the wireless power transmission device 100 and the wireless power reception device 200 is in-band communication using the magnetic field used for wireless power transmission or out-band communication using a separate communication carrier. It can be performed according to any one of (out-band communication) methods. Out-of-band communication may also be called out-of-band communication. Below, the terms are unified and described as out-band communication. Examples of out-band communication may include NFC, Bluetooth, BLE (bluetooth low energy), etc.

Here, the wireless power transmission device 100 may be provided as a fixed or mobile type. Examples of fixed types include those embedded in indoor ceilings, walls, or furniture such as tables, those installed as implants in outdoor parking lots, bus stops, or subway stations, or those installed in transportation vehicles such as cars or trains. There is. The mobile wireless power transmission device 100 may be implemented as part of another device, such as a mobile device of movable weight or size or the cover of a laptop computer.

In addition, the wireless power receiving device 200 should be interpreted as a comprehensive concept that includes various electronic devices equipped with batteries and various home appliances that are driven by receiving power wirelessly instead of a power cable. Representative examples of the wireless power receiving device 200 include portable terminals, cellular phones, smart phones, personal digital assistants (PDAs), and portable media players (PMPs). Portable Media Player, Wibro terminal, tablet, phablet, laptop, digital camera, navigation terminal, television, electric vehicle (EV), etc.

Figure 2 is a block diagram of a wireless power system 10 according to another embodiment.

Referring to FIG. 2, in the wireless power system 10, there may be one or more wireless power receiving devices 200. In FIG. 1, the wireless power transmission device 100 and the wireless power reception device 200 are expressed as exchanging power on a one-to-one basis. However, as shown in FIG. 2, one wireless power transmission device 100 can be connected to a plurality of wireless power reception devices. It is also possible to transmit power in (200-1, 200-2,..., 200-M). In particular, when wireless power transmission is performed using a self-resonance method, one wireless power transmission device 100 uses a simultaneous transmission method or a time-division transmission method to simultaneously transmit multiple wireless power reception devices 200-1, 200-2, ...,200-M) can transmit power.

In addition, Figure 1 shows the wireless power transmission device 100 directly transmitting power to the wireless power reception device 200, but there is a wireless power transmission between the wireless power transmission device 100 and the wireless power reception device 200. A separate wireless power transmission and reception device, such as a relay or repeater, may be provided to increase the power transmission distance. In this case, power is transferred from the wireless power transmission device 100 to the wireless power transmission and reception device, and the wireless power transmission and reception device may then transfer power back to the wireless power reception device 200.

Hereinafter, the wireless power receiver, power receiver, and receiver mentioned in this specification refer to the wireless power reception device 200. Additionally, the wireless power transmitter, power transmitter, and transmitter mentioned in this specification refer to the wireless power reception and transmission device 100.

Figure 3 shows examples of various electronic devices in which a wireless power transmission system is introduced.

FIG. 3 shows electronic devices classified according to the amount of power transmitted and received in the wireless power transmission system. Referring to Figure 3a, wearable devices such as smart watch, smart glass, HMD (Head Mounted Display), and smart ring, as well as earphones, remote controls, smartphones, PDAs, and tablets. A low-power (about 5W or less or about 20W or less) wireless charging method can be applied to mobile electronic devices (or portable electronic devices) such as PCs.

A medium-power (approximately 50W or less or approximately 200W or less) wireless charging method can be applied to small and medium-sized home appliances such as laptops, robot vacuum cleaners, TVs, audio devices, vacuum cleaners, and monitors. Kitchen appliances such as blenders, microwave ovens, and electric rice cookers, and personal mobility devices (or electronic devices/means of transportation) such as wheelchairs, electric kickboards, electric bicycles, and electric cars require high power (approximately 2 kW or less or 22 kW or less). A wireless charging method may be applied.

The electronic devices/mobile means described above (or shown in FIG. 1) may each include a wireless power receiver to be described later. Accordingly, the above-described electronic devices/means of transportation can be charged by wirelessly receiving power from a wireless power transmitter.

Hereinafter, the description will focus on mobile devices to which the wireless power charging method is applied, but this is only an example, and the wireless charging method according to the present specification can be applied to the various electronic devices described above.

Standards for wireless power transmission include wireless power consortium (WPC), air fuel alliance (AFA), and power matters alliance (PMA).

WPC consists of the Qi ecosystem targeting mobile and wearable devices and the HI ecosystem targeting kitchen appliances, robots, and LEV (light electric vehicles). A variety of wireless power transmitters and receivers using different power levels are covered by standards within each ecosystem and can be classified into different power classes or categories.

The Qi standard (belong to the Qi ecosystem) defines the baseline power profile (BPP), extended power profile (EPP), and magnetic power profile. BPP relates to wireless power transmitting and receiving devices that support power transmission of 5W, and EPP and MPP relate to wireless power transmitting and receiving devices that support power transmission in a range greater than 5W and less than 15W. In-band (IB) communication is a mandatory communication protocol of the Qi spec, but out-band (OB) communication, which is used as an optional backup channel, can also be used. The wireless power receiving device can identify whether OB is supported by setting the OB flag in the configuration packet. The wireless power transmitter supporting OB can enter the OB handover phase by transmitting a bit-pattern for OB handover in response to the configuration packet. The response to the configuration packet may be NAK, ND, or a newly defined 8-bit pattern. Applications of Qi spec include smartphones.

The IND standard (belong to HI ecosystem) relates to wireless power transmission and reception devices that provide guaranteed power of 30W to 150W. IB and OB communication channels can be used for mutual information exchange and power control. Applications to the IND spec include robots and power tools.

The LEV standard (belong to HI ecosystem) relates to wireless power transmission and reception devices that provide guaranteed power of 100W to 500W. IB is an essential communication channel for LEV spec, and OB communication can also be used. IB can be used as initialization and link establishment to OB. In response to the configuration packet, the wireless power transmitter can enter the OB handover phase using a bit pattern for OB handover.

The Ki standard (belong to HI ecosystem) is about wireless power transmitting and receiving devices that provide guaranteed power of 200W to 2kW, and essentially uses OB communication channels such as NFC or BLE. The applications include kitchen appliances.

Wireless power transmission and reception devices can provide a very convenient user experience and interface (UX/UI). In other words, a smart wireless charging service can be provided. The smart wireless charging service can be implemented based on the UX/UI of a smartphone including a wireless power transmission device. For these applications, the interface between the smartphone's processor and the wireless charging receiver allows for "drop and play" two-way communication between the wireless power transmitter and receiver.

As an example, a user can experience a smart wireless charging service in a hotel. When a user enters a hotel room and places the smartphone on the wireless charger in the room, the wireless charger transmits wireless power to the smartphone, and the smartphone receives wireless power. In this process, the wireless charger transmits information about the smart wireless charging service to the smartphone. When the smartphone detects that it is placed on a wireless charger, detects reception of wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone asks the user to consent to additional features ( Enters the state of inquiring about opt-in. To this end, the smartphone can display a message on the screen with or without an alarm sound. An example of a message may include phrases such as "Welcome to ### hotel. Select "Yes" to activate smart charging functions: Yes | No Thanks." The smartphone receives the user's input of selecting Yes or No Thanks and performs the next procedure selected by the user. If Yes is selected, the smartphone transmits the information to the wireless charger. And the smartphone and wireless charger perform the smart charging function together.

Smart wireless charging service may also include receiving auto-filled WiFi credentials. For example, a wireless charger transmits WiFi credentials to a smartphone, and the smartphone runs the appropriate app and automatically enters the WiFi credentials received from the wireless charger.

Smart wireless charging service may also include running a hotel application that provides hotel promotions, remote check-in/check-out, and obtaining contact information.

As another example, users can experience smart wireless charging services within a vehicle. When the user gets into the vehicle and places the smartphone on the wireless charger, the wireless charger transmits wireless power to the smartphone, and the smartphone receives wireless power. In this process, the wireless charger transmits information about the smart wireless charging service to the smartphone. When the smartphone detects that it is placed on a wireless charger, detects receipt of wireless power, or receives information about the smart wireless charging service from the wireless charger, the smartphone verifies its identity with the user. Enter the inquiry state.

In this state, the smartphone automatically connects to the car via WiFi and/or Bluetooth. The smartphone can display the message on the screen with or without an alarm sound. An example of a message may include phrases such as "Welcome to your car. Select "Yes" to synch device with in-car controls: Yes | No Thanks." The smartphone receives the user's input of selecting Yes or No Thanks and performs the next procedure selected by the user. If Yes is selected, the smartphone transmits the information to the wireless charger. In addition, the smartphone and wireless charger can perform in-vehicle smart control functions together by running the in-vehicle application/display software. Users can enjoy the music they want and check regular map locations. In-vehicle application/display software may include the capability to provide synchronized access for pedestrians.

As another example, users can experience smart wireless charging at home. When a user enters a room and places the smartphone on the wireless charger in the room, the wireless charger transmits wireless power to the smartphone, and the smartphone receives wireless power. In this process, the wireless charger transmits information about the smart wireless charging service to the smartphone. When the smartphone detects that it is placed on a wireless charger, detects reception of wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone asks the user to consent to additional features ( Enters the state of inquiring about opt-in. To this end, the smartphone can display a message on the screen with or without an alarm sound. An example of a message may include phrases such as "Hi xxx, Would you like to activate night mode and secure the building?: Yes | No Thanks." The smartphone receives the user's input of selecting Yes or No Thanks and performs the next procedure selected by the user. If Yes is selected, the smartphone transmits the information to the wireless charger. Smartphones and wireless chargers can at least recognize user patterns and encourage users to lock doors and windows, turn off lights, or set alarms.

Hereinafter, 'profile' will be newly defined as an indicator/standard that represents/indicates compatibility. In other words, compatibility is maintained between wireless power transmission and reception devices with the same 'profile', enabling stable power transmission and reception, but it can be interpreted that power transmission and reception is not possible between wireless power transmission and reception devices with different 'profiles'. Profiles can be defined independently (or independently) of the ecosystem based on compatibility and/or application.

Profiles can be broadly divided into four categories: i) mobile, ii) robot, iii) kitchen, and iv) LEV.

For the 'mobile' profile, Qi spec, communication protocol/method can be defined as IB and OB, operating frequency can be defined as 87~205kHz, 300~400kHz, and examples of applications include smartphones, laptops, wearables, etc. It can exist.

In the case of the 'Robot' profile, IND spec, communication protocol/method may include IB and OB, and examples of applications may include robots and electric tools.

In the case of the 'kitchen' profile, Ki spec, communication protocol/method can be defined as NFC or BLE-based, operating frequency can be defined as less than 100kHz, and examples of applications can include kitchen/home appliances, etc.

In the case of the 'LEV' profile, LEV spec, communication protocol/method may include IB and OB, and examples of applications may include electric bicycles and electric kickboards.

NFC or BLE communication can be used as an OB communication channel between the wireless power transmitter and receiver of the above profile. When using NFC, the wireless power transmitter and receiver can mutually confirm that they are NFC devices by exchanging WPC NDEF (NFC Data Exchange Profile Format).

Figure 4 is a block diagram of a wireless power transmission system according to one embodiment.

Referring to FIG. 4, the wireless power transmission system 10 includes a mobile device 450 that wirelessly receives power and a base station 400 that transmits power wirelessly.

The base station 400 is a device that provides induced power or resonance power and may include at least one wireless power transmitter (100) and a system circuit 405. The wireless power transmitter 100 can transmit induced power or resonance power and control the transmission. The wireless power transmitter 100 includes a power conversion circuit 110 that converts electrical energy into a power signal by generating a magnetic field through a primary coil(s) and transmits power at an appropriate level. It may include a communication/control circuit (communications & control circuit, 120) that controls communication and power transfer with the wireless power receiver 200. The system circuit 405 may perform other operational controls of the base station 400, such as input power provisioning, control of a plurality of wireless power transmitters, and user interface control.

The primary coil can generate an electromagnetic field using alternating current power (or voltage or current). The primary coil may receive alternating current power (or voltage or current) of a specific frequency output from the power conversion circuit 110, and thereby generate a magnetic field of a specific frequency. The magnetic field may be generated in a non-radiative or radial form, and the wireless power receiving device 200 receives it and generates current. In other words, the primary coil transmits power wirelessly.

In a magnetic induction method, the primary and secondary coils may have any suitable shapes, for example copper wire wound around a high permeability formation such as ferrite or amorphous metal. The primary coil may also be called a transmitting coil, primary core, primary winding, primary loop antenna, etc. Meanwhile, the secondary coil may also be called a receiving coil, secondary core, secondary winding, secondary loop antenna, pickup antenna, etc. .

When using the self-resonance method, the primary coil and secondary coil may be provided in the form of a primary resonance antenna and a secondary resonance antenna, respectively. A resonant antenna may have a resonant structure including a coil and a capacitor. At this time, the resonant frequency of the resonant antenna is determined by the inductance of the coil and the capacitance of the capacitor. Here, the coil may be in the form of a loop. Additionally, a core may be placed inside the loop. The core may include a physical core such as a ferrite core or an air core.

Energy transfer between the primary resonant antenna and the secondary resonant antenna can be achieved through the resonance phenomenon of the magnetic field. The resonance phenomenon refers to a phenomenon in which when a near field corresponding to the resonance frequency is generated in one resonant antenna and another resonant antenna is located nearby, both resonant antennas are coupled to each other, resulting in highly efficient energy transfer between the resonant antennas. . When a magnetic field corresponding to the resonance frequency is generated between the primary resonance antenna and the secondary resonance antenna, a phenomenon occurs in which the primary resonance antenna and the secondary resonance antenna resonate with each other, and accordingly, in general, the magnetic field generated from the primary resonance antenna The magnetic field is focused toward the secondary resonant antenna with higher efficiency compared to the case where it is radiated into free space, and thus energy can be transferred from the primary resonant antenna to the secondary resonant antenna with high efficiency. The magnetic induction method can be implemented similarly to the magnetic resonance method, but in this case, the frequency of the magnetic field does not need to be the resonance frequency. Instead, the magnetic induction method requires matching between the loops that make up the primary and secondary coils, and the gap between the loops must be very close.

Although not shown in the drawing, the wireless power transmitter 100 may further include a communication antenna. A communication antenna can transmit and receive communication signals using a communication carrier other than magnetic field communication. For example, a communication antenna can transmit and receive communication signals such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

The communication/control circuit 120 can transmit and receive information with the wireless power reception device 200. The communication/control circuit 120 may include at least one of an IB communication module or an OB communication module.

The IB communication module can transmit and receive information using magnetic waves with a specific frequency as the center frequency. For example, the communication/control circuit 120 performs in-band communication by carrying communication information at the operating frequency of wireless power transmission and transmitting it through the primary coil, or by receiving the operating frequency containing the information through the primary coil. can do. At this time, modulation methods such as binary phase shift keying (BPSK), frequency shift keying (FSK), or amplitude shift keying (ASK) and Manchester coding or non-zero return level (NZR) are used. Using coding methods such as -L: non-return-to-zero level (L) coding, information can be stored in magnetic waves or magnetic waves containing information can be interpreted. Using this IB communication, the communication/control circuit 120 can transmit and receive information up to a distance of several meters at a data transmission rate of several kbps.

The OB communication module may perform out-band communication through a communication antenna. For example, the communication/control circuit 120 may be provided as a short-range communication module. Examples of short-range communication modules include communication modules such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

The communication/control circuit 120 may control the overall operation of the wireless power transmission device 100. The communication/control circuit 120 can perform computation and processing of various information and control each component of the wireless power transmission device 100.

The communication/control circuit 120 may be implemented in a computer or similar device using hardware, software, or a combination thereof. In hardware, the communication/control circuit 120 may be provided in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it may be provided in the form of a program that drives the hardware communication/control circuit 120. can be provided.

The communication/control circuit 120 can control transmission power by controlling the operating point. The operating point being controlled may correspond to a combination of frequency (or phase), duty cycle, duty ratio, and voltage amplitude. The communication/control circuit 120 may control transmission power by adjusting at least one of frequency (or phase), duty cycle, duty ratio, and voltage amplitude. Additionally, the wireless power transmitter 100 may supply constant power, and the wireless power receiver 200 may control received power by controlling the resonance frequency.

Meanwhile, in the WPC Qi system, the wireless power transmitter 100 can be classified, for example, in terms of the number of primary coils activated for power transmission. At this time, the wireless power transmitter 100 supporting a wireless power transmission amount of up to 5W (i.e., the wireless power transmitter 100 supporting the BPP protocol) is, for example, a type A wireless power transmitter 100 and a type A wireless power transmitter 100. It can be classified into B (type B) wireless power transmitters 100, and supports a wireless power transmission amount of 5W or more (i.e., a wireless power transmitter 100 that supports the MPP or EPP protocol). For example, it can be classified into a type MP-A (MP-A) wireless power transmitter 100 and a type MP-B (type MP-B) wireless power transmitter 100.

- Type A and Type MP A wireless power transmitters (100)

Type A and Type MP A wireless power transmitters 100 may have one or more primary coils. Type A and Type MP A wireless power transmitters 100 activate a single primary coil at a time, so a single primary cell matching the activated primary coil can be used.

- Type B and Type MP B wireless power transmitter (100)

Type B and Type MP B power transmitters may have a primary coil array. And Type B and Type MP B power transmitters can enable free positioning. To this end, Type B and Type MP B power transmitters can activate one or more primary coils in the array to realize primary cells at different locations on the interface surface.

Additionally, a wireless power transmitter that utilizes magnets and supports wireless power transmission of 5W or more (i.e., a wireless power transmitter that supports the MPP protocol) can be proposed, and the MPP protocol will be described later.

However, for high-power wireless power transmission for standards after Qi v2.0, BPP supports power of up to 5W, EPP supports power of more than 5W and less than 50W, and MPP supports power of more than 5W and less than 50W. You can. In other words, EPP or MPP can be considered to support power of 5~50W.

The mobile device 450 receives and stores the power received from the wireless power receiver 200 and a wireless power receiver 200 that receives wireless power through a secondary coil, and supplies it to the device. Includes load (455).

The wireless power receiver 200 may include a power pick-up circuit (210) and a communications/control circuit (220). The power pickup circuit 210 may receive wireless power through the secondary coil and convert it into electrical energy. The power pickup circuit 210 rectifies the alternating current signal obtained through the secondary coil and converts it into a direct current signal. The communication/control circuit 220 can control transmission and reception of wireless power (power transmission and reception).

The secondary coil may receive wireless power transmitted from the wireless power transmission device 100. The secondary coil can receive power using the magnetic field generated by the primary coil. Here, when a specific frequency is the resonance frequency, a self-resonance phenomenon occurs between the primary coil and the secondary coil, allowing power to be transmitted more efficiently.

Meanwhile, although not shown in FIG. 4, the communication/control circuit 220 may further include a communication antenna. A communication antenna can transmit and receive communication signals using a communication carrier other than magnetic field communication. For example, a communication antenna can transmit and receive communication signals such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

The communication/control circuit 220 can transmit and receive information with the wireless power transmission device 100. The communication/control circuit 220 may include at least one of an IB communication module or an OB communication module.

The IB communication module can transmit and receive information using magnetic waves with a specific frequency as the center frequency. For example, the communication/control circuit 220 can perform IB communication by carrying information in magnetic waves and transmitting it through a secondary coil, or by receiving magnetic waves containing information through a secondary coil. At this time, modulation methods such as binary phase shift keying (BPSK), frequency shift keying (FSK), or amplitude shift keying (ASK) and Manchester coding or non-zero return level (NZR) are used. Using coding methods such as -L: non-return-to-zero level (L) coding, information can be stored in magnetic waves or magnetic waves containing information can be interpreted. Using this IB communication, the communication/control circuit 220 can transmit and receive information up to a distance of several meters at a data transmission rate of several kbps.

The OB communication module may perform out-band communication through a communication antenna. For example, the communication/control circuit 220 may be provided as a short-range communication module.

Examples of short-range communication modules include communication modules such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

The communication/control circuit 220 may control the overall operation of the wireless power reception device 200. The communication/control circuit 220 can perform computation and processing of various information and control each component of the wireless power reception device 200.

The communication/control circuit 220 may be implemented in a computer or similar device using hardware, software, or a combination thereof. In hardware, the communication/control circuit 220 may be provided in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it may be provided in the form of a program that drives the hardware communication/control circuit 220. can be provided.

When the communication/control circuit 120 and the communication/control circuit 220 are an OB communication module or a short-range communication module that is Bluetooth or Bluetooth LE, the communication/control circuit 120 and the communication/control circuit 220 are shown in Figure 5, respectively. It can be implemented and operate with the same communication architecture.

Figure 5 is a diagram showing an example of a Bluetooth communication architecture to which an embodiment according to the present specification can be applied.

Referring to FIG. 5, (a) of FIG. 5 shows an example of a Bluetooth Basic Rate (BR)/Enhanced Data Rate (EDR) protocol stack supporting GATT, and (b) shows an example of a protocol stack of Bluetooth Low Energy (LE). Shows an example of a protocol stack.

Specifically, as shown in (a) of FIG. 5, the Bluetooth BR/EDR protocol stack consists of an upper controller stack (Controller stack) 460 and a lower one based on the Host Controller Interface (HCI) 18. May include a host stack (Host Stack, 470).

The host stack (or host module) 470 refers to a wireless transmitting and receiving module that receives a 2.4 GHz Bluetooth signal and hardware for transmitting or receiving Bluetooth packets, and the controller stack 460 is connected to the Bluetooth module and operates the Bluetooth module. Control and perform actions.

The host stack 470 may include a BR/EDR PHY layer 12, a BR/EDR Baseband layer 14, and a Link Manager layer (Link Manager) 16.

The BR/EDR PHY layer 12 is a layer that transmits and receives 2.4GHz wireless signals, and when using GFSK (Gaussian Frequency Shift Keying) modulation, data can be transmitted by hopping 79 RF channels.

The BR/EDR Baseband layer 14 is responsible for transmitting digital signals, selects a channel sequence that hops 1400 times per second, and transmits a time slot of 625us for each channel.

The link manager layer 16 uses the Link Manager Protocol (LMP) to control the overall operation (link setup, control, security) of the Bluetooth connection.

The link manager layer 16 can perform the following functions.

- ACL/SCO logical transport, logical link setup and control.

- Detach: Stops the connection and informs the other device of the reason for the stop.

- Power control and role switch.

- Performs security (authentication, pairing, encryption) functions.

The host controller interface layer 18 provides an interface between the host module and the controller module, allowing the host to provide commands and data to the controller, and allows the controller to provide events and data to the host.

The host stack (or host module, 20) includes Logical Link Control and Adaptation Protocol (L2CAP, 21), Attribute Protocol (Protocol, 22), Generic Attribute Profile (GATT, 23), and Generic Access Profile (Generic Access). Includes Profile, GAP, 24), and BR/EDR Profile (25).

The Logical Link Control and Adaptation Protocol (L2CAP, 21) can provide a bidirectional channel for transmitting data to a specific protocol or profile.

The L2CAP 21 is capable of multiplexing various protocols, profiles, etc. provided by Bluetooth.

L2CAP of Bluetooth BR/EDR uses dynamic channels, supports protocol service multiplexer, retransmission, and streaming mode, and provides segmentation and reassembly, per-channel flow control, and error control.

The general attribute profile (GATT, 23) may be operable as a protocol that describes how the attribute protocol 22 is used when configuring services. For example, the generic attribute profile 23 may be operable to specify how ATT attributes are grouped together into services and may be operable to describe characteristics associated with services.

Accordingly, the general attribute profile 23 and the attribute protocol ATT 22 may use features to describe the state and services of the device, how the features relate to each other and how they are used.

The attribute protocol 22 and the BR/EDR profile 25 define a service (profile) using Bluetooth BR/EDR and an application protocol for exchanging these data, and the general access profile (Generic Access Profile, GAP, 24) defines device discovery, connection, and security levels.

As shown in (b) of FIG. 5 , the Bluetooth LE protocol stack includes a controller stack (480) operable to process a timing-critical wireless device interface and a host stack operable to process high level data. Includes (Host stack, 490).

First, the controller stack 480 may be implemented using a communication module that may include a Bluetooth wireless device and a processor module that may include a processing device, such as a microprocessor.

Host stack 490 may be implemented as part of an OS running on a processor module, or as an instantiation of a package on an OS.

In some instances, the controller stack and host stack may operate or execute on the same processing device within a processor module.

The controller stack 480 includes a physical layer (PHY) 32, a link layer (Link Layer) 34, and a host controller interface (Host Controller Interface) 36.

The physical layer (PHY, wireless transmission/reception module, 32) is a layer that transmits and receives 2.4 GHz wireless signals and uses GFSK (Gaussian Frequency Shift Keying) modulation and a frequency hopping technique consisting of 40 RF channels.

The link layer 34, which plays a role in transmitting or receiving Bluetooth packets, performs advertising and scanning functions using three advertising channels, then creates a connection between devices and transmits data packets of up to 257 bytes through 37 data channels. Provides the function of sending and receiving.

The host stack includes GAP (Generic Access Profile, 40), Logical Link Control and Adaptation Protocol (L2CAP, 41), Security Manager (SM, 42), Attribute Protocol (ATT, 440), and General Attribute Profile. (Generic Attribute Profile, GATT, 44), Generic Access Profile (25), and LT Profile (46). However, the host stack 490 is not limited to this and may include various protocols and profiles.

The host stack uses L2CAP to multiplex various protocols and profiles provided by Bluetooth.

First, L2CAP (Logical Link Control and Adaptation Protocol, 41) can provide one bidirectional channel for transmitting data to a specific protocol or profile.

The L2CAP 41 may be operable to multiplex data between upper layer protocols, segment and reassemble packages, and manage multicast data transmission.

Bluetooth LE basically uses three fixed channels (1 for signaling CH, 1 for Security Manager, and 1 for Attribute protocol). Additionally, dynamic channels can be used as needed.

On the other hand, BR/EDR (Basic Rate/Enhanced Data Rate) basically uses dynamic channels and supports protocol service multiplexer, retransmission, streaming mode, etc.

SM (Security Manager, 42) is a protocol for authenticating devices and providing key distribution.

ATT (Attribute Protocol, 43) defines rules for accessing data of the other device in a server-client structure. ATT has the following six message types (Request, Response, Command, Notification, Indication, Confirmation).

① Request and Response messages: The Request message is a message to request and deliver specific information from a client device to a server device, and the Response message is a response message to the Request message and can be used to transmit from the server device to the client device. says

② Command message: A message sent from a client device to a server device mainly to instruct a command for a specific operation. The server device does not transmit a response to the command message to the client device.

③ Notification message: A message sent from the server device to the client device for notification of events, etc., and the client device does not send a confirmation message for the Notification message to the server device.

④ Indication and Confirm message: A message sent from the server device to the client device for notification of events, etc.. Unlike the Notification message, the client device transmits a confirmation message for the Indication message to the server device.

This specification transmits a value for the data length when requesting long data in the GATT profile using the attribute protocol (ATT, 43) so that the client can clearly know the data length, and uses UUID to obtain characteristic information from the server. Values can be transmitted.

The general access profile (GAP, 45) is a newly implemented layer for Bluetooth LE technology and is used to control role selection for communication between Bluetooth LE devices and how multi-profile operation occurs.

In addition, the general access profile 45 is mainly used in device discovery, connection creation, and security procedures, defines a method of providing information to the user, and defines the types of attributes as follows.

① Service: Defines the basic operation of the device as a combination of data-related behavior

② Include: Defines the relationship between services

③ Characteristics: Data values used in the service

④ Behavior: Computer-readable format defined as UUID (Universal Unique Identifier, value type)

The LE profile 46 is a profile dependent on GATT and is mainly applied to Bluetooth LE devices. The LE profile 46 may include, for example, Battery, Time, FindMe, Proximity, Time, etc., and the specific details of GATT-based Profiles are as follows.

① Battery: How to exchange battery information

② Time: How to exchange time information

③ FindMe: Provides alarm service based on distance

④ Proximity: How to exchange battery information

⑤ Time: How to exchange time information

The general attribute profile (GATT, 44) may be operable as a protocol that describes how the attribute protocol (43) is used when configuring services. For example, the generic attribute profile 44 may be operable to specify how ATT attributes are grouped together into services and may be operable to describe characteristics associated with services.

Accordingly, the general attribute profile 44 and the attribute protocol ATT 43 may use features to describe the state and services of the device, how the features relate to each other and how they are used.

Below, we will briefly look at the procedures of Bluetooth Low Energy (BLE) technology.

BLE procedures can be divided into Device Filtering Procedure, Advertising Procedure, Scanning Procedure, Discovering Procedure, and Connecting Procedure.

Device Filtering Procedure

The device filtering procedure is a method to reduce the number of devices that respond to requests, instructions, notifications, etc. in the controller stack.

Since it is unnecessary to respond when a request is received from all devices, the controller stack can control the power consumption in the BLE controller stack by reducing the number of requests sent.

An advertising device or scanning device may perform the device filtering procedure to limit devices that receive advertising packets, scan requests, or connection requests.

Here, an advertising device refers to a device that transmits advertising events, that is, performs advertising, and is also expressed as an advertiser.

A scanning device refers to a device that performs scanning or a device that transmits a scan request.

In BLE, when a scanning device receives some advertising packets from an advertising device, the scanning device must send a scan request to the advertising device.

However, if a device filtering procedure is used and scan request transmission is unnecessary, the scanning device may ignore advertising packets transmitted from an advertising device.

Device filtering procedures can also be used during the connection request process. If device filtering is used in the connection request process, there is no need to transmit a response to the connection request by ignoring the connection request.

Advertising Procedure

The advertising device performs an advertising procedure to perform a non-directional broadcast to devices within the area.

Here, undirected advertising is advertising aimed at all devices rather than broadcasting towards a specific device, and all devices scan the advertising to request additional information or You can make a connection request.

In contrast, directed advertising allows only devices designated as receiving devices to scan advertising and request additional information or connection.

The advertising procedure is used to establish a Bluetooth connection with a nearby initiating device.

Alternatively, the advertising procedure may be used to provide periodic broadcasts of user data to scanning devices that are listening on the advertising channel.

In the advertising process, all advertisements (or advertising events) are broadcast through advertising physical channels.

Advertising devices may receive scan requests from listening devices that are listening to obtain additional user data from the advertising device. The advertising device transmits a response to the scan request to the device that transmitted the scan request through the same advertising physical channel as the advertising physical channel that received the scan request.

Broadcast user data sent as part of advertisement packets is dynamic data, whereas scan response data is generally static data.

An advertising device may receive a connection request from an initiating device on an advertising (broadcast) physical channel. If the advertising device used a connectable advertising event and the initiating device was not filtered by the device filtering procedure, the advertising device stops advertising and enters connected mode. The advertising device may start advertising again after being in connected mode.

Scanning Procedure

The device that performs scanning, that is, the scanning device, performs a scanning procedure to listen to the non-directional broadcast of user data from advertising devices using an advertising physical channel.

The scanning device transmits a scan request to the advertising device through the advertising physical channel to request additional data from the advertising device. The advertising device transmits a scan response, which is a response to the scan request, including additional data requested by the scanning device through the advertising physical channel.

The scanning procedure can be used while connecting to another BLE device in a BLE piconet.

If the scanning device receives a broadcasted advertising event and is in an initiator mode that can initiate a connection request, the scanning device transmits a connection request to the advertising device through the advertising physical channel, thereby You can start a Bluetooth connection with .

When the scanning device transmits a connection request to the advertising device, the scanning device stops scanning initiator mode for additional broadcasts and enters connection mode.

Discovering Procedure

Devices capable of Bluetooth communication (hereinafter referred to as 'Bluetooth devices') perform advertising and scanning procedures to discover devices existing nearby or to be discovered by other devices within a given area.

The discovery procedure is performed asymmetrically. A Bluetooth device that tries to find other nearby devices is called a discovering device, and it listens to find devices that advertise scannable advertising events. A Bluetooth device that can be discovered and used by other devices is called a discoverable device, and actively broadcasts advertising events so that other devices can scan through an advertising (broadcast) physical channel.

Both the discovering device and the discoverable device may already be connected to other Bluetooth devices in the piconet.

Connecting Procedure

The connection procedure is asymmetric, requiring one Bluetooth device to perform an advertising procedure while another Bluetooth device performs a scanning procedure.

That is, the advertising process can be targeted, with the result that only one device will respond to the advertisement. After receiving a connectable advertising event from an advertising device, a connection may be initiated by transmitting a connection request to the advertising device through an advertising (broadcast) physical channel.

Next, we will briefly look at the operating states in BLE technology, namely Advertising State, Scanning State, Initiating State, and Connection State.

Advertising State

The link layer (LL) enters the advertisement state according to instructions from the host (stack). When the link layer is in an advertising state, the link layer transmits advertising PDUs (Packet Data Circuits) in advertising events.

Each advertising event consists of at least one advertising PDU, and the advertising PDUs are transmitted through the advertising channel indices used. The advertising event may be terminated when each advertising PDU is transmitted through the advertising channel indexes used, or the advertising event may be terminated earlier if the advertising device needs to secure space to perform other functions.

Scanning State

The link layer enters the scanning state under the direction of the host (stack). In the scanning state, the link layer listens for advertising channel indices.

There are two types of scanning states: passive scanning and active scanning, and each scanning type is determined by the host.

No separate time or advertising channel index is defined for performing scanning.

During the scanning state, the link layer listens for the advertising channel index during the scanWindow duration. ScanInterval is defined as the interval between the starting points of two consecutive scan windows.

The link layer must listen for completion of all scan intervals of the scan window as directed by the host, provided there are no scheduling conflicts. In each scan window, the link layer must scan a different advertising channel index. The link layer uses all available advertising channel indices.

When passive scanning, the link layer only receives packets and does not transmit any packets.

When actively scanning, the link layer performs listening to the advertising device to rely on the advertising PDU type and can request additional information about the advertising device.

Initiating State

The link layer enters the initiation state under the direction of the host (stack).

When the link layer is in the startup state, the link layer performs listening for advertising channel indices.

During the launch state, the link layer listens for the advertising channel index during the scan window interval.

connection state

The link layer enters the connected state when the device performing the connection request, that is, the initiating device, transmits a CONNECT_REQ PDU to the advertising device, or when the advertising device receives the CONNECT_REQ PDU from the initiating device.

After entering the connected state, a connection is considered created. However, the connection need not be considered established at the time it enters the connected state. The only difference between a newly created connection and an established connection is the link layer connection supervision timeout value.

When two devices are connected, they act in different roles.

The link layer performing the master role is called the master, and the link layer performing the slave role is called the slave. The master controls the timing of the connection event, and the connection event refers to the point in time when the master and slave are synchronized.

Below, we will briefly look at packets defined in the Bluetooth interface. BLE devices use packets defined below.

Packet Format

The Link Layer has only one packet format used for both advertising channel packets and data channel packets.

Each packet consists of four fields: Preamble, Access Address, PDU, and CRC.

When a packet is transmitted in an advertising channel, the PDU will be an advertising channel PDU, and when a packet is transmitted in a data channel, the PDU will be a data channel PDU.

Advertising Channel PDU

The advertising channel PDU (Packet Data Circuit) has a 16-bit header and payloads of various sizes.

The PDU type field of the advertising channel PDU included in the header indicates the PDU type as defined in Table 1 below.

PDU Type	Packet Name
0000	ADV_IND
0001	ADV_DIRECT_IND
0010	ADV_NONCONN_IND
0011	SCAN_REQ
0100	SCAN_RSP
0101	CONNECT_REQ
0110	ADV_SCAN_IND
0111-1111	Reserved

Advertising PDU

The advertising channel PDU types below are called advertising PDUs and are used in specific events.

ADV_IND: Linkable non-directional advertising event

ADV_DIRECT_IND: Connectable directional advertising event

ADV_NONCONN_IND: Non-directional advertising event not reachable.

ADV_SCAN_IND: Scannable non-directional advertising events

The PDUs are transmitted at the link layer in the advertising state and received by the link layer in the scanning state or initiating state.

Scanning PDU

The advertising channel PDU type below is called a scanning PDU and is used in the conditions described below.

SCAN_REQ: Transmitted by the link layer in the scanning state, and received by the link layer in the advertising state.

SCAN_RSP: Transmitted by the link layer in the advertising state and received by the link layer in the scanning state.

Initiating PDU

The advertising channel PDU type below is called an initiating PDU.

CONNECT_REQ: Sent by the link layer in the initiation state and received by the link layer in the advertisement state.

Data Channel PDU

The data channel PDU has a 16-bit header, a payload of various sizes, and may include a Message Integrity Check (MIC) field.

The procedures, states, packet formats, etc. in BLE technology discussed above can be applied to perform the methods proposed in this specification.

Referring again to FIG. 4, load 455 may be a battery. The battery can store energy using the power output from the power pickup circuit 210. Meanwhile, the mobile device 450 does not necessarily include a battery. For example, the battery may be provided in a detachable external configuration. For another example, the wireless power receiving device 200 may include a driving means that drives various operations of the electronic device instead of a battery.

The mobile device 450 is shown as including a wireless power receiving device 200, and the base station 400 is shown as including a wireless power transmitting device 100, but in a broad sense, the wireless power receiving device ( 200) may be identified with the mobile device 450 and the wireless power transmission device 100 may be identified with the base station 400.

When the communication/control circuit 120 and the communication/control circuit 220 include Bluetooth or Bluetooth LE as an OB communication module or short-range communication module in addition to the IB communication module, wireless power transmission including the communication/control circuit 120 The wireless power receiving device 200 including the device 100 and the communication/control circuit 220 may be represented as a simplified block diagram as shown in FIG. 6.

Figure 6 is a block diagram showing a wireless power transmission system using BLE communication according to an example.

Referring to FIG. 6, the wireless power transmission device 100 includes a power conversion circuit 110 and a communication/control circuit 120. The communication/control circuit 120 includes an in-band communication module 121 and a BLE communication module 122.

Meanwhile, the wireless power receiving device 200 includes a power pickup circuit 210 and a communication/control circuit 220. The communication/control circuit 220 includes an in-band communication module 221 and a BLE communication module 222.

In one aspect, the BLE communication modules 122 and 222 perform the architecture and operation according to FIG. 5 . For example, the BLE communication modules 122 and 222 may be used to establish a connection between the wireless power transmitter 100 and the wireless power receiver 200 and exchange control information and packets necessary for wireless power transmission. there is.

In another aspect, the communication/control circuit 120 may be configured to operate a profile for wireless charging. Here, the profile for wireless charging may be GATT using BLE transmission.

Figure 7 is a block diagram showing a wireless power transmission system using BLE communication according to another example.

Referring to FIG. 7, the communication/ control circuits 120 and 220 include only in- band communication modules 121 and 221, respectively, and the BLE communication modules 122 and 222 include communication/control circuits 120 and 222, respectively. 220) can also be provided separately.

Hereinafter, the coil or coil unit may be referred to as a coil assembly, coil cell, or cell including a coil and at least one element adjacent to the coil.

Meanwhile, when the user places the wireless power receiver 200 within the operating volume of the wireless power transmitter 100, the wireless power transmitter 100 and the wireless power receiver 200 communicate for the purpose of configuring and controlling power transmission. Let's begin. At this time, the power signal can provide a carrier for all communications, and the protocol for communication can be composed of several steps. Hereinafter, the communication protocol will be described.

Figure 8 is a state transition diagram for explaining the wireless power transfer procedure.

WPC can define two communication protocols.

- Baseline Protocol (or BPP): May refer to an original protocol that supports only one-way communication from the wireless power receiver 200 to the wireless power transmitter 100.

- Extended Protocol (or EPP): Supports two-way communication and improved foreign object detection (FOD) functions, and can also support data transport stream functions and authentication options.

Referring to FIG. 8, the power transfer operation between the wireless power transmitter 100 and the wireless power receiver 200 according to an embodiment of the present specification is largely divided into a ping phase 810 and a configuration phase 820. It can be divided into (Configuration Phase), negotiation phase (830) (Negotiation Phase), and power transfer phase (Power Transfer Phase).

- Ping Phase (810)

In the ping phase 810, the wireless power transmitter 100 may attempt to establish communication with the wireless power receiver 200. Before attempting to establish communication, measurements may be performed to determine whether there are objects such as bank cards, coins or other metals that may be damaged or heated during power transfer. Here, these measurements can be performed without waking up the wireless power receiver 200.

Here, the wireless power transmitter 100 obtains design information from the wireless power receiver 200 and then concludes whether the detected metal is a foreign object or a friendly metal in a negotiation phase. You can postpone it to (830).

- Configuration phase (820)

In the configuration phase 820, the wireless power receiver 200 may send basic identification and configuration data to the wireless power receiver 200. And, both the wireless power transmitter 100 and the wireless power receiver 200 can use this information to create a baseline power transfer contract.

Additionally, the wireless power transmitter 100 and the wireless power receiver 200 may determine whether to continue the baseline protocol or the extended protocol in the configuration phase 820.

Here, the wireless power receiver 200 can use functions such as enhanced FOD, data transport stream, and authentication only when implementing the extended protocol.

- Negotiation Phase (830)

In the negotiation phase 830, the wireless power transmitter 100 and the wireless power receiver 200 may establish an extended power transfer contract that includes additional settings and restrictions. Additionally, the wireless power receiver 200 may provide design information to the wireless power transmitter 100. Later, the design information can be used to complete the FOD before transitioning to the power transfer phase 840.

Here, the negotiation phase 830 may correspond to a step that does not exist in the baseline protocol.

- Power transfer phase (840)

The power transfer phase 840 may be a step in which power is transferred to the load of the wireless power receiver 200.

In the extended protocol, the wireless power transmitter 100 and the wireless power receiver 200 may perform system calibration when this step begins. This stage may occasionally be interrupted to renegotiate elements of the power transmission agreement. However, power transfer may continue during this renegotiation.

Hereinafter, the protocols for the ping phase 810, configuration phase 820, negotiation phase 830, and power transfer phase 840, which were described previously. Let us explain each in more detail.

1. Ping Phase (810)

When the ping phase 810 begins, the wireless power transmitter 100 does not yet know whether the wireless power receiver 200 is within the operating volume. In addition, the wireless power transmitter 100 cannot recognize the wireless power receiver 200. For that reason, this system is usually disabled due to lack of power signal.

In this situation, before the wireless power transmitter 100 starts a digital ping to request a response from the wireless power receiver 200, the wireless power transmitter 100 may go through the following steps.

Figure 9 schematically shows an example of the protocol of the ping phase 810.

According to FIG. 9, the wireless power transmitter 100 can perform analog ping (S910). That is, the wireless power transmitter 100 can confirm whether an object exists in the operating volume by transmitting an analog ping. For example, a wireless power transmitter can detect whether an object exists in the operating space based on a change in current in the transmission coil or primary coil.

The wireless power transmitter 100 may apply NFC tag protection (S920). Here, NFC tag protection can be performed through the following procedures.

a) First, it can be confirmed whether one or more of the detected objects include an NFC tag.

b) Afterwards, it can be checked whether the object containing the NFC tag can withstand the power signal without damage.

c) If the wireless power transmitter 100 determines that the NFC tag cannot withstand the power signal, it does not start a digital ping and maintains the ping phase, and the wireless power transmitter 100 may inform the user of the reason why it cannot proceed. there is.

The wireless power transmitter 100 may detect foreign matter (S930). That is, the wireless power transmitter 100 can collect information that helps determine whether there is a foreign substance other than the wireless power receiver 200. For this purpose, the wireless power transmitter 100 can use various methods such as the free-power FOD method.

Meanwhile, in the three steps (S910, S920, and S930) described above, the radio power receiver may not operate.

If the wireless power transmitter 100 performs the above steps and determines that the wireless power receiver 200 is potentially present in the operating volume, the wireless power transmitter 100 may start a digital ping (S940). Here, the digital ping may request a response such as a signal strength (SIG) data packet or an end power transfer (EPT) data packet from the wireless power receiver 200.

Thereafter, the wireless power transmitter 100 may receive the SIG or EPT from the wireless power receiver 200 (S950). Here, the SIG data packet may provide a measure of coupling, and the SIG data packet may include information about signal strength values. Additionally, the EPT data packet may provide a request to stop power transmission and a reason for the request.

If the wireless power transmitter 100 does not receive the above response from the wireless power receiver 200, the wireless power transmitter 100 may repeat the above steps while remaining in the ping phase 810.

2. Configuration phase (820)

The configuration phase 820 is part of the following protocol.

- The wireless power receiver 200 can identify itself to the wireless power transmitter 100.

- The wireless power receiver 200 and the wireless power transmitter 100 can establish a baseline power transfer agreement.

- The wireless power receiver 200 and the wireless power transmitter 100 can determine the protocol variant to be used for power transmission.

In the configuration phase 820, the wireless power transmitter 100 and the wireless power receiver 200 may continue to operate using the digital ping parameter. This may mean that the power and current levels of both the wireless power transmitter 100 and the wireless power receiver 200 change only when the user moves the wireless power receiver 200 from position within the operating volume.

Hereinafter, the protocol in the configuration phase 820 will be described in more detail.

Figure 10 schematically shows an example of the protocol of the configuration phase 820.

According to FIG. 10, the wireless power transmitter 100 may receive an identification (ID) from the wireless power receiver 200 (S1010). Alternatively, the wireless power transmitter 100 may also receive an extended identification (XID) from the wireless power receiver 200 (S1020). That is, the wireless power receiver 200 can identify itself using an ID data packet and, optionally, an XID data packet.

The wireless power transmitter 100 may optionally receive a power control hold-off (PCH) data packet from the wireless power receiver 200 (S1030), and the wireless power transmitter 100 may receive CFG data from the wireless power receiver 200. Data packets can be received (S1040). That is, the wireless power receiver 200 can provide data for use in a power transfer contract using PCH and/or CFG data packets.

Finally, the wireless power transmitter 100 can check the extended protocol if possible (S1050).

Each data packet described above can be summarized as follows.

- ID: The ID data packet may be information that identifies the wireless power receiver 200. Here, the ID may include a manufacturer code, basic device identifier, etc. In addition, the ID may also include information that identifies the presence or absence of an XID data packet in the setup phase.

- XID: XID data packets may contain additional identification data.

- PCH: The PCH data packet may configure the delay between the reception of the CE data packet and the wireless power transmitter 100 starting coil current adjustment.

- CFG: CFG data packets can provide basic configuration data.

For example, a CFG data packet can provide all parameters governing power transfer in the baseline protocol. In addition, CFG data packets can provide all FSK communication parameters used in the extended protocol. Additionally, CFG data packets may provide additional functions of the wireless power receiver 200.

FIG. 11 is a diagram illustrating a message field of a configuration packet (CFG) of a wireless power reception device according to an embodiment.

According to FIG. 11, the configuration packet (CFG) according to one embodiment may have a header value of 0x51, and the message field of the configuration packet (CFG) includes a 1-bit authentication (AI) flag and a 1-bit outband (OB). ) flags may be included.

The authentication flag (AI) indicates whether the wireless power receiving device supports the authentication function. For example, if the value of the authentication flag (AI) is '1', it indicates that the wireless power receiving device supports the authentication function or can operate as an authentication initiator, and the value of the authentication flag (AI) is '1'. If it is '0', it may indicate that the wireless power receiving device does not support the authentication function or cannot operate as an authentication initiator.

The out-of-band (OB) flag indicates whether the wireless power receiving device supports out-of-band communication. For example, if the value of the out-band (OB) flag is '1', the wireless power receiving device indicates out-band communication, and if the value of the out-band (OB) flag is '0', the wireless power receiving device indicates out-band communication. You can indicate that it is not supported.

Provision of the ID and/or XID described above is for identification purposes. And, the provision of PCH and/or CFG is for building a power transmission contract.

3. Negotiation phase (830)

The negotiation phase 830 is a part of an extended protocol that allows the wireless power transmitter 100 and the wireless power receiver 200 to change the power transmission contract. There are two types of this stage.

- Negotiation phase 830: The negotiation phase 830 directly follows the configuration phase 820 and serves to create an initial extended power transmission contract. In addition, the negotiation phase 830 also serves to complete the pre-power FOD function. Here, the length of the negotiation phase is not limited.

-Renegotiation phase: The renegotiation phase can interrupt the power transfer phase 840 multiple times and generally serves to adjust a single element of the power transfer agreement. In addition, FOD/qf, FOD/rf and SRQ/rpr data packets may not be used in the renegotiation phase. Constraints on CE data packets in the power transfer phase 840 limit the length of the renegotiation phase.

In the negotiation or renegotiation stage, the Power Transfer Contract related to the reception/transmission of wireless power between the wireless power receiver and the wireless power transmitter is expanded or changed, or at least some of the elements of the power transfer contract are adjusted. The power transmission contract may be renewed, or information may be exchanged to establish out-of-band communication.

Figure 12 is a flowchart schematically illustrating a protocol of a negotiation stage or a renegotiation stage according to an embodiment.

Referring to FIG. 12, the wireless power transmitter 100 may receive a FOD status data packet (e.g. FOD) from the wireless power receiver 200 (S1210). Here, the wireless power receiver 200 may use the FOD status data packet to inform the wireless power transmitter 100 of the effect its presence has on selected properties of the reference wireless power transmitter 100. And, the wireless power transmitter 100 can configure the FOD function using this information.

The wireless power transmitter 100 may transmit an ACK/NAK for the FOD status data packet to the wireless power receiver 200 (S1215).

Meanwhile, the wireless power receiver 200 may receive an identification data packet (ID), a capabilities data packet (CAP), and an extended CAP (XCAP) of the wireless power transmitter 100 using a general request data packet (GRQ).

The general request packet (GRQ) may have a header value of 0x07 and may include a 1-byte message field. The message field of the general request packet (GRQ) may include a header value of a data packet that the wireless power receiver 200 requests from the wireless power transmitter 100 using the GRQ packet.

For example, in the negotiation or renegotiation stage, the wireless power receiver 200 may transmit a GRQ packet (GRQ/id) requesting an ID packet of the wireless power transmitter 100 to the wireless power transmitter 100 (S1220).

The wireless power transmitter 100 that has received the GRQ/id may transmit an ID packet to the wireless power receiver 200 (S1225). The ID packet of the wireless power transmitter 100 includes information about the 'Manufacturer Code'. The ID packet containing information about the 'Manufacturer Code' allows the manufacturer of the wireless power transmitter 100 to be identified.

Alternatively, in the negotiation stage or the renegotiation stage, the wireless power receiver 200 may transmit a GRQ packet (GRQ/cap) requesting a capability packet (CAP) of the wireless power transmitter 100 to the wireless power transmitter 100 ( S1230). The message field of GRQ/cap may include the header value (0x31) of the capability packet (CAP).

The wireless power transmitter 100 that has received the GRQ/cap may transmit a capability packet (CAP) to the wireless power receiver 200 (S1235).

Alternatively, in the negotiation or renegotiation stage, the wireless power receiver 200 may transmit a GRQ packet (GRQ/xcap) requesting a capability packet (CAP) of the wireless power transmitter 100 to the wireless power transmitter 100 ( S1240). The message field of GRQ/xcap may include the header value (0x32) of the performance packet (XCAP).

The wireless power transmitter 100 that has received GRQ/xcap may transmit a capability packet (XCAP) to the wireless power receiver 200 (S1245).

FIG. 13 is a diagram illustrating a message field of a capability packet (CAP) of a wireless power transmission device according to an embodiment.

A capability packet (CAP) according to one embodiment may have a header value of 0x31 and, referring to FIG. 19, may include a 3-byte message field.

Referring to FIG. 13, the message field of the capability packet (CAP) may include a 1-bit authentication (AR) flag and a 1-bit outband (OB) flag.

The authentication flag (AR) indicates whether the wireless power transmitter 100 supports the authentication function. For example, if the value of the authentication flag (AR) is '1', it indicates that the wireless power transmitter 100 supports the authentication function or can operate as an authentication responder, and the value of the authentication flag (AR) is If this is '0', it may indicate that the wireless power transmitter 100 does not support the authentication function or cannot operate as an authentication responder.

The outband (OB) flag indicates whether the wireless power transmitter 100 supports outband communication. For example, if the value of the outband (OB) flag is '1', the wireless power transmitter 100 indicates outband communication, and if the value of the outband (OB) flag is '0', the wireless power transmitter 100 may indicate that out-of-band communication is not supported.

In the negotiation stage, the wireless power receiver 200 can receive the capability packet (CAP) of the wireless power transmitter 100 and check whether the wireless power transmitter 100 supports the authentication function and whether it supports out-of-band communication.

Returning to FIG. 12, the wireless power receiver 200 uses at least one specific request packet (SRQ, Specific Request data packet) in the negotiation or renegotiation phase to enter into a power transfer agreement (Power Transfer) related to the power to be provided in the power transfer phase. Contract) elements can be updated (S1250), and ACK/NAK for this can be received (S1255).

Meanwhile, in order to confirm the extended power transfer agreement and end the negotiation phase, the wireless power receiver 200 transmits SRQ/en to the wireless power transmitter 100 (S1260) and receives ACK from the wireless power transmitter 100. You can (S1265).

4. Power transfer phase (840)

The power transfer phase 840 is a part of the protocol in which actual power is transmitted to the load of the wireless power receiver 200. Here, power transfer may proceed according to the conditions of the power transfer contract created in the negotiation phase 830.

<Power control based on CE>

The wireless power receiver 200 can control the power level by transmitting control error (CE) data measuring the deviation between the target and the actual operating point of the wireless power receiver 200 to the wireless power transmitter 100. there is. The wireless power transmitter 100 and wireless power receiver 200 aim to make the control error data zero, at which point the system will operate at the target power level.

<In-power transfer FOD method>

In addition to control error data, the wireless power transmitter 100 and the wireless power receiver 200 may exchange information to facilitate FOD. The wireless power receiver 200 regularly reports the amount of power it receives (received power level) to the wireless power transmitter 100, and the wireless power transmitter 100 determines whether a foreign substance has been detected. This can be notified to the receiver 200. Methods that can be used for FOD in the power transfer phase may correspond, for example, to power loss calculations. In this approach, the wireless power transmitter 100 compares the received power level reported by the wireless power receiver 200 with the amount of transmitted power (transmit power level) and when the difference exceeds a threshold, the wireless power receiver 200 ) can send a signal (about whether foreign substances have been monitored).

<Renegotiation phase>

If necessary depending on the situation, the wireless power transmitter 100 or the wireless power receiver 200 may request renegotiation of the power transfer contract during the power transfer phase. Examples of changed circumstances in which renegotiation of a power transmission contract may occur include:

- When the wireless power receiver 200 requires (substantially) more power than previously negotiated.

- When the wireless power transmitter 100 detects that it is operating at low efficiency.

- When the wireless power transmitter 100 can no longer maintain the current power level due to the increased operating temperature (or vice versa, i.e., operates at a higher power level after the wireless power receiver 200 has sufficiently cooled down) when you can).

Here, an example of a specific protocol for the renegotiation phase is the same as described above.

<Data Transport Stream>

The wireless power transmitter 100 and the wireless power receiver 200 may initiate a data transmission stream to exchange application level data throughout the power transfer phase 840.

Here, an important common application is authentication, where each side can verify the other's credentials in a tamper-proof manner. For example, the wireless power receiver 200 may want to check the credentials of the wireless power transmitter 100 to ensure that the wireless power transmitter 100 can be trusted to operate safely at high power levels. Having the appropriate credentials can mean you have passed compliance testing.

Accordingly, the present specification may provide a method of starting power transfer at a low power level and controlling the power to a higher level only after successfully completing the authentication protocol.

<Protocol in power transfer phase 840>

So far, the operation between the wireless power transmitter 100 and the wireless power receiver 200 in the power transfer phase 840 has been schematically described. Hereinafter, for a smooth understanding of the operation in the power transfer phase 840, the protocol in the power transfer phase 840 will be described separately as a baseline protocol and an extended protocol.

Figure 14 schematically shows a flowchart of the data flow for the power transfer phase 840 in the baseline protocol.

According to FIG. 14, the wireless power receiver 200 may transmit CE to the wireless power transmitter 100 (S1410). Here, the wireless power receiver 200 can generally transmit CE data packets several times per second.

The wireless power receiver 200 may generally transmit a received power (RP) data packet (RP8 in the baseline protocol) to the wireless power transmitter 100 once every 1.5 seconds (S1420).

Optionally, the wireless power receiver 200 may transmit a charge status (CHS) data packet to the wireless power transmitter 100 (S1430).

The data packet described above can be summarized and explained as follows.

- CE: CE data packets can provide feedback on the desired power level. The CE data packet may include a control error value, where the control error value may be a signed integer value that is a relative measure of the deviation between the actual operating point and the target operating point of the wireless power receiver 200. . If the control error value at this time is a positive value, it indicates that the actual operating point is below the target operating point, and the wireless power transmitter 100 may be requested to increase the power signal. If the control error value is a negative value, it indicates that the actual operating point is above the target operating point, and the wireless power transmitter 100 may be requested to reduce the power signal.

- RP8: RP8 data packets can report the received power level. Here, RP8 data packets can only be included in the baseline protocol.

- CHS: CHS data packets can provide the charge level of the battery at the load.

Figure 15 schematically shows a flowchart of the data flow for the power transfer phase 840 in the extended protocol.

According to FIG. 15, the wireless power receiver 200 may transmit CE to the wireless power transmitter 100 (S1510). Here, the wireless power receiver 200 can generally transmit CE data packets several times per second.

The wireless power receiver 200 may generally transmit a received power (RP) data packet (RP in the extended protocol) to the wireless power transmitter 100 once every 1.5 seconds (S1515).

In the power transfer phase, the control error packet (CE) and the received power packet (RP) are data packets that must be repeatedly transmitted / received according to the required timing constraints for control of wireless power.

The wireless power transmitter 100 can control the level of wireless power transmitted based on the control error packet (CE) and received power packet (RP) received from the wireless power receiver 200.

Meanwhile, in the extended protocol, the wireless power transmitter 100 may respond to the received power packet (RP) with a bit pattern such as ACK, NAK, or ATN (S1520).

The fact that the wireless power transmitter 100 responds with ACK to a received power packet (RP/0) with a mode value of 0 means that power transmission can continue at the current level.

When the wireless power transmitter 100 responds with NAK to a received power packet (RP/0) with a mode value of 0, this means that the wireless power receiver 200 must reduce power consumption.

For a received power packet (RP/1 or RP/2) with a mode value of 1 or 2, the wireless power transmitter 100 responds with ACK when the wireless power receiver 200 receives a received power packet (RP/1 or RP/2). This means that the power correction value included in RP/2) has been accepted.

For a received power packet (RP/1 or RP/2) with a mode value of 1 or 2, the wireless power transmitter 100 responds with NAK when the wireless power receiver 200 receives a received power packet (RP/1 or RP/2). This means that the power correction value included in RP/2) has not been accepted.

The previously described received power packet (RP/1) with a mode value of 1 may mean the first calibration data point, and the received power packet (RP/2) with a mode value of 2 may mean additional correction data. It may mean a point (additional calibration data point). Here, the wireless power receiver may transmit a plurality of additional power correction values by transmitting a received power packet (RP/2) with a mode value of 2 to the wireless power transmitter multiple times, and the wireless power transmitter may transmit the received RP/1 and several additional power correction values. The calibration procedure can be performed based on the RP/2 of the dog.

When the wireless power transmitter 100 responds with ATN to the received power packet (RP), it means that the wireless power transmitter 100 requests permission for communication. That is, the wireless power transmitter 100 may transmit an attention (ATN) response pattern to request permission to transmit a data packet in response to an RP data packet. In other words, the wireless power transmitter 100 may transmit an ATN to the wireless power receiver 200 in response to the RP data packet and request the wireless power receiver 200 for permission to transmit the data packet.

Optionally, the wireless power receiver 200 may transmit a charge status (CHS) data packet to the wireless power transmitter 100 (S1525).

Meanwhile, the wireless power transmitter 100 and the wireless power receiver 200 use DSR (data stream response) data packets and CAP data to initiate renegotiation of elements in the power transmission contract (generally guaranteed load power). Packets and NEGO data packets can be exchanged.

For example, the wireless power receiver 200 may transmit a DSR data packet to the wireless power transmitter 100 (S1530), and the wireless power transmitter 100 may transmit a CAP to the wireless power receiver 200 (S1535).

In addition, the wireless power receiver 200 transmits a NEGO data packet to the wireless power transmitter 100 (S1540), and the wireless power transmitter 100 can transmit an ACK to the wireless power receiver 200 in response to the NEGO data packet. There is (S1545).

Here, the data packets related to the start of the renegotiation phase can be summarized as follows.

- DSR: Any one of the following values can be set in the DSR data packet.

i) 0x00-DSR/nak: Indicates that the last received data packet of the wireless power transmitter 100 was rejected.

ii) 0x33-DSR/poll: Invite the wireless power transmitter 100 to send a data packet.

iii) 0x55-DSR/nd: Indicates that the last received data packet from the wireless power transmitter 100 was not expected.

iv) 0xFF-DSR/ack: Confirms that the last received data packet of the wireless power transmitter 100 has been properly processed.

- CAP: The CAP data packet provides information about the function of the wireless power transmitter 100. The specific details are the same as described previously.

- NEGO: NEGO data packets may request the wireless power transmitter 100 to proceed to the renegotiation step.

The wireless power transmitter 100 and the wireless power receiver 200 may use auxiliary data control (ADC), auxiliary data transport (ADT), and DSR data packets to exchange application level data.

That is, from the perspective of transmission and reception of a data transmission stream for exchange of application-level data, the wireless power receiver 200 may transmit ADC/ADT to the wireless power transmitter 100 (S1550), and the wireless power transmitter 100 responds thereto. In response, ACK/NAK may be transmitted to the wireless power receiver 200 (S1555). In addition, the wireless power receiver 200 may transmit a DSR to the wireless power transmitter 100 (S1560), and the wireless power transmitter may transmit ADC/ADT to the wireless power receiver (S1565).

Here, the data transport stream serves to transfer application-level data from the data stream initiator to the data stream responder. Additionally, application level data can be broadly divided into i) authentication applications, and ii) proprietary (general purpose) applications.

Among application level data, messages/information related to the authentication application can be organized as follows.

The message used in the authentication procedure is called an authentication message. Authentication messages are used to convey information related to authentication. There are two types of authentication messages. One is an authentication request, and the other is an authentication response. An authentication request is sent by an authentication initiator, and an authentication response is sent by an authentication responder. The wireless power transmitting device and receiving device can be an authentication initiator or an authentication responder. For example, if the wireless power transmitting device is the authentication initiator, the wireless power receiving device becomes the authentication responder, and if the wireless power receiving device is the authentication initiator, the wireless power transmitting device becomes the authentication responder.

Authentication request messages include GET_DIGESTS, GET_CERTIFICATE, and CHALLENGE.

- GET_DIGESTS: This request can be used to retrieve certificate chain digests. The wireless power receiver 200 can request a desired number of digests at a time.

- GET_CERTIFICATE: This request can be used to read segments of the target certificate chain.

- CHALLENGE: This request can be used to initiate authentication of a power transmitter product device.

The authentication response message includes DIGESTS, CERTIFICATE, CHALLENGE_AUTH, and ERROR.

- DIGESTS: The wireless power transmitter 100 can send a certificate chain summary using the DIGESTS response and report slots containing a valid certificate chain summary.

- CERTIFICATE: This response can be used by the wireless power transmitter 100 to send the requested segment of the certificate chain.

- CHALLENGE_AUTH: The wireless power transmitter 100 can respond to the CHALLENGE request using CHALLENGE_AUTH.

- ERROR: This response can be used to transmit error information from the power transmitter.

The authentication message may be called an authentication packet, authentication data, or authentication control information. Additionally, messages such as GET_DIGEST and DIGESTS may also be called GET_DIGEST packets, DIGEST packets, etc.

Meanwhile, as described above, the wireless power receiver 200 and the wireless power transmitter 100 can transmit application level data through a data transmission stream. Application-level data transmitted through a data transport stream may consist of a data packet sequence with the following structure.

- Initial ADC data packet that opens the stream.

i) Types of messages contained in the stream.

ii) Number of data bytes in the stream.

- A series of ADT data packets containing the actual message.

- The final ADC/end data packet that closes the stream.

Hereinafter, the data transport stream for an example in which the above ADC, ADT, and ADC/end data packets are used will be described using the drawings.

FIG. 16 illustrates an application-level data stream between the wireless power transmitter 100 and the wireless power receiver 200 according to an example.

Referring to FIG. 16, the data stream may include auxiliary data control (ADC) data packets and/or auxiliary data transport (ADT) data packets.

ADC data packets are used to open a data stream. ADC data packets can indicate the type of message included in the stream and the number of data bytes. On the other hand, ADT data packets are sequences of data containing the actual message. ADC/end data packets are used to signal the end of a stream. For example, the maximum number of data bytes in a data transport stream may be limited to 2047.

ACK or NAC (NACK) is used to notify whether ADC data packets and ADT data packets are normally received. Between the transmission timing of the ADC data packet and the ADT data packet, control information necessary for wireless charging, such as a control error packet (CE) or DSR, may be transmitted.

Using this data stream structure, authentication-related information or other application-level information can be transmitted and received between a wireless power transmitter and a receiver.

An example for understanding the operation between the wireless power transmitter 100 and the wireless power receiver 200 in the power transfer phase 840 described above may be as follows.

Figure 17 shows a power control control method according to one embodiment.

In the power transfer phase in FIG. 17, the wireless power transmitter 100 and the wireless power receiver 200 can control the amount of power transmitted by performing communication along with power transmission and reception. The wireless power transmitter and wireless power receiver operate at a specific control point. The control point represents the combination of voltage and current provided from the output of the wireless power receiver when power transfer is performed.

To explain in more detail, the wireless power receiving device selects a desired control point - the desired output current/voltage, temperature of a specific location of the mobile device, etc., and additionally selects the actual control point currently operating. ) is determined. The wireless power receiving device can use the desired control point and the actual control point to calculate a control error value and transmit it as a control error packet to the wireless power transmitting device.

And the wireless power transmitter can control power transfer by setting/controlling new operating points - amplitude, frequency, and duty cycle - using the received control error packet. Therefore, control error packets are transmitted/received at regular time intervals in the strategy delivery stage. As an example, the wireless power receiving device sets the control error value to a negative number when trying to reduce the current of the wireless power transmitting device, and sets the control error value to a negative number when trying to increase the current. You can transmit by setting the value to a positive number. In this way, in the inductive mode, the wireless power receiver can control power transmission by transmitting a control error packet to the wireless power transmitter.

In resonant mode, it can operate in a different way than in inductive mode. In resonance mode, one wireless power transmitter must be able to serve multiple wireless power receivers simultaneously. However, when controlling power transfer as in the above-described induction mode, the transferred power is controlled by communication with one wireless power receiver, so it may be difficult to control power transfer to additional wireless power receivers. Therefore, in the resonance mode of this specification, the wireless power transmission device transmits basic power in common, and the wireless power reception device intends to use a method of controlling the amount of power received by controlling its own resonance frequency. However, even in this resonance mode operation, the method described in FIG. 17 is not completely excluded, and additional transmission power control may be performed using the method in FIG. 17.

<Operation according to power profile>

Wireless charging methods include a magnetic induction method that uses the magnetic induction phenomenon between the primary and secondary coils, and a magnetic resonance method that transmits power by creating magnetic resonance using frequencies ranging from tens of kHz to several MHz. Here, the wireless charging standard for the magnetic resonance method is led by a council called A4WP, and the standard for the magnetic induction method is led by the Wireless Power Consortium (WPC). Here, WPC is designed to exchange various status information and commands related to the wireless charging system in-band.

The Qi standard in WPC defines a baseline power profile (BPP), an extended power profile (EPP), and a magnetic power profile. Hereinafter, BPP, EPP, and MPP will be described respectively.

A. Baseline power profile (BPP)

BPP relates to a power transfer profile between a wireless power transmitter and receiver that supports power transfer of up to 5W. And, in BPP, unidirectional communication from a wireless power receiver to a wireless power transmitter is supported. The communication method at this time may correspond to ASK (amplitude shift keying). In BPP, there may be protocol phases of ping, configuration, and power transfer.

B. EPP(extended power profile)

EPP relates to a power transfer profile between a wireless power transmitter and receiver that supports power transfer of up to 15W. And, in EPP, bidirectional communication between a wireless power receiver and a wireless power transmitter is supported. The communication method from the wireless power receiver to the wireless power transmitter may correspond to amplitude shift keying (ASK), and the communication method from the wireless power transmitter to the wireless power receiver may correspond to frequency shift keying (FSK). In EPP, there may be protocol phases of ping, setup, negotiation, and power transfer.

(a) Compatibility in EPP

EPP may correspond to a higher profile of BPP.

For example, if a BPP wireless power receiver is placed on an EPP wireless power transmitter, the EPP wireless power transmitter can operate as a BPP wireless power transmitter.

For example, if the EPP wireless power receiver is placed on a BPP wireless power transmitter, the EPP wireless power receiver can operate as a BPP wireless power receiver.

In other words, EPP can maintain compatibility with BPP.

(b) EPP indication method of EPP wireless power receiver

The EPP wireless power receiver can indicate that it is an EPP wireless power receiver by setting the 'neg' bit in the configuration packet (i.e. CFG) to 1. Specific examples of configuration packets are as described above.

(c) EPP indication method of EPP wireless power transmitter

When the EPP wireless power transmitter receives a configuration packet with the 'neg' bit set to 1 from the wireless power receiver, the EPP wireless power transmitter may respond to the wireless power receiver with an ACK FSK bit pattern.

For reference, as previously explained, the BPP wireless power transmitter does not support the FSK communication method, so the BPP wireless power transmitter cannot transmit FSK bit patterns. Accordingly, the EPP wireless power receiver, which set the 'neg' bit to 1 and transmitted a configuration packet to the BPP wireless power transmitter, does not receive the above ACK response, thereby identifying the other wireless power transmitter as a BPP wireless power transmitter. .

Meanwhile, starting with Qi v2.0, we aim to provide a new power transfer profile for the wireless power transfer system, and among the power transfer profiles proposed at this time is MPP (magnetic power profile). MPP may correspond to a proprietary extension from Apple based on Qi v1.3.0.

C. MPP(magnetic power profile)

MPP relates to a power transfer profile between a wireless power transmitter and receiver that supports power transfer of up to 15W. And, in MPP, bidirectional communication between a wireless power receiver and a wireless power transmitter is supported. The communication method from the wireless power receiver to the wireless power transmitter may correspond to amplitude shift keying (ASK), and the communication method from the wireless power transmitter to the wireless power receiver may correspond to frequency shift keying (FSK). At this time, fast FSK (NCYCLE = 128) can be used during the negotiation and power transfer phase.

In MPP, there may be protocol phases of ping, setup, MPP negotiation, and MPP power transfer.

(a) Compatibility in MPP

MPP may correspond to a higher profile of BPP.

For example, if a BPP wireless power receiver is placed on an MPP wireless power transmitter, the MPP wireless power transmitter can operate as a BPP wireless power transmitter.

For example, if the MPP wireless power receiver is placed on a BPP wireless power transmitter, the MPP wireless power receiver can operate as a BPP wireless power receiver.

In other words, MPP can maintain compatibility with BPP.

(b) MPP operation of MPP wireless power receiver (MPP instruction method)

The MPP wireless power receiver may use a specific MPP indicator within the extended ID packet.

In order for the MPP wireless power receiver to indicate whether MPP is supported through XID, the wireless power receiver must inform the wireless power transmitter that the XID is transmitted through an ID packet. The ID packet transmitted by the MPP wireless power receiver may be as follows.

Figure 18 schematically shows the structure of an MPP ID packet.

According to FIG. 18, in the MPP ID packet, the value of the major version field from b4 to b7 of B0 may be set to 1.

In the MPP ID packet, the value of the minor version field from b0 to b3 of B0 may be a value to be determined later.

In the MPP ID packet, the values of the manufacturer codes of B1 and B2 may be assigned as PRMC codes.

In the MPP ID packet, the value of the 'ext' field of b7 of B3 may be set to 1 to indicate that an XID packet is additionally transmitted.

In the MPP ID packet, the values of the random identifier fields of b0 to b6 of B3 and b3 to b7 of B4 and B5 may be set according to a random device identification policy.

Figure 19 schematically shows an example of an XID packet in MPP.

According to Figure 19, an XID packet in MPP may include an 'XID Selector' field, a 'Restricted' field, and a 'Freq Mask' field.

Here, whether MPP is supported can be determined depending on whether the value of 'XID selector' is 0xFE. That is, if the value of B_0 of the XID is 0xFE, the XID at this time may correspond to information indicating that the wireless power receiver supports MPP.

The 'Restricted' field may correspond to information indicating whether the wireless power receiver operates in MPP restricted mode or MPP full mode. If the wireless power receiver selects to operate in MPP limited mode, the above field can be set to 1. Meanwhile, in other cases (eg, when the wireless power receiver selects not to operate in MPP limited mode), the above field may be set to 0.

The 'Preferred Frequency' field may mean the MPP preferred frequency. Here, if the wireless power receiver wishes to retrieve information from the wireless power transmitter before switching the frequency (in the negotiation phase), this field can be set to 128 kHz. Otherwise, the wireless power receiver can set this field to 360 kHz.

The 'Freq Mask' field corresponds to a field for determining whether the operating frequency of 360 kHz is supported. That is, if the 'Freq Mask' field is set to 0, 360kHz is supported.

In summary, the wireless power transmitter determines whether the 'Ext' bit of the ID received from the wireless power receiver is set to 1 and whether B_0 of the You can decide whether to support it or not.

(c) MPP operation of MPP wireless power transmitter (MPP instruction method)

After detecting the placement of a wireless power receiver on the charging surface, the MPP wireless power transmitter can use the information contained in the ID and XID packets to perform a digital ping and identify the receiver.

Here, the wireless power transmitter may determine that the wireless power receiver supports MPP if all of the following conditions are met.

- Qi version: The Qi protocol version of the ID packet is set to (Major=1, Minor=TBD) or higher.

- MPP support notification: The subheader (byte 0) of the XID packet is set to the MPP selector.

If the above two conditions are not satisfied, the wireless power transmitter can proceed with subsequent procedures according to the Qi v1.3 specification.

Meanwhile, according to the MPP operation mode requested by the MPP wireless power receiver in the XID packet, the wireless power transmitter performs the following.

- Restricted profile activation (MPP restricted mode): When the 'restricted' flag is set to 1.

- Full profile activation (MPP full mode): When the 'restricted' flag is set to 0.

Specific examples of the above limited profile and full profiles will be described later.

Meanwhile, when the MPP wireless power transmitter receives a configuration packet with the 'neg' bit set to 1 from the wireless power receiver (in MPP full mode), the MPP wireless power transmitter (in MPP full mode) responds to this by using the MPP ACK FSK bit pattern. It can respond to the wireless power receiver.

For reference, the wireless power transmitter in MPP limited mode does not support the FSK communication method, so the wireless power transmitter in MPP limited mode cannot transmit FSK bit patterns. However, since the wireless power transmitter in MPP limited mode uses an operation signal of 360 kHz to transmit power, the 'neg' bit is set to 1 and a configuration packet is transmitted to the wireless power transmitter operating in MPP limited mode. The MPP wireless power receiver can identify the other wireless power transmitter as an MPP limited mode wireless power transmitter through the operating frequency.

(d) Mode of MPP

Meanwhile, two modes may exist in MPP. One of them is MPP Restricted mode (also known as MPP Baseline Profile), and the other is MPP Full mode (also known as MPP Full Profile).

To briefly explain the difference between the two, in MPP restricted mode, the 'restricted' field in the XID is set to 1, but in MPP full mode, the 'restricted' field in the XID is set to 0.

Additionally, FSK communication is not supported in MPP limited mode, but FSK communication may be supported in MPP full mode.

Additionally, since FSK communication is not supported in MPP restricted mode, MPP ACK for CFG cannot be transmitted, and therefore, MPP negotiation is not supported in MPP limited mode. On the other hand, in MPP full mode, FSK communication is supported, so MPP ACK for CFG can be transmitted, and accordingly, MPP negotiation can be supported in MPP full mode.

Hereinafter, MPP limited mode and MPP full mode will be described in more detail. Here, MPP limited mode can be used interchangeably with the MPP baseline profile, and MPP full mode can be interchanged with the MPP full profile.

Hereinafter, for a better understanding of MPP limited mode and MPP full mode, the protocols in each mode will be described in more detail.

i) MPP restricted mode

As previously explained, FSK communication is not supported in MPP restricted mode. That is, in the MPP limited mode, there may be no data packets transmitted from the wireless power transmitter to the wireless power receiver. Against this background, the protocol in MPP restricted mode will be explained through the drawings.

Figure 20 schematically shows the protocol in MPP restricted mode.

According to FIG. 20, the wireless power receiver may transmit a SIG to the wireless power transmitter on a first operating frequency (eg, 128 kHz). At this time, the first operating frequency may correspond to an operating frequency at which BPP and/or EPP can be performed. And, the first operating frequency at this time corresponds to the frequency at which the wireless power transmitter operates.

The wireless power receiver may transmit an ID packet to the wireless power transmitter on a first operating frequency. At this time, since the XID is always transmitted in MPP, the 'ext' bit of the ID may be set to 1 to indicate that the XID is additionally transmitted.

The wireless power receiver may transmit an XID packet to the wireless power transmitter on a first operating frequency.

At this time, the value of B0 in the XID may be 0xFE, and if the value of B0 in the XID is set to 0xFE, this may correspond to information indicating that the wireless power receiver supports MPP. In addition, the 'Restricted' field in the XID at this time may be set to 1 to indicate that the wireless power receiver operates in MPP restricted mode.

Here, when the wireless power transmitter receives the above XID packet indicating the MPP limited mode, the wireless power transmitter may remove the power signal and restart the ping phase at a new operating frequency.

When the ping phase is restarted, the wireless power receiver begins transmitting the SIG again. However, the operating frequency at this time may be a second operating frequency (eg, 360 kHz).

Thereafter, the wireless power receiver transmits ID, XID, and CFG packets to the wireless power transmitter at the second operating frequency, respectively. In addition, the wireless power receiver can receive wireless power based on the MPP baseline from the wireless power transmitter by transmitting a CEP to the wireless power transmitter.

ii) MPP full mode

As described previously, FSK communication can be supported in MPP full mode. That is, in MPP full mode, there may be data packets transmitted from the wireless power transmitter to the wireless power receiver. In other words, MPP negotiation, etc. may be conducted between a wireless power transmitter and a wireless power receiver. Against this background, the protocol in MPP full mode will be explained through the drawings.

Figures 21 and 22 schematically show the protocol in MPP full mode.

First, according to FIG. 21, the wireless power receiver may transmit a SIG to the wireless power transmitter on a first operating frequency (eg, 128 kHz). At this time, the first operating frequency may correspond to an operating frequency at which BPP and/or EPP can be performed. And, the first operating frequency at this time corresponds to the frequency at which the wireless power transmitter operates.

The wireless power receiver may transmit an ID packet to the wireless power transmitter on a first operating frequency. At this time, since the XID is always transmitted in MPP, the 'ext' bit of the ID may be set to 1 to indicate that the XID is additionally transmitted.

The wireless power receiver may transmit an XID packet to the wireless power transmitter on a first operating frequency.

At this time, the value of B0 in the XID may be 0xFE, and if the value of B0 in the XID is set to 0xFE, this may correspond to information indicating that the wireless power receiver supports MPP. In addition, the 'Restricted' field in the XID at this time may be set to 0 to indicate that the wireless power receiver operates in MPP full mode.

Meanwhile, in MPP full mode, unlike MPP limited mode, the power signal is not removed even if the wireless power transmitter receives an XID packet from the wireless power receiver. At this time, since the power signal has not yet been removed, the wireless power receiver transmits a CFG packet to the wireless power transmitter after the XID packet.

And, the wireless power receiver can receive an MPP ACK from the wireless power transmitter as a response to the above CFG packet.

The wireless power receiver that receives the MPP ACK enters a negotiation phase with the wireless power transmitter, and both the wireless power receiver and the wireless power transmitter can proceed with negotiation.

After negotiation progresses, the wireless power receiver may enter a power transfer phase with the wireless power transmitter.

Meanwhile, the wireless power receiver transmits an EPT packet to the wireless power transmitter. The wireless power transmitter that receives the EPT packet removes the power signal and can then restart the ping phase at a new operating frequency.

According to FIG. 22, when the ping phase is restarted, the wireless power receiver starts again from transmitting the SIG. However, the operating frequency at this time may be a second operating frequency (eg, 360 kHz).

Thereafter, the wireless power receiver transmits ID, XID, and CFG packets to the wireless power transmitter at the second operating frequency, respectively. And, the wireless power receiver can receive the MPP ACK from the wireless power transmitter.

The wireless power receiver that receives the MPP ACK enters a negotiation phase with the wireless power transmitter at the second operating frequency, and both the wireless power receiver and the wireless power transmitter can proceed with negotiation.

After negotiation, the wireless power receiver enters a power transfer phase with the wireless power transmitter at the second operating frequency. In addition, the wireless power receiver may receive wireless power based on the MPP full mode from the wireless power transmitter by transmitting an XCE to the wireless power transmitter and responding (eg, receiving an ACK).

Hereinafter, this specification will be described in more detail.

An authentication function is provided in the current WPC Qi specification. Here, authentication may proceed as follows.

Regarding authentication, the wireless power receiver can become an initiator and send (request) an authentication request to the wireless power transmitter. In this case, the wireless power transmitter becomes a responder, and the wireless power transmitter transmits an authentication response to the request from the wireless power receiver to the wireless power receiver. Through this, the wireless power receiver can authenticate the wireless power transmitter.

Below, data for authentication will be described.

Figure 23 shows an example of an authentication message header.

According to FIG. 23, all messages related to authentication have a header, and the authentication message header may include an authentication protocol version field and a message type field.

Figure 24 shows an example of the authentication protocol version field.

According to FIG. 24, the authentication protocol version field may have values from 0x0 to 0xF. At this time, if the value of the authentication protocol version field is 0x0, this may mean a reserved value. If the value of the authentication protocol version field is 0x1, this may mean authentication protocol version 1.0. If the value of the authentication protocol version field is 0x2 to 0xF, this may mean a reserved value.

Figure 25 shows an example of the message type field for an authentication request.

According to Figure 25, if the value of the message type field is 0x0 to 0x7, this is the value used for the authentication response. If the value of the message type field is 0x8, this may mean a reserved value. If the value of the message type field is 0x9, this may mean GET_DIGESTS. If the value of the message type field is 0xA, this may mean GET_CERTIFICATE. If the value of the message type field is 0xB, this may mean CHALLENGE. If the value of the message type field is 0xC to 0xF, this may mean a reserved value.

Figure 26 shows an example of the message type field for an authentication response.

According to FIG. 26, if the value of the message type field is 0x0, this may mean a reserved value. If the value of the message type field is 0x1, this may mean DIGESTS. If the value of the message type field is 0x2, this may mean CERTIFICATE. If the value of the message type field is 0x3, this may mean CHALLENGE_AUTH. If the value of the message type field is 0x4 to 0x6, this may mean a reserved value. If the value of the message type field is 0x7, this may mean ERROR. If the value of the message type field is 0x8 to 0xF, this is the value used for the authentication request.

First, the authentication request message sent by the wireless power receiver consists of GET_DIGESTS/GET_CERTIFICATE/CHALLENGE.

Figure 27 shows an example of GET_DIGESTS. Figure 28 shows an example of GET_CERTIFICATE. Figure 29 shows an example of CHALLENGE.

In summary, authentication request messages include GET_DIGESTS, GET_CERTIFICATE, and CHALLENGE.

- GET_DIGESTS: This request can be used to retrieve certificate chain digests. The wireless power receiver 200 can request a desired number of digests at a time.

- GET_CERTIFICATE: This request can be used to read segments of the target certificate chain.

- CHALLENGE: This request can be used to initiate authentication of a power transmitter product device.

The authentication response message sent by the wireless power transmitter includes DIGESTS/CERTIFICATE/CHALLENGE_AUTH. Additionally, the authentication response message may include ERROR.

Figure 30 shows an example of DIGESTS. Figure 31 shows an example of CERTIFICATE. Figure 32 shows an example of CHALLENGE_AUTH. Figure 33 shows an example of ERROR.

In summary, the authentication response message includes DIGESTS, CERTIFICATE, CHALLENGE_AUTH, and ERROR.

- DIGESTS: The wireless power transmitter 100 can send a certificate chain summary using the DIGESTS response and report slots containing a valid certificate chain summary.

- CERTIFICATE: This response can be used by the wireless power transmitter 100 to send the requested segment of the certificate chain.

- CHALLENGE_AUTH: The wireless power transmitter 100 can respond to the CHALLENGE request using CHALLENGE_AUTH.

- ERROR: This response can be used to transmit error information from the power transmitter.

As previously explained, the authentication function has been added as a new feature to WPC Qi, a wireless charging standard. Authentication is a process to check whether the other device has actually been certified by Qi, and is a very important way to check whether a standard product exists.

Authentication in the current specification is carried out at the request of PRx, and this function is an optional configuration rather than a required function. In order to perform the authentication function, the PTx sends an authentication response to the authentication request sent by the PRx, so that the PRx checks whether the PTx has Qi authentication.

The following drawings were prepared to explain a specific example of the present specification. Since the names of specific devices or specific signals/messages/fields described in the drawings are provided as examples, the technical features of this specification are not limited to the specific names used in the drawings below.

Figure 34 is a flowchart of a method for transmitting wireless power, according to an embodiment of the present specification.

According to FIG. 34, the wireless power transmitter may enter a power transfer phase related to transmitting wireless power (S3410).

As described above, the power transfer phase 840 is a part of the protocol in which actual power is transmitted to the load of the wireless power receiver 200. Here, power transfer may proceed according to the conditions of the power transfer contract created in the negotiation phase 830.

The wireless power transmitter 100 and the wireless power receiver 200 may initiate a data transmission stream to exchange application level data throughout the power transfer phase 840.

Here, an important common application is authentication, where each side can verify the other's credentials in a tamper-proof manner. For example, the wireless power receiver 200 may want to check the credentials of the wireless power transmitter 100 to ensure that the wireless power transmitter 100 can be trusted to operate safely at high power levels. Having the appropriate credentials can mean you have passed compliance testing.

Accordingly, the present specification may provide a method of starting power transfer at a low power level and controlling the power to a higher level only after successfully completing the authentication protocol.

Specific examples of the power transfer phase are as described above.

The wireless power transmitter may receive the first application message from the wireless power receiver in the power transfer phase (S3420).

Here, as described above, the first application message may be transmitted through a data transport stream (data stream).

As previously described, the data stream may include auxiliary data control (ADC) data packets and/or auxiliary data transport (ADT) data packets.

ADC data packets are used to open a data stream. ADC data packets can indicate the type of message included in the stream and the number of data bytes. On the other hand, ADT data packets are sequences of data containing the actual message. ADC/end data packets are used to signal the end of a stream.

In the power transfer phase, a second application message that is a response to the first application message may be transmitted to the wireless power receiver.

As previously described, the second application message may also be transmitted through a data transport stream (data stream). A detailed description of the data transport stream is the same as described above.

Here, it has been explained that the application message exchanged between the wireless power transmitter and the wireless power receiver may be an authentication request message or an authentication response message.

For example, if the first application message is an authentication request message, the first application message may correspond to, for example, GET_DIGESTS/GET_CERTIFICATE/CHALLENGE. For example, if the second application message is an authentication response message, the second application message may correspond to DIGESTS/CERTIFICATE/CHALLENGE_AUTH.

At this time, the wireless power transmitter may start transmitting the second application message within a specific time period. And, the starting point of a specific time interval may be the ending point of the first application message.

Here, if the first application message is, for example, GET_DIGESTS and the second application message is, for example, DIGESTS, the specific time interval at this time may be t_DigestReady. And, the value of t_DigestReady may correspond to, for example, 3 seconds. Additionally, t_DigestTimeout may equal 43 seconds.

At this time, the TPR can be configured to send multiple RP/0 packets (e.g., 3-4 times per second). This allows the wireless power transmitter multiple opportunities to respond within 3 seconds after receiving GET_DIGESTS.

Here, the time convention of t_DigestReady may be, for example, as follows. Examples of the time regulations below are explained in more detail, for example, in the examples described later.

- Start of t_DigestReady: From the beginning of the ADC/end packet (for GET_DIGEST) of the TPR.

- t_DigestReady End: Until the start of ATN response from the power transmitter product. (If the wireless power transmitter generates a DIGESTS response, the message type may be 0x1 in the authentication message header.)

Hereinafter, the timing requirements of the wireless power transmitter will be described in more detail. Examples to be described below correspond to a more detailed explanation of the example in FIG. 34. Therefore, it is obvious that all of the contents described below can be applied to the example of FIG. 34.

<Technical challenges that the invention seeks to achieve>

In this specification, by exchanging simple information in the negotiation phase when recharging for a device on which authentication has been performed, fast authentication is performed through confirmation of the device on which authentication has previously been performed, and based on this, quick activation and high-speed charging are performed. We propose a method to make this possible. However, it is not always limited to fast charging (or high power) mode, and a method of performing fast authentication is proposed assuming that trust between devices is established through an authenticated power transfer phase or trusted power transfer phase.

Through the proposed method, it is possible to authenticate the device before entering the PT (Power Transfer) phase of wireless charging, making it possible to quickly enter high-speed charging.

Figure 35 shows problems that may occur in existing technology when charging is stopped due to detection of foreign substances, etc.

Referring to Figure 35, the wireless device enters the PT phase through DP, SS/ID/CFG, Negotiation, and Calibration for charging.

- #1: Charging is interrupted due to detection of foreign substances and other charging errors during initial calibration: Since the wireless device did not perform authentication, recharging begins again from DP and enters high power mode after performing the authentication function.

- #2: Charging stopped due to detection of foreign matter and other charging errors during authentication: Due to a charging error while authentication is in progress, recharging starts again from DP, and since authentication is not completed, the wireless device performs re-authentication again, and High Enter power mode.

- #3: Charging interrupted due to detection of foreign matter or other charging errors during recalibration: After authentication is completed, if foreign matter is detected or other charging errors occur during re-calibration for high-power, the wireless device restarts from the DP and performs authentication again. Do it again.

- #4. High power mode: When entering high-power mode and recharging due to foreign matter detection or an error, authentication is initialized and the wireless device performs authentication again.

Problem: Currently, authentication is a function that takes a lot of time. After the authentication function is performed, if charging is restarted due to a foreign object detection error during charging, a problem occurs where authentication must be re-performed even though the device has not been changed. This causes the problem that it takes a lot of time to enter high power mode, which increases the charging time.

The Certificate Chain Segment in the Certificate response message in Figure 31 is a very large byte, so it takes a long time to perform authentication. However, in the Challenge_Auth response message of FIG. 32, Certificate Chain Hash LSB, Signature r value, Signature s value, etc. have a small number of bits. Accordingly, the corresponding information can be used in the later-described embodiment proposed for fast authentication.

Authentication refers to the process of confirming whether the product is genuine and has received WPC certification. Regardless of Ptx and Prx, the entity performing authentication can be set as authentication initiator and responder.

In MPP (a standard containing magsafe made by Apple), there is no calibration process in Figure 35.

Hereinafter, in this specification, for devices that have undergone authentication and are being charged in high power mode, we seek to reduce the re-entry time into high power mode through the fast authentication procedure.

Example #1. High power mode re-entry through Fast Authentication in negotiation (Fast Authentication through PRx’s SRQ/auth)

Figure 36 shows an example of performing Fast Authentication through SRQ/auth of PRx.

Figure 36 shows an embodiment of performing Fast Authentication by adding a new SRQ packet of SRQ/auth.

Referring to the top of FIG. 36, in the negotiation phase, PRx requests SRQ/auth, and PTx responds with ACK/NAK/ND. At this time, ACK means approval for SRQ/Auth, NAK means rejection for SRQ/Auth, and ND means non-support for SRQ/Auth.

The bottom of Figure 36 shows the bit configuration of SRQ/auth. Value included in B1 of SRQ/auth includes at least one of Certificate chain hash, Signature r value, Signature s value, LSB (Least Significant Bit), and MSB (Most Significant Bit) information of the certificate chain.

For example, PRx transmits the Certificate chain hash LSB as the Value value to SRQ/Auth. The value transmits the Certificate chain hash LSB of the recently authenticated PTx. PRx does not have a certificate chain, so it transmits the value of the recently authenticated PTx.

PTx compares the Certificate chain hash LSB it holds, and if it is the same as the value sent by PRx, it transmits ACK. If it is different, it transmits NAK. If it does not support SRQ/auth, it transmits ND.

Figure 37 shows an example of re-entry into High power mode through Fast Authentication in Negotiation.

Referring to FIG. 37, after entering the first charge, the wireless device stops charging in High power mode, and after re-entering the charge, performs the Fast Authentication of Example #1 in Negotiation (SRQ/Auth - ACK), then skips the Authentication and immediately charges to High Power Mode. Enter power mode and perform high-speed charging.

When recharging, the wireless device compares the value of SRQ/auth with the recently authenticated authentication data before recharging.

That is, if PRx receives ACK for SRQ/Auth, it can skip Authentication and immediately enter High power mode. If PRx receives NACK for SRQ/Auth, it can proceed with Authentication and Re-calibration again and enter High power mode.

Example #2. High power mode re-entry through Fast Authentication in Negotiation (Fast Authentication through GRQ/Auth packet)

Figure 38 shows an example of performing Fast Authentication through GRQ/Auth packet.

Figure 38 shows an embodiment of performing Fast Authentication by adding a new Auth packet for GRQ.

Referring to the top of FIG. 38, in negotiation, PRx requests GRQ, and PTx requests Auth. Send packet.

The bottom of Figure 38 shows the bit configuration of the Auth packet. Value included in B0 to Bn of the Auth packet includes a combination of various information including Certificate chain hash LSB, Signature r value LSB, Signature s value LSB, Certificate chain hash, and certificate chain LSB.

For example, PTx is a data value included in the Auth packet information and transmits the information described above.

PRx compares the information received from PTx with the most recently authenticated information. In other words, PRx compares the information authenticated in the most recent authentication with the information in the Auth packet received from PTx through a GRQ request.

If the information is the same, PRx and PTx enter High power mode immediately after entering the PT phase and perform high-speed charging. If the information is different, PRx and PTx perform authentication again through the Authentication function and enter High power mode.

Figure 39 shows another example of re-entry into high power mode through fast authentication in negotiation.

Referring to FIG. 39, after entering the first charge, the wireless device stops charging in High power mode, and after re-entering the charge, performs the Fast Authentication of Example #2 in the Negotiation phase (GRQ - Auth), then skips Authentication and immediately turns on High power. Enter mode and perform high-speed charging.

When recharging, the wireless device compares the value of the GRQ/Auth packet with the recently authenticated authentication data before recharging.

That is, if the value of the Auth packet is the same as the most recently authenticated information before charging, PRx and PTx can skip authentication and immediately enter High power mode. If the value of the Auth packet is different from the most recently authenticated information before charging, PRx and PTx can perform authentication and re-calibration again and enter high power mode.

Example #3. High power mode re-entry through Fast Authentication in the power transfer phase (Fast Authentication through GRQ/Auth packet)

Figure 40 shows an example of performing Fast Authentication through GRQ/Auth packet.

Figure 40 shows an embodiment of performing Fast Authentication by adding a new Auth packet through GRQ in the power transfer phase.

Referring to the top of FIG. 40, in the power transfer phase, PRx requests GRQ, and PTx requests Auth. Send packet.

The bottom of Figure 40 shows the bit configuration of the Auth packet. Value included in B0 to Bn of the Auth packet includes a combination of various information including Certificate chain hash LSB, Signature r value LSB, Signature s value LSB, Certificate chain hash, and certificate chain LSB.

For example, PTx transmits the data value included in the Auth packet information, that is, the information described above.

PRx compares the information received from PTx with the most recently authenticated information. In other words, PRx compares the information authenticated in the most recent authentication with the information in the Auth packet received from PTx through a GRQ request.

If the information is the same, PRx and PTx immediately enter high power mode and perform high-speed charging. If the information is different, PRx and PTx perform authentication again through the Authentication function and enter High power mode.

Figure 41 shows an example of re-entering high power mode through Fast Authentication in the power transfer phase.

Referring to FIG. 41, after entering the first charge, the wireless device stops charging in High power mode, and after re-entering the charge, performs Fast Authentication of Example #3 in the power transfer phase (GRQ - Auth), then skips Authentication and immediately starts High Power Mode. Enter power mode and perform high-speed charging.

When recharging, the wireless device compares the value of the GRQ/Auth packet with the recently authenticated authentication data before recharging.

In other words, if the value of the Auth packet is the same as the most recently authenticated information before charging, PRx and PTx can skip authentication and immediately enter High power mode. If the value of the Auth packet is different from the most recently authenticated information before charging, PRx and PTx can perform authentication and re-calibration again and enter high power mode.

All of the above-described embodiments propose a method of recharging through Fast Authentication when charging is interrupted in high power mode (i.e., in the Power Transfer phase). Additionally, the above-described embodiment may include not only high power mode, but also cases where charging is stopped during re-calibration. That is, the above-described embodiment (although not shown) may also include a method of recharging through Fast Authentication when charging is interrupted during re-calibration.

Hereinafter, embodiments of the present specification will be described again from the viewpoint of various subjects.

The following drawings were prepared to explain a specific example of the present specification. Since the names of specific devices or specific signals/messages/fields described in the drawings are provided as examples, the technical features of this specification are not limited to the specific names used in the drawings below.

Figure 42 is a flowchart of a method of re-entering the fast power mode through fast authentication from the perspective of a wireless power transmitter, according to an embodiment of the present specification.

According to Figure 42, the wireless power transmitter receives a CFG (Configuration) packet from the wireless power receiver in the configuration phase (S4210).

The wireless power transmitter enters a negotiation phase with the wireless power receiver based on the CFG packet (S4220).

The wireless power transmitter performs authentication in the power transfer phase after the negotiation phase and enters the high power mode (S4230).

When wireless charging is interrupted in the high power mode, the wireless power transmitter may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entered negotiation phase, the wireless power transmitter may receive a General Request (GRQ) packet from the wireless power receiver. In the re-entered negotiation phase, the wireless power transmitter may transmit an Auth packet to the wireless power receiver in response to the GRQ packet.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power transmitter may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power transmitter may re-perform the authentication in the re-entry power transfer phase and enter the high-power mode again.

As another example, not only when wireless charging is interrupted in the high power mode, but also when wireless charging is interrupted during re-calibration, the high-speed power mode can be re-entered through quick authentication.

The wireless power transmitter may perform re-calibration after performing the authentication in the power transfer phase. The recalibration can be performed in the baseline power profile (BPP) and extended power profile (EPP). However, there is no calibration process in magnetic power profile (MPP).

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power transmitter may re-perform the re-calibration after re-performing the authentication in the re-entry power transfer phase.

If wireless charging is interrupted while performing the recalibration, the wireless power transmitter may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entered negotiation phase, the wireless power transmitter may receive the GRQ packet from the wireless power receiver. In the re-entered negotiation phase, the wireless power transmitter may transmit the Auth packet to the wireless power receiver in response to the GRQ packet.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power transmitter may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power transmitter may re-perform the authentication in the re-entry power transfer phase and enter the high-power mode again.

The Auth packet may include at least one information among Certificate chain hash LSB, Signature r value LSB, Signature s value LSB, Certificate chain hash, and certificate chain LSB. Since the above information all has a small number of bits, it may be suitable information for performing fast authentication in this embodiment.

The most recently authenticated information may be information stored in the wireless power receiver through the authentication immediately before the wireless charging is stopped.

As another example, it is possible to re-enter the fast power mode through fast authentication in the re-entrant power transfer phase rather than the re-entry negotiation phase.

When wireless charging is interrupted in the high power mode, the wireless power transmitter may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entrant power transfer phase, the wireless power transmitter may receive the GRQ packet from the wireless power receiver. In the re-entrant power transfer phase, the wireless power transmitter may transmit the Auth packet to the wireless power receiver in response to the GRQ packet.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power transmitter may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power transmitter may re-perform the authentication in the re-entry power transfer phase and enter the high-power mode again.

In other words, this embodiment provides a method of performing quick authentication through confirmation of previously authenticated information by exchanging simple information in the negotiation phase (or power transfer phase) when the authenticated wireless device enters recharging. suggest. As a result, it is possible to quickly authenticate the product and enter high-speed charging, and it is possible to authenticate the wireless device before entering the power transfer phase of wireless charging, which has the effect of enabling rapid entry into high-speed charging.

Figure 43 is a flowchart of a method of re-entering the fast power mode through fast authentication from the perspective of a wireless power receiver, according to an embodiment of the present specification.

According to Figure 43, the wireless power receiver transmits a CFG (Configuration) packet to the wireless power transmitter in the configuration phase (S4310).

The wireless power receiver enters a negotiation phase with the wireless power transmitter based on the CFG packet (S4320).

The wireless power receiver performs authentication in the power transfer phase after the negotiation phase and enters the high power mode (S4330).

When wireless charging is interrupted in the high power mode, the wireless power receiver may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entered negotiation phase, the wireless power receiver may transmit a General Request (GRQ) packet to the wireless power transmitter. In the re-entered negotiation phase, the wireless power receiver may receive an Auth packet in response to the GRQ packet from the wireless power transmitter.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power receiver may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power receiver may re-perform the authentication in the re-entry power transfer phase and enter the high-power mode again.

As another example, not only when wireless charging is interrupted in the high power mode, but also when wireless charging is interrupted during re-calibration, the high-speed power mode can be re-entered through quick authentication.

The wireless power receiver may perform re-calibration after performing the authentication in the power transfer phase. The recalibration can be performed in the baseline power profile (BPP) and extended power profile (EPP). However, there is no calibration process in magnetic power profile (MPP).

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power receiver may re-perform the re-calibration after re-performing the authentication in the re-entry power transfer phase.

If wireless charging is interrupted while performing the recalibration, the wireless power receiver may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entrant negotiation phase, the wireless power receiver may transmit the GRQ packet to the wireless power transmitter in the re-entry negotiation phase. In the re-entered negotiation phase, the wireless power receiver may receive the Auth packet in response to the GRQ packet from the wireless power transmitter.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power receiver may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power receiver may re-perform the authentication in the re-entry power transfer phase and enter the high-power mode again.

The Auth packet may include at least one information among Certificate chain hash LSB, Signature r value LSB, Signature s value LSB, Certificate chain hash, and certificate chain LSB. Since the above information all has a small number of bits, it may be suitable information for performing fast authentication in this embodiment.

The most recently authenticated information may be information stored in the wireless power receiver through the authentication immediately before the wireless charging is stopped.

As another example, it is possible to re-enter the fast power mode through fast authentication in the re-entrant power transfer phase rather than the re-entry negotiation phase.

When wireless charging is interrupted in the high power mode, the wireless power receiver may re-enter the configuration phase, the negotiation phase, and the power transfer phase.

In the re-entrant power transfer phase, the wireless power receiver may transmit the GRQ packet to the wireless power transmitter. In the re-entrant power transfer phase, the wireless power receiver may receive the Auth packet in response to the GRQ packet from the wireless power transmitter.

If the value included in the Auth packet is the same as the most recently authenticated information, the wireless power receiver may re-enter the high power mode without performing the authentication in the re-entry power transfer phase.

If the value included in the Auth packet is different from the most recently authenticated information, the wireless power receiver may re-perform the authentication in the re-entry power transfer phase and enter the high-power mode again.

In other words, this embodiment provides a method of performing quick authentication through confirmation of previously authenticated information by exchanging simple information in the negotiation phase (or power transfer phase) when the authenticated wireless device enters recharging. suggest. As a result, it is possible to quickly authenticate the product and enter high-speed charging, and it is possible to authenticate the wireless device before entering the power transfer phase of wireless charging, which has the effect of enabling rapid entry into high-speed charging.

The effects that can be achieved through specific examples of the present specification are not limited to the effects listed above. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of the present specification are not limited to those explicitly described in the present specification, and may include various effects that can be understood or derived from the technical features of the present specification.

The claims set forth herein may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Additionally, the technical features of the method claims of this specification and the technical features of the device claims may be combined to implement a device, and the technical features of the method claims of this specification and technical features of the device claims may be combined to implement a method.

Claims (16)

1. In a wireless power transmission system, a method for a wireless power transmitter to perform wireless charging,

   Receiving a Configuration (CFG) packet from the wireless power receiver in a configuration phase;

   Entering a negotiation phase with the wireless power receiver based on the CFG packet;

   Including performing authentication in the power transfer phase after the negotiation phase and entering the high power mode,

   If wireless charging is interrupted in the above high power mode,

   re-entering the configuration phase, the negotiation phase, and the power transfer phase;

   In the re-entered negotiation phase, receiving a General Request (GRQ) packet from the wireless power receiver;

   In the re-entered negotiation phase, transmitting an Auth packet to the wireless power receiver in response to the GRQ packet; and

   If the value included in the Auth packet is the same as the most recently authenticated information, the step of re-entering the high power mode without performing the authentication in the re-entered power transfer phase.

   method.
2. According to paragraph 1,

   If the value included in the Auth packet is different from the most recently authenticated information, re-performing the authentication in the re-entered power transfer phase and entering the high power mode again.

   method.
3. According to paragraph 1,

   Performing re-calibration after performing the authentication in the power transfer phase; and

   If the value included in the Auth packet is different from the most recently authenticated information, re-performing the re-calibration after re-performing the authentication in the re-entry power transfer phase.

   method.
4. According to paragraph 3,

   If wireless charging is interrupted while performing the above recalibration,

   re-entering the configuration phase, the negotiation phase, and the power transfer phase;

   In the re-entered negotiation phase, receiving the GRQ packet from the wireless power receiver;

   In the re-entered negotiation phase, transmitting the Auth packet to the wireless power receiver in response to the GRQ packet;

   If the value included in the Auth packet is the same as the most recently authenticated information, re-entering the high power mode without performing the authentication in the re-entered power transfer phase; and

   If the value included in the Auth packet is different from the most recently authenticated information, re-performing the authentication in the re-entered power transfer phase and entering the high power mode again.

   method.
5. According to paragraph 1,

   The Auth packet is characterized in that it contains at least one information among Certificate chain hash LSB, Signature r value LSB, Signature s value LSB, Certificate chain hash, and certificate chain LSB.

   method.
6. According to paragraph 1,

   The most recently authenticated information is information stored in the wireless power receiver through the authentication immediately before the wireless charging is stopped.

   method.
7. According to paragraph 1,

   If wireless charging is interrupted in the above high power mode,

   re-entering the configuration phase, the negotiation phase, and the power transfer phase;

   In the re-entrant power transfer phase, receiving the GRQ packet from the wireless power receiver;

   In the re-entrant power transfer phase, transmitting the Auth packet to the wireless power receiver in response to the GRQ packet;

   If the value included in the Auth packet is the same as the most recently authenticated information, re-entering the high power mode without performing the authentication in the re-entered power transfer phase; and

   If the value included in the Auth packet is different from the most recently authenticated information, re-performing the authentication in the re-entered power transfer phase and entering the high power mode again.

   method.
8. In a wireless power transmission system, the wireless power transmitter,

   Converters involved in transmitting or receiving wireless power; and

   Including a communication/controller related to controlling the transmission or reception of the wireless power,

   The wireless transmission transmitter:

   In a configuration phase, a Configuration (CFG) packet is received from the wireless power receiver;

   enter a negotiation phase with the wireless power receiver based on the CFG packet;

   After the negotiation phase, authentication is performed in the power transfer phase to enter the high power mode,

   If wireless charging is interrupted in the above high power mode,

   re-enter the configuration phase, the negotiation phase and the power transfer phase;

   In the re-entered negotiation phase, receive a General Request (GRQ) packet from the wireless power receiver;

   In the re-entered negotiation phase, transmitting an Auth packet to the wireless power receiver in response to the GRQ packet; and

   If the value included in the Auth packet is the same as the most recently authenticated information, the authentication is not performed in the re-entered power transfer phase and the device enters the high power mode again.

   Wireless power transmitter.
9. In a method for a wireless power receiver to perform wireless charging in a wireless power transmission system,

   Transmitting a CFG (Configuration) packet to a wireless power transmitter in a configuration phase;

   Entering a negotiation phase with the wireless power transmitter based on the CFG packet;

   Including performing authentication in the power transfer phase after the negotiation phase and entering the high power mode,

   If wireless charging is interrupted in the above high power mode,

   re-entering the configuration phase, the negotiation phase, and the power transfer phase;

   In the re-entered negotiation phase, transmitting a General Request (GRQ) packet to the wireless power transmitter;

   In the re-entered negotiation phase, receiving an Auth packet in response to the GRQ packet from the wireless power transmitter; and

   If the value included in the Auth packet is the same as the most recently authenticated information, the step of re-entering the high power mode without performing the authentication in the re-entered power transfer phase.

   method.
10. According to clause 9,

    If the value included in the Auth packet is different from the most recently authenticated information, re-performing the authentication in the re-entered power transfer phase and entering the high power mode again.

    method.
11. According to clause 9,

    Performing re-calibration after performing the authentication in the power transfer phase; and

    If the value included in the Auth packet is different from the most recently authenticated information, re-performing the re-calibration after re-performing the authentication in the re-entry power transfer phase.

    method.
12. According to clause 11,

    If wireless charging is interrupted while performing the above recalibration,

    re-entering the configuration phase, the negotiation phase, and the power transfer phase;

    In the re-entered negotiation phase, transmitting the GRQ packet to the wireless power transmitter;

    In the re-entered negotiation phase, receiving the Auth packet in response to the GRQ packet from the wireless power transmitter;

    If the value included in the Auth packet is the same as the most recently authenticated information, re-entering the high power mode without performing the authentication in the re-entered power transfer phase; and

    If the value included in the Auth packet is different from the most recently authenticated information, re-performing the authentication in the re-entered power transfer phase and entering the high power mode again.

    method.
13. According to clause 9,

    The Auth packet is characterized in that it contains at least one information among Certificate chain hash LSB, Signature r value LSB, Signature s value LSB, Certificate chain hash, and certificate chain LSB.

    method.
14. According to clause 9,

    The most recently authenticated information is information stored in the wireless power receiver through the authentication immediately before the wireless charging is stopped.

    method.
15. According to clause 9,

    If wireless charging is interrupted in the above high power mode,

    re-entering the configuration phase, the negotiation phase, and the power transfer phase;

    In the re-entrant power transfer phase, transmitting the GRQ packet to the wireless power transmitter;

    In the re-entrant power transfer phase, receiving the Auth packet in response to the GRQ packet from the wireless power transmitter;

    If the value included in the Auth packet is the same as the most recently authenticated information, re-entering the high power mode without performing the authentication in the re-entered power transfer phase; and

    If the value included in the Auth packet is different from the most recently authenticated information, re-performing the authentication in the re-entered power transfer phase and entering the high power mode again.

    method.
16. In a wireless power transmission system, a wireless power receiver,

    Converters involved in transmitting or receiving wireless power; and

    Including a communication/controller related to controlling the transmission or reception of the wireless power,

    The wireless power receiver:

    In the configuration phase, a CFG (Configuration) packet is transmitted to the wireless power transmitter;

    enter a negotiation phase with the wireless power transmitter based on the CFG packet;

    After the negotiation phase, authentication is performed in the power transfer phase to enter the high power mode,

    If wireless charging is interrupted in the above high power mode,

    re-enter the configuration phase, the negotiation phase and the power transfer phase;

    In the re-entry negotiation phase, transmitting a General Request (GRQ) packet to the wireless power transmitter;

    In the re-entered negotiation phase, receive an Auth packet in response to the GRQ packet from the wireless power transmitter; and

    If the value included in the Auth packet is the same as the most recently authenticated information, the authentication is not performed in the re-entered power transfer phase and the device enters the high power mode again.

    Wireless power receiver.

Images