Vehicle calling method and device based on service-oriented architecture, equipment and medium

Abstract

The embodiment of the invention relates to the technical field of vehicles, and discloses a vehicle calling method, device and equipment based on a service-oriented architecture and a medium, and the method comprises the steps that a vehicle-mounted man-machine interaction control module responds to user operation and serves as a service user to send a calling control request to a vehicle-mounted communication terminal control module; the vehicle-mounted communication terminal control module serves as a service provider, responds to the call control request and controls the vehicle-mounted communication terminal to execute corresponding call operation; the vehicle-mounted communication terminal control module is used as a service user and sends call state information to the vehicle-mounted man-machine interaction control module; the vehicle-mounted man-machine interaction control module serves as a service provider and controls the vehicle-mounted screen to execute corresponding display operation based on the received call state information. By applying the technical scheme of the invention, decoupling of an integrated form of call service software and a bottom hardware controller is realized.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of vehicle technology, specifically to a vehicle calling method, apparatus, device, and medium based on a service-oriented architecture. Background Technology

[0002] Currently, automotive controllers are gradually evolving into domain controllers. For example, IVI (In-Vehicle Infotainment) and T-BOX (Telematics Box) are integrated into the CDC (Cockpit Domain Controller), or the T-BOX is integrated into the BDC (Body Domain Controller). Furthermore, some automakers are combining the T-BOX with automotive gateways to form new domain controllers. These different controller distributions and integration methods bring complexity and challenges to the design of vehicle call service systems. Summary of the Invention

[0003] In view of the above problems, embodiments of the present invention provide a vehicle calling method, apparatus, device and medium based on service-oriented architecture, which is used to solve the problems of complex design, poor stability and difficulty in adapting to different hardware platforms caused by the diverse integration forms of hardware controllers in the prior art.

[0004] According to one aspect of the present invention, a vehicle calling method based on a service-oriented architecture is provided, wherein the vehicle includes an in-vehicle communication terminal control module and an in-vehicle human-machine interaction control module, the method comprising:

[0005] The vehicle-mounted human-machine interaction control module responds to user operations and, as a service user, sends a call control request to the vehicle-mounted communication terminal control module.

[0006] The vehicle-mounted communication terminal control module, acting as a service provider, responds to the call control request and controls the vehicle-mounted communication terminal to perform the corresponding call operation.

[0007] The vehicle-mounted communication terminal control module, as a service user, sends call status information to the vehicle-mounted human-machine interaction control module;

[0008] The in-vehicle human-machine interaction control module acts as a service provider, controlling the in-vehicle screen to perform corresponding display operations based on the received call status information;

[0009] The vehicle communication terminal control module and the vehicle human-machine interaction control module communicate with each other based on a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0010] According to another aspect of the present invention, a vehicle calling device based on a service-oriented architecture is provided, including an in-vehicle communication terminal control module and an in-vehicle human-machine interaction control module.

[0011] The vehicle-mounted human-machine interaction control module is used to respond to user operations and, as a service user, send a call control request to the vehicle-mounted communication terminal control module.

[0012] The vehicle-mounted communication terminal control module is used as a service provider to control the vehicle-mounted communication terminal to perform corresponding call operations in response to the call control request.

[0013] The vehicle-mounted communication terminal control module is also used as a service user to send call status information to the vehicle-mounted human-machine interaction control module.

[0014] The in-vehicle human-machine interaction control module is also used as a service provider to control the in-vehicle screen to perform corresponding display operations based on the received call status information;

[0015] The vehicle communication terminal control module and the vehicle human-machine interaction control module communicate with each other based on a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0016] According to another aspect of the present invention, a vehicle calling device based on a service-oriented architecture is provided, comprising:

[0017] The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus.

[0018] The memory is used to store at least one executable instruction that causes the processor to perform the operation of the service-oriented architecture-based vehicle calling method as described above.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, the storage medium storing at least one executable instruction that causes a vehicle calling device / apparatus based on a service-oriented architecture to perform the operation of the vehicle calling method based on a service-oriented architecture as described above.

[0020] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0021] The above description is merely an overview of the technical solutions of the embodiments of the present invention. In order to better understand the technical means of the embodiments of the present invention and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0022] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0023] Figure 1 A flowchart illustrating a first embodiment of the vehicle calling method based on a service-oriented architecture provided by the present invention is shown.

[0024] Figure 2 A flowchart illustrating a second embodiment of the vehicle calling method based on a service-oriented architecture provided by the present invention is shown.

[0025] Figure 3 A schematic diagram of the architecture of the vehicle call system based on service-oriented architecture provided by the present invention is shown.

[0026] Figure 4 A schematic diagram of the interactive process for making a fault rescue call provided by the present invention is shown;

[0027] Figure 5 A schematic diagram of the interactive process for making an emergency rescue call provided by the present invention is shown;

[0028] Figure 6 A schematic diagram of an embodiment of the vehicle calling device based on a service-oriented architecture provided by the present invention is shown;

[0029] Figure 7 A schematic diagram of an embodiment of the vehicle calling device based on a service-oriented architecture provided by the present invention is shown;

[0030] Figure 8 A structural schematic diagram of an embodiment of the vehicle provided by the present invention is shown. Detailed Implementation

[0031] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. Although exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein.

[0032] Figure 1 A flowchart of a first embodiment of the vehicle calling method based on a service-oriented architecture of the present invention is shown, which can be executed by a domain controller in a vehicle.

[0033] The vehicle-mounted communication terminal control module is configured as the first service provider, providing atomic services for call operations and also serving as a user of atomic services for state updates. The vehicle-mounted human-machine interface control module is configured as the second service provider, providing atomic services for state updates and also serving as a user of atomic services for call operations. The vehicle-mounted communication terminal control module and the vehicle-mounted human-machine interface control module can be integrated into the same domain controller or deployed separately in different domain controllers. Figure 1 As shown, the method includes the following steps:

[0034] Step 110: In response to the user's operation, the vehicle-mounted human-machine interaction control module sends a call control request to the vehicle-mounted communication terminal control module as a service user.

[0035] In this embodiment of the invention, in response to an operation command initiated by a user via a touchscreen, physical button, or voice input, the vehicle-mounted human-machine interaction control module, as a service user, sends a call control request to the vehicle-mounted communication terminal control module according to a predefined communication interface specification. This request is essentially a call to the atomic service of the call operation. The request may encapsulate parameters such as call type (e.g., emergency rescue, breakdown assistance) and target number.

[0036] Step 120: The vehicle communication terminal control module, as a service provider, responds to the call control request and controls the vehicle communication terminal to perform the corresponding call operation.

[0037] In this step, the vehicle communication terminal control module, acting as a service provider, receives and parses the call control request. Subsequently, this module invokes its internally encapsulated call operation atomic service. This atomic service contains the specific driver logic for interacting with the underlying vehicle communication terminal hardware. By executing this logic, control of the vehicle communication terminal is ultimately achieved, enabling specific operations such as initiating a call, answering an incoming call, or hanging up a call.

[0038] Step 130: The vehicle communication terminal control module, as the service user, sends call status information to the vehicle human-machine interaction control module.

[0039] During a call or when the status changes, the vehicle communication terminal control module, as a service user, sends call status information to the vehicle human-machine interface control module. This information is a call to the status update atomic service, designed to notify the user interface to update its display.

[0040] Step 140: The vehicle-mounted human-machine interaction control module, as a service provider, controls the vehicle screen to perform corresponding display operations based on the received call status information; wherein, the vehicle-mounted communication terminal control module and the vehicle-mounted human-machine interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0041] In this step, the in-vehicle human-machine interaction control module, acting as a service provider, receives and parses the call status information. Subsequently, this module calls its internally encapsulated state update atomic service. This atomic service contains rendering and driving logic for interacting with the underlying display hardware (such as the LCD instrument panel and central control screen). By executing this logic, it ultimately controls the in-vehicle screen to perform corresponding graphics drawing and content update operations, thereby presenting the current call status to the user in real time and accurately.

[0042] It should be noted that the implementation of all the above interactions is based on the fact that all communication between the vehicle communication terminal control module and the vehicle human-machine interaction control module strictly follows the predefined service interface. This service interface predefines the service's identity, method identifier, events, and data format and type at the architectural design level. The definition of this interface is completely independent of the specific integration form of the vehicle's underlying hardware controller. This means that regardless of whether the relevant control module exists as an independent electronic control unit or is integrated into any domain controller or central computing unit, as long as its software implementation follows and exposes the same service interface, it can participate in system collaboration.

[0043] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0044] Figure 2 A flowchart illustrating another embodiment of the vehicle calling method based on a service-oriented architecture of the present invention is shown, which can be executed by a domain controller in the vehicle. The in-vehicle communication terminal control module and the in-vehicle human-machine interaction control module can be integrated in the same domain controller or deployed separately in different domain controllers. Figure 2 As shown, the method includes the following steps:

[0045] Step 210: In response to the user's operation, the vehicle-mounted human-machine interaction control module sends a call control request to the vehicle-mounted communication terminal control module as a service user.

[0046] In one alternative approach, the call control request is one of a call initiation request, a call answering request, or a call hang-up request, and the call is one of a fault rescue call, an emergency rescue call, or an information service call.

[0047] A call initiation request is used to instruct the vehicle-mounted communication terminal to establish a new communication link. A call answer request is used to instruct the vehicle-mounted communication terminal to answer an incoming call. A call hang-up request is used to instruct the vehicle-mounted communication terminal to release an existing communication link.

[0048] A breakdown call (B-CALL) is a specific type of call initiated by the user to request roadside assistance or repair services when a vehicle experiences a mechanical or electrical failure that does not endanger personal safety. This call is typically routed to the vehicle manufacturer's customer service center or a third-party roadside assistance service platform.

[0049] An emergency rescue call (E-CALL) is a high-priority call initiated manually by the user or automatically by vehicle sensors in the event of a major vehicle accident or an emergency that endangers personal safety, intended to request emergency medical, fire, or police assistance. This call typically enjoys network priority and is routed to a public safety answering point.

[0050] An information service call (I-CALL) is a call initiated by a user to obtain non-urgent commercial or informational services, such as requesting navigation destination settings, querying vehicle information, or booking a hotel or restaurant. This call is typically routed to the information service center of the car manufacturer or service provider.

[0051] Step 220: The vehicle communication terminal control module, as a service provider, responds to the call control request and controls the vehicle communication terminal to perform the corresponding call operation.

[0052] In one alternative approach, after controlling the in-vehicle communication terminal to perform the corresponding call operation, the vehicle call method based on a service-oriented architecture of the present invention may further include the following steps:

[0053] The vehicle-mounted communication terminal control module returns the call operation execution result to the vehicle-mounted human-machine interaction control module.

[0054] The call operation execution result is a feedback message characterizing the completion status of this call operation. The call operation execution result includes at least one operation status identifier, which indicates whether the call operation was successful or failed.

[0055] Step 230: The vehicle communication terminal control module, as the service user, periodically sends call status information to the vehicle human-machine interaction control module.

[0056] During call setup or execution, the vehicle-mounted communication terminal control module, as the service user, proactively and periodically sends call status information to the vehicle-mounted human-machine interface control module according to the predefined service interface specifications. This periodic reporting mechanism ensures the real-time performance and accuracy of the user interface display.

[0057] In one alternative approach, the call status information includes at least one of call type, call status, call mode, and call number.

[0058] Call type refers to the service category to which the current call or incoming call belongs, such as emergency rescue call, fault rescue call, etc. Call status refers to the specific stage or state of the current communication link. Call mode refers to the channel configuration mode of the current audio input / output. Call number refers to the peer number or service code identifier of the current call. This information constitutes the complete data foundation for updating the user interface.

[0059] Step 240: The vehicle-mounted human-machine interaction control module, as a service provider, controls the vehicle screen to perform corresponding display operations based on the received call status information; wherein, the vehicle-mounted communication terminal control module and the vehicle-mounted human-machine interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0060] In one alternative approach, the call status displayed on the in-vehicle screen includes one of the following: call initiation status, incoming call notification status, call connection status, or call termination status.

[0061] The call initiation status refers to the state in which the vehicle communication terminal has received and processed the call initiation request and is attempting to establish a communication link with a remote server or rescue center.

[0062] The incoming call notification status refers to the state when the vehicle communication terminal receives an incoming call request from the network side and notifies the vehicle human-machine interaction control module that a call is pending.

[0063] The call connection status refers to the state in which the communication link has been successfully established and two-way voice or data communication is taking place between the vehicle-mounted communication terminal and the remote end.

[0064] The call termination status refers to the state in which the current communication link has been actively released by one party or abnormally interrupted due to network reasons, and the call has completely ended.

[0065] In one alternative approach, after controlling the in-vehicle screen to perform the corresponding display operation, the vehicle calling method based on a service-oriented architecture of the present invention may further include the following steps:

[0066] The vehicle-mounted human-machine interaction control module returns the operation execution result to the vehicle-mounted communication terminal control module.

[0067] The result of the operation is a feedback message indicating the completion status of this interface update operation.

[0068] Reference Figure 3 The diagram shows the architecture of a service-oriented architecture-based vehicle calling system provided by this invention. The system includes an in-vehicle communication terminal control module and an in-vehicle human-machine interaction control module. The in-vehicle communication terminal control module provides atomic services for call operations and is also a user of atomic services for state updates. The in-vehicle human-machine interaction control module provides atomic services for state updates and is also a user of atomic services for call operations.

[0069] Reference Figure 4 The diagram shown illustrates the interactive process of making a fault rescue call provided by the present invention, including:

[0070] 1. When a user touches the B-CALL virtual button on the vehicle screen, the vehicle human-machine interaction control module sends a call initiation request to the vehicle communication terminal control module in response to the user's operation.

[0071] 2. In response to the call initiation request, the vehicle communication terminal control module controls the vehicle communication terminal to perform the corresponding call initiation operation, that is, to initiate a B-CALL, and returns the call operation execution result (call success or failure) to the vehicle human-machine interaction control module;

[0072] 3. After the vehicle-mounted communication terminal initiates a call, it continuously monitors the signaling feedback from the communication network and sends a status notification signal to the vehicle-mounted communication terminal control module. The vehicle-mounted communication terminal control module periodically sends call status information to the vehicle-mounted human-machine interaction control module based on the received status notification signal.

[0073] 4. The vehicle-mounted human-machine interaction control module controls the vehicle screen to perform corresponding display operations based on the received call status information, that is, to display call-related information on the vehicle screen and return the display operation execution result (status update success or failure) to the vehicle-mounted communication terminal control module.

[0074] 5. When the vehicle-mounted communication terminal attempts to establish a communication link with a remote server or rescue center, the vehicle screen displays that it is in call initiation status;

[0075] 6. When the communication link has been successfully established and two-way voice or data communication is taking place between the vehicle-mounted communication terminal and the remote end, the vehicle-mounted screen will display that the current call connection status is active.

[0076] 7. When the call ends, the user touches the B-CALL hang-up virtual button on the vehicle screen. In response to the user's operation, the vehicle human-machine interaction control module sends a call hang-up request to the vehicle communication terminal control module.

[0077] 8. In response to the call hang-up request, the vehicle communication terminal control module controls the vehicle communication terminal to perform the corresponding call hang-up operation, i.e. hang up the B-CALL, and returns the call operation execution result (hang-up successful or failed) to the vehicle human-machine interaction control module.

[0078] 9. After the vehicle-mounted communication terminal hangs up the call, the vehicle screen will display that the call has been terminated.

[0079] Reference Figure 5 The diagram shown illustrates the interactive process of making an emergency rescue call provided by the present invention, including:

[0080] 1. When a vehicle collision event is detected or a manual trigger signal is received from the user, the vehicle human-machine interaction control module sends a call initiation request to the vehicle communication terminal control module;

[0081] 2. In response to the call initiation request, the vehicle communication terminal control module controls the vehicle communication terminal to perform the corresponding call initiation operation, that is, to initiate an E-CALL, and returns the call operation execution result (call success or failure) to the vehicle human-machine interaction control module.

[0082] 3. After the vehicle-mounted communication terminal initiates a call, it continuously monitors the signaling feedback from the communication network and sends a status notification signal to the vehicle-mounted communication terminal control module. The vehicle-mounted communication terminal control module periodically sends call status information to the vehicle-mounted human-machine interaction control module based on the received status notification signal.

[0083] 4. The vehicle-mounted human-machine interaction control module controls the vehicle screen to perform corresponding display operations based on the received call status information, that is, to display call-related information on the vehicle screen and return the display operation execution result (status update success or failure) to the vehicle-mounted communication terminal control module.

[0084] 5. When the vehicle-mounted communication terminal attempts to establish a communication link with a remote server or rescue center, the vehicle screen displays that it is in call initiation status;

[0085] 6. When the communication link has been successfully established and two-way voice or data communication is taking place between the vehicle-mounted communication terminal and the remote end, the vehicle-mounted screen will display that the current call connection status is active.

[0086] 7. When the call ends, the user touches the E-CALL hang-up virtual button on the vehicle screen. In response to the user's operation, the vehicle human-machine interaction control module sends a call hang-up request to the vehicle communication terminal control module.

[0087] 8. In response to the call hang-up request, the vehicle communication terminal control module controls the vehicle communication terminal to perform the corresponding call hang-up operation, i.e. hang up the E-CALL, and returns the call operation execution result (hang-up successful or failed) to the vehicle human-machine interaction control module.

[0088] 9. After the vehicle-mounted communication terminal hangs up the call, the vehicle screen will display that the call has been terminated.

[0089] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0090] The vehicle communication terminal control module and the vehicle human-machine interaction control module collaborate based on predefined, hardware-decoupled service interfaces, thereby achieving flexibility and portability of the call function. By abstracting core functions into atomic services and defining standardized interfaces, the distribution, hardware architecture, and vendor differences of the underlying controllers are shielded. As long as the vehicle platform includes both the vehicle communication terminal control module and the vehicle human-machine interaction control module, the call function can be implemented by deploying the agreed-upon atomic services in the corresponding modules, significantly improving the system's versatility and compatibility across different platforms.

[0091] Figure 6 A schematic diagram of an embodiment of the vehicle calling device based on a service-oriented architecture of the present invention is shown. Figure 6 As shown, the device 600 includes: a vehicle communication terminal control module 610 and a vehicle communication terminal control module 620.

[0092] The vehicle-mounted human-machine interaction control module is used to respond to user operations and, as a service user, send call control requests to the vehicle-mounted communication terminal control module.

[0093] The vehicle-mounted communication terminal control module is used as a service provider to control the vehicle-mounted communication terminal to perform corresponding call operations in response to call control requests.

[0094] The vehicle-mounted communication terminal control module is also used as a service user to send call status information to the vehicle-mounted human-machine interaction control module.

[0095] The in-vehicle human-machine interaction control module is also used as a service provider to control the in-vehicle screen to perform corresponding display operations based on the received call status information;

[0096] The vehicle communication terminal control module and the vehicle human-machine interaction control module communicate based on a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0097] In one alternative approach, the vehicle-mounted communication terminal control module is specifically used for:

[0098] It periodically sends call status information to the vehicle-mounted human-machine interaction control module.

[0099] In one alternative approach, the call status information includes at least one of call type, call status, call mode, and call number.

[0100] In one alternative approach, the vehicle-mounted communication terminal control module is further used for:

[0101] Return the call operation execution result to the vehicle-mounted human-machine interaction control module.

[0102] In one alternative approach, the in-vehicle human-machine interaction control module is further used for:

[0103] The system returns the operation execution result to the vehicle-mounted communication terminal control module.

[0104] In one alternative approach, the call control request is one of a call initiation request, a call answering request, or a call hang-up request, and the call is one of a fault rescue call, an emergency rescue call, or an information service call.

[0105] In one alternative approach, the call status displayed on the in-vehicle screen includes one of the following: call initiation status, incoming call notification status, call connection status, or call termination status.

[0106] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0107] Figure 7 The diagram shows a structural schematic of an embodiment of the vehicle calling device based on a service-oriented architecture according to the present invention. The specific embodiments of the present invention do not limit the specific implementation of the vehicle calling device based on a service-oriented architecture.

[0108] like Figure 7 As shown, the vehicle calling device based on the service-oriented architecture may include: a processor 702, a communications interface 704, a memory 706, and a communication bus 708.

[0109] The processor 702, communication interface 704, and memory 706 communicate with each other via communication bus 708. Communication interface 704 is used to communicate with other network elements such as clients or other servers. Processor 702 executes program 710, specifically performing the relevant steps described above in the embodiment of the vehicle calling method based on a service-oriented architecture.

[0110] Specifically, program 710 may include program code, which includes computer-executable instructions.

[0111] Processor 702 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The vehicle calling device based on a service-oriented architecture may include one or more processors of the same type, such as one or more CPUs; or it may include processors of different types, such as one or more CPUs and one or more ASICs.

[0112] Memory 706 is used to store program 710. Memory 706 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0113] The device includes an in-vehicle communication terminal control module and an in-vehicle human-machine interaction control module. Specifically, program 710 can be called by processor 702 to enable the service-oriented architecture-based vehicle calling device to perform the following operations:

[0114] The vehicle-mounted human-machine interaction control module responds to user operations and, as a service user, sends a call control request to the vehicle-mounted communication terminal control module.

[0115] As a service provider, the vehicle communication terminal control module responds to call control requests and controls the vehicle communication terminal to perform corresponding call operations.

[0116] The vehicle communication terminal control module, as a service user, sends call status information to the vehicle human-machine interaction control module;

[0117] As a service provider, the in-vehicle human-machine interaction control module controls the in-vehicle screen to perform corresponding display operations based on the received call status information;

[0118] The vehicle communication terminal control module and the vehicle human-machine interaction control module communicate based on a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0119] In an alternative approach, program 710 is invoked by processor 702 to cause the service-oriented architecture-based vehicle calling device to perform the following operations:

[0120] The vehicle-mounted communication terminal control module periodically sends call status information to the vehicle-mounted human-machine interaction control module.

[0121] In one alternative approach, the call status information includes at least one of call type, call status, call mode, and call number.

[0122] In an alternative approach, program 710 is invoked by processor 702 to cause the service-oriented architecture-based vehicle calling device to perform the following operations:

[0123] The vehicle-mounted communication terminal control module returns the call operation execution result to the vehicle-mounted human-machine interaction control module.

[0124] In an alternative approach, program 710 is invoked by processor 702 to cause the service-oriented architecture-based vehicle calling device to perform the following operations:

[0125] The vehicle-mounted human-machine interaction control module returns the operation execution result to the vehicle-mounted communication terminal control module.

[0126] In one alternative approach, the call control request is one of a call initiation request, a call answering request, or a call hang-up request, and the call is one of a fault rescue call, an emergency rescue call, or an information service call.

[0127] In one alternative approach, the call status displayed on the in-vehicle screen includes one of the following: call initiation status, incoming call notification status, call connection status, or call termination status.

[0128] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0129] Figure 8A structural schematic diagram of an embodiment of the vehicle of the present invention is shown. (As shown) Figure 8 As shown, the vehicle 800 includes: sensors, one or more processors, and a communication interface;

[0130] Sensors are used to detect whether a vehicle has been involved in a collision.

[0131] The processor is used to execute the steps in the above embodiments of the vehicle calling method based on a service-oriented architecture.

[0132] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0133] This invention provides a computer-readable storage medium storing at least one executable instruction that, when executed on a vehicle calling device / apparatus based on a service-oriented architecture, causes the vehicle calling device / apparatus based on a service-oriented architecture to perform the vehicle calling method based on a service-oriented architecture in any of the above method embodiments.

[0134] The vehicle calling device / device based on the service-oriented architecture includes an in-vehicle communication terminal control module and an in-vehicle human-machine interaction control module. The executable instructions can be used to cause the vehicle calling device / device based on the service-oriented architecture to perform the following operations:

[0135] The vehicle-mounted human-machine interaction control module responds to user operations and, as a service user, sends a call control request to the vehicle-mounted communication terminal control module.

[0136] As a service provider, the vehicle communication terminal control module responds to call control requests and controls the vehicle communication terminal to perform corresponding call operations.

[0137] The vehicle communication terminal control module, as a service user, sends call status information to the vehicle human-machine interaction control module;

[0138] As a service provider, the in-vehicle human-machine interaction control module controls the in-vehicle screen to perform corresponding display operations based on the received call status information;

[0139] The vehicle communication terminal control module and the vehicle human-machine interaction control module communicate based on a predefined service interface, and the definition of the service interface is decoupled from the integration form of the vehicle's underlying hardware controller.

[0140] In one alternative approach, the executable instructions cause the service-oriented architecture-based vehicle calling device / device to perform the following operations:

[0141] The vehicle-mounted communication terminal control module periodically sends call status information to the vehicle-mounted human-machine interaction control module.

[0142] In one alternative approach, the call status information includes at least one of call type, call status, call mode, and call number.

[0143] In one alternative approach, the executable instructions cause the service-oriented architecture-based vehicle calling device / device to perform the following operations:

[0144] The vehicle-mounted communication terminal control module returns the call operation execution result to the vehicle-mounted human-machine interaction control module.

[0145] In one alternative approach, the executable instructions cause the service-oriented architecture-based vehicle calling device / device to perform the following operations:

[0146] The vehicle-mounted human-machine interaction control module returns the operation execution result to the vehicle-mounted communication terminal control module.

[0147] In one alternative approach, the call control request is one of a call initiation request, a call answering request, or a call hang-up request, and the call is one of a fault rescue call, an emergency rescue call, or an information service call.

[0148] In one alternative approach, the call status displayed on the in-vehicle screen includes one of the following: call initiation status, incoming call notification status, call connection status, or call termination status.

[0149] This invention, through abstracting the call function into independent atomic services and defining standardized interfaces, decouples the call service software from the underlying hardware controller integration, thus resolving the hardware platform diversity issues arising from the evolution of automotive electronic and electrical architecture towards domain controllers. This method allows the same service logic to seamlessly adapt to different hardware deployment schemes, significantly avoiding redundant development issues caused by hardware platform differences.

[0150] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Furthermore, the embodiments of this invention are not directed to any particular programming language.

[0151] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. Similarly, for the sake of brevity and to aid in understanding one or more aspects of the invention, in the description of exemplary embodiments of the invention above, various features of the embodiments are sometimes grouped together in a single embodiment, figure, or description thereof. The claims, which follow the detailed description, are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.

[0152] Those skilled in the art will understand that the modules in the device of the embodiment can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiment can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components, except that at least some of such features and / or processes or units are mutually exclusive.

[0153] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.

Claims

1. A vehicle call method based on a service-oriented architecture, characterized by, The vehicle comprises a vehicle communication terminal control module and a vehicle human-computer interaction control module, and the method comprises the following steps: The vehicle human-computer interaction control module sends a call control request to the vehicle communication terminal control module as a service user in response to a user operation; The vehicle communication terminal control module controls the vehicle communication terminal to perform a corresponding call operation as a service provider in response to the call control request; The vehicle communication terminal control module sends call state information to the vehicle human-computer interaction control module as a service user; The vehicle human-computer interaction control module controls the vehicle screen to perform a corresponding display operation as a service provider based on the received call state information; The vehicle communication terminal control module and the vehicle human-computer interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of a vehicle bottom-layer hardware controller.

2. The method of claim 1, wherein, The call state information is sent to the vehicle human-computer interaction control module periodically. The call state information comprises at least one of a call type, a call state, a call mode, and a call number.

3. The method of claim 2, wherein, After the vehicle communication terminal is controlled to perform a corresponding call operation, the method further comprises the following steps:

4. The method of claim 1, wherein, The vehicle communication terminal control module returns a call operation execution result to the vehicle human-computer interaction control module. After the vehicle screen is controlled to perform a corresponding display operation, the method further comprises the following steps:

5. The method of claim 1, wherein, The vehicle human-computer interaction control module returns a display operation execution result to the vehicle communication terminal control module. The call control request is one of a call initiation request, a call answer request, or a call hang-up request, and the call is one of a breakdown rescue call, an emergency rescue call, or an information service call.

6. The method according to any one of claims 1 to 5, characterized in that, The call state displayed on the vehicle screen comprises one of a call initiation state, an incoming call prompt state, a call connection state, or a call termination state.

7. The method according to any one of claims 1 to 5, characterized in that, The vehicle human-computer interaction control module is configured to send a call control request to the vehicle communication terminal control module as a service user in response to a user operation; 8. A vehicle call apparatus based on a service-oriented architecture, characterized by The vehicle communication terminal control module is configured to control the vehicle communication terminal to perform a corresponding call operation as a service provider in response to the call control request; The vehicle communication terminal control module is further configured to send call state information to the vehicle human-computer interaction control module as a service user; The vehicle human-computer interaction control module is further configured to control the vehicle screen to perform a corresponding display operation as a service provider based on the received call state information; The vehicle communication terminal control module and the vehicle human-computer interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of a vehicle bottom-layer hardware controller. The vehicle human-computer interaction control module is configured to send a call control request to the vehicle communication terminal control module as a service user in response to a user operation; The vehicle communication terminal control module is configured to control the vehicle communication terminal to perform a corresponding call operation as a service provider in response to the call control request; 9. A service-oriented architecture based vehicle call device, characterized by The vehicle communication terminal control module is further configured to send call state information to the vehicle human-computer interaction control module as a service user; The vehicle human-computer interaction control module is further configured to control the vehicle screen to perform a corresponding display operation as a service provider based on the received call state information; The vehicle communication terminal control module and the vehicle human-computer interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of a vehicle bottom-layer hardware controller. The vehicle human-computer interaction control module is configured to send a call control request to the vehicle communication terminal control module as a service user in response to a user operation; The vehicle communication terminal control module is configured to control the vehicle communication terminal to perform a corresponding call operation as a service provider in response to the call control request; The vehicle communication terminal control module is further configured to send call state information to the vehicle human-computer interaction control module as a service user; The vehicle human-computer interaction control module is further configured to control the vehicle screen to perform a corresponding display operation as a service provider based on the received call state information; The vehicle communication terminal control module and the vehicle human-computer interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of a vehicle bottom-layer hardware controller. The vehicle human-computer interaction control module is configured to send a call control request to the vehicle communication terminal control module as a service user in response to a user operation; The vehicle communication terminal control module is configured to control the vehicle communication terminal to perform a corresponding call operation as a service provider in response to the call control request; The vehicle communication terminal control module is further configured to send call state information to the vehicle human-computer interaction control module as a service user; The vehicle human-computer interaction control module is further configured to control the vehicle screen to perform a corresponding display operation as a service provider based on the received call state information; The vehicle communication terminal control module and the vehicle human-computer interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of a vehicle bottom-layer hardware controller. The vehicle human-computer interaction control module is configured to send a call control request to the vehicle communication terminal control module as a service user in response to a user operation; The vehicle communication terminal control module is configured to control the vehicle communication terminal to perform a corresponding call operation as a service provider in response to the call control request; The vehicle communication terminal control module is further configured to send call state information to the vehicle human-computer interaction control module as a service user; The vehicle human-computer interaction control module is further configured to control the vehicle screen to perform a corresponding display operation as a service provider based on the received call state information; The vehicle communication terminal control module and the vehicle human-computer interaction control module communicate according to a predefined service interface, and the definition of the service interface is decoupled from the integration form of a vehicle bottom-layer hardware controller. The memory is configured to store at least one executable instruction, which causes the processor to perform the operations of the method for vehicle call based on service-oriented architecture according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The storage medium has at least one executable instruction stored therein, which, when executed on the device / apparatus for vehicle call based on service-oriented architecture, causes the device / apparatus for vehicle call based on service-oriented architecture to perform the operations of the method for vehicle call based on service-oriented architecture according to any one of claims 1-7.

Images