Control request processing method, apparatus, device, and storage medium

Abstract

Embodiments of the application disclose a control request processing method and device, equipment and a storage medium, and belong to the technical field of communication. The method comprises the following steps: receiving a downlink control request from a message queue telemetry transport (MQTT) server through a first downlink topic, wherein the downlink control request is generated by a public service platform and is used for requesting a first terminal device to execute a first service; generating an uplink feedback result corresponding to the downlink control request, wherein the uplink feedback result is used for feeding back a processing result of the downlink control request; and sending the uplink feedback result to the MQTT server through a first uplink topic, so that the MQTT server sends the uplink feedback result to the public service platform, and the first uplink topic and the first downlink topic are both used for executing communication transmission related to the first service. Compared with TCP transmission of a control request, this method helps to improve the processing capacity of the public service platform for high-concurrency control requests.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of communication, and in particular, relate to a control request processing method and device, equipment and a storage medium. BACKGROUND

[0002] With the development of Internet of Things technology, more and more devices support remote control services, which provides great convenience for users' life.

[0003] In the related art, a content service platform performs remote control on a terminal device through a Transmission Control Protocol (TCP). The content service platform and the terminal device maintain TCP communication, and in the case of needing to remotely control the terminal device, the content service platform sends a control request to the terminal device through the TCP protocol.

[0004] However, in the related art, due to the unstable response speed of the TCP protocol, the remote control often appears timeout and disconnection in peak period, and the processing of control information needs further research. SUMMARY

[0005] Embodiments of the present application provide a control request processing method, device and equipment, which can be used to solve the problem of unstable connection between the content service platform and the terminal device in the related art. The technical solution is as follows:

[0006] According to an aspect of the embodiments of the present application, a control request processing method is provided, the method is executed by a first terminal device, and the method comprises:

[0007] receiving a downlink control request from a Message Queuing Telemetry Transport (MQTT) server through a first downlink topic, the downlink control request being generated by a public service platform and being used to request the first terminal device to execute a first service;

[0008] generating an uplink feedback result corresponding to the downlink control request, the uplink feedback result being used to feed back a processing result of the downlink control request;

[0009] sending the uplink feedback result to the MQTT server through a first uplink topic, so that the MQTT server sends the uplink feedback result to the public service platform, and the first uplink topic and the first downlink topic are both used to perform communication transmission related to the first service.

[0010] According to an aspect of the embodiments of the present application, a control request processing method is provided, the method is executed by a public service platform, and the method comprises:

[0011] send a downlink control request to the server through a first downlink topic, the downlink control request being used to request the first terminal device to execute a first service, the MQTT server being used to complete information relay between the first terminal device and the public service platform;

[0012] receive an uplink feedback result sent by the MQTT server through a first uplink topic, the uplink feedback result being generated by the first terminal device, and the uplink feedback result being used to feed back a processing result of the downlink control request.

[0013] According to an aspect of an embodiment of the present application, a control request processing device is provided, and the device comprises:

[0014] a message receiving module, configured to receive a downlink control request from an MQTT server through a first downlink topic, the downlink control request being generated by a public service platform and used to request the first terminal device to execute a first service;

[0015] a result generating module, configured to generate an uplink feedback result corresponding to the downlink control request, the uplink feedback result being used to feed back a processing result of the downlink control request;

[0016] a result feeding back module, configured to send the uplink feedback result to the MQTT server through a first uplink topic, so that the MQTT server sends the uplink feedback result to the public service platform, and the first uplink topic and the first downlink topic are both used to perform communication transmission related to the first service.

[0017] According to an aspect of an embodiment of the present application, a control request processing device is provided, and the device comprises:

[0018] a request receiving module, configured to send a downlink control request to an MQTT server through a first downlink topic, the downlink control request being used to request a first terminal device to execute a first service, and the MQTT server being used to complete information relay between the first terminal device and a public service platform;

[0019] a result receiving module, configured to receive an uplink feedback result sent by the MQTT server through a first uplink topic, the uplink feedback result being generated by the first terminal device, and the uplink feedback result being used to feed back a processing result of the downlink control request.

[0020] According to an aspect of an embodiment of the present application, a computer readable storage medium is provided, and the storage medium stores a computer program, the computer program being used to be executed by a processor to implement the control request processing method.

[0021] According to an aspect of the embodiments of the present application, a computer device is provided, which comprises a processor and a memory, and the memory stores a computer program, which is loaded and executed by the processor to implement the control request processing method described above.

[0022] According to an aspect of the embodiments of the present application, a computer program product is provided, which, when running on a computer device, causes the computer device to execute the control request processing method described above.

[0023] The technical solutions provided by the embodiments of the present application can bring the following beneficial effects:

[0024] In the scenario that the public service platform requests the terminal device to execute a certain service through a downlink control request, the public service platform sends a control request to the MQTT server based on a downlink topic, and the MQTT forwards the downlink control request to the terminal device. In this way, the communication between the terminal device and the public service platform is completed by the MQTT, and the communication mode of the client server is decoupled. This way does not require the terminal device and the public service platform to run at the same time, so that the public service platform does not need to maintain direct communication connections with multiple terminal devices at the same time, which helps to reduce the communication pressure of the public service platform in a high concurrency scenario, improve the response capability of the public service platform to high concurrency control requests, and help to improve the communication stability between the terminal device and the public service platform. BRIEF DESCRIPTION OF DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0026] Figure 1 is a schematic diagram of the control request processing method provided by an exemplary embodiment of the present application;

[0027] Figure 2 is a schematic diagram of the system architecture provided by an exemplary embodiment of the present application;

[0028] Figure 3 is a flowchart of the control request processing method provided by an exemplary embodiment of the present application;

[0029] Figure 4 is a flowchart of the control request processing method provided by another exemplary embodiment of the present application;

[0030] Figure 5is a schematic diagram of a control request processing method provided by an exemplary embodiment of the present application;

[0031] Figure 6 is a flow chart of a control request processing method provided by another exemplary embodiment of the present application;

[0032] Figure 7 is a block diagram of a control request processing apparatus provided by an embodiment of the present application;

[0033] Figure 8 is a block diagram of a control request processing apparatus provided by another embodiment of the present application;

[0034] Figure 9 is a schematic diagram of a computer device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0035] Before introducing the technical solutions of the present application, some background technical knowledge related to the present application is introduced and explained. The following related technologies can be combined with the technical solutions of the embodiments of the present application in any manner as optional solutions, which all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0036] Internet of Things technology refers to connecting terminal devices with a network according to a communication protocol through information sensing devices, supporting information exchange and communication between the terminal devices and the information propagation medium to realize intelligent identification, positioning, tracking and other functions. Internet of Things technology makes it possible to remotely control terminal devices.

[0037] Remote control function uses wireless communication technology to send control requests to terminal devices, so that the terminal devices complete corresponding behaviors based on the control requests. Since wireless communication technology can transmit control information to terminal devices from a very long distance, the emergence of remote control function eliminates the restriction of physical distance on terminal device control. With the help of remote control function, users can control terminal devices to perform corresponding functions anytime and anywhere, which is more convenient for controlling terminal devices.

[0038] Internet of Vehicles technology is a branch of Internet of Things technology. In Internet of Vehicles technology, terminal devices refer to vehicle-mounted terminals in vehicles. Internet of Vehicles technology is based on in-vehicle network, inter-vehicle network and vehicle mobile Internet, and realizes wireless communication and information exchange between vehicle-X (X: vehicle, road, pedestrian and Internet, etc.) according to a communication protocol and data interaction standard. Through Internet of Vehicles technology, an integrated network of intelligent traffic management, intelligent dynamic information service and vehicle intelligent control can be realized.

[0039] A vehicle-mounted terminal mounted in a vehicle is used to implement intelligent management functions related to the vehicle, such as providing navigation services, automatic parking services, remote control services, and the like through the vehicle-mounted terminal. Among them, the vehicle-mounted terminal refers to an electronic device having at least computing, storage and communication functions in the vehicle. The vehicle-mounted terminal can establish communication with a server, and the vehicle-mounted terminal obtains reference information from the server in order to better implement intelligent management functions.

[0040] Among them, the remote control service related to the vehicle includes but is not limited to: remote start, remote air conditioning, remote opening and closing of vehicle doors, remote unlocking, etc. In this scenario, the vehicle-mounted terminal receives a remote control request from the server in order to complete a responsive remote control service based on the remote control request.

[0041] The MQTT protocol is a "lightweight" communication protocol based on a publish / subscribe mode. MQTT is used as an instant communication protocol with low overhead and low bandwidth occupation, and only a small amount of code and limited bandwidth are required to achieve remote communication.

[0042] In the related art, a public service platform transmits a control request to a terminal device through TCP, so that the terminal device receives the control request and executes the function corresponding to the control request to implement a remote control function. The public service platform can provide remote control services for multiple terminal devices. In some scenarios, multiple terminal devices subscribe to the same type of remote control service, and the public service platform needs to send remote control requests to these terminal devices respectively in a short time (such as the demand for remote control of opening and closing vehicle doors is mainly concentrated in the commuting period). That is, in this scenario, the public service platform needs to maintain a long connection with multiple terminal devices. Since the TCP protocol often has timeout and non-response situations when multiple links are used, it is easy to cause the connection between the public service platform and the terminal device to timeout and drop in the peak period, so that the stability of the control request transmission process is poor.

[0043] The system architecture and business scenarios described in the embodiments of the present application are used 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 by the embodiments of the present application. Those skilled in the art can know that the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems as the system architecture evolves and new business scenarios appear.

[0044] Figure 1 is a schematic diagram of a control request processing method provided by an exemplary embodiment of the present application, as shown in Figure 1 In the scheme provided by the present application, MQTT is used as a communication transfer carrier between the client and the public service platform. The client includes multiple terminal devices, and each terminal device can communicate with the public service platform through the MQTT server in order to implement a remote control function.

[0045] In addition, a transmission protocol file is set between the terminal device and the public service platform, and the terminal device or the server determines the communication content from the opposite end based on the transmission protocol file.

[0046] Referring to Figure 2 , a schematic diagram of a system architecture provided by an embodiment of the present application is shown. The system architecture can include a terminal device 10, a public service platform 20, and an MQTT server 30. Based on wireless communication between the terminal device 10, the public service platform 20, and the MQTT server 30, a processing process of a control request is completed, and control of the terminal device 10 is implemented.

[0047] The terminal device 10 and the public service platform 20 are in communication connection. In the embodiment of the present application, information transmission between the terminal device 10 and the public service platform 20 needs to be relayed through the MQTT server 30. The MQTT server 30 is also called a broker, a message server, etc.

[0048] In the case where the public service platform 20 needs to send a control request to the terminal device 10, the public service platform 20 sends the control request to the MQTT server 30, and relays the control request to the terminal device 10 through the MQTT server 30.

[0049] In the case where the terminal device 10 needs to send a feedback result corresponding to the control request to the public service platform 20, the terminal device 10 sends the feedback result to the MQTT server 30, and relays the feedback result to the public service platform 20 through the MQTT server 30.

[0050] In the scheme provided by the embodiment of the present application, the terminal device 10 and the MQTT server 30, and the public service platform 20 and the MQTT server 30 transmit information through topics. Exemplarily, the terminal device 10 subscribes to a certain control service in the public service platform 20, and then the public service platform 20 creates a topic corresponding to the control service. The public service platform 20 sends a control request to the MQTT server 30 through a downlink topic, and relays the control request to the terminal device 10 through the MQTT server 30 through the downlink topic. Then the terminal device 10 sends a feedback result to the MQTT server 30 through an uplink topic, and relays the feedback result to the public service platform 20 through the MQTT server 30 through the uplink topic.

[0051] The terminal device 10 and the public service platform 20 do not need to keep a communication connection at all times by transmitting information through a topic, that is, a long connection between the terminal device 10 and the public service platform 20 does not need to be kept during control request processing. The use of the MQTT server 30 enables asynchronous communication between the terminal device 10 and the public service platform 20, and the terminal device 10 only needs to listen to a downlink topic corresponding to a subscription service to obtain a control request in a timely manner.

[0052] Compared with the method in the related art in which a terminal device and a public service platform transmit a control request through a TCP protocol, the method provided in the present application decouples a client / server mode, which helps to reduce communication pressure of a public service request in a high-concurrency scenario, reduce timeout and a situation in which a public service platform is offline during control request transmission, and help to improve information transmission stability between a terminal device and a public service platform.

[0053] In some embodiments, a control process of the terminal device 10 is triggered by a user terminal, a communication connection exists between the user terminal and the public service platform 20, and the user terminal sends control indication information to the public service platform 20, where the control indication information is used to instruct the terminal device 10 to complete a first service. After receiving the control indication information, the public service platform 20 generates a first control request. The user terminal refers to a device used by a user, such as a personal mobile phone, a tablet computer, a computer, and the like.

[0054] The terminal device 10 is used to manage an article to be controlled. The terminal device 10 is integrated with the article to form a smart article. For example, the terminal device 10 is a vehicle terminal device in a vehicle, and the terminal device 10 is used to control electronic components in the vehicle to realize functions such as automatic opening and closing of a vehicle door and starting of an air conditioner. For another example, the terminal device 10 is a computer device integrated in a household appliance, and is used to control an on-off state and a working state of the household appliance.

[0055] The public service platform 20 and the MQTT server 30 described above are both servers. The public service platform 20 is used to provide a remote control service of a terminal device for a user, and the MQTT server 30 is used to provide a relay transmission service for the public service platform 20 and the terminal device 10. The server can be implemented as a cloud server in a cloud or a node in a blockchain system.

[0056] To make the objects, technical solutions, and advantages of the present application clearer, the following further describes the embodiments of the present application in detail with reference to the drawings.

[0057] Reference is made to Figure 3Fig. 10 shows a flowchart of a control request processing method provided by an embodiment of the present application, and the execution subject of each step of the method can be the first terminal device, e.g., the control request processing method is executed by an application program for implementing remote control in the first terminal device. The method can include at least one of the following steps (310-330):

[0058] In step 310, a downlink control request is received from the MQTT server through a first downlink topic. The downlink control request is generated by the public service platform and is used to request the first terminal device to execute a first service.

[0059] In some embodiments, the first downlink topic is used to transmit the downlink control request corresponding to the first service. In the scheme provided by the embodiments of the present application, the direction from the public service platform to the terminal device is the downlink direction, and the direction from the terminal device to the public service platform is the uplink direction. Optionally, the first service is controlled and executed by the first terminal device. For example, the first service is controlled and executed by the first terminal device on an article. For example, the first terminal device is a vehicle terminal device, and the first service is controlled and executed by the vehicle terminal device on a vehicle. For example, the first service is controlled and executed by the vehicle terminal device on the air conditioner in the vehicle.

[0060] In some embodiments, the public service platform is used to provide at least one remote control service, and the first terminal device is a terminal device that subscribes to at least one service in the public service platform. The first service is any one of the at least one subscribed service. The remote control service refers to a service for controlling a terminal device to complete a function without the user contacting the terminal device.

[0061] Optionally, the timing at which the public service platform generates and sends the downlink control request is determined by the user. For example, the public service platform generates and sends the downlink control request upon receiving control indication information sent by the user terminal, wherein the control indication information is used to indicate that the first terminal device is controlled to execute the first service.

[0062] Optionally, the timing at which the public service platform generates and sends the downlink control request is preconfigured. For example, the execution time of the first service is preconfigured in the public service platform, and if the current time is about to reach the execution time or has reached the execution time, the public service platform generates and sends the downlink control request corresponding to the first service.

[0063] Optionally, the timing at which the public service platform generates and sends the downlink control request is indicated by a staff of the public service platform. For example, the user initiates a help request to the public service platform, and upon verifying the identity provided by the user and determining that the user has the control authority on the first terminal device, the staff sends control indication information to the public service platform through a work device.

[0064] In an example scenario, the terminal device is a vehicle-mounted terminal device, the user is an owner of a vehicle on which the vehicle-mounted terminal device is mounted, and the first service is a vehicle door opening service. Since the vehicle door cannot be opened, the owner initiates a help request to a staff member, and the staff member sends control instruction information to the public service platform through a work device to open the control request processing procedure.

[0065] In some embodiments, the MQTT server refers to a relay server supporting the MQTT protocol. The MQTT server receives a downlink control request corresponding to a certain service from the public service platform and sends the downlink control request to at least one terminal device that subscribes to the service in the public service platform. Optionally, the MQTT server is a cluster built based on a real-time message engine. In order to improve the forwarding capability of the MQTT server for a large amount of communication information in a short time, Haproxy (a multi-core proxy software) is used in the MQTT server to realize load balancing of the cluster. Exemplarily, Elastic Load Balance (ELB) is used as high-availability load in the MQTT server to ensure high availability of the cluster and improve reliability in the communication information forwarding process.

[0066] In some embodiments, the first downlink topic refers to a topic used for transmitting a downlink control request. In a publish / subscribe mode, a topic is a string used for identifying and classifying messages. Optionally, the topic is composed of one or more levels, and a forward slash is used as a separator between the levels. Exemplarily, after the terminal device subscribes to a certain service from the public service platform, the public service platform generates and sends a topic related to the service to the terminal device, so that the terminal device receives the downlink control request forwarded by the MQTT server by listening to the downlink topic of the service.

[0067] Optionally, the first downlink topic is related to the first service. Exemplarily, the first service type identifier of the first service is included in the first downlink topic. The MQTT server determines all terminal devices that subscribe to the first service in the public service platform based on the service type identifier of the first service, and respectively forwards the same downlink control request to the all terminal devices through the first downlink topic. In this way, parallel sending of remote control requests can be completed in a short time.

[0068] Exemplarily, the first downlink topic is further related to a device identification code of the first terminal device. The device identification code of the first terminal device is used to uniquely identify the first terminal device, and the device identification code includes but is not limited to a device serial number, a network access number, and the like. Different terminal devices have different device identification codes. In this case, after receiving the downlink control request, the MQTT server forwards the downlink control request to the first terminal device according to the device identification code of the first terminal device. By carrying the device identification code in the downlink topic, point-to-point transmission of the downlink control request can be achieved, which helps to realize customized execution of the first service based on the needs of different users.

[0069] In some embodiments, the downlink control request is transmitted using the first downlink topic, that is, the public service platform transmits the downlink control request to the MQTT server according to the first downlink topic; and the MQTT server transmits the downlink control request to the terminal device using the first downlink topic.

[0070] In some embodiments, the downlink control request is used to request the at least one terminal device to execute the first service respectively. Optionally, the downlink control request belongs to a remote control request, that is, the first terminal device can be remotely controlled to execute the first service through the downlink control request without contacting the terminal device.

[0071] Optionally, the downlink control request includes a service type identifier of the first service, and the terminal device determines the first service based on the service type identifier to execute the first service. Exemplarily, the downlink control request further includes a parameter related to the first service. In the case where the downlink control request includes the parameter related to the first service, the terminal device executes the first service based on the parameter.

[0072] In some embodiments, the request format of the downlink control request is preconfigured. Optionally, the downlink control request includes at least one field, and the content included in each field is pre-defined. Exemplarily, the first terminal device and the public service platform are both configured with a transmission protocol file, the transmission protocol file is used to indicate the communication format between the first terminal device and the public service platform, the public service platform encodes the downlink control request based on the transmission protocol file, and the first terminal device decodes the downlink control request based on the transmission protocol file. For specific contents, please refer to the embodiments below. Exemplarily, the transmission protocol file is in the form of ProtoBuf.

[0073] In this way, the downlink control request does not need to carry keywords for explaining the meaning of the content, which reduces the information length of the downlink control request, helps to reduce the transmission resources consumed for transmitting the downlink control request, and improves the transmission efficiency of the downlink control request.

[0074] Step 320, generating an uplink feedback result corresponding to the downlink control request, the uplink feedback result being used for feeding back a processing result of the downlink control request.

[0075] After receiving the downlink control request, the first terminal device performs the first service based on the downlink control request, and generates an uplink feedback result. Optionally, the uplink feedback result is used for feeding back an execution result of the first service to the common service platform. Illustratively, the uplink feedback result includes a general reply code, which is used for representing whether the first service is successfully performed.

[0076] For example, the general reply code is represented by 1 bit character, wherein "1" represents that the first terminal device successfully performs the first service, and "0" represents that the first service is not successfully performed.

[0077] In some embodiments, a request format of the uplink feedback result is preconfigured. Optionally, the uplink feedback result includes at least one field, and the content included in each field is pre-defined. The first terminal device generates the uplink feedback result based on the uplink feedback format, and the specific content can be referred to the following embodiments.

[0078] Step 330, sending the uplink feedback result to the MQTT server through a first uplink topic, so that the MQTT server sends the uplink feedback result to the common service platform, and the first uplink topic and the first downlink topic are both used for performing communication transmission related to the first service.

[0079] In some embodiments, the first uplink topic refers to a topic used for transmitting the uplink feedback result of the first service. Optionally, the first uplink topic and the first downlink topic are similar in form. The first uplink topic is pre-set. Illustratively, after the first terminal device subscribes to the first service on the common service platform, the common service platform generates and sends the first downlink topic and the first uplink topic to the first terminal device, so as to subsequently complete the communication process related to the first service through the first downlink topic and the first uplink topic.

[0080] In some embodiments, the first uplink topic includes a platform identifier of the common service platform, and the first terminal device sends the uplink feedback result to the MQTT server by taking the first uplink topic as a topic of the uplink feedback result. The MQTT server forwards the uplink feedback result to the common service platform based on the first uplink topic.

[0081] In summary, in the scenario that the public service platform requests the terminal device to execute a certain service through the downlink control request, the public service platform sends the control request to the MQTT server based on the downlink topic, and the MQTT forwards the downlink control request to the terminal device. In this way, the communication between the terminal device and the public service platform is completed by the MQTT, and the communication mode of the client server is decoupled. This way does not require the terminal device and the public service platform to run at the same time, so that the public service platform does not need to maintain direct communication connection with multiple terminal devices at the same time, which helps to reduce the communication pressure of the public service platform in the high concurrency scenario, and helps to improve the communication stability between the terminal device and the public service platform.

[0082] Reference is made to Figure 4 which shows a flowchart of the control request processing method provided by another embodiment of the application. In the embodiment of the application, the control request processing method includes the following steps.

[0083] Step 310, receiving a downlink control request from the MQTT server through a first downlink topic.

[0084] Step 323, determining the uplink feedback format of the first service according to the transmission protocol file, the uplink feedback format being used to indicate at least one content field included in the uplink feedback result.

[0085] In some embodiments, the transmission protocol file is used to indicate the data format of the feedback result. Optionally, the transmission protocol file includes the data format of the feedback result corresponding to each of a plurality of services. The plurality of services can be all the services supported by the public service platform.

[0086] The data format of the feedback result corresponding to different services can be the same or different. Illustratively, the feedback results corresponding to different services are the same, such as the plurality of feedback results each including only a general reply code. Illustratively, the feedback results corresponding to different services are different. For example, the feedback result includes not only the general reply code but also a parameter related to the service. Since the parameter types corresponding to different services are different, the data formats of the feedback results corresponding to different services are different.

[0087] Optionally, the transmission protocol file is also used to indicate the data format of the control request. The first terminal device decodes the downlink control request based on the transmission protocol file to determine the first service indicated by the downlink control request.

[0088] In some embodiments, the transmission protocol file is preconfigured, and the transmission protocol file is used to indicate a communication format corresponding to each of the at least one service provided by the common service platform. For each of the at least one service, the communication format corresponding to the service includes at least one of the following: a field format of a downlink control request related to the service, a field format of an uplink feedback result related to the service.

[0089] In one example, the transmission protocol file is agreed upon in advance by the common service platform and the first terminal device. The transmission protocol file includes a data format of a downlink control request corresponding to each service and a data format of an uplink feedback result.

[0090] In some embodiments, the uplink feedback format includes at least one content field, and the content field is used to represent a position of a result content included in the uplink feedback result in the uplink feedback result. Optionally, a number of fields included in the uplink feedback format is related to a total number of result contents in the uplink feedback result. The number of fields included in the uplink feedback format is equal to the total number of result contents in the uplink feedback result.

[0091] For example, in a case where the uplink feedback result includes a general reply code and a parameter related to the first service, the uplink feedback format includes two content fields, which are a content field corresponding to the general reply code and a content field corresponding to the parameter related to the first service.

[0092] In some embodiments, a length of the content field is pre-set, and the length of the content field refers to a number of bits of a bit character included in the content field. The lengths of different content fields can be the same or different. Optionally, the length of the content field corresponding to the general reply code is x, and the length of the content field corresponding to the parameter related to the first service is y, x and y are positive integers. For example, x is equal to 1, and y is equal to 10.

[0093] Optionally, the uplink feedback format is also used to indicate an arrangement order of the at least one content field in the uplink feedback result. For example, the uplink feedback format indicates that a first x bits in the uplink feedback result represent the content field corresponding to the general reply code, and x-th bit to x+y-th bit in the uplink feedback result represent the content field corresponding to the parameter related to the first service.

[0094] In some embodiments, if the parameter related to the first service includes multiple categories, the content field corresponding to the parameter related to the first service can be divided into multiple subfields, and the relative positions of the multiple subfields are fixed, and each subfield corresponds to one parameter type.

[0095] In some embodiments, the content field corresponding to the parameter related to the first service further comprises an interference field for carrying interference information. The interference information is irrelevant to the actual parameter of the first service, such as the value of the interference information being outside the value range of the parameter. For another example, the interference information is a piece of random code.

[0096] Optionally, the interference information is pre-agreed between the first terminal device and the public service platform, and the interference information corresponding to different services can be different. The interference field can be randomly inserted between any two subfields. That is, in the process of generating the uplink feedback result, the first terminal device randomly sets the position of the interference field in the content field corresponding to the parameter related to the first service. After receiving the uplink feedback result, the public service platform extracts the interference information from the uplink feedback result to obtain the processed uplink feedback result, and determines the execution of the first terminal device on the first service based on the processed uplink feedback result.

[0097] Carrying the interference information in the uplink feedback information makes the feedback format of the uplink feedback information flexible and changeable, and pre-agreeing the interference information with the public service platform ensures that the interference information in the uplink feedback result can be correctly removed. Since the actual content of the interference information is unknown to other devices, and the uplink feedback format is not fixed after inserting the interference information in the uplink feedback result, even if the uplink feedback result is intercepted by a malicious device or information leakage occurs when the uplink feedback result is transferred in the MQTT server, since the malicious device cannot correctly decode the uplink feedback result, it is difficult for other devices except the public service platform to obtain the execution of the first service, which helps to improve the security of the control request processing process.

[0098] In step 326, the uplink feedback result is generated based on the uplink feedback format.

[0099] In some embodiments, the first terminal fills the corresponding content into the corresponding content field based on the uplink feedback format to obtain the uplink feedback result.

[0100] In step 330, the uplink feedback result is sent to the MQTT server through the first uplink topic, so that the MQTT server sends the uplink feedback result to the public service platform.

[0101] For specific descriptions of steps 310 and 330, please refer to the above embodiments, which will not be repeated here.

[0102] In the embodiments of the present application, the uplink feedback format is set in the protocol transmission file, so that the placement positions of different contents in the uplink feedback result are fixed, and in this way, the uplink feedback result does not need to carry keywords for explaining the meaning of the content, which helps to shorten the length of the uplink feedback result and improve the transmission efficiency of the uplink feedback result.

[0103] In some embodiments, the content field in the downlink control request comprises at least one of: a service type identifier, a request content, the service type identifier is used to represent the first service, and the request content comprises a parameter related to the first service, and / or the content field in the uplink feedback result comprises at least one of: a general reply code, a feedback content, wherein the general reply code is used to represent the execution of the first service by the first terminal device, and the feedback content comprises a parameter related to the first service after the execution of the downlink control request.

[0104] In some embodiments, the parameter related to the first service in the request content is used to indicate a target parameter value that should be reached by the terminal device after the execution of the first service.

[0105] In some embodiments, in the downlink control request, the service type identifier is located before the request content, i.e., the content field corresponding to the service type identifier is arranged before the content field corresponding to the request content. For example, the downlink control request is: service type identifier_request content.

[0106] Optionally, the service type identifier of the first service is an enumeration type of the first service in a plurality of services supported by the public service platform. The service type identifier of the first service is represented by at least one bit code.

[0107] In some embodiments, the parameter related to the first service after the execution of the downlink control request included in the feedback content in the uplink feedback result is used to indicate an actual parameter value reached by the terminal device after the execution of the first service. Optionally, for the same service, the type of the parameter included in the downlink control request of the service is the same as the type of the parameter included in the uplink feedback result of the service.

[0108] In some embodiments, in the uplink feedback result, the general reply code is located before the feedback content, i.e., the content field corresponding to the general reply code is arranged before the content field corresponding to the feedback content. For example, the downlink control request is: general reply code_feedback content.

[0109] In some embodiments, the first uplink subject comprises at least one of: a platform identifier of the public server platform, an uplink transmission identifier, a transmission type identifier, a device identifier code of the first terminal device.

[0110] Optionally, the platform identifier of the public server platform is used to represent the server corresponding to the public service platform. For example, the platform identifier of the public server platform is the name, number, etc. of the server.

[0111] Optionally, the uplink transmission identifier is used to represent a transmission direction of the first uplink topic, and the MQTT server determines to transmit the uplink feedback result received by the MQTT server to the common service platform based on the uplink transmission identifier. For example, the uplink transmission identifier uses "up" to represent.

[0112] Optionally, the transmission type identifier is used to represent a type of the control request. In the embodiments of the present application, the transmission type identifier is used to represent that the control request belongs to a remote control type. For example, the transmission type uses "remote" to represent.

[0113] In one example, the first uplink topic includes a platform identifier of the common server platform, the uplink transmission identifier, and the transmission type identifier.

[0114] In another example, the first uplink topic includes a platform identifier of the common server platform, the uplink transmission identifier, the transmission type identifier, and a device identifier of the first terminal device. For example, the first uplink topic is represented as: Server / rc / V1 / up / Remote / %vin, wherein Server represents the platform identifier of the common server platform, up represents the uplink transmission identifier, remote represents the transmission type identifier, and vin represents the device identifier of the first terminal device.

[0115] In some embodiments, the first downlink topic includes at least one of the following: a platform identifier of the common server platform, a downlink transmission identifier, a transmission type identifier, and a device identifier of the first terminal device.

[0116] In some embodiments, the downlink transmission identifier is used to represent a transmission direction of the first downlink topic, and the MQTT server determines to transmit the downlink control request received by the MQTT server to at least one terminal device based on the downlink transmission identifier. For example, the downlink transmission identifier uses "down" to represent.

[0117] In one example, the first downlink topic includes a platform identifier of the common server platform, a downlink transmission identifier, and a transmission type identifier. In another example, the first downlink topic includes a platform identifier of the common server platform, a downlink transmission identifier, a transmission type identifier, and a device identifier of the first terminal device.

[0118] Optionally, the MQTT server determines which terminal devices to transmit the downlink control request from the common service platform to based on the first downlink topic. For example, if the first downlink topic includes the device identifier of the first terminal device, the MQTT server sends the downlink control request to the first terminal device; if the first downlink topic does not include the device identifier of the terminal device, the MQTT server sends the downlink control request to all terminal devices that subscribe to the first service respectively.

[0119] Exemplarily, the first downlink topic is represented as: Server / rc / V1 / down / Remote / %vin, where Server refers to a platform identifier of the public server platform, down refers to a downlink transmission identifier, remote refers to a transmission type identifier, and vin refers to a device identifier code of the first terminal device.

[0120] Optionally, the first downlink topic includes device identifier codes of k terminal devices, where k is a positive integer. Exemplarily, the first downlink topic includes device identifier codes of multiple terminal devices, so that one downlink topic can be shared by multiple terminal devices, that is, the public server only needs to send a downlink control request to the MQTT server through the first downlink topic once, and the MQTT server can forward the downlink control request to multiple terminal devices according to the first downlink topic. Compared with the public service platform setting a specific downlink topic for each terminal device, this setting helps to reduce the transmission times of the public service platform for downlink control requests with the same content, and helps to reduce the transmission pressure of the public service platform.

[0121] In some embodiments, the Quality of Service (QoS) level between the first terminal device and the MQTT server is the highest level among at least one QoS level; and / or, the QoS level between the MQTT server and the public service platform is the highest level among at least one QoS level.

[0122] In some embodiments, the QoS level is used to indicate the number of information transmissions between the MQTT server and the first terminal device, or is used to indicate the number of information transmissions between the MQTT server and the public service platform.

[0123] Optionally, the highest QoS level is used to indicate that the MQTT server only relays the received information once. Exemplarily, for a downlink control request received from the public service platform, the MQTT server only transmits the downlink control request to the first terminal device once, regardless of whether the first terminal device correctly receives the downlink control request or not, the MQTT server does not send the downlink control request to the first terminal device again.

[0124] Similarly, for an uplink feedback result received from the first terminal device, the MQTT server only transmits the uplink feedback result to the public service platform once, regardless of whether the public service platform correctly receives the uplink feedback result or not, the MQTT server does not send the uplink feedback result to the public service platform again.

[0125] In one aspect, in this way, the transmission times of the MQTT server for downlink control requests and uplink feedback results are reduced, which helps to reduce the pressure of the MQTT server for relaying information.

[0126] On the other hand, the MQTT server only relays the downlink control request once, which helps to avoid the situation that the terminal device has actually received the downlink control request, but the MQTT server considers that the terminal device has not received the downlink control request, and then repeatedly forwards the downlink control request to the terminal device, causing the terminal device to execute the first service multiple times, thereby affecting the implementation effect of the remote control method. By setting the QoS to the highest level, the reliability of remotely controlling the terminal device can be improved.

[0127] In some embodiments, the first terminal device is a vehicle terminal device, and the communication device in the first terminal device completes communication transmission with the MQTT server through the first uplink topic and the first downlink topic.

[0128] In some embodiments, the first terminal device is a vehicle computer configured in a vehicle, and the first terminal device has a communication function which is completed by the communication device in the first terminal device. The communication device serves as a gateway in the first terminal device and is responsible for completing communication with other devices.

[0129] Optionally, the communication device in the first terminal device listens to the first downlink topic, so as to timely obtain the downlink control request when the MQTT server forwards the downlink control request based on the first downlink topic.

[0130] Optionally, after the first terminal device generates the uplink feedback result, the communication device in the first terminal device sends the uplink feedback result to the MQTT server through the first uplink topic.

[0131] In some embodiments, in the case where the first terminal device is a vehicle terminal device, the first service refers to a related service, and the first service is implemented by controlling at least an electronic controller unit in the vehicle through the vehicle terminal device. For example, the first service includes but is not limited to at least one of the following: automatic navigation, automatic parking, opening / closing of the air conditioner in the vehicle, opening / closing of the vehicle door, control of the closing degree of the sunroof, turning on of the vehicle sensor, turning on / off of the driving recorder, etc. It should be noted that the first service is set according to actual needs, and is not limited herein. For example, the device identification code of the first terminal device refers to a vehicle identification code (VIN).

[0132] In some embodiments, the communication device in the first terminal device comprises a telematics box (T_BOX), the T_BOX is coupled with a plurality of electronic control units (ECUs) in the first terminal device, and the T_BOX controls at least one of the plurality of electronic controllers to perform the first service based on the downlink control request.

[0133] In some embodiments, the T_BOX refers to a communication element in the first terminal device, and the T_BOX is connected with other devices in the first terminal device through a bus of the first terminal device. Optionally, the T_BOX comprises a communication module (such as a Bluetooth module, a WiFi module, a subscriber identity module (SIM) card, etc.) and a power supply device.

[0134] For the purpose of saving power consumption and other factors, the state of the T_BOX comprises a full-load state, a sleep state and a low-power state. The T_BOX in the full-load state can communicate with other devices, and the T_BOX in the sleep state or the low-power state needs to be converted to the full-load state to communicate with other devices.

[0135] Optionally, the T_BOX is coupled with at least one ECU in the first terminal device through a bus of the first terminal device. After the T_BOX receives the downlink control request, the T_BOX decodes the downlink control request according to a transmission protocol file to obtain a service type identifier of the first service and parameters related to the first service. Then, the T_BOX mobilizes the at least one ECU to complete the execution process of the first service based on the service type identifier of the first service and the parameters related to the first service.

[0136] Figure 5 is a schematic diagram of a control request processing method provided by an exemplary embodiment of the present application.

[0137] As shown in Figure 5 , the public service platform generates a downlink control request and sends the downlink control request to an MQTT server through a first downlink topic. The MQTT server sends the downlink control request to the first terminal device through the first downlink topic. After the terminal device receives the downlink control request, the terminal device executes the first service and generates an uplink feedback result corresponding to the downlink control request. The first terminal device sends the uplink feedback result to the MQTT server through a first uplink topic. The MQTT sends the uplink feedback result to the public service platform through the first uplink topic. Optionally, in this process, the device identifier code of the first terminal device is included in the first downlink topic and the first uplink topic, so that one-to-one information transfer is realized through MQTT, which is helpful to realize personalized remote control of the terminal device.

[0138] Referring to Figure 6 Fig. 6 shows a flow chart of a control request processing method according to another embodiment of the present application, and the execution subject of each step of the method can be a public service platform. The method can include at least one of the following steps (610-620):

[0139] In step 610, a downlink control request is sent to an MQTT server through a first downlink topic, and the downlink control request is used to request the first terminal device to execute a first service. The MQTT server is used to complete the information transfer between the first terminal device and the public service platform.

[0140] In step 620, an uplink feedback result sent by the MQTT server is received through a first uplink topic, and the uplink feedback result is generated by the first terminal device. The uplink feedback result is used to feed back the processing result of the downlink control request.

[0141] For the specific content of the embodiments of the present application, please refer to the foregoing description, which will not be repeated here.

[0142] In some embodiments, before step 610, the public service platform further includes the following steps:

[0143] In step 605, in the case that the first terminal device is in an offline state, wake-up information is sent to the first terminal device, and the wake-up information is used to control the communication device of the first terminal device to switch from a standby state to an online state.

[0144] Optionally, in addition to the information transfer between the public service platform and the first terminal device through the MQTT platform, the data transfer between the public service platform and the first terminal device can also be completed through a TCP protocol. For example, after the first terminal device is powered on, a TCP communication connection is established between the first terminal device and the public service platform. In this process, the first terminal device reports a device identification code to the public service platform. For the purpose of power saving, the communication device in the first terminal device switches from a full load state to a low power consumption state or a sleep state. Before this, the TCP connection between the first terminal device and the public service platform is disconnected, and the communication state (including an online state and an offline state) of the first terminal device is recorded in the public service platform.

[0145] In some embodiments, before the public service platform sends the downlink control request, the public service platform determines whether the first terminal device is in an offline state. If the terminal device is not in the offline state, the public service platform directly sends the downlink control request to the MQTT server through the first downlink topic. If the terminal device is in the offline state, the public service platform first sends wake-up information to the first terminal device, so as to convert the first terminal device from the offline state to the online state. In some embodiments, the wake-up information is blank information. Optionally, the public service platform sends a blank information in the form of a short message to the first terminal device. After the first terminal device receives the blank information, the communication device in the first terminal device is controlled to convert to a full load state. Then, the first terminal device attempts to establish a TCP connection with the public service platform, so that the public service platform determines that the first terminal device is in the online state, and then sends the downlink control request to the MQTT server through the first downlink topic, so that the MQTT platform transmits the downlink control request to the first terminal device.

[0146] The following is an apparatus embodiment of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the apparatus embodiments of the present application, please refer to the method embodiments of the present application.

[0147] Please refer to Figure 7 which shows a block diagram of a control request processing apparatus provided by an embodiment of the present application. The apparatus has the functions of implementing the control request processing method described above, which can be implemented by hardware or corresponding software executed by hardware. The apparatus can be the terminal device introduced above or can be arranged in the terminal device. The apparatus 700 can include a message receiving module 710, a result generating module 720, and a result feedback module 730.

[0148] The message receiving module 710 is configured to receive a downlink control request from a message queue telemetry transport (MQTT) server through a first downlink topic, where the downlink control request is generated by a public service platform and is used to request a first terminal device to execute a first service.

[0149] The result generating module 720 is configured to generate an uplink feedback result corresponding to the downlink control request, where the uplink feedback result is used to feed back a processing result of the downlink control request.

[0150] The result feedback module 730 is configured to send the uplink feedback result to the MQTT server through a first uplink topic, so that the MQTT server sends the uplink feedback result to the public service platform, where the first uplink topic and the first downlink topic are both used to perform communication transmission related to the first service.

[0151] In some embodiments, the result generation module 720 is configured to determine, according to the transport protocol file, an uplink feedback format of the first service, the uplink feedback format being used to indicate at least one content field included in the uplink feedback result; and generate the uplink feedback result based on the uplink feedback format.

[0152] In some embodiments, the transport protocol file is pre-configured, and the transport protocol file is used to indicate a communication format corresponding to each of at least one service provided by the common service platform, the communication format corresponding to each of the at least one service including at least one of the following: a field format of a downlink control request about the service, a field format of an uplink feedback result about the service.

[0153] In some embodiments, the content field in the downlink control request includes at least one of the following: a service type identifier used to represent the first service, and a request content including a parameter related to the first service; and / or the content field in the uplink feedback result includes at least one of the following: a general reply code used to represent an execution of the first service by the first terminal device, and a feedback content including a parameter related to the first service after the downlink control request is executed.

[0154] In some embodiments, the first uplink topic includes at least one of the following: a platform identifier of the common server platform, an uplink transmission identifier, a transmission type identifier, and a device identifier code of the first terminal device; and / or the first downlink topic includes at least one of the following: a platform identifier of the common server platform, a downlink transmission identifier, a transmission type identifier, and a device identifier code of the first terminal device.

[0155] In some embodiments, a quality of service (QoS) level between the first terminal device and the MQTT server is a highest level among at least one QoS level; and / or a QoS level between the MQTT server and the common service platform is a highest level among at least one QoS level.

[0156] In some embodiments, the first terminal device is a vehicle-mounted terminal device, and a communication device in the first terminal device completes communication transmission with the MQTT server through the first uplink topic and the first downlink topic.

[0157] In some embodiments, the communication device in the first terminal device comprises a telematics box T_BOX coupled with a plurality of electronic controller units ECUs in the first terminal device, and the T_BOX controls at least one of the plurality of electronic controllers to perform the first service based on the downlink control request.

[0158] It should be noted that Figure 8 which shows a block diagram of a control request processing apparatus provided by another embodiment of the present application. The apparatus has the functions of implementing the control request processing method described above, which can be implemented by hardware or corresponding software executed by hardware. The apparatus can be the server introduced above or be arranged in a computer device. The apparatus 800 can comprise: a request receiving module 810, a result receiving module 820.

[0159] The request receiving module 810 is configured to send a downlink control request to an MQTT (Message Queue Telemetry Transport) server through a first downlink topic, the downlink control request being used to request a first terminal device to perform a first service, and the MQTT server being used to complete information relay between the first terminal device and a public service platform.

[0160] The result receiving module 820 is configured to receive an uplink feedback result sent by the MQTT server through a first uplink topic, the uplink feedback result being generated by the first terminal device and used to feed back a processing result of the downlink control request.

[0161] In some embodiments, the apparatus 800 further comprises a device wake-up module configured to send wake-up information to the first terminal device in a case where the first terminal device is in an offline state, the wake-up information being used to control a communication device of the first terminal device to switch from a standby state to an online state.

[0162] It should be noted that the apparatus provided by the above embodiments, when implementing its functions, is only exemplified by the above division of the functional modules, and in actual applications, the above functions can be completed by different functional modules according to needs, that is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0163] It should be noted that Figure 9 which shows a structural block diagram of a computer device 900 provided by an embodiment of the present application. The computer device 900 can be the terminal device or the server introduced above and is used to implement the control request processing method described above.

[0164] Typically, computer device 900 includes a processor 901 and a memory 902.

[0165] Processor 901 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 901 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field Programmable Gate Array), and PLA (Programmable Logic Array). Processor 901 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 901 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 901 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0166] The memory 902 may include one or more computer-readable storage media, which may be non-transitory. The memory 902 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices.

[0167] Those skilled in the art will understand that Figure 9 The structure shown does not constitute a limitation on the computer device 900, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0168] In one example embodiment, a computer device is also provided, comprising a processor and a memory storing a computer program. The computer program is configured to be executed by one or more processors to implement the control request processing method described above.

[0169] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein a computer program is stored therein, which, when executed by a processor of a computer device, implements the control request processing method described above.

[0170] Optionally, the computer readable storage medium can be a ROM (Read-Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0171] In the example embodiment, a computer program product is also provided, which, when running on a computer device, causes the computer device to perform the above control request processing method.

[0172] It should be understood that "multiple" mentioned herein refers to two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A existing alone, A and B existing together, and B existing alone. The character " / " generally represents that the associated objects before and after it are in an "or" relationship. In addition, the step numbers described herein only exemplarily show a possible execution order between steps, and in some other embodiments, the above steps can also be executed in a non-numbered order, such as two steps with different numbers being executed at the same time, or two steps with different numbers being executed in an order opposite to that shown in the figure, and the embodiments of the present application are not limited to this.

[0173] The above only describes example embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A control request processing method, characterized in that, The method is executed by a first terminal device, and the method includes: The first downlink control request is received from the Message Queue Telemetry Transmission (MQTT) server via a first downlink topic. The downlink control request is generated by the public service platform and is used to request the first terminal device to perform the first service. According to the transmission protocol file, the uplink feedback format of the first service is determined. The uplink feedback format is used to indicate at least one content field included in the uplink feedback result. The transmission protocol file is pre-configured and is used to indicate the communication format corresponding to at least one service provided by the public service platform. For each of the at least one service, the communication format corresponding to the service includes at least one of the following: the field format of the downlink control request of the service, and the field format of the uplink feedback result of the service. Based on the aforementioned uplink feedback format, an uplink feedback result corresponding to the downlink control request is generated, and the uplink feedback result is used to provide feedback on the processing result of the downlink control request. The uplink feedback result is sent to the MQTT server through the first uplink topic, so that the MQTT server can send the uplink feedback result to the public service platform. Both the first uplink topic and the first downlink topic are used to perform communication transmissions related to the first service. The content fields in the downlink control request include at least one of the following: service type identifier and request content, wherein the service type identifier is used to characterize the first service, and the request content includes parameters related to the first service; And / or, the content fields in the uplink feedback result include at least one of the following: a general response code and feedback content, wherein the general response code is used to characterize the execution status of the first terminal device on the first service, and the feedback content includes parameters related to the first service after the downlink control request is executed.

2. The method according to claim 1, characterized in that, The first uplink topic includes at least one of the following: the platform identifier of the public service platform, the uplink transmission identifier, the transmission type identifier, and the device identifier code of the first terminal device; And / or, The first downlink subject includes at least one of the following: the platform identifier of the public service platform, the downlink transmission identifier, the transmission type identifier, and the device identifier code of the first terminal device.

3. The method according to claim 1, characterized in that, The QoS level between the first terminal device and the MQTT server is the highest among at least one QoS level; And / or, The QoS level between the MQTT server and the public service platform is the highest among at least one QoS levels.

4. The method according to claim 1, characterized in that, The first terminal device is an in-vehicle terminal device. The communication device in the first terminal device completes the communication transmission with the MQTT server through the first uplink topic and the first downlink topic. The communication device in the first terminal device includes a telematics box T_BOX. The T_BOX is coupled to multiple electronic controller units (ECUs) in the first terminal device. The T_BOX controls at least one of the multiple ECUs to execute the first service based on the downlink control request.

5. A control request processing method, characterized in that, The method is executed by a public service platform, and the method includes: A downlink control request is sent to the Message Queue Telemetry Transmission (MQTT) server via the first downlink topic. The downlink control request is used to request the first terminal device to perform the first service. The MQTT server is used to complete the information relay between the first terminal device and the public service platform. The first terminal device receives an uplink feedback result sent by the MQTT server through a first uplink topic. The uplink feedback result is generated by the first terminal device based on the uplink feedback format of the first service. The uplink feedback format is determined according to a transmission protocol file. The uplink feedback format is used to indicate at least one content field included in the uplink feedback result. The transmission protocol file is pre-configured and is used to indicate the communication format corresponding to at least one service provided by the public service platform. For each of the at least one service, the communication format corresponding to the service includes at least one of the following: a field format for a downlink control request of the service, and a field format for an uplink feedback result of the service. The uplink feedback result is used to provide feedback on the processing result of the downlink control request. The content fields in the downlink control request include at least one of the following: service type identifier and request content, wherein the service type identifier is used to characterize the first service, and the request content includes parameters related to the first service; And / or, the content fields in the uplink feedback result include at least one of the following: a general response code and feedback content, wherein the general response code is used to characterize the execution status of the first terminal device on the first service, and the feedback content includes parameters related to the first service after the downlink control request is executed.

6. A control request processing apparatus, characterized in that, The device includes: The message receiving module is used to receive downlink control requests from the Message Queue Telemetry Transmission (MQTT) server through a first downlink topic. The downlink control requests are generated by the public service platform and are used to request the first terminal device to perform a first service. The result generation module is used to determine the uplink feedback format of the first service according to the transmission protocol file. The uplink feedback format is used to indicate at least one content field included in the uplink feedback result. The transmission protocol file is pre-configured and is used to indicate the communication format corresponding to at least one service provided by the public service platform. For each of the at least one service, the communication format corresponding to the service includes at least one of the following: the field format of the downlink control request of the service, and the field format of the uplink feedback result of the service. Based on the uplink feedback format, the module generates the uplink feedback result corresponding to the downlink control request. The uplink feedback result is used to provide feedback on the processing result of the downlink control request. The result feedback module is used to send the uplink feedback result to the MQTT server through the first uplink topic, so that the MQTT server can send the uplink feedback result to the public service platform. Both the first uplink topic and the first downlink topic are used to perform communication transmissions related to the first service. The content fields in the downlink control request include at least one of the following: service type identifier and request content, wherein the service type identifier is used to characterize the first service, and the request content includes parameters related to the first service; And / or, the content fields in the uplink feedback result include at least one of the following: a general response code and feedback content, wherein the general response code is used to characterize the execution status of the first terminal device on the first service, and the feedback content includes parameters related to the first service after the downlink control request is executed.

7. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing a computer program that is loaded and executed by the processor to implement the control request processing method as described in any one of claims 1 to 4, or the control request processing method as described in claim 5.

Images