CN117201524A

CN117201524A - Communication method, device and equipment among multiple domain controllers in vehicle

Info

Publication number: CN117201524A
Application number: CN202210603680.0A
Authority: CN
Inventors: 尹磊; 刘刚; 胡雄飞
Original assignee: WM Smart Mobility Shanghai Co Ltd
Current assignee: WM Smart Mobility Shanghai Co Ltd
Priority date: 2022-05-30
Filing date: 2022-05-30
Publication date: 2023-12-08

Abstract

The embodiment of the disclosure provides a communication method, a device and equipment among a plurality of domain controllers in a vehicle. The method comprises the following steps: determining the character attribute of each of the plurality of domain controllers; a domain controller with a role attribute of a server side in the plurality of domain controllers sends a service state to a domain controller with a role attribute of a client side; the domain controller with the character attribute of the client sends a service request to the domain controller with the character attribute of the server according to the service state; the domain controller with the character attribute of the service end responds to the service request. In this way, on the premise that the role attribute of the domain controller is still unchanged, the server side can be enabled to change phases to request some services to the client side, so that service limitation brought to the domain controller due to limitation of the role attribute is relieved, and normal communication between different domain controllers can be achieved.

Description

Communication method, device and equipment among multiple domain controllers in vehicle

Technical Field

The present disclosure relates to the field of communications, and in particular, to the field of domain controller technology.

Background

At present, when a plurality of domain controllers in a vehicle communicate with each other, some domain controllers can only be used as clients (for example, an android system which can only be used as clients is applied) due to the limitation of software, and some domain controllers can only be used as servers, so that the domain controller used as a server cannot request a certain service from the domain controller used as a client, and thus, the normal communication between the domain controllers is influenced, and the domain controller used as a server is limited.

Disclosure of Invention

The present disclosure provides a communication method, apparatus, device, and storage medium between a plurality of domain controllers in a vehicle.

According to a first aspect of the present disclosure, a method of communication between a plurality of domain controllers in a vehicle is provided.

The method comprises the following steps:

determining the character attribute of each of the plurality of domain controllers, wherein the character attribute comprises a server or a client;

a domain controller with a role attribute of a server side in the plurality of domain controllers sends a service state to a domain controller with a role attribute of a client side;

the domain controller with the character attribute of the client sends a service request to the domain controller with the character attribute of the server according to the service state;

and the domain controller with the character attribute of the service end responds to the service request.

The embodiment can enable the server to change the phase to request some services to the client by sending the service state to the client and then enabling the client to continue according to a request-response mode on the premise that the role attribute of the domain controller is still unchanged, so that service limitation brought to the domain controller due to limitation of the role attribute is relieved, and normal communication between different domain controllers can be achieved.

In the aspect and any possible implementation manner described above, there is further provided an implementation manner, where the sending, by the domain controller of the client, a service request to the domain controller of the server by the role attribute according to the service state includes:

and the domain controller with the character attribute of the client sends a service request to the domain controller with the character attribute of the server according to the service state and the user request.

In this embodiment, the domain controller with the role attribute being the client may automatically send a service request to the domain controller with the role attribute being the server according to the service state and the user request, so that the domain controller with the role attribute being the server may freely and flexibly request a certain service from the domain controller as the client, so as to avoid that the domain controller as the server cannot request the service due to the limitation of the role attribute, and remove the design limitation on the in-vehicle communication service.

In the aspect and any possible implementation manner described above, there is further provided an implementation manner, where the sending, by a domain controller having a role attribute of a server, a service state to a domain controller having a role attribute of a client includes:

and the domain controller with the character attribute being a service end broadcasts the service state to the domain controller with the character attribute being a client end at one time.

In this embodiment, the domain controller with the role attribute being the server may broadcast the service status to the domain controller with the role attribute being the client at a time, so that the domain controller with the role attribute being the client may comprehensively understand various services that the server may provide, and thus, no matter what kind of service is requested by the client to the server, what kind of service is requested by the server to the client in a phase change manner.

Aspects and any one of the possible implementations as described above, further providing an implementation, the method further including:

and classifying and sequencing the service states when the service states comprise a plurality of items.

When the service states have a plurality of items, the service states can be automatically classified and ordered, so that the client can accurately send requests to the server according to requirements.

When sorting, sorting can be performed according to the receiving time of the service state;

when classifying, the radar service states can be classified according to different types, for example, when the service states are the service states of different radars and the service states of different cameras, the service states of the radars can be classified into one type, and the service states of the cameras can be classified into one type.

In accordance with aspects and any one of the possible implementations described above, there is further provided an implementation in which the plurality of domain controllers employ an ethernet-based SOMEIP communication scheme therebetween.

Compared with CAN communication, the SOMEIP communication mode based on the Ethernet has larger data quantity and higher transmission speed, so that more data CAN be transmitted between different domain controllers more quickly.

Aspects and any one of the possible implementations as described above, further provide an implementation, the service state includes:

a providable service, whether the providable service is abnormal or not, and whether the providable service is started or not.

Aspects and any one of the possible implementations as described above, further provide an implementation, the plurality of domain controllers including: an intelligent driving area controller and an intelligent cabin area controller.

For the specific division of the functional domains, each automobile host manufacturer can be divided into a plurality of different domains according to the design concept difference of the automobile host manufacturer. For example, BOSCH is divided into 5 domains: power domain (Power Train), chassis domain (Chassis), body domain (Body/Comfort), cabin domain (cockpi/Infotainment), autopilot Domain (ADAS). This is the most classical five-domain centralized EEA. Of course, some manufacturers further fuse the original power domain, chassis domain and vehicle body domain into the whole vehicle control domain on the basis of the five-domain centralized architecture.

Intelligent driving domain controller (ADC, adas\ AD Domain Controller), intelligent cockpit domain controller (CDC, cockpit Domain Controller).

According to a second aspect of the present disclosure, there is provided a communication device between a plurality of domain controllers in a vehicle.

The device comprises:

a determining module, configured to determine a role attribute of each of the plurality of domain controllers, where the role attribute includes a server or a client;

the domain controllers with the character attribute of the server side are used for sending service states to the domain controllers with the character attribute of the client side;

the domain controller with the character attribute being a client side is used for sending a service request to the domain controller with the character attribute being a server side according to the service state;

the role attribute is a domain controller of the service end and is used for responding to the service request.

According to a third aspect of the present disclosure, an electronic device is provided. The electronic device includes: a memory and a processor, the memory having stored thereon a computer program, the processor implementing the method as described above when executing the program.

According to a fourth aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a method according to the first and/or second aspects of the present disclosure.

In the present disclosure, after determining the role attribute of each of a plurality of domain controllers, a domain controller with a role attribute being a server sends service states to a domain controller with a role attribute being a client, so that the domain controller of the client can freely send service requests to the domain controller with the role attribute being a server according to the service states, and then the domain controller with the role attribute being the server responds to the service requests, so that the server can send the service states to the client and then continue to request services to the client according to a request-response mode by the client on the premise that the role attribute of the domain controller is still unchanged, thereby eliminating service restrictions brought to the domain controller due to the restriction of the role attribute and enabling normal communication between different domain controllers.

It should be understood that what is described in this summary is not intended to limit the critical or essential features of the embodiments of the disclosure nor to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The above and other features, advantages and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. For a better understanding of the present disclosure, and without limiting the disclosure thereto, the same or similar reference numerals denote the same or similar elements, wherein:

FIG. 1 illustrates a flow chart of a method of communication between multiple domain controllers in a vehicle, according to an embodiment of the disclosure;

FIG. 2 illustrates a flow chart of another method of communication between multiple domain controllers in a vehicle in accordance with an embodiment of the present disclosure;

FIG. 3 illustrates a flow chart of a method of communication between a plurality of domain controllers in a vehicle in accordance with an embodiment of the present disclosure;

FIG. 4 illustrates a block diagram of a communication device between multiple domain controllers within a vehicle according to an embodiment of the disclosure;

fig. 5 illustrates a block diagram of an exemplary electronic device capable of implementing embodiments of the present disclosure.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments in this disclosure without inventive faculty, are intended to be within the scope of this disclosure.

In addition, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Fig. 1 illustrates a flow chart of a method 100 of communication between multiple domain controllers in a vehicle according to an embodiment of the disclosure. The method 100 may include:

step 110, determining respective character attributes of the plurality of domain controllers, wherein the character attributes comprise a server side or a client side;

step 120, the domain controller with the character attribute of the server side in the plurality of domain controllers sends a service state to the domain controller with the character attribute of the client side; domain controllers are known as (DCU, domain Control Unit).

Step 130, the domain controller with the character attribute being a client sends a service request to the domain controller with the character attribute being a server according to the service state;

and 140, responding to the service request by the domain controller of the service end by the character attribute.

After determining the role attribute of each of the domain controllers, the domain controller with the role attribute as the service end sends service states to the domain controller with the role attribute as the client end, so that the domain controller of the client end can freely send service requests to the domain controller with the role attribute as the service end according to the service states, and then the domain controller with the role attribute as the service end responds to the service requests, so that the service end can realize the request of some services to the client end by sending the service states to the client end and then continuing according to a request-response mode by the client end on the premise that the role attribute of the domain controller is unchanged, thereby eliminating service restrictions brought to the domain controller due to the restriction of the role attribute and enabling normal communication between different domain controllers.

For example: the AEB (Autonomous Emergency Braking, automatic braking system) emergency braking function of the intelligent driving domain controller is closed, if the intelligent driving domain controller is in an on state, according to the normal logic, the intelligent driving domain controller can be used as a client to send an opening request to the intelligent cabin domain controller, and then the intelligent cabin domain controller is opened, but because the intelligent cabin domain controller is a host and is applicable to an android system which can only be used as a client, the intelligent driving domain controller can only be used as a server, so that the intelligent driving domain controller can not send a request to the intelligent cabin system, and can not request to start emergency braking function service; the intelligent driving domain controller can send the state that the AEB emergency braking function service is closed to the intelligent cabin domain controller through the intelligent driving domain controller, and then the intelligent cabin domain controller requests the intelligent driving domain controller to start the emergency braking function service by utilizing the identity of the client, so that the intelligent driving domain controller serving as a service end changes phases on the premise of not changing the role attributes of the intelligent driving domain controller and the intelligent cabin domain controller, and the emergency braking function service is requested to be started.

In some embodiments, the sending, by the domain controller with the role attribute being the client, a service request to the domain controller with the role attribute being the server according to the service state includes:

The domain controller with the character attribute being the client can automatically send a service request to the domain controller with the character attribute being the server according to the service state and the user request, so that the domain controller with the character attribute being the server can freely and flexibly request a certain service to the domain controller as the client in a variable way, the situation that the domain controller as the server cannot request the service because of the limitation of the character attribute is avoided, and the design limitation of the communication service in the vehicle is relieved.

In some embodiments, sending, by the domain controller with the role attribute of the server, the service status to the domain controller with the role attribute of the client includes:

The domain controller with the role attribute of the service end can broadcast the service state to the domain controller with the role attribute of the client end at one time, so that the domain controller with the role attribute of the client end can comprehensively know various services which can be provided by the service end, and the service end can request which service from the service end no matter what service is requested from the client end, which service is requested from the client end in a changing way.

In some embodiments, the method further comprises:

In some embodiments, the plurality of domain controllers use a SOMEIP communication manner based on ethernet.

SOME/IP (Scalable service-Oriented MiddlewarE over IP) is a concept introduced by in-vehicle Ethernet communications and is located above layer 4 of the OSI 7 layer model.

Of course, the plurality of domain controllers may also communicate using a simpler communication protocol such as UDP (User Datagram Protocol ).

In some embodiments, the service state comprises:

In some embodiments, the plurality of domain controllers comprises: an intelligent driving area controller and an intelligent cabin area controller.

The technical solution of the present disclosure will be described in further detail below with reference to fig. 2 and 3:

taking an example that an intelligent cabin domain controller (intelligent cabin system) can only be used as a client and an intelligent driving domain controller (intelligent driving system) can only be used as a server, in order to relieve the limitation of service requests of the intelligent driving domain controller as the server, a communication mode shown in fig. 2 can be adopted for communication, so that the domain controller as the server can still realize the request of various services under the condition that the character attribute is unchanged.

Taking an example that an intelligent cabin domain controller (intelligent cabin system) can only serve as a service end and an intelligent driving domain controller (intelligent driving system) can only serve as a client end, in order to relieve service request limitation of the intelligent cabin domain controller serving as the service end, communication can be performed in a communication mode shown in fig. 3, so that the domain controller serving as the service end can still realize requesting various services under the condition that character attributes are unchanged.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present disclosure is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present disclosure. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required by the present disclosure.

The foregoing is a description of embodiments of the method, and the following further describes embodiments of the present disclosure through examples of apparatus.

Fig. 4 illustrates a block diagram of a communication system 400 between multiple domain controllers within a vehicle according to an embodiment of the disclosure. As shown in fig. 4, the system 400 includes:

a determining module 410, configured to determine respective role attributes of the plurality of domain controllers, where the role attributes include a server or a client;

a domain controller 420 with a role attribute of a server among the plurality of domain controllers, configured to send a service state to a domain controller with a role attribute of a client;

the domain controller 430 with the role attribute being a client is configured to send a service request to the domain controller with the role attribute being a server according to the service state;

the role attribute is a domain controller 420 of the server, and is configured to respond to the service request. It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the described modules may refer to corresponding procedures in the foregoing method embodiments, which are not described herein again.

The present disclosure also provides, in accordance with embodiments of the present disclosure, an electronic device and a non-transitory computer-readable storage medium storing computer instructions. Fig. 5 shows a schematic block diagram of an electronic device 500 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

The device 500 comprises a computing unit 501 that may perform various suitable actions and processes in accordance with a computer program stored in a Read Only Memory (ROM) 502 or loaded from a storage unit 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the device 500 can also be stored. The computing unit 501, ROM 502, and RAM 503 are connected to each other by a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.

Various components in the device 500 are connected to the I/O interface 505, including: an input unit 506 such as a keyboard, a mouse, etc.; an output unit 507 such as various types of displays, speakers, and the like; a storage unit 508 such as a magnetic disk, an optical disk, or the like; and a communication unit 509 such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The computing unit 501 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 501 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as method 100. For example, in some embodiments, the method 100 may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 508. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 500 via the ROM 502 and/or the communication unit 509. When the computer program is loaded into RAM 503 and executed by computing unit 501, one or more steps of method 100 described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform the method 100 by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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 or 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 of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.

The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. A method of communication between a plurality of domain controllers in a vehicle, comprising:

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the domain controller with the character attribute being a client sends a service request to the domain controller with the character attribute being a server according to the service state, and the method comprises the following steps:

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the sending, by the domain controller with the role attribute of the server, the service state to the domain controller with the role attribute of the client, includes:

4. The method according to claim 1, wherein the method further comprises:

5. The method of claim 1, wherein the step of determining the position of the substrate comprises,

and SOMEIP communication mode based on Ethernet is adopted among the plurality of domain controllers.

6. The method of claim 1, wherein the service state comprises:

7. The method according to any one of claim 1 to 6, wherein,

the plurality of domain controllers includes: an intelligent driving area controller and an intelligent cabin area controller.

8. A communication system between a plurality of domain controllers in a vehicle, comprising:

9. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

10. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-7.