Light-duty vehicle networking methods, devices, electronic equipment and storage media

By establishing a StarFlash communication network in light-duty vehicles, and having the vehicle itself manage the onboard ecological equipment, the problem of poor communication stability between light-duty vehicles and onboard ecological equipment is solved, achieving stable operation and efficient communication even when the user terminal is offline.

CN123123845APending Publication Date: 2026-11-17SHANGHAI JUNZHENG NETWORK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611313052.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, communication between light-duty vehicles and on-board ecological equipment is easily affected by factors such as mobile phone offline or power outages, resulting in poor operational stability and the inability to communicate independently and continuously.

Method used

By establishing a StarFlash communication network in light-powered vehicles, the vehicle itself acts as the network coordinator, directly managing and controlling on-board ecosystem devices, enabling direct communication between devices, dynamically configuring resources and generating control commands, and reducing transmission latency and misjudgments.

Benefits of technology

It improves the operational stability and communication efficiency of light-duty vehicles and on-board ecological equipment when the user terminal is offline, reduces transmission latency and misjudgment, and enhances the efficiency and security of equipment resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123845A_ABST
    Figure CN123123845A_ABST
Patent Text Reader

Abstract

This application discloses a networking method, apparatus, electronic device, and storage medium for light-duty electric vehicles, belonging to the field of vehicle communication technology. The light-duty electric vehicle includes a StarScan communication module; the method includes: creating a StarScan communication network through the StarScan communication module and connecting multiple on-board ecosystem devices to the StarScan communication network; acquiring status data of each on-board ecosystem device through the StarScan communication network; determining the operating scenario type of the light-duty electric vehicle based on the status data of each on-board ecosystem device, the status data of the StarScan communication network, and the status data of the vehicle, and generating control commands corresponding to each on-board ecosystem device based on the operating scenario type; and sending each control command to the corresponding on-board ecosystem device through the StarScan communication network. This application can improve the stability of the operation of light-duty electric vehicles and on-board ecosystem devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of vehicle communication technology, and in particular relates to a method, device, electronic device and storage medium for networking light-powered vehicles. Background Technology

[0002] With the increasing intelligence of light-powered vehicles such as electric bicycles, electric motorcycles, and electric scooters, intelligent in-vehicle ecosystem devices such as smart helmets, smart locks, locators, alarms, and riding recorders are being introduced into the vehicle's intelligent ecosystem. Each in-vehicle ecosystem device needs to be connected to a wireless network to enable management and control of these devices during vehicle operation.

[0003] In related technologies, a mobile phone-centric networking model is typically adopted, where each in-vehicle ecosystem device connects to the phone via Bluetooth, and the phone then interacts with the vehicle or the cloud. However, in this architecture, communication between the vehicle and the in-vehicle ecosystem devices requires relay communication through the mobile phone, preventing the vehicle's intelligent ecosystem from operating independently. When the phone leaves the vehicle, is powered off, Bluetooth is turned off, the system is in background sleep, or the application is not activated, the original communication link is interrupted, and the vehicle and the in-vehicle ecosystem devices cannot continue to communicate, severely affecting the stability of the operation of light-duty vehicles and in-vehicle ecosystem devices. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a method, apparatus, electronic device, and storage medium for networking light-duty vehicles, so as to improve the operational stability of light-duty vehicles and on-board ecological equipment.

[0005] In a first aspect, this application provides a networking method for light-duty electric vehicles, wherein the light-duty electric vehicle includes a star-flash communication module; the method includes: The StarSpark communication module is used to create a StarSpark communication network and connect multiple vehicle-mounted ecosystem devices to the StarSpark communication network. The status data of each of the vehicle-mounted ecological devices is obtained through the StarFlash communication network. Based on the status data of each of the vehicle-mounted ecological devices, the status data of the Star Flash communication network, and the status data of the light-duty electric vehicle, the operating scenario type of the light-duty electric vehicle is determined, and based on the operating scenario type, control commands corresponding to each of the vehicle-mounted ecological devices are generated. The control commands are sent to the corresponding vehicle-mounted ecological devices via the StarFlash communication network.

[0006] The networking method for light-duty vehicles provided in this application establishes a StarFlash communication network by the light-duty vehicles. The vehicles themselves act as network coordinators and core nodes of the intelligent ecosystem, directly managing and controlling the on-board ecosystem devices in a unified manner. This enables the vehicle's intelligent ecosystem to operate independently even when the user terminal is offline. By enabling data transmission between the vehicle and the on-board ecosystem devices through the StarFlash communication network, the communication path between the on-board ecosystem devices and the light-duty vehicles can be shortened, reducing the transmission latency of status data reporting and control command issuance. By aggregating and comprehensively analyzing the status data of each on-board ecosystem device, the StarFlash communication network, and the vehicle, the operating scenario type of the light-duty vehicles can be determined. Based on the operating scenario type, corresponding control commands for each on-board ecosystem device can be generated. This reduces the possibility of misjudgment caused by a single data source and mismatch between control commands and operating scenarios, thereby improving the stability of the operation of the light-duty vehicles and on-board ecosystem devices.

[0007] According to one embodiment of this application, connecting multiple vehicle-mounted ecological devices to the StarFlash communication network includes: Obtain the access request message sent by the target vehicle ecosystem device, and perform identity authentication on the target vehicle ecosystem device based on the access request message; If the identity authentication is successful, the type of the target vehicle-mounted ecosystem device is determined based on the access request message, and the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined based on the type of the target vehicle-mounted ecosystem device, the current operating scenario type of the light-duty vehicle, and the current status data of the StarFlash communication network. Based on the resource configuration parameters corresponding to the target vehicle-mounted ecological device, network resources are allocated to the target vehicle-mounted ecological device to connect it to the StarFlash communication network.

[0008] In this embodiment, by dynamically determining the resource configuration parameters corresponding to the target vehicle-mounted ecological device and allocating network resources based on the type of the target vehicle-mounted ecological device and the current operating scenario of the light-powered vehicle, the overall communication efficiency of the StarFlash communication network can be improved, and the resource utilization efficiency of each vehicle-mounted ecological device can be increased.

[0009] According to one embodiment of this application, determining the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device based on the type of the target vehicle-mounted ecosystem device, the current operating scenario type of the light-duty vehicle, and the current status data of the StarSignal communication network includes: Based on the type of the target vehicle-mounted ecological device and the current operating scenario of the light-powered vehicle, the communication priority corresponding to the target vehicle-mounted ecological device is determined; Based on the communication priority of each of the vehicle-mounted ecosystem devices and the current status data of the StarFlash communication network, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined.

[0010] In this embodiment, by determining the communication priority of the target vehicle ecosystem device in real time and allocating network resources based on the communication priority of each vehicle ecosystem device, it is possible to reduce the situation where low-priority devices preempt the network resources of high-priority devices, resulting in high-priority devices being unable to communicate normally, thereby improving the operational stability and collaborative efficiency of the vehicle intelligent ecosystem in scenarios with a large number of concurrent vehicle ecosystem devices.

[0011] According to one embodiment of this application, the step of performing identity authentication on the target vehicle-mounted ecosystem device based on the access request message includes: If the access request message includes the device identifier and binding credential of the target vehicle ecosystem device, a list of bound devices is retrieved based on the device identifier of the target vehicle ecosystem device; the list of bound devices stores multiple sets of device identifiers and binding credentials of historical access devices. If a historical access device matching the device identifier of the target vehicle ecosystem device is found, the binding certificate of the target vehicle ecosystem device is verified based on the binding certificate of the historical access device. If the verification passes, the identity authentication of the target vehicle-mounted ecosystem device is deemed successful.

[0012] In this embodiment, by automatically completing the identity verification of the target vehicle-mounted ecosystem device based on the locally maintained list of bound devices, the automatic network access of bound devices can be achieved, thereby improving the efficiency of vehicle-mounted ecosystem devices accessing the StarFlash communication network.

[0013] According to one embodiment of this application, the method further includes: If the access request message does not include the binding credential of the target vehicle ecosystem device, obtain the authentication information of the target vehicle ecosystem device; the authentication information includes at least one of user account binding information and encrypted challenge response result; Verify the authentication information of the target vehicle ecosystem device. If the verification is successful, generate a binding credential corresponding to the target vehicle ecosystem device and store the device identifier and binding credential of the target vehicle ecosystem device together in the list of bound devices. Send the binding credential corresponding to the target vehicle ecosystem device to the target vehicle ecosystem device, and determine that the identity authentication of the target vehicle ecosystem device is successful.

[0014] In this embodiment, by having the vehicle autonomously complete the full identity authentication and binding registration process and return the binding credentials to the target vehicle-mounted ecosystem device, the target vehicle-mounted ecosystem device can automatically access the StarFlash communication network when it subsequently enters the vehicle's communication range again, thereby improving the efficiency of the vehicle-mounted ecosystem device accessing the StarFlash communication network.

[0015] According to one embodiment of this application, the light-duty vehicle includes an alarm device; the method further includes: In response to the alarm information sent by the vehicle-mounted ecological device through the Star Flash communication network, an alarm command is generated and sent to the alarm device; Based on the alarm information, an abnormal event record is generated and sent to the cloud server; When a user terminal accesses the StarSpark communication network, the abnormal event record is sent to the user terminal through the StarSpark communication network.

[0016] In this embodiment, by having the vehicle respond to alarm messages from the in-vehicle ecosystem device and trigger an alarm, and by uploading abnormal event records to the cloud server, the user terminal can be informed of the occurrence of abnormal events through the cloud server even when it is not connected to the StarFlash communication network. By synchronizing the abnormal event records to the user terminal when the user terminal is connected to the StarFlash communication network, the user terminal can be informed of abnormal situations that occurred offline even when it is not communicating with the cloud server, thereby improving the safety of vehicle operation and improving the efficiency of abnormal event record synchronization.

[0017] According to one embodiment of this application, the method further includes: When the user terminal is connected to the StarFlash communication network, the status data of each of the vehicle-mounted ecological devices is sent to the user terminal through the StarFlash communication network; The system acquires the device control command sent by the user terminal through the StarSignal communication network, generates a control instruction corresponding to the device control command based on the device control command, and sends the control instruction corresponding to the device control command to each of the vehicle-mounted ecosystem devices through the StarSignal communication network.

[0018] In this embodiment, by having the vehicle send the aggregated data to the user terminal when the user terminal is connected to the StarFlash communication network, the efficiency of the user terminal in obtaining the status data of each vehicle-mounted ecological device can be improved. By receiving the device control commands sent by the user terminal, generating the corresponding control instructions and sending them to each vehicle-mounted ecological device, the efficiency of controlling the vehicle-mounted ecological devices can be improved.

[0019] Secondly, this application provides a light-duty vehicle networking device, comprising: A creation module is used to create a StarSignal communication network through the StarSignal communication module and connect multiple vehicle-mounted ecological devices to the StarSignal communication network; The acquisition module is used to acquire the status data of each of the vehicle-mounted ecological devices through the StarFlash communication network; The determination module is used to determine the operating scenario type of the light-powered vehicle based on the status data of each of the vehicle-mounted ecological devices, the status data of the Star Flash communication network, and the status data of the light-powered vehicle, and to generate control commands corresponding to each of the vehicle-mounted ecological devices based on the operating scenario type. The transmitting module is used to transmit each of the control commands to the corresponding vehicle-mounted ecological device through the StarFlash communication network.

[0020] According to the light-duty vehicle networking device of this application, a StarFlash communication network is established by the light-duty vehicle, and the vehicle itself acts as the network coordinator and the core node of the intelligent ecosystem, directly managing and controlling the on-board ecological devices in a unified manner. This enables the vehicle's intelligent ecosystem to operate independently even when the user terminal is offline. By enabling data transmission between the vehicle and the on-board ecological devices through the StarFlash communication network, the communication path between the on-board ecological devices and the light-duty vehicle can be shortened, reducing the transmission latency of status data reporting and control command issuance. By aggregating and comprehensively analyzing the status data of each on-board ecological device, the StarFlash communication network, and the light-duty vehicle, the operating scenario type of the light-duty vehicle can be determined, and control commands corresponding to each on-board ecological device can be generated based on the operating scenario type. This reduces the possibility of misjudgment caused by a single data source and mismatch between control commands and operating scenarios, thereby improving the stability of the operation of the light-duty vehicle and the on-board ecological devices.

[0021] Thirdly, this application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the light-powered vehicle networking method described in the first aspect above.

[0022] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the light-powered vehicle networking method as described in the first aspect above.

[0023] Fifthly, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the light-powered vehicle networking method as described in the first aspect above.

[0024] In a sixth aspect, this application provides a computer program product, including a computer program that, when executed by a processor, implements the light-powered vehicle networking method as described in the first aspect above.

[0025] The above-described one or more technical solutions in the embodiments of this application have at least one of the following technical effects: According to the networking method for light-duty vehicles in this application, a StarFlash communication network is established by the light-duty vehicles, with the vehicle itself acting as the network coordinator and core node of the intelligent ecosystem. This allows for unified management and control of the on-board ecosystem devices, enabling the vehicle's intelligent ecosystem to operate independently even when the user terminal is offline. By enabling data transmission between the vehicle and the on-board ecosystem devices through the StarFlash communication network, the communication path between the on-board ecosystem devices and the light-duty vehicles can be shortened, reducing the transmission latency of status data reporting and control command issuance. By aggregating and comprehensively analyzing the status data of each on-board ecosystem device, the StarFlash communication network, and the light-duty vehicles, the operating scenario type of the light-duty vehicles can be determined. Based on the operating scenario type, control commands corresponding to each on-board ecosystem device can be generated, reducing misjudgments caused by a single data source and incompatibility between control commands and operating scenarios, thereby improving the stability of the operation of the light-duty vehicles and on-board ecosystem devices.

[0026] In some embodiments, by dynamically determining the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device and allocating network resources based on the type of the target vehicle-mounted ecosystem device and the current operating scenario of the light-powered vehicle, the overall communication efficiency of the StarFlash communication network can be improved, and the resource utilization efficiency of each vehicle-mounted ecosystem device can be increased.

[0027] In some embodiments, by determining the communication priority of the target vehicle ecosystem device in real time and allocating network resources based on the communication priority of each vehicle ecosystem device, it is possible to reduce the situation where low-priority devices preempt the network resources of high-priority devices, resulting in high-priority devices being unable to communicate normally, thereby improving the operational stability and collaborative efficiency of the vehicle intelligent ecosystem in scenarios with a large number of concurrent vehicle ecosystem devices.

[0028] In some embodiments, by automatically verifying the identity of the target vehicle ecosystem device based on a locally maintained list of bound devices, the automatic network access of bound devices can be achieved, thereby improving the efficiency of vehicle ecosystem devices accessing the StarFlash communication network.

[0029] In some embodiments, by having the vehicle autonomously complete the full identity authentication and binding registration process and return the binding credentials to the target vehicle-mounted ecosystem device, the target vehicle-mounted ecosystem device can automatically access the StarFlash communication network when it subsequently re-enters the vehicle's communication range, thereby improving the efficiency of the vehicle-mounted ecosystem device accessing the StarFlash communication network.

[0030] In some embodiments, by having the vehicle respond to alarm messages from in-vehicle ecosystem devices and trigger alarms, and by uploading abnormal event records to a cloud server, the user terminal can be informed of the occurrence of abnormal events through the cloud server even when it is not connected to the StarFlash communication network. By synchronizing abnormal event records to the user terminal when the user terminal is connected to the StarFlash communication network, the user terminal can be informed of abnormal situations that occurred offline even when it is not communicating with the cloud server, thereby improving the safety of vehicle operation and improving the efficiency of abnormal event record synchronization.

[0031] In some embodiments, when the user terminal is connected to the StarFlash communication network, the vehicle sends the aggregated data to the user terminal, which can improve the efficiency of the user terminal in obtaining the status data of each vehicle-mounted ecological device. By receiving the device control command sent by the user terminal, generating the control instruction corresponding to the device control command and sending it to each vehicle-mounted ecological device, the efficiency of controlling the vehicle-mounted ecological device can be improved.

[0032] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a flowchart illustrating the method for networking light-duty vehicles provided in an embodiment of this application; Figure 2 This is a schematic diagram of the topology of the Starflash communication network provided in the embodiments of this application; Figure 3 This is one of the schematic diagrams of the networking process of light-duty vehicles provided in the embodiments of this application; Figure 4 This is a second schematic diagram of the network formation process of light-duty vehicles provided in the embodiments of this application; Figure 5 This is the third schematic diagram of the networking process of light-duty electric vehicles provided in the embodiments of this application; Figure 6 This is a schematic diagram of the structure of the light-powered vehicle networking device provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0035] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0036] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0037] The following description, in conjunction with the accompanying drawings, details the light-duty vehicle networking method, apparatus, electronic equipment, and storage medium provided in this application through specific embodiments and application scenarios.

[0038] The light-duty vehicle networking method provided in this application can be implemented by an electronic device or a functional module or entity within an electronic device capable of implementing the light-duty vehicle networking method. The electronic devices mentioned in this application include, but are not limited to, vehicle-mounted systems, ECUs (Electronic Control Units), and T-Boxes (Telematics-Boxes). The following description uses a vehicle-mounted system as an example to illustrate the light-duty vehicle networking method provided in this application.

[0039] like Figure 1 As shown, the method for networking light-powered vehicles includes steps 110, 120, 130 and 140.

[0040] In this embodiment, the light-duty vehicle includes a StarScan communication module. The StarScan communication module refers to a hardware unit equipped with a StarScan wireless communication protocol stack. The StarScan communication module can be a hardware unit integrated within the vehicle's SoC (System on Chip), or it can be a communication coprocessor externally connected to the SoC via a hardware interface. Of course, the vehicle can also be equipped with the StarScan communication module in other forms, and this embodiment does not limit this.

[0041] Step 110: Create a StarSpark communication network using the StarSpark communication module, and connect multiple vehicle-mounted ecosystem devices to the StarSpark communication network.

[0042] With the increasing intelligence of light-powered vehicles such as electric bicycles, electric motorcycles, and electric scooters, intelligent in-vehicle ecosystem devices such as smart helmets, smart locks, locators, alarms, and riding recorders are being introduced into the vehicle's intelligent ecosystem. Each in-vehicle ecosystem device needs to be connected to a wireless network to enable management and control of these devices during vehicle operation.

[0043] In related technologies, a mobile phone-centric networking model is typically adopted, where each in-vehicle ecosystem device connects to the phone via Bluetooth, and the phone then interacts with the vehicle or the cloud. However, in this architecture, communication between the vehicle and the in-vehicle ecosystem devices requires relay communication through the mobile phone, preventing the vehicle's intelligent ecosystem from operating independently. When the phone leaves the vehicle, is powered off, Bluetooth is turned off, the system is in background sleep, or the application is not activated, the original communication link is interrupted, and the vehicle and the in-vehicle ecosystem devices cannot continue to communicate, severely affecting the stability of the operation of light-duty vehicles and in-vehicle ecosystem devices.

[0044] During vehicle operation, the vehicle possesses attributes such as fixed power supply, continuous online connectivity, stable location, and strong controllability. Therefore, in this embodiment, the vehicle itself is selected as the core node of the vehicle intelligent ecosystem, responsible for establishing and maintaining the StarFlash communication network. Simultaneously, at the application layer, it serves as the logical control center, responsible for network device access management, identity authentication, policy distribution, and collaborative decision-making.

[0045] When the vehicle is powered on, unlocked, or enters a preset working state, the vehicle's infotainment system starts the StarFlash networking service and initiates the creation of a StarFlash communication network through the StarFlash communication module.

[0046] Network configuration parameters such as network identifiers, access policies, bound device lists, authentication rules, resource allocation policies, service priority policies, and device role templates can be pre-stored locally in the vehicle's infotainment system, or distributed from the cloud server to the vehicle's local storage. This allows the vehicle's infotainment system to load the locally stored network configuration parameters and complete the creation of the StarFlash communication network based on the StarFlash protocol stack.

[0047] After establishing the StarFlash communication network, the vehicle's infotainment system connects multiple in-vehicle ecosystem devices to the network. These in-vehicle ecosystem devices refer to electronic devices within the vehicle's intelligent ecosystem that possess sensing, computing, communication, and interaction capabilities. These devices can be independent of the vehicle, such as smart helmets, smart locks, and cycling recorders; or they can be integrated into the vehicle, such as locators, sensors, and alarms. This application's embodiments do not limit the specific type of device.

[0048] In this embodiment, the vehicle-mounted ecosystem device can be equipped with a StarScan communication module. After establishing the StarScan communication network, the vehicle's infotainment system can periodically broadcast beacon messages to inform surrounding vehicle-mounted ecosystem devices of the existence of the StarScan communication network, network identifier, network capabilities, types of accessible devices, remaining access capacity, and access conditions. The vehicle-mounted ecosystem device can receive the beacon messages broadcast by the vehicle's infotainment system through the StarScan communication module and send access requests to the vehicle's infotainment system. The vehicle's infotainment system can authenticate the vehicle-mounted ecosystem device according to preset authentication rules. After successful authentication, the system assigns parameters such as node address, scheduling cycle, and service channel to the vehicle-mounted ecosystem device, thereby connecting the vehicle-mounted ecosystem device to the StarScan communication network.

[0049] In some embodiments, the vehicle-mounted system can also generate and maintain an in-vehicle ecosystem device management table. The management table can record information such as device identifier, device type, binding status (bound / temporary access), access status (online / offline / dormant), permission status, current link quality, most recent communication time, business group, collaborating objects, current task status, and dormant / wake-up status of each in-vehicle ecosystem device accessed in the StarFlash communication network.

[0050] The vehicle-mounted system can use the vehicle ecosystem device management table to uniformly perform lifecycle management of each vehicle ecosystem device, including operations such as online, offline, abnormal, reconnection, replacement and deregistration.

[0051] For vehicle-mounted ecosystem devices that are already bound but are currently out of communication range, their binding records and configuration information can be retained in the vehicle-mounted ecosystem device management table so that the vehicle-mounted ecosystem device can quickly resume access when it is brought back to the vehicle.

[0052] Step 120: Obtain the status data of each vehicle-mounted ecological device through the StarFlash communication network.

[0053] Once the in-vehicle ecosystem devices are connected to the StarSpark communication network, they can communicate with the vehicle's infotainment system via the StarSpark communication network according to the assigned network parameters.

[0054] When connecting in-vehicle ecosystem devices to the StarFlash communication network, the vehicle's infotainment system and the in-vehicle ecosystem devices can negotiate and determine the data reporting frequency. Then, the in-vehicle ecosystem devices can send their own status data to the vehicle's infotainment system through the StarFlash communication network according to the negotiated data reporting frequency.

[0055] The status data of vehicle-mounted ecological devices may include the device's own operational status data, sensing data collected by the device through sensors, and data and feature information calculated by the device based on the sensing data. Of course, the status data of vehicle-mounted ecological devices may also include other types of data, which are not limited in this embodiment.

[0056] In some embodiments, the StarSpark communication network can be a StarSpark Mesh network. A mesh network is a decentralized network structure where nodes can communicate directly or relay communication through other nodes, forming a mesh topology. This gives the mesh network inherent multipath redundancy and self-healing capabilities.

[0057] like Figure 2 As shown in this embodiment, the vehicle-mounted unit can communicate directly with vehicle-mounted ecosystem devices 1, 2, and 3. When the vehicle-mounted unit needs to transmit data to vehicle-mounted ecosystem device 2, it can send the data directly to vehicle-mounted ecosystem device 2; or it can first send the data to vehicle-mounted ecosystem device 1, which will then forward it to vehicle-mounted ecosystem device 2. When vehicle-mounted ecosystem device 2 needs to transmit data to vehicle-mounted ecosystem device 3, it can first send the data to the vehicle-mounted unit, which will then forward it to vehicle-mounted ecosystem device 3; or it can directly send the data to vehicle-mounted ecosystem device 3 without needing to be forwarded by the vehicle-mounted unit.

[0058] Of course, vehicle-mounted ecological devices 2 and 3 can also serve as relay nodes for forwarding data. Vehicle-mounted ecological devices 1 and 3 can also communicate directly. Data transmission can also pass through more relay nodes. This application embodiment does not limit this.

[0059] Step 130: Based on the status data of each vehicle-mounted ecological device, the status data of the StarFlash communication network, and the status data of the light-duty vehicle, determine the operating scenario type of the light-duty vehicle, and generate control commands corresponding to each vehicle-mounted ecological device based on the operating scenario type.

[0060] In this embodiment, the vehicle-mounted system plays the role of a data aggregation hub and collaborative decision engine at the logical level in the vehicle intelligent ecosystem. It is responsible for comprehensively analyzing and making decisions based on the status data of various in-vehicle ecosystem devices, the status data of the StarFlash communication network, and the status data of the vehicle.

[0061] The status data of the StarSpeed ​​Communication Network represents its operational status. This data can include information such as signal strength and signal-to-noise ratio (SNR) representing the physical state of the channel; bandwidth and QoS (Quality of Service) representing the status of the StarSpeed ​​Communication Link; and data such as the vehicle-mounted ecosystem device management table representing the status of network nodes. The status data can be collected and statistically analyzed by the StarSpeed ​​Communication module, allowing the vehicle's infotainment system to query or report status data from the module. Alternatively, the vehicle's infotainment system can autonomously collect and record the status data. Of course, the status data can also include other types of data, and the vehicle's infotainment system can obtain this data through other methods; this embodiment does not limit the scope of this application.

[0062] Status data of light-duty vehicles characterize their operating status and can include data such as driving speed, remaining battery power, charging status, and fault information. The vehicle's infotainment system can acquire various status data of the light-duty vehicle from the vehicle's battery system, control system, and internally integrated sensors through the communication bus integrated within the vehicle.

[0063] In this embodiment of the application, the vehicle system needs to determine the operating scenario type of the light-powered vehicle based on the status data of each vehicle-mounted ecological device, the status data of the StarFlash communication network, and the status data of the light-powered vehicle.

[0064] Among them, the operating scenario type represents the operating status of the vehicle's intelligent ecosystem. Multiple operating scenario types can be predefined, and the corresponding judgment conditions for each operating scenario type can be set in the form of decision trees, state machines, etc. Then, after receiving various status data, the vehicle's infotainment system can determine the operating scenario type of the light-duty vehicle based on the predefined judgment conditions.

[0065] For example, three types of operating scenarios can be defined: parking scenario, driving scenario, and charging scenario. A parking scenario is defined when the smart lock is locked and the vehicle battery system is in a dormant state; a charging scenario is defined when the smart lock is locked and the vehicle battery system is in a charging state; and a driving scenario is defined when the smart lock is unlocked, the smart helmet is connected to the StarFlash communication network, and the vehicle battery system is in an output state.

[0066] Of course, other operating scenario types can also be set, and multiple subtypes can be divided within each operating scenario type. For example, the driving scenario can be divided into low-speed driving sub-scenario and high-speed driving sub-scenario. In addition to determining the operating scenario type through rule-based matching, other methods can also be used, such as machine learning-based methods. In addition to the status data of each vehicle-mounted ecosystem device, the status data of the StarFlash communication network, and the status data of light-duty vehicles, other data can be introduced to determine the operating scenario type, such as instructions issued by the cloud server and instructions sent by the user through the user terminal. This application embodiment does not limit this.

[0067] After determining the operating scenario type of the light-duty vehicle, control commands corresponding to each on-board ecosystem device are generated based on the operating scenario type.

[0068] Event response strategies for each type of operating scenario can be predefined. When event information is received from in-vehicle ecosystem devices, cloud servers, user terminals, etc., control commands are generated based on the event response strategy corresponding to the current operating scenario type.

[0069] For example, in a parked scenario, if the smart helmet reports that the helmet is not being worn or is not being worn correctly, a corresponding voice reminder command for the smart helmet will be generated; while in a driving scenario, if the tire pressure sensor reports abnormal pressure, a corresponding speed reduction reminder command for the smart helmet will be generated; and in a parked scenario, if both the vibration sensor and the attitude sensor report abnormal data, a corresponding enhanced protection command for the smart lock will be generated.

[0070] When conflicting data is reported from different data sources, a comprehensive decision can be made based on the priority of each data source and the content of the data reported by each data source, so as to reduce the possibility of misjudgment from a single data source.

[0071] For example, when the vehicle is parked, if the attitude sensor reports that the vehicle's attitude is normal, but the location data reported by the locator shows that the vehicle's position is changing rapidly, the data reported by the locator can be accepted first to determine that the vehicle is in an abnormal stolen state, generate the corresponding alarm command for the alarm, and send the abnormal event to the cloud server.

[0072] Of course, control commands can also be generated in other ways. In addition to the control commands corresponding to each in-vehicle ecosystem device, the vehicle system can also generate control commands corresponding to each actuator inside the light-duty vehicle based on the type of operating scenario and various status data. For example, in a parking scenario when the helmet is not worn, a start restriction command corresponding to the vehicle control system is generated; in a driving state, when the tire pressure sensor reports abnormal pressure, a deceleration command corresponding to the vehicle control system is generated; in a parking scenario when the attitude sensor reports abnormal data, audible and visual alarm commands corresponding to the electric horn and headlights are generated, etc. This application embodiment does not limit this.

[0073] Step 140: Send each control command to the corresponding vehicle-mounted ecological device through the StarFlash communication network.

[0074] After generating control commands corresponding to each in-vehicle ecosystem device, the control commands are sent to the corresponding in-vehicle devices via the StarScan communication network. The vehicle-mounted system can send control commands point-to-point to its corresponding in-vehicle ecosystem device, or it can complete data transmission through multi-hop relay paths in the StarScan Mesh network. This application embodiment does not limit this approach.

[0075] In some embodiments, control commands corresponding to each actuator inside a light-duty vehicle can be sent to the corresponding actuator via the communication bus integrated inside the vehicle; if the actuator is connected to the StarSignal communication network, the commands can also be transmitted via the StarSignal communication network. This application does not limit this.

[0076] The light-duty vehicle networking method provided in this application establishes a StarFlash communication network by the light-duty vehicle, with the vehicle itself acting as the network coordinator and core node of the intelligent ecosystem. This allows for unified management and control of onboard ecosystem devices, enabling the vehicle's intelligent ecosystem to operate independently even when the user terminal is offline. By enabling data transmission between the vehicle and onboard ecosystem devices through the StarFlash communication network, the communication path between the onboard ecosystem devices and the light-duty vehicle is shortened, reducing the transmission latency of status data reporting and control command issuance. By aggregating and comprehensively analyzing the status data of each onboard ecosystem device, the StarFlash communication network, and the vehicle, the operating scenario type of the light-duty vehicle is determined, and control commands corresponding to each onboard ecosystem device are generated based on the operating scenario type. This reduces the possibility of misjudgment or mismatch between control commands and operating scenarios caused by a single data source, thereby improving the stability of the operation of the light-duty vehicle and onboard ecosystem devices.

[0077] In some embodiments, connecting multiple in-vehicle ecosystem devices to the StarFlash communication network includes: Obtain the access request message sent by the target vehicle ecosystem device, and perform identity authentication on the target vehicle ecosystem device based on the access request message; Once identity authentication is successful, the type of the target vehicle-mounted ecosystem device is determined based on the access request message. Based on the type of the target vehicle-mounted ecosystem device, the current operating scenario of the light-duty vehicle, and the current status data of the StarFlash communication network, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined. Based on the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device, network resources are allocated to the target vehicle-mounted ecosystem device to connect it to the StarFlash communication network.

[0078] The network resources of StarScan Communication Network, such as time slots, service channels, and bandwidth, are limited. When a large number of vehicle-mounted ecosystem devices access the network concurrently, network resources need to be allocated reasonably to reduce resource waste and conflicts among vehicle-mounted ecosystem devices.

[0079] In this embodiment of the application, the vehicle-mounted system acts as the creator and maintainer of the StarFlash communication network, and is responsible for the device access management, identity authentication and network resource configuration of the StarFlash communication network.

[0080] Different types of in-vehicle ecosystem devices require different amounts of network resources. For example, tire pressure sensors need to transmit numerical tire pressure data, which consumes less bandwidth, while smart helmets need to transmit high-bandwidth audio stream data.

[0081] Meanwhile, the network resources expected to be consumed by the same in-vehicle ecosystem device vary depending on the type of operating scenario. For example, smart helmets need to transmit audio stream data with high bandwidth and low latency when driving, while they only need to report data such as their own battery level at longer intervals when charging.

[0082] Therefore, in this embodiment of the application, the vehicle system will dynamically determine the resource configuration parameters corresponding to the target vehicle ecosystem device based on the type of the target vehicle ecosystem device, the current operating scenario type of the light-duty vehicle, and the current status data of the StarFlash communication network, and allocate network resources to the target vehicle ecosystem device based on the resource configuration parameters corresponding to the target vehicle ecosystem device.

[0083] After establishing a StarFlash communication network, the vehicle's infotainment system periodically broadcasts beacon messages from the StarFlash network and receives access request messages from in-vehicle ecosystem devices based on these beacon messages. Upon receiving an access request message from a target in-vehicle ecosystem device, the system performs authentication on the target device based on the access request message.

[0084] The access request message represents the intention of the target vehicle-mounted ecosystem device to access the StarFlash communication network. It can carry information such as the device identifier, access intent identifier, and binding credentials of the target vehicle-mounted ecosystem device. The vehicle-mounted system can perform identity authentication on the target vehicle-mounted ecosystem device according to preset authentication rules based on the device identifier, binding credentials, and other information in the access request message.

[0085] Upon successful authentication, the type of the target in-vehicle ecosystem device is determined based on the access request message. The target in-vehicle device can write its type in the access request message, allowing the vehicle's infotainment system to directly parse the type from the message. Alternatively, the system can retrieve the target device's type from an in-vehicle ecosystem device lookup table based on its device identifier. Of course, other methods can also be used to determine the type of the target in-vehicle ecosystem device, and this embodiment does not limit this approach.

[0086] After determining the type of the target vehicle-mounted ecosystem device, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined based on the type of the target vehicle-mounted ecosystem device, the current operating scenario of the light-duty vehicle, and the current status data of the StarScan communication network.

[0087] Among them, the current operating scenario type of the light-duty vehicle refers to the operating scenario type of the light-duty vehicle when the identity authentication of the target vehicle-mounted ecosystem device is successful; the current status data of the StarSpark communication network refers to the status data of the StarSpark communication network when the identity authentication of the target vehicle-mounted ecosystem device is successful; the resource configuration parameters characterize the content of the network resources to be allocated to the target vehicle-mounted ecosystem device, which may include network node address, time slot or scheduling cycle, transmission priority, service channel, etc.

[0088] Based on the current status data of the StarSpark communication network, the number of currently connected devices, the type of each connected device, and the network resource occupancy status in the StarSpark communication network can be determined, as well as the currently allocable network resources in the StarSpark communication network. Based on the current operating scenario type of the light-duty vehicle and the type of the target vehicle-mounted ecosystem device, the network resources currently expected to be consumed by the target vehicle-mounted ecosystem device can be determined, and the network resources allocated to the target vehicle-mounted ecosystem device can be determined from the currently allocable network resources in the StarSpark communication network, thereby determining the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device.

[0089] After determining the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device, the network configuration parameters of the StarSpark communication module can be modified based on these parameters. This allows the allocation of network resources such as network node addresses, time slots, transmission priorities, and service channels to the target vehicle-mounted ecosystem device. The resource configuration parameters can then be returned to the target vehicle-mounted ecosystem device, enabling it to configure its own StarSpark communication module accordingly and transmit data according to the relevant strategies in the resource configuration parameters, thereby connecting the target vehicle-mounted ecosystem device to the StarSpark communication network.

[0090] After connecting the target vehicle-mounted ecosystem device to the StarFlash communication network, the vehicle-mounted ecosystem device management table can be updated to facilitate lifecycle management of the target vehicle-mounted ecosystem device.

[0091] In some embodiments, in addition to network resource configuration parameters, other network parameters can be assigned to the target vehicle-mounted ecosystem device, such as network access level, communication encryption level, and data reporting frequency. Besides network-related parameters, other types of parameters can also be assigned to the target vehicle-mounted ecosystem device, such as sleep / wake-up policies; however, this application embodiment does not limit this.

[0092] In this embodiment, by dynamically determining the resource configuration parameters corresponding to the target vehicle-mounted ecological device and allocating network resources based on the type of the target vehicle-mounted ecological device and the current operating scenario of the light-powered vehicle, the overall communication efficiency of the StarFlash communication network can be improved, and the resource utilization efficiency of each vehicle-mounted ecological device can be increased.

[0093] In some embodiments, resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined based on the type of the target vehicle-mounted ecosystem device, the current operating scenario type of the light-duty vehicle, and the current status data of the StarSignal communication network, including: Based on the type of the target vehicle-mounted ecosystem device and the current operating scenario of the light-duty vehicle, determine the communication priority corresponding to the target vehicle-mounted ecosystem device; Based on the communication priority of each vehicle-mounted ecosystem device and the current status data of the StarFlash communication network, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined.

[0094] When a large number of vehicle-mounted ecosystem devices connect concurrently, allocating network resources solely based on the type and resource requirements of the devices may result in low-priority devices preempting network resources from high-priority devices, causing high-priority devices to be unable to communicate normally.

[0095] Therefore, in this embodiment, a priority scheduling mechanism is introduced to allocate network resources based on the communication priority of each vehicle-mounted ecosystem device.

[0096] The communication priorities for different types of in-vehicle ecosystem devices under various operating scenarios can be pre-defined and stored locally in the vehicle's infotainment system in the form of a mapping table. For example, in a parking scenario, high priority can be assigned to smart locks, attitude sensors, and alarms; medium priority to locators and tire pressure sensors; and low priority to smart helmets and cycling recorders. In a driving scenario, high priority can be assigned to smart helmets, cycling recorders, and locators; medium priority to tire pressure sensors and attitude sensors; and low priority to smart locks and alarms. Then, for a target in-vehicle ecosystem device, the corresponding communication priority can be obtained by retrieving the mapping table based on the type of the target device and the current operating scenario of the light-duty vehicle.

[0097] After determining the communication priority of the target vehicle-mounted ecosystem device, the resource configuration parameters for that device are determined based on its communication priority and the current status data of the StarSpark communication network. For example, if the target device has a high communication priority, its network resource requirements will be prioritized. If the available network resources in the StarSpark communication network are insufficient to meet the requirements, network resources allocated to vehicle-mounted ecosystem devices with low communication priorities can be reduced; for example, the data reporting frequency of low-priority devices can be decreased.

[0098] In some embodiments, when the number of access devices in the StarFlash communication network is close to the upper limit, if multiple access request messages from vehicle-mounted ecosystem devices are received simultaneously, access control can be performed based on the communication priority of each vehicle-mounted ecosystem device to prioritize the access of vehicle-mounted ecosystem devices with higher communication priority.

[0099] In some embodiments, in addition to adjusting the allocation of network resources when a new device is connected to the StarSignal communication network, the allocation of network resources can also be dynamically adjusted in real time when the operating scenario type of light-duty vehicles changes, the operating status of the StarSignal communication network changes, or the operating status of the vehicle-mounted ecosystem devices already connected to the StarSignal communication network changes.

[0100] In this embodiment, by determining the communication priority of the target vehicle ecosystem device in real time and allocating network resources based on the communication priority of each vehicle ecosystem device, it is possible to reduce the situation where low-priority devices preempt the network resources of high-priority devices, resulting in high-priority devices being unable to communicate normally, thereby improving the operational stability and collaborative efficiency of the vehicle intelligent ecosystem in scenarios with a large number of concurrent vehicle ecosystem devices.

[0101] In some embodiments, identity authentication is performed on the target in-vehicle ecosystem device based on the access request message, including: If the access request message includes the device identifier and binding credentials of the target vehicle ecosystem device, the list of bound devices is retrieved based on the device identifier of the target vehicle ecosystem device; the list of bound devices stores multiple sets of device identifiers and binding credentials of historical access devices. If a historical access device that matches the device identifier of the target vehicle ecosystem device is found, the binding certificate of the target vehicle ecosystem device is verified based on the binding certificate of the historical access device. If the verification passes, the identity authentication of the target vehicle-mounted ecosystem device is deemed successful.

[0102] In this embodiment, the vehicle-mounted system, acting as the maintainer of the StarFlash communication network, maintains a list of bound devices locally. This list stores the device identifiers and binding credentials of multiple historically accessed devices.

[0103] A binding credential is a digital certificate representing a device's legitimate permission to access the network, and can take the form of a key, digital certificate, encrypted string, etc. When an in-vehicle ecosystem device first accesses the StarFlash communication network, the vehicle-mounted system can generate a binding credential corresponding to the in-vehicle ecosystem device through out-of-band authentication, key negotiation, and other mechanisms, and then associate the device identifier of the in-vehicle ecosystem device with the binding credential and store it in the bound device list. Of course, the vehicle-mounted system can also construct the bound device list through other methods, such as obtaining the bound device list from a cloud server or user terminal and storing it locally, etc., and this application embodiment does not limit this approach.

[0104] The in-vehicle ecosystem device can locally maintain a binding credential record table that associates and stores network identifiers and binding credentials. Upon initial access to the StarSignal communication network, it associates the binding credential negotiated with the vehicle's infotainment system with the network identifier of the StarSignal communication network and stores it in the binding credential record table. When the in-vehicle ecosystem device receives a beacon message broadcast by the vehicle's infotainment system, it can search the binding credential record table for the network identifier carried in the beacon message to see if a binding credential corresponding to that network identifier exists. If it does, it indicates that the in-vehicle ecosystem device has previously accessed the StarSignal communication network corresponding to that network identifier. In this case, the in-vehicle ecosystem device can send an access request message carrying its own device identifier and binding credential to the vehicle's infotainment system.

[0105] For in-vehicle infotainment systems, such as Figure 3 As shown, upon receiving an access request message from the target vehicle ecosystem device, the system first parses the message and checks whether it includes the device identifier and binding credentials of the target vehicle ecosystem device. If the message includes the device identifier and binding credentials, the system retrieves the list of bound devices based on the device identifier.

[0106] If a historical access device matching the device identifier of the target vehicle ecosystem device is found in the list of bound devices, the binding credentials of the target vehicle ecosystem device are verified based on the binding credentials of the retrieved historical access device. Verification can be performed through character-by-character comparison, key verification, digital signature verification, etc., and this application embodiment does not limit the scope of the verification.

[0107] If the verification passes, it indicates that the target vehicle-mounted ecosystem device currently has the legal right to access the StarSpark communication network. Then, the resource allocation stage begins, which identifies the type of the target vehicle-mounted ecosystem device, allocates network resources to the target vehicle-mounted ecosystem device, and connects it to the StarSpark communication network.

[0108] If no historically accessed device matching the device identifier of the target vehicle ecosystem device is found in the list of bound devices, or if the binding credential verification of the target vehicle ecosystem device fails, it indicates that the target vehicle ecosystem device may not have access permissions, or its access permissions may have expired. In this case, the access request of the target vehicle ecosystem device will be rejected. A rejection message indicating a refusal of access can be returned to the target vehicle ecosystem device so that the target vehicle ecosystem device can retry or re-initiate the initial binding access request.

[0109] In this embodiment, by automatically completing the identity verification of the target vehicle-mounted ecosystem device based on the locally maintained list of bound devices, the automatic network access of bound devices can be achieved, thereby improving the efficiency of vehicle-mounted ecosystem devices accessing the StarFlash communication network.

[0110] In some embodiments, the method further includes: If the access request message does not include the binding credentials of the target vehicle ecosystem device, obtain the authentication information of the target vehicle ecosystem device; the authentication information includes at least one of the user account binding information and the encrypted challenge response result; Verify the authentication information of the target vehicle ecosystem device. If the verification is successful, generate the binding certificate corresponding to the target vehicle ecosystem device and store the device identifier and binding certificate of the target vehicle ecosystem device in the list of bound devices. Send the binding certificate corresponding to the target vehicle ecosystem device to the target vehicle ecosystem device, and determine that the identity authentication of the target vehicle ecosystem device is successful.

[0111] If the target vehicle ecosystem device has not been connected to the StarSpark communication network before, or if the binding certificate of the target vehicle ecosystem device has expired, and the target vehicle ecosystem device does not have a valid binding certificate, then when the target vehicle ecosystem device wants to connect to the StarSpark communication network, it can initiate an access request message that does not include the binding certificate.

[0112] like Figure 3 As shown, when the vehicle system receives the access request message sent by the target vehicle ecosystem device, but fails to parse the binding credential from the access request message, it enters the binding registration process to obtain the authentication information of the target vehicle ecosystem device and verify the authentication information of the target vehicle ecosystem device.

[0113] In this embodiment of the application, the authentication information includes at least one of the user account binding information and the encrypted challenge response result.

[0114] The user account binding information represents the identity information of the owner of the target in-vehicle ecosystem device. When the target in-vehicle ecosystem device is first started, the user connects to the device via a user terminal, generates user account binding information based on the user account and the device identifier of the target in-vehicle ecosystem device, and writes the user account binding information to the local storage of the target in-vehicle ecosystem device. When the target in-vehicle ecosystem device initiates an access request to the vehicle's infotainment system, it can write the user account binding information into the access request message and send it to the vehicle's infotainment system. The vehicle's infotainment system can check whether the user account in the user account binding information matches the user account bound to the vehicle's own system, and can also request verification of the correctness of the user account binding information from the cloud server. If both local and cloud verifications pass, the user account binding information is deemed to have passed verification.

[0115] When the vehicle's infotainment system performs identity authentication, it can generate a random string, encrypt it into ciphertext using a key stored locally at the factory, and send the ciphertext to the target in-vehicle ecosystem device as an encryption challenge. The target in-vehicle ecosystem device can decrypt the ciphertext using a key stored locally at the factory and return the decrypted string as the encryption challenge response to the vehicle's infotainment system. The vehicle's infotainment system can then check whether the string returned by the target in-vehicle ecosystem device matches the random string it generated. If they match, the encryption challenge response is considered verified.

[0116] Of course, other methods can also be used to verify the authentication information; the authentication information may also include other types of information, such as vehicle binding information, manufacturer information, security credentials, etc., which are not limited in this application embodiment.

[0117] If all authentication information passes verification, the authentication information of the target vehicle-mounted ecosystem device is deemed to have passed verification. Upon successful verification, a binding credential corresponding to the target vehicle-mounted ecosystem device can be generated through methods such as key negotiation. The device identifier of the target vehicle-mounted ecosystem device and the binding credential are then associated and stored in the list of bound devices. The binding credential corresponding to the target vehicle-mounted ecosystem device is sent to the target vehicle-mounted ecosystem device, and the identity authentication of the target vehicle-mounted ecosystem device is deemed successful, thus initiating the network resource allocation process.

[0118] When the target vehicle ecosystem device re-enters the vehicle's communication range in the future, it can send an access request message carrying the binding credential generated this time to the vehicle's system. If the vehicle's system verifies the binding credential, it can skip the binding registration process and automatically access the StarFlash communication network.

[0119] In this embodiment, by having the vehicle autonomously complete the full identity authentication and binding registration process and return the binding credentials to the target vehicle-mounted ecosystem device, the target vehicle-mounted ecosystem device can automatically access the StarFlash communication network when it subsequently enters the vehicle's communication range again, thereby improving the efficiency of the vehicle-mounted ecosystem device accessing the StarFlash communication network.

[0120] In some embodiments, the vehicle includes an alarm device; the method further includes: In response to alarm information sent by in-vehicle ecosystem devices through the StarFlash communication network, an alarm command is generated and sent to the alarm device; Based on the alarm information, an abnormal event record is generated and sent to the cloud server; When a user terminal is connected to the StarScan communication network, abnormal event records are sent to the user terminal through the StarScan communication network.

[0121] In this embodiment, the user terminal is downgraded to a regular node rather than a core node. For example... Figure 4 As shown, when a user terminal enters the vehicle-to-vehicle communication range and meets the authentication conditions, it is allowed to join the StarFlash communication network as a regular node and communicate with the vehicle-to-vehicle system through the StarFlash communication network to view the device status, remotely control the device, or serve as an optional auxiliary network channel.

[0122] During vehicle operation, the vehicle's infotainment system remains online as the maintainer of the StarFlash communication network. Even when the user terminal leaves the communication range of the infotainment system, experiences a power outage, or suffers an abnormal disconnection, the infotainment system can still communicate with various in-vehicle ecosystem devices through the StarFlash communication network, thereby maintaining the normal operation of the vehicle's intelligent ecosystem.

[0123] During vehicle operation, if the vehicle system receives alarm information sent by in-vehicle ecosystem devices through the StarFlash communication network, such as alarm information sent by the vibration sensor when it detects abnormal vehicle displacement in a parking scenario, alarm information sent by the tire pressure sensor when it detects abnormal tire pressure in a driving scenario, or alarm information sent by the temperature sensor when it detects abnormal battery temperature in a charging scenario, then an alarm command corresponding to the alarm information will be generated.

[0124] After generating an alarm command, the command is sent to the alarm device. The alarm device refers to a hardware unit capable of sending an alarm to the outside world via sound, light, or other means. The alarm device can be a device integrated inside a light-duty vehicle and communicating with the vehicle's infotainment system via an onboard communication bus, such as an electric horn or headlights. Alternatively, it can be an onboard ecosystem device connected to a satellite communication network, such as a smart alarm. The vehicle's infotainment system can then determine one or more target alarm devices from among the available alarm devices based on the alarm information content. Depending on the type of the target alarm device, it can select either the onboard communication bus or the satellite communication network to send the alarm command to the target alarm device, causing it to trigger an alarm.

[0125] Simultaneously, the vehicle's infotainment system generates anomaly event logs based on alarm information. These logs can include information such as the content of the anomaly, the source in-vehicle ecosystem device, and the time of occurrence. After generating the anomaly event logs, the system can store them in its local logs.

[0126] In this embodiment, the vehicle-mounted infotainment system can be equipped with 4G / 5G cellular network communication modules, WLAN (Wireless Local Area Network) communication modules, and other types of communication modules, maintaining a connection with the cloud server via cellular networks or WLAN. After generating an abnormal event record, the vehicle-mounted system can send the record to the cloud server via cellular network or WLAN. The cloud server can then send the abnormal event record uploaded by the vehicle-mounted system to the user terminal via cellular network or WLAN, informing the user of the occurrence of the abnormal event.

[0127] When the user terminal re-enters the vehicle's communication range and connects to the StarFlash communication network, abnormal event records are sent to the user terminal via the StarFlash communication network. The vehicle's system can synchronously send all daily event records from the local logs during the user terminal's offline period to the user terminal, enabling the user terminal to be aware of any abnormal situations that occurred during the offline period without communicating with the cloud server.

[0128] In this embodiment, by having the vehicle respond to alarm messages from the in-vehicle ecosystem device and trigger an alarm, and by uploading abnormal event records to the cloud server, the user terminal can be informed of the occurrence of abnormal events through the cloud server even when it is not connected to the StarFlash communication network. By synchronizing the abnormal event records to the user terminal when the user terminal is connected to the StarFlash communication network, the user terminal can be informed of abnormal situations that occurred offline even when it is not communicating with the cloud server, thereby improving the safety of vehicle operation and improving the efficiency of abnormal event record synchronization.

[0129] In some embodiments, the method further includes: When the user terminal is connected to the StarFlash communication network, the status data of each vehicle-mounted ecosystem device is sent to the user terminal through the StarFlash communication network. The system acquires device control commands sent by user terminals through the StarSignal communication network, generates corresponding control instructions based on the device control commands, and sends the corresponding control instructions to various vehicle-mounted ecosystem devices through the StarSignal communication network.

[0130] In this embodiment of the application, when the user terminal is connected to the StarFlash communication network, the vehicle-mounted system can synchronously send the aggregated status data of each in-vehicle ecosystem device to the user terminal through the StarFlash communication network, without the user terminal needing to communicate with each in-vehicle ecosystem device separately and obtain data, or obtain data from the cloud server.

[0131] Meanwhile, when the user terminal is connected to the StarFlash communication network, the user can also send device control commands, such as unlock commands, to the vehicle's infotainment system via the user terminal. Upon receiving the device control command, the vehicle's infotainment system generates a corresponding control instruction based on the command and sends this instruction to various in-vehicle ecosystem devices via the StarFlash communication network. For example, based on the unlock command, an unlock instruction corresponding to the smart lock is generated and sent to the smart lock; the smart lock can then respond to the unlock instruction and perform an unlocking operation, thereby achieving remote unlocking.

[0132] Of course, in addition to device control commands for in-vehicle ecosystem devices, users can also send control commands to actuators integrated within the vehicle via the user terminal, such as start and shut-down commands. The vehicle's infotainment system can generate corresponding control instructions and send them to the corresponding actuators via the internal communication bus. Besides sending device control commands via the StarFlash communication network, if the user terminal is not connected to the StarFlash communication network, the user terminal can also send device control commands to a cloud server, which will then distribute them to the vehicle's infotainment system. The vehicle's infotainment system can then respond accordingly based on the device control commands distributed by the cloud server. This application embodiment does not limit this approach.

[0133] In this embodiment, by having the vehicle send the aggregated data to the user terminal when the user terminal is connected to the StarFlash communication network, the efficiency of the user terminal in obtaining the status data of each vehicle-mounted ecological device can be improved. By receiving the device control commands sent by the user terminal, generating the corresponding control instructions and sending them to each vehicle-mounted ecological device, the efficiency of controlling the vehicle-mounted ecological devices can be improved.

[0134] The following scenario example illustrates the light-duty vehicle networking method provided in this application. For example... Figure 5 As shown in this scenario example, when a light-duty vehicle is powered on, unlocked, or enters a preset working state, the vehicle's infotainment system starts the StarNet service, creates a StarNet communication network through the StarNet communication module, and periodically broadcasts beacon messages.

[0135] When a user brings a target in-vehicle ecosystem device into the vehicle's communication range, the target device responds to a beacon message by sending an access request message to the vehicle's infotainment system. Upon receiving the access request message, the vehicle's infotainment system performs authentication on the target device. After successful authentication, the system determines the device's type. Based on the device's type and the current operating scenario of the light-duty vehicle, the system determines the device's communication priority. Furthermore, based on the communication priorities of each device and the current status data of the StarSignal communication network, the system determines the resource configuration parameters for each target device and allocates network resources to connect it to the StarSignal communication network.

[0136] During vehicle operation, the vehicle's infotainment system continuously acquires status data from various onboard ecosystem devices via the StarSignal communication network, and also obtains vehicle status data and StarSignal communication network status data via the vehicle communication bus. Based on the status data of each onboard ecosystem device, the StarSignal communication network, and the light-duty vehicle, the system dynamically determines the operating scenario type of the light-duty vehicle. Based on the operating scenario type, it generates control commands corresponding to each onboard ecosystem device and sends them to the corresponding onboard ecosystem device via the StarSignal communication network.

[0137] When the vehicle's infotainment system receives alarm information from the in-vehicle ecosystem devices via the StarFlash communication network, it generates an alarm command and sends the alarm command to the alarm device to trigger the alarm. At the same time, based on the alarm information, it generates an abnormal event record and sends the abnormal event record to the cloud server.

[0138] When the user terminal enters the vehicle-mounted communication range and connects to the StarFlash communication network, the vehicle-mounted system synchronizes the abnormal event records of the user terminal during its offline period to the user terminal via the StarFlash communication network. During vehicle operation, it continuously sends the status data of each in-vehicle ecosystem device it aggregates to the user terminal. At the same time, it obtains the device control commands sent by the user terminal through the StarFlash communication network, generates the corresponding control instructions, and sends the corresponding control instructions to each in-vehicle ecosystem device through the StarFlash communication network to realize remote control of the in-vehicle ecosystem device.

[0139] When the user terminal is offline, the vehicle's infotainment system maintains a communication connection with the cloud server through its built-in cellular network communication module and remains online as the maintainer of the StarFlash communication network. It communicates with various in-vehicle ecosystem devices through the StarFlash communication network to maintain the normal operation of the vehicle's intelligent ecosystem.

[0140] The light-duty vehicle networking method provided in this application can be implemented by a light-duty vehicle networking device. This application uses a light-duty vehicle networking device to implement the light-duty vehicle networking method as an example to illustrate the light-duty vehicle networking device provided in this application.

[0141] This application also provides a networking device for light-duty vehicles.

[0142] like Figure 6 As shown, the light-powered vehicle networking device includes: Create module 610, which is used to create a StarSignal communication network through the StarSignal communication module and connect multiple vehicle-mounted ecosystem devices to the StarSignal communication network; The acquisition module 620 is used to acquire the status data of each vehicle-mounted ecological device through the StarFlash communication network; The determination module 630 is used to determine the operating scenario type of the light-powered vehicle based on the status data of each vehicle-mounted ecological device, the status data of the Star Flash communication network, and the status data of the light-powered vehicle, and to generate control commands corresponding to each vehicle-mounted ecological device based on the operating scenario type. The transmitting module 640 is used to send each control command to the corresponding vehicle-mounted ecological device via the StarFlash communication network.

[0143] According to the light-duty vehicle networking device of this application, a StarFlash communication network is established by the light-duty vehicle, with the vehicle itself acting as the network coordinator and core node of the intelligent ecosystem. This allows for unified management and control of the on-board ecosystem devices, enabling the vehicle's intelligent ecosystem to operate independently even when the user terminal is offline. By enabling data transmission between the vehicle and the on-board ecosystem devices through the StarFlash communication network, the communication path between the on-board ecosystem devices and the light-duty vehicle can be shortened, reducing the transmission latency of status data reporting and control command issuance. By aggregating and comprehensively analyzing the status data of each on-board ecosystem device, the StarFlash communication network, and the vehicle, the operating scenario type of the light-duty vehicle can be determined, and control commands corresponding to each on-board ecosystem device can be generated based on the operating scenario type. This reduces the possibility of misjudgment caused by a single data source and mismatch between control commands and operating scenarios, thereby improving the stability of the operation of the light-duty vehicle and the on-board ecosystem devices.

[0144] In some embodiments, creation module 610 is further configured to: Obtain the access request message sent by the target vehicle ecosystem device, and perform identity authentication on the target vehicle ecosystem device based on the access request message; Once identity authentication is successful, the type of the target vehicle-mounted ecosystem device is determined based on the access request message. Based on the type of the target vehicle-mounted ecosystem device, the current operating scenario of the light-duty vehicle, and the current status data of the StarFlash communication network, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined. Based on the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device, network resources are allocated to the target vehicle-mounted ecosystem device to connect it to the StarFlash communication network.

[0145] In some embodiments, creation module 610 is further configured to: Based on the type of the target vehicle-mounted ecosystem device and the current operating scenario of the light-duty vehicle, determine the communication priority corresponding to the target vehicle-mounted ecosystem device; Based on the communication priority of each vehicle-mounted ecosystem device and the current status data of the StarFlash communication network, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined.

[0146] In some embodiments, creation module 610 is further configured to: If the access request message includes the device identifier and binding credentials of the target vehicle ecosystem device, the list of bound devices is retrieved based on the device identifier of the target vehicle ecosystem device; the list of bound devices stores multiple sets of device identifiers and binding credentials of historical access devices. If a historical access device that matches the device identifier of the target vehicle ecosystem device is found, the binding certificate of the target vehicle ecosystem device is verified based on the binding certificate of the historical access device. If the verification passes, the identity authentication of the target vehicle-mounted ecosystem device is deemed successful.

[0147] In some embodiments, creation module 610 is further configured to: If the access request message does not include the binding credentials of the target vehicle ecosystem device, obtain the authentication information of the target vehicle ecosystem device; the authentication information includes at least one of the user account binding information and the encrypted challenge response result; Verify the authentication information of the target vehicle ecosystem device. If the verification is successful, generate the binding certificate corresponding to the target vehicle ecosystem device and store the device identifier and binding certificate of the target vehicle ecosystem device in the list of bound devices. Send the binding certificate corresponding to the target vehicle ecosystem device to the target vehicle ecosystem device, and determine that the identity authentication of the target vehicle ecosystem device is successful.

[0148] In some embodiments, the light-powered vehicle networking device further includes an alarm module for: In response to alarm information sent by in-vehicle ecosystem devices through the StarFlash communication network, an alarm command is generated and sent to the alarm device; Based on the alarm information, an abnormal event record is generated and sent to the cloud server; When a user terminal is connected to the StarScan communication network, abnormal event records are sent to the user terminal through the StarScan communication network.

[0149] In some embodiments, the alarm module is further configured to: When the user terminal is connected to the StarFlash communication network, the status data of each vehicle-mounted ecosystem device is sent to the user terminal through the StarFlash communication network. The system acquires device control commands sent by user terminals through the StarSignal communication network, generates corresponding control instructions based on the device control commands, and sends the corresponding control instructions to various vehicle-mounted ecosystem devices through the StarSignal communication network.

[0150] The light-duty vehicle networking device in this application embodiment can be an electronic device or a component of an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the specific devices.

[0151] The light-duty vehicle networking device in this application embodiment can be a device with an operating system. This operating system can be a Microsoft (Windows) operating system, an Android operating system, an iOS operating system, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0152] In some embodiments, such as Figure 7 As shown, this application embodiment also provides an electronic device 700, including a processor 701, a memory 702, and a computer program stored in the memory 702 and executable on the processor 701. When the program is executed by the processor 701, it implements the various processes of the above-described light-powered vehicle networking method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0153] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.

[0154] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described light-powered vehicle networking method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here.

[0155] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0156] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method for networking light-powered vehicles.

[0157] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0158] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described light-powered vehicle networking method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0159] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0160] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0161] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0162] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0163] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0164] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A method for networking light-duty electric vehicles, characterized in that, The light-powered vehicle includes a star-flash communication module; the method includes: The StarSpark communication module is used to create a StarSpark communication network and connect multiple vehicle-mounted ecosystem devices to the StarSpark communication network. The status data of each of the vehicle-mounted ecological devices is obtained through the StarFlash communication network. Based on the status data of each of the vehicle-mounted ecological devices, the status data of the Star Flash communication network, and the status data of the light-duty electric vehicle, the operating scenario type of the light-duty electric vehicle is determined, and based on the operating scenario type, control commands corresponding to each of the vehicle-mounted ecological devices are generated. The control commands are sent to the corresponding vehicle-mounted ecological devices via the StarFlash communication network.

2. The method according to claim 1, characterized in that, The process of connecting multiple vehicle-mounted ecological devices to the StarFlash communication network includes: Obtain the access request message sent by the target vehicle ecosystem device, and perform identity authentication on the target vehicle ecosystem device based on the access request message; If the identity authentication is successful, the type of the target vehicle-mounted ecosystem device is determined based on the access request message, and the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined based on the type of the target vehicle-mounted ecosystem device, the current operating scenario type of the light-duty vehicle, and the current status data of the StarFlash communication network. Based on the resource configuration parameters corresponding to the target vehicle-mounted ecological device, network resources are allocated to the target vehicle-mounted ecological device to connect it to the StarFlash communication network.

3. The method according to claim 2, characterized in that, The process of determining the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device based on the type of the target vehicle-mounted ecosystem device, the current operating scenario type of the light-duty vehicle, and the current status data of the StarSignal communication network includes: Based on the type of the target vehicle-mounted ecological device and the current operating scenario of the light-powered vehicle, the communication priority corresponding to the target vehicle-mounted ecological device is determined; Based on the communication priority of each of the vehicle-mounted ecosystem devices and the current status data of the StarFlash communication network, the resource configuration parameters corresponding to the target vehicle-mounted ecosystem device are determined.

4. The method according to claim 2, characterized in that, The step of performing identity authentication on the target vehicle-mounted ecosystem device based on the access request message includes: If the access request message includes the device identifier and binding credential of the target vehicle ecosystem device, a list of bound devices is retrieved based on the device identifier of the target vehicle ecosystem device; the list of bound devices stores multiple sets of device identifiers and binding credentials of historical access devices. If a historical access device matching the device identifier of the target vehicle ecosystem device is found, the binding certificate of the target vehicle ecosystem device is verified based on the binding certificate of the historical access device. If the verification passes, the identity authentication of the target vehicle-mounted ecosystem device is deemed successful.

5. The method according to claim 4, characterized in that, The method further includes: If the access request message does not include the binding credential of the target vehicle ecosystem device, obtain the authentication information of the target vehicle ecosystem device; the authentication information includes at least one of user account binding information and encrypted challenge response result; Verify the authentication information of the target vehicle ecosystem device. If the verification is successful, generate a binding credential corresponding to the target vehicle ecosystem device and store the device identifier and binding credential of the target vehicle ecosystem device together in the list of bound devices. Send the binding credential corresponding to the target vehicle ecosystem device to the target vehicle ecosystem device, and determine that the identity authentication of the target vehicle ecosystem device is successful.

6. The method according to claim 1, characterized in that, The light-powered vehicle includes an alarm device; the method further includes: In response to the alarm information sent by the vehicle-mounted ecological device through the Star Flash communication network, an alarm command is generated and sent to the alarm device; Based on the alarm information, an abnormal event record is generated and sent to the cloud server; When a user terminal accesses the StarSpark communication network, the abnormal event record is sent to the user terminal through the StarSpark communication network.

7. The method according to claim 6, characterized in that, The method further includes: When the user terminal is connected to the StarFlash communication network, the status data of each of the vehicle-mounted ecological devices is sent to the user terminal through the StarFlash communication network; The system acquires the device control command sent by the user terminal through the StarSignal communication network, generates a control instruction corresponding to the device control command based on the device control command, and sends the control instruction corresponding to the device control command to each of the vehicle-mounted ecosystem devices through the StarSignal communication network.

8. A networking device for light-duty electric vehicles, characterized in that, include: A creation module is used to create a StarSignal communication network through the StarSignal communication module and connect multiple vehicle-mounted ecological devices to the StarSignal communication network; The acquisition module is used to acquire the status data of each of the vehicle-mounted ecological devices through the StarFlash communication network; The determination module is used to determine the operating scenario type of the light-powered vehicle based on the status data of each of the vehicle-mounted ecological devices, the status data of the Star Flash communication network, and the status data of the light-powered vehicle, and to generate control commands corresponding to each of the vehicle-mounted ecological devices based on the operating scenario type. The transmitting module is used to transmit each of the control commands to the corresponding vehicle-mounted ecological device through the StarFlash communication network.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the light-powered vehicle networking method as described in any one of claims 1-7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the light-powered vehicle networking method as described in any one of claims 1-7.