Vehicle conference management method, system, device and storage medium

Abstract

The application provides a kind of vehicle meeting management method, system, equipment and storage medium, the method comprises: first domain controller obtains meeting invitation information by application message service, and based on voice prompt service voice broadcast meeting information;First domain controller identifies the first voice information collected by microphone by voice recognition service, obtains meeting reply information;In the case where meeting reply information is participation meeting, first domain controller determines meeting location by navigation service;In the case where the parking location determined by first domain controller through navigation service coincides with meeting location, first domain controller obtains the first service information sent by second domain controller and the second service information sent by third domain controller;In the case where first service information and second service information meet meeting conditions, first domain controller starts intelligent meeting mode function service to carry out vehicle meeting.Such, improve the safety and reliability of vehicle meeting.

Description

Technical Field

[0001] This application relates to the field of vehicle control, and more particularly to a method for managing vehicle-mounted conferencing, a vehicle management system, electronic equipment, and a computer-readable storage medium. Background Technology

[0002] With the rapid development of society and network technology, the forms of meetings are constantly evolving, from offline meetings to online meetings that are not limited by space. Because online meetings do not require a specific location, they have become an important meeting mode for improving work and study efficiency. For example, a vehicle, as a good communication space, can provide a suitable meeting place while traveling. Currently, vehicles can use in-vehicle conferencing systems to allow users to conduct online meetings without disrupting work. However, when users encounter online meetings that need to be handled promptly while driving, the need to concentrate on the meeting while driving may lead to driving accidents. Therefore, ensuring the safety of in-vehicle meetings for vehicle users has become a top priority. Summary of the Invention

[0003] In view of this, this application provides a method for managing in-vehicle conferencing, an in-vehicle management system, an electronic device, and a computer-readable storage medium. By invoking a re-arranged service, the vehicle can automatically enter an intelligent conferencing mode, allowing vehicle users to participate in online meetings in a safe and reliable vehicle environment, thereby improving the safety and reliability of vehicle users participating in in-vehicle conferencing.

[0004] In a first aspect, embodiments of this application provide a method for managing in-vehicle conferencing, which is applied to an in-vehicle management system with multiple domain controllers. The multiple domain controllers include at least a first domain controller, a second domain controller, and a third domain controller. The method includes:

[0005] The first domain controller obtains meeting invitation information through the application messaging service and broadcasts meeting inquiry information via voice prompt service;

[0006] The first domain controller identifies the first voice information collected by the microphone through the voice recognition service and obtains the meeting response information;

[0007] If the participant's response indicates that they are participating in the meeting, the first domain controller determines the participant's location through navigation services;

[0008] If the first domain controller determines that the parking location coincides with the meeting location through the navigation service, the first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller.

[0009] If the first and second service information meet the meeting conditions, the first domain controller will activate the intelligent meeting mode function service to conduct the in-vehicle meeting.

[0010] Secondly, embodiments of this application provide a vehicle management system, which may include a first domain controller, a second domain controller, and a third domain controller, wherein the first domain controller includes:

[0011] The inquiry information broadcasting module is used to obtain meeting invitation information through the application messaging service and broadcast the meeting inquiry information via voice based on the voice reminder service;

[0012] The response information acquisition module is used to identify the first voice information collected by the microphone through the voice recognition service and obtain the response information of the participants.

[0013] The meeting location acquisition module is used to determine the meeting location via navigation services when the meeting response information indicates participation in the meeting.

[0014] The service information acquisition module is used to acquire first service information sent by the second domain controller and second service information sent by the third domain controller when the parking location is determined to coincide with the meeting location through the navigation service.

[0015] The meeting function activation module is used to activate the intelligent meeting mode function service for in-vehicle meetings when the first service information and the second service information meet the meeting conditions.

[0016] Thirdly, embodiments of this application provide an electronic device, which includes a processor, a memory, and a vehicle conferencing management program stored in the memory and executable by the processor, wherein when the vehicle conferencing management program is executed by the processor, it implements the steps of the management program described in any embodiment of this application.

[0017] Fourthly, embodiments of this application provide a computer-readable storage medium, characterized in that the computer-readable storage medium stores a vehicle-mounted conferencing management program, wherein when the vehicle-mounted conferencing management program is executed by a processor, it implements the steps of the management program described in any embodiment of this application.

[0018] This application provides a method for managing in-vehicle conferencing, an in-vehicle management system, an electronic device, and a computer-readable storage medium. The first domain controller can obtain meeting invitations based on domain-internal application messaging services, thus promptly receiving meeting participation information. It can also use a voice reminder service to broadcast meeting inquiries, reducing the probability of vehicle users taking their eyes off the road and improving driving safety. Furthermore, the first domain controller uses a voice recognition service to recognize first voice information collected by the microphone to obtain meeting response information. This allows for timely retrieval of vehicle user responses via domain-internal services, eliminating the need for users to respond on the central control screen and reducing the risk of accidents while driving. When the response indicates participation, the first domain controller can automatically plan a safe and reliable meeting location using navigation services, ensuring user safety. Meanwhile, when the first domain controller determines that the parking location coincides with the meeting location through navigation services, the first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller. If the first service information and the second service information meet the meeting conditions, the first domain controller activates the intelligent meeting mode function service to conduct in-vehicle conferencing. Thus, the first domain controller can determine the status of other vehicle components through the service information, and if the status of other vehicle components meets the meeting conditions, the first domain controller activates the intelligent meeting mode function service to put the vehicle into intelligent meeting mode for in-vehicle conferencing. This allows vehicle users to conduct in-vehicle conferencing in a safe vehicle environment, improving the reliability and safety of the meeting. Attached Figure Description

[0019] To more clearly illustrate the specific embodiments of this application or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This illustration shows a structural diagram of an in-vehicle management system provided in an embodiment of this application;

[0021] Figure 2 This diagram illustrates a flowchart of a vehicle-mounted conferencing management method provided in an embodiment of this application.

[0022] Figure 3 This diagram illustrates a flow chart of another vehicle-mounted conferencing management method provided in an embodiment of this application.

[0023] Figure 4 This illustration shows a schematic diagram of another vehicle management system provided in an embodiment of this application;

[0024] Figure 5 This diagram illustrates the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] To make the above and other features and advantages of this application clearer, the application is further described below with reference to the accompanying drawings. It should be understood that the specific embodiments given herein are for the purpose of explanation to those skilled in the art, and are exemplary only, not restrictive.

[0026] In the following description, numerous specific details are set forth to provide a thorough understanding of this application. However, it will be apparent to those skilled in the art that the specific details are not required to practice this application. In other instances, well-known steps or operations have not been described in detail to avoid obscuring this application.

[0027] Currently, vehicles serve as excellent communication spaces, providing suitable meeting venues for people while traveling. However, when vehicle users encounter meetings that require immediate attention while driving, the low level of vehicle intelligence forces them to find suitable parking locations or estimate arrival times, leading to distracted driving, sudden acceleration or deceleration, or even running red lights. This can easily cause traffic accidents.

[0028] At the same time, the design of general in-vehicle functional systems is not conducive to the development and modification of functions according to user experience requirements. In addition, the process of modification requires a series of related controller logic or data signal changes, which does not support agile development, as well as subsequent function reconstruction and expansion, and cannot achieve a personalized user experience.

[0029] In view of this, this application, on the one hand, adopts SOA technology to construct an in-vehicle management system, that is, decoupling the functional software design architecture and splitting it into two service layers: a service layer and an application layer. Basic vehicle functions (intelligent meeting mode function switch, navigation, vehicle speed, vehicle status, seat control, window control, air conditioning control, voice reminders, information sharing between the vehicle and mobile phone, etc.) are transformed into service layer services, and service interface design is completed. Application layer services can call service layer services, thus enabling flexible arrangement and design of functional logic. Simultaneously, it decouples functional software between or within controllers, so that functional software no longer depends on other functional software and no longer uses fixed data signal communication for logical binding. Instead, it uses Ethernet dynamic connection technology to design service interfaces, allowing functional services to call basic services. This solves the binding problem of intelligent meeting mode functional software, allowing for unlimited reconfiguration according to user needs. Only the services used by the function need to be rearranged, while the service layer does not need to be changed or redesigned. This enables agile software development for intelligent meeting mode functions, saves development costs, and enhances functional scalability. In addition, the required basic services can be called up indefinitely to reorganize functions and complete the development and experience of new intelligent meeting modes.

[0030] On the other hand, the vehicle's intelligent meeting mode function can provide timely voice reminders before a meeting starts. After the vehicle user accepts the meeting, it automatically plans multiple reasonable parking routes based on the vehicle's current location and traffic conditions, offering the user more options. It can also monitor the vehicle's surroundings in real time to ensure a safe environment, automatically adjusting seats, windows, and air conditioning to provide a comfortable meeting environment. Simultaneously, basic services enable meeting information sharing between mobile and vehicle terminals, automatically reminding users and providing an intelligent driving experience while ensuring driving safety. This function can also quickly convert the vehicle into a meeting room mode, facilitating small meetings for occupants.

[0031] One embodiment of this application provides a vehicle management system. Figure 1 This diagram illustrates the structure of an in-vehicle management system according to an embodiment of this application. The in-vehicle management system is built based on Service-Oriented Architecture (SOA) technology, decoupling the functional software. Specifically, it splits the original functional software architecture into a two-layer software architecture: a service layer and an application layer. Each service layer can include multiple basic services, and each application layer can include one or more application functional services. A service is a functional unit of the functional software, possessing independent functionality. For example... Figure 1As shown, the vehicle management system 10 may include: a body control domain controller 11, an entertainment domain controller 12, a powertrain domain controller 13, and a gateway 14. The gateway 14 may include a switch, which can be used for data interaction between different domain controllers. It should be noted that the gateway 14 interacts via Ethernet data transmission, meaning that each domain controller needs to encapsulate the interaction data into Ethernet data format. Each domain controller can deploy and run a service layer. In addition, each domain controller can also deploy and run an application layer.

[0032] In addition, the vehicle management system may also include a navigation system, seat belt sensors, door lock controllers, window controllers, projector controllers, audio system, microphone, gear position sensor, vehicle speed sensor, air conditioning controller, seat controller, central control screen, and other functional sensors or controllers. This application does not limit the structure of the vehicle management system.

[0033] The seat controller is used to collect seat position information and send it to the domain controller, as well as to receive adjustment information sent by the seat adjustment service to control the seat.

[0034] The window controller is used to collect window position information and send it to the domain controller, as well as to receive adjustment information sent by the window adjustment service software to control the windows.

[0035] Seatbelt sensors can be used to collect the status information of vehicle seatbelts and send it to the domain controller.

[0036] A door lock controller can be used to detect the door lock status and send it to the domain controller, and it can also be used to receive control information sent by the door lock control service to control the door lock.

[0037] The projector controller can be used to collect the projector's status information and send it to the domain controller, as well as to receive control information sent by the projector adjustment service software to control the projector and project the meeting content onto the screen.

[0038] The speaker can be used to receive voice reminder messages sent by the voice reminder service.

[0039] A microphone can be used to collect the user's voice information, enabling the user to interact with the vehicle via voice.

[0040] A gear position sensor can be used to detect the gear position information of a vehicle.

[0041] A vehicle speed sensor can be used to detect vehicle speed information.

[0042] An air conditioning controller can be used to collect the status information of the air conditioner and send it to the domain controller, and receive adjustment information sent by the air conditioning control service to adjust the air conditioner.

[0043] The central control screen can be used to display various operating interfaces and prompts. The central control screen can be a display screen, including but not limited to a touchscreen.

[0044] Here, the service layer and the application layer represent two different levels of services. The application layer's functional services can call multiple services in the service layer. The service layer may include, but is not limited to, basic vehicle functional services, such as intelligent meeting mode on / off, navigation, vehicle speed, vehicle status, seat control, window control, air conditioning control, voice prompts, and information sharing between the in-vehicle and mobile devices. The application layer may include, but is not limited to, extended services, such as the intelligent meeting mode functional service.

[0045] The service layer and application layer of the vehicle management system are deployed and run differently in different domain controllers. For example... Figure 1 As shown, the intelligent meeting mode function switch service, voice reminder service, voice recognition service, navigation service, mobile terminal connection service, application message service, seat adjustment service, window adjustment service, seat belt status service, projector adjustment service, air conditioning service, gear position service, and vehicle speed service are respectively deployed in the body control domain controller 11, entertainment domain controller 12, and power domain controller 13.

[0046] Specifically, the vehicle body control domain controller 11 can run service-layer seat adjustment service, window adjustment service, seat belt status service, projector adjustment service, and door lock service. When running the seat adjustment service, the vehicle body control domain controller 11 can connect to the seat controller via the data bus to collect seat status information and adjust the seat position. When running the window adjustment service, the vehicle body control domain controller 11 can connect to the window controller via the data bus to collect window status information and adjust the window position. When running the seat belt status service, the vehicle body control domain controller 11 can connect to the seat belt sensor via the data bus to collect seat belt connection status information. When running the projector adjustment service, the vehicle body control domain controller 11 can connect to the projector controller via a hardwired connection to control the projector device. When running the door lock service, the vehicle body control domain controller 11 can connect to the door lock controller via the data bus to collect door lock status information and control the door locks.

[0047] The entertainment domain controller 12 can run intelligent meeting mode service, intelligent meeting mode on / off service, voice reminder service, voice recognition service, navigation service, mobile terminal connection service, application message service, SMS service, and email service. Specifically, when running the intelligent meeting mode service, the entertainment domain controller 12 can initiate intelligent meeting mode and participate in meetings. When running the mobile terminal connection service, the entertainment domain controller 12 can maintain information interaction between the vehicle terminal and mobile devices. When running the intelligent meeting mode on / off service, the entertainment domain controller 12 can recognize the user's setting status of the switch on the central control screen and obtain the setting information of the function switch. When running the voice reminder service, after obtaining application messages from the meeting software on the vehicle terminal or mobile device, the entertainment domain controller 12 can connect to the speakers via a hardwired connection to control the speakers to play application messages, thereby reminding the user. When running the voice recognition service, the entertainment domain controller 12 can connect to the microphone via a hardwired connection to control the microphone to collect user voice information, thereby enabling voice control of vehicle services and enhancing user safety during driving. When running the navigation service, the entertainment domain controller 12 can quickly plan parking routes through the navigation system. When running the application messaging service, the entertainment domain controller 12 can subscribe to software message pushes in real time. When running the SMS and / or email service, the entertainment domain controller 12 can notify other participants in the meeting via SMS and / or email when a user declines a meeting invitation.

[0048] The powertrain domain controller 13 can run service-layer gear position service, vehicle speed service, and air conditioning service. Specifically, when running the gear position service, the powertrain domain controller 13 can connect to the gear position sensor via the data bus to collect gear position status information. When running the vehicle speed service, the powertrain domain controller can connect to the vehicle speed sensor via the data bus to collect vehicle speed information. When running the air conditioning service, the powertrain domain controller can connect to the air conditioning controller via the data bus to collect air conditioning status information and adjust the air conditioning status.

[0049] In addition, each domain controller may include other vehicle services. Furthermore, the vehicle management system may also include other domain controllers, such as open connectivity domain controllers and information security domain controllers.

[0050] It should be noted that the mobile device in this embodiment can be an electronic product with a display screen, such as a mobile phone, tablet, or laptop. The mobile device may be equipped with a communication connection module for communicating with the vehicle management system, such as a Bluetooth module, a 4G module, a 5G module, or a Wi-Fi module, to complete information interaction and data collection between the vehicle and the mobile device. The mobile device is equipped with conferencing software, which can synchronize information with the conferencing software of the vehicle management system.

[0051] In the above embodiments, by employing SOA technology to build the vehicle management system, the functional software can be restructured. When implementing intelligent conferencing functions, only the required services need to be arranged according to a certain logic, thus eliminating the need for changes or redesigns to the service layer. This allows for agile development of functional services, saving development costs and enhancing functional scalability. Furthermore, the required basic services can be infinitely called for functional reorganization, enabling the development and experience of new intelligent conferencing modes.

[0052] Another aspect of this application provides a method for managing in-vehicle conferencing, which can be applied to, for example... Figure 1 The vehicle management system shown. Figure 2 This illustration shows a flowchart of a vehicle-mounted conferencing management method according to an embodiment of this application. Figure 2 As shown, the management method for this in-vehicle conference may include, but is not limited to, the following steps:

[0053] S21, the first domain controller obtains the meeting invitation information through the application messaging service and broadcasts the meeting inquiry information via voice based on the voice reminder service;

[0054] S22, the first domain controller recognizes the first voice information collected by the microphone through the voice recognition service and obtains the meeting response information;

[0055] S23, if the response information for the meeting is "participation in the meeting", the first domain controller determines the meeting location through the navigation service;

[0056] S24, if the first domain controller determines that the parking location and the meeting location coincide through the navigation service, the first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller.

[0057] S25, if the first service information and the second service information meet the meeting conditions, the first domain controller starts the intelligent meeting mode function service to conduct the in-vehicle meeting.

[0058] The steps described above are described in detail below.

[0059] In S21, the first domain controller can be the entertainment domain controller. The application messaging service can be a service for obtaining information from application software. The meeting invitation message can be a message sent by the conferencing software, used to instruct the current vehicle user to participate in a meeting. The meeting inquiry message can be used to inquire whether the current vehicle user wishes to participate in the meeting.

[0060] In this embodiment, the participant initiates a meeting invitation through the meeting software. The first domain controller of the vehicle management system reads the meeting invitation information on the meeting software through the application messaging service, and controls the speaker to broadcast the meeting inquiry information through the voice reminder service, asking the current vehicle user whether to participate in the meeting.

[0061] In S22, the speech recognition service can recognize the first speech information using natural language processing technology to obtain computer language information. The first speech information is the speech information of the current vehicle user responding to a meeting inquiry. The meeting response information is computer language information obtained based on the first speech information and recognizable by the first domain controller. The meeting response information can indicate whether the user is participating in the meeting or not.

[0062] In this embodiment, after the first domain controller controls the audio system to broadcast the meeting inquiry information through the voice reminder service, it activates the microphone to collect the first voice information of the current vehicle user's response to the meeting inquiry information, and identifies the first voice information through the voice recognition service to obtain the meeting response information that can be recognized by the first domain controller.

[0063] In S23, navigation services can refer to services provided by a navigation system. Navigation services may include, but are not limited to, planning vehicle routes and finding safe and reliable parking locations. The meeting location can be the current vehicle user's location for attending the meeting. The meeting location can be the destination of this trip or a safe and reliable location along the way.

[0064] In this embodiment of the application, when the first domain controller recognizes that the response information indicates participation in the meeting, the first domain controller can determine the meeting location based on the meeting time, vehicle speed, and destination location through the navigation service, so that the current vehicle user can participate in the meeting in a safe and reliable location in a timely manner.

[0065] In S24, the overlap between the parking location and the meeting location can be understood as the vehicle parking at the meeting location. The second domain controller can be a powertrain domain controller. The third domain controller can be a body domain controller. The first service information can be information sent by the service corresponding to the second domain controller. The first service information may include, but is not limited to, vehicle speed information and gear information. The second service information can be information sent by the service corresponding to the third domain controller. The second service information may include, but is not limited to, seatbelt status information. Both the first and second service information are in Ethernet format and can be sent to the first domain controller through a gateway.

[0066] In this embodiment, when the vehicle arrives at the meeting location and parks, the first domain controller determines that the meeting location coincides with the parking location through navigation services. It then sends status query information to the second and third domain controllers via a gateway to query the vehicle's gear position, speed, and seatbelt status. The second and third domain controllers retrieve the gear position, speed, and seatbelt status information through relevant services and encapsulate them into first service information and second service information, respectively. The second and third domain controllers then send the first and second service information to the first domain controller via the gateway, allowing the first domain controller to obtain the first and second service information.

[0067] In S25, meeting conditions can be the prerequisites for vehicle users to participate in a meeting. The intelligent meeting mode function service can be used to put the vehicle into meeting mode, so that vehicle users can isolate themselves from the external environment and participate in in-vehicle meetings safely and comfortably. Meeting mode can adjust the seat to a comfortable position, close the windows, lock the doors, adjust the air conditioning to a comfortable temperature, and project the meeting software content onto the screen.

[0068] In the above embodiments, the first domain controller can obtain meeting invitations based on the domain-internal application messaging service, thereby receiving meeting information in a timely manner. It can also use a voice reminder service to announce meeting inquiries, reducing the probability of vehicle users taking their eyes off the road and improving driving safety. Furthermore, the first domain controller uses a voice recognition service to recognize the first voice information collected by the microphone to obtain the meeting response information. This allows it to promptly obtain the vehicle user's response by calling the domain-internal service, eliminating the need for the vehicle user to reply on the central control screen and reducing the risk during driving. If the meeting response indicates participation, the first domain controller can automatically plan a safe and reliable meeting location using the navigation service, ensuring the user's safety during the meeting. Meanwhile, when the first domain controller determines that the parking location coincides with the meeting location through navigation services, the first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller. If the first service information and the second service information meet the meeting conditions, the first domain controller activates the intelligent meeting mode function service to conduct in-vehicle conferencing. Thus, the first domain controller can determine the status of other vehicle components through the service information, and if the status of other vehicle components meets the meeting conditions, the first domain controller activates the intelligent meeting mode function service to put the vehicle into intelligent meeting mode for in-vehicle conferencing. This allows vehicle users to conduct in-vehicle conferencing in a safe vehicle environment, improving the reliability and safety of the meeting.

[0069] In some embodiments, before the first domain controller obtains the meeting invitation information through the application messaging service and broadcasts the meeting inquiry information via voice prompt service in S21, the management method of the in-vehicle meeting may further include:

[0070] The first domain controller establishes a connection with mobile devices within the vehicle space based on the mobile connectivity service.

[0071] Here, the vehicle management system and mobile devices can communicate bidirectionally. For example, they can establish a connection through communication methods such as Bluetooth, 4G, 5G, and Wi-Fi. The mobile connection service can activate the communication module of the vehicle management system to establish a connection with the mobile device, allowing the vehicle management system and the mobile device to exchange information.

[0072] In this embodiment, the meeting invitation information can be sent by conferencing software on a mobile device or by conferencing software on an in-vehicle device. That is, the first domain controller establishes a connection with the vehicle user's mobile device based on the mobile connectivity service. After establishing the connection, the first domain controller can obtain the meeting invitation information sent by the conferencing software on the mobile device or the in-vehicle device through the application messaging service and announce the meeting invitation information aloud. Thus, by calling the application layer service within the domain, information sharing between the in-vehicle device and the mobile device can be achieved, allowing the vehicle management system to obtain meeting information in a timely manner. Furthermore, calling the voice announcement service can automatically play the meeting information, serving as a reminder to the vehicle user, bringing an intelligent driving experience, and ensuring driving safety.

[0073] When vehicle users encounter meetings that require immediate attention while driving, they need to find a suitable parking location on their own and estimate the time it will take to reach the parking spot. This can lead to distracted driving, various unexpected driving situations, and easily cause traffic accidents, endangering the safety of vehicle users.

[0074] Therefore, in some embodiments, S23, when the meeting response information is "participation in the meeting," the first domain controller determines the meeting location through a navigation service, which may include:

[0075] If the response information indicates participation in the meeting, the first domain controller uses the navigation service to determine the chronological relationship between the meeting time and the arrival time at the destination of this trip;

[0076] If the meeting start time is earlier than the destination arrival time, the first domain controller plans multiple intermediate parking locations through the navigation service, determines the intermediate parking location as the meeting location, and announces the meeting information at the parking location based on the voice reminder service.

[0077] If the meeting time is later than the arrival time at the destination, the destination location of this trip will be determined as the meeting location, and the meeting will be announced to the attendee at the destination location via voice reminder service.

[0078] Here, the meeting time refers to the time you participate in this meeting, which can be obtained from the meeting software. The arrival time of the destination for this trip can be determined by the navigation service based on the distance between the current vehicle location and the destination location, as well as the driving speed. The order of the meeting time and the arrival time of the destination can include the meeting time being earlier than the arrival time, or the meeting time being later than the arrival time.

[0079] Intermediate stops can be located between the start and end points of the trip. Intermediate stops can be on the route or slightly off-route. All intermediate stops must be safe and secure locations.

[0080] In this embodiment, the meeting start time being earlier than the destination arrival time can be understood as the vehicle being unable to reach the destination before the meeting, thus preventing it from attending the meeting at the destination location. Therefore, for safe participation, the first domain controller sends meeting location query information to the navigation service. The navigation service plans multiple parking routes based on the current vehicle location, determines several suitable intermediate parking locations, and sends the intermediate parking location information to the first domain controller. The first domain controller then broadcasts the information about the required intermediate parking locations via a voice reminder service, so that vehicle users are aware of the need to stop midway to safely participate in the meeting.

[0081] The meeting location can be one of several intermediate parking locations. Preferably, the meeting location can be the parking location closest to the current vehicle location.

[0082] In this embodiment, the meeting start time being later than the destination arrival time can be understood as the vehicle arriving at the destination before the meeting begins, meaning the vehicle user can attend the meeting at the destination location. Therefore, the first domain controller uses the destination location of the current trip as the meeting location and controls the audio system to announce that the meeting can be attended at the destination location via a voice reminder service, so that the vehicle user knows the meeting location and can drive with peace of mind.

[0083] It should be noted that, in this embodiment of the application, the vehicle user can be a user in any seat of the vehicle.

[0084] In the above embodiments, the domain controller calls the navigation service to automatically calculate the chronological relationship between the arrival time of the destination and the meeting time, and determines the meeting location based on this relationship, ensuring that vehicle users can attend the meeting in a safe and reliable location. Furthermore, by automatically planning multiple parking locations using the navigation service, the goal is to eliminate the need for vehicle users to manually search for parking during the journey, reducing dangerous driving behaviors and improving driving safety.

[0085] In some embodiments, after the first domain controller plans multiple intermediate parking locations through navigation services and determines these locations as meeting locations, the first domain controller can control the central control screen to display the available intermediate parking location information. Vehicle users can select these locations via voice or on the central control screen. The first domain controller then uses the intermediate parking location selected by the vehicle user as the departure meeting location. This ensures that the meeting location meets both safety requirements and the user's personalized needs.

[0086] In some embodiments, S24, if the first domain controller determines through navigation services that the parking location coincides with the meeting location, the first domain controller obtains first service information sent by the second domain controller and second service information sent by the third domain controller, including:

[0087] If the first domain controller determines that the vehicle's location coincides with the meeting location through the navigation service, the first domain controller sends the first indication information that the vehicle has arrived at the meeting location to the second and third domain controllers.

[0088] Upon receiving the first instruction information, the second domain controller obtains gear information and vehicle speed information based on gear service and vehicle speed service respectively, encapsulates the gear information and vehicle speed information into first service information, and sends it to the first domain controller.

[0089] Upon receiving the first instruction information, the third domain controller obtains the seat belt status information based on the seat belt status service, encapsulates the seat belt status information into second service information, and sends it to the first domain controller.

[0090] The first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller through the gateway.

[0091] Here, the first indication information can be used to instruct the vehicle to arrive at the meeting location. In this embodiment, the second domain controller is connected to the gear position sensor and the vehicle speed sensor via a data bus. Upon receiving the first indication information, the second domain controller collects the gear position information detected by the gear position sensor through the gear position service, and collects the vehicle speed information detected by the vehicle speed sensor through the vehicle speed service. Since information interaction with the first domain controller needs to be conducted through a gateway, the second domain controller encapsulates the gear position information and vehicle speed information into first service information and sends it to the first domain controller via the gateway.

[0092] In this embodiment, the third domain controller is connected to the seatbelt sensor via a data bus. Upon receiving the first indication information, the third domain controller collects the seatbelt status information detected by the seatbelt sensor through the seatbelt status service. Since information exchange with the first domain controller needs to be conducted through a gateway, the third domain controller encapsulates the seatbelt status information into first service information and sends it to the first domain controller via the gateway.

[0093] It should be noted that the installation of status information, gear information, and vehicle speed information all fall under the category of vehicle status information.

[0094] In the above embodiment, the vehicle's status information is collected through the services of the other two domains and encapsulated as service information. The first domain controller obtains the service information through the gateway, thereby the first domain controller can determine the current status of the vehicle, so as to provide a basis for judging whether the vehicle status is suitable for holding a meeting.

[0095] In some embodiments, the first service information includes vehicle speed information and gear information, and the second service information includes seat belt status information. S25, if the first and second service information meet the meeting conditions, the first domain controller initiates the intelligent meeting mode function service to conduct an in-vehicle meeting, including:

[0096] When the first service information and the second service information meet the conditions that the vehicle is in park, the vehicle speed is zero, and the seat belt is off, the first domain controller starts asking for information based on the voice reminder service and the voice broadcast conference mode.

[0097] The first domain controller identifies the second voice information based on the voice recognition service and obtains the conference mode status information.

[0098] When the meeting mode status information is "meeting mode enabled", the first domain controller starts the intelligent meeting mode function service to conduct in-vehicle meetings.

[0099] Here, meeting conditions may include the vehicle being in park, at zero speed, and with the seatbelt fastened. The meeting mode activation prompt can be used to ask the vehicle user whether to activate the intelligent meeting mode. The second voice message can be a voice message responding to the meeting mode activation prompt. The meeting mode status information can be computer-generated language. The meeting mode status information can be used to indicate to the vehicle user whether they agree to activate the intelligent meeting mode, or whether they disagree.

[0100] In this embodiment, the first domain controller determines, based on the first service information and the second service information, that the vehicle is in park, the vehicle speed is 0, and the seat belt is closed, thereby confirming that the vehicle is in a parked state, which satisfies the prerequisites for starting the meeting mode.

[0101] The first domain controller is connected to the audio system via hardwired wiring. Based on a voice prompt service, it uses the audio system to announce to the vehicle user whether the intelligent meeting mode is activated. The vehicle user can respond to inquiries about activating the meeting mode via voice. The first domain controller controls the microphone to collect the user's second voice information, recognizes it through a voice recognition service, and converts it into meeting mode status information to determine whether the vehicle user has activated the intelligent meeting mode.

[0102] In this embodiment, the meeting mode can specifically be an intelligent meeting mode, which adjusts the vehicle status to the optimal state for participating in a meeting. The first domain controller can determine whether the meeting mode can be enabled based on the meeting mode status information. When the meeting mode is enabled, the first domain controller can activate the intelligent meeting mode function service to conduct in-vehicle meetings.

[0103] In the above embodiment, if the service information indicates that the vehicle is in park, the speed is zero, and the seatbelt is off, the first domain controller can determine that the current vehicle state is suitable for enabling the smart conferencing function. It then invokes the voice reminder service to consult the vehicle user via voice broadcast whether to enable the smart conferencing mode. The first domain controller recognizes the user's voice information and determines whether the vehicle user agrees to enable the smart conferencing mode. Thus, the vehicle management system automatically determines whether to enable the conferencing mode based on the user's voice response.

[0104] Currently, vehicles have low levels of intelligence. Before participating in a meeting, users need to manually adjust vehicle components such as seats, windows, and air conditioning. This results in lengthy preparation time and cumbersome adjustment steps, leading to a poor user experience. Therefore, in some embodiments, when the meeting mode status information indicates that meeting mode is enabled, the first domain controller activates the intelligent meeting mode function service to conduct in-vehicle meetings, including:

[0105] When the meeting mode status information indicates that the meeting mode is enabled, the first domain controller displays a graphical interface indicating that the meeting mode is enabled on the central control screen through the meeting mode switch service, and starts the intelligent meeting mode function service.

[0106] The first domain controller sends a second instruction message to the second and third domain controllers to activate the intelligent conferencing mode function service;

[0107] After receiving the second instruction information, the second domain controller adjusts the seat position to the historical meeting position based on the seat adjustment service, closes the windows and locks the doors based on the window adjustment service and door lock control service, and controls the projector to project the meeting interface based on the projector adjustment service.

[0108] After receiving the second instruction information, the third domain controller adjusts the air conditioning setting to the historical setting based on the air conditioning adjustment service.

[0109] Here, the second instruction information can be used to instruct the first domain controller to activate the intelligent meeting mode function service. The historical meeting location can be the seat position set by the vehicle user during historical meeting times prior to this trip. This historical meeting location allows the vehicle user to be in a comfortable position. The historical meeting setting can be the air conditioning setting set by the vehicle user during historical meeting times prior to this trip. The meeting interface can be the display interface of the meeting software on a mobile device or in-vehicle terminal.

[0110] Furthermore, the first domain controller is connected to the central control screen, and the content displayed on the central control screen can be controlled via the conference mode switch service. Displaying a graphical interface indicating that conference mode is enabled on the central control screen can be understood as displaying an interface indicating that the intelligent conference mode switch is on.

[0111] In this embodiment, the first domain controller determines that the vehicle user agrees to enable the conference mode. It can then display a graphical interface indicating that the conference mode is enabled on the central control screen via the conference mode switch service and activate the intelligent conference mode function service. Simultaneously, it sends a second instruction message to the second and third domain controllers via the gateway, informing other domain controllers that the intelligent conference mode is enabled. Upon receiving the second instruction message, the second domain controller adjusts the seat position, window status, door lock status, and projector projection status through corresponding services, while the third domain controller adjusts the air conditioning level through the air conditioning adjustment service.

[0112] In other words, after the smart meeting mode is activated, the seat position is adjusted to the historical meeting position, the windows are closed, the doors are locked, the air conditioning is adjusted to the historical meeting level, and the projector is turned on to project the meeting interface of the meeting software.

[0113] In the above embodiment, after the intelligent meeting mode is activated, the first domain controller instructs the other two domain controllers to adjust the vehicle components through their respective services via the second instruction information, so that the state of the vehicle components reaches a state that makes the vehicle user feel comfortable, thereby improving the comfort of the meeting while ensuring the safety of the meeting.

[0114] In some embodiments, when the first service information and the second service information meet the meeting conditions, the first domain controller initiates the intelligent meeting mode function service to conduct in-vehicle conferencing, including:

[0115] If the first service information and the second service information meet the meeting conditions, the first domain controller obtains the setting operation to enable the meeting mode from the central control screen through the meeting mode switch service, and confirms to enable the meeting mode.

[0116] With meeting mode enabled, activate the intelligent meeting mode service to conduct in-vehicle meetings.

[0117] Here, the option to enable the meeting mode allows vehicle users to select and activate it via the graphical interface of the intelligent meeting mode switch on the central control screen. The meeting mode is set to intelligent meeting mode.

[0118] In this embodiment, when the first service information and the second service information meet the meeting conditions, the first domain controller displays the meeting mode switch image interface on the central control screen through the meeting mode switch service. The vehicle user performs the setting operation to enable the meeting mode on the meeting mode switch image interface, and the first domain controller obtains the setting operation to enable the meeting mode through the meeting mode switch service and confirms that the meeting mode is enabled.

[0119] In this way, users can select to activate the smart meeting mode through the central control screen, thereby improving the efficiency of starting a meeting.

[0120] In some embodiments, when the meeting mode is enabled, activating the intelligent meeting mode function service for in-vehicle conferencing may include: the first domain controller sending a third instruction message to the second and third domain controllers to activate the intelligent meeting mode function service; after receiving the third instruction message, the second domain controller adjusts the seat position to the historical meeting position based on the seat adjustment service, closes the windows and locks the doors based on the window adjustment service and the door lock control service, and controls the projector to project the meeting interface based on the projector adjustment service; and after receiving the third instruction message, the third domain controller adjusts the air conditioning level to the historical meeting level based on the air conditioning adjustment service.

[0121] In other words, after the smart meeting mode is activated, the seat position is adjusted to the historical meeting position, the windows are closed, the doors are locked, the air conditioning is adjusted to the historical meeting level, and the projector is turned on to project the meeting interface of the meeting software.

[0122] In some embodiments, after the first domain controller identifies the first voice information collected by the microphone through the voice recognition service and obtains the meeting response information in S22, the management method of the in-vehicle conference may further include:

[0123] If the response message from the participant indicates a refusal to attend the meeting, the response service is invoked to send the response message to other participating terminals, thereby notifying the other participating terminal users in the vehicle to refuse to attend the meeting.

[0124] Here, the response service can be at least one of the following: email service, SMS service, and software response service. Other participating terminals can be other vehicle-mounted terminals or mobile devices other than this vehicle.

[0125] In this embodiment, when the first domain controller determines that the response information is a refusal to attend the meeting, it invokes the response service to send the response information to other participating terminals using the corresponding response method. For example, when the response service is an email service, the vehicle's first domain controller invokes the email service to send the response information to other participating terminals via email. When the response service is an SMS service, the vehicle's first domain controller invokes the SMS service to send the response information to other participating terminals via SMS. When the response service is a software response service, the vehicle's first domain controller invokes the software response service to send the response information to other participating terminals via the conference software. In this way, by invoking the response service and using various response methods, the vehicle can automatically and promptly reply to other participating terminals that the user is unable to attend the meeting, thereby achieving the goal of eliminating the need for the user to respond manually and facilitating timely adjustments to the meeting time for participating members.

[0126] It should be noted that multiple response methods can be used simultaneously. This application embodiment does not impose any restrictions on the response method.

[0127] In some embodiments, in S25, after the first domain controller initiates the intelligent meeting mode function service to conduct a vehicle-mounted meeting when the first service information and the second service information meet the meeting conditions, the management method of the vehicle-mounted meeting may further include:

[0128] The first domain controller monitors the meeting process based on the Smart Meeting Mode feature service, and disables the Smart Meeting Mode feature service when the meeting ends or the user exits midway.

[0129] Here, "exiting midway" can be understood as the vehicle-mounted device exiting the meeting during the session. The meeting ending or exiting midway can cause the meeting process to terminate. In this embodiment, the first domain controller monitors the meeting process through the intelligent meeting mode function service. Upon detecting meeting information indicating an end to the meeting or a midway exit, it determines that the meeting process on the vehicle-mounted device has ended and automatically closes the intelligent meeting mode function service. This allows for intelligent termination of the intelligent meeting mode.

[0130] In some embodiments, in S25, after the first domain controller initiates the intelligent meeting mode function service to conduct a vehicle-mounted meeting when the first service information and the second service information meet the meeting conditions, the management method of the vehicle-mounted meeting may further include:

[0131] The first domain controller obtains the setting operation to turn off the meeting mode on the central control screen based on the meeting mode switch service, and disables the smart meeting mode function service.

[0132] Here, the central control screen displays a graphical interface for switching the conference mode on and off, allowing vehicle users to configure settings via this interface. If the vehicle user chooses to disable the conference mode, the first domain controller can obtain this setting through the conference mode switch service and disable the intelligent conference mode function. Thus, the vehicle management system can terminate the intelligent conference mode at any time through the center console's settings.

[0133] To further understand the vehicle-mounted conferencing management method provided in the embodiments of this application, this application provides another vehicle-mounted conferencing management method, applied to... Figure 1 The vehicle management system shown. Figure 3 The diagram illustrates another method for managing in-vehicle conferencing according to an embodiment of this application. The method includes the following steps:

[0134] S301 calls the mobile connection service to connect to the mobile device.

[0135] S302, call the application message service to obtain online meeting invitation messages sent by the meeting software in the mobile or vehicle terminal.

[0136] S303 invokes the voice prompt service to control the audio system to play an online meeting invitation message and asks the vehicle user whether they wish to accept the meeting.

[0137] S304: Invoke the voice recognition service to recognize the vehicle's voice response information. If the voice response indicates refusal to participate, proceed to S305. If the voice response indicates participation, proceed to S306.

[0138] S305 sends a refusal-to-attendance message to other participating terminals via SMS or email service.

[0139] S306: Invoke the navigation service to determine whether the destination can be reached before the meeting starts, based on the current location and the destination of this trip. If the destination can be reached, proceed to S307. If the destination cannot be reached, proceed to S308.

[0140] S307, invoke the voice reminder service to prompt the driver that they can attend a meeting at the destination, then jump to S309.

[0141] S308: Invoke the navigation service, plan multiple parking routes based on the current location, and activate the voice reminder service to remind the driver to park at a suitable location to participate in the meeting. Then proceed to S309.

[0142] S309, invoke the navigation service to determine that the vehicle is in a safe parking position; invoke the gear service to determine that the current gear of the vehicle is P; invoke the vehicle speed service to determine that the current vehicle speed is 0 kph; invoke the seat belt status service to determine that the seat belt status is off, and jump to S310.

[0143] S310 invokes the voice reminder service to remind the driver whether to turn on conference mode, then jumps to S311.

[0144] S311, invoke the voice recognition service to recognize the driver's response. If the response indicates "open conference mode," proceed to S312. If the response indicates "do not open conference mode," proceed to S313.

[0145] S312, enable the Smart Meeting Mode service and display "Smart Meeting Mode" switch as "On" on the central control screen, then proceed to S314.

[0146] S313, do not enable the smart meeting mode service.

[0147] S314: Invoke the seat adjustment service to check if the seat is in the preset meeting seat position. If yes, proceed to S315. If not, adjust the seat to the historical meeting position and proceed to S315.

[0148] S315, invoke the window adjustment service to check if all windows are closed. If yes, proceed to S316. If not all windows are closed, close the open windows and proceed to S316.

[0149] S316, call the door lock control service to check if all doors are locked. If yes, proceed to S317. If not all doors are locked, lock the unlocked doors and proceed to S317.

[0150] S318: Invoke the air conditioning adjustment service to check if the air conditioning setting is adjusted to the historical meeting air conditioning setting. If yes, proceed to S319. If not, adjust the air conditioning to the meeting air conditioning setting and proceed to S319.

[0151] S320 invokes the projector service, turns on the projector, and projects the meeting content onto the screen.

[0152] S321, invoke the intelligent meeting mode function service to determine whether the online meeting has ended or has been exited midway, or invoke the intelligent meeting mode function switch service to detect that the "intelligent meeting mode function switch" on the central control screen is off, end the intelligent meeting mode function service, and exit the intelligent meeting mode.

[0153] In the above embodiments, by calling services from different domains according to a certain orchestration logic, when encountering a meeting that needs to be handled in a timely manner while driving, the system can automatically find a suitable parking location based on the current driving situation and plan multiple reasonable parking routes to help the driver choose. At the same time, it can detect the status of the vehicle's surroundings in real time, activate the intelligent meeting mode service, and automatically complete seat adjustment, window adjustment, and air conditioning level adjustment after ensuring that the vehicle is in a safe state. This allows vehicle users to participate in meetings in a safe and comfortable environment, bringing an intelligent driving experience and ensuring the driving safety of vehicle users.

[0154] Another aspect of this application provides an alternative vehicle management system. Figure 4 This application provides a schematic diagram of another vehicle management system, as illustrated in the embodiments thereof. Figure 4 As shown, the vehicle management system may include a first domain controller 41, a second domain controller 42, and a third domain controller 43. The first domain controller 41 may include: an inquiry information broadcasting module 4101, a response information obtaining module 4102, a participant location obtaining module 4103, a service information acquisition module 4104, and a meeting function activation module 4105.

[0155] Here, the inquiry information broadcasting module 4101 can be used to obtain meeting invitation information through the application message service and broadcast the meeting inquiry information by voice based on the voice reminder service.

[0156] The response information acquisition module 4102 can be used to identify the first voice information collected by the microphone through the voice recognition service and obtain the response information of the participants.

[0157] The meeting location acquisition module 4103 is used to determine the meeting location through navigation services when the meeting response information indicates participation in the meeting.

[0158] The service information acquisition module 4104 is used to acquire the first service information sent by the second domain controller 42 and the second service information sent by the third domain controller 43 when the parking location and the meeting location are determined to coincide through the navigation service.

[0159] The meeting function activation module 4105 is used to activate the intelligent meeting mode function service for in-vehicle meetings when the first service information and the second service information meet the meeting conditions.

[0160] In the above embodiments, the first domain controller can obtain meeting invitations based on the domain-internal application messaging service, thereby receiving meeting information in a timely manner. It can also use a voice reminder service to announce meeting inquiries, reducing the probability of vehicle users taking their eyes off the road and improving driving safety. Furthermore, the first domain controller uses a voice recognition service to recognize the first voice information collected by the microphone to obtain the meeting response information. This allows it to promptly obtain the vehicle user's response by calling the domain-internal service, eliminating the need for the vehicle user to reply on the central control screen and reducing the risk during driving. If the meeting response indicates participation, the first domain controller can automatically plan a safe and reliable meeting location using the navigation service, ensuring the user's safety during the meeting. Meanwhile, when the first domain controller determines that the parking location coincides with the meeting location through navigation services, the first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller. If the first service information and the second service information meet the meeting conditions, the first domain controller activates the intelligent meeting mode function service to conduct in-vehicle conferencing. Thus, the first domain controller can determine the status of other vehicle components through the service information, and if the status of other vehicle components meets the meeting conditions, the first domain controller activates the intelligent meeting mode function service to put the vehicle into intelligent meeting mode for in-vehicle conferencing. This allows vehicle users to conduct in-vehicle conferencing in a safe vehicle environment, improving the reliability and safety of the meeting.

[0161] In some embodiments, the meeting location acquisition module 4103 may include:

[0162] The sequence determination submodule can be used to determine the sequence relationship between the meeting time and the arrival time of the destination of this trip by using navigation services when the meeting response information is "participation in the meeting".

[0163] The first meeting attendance announcement submodule can be used to plan multiple intermediate parking locations through navigation services, determine the intermediate parking location as the meeting location, and announce the meeting information at the parking location based on the voice reminder service when the meeting time is earlier than the arrival time of the destination.

[0164] The second meeting attendance announcement submodule can be used to determine the destination location of the trip as the meeting location when the meeting time is late and the destination arrival time is late, and announce the meeting location based on the voice reminder service.

[0165] In some embodiments, the service information acquisition module 4104 may include: an instruction information sending submodule, which can be used to send first instruction information indicating that the vehicle has reached the meeting location to the second domain controller 42 and the third domain controller 43 when the navigation service determines that the vehicle location coincides with the meeting location.

[0166] The second domain controller 42 can be used to, upon receiving the first instruction information, obtain gear information and vehicle speed information based on gear service and vehicle speed service respectively, encapsulate the gear information and vehicle speed information into first service information, and send it to the first domain controller.

[0167] The third domain controller can be used to obtain seat belt status information based on seat belt status service upon receiving the first indication information, encapsulate the seat belt status information into second service information, and send it to the first domain controller.

[0168] The service information acquisition module 4104 may further include: an information acquisition submodule, which can be used for the first domain controller to acquire the first service information sent by the second domain controller and the second service information sent by the third domain controller through the gateway.

[0169] In some embodiments, the first service information includes vehicle speed information and gear information. The second service information includes seat belt status information. The conference function activation module 4105 may include:

[0170] The inquiry information broadcasting submodule can be used to start the inquiry information based on the voice reminder service voice broadcasting conference mode when the first service information and the second service information meet the conditions that the vehicle is in park gear, the vehicle speed is zero, and the seat belt is in the off state.

[0171] The status information submodule can be used to identify second voice information based on the speech recognition service and obtain meeting mode status information;

[0172] The meeting function startup submodule can be used to start the intelligent meeting mode function service for in-vehicle meetings when the meeting mode status information is "meeting mode enabled".

[0173] In some embodiments, the conference function startup submodule may include: a service startup unit, which can be used to display a graphical interface indicating that the conference mode is enabled on the central control screen through the conference mode switch service when the conference mode status information is that the conference mode is enabled, and to start the intelligent conference mode function service.

[0174] The instruction information sending unit can be used to send a second instruction information for starting the intelligent meeting mode function service to the second domain controller and the third domain controller;

[0175] The second domain controller may include: a first adjustment module, which can be used to adjust the seat position to the historical meeting position based on the seat adjustment service after receiving the second instruction information, close the windows and lock the doors based on the window adjustment service and the door lock control service, and control the projector to project the meeting interface based on the projector adjustment service;

[0176] The third domain controller may include: a second adjustment module, which can be used to adjust the air conditioning setting to the historical meeting setting based on the air conditioning adjustment service after receiving the second instruction information.

[0177] In some embodiments, the first domain controller 41 may further include: a first service shutdown module, which can be used to monitor the meeting process based on the smart meeting mode function service, and shut down the smart meeting mode function service when the meeting ends or exits midway.

[0178] Alternatively, the second service shutdown module can be used to obtain the setting operation for shutting down the meeting mode on the central control screen based on the meeting mode switch service, and shut down the smart meeting mode function service.

[0179] It should be understood that the specific features, operations, and details described herein with respect to the methods of this application can also be similarly applied to the apparatus and system of this application, or vice versa. Furthermore, each step of the methods of this application described above can be performed by a corresponding component or unit of the apparatus or system of this application.

[0180] It should be understood that the various modules / units of the device of this application can be implemented wholly or partially through software, hardware, firmware, or a combination thereof. Each module / unit can be embedded in the processor of the electronic device in hardware or firmware form or independent of the processor, or it can be stored in the memory of the electronic device in software form for the processor to call to execute the operation of each module / unit. Each module / unit can be implemented as an independent component or module, or two or more modules / units can be implemented as a single component or module.

[0181] In another aspect, this application provides an electronic device. Figure 5 This illustration shows a structural diagram of an electronic device provided in an embodiment of this application, such as... Figure 5 As shown, the electronic device 500 includes a processor 501 and a memory 502 storing computer program instructions. The processor 501 executes the computer program instructions to implement the steps of the aforementioned vehicle-mounted conference management method. This electronic device 500 can be broadly categorized as a server, terminal, or any other electronic device with the necessary computing and / or processing capabilities.

[0182] In one embodiment, the electronic device 500 may include a processor, memory, network interface, communication interface, etc., connected via a system bus. The processor of the electronic device 500 can be used to provide necessary computing, processing, and / or control capabilities. The memory of the electronic device 500 may include non-volatile storage media and internal memory. The non-volatile storage media may store an operating system, computer programs, etc. The internal memory can provide an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface and communication interface of the electronic device 500 can be used to connect and communicate with external devices via a network. When the computer program is executed by the processor, it performs the steps of the vehicle-mounted conferencing management method of this application.

[0183] This application provides a computer-readable storage medium storing a vehicle-mounted conference management program. When executed by a processor, the vehicle-mounted conference management program implements the steps of the vehicle-mounted conference management method provided in any of the above embodiments.

[0184] Those skilled in the art will understand that the method steps of this application can be performed by a computer program instructing related hardware, such as electronic device 500 or a processor. The computer program can be stored in a non-transitory computer-readable storage medium, and its execution causes the steps of this application to be performed. Depending on the context, any reference herein to memory, storage, or other media may include non-volatile or volatile memory. Examples of non-volatile memory include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid-state drive, etc. Examples of volatile memory include random access memory (RAM), external cache memory, etc.

[0185] The technical features described above can be combined arbitrarily. Although not all possible combinations of these technical features are described, any combination of these technical features should be considered to be covered by this specification, provided that such combination does not contain contradictions.

[0186] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for managing in-vehicle conferencing, characterized in that, An in-vehicle management system comprising multiple domain controllers, wherein the multiple domain controllers include at least a first domain controller, a second domain controller, and a third domain controller, the method comprising: The first domain controller obtains meeting invitation information through the application messaging service and broadcasts meeting inquiry information via voice prompt service; The first domain controller identifies the first voice information collected by the microphone through the voice recognition service to obtain the meeting response information; If the response information indicates participation in the meeting, the first domain controller determines the meeting location via navigation services; If the first domain controller determines that the parking location coincides with the meeting location through the navigation service, the first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller. If the first service information and the second service information meet the meeting conditions, the first domain controller starts the intelligent meeting mode function service to conduct in-vehicle meetings.

2. The management method for in-vehicle conferencing according to claim 1, characterized in that, When the response information indicates participation in the meeting, the first domain controller determines the meeting location via navigation services, including: If the response information indicates participation in the meeting, the first domain controller determines the chronological relationship between the meeting time and the arrival time of the destination of this trip through the navigation service; If the meeting time is earlier than the destination arrival time, the first domain controller plans multiple intermediate parking locations through navigation services, determines the intermediate parking location as the meeting location, and broadcasts the meeting information at the parking location based on the voice reminder service. If the meeting time is later than the arrival time at the destination, the destination location of this trip is determined as the meeting location, and the meeting is announced to the attendee at the destination location via voice reminder service.

3. The management method for in-vehicle conferencing according to claim 1, characterized in that, If the first domain controller determines that the parking location coincides with the meeting location through the navigation service, the first domain controller obtains first service information sent by the second domain controller and second service information sent by the third domain controller, including: If the first domain controller determines that the vehicle's location coincides with the meeting location through the navigation service, the first domain controller sends a first indication message that the vehicle has arrived at the meeting location to the second domain controller and the third domain controller. When the second domain controller receives the first indication information, it obtains gear information and vehicle speed information based on gear service and vehicle speed service respectively, encapsulates the gear information and vehicle speed information into first service information, and sends it to the first domain controller. Upon receiving the first indication information, the third domain controller obtains seat belt status information based on the seat belt status service, encapsulates the seat belt status information into second service information, and sends it to the first domain controller. The first domain controller obtains the first service information sent by the second domain controller and the second service information sent by the third domain controller through the gateway.

4. The management method for in-vehicle conferencing according to claim 1, characterized in that, The first service information includes vehicle speed information and gear information, and the second service information includes seat belt status information. When the first service information and the second service information meet the meeting conditions, the first domain controller activates the intelligent meeting mode function service to conduct in-vehicle conferencing, including: When the first service information and the second service information satisfy the conditions that the vehicle is in park gear, the vehicle speed is zero, and the seat belt is closed, the first domain controller initiates inquiry information based on the voice reminder service voice broadcast conference mode. The first domain controller recognizes the second voice information based on the voice recognition service and obtains the conference mode status information; When the meeting mode status information indicates that the meeting mode is enabled, the first domain controller initiates the intelligent meeting mode function service to conduct in-vehicle meetings.

5. The management method for in-vehicle conferencing according to claim 4, characterized in that, When the meeting mode status information indicates that the meeting mode is enabled, the first domain controller initiates the intelligent meeting mode function service for in-vehicle conferencing, including: When the meeting mode status information indicates that the meeting mode is enabled, the first domain controller displays a graphical interface indicating that the meeting mode is enabled on the central control screen through the meeting mode switch service, and starts the intelligent meeting mode function service. The first domain controller sends a second instruction message to the second and third domain controllers to activate the Smart Meeting Mode function service; After receiving the second instruction information, the second domain controller adjusts the seat position to the historical meeting position based on the seat adjustment service, closes the windows and locks the doors based on the window adjustment service and the door lock control service, and controls the projector to project the meeting interface based on the projector adjustment service. After receiving the second instruction information, the third domain controller adjusts the air conditioning setting to the historical meeting setting based on the air conditioning adjustment service.

6. The management method for in-vehicle conferencing according to claim 1, characterized in that, After the first domain controller identifies the first voice information collected by the microphone through the voice recognition service and obtains the meeting response information, the following steps are also included: If the response information for the meeting is a refusal to attend, the response service is invoked to send the response information to other participating terminals so as to notify the other participating terminal users in the vehicle to refuse to attend the meeting. The response service is at least one of the following services: email service, SMS service, and software response service.

7. The method for managing in-vehicle conferencing according to claim 1, characterized in that, After the first domain controller initiates the intelligent meeting mode function service to conduct in-vehicle conferencing, provided that the first service information and the second service information meet the meeting conditions, the following steps are also included: The first domain controller monitors the meeting process based on the intelligent meeting mode function service, and shuts down the intelligent meeting mode function service when the meeting ends or the user leaves midway. Alternatively, the first domain controller may obtain a setting operation to disable the meeting mode on the central control screen based on the meeting mode switch service, and disable the smart meeting mode function service.

8. The management method for in-vehicle conferencing according to claim 1, characterized in that, Before the first domain controller obtains the meeting invitation information through the application message acquisition service and broadcasts the meeting inquiry information via voice based on the voice reminder service, the following steps are also included: The first domain controller establishes a connection with mobile devices within the vehicle space based on the mobile connectivity service.

9. A vehicle-mounted management system, characterized in that, It includes a first domain controller, a second domain controller, and a third domain controller, wherein the first domain controller includes: The inquiry information broadcasting module is used to obtain meeting invitation information through the application messaging service and broadcast the meeting inquiry information via voice based on the voice reminder service; The response information acquisition module is used to identify the first voice information collected by the microphone through the voice recognition service and obtain the response information of the participants. The meeting location acquisition module is used to determine the meeting location via navigation services when the meeting response information indicates participation in the meeting. The service information acquisition module is used to acquire first service information sent by the second domain controller and second service information sent by the third domain controller when the parking location is determined to coincide with the meeting location through the navigation service. The meeting function activation module is used to activate the intelligent meeting mode function service for in-vehicle meetings when the first service information and the second service information meet the meeting conditions.

10. An electronic device, characterized in that, The electronic device includes a processor, a memory, and a vehicle conference management program stored in the memory and executable by the processor, wherein when the vehicle conference management program is executed by the processor, it implements the steps of the vehicle conference management program as claimed in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a vehicle-mounted conference management program, wherein when the vehicle-mounted conference management program is executed by a processor, it implements the steps of the vehicle-mounted conference management method as described in any one of claims 1 to 8.

Images