Method and apparatus for resetting and abolishing (ABORT) data communication in a wireless power transmission system

Abstract

To provide a method for transmitting wireless power.SOLUTION: The present disclosure provides a method for transmitting wireless power performed by a wireless power transmitter in a wireless power transmission system, and a device using same. The method is characterized by entering a power transmission phase associated with transmission of the wireless power, and transmitting a first data stream to a wireless power receiver during the power transmission phase, where the wireless power transmitter: transmits, to the wireless power receiver, reset information notifying of resetting of the first data stream; receives a response to the reset information from the wireless power receiver; and resets the first data stream on the basis of receiving the response.SELECTED DRAWING: Figure 27

Description

[Technical Field]

[0001] The present specification relates to wireless power transmission. [Background Art]

[0002] Wireless power transmission technology is a technology for wirelessly transmitting power between a power source and an electronic device. As an example, wireless power transmission technology enables charging of a battery of a wireless terminal simply by placing the wireless terminal such as a smartphone or a tablet on a wireless charging pad, thereby providing superior mobility, convenience, and safety compared to a wired charging environment using an existing wired charging connector. Wireless power transmission technology is attracting attention as a replacement for existing wired power transmission environments in various fields other than wireless charging for wireless terminals, including electric vehicles, various wearable devices such as Bluetooth (registered trademark) earphones and 3D glasses, home appliances, furniture, underground facilities, buildings, medical devices, robots, and leisure.

[0003] A wireless power transmission method is also referred to as a contactless power transmission method, a no point of contact power transmission method, or a wireless charging method. A wireless power transmission system may be configured of a wireless power transmitter that supplies electrical energy according to a wireless power transmission method, and a wireless power receiver that receives electrical energy wirelessly supplied from the wireless power transmitter and supplies power to a power receiving device such as a battery cell.

[0004] Wireless power transmission technologies are diverse, including methods that transmit power via magnetic coupling, radio frequency (RF), microwave, and ultrasound. Furthermore, methods based on magnetic coupling are classified into magnetic induction and magnetic resonance. Magnetic induction transmits energy by utilizing a current induced in the receiving coil by a magnetic field generated in the transmitting coil battery cell through electromagnetic coupling between the transmitting and receiving coils. Magnetic resonance is similar to magnetic induction in that it utilizes a magnetic field. However, magnetic resonance differs from magnetic induction in that resonance occurs when a specific resonant frequency is applied to the transmitting and receiving coils, and energy is transmitted through the resulting concentration of magnetic fields at both ends of the transmitting and receiving coils. [Prior art documents] [Non-patent literature] [Non-Patent Document 1] WIRELESS POWER CONSORTIUM, Qi Specification Communications Protocol, Version 1.3, January 2021, Internet URL: https: / / www.wirelesspowerconsortium.com / media / fxqpba3o / qi-v13-comms-protocol.pdf

[0005] On the other hand, this invention aims to provide a method for resetting and terminating (aborting) data communication in a wireless power transmission system, and a device that utilizes this method. [Overview of the project] [Means for solving the problem]

[0006] According to one embodiment of this specification, a method and apparatus can be provided characterized in that a wireless power transmitter transmits reset information to a wireless power receiver indicating a reset of a first data stream, the wireless power transmitter receives a response to the reset information from the wireless power receiver, and the wireless power transmitter performs a reset of the first data stream based on the receipt of the response. [Effects of the Invention]

[0007] According to this specification, the efficiency of the data transport stream is improved, and stable data communication is possible. Furthermore, according to this specification, even if the memory for data communication and storage is stuck and further recovery is impossible, a configuration is provided that performs a reset while keeping the application stream open, so that the wireless power transmitter and wireless power receiver can immediately perform data communication. Furthermore, according to this specification, even if data communication and storage are stuck and further recovery is impossible, a new data communication can be started based on a forced termination.

[0008] The effects obtained by a specific example in this specification are not limited to those listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand or derive from this specification. Thus, the specific effects of this specification are not limited to those explicitly stated herein, but may include a variety of effects that can be understood or derive from the technical features of this specification. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram of a wireless power system 10 according to one embodiment.

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

[0011] [Figure 3] This document illustrates various examples of electronic devices that incorporate wireless power transmission systems.

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

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

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

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

[0016] [Figure 8] It is a state transition diagram for explaining a wireless power transmission process.

[0017] [Figure 9] It schematically illustrates an example of a protocol for a ping phase 810.

[0018] [Figure 10] It schematically illustrates an example of a protocol for a configuration phase 820.

[0019] [Figure 11] It is a drawing illustrating message fields of a configuration (CFG) packet of a wireless power receiver according to an embodiment.

[0020] [Figure 12] It is a flowchart schematically illustrating a protocol in a negotiation phase or a re-negotiation phase according to an embodiment.

[0021] [Figure 13] It is a drawing illustrating message fields of a capabilities (CAP) packet of a wireless power transmitter according to an embodiment.

[0022] [Figure 14]This diagram schematically shows the data flow for power transmission phase 840 in the baseline protocol.

[0023] [Figure 15] A schematic flowchart of the data flow for power transmission phase 840 in the extended protocol is shown.

[0024] [Figure 16] An example of an application-level data stream between a wireless power transmitter 100 and a wireless power receiver 200 is shown.

[0025] [Figure 17] A power control method according to one embodiment is shown.

[0026] [Figure 18] This diagram schematically illustrates the structure of an MPP ID packet.

[0027] [Figure 19] This is a schematic example of an XID packet in MPP.

[0028] [Figure 20] This diagram schematically illustrates the protocol in MPP restriction mode.

[0029] [Figure 21] This is a schematic representation of the MPP full mode protocol. [Figure 22] This is a schematic representation of the MPP full mode protocol.

[0030] [Figure 23] This is a schematic example of an ADC packet.

[0031] [Figure 24] This is a schematic example of an ADT packet.

[0032] [Figure 25] This diagram schematically illustrates an example of how application messages are sent from a data stream initiator to a data stream responder.

[0033] [Figure 26] This diagram schematically illustrates the sequence of data transmission from an application perspective.

[0034] [Figure 27] This is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power according to one embodiment of this specification.

[0035] [Figure 28] This is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power, according to another embodiment of this specification.

[0036] [Figure 29] This outlines the concept of resetting a data stream.

[0037] [Figure 30] An example of reset information is shown below.

[0038] [Figure 31] A schematic example of how a wireless power transmitter sends reset information is shown.

[0039] [Figure 32] A schematic example of how a wireless power receiver transmits reset information is shown.

[0040] [Figure 33] An example of how to send reset information is shown in another form.

[0041] [Figure 34] This is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power, according to another embodiment of this specification.

[0042] [Figure 35] This outlines the concept of aborting a data stream.

[0043] [Figure 36] An example of abort information is shown below.

[0044] [Figure 37] Other examples of abort information are briefly shown below.

[0045] [Figure 38] This is a flowchart illustrating an example of a wireless power transmitter sending abort information to a wireless power receiver. [Figure 39] This is a flowchart illustrating an example of a wireless power transmitter sending abort information to a wireless power receiver.

[0046] [Figure 40] This is a flowchart illustrating an example of a wireless power transmitter sending abort information to a wireless power receiver. [Figure 41] This is a flowchart illustrating an example of a wireless power transmitter sending abort information to a wireless power receiver.

[0047] [Figure 42] Examples of other ways to send abort information are shown.

[0048] [Figure 43] This is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power, according to another embodiment of this specification.

[0049] [Figure 44] This is a flowchart illustrating a method for transmitting wireless power from the perspective of a wireless power transmitter, according to one embodiment of this specification.

[0050] [Figure 45] This is a flowchart illustrating a method for receiving wireless power from the perspective of a wireless power receiver, according to one embodiment of this specification. [Modes for carrying out the invention]

[0051] In this specification, “A or B” can mean “A only,” “B only,” or “both A and B.” Alternatively, in this specification, “A or B” can be interpreted as “A and / or B.” For example, in this specification, “A, B or C” can mean “A only,” “B only,” “C only,” or “any combination of A, B and C.”

[0052] In this specification, slashes ( / ) and commas can mean "and / or". For example, "A / B" can mean "A and / or B". Thus, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B or C".

[0053] In this specification, “at least one of A and B” can mean “A only,” “B only,” or “both A and B.” Furthermore, in this specification, the expressions “at least one of A or B” and “at least one of A and / or B” can be interpreted in the same way as “at least one of A and B.”

[0054] Furthermore, in this specification, “at least one of A, B and C” may mean “A only,” “B only,” “C only,” or “any combination of A, B and C.” Also, “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.”

[0055] Furthermore, parentheses used in this specification can mean "for example." Specifically, when "control information (PDCCH)" is used, "PDCCH" is proposed as an example of "control information." Alternatively, "control information" in this specification is not limited to "PDCCH," but rather "PDDCH" is proposed as an example of "control information." Similarly, when "control information (i.e., PDCCH)" is used, "PDCCH" is proposed as an example of "control information."

[0056] In this specification, technical features described individually within a single drawing may be embodied individually or simultaneously. The term “wireless power” as used below refers to any form of energy associated with electric, magnetic, or electromagnetic fields transmitted from a wireless power transmitter to a wireless power receiver without the use of physical electromagnetic conductors. Wireless power, also known as a wireless power signal, can mean an oscillating magnetic flux enclosed by a primary and secondary coil. For example, power conversion in a system for wirelessly charging devices including mobile phones, cordless phones, iPods®, MP3 players, and headsets is described here. Generally, the basic principles of wireless power transmission include, for example, methods of transmitting power via magnetic coupling, radio frequency (RF), microwaves, and ultrasound.

[0057] Figure 1 is a block diagram of a wireless power system 10 according to one embodiment.

[0058] Referring to Figure 1, the wireless power system 10 includes a wireless power transmitter 100 and a wireless power receiver 200.

[0059] The wireless power transmitter 100 generates a magnetic field when power is applied from an external power source (S). The wireless power receiver 200 receives power wirelessly by generating an electric current using the generated magnetic field.

[0060] Furthermore, in the wireless power system 10, the wireless power transmitter 100 and the wireless power receiver 200 can send and receive various information necessary for wireless power transmission. Here, communication between the wireless power transmitter 100 and the wireless power receiver 200 can be performed by either in-band communication, which utilizes the magnetic field used for wireless power transmission, or out-band communication, which utilizes a separate communication carrier. Out-band communication is also called out-of-band communication. Hereafter, the term out-band communication will be used consistently. Examples of out-band communication include NFC, Bluetooth (registered trademark), and BLE (Bluetooth Low Energy).

[0061] Here, the wireless power transmitter 100 can be provided in a fixed or mobile form. Examples of fixed forms include being embedded in the ceiling or wall or furniture such as a table indoors, being implanted outdoors in a parking lot, bus stop or subway station, or being installed on a means of transport such as a vehicle or train. A mobile wireless power transmitter 100 can be embodied as a mobile device of a movable weight and size, or as part of another device, such as a notebook computer cover.

[0062] Furthermore, the wireless power receiving device 200 must be interpreted as a comprehensive concept that includes various electronic devices equipped with batteries and various home appliances that are powered wirelessly instead of using power cables. Typical examples of wireless power receiving devices 200 include portable terminals, cellular phones, smartphones, personal digital assistants (PDAs), portable media players (PMPs), Wibro terminals, tablets, phablets, notebooks, digital cameras, navigation terminals, televisions, and electric vehicles (EVs).

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

[0064] Referring to Figure 2, in the wireless power system 10, there is one or more wireless power receivers 200. Although Figure 1 shows a one-to-one power exchange between the wireless power transmitter 100 and the wireless power receiver 200, as shown in Figure 2, it is also possible for one wireless power transmitter 100 to transmit power to multiple wireless power receivers 200-1, 200-2, ..., 200-M. In particular, when wireless power transmission is performed using a magnetic resonance method, one wireless power transmitter 100 can simultaneously transmit power to multiple wireless power receivers 200-1, 200-2, ..., 200-M by applying simultaneous transmission or time-division transmission methods.

[0065] Furthermore, although Figure 1 shows a method in which the wireless power transmitter 100 directly transmits power to the wireless power receiver 200, a separate wireless power transceiver or repeater may be provided between the wireless power transmitter 100 and the wireless power receiver 200 to increase the wireless power transmission distance. In this case, power is transmitted from the wireless power transmitter 100 to the wireless power transceiver, and the wireless power transceiver can then transmit power back to the wireless power receiver 200.

[0066] Hereinafter, the terms "wireless power receiver," "power receiver," and "receiver" as used herein refer to the wireless power receiving device 200. Similarly, the terms "wireless power transmitter," "power transmitter," and "transmitter" as used herein refer to the wireless power receiving and transmitting device 100.

[0067] Figure 3 shows various examples of electronic devices into which a wireless power transmission system is implemented.

[0068] Figure 3 shows a classification of electronic devices based on the amount of power transmitted and received by the wireless power transmission system. Referring to Figure 3, low-power (approximately 5W or less or approximately 20W or less) wireless charging methods can be applied to wearable devices such as smart watches, smart glasses, HMDs (Head Mounted Displays), and smart rings, as well as mobile electronic devices (or portable electronic devices) such as earphones, remote controls, smartphones, PDAs, and tablet PCs.

[0069] Medium- and small-sized home appliances such as notebooks, robotic vacuum cleaners, TVs, audio equipment, and monitors can be charged using a medium-power (approximately 50W or less or approximately 200W or less) wireless charging method. Kitchen appliances such as blenders, microwave ovens, and electric rice cookers, as well as personal mobility devices (or electronic devices / means of transportation) such as wheelchairs, electric scooters, electric bicycles, and electric vehicles, can be charged using a high-power (approximately 2kW or less or 22kW or less) wireless charging method.

[0070] The aforementioned electronic devices / mobile devices (or those shown in Figure 1) may each include a wireless power receiver, which will be described later. Therefore, the aforementioned electronic devices / mobile devices can be charged by receiving power wirelessly from a wireless power transmitter.

[0071] The following description will focus on mobile devices to which wireless power charging is applied, but this is merely an example, and the wireless charging method described herein can be applied to the various electronic devices mentioned above.

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

[0073] The WPC standard defines a baseline power profile (BPP) and an extended power profile (EPP). The BPP pertains to wireless power transmitters and receivers that support 5W of power transmission, while the EPP pertains to wireless power transmitters and receivers that support power transmission in the range of greater than 5W and less than 30W.

[0074] A variety of wireless power transmitters and receivers using different power levels are covered by each standard and can be classified into different power classes or categories.

[0075] For example, WPC classifies wireless power transmitters and receivers into power class (PC)-1, PC0, PC1, and PC2, and provides standard documentation for each PC. The PC-1 standard concerns wireless power transmitters and receivers that provide guaranteed power of less than 5W. Applications of PC-1 include wearable devices such as smartwatches.

[0076] The PC0 standard relates to wireless power transmitters and receivers that provide a guaranteed power of 5W. The PC0 standard includes EPP, which provides a guaranteed power of up to 30W. In-band (IB) communication is the mandatory communication protocol for PC0, and out-band (OB) communication can also be used as an optional backup channel. Wireless power receivers can identify whether they support OB by setting an OB flag in a configuration packet. Wireless power transmitters that support OB can enter the OB handover phase by sending a bit pattern for OB handover in response to the configuration packet. The response to the configuration packet is NAK, ND, or a newly defined 8-bit pattern. PC0 applications include smartphones.

[0077] The PC1 standard relates to wireless power transmitters and receivers providing guaranteed power of 30W to 150W. OB is the essential communication channel for PC1, and IB is used for initialization and link establishment to OB. The wireless power transmitter can enter the OB handover phase using a bit pattern for OB handover in response to a configuration packet. PC1 applications include laptops and power tools.

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

[0079] In this way, PCs can be distinguished by their power levels, and supporting compatibility between the same PCs is either optional or mandatory. Here, compatibility between the same PCs means that power can be transmitted and received between the same PCs. For example, if a wireless power transmitter, which is PCx, can charge a wireless power receiver that has the same PCx, then compatibility between the same PCs can be maintained. Similarly, compatibility between different PCs can also be supported. Here, compatibility between different PCs means that power can be transmitted and received between different PCs. For example, if a wireless power transmitter, which is PCx, can charge a wireless power receiver that has PCy, then compatibility between different PCs can be maintained.

[0080] Supporting PC compatibility is a crucial issue from both a user experience and infrastructure construction perspective. However, maintaining PC compatibility presents numerous technical challenges, as outlined below.

[0081] In the case of compatibility between devices of the same PC type, for example, a laptop-charging wireless power receiver, which can only reliably charge when power is transmitted continuously, will have problems receiving a stable power supply from a wireless power transmitter of the same PC type, even if the transmitter is of the same PC type, when the transmitter uses an electric tool type that transmits power discontinuously. Also, in the case of compatibility between devices of different PC types, for example, if a wireless power transmitter with a minimum guaranteed power of 200W transmits power to a wireless power receiver with a maximum guaranteed power of 5W, there is a risk of the receiver being damaged due to overvoltage. As a result, PCs are difficult to define as a representative / indicating indicator / standard for compatibility.

[0082] Wireless power transmitters and receivers can provide a considerably convenient user experience and interface (UX / UI). Specifically, a smart wireless charging service can be provided. This smart wireless charging service can be implemented based on the UX / UI of a smartphone, including the wireless power transmitter. For such applications, the interface between the smartphone's processor and the wireless charging receiver allows for "drop-and-play" bidirectional communication between the wireless power transmitter and receiver.

[0083] As an example, a user can experience a smart wireless charging service at a hotel. When the user enters their hotel room and places their smartphone on the room's wireless charger, 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 located on the wireless charger, or detects that it has received wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone enters a state where it asks the user to consent to additional features (opt-in). To this end, the smartphone can display a message on the screen, with or without an alarm. An example message may include text such as, "Welcome to ### hotel. Select "Yes" to activate smart charging functions: Yes | No Thanks." The smartphone receives the user's input to select Yes or No Thanks and performs the next step selected by the user. If Yes is selected, the smartphone transmits the relevant information to the wireless charger. Then, the smartphone and wireless charger work together to perform the smart charging function.

[0084] Additionally, the smart wireless charging service uses Wi-Fi. Authentication information(Wi-Fi credentials) may include devices that receive auto-filled information. For example, a wireless charger may receive Wi-Fi credentials. Authentication information The data is sent to the smartphone, and the smartphone receives the WiFi signal from the wireless charger by running the appropriate app. Authentication information This will be entered automatically.

[0085] Furthermore, smart wireless charging services may include running hotel applications that offer hotel promotions, or that retrieve remote check-in / check-out and contact information.

[0086] As another example, a user can experience a smart wireless charging service in a vehicle. When a user gets into the vehicle and places their smartphone on a wireless charger, 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 located on the wireless charger, or detects that it has received wireless power, or when the smartphone receives information about the smart wireless charging service from the wireless charger, the smartphone enters a state where it requests identity verification from the user.

[0087] In this state, the smartphone automatically connects to the car via Wi-Fi and / or Bluetooth. The smartphone can display messages on its screen, with or without alarms. An example message could include text such as, "Welcome to your car. Select "Yes" to synchronize device with in-car controls: Yes|No Thanks." The smartphone receives user input to select Yes or No Thanks and then performs the next step selected by the user. If Yes is selected, the smartphone sends the corresponding information to the wireless charger. The smartphone and wireless charger can then work together to perform smart control functions in the vehicle by driving the in-vehicle application / display software. The user can enjoy their desired music and check their official map location. The in-vehicle application / display software may include the ability to provide synchronized proximity for pedestrians.

[0088] As another example, a user can experience smart wireless charging in their home. When a user enters a room and places their smartphone on a 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 to the smartphone regarding the smart wireless charging service. When the smartphone detects that it is located on the wireless charger, or detects that it has received wireless power, or when the smartphone receives information regarding the smart wireless charging service from the wireless charger, the smartphone enters a state where it asks the user to consent to additional features (opt-in). To this end, the smartphone can display a message on its screen, with or without an alarm. An example message might include text such as, "Hi xxx, Would you like to activate night mode and secure the building?: Yes|No Thanks." The smartphone receives input from the user to select Yes or No Thanks and performs the next step selected by the user. If Yes is selected, the smartphone transmits the relevant information to the wireless charger. The smartphone and wireless charger can recognize at least the user's patterns and encourage the user to lock doors and windows, turn off power, or set alarms.

[0089] Below, we define a new 'profile' as an indicator / criterion representing / indicating compatibility. That is, it can be interpreted that compatible and stable power transmission / reception are possible between wireless power transceivers having the same 'profile', while power transmission / reception is not possible between wireless power transceivers having different 'profiles'. Profiles can be defined by compatibility and / or application, regardless of (or independently of) power class.

[0090] The profiles can be broadly divided into three categories: i) mobile and computer, ii) power tools, and iii) kitchen.

[0091] Alternatively, the profiles can be broadly divided into four categories: i) mobile, ii) power tools, iii) kitchen, and iv) wearable.

[0092] For the 'Mobile' profile, the PC can be defined as PC0 and / or PC1, the communication protocol / method as IB and OB, and the operating frequency as 87-205kHz. Examples of applications include smartphones and laptops.

[0093] For the 'Power Tools' profile, the PC can be defined as PC1, the communication protocol / method as IB, and the operating frequency as 87-145kHz. Examples of applications can include power tools.

[0094] For the 'Kitchen' profile, the PC can be defined as PC2, the communication protocol / method as NFC-based, and the operating frequency as less than 100kHz. Examples of applications can include kitchen / home appliances.

[0095] For power tools and kitchen profiles, NFC communication can be used between the wireless power transmitter and receiver. The wireless power transmitter and receiver can confirm that they are NFC devices by exchanging WPC NDEF (NFC Data Exchange Profile Format).

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

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

[0098] The base station 400 is a device that provides inductive or resonant power and may include at least one power transmitter 100 and a system circuit 405. The power transmitter 100 can transmit and control the transmission of inductive or resonant power. The power transmitter 100 may include a power conversion circuit 110 that converts electrical energy into a power signal by generating a magnetic field through primary coils, and a communications and control circuit 120 that controls communication with and power transmission to the power receiver 200 to transmit power at an appropriate level. The system circuit 405 can perform input power provisioning, control of multiple power transmitters, and other operational controls of the base station 400, such as user interface control.

[0099] The primary coil can generate an electromagnetic field using alternating current (AC) power (or voltage or current). The primary coil receives AC power (or voltage or current) of a specific frequency output from the power conversion circuit 110, thereby generating a magnetic field of a specific frequency. The magnetic field can be generated in a non-radiative or radiative manner, and the wireless power receiver 200 receives it and generates a current. In other words, the primary coil transmits power wirelessly.

[0100] In magnetic induction systems, the primary and secondary coils can take any suitable form, such as copper wire wound around a highly permeable material like ferrite or amorphous metal. The primary coil is sometimes called the transmitting coil, primary core, primary winding, or primary loop antenna. The secondary coil, on the other hand, is sometimes called the receiving coil, secondary core, secondary winding, secondary loop antenna, or pickup antenna.

[0101] When using a magnetic resonance method, the primary and secondary coils can be provided in the form of a primary resonant antenna and a secondary resonant antenna, respectively. The resonant antenna can have a resonant structure including a coil and a capacitor. In this case, the resonant frequency of the resonant antenna is determined by the inductance of the coil and the capacitance of the capacitor. Here, the coil can be in the form of a loop, and a core can be placed inside the loop. The core can be a physical core such as a ferrite core or an air core.

[0102] Energy transmission between a primary and secondary resonant antenna can occur via magnetic resonance. Resonance refers to the phenomenon where, when a near-field corresponding to the resonant frequency is generated in one resonant antenna, and other resonant antennas are located around it, the two resonant antennas are coupled to each other, resulting in highly efficient energy transfer between them. When a magnetic field corresponding to the resonant frequency is generated between the primary and secondary resonant antennas, the primary and secondary resonant antennas resonate with each other. As a result, the magnetic field is directed toward the secondary resonant antenna with higher efficiency than, in general, when the magnetic field generated by the primary resonant antenna is radiated into free space, and therefore, energy can be transmitted from the primary to the secondary resonant antenna with high efficiency. The magnetic induction method can be implemented in a manner similar to the magnetic resonance method, but in this case, the frequency of the magnetic field does not need to be the resonant frequency. Instead, the magnetic induction method requires matching between the loops constituting the primary and secondary coils, and the distance between the loops must be considerably close.

[0103] Although not shown in the drawings, the wireless power transmitter 100 may further include a communication antenna. The communication antenna can transmit and receive communication signals using communication carriers other than magnetic field communication. For example, the communication antenna can transmit and receive communication signals such as Wi-Fi®, Bluetooth®, Bluetooth LE, ZigBee®, and NFC.

[0104] The communication / control circuit 120 can send and receive information with the wireless power receiver 200. The communication / control circuit 120 may include at least one of either an IB communication module or an OB communication module.

[0105] An IB communication module can transmit and receive information using magnetic waves with a specific frequency as its center frequency. For example, the communication / control circuit 120 can perform in-band communication by including communication information in the operating frequency of wireless power transmission and transmitting it via the primary coil, or by receiving the operating frequency containing the information via the primary coil. In this case, modulation schemes such as binary phase shift keying (BPSK), frequency shift keying (FSK), or amplitude shift keying (ASK), and coding schemes such as Manchester coding or non-return-to-zero level (NZR-L) coding can be used to include information in the magnetic wave or to interpret the magnetic wave containing the information. Using such IB communication, the communication / control circuit 120 can transmit and receive information over distances of several meters at a data transmission rate of several kbps.

[0106] OB communication modules can also perform out-band communication via a communication antenna. For example, the communication / control circuit 120 can be provided by a short-range communication module. Examples of short-range communication modules include Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

[0107] The communication / control circuit 120 can control the overall operation of the wireless power transmitter 100. The communication / control circuit 120 can perform calculations and processing of various information and control each component of the wireless power transmitter 100.

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

[0109] The communication / control circuit 120 can control the transmitted power by controlling the operating point. The operating point to be controlled can be a combination of frequency (or phase), duty cycle, duty ratio, and voltage amplitude. The communication / control circuit 120 can control the transmitted power by adjusting at least one of the frequency (or phase), duty cycle, duty ratio, and voltage amplitude. In addition, the wireless power transmitter 100 can supply a constant power, and the wireless power receiver 200 can control the received power by controlling the resonant frequency.

[0110] On the other hand, in a WPC system, the wireless power transmitter 100 can be classified, for example, in terms of power transmission amount. In this case, a wireless power transmitter 100 that supports a maximum wireless power transmission amount of 5W (i.e., a wireless power transmitter 100 that supports the BPP protocol) can be classified, for example, into type A wireless power transmitter 100 and type B wireless power transmitter 100, and a wireless power transmitter 100 that supports a maximum wireless power transmission amount of 15W (i.e., a wireless power transmitter 100 that supports the EPP protocol) can be classified, for example, into type MP-A wireless power transmitter 100 and type MP-B wireless power transmitter 100.

[0111] - Type A and Type MP A wireless power transmitter 100

[0112] A Type A and Type MP A wireless power transmitter 100 may have one or more primary coils. Since a Type A and Type MP A wireless power transmitter 100 activates a single primary coil at a time, a single primary cell matching the activated primary coil may be used.

[0113] -Type B and Type MP B wireless power transmitter 100

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

[0115] The mobile device 450 includes a power receiver 200 that receives wireless power via a secondary coil, and a load 455 that receives and stores the power received by the power receiver 200 and supplies it to the device.

[0116] The wireless power receiver 200 may include a power pickup circuit 210 and a communications and control circuit 220. The power pickup circuit 210 can receive wireless power via a secondary coil and convert it into electrical energy. The power pickup circuit 210 rectifies the AC signal obtained via the secondary coil and converts it into a DC signal. The communications and control circuit 220 can control the transmission and reception (power transfer and reception) of wireless power.

[0117] The secondary coil can receive wireless power transmitted by the wireless power transmitter 100. The secondary coil can receive power by utilizing the magnetic field generated by the primary coil. Here, if a specific frequency is the resonant frequency, a magnetic resonance phenomenon occurs between the primary and secondary coils, allowing for more efficient power transmission.

[0118] On the other hand, although not shown in Figure 4, the communication / control circuit 220 may further include a communication antenna. The communication antenna can transmit and receive communication signals using communication carriers other than magnetic field communication. For example, the communication antenna can transmit and receive communication signals such as Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

[0119] The communication / control circuit 220 can send and receive information with the wireless power transmitter 100. The communication / control circuit 220 may include at least one of either an IB communication module or an OB communication module.

[0120] An IB communication module can transmit and receive information using magnetic waves with a specific center frequency. For example, the communication / control circuit 220 can perform IB communication by embedding information in a magnetic wave and transmitting it via a secondary coil, or by receiving a magnetic wave containing information via a secondary coil. In this case, modulation schemes such as binary phase shift keying (BPSK), frequency shift keying (FSK), or amplitude shift keying (ASK), and coding schemes such as Manchester coding or non-return-to-zero level (NZR-L) coding can be used to embed information in a magnetic wave or to interpret a magnetic wave containing information. Using such IB communication, the communication / control circuit 220 can transmit and receive information over distances of several meters at a data transmission rate of several kbps.

[0121] The OB communication module can also perform out-band communication via a communication antenna. For example, the communication / control circuit 220 can be provided in the short-range communication module.

[0122] Examples of short-range communication modules include Wi-Fi, Bluetooth, Bluetooth LE, ZigBee, and NFC.

[0123] The communication / control circuit 220 can control the overall operation of the wireless power receiver 200. The communication / control circuit 220 can perform calculations and processing of various information and control each component of the wireless power receiver 200.

[0124] The communication / control circuit 220 can be implemented in a computer or similar device using hardware, software, or a combination thereof. Hardware-wise, the communication / control circuit 220 can be provided in the form of an electronic circuit that processes electrical signals to perform control functions; software-wise, it can be provided in the form of a program that drives the hardware-based communication / control circuit 220.

[0125] If the communication / control circuit 120 and the communication / control circuit 220 are Bluetooth or Bluetooth LE as OB communication modules or short-range communication modules, then the communication / control circuit 120 and the communication / control circuit 220 can be implemented and operated with the communication architecture shown in Figure 5.

[0126] Figure 5 shows an example of a Bluetooth communication architecture to which one embodiment of this specification can be applied.

[0127] Referring to Figure 5, (a) in Figure 5 shows an example of a Bluetooth BR (Basic Rate) / EDR (Enhanced Data Rate) protocol stack that supports GATT, and (b) shows an example of a Bluetooth LE (Low Energy) protocol stack.

[0128] Specifically, as shown in Figure 5(a), the Bluetooth BR / EDR protocol stack may include an upper controller stack 460 and a lower host stack 470, relative to the host controller interface (HCI, 18).

[0129] The host stack (or host module) 470 refers to a wireless transceiver module that receives 2.4GHz Bluetooth signals and hardware for transmitting or receiving Bluetooth packets, and the controller stack 460 is connected to the Bluetooth module and controls the Bluetooth module to perform its operations.

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

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

[0132] The aforementioned BR / EDR Baseband layer 14 is responsible for transmitting the digital signal, selecting a channel sequence that hops 1400 times per second, and transmitting a time slot of 625us for each channel.

[0133] The aforementioned link manager hierarchy 16 utilizes LMP (Link Manager Protocol) to control the overall operation of the Bluetooth Connection (link setup, control, security).

[0134] The aforementioned link manager hierarchy 16 can perform the following functions:

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

[0136] -Detach: Interrupts the connection and notifies the other device of the reason for the interruption.

[0137] - Perform power control and role switching.

[0138] - Executes security functions (authentication, pairing, encryption).

[0139] The host-controller interface hierarchy 18 provides an interface between the host module and the controller module, enabling the host to provide commands and data to the controller, and the controller to provide events and data to the host.

[0140] The host stack (or host module) 20 includes a Logical Link Control and Adaptive 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.

[0141] The Logical Link Control and Adaptive Protocol (L2CAP) 21 can provide a single bidirectional channel for transmitting data to a specific protocol or profile.

[0142] The aforementioned L2CAP21 can multiplex various protocols and profiles provided at the Bluetooth level.

[0143] Bluetooth BR / EDR's L2CAP utilizes dynamic channels, supports protocol service multiplexer, retransmission, and streaming modes, and provides segmentation and reassembly, per-channel flow control, and error control.

[0144] The General Attribute Profile (GATT) 23 can function as a protocol that describes how the Attribute Protocol 22 is used when configuring a service. For example, the General Attribute Profile 23 can function to define how ATT attributes are grouped together as a service, and can function to describe features associated with a service.

[0145] Therefore, the general attribute profile 23 and the attribute protocol (ATT) 22 can use features to describe the state and services of a device, and to explain how features relate to each other and how they are used.

[0146] The attribute protocol 22 and the BR / EDR profile 25 define the service (profile) that utilizes Bluetooth BR / EDR and the application protocol for exchanging this data, while the Generic Access Profile (GAP) 24 defines device discovery, connection, and security levels.

[0147] As shown in Figure 5(b), the Bluetooth LE protocol stack includes a controller stack 480 capable of handling timing-sensitive radio device interfaces and a host stack 490 capable of handling high-level data.

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

[0149] The host stack 490 is part of an OS running on a processor module, or can be realized by instantiation of a package on the OS.

[0150] In some cases, the controller stack and the host stack can operate or run on the same processing device within the processor module.

[0151] The controller stack 480 includes a Physical Layer (PHY) 32, a Link Layer 34, and a Host Controller Interface 36.

[0152] The aforementioned physical layer (PHY, radio transceiver module) 32 is a layer that transmits and receives 2.4GHz radio signals and uses GFSK (Gaussian Frequency Shift Keying) modulation and a frequency hopping technique consisting of 40 RF channels.

[0153] The link layer 34, which is responsible for transmitting or receiving Bluetooth packets, generates a device-to-device connection after performing advertising and scanning functions using three advertising channels, and provides the ability to exchange data packets of up to 257 bytes via 37 data channels.

[0154] The host stack may include a Generic Access Profile (GAP) 40, a Logical Link Control and Adaptive Protocol (L2CAP) 41, a Security Manager (SM) 42, an Attribute Protocol (ATT) 440, a Generic Attribute Profile (GATT) 44, a Generic Access Profile 25, and an LT profile 46. However, the host stack 490 is not limited to these and may include a variety of protocols and profiles.

[0155] The host stack uses L2CAP to multiplex various protocols and profiles provided above Bluetooth.

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

[0157] The L2CAP41 may be capable of multiplexing data between higher-layer protocols, segmenting and reassembling packages, and managing multicast data transmission.

[0158] Bluetooth LE typically uses three fixed channels (one for the signaling channel, one for the Security Manager, and one for the Attribute protocol). Dynamic channels may also be used as needed.

[0159] On the other hand, BR / EDR (Basic Rate / Enhanced Data Rate) primarily uses dynamic channels and supports protocol service multiplexer, retransmission, and streaming modes.

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

[0161] ATT (Attribute Protocol) 43 defines rules for accessing data from a remote device in a server-client structure. ATT has the following six message types: Request, Response, Command, Notification, Indication, and Confirmation.

[0162] (1) Request and Response messages: A Request message is a message used to request and transmit specific information from a client device to a server device, and a Response message is a response message to a Request message that can be used to send from a server device to a client device.

[0163] (2) Command message: A message sent from a client device to a server device, primarily to instruct it to perform a specific action, and the server device does not send a response to the Command message to the client device.

[0164] (3) Notification message: A message sent from a server device to a client device for notification purposes, such as an event, and the client device does not send a confirmation message to the server device in response to the notification message.

[0165] (4) Indication and Confirm messages: These are messages sent from the server device to the client device for notification purposes, such as events. Unlike notification messages, the client device sends a confirmation message to the server device in response to the Indication message.

[0166] This specification describes how, when a GATT profile using the attribute protocol (ATT) 43 requests long data, a value for the data length can be sent so that the client can clearly understand the data length, and a characteristic value can be received from the server using a UUID.

[0167] The General Proximity Profile (GAP) 45 is a newly embodied hierarchy for Bluetooth LE technology and is used to control how role selection and multi-profile operation occur for communication between Bluetooth LE devices.

[0168] Furthermore, the general proximity profile 45 is primarily used in the device discovery, connection generation, and security procedure sections, defining a way to provide information to the user and defining the following attribute types.

[0169] (1) Service: Defines the basic operation of the device by combining data and associated behaviors.

[0170] (2) Include: Defines the relationships between services.

[0171] (3) Characteristics: Data values ​​used in the service

[0172] (4) Behavior: A computer-readable format defined by a UUID (Universal Unique Identifier, value type).

[0173] The aforementioned LE profile 46 is a GATT-dependent profile and is mainly applied to Bluetooth LE devices. Examples of LE profiles 46 include Battery, Time, FindMe, Proximity, and Time, and the specific contents of GATT-based profiles are as follows.

[0174] (1) Battery: Battery information exchange method

[0175] (2) Time: Method of exchanging time information

[0176] (3) FindMe: Provides distance-based alarm service

[0177] (4) Proximity: Battery information exchange method

[0178] (5) Time: Method of exchanging time information

[0179] The General Attribute Profile (GATT) 44 may function as a protocol describing how the Attribute Protocol 43 is used when configuring a service. For example, the General Attribute Profile 44 may function to specify how ATT attributes are grouped together as a service, and may function to describe the characteristics associated with the service.

[0180] Therefore, the general attribute profile 44 and the attribute protocol (ATT) 43 can use features to describe the state and services of a device and to explain how features relate to each other and how they are used.

[0181] The following is a brief explanation of the Bluetooth Low Energy (BLE) technology procedure.

[0182] BLE procedures can be divided into procedures such as Device Filtering Procedure, Advertising Procedure, Scanning Procedure, Discovering Procedure, and Connecting Procedure.

[0183] Device Filtering Procedure

[0184] Device filtering procedures are a method to reduce the number of devices in the controller stack that perform responses to requests, instructions, notifications, etc.

[0185] Since not all devices need to respond to a request when it is received, the controller stack can reduce the number of requests sent, thereby reducing power consumption on the BLE controller stack.

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

[0187] Here, an advertising device refers to a device that sends advertising events, that is, a device that executes advertisements, and is also referred to as an advertiser.

[0188] A scanning device refers to a device that performs scanning and sends scan requests.

[0189] In BLE, when a scanning device receives some advertising packets from an advertising device, the scanning device is required to send a scan request to the advertising device.

[0190] However, if a device filtering procedure is used and sending a scan request is unnecessary, the scanning device can ignore the advertising packets sent from the advertising device.

[0191] Device filtering procedures can also be used during the connection request process. If device filtering is used during the connection request process, it becomes unnecessary to send a response to the connection request by ignoring it.

[0192] Advertising Procedure

[0193] The advertising device executes advertising procedures to perform omnidirectional broadcasting to devices within its area.

[0194] Here, undirected advertising is advertising directed at all devices, not specific devices, allowing all devices to scan the advertisement and request additional information or connection.

[0195] In contrast, Directed advertising can scan for advertisements only on devices designated as receiving devices, and then request additional information or connections.

[0196] The advertising procedure is used to establish a Bluetooth connection with a nearby starting device.

[0197] Alternatively, the advertising procedure can be used to provide periodic broadcasts of user data to scanning devices that are listening on advertising channels.

[0198] In the advertising process, all advertisements (or advertising events) are broadcast via physical advertising channels.

[0199] An advertising device can receive scan requests from listening devices that are performing listening in order to obtain additional user data from the advertising device. The advertising device sends a response to the scan request to the device that sent the scan request via the same advertising physical channel that received the scan request.

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

[0201] An advertising device can receive connection requests from an initiating device on the physical advertising (broadcast) channel. If an advertising device uses an available advertising event and the initiating device is not filtered by the device filtering procedure, the advertising device will stop the advertisement and proceed to connected mode. The advertising device can start advertising again after entering connected mode.

[0202] Scanning Procedure

[0203] A scanning device performs a scanning procedure to listen to an omnidirectional broadcast of user data from an advertising device that uses an advertising physical channel.

[0204] The scanning device sends a scan request to the advertising device via the advertising physical channel to request additional data from the advertising device. The advertising device sends a scan response, which is a response to the scan request, via the advertising physical channel, containing the additional data requested by the scanning device.

[0205] The aforementioned scanning procedure can be used while connecting with other BLE devices via a BLE piconet.

[0206] If the scanning device is in initiator mode, which allows it to receive broadcast advertising events and initiate connection requests, it can initiate a Bluetooth connection with the advertising device by sending a connection request to the advertising device via the physical advertising channel.

[0207] When a scanning device sends a connection request to an advertising device, the scanning device stops initiator mode scanning for additional broadcasts and proceeds to connection mode.

[0208] Discovering Procedure

[0209] Bluetooth-enabled devices (hereinafter referred to as "Bluetooth devices") perform advertising and scanning procedures to discover nearby devices or to be discovered by other devices within a given area.

[0210] The discovery process is performed asymmetrically. A Bluetooth device that attempts to find other devices in its vicinity is called a discovering device, and it listens to find devices advertising scannable advertising events. A Bluetooth device that is discovered and available to other devices is called a discoverable device, and it actively broadcasts advertising events via advertising (broadcast) physical channels so that other devices can scan them.

[0211] Both the discovering device and the discoverable device can already be connected to other Bluetooth devices via piconet.

[0212] Connection procedure

[0213] The connection procedure is asymmetrical, requiring one Bluetooth device to perform an advertising procedure while another Bluetooth device performs a scanning procedure.

[0214] In other words, the advertising procedure can be the objective, and as a result, only one device should respond to the advertisement. After receiving a connectable advertising event from the advertising device, a connection can be initiated by sending a connection request to the advertising device via the advertising (broadcast) physical channel.

[0215] Next, we will briefly explain the operating states in BLE technology, namely the Advertising State, Scanning State, Initiating State, and Connection State.

[0216] Advertising State

[0217] The Link Layer (LL) enters the advertising state at the direction of the host (stack). When the Link Layer is in the advertising state, it sends advertising PDUs (Packet Data Circuits) from advertising events, etc.

[0218] Each ad event consists of at least one ad PDU, which is sent via the ad channel index being used. Once each ad event has been sent via the ad channel index being used, the ad event can be terminated earlier if it is finished or if the ad device needs to make space for other functions to run.

[0219] Scanning State

[0220] The link hierarchy enters a scanning state at the host's (stack's) instruction. While scanning, the link hierarchy listens to the ad channel index.

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

[0222] No separate time or advertising channel index is defined for scanning.

[0223] During the scanning process, the link hierarchy listens for ad channel indices for a scan window duration. The scan interval is defined as the interval between the start points of two consecutive scan windows.

[0224] The link hierarchy must listen for the completion of all scan intervals within a scan window, as instructed by the host, provided there are no scheduling conflicts. Within each scan window, the link hierarchy must scan other ad channel indexes. The link hierarchy uses all available ad channel indexes.

[0225] In passive scanning, the link hierarchy only receives packets and cannot transmit any packets.

[0226] When scanning is active, the link hierarchy listens to ad PDU types that can request ad PDUs and additional ad device-related information from ad devices.

[0227] Initiating State

[0228] The link hierarchy enters the starting state at the instruction of the host (stack).

[0229] When the link hierarchy is in the starting state, it listens to the ad channel index.

[0230] During the initial state, the link hierarchy listens for the ad channel index during the scan window interval.

[0231] Connection state

[0232] The link hierarchy enters a connected state when the device making the connection request, i.e., 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.

[0233] Once a connection state is entered, it is assumed that the connection has been created. However, it is not necessary to assume that the connection was established at the time it entered the connection state. The only difference between a newly created connection and a pre-established connection is the link hierarchy connection supervision timeout value.

[0234] When both devices are connected, they perform different roles.

[0235] A link hierarchy that acts as the master is called the master, and a link hierarchy that acts as the slave is called the slave. The master coordinates the timing of connection events, which are the points in time when the master and slave are synchronized.

[0236] The following briefly describes the packets defined in the Bluetooth interface. BLE devices use the packets defined below.

[0237] Packet Format

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

[0239] Each packet consists of four fields: the preamble, the access address, the PDU (Packet Data Unit), and the CRC (Color Code).

[0240] When a packet is sent from an advertising physical channel, the PDU should be an advertising channel PDU, and when a packet is sent from a data physical channel, the PDU should be a data channel PDU.

[0241] Advertising Channel PDU (Advertising Channel PDU)

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

[0243] The PDU type field of the ad channel PDU included in the header indicates a PDU type as defined in Table 1 below.

[0244] [Table 1]

[0245] Advertising PDU (Advertising PDU)

[0246] The following ad channel PDU types are called ad PDUs and are used for specific events.

[0247] ADV_IND: Connectable Omnidirectional Ad Events

[0248] ADV_DIRECT_IND: Connectable directional advertising events

[0249] ADV_NONCONN_IND: Unable to connect to omnidirectional ad event

[0250] ADV_SCAN_IND: Scannable Omnidirectional Ad Event

[0251] The aforementioned PDU is transmitted from the Link Layer in advertising state and received by the Link Layer in scanning state or initiating state.

[0252] Scanning PDU

[0253] The following advertising channel PDU types are called scanning PDUs and are used in the conditions described below.

[0254] SCAN_REQ: Sent via the link hierarchy in scanning mode, and received via the link hierarchy in advertisement mode.

[0255] SCAN_RSP: Sent via the link hierarchy in advertisement mode, and received via the link hierarchy in scanning mode.

[0256] Initiating PDUs

[0257] The following ad channel PDU types are called start PDUs.

[0258] CONNECT_REQ: Sent via the link hierarchy in the initial state, and received via the link hierarchy in the advertisement state.

[0259] Data Channel PDU

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

[0261] As described above, procedures, states, packet formats, etc. in BLE technology can be applied to implement the method proposed in this specification.

[0262] Referring again to FIG. 4, the load 455 is a battery. The battery can store energy using the power output from the power pick-up circuit 210. On the other hand, a battery is not necessarily required to be included in the mobile device 450. For example, the battery may be provided as an external configuration in a detachable form. As another example, the wireless power receiver 200 may include a driving means for driving various operations of an electronic device instead of a battery.

[0263] Although the mobile device 450 is illustrated as including the wireless power receiver 200 and the base station 400 is illustrated as including the wireless power transmitter 100, in a broad sense, the wireless power receiver 200 can be equated with the mobile device 450, and the wireless power transmitter 100 can also be equated with the base station 400.

[0264] When the communication / control circuit 120 and the communication / control circuit 220 include Bluetooth or Bluetooth Low Energy as an out-of-band (OB) communication module or a short-range communication module in addition to an in-band (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 can be represented by a simplified block diagram as shown in FIG. 6.

[0265] FIG. 6 is a block diagram showing a wireless power transmission system using BLE communication according to an example.

[0266] Referring 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.

[0267] On the other hand, the wireless power receiving device 200 includes a power pickup circuit 210 and a communication / control circuit 220. The communication / control circuit 220 includes an in-band communication module 221 and a BLE communication module 222.

[0268] In one aspect, the BLE communication modules 122 and 222 perform the architecture and operation shown in 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 to exchange control information and packets necessary for wireless power transmission.

[0269] In other aspects, the communication / control circuit 120 may be configured to operate a profile for wireless charging, where the profile for wireless charging may be GATT utilizing BLE transmission.

[0270] Figure 7 is a block diagram showing a wireless power transmission system using BLE communication as another example.

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

[0272] Hereinafter, a coil or coil section includes a coil and at least one element adjacent to the coil, and may be referred to as a coil assembly, coil cell, or cell.

[0273] On the other hand, when the user places the wireless power receiver 200 within the working space of the wireless power transmitter 100, both the wireless power transmitter 100 and the wireless power receiver 200 begin communicating 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 multiple stages. The communication protocol will be described below.

[0274] Figure 8 is a state transition diagram illustrating the wireless power transmission procedure.

[0275] WPC allows for the definition of two communication protocols.

[0276] -Baseline protocol (or BPP): This can refer to the original protocol that supports only one-way communication from the wireless power receiver 200 to the wireless power transmitter 100.

[0277] - Extended protocol (or EPP): Supports bidirectional communication and improved FOD (foreign object detection) functionality, and can also support data transmission stream functionality and authentication options.

[0278] Referring to Figure 8, the power transfer operation between the wireless power transmitter 100 and the wireless power receiver 200 according to one embodiment of this specification can be broadly divided into the ping phase 810, the configuration phase 820, the negotiation phase 830, and the power transfer phase.

[0279] -Pin Phase 810

[0280] In the pin phase 810, the wireless power transmitting apparatus 100 may attempt to establish communication with the wireless power receiving apparatus 200. Measurement may be performed before attempting to establish communication, and the measurement can check whether there is any object such as a bank card, coin or other metal that may be damaged or heated during power transmission. Here, such measurement may be performed without waking up the wireless power receiving apparatus 200.

[0281] Here, after obtaining design information from the wireless power receiving apparatus 200, the wireless power transmitting apparatus 100 may postpone the conclusion on whether the detected metal is a foreign object or a friendly metal to the negotiation phase 830.

[0282] - Configuration Phase 820

[0283] In the configuration phase 820, the wireless power receiving apparatus 200 may transmit basic identification and configuration data to the wireless power transmitting apparatus 100. Then, both sides of the wireless power transmitting apparatus 100 and the wireless power receiving apparatus 200 can use this information to generate a baseline power transfer contract.

[0284] In addition, the wireless power transmitting apparatus 100 and the wireless power receiving apparatus 200 can determine whether to continue with the Baseline Protocol or the Extended Protocol in the configuration phase 820.

[0285] Here, the wireless power receiving apparatus 200 can utilize improved functions such as FOD, data transmission streams and authentication only when implementing the extended protocol.

[0286] - Negotiation Phase 830

[0287] In negotiation phase 830, the radio power transmitter 100 and the radio power receiver 200 can establish an extended power transfer contract, which includes additional settings and restrictions. The radio power receiver 200 can also provide design information to the radio power transmitter 100. Later, this design information can be used to complete the FOD before switching to power transfer phase 840.

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

[0289] - Power transmission phase 840

[0290] The power transmission phase 840 may be the stage in which power is transmitted to the load of the wireless power receiver 200.

[0291] In the extended protocol, the wireless power transmitter 100 and the wireless power receiver 200 can perform system calibration when this stage begins. This stage may occasionally be interrupted to renegotiate elements of the power transmission contract, but power transmission may continue during such renegotiations.

[0292] The protocols for the aforementioned Ping Phase (810), Configuration Phase (820), Negotiation Phase (830), and Power Transfer Phase (840) will be explained in more detail below.

[0293] 1. Pin Phase 810

[0294] When pin phase 810 begins, the wireless power transmitter 100 does not yet know whether the wireless power receiver 200 is within the operating volume. Furthermore, the wireless power transmitter 100 cannot recognize the wireless power receiver 200 because the system is generally deactivated due to a lack of power signal.

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

[0296] Figure 9 schematically illustrates an example of the pin phase 810 protocol.

[0297] As shown in Figure 9, the wireless power transmitter 100 can perform analog pin operations (S910). That is, the wireless power transmitter 100 can transmit analog pins to determine whether or not an object is present in the operating volume. For example, the wireless power transmitter can sense whether or not an object is present in the operating volume based on a change in the current of the transmitting coil or primary coil.

[0298] The wireless power transmitter 100 can be protected by NFC tag protection (S920). Here, the protection of the NFC tag can be carried out by the following procedure.

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

[0300] b) Subsequently, in the case of an object containing an NFC tag, it can be confirmed whether it can withstand the power signal without being damaged.

[0301] c) If the wireless power transmitter 100 determines that the NFC tag cannot withstand the power signal, it will hold the pin position without starting the digital pin, and the wireless power transmitter 100 can inform the user of the reason why it will not continue.

[0302] The wireless power transmitter 100 can perform foreign object detection (S930). That is, the wireless power transmitter 100 can collect information useful for determining whether or not there are foreign objects other than the wireless power receiver 200. For this purpose, the wireless power transmitter 100 can use various methods such as the free-power FOD method.

[0303] On the other hand, in the three stages mentioned above (S910, S920, and S930), the wireless power receiver does not need to be operational.

[0304] The wireless power transmitter 100 performs the above steps, and the working space No Line power receiving device 200 The possibility exists If it determines that there is a digital pin, the wireless power transmitter 100 can initiate a digital pin (S940). Here, the digital pin can request a response from the wireless power receiver 200, such as a SIG (signal strength) data packet or an EPT (End Power Transfer) data packet.

[0305] Subsequently, the wireless power transmitter 100 can receive a SIG or EPT from the wireless power receiver 200 (S950). Here, the SIG data packet may provide a measurement of the coupling, and the SIG data packet may contain information regarding the signal strength value. The EPT data packet may provide a power transmission cessation request and the reason for the request.

[0306] If the wireless power transmitter 100 is unable to receive the above-mentioned response from the wireless power receiver 200, the wireless power transmitter 100 can remain in pin phase 810 and repeat the above steps.

[0307] 2. Configuration Phase 820

[0308] Configuration phase 820 is part of the following protocol:

[0309] - The wireless power receiver 200 can allow the wireless power transmitter 100 to identify it.

[0310] -The wireless power receiver 200 and the wireless power transmitter 100 can establish a baseline power transmission contract.

[0311] -The wireless power receiver 200 and the wireless power transmitter 100 can determine the protocol modification used for power transmission.

[0312] In configuration phase 820, the wireless power transmitter 100 and the wireless power receiver 200 can continue to operate using digital pin parameters. This may mean that the power and current levels of both the wireless power transmitter 100 and the wireless power receiver 200 are only changed when the user moves the wireless power receiver 200 within the working space.

[0313] The following provides a more detailed explanation of the protocol used in configuration phase 820.

[0314] Figure 10 schematically shows an example of the protocol for configuration phase 820.

[0315] According to Figure 10, the wireless power transmitter 100 can receive an ID (identification) from the wireless power receiver 200 (S1010). Alternatively, the wireless power transmitter 100 can also receive an XID (extended identification) from the wireless power receiver 200 (S1020). In other words, the wireless power receiver 200 can identify itself using the ID data packet and selectively the XID data packet.

[0316] The wireless power transmitter 100 can selectively receive PCH (power control hold-off) data packets from the wireless power receiver 200 (S1030), and the wireless power transmitter 100 can receive CFG data packets from the wireless power receiver 200 (S1040). That is, the wireless power receiver 200 can use the PCH and / or CFG data packets to provide data for use in a power transmission contract.

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

[0318] Summarizing and organizing each of the data packets mentioned above, we get the following:

[0319] -ID: The ID data packet may contain information that identifies the wireless power receiving device 200. Here, the ID may include a manufacturer code, a basic device identifier, etc. The ID may also include information that identifies the presence or absence of the XID data packet during the configuration phase.

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

[0321] -PCH: The PCH data packet can constitute a delay between the reception of the CE data packet and the start of coil current adjustment by the radio power transmitter 100.

[0322] -CFG: CFG data packets can provide basic configuration data.

[0323] For example, a CFG data packet can provide all the parameters that recommend power transmission in the baseline protocol. Simultaneously, a CFG data packet can provide all the FSK communication parameters used in the extended protocol. Furthermore, a CFG data packet can provide additional functionality for the wireless power receiver 200.

[0324] Figure 11 is a diagram showing the message field of a configuration packet (CFG) of a wireless power receiving device according to one embodiment.

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

[0326] The Authentication Flag (AI) indicates whether the wireless power receiver supports authentication functions. For example, a value of "1" for the Authentication Flag (AI) indicates that the wireless power receiver supports authentication functions or can act as an Authentication Initiator, while a value of "0" for the Authentication Flag (AI) indicates that the wireless power receiver does not support authentication functions or cannot act as an Authentication Initiator.

[0327] The Outband (OB) flag indicates whether the radio power receiver supports outband communication. For example, a value of "1" for the Outband (OB) flag indicates that the radio power receiver supports outband communication, while a value of "0" indicates that the radio power receiver does not support outband communication.

[0328] The provision of the aforementioned ID and / or XID is for identification purposes. The provision of the PCH and / or CFG is for the construction of the power transmission contract.

[0329] 3. Negotiation Phase 830

[0330] Negotiation Phase 830 is part of an extended protocol that allows the radio power transmitter 100 and the radio power receiver 200 to modify the power transmission contract. There are two types of this phase.

[0331] - Negotiation Phase 830: Negotiation Phase 830 follows directly from Configuration Phase 820 and serves to generate the initial extended power transmission contract. Simultaneously, Negotiation Phase 830 also serves to complete the pre-power FOD function. Here, there is no limit to the length of the negotiation phase.

[0332] - Renegotiation Phase: The renegotiation phase can interrupt the power transmission phase 840 multiple times and generally serves to adjust a single element of the power transmission contract. Also, FOD / qf, FOD / rf, and SRQ / rpr data packets do not have to be used in the renegotiation phase. Restrictions on CE data packets in the power transmission phase 840 limit the length of the renegotiation phase.

[0333] During the negotiation or renegotiation phase, the Power Transfer Contract may be extended or modified to include the reception / transmission of radio power between a radio power receiver and a radio power transmitter, or the Power Transfer Contract may be renewed to adjust at least some of its elements, or information may be exchanged to establish outband communication.

[0334] Figure 12 is a schematic flowchart illustrating the negotiation or renegotiation protocol in one embodiment.

[0335] Referring to Figure 12, the wireless power transmitter 100 can receive FOD status data packets (egFOD) from the wireless power receiver 200 (S1210). Here, the wireless power receiver 200 can use the FOD status data packets to inform the wireless power transmitter 100 of the impact their presence has on the selected attributes of the reference wireless power transmitter 100. The wireless power transmitter 100 can then use this information to configure the FOD function.

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

[0337] On the other hand, the wireless power receiver 200 can receive the ID (Identification data packet), CAP (Capabilities data packet), and XCAP (extended CAP) from the wireless power transmitter 100 using GRQ (General Request data packet).

[0338] A 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 the header value of a data packet that the wireless power receiver 200 requests from the wireless power transmitter 100 using the GRQ packet.

[0339] For example, during the negotiation or renegotiation phase, the wireless power receiver 200 can send a GRQ packet (GRQ / id) to the wireless power transmitter 100 requesting an ID packet from the wireless power transmitter 100 (S1220).

[0340] Upon receiving the GRQ / id, the wireless power transmitter 100 can transmit an ID packet to the wireless power receiver 200 (S1225). The ID packet from the wireless power transmitter 100 contains information for the "Manufacturer Code". The ID packet containing information for the "Manufacturer Code" allows the manufacturer of the wireless power transmitter 100 to be identified.

[0341] Alternatively, during the negotiation or renegotiation phase, the wireless power receiver 200 may send a GRQ packet (GRQ / cap) to the wireless power transmitter 100 requesting a performance packet (CAP) from the wireless power transmitter 100 (S1230). The message field of the GRQ / cap may include the header value (0x31) of the performance packet (CAP).

[0342] Upon receiving GRQ / cap, the wireless power transmitter 100 can transmit a performance packet (CAP) to the wireless power receiver 200 (S1235).

[0343] Alternatively, during the negotiation or renegotiation phase, the wireless power receiver 200 may send a GRQ packet (GRQ / xcap) to the wireless power transmitter 100 requesting a performance packet (CAP) from the wireless power transmitter 100 (S1240). The message field of the GRQ / xcap may include the header value (0x32) of the performance packet (XCAP).

[0344] Upon receiving GRQ / xcap, the wireless power transmitter 100 can transmit a performance packet (XCAP) to the wireless power receiver 200 (S1245).

[0345] Figure 13 is a diagram showing the message field of a performance packet (CAP) of a wireless power transmission device according to one embodiment.

[0346] A performance packet (CAP) according to one embodiment may have a header value of 0x31, and as shown in Figure 19, it may also include a 3-byte message field.

[0347] Referring to Figure 13, the message field of a performance packet (CAP) may include a 1-bit authentication (AR) flag and a 1-bit out-of-band (OB) flag.

[0348] 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 indicates that the wireless power transmitter 100 does not support the authentication function or cannot operate as an authentication responder.

[0349] The out-of-band (OB) flag indicates whether the wireless power transmitting apparatus 100 supports out-of-band communication. For example, when the value of the out-of-band (OB) flag is "1", it indicates that the wireless power transmitting apparatus 100 supports out-of-band communication, and when the value of the out-of-band (OB) flag is "0", it can indicate that the wireless power transmitting apparatus 100 does not support out-of-band communication.

[0350] In the negotiation phase, the wireless power receiving apparatus 200 receives a capability packet (CAP) of the wireless power transmitting apparatus 100, and can confirm whether the wireless power transmitting apparatus 100 supports an authentication function and whether it supports out-of-band communication.

[0351] Returning to FIG. 12 again, the wireless power receiving apparatus 200 can update elements of a Power Transfer Contract related to power provided in the power transmission phase using at least one Specific Request data packet (SRQ) in the negotiation phase or re-negotiation phase (S1250), and can receive ACK / NAK in response thereto (S1255).

[0352] On the other hand, in order to confirm the extended power transfer contract and end the negotiation phase, the wireless power receiving apparatus 200 can transmit SRQ / en to the wireless power transmitting apparatus 100 (S1260), and receive an ACK from the wireless power transmitting apparatus 100 (S1265).

[0353] 4. Power Transmission Phase 840

[0354] The power transmission phase 840 is a part of the protocol in which actual power is transmitted to a load of the wireless power receiving apparatus 200. Herein, power transfer can be performed according to the conditions of the power transfer contract generated in the negotiation phase 830.

[0355] <CE-based Power Control>

[0356] The wireless power receiver 200 can control the power level by transmitting control error (CE) data to the wireless power transmitter 100, which measures the deviation between the target and the actual operating point of the wireless power receiver 200. 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.

[0357] <FOD method within power transfer>

[0358] In addition to control error data, the wireless power transmitter 100 and the wireless power receiver 200 can exchange information to facilitate FOD detection. The wireless power receiver 200 periodically reports the amount of power it receives (received power level) to the wireless power transmitter 100, and the wireless power transmitter 100 can inform the wireless power receiver 200 whether or not it has detected a foreign object. Methods available for FOD detection during the power transmission phase include, for example, power loss calculation. In this approach, the wireless power transmitter 100 compares the received power level reported by the wireless power receiver 200 with the amount of transmitted power (transmitted power level), and can send a signal to the wireless power receiver 200 (indicating whether or not it has detected a foreign object) when the difference exceeds a threshold.

[0359] <Renegotiation Phase>

[0360] Depending on the circumstances, if necessary, the wireless power transmitter 100 or the wireless power receiver 200 may request renegotiation of the power transmission contract during the power transmission phase. Examples of modified circumstances in which renegotiation of the power transmission contract may take place are as follows:

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

[0362] - If the wireless power transmitter 100 is detected to be operating at low efficiency.

[0363] - If the wireless power transmitter 100 can no longer maintain the current power level due to the increased operating temperature (or conversely, if the wireless power receiver 200 can operate at a higher power level after it has cooled sufficiently).

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

[0365] <Data transmission stream>

[0366] The wireless power transmitter 100 and the wireless power receiver 200 can initiate a data transmission stream and exchange application-level data throughout the entire power transmission phase 840.

[0367] Here, the important common application is authentication, and here both sides Tampering Prevention method for the opponent Authentication information This can be confirmed. For example, the wireless power receiver 200 can confirm whether the wireless power transmitter 100 can be trusted to operate safely at a high power level. Authentication information You can try to verify the appropriate Authentication information If this is present, it can be said that the compliance test has been passed.

[0368] Therefore, this specification provides a method for initiating power transmission at a low power level and controlling the power to a higher level only after the authentication protocol has been successfully completed.

[0369] <Protocol in power transmission phase 840>

[0370] The above provides a general overview of the operation between the wireless power transmitter 100 and the wireless power receiver 200 during the power transmission phase 840. To facilitate a smooth understanding of the operation during the power transmission phase 840, the protocols used in this phase will be described separately for the baseline protocol and the extended protocol.

[0371] Figure 14 schematically shows the data flow for power transmission phase 840 in the baseline protocol.

[0372] According to Figure 14, the wireless power receiver 200 can transmit CE to the wireless power transmitter 100 (S1410). Here, the wireless power receiver 200 can normally transmit CE data packets several times per second.

[0373] The wireless power receiver 200 can generally send RP (received power) data packets (RP8 in the baseline protocol) to the wireless power transmitter 100 once every 1.5 seconds (S1420).

[0374] Selectively, the wireless power receiver 200 can transmit CHS (charge status) data packets to the wireless power transmitter 100 (S1430).

[0375] The data packets mentioned above can be summarized and explained as follows:

[0376] -CE: The CE data packet can provide feedback on the desired power level. The CE data packet may include a control error value, which may be a signed integer value that 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 is positive, it indicates that the actual operating point is below the target operating point, and the wireless power transmitter 100 can be requested to increase the power signal. If the control error value is negative, it indicates that the actual operating point is above the target operating point, and the wireless power transmitter 100 can be requested to decrease the power signal.

[0377] -RP8: The RP8 data packet can report the received power level. Here, the RP8 data packet may be included only in the baseline protocol.

[0378] -CHS: CHS data packets can provide the battery charge level under load.

[0379] Figure 15 schematically shows the data flow for power transmission phase 840 in the extended protocol.

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

[0381] The wireless power receiver 200 can generally send RP (received power) data packets (RP in the extended protocol) to the wireless power transmitter 100 once every 1.5 seconds (S1515).

[0382] During the power transmission phase, control error packets (CEs) and received power packets (RPs) are data packets that should be repeatedly transmitted / received in accordance with the required timing constraints for controlling radio power.

[0383] The wireless power transmitter 100 can control the level of wireless power to transmit based on control error packets (CE) and received power packets (RP) received from the wireless power receiver 200.

[0384] On the other hand, in the extended protocol, the wireless power transmitter 100 can respond to the received power packet (RP) with bit patterns such as ACK, NAK, and ATN (S1520).

[0385] When the wireless power transmitter 100 responds with an ACK to a received power packet (RP / 0) with a mode value of 0, it means that power transmission can continue at the current level.

[0386] When the wireless power transmitter 100 responds with NAK to a received power packet (RP / 0) with a mode value of 0, it means that the wireless power receiver 200 should reduce its power consumption.

[0387] When the wireless power transmitter 100 responds with an ACK to a received power packet (RP / 1 or RP / 2) with a mode value of 1 or 2, it means that the wireless power receiver 200 has accepted the power correction value contained in the received power packet (RP / 1 or RP / 2).

[0388] When the wireless power transmitter 100 responds with NAK to a received power packet (RP / 1 or RP / 2) with a mode value of 1 or 2, it means that the wireless power receiver 200 did not accept the power correction value contained in the received power packet (RP / 1 or RP / 2).

[0389] A received power packet (RP / 1) with a mode value of 1, as described above, can represent a first calibration data point, and a received power packet (RP / 2) with a mode value of 2 can represent an additional calibration data point. Here, the wireless power receiver can transmit multiple received power packets (RP / 2) with a mode value of 2 to the wireless power transmitter to transmit multiple additional power calibration values, and the wireless power transmitter can perform the calibration process based on the received RP / 1 and multiple RP / 2s.

[0390] When the wireless power transmitter 100 responds to a received power packet (RP) with an Attention (ATN), it means that the wireless power transmitter 100 is requesting permission to communicate. In other words, the wireless power transmitter 100 can send an Attention (ATN) response pattern in response to an RP data packet to request permission to transmit the data packet. In other words, the wireless power transmitter 100 can send an Attention (ATN) to the wireless power receiver 200 in response to an RP data packet to request permission from the wireless power receiver 200 to transmit the data packet.

[0391] Selectively, the wireless power receiver 200 can transmit CHS (charge status) data packets to the wireless power transmitter 100 (S1525).

[0392] On the other hand, the wireless power transmitter 100 and the wireless power receiver 200 can exchange DSR (data stream response) data packets, CAP data packets, and NEGO data packets in order to initiate renegotiation of elements in the power transmission contract (generally, guaranteed load power).

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

[0394] Furthermore, the wireless power receiver 200 can transmit a NEGO data packet to the wireless power transmitter 100 (S1540), and the wireless power transmitter 100 can respond to the NEGO data packet by transmitting an ACK to the wireless power receiver 200 (S1545).

[0395] The data packets related to the start of the renegotiation phase can be summarized as follows:

[0396] -DSR: A DSR data packet may be set to one of the following values:

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

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

[0399] iii) 0x55-DSR / nd: Indicates that the last received data packet from the wireless power transmitter 100 was unexpected.

[0400] iv) 0xFF-DSR / ack: Confirms that the last received data packet from the wireless power transmitter 100 was processed correctly.

[0401] -CAP: The CAP data packet provides information about the functions of the wireless power transmitter 100. The specific details are as described above.

[0402] -NEGO:NEGO data packets can be requested from the wireless power transmitter 100 to be used in the renegotiation phase.

[0403] The wireless power transmitter 100 and the wireless power receiver 200 can utilize ADC (auxiliary data control), ADT (auxiliary data transport), and DSR data packets for the exchange of application-level data.

[0404] In other words, in terms of sending and receiving data transmission streams for the exchange of application-level data, the wireless power receiver 200 can transmit ADC / ADT to the wireless power transmitter 100 (S1550), and the wireless power transmitter 100 can transmit ACK / NAK to the wireless power receiver 200 in response (S1555). Also, the wireless power receiver 200 can transmit DSR to the wireless power transmitter 100 (S1560), and the wireless power transmitter can transmit ADC / ADT to the wireless power receiver (S1565).

[0405] Here, the data transmission stream plays the role of transmitting application-level data from the data stream initiator to the data stream responder. This application-level data can be broadly categorized into i) authentication applications and ii) exclusive (general-purpose) applications.

[0406] Among application-level data, messages / information related to the authentication application can be organized as follows:

[0407] A message used in an authentication procedure is called an authentication message. Authentication messages are used to carry information related to authentication. There are two types of authentication messages: an authentication request and an authentication response. An authentication request is sent by an authentication initiator, and an authentication response is sent by an authentication responder. A wireless power transmitter and receiver can be either an authentication initiator or an authentication responder. For example, if the wireless power transmitter is the authentication initiator, the wireless power receiver becomes the authentication responder, and if the wireless power receiver is the authentication initiator, the wireless power transmitter becomes the authentication responder.

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

[0409] -GET_DIGESTS: This request can be used to retrieve certificate chain digests. The wireless power receiver 200 can request any number of digests at once.

[0410] -GET_CERTIFICATE: This request is used to read a segment of the target certificate chain.

[0411] -CHALLENGE: This request can be used to initiate the certification of product equipment for power transmission devices.

[0412] Authentication response messages include DIGESTS, CERTIFICATE, CHALLENGE_AUTH, and ERROR.

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

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

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

[0416] -ERROR: This response can be used to transmit error information on the power transmitter.

[0417] Authentication messages can also be called authentication packets, authentication data, or authentication control information. Messages such as GET_DIGEST and DIGESTS can also be called GET_DIGEST packets or DIGEST packets, respectively.

[0418] On the other hand, as mentioned above, the wireless power receiver 200 and the wireless power transmitter 100 can transmit application-level data via a data transmission stream. The application-level data transmitted via the data transmission stream can consist of a data packet sequence with the following structure.

[0419] - Initial ADC data packet to open the stream.

[0420] i) The type of message contained in the stream.

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

[0422] - A series of ADT data packets, including the actual message.

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

[0424] The following diagrams illustrate the data transmission streams for examples where the above-described ADC, ADT, and ADC / end data packets are used.

[0425] Figure 16 shows an example of an application-level data stream between a wireless power transmitter 100 and a wireless power receiver 200.

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

[0427] An ADC data packet is used to start (open) a data stream. An ADC data packet can indicate the type of message to be included in the stream and the number of data bytes. An ADT data packet, on the other hand, is a sequence of data containing the actual message. An ADC / end data packet is used to signal the end of a stream. For example, the maximum number of data bytes in a data transmission stream may be limited to 2047.

[0428] An ACK or NAC (NACK) is used to indicate whether the ADC data packet and ADT data packet have been received successfully. Control information necessary for wireless charging, such as a control error packet (CE) or DSR, may be transmitted between the transmission timings of the ADC data packet and the ADT data packet.

[0429] Such a data stream structure may be used to transmit and receive authentication-related information or other application-level information between the wireless power transmitter and receiver.

[0430] An example illustrating the operation between the wireless power transmitter 100 and the wireless power receiver 200 during the power transmission phase 840, as described above, is as follows:

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

[0432] In Figure 17, during the power transmission phase, the wireless power transmitter 100 and the wireless power receiver 200 can control the amount of power transmitted by communicating in parallel with power transmission and reception. The wireless power transmitter and wireless power receiver operate at specific control points. The control points indicate the combination of voltage and current provided at the output terminal of the wireless power receiver when power transmission is performed.

[0433] More specifically, the wireless power receiver selects a desired control point—such as the desired output current / voltage and the temperature at a specific location on the mobile device—and additionally determines the actual control point currently in operation. Using the desired and actual control points, the wireless power receiver can calculate a control error value and transmit it to the wireless power transmitter as a control error packet.

[0434] The wireless power transmitter can then use the received control error packets to set / control new operating points—amplitude, frequency, and duty cycle—and control power transfer. Thus, control error packets are transmitted / received at regular time intervals during the power transfer phase. For example, the wireless power receiver can set the control error value to a negative number when attempting to reduce the current of the wireless power transmitter, and to a positive number when attempting to increase the current. In this way, in inductive mode, power transfer can be controlled by the wireless power receiver transmitting control error packets to the wireless power transmitter.

[0435] In resonant mode, operation may differ from that in inductive mode. In resonant mode, one radio power transmitter needs to serve multiple radio power receivers simultaneously. However, when controlling power transfer as in the inductive mode described above, the power transferred is controlled by communication with one radio power receiver, making it difficult to control power transfer to additional radio power receivers. Therefore, in the resonant mode described herein, the radio power transmitter transmits a common base power, and the radio power receiver controls the amount of power received by controlling its own resonant frequency. However, even in such operation of resonant mode, the method described in Figure 17 is not completely excluded, and control of additional transmitted power may be performed using the method in Figure 17.

[0436] <Profile-related operations>

[0437] Wireless charging methods include magnetic induction, which uses the magnetic induction phenomenon between a primary and secondary coil, and magnetic resonance, which transmits power by using magnetic resonance in a frequency band of several MHz at tens of kHz. Wireless charging standards for magnetic resonance are led by the A4WP (Audio-Four-Wave Power Program), while standards for magnetic induction are led by the WPC (Wireless Power Consortium). The WPC is designed to transmit and receive various state information and commands related to wireless charging systems in-band.

[0438] The WPC standard defines a baseline power profile (BPP) and an extended power profile (EPP). The following sections will explain BPP and EPP separately.

[0439] A. BPP (Baseline Power Profile)

[0440] BPP (Broad Power Transfer Profile) is a power transfer profile between wireless power transmitters and receivers that support power transmission up to 5W. BPP supports unidirectional communication from the wireless power receiver to the wireless power transmitter. This communication method can support ASK (amplitude shift keying). BPP has three protocol phases: Ping, configuration, and power transfer.

[0441] B.EPP (extended power profile)

[0442] EPP (Electronic Power Transfer Profile) is a power transfer profile between wireless power transmitters and receivers that support power transmission up to 15W. EPP supports bidirectional communication between wireless power receivers and wireless power transmitters. Communication from the wireless power receiver to the wireless power transmitter can be done using ASK (amplitude shift keying), and communication from the wireless power transmitter to the wireless power receiver can be done using FSK (frequency shift keying). EPP has protocol phases: Ping, configuration, negotiation, and power transfer.

[0443] (a) Compatibility with EPP

[0444] EPP can support higher-level profiles than BPP.

[0445] For example, if a BPP radio power receiver is placed on an EPP radio power transmitter, the EPP radio power transmitter can operate as a BPP radio power transmitter.

[0446] For example, if an EPP radio power receiver is placed on a BPP radio power transmitter, the EPP radio power receiver can operate as a BPP radio power receiver.

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

[0448] (b) EPP instruction method for EPP wireless power receiver

[0449] An EPP wireless power receiver can indicate that it is an EPP wireless power receiver by setting the "neg" bit in the configuration packet (ieCFG) to 1. A specific example of the configuration packet is as described above.

[0450] (c) EPP Wireless Power Transmitter EPP Instruction Method

[0451] When an EPP radio power transmitter receives a configuration packet from a radio power receiver with the "neg" bit set to 1, the EPP radio power transmitter can respond to this with an ACK FSK bit pattern.

[0452] For reference, as mentioned above, BPP wireless power transmitters do not support the FSK communication method, and therefore cannot transmit FSK bit patterns. In this case, an EPP wireless power receiver that has set the "neg" bit to 1 and sent a configuration packet to a BPP wireless power transmitter will not receive the aforementioned ACK response, thus identifying the other wireless power transmitter as a BPP wireless power transmitter.

[0453] On the other hand, wireless power transfer systems are seeking to provide new power transfer profiles, and among the proposed power transfer profiles is the MPP (magnetic power profile). The MPP can support Apple's proprietary extension based on Qiv 1.3.0.

[0454] C.MPP (Magnet Power Profile)

[0455] MPP (Multi-Power Propagation) is a power transfer profile between wireless power transmitters and receivers that support power transmission up to 15W. MPP supports bidirectional communication between the wireless power receiver and wireless power transmitter. Communication from the wireless power receiver to the wireless power transmitter can use ASK (amplitude shift keying), and communication from the wireless power transmitter to the wireless power receiver can use FSK (frequency shift keying). In this case, a fast FSK (NCYCLE=128) can be used during the negotiation and power transfer phases.

[0456] MPP has protocol phases: Ping, configuration, MPP negotiation, and MPP power transfer.

[0457] (a) Compatibility with MPP

[0458] MPP can support higher-level profiles than BPP.

[0459] For example, if a BPP radio power receiver is placed on top of an MPP radio power transmitter, the MPP radio power transmitter can operate as a BPP radio power transmitter.

[0460] For example, if an MPP radio power receiver is placed on a BPP radio power transmitter, the MPP radio power receiver can operate as a BPP radio power receiver.

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

[0462] (b) MPP operation of MPP wireless power receiver (MPP instruction method)

[0463] MPP wireless power receivers can use specific MPP indicators within extended ID packets.

[0464] For an MPP radio power receiver to indicate MPP support via XID, it must inform the radio power transmitter that an XID will be transmitted via an ID packet. The ID packets that the MPP radio power receiver will transmit may be as follows:

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

[0466] According to Figure 18, in the MPP ID packet, the values ​​of the major version fields from b4 to b7 of B0 can be set to 1.

[0467] In an MPP ID packet, the values ​​of the minor version fields b0-b3 of B0 may be values ​​determined later.

[0468] In the MPP ID packet, the values ​​of the B1 and B2 manufacturing codes can be assigned to the PRMC code.

[0469] In an MPP ID packet, the value of the "ext" field in B3's b7 can be set to 1, instructing the system to send an additional XID packet.

[0470] In the MPP ID packet, the values ​​of the random identifier fields b0 to b6 in B3, and b3 to b7 in B4 and B5 can be set according to the random device identification policy.

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

[0472] According to Figure 19, an XID packet in MPP can include fields such as "XID Selector," "Restricted," and "Freq Mask."

[0473] Here, whether or not MPP is supported can be determined by whether or not the value of "XID Selector" is 0xFE. In other words, if the value of XID B_0 is 0xFE, then XID can correspond to information indicating that the wireless power receiver supports MPP.

[0474] The "Restricted" field can correspond to information indicating whether the wireless power receiver operates in MPP restricted mode or MPP full mode. If the wireless power receiver chooses to operate in MPP restricted mode, the field can be set to 1. In other cases (for example, if the wireless power receiver chooses not to operate in MPP restricted mode), the field can be set to 0.

[0475] The "Preferred Frequency" field can represent the MPP preferred frequency. Here, the radio-power receiver can set this field to 128 kHz if it intends to retrieve information from the radio-power transmitter before frequency switching (during the negotiation phase). Otherwise, the radio-power receiver can set this field to 360 kHz.

[0476] The "Freq Mask" field can correspond to a field used to determine whether or not a 360kHz operating frequency is supported. In other words, if the "FreqMask" field is set to 0, 360kHz is supported.

[0477] In summary, the wireless power transmitter can determine whether the wireless power receiver supports MPP by checking whether the "ext" bit of the ID received from the wireless power receiver is set to 1, and whether the B_0 of the XID is set to 0xFE.

[0478] (c) MPP operation of MPP wireless power transmitter (MPP instruction method)

[0479] After sensing the placement of a wireless power receiver on the charging surface, the MPP wireless power transmitter can identify the receiver by performing a digital ping using the information contained in the ID and XID packets.

[0480] Here, the wireless power transmitter can determine that the wireless power receiver supports MPP if all of the following conditions are met:

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

[0482] -MPP support announcement: The lower header (byte 0) of the XID packet is set as the MPP selector.

[0483] If the two conditions mentioned above are not met, the wireless power transmitter may proceed with the subsequent steps according to the Qiv1.3 specification.

[0484] On the other hand, in response to the MPP operating mode requested by the MPP radio power receiver in the XID packet, the radio power transmitter performs the following:

[0485] - Restricted profile activation (MPP restricted mode): When the "restricted" flag is set to 1.

[0486] -Full profile activation (MPP full mode): If the "restricted" flag is set to 0.

[0487] Specific examples of the restricted profiles and the full profiles will be discussed later.

[0488] On the other hand, if an MPP radio-power transmitter receives a configuration packet from a radio-power receiver with the "neg" bit set to 1, the MPP radio-power transmitter can respond to this (in MPP full mode) with an MPP ACK FSK bit pattern.

[0489] For reference, MPP-restricted wireless power transmitters do not support the FSK communication method, and therefore cannot transmit FSK bit patterns. However, since MPP-restricted wireless power transmitters use a 360kHz operating signal for power transmission, an MPP wireless power receiver that sends a configuration packet with the "neg" bit set to 1 to a wireless power transmitter operating in MPP-restricted mode can identify the other wireless power transmitter as an MPP-restricted wireless power transmitter via the operating frequency.

[0490] (d) MPP mode

[0491] On the other hand, MPP has two modes. One is MPP Restricted mode (or MPP Baseline Profile), and the other is MPP Full mode (or MPP Full Profile).

[0492] To briefly explain the difference between the two, in MPP restricted mode, the "restricted" field in the XID is set to 1, while in MPP full mode, the "restricted" field in the XID is set to 0.

[0493] Furthermore, FSK communication is not supported in MPP restricted mode, but it is supported in MPP full mode.

[0494] Furthermore, since FSK communication is not supported in MPP-restricted mode, it is not possible to send an MPP ACK to the CFG, and therefore MPP negotiation is not supported in MPP-restricted mode. In contrast, since FSK communication is supported in MPP-full mode, it is possible to send an MPP ACK to the CFG, and therefore MPP negotiation is supported in MPP-full mode.

[0495] The following provides a more detailed explanation of MPP limited mode and MPP full mode. Note that MPP limited mode can be used in conjunction with the MPP baseline profile, and MPP full mode can be used in conjunction with the MPP full profile.

[0496] Below, we will provide a more detailed explanation of the protocols in each mode to help you gain a better understanding of MPP restricted mode and MPP full mode.

[0497] i) MPP Restricted mode

[0498] As mentioned above, FSK communication is not supported in MPP restricted mode. This means that in MPP restricted mode, there may be no data packets transmitted from the wireless power transmitter to the wireless power receiver. Against this backdrop, the protocol in MPP restricted mode will be explained using diagrams.

[0499] Figure 20 schematically shows the protocol in MPP restriction mode.

[0500] According to Figure 20, the radio power receiver can transmit a SIG to the radio power transmitter on a first operating frequency (e.g., 128 kHz). This first operating frequency can correspond to an operating frequency capable of performing BPP and / or EPP. Furthermore, this first operating frequency can correspond to the frequency at which the radio power transmitter operates.

[0501] A wireless power receiver can transmit an ID packet to a wireless power transmitter on a first operating frequency. In this case, since an XID is always transmitted in MPP, the "ext" bit of the ID can be set to 1 to indicate that an XID should be transmitted further.

[0502] The wireless power receiver can transmit XID packets to the wireless power transmitter on a first operating frequency.

[0503] In this case, the value of B0 in XID is 0xFE, and setting the value of B0 in XID to 0xFE can correspond to information indicating that the radio power receiver supports MPP. In addition, the "restricted" field in XID at this time can be set to 1 to indicate that the radio power receiver is operating in MPP restricted mode.

[0504] If the wireless power transmitter receives the aforementioned XID packet indicating MPP restriction mode, the wireless power transmitter can remove the power signal and restart the Ping phase at the new operating frequency.

[0505] Once the ping phase is restarted, the radio power receiver will begin again with SIG transmission, although the operating frequency at this time may be the second operating frequency (e.g., 360 kHz).

[0506] Subsequently, the radio power receiver transmits ID, XID, and CFG packets to the radio power transmitter at the second operating frequency. In addition, the radio power receiver transmits a CEP to the radio power transmitter, enabling it to receive radio power based on the MPP baseline from the radio power transmitter.

[0507] ii) MPP Full mode

[0508] As mentioned above, FSK communication is supported in MPP full mode. That is, in MPP full mode, there are data packets transmitted from the radio power transmitter to the radio power receiver. In other words, MPP negotiations can take place between the radio power transmitter and the radio power receiver. Against this backdrop, the MPP full mode protocol will be explained using diagrams.

[0509] Figures 21 and 22 schematically illustrate the protocol in MPP full mode.

[0510] First, as shown in Figure 21, the radio power receiver can transmit a SIG to the radio power transmitter on a first operating frequency (e.g., 128 kHz). In this case, the first operating frequency can correspond to an operating frequency on which BPP and / or EPP can be performed. Furthermore, the first operating frequency in this case can correspond to the frequency on which the radio power transmitter is driven.

[0511] A wireless power receiver can transmit an ID packet to a wireless power transmitter on a first operating frequency. In this case, since an XID is always transmitted in MPP, the "ext" bit of the ID can be set to 1 to indicate that an XID should be transmitted further.

[0512] The wireless power receiver can transmit XID packets to the wireless power transmitter on a first operating frequency.

[0513] In this case, the value of B0 in XID is 0xFE, and setting the value of B0 in XID to 0xFE can correspond to information indicating that the radio power receiver supports MPP. In addition, the "restricted" field in XID at this time can be set to 0 to indicate that the radio power receiver is operating in MPP full mode.

[0514] On the other hand, in MPP full mode, unlike MPP limited mode, the radio power transmitter does not remove the power signal even if it receives an XID packet from the radio power receiver. In this case, the radio power receiver still transmits CFG packets to the radio power transmitter after the XID packet because the power signal was not removed.

[0515] The wireless power receiver can then receive an MPP ACK from the wireless power transmitter as a response to the aforementioned CFG packet.

[0516] Upon receiving an MPP ACK, the radio power receiver enters the negotiation phase with the radio power transmitter, and both the radio power receiver and the radio power transmitter can proceed with the negotiation.

[0517] After negotiations are complete, the wireless power receiver can enter the power transfer phase with the wireless power transmitter.

[0518] Meanwhile, the radio power receiver transmits an EPT packet to the radio power transmitter. Upon receiving the EPT packet, the radio power transmitter removes the power signal and can subsequently restart the Ping phase at the new operating frequency.

[0519] As shown in Figure 22, once the Ping phase is restarted, the radio power receiver will start again with SIG transmission. However, the operating frequency at this time may be the second operating frequency (e.g., 360 kHz).

[0520] Subsequently, the radio power receiver transmits ID, XID, and CFG packets to the radio power transmitter at the second operating frequency. The radio power receiver can then receive an MPP ACK from the radio power transmitter.

[0521] Upon receiving the MPP ACK, the radio power receiver enters a negotiation phase with the radio power transmitter at a second operating frequency, and both the radio power receiver and the radio power transmitter can proceed with the negotiation.

[0522] After negotiations are complete, the radio power receiver enters the power transfer phase with the radio power transmitter at the second operating frequency. Simultaneously, the radio power receiver can receive radio power from the radio power transmitter based on MPP full mode by sending an XCE to the radio power transmitter and receiving a response (e.g., an ACK).

[0523] The following provides a more detailed explanation of this specification.

[0524] As mentioned above, a wireless power transmission system defines a data transport stream format that can send and receive application-level data streams between a wireless power transmitter and a wireless power receiver.

[0525] In this case, the format of the data transport stream (in other words, the data stream) is defined as a packet as follows:

[0526] - Initial ADC data packet to open the stream

[0527] Here, the aforementioned ADC data packet can indicate the type of message contained in the stream.

[0528] Furthermore, the aforementioned ADC data packet can indicate the number of data bytes contained in the stream.

[0529] - Sequence of ADT data packets containing the actual message

[0530] - Final ADC / end data packet to close the stream

[0531] Alternatively, the following packets are defined in relation to data transport stream transmission:

[0532] - Regarding data streams: ADC and / or ADT (Radio Power Transmitter and Radio Power Receiver)

[0533] -Regarding responses to ADC and ADT: DSR (Radio Power Receiver), ACK / NAK / ND / ATN (Radio Power Transmitter)

[0534] Here, the ADC is a packet sent by a wireless power transmitter, and the ADC can also be a packet sent by a wireless power receiver. As an example, a more specific explanation of the ADC packet of a wireless power transmitter is as follows.

[0535] Figure 23 schematically shows an example of an ADC packet.

[0536] As shown in Figure 23, the ADC data packet can control the transmission of a data stream to the power receiver. The ADC packet can include a request field and parameter fields. These fields may be as follows:

[0537] - Request field: One of the following values ​​can be set.

[0538] 0-ADC / end: ​​Closes the data transmission stream that goes to the wireless power receiver.

[0539] 2-ADC / auth: Opens the authentication data transmission stream to the wireless power receiver.

[0540] 5-ADC / rst: Reconfigures all incoming and outgoing data transmission streams.

[0541] 0x10...0x1F - ADC / prop: Opens an exclusive data transmission stream to the wireless power receiver.

[0542] The parameter fields can be as follows:

[0543] -Parameter field: For exclusive (ADC / prop) and authenticated (ADC / auth) data transmission streams, this is the number of data bytes in the stream. It can be set to 0 for all other ADC data packets.

[0544] Subsequent DSR data packets may be as follows:

[0545] -DSR / ack: The wireless power receiver successfully completed the request.

[0546] -DSR / nak: The radio power receiver failed to perform the request because the receive and / or transmit data stream is already open or in use.

[0547] -DSR / nd (Open Data Transmission Stream): The wireless power receiver does not support the requested data transmission stream type.

[0548] -DSR / nd (reserved Request value): The wireless power receiver does not support the request.

[0549] -DSR / poll: The wireless power receiver did not receive the last power transmitter data packet.

[0550] In other words, a DSR / poll is a packet that a radio power receiver sends to a radio power transmitter. A DSR / poll can mean that the radio power transmitter is authorized to send any packet (following a previously sent packet, or a packet it intends to send). That is, as mentioned above, a DSR / poll can invite the radio power transmitter to send any data packet.

[0551] On the other hand, ADTs are packets sent by wireless power transmitters, and ADTs can also be packets sent by wireless power receivers. As an example, a more specific explanation of ADT packets from wireless power transmitters is as follows.

[0552] Figure 24 schematically shows an example of an ADT packet.

[0553] As shown in Figure 24, the ADT data packet transmits the application data of the data transmission stream to the power receiver. Here, ADT data packet sizes up to 7 can be used in 1.

[0554] In this case, ADT data packets of each size can be used with odd and even headers. For example, assuming the size of an ADT data packet is 7 bytes, there will be both 7-byte ADT data packets with odd headers and 7-byte ADT data packets with even headers.

[0555] Here, the ADT packet may contain a data field, which may be as follows:

[0556] -Data fields: These can be appropriately defined by the application layer.

[0557] Subsequent DSR data packets may be as follows:

[0558] -DSR / ack: The wireless power receiver has processed the packet data correctly.

[0559] -DSR / nak: The wireless power receiver received the last power transmitter data packet but was unable to process the packet's data. For example, the wireless power receiver may use this response if it is busy or unable to buffer the data.

[0560] -DSR / nd: The wireless power receiver cannot have an incoming data transport stream open.

[0561] -DSR / poll: The wireless power receiver did not receive the last power transmitter data packet.

[0562] In other words, a DSR / poll is a packet that a radio power receiver sends to a radio power transmitter. A DSR / poll can mean that the radio power transmitter is authorized to send any packet (following a previously sent packet, or a packet it intends to send). That is, as mentioned above, a DSR / poll can invite the radio power transmitter to send any data packet.

[0563] On the other hand, a data transport stream (TPL) can be divided into an initiator and a responder, regardless of whether it is a wireless power receiver or wireless power transmitter.

[0564] At this point, the data transmission stream and related packets exchanged between the initiator and the responder will be explained with reference to a diagram.

[0565] Figure 25 schematically illustrates an example of an application message being sent from a data stream initiator to a data stream responder.

[0566] According to Figure 25, the initiator sends a data message to the responder.

[0567] More specifically, the initiator sends an application request message to a specific application (for example, authentication).

[0568] To achieve this, the data stream initiator can first create application-related request messages at the application layer and store them in a buffer. The data stream initiator can then transmit the request messages from the buffer to the transport layer and store them in a local buffer. At the transport layer of the data stream initiator, the application request messages stored in the local buffer are sliced ​​to match the ADT size and then transmitted to the data stream responder via the data stream.

[0569] Whenever a data stream responder receives a sliced ​​application request message from an initiator via an ADT or similar means, the data stream responder can execute a response (ACK / NAK / ND). The data stream responder can then store the received sliced ​​message in its local buffer.

[0570] Once a data stream initiator has sent all application request messages and closed the data stream, it can provide feedback to its own application layer. Then, after the data stream responder has completed the received application request messages, it can transmit them to its own application layer.

[0571] Once the application request message is transmitted to the data stream responder's application layer through this process, the data stream initiator can respond that the transmission of the application request message is complete. The data stream responder can then respond that it has completed receiving the application request message.

[0572] From this point onward, the positions of the data stream initiator and data stream responder are reversed. That is, the new data stream initiator can transmit the application response message (to the application request message) to the new data stream responder. The process of transmitting the application response message is then simply a repetition of the process described above (i.e., the new data stream initiator slices the application response message and transmits it to the new data stream responder via a data stream (e.g., ADT)).

[0573] Here, an example of the process described above, namely, the conversion of an existing data stream initiator into a new data stream responder and the conversion of an existing data stream responder into a new data stream initiator, can be explained from an application perspective using diagrams as follows.

[0574] Figure 26 schematically shows the sequence of data transmission from an application perspective.

[0575] As shown in Figure 26, a data stream initiator can send an (application) request message to a data stream responder. The method by which the data stream initiator sends the (application) request message to the data stream responder is as described above. That is, as shown in Figure 25, the data stream initiator can slice the request message and send it to the data stream responder via a data stream (e.g., an ADT packet).

[0576] Subsequently, a data stream responder that receives an (application) request message converts into a new data stream initiator. That is, a data stream responder can convert into a data stream initiator once it receives the final ADC packet from the data stream initiator, which is a packet indicating the closing of the data stream associated with the application request message.

[0577] Subsequently, the new data stream initiator can send application response messages to the existing data stream initiator via a data stream (e.g., ADT packets). In this case, the existing data stream initiator can become the new data stream responder.

[0578] On the other hand, since wireless power transmission systems are systems that have been developed primarily for transmitting wireless power, a variety of problems can arise in data communication between wireless power transmitters and wireless power receivers.

[0579] The following are examples of problematic situations that can occur when data communication (i.e., TPL communication) is performed between a wireless power transmitter and a wireless power receiver.

[0580] - If, during TPL communication, the initiator (radio power transmitter or radio power receiver) and / or responder (radio power receiver or radio power transmitter) are unable to store the data they send / receive (e.g., memory stack).

[0581] -When TPL communication is in progress, the communication synchronization between the two parties fails, and the initiator and / or responder are waiting for a response from the other party.

[0582] -When inband communication is stuck because it cannot be performed due to charging control-related operations during TPL communication.

[0583] - If, during TPL communication, an unknown error prevents further communication between the initiator and / or responder.

[0584] - If a problem occurs in the transport layer buffer during TPL communication, making TPL communication impossible.

[0585] -others.

[0586] If the aforementioned problem occurs while the wireless power transmitter and / or wireless power receiver are performing data communication with the other party, it is preferable for the wireless power transmitter and / or wireless power receiver to reset or terminate (in other words, abort) this data communication.

[0587] For example, if, with at least one data stream open, the aforementioned problem occurs and it becomes difficult to send or receive any more data streams, the wireless power transmitter and / or wireless power receiver may attempt to reset the data stream.

[0588] One way to achieve this is for the wireless power transmitter and / or wireless power receiver to send reset information to the other party and close all data streams. However, this method does not take into account multiple data streams.

[0589] For example, if a problem occurs in the storage / communication of data (or in the transport layer) while various application data streams (e.g., Stream 1: authentication; Stream 2: configuration; Stream 3: BMS) are progressing, the other streams (Stream 1 and Stream 3) may remain unaffected, excluding the affected stream (let's assume, for example, that the problem occurs in Stream 2).

[0590] If the aforementioned implementation method is applied to perform a reset in this case, the reset may also be performed on other streams that are not affected (e.g., Stream 1 and Stream 3). In this case, the wireless power transmitter and / or wireless power receiver must restart data communication from the beginning for all streams that are not affected. This can be considered an inefficient method.

[0591] Furthermore, for example, if, while at least one data stream is open, the aforementioned problem occurs and it becomes difficult to send or receive any more data streams, the wireless power transmitter and / or wireless power receiver may attempt to terminate the data stream rather than reset it.

[0592] As an example, a problem like the one described above may occur during data communication between a wireless power transmitter and / or wireless power receiver, and the transmitter requests the other party to reset the data communication, but the reset fails. In such a case, it can be said that it is impossible to continue data communication with the other party, so the wireless power transmitter and / or wireless power receiver may attempt to forcibly terminate the data communication rather than reset the data stream.

[0593] However, current technology does not provide a configuration for forcibly terminating data communication, making it impossible for the wireless power transmitter and / or wireless power receiver to forcibly terminate data communication as described above.

[0594] Therefore, this specification aims to provide a method for resetting a data stream and an apparatus for utilizing this method. Furthermore, this specification aims to provide a method for forcibly terminating (aborting) a data stream and an apparatus for utilizing this method.

[0595] 1. Reset the data stream

[0596] The following drawings have been prepared to illustrate a specific example of this specification. The names of specific devices and signals / messages / fields shown in the drawings are presented illustratively, and the technical features of this specification are not limited to the specific names used in the following drawings.

[0597] Figure 27 is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power according to one embodiment of this specification.

[0598] According to Figure 27, the wireless power transmitter can enter the power transfer phase (S2710), which is related to transmitting wireless power.

[0599] As mentioned earlier, once a wireless power transmitter enters the power transfer phase, it can transfer power to a wireless power receiver. The wireless power receiver can then perform power control by periodically transmitting CE packets to the wireless power transmitter. The wireless power transmitter can also perform FOD during power transfer by receiving RP packets from the wireless power receiver. A detailed explanation of these processes has been given above, so a repetition will be omitted.

[0600] Furthermore, the wireless power transmitter and / or wireless power receiver can transmit a data stream to the other party in the capacity of a data stream initiator.

[0601] In other words, the wireless power transmitter can transmit a data stream to the wireless power receiver, or the wireless power transmitter can receive a data stream from the wireless power receiver (S2720). In this case, the data stream may include an initial ADC packet, at least one ADT packet, and a final ADC packet. The initial ADC packet may correspond to a packet associated with opening the data stream, and the final ADC packet may correspond to a packet associated with closing the data stream.

[0602] On the other hand, as described above, while the data stream is being transmitted, the wireless power transmitter and / or wireless power receiver can transmit reset information to the other party (S2730). That is, the wireless power transmitter can transmit reset information to the wireless power receiver regardless of whether it is the data stream initiator or responder. Moreover, the wireless power receiver can transmit reset information to the wireless power transmitter regardless of whether it is the data stream initiator or responder.

[0603] Thereafter, the wireless power transmitter and / or wireless power receiver can perform initialization of the data stream (S2740).

[0604] Here, even though the radio power transmitter and / or radio power receiver initialize the data stream, the data stream can remain open. That is, even if the data stream is reset and the data stream is transmitted again, the radio power transmitter and / or radio power receiver can immediately send the first ADT packet to the receiver without sending a separate initial ADC (i.e., without a separate data stream open).

[0605] However, if reset information is transmitted as described above, the data stream will not remain open, and if reset information is transmitted, the data stream will be temporarily closed and the data stream will be transmitted again from the beginning (as long as they are not mutually incompatible), the embodiments of this specification can still be applied.

[0606] The following provides a more detailed explanation of this specification. For ease of understanding, the following explanation will be based on an example in which a wireless power transmitter transmits a data stream to a wireless power receiver and a wireless power transmitter transmits reset information to the wireless power receiver. However, the following example is intended to facilitate understanding of the specification, and the following examples also apply to an example in which a wireless power transmitter transmits a data stream to a wireless power transmitter. Furthermore, the following examples also apply to an example in which a wireless power receiver transmits reset information to a wireless power transmitter.

[0607] The following drawings have been prepared to illustrate a specific example of this specification. The names of specific devices and signals / messages / fields shown in the drawings are presented illustratively, and the technical features of this specification are not limited to the specific names used in the following drawings.

[0608] Figure 28 is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power, according to another embodiment of this specification.

[0609] According to Figure 28, the wireless power transmitter can enter the power transfer phase related to transmitting the wireless power (S2810).

[0610] Thereafter, the wireless power transmitter can transmit a first data stream to the wireless power receiver during the power transfer phase (S2820). At this time, the first data stream may include an initial ADC (auxiliary data control) packet associated with opening the first data stream, at least one ADT (auxiliary data transport) packet, or a final ADC packet associated with closing the first data stream.

[0611] The wireless power transmitter can transmit reset information to the wireless power receiver to indicate a reset of the first data stream (S2830). In this case, the reset information may correspond to a type of ADC packet. Alternatively, the reset information may correspond to a packet newly defined separately from the ADC and ADT. Specific examples of reset information will be described later.

[0612] The wireless power transmitter can receive a response to the reset information from the wireless power receiver (S2840). At this time, if the wireless power transmitter transmits the reset information to the wireless power receiver via a type of ADC packet (or a newly defined packet), the response received by the wireless power transmitter from the wireless power receiver may be a DSR / ack packet.

[0613] In contrast, unlike in this diagram, if the wireless power receiver transmits reset information to the wireless power transmitter via a type of ADC packet (or a newly defined packet), the response received by the wireless power receiver from the wireless power transmitter can correspond to an ACK response (for example, a type of bit pattern).

[0614] Thereafter, the wireless power transmitter can perform a reset of the first data stream based on the reception of the response (S2850).

[0615] Here, the open state of the first data stream can be maintained both before and after the reset. More specifically, after the reset, the radio power transmitter can transmit the first data stream to the radio power receiver from the beginning. Here, since the open state of the first data stream is maintained, after the reset, the radio power transmitter can transmit at least one ADT packet to the radio power receiver without transmitting an initial ADC packet.

[0616] Of course, conversely, as mentioned above, the first data stream can be closed after a reset, and then reopened (i.e., the initial ADC packet can be sent).

[0617] On the other hand, the embodiments of this specification can also be applied to multi-stream systems. That is, they can also be applied when a wireless power transmitter transmits a second data stream to the wireless power receiver while transmitting a first data stream. In this case, based on the wireless power transmitter receiving a response to reset information from the wireless power receiver, the wireless power transmitter can perform the reset of the first data stream without performing the reset of the second data stream.

[0618] In other words, a wireless power transmitter and / or wireless power receiver can reset only the data streams that are subject to reset information. For this purpose, the reset information may include information that identifies the first data stream.

[0619] Here, performing a reset can mean that the wireless power transmitter discards the data stored below the transport layer based on the reset. This can be illustrated with the following diagram.

[0620] Figure 29 schematically illustrates the concept of resetting a data stream.

[0621] As shown in Figure 29, a wireless power transmitter and / or wireless power receiver (or data stream initiator and / or data stream responder) can discard all data in the transport layer / buffer, including incoming / outgoing data, if a reset is performed during data communication. In this case, the application layer can still be preserved.

[0622] For example, if data stream #2 is reset based on ADC / reset_#2 during data communication with application data streams #1, #2, and #3, the radio power transmitter and / or radio power receiver can perform the reset by deleting the local buffer data and / or incoming and outgoing data exchanged in the stream corresponding to #2. However, even in this case, the radio power transmitter and / or radio power receiver can continue data communication with the stream still open.

[0623] (1) Example of the structure of reset information

[0624] On the other hand, reset information is in the form of an ADC packet, and as mentioned above, reset information is a new packet format that did not exist previously.

[0625] Here, if the reset information takes the form of, for example, an ADC packet, it is as explained in the following diagram.

[0626] Figure 30 schematically shows an example of reset information.

[0627] As shown in Figure 30, reset information can take the form of a kind of ADC packet. That is, reset information can include request fields and parameter fields, like other ADC packets. In addition, reset information can include an application stream number field.

[0628] Each field is an example and is as follows:

[0629] -Request: 5-ADC / rst

[0630] -Parameter: Specifies the application stream information to be reset.

[0631] - Application Stream Number: Add B2 to specify the stream you wish to reset separately.

[0632] (2) Example flowchart for sending reset information

[0633] The examples mentioned above can be explained in more detail using a specific flowchart, as follows:

[0634] During data communication between wireless charging devices, there may be cases where the wireless power receiver and / or wireless power transmitter need to reset data communication due to unrecoverable communication errors and other communication errors.

[0635] In such cases, a configuration is provided that allows resetting on an application stream-by-stream basis, and a reset can be performed on a specific stream through this configuration. At this time, the radio power receiver and / or radio power transmitter can discard all data stored in the local buffer and / or incoming and outgoing data that has been exchanged up to that point.

[0636] In such cases, the application stream that performed the reset is initialized, but the stream can remain open. That is, after the reset, data communication can be restarted from the beginning.

[0637] For example, in the case of a data stream from a wireless power receiver to a wireless power transmitter, the wireless power transmitter and / or wireless power receiver can reset the stream and then continue the data stream from the wireless power receiver to the wireless power transmitter. In other words, the data stream is not terminated.

[0638] First, let's explain an example where a wireless power transmitter sends reset information to a wireless power receiver.

[0639] Figure 31 schematically shows an example of a wireless power transmitter transmitting reset information.

[0640] As shown in Figure 31, a wireless power transmitter can transmit reset information (for example, an ADC packet instructing the receiver to reset stream #3, i.e., ADC / reset / stream#3) to the wireless power receiver while transmitting a data stream to the receiver. Here, the example in Figure 31 illustrates an example where a wireless power transmitter transmits a data stream to a wireless power receiver, but the example in Figure 31 can also be applied when a wireless power receiver transmits a data stream to a wireless power transmitter.

[0641] When a wireless power transmitter sends reset information to a wireless power receiver, the wireless power receiver, after receiving the reset packet for the relevant stream from the wireless power transmitter, can perform a reset of the incoming and / or outgoing data and clear the local buffer. Thereafter, the wireless power receiver can send a DSR / ack to the wireless power transmitter.

[0642] The radio power transmitter can send a reset packet corresponding to the stream it wishes to reset (e.g., #3) as described above, and simultaneously with receiving a DSR / ack from the radio power receiver, it can perform a reset of the incoming and / or outgoing data and clear the local buffer.

[0643] To explain the example in Figure 31 in a different way, it is as follows: The wireless power transmitter can perform the reset function at the moment it signals to the wireless power receiver that it intends to reset a specific application stream and receives a DSR / ack from the receiver.

[0644] When a wireless power receiver receives a reset signal from a wireless power transmitter, it can perform the reset function. Upon completion of the reset function, the wireless power receiver can send a DSR / ack to the wireless power transmitter.

[0645] Based on the response from the radio power receiver, the radio power receiver and / or radio power transmitter discard the data stored in the local buffer and / or incoming and outgoing data that have been exchanged up to that point.

[0646] However, in this case, the wireless power transmitter and / or wireless power receiver may store application layer data, but may discard all transport layer data and data stored in local buffers exchanged up to the present, as well as incoming and outgoing data.

[0647] Even when all wireless power transmitters and / or wireless power receivers have completed their reset, the application stream in question can remain open. The wireless power transmitter can then continue to perform data communication with the application stream that has been reset.

[0648] In other words, if the initiator is a radio power transmitter and the responder is a radio power receiver before the reset, the radio power transmitter can remain the initiator and the radio power receiver can remain the responder after the reset. Conversely, if the initiator is a radio power receiver and the responder is a radio power transmitter before the reset, the radio power receiver can remain the initiator and the radio power transmitter can remain the responder after the reset.

[0649] The following describes an example in which a wireless power receiver transmits reset information to a wireless power transmitter.

[0650] Figure 32 schematically shows an example of a wireless power receiver transmitting reset information.

[0651] As shown in Figure 32, the radio power receiver can transmit reset information (for example, an ADC packet instructing the radio power transmitter to reset stream #3, i.e., ADC / reset / stream#3) to the radio power transmitter while transmitting a data stream to the radio power transmitter. Here, the example in Figure 32 illustrates an example where the radio power receiver transmits a data stream to the radio power transmitter, but the example in Figure 32 can also be applied when the radio power transmitter transmits a data stream to the radio power receiver.

[0652] The radio power transmitter can receive a reset packet corresponding to the stream it wishes to reset (e.g., #3), and simultaneously perform a reset of the incoming and / or outgoing data and clear the local buffer. The radio power transmitter can then send an ACK to the radio power receiver.

[0653] After receiving an ACK from the radio power transmitter, the radio power receiver can perform a reset, including resetting the incoming and / or outgoing data and clearing the local buffer.

[0654] Thereafter, the wireless power transmitter and / or wireless power receiver can restart data communication from the beginning while maintaining the open state of the data stream after the reset is complete.

[0655] To explain the example in Figure 32 in a different way, it is as follows: The moment a wireless power receiver signals to a wireless power transmitter that it intends to reset a specific application stream, and the wireless power receiver receives an ACK from the other wireless power receiver, the wireless power receiver can perform the reset function.

[0656] When the wireless power receiver receives a reset signal from the wireless power transmitter, it can perform the reset function. Upon completion of the reset function, the wireless power transmitter can send an ACK to the wireless power receiver.

[0657] Based on the response from the wireless power transmitter, the wireless power transmitter and / or wireless power receiver discard the data stored in the local buffer and / or incoming and outgoing data that have been exchanged up to that point.

[0658] However, in this case, the wireless power receiver and / or wireless power transmitter may store application layer data, but may discard all transport layer data and data stored in local buffers exchanged up to the present, as well as incoming and outgoing data.

[0659] Even when the wireless power receiver and / or wireless power transmitter have completed their reset, the application stream can remain open. The wireless power receiver can then continue to perform data communication with the application stream that has been reset.

[0660] In other words, if the initiator is a radio power receiver and the responder is a radio power transmitter before the reset, the radio power receiver can remain the initiator and the radio power transmitter can remain the responder after the reset. Conversely, if the initiator is a radio power transmitter and the responder is a radio power receiver before the reset, the radio power transmitter can remain the initiator and the radio power receiver can remain the responder after the reset.

[0661] The method for transmitting reset information will be explained below using diagrams in a different form.

[0662] Figure 33 shows another example of how reset information is transmitted.

[0663] As shown in Figure 33, the initiator and responder status can be maintained and the data stream can proceed regardless of who sends the reset information (i.e., regardless of whether the transmitting entity is a radio power receiver, radio power transmitter, initiator, or responder) until the data stream is closed.

[0664] A problem may occur while a wireless power transmitter and / or wireless power receiver are performing data communication with the data stream open, causing the wireless power transmitter to send an ADC / reset. In this case, the wireless power receiver can receive the reset information and perform the reset function. After the reset function is complete, the wireless power receiver can send a DSR / ack to the wireless power transmitter. If the wireless power transmitter receives a DSR / ack as a response from the wireless power receiver, it can perform the reset function. This is because if the wireless power transmitter were to perform a reset before receiving a response from the wireless power receiver, it would be difficult for the wireless power transmitter to analyze the response received from the wireless power receiver.

[0665] When both the wireless power receiver and / or wireless power transmitter perform a reset, the reset stream remains open. With the stream open, the wireless power transmitter and / or wireless power receiver can then resume data communication.

[0666] On the other hand, as mentioned above, even if a wireless power transmitter or receiver sends reset information to the other party, it may not be able to receive a response from the other party. In such cases, a problem may occur where data communication should continue despite a problem occurring in the wireless power system.

[0667] Therefore, as stated above, this specification describes methods for terminating (in other words, aborting) a data stream.

[0668] Here, the conditions for initiating a forced termination are separate from the conditions for the reset. That is, the wireless power transmitter and / or wireless power receiver can immediately perform a forced termination without resetting the data stream if the problematic situation occurs.

[0669] In response, the wireless power transmitter and / or wireless power receiver may attempt a reset as described above, and if the wireless power transmitter and / or wireless power receiver cannot receive a response to the reset information from the other party (or if a response cannot be received within a certain period of time; or if a response to the reset information cannot be received despite repeatedly transmitting the reset information a certain number of times), it may proceed with a termination protocol.

[0670] The following provides a more detailed explanation of examples of forced termination.

[0671] 2. Terminate the data stream.

[0672] The following drawings have been prepared to illustrate a specific example of this specification. The names of specific devices and signals / messages / fields shown in the drawings are presented illustratively, and the technical features of this specification are not limited to the specific names used in the following drawings.

[0673] Figure 34 is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power, according to another embodiment of this specification.

[0674] According to Figure 34, the wireless power transmitter can enter the power transfer phase related to transmitting wireless power (S3410).

[0675] As mentioned earlier, once a wireless power transmitter enters the power transfer phase, it can transfer power to a wireless power receiver. The wireless power receiver can then perform power control by periodically transmitting CE packets to the wireless power transmitter. Furthermore, the wireless power transmitter can also perform FOD during power transfer by receiving RP packets from the wireless power receiver. A detailed explanation of these processes has already been given, so a repetition will be omitted.

[0676] Furthermore, the wireless power transmitter and / or wireless power receiver can transmit a data stream to the other party in the capacity of a data stream initiator.

[0677] In other words, the wireless power transmitter can transmit a data stream to the wireless power receiver, or the wireless power transmitter can receive a data stream from the wireless power receiver (S3420). In this case, the data stream may include an initial ADC packet, at least one ADT packet, and a final ADC packet. The initial ADC packet may correspond to a packet associated with opening the data stream, and the final ADC packet may correspond to a packet associated with closing the data stream.

[0678] On the other hand, as described above, while the data stream is being transmitted, the wireless power transmitter and / or wireless power receiver can transmit abort information to the other party (S3430). That is, the wireless power transmitter can transmit abort information to the wireless power receiver regardless of whether it is the data stream initiator or responder. Moreover, the wireless power receiver can transmit abort information to the wireless power transmitter regardless of whether it is the data stream initiator or responder.

[0679] Thereafter, the radio power transmitter and / or radio power receiver may abort (i.e., terminate) the data stream (S3440).

[0680] Here, the wireless power transmitter can abort the first data stream based on transmitting abort information. Alternatively, the wireless power transmitter can abort the first data stream based on receiving a response to the abort information.

[0681] After abort, the wireless power transmitter can close the first data stream.

[0682] Here, the wireless power transmitter can discard data stored below the transport layer based on performing an abort. This is illustrated in the diagram below.

[0683] Figure 35 schematically illustrates the concept of data stream abort.

[0684] As shown in Figure 35, a wireless power transmitter and / or wireless power receiver (or data stream initiator and / or data stream responder) can discard all data in the transport layer / buffer, including incoming / outgoing data, if an abort occurs during data communication. In this case, the application layer can still be preserved.

[0685] For example, in the case of an abort during data communication for a specific application stream, either the receiver or transmitter can send abort information, regardless of whether they are the initiator or responder exchanging data.

[0686] (1) Examples of the structure of abort information

[0687] On the other hand, abort information is in the form of a packet for separate data communication (TPL), and as mentioned above, abort information is a modified form of an existing packet. In other words, the way in which a wireless power receiver / transmitter expresses its intention to abort to the other device is by providing a separate TPL packet or by adding bits to an existing packet (DSR / ADC / other packets).

[0688] Here, if the abort information takes the form of a packet for a separate data communication, for example, it is as explained in the following diagram.

[0689] Figure 36 schematically shows an example of abort information.

[0690] As shown in Figure 36, an example of abort information is that a separate packet used in data communication can be defined.

[0691] This information can include fields (information) related to the TPL type. For example, the following values ​​may be provided:

[0692] 0x00-TPL / Pause

[0693] 0x01-TPL / Busy

[0694] 0x02-TPL / Abort

[0695] 0x03~0xFF-TPL / Reserved

[0696] On the other hand, if the abort information takes the form of an existing packet for data communication, for example, as explained in the following diagram. The following example illustrates how a DSR packet is used for abort information.

[0697] Figure 37 schematically shows another example of abort information.

[0698] As shown in Figure 37, one example of abort information is the use of DSR packets, which are used in data communication. For example, a separate field called TPL / type can be defined in a DSR packet.

[0699] This information can include fields (information) related to the TPL type. For example, the following values ​​may be provided:

[0700] 0x00-TPL / Pause

[0701] 0x01-TPL / Busy

[0702] 0x02-TPL / Abort

[0703] 0x03~0xFF-TPL /

[0704] (2) Example flowchart for sending abort information

[0705] The examples mentioned above can be explained in more detail using a specific flowchart, as follows:

[0706] There may be times when data communication between wireless charging devices cannot proceed further. Examples of such situations include when charging is impossible due to a specific abnormal condition, or when charging is temporarily interrupted, or when charging is not functioning properly, or when charging is uncertain, or when an abnormality occurs during data communication.

[0707] In the aforementioned cases, the wireless power transmitter and / or wireless power receiver may terminate data communication by indicating their intention to abort to the other device.

[0708] Here, at the end of data communication, the wireless power transmitter and / or wireless power receiver can discard all data stored in the local buffer and / or incoming and outgoing data that they have exchanged up to that point. However, even in this case, the wireless power transmitter and / or wireless power receiver can still save data in the application layer buffer.

[0709] First, let's explain an example where a wireless power transmitter sends abort information to a wireless power receiver.

[0710] Figures 38 and 39 are flowcharts illustrating an example of a wireless power transmitter transmitting abort information to a wireless power receiver.

[0711] According to Figures 38 and 39, data communication can be terminated the moment a wireless power transmitter signals its intention to terminate to a wireless power receiver, or the moment it signals its intention to terminate and receives a DSR / ack from the other party. In such a case, the wireless power transmitter and / or wireless power receiver can discard all data transmitted and received up to that point, data stored in the local buffer, and / or incoming and outgoing data.

[0712] However, wireless power transmitters and / or wireless power receivers can store application layer data. They can also discard all transport layer, local buffer, and incoming / outgoing data.

[0713] A wireless power receiver and / or wireless power transmitter may indicate to the other device its intention to terminate the connection by adding bits to a Pause packet or an existing packet (DSR / ADC / other packets). The details of this are as described above.

[0714] The difference between Figure 38 and Figure 39 is as follows: In Figure 38, the data stream can be terminated the moment the wireless power transmitter indicates its intention to terminate the data. In Figure 39, the data stream can be terminated when the wireless power transmitter indicates its intention to terminate the data and the wireless power transmitter receives a DSR / ack from the wireless power receiver.

[0715] The following describes an example in which a wireless power receiver transmits abort information to a wireless power transmitter.

[0716] Figures 40 and 41 are flowcharts illustrating an example of a wireless power transmitter transmitting abort information to a wireless power receiver.

[0717] According to Figures 40 and 41, data communication can be terminated the moment the radio power receiver indicates its intention to terminate the radio power transmitter, or the moment it receives an ACK from the other party after indicating its intention to terminate. The radio power transmitter and / or radio power receiver can discard all data transmitted and received up to that point, data stored in the local buffer, and / or incoming and outgoing data. However, even in this case, the radio power transmitter and / or radio power receiver can still save application layer data. On the other hand, the radio power transmitter and / or radio power receiver can discard all transport layer, local buffer data, and incoming and outgoing data.

[0718] Here, a wireless power receiver and / or wireless power transmitter can signal its intention to terminate to the other device by adding bits to an abort packet or an existing packet (DSR / ADC / other packet). Specific examples of this are as described above.

[0719] The difference between Figure 40 and Figure 41 is as follows: In Figure 40, the data stream can be terminated the moment the wireless power receiver indicates its intention to terminate the data. In Figure 41, the data stream can be terminated when the wireless power receiver indicates its intention to terminate the data and receives an ACK from the wireless power transmitter.

[0720] Figure 42 shows another example of how abort information can be transmitted.

[0721] As shown in Figure 42, if an abort occurs during data communication of a specific application stream, abort information can be sent to the other party regardless of whether it is the initiator and / or responder exchanging data (and whether it is the wireless power transmitter and / or wireless power receiver).

[0722] In the example shown in Figure 42, the wireless power transmitter can act as an initiator and transmit abort information to the wireless power receiver. Based on the transmission of the abort information, the data stream between the wireless power transmitter and the wireless power receiver can be terminated.

[0723] 3. Data stream reset and termination merge

[0724] The embodiments described herein have been explained once from the perspective of resetting the data stream and once from the perspective of forcibly terminating the data stream.

[0725] Herein, the above embodiments can operate independently as described above, and at the same time, they can also operate in combination.

[0726] Furthermore, the aforementioned examples can also be applied when the wireless power transmitter and / or wireless power receiver supports multistream.

[0727] An example of how the above examples are combined can be explained with reference to the drawings below.

[0728] Figure 43 is a flowchart illustrating a method by which a wireless power transmitter transmits wireless power, according to another embodiment of this specification.

[0729] As shown in Figure 43, the radio power transmitter and / or radio power receiver can open the first data stream (S4310). That is, the radio power transmitter can send an initial ADC packet for the first data stream (i.e., with the channel of the first data stream marked) to the radio power receiver. Or, the radio power receiver can send an initial ADC packet for the first data stream (i.e., with the channel of the first data stream marked) to the radio power transmitter.

[0730] On the other hand, as mentioned above, this specification can support multi-stream opening. That is, in this specification, a wireless power transmitter and a wireless power receiver can exchange a second data stream while exchanging a first data stream.

[0731] In other words, the radio power transmitter and / or radio power receiver can open a second data stream (S4320). That is, the radio power transmitter can send an initial ADC packet to the radio power receiver for the second data stream (i.e., with the channel of the second data stream marked). Or, the radio power receiver can send an initial ADC packet to the radio power transmitter for the second data stream (i.e., with the channel of the second data stream marked).

[0732] i) In summary, according to this specification, a multi-stream exchange between a wireless power transmitter and a wireless power receiver can be provided.

[0733] Furthermore, for example, a wireless power transmitter can transmit first reset information for a first data stream to a wireless power receiver (S4330). This first reset information may take the form of a type of ADC packet, as described above, or it may take the form of a separate data packet. The first reset information may also be marked to indicate that it pertains to the first data stream.

[0734] The wireless power transmitter can receive a response from the wireless power receiver for the first reset information (S4340). Here, the response received by the wireless power transmitter from the wireless power receiver is, for example, DSR / ack. If the wireless power receiver receives a response from the wireless power transmitter, the response is ACK.

[0735] Thereafter, the wireless power transmitter and / or wireless power receiver can initialize the first data stream (S4350).

[0736] However, since a wireless reset corresponds to a reset of the first data stream, the wireless power transmitter and / or wireless power receiver can transmit or receive the second data stream. In other words, the second data stream is not initialized.

[0737] ii) In summary, according to this specification, a reset can be provided for a specific data stream.

[0738] However, even if a reset is provided for a specific data stream, this specification does not exclude from the scope of rights the ability to perform a reset on all open data streams. Thus, examples of performing a reset on all data streams and examples of performing an abort (on a specific stream or all streams) can be coupled together.

[0739] On the other hand, the wireless power transmitter can transmit a second reset information for the second data stream to the wireless power receiver (S4360).

[0740] In this case, the wireless power transmitter is unable to receive a response from the wireless power receiver for the second data stream.

[0741] If certain conditions are met, the radio power transmitter may transmit abort information for the second data stream to the radio power receiver (S4370).

[0742] The conditions in this case may include the case where the radio power transmitter does not receive a response to the second reset information within a specific time period (which may be exchanged or predefined between the radio power transmitter and the radio power receiver) after the radio power transmitter has transmitted the second reset information.

[0743] Alternatively, the conditions in this case may include the case where the radio power transmitter does not receive a response to the second reset information until it has transmitted the second reset information a predetermined number of times (which may be exchanged or predefined between the radio power transmitter and the radio power receiver in advance).

[0744] Thereafter, the wireless power transmitter and wireless power receiver can abort the second data stream (S4380).

[0745] iii) In summary, according to this specification, aborts can be provided for specific data streams.

[0746] However, even if aborts are provided for specific data streams, this specification does not exclude from the scope of rights the ability to abort all open data streams. Thus, examples of aborting all data streams and examples of resetting (for specific streams or all streams) can be coupled together.

[0747] iv) In summary, according to this specification, the transmission of reset information and the transmission of abort information can be combined.

[0748] Of course, as mentioned earlier, the examples of sending reset information and sending abort information can operate separately.

[0749] The embodiments of this specification will be described again below from the perspectives of various subjects.

[0750] The following drawings have been prepared to illustrate a specific example of this specification. The names of specific devices and signals / messages / fields shown in the drawings are presented illustratively, and the technical features of this specification are not limited to the specific names used in the following drawings.

[0751] Figure 44 is a flowchart illustrating a method for transmitting wireless power from the perspective of a wireless power transmitter, according to one embodiment of this specification.

[0752] According to Figure 44, the wireless power transmitter can enter the power transfer phase related to transmitting the wireless power (S4410).

[0753] The wireless power transmitter can transmit a first data stream to the wireless power receiver during the power transfer phase (S4420).

[0754] Here, the wireless power transmitter transmits reset information to the wireless power receiver to indicate a reset of the first data stream, the wireless power transmitter receives a response to the reset information from the wireless power receiver, and the wireless power transmitter can perform a reset of the first data stream based on the receipt of the response.

[0755] Here, the open state of the first data stream can be maintained before and after the reset. After the reset, the radio power transmitter can transmit the first data stream to the radio power receiver from the beginning. The first data stream includes an initial ADC (auxiliary data control) packet associated with opening the first data stream, at least one ADT (auxiliary data transport) packet, or a final ADC packet associated with closing the first data stream. After the reset, the radio power transmitter can transmit at least one ADT packet to the radio power receiver without transmitting the initial ADC packet.

[0756] Here, the wireless power transmitter can transmit a second data stream to the wireless power receiver while transmitting the first data stream. Based on the wireless power transmitter receiving the response to the reset information from the wireless power receiver, the wireless power transmitter can perform the reset of the first data stream without performing the reset of the second data stream.

[0757] Here, the reset information may include information that identifies the first data stream.

[0758] Here, the wireless power transmitter can discard data stored below the transport layer based on performing the reset.

[0759] Here, the wireless power transmitter can transmit abort information to the wireless power receiver indicating the abort of the first data stream based on the inability to receive the response. The wireless power transmitter can then abort the first data stream based on transmitting the abort information. Alternatively, after the abort, the wireless power transmitter can close the first data stream. The wireless power transmitter can then abort the first data stream based on receiving a response to the abort information. The wireless power transmitter can then discard the data stored below the transport layer based on performing the abort.

[0760] Although not shown separately, a wireless power transmitter may be provided. The wireless power transmitter may include a converter related to transmitting wireless power to a wireless power receiver, and a communications / controller related to controlling the transmission of the wireless power. The wireless power transmitter may enter a power transmission phase related to transmitting the wireless power, and transmit a first data stream to the wireless power receiver during the power transmission phase. The wireless power transmitter may transmit reset information to the wireless power receiver to indicate a reset of the first data stream, the wireless power transmitter may receive a response to the reset information from the wireless power receiver, and the wireless power transmitter may perform a reset of the first data stream based on the receipt of the response.

[0761] Figure 45 is a flowchart illustrating a method for receiving wireless power from the perspective of a wireless power receiver, according to one embodiment of this specification.

[0762] According to Figure 45, the wireless power receiver can enter the power transfer phase associated with receiving the wireless power (S4510).

[0763] The wireless power receiver can receive a first data stream from the wireless power transmitter during the power transfer phase (S4520).

[0764] Here, the wireless power receiver receives reset information from the wireless power transmitter indicating a reset of the first data stream, the wireless power receiver performs a reset of the first data stream based on receiving the reset information, and the wireless power receiver can transmit a response to the reset information to the wireless power transmitter based on performing the reset.

[0765] Although not shown separately, a wireless power receiver may be provided. The wireless power receiver may include a power pickup associated with receiving wireless power from a wireless power transmitter and a communications / controller associated with controlling the reception of the wireless power. The wireless power receiver may enter a power transfer phase associated with receiving the wireless power and receive a first data stream from the wireless power transmitter during the power transfer phase. The wireless power receiver may receive reset information from the wireless power transmitter indicating a reset of the first data stream, the wireless power receiver may perform a reset of the first data stream based on receiving the reset information, and the wireless power receiver may transmit a response to the reset information to the wireless power transmitter based on performing the reset.

[0766] The effects of this specification are described below.

[0767] To explain the effects, I will reiterate the aforementioned issues.

[0768] Essentially, this specification provides a configuration that discards all transport layer buffers and incoming and / or outgoing data via reset or abort, thus resolving the issue when memory for data storage is stuck and further recovery is impossible. Furthermore, in the case of a reset, a configuration is provided that keeps the application stream open, allowing for immediate data communication. In other words, data transmission time can be optimized.

[0769] On the other hand, if a problem occurs in storing / communicating data for a particular stream (or if a problem occurs in the transport layer) while various application data streams are progressing, other streams (stream 1 and stream 3) may remain unaffected, excluding the affected stream (let's assume, for example, that a problem occurs in stream 2).

[0770] In this case, resetting or terminating all streams may also reset or terminate other streams that are not affected (e.g., Stream 1 and Stream 3). In this case, the wireless power transmitter and / or wireless power receiver must restart data communication from the beginning for all streams that are not affected. This can be considered an inefficient method.

[0771] According to this specification, when a problem occurs with a specific stream, the inefficiency of unnecessarily resetting or terminating a non-problematic stream can be prevented by resetting or terminating only that specific stream. As a result, data transmission time can be reduced because non-problematic data streams can continue to be transmitted.

[0772] Additionally, if a wireless power transmitter and / or wireless power receiver performs a reset immediately after transmitting reset information to the other party, a communication error may occur in which the other party cannot receive a response, or even if a response is received, it cannot be parsed. To prevent this problem, this specification provides a configuration in which, in the case of resetting a data stream, the wireless power transmitter and / or wireless power receiver performs the reset after receiving a response from the other party, instead of performing the reset immediately after transmitting reset information to the other party. This has the effect of preventing communication errors.

[0773] The effects obtained through specific examples in this specification are not limited to those listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand or derive from this specification. Thus, the specific effects of this specification are not limited to those explicitly stated herein, and may include a variety of effects that can be understood or derive from the technical features of this specification.

[0774] The claims described herein may be combined in various ways. For example, the technical features of the method claims herein may be combined and embodied in an apparatus, or the technical features of the apparatus claims herein may be combined and embodied in a method. Furthermore, the technical features of the method claims and the technical features of the apparatus claims herein may be combined and embodied in an apparatus, or the technical features of the method claims and the technical features of the apparatus claims herein may be combined and embodied in a method.

Claims

1. In a method for transmitting wireless power in a wireless power transmission system, The aforementioned method, Executed by a wireless power transmitter, The steps include executing a digital pin and receiving a response from a wireless power receiver, Steps to proceed to the configuration phase, The steps include transmitting a first ADC (auxiliary data control) packet to the wireless power receiver to open a first data stream, The steps include transmitting at least one ADT (auxiliary data transport) packet to the first data stream to the wireless power receiver, A step of transmitting a second ADC packet for resetting the first data stream to the radio power receiver, wherein the second ADC packet includes stream number information relating to the first data stream, A method comprising the step of receiving a response to the second ADC packet from the wireless power receiver.

2. In a wireless power transmitter, A converter related to transmitting wireless power to a wireless power receiver, A communication / controller related to controlling the transmission of the wireless power is provided, The aforementioned wireless power transmitter is Execute the digital pin and receive a response from the wireless power receiver. Proceed to the configuration phase, A first ADC (auxiliary data control) packet is transmitted to the wireless power receiver to open the first data stream. At least one ADT (auxiliary data transport) packet for the first data stream is transmitted to the wireless power receiver. A second ADC packet for resetting the first data stream is transmitted to the wireless power receiver, the second ADC packet containing stream number information relating to the first data stream, A wireless power transmitter that receives a response to the second ADC packet from the wireless power receiver.

Images