Methods and apparatus related to time requirements for application messages in wireless power transfer systems

By establishing time requirements for authentication in wireless power systems, the solution addresses compatibility issues and communication delays, ensuring stable and safe charging across diverse power classes.

CN119096449APending Publication Date: 2024-12-06LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034644.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-20
Filing Date
2023-04-20
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing wireless power transmission systems face challenges in maintaining compatibility between wireless power transmitters and receivers of different power classes, leading to instability and potential damage due to overvoltage, and lack effective time requirements for authentication processes that can cause communication delays and loss.

Method used

Implementing time requirements for authentication processes, setting timeouts for response messages based on auxiliary data transport and communication error intervals to prevent indefinite delays and ensure stable power delivery, thereby preventing unauthenticated devices from disrupting high-speed charging.

Benefits of technology

This approach stabilizes power transmission by preventing communication instability and ensuring authentication completion within specified times, allowing for seamless compatibility and safe charging across different power classes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096449A_ABST
    Figure CN119096449A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method for transmitting a response message in a wireless power transmission system, the method being performed by a data flow responder, in which the data flow responder enters a power delivery phase related to transmitting or receiving wireless power, and in which the response message is transmitted to a data flow initiator in the power delivery phase. The response message is transmitted within the first timeout period. The value of the first timeout period is configured based on the ADT packet of one byte, the time interval associated with the DSR packet, and the communication error.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This specification relates to wireless power transfer. Background Art

[0002] Wireless power delivery (or transmission) technology corresponds to a technology that can wirelessly deliver (or transmit) power between a power source and an electronic device. For example, by simply loading the wireless device onto a wireless charging pad, the battery of a wireless device such as a smartphone or tablet PC can be recharged, which provides more outstanding mobility, convenience, and safety compared to a traditional wired charging environment using a wired charging connector. In addition to wirelessly charging wireless devices, wireless power delivery technology has attracted much attention as a substitute for traditional wired power delivery environments in various fields such as electric vehicles, Bluetooth headsets, 3D glasses, various wearable devices, household (or home) appliances, furniture, underground facilities, buildings, medical equipment, robots, leisure places, etc.

[0003] The wireless power transmission (or transfer) method is also called a contactless power transmission method, a contactless power transmission method, or a wireless charging method. A wireless power transmission system may be composed of a wireless power transmitter that supplies power by using the wireless power transmission method, and a wireless power receiver that receives the power supplied by the wireless power transmitter and supplies the received power to a receiver such as a battery cell.

[0004] Wireless power transmission technology includes various methods such as a method of transmitting power by using magnetic coupling, a method of transmitting power by using radio frequency (RF), a method of transmitting power by using microwaves, and a method of transmitting power by using ultrasound (or ultrasonic waves). The method based on magnetic coupling is divided into a magnetic induction method and a magnetic resonance method. The magnetic induction method corresponds to a method of transmitting power by using a current induced in a coil of a receiver due to a magnetic field, which is generated by a coil battery cell of a transmitter according to electromagnetic coupling between a transmitting coil and a receiving coil. The magnetic resonance method is similar to the magnetic induction method in that it uses a magnetic field. However, the magnetic resonance method is different from the magnetic induction method in that energy transmission is caused due to the concentration of magnetic fields on both the transmitting end and the receiving end caused by the resonance generated.

[0005] At the same time, this specification attempts to provide a method and apparatus regarding the time requirements for application messages. Summary of the invention

[0006] Technical Solution

[0007] According to one embodiment of the present disclosure, the data flow responder enters a power delivery phase for transmitting or receiving wireless power.

[0008] The data flow responder sends a response message to the data flow initiator in the power delivery phase.

[0009] The response message is sent within the first timeout period.

[0010] The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transport (ADT) packet, a data stream response (DSR) packet, and a communication error.

[0011] According to this specification, by proposing a time requirement for authentication, presenting the authentication completion time due to communication errors, thereby preventing the authentication function from being delayed indefinitely, and if it is not completed within a specific time, it is treated as an unauthenticated device or the corresponding authentication function is restarted, thereby preventing high-speed charging from being unable to be performed due to the unauthenticated authentication device. In addition, according to this specification, it is also possible to have the effect of solving the communication instability and communication loss of the authentication message.

[0012] The effects that can be obtained through the specific examples of this specification are not limited to the effects listed above. For example, a person of ordinary skill in the art can understand or derive various technical effects from this specification. Therefore, the specific effects of this specification are not limited to those explicitly described in this specification, and may include various effects that can be understood or derived from the technical features of this specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a block diagram of a wireless power system (10) according to an exemplary embodiment of the present disclosure.

[0014] Figure 2 is a block diagram of a wireless power system (10) according to another exemplary embodiment of the present disclosure.

[0015] Figure 3 Exemplary embodiments of various electronic devices employing wireless power transfer systems are shown.

[0016] Figure 4 is a block diagram of a wireless power transfer system according to one embodiment.

[0017] Figure 5 is a diagram illustrating an example of a Bluetooth communication architecture to which an embodiment according to the present disclosure can be applied.

[0018] Figure 6 is a block diagram illustrating a wireless power transfer system using BLE communication according to an example.

[0019] Figure 7 is a block diagram illustrating a wireless power transfer system using BLE communication according to another example.

[0020] Figure 8 It is a state transition diagram used to explain the wireless power transfer process.

[0021] Fig. 9 An example of a protocol for a ping phase 810 is schematically shown.

[0022] Fig.10 An example of a protocol for the configuration phase 820 is schematically shown.

[0023] Fig.11 is a diagram illustrating a message field of a configuration packet (CFG) of a wireless power receiving device according to an embodiment.

[0024] Fig.12 is a flow chart schematically illustrating a protocol of a negotiation phase or a re-negotiation phase according to an embodiment.

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

[0026] Fig.14 A flow chart schematically illustrates the data flow for the power delivery phase 840 in the baseline protocol.

[0027] Fig.15 A flow chart schematically shows the data flow for the power delivery phase 840 in the extended protocol.

[0028] Fig.16 An application-level data flow between the wireless power transmitter 100 and the wireless power receiver 200 according to an example is illustrated.

[0029] Fig.17 A power control method according to one embodiment is shown.

[0030] Fig.18 The structure of the MPP ID packet is schematically shown.

[0031] Fig.19 An example of XID grouping in MPP is schematically shown.

[0032] Fig. 20 The protocol in MPP restricted mode is schematically shown.

[0033] Fig.21 and Fig. 22 The protocol in MPP full mode is schematically shown.

[0034] Fig.23 An example of an authentication message header is illustrated.

[0035] Fig.24An example of an Authentication Protocol Version field is illustrated.

[0036] Fig.25 An example of a message type field for an authentication request is illustrated.

[0037] Fig.26 An example of a message type field for an authentication response is illustrated.

[0038] Fig. 27 An example of GET_DIGESTS is illustrated.

[0039] Fig.28 An example of GET_CERTIFICATE is illustrated.

[0040] Fig.29 An example of a CHALLENGE is illustrated.

[0041] Fig.30 An example of DIGESTS is illustrated.

[0042] Fig.31 An example of CERTIFICATE is illustrated.

[0043] Fig.32 An example of CHALLENGE_AUTH is shown.

[0044] Fig.33 An example of ERROR is shown.

[0045] Fig.34 is a flow chart of a method for delivering wireless power according to one embodiment of the present disclosure.

[0046] Fig.35 An example of timing requirements for a wireless power transmitter is schematically illustrated.

[0047] Fig.36 An example of setting t_Get-DigestTimeout for transport Get-digest is shown.

[0048] Fig.37 The figure shows an example of resending Get-digest when t_Get-DigestTimeout times out.

[0049] Fig.38 Figure shows an example of resending Get-digest and Digests messages when t_DigestsTimeout expires.

[0050] Fig.39An example of sending and receiving Get-digest and Digests messages by setting t_Get-digest, t_DigestsReady, and t_DigestsTimeout according to the present embodiment is illustrated.

[0051] Fig.40 This diagram shows an example of setting t_Get-certificateTimeout for transmitting Get-certificate.

[0052] Fig.41 The diagram shows an example of resending Get-Certificate when t_Get-CertificateTimeout times out.

[0053] Fig.42 An example of resending the Get-Certificate and Certificates messages when t_Certificatetimeout times out is shown.

[0054] Fig.43 An example of sending and receiving Get-Certificate and Certificates messages by setting t_Get-CertificateTimeout, t_CertificatesReady, and t_CertificatesTimeout according to the present embodiment is shown.

[0055] Fig.44 An example of setting t_challengeTimeout for transmitting a challenge is shown.

[0056] Fig.45 An example of resending the challenge when t_challengeTimeout times out is shown.

[0057] Fig.46 An example of resending Challenge and Challenge_Auth messages when t_CertificateAuthTimeout times out is shown.

[0058] Fig.47 An example of sending and receiving Challenge and Challenge_Auth messages by setting t_ChallengeTimeout, t_ChallengeAuthReady, and t_ChallengeAuthTimeout according to the present embodiment is illustrated.

[0059] Fig.48is a flowchart of a method for receiving a response message from the perspective of a data flow initiator according to an embodiment of the present specification.

[0060] Fig.49 is a flowchart of a method for sending a response message from the perspective of a data flow responder according to an embodiment of the present specification. DETAILED DESCRIPTION

[0061] In this specification, "A or B" may refer to "only A", "only B", or "A and B". In other words, "A or B" in this specification may be interpreted as "A and / or B". For example, in this specification, "A, B, or C" may refer to any combination of "only A", "only B", "only C", or "A, B, and C".

[0062] A slash ( / ) or a comma used in this specification may refer to "and / or". For example, "A / B" may refer to "A and / or B". Thus, "A / B" may refer to "only A", "only B", or "both A and B". For example, "A, B, C" may refer to "A, B, or C".

[0063] In the present specification, "at least one of A and B" may refer to "only A", "only B", or "both A and B". In addition, in the present specification, the expression "at least one of A or B" or "at least one of A and / or B" may be interpreted as the same as "at least one of A and B".

[0064] In addition, in the present specification, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "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" may mean "at least one of A, B, and C".

[0065] In addition, brackets used in this specification may refer to "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". In addition, even when "control information (ie, PDCCH)" is indicated, "PDCCH" may be proposed as an example of "control information".

[0066] In this specification, the technical features described separately in one figure may be implemented separately or simultaneously. The term "wireless power" used in this specification hereinafter will be used to refer to any form of energy related to electric fields, magnetic fields and electromagnetic fields, which is transmitted (or sent) from a wireless power transmitter to a wireless power receiver without using any physical electromagnetic conductors. Wireless power may also be referred to as a wireless power signal, and this may refer to an oscillating magnetic flux surrounded by a primary coil and a secondary coil. For example, power conversion for wireless charging of devices including mobile phones, cordless phones, iPods, MP3 players, headphones, etc. within a system will be described in this specification. Generally, the basic principles of wireless power transmission technology include all of a method of transmitting power by using magnetic coupling, a method of transmitting power by using radio frequency (RF), a method of transmitting power by using microwaves, and a method of transmitting power by using ultrasound (or ultrasonic waves).

[0067] Figure 1 is a block diagram of a wireless power system (10) according to an exemplary embodiment of the present disclosure.

[0068] refer to Figure 1 , a wireless power system (10) includes a wireless power transmitter (100) and a wireless power receiver (200).

[0069] The wireless power transmitter (100) is supplied with power by an external power source (S) and generates a magnetic field. The wireless power receiver (200) generates a current by using the generated magnetic field, thereby being able to wirelessly receive power.

[0070] In addition, in the wireless power system (10), the wireless power transmitter (100) and the wireless power receiver (200) can transceive (send and / or receive) various information required for wireless power transfer. Here, the communication between the wireless power transmitter (100) and the wireless power receiver (200) can be performed (or established) according to any one of in-band communication using a magnetic field for wireless power transfer (or transmission) and out-band communication using a separate communication carrier. Out-band communication may also be referred to as out-of-band communication. In the following, out-of-band communication will be mainly described. Examples of out-of-band communication may include NFC, Bluetooth, Bluetooth Low Energy (BLE), etc.

[0071] Here, the wireless power transmitter (100) may be provided as a fixed type or a mobile (or portable) type. Examples of the fixed transmitter type may include an embedded type embedded in an indoor ceiling or wall surface or embedded in furniture such as a table, an implanted type installed in an outdoor parking lot, a bus station, a subway station, etc., or installed in a transportation vehicle such as a vehicle or a train. The mobile (or portable) type wireless power transmitter (100) may be implemented as part of another device such as a housing of a mobile device or a laptop computer having a portable size or weight.

[0072] In addition, the wireless power receiver (200) should be interpreted as a comprehensive concept including various home appliances and devices that operate by being supplied with power wirelessly rather than various electronic devices equipped with batteries and cables. Typical examples of the wireless power receiver (200) may include portable terminals, cellular phones, smart phones, personal digital assistants (PDAs), portable media players (PDPs), Wibro terminals, tablet PCs, tablet phones, laptop computers, digital cameras, navigation terminals, televisions, electric vehicles (EVs), etc.

[0073] Figure 2 is a block diagram of a wireless power system (10) according to another exemplary embodiment of the present disclosure.

[0074] refer to Figure 2 In the wireless power system (10), there may be one wireless power receiver (200) or a plurality of wireless power receivers. Figure 1 , the wireless power transmitter (100) and the wireless power receiver (200) perform power transmission and reception with each other in a one-to-one correspondence (or relationship), but as Figure 2 As shown in , one wireless power transmitter (100) is also capable of simultaneously delivering power to a plurality of wireless power receivers (200-1, 200-2, ..., 200-M). Most specifically, in the case of performing wireless power delivery (or transmission) by using a magnetic resonance method, one wireless power transmitter (100) can deliver power to a plurality of wireless power receivers (200-1, 200-2, ..., 200-M) by using a synchronous transmission (or delivery) method or a time division transmission (or delivery) method.

[0075] In addition, despite Figure 1The wireless power transmitter (100) is shown to directly transmit (or send) power to the wireless power receiver (200), but the wireless power system (10) may also be equipped with a separate wireless power transceiver such as a repeater or a transponder for increasing the wireless power transmission distance between the wireless power transmitter (100) and the wireless power receiver (200). In this case, power is transferred from the wireless power transmitter (100) to the wireless power transceiver, and then the wireless power transceiver can transmit the received power to the wireless power receiver (200).

[0076] Hereinafter, the terms wireless power receiver, power receiver, and receiver mentioned in this specification will refer to the wireless power receiver (200). In addition, the terms wireless power transmitter, power transmitter, and transmitter mentioned in this specification will refer to the wireless power transmitter (100).

[0077] Figure 3 Exemplary embodiments of a variety of electronic devices employing wireless power transfer systems are shown.

[0078] like Figure 3 As shown in , electronic devices included in the wireless power transmission system are classified according to the amount of transmission power and the amount of reception power. Figure 3 , wearable devices such as smart watches, smart glasses, head-mounted displays (HMDs), smart rings, etc., and mobile electronic devices (or portable electronic devices) such as headphones, remote controllers, smart phones, PDAs, tablet PCs, etc. can adopt low-power (about 5 W or less or about 20 W or less) wireless charging methods.

[0079] Small / medium-sized electronic devices such as laptop computers, robot vacuum cleaners, TV receivers, audio equipment, vacuum cleaners, monitors, etc. can adopt medium-power (about 50W or less or about 200W or less) wireless charging methods. Kitchen appliances such as blenders, microwave ovens, rice cookers, etc. and personal transportation devices (or other electronic devices or transportation tools) such as electric wheelchairs, electric scooters, electric bicycles, electric cars, etc. can adopt high-power (about 2kW or less or about 22kW or less) wireless charging methods.

[0080] Above (or in Figure 1 The electronic device or transportation tool (shown in FIG) may each include a wireless power receiver described in detail below. Therefore, the electronic device or transportation tool may be charged (or recharged) by wirelessly receiving power from the wireless power transmitter.

[0081] Hereinafter, although the present disclosure will be described based on a mobile device adopting a wireless power charging method, this is merely exemplary. And, therefore, it should be understood that the wireless charging method according to the present disclosure can be applied to various electronic devices.

[0082] Standards for wireless power delivery (or transmission) include the Wireless Power Consortium (WPC), the Air Fuel Alliance (AFA), and the Power Matters Alliance (PMA).

[0083] The WPC standard defines a base power profile (BPP) and an extended power profile (EPP). The BPP is related to wireless power transmitters and wireless power receivers that support 5W power delivery, and the EPP is related to wireless power transmitters and wireless power receivers that support delivery of a power range greater than 5W and less than 30W.

[0084] Various wireless power transmitters and wireless power receivers, each using different power levels, may be covered by each standard and may be classified in different power classes or categories.

[0085] For example, WPC may classify (or categorize) wireless power transmitters and wireless power receivers into PC-1, PC0, PC1, and PC2, and WPC may provide standard documents (or specifications) for each power level (PC). The PC-1 standard relates to wireless power transmitters and receivers that provide a guaranteed power of less than 5W. Applications of PC-1 include wearable devices such as smart watches.

[0086] The PC0 standard relates to wireless power transmitters and receivers that provide a guaranteed power of 5W. The PC0 standard includes an EPP with a guaranteed power range extended to 30W. Although in-band (IB) communication corresponds to the mandatory communication protocol of PC0, out-of-band (OB) communication, which is used as an optional backup channel, can also be used for PC0. A wireless power receiver can be identified by setting an OB flag indicating whether OB is supported within a configuration packet. A wireless power transmitter that supports OB can enter the OB switching phase by sending a bit pattern for OB switching as a response to a configuration packet. The response to the configuration packet can correspond to NAK, ND, or a newly defined 8-bit pattern. Applications of PC0 include smartphones.

[0087] The PC1 standard relates to wireless power transmitters and receivers that provide guaranteed power ranging from 30W to 150W. OB corresponds to a mandatory communication channel for PC1, and IB is used for initialization and link establishment with OB. The wireless power transmitter can enter the OB switching phase by sending a bit pattern for OB switching as a response to a configuration packet. Applications of PC1 include laptop computers or power tools.

[0088] The PC2 standard relates to wireless power transmitters and receivers that provide guaranteed power ranging from 200W to 2kW, and its applications include kitchen appliances.

[0089] As described above, PCs can be distinguished according to corresponding power levels. And, information about whether compatibility between the same PCs is supported can be optional or mandatory. Here, the compatibility between the same PCs indicates that power transfer / reception can be performed between the same PCs. For example, in a case where a wireless power transmitter corresponding to PC x is able to charge a wireless power receiver with the same PC x, it can be understood that compatibility is maintained between the same PCs. Similarly, compatibility between different PCs can also be supported. Here, the compatibility between different PCs indicates that power transfer / reception can also be performed between different PCs. For example, in a case where a wireless power transmitter corresponding to PC x is able to charge a wireless power receiver with PC y, it can be understood that compatibility is maintained between different PCs.

[0090] Supporting compatibility between PCs corresponds to an extremely important issue in terms of user experience and infrastructure establishment. However, here, there are various problems to be described below when maintaining compatibility between PCs.

[0091] In the case of compatibility between the same PCs, for example, in the case of a wireless power receiver using a laptop charging method in which stable charging is possible only when power is continuously delivered, even if its corresponding wireless power transmitter has the same PC, the corresponding wireless power receiver may have difficulty in stably receiving power from a wireless power transmitter of a power tool method in which power is delivered discontinuously. In addition, in the case of compatibility between different PCs, for example, in the case where a wireless power transmitter with a minimum guaranteed power of 200W delivers power to a wireless power receiver with a maximum guaranteed power of 5W, the corresponding wireless power receiver may be damaged due to overvoltage. As a result, it may be inappropriate (or difficult) to use PS as an index / reference standard to represent / indicate compatibility.

[0092] The wireless power transmitter and receiver can provide a very convenient user experience and interface (UX / UI). That is, a smart wireless charging service can be provided, and the smart wireless charging service can be implemented based on the UX / UI of a smartphone including a wireless power transmitter. For these applications, the interface between the processor of the smartphone and the wireless charging receiver allows "drop and play" two-way communication between the wireless power transmitter and the wireless power receiver.

[0093] As an example, a user is able to experience the smart wireless charging service in a hotel. When the user enters the 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 the 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 the wireless charger, detects the reception of wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone enters a state in which it requests the user to agree to the (optional) additional function. To this end, the smartphone is able to display a message with or without an alarm sound on the screen. An example of a message may include a phrase such as "Welcome to ### Hotel. Select "Yes" to activate the smart charging function: Yes | No, thank you." The smartphone receives an input of the user selecting "Yes" or "No, thank you", and executes the next process selected by the user. If "Yes" is selected, the smartphone sends information to the wireless charger. And the smartphone and the wireless charger jointly perform the smart charging function.

[0094] Smart wireless charging services may also include receiving automatically populated WiFi credentials. For example, the wireless charger sends the WiFi credentials to the smartphone, and the smartphone runs an appropriate app and automatically enters the WiFi credentials received from the wireless charger.

[0095] Smart wireless charging services can also include running a hotel application that provides hotel promotions, remote check-in / check-out, and access to contact information.

[0096] As another example, a user is able to experience the smart wireless charging service in a car. When the user enters the vehicle and places the smartphone on the wireless charger, the wireless charger transmits wireless power to the smartphone, and the smartphone receives the wireless power. During 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 the wireless charger, detects the reception of wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone enters a state requesting the user to confirm his or her identity.

[0097] In this state, the smartphone automatically connects to the car via WiFi and / or Bluetooth. The smartphone is able to display a message on the screen with or without an alarm sound. Examples of messages may include phrases such as "Welcome to your car. Select "Yes" to synchronize the device with the in-car controls: Yes | No, thanks." The smartphone receives input from the user selecting "Yes" or "No, thanks" and executes the next process selected by the user. If "Yes" is selected, the smartphone sends the information to the wireless charger. And by running the in-car application / display software, the smartphone and the wireless charger are able to jointly perform in-car smart control functions. Users are able to enjoy the music they want and view regular map locations. The in-car application / display software may include the ability to provide synchronized access to pedestrians.

[0098] As another example, a user is able to experience smart wireless charging at home. When the user enters the room and places the smartphone on the wireless charger in the room, the wireless charger sends wireless power to the smartphone, and the smartphone receives the wireless power. In the process, the wireless charger sends information about the smart wireless charging service to the smartphone. When the smartphone detects that it is placed on the wireless charger, detects the reception of wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone enters a state requesting the user to agree (opt in) to the additional function. To this end, the smartphone is able to display a message with or without an alarm sound on the screen. Examples of messages may include phrases such as "Hi xxx, do you want to activate night mode and protect the building? : Yes | No, thank you". The smartphone receives input from the user selecting "Yes" or "No, thank you", and executes the next process selected by the user. If "Yes" is selected, the smartphone sends information to the wireless charger. The smartphone and the wireless charger are at least able to recognize the user mode and encourage the user to lock the doors and windows, turn off the lights, or set an alarm.

[0099] Hereinafter, the "profile" will be redefined based on an index / reference standard representing / indicating compatibility. More specifically, it can be understood that by maintaining compatibility between a wireless power transmitter and a receiver having the same "profile", stable power transmission / reception can be performed, and power transmission / reception cannot be performed between a wireless power transmitter and a receiver having different "profiles". The "profile" can be defined according to whether compatibility is possible and / or an application that is not related to (or independent of) a power level.

[0100] For example, profiles may be divided into 3 different categories such as i) Mobile, ii) Power Tools, and iii) Kitchen.

[0101] For another example, profiles may be categorized into 4 different categories such as i) mobile, ii) power tools, iii) kitchen, and iv) wearable.

[0102] In the case of a "mobile" profile, the PC may be limited to PC0 and / or PC1, the communication protocol / method may be limited to IB and OB communications, and the operating frequency may be limited to 87 to 205 kHz, while smartphones, laptops, etc. may exist as exemplary applications.

[0103] In the case of the "power tool" profile, the PC may be defined as PC1, the communication protocol / method may be defined as IB communication, and the operating frequency may be defined as 87 to 145 kHz, and power tools and the like may exist as exemplary applications.

[0104] In the case of the "kitchen" profile, the PC may be defined as PC2, the communication protocol / method may be defined as NFC-based communication, and the operating frequency may be defined as less than 100 kHz, while kitchen / home appliances, etc. may exist as exemplary applications.

[0105] In the case of the power tool and kitchen profile, NFC communication can be used between the wireless power transmitter and the wireless power receiver. The wireless power transmitter and the wireless power receiver can mutually confirm that they are NFC devices by exchanging WPC NFC Data Exchange Profile Format (NDEF).

[0106] Figure 4 is a block diagram of a wireless power transfer system according to one embodiment.

[0107] refer to Figure 4 , a wireless power transmission system (10) includes a mobile device (450) for wirelessly receiving power and a base station (400) for wirelessly transmitting power.

[0108] As a device for providing inductive power or resonant power, a base station (400) may include at least one of a wireless power transmitter (100) and a system unit (405). The wireless power transmitter (100) may transmit inductive power or resonant power and may control transmission. The wireless power transmitter (100) may include a power conversion unit (110) that converts electrical energy into a power signal by generating a magnetic field through a primary coil (or multiple primary coils) and a communication and control unit (120), wherein the power conversion unit (110) generates a magnetic field through a primary coil (or multiple primary coils) and converts electrical energy into a power signal, and the communication and control unit (120) controls communication and power transmission with a wireless power receiver (200) so as to transmit power at a suitable (or appropriate) level. The system unit (405) may perform input power supply, control of multiple wireless power transmitters, and other operation controls of the base station (400) such as user interface control.

[0109] The primary coil may generate an electromagnetic field by using AC power (or voltage or current). The primary coil is provided with AC power (or voltage or current) of a specific frequency being output from the power conversion unit (110). And, therefore, the primary coil may generate a magnetic field of a specific frequency. The magnetic field may be generated in a non-radial shape or a radial shape. And, the wireless power receiver (200) receives the generated magnetic field and then generates current. In other words, the primary coil transmits power wirelessly.

[0110] In the magnetic induction method, the primary coil and the secondary coil can have any suitable shape. For example, the primary coil and the secondary coil can correspond to a copper wire wound on a high magnetic permeability structure such as ferrite or amorphous metal. The primary coil can also be called a transmitting coil, a primary core, a primary winding, a primary loop antenna, etc. In addition, the secondary coil can also be called a receiving coil, a secondary core, a secondary winding, a secondary loop antenna, a pick-up antenna, etc.

[0111] In the case of using a magnetic resonance method, the primary coil and the secondary coil may each be provided in the form of a primary resonant antenna and a secondary resonant antenna. The resonant antenna may have a resonant structure including a coil and a capacitor. At this time, the resonant frequency of the resonant antenna may be determined by the inductance of the coil and the capacitance of the capacitor. Here, the coil may be formed to have a ring shape. And, a core may be placed inside the ring. The core may include a physical core such as a ferrite core or an air core.

[0112] Energy transmission (or delivery) between the primary resonant antenna and the secondary resonant antenna can be performed by a resonance phenomenon occurring in a magnetic field. When a near field corresponding to a resonant frequency appears in the resonant antenna, and when another resonant antenna exists near the corresponding resonant antenna, the resonance phenomenon refers to efficient energy delivery occurring between two resonant antennas coupled to each other. When a magnetic field corresponding to the resonant frequency is generated between the primary resonant antenna and the secondary resonant antenna, the primary resonant antenna and the secondary resonant antenna resonate with each other. And, therefore, under normal circumstances, the magnetic field is concentrated toward the secondary resonant antenna with higher efficiency than the case where the magnetic field generated by the primary antenna is radiated to an empty space. And, therefore, energy can be delivered 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. However, in this case, the frequency of the magnetic field is not required to be the resonant frequency. However, in the magnetic induction method, the loops constituting the primary coil and the secondary coil are required to match each other, and the distance between the loops should be very close.

[0113] Although not shown in the figure, the wireless power transmitter (100) may further include a communication antenna. The communication antenna may send and / or receive communication signals by using a communication carrier other than magnetic field communication. For example, the communication antenna may send and / or receive communication signals corresponding to Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, NFC, etc.

[0114] The communication and control unit (120) may transmit information to the wireless power receiver (200) and / or receive information from the wireless power receiver (200). The communication and control unit (120) may include at least one of an IB communication module and an OB communication module.

[0115] The IB communication module can send and / or receive information by using electromagnetic waves, which use a specific frequency as its center frequency. For example, the communication and control unit (120) can perform in-band (IB) communication by sending communication information about the working frequency of wireless power transmission via a primary coil or receiving communication information about the working frequency via a primary coil. At this time, the communication and control unit (120) can load information into the electromagnetic wave or interpret the information carried by the electromagnetic wave by using a modulation scheme such as binary phase shift keying (BPSK), frequency shift keying (FSK) or amplitude shift keying (ASK) or a coding scheme such as Manchester coding or non-return to zero level (NZR-L) coding. By using the above-mentioned IB communication, the communication and control unit (120) can send and / or receive information at a data transmission rate of several kbps over a distance of several meters.

[0116] The OB communication module may also perform out-of-band communication via a communication antenna. For example, the communication and control unit (120) may be provided as a near field communication module. Examples of the near field communication module may include communication modules such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, NFC, etc.

[0117] The communication and control unit (120) can control the overall operation of the wireless power transmitter (100). The communication and control unit (120) can perform calculation and processing of various information, and can also control each configuration element of the wireless power transmitter (100).

[0118] The communication and control unit (120) may be implemented in a computer or similar device as hardware, software, or a combination thereof. When implemented in the form of hardware, the communication and control unit (120) may be configured as an electronic circuit that performs a control function by processing an electrical signal. And, when implemented in the form of software, the communication and control unit (120) may be configured as a program that operates the communication and control unit (120).

[0119] By controlling the operating point, the communication and control unit (120) can control the transmitted power. The operating point being controlled can correspond to a combination of frequency (or phase), duty cycle, duty cycle and voltage amplitude. The communication and control unit (120) can control the transmitted power by adjusting any one of the frequency (or phase), duty cycle, duty cycle and voltage amplitude. In addition, the wireless power transmitter (100) can provide a consistent level of power, and the wireless power receiver (200) can control the level of received power by controlling the resonant frequency.

[0120] Meanwhile, for example, in the WPC system, the wireless power transmitter 100 can be classified according to the power transmission amount. At this time, the wireless power transmitter 100 supporting the wireless power transmission amount up to 5W (i.e., the wireless power transmitter 100 supporting the BPP protocol) can be classified into, for example, type A wireless power transmitter 100 and type B wireless power transmitter 100, and the wireless power transmitter 100 supporting the wireless power transmission amount up to 15W (i.e., the wireless power transmitter 100 supporting the EPP protocol) can be classified into, for example, type MP-A (MP-A) wireless power transmitter 100 and type MP-B (type MP-B) wireless power transmitter 100.

[0121] - Type A and Type MP A wireless power transmitters (100)

[0122] The type A and type MP A wireless power transmitter 100 may have one or more primary coils. The type A and type MP A wireless power transmitter 100 activates a single primary coil at a time, and thus can use a single primary cell matched with the activated primary coil.

[0123] - Type B and Type MP B Wireless Power Transmitters (100)

[0124] Type B and Type MP B power transmitters may have an array of primary coils. And Type B and Type MP B power transmitters are capable of enabling free positioning. To this end, Type B and Type MP B power transmitters are capable of activating one or more primary coils in the array to achieve primary cells at different locations on the interface surface.

[0125] The mobile device (450) includes a wireless power receiver (200) that receives wireless power through a secondary coil and a load (455) that receives and stores the power received by the wireless power receiver (200) and supplies the received power to the device.

[0126] The wireless power receiver (200) may include a power pickup unit (210) and a communication and control unit (220). The power pickup unit (210) may receive wireless power through a secondary coil and may convert the received wireless power into electrical energy. The power pickup unit (210) rectifies an alternating current (AC) signal received through the secondary coil and converts the rectified signal into a direct current (DC) signal. The communication and control unit (220) may control the transmission and reception of wireless power (transmission and reception of power).

[0127] The secondary coil can receive wireless power being transmitted from the wireless power transmitter (100). The secondary coil can receive power by using the magnetic field generated in the primary coil. Here, in the case where the specific frequency corresponds to the resonant frequency, magnetic resonance may occur between the primary coil and the secondary coil, thereby enabling power to be transmitted with greater efficiency.

[0128] At the same time, despite its Figure 4 Although not shown, the communication and control unit (220) may further include a communication antenna. In addition to magnetic field communication, the communication antenna may send and / or receive communication signals by using a communication carrier. For example, the communication antenna may send and / or receive communication signals corresponding to Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, NFC, etc.

[0129] The communication and control unit (220) may transmit information to the wireless power transmitter (100) and / or receive information from the wireless power transmitter (100). The communication and control unit (220) may include at least one of an IB communication module and an OB communication module.

[0130] The IB communication module can send and / or receive information by using electromagnetic waves, which use a specific frequency as its center frequency. For example, the communication and control unit (220) can perform IB communication by loading information into electromagnetic waves and by sending information via a secondary coil or by receiving electromagnetic waves carrying information via a secondary coil. At this time, the communication and control unit (220) can load information into electromagnetic waves or interpret the information carried by electromagnetic waves by using a modulation scheme such as binary phase shift keying (BPSK), frequency shift keying (FSK) or amplitude shift keying (ASK) or a coding scheme such as Manchester coding or non-return-to-zero level (NZR-L) coding. By using the above-mentioned IB communication, the communication and control unit (220) can send and / or receive information at a data transmission rate of several kbps over a distance of several meters.

[0131] The OB communication module may also perform out-of-band communication through a communication antenna. For example, the communication and control unit (220) may be provided as a near field communication module.

[0132] Examples of the near field communication module may include communication modules such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, NFC, and the like.

[0133] The communication and control unit (220) can control the overall operation of the wireless power receiver (200). The communication and control unit (220) can perform calculation and processing of various information, and can also control each configuration element of the wireless power receiver (200).

[0134] The communication and control unit (220) may be implemented in a computer or similar device as hardware, software, or a combination thereof. When implemented in the form of hardware, the communication and control unit (220) may be configured as an electronic circuit that performs a control function by processing an electrical signal. And, when implemented in the form of software, the communication and control unit (220) may be configured as a program that operates the communication and control unit (220).

[0135] When the communication / control circuit 120 and the communication / control circuit 220 are Bluetooth or Bluetooth LE as an OB communication module or a short-range communication module, as in Figure 5 As shown in , the communication / control circuit 120 and the communication / control circuit 220 can each be implemented and operated using a communication architecture.

[0136] Figure 5 is a diagram illustrating an example of a Bluetooth communication architecture to which an embodiment according to the present disclosure can be applied.

[0137] refer to Figure 5 , Figure 5 (a) shows an example of a protocol stack supporting Bluetooth Basic Rate (BR) / Enhanced Data Rate (EDR) of GATT, and (b) shows an example of a Bluetooth Low Energy (BLE) protocol stack.

[0138] Specifically, as in Figure 5 As shown in (a) of FIG. 8 , the Bluetooth BR / EDR protocol stack may include an upper control stack 460 and a lower host stack 470 based on a host controller interface (HCI) 18 .

[0139] The host stack (or host module) 470 refers to hardware for sending or receiving Bluetooth packets to or from the wireless transmission / reception module, which receives 2.4GHz Bluetooth signals, and the controller stack 460 is connected to the Bluetooth module to control the Bluetooth module and perform operations.

[0140] The host stack 470 may include a BR / EDR PHY layer 12 , a BR / EDR baseband layer 14 , and a link management layer 16 .

[0141] The BR / EDR PHY layer 12 is a layer that transmits and receives a 2.4 GHz radio signal, and in the case of using Gaussian frequency shift keying (GFSK) modulation, the BR / EDR PHY layer 12 may transmit data by hopping 79 RF channels.

[0142] The BR / EDR baseband layer 14 is used to transmit a digital signal, selects a channel sequence for hopping 1400 times per second, and transmits a time slot having a length of 625 us for each channel.

[0143] The link management layer 16 controls the overall operation (link setup, control, security) of the Bluetooth connection by utilizing the Link Management Protocol (LMP).

[0144] The link management layer 16 may perform the following functions.

[0145] -Perform ACL / SCO logical transport, logical link setup and control.

[0146] - Detach: It terminates the connection and informs the counterpart device about the reason for the termination.

[0147] -Perform power control and role switching.

[0148] -Perform security (authentication, pairing, encryption) functions.

[0149] The host controller interface layer 18 provides an interface between the host module and the controller module so that the host provides commands and data to the controller, and the controller provides events and data to the host.

[0150] The host stack (or host module, 470 ) includes a Logical Link Control and Adaptation Protocol (L2CAP) 21 , an Attribute Protocol 22 , a Generic Attribute Profile (GATT) 23 , a Generic Access Profile (GAP) 24 , and a BR / EDR Profile 25 .

[0151] The Logical Link Control and Adaptation Protocol (L2CAP) 21 may provide a bidirectional channel for sending data to a specific protocol or profile.

[0152] L2CAP 21 can multiplex various protocols, profiles, etc. provided from the upper layer Bluetooth.

[0153] L2CAP for Bluetooth BR / EDR uses dynamic channels, supports protocol service multiplexers, retransmission, stream mode, and provides segmentation and reassembly, per-channel flow control, and error control.

[0154] Generic Attribute Profile (GATT) 23 may operate as a protocol that describes how to use the attribute protocol 22 when configuring a service. For example, Generic Attribute Profile 23 may operate to specify how to group ATT attributes together into services and may operate to describe characteristics associated with a service.

[0155] Thus, the Generic Attribute Profile 23 and Attribute Protocol (ATT) 22 may use characteristics to describe the state and services of a device, how the characteristics relate to each other, and how to use them.

[0156] The attribute protocol 22 and the BR / EDR profile 25 define services (profiles) using Bluetooth BR / EDR and application protocols for exchanging these data, and the Generic Access Profile (GAP) 24 defines device discovery, connection, and security levels.

[0157] As in Figure 5 As shown in (b) of FIG. 4 , the Bluetooth LE protocol stack includes a controller stack 480 operable to process a wireless device interface important in timing and a host stack 490 operable to process high-level data.

[0158] First, the controller stack 480 may be implemented using a communication module (eg, a processor module that may include a processing device such as a microprocessor) that may include a Bluetooth radio.

[0159] The host stack 490 may be implemented as part of an OS running on a processor module or as an instance of a packet on the OS.

[0160] In some cases, the controller stack and the host stack may run or execute on the same processing device in a processor module.

[0161] The controller stack 480 includes a physical layer (PHY) 32 , a link layer 34 , and a host controller interface 36 .

[0162] The physical layer (PHY, wireless transmission / reception module) 32 is a layer that transmits and receives a 2.4 GHz radio signal and uses Gaussian frequency shift keying (GFSK) modulation and a frequency hopping scheme including 40 RF channels.

[0163] The link layer 34 for transmitting or receiving Bluetooth packets creates a connection between devices after performing advertising and scanning functions using 3 advertising channels, and provides a function of exchanging data packets of up to 257 bytes through 37 data channels.

[0164] The host stack includes a Generic Access Profile (GAP) 45, a Logical Link Control and Adaptation Protocol (L2CAP, 41), a Security Manager (SM) 42, and an Attribute Protocol (ATT) 43, a Generic Attribute Profile (GATT) 44, a Generic Access Profile 45, and an LE Profile 46. However, the host stack 490 is not limited thereto and may include various protocols and profiles.

[0165] The host stack reuses various protocols, profiles, etc. provided from the upper Bluetooth layer using L2CAP.

[0166] First, the Logical Link Control and Adaptation Protocol (L2CAP) 41 may provide a bidirectional channel for sending data to a specific protocol or profile.

[0167] L2CAP 41 is operable to multiplex data between higher layer protocols, segment and reassemble packets, and manage multicast data transmissions.

[0168] In Bluetooth LE, basically three fixed channels are used (one for signaling CH, one for security manager, and one for attribute protocol). In addition, dynamic channels can be used as needed.

[0169] Meanwhile, basic channel / enhanced data rate (BR / EDR) uses dynamic channels and supports protocol service multiplexer, retransmission, streaming mode, etc.

[0170] The Security Manager (SM) 42 is a protocol for authenticating devices and providing key distribution.

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

[0172] ① Request and response messages: A request message is a message used to request specific information from a client device to a server device, and a response message is a response message to a request message, which is a message sent from a server device to a client device.

[0173] ② Command message: It is a message sent from the client device to the server device to instruct a command for a specific operation. The server device does not send a response to the command message to the client device.

[0174] ③ Notification message: It is a message sent from the server device to the client device in order to notify an event, etc. The client device does not send a confirmation message about the notification message to the server device.

[0175] ④ Indication and confirmation message: It is a message sent from the server device to the client device in order to notify an event, etc. Unlike the notification message, the client device sends a confirmation message about the indication message to the server device.

[0176] In the present disclosure, when long data is requested using the GATT profile of the attribute protocol (ATT) 43, a value regarding the data length is transmitted to allow the client to clearly know the data length, and a characteristic value can be received from the server by using a universal unique identifier (UUID).

[0177] The Generic Access Profile (GAP) 45 is a newly implemented layer for Bluetooth LE technology that is used to select roles for communications between Bluetooth LE devices and controls how multi-profile operation occurs.

[0178] In addition, the Generic Access Profile (GAP) 45 is mainly used for device discovery, connection generation, and security process parts, defines a scheme for providing information to a user, and defines the types of the following attributes.

[0179] ①Service: It defines the basic operation of the device through the combination of data-related behaviors

[0180] ② Include: It defines the relationship between services

[0181] ③Feature: It is the data value used in the server

[0182] ④Behavior: It is a computer-readable format defined by UUID (value type).

[0183] LE profile 46, including profiles based on GATT, is mainly applied to Bluetooth LE devices. LE profile 46 may include, for example, battery, time, FindMe, proximity, time, object delivery service, etc., and the details of the profile based on GATT are as follows.

[0184] ①Battery: Battery information exchange method

[0185] ②Time: Time information exchange method

[0186] ③ FindMe: Provision of alert service based on distance

[0187] ④ Proximity: Battery information exchange method

[0188] ⑤Time: Time information exchange method

[0189] Generic Attribute Profile (GATT) 44 may operate as a protocol that describes how to use Attribute Protocol (ATT) 43 when configuring a service. For example, GATT 44 may operate to define how ATT attributes are grouped together with a service and to describe characteristics associated with a service.

[0190] Thus, GATT 44 and ATT 43 may use characteristics in order to describe the state and services of a device and describe how characteristics are related and how they are used.

[0191] In the following, the process of Bluetooth Low Energy (BLE) technology will be briefly described.

[0192] The BLE process can be classified into a device filtering process, an advertising process, a scanning process, a discovery process, and a connection process.

[0193] Device Filtering Process

[0194] The device filtering process is a method for reducing the number of devices that perform responses to requests, indications, notifications, etc. in the controller stack.

[0195] When requests are received from all devices, there is no need to respond thereto, and therefore, the controller stack may perform control to reduce the number of requests sent to reduce power consumption.

[0196] An advertising device or a scanning device may perform a device filtering process to limit the devices that receive the advertising packets, scanning requests, or connection requests.

[0197] Here, the advertising device refers to a device that sends an advertising event, that is, a device that executes an advertisement, and is also referred to as an advertiser.

[0198] A scanning device is a device that performs scanning, that is, a device that sends a scan request.

[0199] In BLE, in case that the scanning device receives some advertising packets from the advertising device, the scanning device should send a scan request to the advertising device.

[0200] However, where a device filtering process is used and therefore scan request transmission is not required, the scanning device may disregard advertising packets sent from the advertising device.

[0201] Even in the connection request process, the device filtering process can be used. In the case where the device filtering is used in the connection request process, there is no need to send a response to the connection request by ignoring the connection request.

[0202] Advertising Process

[0203] The advertising device performs an advertising process to perform omnidirectional broadcasting to devices within the area.

[0204] Here, omni-directional broadcast is advertising to all devices rather than broadcasting to a specific device, and all devices can scan the advertisement to make a supplementary information request or a connection request.

[0205] In contrast, targeted advertising may make supplemental information requests or connection requests by scanning only for advertisements for devices designated as receiving devices.

[0206] The advertising process is used to establish a Bluetooth connection with a nearby initiating device.

[0207] Alternatively, the advertising process may be used to provide a periodic broadcast of user data to scanning devices listening in the advertising channel.

[0208] During the advertising process, all advertisements (or advertising events) are broadcast through the advertising physical channel.

[0209] The advertising device may receive a scan request from a listening device performing listening to acquire additional user data from the advertising device. The advertising device sends a response to the scan request to the device that has sent the scan request through the same advertising physical channel as the advertising physical channel in which the scan request has been received.

[0210] Broadcast user data sent as part of an advertising packet is dynamic data, while scan response data is typically static data.

[0211] The advertising device may receive a connection request from an initiating device on the advertising (broadcast) physical channel. If the advertising device has used a connectable advertising event and the initiating device has not been filtered according to the device filtering process, the advertising device may stop advertising and enter connection mode. The advertising device may start advertising after connection mode.

[0212] Scanning process

[0213] A device performing scanning, ie, a scanning device performs a scanning process to listen for an omnidirectional broadcast of user data from an advertising device using an advertising physical channel.

[0214] The scanning device sends a scanning request to the advertising device through the advertising physical channel to request additional data from the advertising device. The advertising device sends a scanning response as a response to the scanning request by including the additional user data requested by the scanning device through the advertising physical channel.

[0215] The scanning process may be used when connecting to other BLE devices in a BLE piconet.

[0216] If the scanning device is in the initiator mode, the scanning device can receive the advertising event and initiate a connection request. The scanning device can send a connection request to the advertising device through the advertising physical channel to start a Bluetooth connection with the advertising device.

[0217] When the scanning device sends a connection request to the advertising device, the scanning device stops the initiator mode scan for additional broadcasts and enters the connection mode.

[0218] Discovery Process

[0219] A device usable for Bluetooth communication (hereinafter referred to as a “Bluetooth device”) performs an advertising process and a scanning process in order to discover devices located nearby or to be discovered by other devices in a given area.

[0220] The discovery process is performed asymmetrically. A Bluetooth device that intends to discover other devices in the vicinity is called a discovering device, and listens to discover devices that advertise advertising events that can be scanned. A Bluetooth device that can be discovered by other devices and made available for use is called a discoverable device, and actively broadcasts advertising events so that it can be scanned by other devices over the advertising (broadcast) physical channel.

[0221] Both discovering devices and discoverable devices may already be connected with other Bluetooth devices in the piconet.

[0222] Connection Process

[0223] The connection process is asymmetric and requests that while a particular Bluetooth device is performing an advertising process, another Bluetooth device should perform a scanning process.

[0224] That is, the advertising process can be targeted, and therefore, only one device can respond to the advertisement.After receiving a connectable advertising event from the advertising device, a connection request can be sent to the advertising device over the advertising (broadcast) physical channel to initiate a connection.

[0225] Hereinafter, operation states in the BLE technology, ie, an advertising state, a scanning state, an initiating state, and a connecting state will be briefly described.

[0226] Ad Status

[0227] The Link Layer (LL) enters the Advertising state according to instructions from the host (stack). When the LL is in the Advertising state, the LL sends an Advertising Packet Data Unit (PDU) in an Advertising event.

[0228] Each advertising event includes at least one advertising PDU, and the advertising PDU is sent by the advertising channel index in use. After the advertising PDU is sent by the advertising channel index in use, the advertising event can be terminated, or in the case where the advertising device may need to ensure space for performing other functions, the advertising event can be terminated in advance.

[0229] Scan Status

[0230] LL enters the scanning state according to the instruction from the host (stack). In the scanning state, LL listens to the broadcast channel index.

[0231] There are two types of scanning states: passive scanning and active scanning. Each scanning type is determined by the host.

[0232] The time or advertising channel index used to perform the scan is not defined.

[0233] During the scanning state, the LL listens for the advertising channel index for the duration of the scanning window. The scanning interval is defined as the interval between the start points of two consecutive scanning windows.

[0234] When there is no conflict in the schedule, LL should listen to complete all scan intervals of the scan window as indicated by the host. In each scan window, LL should scan other advertising channel indexes. LL uses every available advertising channel index.

[0235] In passive scanning, the LL only receives packets and cannot send any packets.

[0236] In active scanning, the LL performs listening in order to request the advertising PDU and the advertising device related supplementary information from the advertising device depending on the advertising PDU type.

[0237] Initiate status

[0238] The LL enters the Initiate state based on instructions from the host (stack).

[0239] When the LL is in the initiating state, the LL performs monitoring on the advertising channel index.

[0240] During the Initiation state, the LL listens for the advertising channel index during the scanning window interval.

[0241] Connection Status

[0242] The LL enters the Connecting state when the devices execute the Connecting state, that is, when the initiating device sends a CONNECT_REQ PDU to the advertising device or when the advertising device receives a CONNECT_REQ PDU from the initiating device.

[0243] After LL enters the connected state, it is considered that a connection is generated. However, it is not necessary to consider that a connection should be established at the time point when LL enters the connected state. The only difference between a newly generated connection and an established connection is the LL connection monitoring timeout value.

[0244] When two devices are connected, the two devices play different roles.

[0245] The LL used as a master device is called a master device, and the LL used as a slave device is called a slave device. The master device adjusts the timing of the connection event, and the connection event refers to a time point when the master device and the slave device are synchronized.

[0246] In the following, the packets defined in the Bluetooth interface will be briefly described. A BLE device uses packets defined as follows.

[0247] Packet Format

[0248] LL has only one packet format for both advertising channel packets and data channel packets.

[0249] Each packet includes four fields of preamble, access address, PDU and CRC.

[0250] When a packet is sent in an advertising physical channel, the PDU may be an advertising channel PDU, and when a packet is sent in a data physical channel, the PDU may be a data channel PDU.

[0251] Advertising Channel PDU

[0252] The advertising channel PDU has a 16-bit header and a payload of various sizes.

[0253] The PDU type field of the advertising channel PDU included in the header indicates a PDU type defined in Table 1 below.

[0254] [Table 1]

[0255]

[0256] Advertising PDU

[0257] The following advertising channel PDU types are referred to as advertising PDUs and are used in certain events.

[0258] ADV_IND: connectable non-directional advertising event

[0259] ADV_DIRECT_IND: connectable directed advertising event

[0260] ADV_NONCONN_IND: Non-connectable non-directional advertising event

[0261] ADV_SCAN_IND: Scannable non-targeted ad events

[0262] The PDU is sent from the LL in the Advertising state and received by the LL in the Scanning state or in the Initiating state.

[0263] Scan PDU

[0264] The following advertising channel DPU type is called a scanning PDU and is used in the states described below.

[0265] SCAN_REQ: Sent by the LL in the Scanning state and received by the LL in the Advertising state.

[0266] SCAN_RSP: sent by the LL in the Advertising state and received by the LL in the Scanning state.

[0267] Initiate PDU

[0268] The following Advertising Channel PDU types are referred to as Origination PDUs.

[0269] CONNECT_REQ: sent by the LL in the Originating state and received by the LL in the Advertising state.

[0270] Data Channel PDU

[0271] The data channel PDU may include a message integrity check (MIC) field with a 16-bit header and a payload with various sizes.

[0272] The procedures, states, and packet formats in the BLE technology discussed above may be applied to perform the methods proposed in the present disclosure.

[0273] refer to Figure 4 , the load (455) may correspond to a battery. The battery may store energy by using the power output from the power pickup unit (210). Meanwhile, it is not mandatory to include a battery in the mobile device (450). For example, the battery may be provided as a detachable external feature. As another example, the wireless power receiver may include an operating device that can perform different functions of the electronic device, instead of a battery.

[0274] As shown in the figure, although the mobile device (450) is exemplified as being included in the wireless power receiver (200) and the base station (400) is exemplified as being included in the wireless power transmitter (100), in a broader sense, the wireless power receiver (200) can be identified as (or regarded as) the mobile device (450), and the wireless power transmitter (100) can be identified as (or regarded as) the base station (400).

[0275] When the communication / control circuit 120 and the communication / control circuit 220 include Bluetooth or Bluetooth LE as an OB communication module or a short-range communication module in addition to the IB communication module, the wireless power transmitter 100 including the communication / control circuit 120 and the wireless power receiver 200 including the communication / control circuit 220 may be configured as follows: Figure 6It is represented by the simplified block diagram shown in .

[0276] Figure 6 is a block diagram illustrating a wireless power transfer system using BLE communication according to an example.

[0277] refer to Figure 6 , the wireless power transmitter 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 .

[0278] Meanwhile, the wireless power receiver 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.

[0279] In one aspect, the BLE communication modules 122 and 222 perform the Figure 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.

[0280] 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.

[0281] Figure 7 is a block diagram illustrating a wireless power transfer system using BLE communication according to another example.

[0282] refer to Figure 7 , the communication / control circuits 120 and 220 include only the in-band communication modules 121 and 221 , respectively, and the BLE communication modules 122 and 222 may be provided separately from the communication / control circuits 120 and 220 .

[0283] Hereinafter, the coil or the coil unit includes a coil and at least one device close to the coil, and the coil or the coil unit may also be referred to as a coil component, a coil cell, or a cell.

[0284] Meanwhile, when the user places the wireless power receiver 200 within the operating capacity of the wireless power transmitter 100, the wireless power transmitter 100 and the wireless power receiver 200 begin to communicate for the purpose of configuring and controlling power transmission. At this time, the power signal can provide a carrier for all communications, and the protocol for communication can consist of several steps. Hereinafter, the communication protocol will be described.

[0285] Figure 8 It is a state transition diagram used to explain the wireless power transfer process.

[0286] WPC can define two communication protocols.

[0287] Baseline Protocol (or BPP): may refer to an original protocol that supports only unidirectional communication from the wireless power receiver 200 to the wireless power transmitter 100 .

[0288] - Extended Protocol (or EPP): Supports bidirectional communication and improved foreign object detection (FOD) functionality, and is also capable of supporting data streaming functionality and authentication options.

[0289] refer to Figure 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 can be mainly divided into a ping phase (810), a configuration phase (820), a negotiation phase (830), and a power transfer phase.

[0290] - ping phase (810)

[0291] 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 if 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.

[0292] Here, after acquiring the design information from the wireless power receiver 200 , the wireless power transmitter 100 may postpone the conclusion as to whether the detected metal is a foreign object or a friendly metal to the negotiation stage 830 .

[0293] - Configuration phase (820)

[0294] 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.

[0295] 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 .

[0296] Here, the wireless power receiver 200 can use functions such as enhanced FOD, data transmission flow, and authentication only when the extended protocol is implemented.

[0297] - Negotiation phase (830)

[0298] In the negotiation phase 830, the wireless power transmitter 100 and the wireless power receiver 200 may establish an extended power delivery contract including 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 FOD before transitioning to the power delivery phase 840.

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

[0300] - Power Delivery Stage (840)

[0301] The power delivery phase 840 may be a step of delivering power to a load of the wireless power receiver 200 .

[0302] In the extended protocol, the wireless power transmitter 100 and the wireless power receiver 200 may perform system calibration when this step begins. This phase may sometimes be interrupted to renegotiate elements of the power delivery contract. However, power delivery may continue even during this renegotiation.

[0303] Below, as previously explained, each protocol for the Ping phase 810, the Configuration phase 820, the Negotiation phase 830, and the Power Delivery phase 840 will be explained in more detail.

[0304] 1. Ping stage (810)

[0305] When the Ping phase 810 begins, the wireless power transmitter 100 does not yet know whether the wireless power receiver 200 is within operating capacity. In addition, the wireless power transmitter 100 cannot identify the wireless power receiver 200. Therefore, this system is usually disabled due to the lack of power signal.

[0306] In this case, before the wireless power transmitter 100 initiates a digital ping to request a response from the wireless power receiver 200 , the wireless power transmitter 100 may go through the following steps.

[0307] Fig. 9 An example of a protocol for a ping phase 810 is schematically shown.

[0308] according to Fig. 9 , the wireless power transmitter 100 can perform a simulated ping (S910). That is, the wireless power transmitter 100 can confirm whether there is an object in the operating volume by sending a simulated ping. For example, the wireless power transmitter can detect whether there is an object in the operating space based on the current change in the transmission coil or the primary coil.

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

[0310] a) First, it is possible to determine whether one or more detected objects include an NFC tag.

[0311] b) Afterwards, it is possible to check whether the object containing the NFC tag can withstand the power signal without being damaged.

[0312] c) If the wireless power transmitter 100 determines that the NFC tag cannot withstand the power signal, it does not initiate the digital ping and maintains the ping phase, the wireless power transmitter 100 can inform the user of the reason why it cannot proceed.

[0313] The wireless power transmitter 100 may perform foreign object detection (S930). That is, the wireless power transmitter 100 can collect information that helps determine whether there is a foreign object in addition to the wireless power receiver 200. To this end, the wireless power transmitter 100 can use various methods such as a pre-powered FOD method.

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

[0315] If the wireless power transmitter 100 performs the above steps and determines that the wireless power receiver 200 is potentially present in the operating capacity, the wireless power transmitter 100 may initiate 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.

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

[0317] 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 .

[0318] 2. Configuration phase (820)

[0319] The configuration phase 820 is part of the following protocol.

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

[0321] - The wireless power receiver 200 and the wireless power transmitter 100 are able to establish a baseline power transfer contract.

[0322] - The wireless power receiver 200 and the wireless power transmitter 100 are able to determine the protocol variant to be used for power transmission.

[0323] In the configuration phase 820, the wireless power transmitter 100 and the wireless power receiver 200 may continue to operate using digital ping parameters. 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 a position within the operating capacity.

[0324] In the following, the protocol in the configuration phase 820 will be described in more detail.

[0325] Fig.10 An example of a protocol for the configuration phase 820 is schematically shown.

[0326] 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 may identify itself using the ID data packet and optionally the XID data packet.

[0327] The wireless power transmitter 100 may selectively receive a power control delay (PCH) data packet (S1030) from the wireless power receiver 200, and the wireless power transmitter 100 may receive a CFG data packet (S1040) from the wireless power receiver 200. That is, the wireless power receiver 200 may use the PCH and / or CFG data packets to provide data used in the power transfer contract.

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

[0329] Each data grouping described above can be summarized as follows.

[0330] - ID: The ID data packet may be information for identifying the wireless power receiver 200. Here, the ID may include a manufacturer code, a basic device identifier, etc. In addition, the ID may also include the presence or absence of an XID data packet for identifying the setting stage.

[0331] - XID: The XID data packet may contain additional identification data.

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

[0333] - CFG: The CFG data group can provide basic configuration data.

[0334] For example, the CFG data packet can provide all parameters controlling power delivery in the baseline protocol. In addition, the CFG data packet can provide all FSK communication parameters used in the extended protocol. Additionally, the CFG data packet can provide additional functionality of the wireless power receiver 200.

[0335] Fig.11 is a diagram illustrating a message field of a configuration packet (CFG) of a wireless power receiving device according to an embodiment.

[0336] according to Fig.11 , a configuration packet (CFG) according to one embodiment may have a header value of 0x51, and a message field of the configuration packet (CFG) may include a 1-bit authentication (AI) flag and a 1-bit out-of-band (OB) flag.

[0337] 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 if the value of the authentication flag (AI) is "0", it may indicate that the wireless power receiving device does not support the authentication function or cannot operate as an authentication initiator.

[0338] 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-of-band (OB) flag is "1", the wireless power receiver indicates out-of-band communication, and if the value of the out-of-band (OB) flag is "0", it may indicate that the wireless power receiving device does not support out-of-band communication.

[0339] The provision of ID and / or XID described above is for identification purposes. Additionally, the provision of PCH and / or CFG is for the construction of a power delivery contract.

[0340] 3. Negotiation phase (830)

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

[0342] - Negotiation phase (830): The negotiation phase (830) directly follows the configuration phase (820) and is used to create an initial extended power delivery contract. In addition, the negotiation phase 830 is also used to complete the pre-power FOD function. Here, the length of the negotiation phase is not limited.

[0343] - Renegotiation phase: The renegotiation phase can interrupt the power delivery phase (840) multiple times and is typically used to adjust a single element of the power delivery contract. In addition, FOD / qf, FOD / rf and SRQ / rpr data packets cannot be used in the renegotiation phase. The constraints on CE data packets in the power delivery phase 840 limit the length of the renegotiation phase.

[0344] During the negotiation or renegotiation phase, a power delivery contract related to the reception / transmission of wireless power between a wireless power receiving device and a wireless power transmitting device is extended or changed, or at least some elements of the power delivery contract are adjusted for renewal of the power delivery contract, or information can be exchanged to establish out-of-band communication.

[0345] Fig.12 is a flow chart schematically illustrating a protocol of a negotiation phase or a re-negotiation phase according to an embodiment.

[0346] refer 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 notify the wireless power transmitter 100 of its presence of an influence on the selected attribute of the reference wireless power transmitter 100. And, the wireless power transmitter 100 may use this information to configure the FOD function.

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

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

[0349] 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.

[0350] For example, in the negotiation phase or the re-negotiation phase, 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 ).

[0351] The wireless power transmitter 100 having 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.

[0352] Alternatively, in the negotiation phase or the renegotiation phase, 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 a header value (0x31) of the capability packet (CAP).

[0353] The wireless power transmitter 100 having received the GRQ / cap may transmit a capability packet (CAP) to the wireless power receiver 200 ( S1235 ).

[0354] Alternatively, in the negotiation phase or the renegotiation phase, 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 a header value (0x32) of a capability packet (XCAP).

[0355] The wireless power transmitter 100 having received the GRQ / xcap may transmit a capability packet (XCAP) to the wireless power receiver 200 ( S1245 ).

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

[0357] A Capability Packet (CAP) according to one embodiment may have a header value of 0x31 and refer to Fig.13 , can include a 3-byte message field.

[0358] refer to Fig.13 , the message field of the capability packet (CAP) may include a 1-bit authentication (AR) flag and a 1-bit out-of-band (OB) flag.

[0359] 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 if the value of the authentication flag (AR) is "0", it may indicate that the wireless power transmitter 100 does not support the authentication function or cannot operate as an authentication responder.

[0360] The out-of-band (OB) flag indicates whether the wireless power transmitter 100 supports out-of-band communication. For example, if the value of the out-of-band (OB) flag is "1", the wireless power transmitter 100 indicates out-of-band communication, and if the value of the out-of-band (OB) flag is "0", this may indicate that the wireless power transmitter 100 does not support out-of-band communication.

[0361] In the negotiation phase, the wireless power receiver 200 can receive a capability packet (CAP) of the wireless power transmitter 100 and check whether the wireless power transmitter 100 supports an authentication function and supports out-band communication.

[0362] return Fig.12 The wireless power receiver 200 is able to update elements of a power transfer contract (Power Transfer Contract) related to power to be provided in the power transfer phase using at least one specific request packet (SRQ, specific request data packet) in the negotiation phase or the renegotiation phase (S1250) (ACK / NAK for this can be received (S1255)).

[0363] Meanwhile, in order to confirm the extended power transfer contract and end the negotiation phase, the wireless power receiver 200 transmits SRQ / en to the wireless power transmitter 100 ( S1260 ), and it can receive ACK from the wireless power transmitter 100 ( S1265 ).

[0364] 4. Power delivery phase (840)

[0365] The power delivery phase 840 is the portion of the protocol in which actual power is delivered to the load of the wireless power receiver 200. Here, the power delivery may be performed according to the conditions of the power delivery contract created in the negotiation phase 830.

[0366] <CE-based power control>

[0367] The wireless power receiver 200 is able to control the power level by sending control error (CE) data, which measures the deviation between the target and actual operating points of the wireless power receiver 200, to the wireless power transmitter 100. The wireless power transmitter 100 and the wireless power receiver 200 aim to make the control error data zero, at which point the system will operate at the target power level.

[0368] <Electric FOD Transport Method>

[0369] In addition to controlling error data, the wireless power transmitter 100 and the wireless power receiver 200 can also exchange information to facilitate FOD. The wireless power receiver 200 periodically reports its received power (received power level) to the wireless power transmitter 100, and the wireless power transmitter 100 can notify the wireless power receiver 200 whether a foreign object has been detected. The method that can be used for FOD in the power delivery phase can correspond to, for example, power loss calculation. In this method, the wireless power transmitter 100 compares the received power level reported by the wireless power receiver 200 with the amount of power transmitted (transmitted power level), and when the difference exceeds a threshold, it can send a signal (whether a foreign object has been detected) to the wireless power receiver 200.

[0370] <Renegotiation Phase>

[0371] If necessary depending on the situation, the wireless power transmitter 100 or the wireless power receiver 200 may request a renegotiation of the power transfer contract during the power transfer phase. Examples of situations where changes in the renegotiation of the power transfer contract may occur include:

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

[0373] - When the wireless power transmitter 100 detects that it is operating with low efficiency.

[0374] - When the wireless power transmitter 100 is no longer able to maintain its current power level due to increased operating temperature (or vice versa, ie, when the wireless power receiver 200 is able to operate at a higher power level after sufficient cooling).

[0375] Here, an example of a specific protocol used in the renegotiation phase is the same as described above.

[0376] <Data transfer stream>

[0377] The wireless power transmitter 100 and the wireless power receiver 200 may start a data transmission flow and exchange application level data throughout the power delivery phase 840 .

[0378] Here, an important common application is authentication, where each party can verify the credentials of the other party 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 proper credentials can mean that you have passed compliance testing.

[0379] Thus, the present description may provide a method of initiating power transfer at a low power level and controlling the power to a higher level only after successfully completing an authentication protocol.

[0380] <Protocol in Power Delivery Phase 840>

[0381] So far, the operations between the wireless power transmitter 100 and the wireless power receiver 200 in the power delivery phase 840 have been briefly described. Hereinafter, for smooth understanding of the operations in the power delivery phase 840, the protocols in the power delivery phase 840 will be described as a baseline protocol and an extended protocol, respectively.

[0382] Fig.14 A flow chart schematically illustrates the data flow for the power delivery phase 840 in the baseline protocol.

[0383] 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 is generally capable of transmitting CE data packets multiple times per second.

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

[0385] Alternatively, the wireless power receiver 200 may transmit a charging status (CHS) data packet to the wireless power transmitter 100 ( S1430 ).

[0386] The data grouping described above can be summarized and explained as follows.

[0387] -CE: The CE data packet can provide feedback on the required power level. The CE data packet may include a control error value, where the control error value may be a signed integer value, which is a relative measurement 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 lower than 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 higher than the target operating point, and the wireless power transmitter 100 may be requested to reduce the power signal.

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

[0389] - CHS: The CHS data packet can provide the charge level of the battery at the load.

[0390] Fig.15 A flow chart schematically illustrates the data flow of the power delivery phase 840 in the extended protocol.

[0391] 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 is generally capable of transmitting CE data packets multiple times per second.

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

[0393] In the power delivery phase, control error packets (CE) and received power packets (RP) are data packets that must be repeatedly transmitted / received according to the timing constraints required to control wireless power.

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

[0395] 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 ).

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

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

[0398] For a received power packet having a mode value 1 or 2 (RP / 1 or RP / 2), when the wireless power transmitter 100 responds with ACK, this means that the wireless power receiver 200 has accepted the power correction value included in the received power packet (RP / 1 or RP / 2).

[0399] For a received power packet having a mode value 1 or 2 (RP / 1 or RP / 2), when the wireless power transmitter 100 responds with NAK, this means that the wireless power receiver 200 does not accept the power correction value included in the received power packet (RP / 1 or RP / 2).

[0400] The received power packet (RP / 1) with the mode value 1 described above may mean a first calibration data point, and the received power packet (RP / 2) with the mode value 2 may mean an additional calibration data point. Here, the wireless power receiver may transmit the received power packet (RP / 2) with the mode value 2 to the wireless power transmitter multiple times to transmit multiple additional power calibration values, and the wireless power transmitter may perform a calibration process based on the received RP / 1 and multiple RP / 2.

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

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

[0403] At the same time, the wireless power transmitter 100 and the wireless power receiver 200 can exchange data stream response (DSR) data packets, CAP data packets, and NEGO data packets to initiate renegotiation of elements of the power transfer contract (generally the guaranteed load power).

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

[0405] Furthermore, the wireless power receiver 200 transmits a NEGO data packet to the wireless power transmitter 100 ( S1540 ), and the wireless power transmitter 100 may transmit an ACK to the wireless power receiver 200 in response to the NEGO data packet ( S1545 ).

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

[0407] - DSR: Any of the following values ​​can be set in the DSR data packet.

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

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

[0410] iii) 0x55-DSR / nd: indicates that the data packet last received from the wireless power transmitter 100 is not expected.

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

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

[0413] - NEGO: The NEGO data packet may request the wireless power transmitter 100 to proceed to a re-negotiation phase.

[0414] The wireless power transmitter 100 and the wireless power receiver 200 may exchange application level data using Assistance Data Transfer (ADC), Assistance Data Transfer (ADT), and DSR data packets.

[0415] That is, from the perspective of transmission and reception of a data transmission stream for exchanging 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 may transmit ACK / NAK to the wireless power receiver 200 in response (S1555). In addition, the wireless power receiver 200 may transmit DSR to the wireless power transmitter 100 (S1560), and the wireless power transmitter may transmit ADC / ADT to the wireless power receiver (S1565).

[0416] Here, the data transport stream is used to convey application level data from a data stream initiator to a data stream responder. Additionally, application level data can be roughly divided into i) certified applications, and ii) proprietary (general purpose) applications.

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

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

[0419] Authentication request messages include GET_DIGESTS, GET_CERTIFICATE, and CHALLENGE.

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

[0421] - GET_CERTIFICATE: This request can be used to read segments of a target's certificate chain.

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

[0423] The authentication response message includes digest (DIGESTS), certificate (CERTIFICATE), CHALLENGE_AUTH and error (ERROR).

[0424] -DIGESTS: The wireless power transmitter 100 can use the DIGESTS response to send a certificate chain summary and report a time slot containing a valid certificate chain summary.

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

[0426] -CHALLENGE_AUTH: The wireless power transmitter 100 can respond to a CHALLENGE request using CHALLENGE_AUTH.

[0427] -ERROR: This response can be used to send error information from the power transmitter.

[0428] The authentication message may be referred to as an authentication packet, authentication data, or authentication control information. Additionally, messages such as GET_DIGEST and DIGESTS may also be referred to as GET_DIGEST packets, DIGEST packets, and the like.

[0429] Meanwhile, as described above, the wireless power receiver 200 and the wireless power transmitter 100 are able to transmit application level data through a data transmission stream. The application level data transmitted through the data transmission stream may consist of a data packet sequence having the following structure.

[0430] - Opens the initial ADC data packet for the stream.

[0431] i) The type of messages contained in the stream.

[0432] ii) The number of data bytes in the stream.

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

[0434] - Closes the final ADC of a stream / ends data packet.

[0435] Hereinafter, a data transmission flow of an example using the above-mentioned ADC, ADT, and ADC / end data packet will be described using the drawings.

[0436] Fig.16 An application level data flow between the wireless power transmitter 100 and the wireless power receiver 200 according to an example is illustrated.

[0437] refer to Fig.16 , the data stream may include auxiliary data control (ADC) data packets and / or auxiliary data transfer (ADT) data packets.

[0438] The ADC data packet is used to open a data stream. The ADC data packet can indicate the type of message and the number of data bytes included in the stream. On the other hand, the ADT data packet is a sequence of data containing the actual message. The ADC / end data packet is used to signal the end of the stream. For example, the maximum number of data bytes in a data transfer stream can be limited to 2047.

[0439] ACK or NAC (NACK) is used to notify whether the ADC data packet and the ADT data packet are normally received. Between the transmission timings 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.

[0440] Using this data flow structure, authentication-related information or other application-level information can be sent and received between the wireless power transmitter and receiver.

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

[0442] Fig.17A power control method according to one embodiment is shown.

[0443] exist Fig.17 In the power transfer phase of the wireless power transmitter 100 and the wireless power receiver 200, the amount of power transferred can be controlled by performing communication together with power transmission and reception. The wireless power transmitter and the wireless power receiver operate at a specific control point. The control point represents a combination of voltage and current provided from the output of the wireless power receiver when power transfer is performed.

[0444] More specifically, the wireless power receiver selects a desired control point, a desired output current / voltage, a temperature at a specific location of the mobile device, etc., and additionally determines an actual control point at which the receiver is currently operating. The wireless power receiver calculates a control error value by using the desired control point and the actual control point, and then, the wireless power receiver can send the calculated control error value as a control error packet to the wireless power transmitter.

[0445] In addition, the wireless power transmitter can configure / control new operating points - amplitude, frequency and duty cycle - by using the received control error packet to control power delivery. Therefore, the control error packet can be sent / received at constant time intervals during the power delivery phase, and, according to an exemplary embodiment, in the case where the wireless power receiver attempts to reduce the current of the wireless power transmitter, the wireless power receiver can send the control error packet by setting the control error value to a negative number. And, in the case where the wireless power receiver plans to increase the current of the wireless power transmitter, the wireless power receiver sends the control error packet by setting the control error value to a positive number. During the induction mode, the wireless power receiver can control power delivery by sending the control error packet to the wireless power transmitter as described above.

[0446] In the resonant mode, the device can be operated by using a different method from the inductive mode. In the resonant mode, one wireless power transmitter should be able to serve multiple wireless power receivers at the same time. However, in the case where power delivery is controlled just as in the inductive mode, since the power being delivered is controlled by the communication established with one wireless power receiver, it may be difficult to control the power delivery of the additional wireless power receivers. Therefore, in the resonant mode according to the present disclosure, a method is used to control the amount of power being received by causing the wireless power transmitter to jointly deliver (or transmit) basic power and by causing the wireless power receiver to control its own resonant frequency. Nevertheless, even during operation in the resonant mode, the above Fig.17 The methods described in are not excluded. Fig.17 Method to perform additional control of transmit power.

[0447] Hereinafter, the present specification will be described in more detail.

[0448] Wireless charging methods include a magnetic induction method using a magnetic induction phenomenon between a primary coil and a secondary coil, and a magnetic resonance method in which magnetic resonance is achieved using a frequency in a frequency band of several tens of kHz to several MHz to transmit power. Here, the wireless charging standard of the magnetic resonance method is led by a conference named A4WP, and the magnetic induction method is led by WPC (Wireless Power Consortium). Here, WPC is designed to exchange various status information and commands related to the in-band wireless charging system.

[0449] The standard in WPC defines a Baseline Power Profile (BPP) and an Extended Power Profile (EPP). Hereinafter, BPP and EPP will be described separately.

[0450] A. Baseline Power Profile (BPP)

[0451] BPP refers to a power transfer profile between a wireless power transmitter and a receiver that supports power transfer of up to 5 W. Also, in BPP, one-way 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 stages of ping, configuration, and power transfer.

[0452] B. Extended Power Profile (EPP)

[0453] EPP relates to a power transfer profile between a wireless power transmitter and a receiver that supports power transfer of up to 15W. Also, 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 ASK (Amplitude Shift Keying), 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 stages of ping, setup, negotiation, and power transfer.

[0454] (a) Compatibility in EPP

[0455] EPP may correspond to a higher profile of BPP.

[0456] For example, if a BPP wireless power receiver is placed on an EPP wireless power transmitter, the EPP wireless power transmitter may operate as a BPP wireless power transmitter.

[0457] For example, if an EPP wireless power receiver is placed on a BPP wireless power transmitter, the EPP wireless power receiver may operate as a BPP wireless power receiver.

[0458] In other words, EPP can maintain compatibility with BPP.

[0459] (b) EPP indication method of EPP wireless power receiver

[0460] The EPP wireless power receiver may indicate that it is an EPP wireless power receiver by setting the "neg" bit in the configuration packet (ie, CFG) to 1. Specific examples of the configuration packet are as described above.

[0461] (c) EPP indication method of EPP wireless power transmitter

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

[0463] For reference, as previously explained, the BPP wireless power transmitter does not support the FSK communication method, so the BPP wireless power transmitter cannot send the FSK bit pattern. Therefore, by not receiving the above-mentioned ACK response, the EPP wireless power receiver that sets the "neg" bit to 1 and sends a configuration packet to the BPP wireless power transmitter can identify another wireless power transmitter as a BPP wireless power transmitter.

[0464] In addition, the wireless power transfer system seeks to provide a new power transfer profile, among which the power transfer profile proposed at this time is MPP (Magnetic Power Profile). MPP may correspond to a proprietary extension based on Qi v1.3.0 from Apple.

[0465] C. Magnetic Power Profile (MPP)

[0466] MPP involves a power transfer profile between a wireless power transmitter and a receiver that supports power transfer of up to 15W. Also, 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 ASK (Amplitude Shift Keying), 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) may be used during the negotiation and power transfer phases.

[0467] In MPP, there may be protocol phases of ping, configuration, MPP negotiation, and MPP power delivery.

[0468] (a) Compatibility in MPP

[0469] MPP may correspond to a higher profile of BPP.

[0470] For example, if a BPP wireless power receiver is placed on an MPP wireless power transmitter, the MPP wireless power transmitter may operate as a BPP wireless power transmitter.

[0471] For example, if an MPP wireless power receiver is placed on a BPP wireless power transmitter, the MPP wireless power receiver may operate as a BPP wireless power receiver.

[0472] In other words, MPP can maintain compatibility with BPP.

[0473] (b) MPP operation of MPP wireless power receiver (MPP indication method)

[0474] An MPP wireless power receiver may use a specific MPP indicator within an Extended ID Packet.

[0475] In order for the MPP wireless power receiver to indicate whether it supports MPP through XID, the wireless power receiver must notify the wireless power transmitter to send XID through an ID packet. The ID packet sent by the MPP wireless power receiver may be as follows.

[0476] Fig.18 The structure of the MPP ID packet is schematically shown.

[0477] according to Fig.18 , in the MPP ID packet, the values ​​of the major version fields b4 to b7 of B0 may be set to 1.

[0478] In the MPP ID packet, the values ​​of the Minor Version fields b0 to b3 of B0 may be values ​​determined later.

[0479] In the MPP ID packet, the value of the manufacturer code of B1 and B2 may be assigned as the PRMC code.

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

[0481] 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.

[0482] Fig.19 An example of XID grouping in MPP is schematically shown.

[0483] according to Fig.19 , the XID grouping in MPP may include an "XID Selector" field, a "Restricted" field, and a "Freq Mask" field.

[0484] Here, whether MPP is supported may be determined according to whether the value of "XID selector" is 0xFE. That is, if the value of B_0 of XID is 0xFE, the XID at this time may correspond to information indicating that the wireless power receiver supports MPP.

[0485] The "Restricted" field may correspond to information indicating whether the wireless power receiver is operating in the MPP restricted mode or the MPP full mode. If the wireless power receiver chooses to operate in the MPP restricted mode, the above field may be set to 1. In addition, in other cases (for example, when the wireless power receiver chooses not to operate in the MPP restricted mode), the above field may be set to 0.

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

[0487] The "Freq Mask" field corresponds to a field that determines whether an operating frequency of 360 kHz is supported. That is, if the "FreqMask" field is set to 0, 360 kHz is supported.

[0488] 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 XID is set to 0xFE, the wireless power transmitter can determine whether the wireless power receiver supports MPP.

[0489] (c) MPP operation of MPP wireless power transmitter (MPP indication method)

[0490] After detecting that a wireless power receiver is placed on the charging surface, the MPP wireless power transmitter may use the information contained in the ID and XID packets to perform a digital ping and identify the receiver.

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

[0492] - Qi Version: The Qi protocol version of the ID group is set to (Major=1, Minor=TBD) or higher.

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

[0494] If the above two conditions are not met, the wireless power transmitter may perform subsequent processes according to the Qi v1.3 specification.

[0495] In addition, according to the MPP operation mode requested by the MPP wireless power receiver in the XID packet, the wireless power transmitter performs the following operations.

[0496] - Restricted Profile Enabled (MPP Restricted Mode): When the "restricted" flag is set to 1.

[0497] - Full profile enabled (MPP full mode): when the "restricted" flag is set to 0.

[0498] Specific examples of the above-mentioned restricted profile and full profile will be described later.

[0499] Furthermore, when the MPP wireless power transmitter receives a configuration packet with the “neg” bit set to 1 from the wireless power receiver, the MPP wireless power transmitter (in MPP full mode) may respond thereto to the wireless power receiver with an MPP ACK FSK bit pattern.

[0500] For reference, the wireless power transmitter in the MPP restricted mode does not support the FSK communication method, so the wireless power transmitter in the MPP restricted mode cannot send the FSK bit pattern. However, because the wireless power transmitter in the MPP restricted mode uses a 360 kHz operating signal to transmit power, the MPP wireless power receiver that sets the "neg" bit to 1 and sends a configuration packet to the wireless power transmitter operating in the MPP restricted mode allows another wireless power transmitter to be identified as an MPP restricted mode wireless power transmitter by the operating frequency.

[0501] (d) MPP model

[0502] In addition, there may be two modes in MPP, one of which is an MPP restricted mode (MPP restricted mode) (in other words, an MPP baseline profile), and the other is an MPP full mode (in other words, an MPP full profile).

[0503] 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.

[0504] In addition, FSK communication is not supported in MPP limited mode, but is supported in MPP full mode.

[0505] In addition, since FSK communication is not supported in MPP limited mode, MPP ACK for CFG cannot be sent, so 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 sent, so MPP negotiation can be supported in MPP full mode.

[0506] In the following, the MPP restricted mode and the MPP full mode will be described in more detail. Here, the MPP restricted mode can be mixed with the MPP baseline profile, and the MPP full mode can be mixed with the MPP full profile.

[0507] Below, in order to better understand the MPP restricted mode and the MPP full mode, the protocols in each mode will be explained in more detail.

[0508] i) MPP restricted mode

[0509] As previously explained, FSK communication is not supported in the MPP limited mode. That is, in the MPP limited mode, there may be no data packets sent from the wireless power transmitter to the wireless power receiver. In this context, the protocol in the MPP limited mode will be explained through the accompanying drawings.

[0510] Fig. 20 The protocol in MPP restricted mode is schematically shown.

[0511] according to Fig. 20 , the wireless power receiver may send a SIG to the wireless power transmitter at a first operating frequency (e.g., 128 kHz). At this time, the first operating frequency may correspond to an operating frequency at which BPP and / or EPP may be performed. And, the first operating frequency at this time corresponds to a frequency at which the wireless power transmitter operates.

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

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

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

[0515] Here, when the wireless power transmitter receives the above-mentioned XID packet indicating the MPP limited mode, the wireless power transmitter may remove the power signal and restart the ping phase with a new operating frequency.

[0516] When the ping phase is restarted, the wireless power receiver starts to send the SIG again. However, the operating frequency at this time may be the second operating frequency (eg, 360 kHz).

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

[0518] ii) MPP full mode

[0519] As previously described, FSK communication can be supported in MPP full mode. That is, in MPP full mode, there may be data packets sent from the wireless power transmitter to the wireless power receiver. In other words, MPP negotiation, etc. may be performed between the wireless power transmitter and the wireless power receiver. In this context, the protocol in MPP full mode will be described by the accompanying drawings.

[0520] Fig.21 and Fig. 22 The protocol in MPP full mode is schematically shown.

[0521] First, according to Fig.21 , the wireless power receiver may send a SIG to the wireless power transmitter at a first operating frequency (e.g., 128 kHz). At this time, the first operating frequency may correspond to an operating frequency at which BPP and / or EPP may be performed. And, the first operating frequency at this time corresponds to a frequency at which the wireless power transmitter operates.

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

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

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

[0525] In addition, in the MPP full mode, unlike the MPP limited mode, even if the wireless power transmitter receives an XID packet from the wireless power receiver, the power signal is not removed. At this time, since the power signal has not been removed, the wireless power receiver sends a CFG packet to the wireless power transmitter after the XID packet.

[0526] And, the wireless power receiver may receive an MPP ACK from the wireless power transmitter as a response to the above-mentioned CFG packet.

[0527] The wireless power receiver receiving the MPP ACK enters a negotiation phase with the wireless power transmitter, and both the wireless power receiver and the wireless power transmitter may perform negotiation.

[0528] After the negotiation is performed, the wireless power receiver may enter a power transfer phase with the wireless power transmitter.

[0529] In addition, the wireless power receiver transmits an EPT packet to the wireless power transmitter. The wireless power transmitter receiving the EPT packet removes the power signal and may then restart the ping phase at a new operating frequency.

[0530] according to Fig. 22 When the ping phase is restarted, the wireless power receiver starts again from sending the SIG. However, the operating frequency at this time may be the second operating frequency (eg, 360 kHz).

[0531] 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 may receive MPP ACK from the wireless power transmitter.

[0532] The wireless power receiver receiving 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 may perform negotiation.

[0533] After the 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 can receive wireless power from the wireless power transmitter based on the MPP full mode by sending an XCE to the wireless power transmitter and responding (eg, receiving an ACK).

[0534] Hereinafter, the present specification will be described in more detail.

[0535] The current WPC Qi specification provides an authentication function. Here, authentication can be performed as follows.

[0536] 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 sends an authentication response to the request from the wireless power receiver to the wireless power receiver. In this way, the wireless power receiver can authenticate the wireless power transmitter.

[0537] The data used for authentication is described below.

[0538] Fig.23 An example of an authentication message header is shown.

[0539] 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.

[0540] Fig.24 Figure 1 shows an example of the Authentication Protocol Version field.

[0541] according to Fig.24 , the Authentication Protocol Version field can have a value 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.

[0542] Fig.25 Illustrate an example of a message type field for an authentication request.

[0543] according to Fig.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.

[0544] Fig.26 Illustrate an example of a message type field for an authentication response.

[0545] 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 an authentication request.

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

[0547] Fig. 27 Figure 1. Example of GET_DIGESTS. Fig.28 Figure 1 shows an example of GET_CERTIFICATE. Fig.29 An example of a CHALLENGE is shown.

[0548] In summary, the authentication request message includes GET_DIGESTS, GET_CERTIFICATE and CHALLENGE.

[0549] - GET_DIGESTS: This request can be used to retrieve the certificate chain digest. The wireless power receiver (200) can request any number of digests at a time.

[0550] - GET_CERTIFICATE: This request can be used to read a fragment of the target certificate chain.

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

[0552] The authentication response message sent by the wireless power transmitter includes DIGESTS / CERTIFICATE / CHALLENGE_AUTH. In addition, the authentication response message may include ERROR.

[0553] Fig.30 Figure 1 shows an example of DIGESTS. Fig.31 An example of CERTIFICATE is shown. Fig.32 Figure 1. Example of CHALLENGE_AUTH. Fig.33 An example of ERROR is shown.

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

[0555] - DIGESTS: The wireless power transmitter (100) may use the DIGESTS response to send a certificate chain digest and report the time slots containing a valid certificate chain digest.

[0556] - CERTIFICATE: The wireless power transmitter (100) may use this response to send the requested fragment of the certificate chain.

[0557] - CHALLENGE_AUTH: The wireless power transmitter (100) may use CHALLENGE_AUTH to respond to a CHALLENGE request.

[0558] - ERROR: This response can be used to send error information from the power transmitter.

[0559] As explained above, a new function called Authentication has been added to the wireless charging standard WPC Qi. Authentication is a process of checking whether the other party's device has actually received Qi certification, and is a very important way to check whether a standard product exists.

[0560] Authentication in the current specification is performed at the request of PRx, and this function is an optional configuration, not a mandatory function. In order to perform the authentication function, PTx sends an authentication response to the authentication request sent by PRx, thereby checking whether PRx is authenticated by Qi.

[0561] Currently, the timing requirements for performing this function have not been clearly defined. Therefore, there is a problem that the timing requirements for the authentication function cannot be maintained according to the current specifications.

[0562] Here, considering that the authentication function is based on a message in the application layer, which is data communication for wireless charging, the above-mentioned problem is not limited to the authentication function.

[0563] Therefore, the timing requirements for current authentication functions are difficult to meet because the timing conventions in the application layer are not well defined.

[0564] For example, according to the current specification, the end point of the preparation timing of PTx (application message (eg, authentication)) is not defined.

[0565] More specifically, application messages (e.g., authentication messages) are sent via a structure called the data transport layer. Therefore, according to the current specification, time measurements of actual application message units are not possible.

[0566] Additionally, the current specification does not provide any additional definition for packet-level timing related to application messages. This leads to real problems for developers who have different timing requirements for application messages.

[0567] Therefore, the present specification provides a configuration that specifically defines the timing requirements of a wireless power transmitter that can correspond to a responder (e.g., an authentication responder) for an application message. Specifically, the present specification provides a configuration that defines the content of the timing requirements from the perspective of the application layer. In addition, the present specification also defines the content of the timing requirements from the perspective of the TPL layer. In addition, the present specification describes operations related to the timing requirements.

[0568] The following drawings are created to illustrate specific examples of this specification. The names of specific devices or the names of specific signals / messages / fields depicted in the drawings are presented as examples, and therefore the technical features of this specification are not limited to the specific names used in the following drawings.

[0569] Fig.34 is a flow chart of a method for delivering wireless power according to one embodiment of the present disclosure.

[0570] according to Fig.34 , the wireless power transmitter may enter a power delivery phase associated with delivering wireless power ( S3410 ).

[0571] As described above, the power delivery phase (840) is the portion of the protocol where actual power is delivered to the load of the wireless power receiver (200). Here, the power delivery may be performed according to the conditions of the power delivery contract generated in the negotiation phase (830).

[0572] The wireless power transmitter (100) and the wireless power receiver (200) are capable of initiating a data transmission flow to exchange application-level data throughout the power transfer phase (840).

[0573] An important common application here is authentication, where two parties are able to verify the credentials of the other party in a tamper-proof manner. For example, a wireless power receiver (200) may want to verify the credentials of a wireless power transmitter (100) to ensure that the wireless power transmitter (100) can be trusted to operate safely at high power levels. Possession of the proper credentials can indicate that compliance testing has been passed.

[0574] Thus, the present description can provide a method to start power transfer at a low power level and control the power to a higher level only after the authentication protocol is successfully completed.

[0575] Specific examples of the power delivery phases are described above.

[0576] The wireless power transmitter can receive a first application message from the wireless power receiver in the power transfer phase ( S3420 ).

[0577] Here, as described above, the first application message can be sent via a data transmission stream (data stream).

[0578] As previously described, a data stream may contain auxiliary data control (ADC) packets and / or auxiliary data transfer (ADT) data packets. The ADC packet is used to open a data stream.

[0579] The ADC packet can indicate the type and number of data bytes of the message contained in the stream. On the other hand, the ADT packet is a sequence of data containing the actual message. The ADC / End packet is used to signal the end of a stream.

[0580] During the power transfer phase, a second application message in response to the first application message may be sent to the wireless power receiver.

[0581] As described above, the second application message may also be sent via a data transmission flow (data flow). The specific description of the data transmission flow is as described above.

[0582] Here, it is explained that the application message exchanged between the wireless power transmitter and the wireless power receiver can be an authentication request message or an authentication response message.

[0583] 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.

[0584] At this time, the wireless power transmitter may initiate the transmission of the second application message within a specific time interval. And the starting point of the specific time interval may be the end point of the first application message.

[0585] Here, if the first application message is, for example, GET_DIGESTS and the second application message is, for example, DIGESTS, the specific time interval can be t_DigestReady. And, the value of t_DigestReady can correspond to, for example, 3 seconds. In addition, t_DigestTimeout can correspond to 43 seconds.

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

[0587] Here, the timing convention of t_DigestReady can be, for example, as follows: An example of the timing convention is explained in more detail in the example described below.

[0588] - Start of t_DigestReady: Start of ADC / end packet from TPR (for GET_DIGEST)

[0589] - End of t_DigestReady: until the start of the ATN response of the power transmitter product. (If the wireless power transmitter generates a DIGESTS response, the message type can be 0x1 in the authentication message header.)

[0590] The timing requirements for wireless power transmitters are described in more detail below. The examples described below correspond to Fig.34 Therefore, it goes without saying that the following description can be applied to Fig.34 Examples in .

[0591] Fig.35 An example of timing requirements for a wireless power transmitter is schematically illustrated.

[0592] according to Fig.35 , the timing requirements of the wireless power transmitter, e.g., authentication response preparation time, can be defined as follows.

[0593] Definition of application layer timing requirements (definition of the time for a wireless power transmitter to prepare an authentication response)

[0594] -Start: End of the authentication request

[0595] -end: Start of authentication response

[0596] That is, the start of the second application message can be initiated within a specific time interval starting from the end point of the first application message.

[0597] This can be explained by replacing the authentication message as follows. For example, the transmission of DIGEST can start from the end point of GET_DIGEST within t_DigestsReady. In addition, the transmission of CERTIFICATE can start from the end point of GET_CERTIFICATE within t_CertificatesReady. In addition, the transmission of CHALLENGE_AUTH can start from the end point of CHALLENGE within t_ChallengeAuthReady.

[0598] Here, it is necessary to define more specifically where the end point of the first application message and the start point of the second application message are located in the data transmission layer. This is because it may not be clear where the end point of the first application message and the start point of the second application message are defined in the data transmission layer.

[0599] Therefore, the following provides a configuration for defining an end point of a first application message and a start point of a second application message at a data transmission layer level.

[0600] The following drawings illustrate examples in which the first application message is GET_DIGEST, the second application message is DIGEST, and the specific time interval is t_DigestsReady.

[0601] However, this is just an example, and the following example can also be applied to t_CertificatesReady and / or t_ChallengeAuthReady.

[0602] First, for ease of explanation, we assume that the end point of the first application message is the sending / receiving point of ACK, which is a response to ADC / end related to the first application message.

[0603] In the following, based on the definition of the time requirement of the authentication message (authentication request message and response message), a method for enabling the authentication function to be executed within a given time is proposed. According to this embodiment, the authentication product can execute the authentication function within a given time and achieve the effect of reducing the unauthentication of the authentication product.

[0604] This specification proposes the following:

[0605] In wireless charging, the authentication function can run through various processes. For example, it consists of three steps: Get-digest / Get-certificate / Challenge through request messages. Get-digest must be requested in advance by the authentication initiator through another message (Get-certificate / Challenge) and is an optional message.

[0606] On the other hand, GetCert / Challenge is a message that must be processed (only for the first authentication) and can be requested regardless of the order.

[0607] Additionally, in the case of reauthentication, a challenge is required, but other messages can be processed selectively.

[0608] The authentication function performs the process of checking whether the authentication responder has been authenticated by the authentication initiator after calibration is completed.

[0609] #1. Patent on the timing requirements for authenticating Get-digest / Digests (t_Get-digest / t_DigestsReady / t_DigestsTimeout)

[0610] #1-1. Patent on the timing requirements for authentication Get-digest / Digests (t_Get-DigestTimeout)

[0611] - Problem: Get-digest is an authentication message sent by the authentication initiator, and there is no timeout setting. Therefore, the authentication function may continue indefinitely, and when a communication error occurs, an infinite loop error occurs, preventing the function from being executed correctly, and it is difficult to terminate the function. In other words, a problem occurs in which the function neither progresses nor terminates. Due to this, even if it is a genuine device that has been authenticated, since the authentication function cannot be executed, it becomes an unauthenticated device, and a problem occurs in which fast charging is not possible and only slow charging is possible.

[0612] Fig.36 Figure 1. Example of setting t_Get-DigestTimeout to transmit Get-digest.

[0613] After calibration is complete, the authentication initiator can send a Get-digest for a digest message.

[0614] The Get-Digest (e.g., 19:0F) sent by PRx must be sent within 8.1 seconds. (t_Get-DigestTimeout = 8.1s)

[0615] The time of t_Get-DigestTimeout can be set as follows.

[0616] * tdts = max. 1.5s

[0617] * Assuming ADT / 1 data packet

[0618] * Assuming 50% for communication errors

[0619] * Set the overhead time to 20%

[0620] * t_get-digest timeout = 1.5s * 3 * 1.5 (communication error) * 1.2 (overhead time) = 8.1s

[0621] Fig.37 The figure shows an example of resending Get-digest when t_Get-DigestTimeout times out.

[0622] refer to Fig.37 , the authentication initiator must send Get-Digest within t_Get-DigestTimeout, and if it times out, the corresponding application message is not received and all data stored in the buffer is discarded.

[0623] After this, the authentication initiator can send Get-Digest again, and in this case, the application data communication continues t_Get-DigestTimeout is initialized and applied again. In other words, the authentication initiator can initialize the Get-Digest message and resend it.

[0624] #1-2. Patent on the time requirement for authenticating Get-digest / Digests (t_DigestsReady)

[0625] - Problem: By setting the response time (t_DigestReady) after sending the authentication request message (Get-Digest), preparation time is provided for the authentication response message, and the authentication initiator needs time to prepare for reception. Without this time, there is no time to perform the corresponding function (encryption), and the problem of time desynchronization between PRx / PTx will occur. In addition, time can be measured in packets, so it is necessary to define time at this measurable level.

[0626] The Authentication Responder that receives the Get-Digest sent by the Authentication Initiator must send the digest within 3 seconds (t_DigestReady).

[0627] The time for t_DigestReady can be set as follows.

[0628] * t_DigestReady is measured per packet at the following levels.

[0629] - Start: Start of ADC / end packet of PRx Get-digest.

[0630] - End: Start of ATN response of PTx.

[0631] *Prerequisites are as follows

[0632] - PTx must send a digest message. (The message type of the authentication message header must be 0x1)

[0633] -After the Get-digest message is completed, PRx will send RP / 0 packets several times within 3 seconds. (For example: 3-4 times per second)

[0634] - By sending RP / 0 3-4 times per second as described above, PTx is able to send an ATN response, which is the end point of the time condition of the summary message, so RP / 0 is sent 3-4 times per second to provide an opportunity to send ATN.

[0635] - This time is the preparation time to perform cryptographic functions such as SHA-256, hashing, ECDSA, etc.

[0636] - PTx does not respond to RP / 0 while performing the encryption function to send the digest and sends the ATN response to RP / 0 when preparation is complete.

[0637] - By responding to ATN, PRx recognizes that PTx is ready to send the digest.

[0638] #1-3. Patent on the timing requirement for authentication Get-digest / Digests (t_DigestsTimeout)

[0639] - Problem: By setting a response timeout after sending an authentication request message, an authentication response message must be sent within a specific time. This causes the authentication function to continue indefinitely, and when a communication error occurs, an infinite loop error occurs, making it difficult to correctly execute the function and difficult to terminate the function. In other words, a problem occurs in which the function neither progresses nor terminates. Therefore, even if it is a genuine device that has been authenticated, since the authentication function cannot be executed, it becomes an unauthenticated device, and a problem occurs in which fast charging is not possible and only slow charging is possible.

[0640] The authentication responder must complete sending the digest message within 43 seconds after the authentication initiator receives the Get-digest message. (t_DigestsTimeout)

[0641] The message timeout can be set as follows:

[0642] * PTx uses ADT / 1 grouping.

[0643] * PRx sends DSR packets at 250ms intervals

[0644] * Assuming TPL communication error is about 20%

[0645] * Assuming PTx is sent within min / max range under other relevant timing conditions.

[0646] Fig.38 Figure 1 shows an example of resending Get-digest and Digest messages when t_DigestsTimeout expires.

[0647] refer to Fig.38, the authentication responder must send the digest within t_DigestsTimeout, and if the timeout expires, the authentication initiator discards all data stored in the buffer without receiving the corresponding application message.

[0648] Thereafter, the authentication initiator can send Get-Digest again, and in this case, the application data communication continues t_DigestsTimeout is initialized and applied again. In other words, the authentication initiator can re-execute the function by resending the Get-Digest message.

[0649] In summary, this embodiment defines the time for Get-digest timeout / digest preparation / digest timeout, and describes the specific time definition method and reason.

[0650] Fig.39 An example of sending and receiving Get-digest and Digest messages by setting t_Get-digest, t_DigestsReady, and t_DigestsTimeout according to the present embodiment is illustrated.

[0651] -PRx must complete sending a Get-digest message to PTx within a specific time (Get-digest timeout, for example, 8.1s).

[0652] - PTx must complete preparation within a specific time (digest ready, e.g., 3 seconds) to send a response (digest) to the Get-digest message received from PRx. PTx (performing encryption function) does not respond to RP / 0 while preparing encryption. After PTx completes encryption function and digest message preparation is completed, it sends ATN.

[0653] - PTx must complete the transmission of the summary message within a specific time (Summary Timeout, for example, 43 seconds). At this time, PTx must send a correct summary message (Message Type: 0x1).

[0654] #2. Patent on the time requirement for Get-Certificate / certificate (t_Get-CertificateTimeout / t_CertificatesReady / t_CertificatesTimeout)

[0655] #2-1. Patent on the timing requirement of Get-certificate / certificate (t_Get-certificateTimeout)

[0656] - Problem: Get-certificate is an authentication message sent by the authentication initiator and does not have a timeout setting. This means that the authentication function can continue indefinitely, and when a communication error occurs, an infinite loop error occurs, the function cannot be performed normally, and it is difficult to terminate the function. In other words, a problem occurs that the function neither progresses nor terminates. Due to this, even if it is a genuine device that has been certified, since the authentication function cannot be performed, it becomes an uncertified device, so fast charging cannot be performed and only slow charging can be performed.

[0657] Fig.40 Figure 1. Example of setting t_Get-certificateTimeout to transmit Get-certificate.

[0658] The authentication initiator can send a Get-certificate for certificate message.

[0659] The Get-certificate sent by PRx (for example, 1a:08:00:00) must be sent within 13.5 seconds (t_Get-certificateTimeout = 13.5s)

[0660] The time of t_Get-certificateTimeout can be set as follows.

[0661] * tdts = maximum 1.5 seconds

[0662] * Assuming ADT / 1 data packet

[0663] * Assuming 50% for communication errors

[0664] * Set the overhead time to 20%

[0665] * t_Get-certificateTimeout = 1.5 seconds * 5 * 1.5 (communication error) * 1.2 (overhead time) = 13.5 seconds

[0666] Fig.41 Figure 10.1 shows an example of resending Get-Certificate when t_Get-CertificateTimeout expires.

[0667] refer to Fig.41 , the authentication initiator must send Get-Certificate within t_Get-CertificateTimeout, and if the timeout expires, the corresponding application message will not be received and all data stored in the buffer will be discarded.

[0668] Thereafter, the authentication initiator can send Get-Certificate again, and in this case, application data communication continues t_Get-CertificateTimeout is initialized and applied again. The authentication initiator can re-execute by initiating a Get-Certificate message.

[0669] #2-2. Patent on the time requirement for Get-certificate / certificate (t_CertificateReady)

[0670] -Problem: By setting the response (t_CertificateReady) after sending the authentication request message, a preparation time is provided for the authentication response message, and the authentication initiator needs time to prepare to receive it. Without this time, there is no time to perform the corresponding function (encryption), and the problem of time asynchrony between PRx / PTx will occur. In addition, time can be measured in packets, so it is necessary to define time at this measurable level.

[0671] The authentication responder that receives the Get-Certificate sent by the authentication initiator must send the certificate within 3 seconds (t_CertificateReady).

[0672] The time for t_CertificateReady can be set as follows.

[0673] * t_CertificateReady is measured at the following levels per packet.

[0674] - Start: Start of ADC / End packet of Get-Certificate of PRx.

[0675] - End: Start of ATN response of PTx.

[0676] *Prerequisites are as follows

[0677] - PTx must send a certificate message. (The message type of the authentication message header must be 0x2)

[0678] -After the Get-Certificates message is completed, PRx will send RP / 0 packets multiple times within 3 seconds. (For example: 3-4 times per second)

[0679] - By sending RP / 0 3-4 times per second as described above, PTx is able to send an ATN response, which is the end point of the certificate message time condition, so RP / 0 is sent 3-4 times per second to give PTx the opportunity to send ATN.

[0680] - This time is the preparation time to perform cryptographic functions such as SHA-256, hashing, and ECDSA.

[0681] - PTx does not respond to RP / 0 while performing encryption functions to send the certificate and sends an ATN response to RP / 0 when preparation is complete.

[0682] By responding to the ATN, PRx recognizes that PTx is ready to send the certificate.

[0683] #2-3. Patent on the time requirement for authentication Get-certificate / certificate (t_CertificateTimeout)

[0684] - Problem: By setting a response timeout after sending an authentication request message, the authentication response message must be sent within a specific time. This causes the authentication function to continue indefinitely, and when a communication error occurs, an infinite loop error occurs, preventing the function from being executed correctly, and it is difficult to terminate the function. In other words, a problem occurs in which the function neither progresses nor terminates. Due to this, even a genuine device that has been certified becomes an uncertified device due to the inability to perform the authentication function, thereby preventing fast charging and being able to charge only at a low speed.

[0685] The authentication responder must complete sending the certificate message within (N*0.3 + 4) seconds from the time the authentication initiator receives the Get-Certificate message. (t_Certificatetimeout)

[0686] The time for t_Certificatetimeout can be set as follows.

[0687] * PTx uses ADT / 1 data packet.

[0688] * PRx sends DSR data packets at 250ms intervals

[0689] * Assuming TPL communication error is about 20%

[0690] * Assuming PTx is sent within the min / max range of other relevant timing conditions.

[0691] * Because the certificate message can be different for each device, the variable N is added. N is the total length of the certificate, which is the total number of bytes in the certificate chain.

[0692] Fig.42 Shows an example of resending the Get-Certificate and Certificate messages when t_Certificatetimeout times out.

[0693] refer to Fig.42 , the authentication responder must send the certificate within t_Certificatetimeout, and if the timeout expires, the authentication initiator will discard all data stored in the buffer without receiving the corresponding application message.

[0694] - After that, the authentication initiator can send Get-Certificate again, and in this case, the application data communication continues t_Certificatetimeout is initialized and applied again. In other words, the authentication initiator can re-execute the function by resending the Get-Certificate message.

[0695] In summary, this embodiment defines the time for Get-Certificate timeout / certificate ready / certificate timeout, and describes the specific time definition method and reason.

[0696] Fig.43 An example of sending and receiving Get-Certificate and Certificate messages by setting t_Get-CertificateTimeout, t_CertificatesReady, and t_CertificatesTimeout according to the present embodiment is shown.

[0697] -PRx must complete sending a Get-Certificate message to PTx within a specific time (Get-Certificate timeout, for example, 13.5 seconds).

[0698] - PTx must complete preparation within a specific time (certificate ready, e.g. 3 seconds) to send a response (certificate) to the Get-Certificate message received from PRx. (Encryption function execution completed) At this time, PTx will not respond to RP / 0 while preparing encryption. After PTx completes the encryption function and the certificate message preparation is complete, it sends ATN.

[0699] - PTx must complete sending the certificate message within a specific time (certificate timeout, for example, (N*0.3+4) seconds). At this time, PTx must send the correct certificate message (message type: 0x2).

[0700] #3. Patent on timing requirements for authentication challenge / challenge_auth (t_ChallengeTimeout / t_ChallengeAuthReady / t_ChallengeAuthTimeout)

[0701] #3-1. Patent on timing requirements for authentication challenge / challenge_auth (t_challengeTimeout)

[0702] - Problem: The challenge is an authentication message sent by the authentication initiator, and there is no timeout setting. This means that the authentication function can continue indefinitely, and when a communication error occurs, an infinite loop error occurs, so the function cannot be performed normally, and it is difficult to terminate the function. In other words, there is a problem that the function neither progresses nor terminates. Due to this, even if it is a genuine device that has been authenticated, since the authentication function cannot be performed, it will become an unauthenticated device, so fast charging cannot be performed and only slow charging can be performed.

[0703] Fig.44 An example of setting t_challengeTimeout to transmit a challenge is shown.

[0704] refer to Fig.44 , the authentication initiator can send a challenge with the challenge_auth message.

[0705] The challenge sent by PRx must be sent within 51.3 seconds. (t_challengeTimeout = 51.3s)

[0706] The time of t_challengeTimeout can be set as follows.

[0707] * tdts = maximum 1.5s

[0708] * Assuming ADT / 1 data packet is used

[0709] * Assuming 50% for communication errors

[0710] * Set the overhead time to 20%

[0711] * t_challengeTimeout = 1.5s * 19 * 1.5 (communication error) * 1.2 (overhead time) = 51.3s

[0712] Fig.45 An example showing resending the challenge when t_challengeTimeout expires.

[0713] refer to Fig.45 , the authentication initiator must send the challenge within t_ChallengeTimeout, and if the time expires, the corresponding application message is not received and all data stored in the buffer are discarded.

[0714] - After this, the authentication initiator can send a challenge again, and in this case, the application data communication will continue until t_ChallengeTimeout is initialized and applied again. In other words, the authentication initiator can re-execute by initializing the challenge message.

[0715] #3-2. Patent on the time requirement (t_ChallengeReady) of authentication challenge / challenge_auth

[0716] - Problem: By setting the response (t_ChallengeReady) after sending the authentication request message, a preparation time is provided for the authentication response message, and the authentication initiator needs time to prepare to receive it. Without this time, there is no time to perform the corresponding function (encryption), and the problem of time desynchronization between PRx / PTx will occur. In addition, time can be measured in packets, so it is necessary to define time at this measurable level.

[0717] The Authentication Responder that receives a Challenge sent by the Authentication Initiator must send Challenge_Auth within 3 seconds. (t_ChallengeReady)

[0718] The time of t_ChallengeReady can be set as follows.

[0719] * t_ChallengeReady is measured per group at the following levels.

[0720] - Start: PRx polls the ADC for the start / end of a packet.

[0721] - End: Start of ATN response of PTx.

[0722] *Prerequisites are as follows

[0723] - PTx must send a Challenge_Auth message. (The message type of the authentication message header must be 0x3)

[0724] After the challenge message ends, PRx sends RP / 0 packets multiple times within 3 seconds (e.g., 3-4 times per second).

[0725] By sending RP / 0 3-4 times per second as described above, PTx is able to send an ATN response, which is the end point of the time condition of the challenge message, so RP / 0 is sent 3-4 times per second to give PTx a chance to send ATN.

[0726] This time is the preparation time to perform cryptographic functions such as SHA-256, hashing, and ECDSA.

[0727] PTx does not respond to RP / 0 while performing the encryption function to send Challenge_Auth, and sends an ATN response to RP / 0 when preparation is complete.

[0728] By responding to the ATN, the PRx recognizes that the PTx is ready to send a challenge.

[0729] #3-3. Patent on the time requirement for authentication challenge / challenge_auth (t_ChallengeAuthTimeout)

[0730] - Problem: By setting the response timeout after sending the authentication request message, the authentication response message must be sent within a specific time. This causes the authentication function to continue indefinitely, and when a communication error occurs, an infinite loop error occurs, making it difficult to correctly execute the function and difficult to terminate the function. In other words, a problem occurs that the function neither progresses nor terminates. Due to this, even if it is a genuine device that has been certified, it becomes an uncertified device because the authentication function cannot be executed, and a problem occurs that fast charging cannot be performed and only slow charging can be performed.

[0731] The authentication responder must complete sending the Challenge_Auth message within 23 seconds after the authentication initiator receives the challenge message. (t_ChallengeAuthTimeout)

[0732] The time of t_ChallengeAuthTimeout can be set as follows.

[0733] * PTx uses ADT / 1 data packet.

[0734] * PRx sends DSR data packets at 250ms intervals

[0735] * Assuming TPL communication error is about 20%

[0736] * Assuming PTx is sent within min / max range with other relevant timing conditions.

[0737] Fig.46 An example of resending Challenge and Challenge_Auth messages when t_CertificateAuthTimeout times out is shown.

[0738] refer to Fig.46, the authentication responder must send Challenge_Auth within t_CertificateAuthTimeout, and if the timeout expires, the authentication initiator discards all data stored in the buffer without receiving the corresponding application message.

[0739] Thereafter, the authentication initiator can send the challenge again, and in this case, the application data communication continues t_CertificateAuthTimeout is initialized and applied again. In other words, the authentication initiator can re-execute the function by resending the challenge message.

[0740] In summary, this embodiment defines the time of Challenge Timeout / Challenge_Auth Ready / Challenge_Auth Timeout, and describes the method and reason for defining the specific time.

[0741] Fig.47 An example of sending and receiving a challenge and a Challenge_Auth message by setting t_ChallengeTimeout, t_ChallengeAuthReady, and t_ChallengeAuthTimeout according to the present embodiment is illustrated.

[0742] -PRx must complete sending the challenge message to PTx within a certain time (challenge timeout, for example, 51.3 seconds).

[0743] - PTx must complete preparation to send a response (Challenge_Auth) to the challenge message received from PRx within a specific time (Challenge_Auth ready, for example, 3 seconds). (Cryptographic function execution completed). At this time, PTx does not respond to RP / 0 while preparing for encryption. After PTx completes the encryption function and Challenge_Auth message preparation is complete, it sends ATN.

[0744] - PTx must complete sending the Challenge_Auth message within a specific time (Challenge_Auth timeout, for example, 23 seconds). At this time, PTx must send a correct Challenge_Auth message (message type: 0x3).

[0745] The above examples can be summarized as follows.

[0746] #1. Patent on the time requirement for Get-digest / digest authentication (t_Get-Digest / t_DigestsReady / t_DigestsTimeout)

[0747] - In this embodiment, the Get-digest timeout / digest ready / digest timeout times are defined, and the specific time definition method and reason are described.

[0748] - PRx must complete sending the Get-digest message to PTx within a specific time (Get-digest timeout, for example, 8.1 seconds).

[0749] - PTx must complete preparation to send a response (digest) to a Get-digest message received from PRx within a specific time (Digest Ready, e.g., 3 seconds). (Cryptographic function execution completed)

[0750] - PTx must complete sending the summary message within a certain time (Summary Timeout, e.g., 43 seconds).

[0751] #2. Patent on the timing requirements for Get-Certificate / certificate authentication (t_Get-CertificateTimeout / t_CertificatesReady / t_CertificatesTimeout)

[0752] - In this embodiment, the time of Get-Certificate timeout / certificate ready / certificate timeout is defined, and the specific time definition method and reason are described.

[0753] - PRx must send the Get-Certificate message to PTx within a specific time (Get-Certificate timeout, for example, 13.5 seconds).

[0754] - PTx must complete preparation to send a response (certificate) to the Get-Certificate message received from PRx within a certain time (certificate ready, e.g., 3 seconds). (Cryptographic function execution completed)

[0755] - PTx must complete sending the certificate message within a certain time (certificate timeout, for example, (N*0.3+4) seconds).

[0756] #3. Patent on timing requirements for authentication challenge / challenge_auth (t_ChallengeTimeout / t_ChallengeAuthReady / t_ChallengeAuthTimeout)

[0757] - In this embodiment, the time of challenge timeout / Challenge_Auth ready / Challenge_Auth timeout is defined, and the specific time definition method and reason are described.

[0758] - PRx must send a challenge message to PTx within a certain time (challenge timeout, e.g., 51.3 seconds).

[0759] - PTx must complete preparation to send a response (Challenge_Auth) to the challenge message received from PRx within a certain time (Challenge_Auth ready, for example, 3 seconds). (Cryptographic function execution completed)

[0760] -PTx must complete sending the Challenge_Auth message within a specific time (Challenge_Auth timeout, for example, 23 seconds).

[0761] According to the above embodiment, by proposing a time requirement for authentication, the authentication completion time caused by communication errors is presented, thereby preventing the authentication function from being extended indefinitely, and if it is not completed within a specific time, it will be treated as an unauthenticated device or the corresponding function of the authentication will be restarted, thereby preventing high-speed charging from being unable to be performed due to the unauthenticated authentication device.

[0762] In addition, this embodiment can be applied to the MPP protocol as follows. That is, the name of the MPP group applied in the MPP protocol is as follows.

[0763] S-ADC (value 4: opens the data stream) can be used instead of ADC / auth packet. S-ADC (value 3: closes and completes the data stream) can be used instead of ADC / end packet.

[0764] Furthermore, since a communication error may occur for t_DigestReady / t_CertificatesReady / t_ChallengeAuthReady, the number of RP packets provided per second can be changed to 3-4 XCE or RP+ packets provided per second to provide sufficient data communication opportunities.

[0765] Hereinafter, the embodiments of the present specification will be described again from the perspectives of various subjects.

[0766] The following figures have been created to illustrate specific examples of this specification. The names of specific devices or the names of specific signals / messages / fields described in the figures are presented as examples, and therefore, the technical features of this specification are not limited to the specific names used in the figures.

[0767] Fig.48 is a flowchart of a method for receiving a response message from the perspective of a data flow initiator according to an embodiment of the present specification.

[0768] according to Fig.48, the data flow initiator enters a power delivery phase associated with sending or receiving wireless power (S4810).

[0769] The data flow initiator receives a response message from the data flow responder during the power delivery phase (S4820).

[0770] The response message is sent within the first timeout period.

[0771] The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transmission (ADT) packet, a data stream response (DSR) packet, and a communication error.

[0772] Specifically, the data flow initiator uses a 1-byte ADT packet (ADT / 1 packet), and the data flow responder sends a DSR packet at a time interval of 250ms. At this time, the communication error of the transport layer (TPL) can be set to 20%.

[0773] The start point of the first timeout period may be the start point of transmission of an auxiliary data control (ADC) packet associated with the opening of the response message. The end point of the first timeout period may be the end point of a DSR packet that is a response to an ADC packet associated with the end of the response message.

[0774] The reason why the time point of the first timeout period is set based on the ADC packet (ADC / authentication packet) related to the opening rather than the ADT packet is as follows. Since the ADC / authentication packet means data transmission of the authentication application, the request / response message in the application layer is selected as the ADC / authentication packet because conflicting messages will appear from the perspective of the application layer. However, the ADT packet can be checked separately to confirm a valid response in the authentication.

[0775] The data flow initiator may send a request message for a response message to the data flow responder.

[0776] The request message may be sent within the second timeout period.

[0777] The start point of the second timeout period may be the start point for transmission of an ADC packet associated with the opening of the request message. The end point of the second timeout period may be the end point of a DSR packet that is a response to an ADC packet associated with the end of the request message.

[0778] The data flow initiator can set a preparation period for receiving a response message.

[0779] During the preparation period, the data flow responder may perform encryption functions.During the preparation period, a receive power (RP) packet may be sent to the data flow responder three or four times per second.

[0780] The data flow responder may not respond to the RP packet (RP / 0 packet) while preparing the encryption function. When the encryption function is completed and the preparation of the response message is completed, the data flow responder may send an attention (ATN) packet. The data flow initiator can recognize that the data flow responder is ready to send the response message by receiving the ATN packet.

[0781] The start point of the preparation period may be the start point of an ADC packet related to the end of a request message. The end point of the preparation period may be the start point of an attention (ATN) packet indicating that the encryption function and preparation of a response message are completed.

[0782] The ADC packet related to the opening of the request message and the response message may be an ADC / authentication packet. The ADC packet related to the end of the request message and the response message may be an ADC / end packet.

[0783] The request message can be at least one of a GET_DIGEST message, a GET_CERTIFICATE message, and a Challenge message. The response message can be at least one of a DIGEST message, a CERTIFICATES message, and a Challenge_Auth message.

[0784] The preparation period can be at least one of t_DigestReady, t_CertificatesReady, and t_ChallengeAuthReady.

[0785] For example, if the request message is a GET_DIGEST message, the response message is a Digest message, and the preparation period is t_DigestReady, the timing requirements for authenticating Get-digest / Digest are as follows.

[0786] The data flow initiator shall send the request message within 8.1 seconds. If a timeout occurs, the data flow initiator may discard all data stored in the buffer and resend the request message by initiating a second timeout period. The data flow responder shall be ready to send a response message to the request message within 3 seconds. The data flow responder shall send a response message within 43 seconds after the request message is sent.

[0787] In addition, when the request message is a GET_CERTIFICATE message, the response message is a certificate message, and the preparation time is t_CertificatesReady, the timing requirements for authentication Get-Certificate / certificate are as follows.

[0788] The data flow initiator shall send the request message within 13.5 seconds. If this time is exceeded, the data flow initiator may discard all data stored in the buffer and resend the request message by initiating a second timeout period. The data flow responder shall be ready to send a response message to the request message within 3 seconds. The data flow responder shall send the response message within N*0.3+4 seconds after sending the request message. Here, N is an additional variable because the certificate message may be different for each device, corresponds to the total length of the certificate, and may be the total number of bytes of the certificate chain.

[0789] In addition, when the request message is a challenge message, the response message is a Challenge_Auth message, and the preparation period is t_ChallengeAuthReady, an example of the timing requirement of the authentication challenge / challenge_auth is as follows.

[0790] The data flow initiator shall send the request message within 51.3 seconds. If a timeout occurs, the data flow initiator may discard all data stored in the buffer and resend the request message by initiating a second timeout period. The data flow responder shall be ready to send a response message to the request message within 3 seconds. The data flow responder shall send a response message within 23 seconds after the request message is sent.

[0791] If the data flow initiator is a wireless power transmitter, the data flow responder may be a wireless power receiver. If the data flow initiator is a wireless power receiver, the data flow responder may be a wireless power transmitter.

[0792] Fig.49 is a flowchart of a method for sending a response message from the perspective of a data flow responder according to an embodiment of the present specification.

[0793] according to Fig.49 , the data flow responder enters a power delivery phase associated with sending or receiving wireless power (S4910).

[0794] The data flow responder sends a response message to the data flow initiator in the power delivery phase (S4920).

[0795] The response message is sent within the first timeout period.

[0796] The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transmission (ADT) packet, a data stream response (DSR) packet, and a communication error.

[0797] Specifically, the data flow initiator uses a 1-byte ADT packet (ADT / 1 packet), and the data flow responder sends a DSR packet at a time interval of 250ms. At this time, the communication error of the transport layer (TPL) can be set to 20%.

[0798] The start point of the first timeout period may be the start point of transmission of an auxiliary data control (ADC) packet associated with the opening of the response message. The end point of the first timeout period may be the end point of a DSR packet that is a response of an ADC packet associated with the end of the response message.

[0799] The reason why the time point of the first timeout period is set based on the ADC packet (ADC / authentication packet) related to the opening rather than the ADT packet is as follows. Since the ADC / authentication packet means data transmission of the authentication application, the request / response message in the application layer is selected as the ADC / authentication packet because a conflict message will come from the perspective of the application layer. However, the ADT packet can be checked separately to confirm a valid response in the authentication.

[0800] The data flow initiator may send a request message for a response message to the data flow responder.

[0801] The request message may be sent within the second timeout period.

[0802] The start point of the second timeout period may be the start point for transmission of an ADC packet associated with the opening of the request message. The end point of the second timeout period may be the end point of a DSR packet which is a response of an ADC packet associated with the end of the request message.

[0803] The data flow initiator can set a preparation period for receiving a response message.

[0804] During the preparation period, the data flow responder may perform encryption functions.During the preparation period, a receive power (RP) packet may be sent to the data flow responder three or four times per second.

[0805] While preparing for the encryption function, the data flow responder may not respond to the RP packet (RP / 0 packet). When the encryption function is completed and the preparation of the response message is completed, the data flow responder may send an attention (ATN) packet. The data flow initiator can recognize that the data flow responder is ready to send a response message by receiving the ATN packet.

[0806] The start point of the preparation period may be the start point of an ADC packet related to the end of a request message. The end point of the preparation period may be the start point of an attention (ATN) packet indicating that the encryption function and preparation of a response message are completed.

[0807] The ADC packet related to the opening of the request message and the response message may be an ADC / authentication packet. The ADC packet related to the end of the request message and the response message may be an ADC / end packet.

[0808] The request message can be at least one of a GET_DIGEST message, a GET_CERTIFICATE message, and a Challenge message. The response message can be at least one of a DIGEST message, a CERTIFICATES message, and a Challenge_Auth message.

[0809] The preparation period can be at least one of t_DigestReady, t_CertificatesReady, and t_ChallengeAuthReady.

[0810] For example, if the request message is a GET_DIGEST message, the response message is a Digest message, and the preparation time is t_DigestReady, the timing requirements for Authentication Get-digest / Digests are as follows.

[0811] The data flow initiator shall send the request message within 8.1 seconds. If a timeout occurs, the data flow initiator may discard all data stored in the buffer and resend the request message by initiating a second timeout period. The data flow responder shall be ready to send a response message to the request message within 3 seconds. The data flow responder shall send a response message within 43 seconds after the request message is sent.

[0812] In addition, when the request message is a GET_CERTIFICATE message, the response message is a certificate message, and the preparation time is t_CertificatesReady, the timing requirements for authentication Get-Certificate / certificate are as follows.

[0813] The data flow initiator shall send the request message within 13.5 seconds. If this time is exceeded, the data flow initiator may discard all data stored in the buffer and resend the request message by initiating a second timeout period. The data flow responder shall be ready to send a response message to the request message within 3 seconds. The data flow responder shall send the response message within N*0.3+4 seconds after sending the request message. Here, N is an additional variable because the certificate message may be different for each device, corresponds to the total length of the certificate, and may be the total number of bytes of the certificate chain.

[0814] In addition, when the request message is a Challenge message, the response message is a Challenge_Auth message, and the preparation period is t_ChallengeAuthReady, an example of the timing requirement of the authentication challenge / Challeng_auth is as follows.

[0815] The data flow initiator shall send the request message within 51.3 seconds. If a timeout occurs, the data flow initiator may discard all data stored in the buffer and resend the request message by initiating a second timeout period. The data flow responder shall be ready to send a response message to the request message within 3 seconds. The data flow responder shall send a response message within 23 seconds after the request message is sent.

[0816] If the data flow initiator is a wireless power transmitter, the data flow responder may be a wireless power receiver. If the data flow initiator is a wireless power receiver, the data flow responder may be a wireless power transmitter.

[0817] The effects of the present specification will be described below.

[0818] As explained above, there is no specific timing convention for exchanging application messages between the current wireless power transmitter and the wireless power receiver. Or, even if there is a relevant timing convention, the particularity of the timing convention is lacking.

[0819] That is, the wireless power receiver sends the first application message to the wireless power transmitter, and then waits indefinitely for a response to the first application message. In addition, because the current specification does not provide a time specification for the second application message as a response to the first application message, this problem (i.e., waiting indefinitely for a response) is a real problem in the wireless power transmission system.

[0820] Therefore, this specification provides rules for specific time intervals.

[0821] Therefore, according to the embodiments of the present specification, it is possible to solve the problem that a wireless power transmitter transmits a specific application message to a wireless power transmitter and waits indefinitely for a response application message thereto.

[0822] That is, even if the wireless power receiver transmits a specific application message to the wireless power transmitter and then does not receive a response application message thereto, the wireless power receiver can resend the specific application message and receive a response message after a specific time period.

[0823] In addition, this specification clearly defines the timing conventions related to the sending and receiving of application messages from the perspective of the data transmission layer.

[0824] For example, the wireless power transmitter may set a preparation period for sending the second application in response to the first application data. At this time, the preparation period is the time point at which the ADC / end packet related to the end of the first application data is received, and the reason may be as follows. This is because the reception start time of the ADC / end packet corresponds to the earliest time indicating the intention to end the first application data.

[0825] In addition, the wireless power transmitter can set the end point of the preparation period to the time point when the transmission of the ATN packet indicating the completion of the preparation of the second application data begins. At this time, the reason for setting the end point of the preparation section to the time point of the ATN packet can be, for example, as described below. The reason is that the fact that the wireless power transmitter sends the ATN packet means an attempt to transmit the second application data. That is, even if only the intention to send the second application message is expressed during the preparation period, because the transmission of the second application message is expected in the future, the time point of expressing the intention can be determined as the end point of the preparation period.

[0826] In addition, the wireless power transmitter may set a first timeout period during which the second application message must be sent. At this time, the first timeout period is the time when the transmission of the ADC / authentication packet related to the opening of the second application data starts, and the reason may be as follows. This is because the moment when the transmission of the ADC / authentication packet starts corresponds to the earliest moment indicating the intention to open the second application data.

[0827] In addition, the wireless power transmitter may set the end point of the first timeout period to the end point of the DSR / acknowledgement packet as a response to the ADC / end packet associated with the end of the second application data. At this time, the reason for setting the end point of the first timeout period to the end point of the DSR / acknowledgement packet may be, for example, as follows. The reason is that the reception of the DSR / acknowledgement packet as a response to the ADC / end packet by the wireless power transmitter means that the reception of the second application data has been completed. That is, because the reception of the second application message is completed within the first timeout period, the time point of the above-mentioned intention expression can be determined as the end point of the first timeout period.

[0828] As explained above, from the perspective of the data transmission layer, if the transmission of the second application message in response to the first application message is defined by a time agreement, a more stable authentication function can be provided between the wireless power transmitter and the wireless power receiver. In addition, communication loss can be prevented through the embodiments of the present specification, and the communication instability problem of the authentication message can be solved through the embodiments of the present specification.

[0829] The effects obtainable through the specific examples of this specification are not limited to the effects listed above. For example, a person of ordinary skill in the art may understand or derive various technical effects from this specification. Therefore, the specific effects of this specification are not limited to those explicitly described in this specification, and may include various effects that can be understood or derived from the technical features of this specification.

[0830] The claims set forth herein can be combined in a variety of ways. For example, the technical features of the method claims of this specification can be combined to implement a device, and the technical features of the device claims of this specification can be combined to implement a method. In addition, the technical features of the method claims of this specification and the technical features of the device claims can be combined to implement a device, and the technical features of the method claims of this specification and the technical features of the device claims can be combined to implement a method.

Claims

1. A method for sending a response message performed by a data flow responder in a wireless power delivery system, the method comprising: Entering a power delivery phase associated with transmitting or receiving wireless power; as well as sending the response message to the data flow initiator during the power delivery phase, wherein the response message is sent within a first timeout period, and The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transmission (ADT) packet, a data stream response (DSR) packet, and a communication error.

2. The method according to claim 1, wherein: The time point of the first timeout period is a time point of transmission of an auxiliary data control (ADC) packet associated with opening of the response message.

3. The method according to claim 1, wherein: The end point of the first timeout period is an end point of a DSR packet, and the end point of the DSR packet is a response to an ADC packet related to the end of the response message.

4. The method according to claim 1, further comprising: receiving a request message for the response message from the data flow initiator, Wherein, the request message may be sent within a second timeout period, The starting point of the second timeout period is the starting point for transmission of an ADC packet associated with the opening of the request message, The end point of the second timeout period is the end point of the DSR packet, and the end point of the DSR packet is a response to the ADC packet related to the end of the request message.

5. The method according to claim 4, further comprising: Setting a preparation period for receiving the response message, wherein during the preparation period, the data stream responder performs an encryption function, Wherein, during the preparation period, a receive power (RP) packet is sent to the data flow responder three or four times per second.

6. The method according to claim 5, wherein: The starting point of the preparation period is the starting point of the ADC packet associated with the end of the request message, The end point of the preparation period is the start point of an attention (ATN) packet indicating that the preparation of the encryption function and the response message is completed.

7. The method according to claim 6, wherein: The ADC packet associated with opening of the request message and the response message is an ADC / authentication packet, The ADC group related to the end of the request message and the response message is an ADC / end group.

8. The method according to claim 1, wherein: The request message is at least one of a GET_DIGEST message, a GET_CERTIFICATE message, and a challenge message, The response message is at least one of a DIGEST message, a CERTIFICATES message and a Challenge_Auth message.

9. The method according to claim 8, wherein: The preparation period is at least one of t_DigestReady, t_CertificatesReady, and t_ChallengeAuthReady.

10. A data stream responder in a wireless power delivery system, the data stream responder comprising: A converter associated with transmitting or receiving wireless power; as well as a communication / controller associated with controlling the transmission or reception of the wireless power, Among them, the data stream responder: Entering a power delivery phase associated with transmitting or receiving wireless power; and sending the response message to the data flow initiator during the power delivery phase, wherein the response message is sent within a first timeout period, and The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transmission (ADT) packet, a data stream response (DSR) packet, and a communication error.

11. A method for receiving a response message performed by a data flow initiator in a wireless power transfer system, the method comprising: Entering a power delivery phase associated with transmitting or receiving wireless power; as well as receiving a response message from a data flow responder during the power delivery phase, wherein the response message is sent within a first timeout period, and The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transmission (ADT) packet, a data stream response (DSR) packet, and a communication error.

12. The method according to claim 11, wherein: The time point of the first timeout period is a time point of transmission of an auxiliary data control (ADC) packet associated with opening of the response message.

13. The method according to claim 11, wherein: The end point of the first timeout period is an end point of a DSR packet, and the end point of the DSR packet is a response to an ADC packet related to the end of the response message.

14. The method according to claim 11, further comprising: sending a request message for the response message to the data stream responder, Wherein, the request message may be sent within a second timeout period, The starting point of the second timeout period is the starting point for transmission of an ADC packet associated with the opening of the request message, The end point of the second timeout period is the end point of the DSR packet, and the end point of the DSR packet is a response to the ADC packet related to the end of the request message.

15. The method according to claim 14, further comprising: Setting a preparation period for receiving the response message, wherein during the preparation period, the data stream responder performs an encryption function, Wherein, during the preparation period, a receive power (RP) packet is sent to the data flow responder three or four times per second.

16. The method according to claim 15, wherein: The starting point of the preparation period is the starting point of the ADC packet associated with the end of the request message, The end point of the preparation period is the start point of an attention (ATN) packet indicating that the preparation of the encryption function and the response message is completed.

17. The method according to claim 16, wherein: The ADC packet associated with opening of the request message and the response message is an ADC / authentication packet, The ADC group related to the end of the request message and the response message is an ADC / end group.

18. The method according to claim 11, wherein: The request message is at least one of a GET_DIGEST message, a GET_CERTIFICATE message, and a challenge message, The response message is at least one of a DIGEST message, a CERTIFICATES message and a Challenge_Auth message.

19. The method according to claim 18, wherein: The preparation period is at least one of t_DigestReady, t_CertificatesReady, and t_ChallengeAuthReady.

20. A data flow initiator in a wireless power transmission system, the data flow initiator comprising: a converter associated with transmitting or receiving wireless power; as well as a communication / controller associated with controlling the transmission or reception of the wireless power, Wherein, the data flow initiator: Entering a power delivery phase associated with transmitting or receiving wireless power; and receiving a response message from a data flow responder during the power delivery phase, wherein the response message is sent within a first timeout period, and The value of the first timeout period is set based on a time interval associated with a 1-byte auxiliary data transmission (ADT) packet, a data stream response (DSR) packet, and a communication error.