Systems and methods for managing bunching of vehicles at a battery charging and swapping station

Abstract

Embodiments herein disclose methods and systems for identifying bunching of vehicles at a batteiy charging and swapping station in a live manner and addressing the bunching of vehicles by taking necessary actions through various solutions.

Description

SYSTEMS AND METHODS FOR MANAGING BUNCHING OF VEHICLES AT A BATTERY CHARGING AND SWAPPING STATIONThe following specification particularly describes the invention and the manner in which it is to be performed: -TECHNICAL FIELD

[0001] Embodiments disclosed herein relate to battery charging and swapping stations, and more particularly to detecting and preventing the bunching of vehicles at a battery charging and swapping station.BACKGROUND

[0002] Battery charging and swapping stations are used by vehicles, which use the portable and swappable battery packs stored at these stations. The battery charging and swapping stations arc strategically positioned at different locations considering the demand for a swap based on previous swapping history, vehicle route information, vehicle category, user preferences, etc. However, there are scenarios where the vehicle gets lined up / bunching / queuing at different swapping stations due to the increase in the number of vehicles with swappable battery pack configurations. Bunching of vehicles at the battery charging and swapping station can happen due to multiple factors including time-based demand patterns, seasonal demand patterns, product issues, or improper station-to-vehicle ratios. This leads to customer dissatisfaction as the customer expects the swapping to be done at the earliest time.

[0003] Hence, there is a need in the art for a system and method for monitoring and preventing the bunching of vehicles at the battery charging and swapping station.OBJECTS

[0004] The principal object of embodiments herein is to disclose methods and systems for identifying the bunching of vehicles at a battery charging and swapping station in a live manner and addressing the bunching of vehicles by talcing necessary actions through various solutions.

[0005] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.BRIEF DESCRIPTION OF FIGURES

[0006] Embodiments herein arc illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0007] FIG. 1 depicts a system for providing swappable batteries to one or more vehicles, according to embodiments as disclosed herein;

[0008] FIG. 2 is a flowchart depicting the process of monitoring the bunching of vehicles at battery' charging and swapping stations, according to embodiments as disclosed herein;

[0009] FIG. 3 depicts a battery' pack, according to embodiments as disclosed herein;

[0010] FIG. 4 depicts the battery charging and swapping station, according to embodiments as disclosed herein; and

[0011] FIG. 5 depicts the Control Network Centre (CNC). according to embodiments as disclosed herein.DETAILED DESCRIPTION

[0012] The embodiments herein and the various features and advantageous details thereof arc explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0013] The embodiments herein achieve methods and systems for identifying the bunching of vehicles at a battery charging and swapping station in a live manner and addressing the bunching of vehicles by taking necessary actions through various solutions. Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0014] Embodiments herein disclose systems and methods for identifying and preventing the bunching of vehicles at a battery charging and swapping station. Embodiments herein collect live bunching data at battery charging and swapping stations through broadcast data between the vehicle (i.e., battery packs) and the battery swapping station, sending the live bunching data to a remote-control center (i.e., the controller), creating a bunching record in the controller and performing at least one action based onthe bunching data (on the bunching data meeting one or more pre-defined criteria).

[0015] FIG. 1 depicts a network for providing swappable batteries to one or more vehicles. As illustrated in FIG. 1, the battery swapping network 100 comprises at least one battery charging and swapping station 102 (hereinafter referred to interchangeably as a swap station, station, BSS, and so on), a Control Network Centre (CNC) 104, and a plurality of battery packs 106. The battery charging and swapping station 102 can comprise one or more battery docks / bays (not shown), wherein one or more battery packs 106 may be charged and / or conditioned. The battery charging and swapping station 102 can enable a user of a vehicle to swap battery packs present in the vehicle with charged and conditioned battery packs 106 from the battery charging and swapping station 102, on the user being successfully authenticated. The CNC 104 can be a cloud server, a server, the cloud, or any other remote processing entity.

[0016] The battery' charging and swapping station 102 can communicate with the CNC 104 using a wireless communication means and / or a wired communication means. Examples of the wireless communication means can be, a cellular network, Wi-Fi, and so on. Examples of the wired communication means can be, but not limited to, a local area network, an ethernet connection, and so on.

[0017] In an embodiment herein, the battery packs 106 can be located in a vehicle, wherein the battery pack 106 can provide power / energy to the vehicle. In an embodiment herein, the battery packs 106 can be located in the battery charging and swapping station 102, wherein the battery pack 106 can be charged and / or conditioned and / or stored in battery charging and swapping station 102. The battery packs 106 can communicate with the CNC 104 and / or the battery charging and swapping station 102 using a wireless communication means and / or a wired communication means. Examples ofthe wireless communication means can be, a cellular network, Wi-Fi, and so on. Examples of the wired communication means can be, but not limited to, a local area network, an ethernet connection, and so on.

[0018] In an embodiment herein, on successfully authenticating a user, the battery charging and swapping station 102 can dispense charged battery packs to the user, for fully depleted or partially depleted battery packs (which are present in the battery charging and swapping station 102).

[0019] If the battery charging and swapping station 102 does not have sufficient batteries for dispensing to a user, there may be a queue of users (i.e., vehicles) formed at the battery charging and swapping station 102 (hereinafter referred to as bunching). Embodiments herein disclose methods and systems for monitoring and reducing the bunching of vehicles at the battery charging and swapping station 102.

[0020] Consider a scenario, wherein there arc no battery packs available for swapping immediately at the battery charging and swapping station 102 or there arc no sufficient number of battery packs 106 available at the battery charging and swapping station 102 for swapping. After a first period of time after the ignition of the vehicle has been turned OFF (wherein the battery pack 106 can receive an unlock command from the battery charging and swapping station 102 within the first period of time), the battery pack 106 can enter a broadcasting mode for a second period of time. In the broadcast mode, the battery pack 106 can broadcast a master dock ID of the vehicle and other information (such as, but not limited to, SoC, battery ID, user credentials, and so on). After the second period of time, the battery pack 106 can enter an idle mode for a third period of time. After the third period of time, the battery pack 106 can re-enter the broadcasting mode for the second period of time. The battery pack 106 repeats the above cycle of switching between the broadcast mode and the idle mode for a fourth periodof time. After the fourth period of time, the battery pack 106 can stay in the idle mode.

[0021] In an example herein, after 2 minutes from the ignition of the vehicle having been turned OFF, the battery pack 106 enters a broadcasting mode for five minutes. In the broadcast mode, the battery pack 106 can broadcast the master dock ID of the vehicle. After five minutes, the battery pack 106 enters an idle mode for three minutes. After three minutes, the battery pack 106 can re-enter the broadcasting mode for five minutes. The battery pack 106 repeats the above cycle of switching between the broadcast mode and the idle mode for twenty five minutes. After twenty five minutes, the battery pack 106 stays in the idle mode.

[0022] If there are no battery packs readily available for dispensing within the battery charging and swapping station 102, the battery charging and swapping station 102 can go to scanning mode and continue to be in scanning mode till at least one battery pack is available for dispensing from the station. The battery charging and swapping station 102 can monitor the master dock IDs from different battery packs (as received in the respective broadcast). If the user corresponding to a received master dock ID (i.e., the user in whose vehicle that battery pack has broadcast the master dock ID) has not authenticated himself (using an action such as, but not limited to, providing his username and password, swiping a key fob, and so on), the battery charging and swapping station 102 can store the received master dock IDs in a local memory and increment a counter. The counter can indicate the number of vehicles waiting at the battery charging and swapping station 102. The battery charging and swapping station 102 can send the received master dock IDs to the CNC 104.

[0023] The battery charging and swapping station 102 can identify a unique identification means for the vehicle (such as, but not limited to, the Vehicle Identification Number (VIN) of the vehicle) and vehicle segment(which can be the type of vehicle - 2 wheeler, 3 wheeler, car, bus, truck, van, goods carrier, and so on) using the received master dock IDs, cither from a local source (such as a memory) or a remote entity (such as the CNC 104, a cloud storage, a file server, a data server, and so on). The battery charging and swapping station 102 can store the information in a suitable location (such as a local memory), The battery charging and swapping station 102 can build the bunching data continuously from the received master dock IDs; i.e., the vehicles in which the battery packs 106 have broadcasted the master dock ID and to which, charged battery packs have not yet been dispensed). When the counter exceeds a first pre-defined number of vehicles, the battery charging and swapping station 102 can initiate a bunching alert. The bunching alert can indicate to the CNC 104 about the vehicles getting bunched by triggering sound and display alerts at the CNC 104. When the counter has exceeded a second pre-defined number of vehicles or the battery pack requirement of the vehicles in the queue at the battery charging and swapping station 102 crosses a pre-defined threshold, the battery charging and swapping station 102 can initiate a high priority alert. The high priority alert can trigger one or more additional actions such as, but not limited to, rerouting the vehicle in the queue to nearby battery charging and swapping stations, sending an emergency swapping vehicle to that particular station by the CNC 104, and so on. The battery charging and swapping station 102 can communicate these alerts to the CNC 104.

[0024] Based on the alert, the CNC 104 can take one or more actions, such as, but not limited to, guiding vehicles queued at the battery charging and swapping station 102 to other battery charging and swapping stations 102 (which have lesser waiting time and / or battery packs ready for dispensing), guiding mobile battery charging and swapping stations to the site of the battery charging and swapping station 102 (so as to enable vehicles waiting at the battery charging and swapping station 102 to swap batteries atthe mobile battery charging and swapping station), routing vehicles approaching the battery charging and swapping station 102 to other battery charging and swapping stations 102 (which have lesser waiting time and / or battery packs ready for dispensing), and so on.

[0025] FIG. 2 is a flowchart depicting the process of monitoring the bunching of vehicles at battery charging and swapping stations. Consider a scenario, wherein there are no battery packs available for swapping immediately at the battery charging and swapping station 102 or there are no sufficient number of battery packs 106 available at the battery charging and swapping station 102 for swapping.

[0026] In step 201, the battery pack 106 in vehicles (which are at the battery charging and swapping station 102 and have not received charged batteries) switches between a broadcasting mode and an idle mode for the fourth period of time. In the broadcasting mode, the battery pack 106 sends the master dock ID of the vehicle and other information.

[0027] In step 202, the battery charging and swapping station 102 can be in a scanning mode for any broadcasting information, as broadcasted by the battery packs 106.

[0028] In step 203, the battery charging and swapping station 102 stores the received master dock IDs in a local memory and increments the counter. Further, the battery charging and swapping station 102 identifies the unique identification means for the vehicle using the received master dock IDs and the vehicle segment. On the counter exceeding the first pre-defined number of vehicles (step 204), in step 205, the battery charging and swapping station 102 initiates a bunching alert. When the counter exceeds the second pre-defined number of vehicles or the battery pack requirement of the vehicles in the queue at the battery charging and swapping station 102 crosses the pre -defined threshold (step 206), in step 207, the battery chargingand swapping station 102 initiates a high-priority alert. The battery charging and swapping station 102 communicates these alerts to the CNC 104.

[0029] Based on the received alerts, in step 208, the CNC 104 performs one or more actions, such as, but not limited to, guiding vehicles queued at the battery' charging and swapping station 102 to other battery charging and swapping stations 102 (which have lesser waiting time and / or battery packs ready for dispensing), guiding mobile battery charging and swapping stations 102 to the site of the battery' charging and swapping station 102 (so as to enable vehicles waiting at the battery charging and swapping station 102 to swap batteries at the mobile battery charging and swapping station), routing vehicles approaching the battery charging and swapping station 102 to other battery' charging and swapping stations 102 (which have lesser waiting time and / or battery packs ready for dispensing), and so on. The various actions in method 200 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 2 may be omitted.

[0030] FIG. 3 depicts a battery pack. The battery packs 106 can be present in a vehicle or in the battery charging and swapping station 102. Here, it is assumed that the battery pack 106 is present in a vehicle, wherein the vehicle is at a battery charging and swapping station 102 for swapping the battery packs 106 for fully charged battery packs 106. Each vehicle may comprise of one or more battery packs 106. The battery pack 106, as depicted, comprises a battery controller 302, one or more communication modules 304, and a memory 306.

[0031] The communication module 304 enables the battery pack 106 to communicate with at least one external entity, such as, but not limited to, the battery charging and swapping station 102, the CNC 104, and so on, using at least one communication means. Examples of the communication meanscan be, but not limited to, Bluetooth, Wi-Fi, cellular networks, Bluetooth Low Energy (BLE), and so on.

[0032] The memory 306 can comprise information such as, a master dock ID, vehicle information, information received from the battery charging and swapping station 102, information received from the CNC 104, and so on. Examples of the memory 306 may be, but are not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid- state drive (SSD), and so on. Further, the memory 306 may include one or more computer-readable storage media. The memory 306 may include one or more non-volatile storage elements. Examples of such non-volatile storage elements may include Random Access Memory (RAM), Read Only Memory (ROM), magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory' 306 may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted to mean that the memory is non-movable. In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0033] The term ‘battery controller 302' as used in the present disclosure, may refer to, for example, hardware including logic circuits; a hardware / software combination such as a processor executing software; or a combination thereof. For example, the processing circuitry' more specifically may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), aprogrammable logic unit, a microprocessor, application- specific integrated circuit (ASIC), etc. For example, the battery controller 302 may include at least one of, a single processer, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators.

[0034] Consider that there are no battery packs available for swapping immediately at the battery charging and swapping station 102 or there are no sufficient number of battery packs 106 available at the battery charging and swapping station 102 for swapping. If the vehicle is in the ON state, the battery controller 302 can be in the broadcast mode. In the broadcasting mode, the communication module 304 can use a suitable communication means (such as, Bluetooth) for broadcasting information, such as, but not limited to, the master dock ID of the vehicle, and other related information, wherein the broadcasting information can be received by the battery charging and swapping station 102. On the vehicle being turned OFF, the battery controller 302 can switch between the broadcasting mode and the idle mode based on pre -defined time periods.

[0035] On determining that the vehicle has reached the battery charging and swapping station 102 and the ignition of the vehicle has been turned OFF, the battery controller 302 can wait for the first period of time. Within the first period of time, the battery controller 302 can receive an unlock command from the battery charging and swapping station 102, wherein the battery controller 302 can unlock itself and additional battery packs present in the vehicle (which need to be swapped). After the first period of time, the battery charging and swapping station 102 can enter the broadcasting mode for the second period of time. In the broadcasting mode, the communication module 304 can use a suitable communication means (such as Bluetooth) for broadcasting information, such as, but not limited to,the master dock ID of the vehicle, and other related information, wherein the broadcasting information can be received by the battery charging and swapping station 102.

[0036] On expiry of the second period of time, the battery controller 302 can enter an idle mode for the third period of time, wherein there is no broadcast being performed. After the third period of time, the battery controller 302 can re-enter the broadcasting mode for the second period of time. The battery controller 302 can repeat the above cycle of switching between the broadcast mode and the idle mode for a fourth period of time. After the fourth period of time, the battery' pack 106 can stay in the idle mode.

[0037] In an example herein, after 2 minutes from the ignition of the vehicle having been turned OFF, the battery controller 302 enters a broadcasting mode for five minutes. In the broadcast mode, the battery controller 302 can broadcast the master dock ID of the vehicle. After five minutes, the battery controller 302 enters an idle mode for three minutes. After three minutes, the battery controller 302 can re-enter the broadcasting mode for five minutes. The battery controller 302 repeats the above cycle of switching between the broadcast mode and the idle mode for twenty five minutes. After twenty five minutes, the battery controller 302 stays in the idle mode.

[0038] In an embodiment herein, on receiving information from the battery charging and swapping station 102 that batteries are available for swapping, the battery controller 302 can reset itself, so as to prepare itself for swapping. In an example herein, on receiving information from the battery charging and swapping station 102 that batteries are available for swapping, the battery controller 302 can reset itself by the user turning the vehicle ON and then OFF, so as to prepare itself for swapping.

[0039] FIG. 4 depicts the battery charging and swapping station. The battery charging and swapping station 102 comprises a station controller 402,one or more communication modules 404, a memory 406, an authentication module 408, and one or more user interfaces 410.

[0040] The communication module 404 enables the battery charging and swapping station 102 to communicate with at least one external entity, such as, but not limited to, the battery pack 106, the CNC 104, a user device (i.e., a device being used by the user, such as, but not limited to, a mobile phone, a wearable device, an instrument console in the vehicle, a key fob, and so on), and so on, using at least one communication means. Examples of the communication means can be, but not limited to, Bluetooth, Wi-Fi, cellular networks, Bluetooth Low Energy (BLE), and so on.

[0041] The memory 406 can comprise of information such as, a master dock ID, vehicle information, information received from the battery packs 106, information received from the CNC 104, and so on. Examples of the memory 406 may be, but arc not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. Further, the memory 406 may include one or more computer-readable storage media. The memory 406 may include one or more non-volatile storage elements. Examples of such non-volatile storage elements may include Random Access Memory (RAM), Read Only Memory (ROM), magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 406 may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "nontransit ory" should not be interpreted to mean that the memory is nonmovable. In certain examples, a non-transitory storage medium may storedata that may, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0042] The one or more user interfaces 410 can enable the battery charging and swapping station 102 to communicate with the users. Examples of the one or more user interfaces 410 can be, but not limited to, a display, a touch screen, one or more switches, one or more indicator lights, a microphone, a speaker, and so on. The one or more user interfaces 410 can enable information to be communicated to the users, such as, the number of batteries ready for swapping at the battery charging and swapping station 102, the time taken for batteries to be ready for swapping at the battery charging and swapping station 102, and so on.

[0043] The authentication module 408 enables users to authenticate themselves at the battery charging and swapping station 102. The authentication module 408 can enable a user to use an action such as, but not limited to, providing his username and password, swiping a key fob, biometric means (such as fingerprints, iris scans, palm prints, face scans, and so on), a user device (such as a wearable device, a mobile phone, a tablet, and so on), and so on.

[0044] The term ‘battery controller 402' as used in the present disclosure, may refer to, for example, hardware including logic circuits; a hardware / software combination such as a processor executing software; or a combination thereof. For example, the processing circuitry more specifically may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, application- specific integrated circuit (ASIC), etc. For example, the battery controller 302 may include at least one of, a single processor, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units(CPUs) of different kinds, microcontrollers, special media, and other accelerators.

[0045] On successfully authenticating a user, the battery controller 402 can dispense charged battery packs to the user, for fully depleted or partially depleted battery packs (which are present in the battery charging and swapping station 102), if batteries are available at the battery charging and swapping station 102.

[0046] Consider that there are no battery packs available for swapping immediately at the battery charging and swapping station 102 or there are no sufficient number of battery packs 106 available at the battery charging and swapping station 102 for swapping.

[0047] The battery controller 402 can go into scanning mode using the communication module 404. In an example herein, the communication module 404 can use Bluetooth for performing scanning. In scanning mode, the battery controller 402 can receive information from one or more sources, such as, the battery packs 106. In an embodiment herein, in the scanning mode, the battery controller 402 can receive the broadcast information, such as, the master dock ID, and other information from one or more battery packs 106 present in one or more vehicles. The battery controller 402 can continue to be in scanning mode till at least one battery pack is available for dispensing from the station.

[0048] The battery controller 402 can monitor the master dock IDs from different battery packs (as received in the respective broadcast). If the user corresponding to a received master dock ID (i.e., the user in whose vehicle that battery pack has broadcast the master dock ID) has not authenticated himself, the battery controller 402 can store the received master dock IDs in the memory 406 and increment the counter. In an embodiment herein, the battery controller 402 can send the received master dock IDs to the CNC 104 via the communication module 406.

[0049] On receiving the broadcast information, the battery controller 402 can identify a unique identification means for the vehicle (such as, but not limited to, the Vehicle Identification Number (VIN) of the vehicle and vehicle segment (which can be the type of vehicle - 2 wheeler, 3 wheeler, car, bus, truck, van, goods carrier, and so on) using the received master dock IDs, either from a local source (such as the memory 406) or a remote entity (such as the CNC 104, a cloud storage, a file server, a data server, and so on). The battery controller 402 can built the bunching data continuously from the received master dock IDs; i.e., the vehicles in which the battery packs 106 have broadcasted the master dock ID and to which, charged battery packs have not yet been dispensed).

[0050] When the counter exceeds the first pre-defined number of vehicles, the battery controller 402 can initiate a bunching alert. When the counter has exceeded the second pre-defined number of vehicles or the battery pack requirement of the vehicles in the queue at the battery charging and swapping station 102 crosses a pre-defined threshold, the battery controller 402 can initiate a high-priority alert. The battery controller 402 can communicate these alerts to the CNC 104, via the communication module 406.

[0051] The battery controller 402 can communicate the stored data to the CNC 104 at periodic intervals and / or on pre-defined events occurring (such as determining that an alert is to be issued), via the communication module 406.

[0052] FIG. 5 depicts the Control Network Centre (CNC) 104. The CNC 104, as depicted, comprises a network controller 502, the communication module 504, and a memory 506.

[0053] The communication module 504 enables the CNC 104 to communicate with at least one external entity, such as, but not limited to, the battery pack 106, the battery charging and swapping station 102, a userdevice (i.e., a device being used by the user, such as, but not limited to, a mobile phone, a wearable device, an instrument console in the vehicle, a key fob, and so on), and so on, using at least one communication means. Examples of the communication means can be, but not limited to, Bluetooth, Wi-Fi, cellular networks, Bluetooth Low Energy (BLE), and so on.

[0054] The memory 506 can comprise of information such as, the master dock ID, vehicle information, information received from the battery packs 106, information received from the CNC 104, The memory 506 can comprise of information such as, the master dock ID, vehicle information, information received from the battery packs 106, information received from the battery charging and swapping station 102, alerts, locations of battery charging and swapping stations 102, current locations of mobile swapping stations, bunching alerts, bunching records, and so on. Examples of the memory 506 may be, but arc not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. Further, the memory 506 may include one or more computer-readable storage media. The memory 506 may include one or more non-volatile storage elements. Examples of such non-volatile storage elements may include Random Access Memory (RAM), Read Only Memory (ROM), magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 506 may, in some examples, be considered a non -transitory storage medium. The term "non- transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted to mean that the memory is non-movable. In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0055] The term ‘network controller 502' as used in the present disclosure, may refer to, for example, hardware including logic circuits; a hardware / software combination such as a processor executing software; or a combination thereof. For example, the processing circuitry more specifically may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, application- specific integrated circuit (ASIC), etc. For example, the network controller 502 may include at least one of, a single processer, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators.

[0056] On receiving the alert from the battery charging and swapping station 102, the network controller 502 can take one or more actions, such as, but not limited to, guiding vehicles queued at the battery charging and swapping station 102 to other battery charging and swapping stations 102 (which have lesser waiting time and / or battery packs ready for dispensing), guiding one or more mobile battery charging and swapping stations to the site of the battery charging and swapping station 102 (so as to enable vehicles waiting at the battery charging and swapping station 102 to swap batteries at the mobile battery charging and swapping station), routing vehicles approaching the battery charging and swapping station 102 to other battery charging and swapping stations 102 (which have lesser waiting time and / or battery packs ready for dispensing), and so on.

[0057] The network controller 502 can monitor the bunching of vehicles at stations. Based on the alerts and information received from the battery charging and swapping station 102, the network controller 502 can collate the live bunching status of the stations, which can be accessed / viewedby a display (not shown) and / or an external device (such as a control console, a computer, a laptop, a tablet, a mobile device, a phone, and so on). The network controller 502 can collate information such as, but not limited to, total vehicles in queue at the various stations, vehicles in queue at each stations, types of vehicles, a unique vehicle identifications means, average State of Charge (SoC) of battery packs in each vehicle, duration that the vehicles have been in queue, number of packs required for serving the queued vehicle, corresponding station ID, and so on. For each station, the network controller 502 can maintain the bunching records, wherein the records can comprise: total vehicles in the queue, vehicle type, vehicle ID, average SoC of packs in each vehicle, start time, end time, date, and station ID.

[0058] The network controller 502 can further maintain a consolidated report for bunching at the plurality of battery charging and swapping stations 102, wherein the consolidated report can comprise of the number of occurrences in a day where demand exceeded supply (i.c. , vehicle bunching at the stations), the total number of vehicles waiting on a per day basis, the types, and the corresponding number of vehicles. The consolidated report can further have vehicle queuing time that includes start time, end time, station ID, and average SoC of battery packs in the vehicle during that time. The network controller 502 can make the records on a daily, weekly, monthly, and date selection basis.

[0059] In an embodiment herein, the network controller 502 can create a bunching record for a vehicle only for a waiting time of more than a waiting threshold.

[0060] In an embodiment herein, the battery charging and swapping station 102 can be provided with sensors and cameras. The sensors and cameras can be remotely connected to the CNC 104. The sensors can capture the lineup of vehicles at the station continuously at regular intervals. Thecamera can relay the live information of the vehicle bunched at the station. In an embodiment herein, the cameras arc thermal imaging or infra-red based cameras which can determine and signal the bunching of vehicles at a particular battery charging and swapping station 102.

[0061] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements shown in FIGs. 1, 3, 4 and 5 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0062] The embodiment disclosed herein describes methods and systems for identifying bunching of vehicles at a battery charging and swapping station in a live manner and addressing the bunching of vehicles by taking necessary actions through various solutions. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein couldbe implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, c.g., using a plurality of CPUs.

[0063] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

STATEMENT OF CLAIMSWc claim:

1. A method (200) for monitoring bunching of vehicles at a battery charging and swapping station (102), wherein the battery charging and swapping station (102) does not have sufficient batteries for dispensing to the vehicles, the method comprising: sending (201), by a battery pack (106), broadcasting information in a broadcasting mode, wherein the broadcasting information comprises a master dock ID; receiving (202), by the battery charging and swapping station (102), the broadcasting information, wherein the battery charging and swapping station (102) is in a scanning mode; incrementing a counter (203), by the battery charging and swapping station (102), on receiving a master dock ID, if a user corresponding to the received master dock ID has not authenticated themselves at the battery charging and swapping station (102); sending an alert (205, 207), by the battery charging and swapping station (102) to a Control Network Centre (CNC) (104), on the counter exceeding a first threshold, or a second threshold; and performing at least one action (208) by the CNC (104), on receiving the alert.

2. The method, as claimed in claim 1, wherein the method further comprises: switching, by the battery pack (106), between a broadcast mode and an idle mode for a further period of time, wherein the battery pack (106) enters the broadcasting mode for a second period of time, after a first period of time after an ignition of the vehicle has been turned OFF and the battery pack (106) enters the idle mode for a third period of time, after the second period of time; andstaying, by the battery pack (106), in the idle mode after the fourth period of time.

3. The method, as claimed in claim 1, wherein the method further comprises identifying, by the battery charging and swapping station (102), a unique identification means for the vehicle and vehicle segment using the received master dock ID.

4. The method, as claimed in claim 1, wherein the method further comprises sending a bunching alert, by the battery charging and swapping station (102) to the CNC (104), on the counter exceeding the first threshold.

5. The method, as claimed in claim 1 , wherein the method further comprises sending a high priority alert, by the battery charging and swapping station (102) to the CNC (104, on the counter exceeding the second threshold.

6. The method, as claimed in claim 1, wherein the method further sending an alert by the battery charging and swapping station (102) to the CNC (104) if battery pack requirement of vehicles queued at the battery charging and swapping station (102) crosses a prc-dcfincd threshold.

7. The method, as claimed in claim 1 , wherein the at least one action comprises: guiding vehicles queued at the battery charging and swapping station (102), by the CNC (104) to other battery charging and swapping stations (102), wherein the other battery charging and swapping stations (102) have lesser waiting time and / or battery packs ready for dispensing; guiding at least one mobile battery charging and swapping station, by the CNC (104), to the battery charging and swapping station (102); and routing vehicles approaching the battery charging and swapping station (102), by the CNC (104), to other battery charging and swapping stations (102), wherein the other battery charging and swapping stations (102) have lesser waiting time and / or battery packs ready for dispensing.

8. The method, as claimed in claim 3, wherein the method further comprises generating at least one report, by the CNC (104), based on information provided by the battery charging and swapping station, wherein the information comprises the master dock ID, current value of the counter, the unique identification means for the vehicle; and the vehicle segment.

9. A battery charging and swapping station (102), the battery charging and swapping station configured to: receive information broadcasted by a battery pack (106), wherein the received information comprises a master dock ID and the battery charging and swapping station (102) is in a scanning mode; increment a counter, on receiving a master dock ID, if a user corresponding to the received master dock ID has not authenticated themselves at the battery charging and swapping station (102); send an alert to a Control Network Centre (CNC) (104), on the counter exceeding a first threshold, or a second threshold.

10. The batter}' charging and swapping station, as claimed in claim 9, wherein the battery charging and swapping station is further configured to identify a unique identification means for the vehicle and vehicle segment using the received master dock ID.

11. The batter ' charging and swapping station, as claimed in claim 9, wherein the battery charging and swapping station is further configured to send a bunching alert, by the battery charging and swapping station (102) to the CNC (104, on the counter exceeding the first threshold.

12. The batter}' charging and swapping station, as claimed in claim 9, wherein the battery charging and swapping station is further configured to send a high priority alert to the CNC (104), on the counter exceeding the second threshold.

13. The batter}' charging and swapping station, as claimed in claim 9, wherein tire battery charging and swapping station is further configured tosend to the CNC (104) if battery pack requir ement of vehicles queued at the battery charging and swapping station (102) crosses a pre-defined threshold.

14. A battery pack (106) configured to: broadcast information in a broadcasting mode, wherein the broadcasting information comprises a master dock ID.

15. The battery pack, as claimed in claim 14, wherein the battery pack is further configured to: switch between a broadcast mode and an idle mode for a further period of time, wherein the battery pack (106) is configured to enter the broadcasting mode for a second period of time, after a first period of time after an ignition of the vehicle has been turned OFF and the battery pack (106) enters the idle mode for a third period of time, after the second period of time; and stay in the idle mode after the fourth period of time.

16. A Control Network Centre (CNC) (104) in battery swapping network, the CNC configured to: receive an alert from a battery charging and swapping station (102), on a counter exceeding a first threshold, or a second threshold; and perform at least one action, on receiving the alert, wherein the at least one action comprises: guiding vehicles queued at the battery charging and swapping station (102) to other battery charging and swapping stations (102), wherein the other battery charging and swapping stations (102) have lesser waiting time and / or battery packs ready for dispensing; guiding at least one mobile battery charging and swapping station the battery charging and swapping station (102); and routing vehicles approaching the battery charging and swapping station (102) to other battery charging and swapping stations (102), wherein the other battery charging and swapping stations (102) have lesser waiting time and / or battery packs ready for dispensing.

17. The CNC, as claimed in claim 16, wherein the CNC is further configured to generate at least one report based on information provided by the battery charging and swapping station, wherein the information comprises a master dock ID, current value of the counter, a unique identification means for a vehicle; and a vehicle segment.

Images