SOMEIP-based data processing method and device, equipment and medium

Abstract

The embodiment of the invention provides a data processing method and device based on SOMEIP, equipment and a medium, and belongs to the technical field of vehicle communication. The method comprises the following steps: acquiring a target event group required by a communication service, wherein the target event group comprises a plurality of pieces of initial state change data; determining candidate state change data from the plurality of initial state change data; generating a first subscription message based on the candidate state change data and the target event group; generating at least one second subscription message based on the remaining initial state change data and the target event group, and sending the first subscription message and the second subscription message to the server; and after a subscription success notification signal responded by the server based on the first subscription message is received, sending a confirmation message to the server, and receiving a data initial value corresponding to each piece of initial state change data sent by the server. According to the embodiment of the invention, the packet loss rate of the event can be reduced, and the initial value judgment problem of the field notification is solved.

Description

Technical Field

[0001] The present application relates to the field of vehicle communication technology, and in particular to a data processing method and apparatus, device and medium based on SOMEIP. Background Art

[0002] As autonomous driving technology in intelligent connected vehicles becomes more and more complex, in the field of software development of the microprocessor unit (MPU) of the vehicle controller, a communication solution based on service-oriented middleware technology (Scalable Service-Oriented Middleware over IP, SOMEIP) implemented on top of a network protocol is usually used for communication design, and is usually suitable for communication scenarios such as events and fields between servers and clients developed based on the SOMEIP protocol stack.

[0003] In the related art, the SOMEIP interface level usually subscribes in units of Event or Field Notify (i.e., notifications related to fields), and the SOMEIP service message usually subscribes in units of EventGroup. When an Event / Field Notify in the client starts to subscribe, the server will think that all Event / Field Notify have completed the subscription, and will send the initial values ​​of all Event / Field Notify. In this way, it is easy for unsubscribed Event or Field Notify to fail to receive accurate initial values, resulting in a high packet loss rate of Event, and FieldNotify is prone to initial value determination problems, thereby affecting the communication efficiency between the server and the client. Therefore, how to reduce the packet loss rate of Event and solve the initial value determination problem of Field Notify, thereby improving the communication efficiency between the server and the client, has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] The main purpose of the embodiments of the present application is to propose a data processing method and apparatus, device and medium based on SOMEIP, aiming to reduce the packet loss rate of Event and solve the initial value determination problem of Field Notify, thereby improving the communication efficiency between the server and the client.

[0005] To achieve the above-mentioned purpose, a first aspect of an embodiment of the present application proposes a data processing method based on SOMEIP, which is applied to a client, and the client is connected to a server for communication. The method includes:

[0006] Acquire a target event group corresponding to a communication service demand in a target network communication; wherein the target event group includes a plurality of initial state change data, and the initial state change data is used to indicate an event or field notification of a state change in the target network communication;

[0007] Determine candidate state change data from the plurality of initial state change data based on preset subscription call parameters;

[0008] Generate a first subscription message based on the candidate state change data and the target event group;

[0009] generating at least one second subscription message based on the remaining initial state change data and the target event group, and sending the first subscription message and the second subscription message to the server;

[0010] After receiving a subscription success notification signal from the server in response to the first subscription message, an initial data value corresponding to each of the initial state change data sent by the server is received.

[0011] In some embodiments, generating a first subscription message based on the candidate state change data and the target event group includes:

[0012] Marking the candidate state change data based on preset labels to obtain target state change data;

[0013] The first subscription message is generated based on the target state change data and the target event group.

[0014] In some embodiments, the determining the candidate state change data from the plurality of the initial state change data based on the preset subscription call parameter includes:

[0015] Arrange the plurality of initial state change data based on the preset subscription call parameter to obtain a state change data list, wherein the state change data list is used to indicate the order in which the plurality of initial state change data call the preset subscription call parameter;

[0016] The candidate state change data is determined based on the state change data list, where the candidate state change data is used to represent the initial state change data of the last one in the target event group that calls the preset subscription call parameter.

[0017] In some embodiments, the preset subscription call parameters include business logic data, data dependency, data priority and resource restriction data corresponding to the communication business requirements; the data of the plurality of initial state change data are arranged based on the preset subscription call parameters to obtain a state change data list, including

[0018] Performing data scoring on the initial state change data based on the business logic data to obtain a first score;

[0019] Performing data scoring on the initial state change data based on the data dependency relationship to obtain a second score;

[0020] Performing data scoring on the initial state change data based on the data priority to obtain a third score;

[0021] Performing data scoring on the initial state change data based on the resource restriction data to obtain a fourth score;

[0022] determining a target score for the initial state change data based on the first score, the second score, the third score, and the fourth score;

[0023] The plurality of initial state change data are arranged in descending order based on the target score to obtain the state change data list.

[0024] In some embodiments, obtaining a target event group corresponding to a communication service demand in target network communication includes:

[0025] Performing data analysis on the communication service requirements in the target network communication to obtain service-related data and service scenario data, wherein the service-related data is used to indicate an event or field notification related to the service logic of the communication service requirements, and the service scenario data is used to indicate an event or field notification related to the scenario corresponding to the communication service requirements;

[0026] Based on the business association data and the business scenario data, a plurality of the initial state change data are acquired from a preset state data set, and the target event group is constructed based on the plurality of the initial state change data.

[0027] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application proposes a data processing method based on SOMEIP, which is applied to a server, and the server is connected to a client for communication. The method includes:

[0028] Receive a candidate subscription message based on a target event group sent by the client; wherein the candidate subscription message includes a first subscription message and a second subscription message, the first subscription message is used to indicate the candidate state change data determined from a plurality of initial state change data of the target event group, and the second subscription message is used to indicate the remaining initial state change data in the target event group;

[0029] When the candidate subscription message is the first subscription message, a subscription success notification signal is sent to the client, and an initial value of data corresponding to each of the initial state change data in the target event group is sent to the client.

[0030] In some embodiments, before sending a subscription success notification signal to the client when the candidate subscription message is the first subscription message, the method further includes:

[0031] Parsing the candidate subscription message to obtain parsed data, wherein the parsed data includes a parsed tag;

[0032] Performing label detection on the candidate subscription message based on the preset label and the parsed label to obtain a label detection result;

[0033] The candidate subscription message is determined to be the first subscription message or the second subscription message based on the tag detection result.

[0034] To achieve the above-mentioned purpose, a third aspect of an embodiment of the present application proposes a data processing device based on SOMEIP, the device comprising:

[0035] An acquisition module, used to acquire a target event group corresponding to a communication service demand in a target network communication; wherein the target event group includes a plurality of initial state change data, and the initial state change data is used to indicate an event or field notification of a state change in the target network communication;

[0036] A determination module, configured to determine candidate state change data from a plurality of the initial state change data based on a preset subscription call parameter;

[0037] A first message generating module, configured to generate a first subscription message based on the candidate state change data and the target event group;

[0038] A second message generation module, configured to generate at least one second subscription message based on the remaining initial state change data and the target event group, and send the first subscription message and the second subscription message to a server;

[0039] The first receiving module is used to receive the data initial value corresponding to each initial state change data sent by the server after receiving the subscription success notification signal responded by the server based on the first subscription message.

[0040] To achieve the above-mentioned objectives, the fourth aspect of an embodiment of the present application proposes an electronic device, comprising: at least one processor; at least one memory for storing at least one program; when the at least one program is executed by the at least one processor, the at least one processor implements a data processing method based on SOMEIP as described in the first aspect above; or, a data processing method based on SOMEIP as described in the second aspect above.

[0041] To achieve the above-mentioned purpose, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements a data processing method based on SOMEIP as described in the first aspect above; or, a data processing method based on SOMEIP as described in the second aspect above.

[0042] The present application proposes a data processing method and device based on SOMEIP, an apparatus, a device and a medium, which receives the initial data value corresponding to each initial state change data sent by the server only after receiving the subscription success notification signal based on the first subscription message response at the server. Specifically, the client obtains the target event group corresponding to the communication service demand in the target network communication, the target event group includes multiple initial state change data, and the initial state change data is used to indicate the event or field notification of the state change in the target network communication; further, based on the preset subscription call parameters, the candidate state change data is determined from the multiple initial state change data; further, the first subscription message is generated based on the candidate state change data and the target event group; at least one second subscription message is generated based on the remaining initial state change data and the target event group, and the first subscription message and the second subscription message are sent to the server; further, after receiving the subscription success notification signal based on the first subscription message response from the server, the initial data value corresponding to each initial state change data sent by the server is received. The first subscription message of the embodiment of the present application is a message generated by the present application based on a predetermined event or field notification with specific significance, which can accurately indicate the subscription status sent by the client to the server. Therefore, the present application will receive the accurate initial data value sent by the server only after receiving the subscription success notification signal from the server based on the response to the first subscription message, which can effectively reduce the packet loss rate of the Event and solve the initial value determination problem of the Field Notify, thereby improving the communication efficiency between the server and the client. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It is the first flow chart of the data processing method based on SOMEIP provided in the embodiment of the present application;

[0044] Figure 2 yes Figure 1 A flowchart of step S110 in FIG.

[0045] Figure 3 yes Figure 1 A flowchart of step S120 in FIG.

[0046] Figure 4 yes Figure 3 A flowchart of step S310 in FIG.

[0047] Figure 5 yes Figure 1 A flowchart of step S130 in FIG.

[0048] Figure 6 is a second flow chart of the data processing method based on SOMEIP provided in the embodiment of the present application;

[0049] Figure 7 is the third flow chart of the data processing method based on SOMEIP provided in the embodiment of the present application;

[0050] Figure 8 It is an interactive diagram of the data processing method based on SOMEIP provided in the embodiment of the present application;

[0051] Fig. 9 is a structural diagram of a data processing device based on SOMEIP provided in an embodiment of the present application;

[0052] Fig.10 Another structural diagram of a data processing device based on SOMEIP provided in an embodiment of the present application

[0053] Fig.11 It is a hardware structure diagram of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0055] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0056] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0057] First, some nouns involved in this application are analyzed:

[0058] Scalable Service-Oriented Middleware over IP (SOMEIP): is an automotive embedded communication protocol that is mainly used to control message communication and supports remote service calls, service publishing / subscription, serialization, and service discovery. The SOMEIP protocol is an IP-based service-oriented middleware that can achieve efficient service exchange and remote calls.

[0059] Event: It is a signal that a specific action or state change has occurred. In event-driven programming, events can be detected by subscribers, and when an event occurs, all subscribers who have subscribed to the event will be notified. For example, a user clicks a button, or a network request successfully returns data, these are all events. Among them, Event communication scenarios are widely used in vehicle dynamic monitoring, fault diagnosis, safety warning and other functions. For example, when the tire pressure of a vehicle changes, the sensor generates an Event message and sends it to the vehicle control system through the SOMEIP protocol so that appropriate measures can be taken.

[0060] Field: It is a representation of an object's attributes and is used to store the object's state information. In object-oriented programming, a field is usually a member variable of a class, which can be accessed and modified through getter and setter methods. Fields can contain various types of data, such as integers, strings, Boolean values, etc. Among them, Field communication scenarios are widely used in vehicle control systems, comfort systems, entertainment systems, etc. For example, in an autonomous driving system, sensors and control units need to exchange information such as the vehicle's position, speed, and direction in real time through Field communication in order to achieve precise control. Therefore, the Event and Field communication scenarios developed based on the SOMEIP protocol stack cover various data interaction requirements between different components in the automotive network, providing strong support for the realization of intelligent and efficient vehicle systems.

[0061] Field Notify: is a special mechanism used to notify relevant subscribers when the field value changes. When the value of a field changes, the system will automatically trigger a notification to notify all subscribers who have subscribed to the field change. This mechanism is usually used to implement data binding and data synchronization to ensure that UI components can reflect data changes in real time.

[0062] Service: In SOMEIP, a service is an entity that provides a specific function or operation. Clients can subscribe to events in a service to receive notifications when events occur.

[0063] Microprocessor Unit (MPU): In the automotive field, MPU usually refers to a highly integrated chip that can perform complex computing tasks and logic control. It is one of the core components in automotive electronic systems.

[0064] As the autonomous driving technology in intelligent connected cars becomes more and more complex, for example, in the field of software development of the microprocessor unit (MPU) of the car controller, the communication scheme of Scalable Service-Oriented Middleware over IP (SOMEIP) based on the network protocol is usually used for communication design, and is usually suitable for communication scenarios such as events and fields between the server and the client developed based on the SOMEIP protocol stack. However, this also requires developers to clearly understand the design scheme of Event, Method, and Field under the SOMEIP scheme, and ensure the real-time and stability of communication.

[0065] In the related art, the SOMEIP interface level usually subscribes in units of Event or Field Notify (i.e., notifications related to fields), and the SOMEIP service message usually subscribes in units of EventGroup. When an Event / Field Notify in the client starts to subscribe, the server will think that all Event / Field Notify have completed the subscription, and will send the initial values ​​of all Event / Field Notify. In this way, it is easy for unsubscribed Event or Field Notify to fail to receive accurate initial values, resulting in a high packet loss rate of Event, and FieldNotify is prone to initial value determination problems, thereby affecting the communication efficiency between the server and the client. In addition, the related art also proposes to input the service ID, the event group ID to which the method belongs, and the communication configuration information into a pre-made configuration template through a configuration generation script to generate a configuration file for running the code file, but does not explain how to design and optimize the service. Therefore, how to reduce the packet loss rate of Event and solve the initial value determination problem of Field Notify, thereby improving the communication efficiency between the server and the client, has become a technical problem to be solved urgently.

[0066] Based on this, the embodiments of the present application provide a data processing method and apparatus, device and medium based on SOMEIP, aiming to reduce the packet loss rate of Event and solve the initial value determination problem of Field Notify, thereby improving the communication efficiency between the server and the client.

[0067] The data processing method based on SOMEIP provided in the embodiment of the present application can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal (i.e., the client) or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN) and big data and artificial intelligence platforms; the software can be an application that implements the data processing method based on SOMEIP, etc., but is not limited to the above forms. Therefore, if the data processing method based on SOMEIP provided in the embodiment of the present application is applied to the server side, the server side can be connected to at least one vehicle-mounted terminal for communication.

[0068] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network personal computers (Personal Computer, PC), minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0069] In some embodiments, see Figure 1 , Figure 1 This is an optional flow chart of the SOMEIP-based data processing method provided in the embodiment of the present application. The SOMEIP-based data processing method applied to the client may include but is not limited to steps S110 to S150:

[0070] Step S110, obtaining a target event group corresponding to a communication service demand in a target network communication;

[0071] Step S120, determining candidate state change data from a plurality of initial state change data based on preset subscription call parameters;

[0072] Step S130, generating a first subscription message based on the candidate state change data and the target event group;

[0073] Step S140, generating at least one second subscription message based on the remaining initial state change data and the target event group, and sending the first subscription message and the second subscription message to the server;

[0074] Step S150, after receiving the subscription success notification signal from the server in response to the first subscription message, receiving the initial data value corresponding to each initial state change data sent by the server.

[0075] Steps S110 to S150 shown in the embodiment of the present application determine candidate state change data from multiple initial state change data in the target event group to generate a first subscription message and at least one second subscription message, thereby further receiving the initial value of the data based on the subscription success notification signal received from the server in response to the first subscription message. It focuses on the scenario of multiple Events and Field Notifies under the same service, and specifically discloses how to design an event group and the subscription and communication logic for the Event and Field Notify in the event group, reduces the packet loss rate of the Event, and can solve the problem that the initial values ​​of the Event and Field Notify cannot be normally received by the client after service discovery is established.

[0076] In step S110 of some embodiments, the target event group refers to a collection of multiple event / field notifications under the same service corresponding to the communication service demand in the target network communication. The communication service demand defines the user's expectations for the communication service, including speed, stability, security, etc. Service discovery is a technology in the communication system that allows service instances to be dynamically registered and discovered, thereby improving the flexibility and scalability of the system. Among them, the target network communication refers to the communication established between the server and the client based on the SOMEIP device. The target event group includes multiple initial state change data, and each initial state change data is used to indicate an event or field notification (Event / FieldNotify) of a state change in the target network communication.

[0077] It should be noted that multiple event / field notifications under the same service means that a service can contain multiple different events and fields. For example, suppose there is a service called "CarService", which can contain the following events: "engine_started", which indicates the event triggered when the engine is started; "speed_changed", which indicates the event triggered when the vehicle speed changes. It can also contain the following fields: "current_speed", which indicates the field of the current vehicle speed; "fuel_level", which indicates the field of the remaining fuel. In this way, the client can subscribe to these event / field notifications to receive corresponding notifications, and can also read or modify the values ​​of these fields to understand the status of the vehicle.

[0078] It should be noted that if an event group is designed to include only one Event / Field Notify, it will increase the bandwidth requirements of Ethernet and does not conform to the design concept of Group. Therefore, the target event group of this application includes multiple initial state change data, which can reduce the bandwidth pressure of Ethernet and improve communication efficiency.

[0079] It should be noted that an event group can contain many Event / Field Notify. For the prior art, when an Event / Field Notify in the client starts to subscribe, since the subscription is performed in units of event groups at the interface level, the server will think that all Event / Field Notify have completed the subscription, and will send the initial values ​​of all Event / Field Notify. However, for the client, only when the subscription message corresponding to the Event / Field Notify generated in units of event groups in the client is sent to the server, the interface corresponding to the Event / Field Notify can receive the initial value sent by the server, otherwise it cannot receive the corresponding initial value. Therefore, since there are still many Event / Field Notify that have not started to subscribe, the initial value of Event / Field Notify sent by the server cannot be received, so there is a situation where the initial value of some Event / Field Notify is lost. In addition, the client usually needs to make a logical judgment based on whether the initial value of Event / FieldNotify has changed, but if the value of the first Event / Field Notify has not been received, the client will not be able to accurately identify when the value of Event / Field Notify has changed.

[0080] It should be noted that, in practical applications, reducing the packet loss rate of Events and solving the problem that the initial values ​​of Events and Field Notify cannot be normally received by the client after service discovery is established can effectively solve the synchronization problem in actual communication (i.e., the receiver needs the correct initial value to synchronize with the sender. If the initial value is lost, the receiver may not be able to correctly synchronize with the sent signal, resulting in data parsing errors), data integrity damage problem (i.e., the initial value is usually used to set the starting state of communication. If this state is lost or wrong, it may cause incorrect interpretation of subsequent data streams, affecting data integrity), performance degradation problem (i.e., in communication systems that need to initialize certain parameters, such as keys or session parameters for encrypted communication, the loss of initial values ​​may lead to reduced communication efficiency because the system may need to renegotiate these parameters), resource waste problem (i.e., when trying to regain the lost initial value, additional time and computing resources may be consumed, which is particularly problematic in some systems with high real-time requirements), user experience degradation problem (i.e., for end users, the loss of communication initial values ​​may cause service interruption, delay or other forms of service quality degradation), error propagation problem (i.e., in some systems, incorrect initial values ​​may cause a chain reaction, affecting the normal operation of other parts of the system), etc.

[0081] In some embodiments, see Figure 2 , Figure 2 This is an optional flowchart of step S110 provided in the embodiment of the present application. Step S110 may specifically include but is not limited to steps S210 to S220:

[0082] Step S210, performing data analysis on the communication service requirements in the target network communication to obtain service-related data and service scenario data;

[0083] Step S220: acquiring a plurality of initial state change data from a preset state data set based on the business association data and the business scenario data, and constructing a target event group based on the plurality of initial state change data.

[0084] In step S210 of some embodiments, when constructing an event group, all Event / Field Notify under the same service can be designed in the same event group according to the communication service requirements. At this time, the communication service requirements in the target network communication can be first parsed to obtain service-related data and service scenario data. Among them, the service-related data is used to indicate the event or field notification related to the business logic of the communication service requirements, and the service scenario data is used to indicate the event or field notification related to the scenario corresponding to the communication service requirements.

[0085] It should be noted that the communication service demand refers to the goal that the organization setting up the service hopes to achieve, the service-related data may refer to the relationship between the communication service demand and other services or services, and the service scenario data may refer to the scenario information required to realize the communication service demand, which can reflect the performance and demand of the communication service in different scenarios. The disclosed embodiment can obtain service-related data and service scenario data that are of great significance for optimizing communication services, improving communication efficiency, and enhancing communication security by performing data analysis on the communication service demand in the target network communication.

[0086] In step S220 of some embodiments, further, multiple initial state change data are obtained from a preset state data set based on the business association data and the business scenario data, and a target event group is constructed based on the multiple initial state change data. The preset state data set refers to a pre-constructed set including a complete Event / Field Notify, so the state change data that matches the business association data and the business scenario data can be used as the initial state change data to construct the target event group.

[0087] In the above embodiments, the present application can centralize all relevant events and field notifications into one event group, which helps to simplify synchronization logic, improve system efficiency, and facilitate code management and maintenance.

[0088] In step S120 of some embodiments, the preset subscription call parameter refers to a pre-set parameter for determining candidate state change data from multiple initial state change data. The candidate state change data is a specific Event / Field Notify selected by the present application from multiple initial state change data, which is used to trigger the subscription of the subsequent target event group, that is, to enable the server to know whether to send the initial value corresponding to each Event / Field Notify in the target event group to the client.

[0089] In some embodiments, see Figure 3 , Figure 3 This is an optional flowchart of step S120 provided in the embodiment of the present application. Step S120 may specifically include but is not limited to steps S310 to S320:

[0090] Step S310, arranging a plurality of initial state change data based on preset subscription call parameters to obtain a state change data list;

[0091] Step S320: determining candidate state change data based on the state change data list.

[0092] In step S310 and step S320 of some embodiments, when determining the candidate state change data, the present application may first arrange the data of the multiple initial state change data based on the preset subscription call parameter to obtain a state change data list, and the state change data list is used to indicate the order in which the multiple initial state change data call the preset subscription call parameter. Further, the candidate state change data is determined from the state change data list, and the candidate state change data is used to represent the initial state change data of the last one in the target event group that calls the preset subscription call parameter.

[0093] It should be noted that the preset subscription call parameters correspond to a subscription function, that is, the candidate state change data is used to represent the initial state change data of the last subscription function called in the target event group. When calling the subscription function, the initial state change data will follow the SOMEIP design specification and subscribe to events in units of Event / Field Notify, but when sending to the server, the subscription message will be sent in units of event groups.

[0094] In some embodiments, the preset subscription call parameters may be parameters corresponding to a standard subscription function. In this case, the calls to the initial state change data in the target event group may be sorted according to the parameters corresponding to the standard subscription function, and the initial state change data of the last call to the standard subscription function may be determined as the specific candidate state change data. In this way, it can be ensured that the Event / Notify in the target event group can obtain the initial value.

[0095] It should be noted that the subscription function in communication usually refers to a function that allows an entity (subscriber) to register and receive messages from another entity (publisher). This function is a core component of the publish / subscribe model and is widely used in software engineering, especially in scenarios where decoupling and asynchronous communication between components are required.

[0096] In other embodiments, the preset subscription call parameters may also be parameters corresponding to a subscription function customized according to communication service requirements. In this case, the preset subscription call parameters include business logic data, data dependencies, data priorities, and resource restriction data corresponding to the communication service requirements, such as allowing subscribers to subscribe to specific topics according to their interests. When a message of the corresponding topic is published, the subscriber can receive the message. This function plays a key role in the publish / subscribe mode, realizing flexible distribution and reception of messages.

[0097] See also Figure 4 , Figure 4 It is an optional flowchart of step S310 provided in an embodiment of the present application.

[0098] The step S310 may specifically include but is not limited to steps S410 to S460:

[0099] Step S410, performing data scoring on the initial state change data based on the business logic data to obtain a first score;

[0100] Step S420, performing data scoring on the initial state change data based on the data dependency relationship to obtain a second score;

[0101] Step S430, scoring the initial state change data based on the data priority to obtain a third score;

[0102] Step S440, performing data scoring on the initial state change data based on the resource restriction data to obtain a fourth score;

[0103] Step S450, determining a target score for the initial state change data based on the first score, the second score, the third score, and the fourth score;

[0104] Step S460: Arrange the multiple initial state change data in descending order based on the target score to obtain a state change data list.

[0105] In steps S410 to S440 of some embodiments, the business logic data is used to indicate the order of business logic, which means that the logical order of the initial state change data in the actual business process can be considered when arranging, that is, the higher the logical order in the actual business process, the higher the corresponding first score may be. Data dependency is used to indicate that some event / field notifications may depend on the results of other events or notifications, which means that when arranging, it is necessary to ensure that those event / field notifications as dependencies are processed first, that is, the second score corresponding to the event / field notification as a dependency may be higher. Data priority is used to indicate the priority corresponding to different event / field notifications, where high-priority event / field notifications should be processed before low-priority events or notifications, which means that when arranging, the third score corresponding to the high-priority event / field notification may be higher. Resource restriction data is used to indicate the resource restrictions that may be encountered when processing event / field notifications, such as insufficient memory, high CPU occupancy, etc. In this case, it is necessary to weigh the use of resources and reasonably arrange the processing order of event / field notifications. In this way, the fourth score corresponding to the event / field notification with higher resource restrictions may be higher when arranging. It should be noted that the above data scoring under different conditions can be flexibly selected and adjusted according to actual conditions. For example, in order to process more events or field notifications, the fourth score corresponding to the event / field notification with higher resource constraints can be set lower, which is not limited here.

[0106] In step S450 and step S460 of some embodiments, the present application may set corresponding weights for the parameters included in the preset subscription call parameters, so that after obtaining the first score, second score, third score and fourth score corresponding to each initial state change data, weighted sum calculations may be performed based on the first score, second score, third score and fourth score and the corresponding weights to determine the target score corresponding to each initial state change data. Further, by arranging the multiple initial state change data in descending order based on the target score, a state change data list may be obtained, so that the last candidate state change data for calling the subscription function may be determined from the state change data list.

[0107] It should be noted that the preset subscription call parameters of the present application may also include parameters such as real-time requirements, concurrent processing and error handling, without limitation. Therefore, when arranging multiple event / field notifications of the same event group based on the calling order of the subscription function, the present application can comprehensively consider business logic, dependencies, priorities, resource limitations, real-time requirements, concurrent processing and error handling and other factors to ensure stable operation and efficient processing of the system.

[0108] In step S130 of some embodiments, after determining the candidate state change data and the remaining initial state change data, the present application can generate and send subscription messages on the client side in units of event groups, that is, the subscription message based on the event group can carry which Event / Field Notify initiated the EventGroup subscription message.

[0109] It should be noted that the subscription message of the event / field notification is used to establish the subscription process. Only after the subscription process is successfully established, the data will be sent from the server to the client, and each event / field notification will generate a corresponding subscription message.

[0110] In some embodiments, see Figure 5 , Figure 5 This is an optional flowchart of step S130 provided in the embodiment of the present application. Step S130 may specifically include but is not limited to steps S510 to S520:

[0111] Step S510, labeling the candidate state change data based on the preset label to obtain the target state change data;

[0112] Step S520: Generate a first subscription message based on the target state change data and the target event group.

[0113] In steps S510 and S520 of some embodiments, when generating the first subscription message corresponding to the candidate state change data, the present application will first mark the candidate state change data based on the preset tag to obtain the target state change data, and the preset tag is used to let the server know that the state change data corresponding to the message is the last event / field notification in the target event group that calls the subscription. Further, the present application will generate a message for the target state change data based on the target event group as a unit to obtain the first subscription message.

[0114] In step S140 of some embodiments, for the remaining initial state change data in the target event group except the candidate state change data, the client can generate a message for each candidate state change data based on the target event group as a unit to obtain a corresponding second subscription message, and each candidate state change data will generate a corresponding second subscription message. Further, after each second subscription message is generated, the client will send the second subscription message to the server. However, after the server receives the second subscription message that is not triggered by the candidate state change data, it will not send any response to the client until it receives the first subscription message, and then it will immediately respond to the client with the server's subscription success notification signal.

[0115] In step S150 of some embodiments, when the client receives a subscription success notification signal from the server in response to the first subscription message, the client sends a confirmation message to the server. Further, after receiving the confirmation message, the server begins to send the initial data value corresponding to each initial state change data to the client, so that the client does not lose any initial value corresponding to the event / field notification in the target event group based on service discovery.

[0116] It should be noted that the server sends the initial data value corresponding to each initial state change data to the client in the form of a message, that is, the server can generate a business message based on the initial data value corresponding to each initial state change data, and the server can send the corresponding business messages to the client in the order of the received second subscription message, so that the client can fully receive the initial value corresponding to each event / field notification in the target event group sent by the server.

[0117] Therefore, compared with the related art in which the server sends all initial values ​​after receiving a subscription message generated by an Event / Field Notify, the present application can combine multiple Event / Notify in the target event group and mark the specific Event / Notify (i.e., candidate state change data). The server sends the initial value to the client only when receiving the subscription message triggered by the specific Event / Notify. This can reduce the Ethernet bandwidth and operating system load while ensuring the integrity of the communication data, thereby saving as much development cost as possible and the development cost when the SOMEIP protocol is installed in a real vehicle.

[0118] In some embodiments, see Figure 6 , Figure 6 This is another optional flow chart of the SOMEIP-based data processing method provided in the embodiment of the present application. The SOMEIP-based data processing method applied to the server may include but is not limited to steps S610 to S620:

[0119] Step S610, receiving a candidate subscription message based on a target event group sent by a client;

[0120] Step S620: When the candidate subscription message is the first subscription message, a subscription success notification signal is sent to the client, and the initial value of the data corresponding to each initial state change data in the target event group is sent to the client.

[0121] In steps S610 to S620 of some embodiments, the candidate subscription message includes a first subscription message and a second subscription message, the first subscription message is used to indicate the candidate state change data determined from multiple initial state change data of the target event group, and the second subscription message is used to indicate the remaining initial state change data in the target event group. In other words, the server can receive the first subscription message and the second subscription message based on the target event group sent by the client. When the candidate subscription message received by the server is the first subscription message, the server will send a subscription success notification signal to the client. Furthermore, when the server receives a confirmation message from the client in response to the subscription success notification signal, the server can send the initial data value corresponding to each initial state change data in the target event group to the client.

[0122] In some embodiments, see Figure 7 , Figure 7 It is another optional flow chart of the data processing method based on SOMEIP provided in the embodiment of the present application. Before step S620, the data processing method based on SOMEIP provided in the present application may also include steps S710 to S730:

[0123] Step S710, parsing the candidate subscription message to obtain parsed data;

[0124] Step S720, performing tag detection on the candidate subscription message based on the preset tag and the parsed tag to obtain a tag detection result;

[0125] Step S730: Determine whether the candidate subscription message is the first subscription message or the second subscription message based on the tag detection result.

[0126] In steps S710 to S730 of some embodiments, after receiving each candidate subscription message, the server will parse the candidate subscription message to obtain parsed data, and the parsed data includes the parsed tag and which event / field notification in the target event group corresponding to the message. Further, the server can compare the preset tag and the parsed tag to implement tag detection of the candidate subscription message, and the tag detection result is used to indicate the matching of the preset tag and the parsed tag, and the tag detection result includes a match and a mismatch. Further, it can be determined based on the tag detection result whether the candidate subscription message is the first subscription message or the second subscription message, wherein when the tag detection result is a match, it indicates that the preset tag and the parsed tag are the same, that is, the corresponding candidate subscription message is the first subscription message; when the tag detection result is a mismatch, it indicates that the preset tag and the parsed tag are different, that is, the corresponding candidate subscription message is the second subscription message.

[0127] It should be noted that, for the first subscription message, the corresponding parsing tag is a preset tag. For the second subscription message, the corresponding parsing tag may be an empty tag or other default tags that are different from the preset tag.

[0128] For examples, see Figure 8 , Figure 8It is a specific interactive flow chart of the data processing method based on SOMEIP provided in an embodiment of the present application. First, EventGroup1 (i.e., the target event group) constructed by the client includes Event1, Event2, and Notify1, and Notify1 is set as a specific candidate state change data, and a preset tag is marked for it. Furthermore, Event1 of the client calls the subscription function constructed based on the preset subscription call parameters, and sends a message of EventGroup1.Subscribe.Event1 (i.e., the second subscription message corresponding to Event1) to the server. After parsing the received EventGroup1.Subscribe.Event1 message, the server finds that it is not a message marked with a preset tag, and will not give any response to the client, which is equivalent to sending a message of EventGroup1.NotResponse (i.e., indicating that the server does not respond). Furthermore, Event2 of the client calls the subscription function constructed based on the preset subscription call parameters, and sends a message of EventGroup1.Subscribe.Event2 (i.e., the second subscription message corresponding to Event2) to the server. After parsing the received EventGroup1.Subscribe.Event2 message, the server finds that it is not a message marked with a preset tag, and will not give any response to the client, which is equivalent to sending an EventGroup1.NotResponse message (indicating that the server does not respond). Further, the client's Notify1 calls the subscription function built based on the preset subscription call parameters, and sends the EventGroup1.Subscribe.Notify1 message to the server (that is, the first subscription message corresponding to Notify1). At this time, after parsing the received EventGroup1.Subscribe.Notify1 message, the server finds that it is a message marked with a preset tag, indicating that the client has completed the subscription of all expected Event\Notify, then the server will send an EventGroup1.SubAck message to the client, that is, a subscription success notification signal. Furthermore, the server can send the initial data value corresponding to each initial state change data in the target event group to the client in the form of a business message.

[0129] It is understandable that after the server receives EventGroup1.Subscribe.Event1, the relevant technology will send the initial data value corresponding to each initial state change data in the target event group to the client in the form of a business message, and at this time Event2 and Notify1 have not sent subscription messages. If the server has sent the initial value corresponding to Notify1 before Notify1 sends the corresponding subscription message, when Notify1 sends the EventGroup1.Subscribe.Notify1 message to the server, it will no longer receive the initial value corresponding to Notify1, thereby affecting the subsequent logical judgment of Notify1.

[0130] The data processing method based on SOMEIP provided in the embodiment of the present application clarifies how to design Event, Field Notify and EventGroup in the SOMEIP protocol stack, and adds the design logic for all Event and Field Notify under the same EventGroup, so that the client can stably receive all Event and Field Notify initial values ​​under the EventGroup. Specifically, by setting a specific event / field notification in the target event group, the messages corresponding to all event / field notifications in the target event group can be judged on the server side. After determining that the subscription has been completed, the server side sends a subscription success notification signal, and sends the initial data value corresponding to each initial state change data in the target event group to the client. Therefore, the present application can completely receive the initial data values ​​corresponding to all event / field notifications in the target event group, effectively reduce the packet loss rate of Event, and solve the initial value judgment problem of Field Notify, thereby improving the communication efficiency between the server and the client.

[0131] See also Fig. 9 The embodiment of the present application further provides a data processing device based on SOMEIP, which is applied to a client and can implement the above-mentioned data processing method based on SOMEIP applied to the client. The device includes:

[0132] The acquisition module 910 is used to acquire a target event group corresponding to a communication service demand in a target network communication; wherein the target event group includes a plurality of initial state change data, and the initial state change data is used to indicate an event or field notification of a state change in the target network communication;

[0133] A determination module 920, configured to determine candidate state change data from a plurality of initial state change data based on preset subscription call parameters;

[0134] A first message generating module 930, configured to generate a first subscription message based on the candidate state change data and the target event group;

[0135] A second message generation module 940, configured to generate at least one second subscription message based on the remaining initial state change data and the target event group, and send the first subscription message and the second subscription message to the server;

[0136] The first receiving module 950 is configured to receive the initial data value corresponding to each initial state change data sent by the server after receiving the subscription success notification signal from the server in response to the first subscription message.

[0137] The specific implementation of the SOMEIP-based data processing device is basically the same as the specific implementation of the SOMEIP-based data processing method applied to the client mentioned above, and will not be repeated here.

[0138] See also Fig.10 The embodiment of the present application further provides a data processing device based on SOMEIP, which is applied to the server and can implement the above-mentioned data processing method based on SOMEIP applied to the server. The device includes:

[0139] The second receiving module 1010 is used to receive a candidate subscription message based on a target event group sent by a client; wherein the candidate subscription message includes a first subscription message and a second subscription message, the first subscription message is used to indicate the candidate state change data determined from a plurality of initial state change data of the target event group, and the second subscription message is used to indicate the remaining initial state change data in the target event group;

[0140] The sending module 1020 is used to send a subscription success notification signal to the client when the candidate subscription message is the first subscription message, and send the initial value of the data corresponding to each initial state change data in the target event group to the client.

[0141] The specific implementation of the SOMEIP-based data processing device is basically the same as the specific implementation of the SOMEIP-based data processing method applied to the server, and will not be repeated here.

[0142] The embodiment of the present application also provides an electronic device, which includes at least one processor; at least one memory for storing at least one program; when the at least one program is executed by the at least one processor, the at least one processor implements the data processing method based on SOMEIP in the embodiment of the present application. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0143] See also Fig.11 , Fig.11The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0144] The processor 1110 may be implemented by a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0145] The memory 1120 may be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1120 may store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1120, and the processor 1110 calls and executes the data processing method based on SOMEIP in the embodiment of this application;

[0146] Input / output interface 1130, used to implement information input and output;

[0147] The communication interface 1140 is used to realize the communication interaction between the device and other devices. The communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0148] bus 1150 , which transmits information between the various components of the device (e.g., processor 1110 , memory 1120 , input / output interface 1130 , and communication interface 1140 );

[0149] The processor 1110 , the memory 1120 , the input / output interface 1130 , and the communication interface 1140 are connected to each other in communication within the device via the bus 1150 .

[0150] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned SOMEIP-based data processing method is implemented.

[0151] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0152] The embodiment of the present application also provides a vehicle, which includes the above-mentioned vehicle-mounted camera, vehicle equipment, or the above-mentioned data processing device based on SOMEIP. The vehicle provided in the embodiment of the present application can be a gasoline vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle.

[0153] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0154] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0155] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0156] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0157] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0158] It should be understood that in the present application, "at least one (item)" refers to one or more, "multiple" refers to two or more, "each" refers to each of the corresponding multiple, and "any" refers to any one of the multiple. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0159] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0160] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0161] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0162] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0163] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A data processing method based on SOMEIP, characterized in that: Applied to a client, the client is connected to a server for communication, and the method includes: Acquire a target event group corresponding to a communication service demand in a target network communication; wherein the target event group includes a plurality of initial state change data, and the initial state change data is used to indicate an event or field notification of a state change in the target network communication; Determine candidate state change data from the plurality of initial state change data based on preset subscription call parameters; Generate a first subscription message based on the candidate state change data and the target event group; generating at least one second subscription message based on the remaining initial state change data and the target event group, and sending the first subscription message and the second subscription message to the server; After receiving a subscription success notification signal from the server in response to the first subscription message, an initial data value corresponding to each of the initial state change data sent by the server is received.

2. The method according to claim 1, characterized in that The generating a first subscription message based on the candidate state change data and the target event group includes: Marking the candidate state change data based on preset labels to obtain target state change data; The first subscription message is generated based on the target state change data and the target event group.

3. The method according to claim 2, characterized in that The determining of candidate state change data from the plurality of initial state change data based on the preset subscription call parameter comprises: Arrange the plurality of initial state change data based on the preset subscription call parameter to obtain a state change data list, wherein the state change data list is used to indicate the order in which the plurality of initial state change data call the preset subscription call parameter; The candidate state change data is determined based on the state change data list, where the candidate state change data is used to represent the initial state change data of the last one in the target event group that calls the preset subscription call parameter.

4. The method according to claim 3, characterized in that The preset subscription call parameters include business logic data, data dependency, data priority and resource restriction data corresponding to the communication business requirements; the data of the plurality of initial state change data are arranged based on the preset subscription call parameters to obtain a state change data list, including Performing data scoring on the initial state change data based on the business logic data to obtain a first score; Performing data scoring on the initial state change data based on the data dependency relationship to obtain a second score; Performing data scoring on the initial state change data based on the data priority to obtain a third score; Performing data scoring on the initial state change data based on the resource restriction data to obtain a fourth score; determining a target score for the initial state change data based on the first score, the second score, the third score, and the fourth score; The plurality of initial state change data are arranged in descending order based on the target score to obtain the state change data list.

5. The method according to claim 1, characterized in that The step of obtaining a target event group corresponding to a communication service demand in target network communication includes: Performing data analysis on the communication service requirements in the target network communication to obtain service-related data and service scenario data, wherein the service-related data is used to indicate an event or field notification related to the service logic of the communication service requirements, and the service scenario data is used to indicate an event or field notification related to the scenario corresponding to the communication service requirements; Based on the business association data and the business scenario data, a plurality of the initial state change data are acquired from a preset state data set, and the target event group is constructed based on the plurality of the initial state change data.

6. A data processing method based on SOMEIP, characterized in that: Applied to a server, the server is connected to a client for communication, and the method includes: Receive a candidate subscription message based on a target event group sent by the client; wherein the candidate subscription message includes a first subscription message and a second subscription message, the first subscription message is used to indicate the candidate state change data determined from a plurality of initial state change data of the target event group, and the second subscription message is used to indicate the remaining initial state change data in the target event group; When the candidate subscription message is the first subscription message, a subscription success notification signal is sent to the client, and an initial value of data corresponding to each of the initial state change data in the target event group is sent to the client.

7. The method according to claim 6, characterized in that Before sending a subscription success notification signal to the client when the candidate subscription message is the first subscription message, the method further includes: Parsing the candidate subscription message to obtain parsed data, wherein the parsed data includes a parsed tag; Performing label detection on the candidate subscription message based on the preset label and the parsed label to obtain a label detection result; The candidate subscription message is determined to be the first subscription message or the second subscription message based on the tag detection result.

8. A data processing device based on SOMEIP, characterized in that: The device comprises: An acquisition module, used to acquire a target event group corresponding to a communication service demand in a target network communication; wherein the target event group includes a plurality of initial state change data, and the initial state change data is used to indicate an event or field notification of a state change in the target network communication; A determination module, configured to determine candidate state change data from a plurality of the initial state change data based on a preset subscription call parameter; A first message generating module, configured to generate a first subscription message based on the candidate state change data and the target event group; A second message generation module, configured to generate at least one second subscription message based on the remaining initial state change data and the target event group, and send the first subscription message and the second subscription message to a server; The first receiving module is used to receive the data initial value corresponding to each initial state change data sent by the server after receiving the subscription success notification signal responded by the server based on the first subscription message.

9. An electronic device, characterized in that: include: at least one processor; at least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method according to any one of claims 1 to 5; Alternatively, the method according to any one of claims 6 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented; or the method according to any one of claims 6 to 7 is implemented.

Images