A vehicle-mounted unit application management method and system based on SOA architecture

Abstract

The present invention relates to a vehicle-mounted unit application management method and system based on SOA architecture, wherein the vehicle-mounted unit application includes an RTE layer and an APPS layer, wherein the APPS layer includes a number of independent APPs, and the APPs are used to implement specific CVIS scenarios, and the method includes the following steps: when the APPs layer APP is running, the information type of the standard information required for the scenario running is registered with the RTE layer according to its own scenario requirements. After the registration is completed, the APPs layer APP performs logical operations according to the scenario requirements, and sends the operation results to the RTE layer in the registered information type; the RTE layer routes and sends the operation results sent by the APPS layer to the corresponding device. Each APP is independent of each other. When a certain scenario is not needed, only the corresponding APP needs to be uninstalled, which will not affect the use of other APPs. The APPs have good scalability and are easy to maintain, and can achieve multiple and complex scenario management.

Description

Technical Field

[0001] The present application relates to the fields of vehicle-road collaboration, intelligent driving, and smart road technology, and specifically to a vehicle-mounted unit application management method and system based on SOA architecture. Background Art

[0002] The onboard unit (OBU) and the roadside unit (RSU) form an important hub for connecting the vehicle to the outside world and are important participants in CVIS (vehicle-road cooperative system). In CVIS, the communication between V2X (vehicle-to-vehicle) and V2I (vehicle-to-infrastructure) mainly relies on c-v2x technology. C-V2X (full name cellular vehicle-to-everything) is a vehicle networking communication technology based on cellular networks. It provides a key technical foundation for smart cars, autonomous driving, and intelligent transportation systems. By using the globally unified 5.9GHZ ITS frequency band, C-V2X can use low-latency direct communication technology to provide low-latency information transmission for V2V, V2I, and V2P (vehicle-to-pedestrian). OBU communicates with other OBUs and RSUs through c-V2X to achieve information exchange and sharing, and can provide early warning of dangerous road conditions during vehicle driving.

[0003] The existing traditional APP development method has functional code coupling, and the program needs to be packaged and deployed as a whole. Modifying a part of the logic requires recompilation and deployment. When the functions across controllers are redistributed, the software of all related controllers needs to be updated. The V2X scenarios in OBU applications are numerous and complex. According to the "Cooperative Intelligent Transportation System Vehicle Communication System Application Layer and Application Data Interaction Standard", there are as many as 17 scenarios defined. At this time, the disadvantages of using traditional development are more prominent, and it is not easy to modify and add functional logic to complex scenarios. The code logic is complex and difficult to manage. Summary of the invention

[0004] In view of the above problems, the present application provides a vehicle-mounted unit application management method and system based on SOA architecture to solve the problem that the existing vehicle-mounted unit applications use functional code coupling in traditional APP development, which makes it difficult to modify and add functional logic for complex scenarios.

[0005] To achieve the above object, the inventor provides a vehicle-mounted unit application management method based on SOA architecture, wherein the vehicle-mounted unit application includes an RTE layer and an APPS layer, wherein the APPS layer includes a number of mutually independent APPs, and the APPs are used to implement a specific CVIS scenario. The method includes the following steps:

[0006] When the APP in the APPS layer is running, it registers the information type of the standard information required for the scene operation with the RTE layer according to its own scene requirements;

[0007] After registration is completed, the APP in the APPS layer performs logical operations according to the scenario requirements and sends the operation results to the RTE layer in the registered information type;

[0008] The RTE layer routes and sends the calculation results sent by the APPS layer to the corresponding device.

[0009] Further optimization also includes the following steps:

[0010] When the RTE layer receives information sent from the outside, it classifies the received information and obtains the corresponding information type;

[0011] According to the information type, the RTE layer sends the received information to the APP that has registered the information type;

[0012] APP responds to the information sent by RTE.

[0013] Further optimization also includes the following steps:

[0014] When the RTE layer reads the data sent by the registered APP to the outside, it creates a sending thread, assigns information to the read data, and broadcasts it periodically.

[0015] Further optimized, the information type includes MAP, SPAT, RSI, RSM and BSM.

[0016] Further optimization also includes the following steps:

[0017] The RTE layer installs or uninstalls the corresponding APP according to the application scenarios required in the vehicle-mounted unit application.

[0018] Another technical solution is also provided: an on-board unit application management system based on SOA architecture, including an RTE layer and an APPS layer, wherein the APPS layer includes a number of mutually independent APPs, and the APPs are used to implement specific CVIS scenarios;

[0019] The APP of the APPS layer is also used for runtime. According to its own scenario requirements, the APP registers the information type of the standard information required for scenario runtime with the RTE layer. After registration, logical operations are performed according to the scenario requirements, and the operation results are sent to the RTE layer in the registered information type.

[0020] The RTE layer is used to route and send the calculation results sent by the APPS layer to the corresponding devices.

[0021] Further optimization, the RTE layer is used to classify the received information after receiving the information sent from the outside to obtain the corresponding information type. According to the information type, the RTE layer sends the received information to the APP that has registered the information type;

[0022] The APP is used to respond to the information sent by the RTE.

[0023] For further optimization, the RTE layer is also used to create a sending thread when reading data sent to the outside by a registered APP, assign information to the read data, and broadcast it periodically.

[0024] Further optimized, the information type includes MAP, SPAT, RSI, RSM and BSM.

[0025] For further optimization, the RTE layer is also used to install or uninstall corresponding APPs according to the application scenarios required in the vehicle-mounted unit application.

[0026] Different from the prior art, the above technical solution divides the vehicle-mounted unit application into the RTE layer and the APPS layer. The APPS layer includes many APPs, each of which is independent of each other, and different CVIS scenarios are realized through each APP. In this SOA architecture, the APP in the APPS layer subscribes to the RTE layer for the type of information required by its own scenario. The APP in the APPS layer performs logical operations according to the scenario requirements, and sends the results of the logical operations to the RTE layer in the message format required by the RTE layer. The RTE layer then routes the messages sent by the APP in the APPS layer to the corresponding devices, thereby realizing specific scenario functions. The APPs in the APPS layer are independent of each other. When a certain scenario is not needed, you only need to uninstall the corresponding APP, which will not affect the use of other APPs. At the same time, compared with the traditional APP development method, the management method of the vehicle-mounted unit application developed based on the SOA architecture has better scalability and is easy to maintain, and can realize multiple and complex scenario management.

[0027] The above-mentioned records related to the invention content are only an overview of the technical solution of the present application. In order to enable ordinary technicians in the field to more clearly understand the technical solution of the present application, and then implement it according to the text of the specification and the contents recorded in the drawings, and to make the above-mentioned purpose and other purposes, features and advantages of the present application easier to understand, the following is an explanation in combination with the specific implementation mode and drawings of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The drawings are only used to illustrate the principles, implementation methods, applications, characteristics and effects of the specific embodiments of the present application and other related contents, and shall not be considered as limitations of the present application.

[0029] In the drawings of the specification:

[0030] Figure 1 A flowchart of a vehicle-mounted unit application management method based on SOA architecture described in a specific implementation method;

[0031] Figure 2 A schematic diagram of a process flow of the APP-triggered process described in the specific implementation method;

[0032] Figure 3 Another flowchart of the APP-triggered process described in the specific implementation method is shown below;

[0033] Figure 4 A schematic diagram of a process flow of the APP periodic broadcast process described in the specific implementation method;

[0034] Figure 5 A schematic diagram of a process flow of the APP periodic broadcast process described in the specific implementation method;

[0035] Figure 6 A structural diagram of the vehicle-mounted unit application management system based on SOA architecture described in the specific implementation method.

[0036] The reference numerals in the above drawings are described as follows:

[0037] 110, APPS layer, 111, APP;

[0038] 120. RTE layer. DETAILED DESCRIPTION

[0039] In order to explain in detail the possible application scenarios, technical principles, specific schemes that can be implemented, and the purposes and effects that can be achieved, the following is a detailed description of the specific embodiments listed in conjunction with the accompanying drawings. The embodiments described herein are only used to more clearly illustrate the technical solutions of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.

[0040] Reference to "embodiment" herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The term "embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment, nor does it particularly limit its independence or association with other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, the various technical features mentioned in the embodiments can be combined in any way to form a corresponding implementable technical solution.

[0041] Unless otherwise defined, the technical terms used in this document have the same meanings as those generally understood by those skilled in the art to which this application belongs; the use of relevant terms in this document is only for describing specific embodiments and is not intended to limit this application.

[0042] In the description of this application, the term "and / or" is an expression used to describe the logical relationship between objects, indicating that three relationships may exist, for example, A and / or B, which means: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in this article generally indicates that the objects before and after are in an "or" logical relationship.

[0043] In the present application, terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship of quantity, priority or sequence between these entities or operations.

[0044] Without further limitations, in this application, the words "include", "comprises", "has" or other similar expressions used in the sentences are intended to cover non-exclusive inclusion. These expressions do not exclude the presence of additional elements in the process, method or product including the elements, so that the process, method or product including a series of elements may include not only those limited elements, but also other elements not explicitly listed, or also include elements inherent to such process, method or product.

[0045] Similar to the understanding in the Examination Guidelines, in this application, expressions such as "greater than", "less than", "exceed" and the like are understood to exclude the number itself; expressions such as "above", "below", "within" and the like are understood to include the number itself. In addition, in the description of the embodiments of this application, "multiple" means more than two (including two), and similar expressions related to "multiple" are also understood in this way, such as "multiple groups", "multiple times", etc., unless otherwise clearly and specifically limited.

[0046] In the description of the embodiments of the present application, space-related expressions used, such as "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "vertical", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc., indicate the orientation or position relationship based on the orientation or position relationship shown in the specific embodiments or drawings, and are only for the convenience of describing the specific embodiments of the present application or facilitating the reader's understanding, and do not indicate or imply that the referred device or component must have a specific position, a specific orientation, or be constructed or operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.

[0047] Unless otherwise expressly specified or limited, in the description of the embodiments of the present application, the terms "install", "connect", "connect", "fix", "set", etc. used should be understood in a broad sense. For example, the "connection" can be a fixed connection, a detachable connection, or an integrated setting; it can be a mechanical connection, an electrical connection, or a communication connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium; it can be the internal connection of two elements or the interaction relationship between two elements. For technicians in the technical field to which the present application belongs, the specific meanings of the above terms in the embodiments of the present application can be understood according to the specific circumstances.

[0048] See also Figure 1 This embodiment provides a vehicle-mounted unit application management method based on SOA architecture, which is applied to Figure 6 The vehicle-mounted unit application management method based on SOA architecture is shown, the vehicle-mounted unit application includes an RTE layer 120 and an APPS layer 110, the APPS layer 110 includes a plurality of mutually independent APPs 111, and the APPs 111 are used to implement a specific CVIS scenario. The method includes the following steps:

[0049] Step S110: When the APP of the APPS layer is running, it registers the information type of the standard information required for the scene running with the RTE layer according to its own scene requirements;

[0050] Step S120: After registration is completed, the APP in the APPS layer performs logical operations according to the scenario requirements and sends the operation results to the RTE layer in the registered information type;

[0051] Step S130: The RTE layer routes and sends the calculation result sent by the APPS layer to the corresponding device.

[0052] SOA (Service-Oriented Architecture) is a component model that splits different functional units of an application (called services) and connects them through well-defined interfaces and protocols. The interface is defined in a neutral way, independent of the hardware platform, operating system, and programming language that implements the service. This allows services built in a variety of systems to interact in a unified and universal way.

[0053] STE (Serial-to-Ethernet) layer, serial port service layer, implements the following functions: installation and management of APP applications, definition and routing management of communication messages between APPS and RTE, definition and management of underlying devices (such as HMI devices, CAN devices, etc.), etc.

[0054] APP (application) refers to a computer program that is used to complete one or more specific tasks; the APPS layer is composed of multiple APPs.

[0055] CVIS (Cooperative Vehicle Infrastructure System) is a vehicle-road cooperative system. Vehicle-road cooperation is the effective integration of roads, vehicles and technologies. Through advanced wireless communication and Internet technologies, it realizes real-time data interaction between vehicles, vehicles and roads, vehicles and people, and vehicles and networks.

[0056] The vehicle-mounted unit application is divided into the RTE layer and the APPS layer. The APPS layer includes many APPs, each of which is independent of each other. Different CVIS scenarios are realized through each APP, such as the front collision warning APP, intersection collision warning APP, left turn assistance APP, lane change warning APP, reverse overtaking warning APP, abnormal vehicle reminder APP and speed limit warning APP. In this SOA architecture, the APP in the APPS layer subscribes to the information type required by its own scenario from the RTE layer. The APP in the APPS layer performs logical operations according to the scenario requirements and sends the logical operation results to the RTE layer in the message format required by the RTE layer. Then the RTE layer routes the messages sent by the APP in the APPS layer to the corresponding devices, thereby realizing specific scenario functions. The APPs in the APPS layer are independent of each other. When a certain scenario is not needed, just uninstall the corresponding APP, which will not affect the use of other APPs. At the same time, compared with the traditional APP development method, the management method of the vehicle-mounted unit application developed based on the SOA architecture has better scalability and is easy to maintain, and can realize multiple and complex scenario management. Improve the development efficiency of OBU applications. APPs are independent of each other and have good adaptability to changes in application scenarios.

[0057] See also Figure 2-3 In the APP-triggered process shown, in some embodiments, when external information is received, the external information is sent to the corresponding APP in a triggered manner, specifically, the following steps are also included:

[0058] Step S210: After receiving the information sent from the outside, the RTE layer classifies the received information to obtain the corresponding information type;

[0059] Step S220: According to the information type, the RTE layer sends the received information to the APP that has registered the information type;

[0060] Step S230: APP responds to the information sent by RTE.

[0061] When the RTE layer receives information sent from the outside, it first classifies the received information to obtain the information type of the external information; then, according to the information type of the external information, the RTE layer sends the received external information to the APP that registers the information type, so that the corresponding APP can respond to the external information received by the RTE layer. For example, when classifying the external information, if the external information is judged to be V2X alarm information, the V2X alarm information is sent to the corresponding APP. After the corresponding APP receives the V2X alarm information, it determines whether the alarm condition is met. If the alarm condition is met, the alarm information is sent to the corresponding device, such as sending the alarm information through the vehicle screen to remind the driver.

[0062] See also Figure 4-5 , APP periodic broadcast process, in some embodiments, APP uses periodic broadcasting to send data to external devices, specifically, it also includes the following steps:

[0063] Step S410: When the RTE layer reads the data sent to the outside by the registered APP, it creates a sending thread, assigns information to the read data, and broadcasts it periodically.

[0064] When a registered APP wants to send data to an external device according to the needs of its own scenario, the registered APP sends the data to be sent to the RTE layer. When the RTE layer reads the data sent by the APP to the external device, it creates a sending thread, assigns information to the read data, and broadcasts it periodically. The external device can obtain the corresponding data according to the periodic broadcast. When the periodic broadcast reaches the preset number of times, the broadcast to the external device stops.

[0065] In some embodiments, the information type includes MAP, SPAT, RSI, RSM and BSM. According to the standard "Technical Requirements for Direct Communication System of Wireless Communication Technology for Internet of Vehicles Based on LTE", the message types defined include MAP, SPAT, RSI, RSM and BSM.

[0066] BSM, or Basic Safety Message, includes speed, steering, braking, double flash, location, etc. It is mostly used in V2V scenarios, such as lane change warning, blind spot warning, intersection collision warning, etc.

[0067] RSI, or Road Side Information, is used for the following events, roadside RSU integration, and platform delivery. It is mostly used in V2I scenarios, such as road construction, speed limit signs, speeding warnings, bus lane warnings, etc.

[0068] RSM, or Road Safety Message, is also V2I. It is mainly connected to the edge devices on the roadside for event recognition, such as vehicle accidents, vehicle abnormalities, foreign objects intrusion, etc.

[0069] SPAT, or Signal phase timing message, is also V2I. The roadside RSU integrates the traffic light, or the traffic light is transmitted to the platform through UU for vehicle speed guidance, green wave push scenarios, etc.

[0070] MAP, or map message, is used together with SPAT message. MAP message can describe an intersection and has a corresponding relationship with the traffic lights at the intersection.

[0071] In some embodiments, the following steps are also included:

[0072] The RTE layer installs or uninstalls the corresponding APP according to the application scenarios required in the vehicle-mounted unit application.

[0073] Since each APP in the APPS layer is independent of each other, and each CVIS scenario is implemented through an APP; when a certain scenario is not needed, the corresponding APP can be deleted, and when a new scenario is needed, the corresponding APP can be installed without affecting the normal operation of other APPs; it has good scalability and is easy to maintain.

[0074] See also Figure 6 , another technical solution is also provided: a vehicle-mounted unit application management system based on SOA architecture, including an RTE layer 120 and an APPS layer 110, wherein the APPS layer 110 includes a plurality of mutually independent APPs 111, and the APPs 111 are used to implement a specific CVIS scenario;

[0075] The APP111 of the APPS layer 110 is also used to register the information type of the standard information required for the scene operation with the RTE layer 120 according to its own scene requirements during operation. After the registration is completed, logical operations are performed according to the scene requirements, and the operation results are sent to the RTE layer 120 in the registered information type;

[0076] The RTE layer 120 is used to route and send the calculation result sent by the APPS layer 110 to the corresponding device.

[0077] SOA (Service-Oriented Architecture) is a component model that splits different functional units of an application (called services) and connects them through well-defined interfaces and protocols. The interface is defined in a neutral way, independent of the hardware platform, operating system, and programming language that implements the service. This allows services built in a variety of systems to interact in a unified and universal way.

[0078] STE (Serial-to-Ethernet) layer, serial port service layer, implements the following functions: installation and management of APP applications, definition and routing management of communication messages between APPS and RTE, definition and management of underlying devices (such as HMI devices, CAN devices, etc.), etc.

[0079] APP (application) refers to a computer program that is used to complete one or more specific tasks; the APPS layer is composed of multiple APPs.

[0080] CVIS (Cooperative Vehicle Infrastructure System) is a vehicle-road cooperative system. Vehicle-road cooperation is the effective integration of roads, vehicles and technologies. Through advanced wireless communication and Internet technologies, it realizes real-time data interaction between vehicles, vehicles and roads, vehicles and people, and vehicles and networks.

[0081] The vehicle-mounted unit application is divided into the RTE layer and the APPS layer. The APPS layer includes many APPs, each of which is independent of each other. Different CVIS scenarios are realized through each APP, such as the front collision warning APP, intersection collision warning APP, left turn assistance APP, lane change warning APP, reverse overtaking warning APP, abnormal vehicle reminder APP and speed limit warning APP. In this SOA architecture, the APP in the APPS layer subscribes to the information type required by its own scenario from the RTE layer. The APP in the APPS layer performs logical operations according to the scenario requirements and sends the logical operation results to the RTE layer in the message format required by the RTE layer. Then the RTE layer routes the messages sent by the APP in the APPS layer to the corresponding devices, thereby realizing specific scenario functions. The APPs in the APPS layer are independent of each other. When a certain scenario is not needed, just uninstall the corresponding APP, which will not affect the use of other APPs. At the same time, compared with the traditional APP development method, the management method of the vehicle-mounted unit application developed based on the SOA architecture has better scalability and is easy to maintain, and can realize multiple and complex scenario management. Improve the development efficiency of OBU applications. APPs are independent of each other and have good adaptability to changes in application scenarios.

[0082] In some embodiments, when external information is received, the external information is sent to the corresponding APP in a triggering manner. The RTE layer 120 is used to classify the received information after receiving the externally sent information to obtain the corresponding information type. According to the information type, the RTE layer 120 sends the received information to the APP 111 that has registered the information type.

[0083] The APP111 is used to respond to the information sent by the RTE.

[0084] When the RTE layer 120 receives information sent from the outside, it first classifies the received information to obtain the information type of the external information; then, according to the information type of the external information, the RTE layer 120 sends the received external information to the APP 111 that registers the information type, so that the corresponding APP 11 can respond to the external information received by the RTE layer 120. For example, when classifying the external information, if the external information is judged to be V2X alarm information, the V2X alarm information is sent to the corresponding APP 111. After the corresponding APP 111 receives the V2X alarm information, it determines whether the alarm condition is met. If the alarm condition is met, the alarm information is sent to the corresponding device, such as sending the alarm information through the vehicle screen to remind the driver.

[0085] In some embodiments, APP111 uses periodic broadcasting to send data to external devices. Specifically, the RTE layer 120 is also used to create a sending thread when reading the data sent to the outside by the registered APP111, assign information to the read data, and broadcast it periodically. When the registered APP111 wants to send data to an external device according to the needs of its own scenario, the registered APP111 sends the data to be sent to the RTE layer 120, and when the RTE layer 120 reads the data sent by APP111 to the external device, it creates a sending thread, assigns information to the read data, and broadcasts it periodically. The external device can obtain the corresponding data based on the periodic broadcast. Among them, when the periodic broadcast reaches a preset number of times, the broadcast to the external device is stopped.

[0086] When the RTE layer 120 receives information sent from the outside, it first classifies the received information to obtain the information type of the external information; then, according to the information type of the external information, the RTE layer sends the received external information to the APP that registers the information type, so that the corresponding APP can respond to the external information received by the RTE layer. For example, when classifying the external information, if the external information is judged to be V2X alarm information, the V2X alarm information is sent to the corresponding APP. After the corresponding APP receives the V2X alarm information, it determines whether the alarm condition is met. If the alarm condition is met, the alarm information is sent to the corresponding device, such as sending the alarm information through the vehicle screen to remind the driver.

[0087] In some embodiments, the information type includes MAP, SPAT, RSI, RSM and BSM. According to the standard "Technical Requirements for Direct Communication System of Wireless Communication Technology for Internet of Vehicles Based on LTE", the message types defined include MAP, SPAT, RSI, RSM and BSM.

[0088] BSM, or Basic Safety Message, includes speed, steering, braking, double flash, location, etc. It is mostly used in V2V scenarios, such as lane change warning, blind spot warning, intersection collision warning, etc.

[0089] RSI, or Road Side Information, is used for the following events, roadside RSU integration, and platform delivery. It is mostly used in V2I scenarios, such as road construction, speed limit signs, speeding warnings, bus lane warnings, etc.

[0090] RSM, or Road Safety Message, is also V2I. It is mainly connected to the edge devices on the roadside for event recognition, such as vehicle accidents, vehicle abnormalities, foreign objects intrusion, etc.

[0091] SPAT, or Signal phase timing message, is also V2I. The roadside RSU integrates the traffic light, or the traffic light is transmitted to the platform through UU for vehicle speed guidance, green wave push scenarios, etc.

[0092] MAP, i.e. MAP, map message, is used together with SPAT message. MAP message can describe an intersection and there is a corresponding relationship between it and the traffic lights at the intersection.

[0093] In some embodiments, the RTE layer 120 is also used to install or uninstall the corresponding APP 111 according to the application scenario required in the vehicle-mounted unit application. Since the various APPs 111 of the APPS layer 110 are independent of each other, and each CVIS scenario is implemented by one APP 111; when a certain scenario is not needed, the corresponding APP 111 can be deleted, and when a new scenario is needed, the corresponding APP 111 can be installed, which will not affect the normal operation of other APPs 111; it has good scalability and is easy to maintain.

[0094] Finally, it should be noted that although the above embodiments have been described in the specification and drawings of this application, this does not limit the scope of patent protection of this application. All technical solutions generated by replacing or modifying equivalent structures or equivalent processes based on the essential concept of this application using the contents recorded in the specification and drawings of this application, as well as directly or indirectly implementing the technical solutions of the above embodiments in other related technical fields, are included in the scope of patent protection of this application.

Claims

1. A vehicle-mounted unit application management method based on SOA architecture, characterized in that: The vehicle-mounted unit application includes an RTE layer and an APPS layer. The APPS layer includes a number of independent APPs. The APPs are used to implement a specific CVIS scenario. The method includes the following steps: When the APP in the APPS layer is running, it registers the information type of the standard information required for the scene operation with the RTE layer according to its own scene requirements; After registration is completed, the APP in the APPS layer performs logical operations according to the scenario requirements and sends the operation results to the RTE layer in the registered information type; The RTE layer routes and sends the calculation results sent by the APPS layer to the corresponding device.

2. The vehicle-mounted unit application management method based on SOA architecture according to claim 1 is characterized in that: The following steps are also included: When the RTE layer receives information sent from the outside, it classifies the received information and obtains the corresponding information type; According to the information type, the RTE layer sends the received information to the APP that has registered the information type; APP responds to the information sent by RTE.

3. The vehicle-mounted unit application management method based on SOA architecture according to claim 1 is characterized in that: The following steps are also included: When the RTE layer reads the data sent by the registered APP to the outside, it creates a sending thread, assigns information to the read data, and broadcasts it periodically.

4. The vehicle-mounted unit application management method based on SOA architecture according to claim 1 is characterized in that: The information types include MAP, SPAT, RSI, RSM and BSM.

5. The OUB application management method based on SOA architecture according to claim 1 is characterized in that: The following steps are also included: The RTE layer installs or uninstalls the corresponding APP according to the application scenarios required in the vehicle-mounted unit application.

6. A vehicle-mounted unit application management system based on SOA architecture, characterized in that: It includes an RTE layer and an APPS layer. The APPS layer includes a number of independent APPs, and the APPs are used to implement specific CVIS scenarios. The APP of the APPS layer is also used for runtime. According to its own scenario requirements, the APP registers the information type of the standard information required for scenario runtime with the RTE layer. After registration, logical operations are performed according to the scenario requirements, and the operation results are sent to the RTE layer in the registered information type. The RTE layer is used to route and send the calculation results sent by the APPS layer to the corresponding devices.

7. The vehicle-mounted unit application management system based on SOA architecture according to claim 6 is characterized in that: The RTE layer is used to classify the received information after receiving the information sent from the outside to obtain the corresponding information type. According to the information type, the RTE layer sends the received information to the APP that has registered the information type; The APP is used to respond to the information sent by the RTE.

8. The vehicle-mounted unit application management system based on SOA architecture according to claim 6 is characterized in that: The RTE layer is also used to create a sending thread when reading data sent to the outside by a registered APP, assign information to the read data, and broadcast it periodically.

9. The vehicle-mounted unit application management system based on SOA architecture according to claim 6 is characterized in that: The information types include MAP, SPAT, RSI, RSM and BSM.

10. The vehicle-mounted unit application management system based on SOA architecture according to claim 6, characterized in that: The RTE layer is also used to install or uninstall corresponding APPs according to the application scenarios required in the vehicle-mounted unit application.

Images