Soa-based vehicle local network wake-up method, system, device, and medium

Abstract

The application provides a SOA-based vehicle local network wake-up method, system, device and medium, the SOA-based vehicle local network wake-up method includes receiving network wake-up service request information, the target function identifier is included in network wake-up service request information, the network segment in network is matched based on target function identifier, the first target network segment corresponding to target function identifier is determined, if the first target network segment is in the dormant state, according to the corresponding relationship of the preset network segment-domain controller, the first domain controller belonging to the first target network segment is inquired, so that the first domain controller wakes up the first target network segment, completes the vehicle local network wake-up, through the service design of vehicle local network wake-up function, the unnecessary loss of vehicle battery capacity can be effectively reduced, and the increasingly complex electronic and electrical system of automobile is adapted.

Description

Technical Field

[0001] This application relates to the field of vehicle local network wake-up technology, specifically to a vehicle local network wake-up method, device, electronic device and storage medium based on SOA. Background Technology

[0002] Energy conservation in automobiles has always been a top priority for the automotive industry, and reducing unnecessary energy waste is an effective method for achieving this. Currently, some functions are still needed when a car is in the OFF position (engine off), such as vehicle anti-theft and Bluetooth key unlocking / locking. To avoid excessive battery drain after the engine is turned off, which could prevent the vehicle from starting, most unnecessary functions should be disabled when the vehicle is in the OFF position to minimize power consumption and ensure the battery has a longer operating time.

[0003] Local area network wake-up can reduce unnecessary energy waste. Most existing local area network wake-up methods use network management messages to wake up and put the network segment into sleep mode. However, with the development of intelligent vehicles, the functions of vehicles are becoming more and more diversified, and the electronic and electrical systems of vehicles are becoming more and more complex. Existing local area network wake-up methods will not be able to adapt to the increasingly complex electronic and electrical systems. Summary of the Invention

[0004] In view of the shortcomings of the prior art described above, this application provides a method, system, device and medium for wake-up of vehicle local network based on SOA, so as to solve the technical problem that the existing local network wake-up methods cannot adapt to the increasingly complex electronic and electrical systems.

[0005] This application provides a vehicle local network wake-up method based on SOA. The SOA-based vehicle local network wake-up method includes: receiving network wake-up service request information, the network wake-up service request information including a target function identifier; matching network segments in the network based on the target function identifier to determine a first target network segment corresponding to the target function identifier; if the first target network segment is in a dormant state, querying the first domain controller to which the first target network segment belongs according to a preset network segment-domain controller correspondence, so that the first domain controller wakes up the first target network segment, thereby completing the vehicle local network wake-up.

[0006] In one embodiment of this application, the wake-up mode of the first target network segment is determined according to the wake-up mode parameter. The wake-up mode includes automatic sleep wake-up or manual sleep wake-up, and the wake-up service call request information also includes the wake-up mode parameter. If the wake-up mode is automatic sleep wake-up, the sleep time of the first target network segment is updated based on the wake-up duration, and the wake-up service call request information also includes the wake-up duration. If the wake-up mode is manual sleep wake-up, the first target network segment is bound to a first target caller identifier, and the wake-up service call request information also includes the first target caller identifier.

[0007] In one embodiment of this application, the binding relationship between the first target network segment and the first target caller identifier is queried; if the binding relationship is not bound, the first target network segment is bound to the first target caller identifier.

[0008] In one embodiment of this application, the wake-up mode of the first target network segment is determined according to the wake-up mode parameter. The wake-up mode includes automatic sleep wake-up or manual sleep wake-up, and the wake-up service call request information also includes the wake-up mode parameter. If the wake-up mode is automatic sleep wake-up, the sleep time of the first target network segment is updated based on the wake-up duration, and the wake-up service call request information also includes the wake-up duration. If the wake-up mode is manual sleep wake-up, the first target network segment is bound to a first target caller identifier, and the wake-up service call request information also includes the first target caller identifier.

[0009] In one embodiment of this application, a network hibernation service call request information is received, the network hibernation service call request information including a second target caller identifier; based on the second target caller identifier, a network segment in the network is queried to determine a second target network segment that has a binding relationship with the second target caller identifier, and the binding relationship between the second target network segment and the second target caller identifier is released; the status of the second target network segment is queried, and if the second target network segment is in an idle state, the second domain controller to which the second target network segment belongs is queried according to a preset network segment-domain controller correspondence, so that the second domain controller puts the second target network segment into hibernation.

[0010] In one embodiment of this application, the awakened network segments in the network are polled; if the awakened network segment is in an idle state, the third domain controller to which the awakened network segment belongs is queried according to the preset network segment-domain controller correspondence, so that the third domain controller puts the awakened network segment into hibernation.

[0011] In one embodiment of this application, a network segment in the network is queried based on the first target caller identifier. If a third target network segment that is bound to the first target caller identifier is found, and the third target network segment is a different network segment from the first target network segment, then the binding relationship between the third target network segment and the first target caller identifier is released. The status of the third target network segment is queried. If the third target network segment is in an idle state, then according to the preset network segment-domain controller correspondence, the fourth domain controller to which the third target network segment belongs is queried, so that the fourth domain controller puts the third target network segment into hibernation.

[0012] In one embodiment of this application, the domain controller includes a master domain controller and a slave domain controller. The master domain controller serves as a unified interface to receive the Wake-up Service Invocation Request information or the Network Hibernation Service Invocation Request information.

[0013] In one embodiment of this application, a vehicle local network wake-up system based on SOA is also provided. The SOA-based vehicle local network wake-up system includes: a request receiving module, used to receive network wake-up service request information, the network wake-up service request information including a target function identifier; a mapping relationship query module, used to match network segments in the network based on the target function identifier, determine a first target network segment corresponding to the target function identifier, and query a first domain controller to which the first target network segment belongs according to a preset network segment-domain controller correspondence; a network segment status management module, used to query the status of the first target network segment; a control command distribution module, used to send a first control command if the first target network segment is in a dormant state; and a domain controller, the domain controller including the first domain controller, used to wake up the first target network segment in a dormant state according to the first control command.

[0014] In one embodiment of this application, the domain controller further includes: a second domain controller, configured to put a second target network segment in an idle state into hibernation according to a second control instruction, wherein the second target network segment is obtained by querying network segments in the network based on a second target caller identifier; a third domain controller, configured to put a woken-up network segment in an idle state into hibernation according to a third control instruction; and a fourth domain controller, configured to put a third target network segment in an idle state into hibernation according to a fourth control instruction, wherein the third target network segment is obtained by querying network segments in the network based on a first target caller identifier.

[0015] In one embodiment of this application, an electronic device is also provided, the electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device enables the SOA-based vehicle local network wake-up method as described above.

[0016] In one embodiment of this application, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a computer's processor, causes the computer to perform the SOA-based vehicle local network wake-up method as described above.

[0017] The beneficial effects of the present invention are as follows: The present invention provides a vehicle local network wake-up method, system, device and medium based on SOA. The vehicle local network wake-up method based on SOA architecture matches the corresponding first target network segment according to the target function identifier in the network wake-up service request information, and wakes up the first target network segment in a dormant state through the first domain controller to which the first target network segment belongs. Through the service-oriented design of the vehicle local network wake-up function, unnecessary loss of vehicle battery power can be effectively reduced, adapting to the increasingly complex electronic and electrical systems of automobiles.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0020] Figure 1 This is a schematic diagram illustrating the implementation environment of an SOA-based vehicle local network wake-up method, as shown in an exemplary embodiment of this application.

[0021] Figure 2 This is a flowchart illustrating an exemplary embodiment of the present application of a vehicle local network wake-up method based on SOA;

[0022] Figure 3 This is a flowchart illustrating the wake-up request processing of an automatic sleep / wake-up mode, as shown in a specific embodiment of this application.

[0023] Figure 4 This is a flowchart illustrating a specific embodiment of the manual hibernation process in this application;

[0024] Figure 5 This is a flowchart illustrating an automatic sleep process according to a specific embodiment of this application;

[0025] Figure 6 This is a block diagram illustrating an SOA-based vehicle local network wake-up system, as shown in an exemplary embodiment of this application.

[0026] Figure 7 This is a schematic diagram illustrating the structure of a vehicle local network wake-up system based on SOA, as shown in a specific embodiment of this application.

[0027] Figure 8 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0028] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0029] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0030] It should be noted that in this application, terms such as "first" and "second" are merely for distinguishing similar objects, and do not limit the order or sequence of similar objects. The variations of "including" and "having" indicate that the scope covered by the subject of the word is not exclusive, except for the examples shown by the word.

[0031] It is understood that the various numerical designations, step numbers, and other identifiers recorded in this application are for descriptive convenience and are not intended to limit the scope of this application. The size of the identifiers in this application does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0032] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the present application. However, it will be apparent to those skilled in the art that embodiments of the present application may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the present application.

[0033] It's important to note that SOA, or Service Oriented Architecture, is a method for reusing software components through service interfaces. Specifically, it involves breaking down different functional units of an application and then connecting them through standard interfaces and communication protocols for on-demand invocation. In SOA architecture, services are the core abstraction method and the most basic descriptive unit of the system. Due to its flexibility and scalability, SOA can better support the distributed deployment and iterative updates of vehicle control software. An SOA-based architecture can achieve: interoperability, hardware and software separation (reuse), and shortened development cycles.

[0034] The embodiments of this application respectively propose a vehicle local network wake-up method based on SOA, a vehicle local network wake-up system based on SOA, an electronic device, a computer-readable storage medium, and a computer program product. These embodiments will be described in detail below.

[0035] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating the implementation environment of a vehicle local network wake-up method based on SOA, as shown in an exemplary embodiment of this application.

[0036] like Figure 1 As shown, the implementation environment may include a call terminal 110, an intelligent vehicle 120, a processing terminal 121, and a domain controller 122, wherein the processing terminal 121 and the domain controller 122 are configured in the intelligent vehicle 120. The call terminal 110 may be at least one of the following: vehicle-side, cloud-based, or mobile terminal; the processing terminal 121 may be at least one of the following: microcomputer, embedded computer, or neural network computer; and the number of domain controllers 122 is greater than or equal to one. The call terminal 110 sends a network wake-up service request to the processing terminal 121. The processing terminal 121 receives the network wake-up service request, determines the first target network segment based on the network wake-up service request, and wakes up the first target network segment that is in a dormant state through the domain controller 122.

[0037] Schematic illustration: Processing terminal 121 receives network wake-up service request information, which includes a target function identifier. Based on the target function identifier, it matches network segments in the network to determine a first target network segment corresponding to the target function identifier. If the first target network segment is in a dormant state, it queries the first domain controller to which the first target network segment belongs according to a preset network segment-domain controller correspondence, so that the first domain controller wakes up the first target network segment, completing the vehicle local network wake-up. It can be seen that the technical solution of this application embodiment, through the service-oriented design of the vehicle local network wake-up function, can effectively reduce unnecessary power loss of the vehicle battery and adapt to the increasingly complex electronic and electrical systems of automobiles. It should be noted that domain controller 122 includes a first domain controller.

[0038] It should be noted that the SOA-based vehicle local network wake-up method provided in this application embodiment is generally executed by the processing terminal 121.

[0039] Please see Figure 2 , Figure 2 This is a flowchart illustrating an exemplary embodiment of the SOA-based vehicle local network wake-up method. This method can be applied to... Figure 1 The implementation environment shown is specifically executed by the processing terminal 121 in that implementation environment. It should be understood that this method can also be applied to other exemplary implementation environments and specifically executed by devices in other implementation environments. This embodiment does not limit the implementation environment to which this method is applicable.

[0040] like Figure 2 As shown, in an exemplary embodiment, the SOA-based vehicle local network wake-up method includes at least steps S210 to S230, which are described in detail below:

[0041] Step S210: Receive Wake-up Service Request Information, which includes a target function identifier.

[0042] In one embodiment of this application, when the vehicle is in the OFF position, some network segments in the vehicle network are in a dormant state. When a caller needs to implement certain functional scenarios of the vehicle, it needs to wake up the network segment where the controller implementing these functions resides. Therefore, based on the vehicle SOA architecture, an external request processing module is configured in the system. This external request processing module is responsible for uniformly processing external system requests and serves as the entry point for all application layer dormant / wake-up requests. When a caller needs to implement a functional scenario, it sends a network wake-up service request to the external request processing module. The network wake-up service request includes the network wake-up service request and other relevant information, such as the target function identifier and the target caller identifier. The caller can be a local caller, such as the vehicle lighting system or the vehicle window system, or a remote caller, such as a Bluetooth car key, a mobile APP, or a vehicle cloud platform.

[0043] Step S220: Match network segments in the network based on the target function identifier to determine the first target network segment corresponding to the target function identifier.

[0044] In one embodiment of this application, a mapping relationship query module is configured in the system, and a function-network segment mapping relationship is preset. This allows for matching the first target network segment corresponding to the target function identifier from network segments in the network according to the preset function-network segment mapping relationship. For example, a function enumeration value can be configured for each functional scenario as a function identifier, and a number can be configured for each network segment. The function-network segment mapping relationship is configured based on the function enumeration value of each function and the number of each network segment to obtain the preset function-network segment mapping relationship, so that the function-network segment mapping relationship can be queried according to the function enumeration value. The first target network segment can be one or more.

[0045] Step S230: If the first target network segment is in a dormant state, then according to the preset correspondence between network segments and domain controllers, query the first domain controller to which the first target network segment belongs, so that the first domain controller can wake up the first target network segment and complete the vehicle local network wake-up.

[0046] In one embodiment of this application, a network segment status management module is configured in the system as an internal state machine to mark and query the status of network segments and execute wake-up and sleep logic. When executing the wake-up logic, the status of the first target network segment is queried. If the first target network segment is in a sleep state, the mapping relationship query module is controlled to query the first domain controller corresponding to the first target network segment. A wake-up control command is sent to the first domain controller, invoking the network segment mode control basic service configured on the first domain controller, so that the first domain controller wakes up the target network segment, completing the vehicle local network wake-up. The mapping relationship query module also presets the network segment-domain controller mapping relationship. For example, an identifier is configured for each domain controller, and the network segment-domain controller mapping relationship is configured according to the number of each network segment and the identifier of each domain controller, so as to query the first domain controller to which the first target network segment belongs based on the number of the target network segment.

[0047] If the first target network segment is already in a wake-up state, there is no need to wake it up again.

[0048] It should be noted that in this embodiment, the state of the network segment includes a dormant state or a wake-up state, and the wake-up state includes an occupied state or an idle state.

[0049] In one embodiment of this application, the domain controller includes a master domain controller and slave domain controllers. The master domain controller serves as a unified interface to receive network wake-up service call request information or network hibernation service call request information.

[0050] In this embodiment, the vehicle includes multiple VIUs (Vehicle Integration Units, domain controllers), such as VIUFL (left domain controller), VIUFR (right domain controller), and VIUR (rear domain controller). Each VIU deploys a control execution module with local wake-up / sleep functionality. Each control execution module integrates a ComM (Communication Manager) network management component to implement actual sleep, wake-up, and query management functions on the downstream CAN (Controller Area Network) segment under the domain controller. Furthermore, for interface consistency, VIUFL is designated as the master domain controller, and VIUFR and VIUR as slave domain controllers. The network wake-up / sleep service on the VIUFL serves as the sole request interface for this local network wake-up / sleep function, and external requests (network wake-up / sleep service requests) also include requests from VIUFR and VIUR. For example, a controller on a network segment connected to VIUFR triggers passive wake-up. When business operations are needed, it is necessary to wake up certain network segments of VIUFR and VIUR. At this time, it is necessary to call the network wake-up service deployed on VIUFL through DDS (Data Distribution Service, i.e. Ethernet), and the network wake-up service will then wake up the network segments on VIUR and VIUFR.

[0051] In one embodiment of this application, if the first target network segment is in a dormant state, the first domain controller to which the first target network segment belongs is queried according to a preset network segment-domain controller correspondence, so that the first domain controller wakes up the first target network segment. This includes: determining the wake-up mode of the first target network segment based on wake-up mode parameters, where the wake-up mode includes automatic sleep wake-up or manual sleep wake-up, and the wake-up service call request information also includes wake-up mode parameters; if the wake-up mode is automatic sleep wake-up, the sleep time of the first target network segment is updated based on the wake-up duration, and the wake-up service call request information also includes the wake-up duration; if the wake-up mode is manual sleep wake-up, the first target network segment is bound to the first target caller identifier, and the wake-up service call request information also includes the first target caller identifier.

[0052] In this embodiment, two wake-up modes are set for the Wake-up Network service: automatic sleep wake-up and manual sleep wake-up. The wake-up mode parameters for automatic and manual sleep wake-up are as follows: for example, `autorelease` is used for automatic sleep wake-up, and `handrelease` is used for manual sleep wake-up. Different wake-up modes correspond to different wake-up logic. When the wake-up mode is automatic sleep wake-up, the network segment will automatically sleep for a period of time after being woken up; when the wake-up mode is manual sleep wake-up, the network segment will remain awake after being woken up and needs to be manually put to sleep. When the caller invokes the Wake-up Network service, it selects the wake-up mode parameter according to business needs (automatic sleep wake-up or manual sleep wake-up) to generate Wake-up Network service call request information including the wake-up mode parameter. After waking up the first target network segment, the network segment status management module determines the wake-up mode of the first target network segment according to the wake-up mode parameter and executes the corresponding wake-up logic.

[0053] If the wake-up mode is automatic sleep-wake, the current time is obtained, and the sleep time of the first target network segment is updated according to the current time and the wake-up duration in the network wake-up service call request information. Sleep time refers to the time point at which a network segment, after being woken up in automatic sleep-wake mode, can re-enter sleep mode. The current time can be obtained through T-Box (Telematics Box) or vehicle-mounted systems, etc. The specific method for updating the sleep time of the first target network segment can be: determining the sleep time using expiretime = now + duration, where expiretime is the sleep time, now is the current time, and duration is the wake-up duration, and inserting the sleep time of the first target network segment into the network segment list, which is pre-created based on network segments in the network. It should be noted that when the caller selects automatic sleep-wake mode to call the network wake-up service, the wake-up duration also needs to be set. A network wake-up service request information is generated and sent based on the target function identifier, wake-up mode parameters, wake-up duration, and the network wake-up service request.

[0054] If the wake-up mode is manual sleep-wake, the first target network segment is bound to the first target caller identifier in the Wake-up service call request information. The sleep time of the first target network segment is updated to a special value, such as FF, and the sleep time of the first target network segment is inserted into the network segment list, so that the first target network segment remains awake until it is manually put into sleep mode. It should be noted that when the caller selects the manual sleep-wake mode to call the Wake-up service, the first target caller identifier also needs to be set. Based on the target function identifier, wake-up mode parameters, the first target caller identifier, and the Wake-up service request, a Wake-up service request message is generated and sent.

[0055] In addition, priorities can be set for the two wake-up modes. For example, the priority of the manual sleep wake-up mode / service can be set higher than that of the automatic sleep wake-up mode / service. When the first target network segment corresponding to the manual sleep wake-up service and the first target network segment corresponding to the automatic sleep wake-up service are the same network segment, the service can decide the conflict based on the priority.

[0056] In addition, after the first target network segment is successfully woken up, the first target network segment will also be marked as woken up.

[0057] In one embodiment of this application, before binding the first target network segment with the first target caller identifier, the method includes: querying the binding relationship between the first target network segment and the first target caller identifier; if the binding relationship is not bound, then binding the first target network segment with the first target caller identifier.

[0058] In this embodiment, the network segment status management module is also used to bind, unbind, and query the binding relationship between network segments and caller identifiers. The binding relationship between the first target network segment and the first target caller identifier can be queried based on the number of the first target network segment. If the binding relationship is unbound, the first target network segment is bound to the first target caller identifier. If the binding relationship is already bound, it means that the first target network segment and the first target caller identifier are already bound, and there is no need for repeated binding. The technical solution of this embodiment can avoid duplicate binding between network segments and caller identifiers.

[0059] In one embodiment of this application, if the first target network segment is in a wake-up state, the SOA-based vehicle local network wake-up method includes: determining the wake-up mode of the first target network segment according to wake-up mode parameters, wherein the wake-up mode includes automatic sleep wake-up or manual sleep wake-up, and the network wake-up service call request information also includes wake-up mode parameters; if the wake-up mode is automatic sleep wake-up, then the sleep time of the first target network segment is updated based on the wake-up duration, and the network wake-up service call request information also includes the wake-up duration; if the wake-up mode is manual sleep wake-up, then the first target network segment is bound to the first target caller identifier, and the network wake-up service call request information also includes the first target caller identifier.

[0060] In this embodiment, if the first target network segment is in a wake-up state, the wake-up mode of the first target network segment is determined according to the wake-up mode parameter in the network wake-up service call request information, and different wake-up logic is executed based on different wake-up modes. The specific wake-up logic has been described in detail in the above embodiments and will not be repeated here.

[0061] In one embodiment of this application, if the wake-up mode is manual sleep-wake, the SOA-based vehicle local network wake-up method further includes: querying network segments in the network based on a first target caller identifier; if a third target network segment with a binding relationship to the first target caller identifier is found, and the third target network segment is a different network segment from the first target network segment, then the binding relationship between the third target network segment and the first target caller identifier is released; querying the status of the third target network segment; if the third target network segment is in an idle state, then according to the preset network segment-domain controller correspondence, querying the fourth domain controller to which the third target network segment belongs, so that the fourth domain controller puts the third target network segment into sleep mode.

[0062] In this embodiment, if the number of network segments that need to be woken up by the caller corresponding to the first target caller identifier is reduced compared to the previous network wake-up service call, the binding relationship between the first target caller identifier and other network segments besides the target network segment can also be released. Specifically, the network segments that are bound to the first target caller identifier are queried in the network according to the first target caller identifier, which are used as the third target network segments. The third target network segment can be compared with the first target network segment based on the number of each network segment. If the number of the third target network segment is different from the number of the first target network segment, it means that the third target network segment and the first target network segment are different network segments, and the binding relationship between the third target network segment and the first target caller identifier is released. If the number of the third target network segment is the same as the number of the first target network segment, it means that the third target network segment and the first target network segment are the same network segment, and the binding relationship between the third target network segment and the first target caller identifier is not released.

[0063] After unbinding the third target network segment from the first target caller identifier, the following operations can be performed: query the status of the third target network segment based on its number. If the third target network segment is in an idle state, query the fourth domain controller to which the third target network segment belongs so that the fourth domain controller can put the third target network segment into hibernation. After successful hibernation, mark the third target network segment as hibernating. If the third target network segment is in an occupied state, ignore it.

[0064] It should be noted that when a network segment in the wake-up state is not bound to any caller identifier and is not occupied by a wake-up service in the automatic sleep-wake mode (the sleep time of the network segment is less than the current time), it means that the network segment is in an idle state. When a network segment in the wake-up state is bound to any caller identifier or is occupied by a wake-up service in the automatic sleep-wake mode, it means that the network segment is in an occupied state.

[0065] In one specific embodiment of this application, the Wake-on-LAN service has two invocation methods (wake-up modes): automatic sleep mode (automatic sleep-wake-up mode) and manual sleep mode (manual sleep-wake-up mode). The caller can decide which invocation method to use according to business needs. Based on the decided invocation method, the automatic mode parameter (wake-up mode parameter) is set when calling the Wake-on-LAN interface. The specific processes of the two invocation methods are as follows:

[0066] The first calling method: Automatic sleep mode. When the target caller calls the Wake-on-LAN service interface, it sets the automatic mode parameter to automatic sleep, specifies certain CAN network segments to wake up (i.e., the first target network segment), and sets the wake-up duration (Duration, in seconds). After the duration expires, the service will automatically execute the sleep logic, but it may not necessarily sleep; internal decision conflicts may occur. For example, if the same network segment is occupied by both the automatic sleep wake-up service and the manual sleep wake-up mode, when the automatic sleep wake-up service expires, the network segment will not automatically sleep and will need to be manually put into sleep mode. The execution logic is as follows:

[0067] 1. The internal state machine iterates through each relevant network segment (the first target network segment) and executes the wake-up logic:

[0068] 1) If the relevant network segment is already awake, update the sleep time expiretime of the relevant network segment;

[0069] 2) If the relevant network segment is in a dormant state:

[0070] i. Query which domain controller (control execution slave module) the relevant network segment belongs to;

[0071] ii. Call the network segment mode control basic service on this module to wake up the relevant network segment;

[0072] iii. Update the expiration time of the relevant network segment;

[0073] 2. Once all relevant network segments have been traversed, they are all marked as awake.

[0074] 3. The API returned a success message.

[0075] The second calling method: manual sleep mode. This is suitable for operations with long wake-up times or uncertain durations. When the target caller calls the Wake-on-LAN service interface, the automatic mode parameter is set to manual sleep. In this case, the interface is understood as a wake-up persistence interface. It is necessary to compare the network segment wake-up persistence status with the last call from the target caller, and obtain the numbers of the network segments that need to be newly woken up and those that are no longer in use based on the addition or removal of network segments.

[0076] If a new network segment has been added since the last call, the process is as follows:

[0077] 1. The network wake-up scenario service received an interface request;

[0078] 2. Query the mapping relationship between functions and network segments according to the function enumeration values, and determine the relevant network segments;

[0079] 3. Traverse and execute the wake-up logic for each relevant network segment:

[0080] 1) If the relevant network segment is already in a wake-up state, then bind the caller SourceMod (the first target caller identifier) ​​to the relevant network segment;

[0081] 2) If the relevant network segment is in a dormant state:

[0082] i. Query which domain controller (control execution slave module) the relevant network segment belongs to;

[0083] ii. Call the network segment mode control basic service on this module to wake up the relevant network segment;

[0084] iii. Bind the caller SourceMod to the relevant network segment;

[0085] 4. Once all relevant network segments have been traversed, they are all marked as awake.

[0086] 5. The API returned a success message.

[0087] If the number of network segments has decreased compared to the last call, the process is as follows:

[0088] 1. Identify the network segment that has been reduced compared to the previous call (i.e., the third target network segment that is different from the first target network segment), and unbind this network segment from the caller SourceMod. After unbinding, perform the following checks:

[0089] 1) Is the network segment no longer occupied (bound) by any caller SourceMod?

[0090] 2) Whether the network segment is not being used by the automatic wake-up service;

[0091] When the above two conditions are met, perform the following hibernation operation on the network segment:

[0092] i. Query which domain controller (control execution slave module) this network segment belongs to;

[0093] ii. Call the network segment mode control on this module to put the basic service to sleep on this network segment;

[0094] iii. Mark this network segment as dormant;

[0095] 2. Traversal complete;

[0096] 3. The API returned a success message.

[0097] Please see Figure 3 , Figure 3 This is a flowchart illustrating the wake-up request processing of an automatic sleep / wake-up mode, as shown in a specific embodiment of this application. Figure 3 As shown, the wake-up request processing flow includes: receiving a network wake-up service request, including the wake-up request (network wake-up service request), function (target function identifier), duration (wake-up duration), and autorelease (wake-up mode parameters corresponding to automatic sleep / wake-up). Querying the required network segment for the function, i.e., the first target network segment, which must be at least one, and generating a network segment list based on the first target network segment. Traversing the network segment list, taking network segment N in the list as an example, querying whether network segment N has already been woken up; if network segment N is already woken up (state), updating the sleep time expiretime of network segment N in NetList (network segment list), expiretime = now + duration, where now is the current time; if network segment N is not woken up (state), querying which domain controller network segment N belongs to, and issuing a (active) wake-up control command to the domain controller (i.e., the first domain controller) to wake up network segment N. This domain controller can be the primary domain controller itself or a secondary domain controller. If network segment N successfully wakes up, its sleep time `expiretime` is inserted into `NetList`, where `expiretime = now + duration`. If network segment N fails to wake up, the wake-up failure is handled, such as recording the number of the failed network segment N, returning a wake-up failure message, and ending the current wake-up service. After completing the wake-up process for each network segment, it is checked whether the network segment list has been traversed completely. If not, the wake-up process for the next network segment continues until it is completed, at which point a wake-up success message is returned, and the current wake-up service ends. In the wake-up request processing flow of manual sleep-wake mode, the sleep time `expiretime` is a special value, such as FF.

[0098] In one embodiment of this application, the SOA-based vehicle local network wake-up method further includes: receiving network hibernation service call request information, the network hibernation service call request information including a second target caller identifier; querying network segments in the network based on the second target caller identifier to determine a second target network segment that is bound to the second target caller identifier, and unbinding the second target network segment from the second target caller identifier; querying the status of the second target network segment, and if the second target network segment is in an idle state, querying the second domain controller to which the second target network segment belongs according to a preset network segment-domain controller correspondence, so that the second domain controller puts the second target network segment into hibernation.

[0099] In this embodiment, when a caller wants to hibernate its bound network segment, it sends a network hibernation service call request, including a second caller identifier and the network hibernation service call request. The network segment status management module queries the second target network segment bound to the second caller identifier and unbinds the second target network segment from the second target caller identifier. After unbinding, the status of the second target network segment is queried or determined. If the second target network segment is in an idle state, the mapping relationship query module queries the second domain controller to which the second target network segment belongs. A hibernation control command is sent to the second domain controller, invoking the network segment mode control basic service configured by the second domain controller to cause the second domain controller to hibernate the second target network segment. Furthermore, after successful hibernation, the second target network segment is marked as hibernating. If the second target network segment is in an occupied state, this is ignored.

[0100] In one embodiment of this application, a network segment woken up via manual sleep / wake-up mode cannot automatically go into sleep mode and needs to be manually put into sleep mode upon receiving a sleep request (network sleep service call request). Please refer to [link to relevant documentation]. Figure 4 , Figure 4 This is a flowchart illustrating a specific embodiment of the manual hibernation process described in this application. Figure 4 As shown, the sleep request processing flow is as follows:

[0101] The system receives network hibernation service call request information, including the hibernation request and SourceMod (as the second target caller identifier). It queries the network segment corresponding to SourceMod and designates it as the second target network segment. When specifying the network segment to be woken up from hibernation (i.e., the second target network segment), it generates a network segment list based on the second target network segment. The internal state machine traverses the network segment list. Taking network segment N in the list as an example, it unbinds network segment N from SourceMod and determines whether network segment N is currently in a period of wake-up by other services. If network segment N is not bound to any other caller identifier and its hibernation time expires, it is considered that network segment N is not currently in a period of wake-up by other services, i.e., network segment N is in an idle state. Otherwise, it is considered that network segment N is currently in a period of wake-up by other services, i.e., network segment N is in a occupied state. When network segment N is not currently in a period of wake-up by other services, it queries which domain controller manages network segment N and distributes the active hibernation command (manual hibernation command) to the corresponding domain controller (i.e., the second domain controller) to cause that domain controller to hibernate network segment N. If hibernation is successful, the hibernation logic is executed on the next network segment. If hibernation fails, the failure handling sub-process is entered, for example, recording the network segment number that failed to hibernate and returning a hibernation failure message, and then executing the hibernation logic on the next network segment. When network segment N is in the wake-up period of other services, the hibernation logic is executed on the next network segment until the traversal is complete.

[0102] In one embodiment of the present application, the SOA-based vehicle local network wake-up method further includes: polling a woke-up network segment that is in a wake-up state in the network; if the woke-up network segment is in an idle state, querying, according to a preset correspondence between network segments and domain controllers, a third domain controller to which the woke-up network segment belongs, so that the third domain controller puts the woke-up network segment into sleep.

[0103] In this embodiment, a timer may also be set to poll network segments in the wake-up state, and periodically query the status of the woke-up network segment. If the woke-up network segment is in the idle state, the domain controller to which the woke-up network segment belongs is queried through a mapping query module, and used as the third domain controller. A sleep control command is sent to the third domain controller, and the basic network segment mode control service configured by the third domain controller is called, so that the third domain controller puts the woke-up network segment into sleep. In addition, after the sleep is successful, the woke-up network segment is marked as a sleep state. If the woke-up network segment is in an occupied state, it is ignored, and the next poll is waited for.

[0104] In one embodiment of the present application, a network segment woken up only through the automatic sleep-wakeup mode can automatically enter sleep. See Figure 5 , Figure 5 is an automatic sleep flow chart shown in a specific embodiment of the present application. As shown in Figure 5 , when a woken up network segment automatically enters sleep, the flow of an internal state machine traversing woken up network segments is as follows:

[0105] 1. Start traversing the woke-up network segment list NetList;

[0106] 2. Make the following judgments on the network segment (referring to the woke-up network segment):

[0107] 1) Whether the network segment is not occupied by a service that has not been manually put to sleep (woken up), that is, whether the network segment is not occupied by any caller SourceMod;

[0108] 2) Whether the network segment is not occupied by an automatic sleep-wakeup service, that is, whether the sleep time expiretime of the network segment has expired (whether expiretime < now, where now is the current time).

[0109] If both of the above conditions are met, the following sleep operation is performed on the network segment:

[0110] i. Query the domain controller (referring to the third domain controller) to which the network segment belongs;

[0111] ii. Issue a sleep instruction to an instruction execution module under the domain controller, and call the basic network segment mode control service on the module to put the network segment to sleep;

[0112] iii. If the sleep is successful, mark the network segment as a sleep state.

[0113] Regardless of whether the hibernation of a network segment is successful or not, the hibernation logic will continue to be executed on the next network segment until the traversal is complete.

[0114] The awakened network segment should only be put into sleep mode when all callers have stopped occupying the awakened network segment and the automatic sleep time expires.

[0115] Please see Figure 6 , Figure 6 This is a block diagram illustrating an SOA-based vehicle local network wake-up system, as shown in an exemplary embodiment of this application. This system can be applied to... Figure 1 The implementation environment shown can also be applied to other exemplary implementation environments. This embodiment does not limit the implementation environment to which the device is applicable.

[0116] like Figure 6 As shown, this exemplary SOA-based vehicle local network wake-up system includes:

[0117] The request receiving module 610 is used to receive Wake-up Service (WPS) request information, which includes a target function identifier; the mapping relationship query module 620 is used to match network segments in the network based on the target function identifier, determine the first target network segment corresponding to the target function identifier, and query the first domain controller to which the first target network segment belongs according to the preset network segment-domain controller mapping relationship; the network segment status management module 630 is used to query the status of the first target network segment; the control command distribution module 640 is used to send a first control command if the first target network segment is in a dormant state; and the domain controller 650 includes a first domain controller, which is used to wake up the first target network segment in a dormant state according to the first control command.

[0118] In this embodiment, based on the vehicle SOA architecture, a request receiving module 610 (external request processing module) is configured in the SOA-based vehicle local network wake-up system. This external request processing module is responsible for uniformly processing external system requests (network wake-up / sleep service request information) and serves as the entry point for network wake-up / sleep requests from all application layers. A mapping relationship query module 620 is configured in the SOA-based vehicle local network wake-up system to preset function-network segment mapping relationships, so as to match the first target network segment corresponding to the target function identifier from the network segments according to the preset function-network segment mapping relationships. A network segment status management module 630 is configured in the SOA-based vehicle local network wake-up system as an internal system state machine, used to mark and query the status of network segments and execute wake-up and sleep logic. When executing the wake-up logic, the status of the first target network segment is queried. If the first target network segment is in a sleep state, the mapping relationship query module 620 queries the first domain controller corresponding to the first target network segment. The control command distribution module 640 sends a wake-up control command (first control instruction) to the first domain controller in the domain controller 650, invoking the network segment mode control basic service configured on the first domain controller, so that the first domain controller wakes up the target network segment and completes local network wake-up. The mapping relationship query module 620 is also used to preset the network segment-domain controller mapping relationship, so as to query the first domain controller to which the first target network segment belongs based on the preset network segment-domain controller mapping relationship.

[0119] In one embodiment of this application, the domain controller 640 further includes: a second domain controller, configured to put a second target network segment in an idle state into sleep mode according to a second control instruction, wherein the second target network segment is obtained by querying network segments in the network based on a second target caller identifier; a third domain controller, configured to put a woken-up network segment in an idle state into sleep mode according to a third control instruction; and a fourth domain controller, configured to put a third target network segment in an idle state into sleep mode according to a fourth control instruction, wherein the third target network segment is obtained by querying network segments in the network based on a first target caller identifier.

[0120] In this embodiment, when a caller wants to hibernate its bound network segment, it sends a network hibernation service call request to the request receiving module 610, including a second caller identifier and a network hibernation service call request. The network segment status management module 630 queries the second target network segment bound to the second caller identifier and unbinds the second target network segment from the second target caller identifier. After unbinding, the network segment status management module 630 queries or determines the status of the second target network segment. If the second target network segment is in an idle state, it queries the second domain controller to which the second target network segment belongs through the mapping relationship query module 620. The control command distribution module 640 sends a hibernation control command (referring to the second control instruction) to the second domain controller, calling the network segment mode control basic service configured by the second domain controller, so that the second domain controller hibernates the second target network segment.

[0121] In this embodiment, a timer is set in the SOA-based vehicle local network wake-up system to enable the network segment status management module 630 to poll the network segments in the wake-up state and periodically query the status of the woken-up network segments. If the woken-up network segment is in an idle state, the mapping relationship query module 620 queries the third domain controller to which the woken-up network segment belongs. The control command distribution module 640 sends a sleep control command (referring to the third control instruction) to the third domain controller, calling the network segment mode control basic service configured by the third domain controller, so as to put the third domain controller into sleep mode for the woken-up network segment.

[0122] In this embodiment, the Wake-on-LAN service has two wake-up modes: automatic sleep wake-up and manual sleep wake-up. If the wake-up mode is manual sleep wake-up, and if the number of network segments to be woken up by the caller corresponding to the first target caller identifier is less than that of the last Wake-on-LAN service call, the binding relationship between the first target caller identifier and the network segments other than the target network segment can be released. Specifically, the network segment status management module 630 queries the network for the third target network segment that is bound to the first target caller identifier based on the first target caller identifier, compares the third target network segment with the first target network segment, and if the third target network segment and the first target network segment are different network segments, the binding relationship between the third target network segment and the first target caller identifier is released. If the third target network segment and the first target network segment are the same network segment, the binding relationship between the third target network segment and the first target caller identifier is not released.

[0123] After unbinding the third target network segment from the first target caller identifier, the following operations can be performed: The network segment status management module 630 queries the status of the third target network segment. If the third target network segment is in an idle state, the mapping relationship query module 620 queries the fourth domain controller to which the third target network segment belongs, and sends a hibernation control command (referring to the fourth control instruction) to the fourth domain controller through the control command distribution module 640, calling the network segment mode control basic service configured by the fourth domain controller so that the fourth domain controller puts the third target network segment into hibernation.

[0124] Please see Figure 7 , Figure 7 This is a schematic diagram illustrating the structure of a vehicle local network wake-up system based on SOA, as shown in a specific embodiment of this application. Figure 7 As shown, the structure of the SOA-based vehicle local network wake-up system includes: an external request processing module, a network segment status management module, a mapping relationship query module, a control command distribution module, and a control execution module. The external request processing module is responsible for uniformly receiving and processing network wake-up service requests or network hibernation service requests sent by external services. It is the entry point for all application layer network hibernation / wake-up service requests. External services include subsystems such as exterior lights, windows, and air conditioning, which aggregate system services. The network segment status management module is an internal state machine responsible for executing network segment wake-up / hibernation logic and querying and marking the hibernation / wake-up status of network segments. It is the main controller of the business logic. The mapping relationship query module is used to configure and query the mapping relationship between "function-network segment" and "network segment-domain controller". The control command distribution module is responsible for distributing control commands to the control execution modules on different domain controllers for execution. The control execution module integrates the ComM network management component and is the actual executor of wake-up / hibernation for network segments.

[0125] The external request processing module, network segment status management module, mapping relationship query module, and control command distribution module are deployed within the VIUFL. There are three control execution modules, deployed within the VIUFL, VIUFR, and VIUR respectively. To maintain a unified entry point, the network wake-up / sleep service on the VIUFL serves as the sole request entry point for this local network wake-up / sleep function; external requests also include those from the VIUFR and VIUR. The VIUFL, as the main entry point for the business process and the main module for running business logic, receives business requests (network wake-up / sleep service requests), manages the wake-up / sleep status of each network segment, and distributes control commands to the control execution modules within each VIU (including itself). The main module implements the core business logic, i.e., external network wake-up service requests or external network sleep service requests, and internally configures a timer to poll whether a network segment should be in sleep mode. Each VIU (VIUFL, VIUFR, and VIUR) deploys a control execution module containing local wake-up / sleep functionality. This control execution module, through integration with the ComM network management component, implements actual sleep, wake-up, and query management functions for the CAN network segments connected to the domain controller.

[0126] It should be noted that the first domain controller, the second domain controller, the third domain controller, and the fourth domain controller in the embodiments of this application can be the same domain controller or different domain controllers. Similarly, the first target network segment, the second target network segment, and the third target network segment in the embodiments of this application can be the same network segment or different network segments.

[0127] It should be noted that the SOA-based vehicle local network wake-up system and the SOA-based vehicle local network wake-up method provided in the above embodiments belong to the same concept. The specific methods by which each module and unit performs operations have been described in detail in the method embodiments and will not be repeated here. In practical applications, the SOA-based vehicle local network wake-up system provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. This is not a limitation here.

[0128] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the electronic device to implement the SOA-based vehicle local network wake-up method provided in the above embodiments.

[0129] Please see Figure 8 , Figure 8A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 8 The computer system 800 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0130] like Figure 8 As shown, the computer system 800 includes a Central Processing Unit (CPU) 801, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 802 or programs loaded from storage portion 808 into Random Access Memory (RAM) 803, such as performing the methods described in the above embodiments. The RAM 803 also stores various programs and data required for system operation. The CPU 801, ROM 802, and RAM 803 are interconnected via a bus 804. An Input / Output (I / O) interface 805 is also connected to the bus 804.

[0131] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 810 as needed so that computer programs read from it can be installed into storage section 808 as needed.

[0132] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable medium 811. When the computer program is executed by central processing unit (CPU) 801, it performs various functions defined in the system of this application.

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

[0134] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0135] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0136] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a computer's processor, causes the computer to perform the SOA-based vehicle local network wake-up method as described above. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not incorporated into the electronic device.

[0137] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the SOA-based vehicle local network wake-up method provided in the various embodiments described above.

[0138] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. A SOA-based vehicle local network wake-up method, characterized in that, The SOA-based vehicle local network wake-up method includes: Receive a Wake-on-LAN service request message, wherein the Wake-on-LAN service request message includes a target function identifier; Based on the target function identifier, network segments in the network are matched to determine the first target network segment corresponding to the target function identifier; If the first target network segment is in a dormant state, the first domain controller to which the first target network segment belongs is queried according to the preset network segment-domain controller correspondence, so that the first domain controller wakes up the first target network segment and completes the vehicle local network wake-up; the wake-up mode of the first target network segment is determined according to the wake-up mode parameters, the wake-up mode includes automatic sleep wake-up or manual sleep wake-up, and the wake-up service call request information also includes the wake-up mode parameters; if the wake-up mode is automatic sleep wake-up, the sleep time of the first target network segment is updated based on the wake-up duration, and the wake-up service call request information also includes the wake-up duration; if the wake-up mode is manual sleep wake-up, the first target network segment is bound to the first target caller identifier, and the wake-up service call request information also includes the first target caller identifier; If the first target network segment is in a wake-up state, the wake-up mode of the first target network segment is determined according to the wake-up mode parameters; if the wake-up mode is automatic sleep wake-up, the sleep time of the first target network segment is updated based on the wake-up duration; if the wake-up mode is manual sleep wake-up, the first target network segment is bound to the first target caller identifier. Among them, the priority of manual sleep-wake mode is higher than that of automatic sleep-wake mode. When the first target network segment corresponding to the manual sleep-wake service and the first target network segment corresponding to the automatic sleep-wake service are the same network segment, the conflict is decided according to the priority.

2. The SOA-based vehicle local network wake-up method according to claim 1, characterized in that, Before binding the first target network segment with the first target caller identifier, the SOA-based vehicle local network wake-up method includes: Query the binding relationship between the first target network segment and the first target caller identifier; If the binding relationship is not bound, then the first target network segment will be bound to the first target caller identifier.

3. The SOA-based vehicle local network wake-up method according to claim 1 or 2, characterized in that, The SOA-based vehicle local network wake-up method further includes: Receive network hibernation service call request information, wherein the network hibernation service call request information includes a second target caller identifier; Based on the second target caller identifier, the network segments in the network are queried to determine the second target network segment that is bound to the second target caller identifier, and the binding relationship between the second target network segment and the second target caller identifier is released; The status of the second target network segment is queried. If the second target network segment is in an idle state, the second domain controller to which the second target network segment belongs is queried according to the preset correspondence between network segments and domain controllers, so that the second domain controller puts the second target network segment into hibernation.

4. The SOA-based vehicle local network wake-up method according to claim 1 or 2, characterized in that, The SOA-based vehicle local network wake-up method further includes: Poll the woken-up network segments in the network that are in the wake-up state; If the woken-up network segment is in an idle state, then according to the preset network segment-domain controller correspondence, the third domain controller to which the woken-up network segment belongs is queried, so that the third domain controller puts the woken-up network segment into hibernation.

5. The SOA-based vehicle local network wake-up method according to claim 1, characterized in that, If the wake-up mode is manual sleep wake-up, the SOA-based vehicle local network wake-up method further includes: Based on the first target caller identifier, the network segment in the network is queried. If a third target network segment that is bound to the first target caller identifier is found, and the third target network segment is a different network segment from the first target network segment, then the binding relationship between the third target network segment and the first target caller identifier is released. The status of the third target network segment is queried. If the third target network segment is in an idle state, the fourth domain controller to which the third target network segment belongs is queried according to the preset network segment-domain controller correspondence, so that the fourth domain controller puts the third target network segment into hibernation.

6. The SOA-based vehicle local network wake-up method according to claim 3, characterized in that, The domain controller includes a master domain controller and slave domain controllers. The master domain controller serves as a unified interface to receive network wake-up service call request information or network hibernation service call request information.

7. A vehicle local network wake-up system based on SOA, characterized in that, The SOA-based vehicle local network wake-up system includes: A request receiving module is used to receive Wake-up Service request information, wherein the Wake-up Service request information includes a target function identifier. The mapping relationship query module is used to match network segments in the network based on the target function identifier, determine the first target network segment corresponding to the target function identifier, and query the first domain controller to which the first target network segment belongs according to the preset network segment-domain controller correspondence. The network segment status management module is used to query the status of the first target network segment; determine the wake-up mode of the first target network segment according to the wake-up mode parameters, wherein the wake-up mode includes automatic sleep wake-up or manual sleep wake-up, and the wake-up service call request information also includes the wake-up mode parameters; if the wake-up mode is automatic sleep wake-up, the sleep time of the first target network segment is updated based on the wake-up duration, and the wake-up service call request information also includes the wake-up duration; if the wake-up mode is manual sleep wake-up, the first target network segment is bound to the first target caller identifier, and the wake-up service call request information also includes the first target caller identifier; wherein, the priority of the manual sleep wake-up mode is higher than the priority of the automatic sleep wake-up mode, and when the first target network segment corresponding to the manual sleep wake-up service and the first target network segment corresponding to the automatic sleep wake-up service are the same network segment, the conflict is decided according to the priority. The control command distribution module is used to send a first control command if the first target network segment is in a dormant state. A domain controller, including the first domain controller, is configured to wake up the first target network segment that is in a dormant state according to the first control command.

8. The SOA-based vehicle local network wake-up system according to claim 7, characterized in that, The domain controller also includes: The second domain controller is used to put the second target network segment, which is in an idle state, into hibernation according to the second control command. The second target network segment is obtained by querying the network segments in the network based on the second target caller identifier. The third domain controller is used to put awakened network segments that are in an idle state into hibernation according to third control instructions; The fourth domain controller is used to put the third target network segment, which is in an idle state, into hibernation according to the fourth control command. The third target network segment is obtained by querying the network segments in the network based on the first target caller identifier.

9. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the SOA-based vehicle local network wake-up method as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the SOA-based vehicle local network wake-up method as described in any one of claims 1 to 6.

Images