Device-to-grid discharging and charging

Abstract

Aspects of the disclosure relate to wireless communications, and more particularly, to techniques for device-to-grid charge transfer. Certain aspects relate to a method for device-to-grid charge transfer. The method generally includes receiving, from a controller associated with a grid, a request for a transfer of charge from a wireless communication device to the grid, where the request indicates a power requirement of the grid during a time period; transmitting a message indicating whether to accept the request for the transfer of charge based on the power requirement; and initiating the transfer of charge from the wireless communication device to the grid during the time period when the message indicates to accept the transfer of charge.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Patent Application No. 18 / 516,611, filed November 21, 2023, entitled “Device to Grid Discharging and Charging,” which is assigned to the assignee of this application and whose entire contents are incorporated herein by reference. Technical Field

[0002] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for device-to-grid charge transfer. Background Technology

[0003] The power grid faces increased challenges during periods of high electricity demand. Peak power consumption can be driven by a variety of factors. The increased power consumption from the grid during these periods can strain the grid infrastructure, leading to inefficiencies, reliability issues, and increased operating costs.

[0004] Vehicle-to-grid (V2G) technology allows electricity to flow from vehicles to power lines. For example, V2G can be used to supply power to the grid during peak hours, regulate grid load, reduce grid storage requirements, and alleviate the need for many fuel-based plants. During charging, the vehicle acts as an electrical load, with its battery drawing power from the grid. During discharging, the vehicle can act as a power source, injecting power back into the grid. V2G can be used with all-electric, hybrid, or even hydrogen / solar or supplemental fuel cell units. Vehicles may include communication controllers (also known as Electric Vehicle Communication Controllers (EVCCs)) that can communicate with the charging station's communication controller (e.g., also known as Service Equipment Communication Controllers (SECCs)). The SECC can act as a bridge between the charging station's DC charger and the vehicle's battery management system. With the increasing ownership of hybrid and electric vehicles, efficient V2G systems are crucial. Typical V2G systems do not provide an efficient system for managing charge transfer. For example, current V2G systems cannot provide an organized and efficient system for coordinating and activating charge transfer to the grid. Summary of the Invention

[0005] Some aspects relate to a method for device-to-grid charge transfer. The method generally includes: receiving from a controller associated with the grid a request for charge transfer from a wireless communication device to the grid, wherein the request indicates power requirements of the grid during a certain time period; transmitting a message based on the power requirements indicating whether the request for charge transfer is accepted; and configuring the charge transfer from the wireless communication device to the grid during the time period when the message indicates acceptance of the charge transfer.

[0006] Some aspects relate to a method for device-to-grid charge transfer. The method generally includes: transmitting from a controller associated with the grid a request for charge transfer from a wireless communication device to the grid, wherein the request indicates a power requirement of the grid during a certain time period; receiving, based on the power requirement, a message indicating whether to accept the request for the charge transfer; and configuring the charge transfer from the wireless communication device to the grid during the time period when the message indicates acceptance of the charge transfer.

[0007] Some aspects relate to a method for device-to-grid charge transfer. The method generally includes: transmitting from a controller associated with a wireless communication device a request for a charge transfer from the wireless communication device to the grid, wherein the request indicates an amount of power available for transfer to the grid during a certain time period; receiving a message indicating whether the request for the charge transfer is accepted; and configuring the charge transfer from the wireless communication device to the grid during the time period when the message indicates acceptance of the charge transfer.

[0008] Some aspects relate to a method for device-to-grid charge transfer. The method generally includes: receiving from a controller associated with a wireless communication device a request for a charge transfer from the wireless communication device to the grid, wherein the request indicates an amount of power available for transfer to the grid during a certain time period; transmitting a message indicating whether the request for the charge transfer is accepted; and configuring the charge transfer from the wireless communication device to the grid during the time period when the message indicates acceptance of the charge transfer.

[0009] Other aspects provide: an apparatus capable of operating to, being configured to, or otherwise adapted to perform one or more of the foregoing methods and / or those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of the apparatus, cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0010] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example decomposed base station architecture is described.

[0014] Figure 3 Various aspects of the example base station and example user equipment are described.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0016] Figure 5 An example of a vehicle-to-grid (V2G) charge transfer system is shown.

[0017] Figure 6 An example of a V2G charge transfer system is shown, which includes an electric vehicle (EV) communication controller (EVCC), a power supply unit (SE), and an auxiliary actuator (SA).

[0018] Figure 7 An example is a V2G charge transfer system comprising multiple vehicles that transfer charge to the power grid.

[0019] Figure 8 Example signaling for performing grid-initiated V2G discharges according to certain aspects of this disclosure is illustrated.

[0020] Figure 9 Examples of signaling for executing a vehicle-initiated V2G discharge are illustrated according to certain aspects of this disclosure.

[0021] Figure 10 Examples of signaling for V2G selective group transfer according to certain aspects of this disclosure are illustrated.

[0022] Figure 11 An example is illustrated of a family of multiple vehicles participating in V2G charge transfer according to certain aspects of this disclosure.

[0023] Figure 12 Example techniques for V2G transfer using communication between a grid controller and a SECC, according to certain aspects of this disclosure, are illustrated.

[0024] Figure 13 An example of a method for device-to-grid charge transfer performed at a controller associated with a wireless communication device, according to certain aspects of this disclosure, is shown.

[0025] Figure 14 An example of a method for transferring device-to-grid charge at a controller associated with a grid controller is shown.

[0026] Figure 15 An example of a method for performing device-to-grid charge transfer at a controller associated with a wireless communication device is shown.

[0027] Figure 16 An example of a method for transferring device-to-grid charge at a controller associated with a grid controller is shown.

[0028] Figure 17 Various aspects of the example communication device are described. Detailed Implementation

[0029] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0030] Various aspects of this disclosure provide apparatus, methods, processing systems, and computer-readable media for device-to-grid charge transfer. While some aspects of this disclosure are described with respect to charge transfer from vehicles to the grid to facilitate understanding, certain aspects of this disclosure are applicable to charge transfer from any device (e.g., a wireless communication device) to the grid.

[0031] Some aspects provide techniques for grid-initiated charge transfer to the power grid. For example, a wireless communication device may receive a request from a grid controller for a charge transfer from the device to the grid. This request may include various charge transfer parameters, such as the power requirements of the grid during a specific time period. Based on this request, the device may transmit a response accepting or rejecting the request, as described in more detail herein.

[0032] Some aspects provide techniques for device-initiated (e.g., vehicle-initiated) charge transfers to the grid. For example, the device may send a request for charge transfer to the grid controller. This request may include charge transfer parameters such as the device's current battery percentage, a charge transfer window, or the total power available for transfer. The grid controller may accept or reject the charge transfer. In some aspects, the device's prior history of charge transfers may be used to predict periods within which a charge transfer can be requested, thus providing an efficient method that is agnostic to the owner initiating the charge transfer from the device to the grid.

[0033] Some aspects of this disclosure relate to managing multiple wireless communication devices (e.g., vehicles) to collaboratively perform charge transfer to a power grid. For example, the devices may receive requests for group charge transfer from a power grid controller. The devices may (e.g., via requests for voting and responses) identify one or more other devices that wish to participate in the group charge transfer to the power grid. Based on the participation of other devices, the devices may accept or reject requests for group charge transfer from the power grid controller. In some cases, the devices may also manage the allocation of the amount of charge to be transferred by each device during the group charge transfer, as described in more detail herein.

[0034] Some aspects of this disclosure relate to techniques for charge transfer using communication between a grid controller and a power supply equipment communication controller (SECC) associated with one or more wireless communication devices (e.g., instead of communication between the grid and the devices themselves). For example, the SECC may receive (or transmit) a request for charge transfer to the grid from the grid controller. The SECC can then manage the setup and control of the charge transfer. For example, the SECC may manage the charging levels among the devices associated with the SECC so that no single device is over-discharged.

[0035] Specific aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, grid-initiated charge transfer provides techniques for managing and initiating charge transfers from one or more devices to the grid, thereby improving charge transfer efficiency. For example, a grid controller may indicate parameters, such as the grid's power requirements, allowing charge transfers to be performed when the grid has high power needs. Some aspects provide device-initiated charge transfer, allowing a device to request a charge transfer to the grid in a highly efficient manner. For example, a device may request a charge transfer when it typically has excess charge. The device may consider charge transfer history to identify the most appropriate time for the charge transfer, providing an efficient method that is agnostic to the owner initiating the charge transfer. Some aspects provide techniques for managing groups of devices (e.g., vehicle queues), allowing for efficient management and coordination of groups of devices requesting charge transfers to serve the grid. In some aspects, charge transfer coordination may be performed using an SECC (e.g., instead of the devices themselves), thereby keeping vehicle information private and allowing the SECC to efficiently coordinate charge transfers.

[0036] An introduction to wireless communication networks

[0037] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0038] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0039] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects, such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0040] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0041] Figure 1 Various example UEs 104 are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0042] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to BS 102 and / or downlink (DL) (also known as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0043] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each BS in BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0044] Although BS 102 is described as a single communication device in various aspects, it can be implemented in various configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0045] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0046] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz-7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0047] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0048] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1 The BS 180 (180) can utilize beamforming 182 with the UE 104 to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0049] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0050] Some UEs 104 may use device-to-device (D2D) communication links 158 (e.g., PC5 links) to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0051] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0052] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0053] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to BS 102 in a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0054] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0055] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0056] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0057] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0058] In some respects, relative to Figure 1 The described UE can be any suitable controller or modem for wireless communication devices such as vehicles. The UE can communicate with the controller 199 associated with the power grid via a Uu link or via a side link (e.g., a PC5 link).

[0059] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0060] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the cells, or an associated processor or controller that provides instructions to the cell's communication interface, may be configured to communicate with one or more other cells via the transmission medium. For example, these cells may include a wired interface configured to receive signals or transmit signals to one or more other cells via a wired transmission medium. Additionally or alternatively, a cell may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other cells, or both.

[0061] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling, as needed.

[0062] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0063] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, an RU240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the implementation of the DU 230 and CU 210 in cloud-based RAN architectures (such as vRAN architectures).

[0064] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0065] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0066] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0067] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0068] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively referred to as 334), transceivers 332a-332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0069] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively referred to as 352), transceivers 354a-354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0070] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical HARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Shared PDCCH (GC PDCCH), and / or others. In some examples, this data may be for the Physical Downlink Shared Channel (PDSCH).

[0071] The transmitter processor 320 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0072] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0073] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a-354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0074] The MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes (e.g., demodulates, deinterleaves, and decodes) the detected symbols, provides the decoded data for UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0075] Regarding the example uplink transmission, UE 104 further includes a transmission processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmission processor 364 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmission processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0076] At BS 102, uplink signals from UE 104 can be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0077] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0078] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0079] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms for outputting data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-t, antenna 334a-t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms for acquiring data, such as from antenna 334a-t, transceiver 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0080] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms for outputting data, such as outputting data from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceiver 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms for acquiring data, such as acquiring data from antenna 352a-t, transceiver 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0081] In some respects, one or more processors may be configured to perform various operations (such as those associated with the methods described herein) and respectively send (output) data to another interface configured to send data or receive (obtain) data from another interface configured to receive data.

[0082] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0083] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0084] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) reduce system bandwidth (e.g., as...) Figure 4B and Figure 4D The data (as depicted in the diagram) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0085] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0086] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X can be flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0087] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 6 allow 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2µ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. Therefore, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 960 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0088] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0089] like Figure 4A As illustrated, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0090] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0091] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0092] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

[0093] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0094] As in Figure 4CAs illustrated, some REs carry DMRS for channel estimation at the base station (indicated as R for a specific configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol preceding the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE 104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0095] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0096] An introduction to vehicle-to-grid (V2G) charge transfer.

[0097] Vehicle-to-grid (V2G) is a technology that allows electricity to flow from a vehicle (also referred to herein as a “vehicle”) to an electric power line. V2G can be used to supply electrical power to the grid during peak hours, regulate and balance grid loads, reduce power storage, and reduce fossil fuel-based plants. During charging operations, V2G charge transfer can behave as an electrical load as the battery draws power from the grid. During discharging operations, V2G power transfer behaves as a power source, injecting electricity into the grid. V2G can be used with all-electric, hybrid, or even hydrogen, solar, or supplemental fuel cell vehicles. While some aspects of this disclosure are described with respect to charge transfer from a vehicle to the grid to facilitate understanding, some aspects of this disclosure can be applied to charge transfer from any wireless communication device to the grid, such as a heating, ventilation, and air conditioning (HVAC) system.

[0098] Figure 5A V2G charge transfer system 500 is illustrated. System 500 may include multiple V2G devices (e.g., vehicles transferring charge to the grid) that can be coupled to a DC link 502. DC power from DC link 502 can be converted to AC power via a DC-to-AC converter 504. As shown, the AC power can be supplied to the grid 506. With the increasing ownership of hybrid and electric vehicles (EVs), efficient V2G discharge management services are important. A similar architecture can be implemented for any wireless communication device, allowing charge transfer from the device to the grid. For example, an HVAC system can be coupled to a DC link for charge transfer to or from the grid. In some aspects, the grid can be associated with a grid controller, and various parameters used to facilitate charge transfer can be communicated between the device and the grid controller. For example, a device or grid controller can request a charge transfer from the device to the grid, where parameters indicate the time for the transfer or the amount of charge to be transferred.

[0099] Figure 6 An exemplary V2G charge transfer system 600 is illustrated, including an EV communication controller (EVCC), a power supply unit (SE), and an auxiliary actuator (SA). As shown, a vehicle system 602 may include a vehicle communicatively coupled to the EVCC, which may be an EV, a battery EV (BEV), or a plug-in hybrid EV (PHEV). The EVCC may be coupled to a charger system 604, including an SE communication controller (SECC) and an EV power supply unit (EVSE). For example, the EVSE may include charging / discharging equipment, which may be private or public. The vehicle may be coupled to the charger using power line communication (PLC), charging cables, or inductive coupling. As shown, the charger system 604 may be coupled to an auxiliary participant 606 (e.g., via a transmit control protocol (TCP) connection or WiFi), which may be a software entity managed by a public or private entity, such as a city gas and electric company or any utility company. The auxiliary participant may also be a private entity, such as the owner of a parking structure (e.g., where the charger system 604 may be located).

[0100] Cloud-connected power grids and cellular-connected SECCs can communicate with each other to negotiate various attributes used by the SECC to monitor energy specifications and for billing based on consumption. Certain aspects of this disclosure relate to techniques for power grids to notify vehicles of their need for replenishment under peak load conditions. Certain aspects relate to the power grid sending V2G discharge requests to vehicles served by the same grid, thereby allowing such vehicles to transfer charge to serve the grid's power needs. For example, sending V2G discharge requests to vehicles that do not have a connection to the grid or may never connect to the grid for V2G charging or discharging purposes is not useful.

[0101] In one scenario, a car owner may be unwilling to authorize the transfer of energy from their vehicle to the grid due to an upcoming trip. Some aspects concern how EV owners can efficiently schedule V2G discharge in terms of cost and energy. In another example, a single household may own several EVs. Some aspects provide an efficient way to charge and / or discharge multiple EVs via cloud services.

[0102] Some aspects also offer technologies for managing V2G discharge in vehicle queues. For example, simultaneously discharging all vehicles in a company queue may not be efficient. Some aspects provide distributed, time-multiplexed, and coordinated V2G queue management systems that can perform vehicle discharge based on availability, power chain requirements, company operations, and driver logistics. As another scenario, if every vehicle in a neighborhood activates vehicle charging during the same time window (e.g., during peak evening hours), the grid may be unable to supply sudden power surges. Conversely, suppose all vehicles activate V2G discharge within the same time window. In that case, the grid may be unprepared, V2G discharge may go unmonitored, or vehicles may trigger unnecessary signaling between EVCCs and SECCs or between SECCs and SAs. Therefore, robust and secure methods are important for organizing, coordinating, and activating (or deactivating) direct discharge between EVCCs and the grid, or vice versa.

[0103] Figure 7 An example is illustrated of a V2G charge transfer system 700 comprising multiple vehicles that transfer charge to the power grid. As shown, each of the vehicles 712, 714, and 716 can be connected to a base station 718 (e.g., corresponding to a location relative to the power grid). Figure 1 The described BS 102's 5G gNB or 5G cloud service). In some cases, (e.g., corresponding to relative to Figure 1 Each vehicle (as described in UE 104) has a network connection via a Uu link or a PC5 link (or any suitable side link). The vehicle can be connected for charging (e.g., connected to an EVSE in the vehicle user's home). In some respects, charge can be wirelessly supplied to or from the vehicle. A power line 750 (e.g., a wired connection) can be coupled between the EVSE and a networked grid controller 708. The grid controller 708 can be connected to the network using a Uu or PC5 link. The grid controller 708 can be coupled to control power transfer to or from the grid 710.

[0104] Some aspects of this disclosure relate to techniques for grid-initiated V2G discharge. As used herein, V2G discharge generally refers to the transfer of charge from a vehicle to the grid (e.g., resulting in vehicle discharge). Grid-initiated signaling can be used to initiate and activate (and also deactivate) V2G transfers. Some aspects relate to vehicle-initiated V2G discharge. Vehicle-initiated signaling can be used to identify, evaluate, and activate (or deactivate) V2G transfers. Some aspects relate to selecting vehicle groups for discharge. V2G negotiation can be used prior to vehicle-to-vehicle (V2V) discharge to identify which group of vehicles is suitable to perform V2G discharge. For example, vehicles in a neighborhood (or queue) can determine which group of vehicles is more suitable to perform V2G discharge and the percentage of total power that can be transferred by the selected vehicles. Similarly, vehicle groups in a single household can negotiate power discharge or charging schedules. Some decisions may be cost-effective for owners of these vehicles during power surges due to price increases. Some aspects of this disclosure provide direct communication with the SECC grid (e.g., rather than with the grid of the vehicle itself). For example, when the grid wants to initiate energy transfer, it can request energy from the SECC. V2G sleep cycles can be used, where vehicles can deplete their batteries for a period of time (e.g., during discharge) and then recharge a portion based on a duty cycle. Cloud services operating alongside the grid can define the duty cycle.

[0105] Figure 8 Example signaling for performing grid-initiated V2G discharge according to certain aspects of this disclosure is illustrated. As shown, at 802, the grid controller (e.g., relative to...) Figure 7 The described grid controller 708, or network device connected to the grid controller, can direct power to connected vehicles (e.g., such as vehicles relative to the grid controller). Figure 7 The described vehicle 712) transmits a dedicated V2G transfer request message (e.g., on a Uu link). The request message may indicate various charge transfer characteristics. For example, the message may include one or more of the following: the location of the grid controller, the total power requirement at the grid (e.g., during any time period of day or night), and cost benefits that can be provided by the grid controller. For example, if the vehicle completes a V2G transfer as requested, the vehicle owner may receive a discount on their electricity bill. The request may also include a schedule for charge transfers to the grid. In some cases, the request may include a Universal Time Coordination (UTC) timestamp associated with the request transmitted to the vehicle and / or a message count indicating the number of requests transmitted to the vehicle. The request may also include security credentials, but in some cases, inherited Uu or PC5 security may be reused.

[0106] At 804, the request may initiate a series of handshake messages between the PLC and EVCC to determine whether to perform a V2G transfer. At 806, a V2G transfer accept or reject message may be transmitted from the vehicle to the grid controller. The vehicle may transmit an accept message to the controlled grid (e.g., via a 5G gNB or V2G cloud service). The accept message may indicate one or more of the following: V2G start and end schedules, vehicle ID, approximate location of the vehicle, and total power that can be transferred throughout the transfer. In some aspects, the vehicle may follow a V2G transfer schedule calculated by the grid controller (e.g., and indicated to the vehicle in the request message), in which case any schedule and power fields (e.g., indicating the amount of power transferred and the schedule) may not be included in the accept message.

[0107] As described, the vehicle may transmit a rejection message. The vehicle may obtain the owner's consent to accept the transfer request. If any impending or urgent trip is planned or scheduled, if the battery is low, or if the vehicle owner simply refuses the request due to a lack of interest in V2G participation, the vehicle may transmit a rejection message indicating the reason for the rejection.

[0108] If the start time for power transfer is in the distant future, the grid controller may signal a transfer request as the start time approaches the scheduled time, based on the power demand at the grid. If the start time is in the near future, the grid controller may create a time schedule at box 808. For example, the grid controller may assign a periodic V2G transfer schedule (e.g., and / or an aperiodic transfer schedule) to a vehicle during a certain time period. In one example, the grid controller may request the vehicle to transfer only a certain amount of power (e.g., a certain percentage of total power in kilowatt-hours (kWh) transferred over 20 minutes out of every 60 minutes). In another example, the vehicle may be assigned a longer time period or an aperiodic transfer schedule. In some cases, at box 808, the grid controller may accept (e.g., finalize) the schedule transmitted by the vehicle as part of an acceptance message. At 810, the grid controller transmits an acknowledgment message before a charge transfer can be initiated. At box 812, the V2G transfer may occur.

[0109] While some of the examples described herein involve a grid controller transmitting an acknowledgment message, there are cases where charge transfer can be initiated without an acknowledgment message. For example, a request message from the grid may also include a Boolean field, referred to herein as the unacknowledged transfer field. If the field is set to true, the vehicle may not wait for acknowledgment from the grid controller, and the V2G charge transfer may begin immediately after the acceptance message is transmitted. If the field is set to false, the vehicle will wait for acknowledgment (if any) from the grid controller before initiating the V2G charge transfer.

[0110] Figure 9 Examples of signaling for performing a vehicle-initiated V2G discharge according to certain aspects of this disclosure are illustrated. At 902, signaling originating from the vehicle (e.g., Figure 7 The vehicle 712) to the grid controller (e.g., corresponding to Figure 7 The V2G transfer request originating from the vehicle's grid controller (708) may include various V2G transfer parameters, such as the vehicle's current battery percentage, the V2G transfer window (e.g., including start and end times), the total power available for transfer, the vehicle ID, and the owner's authorization for charge transfer. In some aspects, transfer requests originating from the vehicle may be transmitted periodically over a specific duration or until a response is received from the grid. The request message may be transmitted while the vehicle is not stationary. For example, the vehicle may initiate the request while en route to a specific destination (e.g., while traveling to the specific destination).

[0111] At position 904, a V2G transfer acceptance or rejection message originating from the grid controller to the vehicle can be transmitted. The rejection message may include possible reasons for rejection. For example, a rejection message may indicate that the grid does not require any V2G discharge or that the grid controller is malfunctioning. In some aspects, the rejection message may indicate different grid locations that may be operational and require power. In some aspects, the acceptance or rejection message may include a no-acknowledgment transfer field indicating whether the vehicle should wait for an acknowledgment message before initiating a charge transfer.

[0112] In some aspects, at 906, the grid controller transmits an acknowledgment message before a charge transfer can be initiated. At 908, a V2G transfer can occur. In some cases, at 910, if V2G discharge service is no longer needed, the grid controller may transmit a V2G transfer stop request in advance. If the V2G transfer duration has expired (e.g., earlier than scheduled by transfer request / acceptance), the grid controller may transmit a stop acknowledgment. At 912, a V2G transfer can be terminated by one or more handshake messages involving the vehicle and the grid controller.

[0113] In some respects, vehicles can use history (e.g., driver commuting patterns or aggregated driver patterns within a home) to predict time periods when V2G discharges can be initiated for transfer scheduling. This process can be efficient and owner-agnostic. For example, a fully autonomous vehicle can automatically initiate and schedule V2G transfers unless the owner changes the schedule.

[0114] As an example, a cloud-connected power grid entity can receive V2G transfer requests from various vehicles (e.g., during peak hours) and can determine the priority associated with power transfer to the vehicles at the power grid controller. Priorities can be determined based on certain conditions, which may be implementation-specific. The power grid controller can determine priorities before transmitting accept or reject messages.

[0115] Figure 10 Examples of signaling for V2G selective group transfer according to certain aspects of this disclosure are illustrated. In some aspects, relative to Figure 10 The described signaling can be relative to Figure 8 The described block 804 occurs after this. At 1002, the V2G group transfer request message can be sent by the grid controller (e.g., Figure 7 The power grid controller 708 transmits data to the vehicle (e.g., labeled "vehicle 1", such as...). Figure 7 (Vehicle 712). The request message may request a vehicle group (e.g., including those corresponding to vehicles). Figure 7 The power transfer of vehicles 714 and 716 ("Vehicle 2" to "Vehicle N", where N is a positive integer) is described. Requests may include various parameters, such as those relative to... Figure 8 or Figure 9 The parameters are included as part of the described request message. Additionally, the grid controller may announce the total power demand at the grid during surges. The request may also indicate the group size. For example, the request may indicate whether it is for charge transfers from vehicles in a specific neighborhood.

[0116] As shown in the figure, at 1004, vehicle 1 broadcasts a V2X group participation vote request message. This vote request message can be transmitted using a side link or a Uu link. At 1006, vehicles 2 through N receive the group message (vote request message). As shown in the figure, at 1020, each vehicle can respond with a participation message indicating whether to vote "yes" or "no" regarding participation in the V2G transfer.

[0117] In some respects, vehicle 1 can receive or collect voting responses and vehicle IDs from participating vehicles. For example, vehicles 2 and 3 can vote to participate in V2G transfers, while vehicle N can vote not to participate in V2G transfers.

[0118] At point 1008, vehicle 1 may transmit a group transfer acceptance message to the grid controller. The acceptance message may include the total number of vehicles in the group (e.g., 3 vehicles, including vehicles 1-3). If the total number of vehicles is less than two, vehicle 1 may transmit a rejection message at point 1008.

[0119] At point 1010, vehicle 1 calculates the V2G discharge rate or power budget for each vehicle and then transmits allocation share messages (e.g., messages 1012, 1014) to the corresponding vehicles. For example, vehicle 1 may request vehicles 2 and 3 to transfer 100 kWh and 200 kWh respectively within one hour. Vehicle 1 may also consider its own share of power transfer. Vehicle 1 may act as a shared controller for actions such as safety, cost compensation calculations, scheduling, or interruption handling.

[0120] As shown in the figure, the grid controller can send a V2G confirmation message to each vehicle (vehicle 1, vehicle 2, and vehicle 3) participating in the V2G transfer. As shown, the confirmation message may not be sent to vehicles N that are not participating in the V2G transfer. In some aspects, if multiple vehicles (e.g., vehicle 1, vehicle 2, and vehicle 3) are owned by a single owner, the vote at box 1020 can be completed by the vehicle owner themselves.

[0121] Figure 11 An example is illustrated of a home with multiple vehicles (e.g., labeled as car 1, car 2, and car 3) for V2G transfer according to certain aspects of this disclosure. As shown, each of vehicles 1104, 1106, and 1108 can be connected to BS 718 (e.g., via a corresponding Uu link). Each of vehicles 1104, 1106, and 1108 may include an EVCC and may be connected to the SECC of home 1102 via a power line. As shown, vehicles 1104, 1106, and 1108 can be communicatively coupled via a side link (e.g., a PC5 interface). As described, vehicles 1104, 1106, and 1108 can be configured by the vehicle owner (e.g., ...). Figure 10 Voting is performed at box 1020. In some cases, only one vehicle in the vehicle may send a voting message to the grid controller, indicating whether one or more vehicles in the household will participate in V2G transfer.

[0122] While some examples described herein have been described with respect to a grid controller communicating with one or more vehicles, certain aspects of this disclosure may be performed using communication between the grid controller and the SECC. The SECC may be a private SECC (e.g., in house 1102) or a public SECC (e.g., at a charging station).

[0123] Figure 12 Example techniques for V2G transfer using communication between a grid controller 708 and (e.g., an SECC as part of house 1102) are illustrated according to certain aspects of this disclosure. As shown, each vehicle in the vehicle system may be coupled to the SECC (e.g., at house 1102) via a PC5 interface and to an EVSE (e.g., at house 1102) via a power line for charging and discharging. The EVSE may be coupled to the grid via the power line. The grid controller 708 may transmit a request message to the SECC requesting energy from the SECC when the grid determines that an energy transfer has been initiated. The SECC may be responsible for managing (e.g., via PC5 or WiFi) the charging levels among multiple vehicles (e.g., vehicles 1104, 1106, 1108), thus maintaining sufficient charge in each vehicle without causing any vehicle to be completely discharged. For example, if a vehicle initiates an energy transfer, the vehicle may communicate (e.g., via wired or wireless communication) with the associated SECC, which may negotiate the energy transfer with the grid controller. SECC can act as a "middleman" handling communication between the grid controller and vehicles (e.g., via Uu or PC5 links). Private vehicle information, such as location and charging level, may not be transferred to the grid controller. Instead, SECC information can be transmitted to the grid controller. If multiple vehicles are available for SECC, the grid controller can ping only the SECC.

[0124] Example operation for grid-initiated charge transfer

[0125] Figure 13 An example of a method 1300 for device-to-grid charge transfer at a controller associated with a wireless communication device is shown. The wireless communication device can be any equipment, such as a heating, ventilation, and air conditioning (HVAC) system or a vehicle. The controller can be any networking (e.g., 5G) type controller or any controller that supports signaling via Uu and / or PC5 links. In some aspects, the controller can be a modem associated with the wireless communication device.

[0126] Method 1300 begins at step 1305, where the controller receives a request from a controller associated with the power grid for a charge transfer from a wireless communication device to the power grid. This request may indicate the power requirements of the power grid during a certain time period. In some cases, the operation of this step refers to... (refer to...) Figure 17 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0127] At step 1310, the controller transmits a message indicating whether to accept a request for charge transfer based on the power requirement. In some cases, this step refers to... (refer to...) Figure 17 The circuitry described for sending / transmitting and / or the code for sending / transmitting, or the circuitry and / or the code that can be executed.

[0128] At step 1315, the controller initiates a charge transfer from the wireless communication device to the power grid during the specified time period upon receiving a message indicating acceptance of the charge transfer. In some cases, this step refers to the operation as described in reference [reference needed]. Figure 17 The circuitry and / or code described for configuration, or that can be executed by such circuitry and / or code, are described. For example, initiating a charge transfer may involve supplying charge from the battery of a wireless communication device to a DC link coupled to the power grid (e.g., DC link 502).

[0129] In some aspects, a request indicating a power requirement may include a request indicating an expected power surge during the specified time period. The request may further indicate charge transfer information, including at least one of the following: the location of the power grid, the cost-effectiveness of the charge transfer to the owner of the wireless communication device, a schedule associated with the charge transfer, one or more timestamps associated with the request, a message count indicating the number of requests transmitted to the wireless communication device, or security credentials transmitted based on the charge transfer information. In some aspects, the request may include an indication of whether to wait for an acknowledgment message before performing the charge transfer.

[0130] In some respects, the controller can receive an acknowledgment message in response to the transmission of a message accepting a charge transfer. The charge transfer can be initiated based on the receipt of the acknowledgment message.

[0131] In some respects, the controller may receive instructions for periodic (or aperiodic) charge transfer schedules. In some cases, the controller may receive instructions for periodic charge transfer schedules for charge transfers during a first time period and instructions for aperiodic charge transfer schedules for charge transfers during a second time period.

[0132] In some respects, the message accepts charge transfer and includes at least one of the following: a charge transfer schedule, an identifier associated with the wireless communication device, the location of the wireless communication device, authorization from the owner of the wireless communication device, or the amount of power to be transferred during a time period. In some cases, the message rejects charge transfer and indicates the reason for rejecting the charge transfer.

[0133] In some aspects, a wireless communication device is one of a plurality of wireless communication devices. A controller may transmit another request to one or more of these wireless communication devices to participate in charge transfer. The controller may receive a response from each of the one or more wireless communication devices indicating whether each of the one or more wireless communication devices will respond to the other request to participate in charge transfer. In this case, the message indicating whether to accept the request for charge transfer is transmitted based on the responses from each of the one or more wireless communication devices. The controller may transmit an indication to each of the one or more wireless communication devices of the amount of power to be transferred by each of the one or more wireless communication devices. This message may indicate acceptance of charge transfer, further indicating a first amount of the wireless communication device that will participate in the charge transfer to the power grid based on the responses from each of the one or more wireless communication devices. The request may indicate a second amount of the wireless communication device requested to participate in the charge transfer to the power grid. The second amount may be greater than or equal to the first amount of the wireless communication device.

[0134] In some aspects, the request may be received at the power supply equipment communication controller (SECC) associated with the wireless communication device. The wireless communication device may be one of a plurality of wireless communication devices associated with the communication controller. Controlling charge transfer may include: controlling the charge transfer from each of the plurality of wireless communication devices to the grid via the SECC based on the amount of remaining charge of each of the plurality of wireless communication devices, a scheduling table set by the owner of the respective wireless communication device or by the power grid for the respective wireless communication device, or with the consent of the owner of the respective wireless communication device.

[0135] Figure 14 An example of method 1400 for device-to-grid charge transfer at a controller associated with a grid controller is shown. The controller can be any networked (e.g., 5G) controller or any controller that supports signaling via Uu and / or PC5 links.

[0136] Method 1400 begins at step 1405, where the controller transmits a request for charge transfer from the wireless communication device to the power grid. This request may indicate the power requirements of the power grid during a certain time period. In some cases, the operation of this step refers to... (refer to...) Figure 17 The circuitry and / or code described for transmission, or that can be executed by the circuitry and / or the code.

[0137] At step 1410, the controller receives a message indicating whether to accept a request for charge transfer based on the power requirement. In some cases, this step refers to... (refer to...) Figure 17 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0138] At step 1415, the controller initiates a charge transfer from the wireless communication device to the power grid during the specified time period upon receiving a message indicating acceptance of the charge transfer. In some cases, this step refers to the operation as described in reference [reference needed]. Figure 17 The described circuitry and / or code for configuration, or the circuitry and / or code that can be executed by such circuitry and / or code. Wireless communication devices can be vehicles.

[0139] In some aspects, a request indicating a power requirement may include a request indicating an expected power surge during the specified time period. In some aspects, the request may also indicate charge transfer information, which includes at least one of the following: the location of the power grid, the cost-effectiveness of the charge transfer to the owner of the wireless communication device, a schedule associated with the charge transfer, one or more timestamps associated with the request, a message count indicating the number of requests transmitted to the wireless communication device, and authorization or security authentication from the owner of the wireless communication device. The request may include an indication of whether to wait for a confirmation message before performing the charge transfer.

[0140] In some aspects, the controller may transmit an acknowledgment message in response to receiving a message accepting a charge transfer, wherein the charge transfer is initiated based on the transmission of the acknowledgment message. In some aspects, the controller may transmit an indication of a periodic charge transfer schedule, wherein the charge transfer is performed based on a periodic charge transfer schedule. The controller may transmit an indication of a periodic charge transfer schedule for a charge transfer during a first time period and an indication of an aperiodic charge transfer schedule for a charge transfer during a second time period.

[0141] In some aspects, the message accepts charge transfer and includes at least one of the following: a charge transfer schedule, an identifier associated with a wireless communication device, the location of the wireless communication device, or the amount of power to be transferred during a time period. The message may reject charge transfer, indicating the reason for rejection. The message may indicate acceptance of charge transfer, further indicating a first amount of wireless communication devices that will participate in the charge transfer to the power grid. The request may indicate a second amount of wireless communication devices requested to participate in the charge transfer to the power grid, the second amount being greater than or equal to the first amount of wireless communication devices.

[0142] In some respects, the request may be transmitted to a power supply equipment communication controller (SECC) associated with a wireless communication device. The wireless communication device may be one of multiple wireless communication devices associated with the SECC, and the request is for charge transfer from multiple wireless communication devices.

[0143] Example operation for device-initiated charge transfer

[0144] Figure 15 An example of method 1500 for device-to-grid charge transfer at a controller associated with a wireless communication device is shown. The wireless communication device can be any equipment, such as a heating, ventilation, and air conditioning (HVAC) system or a vehicle. The controller can be any networking (e.g., 5G) type controller or any controller that supports signaling via Uu and / or PC5 links. In some aspects, the controller can be a modem associated with the wireless communication device.

[0145] Method 1500 begins at step 1505, wherein the controller transmits a request for charge transfer from the wireless communication device to the power grid, wherein the request indicates the amount of power available for transfer to the power grid during a certain time period. In some cases, the operation of this step refers to, as referenced... Figure 17 The circuitry and / or code described for transmission, or that can be executed by the circuitry and / or the code.

[0146] At step 1510, the controller receives a message indicating whether to accept the request for charge transfer. In some cases, this step refers to... (refer to...) Figure 17 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0147] At step 1515, the controller initiates a charge transfer from the wireless communication device to the power grid during the specified time period upon receiving a message indicating acceptance of the charge transfer. In some cases, this step refers to the operation as described in reference [reference needed]. Figure 17 The circuitry and / or code described for configuration, or that can be executed by the circuitry and / or the code.

[0148] In some aspects, the controller determines a schedule for charge transfer based on the operational history of the wireless communication device. Requests for charge transfer can be transmitted based on this schedule. The request may further indicate charge transfer information, including at least one of the following: the current amount of available charge of the wireless communication device, a transfer window including the start and end times for the charge transfer, an identifier associated with the wireless communication device, or authorization from the owner of the wireless communication device. In some aspects, the request is part of a plurality of charge transfer requests periodically transmitted by the wireless communication device. The request can be transmitted when the wireless communication device is not at rest.

[0149] In some aspects, the controller receives an acknowledgment message after receiving a message to accept charge transfer, wherein the charge transfer is initiated based on the receipt of the acknowledgment message. In some aspects, the message includes an indication of whether to wait for the receipt of the acknowledgment message before performing the charge transfer. In some aspects, the controller receives a stop transfer request, wherein the charge transfer is stopped based on the stop transfer request.

[0150] In some aspects, a message received by a controller associated with the wireless communication device rejects charge transfer, indicating the reason for rejecting the charge transfer. A message received by the controller associated with the wireless communication device may reject charge transfer for a first grid location, indicating a second grid location where charge transfer can be accepted.

[0151] In some aspects, the wireless communication device is one of a plurality of wireless communication devices. The controller may transmit another request to one or more of the plurality of wireless communication devices to participate in charge transfer, and receive a response from each of the one or more wireless communication devices indicating whether each of the one or more wireless communication devices will respond to the other request to participate in charge transfer. Configuring charge transfer may be based on the responses from each of the one or more wireless communication devices. In some aspects, the controller transmits an indication to each of the one or more wireless communication devices of the amount of power to be transferred by each of the one or more wireless communication devices. In some aspects, the request may further indicate the amount of wireless communication device that will participate in charge transfer to the power grid based on the responses to each of the one or more wireless communication devices.

[0152] This request can be transmitted by the power supply equipment communication controller (SECC) associated with the wireless communication device. The wireless communication device can be one of multiple wireless communication devices associated with the SECC. Configuring charge transfer can include configuring charge transfer from each of the multiple wireless communication devices to the power grid via the SECC based on the amount of remaining charge in each of the multiple wireless communication devices.

[0153] Figure 16 An example of method 1600 for device-to-grid charge transfer at a controller associated with a grid controller is shown. The controller can be any networked (e.g., 5G) controller or any controller that supports signaling via Uu and / or PC5 links.

[0154] Method 1600 begins at step 1605, wherein the controller receives a request from a controller associated with the wireless communication device for a charge transfer from the wireless communication device to the power grid. This request may indicate the amount of power available for transfer to the power grid during a given time period. In some cases, the operation of this step refers to... (refer to...) Figure 17 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0155] At step 1610, the controller transmits a message indicating whether to accept the request for charge transfer. In some cases, this step refers to... (refer to...) Figure 17 The circuitry and / or code described for transmission, or that can be executed by the circuitry and / or the code.

[0156] At step 1615, the controller initiates a charge transfer from the wireless communication device to the power grid during the specified time period upon receiving a message indicating acceptance of the charge transfer. In some cases, this step refers to the operation as described in reference [reference needed]. Figure 17 The described circuitry and / or code for configuration, or the circuitry and / or code that can be executed by such circuitry and / or code. Wireless communication devices can be vehicles.

[0157] In some aspects, the request further indicates charge transfer information, which includes at least one of the following: the current amount of available charge of the wireless communication device, a transfer window including start and end times for the charge transfer, an identifier associated with the wireless communication device, or authorization from the owner of the wireless communication device, wherein the message is transmitted based on the charge transfer information. In some aspects, the request is part of a plurality of requests for charge transfer received periodically from the wireless communication device.

[0158] The controller may transmit an acknowledgment message after transmitting a message accepting charge transfer, wherein the charge transfer is initiated based on the acknowledgment message. This message may include an indication of whether to wait for an acknowledgment message before performing the charge transfer. The controller may also transmit a stop transfer request, wherein the charge transfer is stopped based on the stop transfer request.

[0159] In some aspects, the message rejects charge transfer, indicating the reason for rejection. The message may reject charge transfer for a first grid location, and may indicate a second grid location for which charge transfer may be accepted. In some aspects, the request further indicates the amount of wireless communication equipment that will participate in the charge transfer to the grid.

[0160] In some respects, the request may be received from a power supply equipment communication controller (SECC) associated with a wireless communication device. The wireless communication device may be one of multiple wireless communication devices associated with the SECC, and the request is for charge transfer from multiple wireless communication devices.

[0161] In some respects, the request may be one of multiple requests for charge transfer from multiple wireless communication devices received by a controller associated with the power grid. The controller may determine the priority associated with the multiple requests, and the message is transmitted based on that determination.

[0162] Example communication device

[0163] Figure 17 Various aspects of the example communication device 1700 are depicted. In some aspects, the communication device 1700 is a controller (e.g., a V2G controller, a power grid controller, a modem, or any suitable network connectivity device).

[0164] Communication device 1700 includes a processing system 1705 coupled to transceiver 1775 (e.g., transmitter and / or receiver). In some respects (e.g., when communication device 1700 is a network entity), processing system 1705 may be coupled to network interface 1785, which is configured to communicate via a communication link (such as, as described herein, relative to...). Figure 2 The described backhaul link, midhaul link, and / or fronthaul link receive and transmit signals for communication device 1700. Transceiver 1775 is configured to transmit and receive signals for communication device 1700 via antenna 1780, such as the various signals described herein. Processing system 1705 may be configured to perform processing functions of communication device 1700, including processing signals received by communication device 1700 and / or to be transmitted by the communication device.

[0165] Processing system 1705 includes one or more processors 1710. In various aspects, the one or more processors 1710 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as relative to... Figure 3 As described. In various respects, one or more processors 1710 may represent one or more of the following: receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as relative to Figure 3 As described herein. One or more processors 1710 are coupled to a computer-readable medium / memory 1740 via a bus 1770. In some aspects, the computer-readable medium / memory 1740 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1710, cause one or more processors 1710 to perform the techniques described herein or any aspects thereof. It should be noted that references to processors performing the functions of communication device 1700 may include one or more processors 1710 performing such functions of communication device 1700.

[0166] In the depicted example, computer-readable medium / memory 1740 stores code (e.g., executable instructions), such as code 1745 for receiving, code 1750 for sending / transmitting, code 1755 for determining, and code 1765 for initiating. Processing of code 1745 for receiving, code 1750 for sending / transmitting, code 1755 for determining, and code 1765 for initiating are also described.

[0167] One or more processors 1710 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1740, including circuitry 1715 for receiving, circuitry 1720 for transmitting / transmitting, circuitry 1725 for determining, and circuitry 1735 for initiating. Processing is performed using the circuitry 1715 for receiving, the circuitry 1720 for transmitting / transmitting, the circuitry 1725 for determining, and the circuitry 1735 for initiating.

[0168] Various components of the communication device 1700 may provide parts for performing the methods described herein or any aspect thereof. For example, parts for transmitting, conveying, or outputting for transmission may include... Figure 3 The transceiver 354 and / or antenna 352 of the illustrated UE 104 Figure 3 The transceiver 332 and / or antenna 334 of the illustrated BS 102, and / or Figure 17 The communication device 1700 includes a transceiver 1775 and an antenna 1780. Components for receiving or acquiring data may include... Figure 3The transceiver 354 and / or antenna 352 of the illustrated UE 104 Figure 3 The transceiver 332 and / or antenna 334 of the illustrated BS 102 Figure 17 The transceiver 1775 and antenna 1780 of the communication equipment 1700.

[0169] Example Terms

[0170] Specific implementation examples are described in the following numbered clauses:

[0171] Aspect 1: A method for device-to-grid charge transfer, the method comprising: receiving from a controller associated with a grid a request for charge transfer from a wireless communication device to the grid, wherein the request indicates a power requirement of the grid during a time period; transmitting, based on the power requirement, a message indicating whether to accept the request for the charge transfer; and, when the message indicates acceptance of the charge transfer, initiating the charge transfer from the wireless communication device to the grid during the time period.

[0172] Aspect 2: According to the method of aspect 1, the wireless communication device includes a vehicle.

[0173] Aspect 3: The method according to aspect 1 or aspect 2, wherein the request indicating the power requirement includes a request indicating an expected power surge during the time period.

[0174] Aspect 4: The apparatus according to any one of Aspects 1 to 3, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the location of the power grid, the cost-effectiveness of the charge transfer to the owner of the wireless communication device, a schedule associated with the charge transfer, one or more timestamps associated with the request, a message count indicating the number of requests transmitted to the wireless communication device, or a security credential, the messages being transmitted based on the charge transfer information.

[0175] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the request includes an indication of whether to wait to receive an acknowledgment message before performing the charge transfer.

[0176] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: receiving an acknowledgment message in response to transmitting the message accepting the charge transfer, wherein the charge transfer is initiated based on receiving the acknowledgment message.

[0177] Aspect 7: The method according to any one of aspects 1 to 6, the method further comprising: receiving an instruction for a periodic charge transfer schedule.

[0178] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: receiving an indication of a periodic charge transfer schedule for charge transfer during a first time period and an indication of an aperiodic charge transfer schedule for charge transfer during a second time period.

[0179] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the message accepts the charge transfer, the message including at least one of: a charge transfer schedule, an identifier associated with the wireless communication device, the location of the wireless communication device, authorization from the owner of the wireless communication device, or the amount of power to be transferred during the time period.

[0180] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the message rejects the charge transfer, and the message indicates the reason for rejecting the charge transfer.

[0181] Aspect 11: The method according to any one of Aspects 1 to 10, wherein: the wireless communication device is one of a plurality of wireless communication devices; the method further comprises: transmitting to one or more of the plurality of wireless communication devices another request to participate in the charge transfer; and receiving from each of the one or more wireless communication devices a response indicating whether each of the one or more wireless communication devices will respond to the other request to participate in the charge transfer; and the message indicating whether to accept the request for the charge transfer is transmitted based on the response from each of the one or more wireless communication devices.

[0182] Aspect 12: The method according to aspect 11, the method further comprising: transmitting to each of the one or more wireless communication devices an indication of the amount of power to be transferred by each of the one or more wireless communication devices.

[0183] Aspect 13: The method according to aspect 11 or aspect 12, wherein the message indicates acceptance of the charge transfer, and the message further indicates a first amount of wireless communication devices that will participate in the charge transfer to the power grid based on the response from each of the one or more wireless communication devices.

[0184] Aspect 14: According to the method of aspect 13, wherein the request indicates a second amount of a wireless communication device requested to participate in the charge transfer of the power grid, the second amount being greater than or equal to the first amount of the wireless communication device.

[0185] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the request is received at a power supply equipment communication controller (SECC) associated with the wireless communication device.

[0186] Aspect 16: The method according to aspect 15, wherein: the wireless communication device is one of a plurality of wireless communication devices associated with the communication controller; and configuring the charge transfer includes: configuring the charge transfer from each of the plurality of wireless communication devices to the power grid via the SECC based on the amount of remaining charge of each of the plurality of wireless communication devices, a scheduling table set by the owner of the respective wireless communication device or by the power grid for the respective wireless communication device, or with the consent of the owner of the respective wireless communication device.

[0187] Aspect 17: A method for device-to-grid charge transfer, the method comprising: transmitting from a controller associated with a grid a request for a charge transfer from a wireless communication device to the grid, wherein the request indicates a power requirement of the grid during a time period; receiving, based on the power requirement, a message indicating whether to accept the request for the charge transfer; and, when the message indicates acceptance of the charge transfer, initiating the charge transfer from the wireless communication device to the grid during the time period.

[0188] Aspect 18: According to the method of aspect 17, the wireless communication device includes a vehicle.

[0189] Aspect 19: The method according to aspect 17 or aspect 18, wherein the request indicating the power requirement includes a request indicating an expected power surge during the time period.

[0190] Aspect 20: The method according to any one of Aspects 17 to 19, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the location of the power grid, the cost-effectiveness of the charge transfer to the owner of the wireless communication device, a schedule associated with the charge transfer, one or more timestamps associated with the request, a message count indicating the number of requests transmitted to the wireless communication device, and authorization or security credentials from the owner of the wireless communication device.

[0191] Aspect 21: The method according to any one of aspects 17 to 20, wherein the request includes an indication of whether to wait to receive an acknowledgment message before performing the charge transfer.

[0192] Aspect 22: The method according to any one of aspects 17 to 21, the method further comprising: transmitting an acknowledgment message in response to receiving the message accepting the charge transfer, wherein the charge transfer is initiated based on transmitting the acknowledgment message.

[0193] Aspect 23: The method according to any one of aspects 14 to 22, the method further comprising: transmitting an instruction to a periodic charge transfer schedule, wherein the charge transfer is performed based on the periodic charge transfer schedule.

[0194] Aspect 24: The method according to any one of aspects 17 to 23, the method further comprising: transmitting an indication of a periodic charge transfer schedule for charge transfer during a first time period and an indication of an aperiodic charge transfer schedule for charge transfer during a second time period.

[0195] Aspect 25: The method according to any one of Aspects 17 to 24, wherein the message accepts the charge transfer, the message including at least one of: a charge transfer schedule, an identifier associated with the wireless communication device, the location of the wireless communication device, or the amount of power to be transferred during the time period.

[0196] Aspect 26: The method according to any one of aspects 17 to 25, wherein the message rejects the charge transfer, and the message indicates the reason for rejecting the charge transfer.

[0197] Aspect 27: The method according to any one of Aspects 17 to 26, wherein the message indicates acceptance of the charge transfer, and the message further indicates a first amount of wireless communication device that will participate in the charge transfer of the power grid.

[0198] Aspect 28: The method according to aspect 27, wherein the request indicates a second amount of a wireless communication device requested to participate in charge transfer of the power grid, the second amount being greater than or equal to the first amount of the wireless communication device.

[0199] Aspect 29: The method according to any one of aspects 17 to 28, wherein the request is transmitted to a power supply equipment communication controller (SECC) associated with the wireless communication device.

[0200] Aspect 30: The method according to aspect 29, wherein the wireless communication device is one of a plurality of wireless communication devices associated with the SECC, and the request is for charge transfer from the plurality of wireless communication devices.

[0201] Aspect 31: A method for device-to-grid charge transfer, the method comprising: transmitting from a controller associated with a wireless communication device a request for a charge transfer from the wireless communication device to a grid, wherein the request indicates an amount of power available for transfer to the grid during a time period; receiving a message indicating whether to accept the request for the charge transfer; and, when the message indicates acceptance of the charge transfer, initiating the charge transfer from the wireless communication device to the grid during the time period.

[0202] Aspect 32: According to the method of aspect 31, the wireless communication device includes a vehicle.

[0203] Aspect 33: The method according to aspect 31 or aspect 32, the method further comprising: determining a schedule for the charge transfer based on the operation history of the wireless communication device, wherein the request for the charge transfer is transmitted based on the schedule.

[0204] Aspect 34: The method according to any one of Aspects 31 to 33, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the current amount of available charge of the wireless communication device, a transfer window including a start time and an end time for charge transfer, an identifier associated with the wireless communication device, or authorization from the owner of the wireless communication device.

[0205] Aspect 35: The method according to any one of aspects 31 to 34, wherein the request is part of a plurality of requests for charge transfer periodically transmitted by the wireless communication device.

[0206] Aspect 36: The method according to any one of aspects 31 to 35, wherein the request is transmitted when the wireless communication device is not stationary.

[0207] Aspect 37: The method according to any one of aspects 31 to 36, the method further comprising: receiving an acknowledgment message after receiving the message accepting the charge transfer, wherein the charge transfer is initiated based on receiving the acknowledgment message.

[0208] Aspect 38: The method according to any one of aspects 31 to 37, wherein the message includes an indication of whether to wait to receive an acknowledgment message before performing the charge transfer.

[0209] Aspect 39: The method according to any one of aspects 31 to 38, the method further comprising: receiving a stop transfer request, wherein the charge transfer is stopped based on the stop transfer request.

[0210] Aspect 40: The method according to any one of aspects 31 to 39, wherein the message received by the controller associated with the wireless communication device rejects the charge transfer, the message indicating the reason for rejecting the charge transfer.

[0211] Aspect 41: The method according to aspect 40, wherein the message received by the controller associated with the wireless communication device rejects the charge transfer for a first power grid location, the message indicating a second power grid location for which a charge transfer can be accepted.

[0212] Aspect 42: The method according to any one of aspects 31 to 41, wherein: the wireless communication device is one of a plurality of wireless communication devices; the method further comprises: transmitting to one or more of the plurality of wireless communication devices another request to participate in the charge transfer; and receiving from each of the one or more wireless communication devices a response indicating whether each of the one or more wireless communication devices will respond to the other request to participate in the charge transfer; and initiating the charge transfer based on the response from each of the one or more wireless communication devices.

[0213] Aspect 43: The method according to aspect 42, the method further comprising: transmitting to each of the one or more wireless communication devices an indication of the amount of power to be transferred by each of the one or more wireless communication devices.

[0214] Aspect 44: The method according to aspect 42 or 43, wherein the request further indicates the amount of wireless communication devices that will participate in the charge transfer of the power grid based on the response to each of the one or more wireless communication devices.

[0215] Aspect 45: The method according to any one of aspects 31 to 44, wherein the request is transmitted by a power supply equipment communication controller (SECC) associated with the wireless communication device.

[0216] Aspect 46: The method according to aspect 45, wherein: the wireless communication device is one of a plurality of wireless communication devices associated with the SECC; and configuring the charge transfer includes: configuring a charge transfer from each of the plurality of wireless communication devices to the power grid via the SECC based on the amount of remaining charge of each of the plurality of wireless communication devices.

[0217] Aspect 47: A method for device-to-grid charge transfer, the method comprising: receiving from a controller associated with a wireless communication device a request for a charge transfer from the wireless communication device to a grid, wherein the request indicates an amount of power available for transfer to the grid during a time period; transmitting a message indicating whether the request for the charge transfer is accepted; and, when the message indicates acceptance of the charge transfer, initiating the charge transfer from the wireless communication device to the grid during the time period.

[0218] Aspect 48: According to the method of aspect 47, the wireless communication device includes a vehicle.

[0219] Aspect 49: The method according to aspect 47 or aspect 48, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the current amount of available charge of the wireless communication device, a transfer window including start and end times for charge transfer, an identifier associated with the wireless communication device, or authorization from the owner of the wireless communication device, wherein the message is transmitted based on the charge transfer information.

[0220] Aspect 50: The method according to any one of aspects 47 to 49, wherein the request is part of a plurality of requests for charge transfer received periodically from the wireless communication device.

[0221] Aspect 51: The method according to any one of aspects 47 to 50, the method further comprising: transmitting an acknowledgment message after transmitting the message of accepting the charge transfer, wherein the charge transfer is initiated based on the acknowledgment message.

[0222] Aspect 52: The method according to any one of aspects 47 to 51, wherein the message includes an indication of whether to wait to receive an acknowledgment message before performing the charge transfer.

[0223] Aspect 53: The method according to any one of aspects 47 to 52, the method further comprising: transmitting a stop transfer request, wherein the charge transfer is stopped based on the stop transfer request.

[0224] Aspect 54: The method according to any one of aspects 47 to 53, wherein the message rejects the charge transfer, and the message indicates the reason for rejecting the charge transfer.

[0225] Aspect 55: According to the method of aspect 54, wherein the message rejects the charge transfer for the first grid location, and the message indicates a second grid location for which a charge transfer can be accepted.

[0226] Aspect 56: The method according to any one of Aspects 47 to 55, wherein the request further indicates the amount of wireless communication devices that will participate in the charge transfer of the power grid.

[0227] Aspect 57: The method according to any one of aspects 47 to 56, wherein the request is received from a power supply equipment communication controller (SECC) associated with the wireless communication device.

[0228] Aspect 58: The method according to aspect 57, wherein the wireless communication device is one of a plurality of wireless communication devices associated with the SECC, and the request is for charge transfer from the plurality of wireless communication devices.

[0229] Aspect 59: The method according to any one of Aspects 47 to 58, wherein the request is one of a plurality of requests for charge transfer received by a controller associated with the power grid from a plurality of wireless communication devices, the method further comprising: determining a priority associated with the plurality of requests, wherein the message is transmitted based on the determination.

[0230] Aspect 60: An apparatus comprising: a memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform the method according to any one of aspects 1 to 59.

[0231] Aspect 61: An apparatus comprising: components for performing the method according to any one of aspects 1 to 59.

[0232] Aspect 62: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of a device, cause the device to perform the method according to any one of aspects 1 to 59.

[0233] Aspect 63: A computer program product embodied on a computer-readable storage medium, the computer program product comprising code for performing the method according to any one of aspects 1 to 59.

[0234] Additional Notes

[0235] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0236] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0237] As used herein, “processor,” “at least one processor,” or “one or more processors” generally refers to a single processor configured to perform one or more operations, or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may collectively perform a single operation. Similarly, “memory,” “at least one memory,” or “one or more memory” generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to collectively store data and / or instructions.

[0238] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these entries, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0239] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Furthermore, "determine" can include parsing, selecting, picking, building, etc.

[0240] The methods disclosed herein include one or more actions for implementing the methods. These method actions may be interchanged without departing from the scope of the claims. In other words, unless a specified order of actions is given, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above can be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0241] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless specifically stated otherwise, the term “some” means one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person of ordinary skill in the art, or will be known later, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims.

Claims

1. An apparatus for transferring charge from a device to the power grid, the apparatus comprising: At least one processor; At least one memory, said at least one memory being coupled to said at least one processor; and Instructions, which are stored in the memory and can be executed by the at least one processor, to cause the device to: Receive a request from a controller associated with the power grid for a charge transfer from a wireless communication device to the power grid, wherein the request indicates the power requirements of the power grid during a certain period of time; Based on the power requirement, a message indicating whether to accept the request for the charge transfer is transmitted; as well as When the message indicates acceptance of the charge transfer, the charge transfer from the wireless communication device to the power grid is initiated during the time period.

2. The apparatus of claim 1, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the location of the power grid, the cost-effectiveness of the charge transfer to the owner of the wireless communication device, a schedule associated with the charge transfer, one or more timestamps associated with the request, a message count indicating the number of requests transmitted to the wireless communication device, or security credentials, the messages being transmitted based on the charge transfer information.

3. The apparatus of claim 1, wherein the instructions further cause the apparatus to: receive an acknowledgment message in response to transmitting the message accepting the charge transfer, wherein the charge transfer is initiated based on receiving the acknowledgment message.

4. The apparatus of claim 1, wherein the message accepts the charge transfer, the message comprising at least one of: a charge transfer schedule, an identifier associated with the wireless communication device, the location of the wireless communication device, authorization from the owner of the wireless communication device, or the amount of power to be transferred during the time period.

5. The apparatus according to claim 1, wherein: The wireless communication device is one of a plurality of wireless communication devices; The instruction further enables the device to: Transmit another request to one or more of the plurality of wireless communication devices to participate in the charge transfer; as well as Receive a response from each of the one or more wireless communication devices, the response indicating whether each of the one or more wireless communication devices will respond to the other request to participate in the charge transfer; and The message indicating whether to accept the request for the charge transfer is transmitted based on the response from each of the one or more wireless communication devices.

6. The apparatus of claim 5, wherein the instructions further cause the apparatus to: transmit to each of the one or more wireless communication devices an indication of the amount of power to be transferred by each of the one or more wireless communication devices.

7. The apparatus of claim 5, wherein the message indicates acceptance of the charge transfer, and the message further indicates a first amount of wireless communication devices that will participate in the charge transfer to the power grid based on the response from each of the one or more wireless communication devices.

8. The apparatus of claim 1, wherein the request is received at a power supply equipment communication controller (SECC) associated with the wireless communication device.

9. The apparatus according to claim 8, wherein: The wireless communication device is one of a plurality of wireless communication devices associated with the SECC; and In order to configure the charge transfer, the instructions cause the device to configure the charge transfer from each of the plurality of wireless communication devices to the power grid via the SECC, based on the amount of remaining charge of each of the plurality of wireless communication devices, a schedule set by the owner of the respective wireless communication device or by the power grid for the respective wireless communication device, or with the consent of the owner of the respective wireless communication device.

10. An apparatus for transferring charge from a device to a power grid, the apparatus comprising: At least one processor; At least one memory, said at least one memory being coupled to said at least one processor; and Instructions, which are stored in the memory and can be executed by the at least one processor, to cause the device to: A request for charge transfer from a wireless communication device to the power grid is transmitted from a controller associated with the power grid, wherein the request indicates the power requirements of the power grid during a certain period of time; Based on the power requirement, receive a message indicating whether to accept the request for the charge transfer; as well as When the message indicates acceptance of the charge transfer, the charge transfer from the wireless communication device to the power grid is initiated during the time period.

11. The apparatus of claim 10, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the location of the power grid, the cost-effectiveness of the charge transfer to the owner of the wireless communication device, a schedule associated with the charge transfer, one or more timestamps associated with the request, a message count indicating the number of requests transmitted to the wireless communication device, authorization from the owner of the wireless communication device, or security credentials.

12. The apparatus of claim 10, wherein the instructions further cause the apparatus to: transmit an acknowledgment message in response to receiving the message accepting the charge transfer, wherein the charge transfer is initiated based on transmitting the acknowledgment message.

13. The apparatus of claim 10, wherein the request is transmitted to a power supply equipment communication controller (SECC) associated with the wireless communication device.

14. The apparatus of claim 13, wherein the wireless communication device is one of a plurality of wireless communication devices associated with the SECC, and the request is for charge transfer from the plurality of wireless communication devices.

15. An apparatus for transferring charge from a device to a power grid, the apparatus comprising: At least one processor; At least one memory, said at least one memory being coupled to said at least one processor; and Instructions, which are stored in the memory and can be executed by the at least one processor, to cause the device to: A request for charge transfer from the wireless communication device to the power grid is transmitted from a controller associated with the wireless communication device, wherein the request indicates the amount of power available for transfer to the power grid during a certain period of time; Receive a message indicating whether to accept the request for the charge transfer; as well as When the message indicates acceptance of the charge transfer, the charge transfer from the wireless communication device to the power grid is initiated during the time period.

16. The apparatus of claim 15, wherein the instructions further cause the apparatus to: determine a schedule for the charge transfer based on the operational history of the wireless communication device, wherein the request for the charge transfer is transmitted based on the schedule.

17. The apparatus of claim 15, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the current amount of available charge of the wireless communication device, a transfer window including a start time and an end time for the charge transfer, an identifier associated with the wireless communication device, or authorization from the owner of the wireless communication device.

18. The apparatus of claim 15, wherein the instructions further cause the apparatus to: After receiving the message accepting the charge transfer, an acknowledgment message is received, wherein the charge transfer is initiated based on the receipt of the acknowledgment message.

19. The apparatus of claim 15, wherein the message received by the controller associated with the wireless communication device rejects the charge transfer, the message indicating a reason for rejecting the charge transfer.

20. The apparatus of claim 19, wherein the message received by the controller associated with the wireless communication device rejects the charge transfer for the first power grid location, the message indicating a second power grid location for which a charge transfer can be accepted.

21. The apparatus according to claim 15, wherein: The wireless communication device is one of a plurality of wireless communication devices; The instruction further enables the device to: Transmit another request to one or more of the plurality of wireless communication devices to participate in the charge transfer; as well as Receive a response from each of the one or more wireless communication devices, the response indicating whether each of the one or more wireless communication devices will participate in the charge transfer in response to the other request; and The instructions cause the device to configure the charge transfer based on the response from each of the one or more wireless communication devices.

22. The apparatus of claim 21, wherein the instructions further cause the apparatus to: transmit to each of the one or more wireless communication devices an indication of the amount of power to be transferred by each of the one or more wireless communication devices.

23. The apparatus of claim 15, wherein the request is transmitted by a power supply equipment communication controller (SECC) associated with the wireless communication device.

24. The apparatus according to claim 23, wherein: The wireless communication device is one of a plurality of wireless communication devices associated with the SECC; and In order to configure the charge transfer, the instructions cause the device to: configure charge transfer from each of the plurality of wireless communication devices to the power grid via the SECC, based on the amount of remaining charge in each of the plurality of wireless communication devices.

25. An apparatus for transferring charge from a device to the power grid, the apparatus comprising: At least one processor; At least one memory, said at least one memory being coupled to said at least one processor; and Instructions, which are stored in the memory and can be executed by the at least one processor, to cause the device to: Receive a request from a controller associated with a wireless communication device for a charge transfer from the wireless communication device to the power grid, wherein the request indicates the amount of power available for transfer to the power grid during a certain period of time; Transmit a message indicating whether to accept the request for the charge transfer; as well as When the message indicates acceptance of the charge transfer, the charge transfer from the wireless communication device to the power grid is initiated during the time period.

26. The apparatus of claim 25, wherein the request further indicates charge transfer information, the charge transfer information including at least one of: the current amount of available charge of the wireless communication device, a transfer window including a start time and an end time for the charge transfer, an identifier associated with the wireless communication device, or authorization from the owner of the wireless communication device, wherein the message is transmitted based on the charge transfer information.

27. The apparatus of claim 25, wherein the request is received from a power supply equipment communication controller (SECC) associated with the wireless communication device.

28. The apparatus of claim 27, wherein the wireless communication device is one of a plurality of wireless communication devices associated with the SECC, and the request is for charge transfer from the plurality of wireless communication devices.

29. The apparatus of claim 25, wherein the request is one of a plurality of requests for charge transfer from a plurality of wireless communication devices received by a controller associated with the power grid, the instructions further causing the at least one processor to determine a priority associated with the plurality of requests, wherein the message is transmitted based on the determination.

Images