CN116319852A - APP and cabin system platform docking method - Google Patents
APP and cabin system platform docking method Download PDFInfo
- Publication number
- CN116319852A CN116319852A CN202310029306.9A CN202310029306A CN116319852A CN 116319852 A CN116319852 A CN 116319852A CN 202310029306 A CN202310029306 A CN 202310029306A CN 116319852 A CN116319852 A CN 116319852A
- Authority
- CN
- China
- Prior art keywords
- instruction
- cabin system
- information
- system platform
- vehicle control
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003032 molecular docking Methods 0.000 title claims abstract description 50
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000000875 corresponding effect Effects 0.000 claims abstract description 43
- 238000012544 monitoring process Methods 0.000 claims abstract description 31
- 238000004891 communication Methods 0.000 claims abstract description 19
- 239000011230 binding agent Substances 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000011161 development Methods 0.000 description 5
- 101000711846 Homo sapiens Transcription factor SOX-9 Proteins 0.000 description 3
- 102100034204 Transcription factor SOX-9 Human genes 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to the technical field of intelligent cabins, in particular to an APP and cabin system platform docking method, which comprises the following steps: determining a target event standard and an information query interface standard, based on the information query interface standard, docking a plurality of cabin system platforms, receiving a vehicle control instruction, an information query instruction and/or a monitoring instruction sent by a preset mobile terminal based on a preset middleware SDK, and simultaneously, based on the target event standard, respectively sending the determined vehicle control instruction, the determined information query instruction and/or the determined monitoring instruction to the corresponding cabin system platform so as to execute corresponding actions through the corresponding cabin system platform. Therefore, the problems that in the related art, different docking needs to be carried out on different cabin systems by using a method for respectively docking, so that docking workload and debugging difficulty are increased, and communication cost is increased are solved.
Description
Technical Field
The application relates to the technical field of intelligent cabins, in particular to a docking method of APP (application) and a cabin system platform.
Background
Along with the rapid development of global Internet of vehicles and intelligent cabin technology, cabin ecological APP is also gradually enriched, matured and perfected, and APP for improving driving experience is also gradually intelligent, wherein the main thing is to monitor and control vehicle parts through a certain algorithm, so that the APP needs to be connected with a vehicle control system platform, and the purpose of controlling vehicles is achieved by using a vehicle control interface provided by the APP.
In the related art, a mode of an SDK (Software Development Kit ) is mainly adopted to externally provide a vehicle control interface, and APP is developed based on the SDK so as to realize docking of the APP and a cabin system.
However, the interface is provided only by the SDK, so that different docking needs to be performed on the APP which needs to be compatible with various cabin systems, thus causing large docking workload, large debugging difficulty and improving communication cost.
Disclosure of Invention
The application provides a docking method of an APP and a cabin system platform, which aims to solve the problems that in the related art, different docking needs to be performed on different cabin systems by the docking method, so that docking workload and debugging difficulty are increased, and meanwhile, communication cost is increased.
The application provides an APP and cabin system platform docking method, which comprises the following steps:
determining a target event standard and an information query interface standard;
based on the information inquiry interface standard, a plurality of cabin system platforms are connected, and a vehicle control instruction, an information inquiry instruction and/or a monitoring instruction sent by a preset mobile terminal based on a preset middleware SDK are received; and
and determining a cabin system platform corresponding to the vehicle control instruction, the information inquiry instruction and/or the monitoring instruction based on the target event standard, and respectively sending the vehicle control instruction, the information inquiry instruction and/or the monitoring instruction to the corresponding cabin system platform so as to execute corresponding actions through the corresponding cabin system platform.
According to one embodiment of the present application, the determining the target event criteria and the information query interface criteria includes:
determining at least one event group, wherein the event group comprises a vehicle control event group, a vehicle attribute information event group and a vehicle state information event group;
numbering at least one target event in each event group to obtain the target event standard.
According to one embodiment of the present application, before docking the multiple cabin system platforms based on the information query interface standard and receiving a vehicle control instruction, an information query instruction and/or a monitoring instruction sent by a preset mobile terminal based on the preset middleware SDK, the method further includes:
according to a first preset starting strategy, starting a middleware service, and calling a vehicle control interface while starting the middleware service;
and starting a preset component in the middleware service according to a second preset starting strategy, and connecting with the preset mobile terminal through a binder communication mechanism.
According to an embodiment of the present application, the docking method of the APP and the cabin system platform further includes:
judging whether a cabin system platform is newly added to the current vehicle;
and if the cabin system platform is newly added to the current vehicle, docking the cabin system platform is directly based on the information query interface standard.
According to one embodiment of the present application, after the vehicle control command, the information query command and/or the monitoring command are respectively sent to the corresponding cabin system platform to perform the corresponding actions by the corresponding cabin system platform, the method further includes:
acquiring instruction execution results of the cabin system platforms, wherein the instruction execution results comprise controlled information corresponding to the vehicle control instruction, queried information corresponding to the information query instruction and/or monitored information corresponding to the monitoring instruction;
and sending the control information, the queried information and/or the monitored information to the preset mobile terminal.
According to the APP and cabin system platform docking method, a plurality of cabin system platforms are docked based on the information query interface standard by determining the target event standard and the information query interface standard, and a vehicle control instruction, an information query instruction and/or a monitoring instruction sent by a preset mobile terminal based on a preset middleware SDK are received, and meanwhile, the determined vehicle control instruction, the determined information query instruction and/or the determined monitoring instruction are respectively sent to the corresponding cabin system platform based on the target event standard so as to execute corresponding actions through the corresponding cabin system platform. Therefore, the problems that in the related art, different docking needs to be performed on different cabin systems by the docking method are solved, so that docking workload and debugging difficulty are increased, communication cost is improved, and the like are solved, and the purposes of high-efficiency and low-cost docking of the APP and the cabin systems and normal operation of the multi-system platform can be achieved through one-time development by means of unified standard and dynamically-expandable middleware services and the same middleware SDK in docking with the cabin systems.
Additional aspects and advantages of the 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 the application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
fig. 1 is a flowchart of an APP and cabin system platform docking method provided according to an embodiment of the present application;
FIG. 2 is a flow chart of a docking method of an APP and cockpit system platform according to one embodiment of the present application;
FIG. 3 is a timing flow diagram for implementation of a specific technique according to one embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present application and are not to be construed as limiting the present application.
The APP and cabin system platform docking method of the embodiment of the present application is described below with reference to the accompanying drawings. Aiming at the problems that the docking method in the related art mentioned in the background art needs to carry out different docking for different cabin systems, so that docking workload and debugging difficulty are increased and communication cost is also improved, the application provides an APP and cabin system platform docking method. Therefore, the problems that in the related art, different docking needs to be performed on different cabin systems by the docking method are solved, so that docking workload and debugging difficulty are increased, communication cost is improved, and the like are solved, and the purposes of high-efficiency and low-cost docking of the APP and the cabin systems and normal operation of the multi-system platform can be achieved through one-time development by means of unified standard and dynamically-expandable middleware services and the same middleware SDK in docking with the cabin systems.
Specifically, before describing the embodiments of the present application, related modules related to the embodiments of the present application, including definition of an event standard, middleware SDK, a communication channel maintaining module, middleware service, an event management and forwarding module, and a specific vehicle control implementation module, are first described.
The event standard is used for defining an event group monitored by the vehicle control state and a specific event numbering standard, and all modules are communicated based on the standard uniformly.
The middleware SDK is used for providing the cabin APP for use, has uniformity for the cabin APP and does not change along with the change of a system platform. The middleware SDK internally comprises an event standard definition, event sending and receiving module and a client part maintained by a communication channel, and the cabin APP uses the SDK to send and receive events to the middleware service.
The communication channel maintaining module is arranged in the middleware SDK and used for ensuring the availability of the communication channels of the cabin APP and the middleware service process, monitoring the state of the channels in real time, and reconnecting with the middleware service based on the binder communication once one party is disconnected and reconnecting immediately.
The middleware Service is used for receiving and processing various events sent by the cabin APP, and a Android platform-based binder communication mechanism is used for cross-process communication with the APP client, is resident in the system platform and exists in an independent process mode, and is an Android system Service component. The middleware service has good expansibility and is easy to expand to different system platforms.
And the event management and forwarding module is used for forwarding and managing the circulation process of the event and exists in the process of the middleware service.
The specific vehicle control implementation module is used for interfacing with specific cabin system platforms, adapting different system platforms based on the same socket standard, and implementing specific vehicle control logic and query and monitoring logic of vehicle conditions and attribute information.
Specifically, fig. 1 is a schematic flow chart of a docking method of an APP and cabin system platform provided in an embodiment of the present application.
As shown in fig. 1, the docking method of the APP and the cabin system platform comprises the following steps:
in step S101, determining a target event criterion and an information query interface criterion;
further, in some embodiments, determining the target event criteria and the information query interface criteria includes: determining at least one event group, wherein the event group comprises a vehicle control event group, a vehicle attribute information event group and a vehicle state information event group; numbering at least one target event in each event group to obtain a target event standard.
Specifically, as shown in fig. 2, in the embodiment of the present application, taking docking between an APP and a cabin system platform as an example, before docking between the APP and the cabin system platform, the embodiment of the present application needs to define a set of target event standard and information query interface standard; second, the target event criteria are divided into different event groups according to different requirements, for example, a vehicle control event group, a vehicle attribute information event group and a vehicle state information event group, and at least one target event in the event groups is numbered to achieve finer distinction of each event in the event groups. The event number needs to have at least intra-group uniqueness, and if the event has better universality, the event needs to have global uniqueness.
In step S102, based on the information query interface standard, a plurality of cabin system platforms are docked, and a vehicle control instruction, an information query instruction and/or a monitoring instruction sent by the preset mobile terminal based on the preset middleware SDK are received.
Further, in some embodiments, before receiving the vehicle control command, the information query command, and/or the monitoring command sent by the preset mobile terminal based on the preset middleware SDK, the method further includes: according to a first preset starting strategy, starting a middleware service, and calling a vehicle control interface while starting the middleware service; and starting a preset component in the middleware service according to a second preset starting strategy, and connecting with the preset mobile terminal through a binder communication mechanism.
The preset mobile terminal may be a cabin APP, and the first preset starting policy and the second preset starting policy may be set correspondingly by a timekeeper in the field according to actual application conditions, which is not limited herein.
Specifically, as shown in fig. 2, when the cabin system in the embodiment of the present application is started, an independent middleware Service needs to be started according to a first preset starting policy, so that the middleware Service is in a surviving state, and when the middleware Service is started, a vehicle control interface is called through the cabin APP, and according to a second preset starting policy, a preset component, such as an Android Service component, is started in the middleware Service, and the mobile terminal is waited for connection.
Further, in the embodiment of the present application, after the Android Service component is started in the middleware Service, a vehicle control instruction, an information query instruction and/or a monitoring instruction are sent to the middleware Service by using a preset middleware SDK through a vehicle control interface, when the middleware Service receives the above instruction, an event management and forwarding module in the middleware Service forwards and manages a circulation process of an event according to a target event standard, and meanwhile, the cabin APP integrates and initializes the preset middleware SDK, and enables the inside of the preset middleware SDK to cooperate with the middleware Service, and is connected with a preset mobile terminal through a binder communication mechanism, so as to ensure availability of a cross-process communication channel, and can trigger reconnection when any party is disconnected.
Further, the event management and forwarding module in the embodiment of the present application executes specific vehicle control instructions, information query instructions, and/or monitoring instructions according to the target event criteria after forwarding and managing the event according to the target event criteria, so as to correspond to the target event instructions.
Further, in step S103, based on the target event criteria, a cabin system platform corresponding to the vehicle control instruction, the information query instruction and/or the monitoring instruction is determined, and the vehicle control instruction, the information query instruction and/or the monitoring instruction are respectively sent to the corresponding cabin system platform, so that corresponding actions are executed through the corresponding cabin system platform.
Specifically, if three different cabin system platforms, namely a platform a, a platform B and a platform C, are respectively configured in the embodiment of the present application, at this time, the embodiment of the present application determines a cabin system platform corresponding to a vehicle control instruction, an information query instruction and/or a monitoring instruction based on a target event standard, and if the vehicle control instruction corresponds to the platform a, the control platform a executes the vehicle control instruction; if the information inquiry instruction corresponds to the platform B, the control platform B executes the information inquiry instruction; and if the monitoring instruction corresponds to the platform C, the control platform C executes the monitoring instruction.
For example, if the cabin APP wants to implement the windowing function, it is assumed that the windowing command is defined as CMD1, at this time, the cabin APP needs to call an interface of the middleware SDK to send CMD1 to the middleware service, after the middleware service parses CMD1, the middleware service matches a call interface (for example, FUN 1) corresponding to the currently docked cabin system platform according to the parsing result to implement the windowing function, and it should be noted that the interfaces corresponding to different cabin system platforms when implementing a certain function are different, and may be selected accordingly according to practical applications, which is not limited herein.
Further, in the embodiment of the application, when the vehicle state and the attribute information are changed, the specific vehicle control logic, the vehicle condition and the query and monitoring logic of the attribute information are realized through the specific vehicle control realizing module.
Further, in some embodiments, after the vehicle control instructions, the information query instructions, and/or the monitoring instructions are respectively sent to the corresponding cabin system platform to perform the corresponding actions by the corresponding cabin system platform, the method further includes: acquiring instruction execution results of a plurality of cabin system platforms, wherein the instruction execution results comprise control information corresponding to a vehicle control instruction, queried information corresponding to an information query instruction and/or monitored information corresponding to a monitoring instruction; and sending the controlled information, the queried information and/or the monitored information to a preset mobile terminal.
Specifically, as shown in fig. 3, in the embodiment of the present application, after a vehicle control instruction, an information query instruction, and/or a monitoring instruction are parsed and corresponding actions are executed through corresponding cabin system platforms, a middleware service sends acquired instruction execution results of multiple cabin system platforms to a preset mobile terminal, and meanwhile, a specific vehicle control implementation module packages state and attribute change information of a cabin system into events and gives the events to a middleware service, and the events are forwarded to a cabin APP process through the middleware service, and event content is parsed through a preset middleware SDK in the cabin APP process, so that a cabin APP logic layer decides own service logic.
Further, in some embodiments, the APP docking method with the cabin system platform further includes: judging whether a cabin system platform is newly added to the current vehicle; if a cabin system platform is newly added to the current vehicle, the cabin system platform is directly docked based on the information query interface standard.
Specifically, if the newly added cabin system platform exists in the current vehicle in the embodiment of the application, the newly added cabin system platform is directly docked based on the information query interface standard, so that the purpose that the vehicle can normally operate on the multi-system cabin platform after one development is achieved.
According to the APP and cabin system platform docking method, a plurality of cabin system platforms are docked based on the information query interface standard by determining the target event standard and the information query interface standard, and a vehicle control instruction, an information query instruction and/or a monitoring instruction sent by a preset mobile terminal based on a preset middleware SDK are received, and meanwhile, the determined vehicle control instruction, the determined information query instruction and/or the determined monitoring instruction are respectively sent to the corresponding cabin system platform based on the target event standard so as to execute corresponding actions through the corresponding cabin system platform. Therefore, the problems that in the related art, different docking needs to be performed on different cabin systems by the docking method are solved, so that docking workload and debugging difficulty are increased, communication cost is improved, and the like are solved, and the purposes of high-efficiency and low-cost docking of the APP and the cabin systems and normal operation of the multi-system platform can be achieved through one-time development by means of unified standard and dynamically-expandable middleware services and the same middleware SDK in docking with the cabin systems.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or N embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more N executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the N steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or part of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, where the program when executed includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented as software functional modules and sold or used as a stand-alone product.
Claims (5)
1. An APP and cabin system platform docking method is characterized by comprising the following steps:
determining a target event standard and an information query interface standard;
based on the information inquiry interface standard, a plurality of cabin system platforms are connected, and a vehicle control instruction, an information inquiry instruction and/or a monitoring instruction sent by a preset mobile terminal based on a preset middleware SDK are received; and
and determining a cabin system platform corresponding to the vehicle control instruction, the information inquiry instruction and/or the monitoring instruction based on the target event standard, and respectively sending the vehicle control instruction, the information inquiry instruction and/or the monitoring instruction to the corresponding cabin system platform so as to execute corresponding actions through the corresponding cabin system platform.
2. The method of claim 1, wherein determining target event criteria and information query interface criteria comprises:
determining at least one event group, wherein the event group comprises a vehicle control event group, a vehicle attribute information event group and a vehicle state information event group;
numbering at least one target event in each event group to obtain the target event standard.
3. The method of claim 1, further comprising, prior to interfacing the plurality of cabin system platforms based on the information query interface standard and receiving vehicle control instructions, information query instructions, and/or listening instructions sent by a preset mobile terminal based on the preset middleware SDK:
according to a first preset starting strategy, starting a middleware service, and calling a vehicle control interface while starting the middleware service;
and starting a preset component in the middleware service according to a second preset starting strategy, and connecting with the preset mobile terminal through a binder communication mechanism.
4. The method as recited in claim 1, further comprising:
judging whether a cabin system platform is newly added to the current vehicle;
and if the cabin system platform is newly added to the current vehicle, docking the cabin system platform is directly based on the information query interface standard.
5. The method of claim 1, further comprising, after sending the vehicle control instructions, the information query instructions, and/or the listening instructions to the corresponding cabin system platform, respectively, to perform respective actions by the corresponding cabin system platform:
acquiring instruction execution results of the cabin system platforms, wherein the instruction execution results comprise controlled information corresponding to the vehicle control instruction, queried information corresponding to the information query instruction and/or monitored information corresponding to the monitoring instruction;
and sending the control information, the queried information and/or the monitored information to the preset mobile terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310029306.9A CN116319852A (en) | 2023-01-09 | 2023-01-09 | APP and cabin system platform docking method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310029306.9A CN116319852A (en) | 2023-01-09 | 2023-01-09 | APP and cabin system platform docking method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116319852A true CN116319852A (en) | 2023-06-23 |
Family
ID=86785895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310029306.9A Pending CN116319852A (en) | 2023-01-09 | 2023-01-09 | APP and cabin system platform docking method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116319852A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215958A (en) * | 2023-10-11 | 2023-12-12 | 深圳市浩科智联科技有限公司 | Vehicle-mounted application separation design software and test method thereof |
| CN117215958B (en) * | 2023-10-11 | 2024-05-31 | 深圳市浩科智联科技有限公司 | Vehicle-mounted application separation design software and test method thereof |
-
2023
- 2023-01-09 CN CN202310029306.9A patent/CN116319852A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215958A (en) * | 2023-10-11 | 2023-12-12 | 深圳市浩科智联科技有限公司 | Vehicle-mounted application separation design software and test method thereof |
| CN117215958B (en) * | 2023-10-11 | 2024-05-31 | 深圳市浩科智联科技有限公司 | Vehicle-mounted application separation design software and test method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1784693B1 (en) | Method for providing a rapid response to queries on a vehicle bus | |
| CN105282213B (en) | Limp-home operation of an audio video bridging network | |
| CN107659494B (en) | Data processing method and intelligent vehicle-mounted gateway | |
| US10673986B2 (en) | Operation method of communication node for selective wake-up in vehicle network | |
| US20030223436A1 (en) | System for managing networks | |
| KR20170040326A (en) | Communication control device for a subscriber station of a bus system, programming tool and method for programming subscriber stations in a bus system which has subscriber stations communicating according to different protocols | |
| KR20160146055A (en) | Operating method of a communication node in automotive network | |
| CN112578764A (en) | Vehicle fault diagnosis method and system and vehicle | |
| CN115857985A (en) | Cabin upgrading system, operation method and storage medium | |
| CN113672254A (en) | Vehicle OTA (over the air) upgrading method and device, storage medium and unmanned equipment | |
| CN111490918A (en) | Vehicle-mounted Ethernet network awakening system, method and device and computer equipment | |
| US20100205307A1 (en) | Communication control system | |
| CN116319852A (en) | APP and cabin system platform docking method | |
| US9118651B2 (en) | Control unit for in-vehicle ethernet and method for controlling thereof | |
| CN115224685B (en) | Power distribution management method, device, vehicle and storage medium | |
| CN113891397A (en) | Method and system for segmenting and transmitting data between computing device and carrier head unit | |
| CN112468528B (en) | Vehicle double-path WiFi implementation method and vehicle-mounted information entertainment system | |
| KR102029371B1 (en) | Power Supply system and method for ethernet communication network in vehicle | |
| WO2021094385A1 (en) | Method and system for data communication network in a vehicle | |
| KR102313599B1 (en) | Method for software update of vehicle and device for the same | |
| CN107800677B (en) | Apparatus and method for providing adaptive connection service | |
| CN110690998B (en) | Master-slave equipment management method based on BMC | |
| CN114185297B (en) | Control method and device for vehicle-mounted software upgrading | |
| US20240089142A1 (en) | Vehicle-mounted apparatus and a method for relaying | |
| KR101836671B1 (en) | Method for dynamic scheduling in local interconnection network communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |