An acquisition method and device of a vehicle cloud data collection system architecture, an equipment and a medium

Abstract

The application provides a vehicle cloud data acquisition system architecture acquisition method, device, equipment and medium, the vehicle cloud data acquisition system architecture acquisition method comprises the following steps: obtaining information of a plurality of business cases by analyzing business requirements; splitting the information of the plurality of business cases to obtain information of a domain model of the vehicle cloud data acquisition system architecture and information of a plurality of business concepts; performing step splitting on functions of the plurality of business concepts to obtain information of a domain service; arranging the information of the domain service to obtain information of an interface protocol for port interaction of a plurality of plug-in adapters; and according to the information of the interface protocol, the plurality of plug-in adapters interact with the vehicle cloud data acquisition system architecture. The vehicle cloud data acquisition system architecture acquisition method disclosed by the application improves the expansibility and flexibility of the vehicle cloud data acquisition system architecture.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software system architecture, and particularly relates to a vehicle cloud data acquisition system architecture acquisition method and device, equipment and medium. BACKGROUND

[0002] With the rapid development of automobiles towards networking and intelligence, a large amount of data generated by automobiles in the use process is stored in the cloud. Among them, how to collect the information under the specific collection rules such as the key data in the vehicle driving process and the key information when the vehicle fails and upload it to the cloud so as to facilitate subsequent data analysis and data value mining is a problem. Moreover, the software service of these specific collection rule information is also very important for adding and maintaining. Among them, the architecture design as the cornerstone of software service not only needs to consider completing the current function in the early stage of construction, but also needs to consider the robustness of the software and the coupling degree between modules to increase the software life cycle and reduce the software maintenance cost. However, the data acquisition software designed through the software architecture design can only be designed for specific protocols, so that the data acquisition can only identify the parameter data in the specific protocol format, and when new data specifications need to be collected and analyzed, the key components cannot be directly reused and flexibly expanded. SUMMARY

[0003] In view of the above-mentioned shortcomings of the prior art, the present application provides a vehicle cloud data acquisition system architecture acquisition method to solve the problems of reducing the software life cycle, increasing the maintenance cost and being able to only collect data for specific protocols.

[0004] The vehicle cloud data acquisition system architecture acquisition method provided by the present application comprises the following steps:

[0005] Through the analysis of the business requirements of the vehicle cloud data acquisition system architecture, the information of a plurality of business use cases of the vehicle cloud data acquisition system architecture is acquired;

[0006] The information of a plurality of business use cases is split to acquire the information of the domain model of the vehicle cloud data acquisition system architecture and the information of a plurality of business concepts in the domain model;

[0007] The functions to be implemented by a plurality of business concepts are step-split to acquire the information of the domain service of the vehicle cloud data acquisition system architecture;

[0008] The information of the domain service is arranged to acquire the information of the interface protocol for port interaction of a plurality of plug-in adapters; and

[0009] According to the information of the interface protocol, a plurality of plug-in adapters interact with the vehicle cloud data acquisition system.

[0010] In an embodiment of the present application, the information of the business use cases of the vehicle cloud data collection system architecture comprises the following steps:

[0011] Through the analysis of the business requirements of the vehicle cloud data collection system, the boundary information of the vehicle cloud data collection system is obtained; and

[0012] Through the division of the boundary of the vehicle cloud data collection system, the information of the plurality of business use cases is obtained.

[0013] In an embodiment of the present application, the information of the domain model of the vehicle cloud data collection system architecture comprises the following steps:

[0014] Through the splitting of the plurality of business use cases, the information of the key problems in the business use cases is obtained;

[0015] Through the extraction of the information of the key problems in the business use cases, the information of the domain model is obtained.

[0016] In an embodiment of the present application, the following steps are further included:

[0017] Obtaining a new type of vehicle data;

[0018] Obtaining the port information of a new plug-in adapter matched with the new type of vehicle data.

[0019] In an embodiment of the present application, the following steps are further included:

[0020] Arranging the information of the domain service to obtain the information of the interface protocol interacting with the port of the new plug-in adapter;

[0021] According to the information of the interface protocol, the new plug-in adapter interacts with the vehicle cloud data collection system, and the vehicle cloud data collection system collects and parses the new type of vehicle data.

[0022] In an embodiment of the present application, the information of the interface protocol interacting with the port of the plurality of plug-in adapters comprises the following steps:

[0023] Obtaining the port information of a warehouse adapter;

[0024] Obtaining the port information of a collection rule adapter;

[0025] Obtaining the port information of a front-end user interface adapter; and

[0026] Obtaining the port information of an external system adapter.

[0027] In an embodiment of the present application, the information of the interface protocol interacting with the ports of the plurality of plug-in adapters comprises the following steps:

[0028] According to the port information of the warehouse adapter, the port information of the collection rule adapter, the port information of the front-end user interface adapter and the port information of the external system adapter, the information of the domain service is arranged, and the information of the interface protocol interacting with the ports of the warehouse adapter, the ports of the collection rule adapter, the ports of the front-end user interface adapter and the ports of the external system adapter is obtained.

[0029] The present application provides a vehicle cloud data acquisition system architecture obtaining device, the device comprises:

[0030] A use case obtaining module is configured to obtain information of a plurality of business use cases of the vehicle cloud data acquisition system architecture by analyzing business requirements of the vehicle cloud data acquisition system architecture.

[0031] A domain model obtaining module is configured to split the information of the plurality of business use cases, and obtain information of a domain model of the vehicle cloud data acquisition system architecture and information of a plurality of business concepts in the domain model.

[0032] A domain service obtaining module is configured to split the functions to be implemented by the plurality of business concepts into steps, and obtain information of a domain service of the vehicle cloud data acquisition system architecture.

[0033] An interface protocol obtaining module is configured to arrange the information of the domain service, and obtain information of an interface protocol interacting with ports of a plurality of plug-in adapters.

[0034] An interaction module is configured to interact, according to the information of the interface protocol, the plurality of plug-in adapters with the vehicle cloud data acquisition system.

[0035] The present application provides an electronic device, the electronic device comprises:

[0036] At least one processor;

[0037] A storage device is configured to store at least one program, when the at least one program is executed by the at least one processor, the electronic device implements the vehicle cloud data acquisition system architecture obtaining method of any one of the above.

[0038] The present application provides a computer readable storage medium, characterized in that a computer program is stored thereon, when the computer program is executed by a processor of a computer, the computer executes the vehicle cloud data acquisition system architecture obtaining method of any one of the above.

[0039] The application has the advantages that: the application supports multiple types of data to be added in the form of plug-in adapters, so as to achieve collection and analysis of data in different formats. When a new data type is accessed, only a new plug-in adapter needs to be implemented for interactive connection, which has the advantages of reuse of key components and flexible expansion. Meanwhile, under the premise of ensuring reliable and stable operation of the vehicle cloud data collection system, the system meets various complex and frequently changing business demand scenarios, which is beneficial to prolong the system life cycle and reduce the maintenance cost of the system.

[0040] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory and are not restrictive of the application. BRIEF DESCRIPTION OF DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application. It is clear that the drawings in the following description are only some embodiments of the application, and other drawings can be obtained from these drawings without creative labor for those skilled in the art. In the drawings:

[0042] Figure 1 is a schematic diagram of an application environment of an acquisition method of a vehicle cloud data collection system architecture according to an exemplary embodiment of the application;

[0043] Figure 2 is a flowchart of an acquisition method of a vehicle cloud data collection system architecture according to an exemplary embodiment of the application;

[0044] Figure 3 is a flowchart of an acquisition method of a business use case according to an exemplary embodiment of the application;

[0045] Figure 4 is a flowchart of an acquisition method of a business concept according to an exemplary embodiment of the application;

[0046] Figure 5 is a flowchart of a data collection method after access of a new type of data according to an exemplary embodiment of the application;

[0047] Figure 6 is a structural schematic diagram of an acquisition device of a vehicle cloud data collection system architecture according to an exemplary embodiment of the application.

[0048] Figure 7 shows a structural schematic diagram of a computer system of an electronic device suitable for implementing embodiments of the application. DETAILED DESCRIPTION

[0049] The objectives, technical contents and effects of the present application can be further understood by the following detailed description of the preferred embodiment with reference to the drawings. It is understood that the detailed description and specific examples, while indicating preferred embodiments of the application, are given by way of illustration only, since various changes and modifications within the spirit of the application will become apparent to those skilled in the art from this detailed description.

[0050] It is to be understood that the drawings are designed solely for the purpose of illustration and are not intended to limit the scope of the present application.

[0051] In the following description, numerous specific details are discussed in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one of ordinary skill in the art that the embodiments of the present application can be practiced without these specific details. In other instances, well-known structures and devices are not described in detail in order to avoid obscuring the embodiments of the present application.

[0052] First of all, it should be noted that the software architecture is a series of related abstract patterns used to guide the design of various aspects of a large software system. The software architecture is a sketch of a system, and the object described by the software architecture is an abstract component that directly constitutes the system. The connection between components explicitly and relatively elaborately describes the communication between components. In the implementation phase, these abstract components are refined into actual components, such as specific classes or objects. In the object-oriented field, the connection between components is usually implemented by interfaces. When a complex business system needs to be built, not only a stable technical architecture needs to be built from a technical point of view, but also a business architecture needs to be built to ensure that the system can meet the business requirements. DDD (Domain Driven Design) integrates the technical architecture and the business architecture, which can reflect the business of the system and guide the development of technical code.

[0053] Domain-driven design can split complex problems, split the correlation between each subsystem, and how each subsystem works and how they are connected, helping us solve the principles that large complex systems should follow when landing. Among them, domain-driven design is an idea of driving system design by domain model, where domain model is an abstraction of business model, domain model carries the attributes and specific behaviors of business, and is a method of business expression. And the domain model is a class with properties, including setting properties and getting properties. Among them, the business behavior operation is also in the model class, which is called data transfer object. Among them, the domain model includes three types of entities, value objects, and services. The layered structure of domain-driven design includes the user interface layer, the application layer, the domain layer, and the basic implementation layer.

[0054] Figure 1 is an application environment diagram of the acquisition method of the vehicle cloud data collection system architecture shown by an exemplary embodiment of the present application. As shown in Figure 1 some embodiments, the vehicle cloud data collection system architecture acquisition module 110 acquires the vehicle cloud data collection system architecture according to the business requirements of the vehicle cloud data collection system architecture, the relationship between the business requirements, and the steps of implementing the functions required to implement the business requirements. The technical personnel 120 design the technical architecture according to the vehicle cloud data collection system architecture, complete the vehicle cloud data collection system, i.e., the vehicle cloud data collection application 130. The three-party service 140 includes data storage, collection rules, user interfaces, and three-party data analysis systems. The vehicle cloud data collection application 130 is connected through the interface of the vehicle cloud data collection application 130, transmits data to the vehicle cloud data collection application 130, or calls data in the vehicle cloud data collection application 130. The embodiments of the present application do not limit the specific role of the vehicle cloud data collection system architecture acquisition module 110, Figure 1 The vehicle cloud data collection application 130 shown in FIG. 13 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Basic cloud computing services, etc. Here, no limitation is made. The mutual transmission of data between the vehicle cloud data collection application 130 and the three-party service 140 can be operated through 3G (third-generation mobile information technology), 4G (fourth-generation mobile information technology), 5G (fifth-generation mobile information technology), etc. Wireless network, the embodiments of the present application do not limit this, which can be set according to actual needs.

[0055] In some embodiments, existing data acquisition software designed through software architecture tends to be designed for a specific protocol, which makes the data acquisition only identify parameter data in a specific protocol format, and when new data specifications need to be collected and parsed, key components cannot be directly reused and expanded flexibly. To solve these problems, embodiments of the present application respectively propose a vehicle cloud data acquisition system architecture acquisition method, device, equipment and medium, which will be described in detail below.

[0056] Please refer to Figure 2 , Figure 2 is a flowchart of a vehicle cloud data acquisition system architecture acquisition method according to an example embodiment of the present application. In some embodiments, the method can be applied to the implementation environment shown in Figure 1 and specifically executed by the vehicle cloud data acquisition system architecture acquisition module 110 in the implementation environment. It should be understood that the method can also be applied to other example implementation environments and specifically executed by devices in other implementation environments, and the present embodiment does not limit the implementation environment to which the method is applied.

[0057] For example, the vehicle cloud data acquisition system architecture acquisition module 110 to which the vehicle cloud data acquisition system architecture acquisition method disclosed in the present embodiment is applied can be installed with an SDK (Software Development Kit, software development kit, a collection of development tools for a specific software package, software framework, operating system, etc. when developing application software), and the method disclosed in the present embodiment is specifically implemented as one or more functions provided by the SDK.

[0058] As shown in Figure 2 , in an example embodiment, the vehicle cloud data acquisition system architecture acquisition method includes at least steps S210 to S250, which are described in detail as follows:

[0059] Step S210: Through analysis of the business requirements of the vehicle cloud data acquisition system, information of a plurality of business use cases of the vehicle cloud data acquisition system is acquired.

[0060] First of all, it is necessary to analyze the business requirements of the vehicle cloud data acquisition system architecture, and then divide the boundaries of the vehicle cloud data acquisition system, so as to extract business use cases. Business use cases express the user's requirements for the vehicle cloud data acquisition system, define the boundaries of the vehicle cloud data acquisition system and the scenarios of system interaction between external roles and the vehicle cloud data acquisition system. The main business use cases in the system include business use cases for collecting various specifications of data uploaded by vehicles, business use cases for identifying vehicle-mounted data, and business use cases for parsing and processing data.

[0061] The boundary of the vehicle cloud data collection system is a bounded context, which defines the application scope of the model.

[0062] In step S220, the information of the plurality of business use cases is split to obtain the information of the domain model of the vehicle cloud data collection system architecture and the information of the plurality of business concepts within the domain model.

[0063] Through the splitting of the business use cases, the key problems in the business use cases are obtained, and the domain concepts of the vehicle cloud data collection system are extracted therefrom. Then, the concept model is obtained according to the domain concepts, and the concept model is converted into the domain model. The domain model is obtained by brainstorming and experiments, thereby abstracting the business concepts used in the vehicle cloud data collection system. The business concepts include structured data concepts, semi-structured data concepts, and unstructured data concepts.

[0064] The domain model is an abstraction of a domain with a certain boundary. The domain model only reflects the business and is independent of the task technology implementation, and reflects the essence of the business requirements of the users in the domain. In the present application, the domain model is an abstraction of the business concepts in the vehicle cloud data collection system.

[0065] In step S230, the functions to be implemented by the plurality of business concepts are step-split to obtain the information of the domain services of the vehicle cloud data collection system architecture.

[0066] Through the step-splitting of the functions to be implemented by the business requirements represented by the business concepts of the vehicle cloud data collection system architecture, a plurality of steps included in the functions to implement the business requirements are obtained. Then, the plurality of steps are refined to extract a plurality of key steps, and the plurality of key steps are corresponded to the vehicle cloud data collection system. In this way, the plurality of key steps to implement the business requirements are refined into the capabilities possessed by the domain services. Moreover, the capabilities have atomicity, which can ensure that the capabilities in the domain services are single and indivisible, and a plurality of domain services can be called to implement a task specific to a certain domain.

[0067] The domain service has three features. The first feature is to emphasize a stateless operation, and the state should be maintained in the entity. The domain service handles a stateless logical process. The second feature is to implement a task of a certain domain, and to do something within the domain boundary. The domain service is not an application service, and the application service is a customer side of the domain service, such as an API (Application Programming Interface) aggregation service. The application service does not do something within the domain. The third feature is to consider the modeling of an aggregation or a value object first. If an operation is not suitable for being placed on the aggregation or the value object, the domain service is used. The domain service refers to an abstraction of a function that can be completed by the vehicle cloud data acquisition system. The domain service is a collection of all core business functions that can be completed by the system. The domain service includes intelligent identification, transmission, monitoring, preprocessing, and management of data.

[0068] In step S240, information of the domain service is arranged, and information of an interface protocol for interacting with ports of the plurality of plug-in adapters is obtained.

[0069] The capability provided by the domain service has atomicity, so it is necessary to adapt the business requirements of the vehicle cloud data acquisition system architecture by arranging and combining the domain service. The vehicle cloud data acquisition system architecture includes a domain layer, an application program layer (application layer), and a plug-in adaptation layer. The domain layer is an extraction of core business objects and core business logic of the vehicle cloud data acquisition system, and includes domain objects and domain services. The domain layer is only responsible for expressing business concepts, business state information, and business rules. The domain objects include domain models. The application program layer has the responsibility of organizing and arranging the domain objects and the domain services. The plug-in adaptation layer includes a plurality of plug-in adapters. Because the application layer and the domain layer do not care about specific technologies used, only the input object data is obtained, and the output object data information required by the interfaces of the plug-in adapters is aggregated and constructed. Therefore, after obtaining the port information of the plurality of plug-in adapters, such as the port information of the warehouse adapter, the port information of the acquisition rule adapter, the port information of the front-end user interface adapter, and the port information of the external system adapter, the interface protocol for interacting with the ports of the plurality of plug-in adapters is established in the application program layer by arranging the domain service, and the data specifications of the input and output items are specified. This has the advantage that the modules are decoupled, thereby achieving single responsibility, supporting data acquisition and uploading of various data rules, and supporting interaction functions with different systems. When new data needs to be parsed or changed, the plug-in adapters can be flexibly expanded, and the key components can be reused and flexibly expanded.

[0070] The plug-in adapter layer includes a warehouse adapter, a collection rule adapter, a front-end UI (User Interface) adapter, and an external system adapter. The warehouse adapter mainly interacts with a data storage, which includes a relational database, a non-relational database, and a file, etc. The collection rule adapter adapts different specifications of data formats according to a uniform interaction interface specification provided by the application layer, and interacts with the application layer after the adaptation of the data, so as to achieve the purpose that multiple different data formats can be recognized by the system and subsequent business processing. The front-end UI adapter is at the same level as the collection rule adapter, and is used for the display and interaction of different data types, and is used for displaying data on the front-end UI interface or uploading data to the vehicle cloud data collection system. The external system adapter is mainly used for data interaction and function calling with other systems.

[0071] In step S250, the multiple plug-in adapters interact with the vehicle cloud data collection system according to the information of the interface protocol.

[0072] The vehicle cloud data collection system is arranged on the application program layer. In order to convert the input and output items of other systems or third-party services into a data format that can be recognized by the application program layer and the domain layer, the multiple plug-in adapters should be converted according to the interface specification formulated by the application program layer through the plug-in adapters, so that the collected data in different formats can be recognized and processed by the vehicle cloud data collection system. The third-party services mainly refer to services that are different from the application program layer and the domain layer of the most core business logic processing part of the vehicle cloud data collection system, and mainly include data storage, data collection rules, UI interfaces, and third-party systems. In this way, when processing data, the most stable part of the system is the domain layer and the application program layer. After the software design is completed, this part as the most core part can be rarely modified or even not modified. Because of the existence of the internal interaction interface protocol, changes mainly occur in the plug-in adapter layer, and the main responsibility of the plug-in adapter layer is to adapt the externally changed data to data conforming to the internal interface specification, so that when a new data needs to be collected, the plug-in adapter layer only needs to convert the data to be collected into data that can be recognized by the internal interface protocol. At this time, the data flow flows from the plug-in adapter layer to the application program layer, and the business is processed through the domain service. The plug-in adapter and the vehicle cloud data collection system interact through the interface protocol, which is not only limited to collecting multiple different formats of data generated by multiple third-party services, but also can realize the interaction of the UI interface, the data storage, and the data analysis of the third-party data analysis system through the similar plug-in adapter.

[0073] Figure 3 is a flowchart of a business use case acquisition method according to an example embodiment of the present application. As shown in FIG. 1, the method includes the following steps. Figure 3As shown in the exemplary embodiment, the business case acquisition method includes at least steps S310 to S330, which are described in detail as follows:

[0074] Step S310, acquiring information of business requirements of the vehicle cloud data acquisition system.

[0075] Step S320, acquiring boundary information of the vehicle cloud data acquisition system by analyzing the information of business requirements.

[0076] The boundary of the vehicle cloud data acquisition system is a bounded context, which defines the application scope of the model.

[0077] Step S330, acquiring information of multiple business cases by dividing the boundary of the vehicle cloud data acquisition system.

[0078] The main business cases in the vehicle cloud data acquisition system include business cases of collecting various specifications of data uploaded by vehicles, business cases of identifying vehicle-mounted data, and business cases of analyzing and processing data.

[0079] Figure 4 is a flowchart of the business concept acquisition method shown in an exemplary embodiment of the present application. As shown in the exemplary embodiment, Figure 4 the business concept acquisition method includes at least steps S410 to S420, which are described in detail as follows:

[0080] Step S410, acquiring information of key issues in the business case by splitting the multiple business cases.

[0081] Step S420, acquiring information of the domain model by extracting the information of the key issues in the business case.

[0082] Among them, by splitting the business case, the key issues in the business case are acquired, and the domain concept of the vehicle cloud data acquisition system is extracted therefrom. Then, the concept model is obtained according to the domain concept, and the concept model is converted into the domain model. The domain model is an abstraction of a domain with a certain boundary, and the domain model only reflects the business and is independent of the task technology implementation, reflecting the essence of the business requirements of the users in the domain. In the present application, it is an abstraction of the business concept in the vehicle cloud data acquisition system.

[0083] Figure 5 is a flowchart of the data acquisition method after the new type of data access shown in an exemplary embodiment of the present application. As shown in the exemplary embodiment, Figure 5 the data acquisition method after the new type of data access includes at least steps S510 to S530, which are described in detail as follows:

[0084] Step S510, acquiring the new type of vehicle data.

[0085] The new type of vehicle data can be acquired by the external third-party service, such as the automatic navigation system, and the automatic navigation system can generate the new type of vehicle data.

[0086] Step S520, acquiring the port information of the new plug-in adapter matched with the new type of vehicle data.

[0087] The automatic navigation adapter, i.e. the new plug-in adapter, can be matched with the automatic navigation system.

[0088] Step S530, arranging the information of the domain service, and acquiring the information of the interface protocol interacting with the port of the new plug-in adapter.

[0089] The capability provided by the domain service is atomic, so the arrangement and combination of the domain service are needed to adapt to the business requirement of the vehicle cloud data acquisition system architecture, and the interface protocol interacting with the port of the new plug-in adapter is acquired.

[0090] Step S540, according to the information of the interface protocol, the new plug-in adapter interacts with the vehicle cloud data acquisition system, and the vehicle cloud data acquisition system acquires and analyzes the new type of vehicle data.

[0091] According to the interface protocol interacting with the port of the new plug-in adapter, the new plug-in adapter interacts with the vehicle cloud data acquisition system, the vehicle cloud data acquisition system acquires and analyzes the new type of data, and the third-party service can also call the vehicle data in the vehicle cloud data acquisition system.

[0092] Figure 6 is a structural schematic diagram of an acquisition device of a vehicle cloud data acquisition system architecture according to an example embodiment of the present application. The device can be applied to Figure 1 the application environment shown, and is specifically configured in the acquisition module 110 of the vehicle cloud data acquisition system architecture. The device can also be applied to other example implementation environments, and is specifically configured in other devices, and the implementation environment to which the device is applied is not limited in the present embodiment.

[0093] As Figure 6 shown, the example data security storage device includes:

[0094] The use case acquisition module 610 is configured to acquire information of a plurality of business use cases of the vehicle cloud data collection system architecture by analyzing business requirements of the vehicle cloud data collection system architecture; the domain model acquisition module 620 is configured to split the information of the plurality of business use cases to acquire information of a domain model of the vehicle cloud data collection system architecture and information of a plurality of business concepts in the domain model; the domain service acquisition module 630 is configured to split steps of functions to be implemented by the plurality of business concepts to acquire information of a domain service of the vehicle cloud data collection system architecture; the interface protocol acquisition module 640 is configured to arrange the information of the domain service to acquire information of an interface protocol for port interaction of the plurality of plug-in adapters; and the interaction module 650 is configured to interact the plurality of plug-in adapters with the vehicle cloud data collection system according to the information of the interface protocol.

[0095] Figure 7 A structural schematic diagram of a computer system of an electronic device suitable for implementing the embodiments of the present application is shown. It should be noted that, Figure 7 The computer system 700 of the electronic device shown is only an example and should not impose any limitation on the functions and use range of the embodiments of the present application.

[0096] As Figure 7 shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 702 or programs loaded from a storage portion 708 into a random access memory (RAM) 703, such as performing the methods described in the above embodiments. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0097] The following components are connected to the I / O interface 705: an input part 706 including a keyboard, a mouse, etc.; an output part 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc.; a storage part 708 including a hard disk, etc.; and a communication part 709 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication part 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as necessary. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 710 as necessary, so that a computer program read out therefrom is installed in the storage part 708 as necessary.

[0098] In particular, according to embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing a computer program for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, various functions defined in the system of the present application are executed.

[0099] It should be noted that the computer-readable medium in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium may, for example, be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this application, the computer-readable signal medium can include a data signal propagated in a baseband or as a carrier wave in a propagated data signal, in which the computer-readable computer program is carried. Such a propagated data signal can take on many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate, or transmit the program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted in any suitable medium, including but not limited to wireless, wired, or the like, or any suitable combination thereof.

[0100] The flowcharts and block diagrams in the drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Each block in the flowcharts or block diagrams can represent a module, a program segment, or a portion of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in a different order than that shown in the figures. For example, two blocks noted in succession can actually be executed substantially concurrently, or they can sometimes be executed in reverse order, depending on the functionality involved. It should also be noted that each block in the flowcharts or block diagrams, and combinations of blocks in the flowcharts or block diagrams, can be implemented by special-purpose hardware-based systems, which perform the specified functions or operations, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0101] The units described in the embodiments of the present application can be implemented in the form of software, or can be implemented in the form of hardware, and the described units can also be arranged in a processor. In some cases, the names of the units do not constitute a limitation on the units themselves.

[0102] Another aspect of the present application also provides a computer readable storage medium, which stores a computer program. The computer program is executed by a processor of a computer, so that the computer executes the acquisition method of the vehicle cloud data collection system architecture as described above. The computer readable storage medium can be included in the electronic device described in the above embodiments, or can exist separately and not be assembled into the electronic device.

[0103] Another aspect of the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the acquisition method of the vehicle cloud data collection system architecture provided in each of the above embodiments.

[0104] The above embodiments only exemplarily illustrate the principles and effects of the present application, and are not used to limit the present application. Any person skilled in the art can modify or change the above embodiments without departing from the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by those skilled in the art without departing from the spirit and technical thought of the present application should be covered by the claims of the present application.

Claims

1. A method for acquiring the architecture of a vehicle cloud data acquisition system, characterized in that, The method comprises: obtaining boundary information of the vehicle cloud data collection system through analysis of business requirements of the vehicle cloud data collection system; and obtaining information of multiple business use cases of the vehicle cloud data collection system through division of the boundary of the vehicle cloud data collection system; splitting the information of multiple business use cases to obtain information of a domain model of a vehicle cloud data collection system architecture and information of multiple business concepts in the domain model; splitting the functions to be implemented by the multiple business concepts to obtain information of a domain service of the vehicle cloud data collection system architecture; arranging the information of the domain service to obtain information of an interface protocol for port interaction with multiple plug-in adapters; and According to the information of the interface protocol, multiple plug-in adapters interact with the vehicle cloud data collection system; wherein the plug-in adapter is used to adapt external changing data to data conforming to internal interface specifications; obtain new types of vehicle data; obtain port information of a new plug-in adapter matching the new types of vehicle data; arrange the information of the domain service to obtain information of an interface protocol for port interaction with the new plug-in adapter; according to the information of the interface protocol, the new plug-in adapter interacts with the vehicle cloud data collection system, and the vehicle cloud data collection system collects and parses the new types of vehicle data.

2. The method of claim 1, wherein the vehicle cloud data acquisition system architecture is obtained by: Obtaining information of a domain model of a vehicle cloud data collection system architecture comprises the following steps: Through splitting of multiple business use cases, information of key problems in the business use cases is obtained; Through extraction of the information of key problems in the business use cases, information of the domain model is obtained, which is used to reflect business requirements of users in the domain.

3. The method of claim 1, wherein the vehicle cloud data acquisition system architecture is acquired by: Obtaining information of an interface protocol for port interaction with multiple plug-in adapters comprises the following steps: obtaining port information of a warehouse adapter; obtaining port information of a collection rule adapter; obtaining port information of a front-end user interface adapter; and obtaining port information of an external system adapter.

4. The method of claim 3, wherein the vehicle cloud data acquisition system architecture is acquired by, Obtaining information of an interface protocol for port interaction with multiple plug-in adapters comprises the following steps: According to the port information of the warehouse adapter, the port information of the collection rule adapter, the port information of the front-end user interface adapter, and the port information of the external system adapter, the information of the domain service is arranged to obtain information of an interface protocol for port interaction with the ports of the warehouse adapter, the ports of the collection rule adapter, the ports of the front-end user interface adapter, and the ports of the external system adapter.

5. An acquisition device of a vehicle cloud data collection system architecture, characterized in that, The device comprises: A use case acquisition module is configured to obtain boundary information of a vehicle cloud data collection system through analysis of business requirements of the vehicle cloud data collection system architecture; and obtain information of multiple business use cases of the vehicle cloud data collection system architecture through division of the boundary of the vehicle cloud data collection system. The domain model acquisition module is configured to split the information of the business use cases, acquire information of a domain model of the vehicle cloud data acquisition system architecture and information of a plurality of business concepts in the domain model. The domain service acquisition module is configured to split the functions to be implemented by the business concepts, acquire information of a domain service of the vehicle cloud data acquisition system architecture. The interface protocol acquisition module is configured to arrange the information of the domain service, and acquire information of an interface protocol for port interaction with a plurality of plug-in adapters. The interaction module is configured to interact with the vehicle cloud data acquisition system according to the information of the interface protocol, wherein the plug-in adapter is configured to adapt external changed data into data conforming to internal interface specifications, acquire new types of vehicle data, acquire port information of a new plug-in adapter matching the new types of vehicle data, arrange the information of the domain service, acquire information of an interface protocol for port interaction with the new plug-in adapter, and interact with the vehicle cloud data acquisition system according to the information of the interface protocol, so that the vehicle cloud data acquisition system acquires and parses the new types of vehicle data. 6.An electronic device, comprising: at least one processor; a storage device configured to store at least one program, which, when executed by the at least one processor, causes the electronic device to implement the acquisition method of the vehicle cloud data acquisition system architecture according to any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, a computer program stored thereon, which, when executed by a processor of a computer, causes the computer to implement the acquisition method of the vehicle cloud data acquisition system architecture according to any one of claims 1 to 4.

Images