WO2023046088A1 - 一种应用于音视频数据传输的端到端系统解决方法 - Google Patents
一种应用于音视频数据传输的端到端系统解决方法 Download PDFInfo
- Publication number
- WO2023046088A1 WO2023046088A1 PCT/CN2022/120953 CN2022120953W WO2023046088A1 WO 2023046088 A1 WO2023046088 A1 WO 2023046088A1 CN 2022120953 W CN2022120953 W CN 2022120953W WO 2023046088 A1 WO2023046088 A1 WO 2023046088A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- transmission
- client
- registration
- audio
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 183
- 238000000034 method Methods 0.000 title claims abstract description 16
- 238000012545 processing Methods 0.000 claims abstract description 14
- 238000013461 design Methods 0.000 claims abstract description 7
- 238000012546 transfer Methods 0.000 claims description 30
- 230000004044 response Effects 0.000 claims description 26
- 238000012360 testing method Methods 0.000 claims description 12
- 230000035515 penetration Effects 0.000 claims description 8
- 230000008569 process Effects 0.000 claims description 7
- 230000007423 decrease Effects 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 64
- 238000010586 diagram Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 108700023290 Stanford University protocol Proteins 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005728 strengthening Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
Definitions
- the invention relates to the technical field of communication, in particular to an end-to-end system solution applied to audio and video data transmission.
- RTP technology is widely used in professional video security products. Since professional security products are usually deployed in private networks, the relatively complex WAN private network has relatively less interference, and has become a standard transmission protocol in the professional security field; RTMP protocol is mostly used for WAN video In website on-demand, the standard protocol for FLASH plug-in video playback (currently FLASH has been eliminated); the HTTP protocol is very old, but driven by the demand for network audio and video, a large amount of video data is transmitted through the HTTP protocol in the form of files, and through continuous strengthening of the server The performance and bandwidth to achieve the desired effect; WEBRTC is currently the most popular video transmission protocol, characterized by point-to-point, real-time audio and video streaming.
- Security products are mainly used in the professional security field. RTP and other technologies are consistently used and are completely different from mainstream video websites.
- RTP and other technologies are consistently used and are completely different from mainstream video websites.
- the current mainstream solution is to use cloud servers for data storage and forwarding, which satisfies the current customer experience, but as products continue to be introduced to the market, the high cost of video data forwarding has become the main difficulty, and most security video products are designed in It is used within a private local area network, and users expect to see video from any location.
- the product needs to be able to transmit data in a wide area network environment. Need to penetrate the network between the user and the device for data transmission.
- the purpose of the present invention is to overcome the deficiencies of the prior art, an end-to-end system solution applied to audio and video data transmission, through the self-designed software service framework, thereby reducing the number of servers in the same environment, reducing server hardware requirements, thereby Reduce operating costs, improve the fault tolerance of the entire software system, reduce the impact of downtime and network abnormalities on the system, and reduce the total data transmission volume of the entire system through the new message transmission mode, thereby reducing data transmission costs.
- the present invention provides an end-to-end system solution applied to audio and video data transmission.
- the end-to-end system includes a client, a device, and a server.
- the server includes a management server, a registration server, and a transmission server. The steps are:
- S1 The management server adds the transmission server
- S2 The management server adds the device side
- S1 comprises the steps of:
- the management service submits an application for creating a server through the cloud service operator;
- S104 the cloud service operator completes the creation and startup of the new server
- the management server updates the transmission service information to all registration servers.
- S2 comprises the steps of:
- S202 The management server saves the added device to the database
- S203 The management server updates the device information to all registration servers.
- S3 includes the steps of:
- the device starts, sends a registration information query message to the registration server, and obtains a list of transmission servers corresponding to the device;
- the device After obtaining the transmission server list, the device sends a registration request to the transmission server, and completes the registration after receiving a registration response message from the transmission server;
- the device After the device registers with the transfer server, it sends a heartbeat message to the transfer server.
- the heartbeat response message sent by the transfer server contains the load information of the transfer server. If the device receives 3 times of server overload information, it needs to send it to the registration server again. Register query message, if the transfer server list changes, re-execute the initialization process.
- S4 comprises the following steps:
- S401 The client requests the registration server to query the transmission server information associated with the device;
- the registration server returns the transmission server information of the designated device
- S405 The transmission server forwards the query request of the client to the device;
- S409 The device receives the connection request from the client, sends a connection request response message, the client receives the connection request response message, and the connection is established;
- the forwarding server receives the forwarding connection request, establishes a forwarding channel, and sends the forwarding connection request to the device;
- S412 The device side receives the forwarding connection request from the forwarding server, and sends a response message
- S413 The client receives the forwarding response message from the forwarding server, and the connection establishment is completed.
- S5 comprises the steps of:
- S503 the management server transfers the devices under the high-load transfer server to a new low-load transfer server, and updates the modified device information list to the registration server;
- the device side After receiving the high-load message from the transfer server multiple times, the device side re-requests the device information list from the registration server to obtain a new transfer server;
- S55 The device side migrates to a new low-load transmission server.
- S6 is: when the forwarding link established by the transmission server for a client and the device stops, the resources of the transmission server are released, and when the resources reach the low load threshold, the transmission server is a low-load server and reports The status message sent, the management server will transfer some devices to the low-load server;
- the management server adopts a standard website architecture design, which is divided into a front end, a back end, and a database.
- the front end provides a user configuration management interface
- the back end completes configuration message processing and interacts with other servers for data processing
- the database is used to store device information.
- the registration server provides the client and the device to query the associated information of the transmission server of the corresponding device.
- the registration server is divided into a high-concurrency query service and an update service.
- the high-concurrency query service provides query function support for the client and the device side; the update service uses the http protocol to interact with the management server to obtain a list of devices and a list of transmission servers .
- the transmission server is dynamically adjusted according to the number of devices.
- the management server dynamically increases or decreases the transmission server through the server operator interface.
- the transmission server is divided into network penetration, forwarding service and update service, and the update service has the same function as the registration server, providing information interaction with the management server.
- the client provides external program calls in the form of a runtime library, and completes the establishment and transmission of audio and video connections through the client interface API.
- the device side provides external program calls in the form of a runtime library, and completes the establishment and transmission of audio and video connections through the device-side interface API.
- the present invention through the unique architecture design of the client, server and device, the user only needs to call the API interface provided by the client and the device to realize real-time audio and video data transmission, and the management server can quickly Configure and manage related equipment.
- the system can adjust the increase or decrease of servers according to the load to meet the current business needs. It has the following technical effects:
- This solution reduces data transmission costs, and compared with existing solutions, it can effectively reduce server downtime or network failures.
- the failure caused by the problem has higher reliability.
- the cost of idle servers can be reduced, and the comprehensive system management of equipment can be carried out to reduce maintenance costs.
- FIG. 1 is a schematic diagram of the overall architecture of the present invention.
- FIG. 2 is a schematic diagram of the registration server architecture of the present invention.
- FIG. 3 is a schematic diagram of the architecture of the transmission server of the present invention.
- Fig. 4 is a schematic diagram of the client interface of the present invention.
- FIG. 5 is a schematic diagram of the device-side interface of the present invention.
- Fig. 6 is a schematic diagram of adding a transfer server to the management server of the present invention.
- Fig. 7 is a schematic diagram of adding equipment to the management server of the present invention.
- FIG. 8 is a schematic diagram of device startup and initialization in the present invention.
- FIG. 9 is a first schematic diagram of a client startup and connection device according to the present invention.
- FIG. 10 is a second schematic diagram of the client startup and connection device of the present invention.
- Fig. 11 is a schematic diagram of overload processing of the transmission server in the present invention.
- the present invention provides an end-to-end system solution applied to audio and video data transmission.
- the end-to-end system solution refers to a method for solving audio and video data transmission from a client to a device.
- the end-to-end system includes a client, a device and a server, and the server includes a management server, a registration server and a transmission server. The steps are as follows:
- S1 The management server adds the transmission server
- S1 includes the following steps:
- S101 The user adds the transmission server through the management server configuration page, and the management server forms configuration information.
- the management server When it is set to be automatically added, the management server will be triggered by a message to automatically complete the entire logic, that is, steps S101 to S106;
- S103 the management service submits an application for creating a server through the API interface provided by the cloud service operator;
- S104 The cloud service operator finishes creating and starting a new server, specifically, the new server is a newly established transmission server;
- the management server forms transmission service information based on the registration request, the management server updates the transmission service information to all registration servers, and the transmission service information is used to represent the connection relationship between the transmission server and the registration server;
- S2 includes the following steps:
- S201 The user adds (modifies/deletes) the device through the management server configuration page;
- S202 The management server saves the added (modified/deleted) device to the database to form device information
- S203 The management server updates the device information to all registration servers
- S301 start the device, firstly send a registration information query message to the registration server to obtain a list of transfer servers corresponding to the device, the transfer server list is used to represent the list of transfer servers that the device can connect to when the device starts;
- the device After obtaining the transmission server list, the device sends a registration request to the transmission server in the transmission server list, and completes the registration after receiving the transmission server registration response message;
- the device After the device registers with the transmission server, it needs to send a heartbeat message to the transmission server at regular intervals of 15 seconds. After the transmission server receives the heartbeat information from the device, the heartbeat response message sent by the transmission server to the device contains the load information of the transmission server and the load of the transmission server. The information is used to indicate whether the transmission server is overloaded. If the device receives 3 consecutive server overload messages, it needs to resend the registration query message to the registration server. If the transmission server list changes, the initialization process is re-executed. The initialization process is from step S302 to step S303;
- S4 includes the following steps:
- S401 The client requests the registration server to query the transmission server information associated with the device;
- the registration server returns the transmission server information of the specified device, and the designated device is the client. In the request sent to the registration server, specify the device to be queried;
- S405 The transmission server corresponding to the specified device forwards the query request of the client to the device;
- S409 The designated device receives the connection request from the client, sends a connection request response message, the client receives the connection request response message, and the connection is established;
- the client If the client does not receive the test message from the device after a timeout, the client initiates a forwarding connection request to the forwarding server, specifically, the forwarding server is a transmission server corresponding to the designated device;
- the forwarding server receives the forwarding connection request, establishes a forwarding channel, and sends the forwarding connection request to the designated device;
- S412 The designated device receives the forwarding connection request from the forwarding server, and sends a response message to the forwarding server;
- the forwarding server forwards the response message of the designated device to the client, the client receives the response message forwarded by the forwarding server, and the connection is established;
- S5 is the transmission server that provides penetration connection assistance for the client and the device.
- the transmission server provides data forwarding services, including The following steps:
- the transmission server When a transmission server forwards a large amount of data or loads more devices, the transmission server sends an overload message to the management server; the load device of the transmission server refers to the device connected to the transmission server and transmits data through the transmission server.
- the transmission server When a transmission server forwards a large amount of data or loads a large number of devices, the transmission server is a high-load transmission server.
- the amount of data forwarded by the transmission server or the number of loaded devices specifically means that the amount of data forwarded by the transmission server is greater than or equal to a preset data volume threshold or the number of load devices of the transmission server is greater than or equal to a preset load number threshold.
- the low-load transmission server specifically refers to a transmission server whose amount of forwarded data is less than a preset data volume threshold and whose number of load devices is less than a preset load number threshold.
- the management server transfers some devices under the high-load transfer server to a new low-load transfer server, and updates the modified device information list to the registration server; specifically, the device information list is used to map between the device end and the transfer server connection relationship.
- the device After receiving the high-load message from the transmission server multiple times in succession, the device re-requests the device information list from the registration server to obtain a new transmission server. The number of high-load messages received by the device is greater than the preset threshold;
- S505 The device side migrates to a new low-load transmission server
- S6 is: when the forwarding link established by the transmission server for a client and the device stops, the transmission resources of the transmission server are released, and when the transmission resources of the transmission server reach the low load threshold, the transmission of the transmission server sends a status message to the management server , after receiving the status message, the management server will transfer some devices to the low-load server, specifically, the transferred devices may be random devices;
- the present invention has extremely high scalability, and can run all the servers on a PC hardware platform when the service is provided to the minimum.
- the hardware upgrade function provided by cloud service operators such as Amazon and Facebook can upgrade the system very quickly and smoothly.
- the management server adopts a standard website architecture design, which is divided into front-end, back-end, and database.
- the front-end provides a user configuration management interface
- the back-end completes configuration message processing, interacts with other servers (such as transmission servers and registration servers) for data processing, and the database is used for storage.
- the management server runs on the host of the cloud server operator as an independent program, the data is stored using the mysql database, and the management server provides user configuration management in the standard http manner.
- the registration server provides the client and the device side to query the associated information of the transmission server of the corresponding device.
- the associated information has a huge amount of concurrency and the string is short.
- the registration server runs on the host of the cloud server operator as an independent program.
- the registration server does not have a database, and the server starts Finally, all data is obtained from the management server after the server is started, and the server is provided after the data is obtained from the management server.
- the registration server is divided into high-concurrency query service and update service.
- the high-concurrency query service provides query function support for the client and the device side. This service is characterized by high concurrency and the data of each message is short (84 bytes); the update service uses http
- the protocol interacts with the management server to obtain a list of devices and a list of transport servers. Compared with mainstream http servers, the design of high-concurrency query service requires tcp three-way handshake for each transmission, and the actual data will increase the http protocol header information.
- the multi-registration server and the management server operate relatively independently, which improves the fault tolerance of the entire system. Unless all the registration servers are down, the system can still guarantee the normal operation of the system. Compared with the traditional fault-tolerant solution using a backup server, first, the multi-registration Local deployment can effectively reduce connection delays in different regions. Secondly, all registration servers are mutual backups, and traditional backup servers need to pay for them even if they are not working. All registration servers in this system are distributed in different regions, which also reduces regional differences. The probability that the system cannot function normally due to network failure.
- the registration server can request the device information list from the management server, report the status information to the management server, and the reported information status includes registration server load, number of requests per second, CPU/memory usage and other information, and receive the device information list update request from the management server (system After the administrator performs operations such as adding/deleting/modifying on the management server, the management server sends updated device information to the registration server), receives client device query requests and receives device-side device query requests.
- only one unit can be configured for domestic use, and two units can be configured for use in Asia. If business load is required globally, one unit can be configured for Asia, Europe, Africa, and North and South America, depending on the central node of the global backbone network. , more registration servers allow for faster response from nearby devices.
- the transmission server is dynamically adjusted according to the number of equipment terminals in various places, and the number is not limited.
- the management server When the load of the transmission server in a certain area is too large, the management server will dynamically increase the operation of the transmission server through the server operator interface; or when the server is too idle , the management server dynamically reduces the operation of the transmission server through the server operator interface; the present invention saves the detection of the network type on the client side and the device side, and is different from the STUN protocol.
- the terminal and the device side try to establish the penetration and forwarding channels at the same time. That is, when the penetration is successful, the forwarding process is stopped. If the penetration fails, the forwarding channel is used.
- the management service When a transmission server undertakes more forwarding services
- the management service When the load is high, the management service will execute the transmission server overload processing process.
- the management server When the forwarding business on more transmission servers stops, the management server will execute the transmission server overload recovery process.
- the transmission server is divided into network penetration, forwarding service and update service.
- the function of the update service is the same as that of the registration server, providing information interaction with the management server.
- the scale of equipment is 10: the management server, registration server, and transmission server are deployed on Facebook Cloud 1-core 1G cloud server at the same time.
- the management server the registration server are deployed on a 1-core 1G cloud server, and the transmission server is deployed on a 1-core 1G cloud server.
- the management server and registration server are deployed on multi-core large memory servers, the registration servers are distributed in major network nodes around the world, and the transmission servers are dynamically deployed in various places according to the actual situation.
- the client provides external program calls in the form of a runtime library, and quickly completes the establishment and transmission of audio and video connections with the device through the existing client interface API.
- the device side provides external program calls in the form of a runtime library, and quickly completes the establishment and transmission of audio and video connections with the device side through the existing device-side interface API.
- the device-side program theme calls the device-side API Interface list enables fast end-to-end connections.
- the present invention reduces the number of servers deployed as a whole, greatly reduces service operation costs, and reduces data transmission costs. Compared with existing solutions, it effectively reduces failures caused by server downtime or network problems, and has higher reliability. Actively adjust the number of servers, reduce the cost of idle servers, and perform comprehensive system management on equipment to reduce maintenance costs.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
本申请涉及通信技术领域，具体地说是一种应用于音视频数据传输的端到端系统解决方法，包括客户端，设备端，和服务端，服务端包括管理服务器，注册服务器和传输服务器以及对应的处理步骤，本申请同现有技术相比，通过独特的客户端、服务端和设备端的架构设计，有效降低因服务器宕机或网络问题导致的故障，有更高的可靠性，通过对系统负载主动调整服务器数量，降低闲置服务器成本，可对设备进行综合系统管理，减少维护成本。
Description
本发明涉及通信技术领域，具体地说是一种应用于音视频数据传输的端到端系统解决方法。
现有RTP，RTMP，WEBRTC，HTTP等为目前使用较为广泛的音视频传输技术，音视频传输技术的被专业安防视频领域和网络视频业务的兴起所推动，在各自的领域内有不同程度的发展，相对专业安防领域，网络视频业务的发展更快。
RTP技术被普遍使用在专业视频安防产品中，由于专业安防产品通常被部署在专用网络中，相对复杂的广域网专用网络相对干扰较少，成为专业安防领域内标准传输协议；RTMP协议多用于广域网视频网站点播中，FLASH插件视频播放的标准协议(目前FLASH已被淘汰)；HTTP协议已经非常陈旧，但网络音视频需求推动下，大量的视频数据采用文件方式通过HTTP协议进行传输，通过不断加强服务器的性能和带宽达到理想的效果；WEBRTC是目前最热门的视频传输协议，特点是点对点，实时音视频流传输。
安防类产品主要应用于专业安防领域，一贯使用RTP等技术并与主流视频网站完全是两种技术路线，由于安防类产品逐渐进入个人消费类市场，一些面向消费类安防产品面临各种不兼容问题，目前主流方案为使用云服务器进行数据的存储和转发，其满足当前客户的使用体验，但随着产品不断推向市场，高昂的视频数据转发费用成为了最主要困难，安防视频产品多设计在一个专用局域网内使用，而用户期望在任何位置都能看到视频。首先需要产品能够在广域网环境下传输数据。需要穿透用户和设备之间的网络进行数据传输。通过增设服务器可解决网络数据传输问题，但同时带来巨大的成本压力，安防视频产品每时每刻生产大量的数据，全部通过服务器转发，导致运营成本剧增，通过存储成文件方式进行数据发送又会产生大量的延时。
因此，需要设计一种应用于音视频数据传输的端到端系统解决方法,通过自主设计的软件服务构架,从而减少同等环境下服务器数量,降低服务器硬件要求,从而降低运营成本,提高整个软件系统的容错性，降低宕机，网络异常对系统的影响，通过新的消息传输模式降低整个系统总数据传输量，从而降低数据传输成本。
发明内容
本发明的目的是克服现有技术的不足，一种应用于音视频数据传输的端到端系统解决方法，通过自主设计的软件服务构架,从而减少同等环境下服务器数量,降低服务器硬件要求,从而降低运营成本,提高整个软件系统的容错性，降低宕机，网络异常对系统的影响，通过新的消息传输模式降低整个系统总数据传输量，从而降低数据传输成本。
为了达到上述目的，本发明提供一种应用于音视频数据传输的端到端系统解决方法，端到端系统包括客户端，设备端和服务端，服务端包括管理服务器，注册服务器和传输服务器，其步骤在于：
S1：管理服务器添加传输服务器；
S2：管理服务器添加设备端；
S3：设备端启动和初始化；
S4：客户端启动和连接设备端；
S5：传输服务器过载处理；
S6：传输服务器过载恢复。
在一些实施方案中，S1包括以下步骤：
S101：用户通过管理服务器配置页面添加传输服务器；
S102：管理服务器将配置信息保存到数据库；
S103：管理服务通过云服务运营商提交创建服务器申请；
S104：云服务运营商完成新服务器的创建和启动；
S105：新服务器启动后向管理服务器发送注册请求；
S106：管理服务器将传输服务信息更新到所有注册服务器。
在一些实施方案中，S2包括以下步骤：
S201：用户通过管理服务器配置页面添加设备端；
S202：管理服务器将添加的设备端保存到数据库；
S203：管理服务器将设备信息更新到所有注册服务器。
在一些实施方案中，S3包括以下步骤：
S301：设备端启动，向注册服务器发送注册信息查询消息，获取设备端对应的传输服务器列表；
S302：设备端获取传输服务器列表后，向传输服务器发送注册请求，收到传输服务器注册应答消息后，完成注册；
S303：设备端完成向传输服务器注册后，向传输服务器发送心跳消息，传输服务器发送的心跳应答消息中包含传输服务器负载信息，若设备端收到3次服务器过载信息时，需重新向注册服务器发送注册查询消息，若传输服务器列表变更，则重新执行初始化流程。
在一些实施方案中，S4包括以下步骤：
S401：客户端向注册服务器请求查询设备端关联的传输服务器信息；
S402：注册服务器返回指定设备的传输服务器信息；
S403：客户端向传输服务器发送查询请求；
S404：传输服务器向客户端发送查询应答；
S405：传输服务器向设备端转发客户端的查询请求；
S406：客户端收到传输服务器的应答后，向设备端发送试探消息；
S407：设备端收到传输服务器转发的查询请求后，向客户端发送试探消息；
S408：若客户端收到设备端的试探消息，客户端发起连接请求；
S409：设备端收到客户端连接请求，发送连接请求应答消息，客户端收到连接请求的应答消息，连接建立完成；
S410：若客户端超时未收到设备端的试探消息，客户端向转发服务器发起转发连接请求；
S411：转发服务器收到转发连接请求，建立转发通道，向设备端发送转发连接请求；
S412：设备端收到转发服务器的转发连接请求，发送应答消息；
S413：客户端收到转发服务器的转发应答消息，连接建立完成。
在一些实施方案中，S5包括以下步骤：
S501：当一个传输服务器转发数据量或负载设备较多时，传输服务器向管理服务器发送过载消息；
S502：当一个传输服务器转发数据量或负载设备较多时，传输服务器向所有连接的设备发送负载过高消息；
S503：管理服务器将高负载传输服务器下的设备转移到新的低负载传输服务器，向注册服务器更新修改后的设备信息列表；
S504：设备端多次收到传输服务器的高负载消息后，向注册服务器重新请求设备信息列表以获取新的传输服务器；
S55：设备端向新低负载传输服务器迁移。
在一些实施方案中，S6为：当传输服务器为某客户端和设备端建立的转发链接停止时，传输服务器资源得到释放，当资源到达低负载阈值时，传输服务器为低负载服务器并向管理服务器发送的状态消息，管理服务器将转移部分设备到低负载服务器；
在一些实施方案中，管理服务器采用标准网站构架设计，分为前端，后端，数据库，前端提供用户配置管理界面，后端完成配置消息处理以及与其他服务器交互数据处理，数据库用于存储设备信息。
在一些实施方案中，注册服务器提供客户端和设备端查询对应设备的传输服务器关联信息。
在一些实施方案中，注册服务器分为高并发查询服务和更新服务，高并发查询服务为客户端和设备端提供查询功能支持；更新服务使用http协议与管理服务器交互，获取设备列表和传输服务器列表。
在一些实施方案中，传输服务器根据设备端数量进行动态调整，当传输服务器负载过大或服务器闲置过多时，管理服务器通过服务器运营商接口进行动态增减传输服务器操作。
在一些实施方案中，传输服务器分为网络穿透，转发服务和更新服务，更新服务功能与注册服务器相同，提供与管理服务器的信息交互。
在一些实施方案中，客户端以运行库方式提供外部程序调用，通过客户端接口API完成音视频连接的建立传输。
在一些实施方案中，设备端以运行库方式提供外部程序调用，通过设备端接口API完成音视频连接的建立传输。
本发明同现有技术相比，通过独特的客户端、服务端和设备端的架构设计，用户仅需调用客户端和设备端提供的API接口即可实现实时音视频数据传输，通过管理服务器可快速配置和管理相关设备，通过配置，系统可根据负载自行调整增减服务器以适应当前业务需求，具备以下的技术效果：该方案降低数据传输成本，相比现有方案有效降低因服务器宕机或网络问题导致的故障，有更高的可靠性，通过对系统负载主动调整服务器数量，降低闲置服务器成本，可对设备进行综合系统管理，减少维护成本。
图1为本发明的整体架构示意图。
图2为本发明的注册服务器架构示意图。
图3为本发明的传输服务器架构示意图。
图4为本发明的客户端接口示意图。
图5为本发明的设备端接口示意图。
图6为本发明的管理服务器添加传输服务器示意图。
图7为本发明的管理服务器添加设备示意图。
图8为本发明的设备端启动和初始化示意图。
图9为本发明的客户端启动和连接设备示意图一。
图10为本发明的客户端启动和连接设备示意图二。
图11为本发明的传输服务器过载处理示意图。
现结合附图对本发明做进一步描述。
参见图1-2，本发明提供一种应用于音视频数据传输的端到端系统解决方法，该端到端系统解决方法指的是用于解决客户端至设备端的音视频数据传输的方法，端到端系统包括客户端，设备端和服务端，服务端包括管理服务器，注册服务器和传输服务器，其步骤在于：
S1：管理服务器添加传输服务器；
S2：管理服务器添加设备；
S3：设备端启动和初始化；
S4：客户端启动和连接设备；
S5：传输服务器过载处理；
S6：传输服务器过载恢复；
S1包括以下步骤：
S101：用户通过管理服务器配置页面添加传输服务器，管理服务器形成配置信息当被设置成自动添加时，管理服务器将由消息触发，自动完成整个逻辑，即步骤S101至步骤S106，；
S102：管理服务器将配置信息保存到数据库；
S103：管理服务通过云服务运营商提供的API接口提交创建服务器申请；
S104：云服务运营商完成新服务器的创建和启动，具体地，新服务器为新建立的传输服务器；
S105：新服务器启动后向管理服务器发送注册请求；
S106：管理服务器基于所述注册请求形成传输服务信息，管理服务器将传输服务信息更新到所有注册服务器，传输服务信息用于表征传输服务器与注册服务器之间的连接关系；
如图6-7所示，S2包括以下步骤：
S201：用户通过管理服务器配置页面添加(修改/删除)设备端；
S202：管理服务器将添加(修改/删除)的设备端保存到数据库，形成设备信息；
S203：管理服务器将设备信息更新到所有注册服务器；
S3包括以下步骤：
S301：设备端启动，首先向注册服务器发送注册信息查询消息，获取设备端对应的传输服务器列表，传输服务器列表用于表征设备端启动时，可供设备端进行连接的传输服务器的列表；
S302：设备端获取传输服务器列表后，向传输服务器列表中的传输服务器发送注册请求，收到传输服务器注册应答消息后，完成注册；
S303：设备端完成向传输服务器注册后，需定时15s向传输服务器发送心跳消息，传输服务器接收设备端的心跳信息后，传输服务器向设备端发送的心跳应答消息中包含传输服务器负载信息，传输服务器负载信息用于表征传输服务器是否过载，若设备端连续收到3次服务器过载信息，需重新向注册服务器发送注册查询消息，若传输服务器列表变更，则重新执行初始化流程，初始化流程即步骤S302至步骤S303；
如图9-10所示，S4包括以下步骤：
S401：客户端向注册服务器请求查询设备端关联的传输服务器信息；
S402：注册服务器返回指定设备端的传输服务器信息，指定设备端为客户端在向注册服务器发出的请求中，指定要进行查询的设备端；
S403：客户端向与指定设备端对应的传输服务器发送查询请求；
S404：与指定设备端对应的传输服务器向客户端发送查询应答；
S405：与指定设备端对应的传输服务器向设备端转发客户端的查询请求；
S406：客户端收到与指定设备端对应的传输服务器的应答后，向指定设备端发送试探消息；
S407：指定设备端收到传输服务器转发的查询请求后，向客户端发送试探消息；
S408：若客户端收到设备端的试探消息，表明两者可建立直接连接，客户端向指定设备端发起连接请求；
S409：指定设备端收到客户端连接请求，发送连接请求应答消息，客户端收到连接请求的应答消息，连接建立完成；
S410：若客户端超时未收到设备端的试探消息，客户端向转发服务器发起转发连接请求，具体地，转发服务器为与指定设备端对应的传输服务器；
S411：转发服务器收到转发连接请求，建立转发通道，向指定设备端发送转发连接请求；
S412：指定设备端收到转发服务器的转发连接请求，向转发服务器发送应答消息；
S413：转发服务器向客户端转发指定设备端的应答消息，客户端收到转发服务器转发的应答消息，连接建立完成；
如图5-6、图11所示，S5为传输服务器为客户端和设备端提供穿透连接协助，当客户端和设备端的网络限制导致无法成功穿透时，传输服务器提供数据转发服务，包括以下步骤：
S501：当一个传输服务器转发数据量或负载设备较多时，传输服务器向管理服务器发送过载消息；传输服务器的负载设备指与该传输服务器连接并通过该传输服务器进行数据传输的设备端。当一个传输服务器转发数据量或负载设备较多时，该传输服务器为高负载传输服务器。传输服务器转发数据量或负载设备较多具体指传输服务器转发数据量大于等于预设的数据量阈值或传输服务器的负载设备数量大于等于预设的负载数量阈值。低负载传输服务器具体指转发数据量小于预设数据量阈值且负载设备数量小于预设负载数量阈值的传输服务器。
S502：当一个传输服务器转发数据量或负载设备较多时，传输服务器向所有连接的设备端(除已建立转发的设备端)发送负载过高消息；
S503：管理服务器将高负载传输服务器下的部分设备端转移到新的低负载传输服务器，向注册服务器更新修改后的设备信息列表；具体地，设备信息列表用于映射设备端与传输服务器之间的连接关系。
S504：设备端连续多次收到传输服务器的高负载消息后，向注册服务器重新请求设备信息列表以获取新的传输服务器，具体地，设备端连续多次收到传输服务器的高负载消息具体指设备端收到高负载消息的次数大于预设次数阈值；
S505：设备端向新低负载传输服务器迁移；
S6为：当传输服务器为某客户端和设备端建立的转发链接停止时，传输服务器的传输资源得到释放，当传输服务器的传输资源到达低负载阈值时，传输服务器的传输向管理服务器发送状态消息，管理服务器接收状态消息后将转移部分设备端到此低负载服务器，具体地，转移的部分设备端可为随机的设备端；
本发明具有极高可扩展性，最小化服务提供时可在一个PC硬件平台上运行所有的服务器，当设备端逐步增加时，逐渐将注册服务器，传输服务器依次部署到独立PC硬件平台，结合当前亚马逊，阿里等云服务运营商提供的硬件升级功能，可以非常快速平滑升级系统。
管理服务器采用标准网站构架设计，分为前端，后端，数据库，前端提供用户配置管理界面，后端完成配置消息处理，与其他服务器(如传输服务器及注册服务器)交互数据处理，数据库用于存储设备信息，如设备端的信息，管理服务器以独立程序方式运行在云服务器运行商的主机上，数据存储使用mysql数据库，管理服务器以标准http方式提供用户配置管理。
注册服务器提供客户端和设备端查询对应设备的传输服务器关联信息，关联信息并发量巨大且字符串短小，注册服务器以独立程序方式运行在云服务器运行商的主机上，注册服务器没有数据库，服务器启动后所有数据均从服务器启动后从管理服务器获取，从管理服务器获取数据后开始提供服务器。
注册服务器分为高并发查询服务和更新服务，高并发查询服务为客户端和设备端提供查询功能支持，该服务特性为高并发且每个消息的数据短小(84字节)；更新服务使用http协议与管理服务器交互，获取设备列表和传输服务器列表。高并发查询服务的设计相比主流http服务器，每次传输需要进行tcp三次握手，实际数据会增加http协议头信息，对于每个请求服务需要分配独立的内存用于处理tcp数据，再连接结束之间都会占用内存，所以采用http服务方式应对高并发请求需要建立集群服务器处理，而本方案使用udp方式，服务端无需为每个连接分配独立内存，udp数据传输无需握手，总体数据传输减少50％以上，对服务器硬件性能要求降低50％以上。
多注册服务器与管理服务器相对独立运行，提升了整个系统的容错性，除非所有注册服务器全部宕机否则系统依然能够保证系统正常运行，相对传统使用备份服务器的容错方案，首先多注册服务器分别在多地部署可有效降低对不同区域连接延时，其次所有注册服务器互为备份，且传统备份服务器即使不在工作状态也需要为其支付费用，本系统中所有注册服务器分布在不同地区，也降低地区性网络瘫痪导致系统不能正常运行的概率。
注册服务器可实现向管理服务器请求设备信息列表，向管理服务器上报状态信息，上报信息状态包含注册服务器负载，每秒请求数量，CPU/内存占用率等信息，接收管理服务器设备信息列表更新请求(系统管理员在管理服务器上进行添加/删除/修改等操作后，管理服务器将更新的设备信息发送到注册服务器)，接收客户端设备查询请求以及接收设备端设备查询请求。
例如仅在国内使用可配置1台，若在亚洲区域使用配置2台，若需要业务负载全球可根据地理情况为亚洲，欧洲，非洲，南北美洲各配置1台，视全球骨干网络中心节点而定，更多的注册服务器可让就近的设备获得更快速的响应。
如图3所示，传输服务器根据各地设备端数量进行动态调整，数量不限，当某地区传输服务器负载过大时，管理服务器通过服务器运营商接口进行动态增加传输服务器操作；或服务器闲置过多时，管理服务器通过服务器运营商接口进行动态减少传输服务器操作；本发明省去了客户端和设备端对网络类型的检测，同时与STUN协议不同，本发明将转发和穿透流程同时进行，即客户端和设备端在连接过程中同时进行尝试下穿透和转发通道的建立，即穿透成功时，停止转发流程，若穿透失败，则使用转发通道，当一个传输服务器承担较多的转发业务时，其负载较高，管理服务将执行传输服务器过载处理流程，当较多的传输服务器上的转发业务停止时，管理服务器将执行传输服务器过载恢复流程。
传输服务器分为网络穿透，转发服务和更新服务，更新服务功能与注册服务器相同，提供与管理服务器的信息交互。
例如，设备规模10个：管理服务器，注册服务器，传输服务器同时部署在阿里云1核1G云服务器上。
例如，设备规模100个：管理服务器，注册服务器部署在1台1核1G云服务，传输服务器部署在1台1核1G云服务器。
例如，设备规模超百万级别后：管理服务器和注册服务器部署在多核心大内存服务器，注册服务器分布于全球各大网络节点，传输服务器根据实际情况动态部署各地。
如图4所示，客户端以运行库方式提供外部程序调用，通过现有的客户端接口API快速完成与设备端的音视频连接的建立和传输。
如图5、图8所示，设备端以运行库方式提供外部程序调用，通过现有的设备端接口API快速完成与设备端的音视频连接的建立和传输，设备端程序主题通过调用设备端API接口列表可快速实现端对端连接。
以上仅是本发明的优选实施方式，只是用于帮助理解本申请的方法及其核心思想，本发明的保护范围并不仅局限于上述实施例，凡属于本发明思路下的技术方案均属于本发明的保护范围。应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理前提下的若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。
本发明从整体上降低服务器部署数量，大量降低服务运营成本，降低数据传输成本，相比现有方案有效降低因服务器宕机或网络问题导致的故障，有更高的可靠性，通过对系统负载主动调整服务器数量，降低闲置服务器成本，可对设备进行综合系统管理，减少维护成本。
Claims (14)
- 一种应用于音视频数据传输的端到端系统解决方法，其特征在于：端到端系统包括客户端，设备端，和服务端，所述服务端包括管理服务器，注册服务器和传输服务器，所述方法包括步骤：S1：管理服务器添加传输服务器；S2：管理服务器添加设备端；S3：设备端启动和初始化；S4：客户端启动和连接设备端；S5：传输服务器过载处理；S6：传输服务器过载恢复。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述S1包括步骤：S101：用户通过管理服务器配置页面添加传输服务器；S102：管理服务器将配置信息保存到数据库；S103：管理服务通过云服务运营商提交创建服务器申请；S104：云服务运营商完成新服务器的创建和启动；S105：新服务器启动后向管理服务器发送注册请求；S106：管理服务器将传输服务信息更新到所有注册服务器。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述S2包括步骤：S201：用户通过管理服务器配置页面添加设备端；S202：管理服务器将添加的设备端保存到数据库；S203：管理服务器将设备信息更新到所有注册服务器。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述S3包括步骤：S301：设备端启动，向注册服务器发送注册信息查询消息，获取设备端对应的传输服务器列表；S302：设备端获取传输服务器列表后，向传输服务器发送注册请求，收到传输服务器注册应答消息后，完成注册；S303：设备端完成向传输服务器注册后，向传输服务器发送心跳消息，传输服务器发送的心跳应答消息中包含传输服务器负载信息，若设备端收到3次服务器过载信息，向注册服务器发送注册查询消息，若传输服务器列表变更，则重新执行初始化流程。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述S4包括步骤：S401：客户端向注册服务器请求查询设备端关联的传输服务器信息；S402：注册服务器返回指定设备的传输服务器信息；S403：客户端向传输服务器发送查询请求；S404：传输服务器向客户端发送查询应答；S405：传输服务器向设备端转发客户端的查询请求；S406：客户端收到传输服务器的应答后，向设备端发送试探消息；S407：设备端收到传输服务器转发的查询请求后，向客户端发送试探消息；S408：若客户端收到设备端的试探消息，客户端发起连接请求；S409：设备端收到客户端连接请求，发送连接请求应答消息，客户端收到连接请求的应答消息，连接建立完成；S410：若客户端超时未收到设备端的试探消息，客户端向转发服务器发起转发连接请求；S411：转发服务器收到转发连接请求，建立转发通道，向设备端发送转发连接请求；S412：设备端收到转发服务器的转发连接请求，发送应答消息；S413：客户端收到转发服务器的转发应答消息，连接建立完成。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述S5包括步骤：S501：当一个传输服务器转发数据量或负载设备较多时，传输服务器向管理服务器发送过载消息；S502：当一个传输服务器转发数据量或负载设备较多时，传输服务器向所有连接的设备端发送负载过高消息；S503：管理服务器将高负载传输服务器下的设备端转移到低负载传输服务器，向注册服务器更新修改后的设备信息列表；S504：设备端多次收到传输服务器的高负载消息后，向注册服务器重新请求设备信息列表以获取新的传输服务器；S505：设备端向新低负载传输服务器迁移。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述S6包括：当传输服务器为某客户端和设备端建立的转发链接停止时，传输服务器资源得到释放，当资源到达低负载阈值时，传输服务器为低负载服务器并向管理服务器发送状态消息，管理服务器将转移部分设备端到所述低负载服务器。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述管理服务器采用标准网站构架设计，分为前端，后端，数据库，前端提供用户配置管理界面，后端完成配置消息处理以及与其他服务器交互数据处理，数据库用于存储设备信息。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述注册服务器提供客户端和设备端查询对应设备的传输服务器关联信息。
- 根据权利要求9所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述注册服务器分为高并发查询服务和更新服务，所述高并发查询服务为客户端和设备端提供查询功能支持，所述更新服务使用http协议与管理服务器交互，获取设备列表和传输服务器列表。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述传输服务器根据设备端数量进行动态调整，当传输服务器负载过大或服务器闲置过多时，管理服务器通过服务器运营商接口进行动态增减传输服务器操作。
- 根据权利要求11所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述传输服务器分为网络穿透，转发服务和更新服务，更新服务功能与注册服务器相同，提供与管理服务器的信息交互。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述客户端以运行库方式提供外部程序调用，通过客户端接口API完成音视频连接的建立传输。
- 根据权利要求1所述的一种应用于音视频数据传输的端到端系统解决方法，其特征在于：所述设备端以运行库方式提供外部程序调用，通过设备端接口API完成音视频连接的建立传输。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111117683.5 | 2021-09-23 | ||
| CN202111117683.5A CN113824723B (zh) | 2021-09-23 | 2021-09-23 | 一种应用于音视频数据传输的端到端系统解决方法 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023046088A1 true WO2023046088A1 (zh) | 2023-03-30 |
Family
ID=78921069
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/120953 WO2023046088A1 (zh) | 2021-09-23 | 2022-09-23 | 一种应用于音视频数据传输的端到端系统解决方法 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113824723B (zh) |
| WO (1) | WO2023046088A1 (zh) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113824723B (zh) * | 2021-09-23 | 2023-12-08 | 上海安威士科技股份有限公司 | 一种应用于音视频数据传输的端到端系统解决方法 |
| US11973824B2 (en) | 2021-09-23 | 2024-04-30 | Shanghai Anviz Technology Co., Ltd. | Method for data transmission of audio and video in end-to-end system |
| CN114268805B (zh) * | 2021-12-23 | 2024-04-02 | 杭州登虹科技有限公司 | 远程快速拉取低功耗设备音视频流的方法 |
| CN115460291B (zh) * | 2022-08-23 | 2023-05-02 | 成都智元汇信息技术股份有限公司 | 一种基于中心配置的组间调度方法、中心服务器及系统 |
| CN116055458B (zh) * | 2023-03-31 | 2023-06-20 | 睿云联(厦门)网络通讯技术有限公司 | 一种物联网云平台设备间的音视频通话方法、设备及介质 |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103442224A (zh) * | 2013-09-09 | 2013-12-11 | 杭州巨峰科技有限公司 | 一种基于nat穿透的视频监控访问策略和实现方法 |
| CN103581740A (zh) * | 2013-10-25 | 2014-02-12 | 中兴通讯股份有限公司 | 一种分布式的iptv多屏网关和iptv多屏互动方法 |
| US20150128199A1 (en) * | 2011-11-10 | 2015-05-07 | Through Tek Technology (ShenZhen) Co., Ltd. | Information concentrating center capable of making p2p connections with remote client devices |
| CN106331115A (zh) * | 2016-08-26 | 2017-01-11 | 深圳市同为数码科技股份有限公司 | 一种支持多台设备连接的分布式可扩展服务器系统 |
| CN207820121U (zh) * | 2018-01-16 | 2018-09-04 | 深圳市安托邦网络科技有限公司 | 一种局域网摄像机进行网络流媒体直播的管理系统 |
| US20190394174A1 (en) * | 2018-06-26 | 2019-12-26 | Arm Limited | Automatic Client Device Registration |
| CN113099252A (zh) * | 2021-03-29 | 2021-07-09 | 浙江工业大学 | 一种基于sip与rtmp的远程投食器视频推送系统 |
| CN113824723A (zh) * | 2021-09-23 | 2021-12-21 | 上海安威士科技股份有限公司 | 一种应用于音视频数据传输的端到端系统解决方法 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107333143B (zh) * | 2017-06-26 | 2020-04-17 | 南京邮电大学 | 5g多接入并发传输控制系统及方法 |
| CN108965779B (zh) * | 2017-11-28 | 2021-07-06 | 视联动力信息技术股份有限公司 | 一种音视频流的传输方法、录播方法、装置及系统 |
-
2021
- 2021-09-23 CN CN202111117683.5A patent/CN113824723B/zh active Active
-
2022
- 2022-09-23 WO PCT/CN2022/120953 patent/WO2023046088A1/zh unknown
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150128199A1 (en) * | 2011-11-10 | 2015-05-07 | Through Tek Technology (ShenZhen) Co., Ltd. | Information concentrating center capable of making p2p connections with remote client devices |
| CN103442224A (zh) * | 2013-09-09 | 2013-12-11 | 杭州巨峰科技有限公司 | 一种基于nat穿透的视频监控访问策略和实现方法 |
| CN103581740A (zh) * | 2013-10-25 | 2014-02-12 | 中兴通讯股份有限公司 | 一种分布式的iptv多屏网关和iptv多屏互动方法 |
| CN106331115A (zh) * | 2016-08-26 | 2017-01-11 | 深圳市同为数码科技股份有限公司 | 一种支持多台设备连接的分布式可扩展服务器系统 |
| CN207820121U (zh) * | 2018-01-16 | 2018-09-04 | 深圳市安托邦网络科技有限公司 | 一种局域网摄像机进行网络流媒体直播的管理系统 |
| US20190394174A1 (en) * | 2018-06-26 | 2019-12-26 | Arm Limited | Automatic Client Device Registration |
| CN113099252A (zh) * | 2021-03-29 | 2021-07-09 | 浙江工业大学 | 一种基于sip与rtmp的远程投食器视频推送系统 |
| CN113824723A (zh) * | 2021-09-23 | 2021-12-21 | 上海安威士科技股份有限公司 | 一种应用于音视频数据传输的端到端系统解决方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113824723A (zh) | 2021-12-21 |
| CN113824723B (zh) | 2023-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2023046088A1 (zh) | 一种应用于音视频数据传输的端到端系统解决方法 | |
| US11030020B2 (en) | Asynchronous handling of service requests | |
| WO2017114017A1 (zh) | 实现负载均衡的计算机设备、系统和方法 | |
| US9641415B2 (en) | Method and system for seamless SCTP failover between SCTP servers running on different machines | |
| US20140068045A1 (en) | Network system and virtual node migration method | |
| WO2020001442A1 (zh) | 一种数据处理方法及相关设备 | |
| US8984114B2 (en) | Dynamic session migration between network security gateways | |
| CN107528891B (zh) | 一种基于WebSocket的自动集群方法及其系统 | |
| US20210337035A1 (en) | Highly available private cloud service | |
| US11303737B2 (en) | Method and device for data transmission | |
| CN116405461A (zh) | 一种数据处理方法、网元设备以及可读存储介质 | |
| US20190306007A1 (en) | Mechanism for rapid network failure detection for faster switch-over in server-to-server applications | |
| CN111414208A (zh) | 应用程序的启动方法、装置及设备 | |
| WO2021184992A1 (zh) | 一种镜像文件的上传方法、相关设备及计算机存储介质 | |
| WO2019011142A1 (zh) | 一种进行网络链路切换的方法和系统 | |
| CN102055605B (zh) | 一种应用于aaa服务器的容灾系统及方法 | |
| US11973824B2 (en) | Method for data transmission of audio and video in end-to-end system | |
| Ramanathan et al. | Demonstration of containerized central unit live migration in 5G radio access network | |
| CN116048538B (zh) | 用于dpu的服务网格部署方法及装置 | |
| US20160261719A1 (en) | Information processing system, control program, and control method | |
| US20220217093A1 (en) | Sequence Number Synchronization Method and Apparatus | |
| CN114143569B (zh) | 一种网页录制和直播方法及系统 | |
| CN110753043B (zh) | 一种通信方法、装置、服务器及介质 | |
| CN113949631A (zh) | 客户端容灾的处理方法、系统及电子设备 | |
| WO2015172320A1 (zh) | 视频缓存切换处理方法、装置和系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22872132 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |