Data transmission method and apparatus, device, and storage medium

Abstract

The application provides a data transmission method, device and equipment and a storage medium, which can be applied to various scenes such as cloud technology and Internet of Things. The method comprises the following steps: a controller receives service configuration parameters sent by a service device; when a network element device fault is detected, the received service configuration parameters are written into a queue corresponding to the network element device; and when the network element device is detected to be back online, the service configuration parameters in the queue are sent to the network element device. That is, when the network element device fails, the application does not affect the upper-layer service, so that the service device in the application layer can continue to arrange tasks for the service configuration parameters of the network element device, when the network element device recovers, the service configuration parameters missed during the network element device failure are automatically synchronized, the atomicity and sequence of the service configuration parameters are ensured, and the transmission efficiency and accuracy of the service configuration parameters are improved.

Description

Technical Field

[0001] This application relates to the field of data transmission technology, and in particular to a data transmission method, apparatus, device, and storage medium. Background Technology

[0002] With the development of communication technology, the Internet of Things (IoT) technology has emerged. The IoT refers to connecting any object to a network through information sensing devices and according to agreed-upon protocols. Objects exchange and communicate information through information transmission media to achieve functions such as intelligent identification.

[0003] The Internet of Things (IoT) mainly consists of controllers and multiple network elements. Controllers send service configuration parameters from upper-layer applications to network elements, enabling the network elements to execute corresponding services based on these parameters. However, current technology cannot achieve rapid and accurate updates of service configuration parameters after a network element fails and restarts. Summary of the Invention

[0004] This application provides a data transmission method, apparatus, device, and storage medium to enable rapid and accurate updates of service configuration parameters after a network element device fails and restarts.

[0005] In a first aspect, embodiments of this application provide a data transmission method, including: Receive service configuration parameters sent by the service device, the service configuration parameters being used to instruct the network element device to execute the target service; When a network element device failure is detected, the received service configuration parameters are written into the queue corresponding to the network element device. When the network element is detected to be back online, the service configuration parameters in the queue are sent to the network element.

[0006] Secondly, embodiments of this application provide a data transmission apparatus, including: The receiving unit is used to receive service configuration parameters sent by the service equipment, the service configuration parameters being used to instruct the network element equipment to execute the target service; The processing unit is used to write the received service configuration parameters into the queue corresponding to the network element device when a network element device fault is detected. The sending unit is used to send the service configuration parameters in the queue to the network element device when the network element device is detected to be back online.

[0007] Thirdly, embodiments of this application provide an electronic device, including: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to perform the method of the first aspect.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to perform the method of the first aspect.

[0009] Fifthly, embodiments of this application provide a chip for implementing the methods of any one of the first aspects or their respective implementations. Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the methods of any one of the first aspects or their respective implementations.

[0010] In a sixth aspect, embodiments of this application provide a computer program product, including computer program instructions that cause a computer to perform the methods in any of the first aspects or their implementations described above.

[0011] In a seventh aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to perform the methods in any of the first aspects or their implementations described above.

[0012] In summary, this application establishes a queue for network element devices. During data transmission, the controller receives service configuration parameters sent by service devices, which instruct the network element devices to execute target services. When a network element device failure is detected, the received service configuration parameters are written into the corresponding queue of the network element device. When the network element device is detected to be back online, the service configuration parameters in the queue are sent back to the network element device. In other words, this application ensures that upper-layer services are not affected when a network element device fails, allowing application layer service devices to continue orchestrating tasks based on the network element device's service configuration parameters. When the network element device recovers, it automatically synchronizes the service configuration parameters missed during the failure period, ensuring the atomicity and order of the service configuration parameters and preventing out-of-order delivery to the network element device that could cause a failure. Furthermore, the entire process requires no manual intervention, improving the transmission efficiency and accuracy of service configuration parameters. Attached Figure Description

[0013] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application; Figure 2 A flowchart illustrating a data transmission method provided in an embodiment of this application; Figure 3 This is a schematic diagram of the system architecture involved in an embodiment of this application; Figure 4 This is a schematic diagram of a queue according to an embodiment of this application; Figure 5 This is a schematic flowchart of a data transmission method provided in an embodiment of this application; Figure 6 This is a schematic flowchart of a data transmission method provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a data transmission device provided in an embodiment of this application; Figure 8 This is a schematic block diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0014] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0016] The technical solutions provided in this application can be applied to technical fields that require data transmission, such as the Internet of Things and cloud computing.

[0017] The Internet of Things (IoT) refers to the use of various information sensors, RFID technology, GPS, infrared sensors, laser scanners, and other devices and technologies to collect real-time data on any object or process that needs to be monitored, connected, or interacted with. This data includes information on sound, light, heat, electricity, mechanics, chemistry, biology, location, and other parameters. Through various possible network access methods, it achieves ubiquitous connectivity between things and between things and people, enabling intelligent perception, identification, and management of objects and processes. The IoT is an information carrier based on the internet and traditional telecommunications networks, enabling all independently addressable ordinary physical objects to form an interconnected network.

[0018] Cloud IoT aims to connect the information sensed and commands received by traditional IoT devices to the Internet, truly achieving networking. It also enables massive data storage and computation through cloud computing technology. Due to the nature of IoT, which involves connecting things to each other and sensing the current operating status of each "object" in real time, a large amount of data is generated in this process. How to aggregate this information and how to sift out useful information from the massive amount of data to support decision-making for future development have become key issues affecting the development of IoT. As a result, IoT cloud based on cloud computing and cloud storage technology has become a powerful support for IoT technology and applications.

[0019] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application, such as... Figure 1 As shown, it includes service equipment 101, controller 102, multiple network element devices 103 and cloud server 104.

[0020] Service device 101 is used to send service configuration parameters to each network element device 103. A set of service configuration parameters corresponds to a service. The network element device 103 can execute the corresponding service according to the service configuration parameters sent by service device 101.

[0021] The controller 102 receives service configuration parameters sent by the service device 101 and sends these parameters to the corresponding network element device 103. In some embodiments, the controller 102 can control the network element device 103 to perform corresponding operations, enabling multiple network element devices 103 to collaboratively provide intelligent services to users. The network element device 103 can also communicate with the cloud server 104. For example, the controller 102 can send data related to the network element device 103 to the cloud server 104.

[0022] In some embodiments, the controller 102 may be a terminal device with control functions, such as a smartphone, a laptop, etc.

[0023] In some embodiments, the controller 102 can be a server, which can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server 104 that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0024] Cloud server 104 can provide data services to the multiple network element devices 103, such as providing cloud storage to the multiple network element devices 103. Cloud storage is a new concept that extends and develops from the concept of cloud computing. A distributed cloud storage system refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to aggregate a large number of storage devices of various types (storage devices are also called storage nodes) in the network through application software or application interfaces to work together and jointly provide data storage and business access functions to the outside world.

[0025] Network element device 103 can also be understood as an Internet of Things (IoT) device, that is, an IoT device with specific functions. In some embodiments, network element device 103 can be any smart device, such as a television, smartphone, tablet, laptop, desktop computer, smart air conditioner, smart speaker, hygrometer / thermometer, curtain remote control, smart clock, smart water heater, smart camera device, smart lighting, smart vehicle, etc. This application embodiment does not limit the specific type of network element device 103.

[0026] In one example, network element 103 can directly establish a wireless communication connection with controller 102 and conduct data communication through Internet of Things communication protocols, such as smart home communication protocols.

[0027] In one example, network element 103 can communicate with controller 102 via other communication service devices according to the Internet of Things communication protocol.

[0028] In one example, controller 102 can communicate with cloud server 104 via a mobile communication network.

[0029] In one example, controller 102 can communicate with cloud server 104 via a wireless communication network provided by other communication service devices.

[0030] In some embodiments, the controller 102 described above can be a Software Defined Network (SDN) controller. The SDN controller's distribution of service configuration parameters to network element 103 has two characteristics: first, these service configuration parameters are strongly atomic, meaning that a service is a set of service configuration parameters; either all parameters in this set are configured successfully, or all fail, with no intermediate states. Second, the services between network element 103 have strong dependencies and can only be executed sequentially; out-of-order execution will result in unpredictable errors. When network element 103 fails and restarts, the SDN controller must ensure both atomicity and sequentiality when sending service configuration parameters to network element 103.

[0031] Currently, when a network element device fails and is restarted, the service configuration parameters are distributed through a configuration verification scheme.

[0032] The configuration verification scheme involves sending an "online" message to the controller after a network element recovers. The controller then initiates configuration verification, comparing the service-side and network element-side parameter configurations. If there are no discrepancies, the network element resumes service. If discrepancies exist, the issue is reported to operations personnel who then investigate, resolve the conflicts, and synchronize the changes back to the network element. Only after the network element is successfully updated can it resume providing services. Therefore, this configuration verification scheme requires manual intervention and is inefficient and inaccurate.

[0033] To address the aforementioned technical issues, in this embodiment, when a network element device malfunctions, the controller can normally receive service configuration parameters sent by upper-layer service devices and store these parameters in a queue corresponding to the network element device. Upon detecting that the network element device has re-energized, the controller can send the service configuration parameters from the queue back to the network element device. In other words, when a network element device malfunctions, upper-layer services are not affected, and task orchestration of the network element device's service configuration parameters can continue. When the network element device recovers, the controller automatically synchronizes the service configuration parameters missed during the malfunction, ensuring the atomicity and sequentiality of the service configuration parameters and preventing out-of-order delivery to the network element device that could cause a malfunction. Furthermore, the entire process requires no manual intervention, improving the transmission efficiency and accuracy of the service configuration parameters.

[0034] The technical solutions of the embodiments of this application will be described in detail below through some examples. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0035] Figure 2 A flowchart illustrating a data transmission method provided in an embodiment of this application. Figure 2 As shown, the method includes the following steps: S201. Receive service configuration parameters sent by the service device. These service configuration parameters are used to instruct the network element device to execute the target service.

[0036] The execution subject of this application embodiment is a device with data transmission function, such as a data transmission device. The data transmission device can be a separate electronic device, or a part of an electronic device, such as a processor in an electronic device.

[0037] In some embodiments, the data transmission device is the aforementioned Figure 1 The controller shown is, for example, an SDN controller.

[0038] The following example uses a controller as the execution subject for illustration.

[0039] It should be noted that the controller described below can be a single controller or a controller cluster composed of multiple controllers, and this application embodiment does not impose any restrictions on this.

[0040] In this embodiment, the data transmission method of each network element device is consistent. For ease of description, this embodiment uses one network element device as an example.

[0041] The service device in this application embodiment is used to generate service configuration parameters corresponding to the network element device, and send them to the network element device through the controller. The network element device can execute the corresponding target service according to the service configuration parameters.

[0042] Figure 3 This is a schematic diagram of a system architecture according to an embodiment of this application, including an application layer and a control layer. Service devices reside in the application layer, which primarily deals with business logic; exceptions from lower layers are transparent to the application layer. The controller resides in the control layer, which provides high-availability services to upper-layer northbound applications through a cluster, such as an SDN controller cluster. When a network element device fails, the fault is closed to the controller, preventing the exception from being transmitted to the application layer. This allows the application layer to generate normal service configuration parameters for the network element device.

[0043] This application does not limit the method by which the service equipment generates the service configuration parameters corresponding to the network element equipment.

[0044] In one possible implementation, such as Figure 3 As shown, an application app is installed on the service device, allowing users to generate service configuration parameters for the network element device. For example, if the network element device is a smart air conditioner, and the user expects the smart air conditioner to turn on when the indoor temperature exceeds 25 degrees Celsius, the user can write the service configuration parameters for this target service in the application app and send them to the controller. The controller then sends these parameters to the smart air conditioner, which, based on the configuration parameters, turns on when the indoor temperature exceeds 25 degrees Celsius.

[0045] S202. When a network element device fault is detected, the received service configuration parameters are written into the queue corresponding to the network element device.

[0046] Typically, network elements load their own configuration files upon restart. However, due to the high frequency of service configuration parameters being sent to network elements, synchronizing these parameters to the configuration file each time is inefficient. This is because the high-speed central processing unit (CPU) reduces computation to low-speed input / output (I / O) read / write operations. To improve forwarding capabilities, network elements typically store service configuration parameters in their memory upon receipt. When the memory is nearly full, the parameters are synchronized to the configuration file. Since network elements have limited memory resources, usually in the megabyte (MB) range, these parameters are frequently persisted to the configuration file.

[0047] Due to hardware limitations, network element devices have limited memory. Therefore, this embodiment sets up a queue for the network element device, which can be understood as an extended memory space for the network element device. In this way, the controller can store the service configuration parameters corresponding to the network element device in the queue corresponding to the network element device. When the network element device malfunctions, the upper layer can still continue to send parameters. After the network element device recovers, automatic synchronization can be achieved through the service configuration parameters in the queue. The application layer is unaware of whether the network element device malfunctioned.

[0048] Specifically, such as Figure 3 As shown, the data transmission system of this application embodiment also includes a queue layer. That is, in this application embodiment, a queue is set up for each network element device, and the data related to the network element device can be stored in the queue.

[0049] In some embodiments, the queue of this application is located in the cloud, such as on a cloud server. That is, in this application, a memory space is extended in the cloud for the network element device to store the data corresponding to the network element device.

[0050] like Figure 4 As shown, the queue itself has a first-in, first-out (FIFO) characteristic, which satisfies the sequential requirements of the issued business configuration parameters. For example, business configuration parameters a1 to a2... n-1 They enter the queue sequentially; correspondingly, when dequeuing, the business configuration parameters a1 to a... n-1 The configuration parameters are dequeued sequentially. In this way, the service configuration parameters issued first are synchronized to the network element devices first, and the service configuration parameters issued later are synchronized to the network element devices later, so as to maintain consistency with the operation of the application layer.

[0051] Based on this, in this embodiment of the application, when a network element device failure is detected, the received service configuration parameters are written into the queue corresponding to the network element device. That is, in this embodiment of the application, when a network element device fails, the service configuration parameters are not directly sent to the network element device. Instead, the parameters are sent to the queue corresponding to the network element device in the queue layer through interaction with the queue layer. After the network element device recovers, the service configuration parameters in the queue layer can be automatically synchronized, achieving abnormal synchronization without affecting the controller's orchestration.

[0052] S203. When the network element device is detected to be back online, the service configuration parameters in the queue are sent to the network element device.

[0053] In this embodiment, when a network element device failure is detected, the service configuration parameters issued by the service device can be written into the queue corresponding to the network element device. When the network element device is detected to be back online, the service configuration parameters stored in the queue are sent to the network element device for processing. As can be seen from the above, the queue corresponding to the network element device can be understood as an extended memory space for the network element device. The network element device can quickly interact with the queue, so that when the network element device is back online, it can quickly obtain the service configuration parameters from the queue for operation, thereby improving the forwarding efficiency of the service configuration parameters and enhancing the service execution response of the network element device.

[0054] In some embodiments, such as Figure 3 As shown, the data transmission system in this embodiment of the application also includes a forwarding layer, which mainly focuses on route calculation and packet forwarding. Based on this, when the controller detects that a network element device has come back online, it can send the service configuration parameters in the queue to the network element device for processing through the forwarding layer.

[0055] In this embodiment, the controller manages the service configuration parameters of a massive number of network elements in a unified manner. If a network element fails, the controller needs to close the loop on the impact of this failure on services. Specifically, when a network element fails, the controller writes the service configuration parameters sent by the service devices to that network element into the queue corresponding to that network element. This way, for application-layer service devices, the service configuration parameters sent by the service devices to the controller are not affected, and the application-layer service devices are unaware of the network element failure. For network element failure recovery, the controller can send the service configuration parameters from the queue corresponding to that network element to that network element. Since the queue has a first-in, first-out characteristic, the atomicity and order of the network element receiving the service configuration parameters are not affected, and the entire process does not require manual intervention, improving the transmission efficiency and accuracy of the service configuration parameters.

[0056] In some embodiments, the queues corresponding to the aforementioned network element devices include a pending submission queue and a submitted queue. That is, in this embodiment, each network element device can have one pending submission queue and one submitted queue. The pending submission queue stores service configuration parameters that have not yet been submitted to the network element device. The submitted queue stores service configuration parameters that have already been submitted to the network element device. For example, the controller can first write the service configuration parameters issued by the service device into the pending submission queue. When sending the service configuration parameters in the pending submission queue to the network element device for processing, the service configuration parameters are transferred from the pending submission queue to the submitted queue. Therefore, the service configuration parameters stored in the submitted queue are the service configuration parameters currently running on the network element device.

[0057] In some embodiments, the queue corresponding to the network element is located in the cloud. This means that a persistent storage space is allocated to the network element in the cloud. This storage space can be designed as at least two types of queues: a pending-commit queue and a committed queue. Logically, these two queues can be considered dedicated to the network element. The committed queue is equivalent to the network element's memory, storing the service configuration parameters currently running in the network element's memory. The pending-commit queue is equivalent to a disk cache that is about to be loaded into the network element's memory. Once the service configuration parameters in the pending-commit queue are successfully sent to the network element, they can be transferred to the committed queue.

[0058] At this time, the step of writing the received service configuration parameters into the queue corresponding to the network element device when a network element device failure is detected in S202 above includes: writing the received service configuration parameters into the queue to be submitted when a network element device failure is detected.

[0059] As mentioned above, the submitted queue is equivalent to the memory of the network element device, storing the service configuration parameters currently running in the network element device's memory. When the network element device fails, the service configuration parameters currently running in the memory are lost. Therefore, when the network element device comes back online after a failure, it is necessary not only to send the service configuration parameters in the unsubmitted queue to the network element device, but also to send the service configuration parameters in the corresponding submitted queue to the network element device. Based on this, the process in S203 above, when the network element device is detected to be back online, sending the service configuration parameters in the queue to the network element device for processing includes: when the network element device is detected to be back online, sending the service configuration parameters in the pending submission queue and the service configuration parameters in the submitted queue to the network element device, where the submitted queue includes the service configuration parameters running on the network element device before the failure. Then, the service configuration parameters in the pending submission queue are transferred to the submitted queue.

[0060] In this embodiment of the application, the method for sending service configuration parameters in the submitted queue to the network element device includes at least the following two methods: Method 1: When a network element failure is detected, neither the pending nor submitted queues transmit data. Specifically, the received service configuration parameters are written to the pending queue of the network element, while the service configuration parameters in the submitted queue are not transferred. In this case, when the network element is detected to be back online, the controller sends both the service configuration parameters from the pending queue and the submitted queue of the network element to the network element.

[0061] Method 2: When a network element failure is detected, data transmission occurs between the pending submission queue and the submitted queue. Specifically, the received service configuration parameters are written to the unsubmitted queue of the network element, while the service configuration parameters in the submitted queue are transferred to the pending submission queue. At this point, the unsubmitted queue includes both service configuration parameters that have not yet been submitted to the network element and those that have been submitted. In this case, when the network element is detected to be back online, the service configuration parameters in the pending submission queue can be directly sent to the network element.

[0062] In some embodiments, the queues corresponding to the network element device include not only the unsubmitted queue and the submitted queue mentioned above, but also a failure queue. That is, in this embodiment, three queues are set up for the network element device in the cloud: an unsubmitted queue, a submitted queue, and a failure queue. The submitted queue is equivalent to the network element device's memory, storing the service configuration parameters currently running in the network element device's memory. The pending-submitted queue is equivalent to the disk cache about to be loaded into the network element device's memory, and the failure queue is equivalent to the network element device's external storage disk. When a service configuration parameter in the pending-submitted queue is successfully sent to the network element device, it can be transferred to the submitted queue. If the service configuration parameter in the pending-submitted queue fails to be sent to the network element device, a retry will be performed. If the retry also fails, the service configuration parameter in the pending-submitted queue will be transferred to the failure queue. Therefore, the failure queue includes service configuration parameters that were not successfully submitted to the network element device before the current failure. At this time, when the controller detects that the network element device has come back online, in addition to sending the service configuration parameters in the pending and submitted queues to the network element device, it also sends the service configuration parameters in the failure queue to the network element device, thereby ensuring that the network element device can obtain the complete service configuration parameters required after the fault restart.

[0063] In some embodiments, the controller sends the service configuration parameters in the failure queue to the network element device according to the retransmission mechanism. That is, in this embodiment, a preset number of retransmissions is set for the failure queue. The controller sends the service configuration parameters in the failure queue to the network element device. If the transmission fails, it determines whether the preset number of retransmissions has been reached. If the preset number of retransmissions has not been reached, it waits for one period (usually seconds) before retransmitting the service configuration parameters in the failure queue to the network element device.

[0064] In some embodiments, if the service configuration parameters in the failure queue are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters in the failure queue are transferred to the submitted queue for archiving.

[0065] In some embodiments, if the service configuration parameters in the failure queue are not successfully sent to the network element within the number of retransmissions corresponding to the retransmission mechanism, a failure message is reported. This failure message indicates that the service configuration parameters in the failure queue failed to be sent. For example, this identification information can be sent to operation and maintenance management personnel for service configuration parameter verification.

[0066] In other words, in this embodiment, if the queue corresponding to the network element device includes a failure queue, when the controller reconnects after detecting a network element device failure, it sends the service configuration parameters in the pending and submitted queues to the network element device, as well as the service configuration parameters in the failure queue. In some embodiments, to prevent service configuration parameter transmission failure due to network jitter or other reasons, in this embodiment, the controller sends the service configuration parameters in the failure queue to the network element device according to the retransmission mechanism. Specifically, if the transmission is successful, the service configuration parameter in the failure queue is transferred to the submitted queue for archiving. If the transmission fails, it is determined whether the retransmission count corresponding to the retransmission mechanism has been reached. If the retransmission count has not been reached, the controller waits for one period and then retransmits the service configuration parameter in the failure queue to the network element device. If the retransmission count has been reached, a failure message is reported, which indicates that the service configuration parameter in the failure queue failed to be transmitted.

[0067] In this embodiment of the application, the method by which the controller sends the service configuration parameters in the failure queue to the network element device includes at least the following two: Method 1: When the controller detects that a network element has come back online, it sends the service configuration parameters in the failure queue to that network element.

[0068] Method 2: When the controller detects a network element device failure, it first transfers the service configuration parameters in the failure queue to the pending submission queue. Then, when the controller detects that the network element device has come back online, it sends the service configuration parameters in the pending submission queue to the network element device.

[0069] As described above, in this embodiment, the queue corresponding to the network element device can be understood as an additional virtual memory space allocated to that network element device, and the size of this virtual memory space is limited. Therefore, in this embodiment, when the preset period arrives, the service configuration parameters in the submitted queue are saved to the configuration file of the network element device, and the service configuration parameters in the submitted queue are cleared. That is to say, in this embodiment, the queue corresponding to the network element device stores the service configuration parameters recently issued to the network element device by the service device. In this way, after the network element device comes back online, it can quickly obtain the service configuration parameters from the queue and start running. In addition, when the network element device restarts, it automatically loads the service configuration parameters in the configuration file, ensuring that the network element device can obtain complete service configuration parameters after restarting, thereby improving the working reliability of the network element device.

[0070] The data transmission method provided in this application sets up a queue for network element devices. During data transmission, the controller receives service configuration parameters sent by service devices. These service configuration parameters instruct the network element devices to execute target services. When a network element device failure is detected, the received service configuration parameters are written into the corresponding queue of the network element device. When the network element device is detected to be back online, the service configuration parameters in the queue are sent back to the network element device. In other words, this application does not affect upper-layer services when a network element device fails, allowing service devices in the application layer to continue task orchestration of the network element device's service configuration parameters. When the network element device recovers, it automatically synchronizes the service configuration parameters missed during the failure period, ensuring the atomicity and order of the service configuration parameters and preventing out-of-order delivery to the network element device that could cause a failure. Furthermore, the entire process requires no manual intervention, improving the transmission efficiency and accuracy of service configuration parameters.

[0071] The data transmission method of this application embodiment is described below when the target service is either synchronous or asynchronous.

[0072] Let's take a synchronous business as an example to illustrate.

[0073] Figure 5 This is a schematic diagram of a data transmission method provided in an embodiment of this application, as shown below. Figure 5 As shown, it includes: S501, Receive service configuration parameters sent by the service equipment.

[0074] Among them, the service configuration parameters are used to instruct network element devices to execute the target service.

[0075] In this embodiment of the application, if the target service is a synchronous service, the controller can skip the intermediate queue layer and directly send the service configuration parameters issued by the service device to the network element device.

[0076] The specific implementation process of S501 is described in the specific description of function S201, and will not be repeated here.

[0077] S502. If the target service is a synchronous service, determine whether the network element device is online.

[0078] In this embodiment, before sending the received service configuration parameters to the network element device, the controller first determines whether the network element device is online. For example, the network element device periodically sends heartbeat information to the controller. If the controller does not receive the heartbeat information from the network element device within a preset time, it determines that the network element device is offline. If the controller can receive the heartbeat information from the network element device normally, it determines that the network element device is online. If the controller determines that the network element device is online, it executes steps S503 to S505, that is, the controller sends the received service configuration parameters to the network element device. If the network element device successfully receives the parameters, it writes the service configuration parameters into the submitted queue for archiving. If the network element device fails to receive the parameters, it writes the service configuration parameters into the failure queue.

[0079] S503. If the network element is online, the received service configuration parameters will be sent to the network element according to the retransmission mechanism.

[0080] In this embodiment of the application, the received service configuration parameters are sent to the network element device according to the retransmission mechanism to avoid failure to send the service configuration parameters due to network or other reasons, thereby improving the reliability of the service configuration parameters.

[0081] S504. If the received service configuration parameters are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are written into the submitted queue.

[0082] S505. If the received service configuration parameters are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters shall be written into the failure queue.

[0083] In this embodiment of the application, no restrictions are placed on the specific method for determining whether the service configuration parameters have been successfully sent to the network element device.

[0084] In one possible implementation, when a network element receives service configuration parameters from the controller, the network element sends a response to the controller indicating that the service configuration parameters were successfully received. In this way, the controller can determine that the service configuration parameters were successfully sent based on the response from the network element.

[0085] If the controller sends the service configuration parameters to the network element and does not receive a response from the network element within a preset time, the controller determines whether the current number of transmissions exceeds the retransmission limit corresponding to the retransmission mechanism. If it does not exceed the retransmission limit, the controller retransmits the service configuration parameters to the network element. If the controller still does not receive a response from the network element when the retransmission limit is reached, the controller determines that the transmission of the service configuration parameters has failed.

[0086] In this embodiment, if the controller determines that the received service configuration parameters have been successfully sent to the network element within the retransmission count corresponding to the retransmission mechanism, the service configuration parameters are written to the submitted queue for archiving. If the controller determines that the received service configuration parameters have not been successfully sent to the network element within the retransmission count corresponding to the retransmission mechanism, the service configuration parameters are written to the failure queue. Optionally, when the service configuration parameters fail to be sent, a failure message is sent to indicate that the service configuration parameters have failed to be sent, so that operation and maintenance personnel can verify and process the failed service configuration parameters.

[0087] In some embodiments, the successful transmission of service configuration parameters to the network element device as described in this application includes not only the network element device receiving the service configuration parameters but also the qualification verification of the service configuration parameters. That is, the controller sends the service configuration parameters to the network element device, and after receiving the service configuration parameters, the network element device performs qualification verification on the service configuration parameters. For example, if the service configuration parameters include a network element device identifier, the network element device identifier is used to determine whether the service configuration parameters were sent to the network element device; or, the integrity of the service configuration parameters is checked, etc. This application does not limit the specific method of qualification verification of service configuration parameters. If the network element device determines that the service configuration parameters have passed the verification, then the service configuration parameters are considered successfully received. If the network element device does not receive the service configuration parameters, or if the network element device receives the service configuration parameters but the verification of the service configuration parameters fails, then the service configuration parameters are considered not successfully received.

[0088] The above S503 to S505 describe the transmission process of service configuration parameters when the target service is a synchronous service and the network element equipment is online.

[0089] In some embodiments, when the target service is a synchronous service and the network element device fails, the transmission process of the service configuration parameters in this application embodiment is described in S506 and S507 as follows.

[0090] S506. When a network element device fault is detected, the received service configuration parameters are written into the unsubmitted queue corresponding to the network element device, and the service configuration parameters in the submitted queue are transferred to the pending submission queue.

[0091] S507. When a network element is detected to be back online, the service configuration parameters in the pending submission queue are sent to the network element.

[0092] In this embodiment, when a network element device failure is detected, the received service configuration parameters are written into the queue corresponding to the network element device. That is, in this embodiment, when a network element device fails, the service configuration parameters are not directly sent to the network element device. Instead, the parameters are sent to the queue corresponding to the network element device through interaction with the queue layer. After the network element device recovers, the service configuration parameters in the queue layer can be automatically synchronized, achieving abnormal synchronization without affecting the controller's orchestration.

[0093] In some embodiments, when the controller detects that a network element has come back online, in addition to sending the service configuration parameters in the pending and submitted queues to the network element, it also sends the service configuration parameters in the failure queue to the network element, thereby ensuring that the network element can obtain the required complete service configuration parameters after a fault restart.

[0094] In some embodiments, according to the retransmission mechanism, the service configuration parameters in the pending submission queue are sent to the network element device to avoid failure to send the service configuration parameters due to network or other reasons, thereby improving the reliability of the service configuration parameter transmission. Specifically, if the service configuration parameters in the pending submission queue are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are written to the submitted queue. If the service configuration parameters in the pending submission queue are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are written to the failure queue.

[0095] For example, the controller sends service configuration parameters from the queue to the network element. If the network element receives the service configuration parameters from the controller, it sends a response to the controller indicating that the service configuration parameters were successfully received. In this way, the controller can determine that the service configuration parameters were successfully sent based on the response from the network element.

[0096] If the controller sends the service configuration parameters to the network element and does not receive a response from the network element within a preset time, the controller determines whether the current number of transmissions exceeds the retransmission limit corresponding to the retransmission mechanism. If it does not exceed the retransmission limit, the controller retransmits the service configuration parameters to the network element. If the controller still does not receive a response from the network element when the retransmission limit is reached, the controller determines that the transmission of the service configuration parameters has failed.

[0097] In this embodiment, if the controller determines that the service configuration parameters in the pending submission queue have been successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then the service configuration parameters are written into the submitted queue for archiving. If the controller determines that the service configuration parameters in the pending submission queue have not been successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then the service configuration parameters are written into the failure queue. Optionally, when the service configuration parameters fail to be sent, a failure message is sent. This failure message indicates that the service configuration parameters failed to be sent, allowing operation and maintenance personnel to verify the failed service configuration parameters.

[0098] S503 to S505 above describe the transmission process of service configuration parameters when the target service is a synchronous service and the network element is online. S506 and S507 above describe the transmission process of service configuration parameters when the target service is a synchronous service and the network element is offline due to a fault.

[0099] S508. When the preset period arrives, save the service configuration parameters in the submitted queue to the configuration file of the network element device, and clear the service configuration parameters in the submitted queue.

[0100] Since the queue size corresponding to the network element device is limited, this application embodiment needs to periodically write the service configuration parameters in the submitted queue into the configuration file, and clear the submitted queue to store the latest service configuration parameters, thereby ensuring the reliability of the transmission of service configuration parameters.

[0101] In some embodiments, when a network element restarts, it loads the service configuration parameters in the configuration file and receives the service configuration parameters in the unsubmitted queue and the submitted queue, thereby ensuring the normal operation of each service and improving the working reliability of the network element.

[0102] In this embodiment, if the target service is a synchronous service, the controller determines whether the current network element is online. If the network element is online, the controller directly sends the received service configuration parameters to the network element and writes them into the submitted queue of the network element after confirming successful transmission. If the controller determines that the network element is offline, the controller writes the received service configuration parameters into the pending submission queue of the network element. When the network element is detected to be back online, the controller sends the service configuration parameters in the pending submission queue back to the network element. This ensures that when the network element is back online after a failure, the service configuration parameters missed during the failure can be automatically synchronized, and the atomicity and order of the service configuration parameters are guaranteed. Out-of-order delivery of the parameters to the network element will not cause failures. The entire process does not require manual intervention, improving the transmission efficiency and accuracy of the service configuration parameters.

[0103] Figure 6 This is a schematic diagram of a data transmission method provided in an embodiment of this application, as shown below. Figure 6 As shown, it includes: S601, Receive service configuration parameters sent by the service equipment.

[0104] Among them, the service configuration parameters are used to instruct network element devices to execute the target service.

[0105] S602. If the target service is an asynchronous service, write the received service configuration parameters into the pending submission queue.

[0106] In this embodiment of the application, if the target service is an asynchronous service, the controller first writes the service configuration information into the pending submission queue of the network element device, and when the polling time of the pending submission queue arrives, it sends the service configuration parameters in the pending submission queue to the network element device.

[0107] S603. When the polling time of the pending submission queue arrives, determine whether the network element device is online.

[0108] In this embodiment, before sending the service configuration parameters in the queue to the network element device, the controller first determines whether the network element device is online. For example, the network element device periodically sends heartbeat information to the controller. If the controller does not receive the heartbeat information from the network element device within a preset time, it determines that the network element device is offline. If the controller can receive the heartbeat information from the network element device normally, it determines that the network element device is online.

[0109] If the controller determines that the network element is online, it executes steps S604 to S606. That is, the controller sends the received service configuration parameters to the network element. If the network element successfully receives the parameters, it writes the service configuration parameters into the submitted queue for archiving. If the network element fails to receive the parameters, it writes the service configuration parameters into the failure queue.

[0110] S604. When a network element device is detected to be online, the service configuration parameters in the pending submission queue are sent to the network element device according to the retransmission mechanism.

[0111] In this embodiment, the received service configuration parameters are sent to the network element device according to the retransmission mechanism to avoid failure to send service configuration parameters due to network or other reasons, thereby improving the reliability of service configuration parameter transmission.

[0112] S605. If the service configuration parameters in the pending submission queue are successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then the service configuration parameters are transferred from the pending submission queue to the submitted queue.

[0113] S606. If the service configuration parameters in the pending submission queue are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are transferred from the pending submission queue to the failure queue.

[0114] In this embodiment of the application, no restrictions are placed on the specific method for determining whether the service configuration parameters have been successfully sent to the network element device.

[0115] In one possible implementation, when a network element receives service configuration parameters from the controller, the network element sends a response to the controller indicating that the service configuration parameters were successfully received. In this way, the controller can determine that the service configuration parameters were successfully sent based on the response from the network element.

[0116] If the controller sends the service configuration parameters to the network element and does not receive a response from the network element within a preset time, the controller determines whether the current number of transmissions exceeds the retransmission limit corresponding to the retransmission mechanism. If it does not exceed the retransmission limit, the controller retransmits the service configuration parameters to the network element. If the controller still does not receive a response from the network element when the retransmission limit is reached, the controller determines that the transmission of the service configuration parameters has failed.

[0117] In this embodiment, if the controller determines that the received service configuration parameters have been successfully sent to the network element within the retransmission count corresponding to the retransmission mechanism, the service configuration parameters are written to the submitted queue for archiving. If the controller determines that the received service configuration parameters have not been successfully sent to the network element within the retransmission count corresponding to the retransmission mechanism, the service configuration parameters are written to the failure queue. Optionally, when the service configuration parameters fail to be sent, a failure message is sent to indicate that the service configuration parameters have failed to be sent, so that operation and maintenance personnel can verify and process the failed service configuration parameters.

[0118] In some embodiments, the successful transmission of service configuration parameters to the network element device as described in this application includes not only the network element device receiving the service configuration parameters but also the qualification verification of the service configuration parameters. That is, the controller sends the service configuration parameters to the network element device. After receiving the service configuration parameters, the network element device performs a qualification verification on the service configuration parameters. If the network element device determines that the service configuration parameters have passed the verification, it determines that the service configuration parameters have been successfully received and sends a response to the controller. If the network element device does not receive the service configuration parameters, or if the network element device receives the service configuration parameters but the verification of the service configuration parameters fails, it determines that the service configuration parameters have not been successfully received, and in this case, it may not send a response to the controller.

[0119] The above S604 to S606 describe the transmission process of service configuration parameters when the target service is an asynchronous service and the network element equipment is online.

[0120] In some embodiments, when the target service is an asynchronous service and the network element device fails, the transmission process of the service configuration parameters in this application embodiment is described in S607 and S608 as follows.

[0121] S607. When a network element device failure is detected, the service configuration parameters in the submitted queue are transferred to the pending submission queue.

[0122] S608. When a network element is detected to be back online, the service configuration parameters in the pending submission queue are sent to the network element.

[0123] In some embodiments, when the controller detects a network element failure, it stops sending service configuration parameters from the pending submission queue to the network element and simultaneously transfers the service configuration parameters from the submitted queue to the pending submission queue. This way, when the network element is detected to be back online, the controller sends the service configuration parameters from the pending submission queue to the network element.

[0124] In some embodiments, when the controller detects that a network element has come back online, in addition to sending the service configuration parameters in the pending and submitted queues to the network element, it also sends the service configuration parameters in the failure queue to the network element, thereby ensuring that the network element can obtain the required complete service configuration parameters after a fault restart.

[0125] In some embodiments, according to the retransmission mechanism, the service configuration parameters in the pending submission queue are sent to the network element device to avoid failure to send the service configuration parameters due to network or other reasons, thereby improving the reliability of the service configuration parameter transmission. Specifically, if the service configuration parameters in the pending submission queue are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are written to the submitted queue. If the service configuration parameters in the pending submission queue are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are written to the failure queue.

[0126] In this embodiment, if the controller determines that the service configuration parameters in the pending submission queue have been successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then the service configuration parameters are written into the submitted queue for archiving. If the controller determines that the service configuration parameters in the pending submission queue have not been successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then the service configuration parameters are written into the failure queue. Optionally, when the service configuration parameters fail to be sent, a failure message is sent. This failure message indicates that the service configuration parameters failed to be sent, allowing operation and maintenance personnel to verify the failed service configuration parameters.

[0127] S609. When the preset period arrives, save the service configuration parameters in the submitted queue to the configuration file of the network element device, and clear the service configuration parameters in the submitted queue.

[0128] In some embodiments, when a network element restarts, it loads the service configuration parameters in the configuration file and receives the service configuration parameters in the unsubmitted queue and the submitted queue, thereby ensuring the normal operation of each service and improving the working reliability of the network element.

[0129] In this embodiment, if the target service is asynchronous, the controller first writes the received service configuration information into the pending submission queue of the network element device. When the polling time of the pending submission queue arrives, it determines whether the current network element device is online. If the network element device is online, the controller directly sends the service configuration parameters in the pending submission queue to the network element device. After confirming successful transmission, the controller writes the service configuration parameters into the submitted queue of the network element device. If the controller determines that the network element device is offline, it writes the service configuration parameters in the submitted queue into the pending submission queue. When the network element device is detected to be back online, the controller sends the service configuration parameters in the pending submission queue to the network element device. This ensures that when the network element device is back online after a failure, the service configuration parameters missed during the failure period can be automatically synchronized, and the atomicity and order of the service configuration parameters are guaranteed. Out-of-order delivery of the service configuration parameters to the network element device will not cause failures. The entire process does not require manual intervention, improving the transmission efficiency and accuracy of the service configuration parameters.

[0130] It should be understood that Figures 2 to 6 This is merely an example of what is being done and should not be construed as limiting the scope of this application.

[0131] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application.

[0132] The above text combined Figures 2 to 6 The method embodiments of this application have been described in detail below, and the device embodiments of this application are described in detail below.

[0133] Figure 7 This is a schematic diagram of the structure of a data transmission device provided in an embodiment of this application. The device 10 includes: The receiving unit 11 is used to receive service configuration parameters sent by the service device, wherein the service configuration parameters are used to instruct the network element device to execute the target service; Processing unit 12 is used to write the received service configuration parameters into the queue corresponding to the network element device when a network element device fault is detected; The sending unit 13 is used to send the service configuration parameters in the queue to the network element device when the network element device is detected to be back online.

[0134] In some embodiments, the queue includes a queue to be submitted and a queue that has been submitted. The processing unit 12 is specifically used to write the received service configuration parameters into the queue to be submitted when a fault is detected in the network element device. The sending unit 13 is specifically used to send the service configuration parameters in the pending submission queue and the service configuration parameters in the submitted queue to the network element device when the network element device is detected to be back online. The submitted queue includes the service configuration parameters that the network element device was running before the current failure. The service configuration parameters in the pending submission queue are transferred to the submitted queue.

[0135] In some embodiments, the processing unit 12 is further configured to transfer the service configuration parameters in the submitted queue to the pending submission queue when a fault is detected in the network element device; The sending unit 13 is specifically used to send the service configuration parameters in the queue to the network element device when the network element device is detected to be back online.

[0136] In some embodiments, the queue further includes a failure queue, which includes service configuration parameters that were not successfully submitted to the network element device before the current failure. The sending unit 13 is also used to send the service configuration parameters in the failure queue to the network element device according to the retransmission mechanism when the network element device is detected to be back online.

[0137] In some embodiments, the sending unit 13 is further configured to: if the service configuration parameters in the failure queue are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then transfer the service configuration parameters in the failure queue to the submitted queue; if the service configuration parameters in the failure queue are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then report failure information, the failure information being used to indicate that the service configuration parameters in the failure queue failed to be sent.

[0138] In some embodiments, the sending unit 13 is further configured to send the received service configuration parameters to the network element device according to the retransmission mechanism if the target service is a synchronous service and the network element device is online.

[0139] In some embodiments, the sending unit 13 is further configured to: if the received service configuration parameters are successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then write the service configuration parameters into the submitted queue; if the received service configuration parameters are not successfully sent to the network element device within the retransmission count corresponding to the retransmission mechanism, then write the service configuration parameters into the failure queue.

[0140] In some embodiments, the processing unit 12 is further configured to write the received service configuration parameters into the queue to be submitted if the target service is an asynchronous service and the network element device is online; The sending unit 13 is also configured to send the service configuration parameters in the queue to the network element device according to the retransmission mechanism when the polling time of the queue to be submitted arrives.

[0141] In some embodiments, the processing unit 12 is further configured to: if the service configuration parameters in the queue to be submitted are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then transfer the service configuration parameters from the queue to be submitted to the submitted queue; if the service configuration parameters in the queue to be submitted are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then transfer the service configuration parameters from the queue to be submitted to the failure queue.

[0142] In some embodiments, the processing unit 12 is further configured to save the service configuration parameters in the submitted queue to the configuration file of the network element device when the preset period arrives, and clear the service configuration parameters in the submitted queue.

[0143] In some embodiments, the queue corresponding to the network element device is located in the cloud.

[0144] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 7 The apparatus 10 shown can perform the above-described method embodiments, and the foregoing and other operations and / or functions of each module in the apparatus 10 are for implementing the above-described method embodiments, which will not be described in detail here for the sake of brevity.

[0145] The apparatus of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0146] Figure 8 This is a schematic block diagram of an electronic device provided in an embodiment of this application. The electronic device may be the controller described above.

[0147] like Figure 8 As shown, the electronic device 40 may include: Memory 41 and memory 42 are provided. Memory 41 is used to store computer programs and to transfer the program code to memory 42. In other words, memory 42 can call and run computer programs from memory 41 to implement the methods in the embodiments of this application.

[0148] For example, the memory 42 can be used to execute the above-described method embodiments according to instructions in the computer program.

[0149] In some embodiments of this application, the memory 42 may include, but is not limited to: General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0150] In some embodiments of this application, the memory 41 includes, but is not limited to: Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0151] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 41 and executed by the memory 42 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the video production device.

[0152] like Figure 8 As shown, the electronic device 40 may further include: Transceiver 40, transceiver 43 can be connected to memory 42 or memory 41.

[0153] The memory 42 can control the transceiver 43 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 43 may include a transmitter and a receiver. The transceiver 43 may further include antennas, and the number of antennas can be one or more.

[0154] It should be understood that the various components in the video production equipment are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0155] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0156] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0157] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0158] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0159] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0160] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, characterized in that, include: Receive service configuration parameters sent by the service device, the service configuration parameters being used to instruct the network element device to execute the target service; When a network element device failure is detected, the received service configuration parameters are written into the pending submission queue in the queue corresponding to the network element device. When the network element device is detected to be back online, the service configuration parameters in the pending submission queue and the service configuration parameters in the submitted queue corresponding to the network element device are sent to the network element device. The submitted queue includes the service configuration parameters that the network element device was running before this failure. Transfer the business configuration parameters in the pending queue to the submitted queue.

2. The method according to claim 1, characterized in that, The method further includes: When a fault is detected in the network element device, the service configuration parameters in the submitted queue are transferred to the pending submission queue; The step of sending the service configuration parameters in the pending submission queue and the service configuration parameters in the submitted queue to the network element device when the network element device is detected to be back online includes: When the network element is detected to be back online, the service configuration parameters in the pending submission queue are sent to the network element.

3. The method according to claim 1 or 2, characterized in that, The queue also includes a failure queue, which includes service configuration parameters that were not successfully submitted to the network element device before this failure. The method further includes: When the network element is detected to be back online, the service configuration parameters in the failure queue are sent to the network element according to the retransmission mechanism.

4. The method according to claim 3, characterized in that, The method further includes: If the service configuration parameters in the failure queue are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then the service configuration parameters in the failure queue are transferred to the submitted queue. If the service configuration parameters in the failure queue are not successfully sent to the network element within the number of retransmissions corresponding to the retransmission mechanism, a failure message is reported. The failure message is used to indicate that the service configuration parameters in the failure queue failed to be sent.

5. The method according to claim 3, characterized in that, The method further includes: If the target service is a synchronous service and the network element device is online, the received service configuration parameters will be sent to the network element device according to the retransmission mechanism.

6. The method according to claim 5, characterized in that, The method further includes: If the received service configuration parameters are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then the service configuration parameters are written into the submitted queue. If the received service configuration parameters are not successfully sent to the network element within the number of retransmissions corresponding to the retransmission mechanism, the service configuration parameters are written into the failure queue.

7. The method according to claim 3, characterized in that, The method further includes: If the target service is an asynchronous service and the network element device is online, the received service configuration parameters are written into the pending submission queue according to the retransmission mechanism. When the polling time of the queue to be submitted arrives, the service configuration parameters in the queue to be submitted are sent to the network element device.

8. The method according to claim 7, characterized in that, The method further includes: If the service configuration parameters in the pending submission queue are successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then the service configuration parameters are transferred from the pending submission queue to the submitted queue. If the service configuration parameters in the pending submission queue are not successfully sent to the network element device within the number of retransmissions corresponding to the retransmission mechanism, then the service configuration parameters are transferred from the pending submission queue to the failure queue.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: When the preset period arrives, the service configuration parameters in the submitted queue are saved to the configuration file of the network element device, and the service configuration parameters in the submitted queue are cleared.

10. A data transmission device, characterized in that, include: The receiving unit is used to receive service configuration parameters sent by the service equipment, the service configuration parameters being used to instruct the network element equipment to execute the target service; The processing unit is used to write the received service configuration parameters into the pending submission queue in the queue corresponding to the network element device when a network element device fault is detected. The sending unit is configured to, when the network element device is detected to be back online, send the service configuration parameters in the pending submission queue and the service configuration parameters in the submitted queue corresponding to the network element device to the network element device, wherein the submitted queue includes the service configuration parameters that the network element device was running before the current failure; and transfer the service configuration parameters in the pending submission queue to the submitted queue.

11. An electronic device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the method of any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method according to any one of claims 1 to 9.

Images